Extras/NewPackageProcessMarkTwo

Redirect to:

• New package process for existing contributors

Goals of the New Package Process

1. Simplicity. 1. Trackability.

Who Does Stuff?

1. SUBMITTER. This is the lucky soul looking to get a package into Extras. 1. REVIEWER. This is the person who chooses to review the package. For the sake of clarity, one person takes ownership of the review. Other people are encouraged to comment on the review as well, either in the bug or on the mailing list. The primary REVIEWER can be any current package owner, unless the SUBMITTER is a first timer. a. If you wish to be a REVIEWER, make sure you have the proper permissions on your Fedora account. Follow the steps below. a. Go to: https://admin.fedora.redhat.com/accounts/ a. Click the "Edit your account" link a. Go to the "Add new membership" section and fill out the fields as follows a. Groupname: fedorabugs a. Role type: user a. Role domain: -empty- 1. SPONSOR. If the SUBMITTER is a first-timer, then the REVIEWER must also be an officially designated SPONSOR. The list of official SPONSORs can be found here .

New Package Process

1. MAKE THE PACKAGE. Performed by SUBMITTER. The SUBMITTER should already have a package that builds properly on a local system. The package should adhere to the Package Naming Guidelines and Packaging Guidelines . Also be aware of ForbiddenItems.

1. BUGZILLA SUBMISSION. Performed by SUBMITTER. Fill out this form , replacing FIXMEs appropriately. One package per request. SUBMITTER must create a bugzilla account if one does not already exist. If SUBMITTER is a first-timer, this is also the time to request Fedora Extras CVS account creation in the account system .

1. ACCEPTANCE FOR REVIEW. Performed by REVIEWER. If the packager is a first-timer, the person accepting the package for review must also be a SPONSOR. REVIEWER must: a. Change the blocking bug from FE-NEW to FE-REVIEW. a. Assign the bug to self.

1. PACKAGE REVIEW. Performed by REVIEWER. REVIEWER reviews the package according to the Package Naming Guidelines and Packaging Guidelines and takes one of the following actions: a. ACCEPT. If the package is good, change the blocker bug from FE-REVIEW to FE-ACCEPT. If REVIEWER is also acting as SPONSOR, then this is the time to promote the SUBMITTER in the account system . a. FAIL, LEGAL. If the package is legally risky for whatever reason (known patent or copyright infringement, trademark concerns) close the bug WONTFIX and leave an appropriate comment (i.e. we don't ship mp3, so stop submitting it). a. FAIL, OTHER. If the package is just way off or unsuitable for some other reason, and there is no simple fix, then close the bug WONTFIX and leave an appropriate comment (i.e. we don't package pornography for redistribution, sorry. Or, this isn't a specfile, it's a McDonald's menu, sorry.)

a. REWORK. Anything that isn't explicitly failed should be left open while the submitter and reviewer work together to fix any potential issues. 1. PACKAGE COMPLETION. Performed by SUBMITTER. SUBMITTER, having completed his/her mission, is now a full-fledged package owner and must now perform the final steps: a. Check the new package into CVS. a. Request a build . a. When the package is building properly, close the bug NEXTRELEASE. a. Check out "owners" module in CVS and edit "owners.list" file to create a bugzilla component for the package.

Tracking of package requests

• FE-NEW (New Review Requests)
• FE-REVIEW (Packages Currently Under Review)
• FE-ACCEPT (Packages Accepted, Implementation Pending)

---