Re: [whatwg] A New Way Forward for HTML5 (revised)

2009-07-27 Thread Sam Ruby
John Foliot wrote: Peter Kasting wrote: It seems like the only thing you could ask for beyond this is the ability to directly insert your own changes into the spec without prior editorial oversight. I think that might be what you're asking for. This seems very unwise. Really? This appears

Re: [whatwg] A New Way Forward for HTML5 (revised)

2009-07-27 Thread Peter Kasting
On Mon, Jul 27, 2009 at 12:06 PM, John Foliot jfol...@stanford.edu wrote: That said, the barrier to equal entry remains high: http://burningbird.net/node/28 I don't understand. That page says We're told that to propose changes to the document for consideration, we need to ... and then a long

Re: [whatwg] A New Way Forward for HTML5 (revised)

2009-07-27 Thread Sam Ruby
John Foliot wrote: Sam Ruby wrote: Really? This appears to be exactly the single, special status privilege currently reserved for Ian Hickson. False. ...and yes, I stand corrected. Although the *impression* that this is the current status remains fairly pervasive; however I will endeavor

Re: [whatwg] A New Way Forward for HTML5 (revised)

2009-07-27 Thread Manu Sporny
Peter Kasting wrote: On Mon, Jul 27, 2009 at 12:06 PM, John Foliot jfol...@stanford.edu mailto:jfol...@stanford.edu wrote: That said, the barrier to equal entry remains high: http://burningbird.net/node/28 I don't necessarily agree with most of Shelley's take on the situation. I do

Re: [whatwg] A New Way Forward for HTML5 (revised)

2009-07-26 Thread Manu Sporny
Michael Enright wrote: On Thu, Jul 23, 2009 at 2:48 PM, Manu Spornymspo...@digitalbazaar.com wrote: I can git clone the Linux kernel, mess around with it and submit a patch to any number of kernel maintainers. If that patch is rejected, I can still share the changes with others in the

Re: [whatwg] A New Way Forward for HTML5 (revised)

2009-07-26 Thread Peter Kasting
On Sun, Jul 26, 2009 at 7:16 PM, Manu Sporny mspo...@digitalbazaar.comwrote: I'm not proposing that we allow people to directly stomp all over Ian's specification - that wouldn't help anything. I am also not suggesting that Ian should change how he authors his HTML5 specification. What I'm

Re: [whatwg] A New Way Forward for HTML5 (revised)

2009-07-26 Thread Maciej Stachowiak
On Jul 26, 2009, at 8:30 PM, Peter Kasting wrote: So far you have not given a use case (that I've seen) so much as a vague assertion that because the number of spec contributors is in the hundreds rather than tens of thousands, there is some not-well- defined barrier to entry in the

Re: [whatwg] A New Way Forward for HTML5 (revised)

2009-07-26 Thread Manu Sporny
Peter Kasting wrote: On Sun, Jul 26, 2009 at 6:26 PM, Manu Sporny mspo...@digitalbazaar.com mailto:mspo...@digitalbazaar.com wrote: If people sending emails containing proposals, and having the editor directly respond to all of those emails, frequently by changing the spec,

Re: [whatwg] A New Way Forward for HTML5 (revised)

2009-07-26 Thread Manu Sporny
Maciej Stachowiak wrote: WebKit also has, arguably, a more open development model than either Linux or HTML5. There are many reviewers with the authority to approve a checkin, even more people with the ability to directly commit to the code after review, and even more people who have submitted

Re: [whatwg] A New Way Forward for HTML5 (revised)

2009-07-26 Thread Maciej Stachowiak
On Jul 26, 2009, at 9:27 PM, Manu Sporny wrote: Maciej Stachowiak wrote: I would also caution that, by their nature, standards projects are not quite the same thing as software projects. While the way HTML5 has been run is much more in the spirit of open source than many past Web

Re: [whatwg] A New Way Forward for HTML5 (revised)

2009-07-26 Thread Jeremy Orlow
On Sun, Jul 26, 2009 at 8:58 PM, Maciej Stachowiak m...@apple.com wrote: On Jul 26, 2009, at 9:27 PM, Manu Sporny wrote: Maciej Stachowiak wrote: I would also caution that, by their nature, standards projects are not quite the same thing as software projects. While the way HTML5 has been