forked from kubernetes/community
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
changed leadership titles, links, cleared TODOs, and other formatting
- Loading branch information
Paris Pittman
committed
Mar 30, 2018
1 parent
d5ba19a
commit 9e418f8
Showing
1 changed file
with
27 additions
and
31 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,21 +1,25 @@ | ||
| # Contributor Experience Special Interest Group Charter | ||
| *checking in for comments and will add TODOs at bottom along with feedback that comes in* | ||
|
|
||
|
|
||
| ## Leads: | ||
| * Garrett Rodrigues (**[@grodrigues3](https://github.com/grodrigues3)**) | ||
| ## Chairs: | ||
| * Elsie Phillips (**[@Phillels](https://github.com/Phillels)**) | ||
| * Paris Pittman (**[@parispittman](https://github.com/parispittman)**) | ||
|
|
||
| ## Technical Leads (TL): | ||
| * Garrett Rodrigues (**[@grodrigues3](https://github.com/grodrigues3)**) | ||
| * Christoph Blecker (**[@cblecker](https://github.com/cblecker)**) | ||
|
|
||
| ## Subprojects and OWNERs | ||
| Can be found on our [README](README.md) | ||
|
|
||
| ## Processes and Responsibilities | ||
| * Leads run weekly meetings in accordance with [SIG governance procedures](/sig-governance.md) | ||
| * Leads run quarterly planning meetings where we decide goals for the next release, to be published in the SIG’s [README](README.md) | ||
| * Leads plan at least one annual face to face Contributor Experience SIG meeting proposed via mailing list and announced via slack and other channels | ||
| * Chairs run weekly meetings in accordance with [SIG governance procedures](/sig-governance.md) unless TLs need to fill in | ||
| * Chairs and TLs run quarterly planning meetings where we decide goals for the next release, to be published in the SIG’s [README](README.md) | ||
| * Chairs plan at least one annual face to face Contributor Experience SIG meeting proposed via mailing list and announced via slack and other channels | ||
| * Members run and organize the weekly [Kubernetes Community Meeting](/events/community-meeting.md) | ||
| * This SIG will act as owners and maintainers of [kubernetes/community](https://github.com/kubernetes/community) | ||
| * We participate in [lazy consensus](http://en.osswiki.info/concepts/lazy_consensus) for our decisions | ||
| * We participate in [lazy consensus](http://en.osswiki.info/concepts/lazy_consensus) for our decisions and the [KEP](/keps) process for major features and enhancements | ||
| * Idea and/or solution is proposed via the [email protected] mailing list. Link(s) to GitHub issue proposal is a nice to have but not required | ||
| * Author will give a time period of no less than 3 working days being cognizant of popular observed world holidays to respond with questions, issues, or hold from a lead(s) for more information/research needed | ||
| * Author will give a time period of no less than 3 working days being cognizant of popular observed world holidays to respond with questions, issues, or hold from a Chair/TL(s) for more information/research needed | ||
| * Author will participate in implementation of the proposed idea and/or solution | ||
| * We are responsible for community growth and management of Kubernetes and its ecosystem. We support this growth by creating programs for SIGs, WGs and subprojects to address mentoring, learning and development, contributors, and GitHub workflows. | ||
| * We will build metrics that capture the project’s velocity and stability | ||
|
|
@@ -27,22 +31,10 @@ | |
| * We ensure communication platforms are a safe environment for discourse and maintain them and in some cases in conjunction with CNCF/LF. Depending on the situation, we will warn first and then report to Steering Committee. Platforms may include Slack, Kubernetes weekly meetings, Zoom, YouTube, etc. | ||
| * Provide guidance and mediation between SIGs and WGs that are having contributor experience issues. For example, consolidation around a certain workflow | ||
| * Solicit feedback from other SIGs, project areas, and contributors formally twice a year (mid and end) about our performance and how we can improve the contributor experience | ||
| * We encourage and determine where automation makes sense for the contributor workflow. | ||
| * We encourage and determine where automation makes sense for the contributor workflow | ||
| * We own no code outside of the kubernetes/community repo although we may collaborate with other OWNERs of repos and SIG and WG leads | ||
| * Drives consistent automation surrounding the PR workflow and issue triaging, and collaborates with other groups on implementing our design | ||
| * Leadership | ||
| * Minimum of two(2) leads, a maximum of four(4) leads | ||
| * Each lead will be responsible for a sub-group in addition to assisting with the processes outlined here. [tbu on sub-group creation] | ||
| * Lazy Consensus within the SIG to make final decision | ||
| * Changing leadership | ||
| * Candidates are nominated through the mailing list and confirmed at SIG meeting; self nomination is fine. Candidate needs two +1’s from folks representing different companies or independent/freelancers in the community to be considered a nominee | ||
| * Lead may step down at any time for any reason and propose a replacement that is already an active contributing member of Contributor Experience. They will make the change to the OWNERs file | ||
| * A lead may be asked to step down if one of the following occurs: | ||
| * Inactivity as determined by the governance of the project or as specifically described in the ask to SIG leadership. | ||
| * Inappropriate behavior or code of conduct issues | ||
| * For other reasons as determined by the leads at that time but also discussed in conjunction with the lead in question | ||
| * Leads may appoint a temporary lead if a leave of absence is desired, called a delegate that is already an active contributing member of Contributor Experience | ||
| * Process change communication: | ||
| * Process change communication: | ||
| * Socialize on [email protected] and on our weekly update calls | ||
| * If the change impacts a small number (<4) of SIGs, WGs, or repos, we will go to each lead, their mailing lists, slack channel, and/or their update meetings and ask for feedback and a lazy consensus process. We will follow up with a post to [email protected] mailing list | ||
| * In cases of impacts across a large number of areas and/or project wide, we will: | ||
|
|
@@ -52,11 +44,15 @@ | |
| * kubernetes-wg-contribex@ | ||
| * Announce at weekly Kubernetes Community Meeting on Thursdays | ||
|
|
||
|
|
||
|
|
||
| ## TODO: | ||
| * Next iteration needs a breakdown of responsibilities by each leader | ||
| * Provide some guidance, like a super lightweight proposal template. Or at least ask those making a proposal to consider things like: "Who does this change impact, and how? What can/will cease working as part of this change, and how does the proposer plan to help mitigate that?" | ||
| * Add KEP proposal process info^? | ||
|
|
||
| ### thanks to those who have reviewed this doc and provided guidance already | ||
| ## Leadership Composition | ||
| * Two (2) Chairs and Two (2) Technical Leads unless group decides that more is needed | ||
| * Each Chair and Technical Lead will be responsible for a sub-group in addition to assisting with the processes outlined here. | ||
| * Lazy Consensus within the SIG to make final decision | ||
| * Changing leadership | ||
| * Candidates are nominated through the mailing list and confirmed at SIG meeting; self nomination is fine. Candidate needs two +1’s from folks representing different companies or independent/freelancers in the community to be considered a nominee | ||
| * Chair/TL may step down at any time for any reason and propose a replacement that is already an active contributing member of Contributor Experience. They will make the change to the OWNERs file | ||
| * A Chair/TL may be asked to step down if one of the following occurs: | ||
| * Inactivity as determined by the governance of the project or as specifically described in the ask to SIG leadership. | ||
| * Inappropriate behavior or code of conduct issues | ||
| * For other reasons as determined by the Chair/TLs at that time but also discussed in conjunction with the lead in question | ||
| * Chair/TLs may appoint a temporary replacement if a leave of absence is desired, called a delegate that is already an active contributing member of Contributor Experience | ||