Fwd: Copying jlreq documents to www.org/TR

みなさま、JLReq のアップデートを www.w3c.org/TR に公開するとのこと、問題はないかと思いますがいかがでしょう？


以降、w3c i18n グループのポリシーにより、アップデートは特に許可を得ることなくエディターの判断で行えるとのこと。GitHub にあるエディタードラフトに溜まった修正を反映するために適宜アップデートされてゆくことが期待されているとも言えましょう。

木田

> 差出人: r12a <ishida@w3.org>
> 日時: 2020年5月28日 1:28:01 JST
> 宛先: public-jlreq-admin@w3.org
> 件名: Copying jlreq documents to www.org/TR
> 
> 
> 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