W3C home > Mailing lists > Public > www-style@w3.org > September 2013

Re: [spec tools] spec tools should be checked into the csswg repo

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Fri, 20 Sep 2013 10:23:14 -0700
Message-ID: <CAAWBYDAWUJ+p06EOE3f8ERs_1vsZ5pJcfpaGA1Sfogsqp+ztVA@mail.gmail.com>
To: John Daggett <jdaggett@mozilla.com>
Cc: W3C Style <www-style@w3.org>
On Thu, Sep 19, 2013 at 7:25 PM, John Daggett <jdaggett@mozilla.com> wrote:
> During the F2F, the use of Tab's preprocessor, bikeshed, was discussed:
> http://lists.w3.org/Archives/Public/www-style/2013Sep/0469.html
>
> I think if we're going to switch to using this that we should use a copy
> that is checked into the csswg hg repo, along with a copy of the biblio.ref
> references file.  That makes life simpler for pulling all needed resources
> at the same time and makes it easier for editors in the group to make
> changes to the source of the preprocessor, rather than relying on tab
> for this.

The biblio.ref file does need to be public, but just so Bikeshed can
update its internal files with its standard update mechanism, rather
than waiting for the copy in the repo to be manually updated.  (Note
that all of its spec and anchor data lives over in Shepherd, but it
maintains local versions of that data in itself.)

Editting the preprocessor is trivial - just submit a PR.  As Dirk and
Simon can tell you, I'm very quick to adopt them.

Pulling all necessary resources is a single operation regardless of
where we put things - Bikeshed keeps everything it needs to run
locally.

~TJ
Received on Friday, 20 September 2013 17:24:01 UTC

This archive was generated by hypermail 2.3.1 : Friday, 20 September 2013 17:24:01 UTC