+1 on both. I think the good way of looking at the Chair from PMC side is - a bureaucrat, who's responsible to file board@ reports on time and carry on some other functions like updating PMC records, etc. - a neutral mediator shall any conflicts within the community arise
A good practice which worked in a few of projects is for the current chair to start a [DISCUSS] to nominate a new chair every year or so. If no nominations were made, the current chair simply stays for another periodk Cos On Mon, Oct 12, 2015 at 08:26AM, Jim Jagielski wrote: > I am +1. > > Just for the record: We all need to recall that the Chair is > not indicate some sort of "hierarchy" level in the PMC; that > is, it doesn't mean that the Chair is the "main" developer, > or the "most important person" or even, at some level, the > person "most deserving of respect"... It is easy to confuse > the term Chair or VP of a PMC, which relates to the *foundation* > as someone also being relative to their authority in the *PMC* > (if you catch my drift). > > I know that here in Groovy-land, we all grok this; but it's always > good to add these kinds of reminders :)
signature.asc
Description: Digital signature
