W3C home > Mailing lists > Public > public-aria-editors@w3.org > December 2016

Re: ARIA common files approach

From: Rich Schwerdtfeger <richschwer@gmail.com>
Date: Wed, 7 Dec 2016 15:03:21 -0600
Cc: ARIA Editors <public-aria-editors@w3.org>
Message-Id: <8C2DD2B4-EA98-41A6-BD27-CDD6AE63757D@gmail.com>
To: Michael Cooper <cooper@w3.org>
Who will control common and what is the update process if needed? 

Sent from my iPhone

> On Dec 7, 2016, at 2:38 PM, Michael Cooper <cooper@w3.org> wrote:
> 
> In today's ARIA Editors call we discussed the ongoing issue with handling the common resources when splitting the ARIA repository:
> 
> https://www.w3.org/2016/12/07-aria-editors-minutes.html#item03
> 
> Given intractable problems with getting submodules to work with rawgit, and the need for that feature to work, we revisited forking. The proposal now is to:
> 
> Put the common files in their own repository (aria-common) as previously planned;
> Put copies of the files (forks) in each of the ARIA repositories after we split;
> Set up a commit hook that updates each of the forks whenever an update is pushed to aria-common;
> Document that people should not edit the aria-common forks in repos.
> This isn't the theoretically right way to use git but is practical and achievable, and unblocks the repository split project. We wanted to run the thought past the rest of the editors to see about thoughts before making a firm decision to implement.
> 
> Thoughts?
> 
> Michael
Received on Wednesday, 7 December 2016 21:04:08 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 December 2016 21:04:08 UTC