From 9bd998d78c0459b2819a48c9ff457f4cadec3dbb Mon Sep 17 00:00:00 2001 From: Troy Dawson Date: Jun 01 2022 16:14:39 +0000 Subject: EPEL has no marketing setup --- diff --git a/modules/ROOT/pages/epel-help.adoc b/modules/ROOT/pages/epel-help.adoc index 6affe60..18c107b 100644 --- a/modules/ROOT/pages/epel-help.adoc +++ b/modules/ROOT/pages/epel-help.adoc @@ -12,10 +12,6 @@ Package Maintainers update, fix bugs and improve packages in the EPEL collection EPEL strives to ship packages that are as stable and bug free as possible. Testing of packages is always welcome. EPEL uses the Bodhi updates system to manage updates. Packages enter the epel-testing repository where they MUST spend 2 weeks or until sufficient testing is done on them. See our xref:epel-qa.adoc[EPEL QA] page for information on helping with testing and quality assurance. -== Marketing == - -Informing Enterprise Linux users that EPEL is here and ready with add-on packages as well as growing our contributor base is the task of our Marketing folks. See [[EPEL_Marketing|EPEL Marketing]] for more information. - == Release Engineering == EPEL Release engineering is responsible for making sure packages are built and signed and mirrored out. Currently this group is a subset of the Fedora Release Engineering group. See the link:https://docs.pagure.org/releng/contributing.html[Fedora Release Engineering page] for more information. diff --git a/modules/ROOT/pages/index.adoc b/modules/ROOT/pages/index.adoc index f002366..e010e4c 100644 --- a/modules/ROOT/pages/index.adoc +++ b/modules/ROOT/pages/index.adoc @@ -239,7 +239,7 @@ more information. == How can I contribute? The EPEL SIG is always looking for interested folks to help out. We -always need package maintainers, QA/testers, bug triagers, marketing and +always need package maintainers, QA/testers, bug triagers and documentation writers. Please see our link:epel-help[Joining EPEL] page for more information on how to join the SIG.