Call for Agreement: OKD WG Charter (Revised Proposal) #3
Conversation
openshift-ci-robot
added
the
size/L
|
accept |
3 similar comments
|
accept |
|
accept |
|
accept |
Everybody, please note you need to be on MEMBERS.md to be eligible for a vote^ |
|
accept |
3 similar comments
|
accept |
|
accept |
|
accept |
According to the charter, It looks like we had to be a member 21 days before the vote in order to vote, is that also the case for this vote? I just opened a PR to add myself to MEMBERS.md. |
|
@jasonbrooks see https://github.com/openshift/community/pull/3/files#diff-ae639c0fd2b72908428b2e550e421bf0R109 |
|
accept |
4 similar comments
|
accept |
|
accept |
|
accept |
|
accept |
| The OKD Working Group is run and managed by the following chairs: | ||
| * Red Hat Community Development Liaison (CDL Chair) - Diane Mueller | ||
| * External to Red Hat (Community Chair) - Dani Comnea | ||
| * Red Hat Engineering Liaison (Engineering Chair) - Christian Glombek |
There was a problem hiding this comment.
| * Red Hat Engineering Liaison (Engineering Chair) - Christian Glombek | |
| * Red Hat Engineering Liaison (Engineering Chair) - Christian Glombek |
| * Revoke a previous decision made by the Call for Agreement process. | ||
| * Approval of a Sub-Working Group when such SWG has any delegated authority. | ||
|
|
||
| Once the Call for Agreement voting period has elapsed, all votes are counted, with at least a 51% majority needed for consensus. A Chair will then declare the agreement “accepted” or “declined”, ending the Call for Agreement. |
There was a problem hiding this comment.
Further clarify that 51% of votes need agree, not 51% of working group since no quorum requirement.
| Once the Call for Agreement voting period has elapsed, all votes are counted, with at least a 51% majority needed for consensus. A Chair will then declare the agreement “accepted” or “declined”, ending the Call for Agreement. | |
| Once the Call for Agreement voting period has elapsed, all votes are counted, with at least a 51% majority of votes needed for consensus. A Chair will then declare the agreement “accepted” or “declined”, ending the Call for Agreement. |
| * Scheduling discussing of proposals that have been submitted. | ||
| * Asking for new proposals to be made to address an identified need. | ||
| * Oversee disciplinary action for members. The Chairs have the authority to declare a member inactive and expel members for cause. | ||
| * Chairs will serve for one-year revolving terms and will be approved using the [Condorcet Method](https://en.wikipedia.org/wiki/Condorcet_method). Upon the expiration of a Chair’s term, it will continue for another year, unless challenged. |
There was a problem hiding this comment.
Needs further clarification. How are we using the Condorcet Method?
|
|
||
| When no candidate has submitted their name for consideration, the current Chairs may appoint an acting Chair until a candidate comes forward. | ||
|
|
||
| Chairs must be active members. Any inactivity, disability or ineligibility results in immediate removal. |
There was a problem hiding this comment.
If we're using the oxford comma, it should be consistent.
| Chairs must be active members. Any inactivity, disability or ineligibility results in immediate removal. | |
| Chairs must be active members. Any inactivity, disability, or ineligibility results in immediate removal. |
| * Extending discussion via asynchronous communication to be inclusive of members who cannot attend a specific meeting time. | ||
| * Scheduling discussing of proposals that have been submitted. | ||
| * Asking for new proposals to be made to address an identified need. | ||
| * Oversee disciplinary action for members. The Chairs have the authority to declare a member inactive and expel members for cause. |
There was a problem hiding this comment.
| * Oversee disciplinary action for members. The Chairs have the authority to declare a member inactive and expel members for cause. | |
| * Oversee disciplinary action for members. The Chairs have the authority to declare a member inactive and expel members for cause. |
|
|
||
| OKD is the Origin Community Distribution of Kubernetes that is upstream to Red Hat’s OpenShift Container Platform and is built around a core of OCI containers, and Kubernetes container cluster management. OKD is augmented by application lifecycle management functionality and DevOps tooling. | ||
|
|
||
| The OKD Working Group's purpose is to discuss, give guidance to, and enable collaboration on current development efforts for OKD4, Kubernetes and related CNCF projects. The OKD Working Group will also include the discussion of shared community goals for OKD4 and beyond. Additionally, the Working Group will produce supporting materials and best practices for end-users and will provide guidance and coordination for CNCF projects working within the SIG's scope. |
There was a problem hiding this comment.
| The OKD Working Group's purpose is to discuss, give guidance to, and enable collaboration on current development efforts for OKD4, Kubernetes and related CNCF projects. The OKD Working Group will also include the discussion of shared community goals for OKD4 and beyond. Additionally, the Working Group will produce supporting materials and best practices for end-users and will provide guidance and coordination for CNCF projects working within the SIG's scope. | |
| The OKD Working Group's purpose is to discuss, give guidance to, and enable collaboration on current development efforts for OKD, Kubernetes, and related CNCF projects. The OKD Working Group will also include the discussion of shared community goals for OKD 4 and beyond. Additionally, the Working Group will produce supporting materials and best practices for end-users and will provide guidance and coordination for CNCF projects working within the SIG's scope. |
|
|
||
| The OKD Working Group's purpose is to discuss, give guidance to, and enable collaboration on current development efforts for OKD4, Kubernetes and related CNCF projects. The OKD Working Group will also include the discussion of shared community goals for OKD4 and beyond. Additionally, the Working Group will produce supporting materials and best practices for end-users and will provide guidance and coordination for CNCF projects working within the SIG's scope. | ||
|
|
||
| The OKD Working Group is independent of both Fedora and the Cloud Native Container Foundation (CNCF). The OKD Working Group is a community sponsored by Red Hat. |
There was a problem hiding this comment.
| The OKD Working Group is independent of both Fedora and the Cloud Native Container Foundation (CNCF). The OKD Working Group is a community sponsored by Red Hat. | |
| The OKD Working Group is independent of both Fedora and the Cloud Native Container Foundation (CNCF). The OKD Working Group is a community sponsored by Red Hat. |
There was a problem hiding this comment.
Hey, one quick note. CNCF is Cloud Native "Computing" Foundation.
| The OKD Working Group is independent of both Fedora and the Cloud Native Container Foundation (CNCF). The OKD Working Group is a community sponsored by Red Hat. | |
| The OKD Working Group is independent of both Fedora and the Cloud Native Computing Foundation (CNCF). The OKD Working Group is a community sponsored by Red Hat. |
| The mission of the OKD Working Group is: | ||
| * To collaborate on areas related to developing, deploying, managing, and operating OKD. | ||
| * To develop informational resources like guides, tutorials, and white papers to give the community an understanding of best practices, trade-offs, and value adds as it relates to developing, deploying, and managing applications in cloud native environments. | ||
| * To identify suitable projects and gaps in the ecosystem for future collaboration and coordination with those projects. |
There was a problem hiding this comment.
| * To identify suitable projects and gaps in the ecosystem for future collaboration and coordination with those projects. | |
| * To identify suitable projects and gaps in the ecosystem for future collaboration and coordination with those projects. |
| * External to Red Hat (Community Chair) - Dani Comnea | ||
| * Red Hat Engineering Liaison (Engineering Chair) - Christian Glombek | ||
|
|
||
| Note: The referenced names and chair positions will be edited in-place as chairs are added, removed or replaced. See the roles of chairs section for more information. |
There was a problem hiding this comment.
| Note: The referenced names and chair positions will be edited in-place as chairs are added, removed or replaced. See the roles of chairs section for more information. | |
| Note: The referenced names and chair positions will be edited in-place as chairs are added, removed, or replaced. See the roles of chairs section for more information. |
|
|
||
| Each Call for Agreement will be considered independently, except for elections of Chairs. | ||
|
|
||
| The Chairs will submit all Calls for Agreement unless vague, unprofessional, off-topic or lacking sufficient detail to determine what is being agreed. |
There was a problem hiding this comment.
| The Chairs will submit all Calls for Agreement unless vague, unprofessional, off-topic or lacking sufficient detail to determine what is being agreed. | |
| The Chairs will submit all Calls for Agreement that are not vague, unprofessional, off-topic, or lacking sufficient detail to determine what is being agreed. |
|
accept |
1 similar comment
|
accept |
|
accept (both the current version excluding @jamescassell 's suggestions at #3 (review) and a version including his suggestions) |
|
accept |
1 similar comment
|
accept |
cheers @jamescassell for feedback, much appreciated ! |
|
@jamescassell @cgruver thanks for the reviews! I don't want to create a precedence here by changing it now, but I'll make sure to put all your proposed changes in a new PR once this one has merged so that we can vote on it as a follow up. |
|
Understood.
Accepted as is.
Sent from Yahoo Mail for iPad
On Friday, September 6, 2019, 8:01 AM, Christian Glombek <[email protected]> wrote:
@jamescassell @cgruver thanks for the reviews! I don't want to create a precedence here by changing it now, but I'll make sure to put all your proposed changes in a new PR once this one has merged so that we can vote on it as a follow up.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
accept |
|
Accept and please can I request membership too |
|
Accept |
1 similar comment
|
Accept |
|
accept |
|
just a quick heads up to know where we are wrt folks's membership there is a minor glitch in the bot's setup and as such @LorbusChris can't |
|
accept |
1 similar comment
|
accept |
|
The Charter has been accepted! |
|
|
||
| Once the Call for Agreement voting period has elapsed, all votes are counted, with at least a 51% majority needed for consensus. A Chair will then declare the agreement “accepted” or “declined”, ending the Call for Agreement. | ||
|
|
||
| Once rejected, a Call for Agreement must be revised before re-submission for a subsequent vote. All rejected Calls for Agreement will reported to the Working Group as rejected. |
|
All of the proposed fixes will go into #44 I will call for a separate vote on it after this PR here has merged. |
|
/lgtm thanks @LorbusChris for leading this activity and everyone else who got involved |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: DanyC97, LorbusChris The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci-robot
added
the
approved
Dear OKD Community,
this is the second Call for Agreement on the topic of the OKD WG Charter, per the terms of the proposed Charter.
Question:
Do you accept or reject the proposed charter as the OKD Working Group's main governing document.
Please comment on the pull request to indicate your vote ("accept" or "reject").
Make sure you apply for membership by opening a PR to add yourself to
MEMBERS.mdor by openening an Issue expressing the desire to be added before you vote.The voting period will conclude on September 13, 2019, at 00:00 UTC.
The outcome of the Call for Agreement will be published here as well as on the Mailing List.
Thank you for your participation.