OpenAPITools / OpenAPITools/openapi-generator
[REQ] Create GitHub teams for technical committee
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 26.8k
- Forks
- 7.7k
- PR merge metrics
- PR metrics pending
Description
When creating a PR for this project, the last step says:
Copy the technical committee to review the pull request if your PR is targeting a particular programming language.
The list of users to mention can be quite long.
Maybe it would make sense to create GitHub teams for each language and add the users of the technical committee to the respective team in order to be able to assign PRs and issues to them and notify the whole team with a single mention.
- https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams
- https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/about-teams
- https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team
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 with the technical committee section linked in the issue and review GitHub's team-management guidance. Identify the language-specific teams and their committee members, then update the PR guidance so contributors can mention or assign the appropriate team. Done means the teams exist with the intended members and the workflow reflects their use.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100