(New page: This document is an outline of the duties of an entity within the Fedora project overseeing the care of packagers and packages within the distribution. * I believe this entity should be F...) |
No edit summary |
||
Line 9: | Line 9: | ||
== The packager process == | == The packager process == | ||
New packagers must go through a somewhat arduous process over and above the difficulty of learning how to actually package software. Some of this (such as the new account and CLA process) is beyond the scope of packager care and has gotten much easier lately, but we still have | |||
Note: I'm assuming that the recently-approved maintainer containment procedure is in place. | |||
=== Initial review and sponsorship === | === Initial review and sponsorship === | ||
Elevation to supergroup | Users basically have to post a package somewhere, and create a review ticket. They have to manually set up things like the NEEDSPONSOR blocker. | ||
This breaks down because | |||
=== Elevation to supergroup === | |||
=== Elevation to sponsor === | |||
=== General issues === | |||
== The package process == | |||
=== Review === | |||
=== Checkin === | |||
=== Post review === | |||
Maintenance | |||
Rebuilds | |||
Periodic re-review |
Revision as of 23:24, 9 June 2008
This document is an outline of the duties of an entity within the Fedora project overseeing the care of packagers and packages within the distribution.
- I believe this entity should be FESCo. If it is affirmed that FESCo should handle this, I intend to stand for election. If it is decided to assign these duties to a separate committee, I'd like to be on it.
- I place "Packager" before "Package" because while the distribution is composed of Packages, they don't maintain themselves. Without packagers, there is little to actually distribute.
- Both packagers and packages are covered because both need attention and while
- This is a brainstorm of both what I think the committee should handle and various ideas I'd like it to pursue.
The packager process
New packagers must go through a somewhat arduous process over and above the difficulty of learning how to actually package software. Some of this (such as the new account and CLA process) is beyond the scope of packager care and has gotten much easier lately, but we still have
Note: I'm assuming that the recently-approved maintainer containment procedure is in place.
Initial review and sponsorship
Users basically have to post a package somewhere, and create a review ticket. They have to manually set up things like the NEEDSPONSOR blocker.
This breaks down because
Elevation to supergroup
Elevation to sponsor
General issues
The package process
Review
Checkin
Post review
Maintenance Rebuilds Periodic re-review