Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update themes with base16-project/base16-schemes and builder-go #6

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

JamyGolden
Copy link

@JamyGolden JamyGolden commented Jul 11, 2022

Hi @HaoZeke,

To understand the PR requires a tiny bit of backstory. There was a github "issue" on chriskempson/base16 that was started in 2016, discussing the concept of a "base16 organization" instead of having everything under 1 person's control. The issue had a lot of activity, but Chris became inactive on github and wasn't contactable. Fast forward to 2022, the base16 core project had become stale. This year the base16 community involved in the previously mentioned github "issue" moved forward with creating the base16 organization and have been contacting base16-* template repos and having them join tinted-theming umbrella. Since then there has been progression where Chris returned and his actions have indicated that he is not interested in being part of the community.

To generate the themes in this PR I used base16-project/base16-builder-go and base16-project/base16-schemes.


base16-project is still looking for collaborators. We're interested in having theme maintainers transfer their projects to the organization, join the organization themselves and and to be the primary maintainer of the project. Among other benefits, having projects in the organiuzation allows for maintainers to easily move around between repos and if someone disappears, the repo doesn't go stale. Centralising things also allows for organic discussion around the project as a whole, which you can see has been quite active. Also, we've got a #base16 irc channel on Libera.Chat.

Having said all that, there will be base16-* template repos that don't join the umbrella and we also want to work with them. Having a closer relationship and having the template owners involved in the decisions of the core work would be great.

Would you be interested in joining base16-project umbrella?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant