[Bug 11197] New: Require Change Proposals in order to reintroduce a change related to a revert


           Summary: Require Change Proposals in order to reintroduce a
                    change related to a revert
           Product: HTML WG
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: working group Decision Policy
        AssignedTo: dave.null@w3.org
        ReportedBy: rubys@intertwingly.net
         QAContact: public-html-bugzilla@w3.org
                CC: mjs@apple.com, Paul.Cotton@microsoft.com,
                    rubys@intertwingly.net, mike@w3.org

We have an instance of a change made after the last call cutoff that was made
without any discussion on public-html and was not made in response to any bug
report.  This caused people to object, and the chairs (per the Enhanced Change
Control policy in effect) asked for it to be reverted, and the editor refused,
not once, but twice to do so.  The chairs then requested the the WG Staff make
the change that the editor was unwilling to do.

Again, without participating in the discussion or any bug report, the editor
made another change, and this has resulted in a second round of discussions and
even bug reports.  At this time, the outcome of that is unclear.  In any case,
we are rushing to resolve an issue that is not related to getting us to last

The proposed solution is that we require a change proposal, including rationale
and a description of the proposed change, after which the chairs will seek
amicable resolution.  Failing that, alternate change proposals will be sought.

At a minimum, this will allow us to more predictably schedule our time.

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 Tuesday, 2 November 2010 14:04:47 UTC