Development/Schedule
From FedoraProject
Contents |
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.
.png){kind=small}
| Task Name | Owner | Target Date | Notes |
| Priority 1 -- Look at it in every meeting | |||
| Auditing all Fedora packages for proper review | c4chris, tibbs, nirik | ||
| MISC | all | right away | |
| 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 fedora-devel-list@redhat.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 | |
| Features | poelcat | ongoing | |
| Priority 2 -- Do it soon | |||
| Sponsor Criteria | tibbs | ||
| 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, sharkcz, jds2001, j-rod
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 -- https://fedoraproject.org/wiki/PackagingDrafts/RenamingPackages - nirik
EPEL
Extra Packages for Enterprise Linux (EPEL) is a volunteer-based community effort from the Fedora project to create a repository of high-quality add-on packages for Red Hat Enterprise (RHEL) and its compatible spinoffs such as CentOS or Scientific Linux. Fedora is the upstream of RHEL and add-on packages for EPEL are sourced from the Fedora repository primarily and built against RHEL.
Getting Started with EPEL
- About EPEL
- How to use EPEL
- FAQ
- EPEL Package Wish List
- Available Packages:
- Export Regulations
Current Events
EPEL for Contributors
Joining EPEL is as simple as being part of Fedora (e.g. be a part of the packager group in the account system) and having a love for Enterprise Linux. There is a template that can be used for maintaining EPEL packages as part of a job. More details in the FAQ entry on contributing.
Communicate with the EPEL SIG or other EPEL contributors via the EPEL developers mailing list and #epel on the Freenode IRC Network.
- EPEL SIG - EPEL Special Interest Group
- EPEL Steering Committee - leads the EPEL SIG
- Schedule - tasks the EPEL SIG and its Steering Committee are working on
- Meetings - the EPEL SIG meets every other week on IRC; come and join us!
- Reports - happenings in EPEL-land summed up.
- Guidelines and Policies - specific to EPEL
- List of Fedora Contributors not participating - not all of them participate in EPEL
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.
Accepted Fedora 11 Features
- Feature pages in Category:FeatureAcceptedF11 indicate that FESCo has accepted the feature through a vote.
- Feature list summary: Releases/11/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.
