Just a few comments... > On May 25, 2026, at 00:49, Jarek Potiuk <[email protected]> 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 [email protected]
