<scribe> scribe: AnnAbbott

<jamesn> scribe: annabbott

<mck> make log public

<jemma_> what is on the agenda?

Organizing our efforst for success

Matt: brainstorming to speed up progress to finish by end of this year, not next year.
... how to leverage outside resources?
... wide open discussion for 10 mins...

James: might be able to speed up review process by making edits/tweaks to section without multiple times

Matt: make a branch, make some edits then review

James: use meeting time to discuss contentious items

Jemma: likes James' suggestion
... what is success criteria/goal?

Matt: "finished" means fundamentally information about each 1.1 roles. Not clear that all structural roles need to be covered.

James: agrees that not all structural roles need to be covered.

Matt: roles like headings & lists are covered elsewhere.
... reviewed entire doc and ensure useful and accurate. Examples are clear.

Jemma: need list of items representing success criteria

Matt: can list high level items. Status page was intended for this purpose.
... how can we leverage those not part of Task Force?
... from last week's meeting, Jemma suggested Use Cases.

<MichielBijl> +1 to Matt's proposal

<jamesn> I like that

Matt: design stubs to include Use Cases to be filled out except code examples
... then outside folks can add code

Jon: concern is that code examples will be all over the place - not standardized

Matt: not concerned with formatting standards, but worth discussing
... could create wiki page with how to instructions

Jon: interesting idea but 1) hard to find people to make examples

Matt: thinks he can find people as long as clearly defined
... confine scope so talent is used smart = learning benefit.

Jon: 2) examples clearly communicate how ARIA should be used
... not a hodge podge

Matt: one of task force completes the documentation (Use Case)
... may shed light on how good documentation is

Ann: would be interesting way to proof what we've got

<jemma_> +q

Jemma: what envisioning for wiki page?
... requirements changed all the time while working on examples
... not sure wiki page will help that

Matt: wiki page is Step by step instructions
... James had an idea for editing APG, Matt's idea is on how to speed up creating examples
... any other barriers that are slowing down progress?

Jemma: wiki page sounds like workflow process
... barriers are clarification for specs/ambiguity in spec

Jon: examples take time to code, refactoring, streamlining
... will continue to build examples that may be more detailed
... treeview will need overview page to define what the differences are between the various examples

Birkir: would it make sense to have documentation before starting examples

Matt: existing list was intended to show order - simpler to more complex
... most simple widgets have examples

Birkir: assign tasks at end of each call?

Jon: need more bodies to do stuff

Matt: core group contribution by strength would enable people outside group to contribute
... another idea - perhaps planning for next meetings weeks out

<Birkir> How about a Face to Facebook meeting to speed things up.

<jemma_> +1 face to face meeting

Matt: face-to-face would be more effective if we have a LOT to review
... would like to try other methods before face-to-face and judge success
... started a Style guide

<jemma_> A style guide by Matt sounds very useful and helpful

<jemma_> can you share the link, Matt?

Matt: will add link to Style Guide to wiki
... start with prose for examples (description) then create example code
... any volunteer to write guidance for example code?

Jon: would like to review treeview work completed
... need to keep in mind this is for education

Matt: write a workflow wiki page for volunteer to create example X

Jon: hard to because no agreement on what needs to be included

<jemma_> https://github.com/w3c/aria-practices/wiki

<jemma_> this is home page of apg wiki

Jon: who has permissions to edit this pag e?

<jemma_> Matt will make one for coding example workflow documentation.

Michiel: looking at setting up group for permissions

Matt: what is best way to get members edit access?

<jemma_> https://gist.github.com/

Matt: suggest Jon create markdown file

<MichielBijl> https://gist.github.com/MichielBijl/7f0d14a1c75f84778adf

Matt: code standards?
... Ian was getting started on something

Michiel: accordion, I think

Jon: use treeview as an example for code standards

Matt: next week let's plan on making some time to determine who will do what
... plus review
... review how to use call time
... to speed up, review and make corrections when not on call

<jongund> https://gist.github.com/jongund/2f4510cbddd4d7ace40154656a6867d4

James: don't know how to resolve

Matt: wants to think about ways to get more off-line input

<MichielBijl> mck: https://github.com/w3c/aria-practices/pull/62

General discussion on how to effectively use github

This is scribe.perl Revision: 1.144  of Date: 2015/11/17 08:39:34  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/Michael/Michiel/
Succeeded: s/guihub/github/
Found Scribe: AnnAbbott
Found Scribe: annabbott
Inferring ScribeNick: annabbott
Present: AnnAbbott JaEunJemmaKu Michiel_Bijl jongund matt_king JamesNurthen Birkir
Got date from IRC log name: 20 Jun 2016
Guessing minutes URL: http://www.w3.org/2016/06/20-aria-apg-minutes.html
People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.