I would like to apply for membership in the Provenpackager group.
I have been a Fedora packager for almost nine years, during which I have actively maintained dozens of packages. Beyond my own packages, I contribute to the maintenance and improvement of hundreds of others through my involvement in packaging groups and SIGs. My work often involves packages with wide-reaching dependencies, where updates can have a significant impact on other parts of the distribution. I strongly prefer PR workflow to direct pushes, but sometimes an unresponsive maintainer can cause issues for many others. I fully intend to use the proven packager rights only in isolated instances and still do the majority of my Fedora work the regular way via PRs.
Becoming a Provenpackager would allow me to efficiently fix issues in dependent packages when my updates introduce necessary changes, and maintainers don't respond promptly. Having these permissions would help maintain the stability and quality of Fedora, especially for ecosystem-wide updates.
The primary motivation for my application is the upcoming mass rebuild for Python 3.14, where I plan to actively participate. Provenpackager access would greatly streamline this effort, allowing me to bump release tags in all affected packages and address rebuild issues and dependency breakages promptly, reducing friction for the broader community.
I've read the Provenpackager policy and I will abide it.
Thank you for considering my request.
+1
This needs to be forwarded to sponsors, but I'm not sure how exactly we do this.
Just send an email to packager-sponsors-members@fedoraproject.org linking here and noting the initial comment.
I have now done so.
+1 as a sponsor. @lbalhar and the python-maint team as a whole do great work in Fedora.
+1 as a sponsor, I can vouch for his packaging work
Also, confirmation that we plan to use @lbalhar for the Python 3.14 rebuilds.
It's been a week. I see 12 +1's and no -1's so this request it approved.
use your powers wisely!
Metadata Update from @kevin: - Issue close_status updated to: Accepted - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.