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

Does the CSS WG have an GitHub account? Would it be ok if this account would fork bikeshed from Tab and it gets merged once in a while? Would that be sufficient enough? Maybe the concern is just that Tab could (theoretically) restrict access to the repo, or the account is lost/not available anymore for what ever reason.


On Sep 21, 2013, at 8:48 AM, Tab Atkins Jr. <> wrote:

> On Fri, Sep 20, 2013 at 7:27 PM, fantasai <> wrote:
>> 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.
> And if we put an appropriate curl script in the dvcs repo, they can do
> that.  Even if we stored Bikeshed in the dvcs repo, you can't use it
> straight from there - you have to install some dependencies as well.
> Plus, Bikeshed *is* intended to be useful for more than just CSS.
> Even if you *could* run it without installing anything else, I'd be
> loathe to put it directly in the CSSWG repo for that reason.
> ~TJ

Received on Saturday, 21 September 2013 08:32:26 UTC