ISSUE-35: Clarify "base" document for Technical Reports change requests
Clarify "base" document for Technical Reports change requests
- State:
- CLOSED
- Product:
- Document life cycle (pre 2014 chapter 7, now chapter 6)
- Raised by:
- Arthur Barstow
- Opened on:
- 2013-07-08
- Description:
- 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.
- Related Actions Items:
- No related actions
- Related emails:
- Re: w3process-ISSUE-35: Clarify "base" document for Technical Reports change requests [Document life cycle (ch 7)] (from chaals@yandex-team.ru on 2013-07-08)
- w3process-ISSUE-35: Clarify "base" document for Technical Reports change requests [Document life cycle (ch 7)] (from sysbot+tracker@w3.org on 2013-07-08)
Related notes:
The relevant document is https://dvcs.w3.org/hg/AB/raw-file/default/tr.html (but nothing stops you referring to the current active chapter 7 - or anything else).
Charles 'chaals' (McCathie) Nevile, 18 Jul 2013, 23:40:07Display change log
