One thing to note about modules in epel9. epel9 modules will not be able to build against RHEL 9 modules.
At the time I'm writting this, there aren't any RHEL 9 modules, but when there are some, epel9 will not be able to build against them.

Talked about this in the 2021-12-08 committee meeting. Nobody said no, but that it was a low priority at the moment. We will discuss it again in the new year.
If others want to build modules in epel9, please put it down here so we know how much interest there is.

I would like to provide zabbix as modules. I do not believe I would need to build against any future modules, though it would certainly make use of php modules as needed by the end user.

At this time, the amount of work to bootstrap and maintain modularity is more than can be taken up by either EPEL Steering Committee or Fedora Releng. We are going to close this and will revisit in the future.

For transparency, I wanted to share some of the information I gathered to help inform this decision. EPEL8 currently has 14 modules. I emailed all of the maintainers of these modules and asked if they were planning on adding the same module to EPEL9.

• 4 modules had maintainers respond that they were interested in adding it to EPEL9.
• 5 modules had maintainers respond that they were not interested in adding it to EPEL9.
• 5 modules didn't have any maintainers respond.

Of the 4 modules that had maintainers reply in favor:

• 2 modules only have a single stream and could likely work as regular RPMs in EPEL9.
• 1 does not install (any of the available streams)
• 1 had a maintainer express they would be OK with other solutions if EPEL9 skipped adding a modular repo.