ARIA Editors -- 20 Jul 2016

<scribe> scribe: MichaelC

Timeline check

Publishing ARIA LC tomorrow, via Echidna

probably hope to advance to CR in a couple months

Branch cleanup ahead of repository split

MC to ping on branches to maybe remove

Matt has a few to clean

You can find branches you created via https://github.com/w3c/aria/branches/yours

<mck> git for-each-ref --format='%(committerdate) %09 %(authorname) %09 %(refname)' | sort -k5n -k2M -k3n -k4n

merged branches are usually safe to delete

but we don´t do so, in case you wanted to keep it, so please remove ones you don´t need any more

can see auto-merged branches in the web interface

<mck> git log master..yourbranch

manually merged can see

Archiving inactive branches

To archive and delete the branch:

git tag archive/<branchname> <branchname>

git branch -d <branchname>

To restore the branch some time later:

git checkout -b <branchname> archive/<branchname>

MC to do more research

and look at tagging better

this is for branches that were never merged for some reason

as well as for things we´re saving for later

so you know where to look

there may multiple approaches, but helpful to have a common approach

CSS-AAM first repository split?

MC wants to split CSS-AAM out now

<joanie> +1

so APA can work on it

and so if I break something, it doesn´t hurt

Assigning issues to people who don't have commit access

Can set up a ¨team¨ that doesn´t have commit access

so people can have issues assigned to them

without having commit access

RESOLUTION: set up a team with non-commit access for all the ARIA repositories

Respec Lint

Respec now has a lint feature

you can enable via ¨lint¨ property

should we add a11y features to it?

e.g., an accessibility section

<ShaneM> joanie: lets discuss

though it shows as a warning, that´s potentially scary

maybe make lint warnings less scary

but go ahead with an a11y section check

(also note some specs have CSS-generated content that is a11y problem, but those are probably not Respec specs)

<ShaneM> could we get it into pubrules??

<ShaneM> There's this https://dokie.li/

Security and Privacy sections?

<ShaneM> Check this spec out: https://github.com/linkeddata/dokieli

<clown> https://w3ctag.github.io/security-questionnaire/

<ShaneM> The workiong group believes there are no security nor privacy concerns related to this specificaiton.

<clown> the warning is "This specification doesn't appear to have any 'Privacy' or 'Security' considerations sections."

let´s take to ARIA WG to explore putting in those sections, with a weak recommendation to do so

ARIA Roadmap retire

Proposal to retire old Roadmap doc as we just did with 1.0 Primer and Practices

RESOLUTION: Retire ARIA Roadmap, after LC of 1.1

<ShaneM> clown++

Practices examples and references

question of how to reference sections in practices

came up in examples

though it applies to other specs as well

the respec-using specs have a feature for that

but the examples don´t use respec

<Zakim> clown, you wanted to say when I was editing the APG there were classes widget-reference, and design-pattern-reference

suggest link to practices spec from examples as ../../#section

<ShaneM> If someone wants to send me out a link I can look at it...

could rename aria-practices.html to index.html, though it impedes access to history

could have a simple script that runs only if on rawgit and changes ../../ to w3c.github.io/aria-practices/

would need to remove that script when publishing to TR

can change the links to reference the directoryindex now, and add the script later

AOB

none

Next Meeting

Next meeting is 3 August 2016

ARIA Editors

20 Jul 2016

Attendees

Contents