Move repo to jupyterhub/ org

[yuvipanda]

This library is pretty good, but primarily used by jupyter-server-proxy. As such, I'd like to move it to the jupyterhub org, where it can live alongside it, and be maintained better when needed.

Part of my Volunteer Amnesty Day (https://www.volunteeramnestyday.net/) work :)

/cc @minrk @consideRatio @manics (and others?)

[minrk]

If it's mainly part of jupyter-server-proxy, 👍 to moving it.

[consideRatio]

If it is primarily important to jupyter-server-proxy, its maintenance will be focused around that, and then I think it makes sense to me. 👍

Suggested action points

Some general maintenance wishes associated with moving into the JupyterHub org are.

• Update README.md with:
  • Provide a non-technical introduction paragraph helping anyone understand its role in the JupyterHub ecosystem and purpose without themselves needing to understand much technical details.
  • Update badges like other JupyterHub projects (copy paste from https://github.com/jupyterhub/oauthenticator/ for example)
• Update master branch to main (described in Rename GitHub branches from master to main team-compass#412)
• Use GitHub workflows for running tests
  • Fix broken state GitHub workflow tests (Fix CI test failures #12)
• Use GitHub workflows for release automation
  • Register PyPI environment variables:
    • Add jupyterhub-bot as a PyPI maintainer of the PyPI project at https://pypi.org/project/simpervisor/
    • Mimic release workflow from for example https://github.com/jupyterhub/oauthenticator/blob/master/.github/workflows/publish.yml
    • Setup a PYPI_PASSWORD GitHub Secret with a jupyterhub-bot PyPI deployment token

[yuvipanda]

@minrk @consideRatio ok yay I moved it :) <3 I also added @consideRatio and @minrk as owners on PyPI.

[consideRatio]

Closing this as resolved, I've opened other issues to represent action points in checklist above!