FESCo Open Issues
This page describes all open actions that are currently handled by the Fedora Engineering Steering Commitee (FESCo). The committee currently has 13 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.
Hint: The right column in below table is only an overview of the status and the remaing todo-items. For the full contect of a topic please click on the name of the topic in the left column and you'll normally find a own page that describes everything in more detail
Rough plan for the next IRC meeting
FESCo meeting ping -- bpepple, caillon, c4chris, dgilmore, dwmw2, f13, jeremy, jwb, notting, spot, nirik, tibbs, warren
Hi everybody; who's around?
/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.
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:
- EPEL 7: x86_64, ppc64, ppc64le, aarch64, sources
- EPEL 6: i386, x86_64, ppc64, sources
- EPEL 5: i386, x86_64, ppc, sources
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
If you are running an EL5 version, please visit here to get the newest 'epel-release' package for EL5: The newest version of 'epel-release' for EL5
You can verify these packages and their keys from the Fedora project's keys page: https://fedoraproject.org/keys
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 Friday every week in the https://apps.fedoraproject.org/calendar/location/fedora-meeting%40irc.freenode.net/; 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 17:00 UTC. Please check the time on
/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.