Gregory J. Rosmaita wrote:
...
all of this begs the question, what function does the WG serve in the
HTML5 drafting process? are WG members intended to raise and work on
issues in their particular areas of expertise, or are WG members simply
glorified graduate students, performing research and grunt work for
the editor, chairs and staff contact only on topics approved by the
editor, chairs, and staff contact? that is not the collaborative
dynamic i have experienced in my dozen years participating in W3C as an
invited expert, nor as a former member of an domain coordination group
...
I have to agree with Gregory here.
Collaboration in the HTML WG suffers from the fact that there really
never was a real transition from a WHATWG work item to a W3C work item
(I think some WG members assume this is a feature, but I don't).
For those who feel that their concerns or proposals are not taken
seriously, the issue tracker is an obvious way to document that there's
an open issue, and to track it. I've used it that way myself, so please
don't blame only those who opened the last few issues.
At the end of the day, the HTML5 spec is so huge that we need *some*
machinery to track open issues, their discussion, and how it get
resolved (or not). If the issue tracker is not for that, what else
should it be used for? I don't think that the editor's inbox qualifies,
even if it is exposed through a web interface.
Best regards, Julian
