- 1 FESCo Open Issues
- 2 Rough plan for the next IRC meeting
- 3 Extra Packages for Enterprise Linux (EPEL)
- 3.1 Quickstart
- 3.2 What is Extra Packages for Enterprise Linux (or EPEL)?
- 3.3 What packages and versions are available in EPEL?
- 3.4 END OF LIFE RELEASES
- 3.5 How can I use these extra packages?
- 3.6 Can I rely on these packages?
- 3.7 History and background of the project
- 3.8 How can I contribute?
- 3.9 Communicating with the EPEL SIG
- 4 Fedora Feature Dashboard
- 5 Proposed Fedora Features
- 6 Accepted Fedora 14 Features
- 7 Feature Pages Under Construction
- 8 Process & Policy
FESCo Open Issues
This page describes all open actions that are currently handled by the Fedora Engineering Steering Commitee (FESCo). The committee currently has 9 members -- look at the FESCo page ) for their real names and their nicknames -- the latter are used on this page to show who owns a task.
FESCo looks at this list in their weekly meetings . All topics listed here normally have an owner because things tend to get stuck if there is no one who drives stuff forward (or is poked to work further on it).
You think FESCo needs to handle another issue? See Meeting Guidelines for information on how to propose a new topic. Or:
- Add it to the Container and hope somebody runs with it.
- Send a mail to the FESCo Chair, and hope somebody runs with it.
|Task Name||Owner||Target Date||Notes|
|Priority 1 -- Look at it in every meeting|
|Auditing all Fedora packages for proper review||c4chris, tibbs, nirik|
|Priority 1.5 -- Standing events, normally visitied each meeting|
|Packaging Committee Report||spot, abadger1999, rdieter, tibbs, scop||ongoing||A representative from the packaging committee will send a report after each committee meeting to email@example.com for public discussion. In order to give ample discussion time, this report should be sent no less than 24 hours before the next FESCo meeting; if the report is late, the veto period will be extended by one additional FESCo meeting. FESCo may also extend the veto period if there is still ongoing discussion.|
|Administrative requests||Meeting Chair||ongoing|
|Priority 2 -- Do it soon|
|Priority 3 -- Do it at some point|
|Compat Policy||bpepple||Jan '08||Has been dropped for now, due to response that it's not needed. Will keep it here for now, in case a need for it shows-up in the future.|
|Alternative paths of membership advancement|
|MISC long term||all||not urgent|
|Priority 3.5 -- handled mostly by other groups, but needed for Fedora|
Rough plan for the next IRC meeting
/topic FESCo meeting -- Meeting rules at http://www.fedoraproject.org/wiki/Development/Schedule/MeetingGuidelines -- Init process
FESCo meeting ping -- bpepple, dgilmore, dwmw2, jwb, notting, nirik, kick_, jds2001, j-rod
Hi everybody; who's around?
/topic FESCo meeting -- Any objection to last week's report from FPC at https://www.redhat.com/archives/fedora-devel-list/2008-September/msg02133.html
/topic FESCo-Meeting -- Elect new FESCo chair - all
/topic FESCo-Meeting -- New FESCo meeting time - all
/topic FESCo-Meeting -- Adding provenpackagers to experienced maintainer definition - http://www.redhat.com/archives/fedora-devel-list/2008-December/msg02338.html - nirik
/topic FESCo-Meeting -- PackagingDrafts/RenamingPackages - nirik
Extra Packages for Enterprise Linux (EPEL)
Welcome to the home of the EPEL Special Interest Group.
You may retrieve signed binary configuration files from one the above two links (varying by the major release number of the installation target machine). They may be automatically installed by root thus:
- RHEL/CentOS 6:
- RHEL/CentOS 7:
- on RHEL 7 it is recommended to also enable the optional and extras repositories:
# subscription-manager repos --enable rhel-7-server-optional-rpms --enable rhel-7-server-extras-rpms
What is Extra Packages for Enterprise Linux (or EPEL)?
Extra Packages for Enterprise Linux (or EPEL) is a Fedora Special Interest Group that creates, maintains, and manages a high quality set of additional packages for Enterprise Linux, including, but not limited to, Red Hat Enterprise Linux (RHEL), CentOS and Scientific Linux (SL), Oracle Linux (OL).
EPEL packages are usually based on their Fedora counterparts and will never conflict with or replace packages in the base Enterprise Linux distributions. EPEL uses much of the same infrastructure as Fedora, including buildsystem, bugzilla instance, updates manager, mirror manager and more.
Learn more about EPEL in the following pages:
What packages and versions are available in EPEL?
You can take a look on any of the available EPEL mirrors from our mirror list
Alternately, you can browse the package set:
END OF LIFE RELEASES
THESE ARE NO LONGER SUPPORTED
How can I use these extra packages?
EPEL has an 'epel-release' package that includes gpg keys for package signing and repository information. Installing this package for your Enterprise Linux version should allow you to use normal tools such as yum to install packages and their dependencies. By default the stable EPEL repo is enabled, there is also a 'epel-testing' repository that contains packages that are not yet deemed stable.
If you are running an EL7 version, please visit here to get the newest 'epel-release' package for EL7: The newest version of 'epel-release' for EL7
If you are running an EL6 version, please visit here to get the newest 'epel-release' package for EL6: The newest version of 'epel-release' for EL6
EPEL for EL5 is no longer supported. If you are running EL5, please upgrade your operating system to either EL6 or EL7.
You can verify these packages and their keys from the Fedora project's keys page: https://fedoraproject.org/keys
Can I rely on these packages?
The EPEL project strives to provide packages with both high quality and stability. However, EPEL is maintained by a community of people who generally volunteer their time and no commercial support is provided. It is the nature of such a project that packages will come and go from the EPEL repositories over the course of a single release. In addition, it is possible that occasionally an incompatible update will be released such that administrator action is required. By policy these are announced in advance in order to give administrators time to test and provide suggestions.
It is strongly recommended that if you make use of EPEL, and especially if you rely upon it, that you subscribe to the epel-announce list. Traffic on this list is kept to a minimum needed to notify administrators of important updates.
History and background of the project
The EPEL project was born when Fedora maintainers realized that the same infrastructure that builds and maintains packages for Fedora would be great to also maintain add on packages for Enterprise Linux. Much of the early need was driven by what Fedora infrastructure needed on the RHEL machines that built and maintained Fedora. From there things have grown to a large collection of varied packages. See our history and Philosophy page for 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 documentation writers. Please see our Joining EPEL page for more information on how to join the SIG.
Communicating with the EPEL SIG
There are many ways to communicate with the EPEL SIG and its members:
- The IRC channel on irc.freenode.net offers real-time support for EPEL users and developers.
- The epel-devel is for general developer and SIG discussion.
- The epel-announce mailing list is a low volume mailing list for only important announcements.
- The epel-package-announce list is a list that gets information about package updates as they happen in the stable repository.
- If you find a bug in a EPEL maintained package, please report it to https://bugzilla.redhat.com/ under the "Fedora EPEL" product.
- The EPEL SIG meets on Wednesday every week in the epel-Fedocal; sometimes it can change or a meeting can be skipped. Feel free to join us! Logs of past meetings can be found at: http://meetbot.fedoraproject.org/epel/ channel at 18:00 UTC. Please check the time on
Fedora Feature Dashboard
Proposed Fedora Features
Ready for Feature Wrangler
- Feature pages in Category:FeatureReadyForWrangler indicate that they are believed to be complete and ready for FESCo. The Feature Wrangler performs a sanity check of the feature page changes it to Category:FeatureReadyForFesco if everything is in order.
Ready For FESCo
- Feature pages in Category:FeatureReadyForFesco indicate that they have been reviewed by the Feature Wrangler and are ready for FESCo's review.
- FESCo tracks features to be reviewed in their ticketing system after they reach Category:FeatureReadyForFesco. If you are a feature owner you should be notified prior to the meeting so you can be present. Routine meeting information for FESCo is found on the FESCo page. However, FESCo does hold supplementary meetings from time to time. If you do not know the meeting time, you can ask on IRC Freenode, #fedora-devel, or email the FESCo list.
Accepted Fedora 14 Features
- Feature pages in Category:FeatureAcceptedF14 indicate that FESCo has accepted the feature through a vote.
- Feature list summary: Releases/14/FeatureList
Feature Pages Under Construction
- Feature pages in Category:FeaturePageIncomplete indicates that work is in progress for the feature page.
Process & Policy
- More details about how the feature process works are at Features/Policy
/topic FESCo meeting -- Free discussion around Fedora
/me will end the meeting in 60
/me will end the meeting in 30
/me will end the meeting in 15
-- MARK -- Meeting End
Fedora Engineering Closed Issues
Issues that we've closed are listed on their own Closed Issues page . Y'know, so we can actually track some progress.