Long term home of eslint-plugin-n

[voxpelli]

As discussed in a previous thread with eg. me, you @aladdin-add, @MichaelDeBoey: standard/eslint-config-standard#192 (comment)

Having an eslint-community organization (or similar) that's home to this module + eslint-plugin-promise and other important modules would be good .

@aladdin-add You mentioned that @nzakas were setting up an eslint-community organization, do you know anything more?

[MichaelDeBoey]

Would be lovely if we could move eslint-plugin-node, eslint-plugin-es, eslint-utils, @mysticatea/eslint-plugin & eslint-plugin-promise to this new org too

[nzakas]

There’s nothing more to report right now. We’ve got some other higher priority tasks I need to work on first. Stay tuned to the blog and Twitter for updates.

[MichaelDeBoey]

@nzakas If there's some work we can take out of your hands, I'm happy to help out!

[voxpelli]

eslint-community is mentioned in eslint/eslint#15383

[MichaelDeBoey]

It seems like the team agreed to not make it a priority: eslint/eslint#15383 (comment) 🤔

[aladdin-add]

However, I did not see it was discussed in the meeting. :-( 

Anyway, the only thing is to write a RFC to talk about how it runs: https://github.com/eslint/rfcs

[thernstig]

Definitely go for eslint-community once its been setup by ESLint maintainers, it will give it a well-known home :)

Then it can live in npm under @eslint/eslint-plugin-node possibly.

[nazrhyn]

Keeping the name via a namespace like that would be awesome, as well as having these under an org. Looking forward to the changes!

[voxpelli]

Created a discussion around this in the ESLint repo: eslint/eslint#15929

[voxpelli]

And now an RFC regarding this is up: eslint/rfcs#91

[MichaelDeBoey]

Let's hope, we can transfer the original repo asap to the new @eslint-community org 🙏

mysticatea#341

[thernstig]

Would it be time to consider that https://github.com/mysticatea/eslint-plugin-node (see mysticatea#341) will not be transfered? And instead transfer this repo?

[MichaelDeBoey]

@thernstig We're working on transferring @mysticatea's repos one at a time

[aladdin-add]

a few months passed, but we are still not able to transfer the original repo( we have not gotten response from @mysticatea 😢). I think it's time to make the new @eslint-community/eslint-plugin-node.

I have the following plans:

1. checkout a new branch from the original main.
2. pick all the features/bugfixes from eslint-plugin-n.
3. transfer the opened issues/PRs to the new repo.
4. review & merge the "ready" PRs.
5. release @eslint-community/eslint-plugin-node v1.0.
6. make the eslint-plugin-n as an alias of the new package. (DX matters! 😄 )

questions:

• does anyone have the admin access to https://github.com/mysticatea/eslint-plugin-node, please add me. cc @ota-meshi
• how can I get the publish access to @eslint-community/eslint-plugin-node? cc @MichaelDeBoey
• should the new package be another repo? I'd slightly prefer renaming the repo back to eslint-plugin-node, but open to create a new one to avoid possible confusion.

[nazrhyn]

I think the horizontal name changes happen regularly enough (e.g. apollo-server -> @apollo/server) that eslint-plugin-node -> @eslint-community/eslint-plugin-node makes sense. Even makes it seem "official", which is probably good.

[voxpelli]

@aladdin-add I think we should keep working in this repo unless we can move the original repo here

I am pro on renaming this repo to eslint-plugin-node

I think this issue should be considered resolved when #55 is resolved

[scagood]

As #55 is closed shall we close this?

[voxpelli]

@scagood Yeah, I think a rename to @eslint-community/eslint-plugin-node or such is a bit late to do now anyway and out of scope of this issue