W3C home > Mailing lists > Public > public-html@w3.org > July 2009

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

From: Peter Kasting <pkasting@google.com>
Date: Sun, 26 Jul 2009 19:10:27 -0700
Message-ID: <d62cf1d10907261910u70b83753m848f2aa4bde4f51d@mail.gmail.com>
To: Manu Sporny <msporny@digitalbazaar.com>
Cc: HTMLWG WG <public-html@w3.org>, WHATWG <whatwg@lists.whatwg.org>
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).

On Sun, Jul 26, 2009 at 6:26 PM, Manu Sporny <msporny@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, does not give you the impression you can impact the specification,
> > I'm not sure what would.
> Having a distributed source control system in place that would provide
> the tools available to generate, modify and submit specification text
> for HTML5. Having the ability to generate alternate HTML5 specification
> text.

Are you are saying that writing an email is too taxing, but checking text in
and out of source control is not?

If so, given my experience with writing email and using version control
systems, I think this is untrue.

If not, see the final paragraph below.

The tools and mechanism doesn't exist to do this easily in the HTML5
> community. The process is unclear and undocumented. I'm working to
> resolve these issues.

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.

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

Received on Monday, 27 July 2009 02:11:06 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 9 October 2021 18:44:51 UTC