Comunidad

Esta página lista los canales de comunicación de los miembros del Modularity Working Group (Modularity WG) (Grupo de Trabajo de Modularidad), de los proyectos relacionados y de como puede usted colaborar con el proyecto.

Table of Contents

Canales
Working Groups and Teams
Reporting Issues
- Issues with Content
- Tools Related to Modularity:

Canales

There are two main communication channels the Modularity WG uses:

IRC channel #fedora-devel on Libera.Chat: Most of the discussions happen on this IRC channel.
devel@lists.fedoraproject.org mailing list: 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.

Related channels:

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
Marek Kulik mkulik@redhat.com — Developer and infrastructure
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

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.

Issues with Content

Fedora Modules product in Bugzilla — Bugs in concrete Fedora modules.
fedora-module-defaults issue tracker — Setting default profiles, default streams, stream end of lives, obsoleted and replacing streams.

Tools Related to Modularity:

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 dnf module command.

Want to help? Learn how to contribute to Fedora Docs ›