Justin, you're trying too hard. It feels like you're pushing Alex out. You keep referring to our guidelines, so here is the relevant part (emphasis mine):
"The term of chair is for one one year or UNTIL THEY RETIRE. After one year THE CHAIR CAN ELECT TO STAND FOR ANOTHER YEAR or a vote by the PMC be taken for a new chair." Alex just indicated that he doesn't intend to retire, thereby electing to stand for another year. Now, that same rule says you can call a vote to remove Alex from office and take the seat yourself, sure. But I don't think that would be in the best interest of the project and the best interest of the project should be the prime directive for a (would be) chair... EdB On Tue, Dec 3, 2013 at 12:51 AM, Justin Mclean <jus...@classsoftware.com> wrote: > Hi, > >> Hmm. Maybe there's need for some improvement to the guideline's wording. >> It really should only be my call to say if I don't want to continue in the >> role and up to the PMC with community input as to whether I should >> continue if I'm willing to do so (which I am). > > Sorry but I have to disagree there. Back when we first discussed the bylaws > (now guidelines) and what the chairs term should be consensus was that the > chair should be for a year/reviewed every year. A lot of other Apache > projects use the one year term for chairs [1][2][3][4] (+ more) - although > the exact wording/rules vary a little. IMO having the chair commit to the > role for a year (every year) is important - as is having the role rotated. > > You can certainly propose a change to the guidelines and have it voted on if > you want it changed. > > Thanks, > Justin > > 1. https://cloudstack.apache.org/bylaws.html > 2. http://pig.apache.org/bylaws.html > 3. http://wiki.apache.org/jclouds/Bylaws > 4. http://ant.apache.org/bylaws.html -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
