Howdy @dorafee! We're always glad to have new folks join in on the work.

The best place to start will be filing pull requests against the package source repos. That doesn't require any special permissions. You can use this to propose updates for packages, such as updating packages to new versions or fixing spec files that don't follow the packaging guidelines. Make sure that whatever you propose follows the Fedora or EPEL updates policies, depending on the branch.

To become a full blown maintainer or co-maintainer (such as for jitterentropy-rngd), you'll need to join the packager group, which requires finding a sponsor and demonstrating your proficiency. You can read more about that process in the documentation. I recommend following the path for new software as that will give you a better overview of processes than jumping directly into an existing package. The new package review process is usually a great learning experience for new packagers.

If you get stuck or have more questions, then I encourage you to join us in #epel:fedoraproject.org on Matrix, #epel on Libera Chat IRC, Fedora Discussion (discourse), or one of the development mailing lists (Fedora or EPEL) .

I'm going to close this issue out as it doesn't fit the purpose of this issue tracker, but I look forward to seeing you around the Fedora project and EPEL in particular.

Many thanks for your kind words and for pointing me to all the right resources, @carlwgeorge!

I’ve found filing the pull request for jitterentropy-rngd that you suggested to be a really helpful experience, as I got to absorb how fedora packagers do things while updating the source files.

I definitely look forward to working my way through the sponsorship rite de passage.

This issue has been migrated to Fedora Forge:
https://forge.fedoraproject.org/epel/steering/issues/229

Please continue any further discussion there.