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

The move to base16-project GitHub organization #30

Closed
JamyGolden opened this issue Jun 22, 2022 · 3 comments
Closed

The move to base16-project GitHub organization #30

JamyGolden opened this issue Jun 22, 2022 · 3 comments

Comments

@JamyGolden
Copy link

JamyGolden commented Jun 22, 2022

Hi @golf1052, there is a group of us working on reviving the base16 project and I'm wondering if you'd be willing to join?

The discussion about a base16 Github organization initially started in 2016. Now, with the disappearance of Chris Kempson, the importance of the base16 organization is more vital than ever to keep the project structured and thriving. Currently there is a "deprecation" notice on the old chriskempson/base16 repo.

Seeing as you maintain this repo (and other base16 repos), we're looking for more colaborators and I was wondering if you are you interested in joining github.com/base16-project and helping us maintain some of the projects?

Right now, logistical communication around this is happening at tinted-theming/home#1. Some of us are also on #base16 on Libera Chat [IRC] (for more general discussions and hangouts)

Are you interested in maintaining any base16-project repositories and being part of the organization?

@golf1052
Copy link
Owner

golf1052 commented Aug 1, 2022

It looks like the original base16 project doesn't have a deprecation notice anymore but I think it's good the base16-project org exists now. When I started updating this repo in the last few days read through some of your repos and issues. I'd be glad to join the org as a collaborator but my focus has always been on just (poorly as you can see by the large gap since the last update) maintaining a decently high quality VSCode extension that supports all the known base16 themes (and the underlying builder that is required). I wouldn't want to be responsible for updating other builders or schemes besides the ones I currently maintain.

I'm also somewhat skeptical of base24 as I'd assume the plan would be to update all known base16 schemes to support base24 which seems like a somewhat large undertaking if you want scheme authors to update their schemes.

@JamyGolden
Copy link
Author

Yes there was a lot that changed soon after I sent you the message which, I'm guessing you've come across, is summarised here: tinted-theming/home#51 I totally understand joining and only maintaining this project. The goal isn't to have maintainers update all their templates to support base24, the builders will be backwards compatible and it will allow template maintainers to fix existing bugs (tinted-theming/home#10). It's not a feature, not a requirement though.

I'll add you to the org and you should be able to transfer the project under the repo settings page.

@golf1052
Copy link
Owner

golf1052 commented Aug 3, 2022

I've transferred in the base16-vscode project. I would need to figure out which contributors I'd need to add to the npm project for base16-builder-typescript. I'd like to keep this repo under my account for the time being but the latter items can be discussed in the org.

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

No branches or pull requests

2 participants