Triage, as described in the test handbook, is a process of sorting, labeling, and closing issues on the Trac or Github.
In the context of the Themes Team, the triage encompasses several things:
- Theme Review component trac tickets
- Theme Directory component trac tickets
- WPThemeReview coding standards issues
- Theme Sniffer issues
- Theme Check issues
The idea is to go through the tickets/issues and see which can be closed, change the priority (if needed), and finding ‘champions’ who will be responsible for handling the issues.
If you are interested in discussing a specific ticket, you are welcome to bring it up during a team meeting.
Triage workflow
During triage, we go through the open issues, closing the ones that can be closed and prioritizing other issues.
We try to assign a champion to the issues with the highest priority. Some tickets/issues already have a priority registered, but we need to see if these priorities need to be changed.
Championing the ticket/issue/PR/patch
Championing means being the person who is responsible for seeing that the issue is worked on. Ideally, champions are people who have some coding knowledge and can work on the issues.
But they can also be people who are good at managing a project and finding people willing to work on the issue and seeing the issue is resolved within a sensible time frame.
For the meta tickets, we need people who are comfortable with working on the meta repository alongside meta contributors.
For some of these issues, we depend on the meta team who can change how things work on the theme directory.
Other issues should have either a good proposal with a clear way of solving them or need input from the meta team. Hopefully, once we show some initiative on them we’ll have good feedback and will be able to sort them out.
For the theme coding standards and Theme Sniffer issues, we need people who will work on providing code examples (in the case of the standards) or are willing to learn how to write sniffs and how to fix issues on the Theme Sniffer plugin.
We also need to reach some conclusion on the open issues in the coding standards so that sniffs can be written for them.
Once we have the prioritization fixed we can schedule additional meetings for discussion on working on these projects.
Resources
This Google docs sheet can be used as a reference for the meta related issues. Issues form the other projects will be added as the time passes so that we have it in one place and can reference it in the meetings.