Cool. Some comments. Side 5
PMC Chairs are Vice Presidents of the project and officers of the Foundation. Slide 8 In my opinion, Vendor Neutrality is either a 4th Pillar, the Foundation, or an adjunct to the “How It Works”. I’m not sure which metaphor is best, but the topic should be covered. Slide 12 In the Incubator we like to guide podlings to delay users@ until there is a proven need. Reason is that having just dev@ can be important to all interested devs and new users to their experience with the code and developing community. Also, you don’t mention commits@ where most project direct various code changes and other logging. The usual impetus for that that dev@ is getting hammered with these emails. That said the PMC is expected to subscribe to and follow a commits@ mailing list. Slide 13 If the PMC Chair is negligent in reporting duties to the Board then the other PMC members can step in and submit the quarterly board report. Beyond the duty to the foundation as an officer PMC Chairs have no more responsibilities or rights than the other PMC members. In a sense their duties are more secretarial than leadership. The ASF goes for a flat hierarchy as much as feasible. ASF Members do not vote on new Incubator podlings. It works as so (currently) - any member can join the Incubator PMC. The Incubator PMC can also elect PMC members from people that they have identified as knowledgeable on the Apache Way (and likely candidates for Apache Membership at the next annual meeting (recently in March)). Slide 16 You miss voting on new committers and PMC members which is technically your “Majority Approval” but culturally is better as “Consensus Approval”. I think that the distinction between the two is not so much as you describe. It is more that “Consensus” is preferred, but sometimes “Majority” is what you get. I think that others will want to debate this point. Slide 20 Should the escalation point be the code of conduct? That does offer a concrete ML to escalate towards. Slide 21 I think your description of a PMC member applies to Committers as well. For PMC members I would discuss binding votes on releases, approving new committers and PMC members and managing the project brand. I’m sure that lis tis incomplete. Sorry, this is way more wordy than I intended. Take it as you wish. Regards, Dave > On Jan 21, 2019, at 8:20 PM, Aizhamal Nurmamat kyzy > <aizha...@google.com.INVALID> wrote: > > Hello everyone, > > I recently shared a slide deck with an introduction to "The Apache Way" in > this mailing list. I've got some very valuable feedback from community > members, and I have incorporated some into the slides. The updated deck is > here: > > https://docs.google.com/presentation/d/183nXPAxpJymQBOYOt1FnFaahRcQskIvOyIvHRC6UAnE/edit#slide=id.p > <https://docs.google.com/presentation/d/183nXPAxpJymQBOYOt1FnFaahRcQskIvOyIvHRC6UAnE/edit#slide=id.p> > > The material is intended to be used by anyone for their presentations. I am > not a committer, but I was wondering if it would be of decent enough > quality to be included in the slides section[2]? If it is, is there a > committer in this group that could help me do that change? > > Thanks to everyone for your help and feedback! > -A. > > [1] > https://docs.google.com/presentation/d/183nXPAxpJymQBOYOt1FnFaahRcQskIvOyIvHRC6UAnE/edit#slide=id.p > <https://docs.google.com/presentation/d/183nXPAxpJymQBOYOt1FnFaahRcQskIvOyIvHRC6UAnE/edit#slide=id.p> > [2] https://community.apache.org/speakers/slides.html > > -- --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
