(Created page with "= 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...") |
|||
| Line 1: | Line 1: | ||
= | = 加入EPEL特别兴趣小组 = | ||
您可以通过很多途径来帮助完善EPEL，具体可以见下面的列表。如果您有更好的想法，请通过电子邮件列表与EPEL的管理员交流。 | |||
== | == 维护软件包 == | ||
成为维护人员，您需要升级软件包、修复陈旧软件包的漏洞、增加EPEL仓库中软件的数量。详情请见[[EPEL_Package_Maintainers|EPEL软件包维护人员指南]]。 | |||
== Testing and Quality Assurance == | == Testing and Quality Assurance == | ||
Revision as of 04:39, 27 December 2011
加入EPEL特别兴趣小组
您可以通过很多途径来帮助完善EPEL，具体可以见下面的列表。如果您有更好的想法，请通过电子邮件列表与EPEL的管理员交流。
维护软件包
成为维护人员，您需要升级软件包、修复陈旧软件包的漏洞、增加EPEL仓库中软件的数量。详情请见EPEL软件包维护人员指南。
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.