- From: <bugzilla@wiggum.w3.org>
- Date: Sun, 07 Feb 2010 21:01:40 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8892 --- Comment #6 from Laura Carlson <laura.lee.carlson@gmail.com> 2010-02-07 21:01:40 --- Sam wrote: > I'll postulate that the reaction to the changes is addressing a > symptom, but not the underlying problem. I agree that clear definition of terms and communication is a problem, Sam. But beneath those has been a fundamental disagreement in the concept of and approach to consensus. In July 2008 the HTML5 editor wrote: <quote> The HTML5 work isn't using the traditional W3C approach, and will never use a consensus approach so long as I am editor. Consensus simply isn't a good way to get technically solid specifications, and is in any case basically impossible to achieve in a group with hundreds of participants such as this one. </quote> http://lists.w3.org/Archives/Public/public-html/2008Jul/0354.html <quote> I have no intention of developing HTML5 based on consensus, and will continue to base decisions on the weight of technical arguments without regard to the number of people who hold opinions and without attempting to wait for everyone to agree on a topic before moving forward. I certainly won't put the W3C process above bringing the Web forward to the best of my ability, whatever that may be. I have been very clear about this since well before I was appointed co-editor in the W3C HTMLWG. </quote> http://lists.w3.org/Archives/Public/public-html/2008Jul/0359.html Has the editor's position on and approach to consensus changed? An editor trying to reach consensus would indeed be a positive achievement and help allay worst possible fears. How can that be addressed in a policy? -- 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 21:01:42 UTC