Rename to jupyter-resource-usage

[jtpio]

Now that the repo has been moved to the jupyter-server organization (jupyter-server/team-compass#3), we should be able to rename the Python package and other instances of nbresuse to jupyter-resource-usage.

And publish a new version on PyPI with the new name.

TODO

• Rename the jupyter-resource-usage
• Publish to PyPI: https://pypi.org/project/jupyter-resource-usage/
• Publish the lab extension to npm
• Add new maintainers for the PyPI package
• Document how to migrate to 0.5.0 in the changelog (and compatibility with JupyterLab 2 and 3)
• Create new conda recipe: Add jupyter-resource-usage conda-forge/staged-recipes#13508
• Handle the renaming for the conda forge package: https://github.com/conda-forge/nbresuse-feedstock -> https://github.com/conda-forge/jupyter-resource-usage-feedstock
• Update Binder

[manics]

If you're renaming the package this might be a good opportunity to make any breaking changes? e.g. following up from #68 /metrics could be completely removed instead of just deprecated?

[jtpio]

Good point.

And include the lab extension for JupyterLab 3: #69

So everything would work with the new endpoint with a single: pip install jupyter-resource-usage.

[jtpio]

To rename the project on PyPI, we can follow this: https://www.python.org/dev/peps/pep-0423/#how-to-rename-a-project

For conda, we can probably do something similar:

• create a new feedstock for jupyter-resource-usage
• make the current recipe only depend on the new package in https://github.com/conda-forge/nbresuse-feedstock

[jtpio]

Also, even though the name of the package changes, we can continue with 0.5.0 for the next version.

Which should make make things less confusing, especially when following the changelog.

[jtpio]

Since this repo lives in the jupyter-server organization, I just invited the same list of maintainers as for the jupyter-server package: https://pypi.org/project/jupyter-server/ + Yuvi.

Let me know if you would like to be added as a maintainer on PyPI.

[Jeffwan]

I am new to this area. What does it mean when this repo moved to jupyter-server org? Will this repo ship with jupyter server together?

[jtpio]

Thanks and welcome @Jeffwan!

The move was done mostly to answer some questions about the maintainability of the project and its future. There are a couple of other projects using it, and some people willing to contribute to it.

There are also some answers in jupyter-server/team-compass#3 and #62.

And the roadmap: #58
With some items talking about having metrics baked in Jupyter Server at some point in the future.

[krassowski]

It looks like this issue could be closed.

[jtpio]

yes!

[jtpio]

btw @krassowski and / or @echarles (or anyone interested) if you would like to be added as maintainer for the conda package, feel to open a PR on https://github.com/conda-forge/jupyter-resource-usage-feedstock. Thanks!