There are two main communication channels the Modularity WG uses:
Modularity is driven by the Modularity and DNF team.
However, Modularity couldn’t happen without other working groups contributing a significant portion of effort into it, i.e.:
General issues such as bugs or feature requests for the Modularity project can be created by anyone in the General Modularity issue tracker. This issue tracker is then processed by the team and new issues or even issues against other projects may be created as a result.
Fedora Infrastructure issue tracker — Issues related to Module Build Service (MBS) and particular MBS module builds (started with
fedpkg module-build). Use this tracker, for instance, if your build hangs without finishing or failing.
Module Build Service issue tracker — Issues regarding MBS source code. If your want to propose changing a syntax or semantics of the MBS input (modulemd documents) or the MBS output (RPM packages built in a module or resulting modular metadata), it does belong to the general tracker.
libmodulemd issue tracker — Issues regarding the modulemd specification, libmodulemd library, and modulemd-validator tool.
modulemd-tools issue tracker — A collection of tools for module maintainers.
DNF component in Bugzilla — Issues regarding the