Maintenance

[xhochy]

Hello @betatim, not sure how much motivation you have on keeping to maintain this here. We are heavy users of this extension. Currently, we are blocked by #32 from upgrading to a new code-server version. This repo only works with code-server<4. One thing forward for us would be to merge the PR but then we will come to the point where a release is necessary and a bit of github automation would probably be nice. Happy to contribute that but:

1. Do you have the time/motivation to review this?
2. Should we instead fork this and do our own maintenance?
3. Would you trust me as a second maintainer here (instead of forking)?

[xhochy]

To show that I really want this, here is a simple CI to build and publish: #34

[betatim]

For a short term solution I've added you as a collaborator. Instead of forking I wonder if we can move the repo somewhere where it is easier/more natural to have more people take care of this?

[xhochy]

That would be nice but I guess you know the possible places in the Jupyter ecosystem better than me ;)

[betatim]

Hah, in general I vote against adding things like this to the jupyterhub org. The people in the JH org have enough to do already, without having to maintain random repos that are only of interest to ~5 people in the world :-/

[maresb]

More than just 5 people! 👋 😉 (At least 6.)

[xhochy]

I was hoping there would be some -contrib org for related but unpopular stuff.

[manics]

I'm in favour of jupyterhub-contrib!
Relevant discussion: jupyterhub/team-compass#519