(initial dump) |
mNo edit summary |
||
| (8 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
'''THE EPEL WIKI PAGES ARE NO LONGER USED AND ARE OUT OF DATE - SEE [https://docs.fedoraproject.org/en-US/epel/ THE EPEL DOCS] FOR UP TO DATE INFORMATION.''' | |||
(These wiki pages are being kept for historical reference only.) | |||
{{autolang|base=yes}} | |||
= Joining the EPEL SIG = | = Joining the EPEL SIG = | ||
| Line 5: | Line 11: | ||
== Maintaining Packages == | == Maintaining Packages == | ||
Package Maintainers update, fix bugs and improve packages in the EPEL collection. See the [ | Package Maintainers update, fix bugs and improve packages in the EPEL collection. See the [[EPEL_Package_Maintainers|EPEL Package Maintainers]] page for more information on roles and how to join this group. | ||
== Testing and Quality Assurance == | == Testing and Quality Assurance == | ||
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 sufficent testing is done on them. See our [ | 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 sufficent testing is done on them. See our [[EPEL_QA |EPEL QA]] page for information on helping with testing and quality assurance. | ||
== Marketing == | == 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 [ | 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 == | == Release Engineering == | ||
EPEL Release engineering is | 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 [[ReleaseEngineering|Fedora Release Engineering page]] for more information. | ||
[[Category:EPEL]] | |||
Latest revision as of 19:55, 6 January 2022
THE EPEL WIKI PAGES ARE NO LONGER USED AND ARE OUT OF DATE - SEE THE EPEL DOCS FOR UP TO DATE INFORMATION.
(These wiki pages are being kept for historical reference only.)
Joining the EPEL SIG
There are many ways to join in and help out with EPEL. A few are listed below. If you think of another way to help out the SIG, feel free to bring it up on our mailing list or at our weekly meetings.
Maintaining Packages
Package Maintainers update, fix bugs and improve packages in the EPEL collection. See the EPEL Package Maintainers page for more information on roles and how to join this group.
Testing and Quality Assurance
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 sufficent testing is done on them. See our 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 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 Fedora Release Engineering page for more information.