revert requests

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

revert requests

Shelley Powers
What is the procedure for revert requests? How long before we can expect
the co-chairs to acknowledge the revert request?

Shelley

Reply | Threaded
Open this post in threaded view
|

Re: revert requests

Sam Ruby-2
On 06/17/2011 12:22 PM, Shelley Powers wrote:
> What is the procedure for revert requests? How long before we can expect
> the co-chairs to acknowledge the revert request?

Relevant links:

http://dev.w3.org/html5/decision-policy/decision-policy-v2.html

"If any Working Group member sees a change go into any draft subject to
a cutoff that seems controversial and likely to reduce rather than
increase consensus, the correct step is to let the Chairs know, ideally
via a post to the public list."

http://lists.w3.org/Archives/Public/public-html/2010Sep/0125.html

"If any Working Group member sees a change go into any Last Call-track
draft after the October 1st cutoff that seems controversial and likely
to reduce rather than increase consensus, please let the Chairs know and
we will make the call."

  - - -

My input (without having vetted it yet with my co-chairs) is that I have
yet to see any technical justification for this revert request, so I
would not support it at this time.  I do, however, see that the
TrackerRequest keyword has been added, and if raising an issue will
ultimately result in a Change Proposal that includes a technical
rationale, I would support the opening of an issue.  Note that this step
doesn't need to wait for a chair action, any of the following may take
this step:

http://www.w3.org/2000/09/dbwg/details?group=41863

  - - -

Finally, if there are comments on the process for changes made without
prior discussion on the working group, I encourage them to be recorded
in the Decision Policy bug on that topic:

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

> Shelley

- Sam Ruby


Reply | Threaded
Open this post in threaded view
|

Re: revert requests

Shelley Powers
In reply to this post by Shelley Powers
Well, I am not a working group member, so that leaves me out. Which you
very well know.

I was under the impression that HTML5 was in Last Call, and open for
review from people outside of the group.

I was also under the impression that there was a procedure in place to
control major changes to the HTML5 specification. The addition of CORS
and crossorigin is a major change.

There was no justification for adding this change. It was just plopped
in after a minor discussion in a non W3C email list. It was not given
due diligence. I was assuming, from past communications issued by the
co-chairs of the group, that the person who wants to add the major
change is the one who must provide a technical argument justifying the
addition--not up to those of us who disagree with the change spending
the next six months fighting for something to be removed that was added
after a few hours of discussion in an IRC and a non-W3C email list.

Is HTML5 is Last Call or not? Does the HTML WG invite outside comments,
or not? If so, then provide a procedure in place for those outside the
group to actually participate without having walls throw into our faces.

And please: consistency in responding to different individuals would be
appreciated.

Thank you