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

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

           Summary: Clarify how Change Proposals get reviewed and what
                    happens to Change Proposals that do not meet
                    requirements
           Product: HTML WG
           Version: unspecified
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: working group Decision Policy
        AssignedTo: dave.null@w3.org
        ReportedBy: mjs@apple.com
         QAContact: public-html-bugzilla@w3.org
                CC: mjs@apple.com, Paul.Cotton@microsoft.com,
                    rubys@intertwingly.net, mike@w3.org


Larry Masinter said:

"In the escalation process, the chairs review change  proposals, and ask for
resubmission if they believe the change proposal doesn't meet the requirements
for a change proposal. It's not clear how many times this can happen or whether
it affects the deadline."

I replied:

"Carification: When we give review feedback of this kind it is as a courtesy to
the submitter of the Change Proposal. We will try to do it, but it's not
mandatory for us to do it, or for anyone to take our suggestions. Once a Change
Proposal is submitted, there is no firm deadline. The author of the Change
Proposal can make revisions up until the time we are ready to call for
consensus, issue a poll, or otherwise drive to a decision. Others can also
submit additional Change Proposals. Thus, suggesting improvements can happen
any number of times and does not affect any deadlines.

Possible Policy Update: We think the Decision Policy should state that Change
Proposals that do not meet the formal requirements for a Change Proposal will
fail; but Change Proposal authors will be given ample opportunity to make
revisions and resolve any problems."


-- 
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 Sunday, 7 February 2010 06:23:12 UTC