Formalize community teams with GitHub teams
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 141
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
GitHub offers a mechanism to group people together to assign them to issues or pull requests, and provide contact and other information. Currently we don't use it in any structured fashion, which makes discoverability of team members and their activities unnecessarily hard.
Contributor guide
No contributing guide indexed for this repository
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 reviewing how the community and its members are currently organized in GitHub. Define the team structure and the member, contact, and activity information it should expose. Done means community teams are established in a consistent, discoverable way and can be used for issue or pull request assignment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100