Should we move NPM package to @jupyterlab scope?

[krassowski]

I took a look at releasing a new version but it seems that the package is not scope to @jupyterlab. Instead it was published to npm as jupyterlab_pygments:

jupyterlab_pygments/package.json

Line 2 in a26fdd6

"name": "jupyterlab_pygments",

https://www.npmjs.com/package/jupyterlab_pygments (owned by @martinRenou)

Should we rename it to @jupyterlab/pygments and move npm under jupyterlab org to facilitate releases?

[welcome]

Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗

If you haven't done so already, check out Jupyter's Code of Conduct. Also, please try to follow the issue template as it helps other other community members to contribute more effectively.

You can meet the other Jovyans by joining our Discourse forum. There is also an intro thread there where you can stop by and say Hi! 👋

Welcome to the Jupyter community! 🎉

[martinRenou]

Happy to move it under the jupyterlab org. Not sure how to proceed though.

[jtpio]

It makes sense to move it under the jupyterlab organization since it's already under the JupyterLab org on GitHub.

That way we can reuse the same bot and credentials for making releases.

[jtpio]

For PyPI it seems to be already under the Jupyter organization, which is good:

Someone with access to that package should check whether the trusted publisher is set up.