Thanx Shane for the clarification, makes sense to me!!! -Ayush
> On 31-Jul-2023, at 4:03 PM, Shane Curcuru <a...@shanecurcuru.org> wrote: > > Ayush Saxena wrote on 7/30/23 2:49 PM: >> Hi Shane, >> Thanx for the work, Read it & it is really very helpful!!! > > Yay! Someone actually read it! > >> Just two minor doubts or confusion: >> First, >>> Chairs are responsible for sharing any Board feedback with your PMC >> Doesn't the feedback come directly to the PMC & anyone from the PMC can >> answer? >> Context: There was an email from Rich to all dev lists [1] which read: >> ``` >> Every PMC member can, and should, respond when the Board sends email >> to your private list. You should not wait for the PMC Chair to >> respond. The Board views the entire PMC as responsible for the >> project, not just one member. >> ``` > > Both are true. The whole PMC should feel empowered to help oversee the > project, including answering any board questions. But the board holds the > chair personally responsible for making sure board questions are answered. > Otherwise, we sometimes get the case where the committee of many people each > assume someone else is handling it, and questions never get answered. > > In particular, the board will sometimes replace the chair when a project's > reports or answers aren't sufficient. That's generally either a sign that > "Hey, your PMC *really* needs to shape up your projects", and the board tells > the PMC to pick a new chair who's more active (this sometimes happens when > the chair changes jobs or goes away). > >> Second, >>> While any PMC member can handle some PMC updates, in some cases only the >>> Chair may have permissions to make roster updates. >> This sounds a little bit incomplete, What are some of those cases? Can >> we link that as well. Most of the things any member can handle via >> Whimsy - apache id creation AFAIK > > Both are true. The purpose of this specific bit of content is to only have > the minimal required/recommended setup steps for becoming a new Chair. > Everything else - like what those cases are - should be documented on the > existing /dev/pmc.html page. > > Does that make sense? > > -- > - Shane > ComDev PMC > The Apache Software Foundation > >> -Ayush >> [1] https://lists.apache.org/thread/xyfpw41m65wrk3ftds4jtvyzjoxhtx70 >>> On Mon, 31 Jul 2023 at 00:04, Shane Curcuru <a...@shanecurcuru.org> wrote: >>> >>> I plan to update the email and how-to information we provide to new PMC >>> members. Please comment or make any factual corrections on the wiki: >>> >>> >>> https://cwiki.apache.org/confluence/display/COMDEV/PMC+Chair+Onboarding+Change+Proposal >>> >>> I'll be working with M&P to see where this fits on the a.o/dev tree. >>> >>> -- >>> - Shane >>> ComDev PMC >>> The Apache Software Foundation > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
