-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
add Erl package #3576
add Erl package #3576
Conversation
What are the differences to the fork origin, SublimErl, and why didn't you submit a pull request? cc @ostinelli |
My fork works with ST3, author doesn't respond to other PR's and stopped working on this plugin. |
@ostinelli, please consider transfering ownership of your package if you no longer plan to maintain it. The most optimal procedure would be for @artemeff to remove your package from the list and add the old name to a |
Let me get this straight. There's an ongoing feature request to port the package to ST3, where I've responded that I'm not working on this feature. This does not mean that "I've stopped working on this plugin", nor that I "don't respond" (clearly, since I did). So @artemeff you go ahead and fork the work that has been done until now by other contributors, and submit a pull request to @FichteFoll to point to your fork instead of the original, and all of this without even contacting me? |
Ok |
It seems to me that perhaps a better course of action @artemeff would be to fork the current state of the package and send a PR with fixes to make it work both on ST2 and ST3. Then you could collaborate with @ostinelli. |
As I (maybe poorly) stated above, we do not remove packages without contacting the original author of the package, or at least trying to. |
Indeed @FichteFoll, I was obviously not referring to you. Thank you for following this up. |
No description provided.