May 14, 2019 Meeting

Agenda for May 14, 2019

Setup and review agenda -- 3 minutes.

Start at 11:03 - 12 minutes

Discuss review objectives: What do we want to ensure every example review covers? Possibilities:
- Code review: from engineering perspective, what do we want to ensure?
- Functional testing: without assistive technology, do examples perform as expected in target browsers?
- Assistive technology interoperability: Is the ARIA markup correct? That is, if an AT supported ARIA correctly, would it be able to function as expected?
- Editorial: Does documentation follow editorial guidelines?
To make reviews more efficient for individuals, should we have specific people assigned to specific types of review?
Would people be able to better manage time commitment if they had a specific scope of responsibility for their review work?
Unless actively making pull requests, can each task force member commit to an average of 1 review per week?

Start at 11:15 - 10 minutes

Start at 11:25 - 25 minutes

If ahead of schedule, use remaining time until 11:55.

Triage open issues missing labels
Triaged issues have:
- One of the labels that indicates type of issue: bug, enhancement, editorial, documentation, maintenance
- One of the labels that indicates part of APG: code example, pattern, guidance
- A milestone indicating target resolution date
- If related to a pattern or code example, it is assigned to a project.
Unlabeled issues needing triage

Start at 11:55 -- 3 minutes.