Re: [admin] Migrating away from W3C Mercurial

+1

On 29 July 2015 at 16:48, Manu Sporny <msporny@digitalbazaar.com> wrote:

> While processing the latest use cases publication through the W3C
> publication team, we hit a snag with synchronizing the work that we do
> on Github to the W3C systems. It's an exception-prone process. It didn't
> take long to fix the issue, but the publication team suggested that we
> stop sync'ing Github to W3C systems.
>
> We were under the impression that W3C Process required us to sync to W3C
> systems, as this was communicated as a requirement to the RDF WG when we
> did JSON-LD. That is no longer the case (or never was).
>
> All we need to do is send in a request to the W3C systems team to
> redirect the source control system on W3C to Github. This would remove
> an error-prone step for publication and be one less place the group
> would have to keep in sync for our documents. Archival of our work will
> still occur on Github and on every editor's machine, so the likelihood
> of loosing the day-to-day work permanently is fantastically low. All
> published snapshots of working drafts will still be stored and backed up
> on W3C systems.
>
> I suggest we eliminate the exception-prone synchronization step to W3C
> systems. There really isn't a downside to doing this. I won't send the
> request out until next Monday to give group members the opportunity to
> object to the elimination of this step in our document editing workflow.
>
> -- manu
>
> --
> Manu Sporny (skype: msporny, twitter: manusporny, G+: +Manu Sporny)
> Founder/CEO - Digital Bazaar, Inc.
> blog: Web Payments: The Architect, the Sage, and the Moral Voice
> https://manu.sporny.org/2015/payments-collaboration/
>
>