From 3d5889821001c88ca7e4a4bac9f20381b1b2d537 Mon Sep 17 00:00:00 2001 From: Martin Curlej Date: Jun 02 2021 11:25:53 +0000 Subject: Updated contact info on the 'Community Page' Signed-off-by: Martin Curlej --- diff --git a/modules/ROOT/pages/community.adoc b/modules/ROOT/pages/community.adoc index 7aa24c2..13b3db6 100644 --- a/modules/ROOT/pages/community.adoc +++ b/modules/ROOT/pages/community.adoc @@ -11,7 +11,7 @@ There are two main communication channels the Modularity WG uses: :hash: # -https://webchat.freenode.net/?channels=fedora-modularity[{hash}fedora-modularity^] on freenode:: +https://webchat.freenode.net/?channels=fedora-devel[{hash}fedora-devel^] on freenode:: Most of the discussions happen on this IRC channel. https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/[devel@lists.fedoraproject.org^]:: @@ -24,11 +24,13 @@ The https://fedoraproject.org/wiki/Server[Server SIG^] also discusses Modularity == Working Groups and Teams -Modularity is driven by Redhat and DNF team. +Modularity is driven by the Modularity and DNF team. -* Daniel Mach mailto:dmach@redhat.com[dmach@redhat.com] - modularity product owner and tech lead -* Jaroslav Mracek mailto:jmracek@redhat.com[jmracek@redhat.com] - modularity in DNF -* Martin Curlej mailto:mcurlej@redhat.com[mcurlej@redhat.com] - documentation and infrastructure +* 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 However, Modularity couldn’t happen without other working groups contributing a significant portion of effort into it, i.e.: @@ -49,4 +51,4 @@ Issues such as bugs or feature requests can be created by anyone in the Modulari * 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. \ No newline at end of file +* https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&short_desc=%5Bmodularity%5D&component=dnf[Bugzilla^] — Issues regarding the "dnf module" command.