W3C

ARIA Editors

02 Nov 2016

Agenda

See also: IRC log

Attendees

Present
Joanmarie_Diggs, MichaelC, tzviya, MichielBijl, Fred, fesch, JamesN, JamesNurthen
Regrets
Chair
MichaelC
Scribe
MichaelC

Contents


<scribe> scribe: MichaelC

Timeline check http://www.w3.org/WAI/ARIA/project

DPub roles for CR target 17 Nov

DPub-AAM may not make that because still awaiting mappings from browsers

nothing else to publish before 2017

any early Jan publications need to start queuing by early Dec

APG coming up soonish, when next milestone reached

Revisit approach to common files after repository split

ARIA common files are in their own repo https://github.com/w3c/aria-common

In CSS repo can see it as a submodule https://github.com/w3c/css-aam

but not available via rawgit

options are to leave rawgit out of the workflow, or use subtree merge

MC to keep playing with it

Ivan may have some knowledge

Use of releases in GitHub

Joanie has set up https://github.com/w3c/aria/releases/tag/CR_ARIA_1_1_0

<joanie> 1. check out commit to tag

<joanie> 2. git tag -a YOUR_TAG_NAME_1_1_1000002

<joanie> 3. In editor, type useful commit message

<joanie> 4. git push origin YOUR_TAG_....

this is a feature you can use in your repos

can use to tag ¨key¨ things you might need to get

could tag every time we publish a TR version

might also tag points were FOs were filed, and where they were resolved

<joanie> git tag -l

<joanie> (will list existing tags)

<joanie> git checkout CR_ARIA_BLA

Use of milestones in GitHub

Can tag issues to milestones

<jnurthen> https://github.com/w3c/aria-practices/milestones

addressing the issues for the milestones completes

Practices people finding this useful

have put in milestones for key transitions plus upcoming WD

helps keep on track for what´s urgent and what can wait

which could help with scope

good to start using these after splitting the repos

some of the milestones we´d keep due dates in sync

Labels

have set up version labels in ARIA

https://github.com/w3c/aria/labels

many of these will not be needed after repo split

perhaps versioning and spec applicability labels not useful after split

AOB

none

Next meeting is 16 November 2016

at the usual time for all time zones

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.148 (CVS log)
$Date: 2016/11/02 17:32:56 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.148  of Date: 2016/10/11 12:55:14  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Found embedded ScribeOptions:  -final

*** RESTARTING DUE TO EMBEDDED OPTIONS ***

Found Scribe: MichaelC
Inferring ScribeNick: MichaelC
Present: Joanmarie_Diggs MichaelC tzviya MichielBijl Fred fesch JamesN JamesNurthen
Agenda: https://lists.w3.org/Archives/Public/public-aria-editors/2016Nov/0000.html
Got date from IRC log name: 02 Nov 2016
Guessing minutes URL: http://www.w3.org/2016/11/02-aria-editors-minutes.html
People with action items: 

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


[End of scribe.perl diagnostic output]