ARIA Editors

<scribe> scribe: MichaelC

agenda order 1, 2, 8

Publication timeline check

FPWDs needed this week

Graphics mapping ok

list of pubs mainly from https://www.w3.org/2016/01/20-aria-editors-minutes#item02

others should be ok

need WDs by next Friday

remember need time for CfC to close before that time

scroll-to-fragID issue https://github.com/w3c/aria/pull/256

new styles and respec broken

yesterday new TR styles became official, and Respec updated

the updates are broken in Respec

some of the hooks we use appear not to be working

and fixup.js, required to be added to docs, seems to breaking things

Shane working with other Respec maintainers to fix this

there is a chance we´ll have to change our resolveReferences; if so Shane will do and alert everyone

scroll-to-fragID issue https://github.com/w3c/aria/pull/256

had a pull request, that was working until the respec rewrite broke it

<Zakim> ShaneM, you wanted to comment

but this only affects live docs, not the static ones

so ok to pull in change

RESOLUTION: accept Joseph´s pull request

Error recovery procedures

https://xkcd.com/1597/

if something breaks for you, make sure to fix it before pushing to server

can ask for help from other editors

also it´s often easier to blow away the repo and try again with fresh clone

Cleaning old branches, starting with merged branches in https://github.com/w3c/aria/branches/stale

there are lots of old branches

some of which have been merged, so probably safe to remove

other stale branches haven´t been committed to in a while, should check if they can be removed

one question is when editor has merged a branch, should s/he clear the branch?

means editors need to be careful not to combine features / actions in a branch, because work in progress could get blown away

RESOLUTION: editor gets to clear branches after merging them into master - authors, expect this!
... authors should use working branches for one item only. Create separate branches for separate actions.

everyone, check your own branches and remove if reasonable. later we´ll see if further cleanup needed

zak j

<Zakim> joanie, you wanted to ask about procedures in this regard

Migrate to submodules at version change? https://www.git-scm.com/book/en/v2/Git-Tools-Submodules

this would allow us to track specs in separate repositories yet keep the shared elements together[

it would probably mean a repository per spec

plus a gathering repository that includes the others as sub-modules

would need to sort out how the common elements should be referenced

(Respec data-include does accept a URI)

can split the files with their histories, but there is a chunk of work on it

might replace the repository re-org action

AOB

none

Next meeting

March 16, 2016

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)

Found embedded ScribeOptions:  -final

*** RESTARTING DUE TO EMBEDDED OPTIONS ***

Found Scribe: MichaelC
Inferring ScribeNick: MichaelC
Present: ShaneM Joanmarie_Diggs MichaelC Michiel Rich fesch Rich_Schwerdtfeger Fred Tzviya JamesN Joseph_Scheuhammer
Agenda: https://lists.w3.org/Archives/Public/public-aria-editors/2016Mar/0000.html
Got date from IRC log name: 02 Mar 2016
Guessing minutes URL: http://www.w3.org/2016/03/02-aria-editors-minutes.html
People with action items: 

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