<Kim> https://www.w3.org/WAI/GL/wiki/Accepted_WCAG_2.1_SC

<Kim> https://www.w3.org/WAI/GL/wiki/Accepted_WCAG_2.1_SC

<scribe> scribe: Detlev

<patrick_h_lauke> i could tackle concurrent

Kim: Device sensors will be accepted with an editorial note to clarify scope (what sensors?) so it tackles motion sensors

MelanieP_: Not so familiar with device sensors - possibly with help of someone else

Kim: Editing can happen on Github or elsewhere (wiki)

Chris: Happy to help out with Github

Melanie: May work in google docs then Chris will help moving ot to Git

Kim: Permissions issue

Chris: explains Permissions structure owner, pull request author etc

Kim: Permissions may have been changed for the repository - may need to be changed to make edits easier

Chris: Do you want edits on the fly for Github pull requests?

Kim: Does not waht to edit a pull request - edit directly
... Wants to edit in the view ..(soory I give up on keeping track with this technical discussion over Githu functionality)

Chris: Pull request important - no quick answer, but next week

<chriscm> LOL, technical discussion on GitHub probably not important

Chris: two issues: 1 permissions - you need to be careful with two many people editing the same material at the same time - thats why there are branches and pull requests merging stuff into one coherent master branch
... we can create a 'sandbox' for a subgroup of people with broader permissions, do the edits in the sandbox, then something knowing Git better can go in and merges it with the other stuff

Kim: good idea - we used the wiki for that

Chris: requrests a list of repositories that we would need

Kim: Kathy would be the one to do that

Chris: put her in cc

<Kim> https://w3c.github.io/Mobile-A11y-Extension

Kim: Mobile accessibility work before

Detlev: When is the next PWD going to be released?

<Kim> https://rawgit.com/w3c/wcag21/target-size/understanding/21/target-size.html

Kim: Kathy has tackled target size understanding in Github already
... Github threads in the issues contain a lot of material need to update the understanding docs

<patrick_h_lauke> +1 reading/discussing long documents like this by voice in a call is not well spent time

<patrick_h_lauke> needs time to think, evaluate, suggest, etc

<patrick_h_lauke> best done async via email etc

Kim: Process: For dicussion, we should prefer github comments on the issue dedicated to the new SCs over mails on the mailing list

<patrick_h_lauke> (i'll note that the way github has been used so far for the process is...suboptimal, but we'll make the most of it)

Kim: Kathy will be directing thisdiscussion, tackling one by one
... Any questions about the template, or any other questions?

Chris: will support Melanie, propose something for setting up Github sandbox
... if we firm up process, the meetings will be more productive

Kim: We finish up early then - get started on the understanding docs
... Will continue MATF meetings at this slot regularly

Chris: Will try to simplify the workflow for our TF

This is scribe.perl Revision: 1.152  of Date: 2017/02/06 11:04:15  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Succeeded: s/his /this/
Present: patrick_h_lauke Detlev shadi MelanieP__ Chris
Found Scribe: Detlev
Inferring ScribeNick: Detlev

WARNING: No "Topic:" lines found.

Found Date: 07 Sep 2017
Guessing minutes URL: http://www.w3.org/2017/09/07-mobile-a11y-minutes.html
People with action items: 

WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report