- From: Michael Cooper <cooper@w3.org>
- Date: Mon, 05 Aug 2013 11:08:48 -0400
- To: James Craig <jcraig@apple.com>
- CC: PF <public-pfwg@w3.org>
- Message-ID: <51FFC000.8050508@w3.org>
Hi James - we had a brief chat in the ARIA call today about what to do with the ARIA 1.1 source. I explained that you and I had agreed to put the source in the CVS and not migrate to Mercurial until 2.0. The primary reason for this was to keep the existing tool chain in place, since the 1.1 spec will be very close to the 1.0 spec. However, a couple additional use cases came up in the call: in Mercurial it is easier for people who aren't official editors to add content, so we don't have a bottleneck if a couple of us happen to be away at the same time; and the timeline to ARIA 2.0 may be longer than we want to wait to adjust the tool chain. After kicking around these use cases, we cooked up the following suggestion: * Put the ARIA 1.1 spec in Mercurial now, instead of putting it in CVS. * Keep the current XSLT-based generator for the ARIA 1.1 spec, in the short term. This will require a little bit of tweaking paths in the generator environment on your and my machines but shouldn't be horrible. * Publish a public editors' draft of ARIA 1.1 with the preliminary proposal for ARIA-describedat, this September as proposed. The editors' draft would probably be in CVS somewhere; people could of course load up the Mercurial version but it wouldn't have the pieces that are provided by the generator. * At some point after this, probably next year sometime, implement a new build environment. Currently the expectation is that it will be Respec-based with custom scripts in place of the XSLT-based generator. The timeline for transition is flexible, based on when there is a window between other more urgent tasks. At this point we retire the XSLT-based generator and start pointing to the Mercurial version as the sole editors' draft location. Is this a plan that sounds ok to you? If so I can set it up in Mercurial, unless you'd like to so you can control how the branch is set up. Michael -- Michael Cooper Web Accessibility Specialist World Wide Web Consortium, Web Accessibility Initiative E-mail cooper@w3.org <mailto:cooper@w3.org> Information Page <http://www.w3.org/People/cooper/>
Received on Monday, 5 August 2013 15:08:53 UTC