Rename package please

[hd-deman]

@kanongil, Please, could you rename your package to something like linter-contrib-eslint. The same practice for naming SublimeLinter packages that are not included in the official organization https://sublime.wbond.net/search/SublimeLinter-contrib

steelbrain/linter#152

[kanongil]

Sorry, but I am not inclined to spend energy moving the repo as a favor to you when you have shown no appreciation or acknowledgement of my work.

[hd-deman]

I did it because you did not want to move to the AtomLinter organization. I do not know what's stopping you to do this. You would have stayed this repository administrator and users would get a good support service from you and core team. But your ego will not let you do that. I have nothing against. I'm asking you move the repository to us or rename it. It interferes with our work. I really respect your work. But it seems that you are not really ours.

[hd-deman]

We spent countless hours. And you do not want to spend a couple of minutes that would make our work harmoniously. So claims about not respecting looks to me ridiculous.

[kanongil]

I seriously don't know what all the fuss is about. You offered to include it in your org and I declined because I did not see any benefit from moving it (and you didn't offer any). Now you are acting all hostile and making demands of me.

[hd-deman]

no demands. just a polite request. )

[hd-deman]

can you explain the good reasons not to join us? or not to follow the doctrine and rename package. ::)

[park9140]

@kanongil, Sorry for any confusion regarding this request being anything other than a request. If you check out the other linters it has been common practice to migrate linters into the primary AtomLinter organization.

There are some definite benefits to doing this.

Primarily, this allows us to more easily keep track of linters that need to be fixed after major updates to the core linter. Additionally, by pulling you into the organization it allows us to keep linter creators up to date with changes and plans people have to advance the project. Lastly it has been a good tool when people have issues with the linters where users can rely on a larger stable of developers to help them with their issues on any given linter.

We are currently in an extremely fortunate situation where two separate developers (you, and @jfaissole) have both committed separately to create and support an eslint plugin.

I think you will find that @jfaissolle would love to have some additional support in making decisions, and fixing issues on an official eslint plugin. If you would take the time, I think some of your ideas on how you built your plugin could help in making a better plugin for everyone involved.

Hopefully, with a little understanding and work we can eliminate the current confusion by having two separate implementations.

[kanongil]

@park9140 Thanks for elaborating.

I'm a bit busy right now but I'm willing to work with you on this issue. Any ideas for the best course of action?

[hd-deman]

the best course of action:

1 run apm unpublish linter-eslint command to unpublish your package
2 contribute to https://github.com/AtomLinter/linter-eslint (you already have admin permissions)

[kanongil]

@hd-deman package has been unpublished.

[hd-deman]

@kanongil thx! 🎊

[dmnd]

✨

thanks for working it out guys 😄