Update Working Committee elections date
This is not accurate to the current elections process. This should fix it. We can amend later with the next election process if necessary. Change-Id: I1686aae3aa69a88340e33d32634debb7b63535b3
This commit is contained in:
parent
a668248c4b
commit
a54988be84
|
@ -111,7 +111,7 @@ appoint a Lead at their own discretion and using their own process to help be a
|
|||
Representatives are expected to be active contributors who are committed to the health and success of the project. It is
|
||||
comprised of 5 members, who are elected by an election process.
|
||||
|
||||
Working Committee elections take place once in June (5 seats available). Anyone who is a Contributor (as defined above)
|
||||
Working Committee elections take place in August (5 seats available). Anyone who is a Contributor (as defined above)
|
||||
before the election will be eligible to run. Core Reviewers of projects will be eligible to vote. There are no term
|
||||
limits, but in order to encourage diversity, no more than 2 of the 5 seats can be filled by any one organization. The
|
||||
Working Committee will meet regularly in an open forum with times and locations published in
|
||||
|
@ -138,4 +138,4 @@ their position.
|
|||
The project’s formal governance document is maintained in the [airship-governance](https://opendev.org/airship/governance)
|
||||
repository. Changes to the document can be proposed by any project Contributor but would need to be ratified by the
|
||||
Working Committee with a super-majority (2/3rds) vote. The Working Committee should strive for consensus for any change
|
||||
to the project’s formal governance.
|
||||
to the project’s formal governance.
|
||||
|
|
Loading…
Reference in New Issue