-
Notifications
You must be signed in to change notification settings - Fork 453
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
Future maintenance #40
Comments
I'd say for now, just add @Glavin001 and let him take the lead, he's the one adding features now :) |
I'd be honoured to take lead and develop out the future goals of atom-beautify :). Also, hope you had an amazing honeymoon! |
Thank you very much. The wedding was really amazing! The honeymoon... well, we could have better weather ;) Great. I'll transfer the ownership now! |
Oops. It seems that you need to remove your |
Done :). |
Done, too ;) |
Excellent. Thank you! |
Hi @Glavin001 and @karolyi,
thank you both for the great work on this project in the last weeks. Amazing! As you've seen I didn't contributed a lot recently (say: nothing).
Reasons for this: little free time and little motivation, because Atom isn't my main editor. I've created this package even before I had access to Atom, because I wanted to test the APIs for plugins :) So I couldn't know if I like Atom from a user perspective or not beforehand. It's cool, but I still need more features and stability for my daily IDE.
To make a long story short: How should this project be maintained in the future? Does one of you would like to take the leadership? Should this project be maintained by an "organization"?
Greets and sorry for letting you down,
Pipo :)
The text was updated successfully, but these errors were encountered: