Table of Contents

Election process revision proposal

There have been a number of flags raised around the first committer elections for the board, and the proposed election process for "committer seats" and the chair of the TSC. The goal of this page is to draft an alternate proposal, which will cover guidelines for running elections and proposed by-laws changes to be considered and voted by the board.

Problem statement

Some of the concerns which have been raised are:

Proposed process

Proposal 1: "Active Technical Contributor"

I propose adopting the following processes for member board elections:

OPNFV is a "mid-stream" project - many of the most beneficial activities in our community are not source code related (or, at least, not in the OPNFV project), so this is the wrong metric to use. In addition, different projects have different bars for commit access, or do not maintain the committer lists with the same dilligence, and I would expect voting rights to be set to some objective level of participation. Using the committer lists also puts the burden of maintaining the voting list to project maintainers (via the INFO files) and as the number of maintainers grows with the number of projects, the risk of disenfranchising community members by omission grows.

We will soon have community metrics we can use to measure participation in other areas, and we should use these to define voting rights.

Proposal 2: Community election process

Publication of election results

For all OPNFV community elections full (anonymized) results are published to allow independent verification of the results.

Community board member election

Community TSC member election

(this is according to current bylaws and aligned with the proposed process, assuming we would aim at the same election cadence even if we don't start there.)

TSC Chairperson election