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

Re: [css-ui] converting to bikeshed

From: Tantek Çelik <tantek@cs.stanford.edu>
Date: Thu, 13 Nov 2014 10:50:15 -0800
Message-ID: <CAEV2_WYpMw3dfemjxN0eGzcO1T4VTd+G6EGBaTcc4oqFJd5V0Q@mail.gmail.com>
To: Florian Rivoal <florian@rivoal.net>
Cc: Tantek Çelik <tantek@cs.stanford.edu>, www-style list <www-style@w3.org>
On Wed, Nov 12, 2014 at 1:30 PM, Florian Rivoal <florian@rivoal.net> wrote:
> Hi Tantek,
> Before I push the commit that converts the source of css3-ui to bikeshed, there's 3 points I'd like to clarify with you:
> 1) Your "Editor:" line uses a pattern not supported by Bikeshed, due to mentioning both Mozilla and (formerly) Microsoft as your affiliations. Do you prefer that I:
>  a - simplify it to only mention the current one (Mozilla), and let bikeshed generate the markup

I'm fine with current one (Mozilla) only.

> 2) The conformance section of the spec uses what is no longer standard boilerplate. I would like to let bikeshed replace it with the current text. Any issue with that?

No issue. Makes sense.

> 3) Similarly, the status section uses text that is not standard boilerplate. I'd like, for the ED, to let bikeshed just generate the standard text.

Makes sense.

> Next time you prepare to publish to TR will be the right time to write a custom statement explaining the specific status, depending on exactly what we end up publishing as (I suspect it will be a new process WD, but that's a separate discussion)

Indeed, and as more of our documents use the new process, we'll likely
want bikeshed to automatically handle that for us.


Received on Thursday, 13 November 2014 18:51:21 UTC

This archive was generated by hypermail 2.4.0 : Monday, 23 January 2023 02:14:45 UTC