https://github.com/jupyter/jupyter_events needs maintenance.

[Carreau]

It has been breaking downstream projects (including jupyter_server CI) for some time due to deprecation and various other issues.

I'll try to spend a few hours on it as I can; but it will need a long term maintenance plan.

[Carreau]

I fixed the critical things and published a new release because it was critical and I was able to afford the few hours; but having regular monitoring of issues/PRs on this package and other woudl be a good thing.

[jasongrout]

Thanks @Carreau! What subproject council do you think is responsible for this repo?

[Carreau]

I don't know. The only visible maintainer is @Zsailer ; as AFAICT from the PR it affect jupyter-server and jupyter-lab.

I did a 0.11 release to fix some failing CI in jupyter-server, but I might yank it as it seem to have deep reaching consequences.

In general I think there should be tools to check the mapping activity of GH-repos, to pypi packages, and a file that describe who should be responsible to check and maybe auto-open issues here if a repo seem unmaintained.

[afshin]

I would propose this project be part of Jupyter Server.

[Zsailer]

I would propose this project be part of Jupyter Server.

I agree. I will trigger the transfer by opening a vote with the team.

I fixed the critical things and published a new release because it was critical and I was able to afford the few hours; but having regular monitoring of issues/PRs on this package and other woudl be a good thing.

Thank you, Matthias. I appreciate your time here. I'm in the same boat—doing my best to contribute/maintain this project when I get space/time. We do track this in the Jupyter Server meeting, but it's fallen through the cracks.

[Carreau]

We do track this in the Jupyter Server meeting

I believe that's where there should be some tooling, like a single place with all the repo "last activity", time since last publication on PyPI (if relevant) ... etc.

This is the kind of things that typically are easier with a single org as you can view all repos of an org e.g: https://github.com/orgs/jupyter-server/repositories which you can now sort by "last push" etc.

And also not having to transfer repositories and changing all urls is also one more reaosns to stop have 21+ orgs.