-
Notifications
You must be signed in to change notification settings - Fork 361
May 7, 2019 Meeting
Matt King edited this page May 3, 2019
·
8 revisions
Setup and review agenda -- 3 minutes.
Update from Jon and Mark on pattern and combobox example.
- Discuss which sections need task force feedback.
- Discuss any open issues or questions blocking progress.
- 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:30 -- 25 minutes
- 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
Start at 11:55 -- 5 minutes.
- Next meeting: May 14, 2019
- Other business for future agendas?
- Home
- About the APG TF Work
- Contributing
- Meetings
- Management and Operations Documentation
- Publication Change Logs