Overview of Erik's TLJH maintenance effort

[consideRatio]

Attention spotlight

• 719

• 732

• 726

• 725

• 701

Misc contributions

• [x] Refactor bootstrap/bootstrap.py for readability

  • 715

• [x] Refactor integration-tests/test_bootstrap.py for readability
• [x] Refresh GitHub workflow files based on insights gained over time

  710 covers...

  • [x] Test against Ubuntu 18.04 20.04
  • [x] Test against Python 3.6 3.9
  • [x] Coalesce the duplicated test logic in integration-test.yml and upgrade-test.yml
  • [x] Adds badges to README.md
  • [x] Massive efforts to add tests against 21.10
    • [x] To pass 21.10 tests, we require a traefik-proxy release also https://github.com/jupyterhub/traefik-proxy/issues/136 https://github.com/jupyterhub/traefik-proxy/pull/139 https://github.com/jupyterhub/traefik-proxy/pull/138 https://github.com/jupyterhub/traefik-proxy/pull/137
• [x] ReadTheDocs details
  • [x] Get myself added as a RTD maintainer: https://readthedocs.org/projects/the-littlest-jupyterhub/
  • [x] Enable RTD docs builds on PRs and preview
  • [x] Add modern .readthedocs.yml file

    712

• [x] Figure out if the template file is added by mistake in #342. If so, delete it.

  713

• Update language #718

• 721

• 741

• 742

• 743

• 749

• [x] pre-commit
  • [x] Submit a PR with small fixes for flake8 etc

    747

  • [x] Submit a PR adding the config

    748

  • [x] Submit a PR making autoformat changes

    755

  • [x] Activate pre-commit.ci after merges
• [x] Version management While it is some extra work to do version management, I've found that it can be easier down the line. Having done some version management provides a clear way for documenting development changes that otherwise needs to be documented elsewhere where it will be less findable. I'd much prefer doing some additional work with managing a changelog and releases than to handle the consequences of not doing so down the line as a maintainer.

PR reviews

• [x] Review #213 I pushed a commit making the PR reasonable to merge in my mind.
• [x] Review #232
• [x] Review #325
• [x] Review #381
• [x] Review #413 I have to delegate this to someone else for now due to a lack of relevant understanding, I tried summarizing the situation though.
• [x] Review #414
• [x] Review #475
• [x] Review #521
• [x] Review #528
• [x] Review #539 I described an action point for this PR which is stale by the author, and anyone can fix it now.
• [x] Review #635
• [x] Review #649 I suggest we don't accept this PR based on personal opinion.
• [x] Review #666 I made some suggestions and then I approved and merged it.
• [x] Review #674
• [x] Review #679
• [x] Review #696
• [x] Review #697
• [x] Review #703
• [x] Review #704 I pushed a commit making the PR reasonable to merge in my mind.

Processing issues

• [x] Go through all issues

I've processed all issues, starting from the oldest to the newest. My process has been somewhere along the lines of trying to...

• provide an overview of what has been said
• make sure the original post and title reflect the situation well enough for future readers
• suggest a path to resolving the issue by outlining action points
• close it as resolved
• close it as a duplicate
• close it as something we can't/won't address

[welcome[bot]]

Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! :hugs:
If you haven't done so already, check out Jupyter's Code of Conduct. Also, please try to follow the issue template as it helps other other community members to contribute more effectively. You can meet the other Jovyans by joining our Discourse forum. There is also an intro thread there where you can stop by and say Hi! :wave:
Welcome to the Jupyter community! :tada:

[yuvipanda]

This is beautiful