<div class="gmail_quote">On Thu, Jul 23, 2009 at 2:48 PM, Manu Sporny <span dir="ltr"><<a href="mailto:msporny@digitalbazaar.com">msporny@digitalbazaar.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">contribute ideas: great!</div>
scrutinize them: wonderful!<br>
form consensus: fail (but that's what the W3C is for, right?)<br>
produce: fail (unless we don't want to scale the community)<br>
<br>
Ian is really the only one that is actively allowed to produce anything<br>
of significance in WHAT WG. In general, if he doesn't agree with you, it<br>
doesn't go in.</blockquote><div><br></div><div>It's already been stated explicitly multiple times in the past that the HTML5 process is not ultimately consensus-driven, so this shouldn't be news to anyone. I for one consider that a feature, not a bug.</div>
<div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">I think it's fair to say that one needs to have a pretty<br>
significant chunk of time on their hands as well as technical chops to<br>
make a contribution to the HTML5 specification.</blockquote><div><br></div><div>Incorrect. All sorts of people have made contributions of small corrections, opinions on issues, spec proposals, etc. Ian has publicly committed to reply to every email and so far I see him doing precisely that; frequently this results in spec changes. When people's opinions are ultimately rejected, it is not without due consideration first.</div>
<div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">To approach the issue from another angle, we have roughly 1,000 members<br>
on this mailing list and could have close to 1 billion people[1] that<br>
could be using some form of HTML by 2012, a number of those are web<br>
developers (read: a huge developer base).<br>
<br>
The Linux kernel mailing lists have close to 30,000 members[2], and I<br>
don't think it's a stretch to say that there are fewer kernel developers<br>
in the world (read: small developer base) than there are web developers<br>
and designers. So, I've been wondering about the 30:1 discrepancy.</blockquote><div><br></div><div>You're comparing non-analogous situations. LKML is inherently of interest to all kernel developers, pretty much by definition. The HTML spec creation process is not inherently interesting to all web developers.</div>
<div><br></div><div>A closer analogy would be to the engineers working on HTML support in UAs. I suspect that this mailing list _is_ inherently of interest to that group.</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
We don't give anybody the impression</blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
here that they could directly impact the specification if they so<br>
desired.</blockquote><div><br></div><div>If people sending emails containing proposals, and having the editor directly respond to all of those emails, frequently by changing the spec, does not give you the impression you can impact the specification, I'm not sure what would.</div>
<div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">I can git clone the Linux kernel, mess around with it and submit a patch<br>
to any number of kernel maintainers. If that patch is rejected, I can<br>
still share the changes with others in the community.</blockquote><div><br></div><div>Similarly, nothing prevents UA authors from coding any feature they wish and hoping it will gain traction. Similarly, nothing in the HTML5 process prevents anyone from proposing a feature that has been rejected by HTML5, and attempting to convince UA authors to support it directly. To the degree that these don't happen, it is because practical considerations make success unlikely: it is much more difficult for a random web developer to convince a vendor to support his idea in a particular UA than for a random coder to post a patch online alongside a modified kernel build.</div>
<div><br></div><div>(However, it is not impossible: at least Firefox and Google Chrome can be built, as non-branded versions, from source by any interested party; and in fact that capability has been used for precisely the above purposes: see e.g. Iceweasel.)</div>
<div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Similarly, people<br>
that are creating user agents tend to not care about examples (in<br>
general)</blockquote><div><br></div><div>Speaking as one of those people, you are completely mistaken. Examples are highly useful to UA authors. And implementation details are occasionally useful to web developers, insofar as they document expected behaviors very precisely and thus are useful when trying to test how real-world UA behaviors differ.</div>
<div><br></div><div>I think the only valid point here is that web developers trying to read the spec directly probably want the "implementation details" as a reference rather than inline.</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">They should be able to edit /something/ lasting, publish it for review,</div>
and rise or fall on the merits and accuracy of their specification<br>
language. They are not being given the opportunity to do so.</blockquote><div><br></div><div>Anyone can post a proposal anywhere on the web, which they themselves edit. If they want the imprimatur of the WHATWG, then it seems reasonably to expect that that proposal would have to be accepted by the editor(s) of that group.</div>
<div><br></div><div>I'm not sure why there is a perceived lack of clarity here. Rejected proposals are always given concrete rationale for rejection (IMO).</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
it<br>
was meant as a feeler document to see how this community would react to<br>
the proposed changes.</blockquote><div><br></div><div>For my part, I would be very unhappy to see the HTML5 process made more consensus-driven; I much prefer systems that approximate benevolent dictatorships, and I don't perceive the current leadership of the group to be insufficiently responsive to communication.</div>
<div><br></div><div>PK </div></div>