There are two main communication channels the Modularity WG uses:
- #fedora-modularity on freenode
Most of the discussions happen on this IRC channel.
The Modularity WG doesn’t have a dedicated mailing list. Instead, the Fedora Devel mailing list is used time to time for more complex decisions or announcements.
Modularity is driven by Redhat and DNF team.
However, Modularity couldn’t happen without other working groups contributing a significant portion of effort into it, i.e.:
Issues such as bugs or feature requests can be created by anyone in the Modularity issue tracker. This issue tracker is then processed by the team and new cards or even epics may be created as a result. Separating user feedback from the work lowers the pressure on the person who reports the feedback — they don’t have to understand our tracking system.
MBS (Module Build Service) issue tracker — Issues regarding MBS upstream project specifically. If your issue or RFE changes the syntax or semantics of the MBS input or the MBS output (RPMs built in a module or resulting modular metadata), it does belong to General Modularity issue tracker. If your issue is related to particular module build in Fedora infrastructure, it belongs to Fedora Infrastructure issue tracker.
libmodulemd issue tracker — Issues regarding the modulemd specification and the libmodulemd library.
Bugzilla — Issues regarding the "dnf module" command.