Re: discrepancy re. github policy for CGs

On 02/03/2023 14:45, Dominique Hazael-Massieux wrote:
> There are hacks that allows to do client-side redirects from 
> w3c.github.io - e.g. 
> https://github.com/w3c/w3c.github.io/blob/main/DOM-Level-3-Events-code/index.html

This could do it. But we can't use that trick for a whole directory, 
this needs to be created for each individual file, right? (which should 
be feasible, although a little tedious)
>
> If that's not sufficient or acceptable, maybe we could give an 
> exception to allow continued usage of the w3c org since the policy 
> didn't really discuss or consider that situation?
I expect that a significant number of CGs are using GH pages, so this 
should be a real issue if migration is required/encouraged...
>
> Dom
>
> Le 02/03/2023 à 14:37, Ian Jacobs a écrit :
>> [Adding Dom]
>>
>> I don’t believe we plan to migrate existing CG repos from W3C to 
>> W3C-CG. I don’t think we would object if you wanted to move your
>> previous repo to W3C-CG. However, if links break and there’s nothing 
>> W3C can do to prevent that, then it seems worse to move the
>> repo than to have repos under 2 organizations. So my advice would be 
>> “don’t move it.”
>>
>> Dom, thoughts?
>>
>> Ian
>>
>>> On Mar 2, 2023, at 3:04 AM, Pierre-Antoine Champin 
>>> <pierre-antoine@w3.org> wrote:
>>>
>>>
>>> On 01/03/2023 22:51, Ian Jacobs wrote:
>>>> Hi Pierre-Antoine,
>>>>
>>>> Thank you _very much_ for this report. I have updated the CG 
>>>> infrastructure documentation:
>>>>   https://www.w3.org/community/about/tool/#github

>>>
>>> No problem ;)
>>>
>>> As we are at it: the N3 CG is considering opening two new 
>>> repositories (that's how I discovered the new policy...)
>>>
>>> But they currently have one repo in the w3 organization (w3c/N3). It 
>>> might be confusing to have our repos scattered across the two 
>>> organizations, so we may require to moved the old one  to w3c-cg/N3 
>>> (maybe there even is a plan to do that for all CG repos?).
>>>
>>> The prooblem is: when a repo is renamed or relocated to a new 
>>> organisation, github manages the redirections for repo pages on 
>>> github.com [1, 5th bullet]... but not for the gh-pages on github.io! 
>>> So this would break any link / bookmarks that people may have on the 
>>> pages the CG has published in the past. Which is really not in line 
>>> with W3C policy about persistent URIs...
>>>
>>> What would be your advice on that?
>>>
>>>    pa
>>>
>>> [1] 
>>> https://docs.github.com/en/repositories/creating-and-managing-repositories/transferring-a-repository#whats-transferred-with-a-repository

>>>
>>>>
>>>> Ian
>>>>
>>>>> On Mar 1, 2023, at 3:10 PM, Pierre-Antoine Champin 
>>>>> <pierre-antoine@w3.org> wrote:
>>>>>
>>>>> This page:
>>>>>
>>>>>      https://www.w3.org/2016/04/cg-support/

>>>>>
>>>>> says that, starting May 2022, CG repos are in the w3c-cg 
>>>>> organisation (instead of w3c)
>>>>>
>>>>> That page
>>>>>
>>>>>      https://www.w3.org/community/about/tool/#github

>>>>>
>>>>> does not reflect that change.
>>>>>
>>>>>    pa
>>>>>
>>>>> <OpenPGP_0x9D1EDAEEEF98D438.asc>
>>>> -- 
>>>> Ian Jacobs <ij@w3.org>
>>>> https://www.w3.org/People/Jacobs/

>>>> Tel: +1 917 450 8783
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> -- 
>>>> Ian Jacobs <ij@w3.org>
>>>> https://www.w3.org/People/Jacobs/

>>>> Tel: +1 917 450 8783
>>>>
>>>>
>>>>
>>>>
>>>>
>