Take on the GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged by the repository owner. https://github.com/ Issues Coordinator role for the WordPress Documentation team. Beyond labeling, you’ll assign contributors to issues, welcome them with the right resources, manage project board columns, and help prevent issues from going stale.
- Prerequisite: Label Documentation Issues — you should be comfortable labeling issues and familiar with the Documentation Issue Tracker before taking on this role
- Reference: GitHub Issues Coordinator role description
- Connect: Join #docs on SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/ if you haven’t already
Steps
- Monitor new issues daily. Subscribe to the Documentation Issue Tracker and watch #docs-firehose. Label new issues as they come in — project label first, then type-of-work, then version if applicable.
-
Assign contributors to issues. When someone comments on an issue expressing interest, assign them. They must have commented on the issue for GitHub to allow assignment.
-
Welcome assigned contributors. Comment with the name of the project rep for that documentation area, a link to any relevant onboarding docs, and when the next Docs team meeting is where they can ask for help.
-
Manage project board columns. Move issues to the appropriate column (To do, In progress, Review, Done) as work progresses. If an issue has been assigned but untouched for a month, reassign it or move it back to unassigned.
-
Attend or follow triage meetings. Every two weeks the team runs an issues triage. This is where priorities are discussed and stale issues get unblocked. Attending helps you understand what the team needs most.
Contribution checklist
- Labeling new issues as they arrive
- Assigning and welcoming contributors with relevant project info
- Keeping project board columns up to date
- Flagging or reassigning stale issues
What happens next
This role complements the Issues Triage Facilitator and Issues Reviewer roles. As you build a picture of the full issue landscape, you may want to take on one of those roles as well — or combine them.
Help
Stuck? Check the getting help guide, then ask in #docs.
Further reading:
– GitHub roles onboarding video — video walkthrough of all GitHub-related roles
– Labels guide — detailed reference for all label groups
– Team roles — list of all project reps and their areas
