W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > March 2010

[Bug 8893] Clarify how Change Proposals get reviewed and what happens to Change Proposals that do not meet requirements

From: <bugzilla@wiggum.w3.org>
Date: Wed, 03 Mar 2010 16:13:56 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1NmrCu-0008GR-1X@wiggum.w3.org>

Larry Masinter <lmm@acm.org> changed:

           What    |Removed                     |Added
                 CC|                            |lmm@acm.org

--- Comment #1 from Larry Masinter <lmm@acm.org>  2010-03-03 16:13:55 ---
I wasn't sure how the process outlined above applied to the URL change
proposal, which was rejected as not "proper" (and issue CLOSED) because it had
been submitted in two messages instead of one, and the rationale contained a
pointer to the original bug report with rationale rather than copying the
rationale inline.

What are the "formal requirements" for a change proposal anyway?

What's formal about them? Why can't people poll or opinions be solicited for a
change proposal that the proposer believes are explicit enough? 

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 Wednesday, 3 March 2010 16:13:57 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:30:47 UTC