Migrating to jupyterlab-contrib or similar?

[cmd-ntrf]

While doing my best to keep with JupyterLab, it appears it has not been enough in the last year. This brings the question if anyone would be interested in officially assisting with maintaining and development task of this project? And the follow-up question is, should we move it to something under a GitHub org like jupyterlab-contrib?

For JupyterLab-contrib, the procedure seems straightforward enough - https://jupyterlab-contrib.github.io/.

@mahendrapaipuri : Would you be interested and available in a taking an official maintainer role for this project? Would you have to keep maintaining the IDRIS-CNRS repo? Or both here and IDRIS-CNRS repo could then be archived. I think the move to renaming the extension to jupyterlab-env-modules is the right one.

@lexming : any thoughts or comments on this?

Best,
Felix

[mahendrapaipuri]

Hello @cmd-ntrf ,

Yes, I can help you out in maintaining it. We will have to rebuild our modules for the OS upgrade and once that is done, we will archive our internal fork.

Regarding the name, the legacy Tmod is renamed as environment modules and that is why I named our internal fork as jupyterlab-env-modules. If we would like to change the name of the repo, how about using jupyter-hpc-modules? Irrespective of we change the repo name or not, distributing the package under the same name jupyterlmod is a sensible option? As long as we clearly state in the README that the extension supports Tmod/Environment modules, I guess we should be ok. This way we dont break any existing installations and dependency hells.

How do you think?

[ktaletsk]

@cmd-ntrf we are using environment modules (Lmod) and this extension in our project called Notebooks Hub (learn more here: https://polusai.github.io/notebooks-hub/ and https://youtu.be/n23trabjifI?si=07pZf9vsC6qu0eIE&t=2214). I have experience updating extensions to the newest versions of JupyterLab along the years This extension helped us a lot along the way and I would also like to offer my help to maintain it.

@mahendrapaipuri I actually like the name jupyterlab-env-modules!

[lexming]

@cmd-ntrf getting this extension into jupyterlab-contrib seems a good idea, it will improve the visibility of the project and in time attract contributions. Regardless of where it is hosted though, I fully agree that merging with the IDRIS fork is the right action to keep the good health of the project.

About the name... that's tricky. Keeping the current name is definitely the least disrupting approach. But I also like the jupyterlab-env-modules option. Even though Tmod was renamed to environment modules, this term is also commonly used to generically refer to modules.