From abfb3cb3dcfa7e3c88f76d4c8e7016e0b1811809 Mon Sep 17 00:00:00 2001 From: Petr Písař Date: Mar 25 2022 12:36:59 +0000 Subject: Update Community page New IRC, new people. Issue trackers restructured. --- diff --git a/modules/ROOT/pages/community.adoc b/modules/ROOT/pages/community.adoc index b2f0cdb..fa20d2f 100644 --- a/modules/ROOT/pages/community.adoc +++ b/modules/ROOT/pages/community.adoc @@ -13,13 +13,15 @@ There are two main communication channels the Modularity WG uses: :hash: # -https://web.libera.chat/#fedora-devel[{hash}fedora-devel^] on Libera.Chat:: +IRC channel https://web.libera.chat/#fedora-devel[{hash}fedora-devel^] on Libera.Chat:: Most of the discussions happen on this IRC channel. -https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/[devel@lists.fedoraproject.org^]:: +https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/[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: + https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org/[server@lists.fedoraproject.org^]:: The https://fedoraproject.org/wiki/Server[Server SIG^] also discusses Modularity at times as the Server Edition is a primary stakeholder in the goals of the https://fedoraproject.org/wiki/Objectives#Current[Modularity Objective^]. @@ -31,7 +33,6 @@ Modularity is driven by the Modularity and DNF team. * Martin Čurlej mailto:mcurlej@redhat.com[mcurlej@redhat.com] - Modularity product owner and tech lead * Petr Písař mailto:ppisar@redhat.com[ppisar@redhat.com] - Developer and libmodulemd maintainer * Filip Valder mailto:fvalder@redhat.com[fvalder@redhat.com] - Developer and infrastructure -* Daniel Mach mailto:dmach@redhat.com[dmach@redhat.com] - DNF product owner and tech lead * Jaroslav Mráček mailto:jmracek@redhat.com[jmracek@redhat.com] - Modularity in DNF @@ -41,16 +42,19 @@ However, Modularity couldn’t happen without other working groups contributing * https://docs.pagure.org/releng/[Fedora Release Engineering^] * https://fedoraproject.org/wiki/Infrastructure[Fedora Infrastructure^] -== Reporting issues +== 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 issues such as bugs or feature requests for the Modularity project can be created by anyone in the https://pagure.io/modularity/issues[General Modularity issue tracker][[gerneral_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. -* https://pagure.io/modularity/issues[General Modularity issue tracker^] — For general issues or when it is not clear where to report specifically +=== Issues with Content === -* Bugs against Fedora modules are reported in https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora%20Modules&short_desc=%5Bmodularity%5D&component=dnf[Bugzilla^]. +* https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora%20Modules[Fedora Modules product in Bugzilla] — Bugs in concrete Fedora modules. +* https://pagure.io/releng/fedora-module-defaults/issues[fedora-module-defaults issue tracker] — Setting default profiles, default streams, stream end of lives, obsoleted and replacing streams. -=== Project and Components related to Modularity: +=== Tools Related to Modularity: -* https://pagure.io/fm-orchestrator/issues[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 https://pagure.io/modularity/issues[General Modularity issue tracker^]. If your issue is related to particular module build in Fedora infrastructure, it belongs to https://pagure.io/fedora-infrastructure/[Fedora Infrastructure issue tracker^]. -* https://github.com/fedora-modularity/libmodulemd/issues[libmodulemd issue tracker^] — Issues regarding the modulemd specification and the libmodulemd library. -* https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&short_desc=%5Bmodularity%5D&component=dnf[Bugzilla^] — Issues regarding the "dnf module" command. +* https://pagure.io/fedora-infrastructure/[Fedora Infrastructure issue tracker^] — Issues related to https://mbs.fedoraproject.org/module-build-service/2/module-builds/[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. +* https://pagure.io/fm-orchestrator/issues[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 <>. +* https://github.com/fedora-modularity/libmodulemd/issues[libmodulemd issue tracker^] — Issues regarding the modulemd specification, libmodulemd library, and modulemd-validator tool. +* https://github.com/rpm-software-management/modulemd-tools/issues[modulemd-tools issue tracker] — A collection of tools for module maintainers. +* https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&short_desc=%5Bmodularity%5D&component=dnf[DNF component in Bugzilla^] — Issues regarding the `dnf module` command.