- From: Ian Hickson <ian@hixie.ch>
- Date: Tue, 6 Jul 2004 13:46:30 +0000 (UTC)
On Tue, 6 Jul 2004, Jim Ley wrote: > > On Tue, 6 Jul 2004 12:05:55 +0000 (UTC), Ian Hickson <ian at hixie.ch> wrote: >> The working group members should also >> respond to queries from the public on this mailing list.", it doesn't say >> that if someone contacts an editor directly the editor can't also take >> that feedback into account. > > Could you clarify this in the charter please, as I took "Specifications > will be developed in public", to be just that, that the specifications > will be developed in public. They are developed in public. Here is the absolute latest copy of the development: http://whatwg.org/specs/web-forms/current-work/ > Not they'll be developed in public, except for comments that are > provided in private. (Clarifying that it's only the result in the > document itself that is public) If a painter stands in the street and paints, he is painting in public, yes? If someone shouts a suggestion to him and he takes it into account, he is still painting in public, no? If someone walks up to him and whispers something that only the painter can hear, and he then takes it into account, that is still painting in public, no? If I make a change to the spec mentioned above, that is in public, right? If I make a change to the spec in response to the comments here, that's still in public, right? So why do you think that making a change in response to a comment you didn't hear is no longer in public? In particular, why is a change that I come up with considered "public" but a change that someone suggests over lunch no longer public? WHATWG specs are developed in public. Feedback is accepted in public. That public feedback is responded to in public. That private feedback is also accepted doesn't change any of this. -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Received on Tuesday, 6 July 2004 06:46:30 UTC