Official Handover of the maintainer role to stefan6419846

[MartinThoma]

@stefan6419846 has been way more active in the past year than I was. He has proven to have the technical knowledge and the necessary skills to be the core maintainer of pypdf. We have discussed this and I will handover to him.

For the community, not much will change. The project is pretty mature and stefan is contributing for a while already. This step is mainly to give him the credit he deserves and to ensure we keep a good development speed :-)

I'll use this issue to keep track of things I need to do / to answer questions if anybody has any / to give others the option to remind me of stuff I might have forgotten. Maybe I should write a guide in this context as well 🤔

I will still be available, but as in the past months it might take me longer to respond (just ping me again if I don't react within 3 days :-) ).
I will also keep having access to all of the systems, but I'll only use it if a security issue / lost access happens. Similar to how some previous maintainers also still have access.

Thank you @stefan6419846 for all the time and expertise you put into pypdf ❤

TODO

• 🔲 Documentation: Adjust the "history of pypdf" and mention Stefan; switch my name to his as the "benevolent dictator"
• ✅ Permissions on Readthedocs
• ✅ Permissions on Github: Upgraded from "maintain" to "admin"
• ✅ Permissions on PyPI

[stefan6419846]

Thanks for the kind words and trusting me with ensuring future maintenance of pypdf.

As a short follow-up: I just accepted the invitation for Read the Docs and the builds for PRs are still being triggered and the status got reported in the latest PR (#3059) as well, but there seems to be some odd warning on the actual builds page (https://app.readthedocs.org/projects/pypdf/builds/):

GitHub build status report failed

Could not send GitHub build status report for "pypdf". Make sure you have the correct GitHub repository permissions and your GitHub account is connected to Read the Docs.

[MartinThoma]

Yes, this warning exists for a long time. I have no idea why it's there or how to fix it ... but as long as the docs get generated I also had no pressure to fix it 😅

[shartzog]

Thanks so much for resurrecting this project @MartinThoma. Best of luck in the future.
Congratulations (I think ;)), @stefan6419846! Your dedication to this project is evident and impressive. Looking forward to more great things from pypdf in the future.