W3C home > Mailing lists > Public > www-style@w3.org > November 2005

RE: How Do I Propose a CSS3 Spec Change?

From: Mark Moore <mark.moore@notlimited.com>
Date: Wed, 9 Nov 2005 11:10:37 -0800
To: <www-style@w3.org>
Cc: "'Felix Miata'" <mrmazda@ij.net>, "'Ian Hickson'" <ian@hixie.ch>
Message-ID: <006b01c5e561$4542eed0$01a8a8c0@FATBOY>

What Ian is trying to say, Felix, is that there really is no effective way
for lay people to make changes to the spec.[1]  The committee has its own
idea of how the spec should look, and its own time table.  Thank you very
much.

You're always welcome to follow the newsgroup, but if you have, you'll see
that the "informal process" is equally ineffective.[2]

Sorry Virginia, there is no way to get your spec change adopted.

-MM

[1] If the $6K individual membership fee (for the US) doesn't thwart you,
the requirement to travel internationally to attend meeting probably will.

[2] I've only been following it for the last two years.  There may have been
times in the past that it was more accommodating of its subscribers'
suggestions.




> -----Original Message-----
> From: www-style-request@w3.org [mailto:www-style-request@w3.org] On Behalf
> Of Ian Hickson
> Sent: Wednesday, November 09, 2005 10:32 AM
> To: Felix Miata
> Cc: www-style@w3.org
> Subject: Re: How Do I Propose a CSS3 Spec Change?
> 
> 
> On Wed, 9 Nov 2005, Felix Miata wrote:
> >
> > Is there a formal procedure to do this?
> 
> Yes: Become a W3C member, become a member of the CSS working group, send a
> proposal to the mailing list asking for it to be added to the next
> meeting's agenda, come to the meeting, defend the idea, write a spec for
> it, send the spec to the mailing list asking for it to be added to the
> next meeting's agenda, come to the meeting, and defend the spec. (If you
> want it to actually get further than a proposal, you'll also need to
> address the issues raised by the other members of the group, get a minuted
> decision to publish, go through the publication process, then repeat the
> last few steps (also addressing public feedback) to get the spec to CR,
> then write a test suite, then get implementation reports created showing
> interoperability, then get the spec to go to PR, and wait for the W3C
> membership to vote on the spec for it to become a REC).
> 
> To become a W3C member, the first step of that formal process, see:
>    http://www.w3.org/Consortium/join
>    http://www.w3.org/Consortium/fees
> 
> 
> > Do I simply send an email to this list?
> 
> That is the informal procedure.
> 
> --
> Ian Hickson               U+1047E                )\._.,--....,'``.    fL
> http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
> Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Wednesday, 9 November 2005 19:16:23 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 April 2009 13:54:41 GMT