Adding more details into the non-code contributor guide roles
Corrected italics
This commit is contained in:
Jonas Rosland
parent
69686f927f
commit
3450708f13
|
|
@ -1,40 +1,87 @@
|
||||||
# Non-code Contributions
|
# Non-code Contributions
|
||||||
|
|
||||||
This section is new and in progress. Expect this document to change often.
|
*This section is new and in progress. Expect this document to change often.*
|
||||||
|
|
||||||
If you are interested in helping define and structure this work, [check the weekly meeting notes](https://docs.google.com/document/d/1gdFWfkrapQclZ4-z4Lx2JwqKsJjXXUOVoLhBzZiZgSk/edit#) for information on how to get involved. You can also find us in the SIG Contributor Experience [slack channel](https://kubernetes.slack.com/messages/sig-contribex).
|
*If you are interested in helping define and structure this work, [check the weekly meeting notes](https://docs.google.com/document/d/1gdFWfkrapQclZ4-z4Lx2JwqKsJjXXUOVoLhBzZiZgSk/edit#) for information on how to get involved. You can also find us in the SIG Contributor Experience [Slack channel](https://kubernetes.slack.com/messages/sig-contribex).*
|
||||||
|
|
||||||
New contributors welcome!
|
*All contributors welcome, new and old!*
|
||||||
|
|
||||||
* Plan of attack
|
### What is this?
|
||||||
* Identify Non-Dev focused roles
|
|
||||||
* Tasks tied to these roles
|
The list below is meant to help non-code contributors find areas of the Kubernetes project where their expertise can be best utilized. The goal of this is to both provide a starting guide for anyone looking to become a contributor not necessarily writing code, and also to fill any needs that the SIGs have that might not currently be filled by code-focused contributors.
|
||||||
* Examples:
|
|
||||||
* Technical project leadership
|
This list is meant to be used by both new contributors looking for a good entrance into the project, and current contributors who would live to do something different.
|
||||||
* SIG contribution
|
|
||||||
* Leading contributor communities
|
Are you interested in any of the roles below? Come chat with us [on Slack](https://kubernetes.slack.com/messages/sig-contribex)!
|
||||||
* Promotion of people and projects
|
|
||||||
* Recognition
|
#### Project general roles
|
||||||
* Managing communication tools
|
These are roles that either span the project as a whole, or span several areas of the project. Most of the roles below can be considered "good-first-roles".
|
||||||
* Zoom, Slack, Discourse, ...
|
|
||||||
* Writing articles/blogs
|
- Community education
|
||||||
* Capture it somewhere, not sure where yet
|
- Answering questions on Discuss, Slack, StackOverflow, etc
|
||||||
* Feed into Kube.weekly?
|
- K8s Office Hours
|
||||||
* Creating artwork
|
- Meet Our Contributors
|
||||||
* Conference specific, project specific
|
- Onboarding new contributors
|
||||||
* Answering questions from community members
|
- Capturing the experiences of “Fresh Eyes” in the project
|
||||||
* Updating documentation
|
- Getting more people to SIG-Docs
|
||||||
* "Everybody owns docs" can equal "nobody owns docs"
|
- Outward facing community work (might be more CNCF-oriented)
|
||||||
* Strengthen the entry point for doc ownership
|
- Hosting meetups and general evangelism
|
||||||
* Get specific enough so that someone would have an entrypoint to get started and take ownership
|
- Presentation of work to meetups
|
||||||
* Funneling more people to SIG-Docs
|
- Design
|
||||||
* Operations or "Tech" that is generally not considered "dev"
|
- Web Development
|
||||||
* e.g. ansible
|
- Artistic contributions
|
||||||
* This! (Onboarding and enabling new people)
|
- Conference-specific or Project-specific
|
||||||
* You only get one chance to see this onboarding process for the first time, so a steady stream a fresh eyes is important.
|
- Non-Documentation writing
|
||||||
* Let's just ask the SIGs!
|
- Blogging about early experiences
|
||||||
* Chat with Paris regarding alternate entry paths, as may have come up during mentoring efforts.
|
- Operational manuals
|
||||||
* Follow up on Contrib-Ex call
|
- Walkthroughs
|
||||||
* Identify Non-Dev tasks in primarily Dev roles
|
- How-tos about integration experiences, tools, etc
|
||||||
* Is it a dis-service to suggest Docs are Non-Dev?
|
- Playbooks for Ansible, Chef, Salt, etc
|
||||||
* New functionality vs Updates/common documentation
|
- Indexing of blogs, videos, etc
|
||||||
|
- Maintaining content for the new Contributor Site
|
||||||
|
- Management of communication tools (at the discretion of project maintainers)
|
||||||
|
- Mailing list moderation
|
||||||
|
- Slack or Discourse management
|
||||||
|
- Calendar management
|
||||||
|
- Analysis of our comm tools/metrics
|
||||||
|
- Volunteer management
|
||||||
|
- Finding/Funneling contributors to the right SIGs or WGs
|
||||||
|
- Recognition of those who contribute a lot
|
||||||
|
- Recognition of projects and growth efforts
|
||||||
|
- Issue Triage
|
||||||
|
- Issue triage & labeling
|
||||||
|
|
||||||
|
#### SIG-specific roles
|
||||||
|
These are roles that are important to each and every SIG within the Kubernetes project. If you are interested in a specific topic within the project, you can contribute in several different ways for that specific SIG.
|
||||||
|
|
||||||
|
- Documentation
|
||||||
|
- Common documentation for the SIG expertise area
|
||||||
|
- Updates
|
||||||
|
- Reviewing/logging technical ownership for documentation that might need updating
|
||||||
|
- Translation
|
||||||
|
- Release roles
|
||||||
|
- All roles have shadows for onboarding new members
|
||||||
|
- Project management
|
||||||
|
- Confirming ownership of tasks, issues, objects, etc
|
||||||
|
- Rectifying “owned by everyone, so owned by no-one”
|
||||||
|
- Pull requests
|
||||||
|
- PR triage & labeling
|
||||||
|
- Editing PR text: release note, statement
|
||||||
|
|
||||||
|
#### Non-Code Tasks in Primarily-Code roles
|
||||||
|
These are roles that are not code-based, but require knowledge of either general coding, or specific domain knowledge of the Kubernetes code base.
|
||||||
|
|
||||||
|
- Documentation
|
||||||
|
- Documenting new features
|
||||||
|
- Some release roles
|
||||||
|
- Managing release notes
|
||||||
|
- Github management (Tags, repos, etc)
|
||||||
|
|
||||||
|
#### Post-Code Roles
|
||||||
|
These are roles that are not code-based, but require knowledge of either general coding, or specific domain knowledge of the Kubernetes code base.
|
||||||
|
|
||||||
|
- Technical project leadership
|
||||||
|
- Specifically, SIG-Architecture and Steering Committee
|
||||||
|
- Some release roles
|
||||||
|
- Release Lead, Features Lead, etc
|
||||||
|
- Mentoring new contributors
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue