You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 1, 2024. It is now read-only.
Lately, as you well know, I have not had time to update the repository with pull requests, improvement requests, etc.
I would like to propose something: any of the people who maintain Alpenglow, you want to be part of the Afterglow repository as contributors? This way, you could directly resolve pull requests, upload improvements, etc.
Obviously, the name of all the collaborators will appear prominently in the Readme.md.
I'm sorry I do not have time to keep this theme. I initially built it when I changed my IDE to Sublime Text and there was no theme I liked. So I decided to share it, and I never thought so many people would like it. It's a shame to leave him inactive.
I do not know if there are other ways that can interest you more: create a new organization from scratch and transfer the repository? I am open to any solution that seems valid to you.
Thank you very much.
The text was updated successfully, but these errors were encountered:
I am glad to hear something after all this time 😄, thank you for the great theme.
I fully understand your time limitations on this theme, I think on the Alpenglow side, we are also struggling to keep up with doing justice to the nice theme.
On the one hand, I think you suggestion of resuming work under the Afterglow flag has the huge benefit of a larger user base, derived works having some presence, ...
However, I also think that what we having going on right now with an "organization" and repositories for different IDEs is a good thing in the long run to provide themes with some uniformity.
What is certain to me, is that it is better to merge our efforts in one way or another, given the time constraints of everybody involved and for the sake of our users: nobody fares well with a derived product that tries to stay close to the original (which is how Alpenglow got to be: a few of us trying to fix some minor inconveniences in an otherwise very nice theme).
Let's see what some of the others think about all of this.
We could adopt the Afterglow repository under the Alpenglow organization and bring @YabataDesign on as a contributor?
This way everyone is able to contribute towards a common ecosystem and eventually merge our combined efforts, either back into Afterglow proper, or Just have two different flavors as it were?
This almost feels like the Node and IO.js split when they discussed merging :P
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi. I'm @YabataDesign, responsible for Afterglow Theme for Sublime Text.
Lately, as you well know, I have not had time to update the repository with pull requests, improvement requests, etc.
I would like to propose something: any of the people who maintain Alpenglow, you want to be part of the Afterglow repository as contributors? This way, you could directly resolve pull requests, upload improvements, etc.
Right now, Afterglow has almost 2000 starts in GitHub, and 101K downloads in Package Control: https://packagecontrol.io/packages/Theme%20-%20Afterglow.
Obviously, the name of all the collaborators will appear prominently in the Readme.md.
I'm sorry I do not have time to keep this theme. I initially built it when I changed my IDE to Sublime Text and there was no theme I liked. So I decided to share it, and I never thought so many people would like it. It's a shame to leave him inactive.
I do not know if there are other ways that can interest you more: create a new organization from scratch and transfer the repository? I am open to any solution that seems valid to you.
Thank you very much.
The text was updated successfully, but these errors were encountered: