similar to ContribEx @ K8s. This would help us to write down some of the guiding principles we identified already (i.e. “work async”),
make sure that this is for contributors and not for end-users or developers. Have at least something in the repo README.md
Repository Setup
Create labels + issues. Suggestion: have a “quick win” label for things that are easy to implement and that can help us to show value to the community quickly.
Find orphaned issues around contributor experience and move them into that repository. (Juraci and Severin (and other GC members) should have permissions to move
Help to validate if an issue should be moved by having an (early) charter
Create a “contributor journey”
using what we have already + imagination, use that to label Issues and see what we can do to help people at different stages
Implies defining stages
Example: Outsider -> First Contribution -> Continuous Contributor -> Established Member _> approver -> maintainer -> “and beyond” -> emeritus
Sometimes it’s about the transition
For labeling issues but also for documents that allow members in a certain spot to jump to the right documents/material/etc.
svrnm
commented
1 month ago
This is more a "how and why" question for this SIG:
How do we want to operate? What practices do we want to implement? What guiding principles do we have?
A few proposals, that also have been discussed druing the SIG meeting today (Jul 22th 2024):
Establish a charter
similar to ContribEx @ K8s. This would help us to write down some of the guiding principles we identified already (i.e. “work async”), make sure that this is for contributors and not for end-users or developers. Have at least something in the repo README.md
Repository Setup
Create a “contributor journey”
using what we have already + imagination, use that to label Issues and see what we can do to help people at different stages