Update npm packages to the `@jupyter-notebook` scope

[jtpio]

Problem

At the moment we are publishing the npm packages under the @retrolab scope.

Now that the Notebook v7 JEP has been merged and in preparation for the first 7.0.0a0 pre-release, we should consider renaming the npm packages to use the @jupyter-notebook scope.

Proposed Solution

This should only consist in a search / replace, and make sure the publishConfig is set to public. The releaser will take of the publishing.

Additional context

Other organizations on npm such as @notebook and @jupyter seem to be taken. But we manage to get a hold on @jupyter-notebook which can be used for this project but also for other projects related to the Jupyter notebook ecosystem.

[afshin]

I just took a look and npm/jupyter was published by @rgbkrk 🤓

[jtpio]

Nice. Although this corresponds to a single package?

@rgbkrk do you happen to also own the @jupyter organization on npm?

[afshin]

I can't remember for sure but I think NPM allows changing a package name to an org name. But that might not be the case.

[rgbkrk]

I'll double check now.

[rgbkrk]

I do not own nor am I a member of the @jupyter org on npm.

[bollwyvl]

As discussed in the notebook meeting: I think somebody found it's possible to turn a user into an org, but not a package.

So the un- @-prefixed at e.g. https://www.npmjs.com/package/jupyter doesn't really push things forward much.

[afshin]

So the un- @-prefixed at e.g. https://www.npmjs.com/package/jupyter doesn't really push things forward much.

At least it means no one can squat the @jupyter scope but I wonder if we can ask NPM support about this.

[rgbkrk]

Someone has the @jupyter scope. I tried to register it yesterday and couldn't. IIRC @minrk or @Carreau grabbed @jupyter a long time ago.

[Carreau]

I don't think that's me.