On 06/17/2011 08:51 PM, Shelley Powers wrote:
Well, I am not a working group member, so that leaves me out. Which you
very well know.

I also very well know that this is entirely by your choice.

You can call bullshit[1] if you like, and direct all of your anger at me, but all I did was quote long standing and published policy -- and point you in the direction of how you can effect change

As to you not being a working group member, you won't let people talk about it[2], but you continue to bring it up. I ask you to pick one. Either discuss fully why you chose not to be a member of the working group, or don't bring this up again.

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

Comments will turn into bug reports, bug reports into issues, and issues into decisions.

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.

I cited the procedure that is in place, and encouraged you to participate in the bug report on that procedure.

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.

I cited the procedure that is in place, and encouraged you to participate in the bug report on that procedure.

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.

HTML5 is in last call. Outside comments will result in bug reports. We are following the procedures that we have documented and agreed to.

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

And a request from me: if you ask a question about a policy, and I point you to a bug report, please don't ignore that response and ask what amounts to essentially the same question again.

We are following the documented procedures. The way to change those procedures is via bug reports. Until those procedures are changes, they are the procedures that we are operating under.

Thank you

- Sam Ruby

[1] http://twitter.com/shelleypowers/status/81886893989560321
[2] http://twitter.com/shelleypowers/status/79659265396178944

Reply via email to