The FPC is an independent subcommittee of the [[Development/SteeringCommittee | Fedora Steering Committee (FESCo)]] , and reports to [[Development/SteeringCommittee | FESCo]] for final approval on all Packaging Guidelines changes.

+

The FPC is an independent subcommittee of the [[Development/SteeringCommittee | Fedora Steering Committee (FESCo)]].

+

+

{{admon/note||The FPC will no longer require FESCo ratification of approved drafts/changes, however, any FPC member who feels an approved draft/change would benefit from explicit FESCo review and ratification may request it.}}

== Meetings and Discussions ==

== Meetings and Discussions ==

Line 13:

Line 15:

{{Anchor|Meetings}}

{{Anchor|Meetings}}

=== Meetings ===

=== Meetings ===

−

The Fedora Packaging Committee currently meets every other Tuesday at 17:00 UTC, in #fedora-meeting on the [http://freenode.net FreeNode IRC Network] .

+

The Fedora Packaging Committee currently meets every Thursday at 16:00 UTC, in {{fpchat|#fedora-meeting-1}} on the freenode.net .

{{Anchor|Minutes}}

{{Anchor|Minutes}}

Line 20:

Line 22:

{{Anchor|MailingList}}

{{Anchor|MailingList}}

+

=== Discussions ===

=== Discussions ===

−

Discussion and decisions can also take place on the mailing list fedora-packaging@redhat.com. The mailing list is open to the public. To subscribe or view the archives, go to http://www.redhat.com/mailman/listinfo/fedora-packaging .

+

Discussion and decisions can also take place in the {{fplist|packaging}} mailing list. The mailing list is open to the public. To subscribe or view the archives, go to http://lists.fedoraproject.org/pipermail/packaging/.

{{Anchor|Members}}

{{Anchor|Members}}

+

== Members ==

== Members ==

+

* James Antill

* Tom Callaway (chair)

* Tom Callaway (chair)

+

* Jon Ciesla

* Ralf Corsepius

* Ralf Corsepius

* Rex Dieter

* Rex Dieter

−

* Hans de Goede

* Toshio Kuratomi

* Toshio Kuratomi

* Xavier Lamien

* Xavier Lamien

−

* Denis Leroy

* Dominik Mierzejewski

* Dominik Mierzejewski

* Jason Tibbitts

* Jason Tibbitts

Line 39:

Line 43:

== Agenda ==

== Agenda ==

−

The issues the committee is set to discuss are available at [[Packaging/GuidelinesTodo]].

+

The issues the committee is set to discuss are available in the [https://fedorahosted.org/fpc/report/3 fpc trac instance]

+

+

The old wiki page for tracking Guidelines for discussion and approval is here: [[Packaging/GuidelinesTodo]] but is no longer used. It's mentioned here in case someone wants to take over work on one of the old proposals.

{{Anchor|GuidelineChangeProcedure}}

{{Anchor|GuidelineChangeProcedure}}

Line 46:

Line 52:

=== Step One: Draft Guidelines ===

=== Step One: Draft Guidelines ===

−

All Fedora Packaging Guidelines changes start out as Draft documents. Any Fedora contributor may propose new or amended Packaging Guidelines. To create a new Draft, add a new page under [[PackagingDrafts]] on the wiki. Once you're happy with the Draft, add it to the [[PackagingDrafts/DraftsTodo | DraftsTodo table]] . Draft authors are highly encouraged to announce the draft on the fedora-packaging mailing list.

+

All Fedora Packaging Guidelines changes start out as Draft documents. Any Fedora contributor may propose new or amended Packaging Guidelines. To create a new Draft, add a new page on the wiki with the [[:Category:Packaging_guidelines_drafts|Packaging guidelines drafts]]. Once you're happy with the Draft, open a trac ticket on https://fedorahosted.org/fpc/ with a link to the draft. Draft authors are highly encouraged to announce the draft on the {{fplist|packaging}} mailing list.

=== Step Two: Packaging Committee Review ===

=== Step Two: Packaging Committee Review ===

−

The Packaging Committee will consider items on the [[PackagingDrafts/DraftsTodo | DraftsTodo]] in its weekly meetings and on the mailing list. The meetings and mailing list are open to the public, and Fedora contributors are invited and encouraged to participate (especially if you are a Draft author).

+

The Packaging Committee will consider items on the [https://fedorahosted.org/fpc/report/3 fpc trac instance] in its weekly meetings and on the mailing list. The meetings and mailing list are open to the public, and Fedora contributors are invited and encouraged to participate (especially if you are a Draft author).

=== Step Three: Packaging Committee Vote ===

=== Step Three: Packaging Committee Vote ===

The Packaging Committee votes on Drafts. A majority quorum is required for a Draft to be ratified by the FPC. Currently, five yes votes are required for Draft approval. Approved drafts are listed in the Action Items section of the [[Packaging/GuidelinesTodo | GuidelinesTodo table]] and marked "ratify".

The Packaging Committee votes on Drafts. A majority quorum is required for a Draft to be ratified by the FPC. Currently, five yes votes are required for Draft approval. Approved drafts are listed in the Action Items section of the [[Packaging/GuidelinesTodo | GuidelinesTodo table]] and marked "ratify".

−

=== Step Four: FESCo Ratification ===

+

=== Step Four: FESCo Ratification (optional) ===

−

FPC approved drafts are presented to the [[Development/SteeringCommittee | Fedora Steering Committee (aka FESCo)]] for final ratification. When [[Development/SteeringCommittee | FESCo]] approves drafts, the Action Items section of the [[Packaging/GuidelinesTodo | GuidelinesTodo table]] is updated, and the item is marked "writeup".

+

FPC approved drafts normally go into effect immediately after a positive vote. However, provision is made for any FPC member to request explicit FESCo review of the changes after the vote is taken. This allows things that are controversial to be explicitly reviewed by a second set of people before being pushed live. In this case, FESCo needs to review the decision and can either approve it or request changes be made before the draft goes live.

=== Step Five: Writeup ===

=== Step Five: Writeup ===

−

Once a draft is approved by [[Development/SteeringCommittee | FESCo]] , the Draft text is added to the Fedora Packaging Guidelines. The Draft item is then moved from the Action Items section of the [[Packaging/GuidelinesTodo | GuidelinesTodo table]] to the Resolved Items section.

+

Once a draft is approved, the Draft text is added to the Fedora Packaging Guidelines. The Draft wiki page may be moved to a new location in the <code>Packaging:</code> namespace or the information may be merged with existing Guideline pages and the draft page moved into archives. The fpc trac ticket is closed with information about where the new Guideline lives.

=== Step Six: Announcement ===

=== Step Six: Announcement ===

−

As the final step, the new Packaging Guidelines (or changes to the existing Guidelines) are announced on the fedora-maintainers and fedora-devel mailing lists.

+

As the final step, the new Packaging Guidelines (or changes to the existing Guidelines) are announced on the fedora-maintainers and {{fplist|devel}} mailing lists.

+

+

+

==== Ticket updates ====

+

In the interests of keeping the process moving for all contributors, please supply information requested by FPC members in your trac ticket in a timely manner. If outstanding information requested in a trac ticket is not provided within two weeks, the ticket may be closed due to inactivity.

Fedora Packaging Committee

Purpose

The FPC will no longer require FESCo ratification of approved drafts/changes, however, any FPC member who feels an approved draft/change would benefit from explicit FESCo review and ratification may request it.

Meetings and Discussions

Meetings

The Fedora Packaging Committee currently meets every Thursday at 16:00 UTC, in #fedora-meeting-1[?] on the freenode.net .

Agenda

The old wiki page for tracking Guidelines for discussion and approval is here: Packaging/GuidelinesTodo but is no longer used. It's mentioned here in case someone wants to take over work on one of the old proposals.

Guideline Change Procedure

How a Packaging Draft becomes a Fedora Packaging Guideline, in six easy steps!

Step One: Draft Guidelines

All Fedora Packaging Guidelines changes start out as Draft documents. Any Fedora contributor may propose new or amended Packaging Guidelines. To create a new Draft, add a new page on the wiki with the Packaging guidelines drafts. Once you're happy with the Draft, open a trac ticket on https://fedorahosted.org/fpc/ with a link to the draft. Draft authors are highly encouraged to announce the draft on the packaging mailing list.

Step Two: Packaging Committee Review

The Packaging Committee will consider items on the fpc trac instance in its weekly meetings and on the mailing list. The meetings and mailing list are open to the public, and Fedora contributors are invited and encouraged to participate (especially if you are a Draft author).

Step Three: Packaging Committee Vote

The Packaging Committee votes on Drafts. A majority quorum is required for a Draft to be ratified by the FPC. Currently, five yes votes are required for Draft approval. Approved drafts are listed in the Action Items section of the GuidelinesTodo table and marked "ratify".

Step Four: FESCo Ratification (optional)

FPC approved drafts normally go into effect immediately after a positive vote. However, provision is made for any FPC member to request explicit FESCo review of the changes after the vote is taken. This allows things that are controversial to be explicitly reviewed by a second set of people before being pushed live. In this case, FESCo needs to review the decision and can either approve it or request changes be made before the draft goes live.

Step Five: Writeup

Once a draft is approved, the Draft text is added to the Fedora Packaging Guidelines. The Draft wiki page may be moved to a new location in the Packaging: namespace or the information may be merged with existing Guideline pages and the draft page moved into archives. The fpc trac ticket is closed with information about where the new Guideline lives.

Step Six: Announcement

As the final step, the new Packaging Guidelines (or changes to the existing Guidelines) are announced on the fedora-maintainers and devel mailing lists.

Ticket updates

In the interests of keeping the process moving for all contributors, please supply information requested by FPC members in your trac ticket in a timely manner. If outstanding information requested in a trac ticket is not provided within two weeks, the ticket may be closed due to inactivity.