W3C home > Mailing lists > Public > public-w3process@w3.org > January 2017

Re: Mirroring Re: Moving the process to github…

From: fantasai <fantasai.lists@inkedblade.net>
Date: Sat, 7 Jan 2017 23:06:03 -0500
To: chaals@yandex-team.ru, "ted@w3.org" <ted@w3.org>, Jeff Jaffe <jeff@w3.org>, Coralie Mercier <coralie@w3.org>, Revising W3C Process Community Group <public-w3process@w3.org>
Message-ID: <88dedd4d-1f8d-19c1-42ed-1bc3cd954fc2@inkedblade.net>
On 01/04/2017 08:57 PM, chaals@yandex-team.ru wrote:
>
>>>  >    d) A read-write mercurial mirror of the git repos on
>>>  hg.csswg.org
>>>
>>>  Hmm. Was that hard to set up? If we could match that on the current
>>>  dvcs.w3.org repo we would have a continuous history…
>>
>> Most have decommissioned their mercurial repo when they move to github
>> (with a redirect) and I think that is the preferred practice. In fact
>> we would like to retire dvcs.w3.org or rather mercurial and perhaps
>> have dvcs.w3.org a live checkout of master (or gh-pages) branch of all
>> github.com/w3c repos but this is a bigger picture item beyond this
>> discussion.
>
> Based on Geoffrey's explanation, I'm happy to drop this. I don't think there is a lot of real value beyond archiving, and I think we can live with a simple swap point if the archive still actually exists. So I'm not going to put much effort into following this up.

Importing the full history into git should be fine. As Peter mentioned,
there are historical reasons why the CSSWG has a read-write hg mirror;
those don't apply to most groups. But having a full, up-to-date copy of
the repo on W3C servers is imho useful and important for the sake of
archiving.

~fantasai
Received on Monday, 9 January 2017 18:08:13 UTC

This archive was generated by hypermail 2.3.1 : Monday, 9 January 2017 18:08:13 UTC