Hi everybody,

I would like to apply to be a provenpackager. My main motivation for requesting this is that I'd like to be able to perform go CVE rebuilds without having to pester a provenpackager to handle it. Currently, I handle the repoquerying, announcing, coordination, and script writing. I rebuild the packages that the @go-sig has access to and then give @eclipseo a script to run for the others[1]. It would be more efficient if I could completely handle the process myself. The go-sig is trying to do a better job with doing (targeted) rebuilds[2] when golang or one of the libraries has a CVE. This rebuilding is necessary due to static linking.

I will also be able to help out with other provenpackager tasks (.so name bump rebuilds, important bugs, planned mass specfile cleanups, etc.)

Re my Fedora credentials:

I directly maintain or co-maintain 48 packages, according to the packager-dashboard. I also help maintain several more as a member of the go-sig. My packages consist of some python packages (mostly applications), some go packages, a C++ package, several ansible collections, and ansible-packaging, a set of macros and generators for packaging ansible collections. I am very familiar with RPM packaging, the Fedora Packaging Guidelines, and our macros. I have also contributed to the go macros and the Python macros (in EPEL).

I have completed 29 reviews myself. I have contributed to or started some other reviews. I have also recently become a packager sponsor.

[1]: We have sent multiple emails asking packagers to give @go-sig permissions on their go packages but there are still a good amount of packagers that have not responded.

[2]: In the past, rebuilds didn't happen at all.