You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@magpie.apache.org by Jarek Potiuk <ja...@potiuk.com> on 2026/05/25 07:49:51 UTC
[DISCUSS] Governance after becoming TLP
Hello everyone,
It’s great to be working with such an experienced group of ASF members, and
a warm welcome to those who are newer to our community! While we all know
the general ropes, every project has its own unique rhythm. I’ve included
some helpful links regarding ASF governance, but I would love for us to
chat about how we want to shape our own path forward.
As I transition from my initial "Benevolent Dictator" role to PMC chair,
I’m really looking forward to hearing your perspectives. I have some
thoughts, but I’m much more interested in the collective vibe of the group!
Here are a few friendly topics for us to explore:
1) Criteria for new Committers/PMC members: Should we lean toward a more
relaxed approach for newcomers, or maintain stricter bars due to our
architecture? I'd love to hear your thoughts on what qualities we should
value most.
2) Valuing all contributions: Since so much of our work involves logic and
language, the line between "code" and "non-code" is beautifully blurred. Do
you think we should have distinct criteria for different types of help, or
should we celebrate all contributions under one umbrella?
3) Review processes (CTR vs. RTC): We’ve been moving fast lately to get
Magpie ready, primarily using Commit-Then-Review. As we settle into a more
sustainable pace, would you prefer to stick with that or try
Review-Then-Commit? Given how much AI open ways to have more PRs, it can
assist our reviews (and dogfooding the process of making it efficient
should be really helpful to make this part of Magpie right), I’m curious
what feels right to you.
4) Voting Rights: How would you like to structure voting for the PMC and
committers? Some projects prefer to keep these roles separate, while others
combine them—I'm open to whatever feels most inclusive for us.
5) Mailing List Volume: I’ve redirected PR notifications to the dev-list
for archiving purposes. If this feels like too much noise, please let me
know what is and is not useful! We can easily adjust to keep our
communication clear and helpful.
I’m so appreciative of everyone’s time and dedication. Please share your
thoughts on these points or any other governance ideas you might have!
Best,
Jarek
Some links for those who are not yet familiar with Apache Way:
[1] Apache Voting Process https://www.apache.org/foundation/voting.html
[2] Apache Community development https://community.apache.org/
[3] Apche Developer Information https://www.apache.org/dev/
[4] ASF Governance primer https://www.apache.org/foundation/governance/
Re: [DISCUSS] Governance after becoming TLP
Posted by Craig Russell <ap...@gmail.com>.
Just a few comments...
> On May 25, 2026, at 00:49, Jarek Potiuk <ja...@potiuk.com> wrote:
>
> Hello everyone,
>
> It’s great to be working with such an experienced group of ASF members, and
> a warm welcome to those who are newer to our community! While we all know
> the general ropes, every project has its own unique rhythm. I’ve included
> some helpful links regarding ASF governance, but I would love for us to
> chat about how we want to shape our own path forward.
>
> As I transition from my initial "Benevolent Dictator" role to PMC chair,
> I’m really looking forward to hearing your perspectives. I have some
> thoughts, but I’m much more interested in the collective vibe of the group!
>
> Here are a few friendly topics for us to explore:
>
> 1) Criteria for new Committers/PMC members: Should we lean toward a more
> relaxed approach for newcomers, or maintain stricter bars due to our
> architecture? I'd love to hear your thoughts on what qualities we should
> value most.
I consider this project to be a high risk high reward project which affects my views on this and other items below. If we value contributors' input enough to make them committers, I feel they deserve to be PMC members as well.
>
> 2) Valuing all contributions: Since so much of our work involves logic and
> language, the line between "code" and "non-code" is beautifully blurred. Do
> you think we should have distinct criteria for different types of help, or
> should we celebrate all contributions under one umbrella?
All contributions that move the project forward are of value.
>
> 3) Review processes (CTR vs. RTC): We’ve been moving fast lately to get
> Magpie ready, primarily using Commit-Then-Review. As we settle into a more
> sustainable pace, would you prefer to stick with that or try
> Review-Then-Commit? Given how much AI open ways to have more PRs, it can
> assist our reviews (and dogfooding the process of making it efficient
> should be really helpful to make this part of Magpie right), I’m curious
> what feels right to you.
This is one of those risk/reward things. I'd feel more comfortable requiring that every PR is reviewed before merging.
>
> 4) Voting Rights: How would you like to structure voting for the PMC and
> committers? Some projects prefer to keep these roles separate, while others
> combine them—I'm open to whatever feels most inclusive for us.
My preference is for committer==PMC member so this is moot.
>
> 5) Mailing List Volume: I’ve redirected PR notifications to the dev-list
> for archiving purposes. If this feels like too much noise, please let me
> know what is and is not useful! We can easily adjust to keep our
> communication clear and helpful.
Yes, please keep discussions on dev and send merges and new issues separately.
Craig
>
> I’m so appreciative of everyone’s time and dedication. Please share your
> thoughts on these points or any other governance ideas you might have!
>
> Best,
> Jarek
>
> Some links for those who are not yet familiar with Apache Way:
>
> [1] Apache Voting Process https://www.apache.org/foundation/voting.html
> [2] Apache Community development https://community.apache.org/
> [3] Apche Developer Information https://www.apache.org/dev/
> [4] ASF Governance primer https://www.apache.org/foundation/governance/
Craig L Russell
clr@apache.org
Re: [DISCUSS] Governance after becoming TLP
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi.
Thanks for kicking this off so thoughtfully. Great to see these questions on the table early; getting alignment here will save friction later.
A few thoughts from my side:
1) Committer/PMC criteria: I'd lean toward the Apache Way standard of demonstrated merit rather than a strict technical bar. Given Magpie's nature, merit should be interpreted broadly from the start. Contributing a well-crafted SKILL file, improving documentation, or supporting the community is just as valuable as writing code.
2) Valuing all contributions: One umbrella makes sense here, and it fits naturally with how Magpie already works. Many meaningful contributions to this project don't involve writing code at all, so building that recognition in from the start seems right.
3) CTR vs RTC: I'm fairly relaxed about this one given that the project is already building AI guardrails for new SKILLs and has test coverage for most of them. That safety net changes the calculus a bit compared to a typical project. CTR with those checks in place seems workable, but RTC is still a useful default for more significant changes.
4) Voting rights: I'd suggest keeping PMC and committer roles distinct in terms of binding votes, following the standard Apache model. PMC members hold binding votes on releases and key decisions; committers have voice but non-binding votes.
5) Mailing list volume: A separate notifications@ or commits@ list for PR traffic is a pretty common and clean solution. Keeps dev@ focused on discussion and decisions, which makes it easier to stay on top of what actually needs attention.
Thanks again for setting a collaborative tone from the start.
Kind Regards,
Justin
Re: [DISCUSS] Governance after becoming TLP
Posted by Richard Zowalla <rz...@apache.org>.
Hi Jarek, all,
A few quick thoughts from my side:
1) Thanks for cutting the noise on the list! Just worked through a phone full of new mails to digest ;-)
2) I really like Yeonguk's idea of using Magpie itself to help manage Magpie - would be a great real-world use case and good dogfooding for the project.
3) On CTR vs RTC: I personally lean RTC, but I can live with CTR depends a bit on the pace we end up settling into.
Gruß
Richard
> Am 25.05.2026 um 18:20 schrieb Jarek Potiuk <ja...@potiuk.com>:
>
> Quick one: I will disable commits for now (move them back to commit@) ..
> They are ALREADY noisy::)
>
> On Mon, May 25, 2026 at 1:32 PM Yeonguk Choo <ch...@apache.org> wrote:
>
>> Hi, Jarek,
>> Thanks for starting this discussion.
>>
>> I’d also like to share a few thoughts from my side.
>>
>> 1. Committer / PMC criteria:
>> Like Justin mentioned, I also think it makes sense to focus more on
>> demonstrated merit rather than purely technical contributions.
>> However, given the architectural nature of the project, I believe it is
>> also important for contributors to understand how the overall system and
>> workflows fit together.
>>
>> Additionally, considering the likelihood that AI-assisted contributions
>> will increase significantly in this project over time, I think it makes
>> sense to maintain some level of standard around trust and understanding.
>>
>> 2. Valuing all contributions:
>> I also agree with recognizing different forms of contribution under the
>> same umbrella.
>> However, in terms of impact, I believe there are contributions that can
>> significantly influence usability, project direction, and the overall user
>> experience, even if the line between code and non-code becomes blurry.
>>
>> 3. CTR vs RTC:
>> Regarding CTR vs RTC, I’m also fairly flexible on this point. Personally,
>> I think it could be both interesting and valuable to adopt Magpie itself to
>> help manage Magpie.
>>
>> I also believe that dogfooding can genuinely help improve the project, and
>> I like the idea of the project itself becoming a real-world use case for
>> the project.
>>
>> At that point, maybe it becomes MTC(Magpie Then Commit) or MTR(Magpie Then
>> Review) instead :)
>>
>> 4. Voting rights:
>> For this point, I think following the standard Apache-recommended model
>> would be the most natural approach.
>>
>> 5. Mailing lists:
>> I also agree with Justin’s opinion here. Separating dev@ and commits@
>> seems like a clean and practical approach.
>>
>> Thanks,
>> Yeonguk
>>
>> On 2026/05/25 07:49:51 Jarek Potiuk wrote:
>>> Hello everyone,
>>>
>>> It’s great to be working with such an experienced group of ASF members,
>> and
>>> a warm welcome to those who are newer to our community! While we all know
>>> the general ropes, every project has its own unique rhythm. I’ve included
>>> some helpful links regarding ASF governance, but I would love for us to
>>> chat about how we want to shape our own path forward.
>>>
>>> As I transition from my initial "Benevolent Dictator" role to PMC chair,
>>> I’m really looking forward to hearing your perspectives. I have some
>>> thoughts, but I’m much more interested in the collective vibe of the
>> group!
>>>
>>> Here are a few friendly topics for us to explore:
>>>
>>> 1) Criteria for new Committers/PMC members: Should we lean toward a more
>>> relaxed approach for newcomers, or maintain stricter bars due to our
>>> architecture? I'd love to hear your thoughts on what qualities we should
>>> value most.
>>>
>>> 2) Valuing all contributions: Since so much of our work involves logic
>> and
>>> language, the line between "code" and "non-code" is beautifully blurred.
>> Do
>>> you think we should have distinct criteria for different types of help,
>> or
>>> should we celebrate all contributions under one umbrella?
>>>
>>> 3) Review processes (CTR vs. RTC): We’ve been moving fast lately to get
>>> Magpie ready, primarily using Commit-Then-Review. As we settle into a
>> more
>>> sustainable pace, would you prefer to stick with that or try
>>> Review-Then-Commit? Given how much AI open ways to have more PRs, it can
>>> assist our reviews (and dogfooding the process of making it efficient
>>> should be really helpful to make this part of Magpie right), I’m curious
>>> what feels right to you.
>>>
>>> 4) Voting Rights: How would you like to structure voting for the PMC and
>>> committers? Some projects prefer to keep these roles separate, while
>> others
>>> combine them—I'm open to whatever feels most inclusive for us.
>>>
>>> 5) Mailing List Volume: I’ve redirected PR notifications to the dev-list
>>> for archiving purposes. If this feels like too much noise, please let me
>>> know what is and is not useful! We can easily adjust to keep our
>>> communication clear and helpful.
>>>
>>> I’m so appreciative of everyone’s time and dedication. Please share your
>>> thoughts on these points or any other governance ideas you might have!
>>>
>>> Best,
>>> Jarek
>>>
>>> Some links for those who are not yet familiar with Apache Way:
>>>
>>> [1] Apache Voting Process https://www.apache.org/foundation/voting.html
>>> [2] Apache Community development https://community.apache.org/
>>> [3] Apche Developer Information https://www.apache.org/dev/
>>> [4] ASF Governance primer https://www.apache.org/foundation/governance/
>>>
>>
Re: [DISCUSS] Governance after becoming TLP
Posted by Jarek Potiuk <ja...@potiuk.com>.
Quick one: I will disable commits for now (move them back to commit@) ..
They are ALREADY noisy::)
On Mon, May 25, 2026 at 1:32 PM Yeonguk Choo <ch...@apache.org> wrote:
> Hi, Jarek,
> Thanks for starting this discussion.
>
> I’d also like to share a few thoughts from my side.
>
> 1. Committer / PMC criteria:
> Like Justin mentioned, I also think it makes sense to focus more on
> demonstrated merit rather than purely technical contributions.
> However, given the architectural nature of the project, I believe it is
> also important for contributors to understand how the overall system and
> workflows fit together.
>
> Additionally, considering the likelihood that AI-assisted contributions
> will increase significantly in this project over time, I think it makes
> sense to maintain some level of standard around trust and understanding.
>
> 2. Valuing all contributions:
> I also agree with recognizing different forms of contribution under the
> same umbrella.
> However, in terms of impact, I believe there are contributions that can
> significantly influence usability, project direction, and the overall user
> experience, even if the line between code and non-code becomes blurry.
>
> 3. CTR vs RTC:
> Regarding CTR vs RTC, I’m also fairly flexible on this point. Personally,
> I think it could be both interesting and valuable to adopt Magpie itself to
> help manage Magpie.
>
> I also believe that dogfooding can genuinely help improve the project, and
> I like the idea of the project itself becoming a real-world use case for
> the project.
>
> At that point, maybe it becomes MTC(Magpie Then Commit) or MTR(Magpie Then
> Review) instead :)
>
> 4. Voting rights:
> For this point, I think following the standard Apache-recommended model
> would be the most natural approach.
>
> 5. Mailing lists:
> I also agree with Justin’s opinion here. Separating dev@ and commits@
> seems like a clean and practical approach.
>
> Thanks,
> Yeonguk
>
> On 2026/05/25 07:49:51 Jarek Potiuk wrote:
> > Hello everyone,
> >
> > It’s great to be working with such an experienced group of ASF members,
> and
> > a warm welcome to those who are newer to our community! While we all know
> > the general ropes, every project has its own unique rhythm. I’ve included
> > some helpful links regarding ASF governance, but I would love for us to
> > chat about how we want to shape our own path forward.
> >
> > As I transition from my initial "Benevolent Dictator" role to PMC chair,
> > I’m really looking forward to hearing your perspectives. I have some
> > thoughts, but I’m much more interested in the collective vibe of the
> group!
> >
> > Here are a few friendly topics for us to explore:
> >
> > 1) Criteria for new Committers/PMC members: Should we lean toward a more
> > relaxed approach for newcomers, or maintain stricter bars due to our
> > architecture? I'd love to hear your thoughts on what qualities we should
> > value most.
> >
> > 2) Valuing all contributions: Since so much of our work involves logic
> and
> > language, the line between "code" and "non-code" is beautifully blurred.
> Do
> > you think we should have distinct criteria for different types of help,
> or
> > should we celebrate all contributions under one umbrella?
> >
> > 3) Review processes (CTR vs. RTC): We’ve been moving fast lately to get
> > Magpie ready, primarily using Commit-Then-Review. As we settle into a
> more
> > sustainable pace, would you prefer to stick with that or try
> > Review-Then-Commit? Given how much AI open ways to have more PRs, it can
> > assist our reviews (and dogfooding the process of making it efficient
> > should be really helpful to make this part of Magpie right), I’m curious
> > what feels right to you.
> >
> > 4) Voting Rights: How would you like to structure voting for the PMC and
> > committers? Some projects prefer to keep these roles separate, while
> others
> > combine them—I'm open to whatever feels most inclusive for us.
> >
> > 5) Mailing List Volume: I’ve redirected PR notifications to the dev-list
> > for archiving purposes. If this feels like too much noise, please let me
> > know what is and is not useful! We can easily adjust to keep our
> > communication clear and helpful.
> >
> > I’m so appreciative of everyone’s time and dedication. Please share your
> > thoughts on these points or any other governance ideas you might have!
> >
> > Best,
> > Jarek
> >
> > Some links for those who are not yet familiar with Apache Way:
> >
> > [1] Apache Voting Process https://www.apache.org/foundation/voting.html
> > [2] Apache Community development https://community.apache.org/
> > [3] Apche Developer Information https://www.apache.org/dev/
> > [4] ASF Governance primer https://www.apache.org/foundation/governance/
> >
>
Re: [DISCUSS] Governance after becoming TLP
Posted by Yeonguk Choo <ch...@apache.org>.
Hi, Jarek,
Thanks for starting this discussion.
I’d also like to share a few thoughts from my side.
1. Committer / PMC criteria:
Like Justin mentioned, I also think it makes sense to focus more on demonstrated merit rather than purely technical contributions.
However, given the architectural nature of the project, I believe it is also important for contributors to understand how the overall system and workflows fit together.
Additionally, considering the likelihood that AI-assisted contributions will increase significantly in this project over time, I think it makes sense to maintain some level of standard around trust and understanding.
2. Valuing all contributions:
I also agree with recognizing different forms of contribution under the same umbrella.
However, in terms of impact, I believe there are contributions that can significantly influence usability, project direction, and the overall user experience, even if the line between code and non-code becomes blurry.
3. CTR vs RTC:
Regarding CTR vs RTC, I’m also fairly flexible on this point. Personally, I think it could be both interesting and valuable to adopt Magpie itself to help manage Magpie.
I also believe that dogfooding can genuinely help improve the project, and I like the idea of the project itself becoming a real-world use case for the project.
At that point, maybe it becomes MTC(Magpie Then Commit) or MTR(Magpie Then Review) instead :)
4. Voting rights:
For this point, I think following the standard Apache-recommended model would be the most natural approach.
5. Mailing lists:
I also agree with Justin’s opinion here. Separating dev@ and commits@ seems like a clean and practical approach.
Thanks,
Yeonguk
On 2026/05/25 07:49:51 Jarek Potiuk wrote:
> Hello everyone,
>
> It’s great to be working with such an experienced group of ASF members, and
> a warm welcome to those who are newer to our community! While we all know
> the general ropes, every project has its own unique rhythm. I’ve included
> some helpful links regarding ASF governance, but I would love for us to
> chat about how we want to shape our own path forward.
>
> As I transition from my initial "Benevolent Dictator" role to PMC chair,
> I’m really looking forward to hearing your perspectives. I have some
> thoughts, but I’m much more interested in the collective vibe of the group!
>
> Here are a few friendly topics for us to explore:
>
> 1) Criteria for new Committers/PMC members: Should we lean toward a more
> relaxed approach for newcomers, or maintain stricter bars due to our
> architecture? I'd love to hear your thoughts on what qualities we should
> value most.
>
> 2) Valuing all contributions: Since so much of our work involves logic and
> language, the line between "code" and "non-code" is beautifully blurred. Do
> you think we should have distinct criteria for different types of help, or
> should we celebrate all contributions under one umbrella?
>
> 3) Review processes (CTR vs. RTC): We’ve been moving fast lately to get
> Magpie ready, primarily using Commit-Then-Review. As we settle into a more
> sustainable pace, would you prefer to stick with that or try
> Review-Then-Commit? Given how much AI open ways to have more PRs, it can
> assist our reviews (and dogfooding the process of making it efficient
> should be really helpful to make this part of Magpie right), I’m curious
> what feels right to you.
>
> 4) Voting Rights: How would you like to structure voting for the PMC and
> committers? Some projects prefer to keep these roles separate, while others
> combine them—I'm open to whatever feels most inclusive for us.
>
> 5) Mailing List Volume: I’ve redirected PR notifications to the dev-list
> for archiving purposes. If this feels like too much noise, please let me
> know what is and is not useful! We can easily adjust to keep our
> communication clear and helpful.
>
> I’m so appreciative of everyone’s time and dedication. Please share your
> thoughts on these points or any other governance ideas you might have!
>
> Best,
> Jarek
>
> Some links for those who are not yet familiar with Apache Way:
>
> [1] Apache Voting Process https://www.apache.org/foundation/voting.html
> [2] Apache Community development https://community.apache.org/
> [3] Apche Developer Information https://www.apache.org/dev/
> [4] ASF Governance primer https://www.apache.org/foundation/governance/
>