treewide: remove myself as maintainer

[jefferyto]

📦 Package Details

Maintainer: me (also: @ja-pa for python-packaging, python-pluggy, python-typing-extensions; @commodo for python3)
_{(You can find this by checking the history of the package Makefile.)}

Description:

I haven't had time to maintain these packages in a while, and saying I am a maintainer doesn't help these packages be maintained. Better to remove myself than continue standing in the way of "progress".

I will keep this PR open for at least four weeks, in case someone would like to take over maintenance for some of these packages.

---

🧪 Run Testing Details

N/A

---

✅ Formalities

• I have reviewed the CONTRIBUTING.md file for detailed contributing guidelines.

If your PR contains a patch:

• It can be applied using git am
• It has been refreshed to avoid offsets, fuzzes, etc., using

  make package/<your-package>/refresh V=s

• It is structured in a way that it is potentially upstreamable
  _{(e.g., subject line, commit description, etc.)
  We must try to upstream patches to reduce maintenance burden.}

[GeorgeSapkin]

Sorry to hear that. Can any of those packages be dropped perhaps?

[jefferyto]

Maybe we can wait for others to comment before suggesting dropping packages?

[jefferyto]

Actually I'm not sure anyone else has a more complete view of the Python packaging system so it would be irresponsible of me to not add: Most of the Python packages are either core build system packages or dependencies of other Python packages/applications, so maybe only 2-3 are completely optional. This is just my opinion though, I'm sure others will disagree.