IRC log of aria-apg on 2016-10-17
Timestamps are in UTC.
- 16:56:49 [RRSAgent]
- RRSAgent has joined #aria-apg
- 16:56:49 [RRSAgent]
- logging to http://www.w3.org/2016/10/17-aria-apg-irc
- 16:56:57 [jamesn]
- rrsagent, make log world
- 16:57:45 [jamesn]
- Agenda+ Meeting length and project management
- 16:57:45 [jamesn]
- Agenda+ Review example development status page https://github.com/w3c/aria-practices/wiki/Design-Patterns-Status
- 16:57:45 [jamesn]
- Agenda+ Review 4Q working draft milestone and set priorities for next 2 weeks
- 16:57:45 [jamesn]
- Agenda+ Issue #120: Clarify menu processing https://github.com/w3c/aria-practices/issues/120
- 16:57:46 [jamesn]
- Agenda+ Issues #20 and #114: Develop example of tabs design pattern
- 16:59:12 [jamesn]
- Meeting: ARIA APG TF
- 16:59:15 [jemma_]
- jemma_ has joined #aria-apg
- 17:01:34 [jongund]
- jongund has joined #aria-apg
- 17:03:23 [jongund]
- present+ jongund
- 17:08:47 [jamesn]
- scribe: jamesn
- 17:09:04 [MichielBijl]
- present+ MichielBijl
- 17:09:20 [jamesn]
- present+ JamesNurthen
- 17:09:32 [jemma_]
- present+ JemmaJaEunKu
- 17:09:42 [jamesn]
- Introductions (not scribed)
- 17:14:54 [jamesn]
- zakim, next item
- 17:14:54 [Zakim]
- agendum 1. "Meeting length and project management" taken up [from jamesn]
- 17:16:05 [jamesn]
- MK: personally I would like to discuss the idea of optimizing the value of the time people are contributing we have more targetted agendas planned in advance by the group and perhaps consider not meeting every week - depending on the status of what people are working on
- 17:16:22 [jamesn]
- not all of the work has to be done in a meeting - but some is more fruitful with a discussion
- 17:16:30 [jemma_]
- +1
- 17:16:51 [jamesn]
- would be helpful at this point in time to make sure that people don't spend any more time on the phone than necessary
- 17:17:03 [jamesn]
- reviewing other peoples text and code etc.
- 17:17:10 [jamesn]
- q+
- 17:18:01 [jemma_]
- +1 for one hour meeting instead of one and half hour meeting.
- 17:18:32 [jamesn]
- JN: getting meeting down to 1 hour , a 30 min editors meeting weekly - and then only meet when necessary
- 17:19:50 [jamesn]
- MK: in terms of managing the project - what I would like to be able to do - in the next week or 2 weeks
- 17:20:42 [jamesn]
- look at the issues later in the week - can see if anything has come up that is a roadblock for agenda discussion. Default cadence is every other week - unless there is a roadblock where asynchronous review isn't going well and need hellp from the group
- 17:22:08 [jamesn]
- MK: can either functionally review - with JAWS/NVDA etc. read text and feedback when not clear etc. There should be a way for everyone to contribute.Instead of trhe meeting they would use the hour to updayte iossues etc.
- 17:22:15 [jamesn]
- MK: that would be my hope
- 17:25:25 [jamesn]
- JK: weekly meetings give deadlines
- 17:25:48 [jamesn]
- MK: deadline could still be there - but you don't always have to call in
- 17:26:07 [jamesn]
- MK: in the weeks without a meeting - there will still be an agenda of items which need review etc.
- 17:26:27 [jamesn]
- MK: if you have comitted to doing something need a comment in the assigned issue
- 17:26:36 [jamesn]
- MK: will always be an agenda but not always a call
- 17:26:41 [jamesn]
- MK: 1 hour weekly call
- 17:26:57 [jamesn]
- MK: unless the agenda says offline meeting cancelled
- 17:26:58 [jamesn]
- q+
- 17:29:46 [jamesn]
- https://gitter.im/w3c/a11ySlackers
- 17:31:06 [jamesn]
- JN: would be 1 extra thing to check unless a critical mass of people use it
- 17:34:14 [jamesn]
- https://gitter.im/w3c/aria-practices
- 17:35:43 [jamesn]
- zakim, next item
- 17:35:43 [Zakim]
- I see a speaker queue remaining and respectfully decline to close this agendum, jamesn
- 17:35:46 [jamesn]
- q-
- 17:35:49 [jamesn]
- zakim, next item
- 17:35:49 [Zakim]
- agendum 2. "Review example development status page https://github.com/w3c/aria-practices/wiki/Design-Patterns-Status" taken up [from jamesn]
- 17:36:33 [MichaelC_]
- MichaelC_ has joined #aria-apg
- 17:36:40 [jamesn]
- MK: goal was for 99% of WIP table to have an issue everywhere
- 17:36:53 [jamesn]
- was thinking of deleting the 1st column and having 2 columns only
- 17:38:03 [jamesn]
- MK: would like to talkk abnout how we work through a design pattern - and how we work through issues. need to make sure 1 issue for drafting the pattern and 1 for deving the example
- 17:39:07 [jamesn]
- my questions are how we want to manage the issues... i noted that the tabs one - you had issue #20 which was assigned for developing the implementatioon but then created #114 for a review of #20 as opposed to adding it to #20
- 17:39:47 [jamesn]
- MB: not sure what the best way is... this is when we transitioned to the new repos... just staRTED logging a bunch of iossues... I think it is a bit too granular but allows to assign the reviewing to someone else
- 17:40:17 [jamesn]
- MK: there are some people who will be most productive in reviewing and others most productive in coding.
- 17:40:48 [jamesn]
- MK: was wondering if we have a master issue and a seperate for functional and editorial review... where to put code review?
- 17:41:07 [jamesn]
- MK: also not enough people to do that too
- 17:41:30 [jamesn]
- MK: if we had some code review people, could have a seperate code review issue for the example and could be assigned to them
- 17:41:54 [jamesn]
- if you write or dev an example, provide a link to the review issue... please provide feedback at this issue
- 17:42:51 [jamesn]
- MB: another possible is have 1 issue for the review process and have a list with checkboxes and have code review etc. checkboxes... so we don't end up with a gazillion issues
- 17:43:20 [jamesn]
- MK: if person wants feedback from specific people could create a review issue and assing it
- 17:43:29 [jamesn]
- could always make remarks in it
- 17:43:52 [jamesn]
- if did finish a piece of work and want people to review it - no need to be shy about it
- 17:44:09 [jamesn]
- expect people to provide a comment in it- either looks good or add comments
- 17:44:29 [jamesn]
- need some agreement on how can be asynchonous if going to work in that way more
- 17:46:12 [mck_]
- mck_ has joined #aria-apg
- 17:46:13 [jamesn]
- MK: will add a link to review issue in the coding template
- 17:46:41 [jamesn]
- for people with stuff in review state - menu menubar tabs... link in the exmaple to the issue and a link the in the issue to the example
- 17:47:47 [jamesn]
- was reviewing as a group, but now if going to write or edit a pattern just do it and then submit to the group for review... no need for the first column in the trable
- 17:48:39 [jamesn]
- zakim, next item
- 17:48:39 [Zakim]
- agendum 3. "Review 4Q working draft milestone and set priorities for next 2 weeks" taken up [from jamesn]
- 17:49:02 [mck_]
- https://github.com/w3c/aria-practices/milestone/4
- 17:50:04 [jemma_]
- https://github.com/w3c/aria-practices/issues
- 17:51:08 [jamesn]
- have 17 issues here
- 17:53:38 [jamesn]
- Jemma: no Q4 issues for me
- 17:56:58 [jamesn]
- JN: moved the menu and menubar to Q4
- 18:00:26 [jamesn]
- MK: MB focussed on tabs?
- 18:00:42 [jamesn]
- MB: pretty much ready for review... if you know more than I do then tell me
- 18:01:01 [jamesn]
- MK: looks like there were some issues in #114 that not finished
- 18:01:47 [jamesn]
- MK: were you also going to develop an implementation that selection doesn't follow focus.
- 18:02:01 [jamesn]
- MB: an option is available....
- 18:02:09 [jamesn]
- MK: might be easier if 2 on 1 page
- 18:02:24 [jamesn]
- MB: need to see if the script supports 2 tab widgets on 1 page
- 18:02:31 [jamesn]
- MK: Jemma on menu bar
- 18:02:58 [jamesn]
- MK: noticed on the tabs one that some of the template features aren't there
- 18:03:17 [jamesn]
- some structural elements where regions aropund the html code source and the example itself
- 18:03:31 [jamesn]
- MB: the code example page
- 18:03:48 [jamesn]
- MK: can look in the code template subdirectory... comments in the code
- 18:09:29 [jamesn]
- rrsagent, make minutes
- 18:09:29 [RRSAgent]
- I have made the request to generate http://www.w3.org/2016/10/17-aria-apg-minutes.html jamesn
- 18:09:31 [jemma_]
- info from meeting minute 10/3/2016
- 18:10:30 [jamesn]
- zakim, please part
- 18:10:30 [Zakim]
- leaving. As of this point the attendees have been JamesNurthen, JaEunJemmaKu, MichielBijl, jongund, AnnAbbott, Bryan_Garaventa, IanPouncey, JemmaJaEunKu
- 18:10:30 [Zakim]
- Zakim has left #aria-apg
- 18:10:35 [jamesn]
- rrsagent, make minutes
- 18:10:35 [RRSAgent]
- I have made the request to generate http://www.w3.org/2016/10/17-aria-apg-minutes.html jamesn