DOC: stefan6419846 becomes BDFL of pypdf

[MartinThoma]

See #3063

[MartinThoma]

@stefan6419846 Could you please directly edit the two TODOs? I'm not sure how you want to handle that.

Due to past experiences I wanted to provide an official guide on how to deal with an unresponsive BDFL. As the new BDFL, it's your choice how to handle that :-) (Same for the security contact, of course)

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.50%. Comparing base (493785c) to head (045dcb6).
Report is 13 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3078      +/-   ##
==========================================
+ Coverage   96.47%   96.50%   +0.02%     
==========================================
  Files          52       52              
  Lines        8778     8807      +29     
  Branches     1600     1612      +12     
==========================================
+ Hits         8469     8499      +30     
+ Misses        184      183       -1     
  Partials      125      125              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[stefan6419846]

Thanks, I will have a look at the this in the next days. For security issues, GitHub seems to provide an option for "Private vulnerability reporting" (https://docs.github.com/en/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/privately-reporting-a-security-vulnerability), which avoids relying on sending e-mails explicitly and seems to be the recommended way, but I will have to do some more reading before changing and activating this.

[stefan6419846]

@MartinThoma I have adapted some of the parts and enabled private vulnerability reporting. Feel free to have a look if you are okay with the general changes before merging.