Maintainer renewal

[Lucas-C]

Hi fpdf2 users 🙂👋

Just a quick word to announce a change among this project maintainers.

@gmischler, a maintainer and active developper of fpdf2 for several years,
has seemingly stopped contributing to GitHub projects for over 8 months.
After trying to contact him for several weeks without getting a response,
I decided today, with @andersonhc approval, to remove his access as a maintainer of the project.

@gmischler has been a wonderful fpdf2 contributor for several years,
helping to answer users demands, and tackling ambitious refactoring projects in fpdf2.
I sincerely want to thank him for all his volunteer work. 🙏
I hope that he is doing well, and fpdf2 would be happy to welcome him back as maintainer if he wants to.
For now however, mainly for security reasons, I want to ensure that no maintainer access to fpdf2 is given to an inactive developper.

That means that currently, fpdf2 has 2 maintainers:

• your humble servant
• @andersonhc

We would like ro recruit at least one other maintainer for fpdf2, to ensure the project continues to live on.
If you are interested in helping, please drop a comment there or contact me by email.
Just now that I expect a few things before handing maintainer access to a fellow developper:

• ensure that you are motivated in helping this project to live & grow
• ensure that you are willing to spend a few hours per month helping on answering users & fixing issues (and do even more if you wish)
• ensure that you are already an active & trustworthy open-source contributor

[ghost]

Hey @Lucas-C saw the call for contributors in the README and wanted to raise my hand. I found the project as an actual user, so my interest in contributing is genuine. I've spent a few hours in the codebase and have a decent feel for how it's structured. I noticed most of the open issues have been claimed, so I wanted to reach out directly rather than pile onto an existing thread. On the availability side, I recently finished an internship, so I have real bandwidth right now and can check in daily. Once my semester starts again I'd shift to at least weekly but I tend to stay consistent once I'm invested in something. For context on my background, I contribute to psutil and have also worked on moinmoin wiki engine, and I've dealt with large production codebases professionally. Happy to start small a bug fix, a test, whatever makes sense just wanted to let you know I'm here and motivated to work on this.

Thanks for reading.

[andersonhc]

Hi @HoraDomu, thanks a lot for reaching out and for the detailed context. That is much appreciated!

Starting small sounds like the right approach. For now, feel free to help wherever you see something relevant: commenting on issues, helping clarify bug reports, reviewing pull requests, improving tests, or submitting small fixes. That kind of contribution is already very valuable, and it is also the best way for us to get a shared sense of fit over time.

If you find an issue you would like to work on, just leave a comment there before starting so we can avoid duplicated effort. And if nothing obvious is available, PR reviews and issue triage are always helpful.

Thanks again for offering to help!