Hi all, Strong +1 from me for having an election. The board election issue was already a really visible issue in 2015 when we had a discussion of the board election process. The Board Election Process <https://wiki.jenkins.io/display/JENKINS/Board+Election+Process> referenced by Tracy was an outcome of months of discussions in the community. The process was signed off by the governance meeting though many current key contributors were not in the community in 2015. The vote itself has never happened due to the voting system implementation issues, but there was a strong consensus that we do need an election. In 2019 it is even more needed IMHO, just few reasons:
- The current Jenkins board includes 3 people, but one is completely inactive in the community. So we are down to two, which is a pretty bad bus factor for a project of the Jenkins' size. Kohsuke and Tyler have a lot of commitments in the project and IRL, so having more board members would definitely improve the board's bandwidth - Some critical processes in the Jenkins project are either stalled or defunct: regular Governance meetings, JEPs, officer reelections, etc. Having an active Jenkins board is instrumental to reviving these processes - Migration to CDF requires a lot of changes in the project: infrastructure and service accounts handover, trademark approval process, etc. It would require extra capacity from the board to coordinate the effort and to get it over the line. Jenkins has joined CDF almost 1 year ago, but there are still A LOT of open questions about the migration to CDF - Lack of Technical Steering Committee in Jenkins, it is one of the stories we were originally discussing for "Jenkins Software Foundation" at the at Jenkins World 2017. Having an active Jenkins board would be a precondition to make this steering committee happen. IMHO we desperately need it to work on the Jenkins evolution in the CDF environment where we will need to facilitate contributions from individual contributors and company contributors. A steering committee would be really helpful to make it happen The proposed schedule is pretty tight assuming that the target Governance meeting will happen in Sep 11, but I believe we can make it work if there is a consensus. The Board Election Process <https://wiki.jenkins.io/display/JENKINS/Board+Election+Process> defined in 2015 still looks pretty solid in 2019, so we could start there. I also agree with the changes proposed by Tracy. Some other questions to answer in the discussion: - *How many board members do we want to elect?* We are supposed to elect only 2 board members at once, but, If we follow the 2015 process, 2-year terms are long expired. So we can vote for 2, 3 (assuming that Dean Yu is inactive) or 4 (if Tyler wants to step down) board members.My suggestion would be to elect 2 or 3 board members so that we have a smooth transition from the current state - *Allowing amendments?* Do we want to use the meeting on Sep 11 to vote for suggested amendments to the process like it happened in 2015? I would vote for doing so so that all contributors have an opportunity to suggest a change and to integrate it into the final process. Please review the above and share your thoughts. Ideally we discuss now > with the goal of reaching consensus by the next governance meeting on > August 11th when we can finalize/ratify the proposal. > I think our main goal is to have a consensus about the elections happening and about the timeline. For the technical implementation of the voting system and process we have a bit more time, because the system will be used only on Oct 14. It gives us a bit more time to discuss options and to test the voting system (e.g. by voting for a best Jenkins logo or other similar fun tooic? :) ). Best regards, Oleg On Wednesday, September 4, 2019 at 10:38:22 PM UTC+2, Tracy Miranda wrote: > > Hi all, > > As you may or may not know Jenkins project is run by a Governance Board > with support from a set of Officers. > > While a process has been set out for elections we are overdue an election. > With Jenkins moving from SPI to CDF > <https://jenkins.io/blog/2019/03/12/cdf-launch/> the timing is good to do > this. CD.Foundation is a multi-project foundation with corporate sponsors > and various oversight bodies. The nature of the foundation means we need to > ensure good channels for communications and a robust operating model. > > With that in mind I am proposing the following set of dates for running a > new elections. The election process will be bootstrapped by the existing > board and we will request CDF run and supervise the election using the The > Condorcet Internet voting system <https://civs.cs.cornell.edu/>. > > Please review the proposal below and links outlining the process for new > board and officer elections. > > 2019 Election Schedule > > (Proposed): > > 13 September, 2019: Nominations open. To nominate someone, send an email > to [email protected] <javascript:> > > 4 October, 2019: Nominations close > > 8 October, 2019: List of nominees posted to (mailing list) > > 11 October, 2019: Nominees’ personal statements made available > > 14 October, 2019: Voting begins > > 27 October, 2019: Voting closes 5pm Pacific Time > > 4 November, 2019: New representatives announced > > For voting eligibility I propose we generally stick with the process > outlined in the Board Election Process > <https://wiki.jenkins.io/display/JENKINS/Board+Election+Process> with the > following specific modifications: > > > - cut-off date for voter eligibility being September 1st 2019. > - I would also like to propose that any Jenkins contributor who does > not meet the eligibility criteria but is a community contributor can also > register to vote by writing to the existing board of directors. (as I have > been made aware of a subset of contributors who potentially fall in this > category) > > > Please review the above and share your thoughts. Ideally we discuss now > with the goal of reaching consensus by the next governance meeting on > August 11th when we can finalize/ratify the proposal. > > If you are happy with the proposal I hope you will consider putting > yourself forward for one of the positions. > > Regards, > Tracy > > > > > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/bc30b00e-594a-4d68-bbd7-88a412f20720%40googlegroups.com.
