Moving this package to the new Stencil organisation

[christian-bromann]

Hey @raphaelpor 👋

first off, thank you so much for maintaining this package for the Stencil community 🙏

I am Christian and one of the maintainers of the Stencil project from OutSystems. We are currently in the process of moving all Stencil assets into a new organisation. I've been looking into the community org and think that this package could be part of that new organisation as it seems essential for all Stencil developers.

I wonder if you would be ok, migrating it over to the new organisation. Obviously you would get an invite to it so you remain in control of the code. For us it is more important that we can support you maintaining this package and make releases without depending on you.

Let me know your thoughts!

Cheers
Christian

[raphaelpor]

Hey @christian-bromann,

Of course! Let me know how I can support you in this migration.

Also, I will be more active here in the coming weeks, so we can make sure the library gets fair attention as well.

I would love to hear more about the new plans and what it means for the community as well.

Have a nice day.

[christian-bromann]

Awesome! Glad to hear you support the idea.

Let me know how I can support you in this migration.

I've invited you to the new org. Mind transferring the project over there? I will then go ahead and set up a release pipeline. The overall idea is to allow unblock the maintainers from making contributions and releases. With that we would release this package under @stencil/eslint-plugin rather than @stencil-community/eslint-plugin, wdyt?

I would love to hear more about the new plans and what it means for the community as well.

I've sent you an email (looked up your commit email) and shared my availability for next week. Would love to get you involved!

Thanks again!

[raphaelpor]

Great! I will have a look at this during the weekend since it's a bit late over here.

But thanks for all the info. :)

[raphaelpor]

It seems that I don't have enough rights for the transfer:

@rwaskiewicz Would you have access to that?

[rwaskiewicz]

Done - GH should do redirects automatically, but we'll still need to replace @stencil-community with @stenciljs in the README, package.json, etc.

[raphaelpor]

Thanks @rwaskiewicz. I will make sure to update the files.

@christian-bromann do we need to change the npm organization as well?

[christian-bromann]

Thanks @rwaskiewicz 🙏

I would suggest the following next steps:

1. update metadata information about the project to point to @stencil/eslint-plugin (Eslint suggests plugins to be named that way if scoped)
2. add a release pipeline, I'ld suggest something simple like this one, note: we already have an NPM_TOKEN token available in the org to push packages to NPM
3. deprecate community package and point user to the new package name

Anything I forgot?

[christian-bromann]

2. add a release pipeline,

Raised #130

[rwaskiewicz]

update metadata information about the project to point to @stencil/eslint-plugin (Eslint suggests plugins to be named that way if scoped)

While not complete (someone should do a more thorough check) there’s prior art

• 5603ce9
• chore(repo): move repo to community #82