Closed joshgoebel closed 2 years ago
I've been thinking about this a bit - what would you think if we also put schemes in each of the separate repos (perhaps in a directory called schemes)? Then each repo could be a self-contained bundle of info about the scheme system and all the "official" schemes supported by that system.
That had crossed my mind at one point but I hadn't given it much thought. Seems reasonable at first glance.
I think we're in agreement on this - we'll have a separate repo for each scheme system. If a system needs color schemes, they should be included under a folder (tentatively named "schemes")
To me it seems we then need to:
base16
that is a fork of Chris's base16 (before he destroyed the repo) - we'd make it clear this is a link aggregation of base16 resources (if we want to maintain that) and clearly link to Chris's official copy of the spec (in addition to hosting an "archival" copy for convenience - and to show a sample, etc).base17
that is a more fork of home
right before it went multi-format. (ie, the continuation of Base16) - and can include all the new builder spec stuff (until we figure out if that moves)base17
to something else... to indicate that it's perhaps further down the road and perhaps a new beast (if we go that direction)... Thoughts?
I'm beginning to think that each should perhaps have their own repo:
https://github.com/new-org-name/base24
https://github.com/new-org-name/base17
https://github.com/new-org-name/ansi16
That gives each spec room to spread out:
This is based on our new direction of supporting multiple style specs and empowering creators, etc... and it also easily allows specs to live wherever - in
contrib
, or even outside the organization. It seems obvious (after recent experience) that some spec owners would desire this - even if it's sub-optimal in some ways.Thoughts?