W3C home > Mailing lists > Public > public-jlreq-admin@w3.org > April to June 2020

Re: Copying jlreq documents to www.org/TR

From: 木田泰夫 <kida@mac.com>
Date: Thu, 28 May 2020 22:57:37 +0900
Cc: public-jlreq-admin@w3.org
Message-Id: <8E7020E5-4469-4D38-8526-CB39BE430A98@mac.com>
To: r12a <ishida@w3.org>
Hi Richard,

Thank you for explaining the background. Given the document is already in use, and it will be like a live document with constant updates, I think we can review it after it was brought to FPWD.

I am still waiting for possible feedback from TF members. I will get back to you by end of the week.

best,

- kida

> 2020/05/28 20:43、r12a <ishida@w3.org>のメール:
> 
> 
> hi Kida-san,
> 
> Could you complete the review by the end of next week?  I have many documents to publish, and it will save me time to publish them as a batch. I'd like to begin the process towards the end of next week.
> 
> Btw, note that this really boils down to just getting a copy of the document into TR. We don't need to make the document look complete in any way. FPWD is the beginning of a draft, not the end. 
> 
> The ED is already in use as a reference, and we are currently pointing people to that. What we aim to change here is simply that we point people to the TR copy instead. So what i'm saying is that nothing much will change from the current situation, other than that we will link to the document externally using a slightly different URL.  
> 
>  If proposed changes arise from the review, they should be handled in the same way, via the GH issues, and as changes are made we should resynch the ED and TR working draft constantly (using the quick process i'll set up using echidna tools, which largely makes publication a simple button press.  We can't use echidna, however, until we have an initial version of the document on TR. ) I don't want the review to delay us getting that initial FPWD set up - changes can be made on a daily or hourly basis as they become ready.
> 
> thanks.
> ri
> 
> 
> 木田泰夫 wrote on 28/05/2020 09:56:
>> Hi Richard, Good morning!
>> 
>> Actually, we would like to review it to make sure it is ready for FPWD. Could you give us a week or so?
>> 
>> - kida
>> 
>>> 2020/05/28 7:57、木田泰夫 <kida@mac.com>のメール:
>>> 
>>> 
>>> Thank you Richard. I have no objections. I will double check with the group and get back to you soon.
>>> 
>>> - kida
>>> 
>>>> 2020/05/28 1:28、r12a <ishida@w3.org>のメール:
>>>> 
>>>> 
>>>> dear Kida-san & jlreq layout task force folks,
>>>> 
>>>> I'd like to publish an up-to-date copy of the following respec document on the /TR space of the W3C server, so that people pointing to the documents can use www.org URLs, rather than GitHub ones to find the content.
>>>> 
>>>> Japanese Gap Analysis
>>>> https://w3c.github.io/jlreq/gap-analysis/
>>>> 
>>>> This means publishing a First Public Working Draft.  Note that FPWD status indicates the beginning of work on a document; the document is not expected to be in a near final state.
>>>> 
>>>> Unless there are objections from this group, i will recommend the publication to the Internationalization Working Group (which publishes mlreq 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
> 

Received on Thursday, 28 May 2020 13:58:30 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 28 May 2020 13:58:30 UTC