< PackageMaintainersRedirect page
This content has been merged in Category:Package_Maintainers
Resources for Fedora Package Collection contributors
- New package process for existing contributors (shorter variant of Join the package collection maintainers ).
- How to review packages, or have a package reviewed
- Package maintainer responsibilities
- Package sponsor responsibities
- Package maintainer policy
- Package update guidelines
- Package update HOWTO
- How to remove a package at end of life - How to remove a package from Fedora Package Collection when it's no longer useful (project renamed upstream, inactive upstream projects, etc)
- SIGs - Fedora Special Interest Groups
- How to use and edit comps.xml for package groups - How to use and edit comps.xml (used for package groups)
- Fedora package components in bugzilla
- Tracking upstream projects - Various tips on tracking upstream projects to coordinate effectively for packagers
- Tracking downstream packages - Tips on how to track which packages are using your package
- Using Mock to test package builds - Using Mock to test build your packages
- Scripts for package maintainers - Handy scripts for Fedora packagers.
- Using CVS FAQ for package maintainers - FAQ about using the Fedora Package CVS
- Using the Koji build system - A guide to using Koji, the build system for F-7 and later.
- Using the package database - How to use the Package Database to manage ownership of a package.
- How to sponsor a new contributor - Guide for sponsors, who can approve new contributors.
- Staying close to upstream projects - Best practice guidelines on avoiding deviations from upstream projects.
- Package status - Summary of Fedora package status reports
- Packaging tricks - assorted packaging tricks (some are controversial, so do not take these as official.)
- Common Rpmlint issues - Summary of the rpmlint output and hints to make rpmlint quiet.
- Vacation Notice - Add a vacation note if you are going to be unavailable for a few days.