InnerSourceCommons / InnerSourceCommons/InnerSourcePatterns
[Pattern Draft] Recruiting and nurturing contributors for InnerSource projects
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 853
- Forks
- 206
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 2
Description
In conversations in Slack @MaineC has shared many great tips about how to keep the number of contributors to a project healthy. Her tips are focused on
- increasing the number of contributors
- helping contributors to level up into the role of Trusted Committer
We would like to interview her about these topics, and see how we could turn this content into a pattern.
See our full pattern syntax to understand the type of information we would like to extract by doing an interview.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading meta/pattern-template.md to understand the required pattern structure, then arrange an interview with MaineC about recruiting contributors and helping them become Trusted Committers. Done means turning the interview content into a draft pattern that follows the repository's full pattern syntax.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- markdown
- Domain
- content, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100