I'm requesting to be added to the proven packager group. The primary purpose is to address any release-to-release ABI issues that arise due to packages that I maintain. I am the primary maintainer of glibc and libffi and support these packages with the help of the Fedora toolchain team.

Most pressing is the libffi 3.1 to 3.4 transition planned for Fedora 34 which will be handled with a compatibility library, but there is still the chance that we need to rebuild specific packages or fix ABI or API issues quickly and in a timely fashion to resolve regressions in Rawhide. The 3.1 to 3.4 libffi transition should be API compatible but because of the SONAME bump and the structure size and layout changes it may require NEVRA bumps and rebuilds of specific packages. For now I've tested that 11-kit, python3.9, glib2, gobject-introspection, pygobject3, guile22, wayland and
llvm have built correctly with the new ABI, but if any other lingering packages exposed the size of the closure in another structure that was ABI then we'd need to do targetted rebuilds.

Concretely there is always a release-to-release need to potentially fix any glibc ABI or API fallout and help the community with these transitions.

I've been a package maintainer in Fedora since 2012 when I took over the maintenance of glibc and I file system-wide change requests for every Fedora release in order to schedule and coordinate the ABI and API transitions for glibc.

I'm reaching out to @fweimer, @jwakely and @law for votes to get proven packager.

Thanks,
Carlos O'Donell
carlos@redhat.com