Community
This page lists the communication channels of members of the Modularity Working Group (Modularity WG), related projects and also how you can contribute to the project.
Channels
There are two main communication channels the Modularity WG uses:
- #fedora-devel on Libera.Chat
-
Most of the discussions happen on this IRC channel.
- devel@lists.fedoraproject.org
-
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.
- server@lists.fedoraproject.org
-
The Server SIG also discusses Modularity at times as the Server Edition is a primary stakeholder in the goals of the Modularity Objective.
Working Groups and Teams
Modularity is driven by the Modularity and DNF team.
-
Martin Čurlej mcurlej@redhat.com - Modularity product owner and tech lead
-
Petr Písař ppisar@redhat.com - Developer and libmodulemd maintainer
-
Filip Valder fvalder@redhat.com - Developer and infrastructure
-
Daniel Mach dmach@redhat.com - DNF product owner and tech lead
-
Jaroslav Mráček jmracek@redhat.com - Modularity in DNF
However, Modularity couldn’t happen without other working groups contributing a significant portion of effort into it, i.e.:
Reporting issues
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.
-
General Modularity issue tracker — For general issues or when it is not clear where to report specifically
-
Bugs against Fedora modules are reported in Bugzilla.
Project and Components related to Modularity:
-
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.