- From: Alberto Lepe <dev@alepe.com>
- Date: Wed, 14 Apr 2010 09:49:54 +0900
- To: www-style@w3.org
On Tue, Apr 13, 2010 at 3:48 AM, Eduard Pascual <herenvardo@gmail.com> wrote: > On Mon, Apr 12, 2010 at 7:34 PM, David Singer <singer@apple.com> wrote: >> I'd suggest that we link to places describing the W3C rec track, rather than (re-)describing it and possibly varying from it. >> >> 7.1 of http://www.w3.org/2003/06/Process-20030618/tr.html seems to fit the bill... > > Indeed, I took the information mostly from there; but I had to take > also a bit from 7.4.2. Actually, I would have just put a link (and > maybe a quote) if the information had been all on the same place; but > the Last Call is an announcement within the WD stage, rather than a > stage of its own: should the average contributor bother about this > kind of details? Or, should they be bothered with what a "Technical > Report" is? Also, I took the chance to use a less formal language for > the FAQ. > > IMO the informal summary *plus* the link would be ideal; but that's > only my opinion. > > Regards, > Eduard Pascual > > Eduard, I think that your FAQ is very very good! I would add one thing at the last part: (Which is the right module to propose feature X?) One of the best ways to figure it out (In my experience), is to search in the mailing list for similar topics. Also, in that way, it prevents people from posting repeated proposals that are still active or has been rejected for technical or structural reasons (or any other reason). In general, I think it would be good to comment more about the mailing lists, how to search in them and how to post in them (briefly). Like for example, prepend to the title [css-module]. If you think this information would be repetitive to the one in the mailing list page, then a link would be enough. Lepe
Received on Wednesday, 14 April 2010 00:50:28 UTC