w3process-ISSUE-35: Clarify "base" document for Technical Reports change requests [Document life cycle (ch 7)] from Revising W3C Process Community Group Issue Tracker on 2013-07-08 (public-w3process@w3.org from July 2013)

From: Revising W3C Process Community Group Issue Tracker <sysbot+tracker@w3.org>
Date: Mon, 08 Jul 2013 12:27:27 +0000
To: public-w3process@w3.org
Message-Id: <E1UwAXP-0006Ag-Vx@tibor.w3.org>

w3process-ISSUE-35: Clarify "base" document for Technical Reports change requests [Document life cycle (ch 7)]

http://www.w3.org/community/w3process/track/issues/35

Raised by: Arthur Barstow
On product: Document life cycle (ch 7)

The first order problem is that it is not clear which document should be used as the basis for change requests for the Technical Reports process. It appears there are at least two candidates:

1. http://www.w3.org/2005/10/Process-20051014/tr.html

2. Chaals' document

After that is clarified, the canonical document must be placed in some type of source code control system that facilitates creating and proposing patches. My preference is to use GitHub so PRs can be used. W3C's Hg/Mercurial would be second preference. Please do NOT use CVS.

Received on Monday, 8 July 2013 12:27:28 UTC