[Bug 11168] New: Remove WhatWG and html5.org references in status section of document

http://www.w3.org/Bugs/Public/show_bug.cgi?id=11168

           Summary: Remove WhatWG and html5.org references in status
                    section of document
           Product: HTML WG
           Version: unspecified
          Platform: Macintosh
        OS/Version: Mac System 9.x
            Status: NEW
          Severity: normal
          Priority: P3
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: shelleyp@burningbird.net
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
                    public-html@w3.org


The status section of the HTML5 spec contains the following:

The latest stable version of the editor's draft of this specification is always
available on the W3C CVS server and in the WHATWG Subversion repository. The
latest editor's working copy (which may contain unfinished text in the process
of being prepared) contains the latest draft text of this specification
(amongst others). For more details, please see the WHATWG FAQ.

There are various ways to follow the change history for the HTML
specifications:

E-mail notifications of changes
    HTML-Diffs mailing list (diff-marked HTML versions for each change):
http://lists.w3.org/Archives/Public/public-html-diffs/latest
    Commit-Watchers mailing list (complete source diffs):
http://lists.whatwg.org/listinfo.cgi/commit-watchers-whatwg.org
Real-time notifications of changes:
    Generated diff-marked HTML versions for each change:
http://twitter.com/HTML5
    All (non-editorial) changes to the spec source: http://twitter.com/WHATWG
Browsable version-control record of all changes:
    CVSWeb interface with side-by-side diffs: http://dev.w3.org/cvsweb/html5/
    Annotated summary with unified diffs:
http://html5.org/tools/web-apps-tracker
    Raw Subversion interface: svn checkout http://svn.whatwg.org/webapps/

The W3C HTML Working Group is the W3C working group responsible for this
specification's progress along the W3C Recommendation track. This specification
is the 25 October 2010 Editor's Draft.

Work on this specification is also done at the WHATWG. The W3C HTML working
group actively pursues convergence with the WHATWG, as required by the W3C HTML
working group charter.

---

There is no need to continue referencing parallel organizations in the spec.
This is a W3C document, not a WhatWG document. It should only reference W3C
resources. To continue with the parallel references only serves to add
confusion. In addition, the W3C has no control over the servers at the
WhatWG--including their stability, and their content. 

Details:

Remove the reference to the WhatWG subversion server. There is a reference to
the W3C CVS server, which is sufficient. In addition, the material at the
WhatWG subversion server differs from the material at the W3C server. Such
differences generate confusion.

Remove the commit-watchers-list for the WhatWG. We already have  way for people
to follow commits in the W3C space. In addition, the WhatWG work is not
identical to the W3C's work, and commits in the WhatWG space may generate
confusion about what is in the W3C HTML5 spec.

Correct the reference labeled "CVSWeb interface with side-by-side diffs". It
seems to be pointing to a directory, rather than a specific document with side
by side differences.

Remove the reference to the annotated differences document at html5.org, which
again is to an external web server outside of the control of W3C. 

Remove the reference to subversion access to WhatWG documents. Not pertinent,
not useful for those accessing the W3C documents. 

Remove the paragraph mentioning work is also being done at the WhatWG. This is
a spec, not a marketing brochure. People don't need to have the "convergence"
between the two groups embedded in a tech spec.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Friday, 29 October 2010 14:38:56 UTC