Time flies and the Jenkins elections period are coming.
We already had two successful editions in a row. I want us to continue on that path.
This is a tremendous opportunity for community members to influence the direction of the project for the next two years.
To make this year’s election even better, I am proposing to leverage our new community platform aka community.jenkins.io and I am looking for feedback.
I would like your feedback on the following plan.
To participate in the election, we ask every Jenkins community member to have an account on community.jenkins.io.
You can either reuse your Github account or create a new discourse account specific to community.jenkins.io.
The second requirement is to be able to showcase at least one contribution done before the first of September 2021.
As mentioned on www.jenkins.io/participate/, they are many different ways to contribute to Jenkins and for many of them, it’s very difficult to measure.
Therefore we’ll trust participants and will not require that they provide evidence of contribution as part of their voter registration. We reserve the right to ban the specific account from the election process if we identify abuse.
The election would then work in three stages:
.1 Identify voters and nominees
.2 Voting period
.3 Announce results
To invite participants to vote, we need a list of email’s addresses that we would share with civs.cs.cornell.edu
Therefore we ask every community members who match the requirement to join the group election-voter on discourse election-voter.
The group will be open for joining during the registration period after we’ll close registration during the voting period.
To retrieve emails from the “election-voter” group members, we’ll need to play a little bit with discourse API.
During the same timeframe, we’ll ask every community member to nominate candidates by sending a message to the group election-committee.
Once the nomination period is over, we’ll notify every nominee and get confirmation that they are interested in running as a candidate.
Everybody can nominate an individual for specific positions.
Once voters and candidates are identified, we’ll invite everybody to vote using civs.cs.cornell.edu
As soon as we have the election results, we’ll publish them.
Elected members will officially be the new officer/board member on the 3rd of December 2021.
I see the timeline as follow:
- Collecting feedback regarding the new process.
- Board members validate the new election procedure during the governance meeting
- Announcement on
- Dev mailing list
- Start of the voter registration process.
- Start of the nomination process.
- Closing Nomination Period
- Candidates are announced
- Closing registration period
- Every voter receive an email with a link to https://civs.cs.cornell.edu/
- Closing Voting Period
- Results announce
- Nominees are referenced via the private group election-committee
- Voters register for election using the public group election-voter
- Nobody can register for the election once we send invitations to civs.cs.cornell.edu
- Once the election is over, every member of the group “election-voter” will get a badge on https://community.jenkins.io as a “2021 Election Participant”
- Once the election is over, every nominee will get the badge “2021 Election Nominee”
Any questions or suggestions?
I would like to submit this proposal for approval during the next Governance meeting which will be on the 8th of September so please provide your feedback before that date.