Still maintained? - Githubissues

altercation / solarized

precision color scheme for multiple applications (terminal, vim, etc.) with both dark/light modes

http://ethanschoonover.com/solarized

MIT License

15.78k stars 3.52k forks source link

Still maintained? #200

Closed honza closed 12 years ago

honza commented 12 years ago

There are 50 open pull requests and the last commit was over a year ago. This is a great project and I would hate to see it die a slow death.

danielbayerlein commented 12 years ago

altercation commented 12 years ago

Rest assured, not dead. Making decisions about how to handle some of the git issues (not just pull requests, larger structural issues that I don't want to make worse by just accepting all the requests in one go).

On May 24, 2012, at 06:06, Honza Pokorny wrote:

There are 50 open pull requests and the last commit was over a year ago. This is a great project and I would hate to see it die a slow death.

Reply to this email directly or view it on GitHub: https://github.com/altercation/solarized/issues/200

honza commented 12 years ago

Can you provide a rough timeline? Thanks

altercation commented 12 years ago

I don't want to provide any schedule yet. What I can say is that I'm very committed to taking this forward. I am working on version 2 and need to decide if I try to wrap that up into this or keep it on a separate project track. I am also trying to figure out the communication side of things better.

Also, I'm reading Fogel and taking notes on best practice. Trying to do this the right way.

On May 24, 2012, at 10:28, Honza Pokorny wrote:

Can you provide a rough timeline? Thanks

Reply to this email directly or view it on GitHub: https://github.com/altercation/solarized/issues/200#issuecomment-5912448

Quantisan commented 12 years ago

rather than doing this for N variants, it'd be easier to make one master colour palette, then all the variants could be generated from scripts

altercation commented 12 years ago

I have scripts that generate Solarized, but they are duct taped together and involve some ugly massaging of data out of proprietary palette formats. Ideally I'd like to move the design process into 100% open source apps, but L_a_b support in things like GIMP is pretty terrible.

On Mon, Aug 6, 2012 at 1:44 AM, Paul Lam reply@reply.github.com wrote:

rather than doing this for N variants, it'd be easier to make one master colour palette, then all the variants could be generated from scripts

Reply to this email directly or view it on GitHub: https://github.com/altercation/solarized/issues/200#issuecomment-7519326

Quantisan commented 12 years ago

Something like this...

Solarized
1. colours.json -- master colours palette in JSON or some generic data structure (or even some algorithmic colours generator)
GIMP repo with Solarized as submodule
1. script to generate GIMP profile based on colours.json
2. generated GIMP profile
VIM repo with Solarized as submodule
1. script to generate VIM profile from colours.json
2. generated VIM profile
etc.

The idea is to represent colours as data and each variant will be mutually independent transformation hosted in their own git repo with the master colours repo as a submodule. Then you can tweak the colours at will and you wouldn't be getting like a 100 pull requests in one repo for all kinds of unrelated stuff. Each module can have a different crew of committers to accept pull requests too if you want to delegate some work (e.g. anything hard to work with like GIMP)