[WIP][1st Draft] Contributor Experience Charter #2810
Conversation
parispittman
added
sig/contributor-experience
k8s-ci-robot
added
size/L
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: If they are not already assigned, you can assign the PR to them by writing 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 |
parispittman
changed the title
Nit: We probably mean 72 working hours to account for weekends and holidays. |
|
/cc |
|
/committee steering |
k8s-ci-robot
added
the
committee/steering
|
|
||
| ## Scope | ||
|
|
||
| The Contributor Experience Special Interest Group (SIG) is responsible for creating programs and process (even un-processing in some cases) to encourage the health and velocity of the Kubernetes contributor community. Being concentious to our contributor base is critical to scaling the project, growing the ecosystem, and attributes to the projects success. |
There was a problem hiding this comment.
The wording was a bit weird to me and didn't mention contributor experience. Take or leave this suggestion:
"is responsible for improving the experience of those who contribute to the Kubernetes project. We do this by creating, and maintaining programs and processes that promote community health and reduce project friction, while retiring those programs and processes that don't. Being conscientious of our contributor base is critical to scaling the project, growing the ecosystem, and helping the project succeed."
|
|
||
| #### Code, Binaries and Services | ||
|
|
||
| - Establish policies, standards, and procedures: |
There was a problem hiding this comment.
I personally don't need to see all the specifics of GitHub spelled out. I would be comfortable broadening this bullet, and replacing the github and moderation content below (lines 18-22, 25-30)
eg:
-
Establish policies, standards and procedures for the use, moderation, and management of all public platforms officially used by the project, including but not limited to:
- Discuss (link to discuss)
- GitHub (link to github administration subproject)
- Mailing lists / Google groups (link to mailing list section of moderation guidelines) for the project as a whole (eg: kubernetes-dev) and for individual sigs and wgs (eg: kubernetes-sig-testing, kubernetes-wg-apply)
- Slack (link to slack guide)
- Youtube (link to kubernetescommunity channel)
- Zoom (link to zoom guidelines)
-
Establish and staff teams responsible for the administration and moderation of these platforms
- Teams must be staffed by trusted contributors spanning time zones
- They are authorized to take immediate action when dealing with code of conduct issues
- They are expected to escalate to the project's code of conduct committee when issues rise above the level of simple moderation
| - Establishing a "GitHub Administration team" that will oversee the execution of GitHub management tasks: inviting new members to the org, creating repos, executing moderation decisions, auditing permissions. | ||
| - Work with other SIGs and interested parties in the project to execute GitHub tasks where required | ||
| - Deliver and iterate on Thursday community meeting by delivering a variety of content for a weekly overview into the contributor community. | ||
| - Strategize, build, and execute on scalable mentoring programs for all contributor levels. |
There was a problem hiding this comment.
Do you want to spell out any of these programs (I'm totally OK with you not spelling them out)
| - YouTube via the /kubernetescommunity channel [link] | ||
| - Slack via CNCF funding [link] | ||
| - discuss.kubernetes.io via CNCF funding [link] | ||
| - Help onboard new contributors and current into the culture, workflow, and CI of our contributor experience through the constant addition, modification and retirement of contributor documentation and programs tailored to onboarding. |
There was a problem hiding this comment.
"... of our contributor experience via the [contributor guide], [contributor summits] and other programs tailored to onboarding
| - Slack via CNCF funding [link] | ||
| - discuss.kubernetes.io via CNCF funding [link] | ||
| - Help onboard new contributors and current into the culture, workflow, and CI of our contributor experience through the constant addition, modification and retirement of contributor documentation and programs tailored to onboarding. | ||
| - Perform issue triage and maintain the kubernetes/community repository. |
There was a problem hiding this comment.
Do mean issue triage across the whole project? Or just the kubernetes/community repo?
eg: "Maintaining the kubernetes/community repository, including issue triage"
| - Help SIGs with being as transparent and open as possible through creating best practices, guidelines, and general administration of YouTube, Zoom, and our mailing lists where applicable | ||
| - Assist SIGs/WGs with organizational management operations as laid out in the sig governance doc [link] | ||
| - Plan and execute on face to face Contributor Summit(s) and our own SIG Face to Face meetings as well as others (upon request). | ||
| - Own and execute on other events that are targeted to the Kubernetes contributor such as the Steering Committee Election process. |
There was a problem hiding this comment.
You could maybe roll a few things up under this bullet, e.g.
"Own and execute events that are targeted to the Kubernetes contributor community, including:
- The weekly Kubernetes Community meeting
- Contributor Summits
- SIG Contributor Experience F2F meetings
- Steering Committee elections (though we do not own policy creation, see 'out of scope' below)
- Retrospective moderation for other SIGs upon request
- other events upon request and consideration"
| - Plan and execute on face to face Contributor Summit(s) and our own SIG Face to Face meetings as well as others (upon request). | ||
| - Own and execute on other events that are targeted to the Kubernetes contributor such as the Steering Committee Election process. | ||
| - Distribute contributor related news on various Kubernetes channels and liaison to CNCF for posting blogs and social media on their channels. | ||
| - Work with CNCF to improve DevStats and increase adoption within our community to establish metrics that can be used in process improvements, mapping trends, or charting successes. |
There was a problem hiding this comment.
This seems like over-specifying on devstats. Maybe rephrase in terms of project health? e.g.
"Establish and share metrics to measure project health, community health, and general trends, including:
- ongoing work with the CNCF to improve DevStats
- the contributor experience / communication platform survey(s)
- engagement on project platforms that we manage"
There was a problem hiding this comment.
Main comment: Overall this looks good. I think there are some things that are over-specified when it comes to in scope. I made some suggestions on places to trim it down and generalize a bit, take or leave as you will.
Other comment: would like to see CNCF interface (what's ours, what's theirs, how do we interact and why) spelled out a bit more either in "external facing" or "out of scope" section
|
|
||
| We cross-cut all SIGs and WGs to deliver the following processes: | ||
|
|
||
| Our standard time box is 3 days; however, there may be situations where we need to act quickly but the time period will always be clear and upfront. |
There was a problem hiding this comment.
This seems out of place as a "following process". If you're trying to say your standard response time for anything is no more than 3 (business?) days, maybe state above before enumerating processes
| - We do not create SIGs/WGs but can assist in the various community management needs of their micro communities that would kick off their formation and keep them going. | ||
| - communication platforms that are out of our scope for maintenance and support but we may still have some influence: | ||
| - r/kubernetes | ||
| - kubernetesio@ twitter account |
There was a problem hiding this comment.
do you own the kubernetes.io blog? does the CNCF? may be worth spelling out collaboration on that in "externally facing processes" or being clear that it's out of scope here
There was a problem hiding this comment.
we don't own it. good catch.
| ### Out of scope | ||
|
|
||
| - Code for the testing and CI infrastructure - that’s SIG Testing | ||
| - k/community ownership of folders for KEPs and Design Proposals. Members are to follow those folders owners files and SIG leadership for the specific issue/PR in question. |
| - Code for the testing and CI infrastructure - that’s SIG Testing | ||
| - k/community ownership of folders for KEPs and Design Proposals. Members are to follow those folders owners files and SIG leadership for the specific issue/PR in question. | ||
| - User community management. We hold office hours because contributors are a large portion of the volunteers that run that program. | ||
| - The contributor experience for repos not included in the [GitHub Management subprojects list](https://git.k8s.io/community/github-management) |
There was a problem hiding this comment.
you could either say "for repos not in orgs actively used by the Kubernetes project"
or "for associated repositories and repos that are not part of the Kubernetes project"
|
|
||
| ## Roles and Organization Management | ||
|
|
||
| #### |
|
|
||
| ### Subproject Creation - TODO | ||
| Pick one: | ||
| SIG Technical Leads |
There was a problem hiding this comment.
FWIW, if this helps unblock your decision, I'm fine with this option but with SIG Chairs in addition (or instead). I think Steering didn't have code-light/process-heavy sigs like Contribex, Release, PM etc. in mind when this option was put forth, and am happy to revisit this.
| - Research other OSS projects and consult with their leaders about contributor experience topics to make sure we are always delivering value to our contributors. | ||
| - Provide retrospective hosting services on request to SIGs | ||
|
|
||
| #### Cross-cutting and Externally Facing Processes |
There was a problem hiding this comment.
I don't know if it belongs here or out of scope. But I would prefer the interface between this SIG and CNCF get spelled out in one of these two sections.
It looks like at the very least, we expect CNCF to take care of billing. Are there admin rights. etc that they have that we don't?
Are there any projects or programs that require ongoing collaboration with the CNCF? Those would probably belong here.
cblecker
changed the title
k8s-ci-robot
added
the
do-not-merge/work-in-progress
parispittman
force-pushed
the
charterwork
branch
3 times, most recently
from
7b69e1a to
f54685a
Compare
parispittman
force-pushed
the
charterwork
branch
from
f54685a to
3f6b740
Compare
|
/reopen |
|
@spiffxp: Reopening this PR. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
@spiffxp: failed to re-open PR: state cannot be changed. The pull request cannot be reopened. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Fwiw, it's nice to see that prow explicitly adds a comment for this and does not fail silently. |
@cblecker @Phillels @grodrigues3
top of doc:
This is a WIP. There is jargon in here that will be defined, acronyms drawn out, and links correctly applied after all content suggestions and changes come through.