kubernetes
/
community
mirror of https://github.com/kubernetes/community.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update charter.md 

Correcting nits that are in the comments
This commit is contained in:
Paris 2018-02-27 18:39:03 -08:00 committed by GitHub
parent 7adca3bec5
commit 26f5885f3d
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 28 additions and 29 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

57
sig-contributor-experience/charter.md
View File

@ -1,52 +1,51 @@
# Contributor Experience Special Interest Group Charter
*checking in for comments and will add TODOs at bottom along with feedback that comes in*
The Contributor Experience Special Interest Group is dedicated to ensuring that Kubernetes contributors have a consistent workflow and great experience within the ecosystem. Developing and sustaining a healthy community of contributors is critical to scaling the project and growing the folks who build it. We champion the needs of these contributors by building programs and processes that address any gaps, learning and development, reward and recognize positive actions, and facilitiate project wide communications.
## Leads:
Garrett Rodrigues
Paris Pittman
Elsie Phillips
* Garrett Rodrigues (**[@grodrigues3](https://github.com/grodrigues3)**)
* Elsie Phillips (**[@Phillels](https://github.com/Phillels)**
* Paris Pittman (**[@parispittman](https://github.com/parispittman)**)
## Processes and Responsibilities
* Leads run weekly meetings in accordance with [SIG governance procedures](sig-governance.md)
* 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)
* SIG Leads plan at least one annual face to face Contributor Experience SIG meeting proposed via mailing list and announced via slack and other channels
* SIG members run and organize the weekly [Kubernetes Community Meeting](https://goo.gl/zMRLeu)
* This SIG will act as owners and maintainers of [github.com/kubernetes/community](https://github.com/kubernetes/community)
* We participate in [lazy consensus](http://en.osswiki.info/concepts/lazy_consensus) for our decisions.
* Idea and/or solution is proposed via the kubernetes-wg-contribex@googlegroups.com 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 participate in implementation of the solution
* Leads 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
* Idea and/or solution is proposed via the kubernetes-wg-contribex@googlegroups.com 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 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.
* This group does not create new SIGs/WGs/subprojects themselves but will mentor new SIGs in the creation and management of their own:
* We will build metrics that capture the project’s velocity and stability
* This SIG does not create new SIGs, WGs, subprojects themselves but will mentor new SIGs in the creation and management of their own:
* YouTube playlist
* Zoom account
* Zoom account(s)
* Slack channel(s)
* Github service groups
* GitHub service teams
* 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/working groups that are having contributor experience issues. For example, consolidation around a certain workflow.
* 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 and contributors throughout the project and continuously improve contribution 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/WG leads.
* Drives consistent automation surrounding the PR workflow and issue triaging, and collaborates with other groups on implementing our design.
* 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.
* 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 group to make final decision.
* 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.
* 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 SIG leads at that time but also discussed in conjunction with the SIG lead in question.
* SIG Leads may appoint a temporary lead if a leave of absence is desired, called a delegate. The Lead needing the leave of absense can also propose a delegate that is already an active contributing member of Contributor Experience.
* 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:
* Socialize on kubernetes-wg-contribex@googlegroups.com 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 kubernetes-dev@googlegroups.com mailing list.
* In cases of impacts across a large number and/or project wide, we will post to the kubernetes-dev@googlegroups.com mailing list and waiting for a lazy consensus period of five days. Followed up by a reminder 24 hours beforehand if no feedback has come through.
* Socialize on kubernetes-wg-contribex@googlegroups.com 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 kubernetes-dev@googlegroups.com mailing list
* In cases of impacts across a large number and/or project wide, we will post to the kubernetes-dev@googlegroups.com mailing list and waiting for a lazy consensus period of five days. Followed up by a reminder 24 hours beforehand if no feedback has come through