Re: Copying IIP documents to www.org/TR

hi Alolita,

No. Nothing changes other than that we have a copy of the current 
documents on https://www.w3.org/TR/, and that:

1. external URLs pointing to the content of those documents (such as 
from the Language Enablement Index) will be transitioned to point to the 
TR space rather than to the ED.
2. as additions are made to the ED, we synch regularly to TR

ri

Alolita Sharma wrote on 27/05/2020 23:22:
> Sounds good. Does that mean we should fork and continue the project 
> work on GitHub elsewhere on a non w3c repo?
>
> Alolita
>
> On Wed, May 27, 2020, 9:29 AM r12a <ishida@w3.org 
> <mailto:ishida@w3.org>> wrote:
>
>     dear IIP task force folks,
>
>     I'd like to publish up-to-date copies of the IIP respec documents
>     on the /TR space of the W3C server, so that people pointing to the
>     documents can use www.org <http://www.org> URLs, rather than
>     GitHub ones to find the content.
>
>     This means publishing a First Public Working Draft for the
>     following documents.  Note that FPWD status indicates the
>     beginning of work on a document; the document is not expected to
>     be in a near final state.
>
>     Bengali Gap Analysis
>     https://w3c.github.io/iip/gap-analysis/beng-gap.html
>
>     Devanagari Gap Analysis
>     https://w3c.github.io/iip/gap-analysis/deva-gap.html
>
>     Gurmukhi Gap Analysis
>     https://w3c.github.io/iip/gap-analysis/guru-gap.html
>
>     Gujarati Gap Analysis
>     https://w3c.github.io/iip/gap-analysis/gujr-gap.html
>
>     Tamil Gap Analysis
>     https://w3c.github.io/iip/gap-analysis/taml-gap.html
>
>     Tamil Layout Requirements
>     https://w3c.github.io/iip/tamil/
>
>
>     Unless there are objections from this group, i will recommend the
>     publication to the Internationalization Working Group (which
>     publishes IIP documents),  submit a transition request upon
>     approval, and publish the documents.
>
>     Going forward, we should regularly publish updates to the /TR
>     space as changes accrue to the GitHub Editor's Draft. To
>     facilitate that, we have the echidna tool, which makes publication
>     relatively simple and quick.  We don't need to go through the
>     Webmaster to publish ordinary Working Drafts (WDs) using echidna;
>     we only need to follow that more complicated transition process
>     for publication of a First Public Working Draft (FPWD) or Working
>     Group Note.  The policy of the Internationalisation WG, which
>     publishes the documents for you, is to allow updates to the /TR
>     space at the discretion of the editors of the document (no prior
>     approval needed) for ordinary Working Draft updates.
>
>     Please let me know by the end of this week if you have any
>     objection to me proceeding with this.
>
>     If i receive no objection, i'll move ahead.
>
>     thanks,
>     ri