Base16 Project lives on [Discussion]

[belak]

This is the companion issue to #51. We're leaving the discussion here to avoid any heated discussion on that issue, which aims to describe what happened during the controversy, explain where we were coming from, and what we plan on doing next.

What we have done so far to eliminate any confusion that "we are base16":

• rename our main planning repo from base16 to home
• rewrite the README to make it clear we're an initiative that supports multiple style systems including Base16 (with links back to Chris's own repo)
• change the visible org name to "TBD (formerly Base16 Project)
• fully rename the organization (still in discussion to find the right name)

[MultisampledNight]

What specific changes can I expect between this base16 and chriskempson' original (?) https://github.com/chriskempson/base16? I only recently found out about base16 on their repository, am in the process of converting my colorschemes from a custom solution to this one and am now a bit confused about how this project is or will be different.

[MultisampledNight]

Also, can I use older builders like https://github.com/InspectorMustache/base16-builder-python through just changing the sources.yaml? I'm not too keen on installing Go or Node only for building colorschemes.

[joshgoebel]

What specific changes can I expect between this base16 and chriskempson' original (?) https://github.com/chriskempson/base16?

Have a read thru some of the issues for ideas on what we're thinking... but the overall idea is "broader"... we'd like to host and support multiple style specs... Base16, Base24, Ansi16... new specifications that will add new features and flexibility for scheme authors to better support applications.

Things like: #45, #35, #10, #36, #11

I'm not too keen on installing Go or Node only for building colorschemes.

If you want to be a template author those are the two supported builders at the moment. Node.js is the first universal builder (multi-spec) but I'd imagine Go is soon to follow. But it's also pretty easy to just setup a GitHub action to do all the building for you. (though that makes it hard to test your work locally).

can I use older builders like

If all you care about is base16, I think so... but that's not going to support the newer style specs and features we have plans for. Though anyone is of course free to add support to the Python builder to support our extended builder spec and additional style specs.

process of converting my colorschemes from a custom solution

Are your color schemes for use in editors? You may care a lot about #10 and #11... base16 can be pretty restrictive in how it binds colors to each other - depending on which direction you want to go with your schemes.

[JamyGolden]

To add to what @joshgoebel said above regarding github actions: all of our template repos automatically build once a week using github actions. You can have a look at the setup here as an example: https://github.com/base16-project/base16-emacs/blob/main/.github/workflows/update.yml

[MultisampledNight]

Okay, I see. Thank you both. In that case I'll just stick around looking at what this is going to become, because this could explode both in a great and horrible way.

[joshgoebel]

because this could explode both in a great and horrible way.

You're a part of the community - you can help us make sure it explodes in a great way. :-)

[Misterio77]

Whoa. A lot seems to have happened these last few days, It's sad we can't go through with the name. I hope we can build a nice community driven architecture, even if we have to rename :)

[belak]

I'm closing this for now, but it's still linked to from the other issue, so feel free to comment if you have comments/concerns you want to bring up.