...
The prioritization process:
The co-leaders survey lead reviews Bug and Feature Request Jira tickets and assign tickets to subteam members to investigate and discuss at the subteam meetings. In . Each meeting tries to address a mixture of Bug and Feature requests, from both the “Awaiting Prioritization” and “Awaiting More Information” queues. In preparation for the meeting, subteam members:
...
During the Dev. Pri. meetings, the subteam discusses the tickets and their recommendations and route them to their next status. The subteam member assigned to the ticket will follow up on the ticket with explanatory comments on the decision . Each meeting tries to address a mixture of Bug and Feature requests, from both the “Awaiting Prioritization” and “Awaiting More Information” queuesand the subteam lead updates the ticket status.
Factors influencing the prioritization include
- Demonstrated community interest in the issue by supporting votes and comments on the tickets and/or discussion on the member listserv and Google Group
- Sufficient specification (see the How to Request a new Feature/How to Report a Bug documentation)
- Developer capacity and expertise
- Priorities outlined in the Development RoadmapResults of the July 2016 Development prioritization survey and Fall 2019 Survey
Average Workload:
The ensure that Dev. Pri. discusses enough tickets and has time for discussion, the monthly meetings are 1.5 hours long.
...
The average time commitment for co-chairsthe subteam lead is approximately 4 3.5 hours per month (including the monthly meeting time). The co-chairs select and assign the tickets, facilitate the meetings, route the tickets on the kanban boards, and prepare quarterly reports to the UAC or TAC chair as requested. The co-chairs usually alternate months on assigning tickets, so actual monthly time commitment may vary.