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

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

From: fantasai <fantasai.lists@inkedblade.net>
Date: Fri, 20 Sep 2013 19:27:34 -0700
Message-ID: <523D0416.2090003@inkedblade.net>
To: www-style@w3.org
On 09/20/2013 10:23 AM, Tab Atkins Jr. wrote:
> 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.

I think what John means is that in order to work with CSSWG specs,
one only needs to learn one VCS and pull one repo. Yes, everything
for Bikeshed is in one repo, but Bikeshed is not in the CSSWG repo.

~fantasai
Received on Saturday, 21 September 2013 02:28:04 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:34 UTC