From Fedora Project Wiki
m (→FESCo Open Issues: Fix punctuation.) |
|||
| (4 intermediate revisions by 2 users not shown) | |||
| Line 9: | Line 9: | ||
<!-- and the entry for it on this page --> | <!-- and the entry for it on this page --> | ||
== FESCo Open Issues == | == FESCo Open Issues == | ||
{{Admon/caution | This page is no longer used and maintained. }} | |||
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 [[Development/SteeringCommittee| FESCo page]] for their real names and their nicknames -- the latter are used on this page to show who owns a task). | 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 [[Development/SteeringCommittee| FESCo page]] for their real names and their nicknames -- the latter are used on this page to show who owns a task). | ||
| Line 14: | Line 17: | ||
FESCo looks at this list in their weekly [[Development/SteeringCommittee/Meetings| 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). | FESCo looks at this list in their weekly [[Development/SteeringCommittee/Meetings| 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 [[Development/Schedule/MeetingGuidelines| Meeting Guidelines]] for information on how to propose a new topic | You think FESCo needs to handle another issue? See [[Development/Schedule/MeetingGuidelines| Meeting Guidelines]] for information on how to propose a new topic. | ||
{{Admon/caution | 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}} | {{Admon/caution | 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}} | ||
| Line 53: | Line 54: | ||
|} | |} | ||
= FESCo Closed Issues = | |||
= | |||
You can find all currently tracked issues, including ones we resolved already, in our [https://fedorahosted.org/fesco/report/6 report of all Trac issues]. Old issues that we've closed before moving to Trac are listed on their own [[Extras/Schedule/ClosedIssues| Closed Issues]] page. | |||
[[Category:FESCo]] | [[Category:FESCo]] | ||
Latest revision as of 18:11, 21 May 2012
FESCo Open Issues
.png){kind=small}
This page is no longer used and maintained.
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.
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
| 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 | |||
FESCo Closed Issues
You can find all currently tracked issues, including ones we resolved already, in our report of all Trac issues. Old issues that we've closed before moving to Trac are listed on their own Closed Issues page.