Update themes with base16-project/base16-schemes and builder-go #6
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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?