<div class="gmail_quote">I have only responded below to the parts of your email that I think are critical to the point you're making (as I understand it).</div><div class="gmail_quote"><br></div><div class="gmail_quote">
On Sun, Jul 26, 2009 at 6:26 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;">
> If people sending emails containing proposals, and having the editor</blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
> directly respond to all of those emails, frequently by changing the<br>
> spec, does not give you the impression you can impact the specification,<br>
> I'm not sure what would.<br>
<br>
Having a distributed source control system in place that would provide<br>
the tools available to generate, modify and submit specification text<br>
for HTML5. Having the ability to generate alternate HTML5 specification<br>
text.</blockquote><div><br></div><div>Are you are saying that writing an email is too taxing, but checking text in and out of source control is not?</div><div><br></div><div>If so, given my experience with writing email and using version control systems, I think this is untrue.</div>
<div><br></div><div>If not, see the final paragraph below.</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">The tools and mechanism doesn't exist to do this easily in the HTML5<br>
community. The process is unclear and undocumented. I'm working to<br>
resolve these issues.</blockquote><div><br></div><div>Ian has just added a way to submit comments immediately, anonymously, on the spec itself. Does this ameliorate your concern? I can hardly imagine a lower barrier to entry.</div>
<div><br></div><div>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.</div>
<div><br></div><div>PK</div></div>