Font package lifecycle

Putting it all together.

The following is a quick summary to help newcomers undertand the Fonts SIG workflow.

Who are they?
Requester and Packager can be the same person. Reviewer must be different from the Packager.

A font package lifecycle

Phase	#	Who	Actions	Requirements
Conception	1	Requester	finds a nice font to package in Fedora, checks its licensing is acceptable, basically that: redistribution, including commercial is allowed, and modification, including of existing glyphs is allowed too Don't stop there This is a simplistic summary, do read our legal page before proposing new fonts. fills a packaging request in the wiki using the current template a complete and accurate request will increase packaging and adoption potential notifies the SIG mailing list of the new packaging request (optional but recommended)	a Fedora account, to edit the wiki (help), subscription to the main SIG list, to send the request notification.
Gestation	2.a	Packager	picks up a packaging request in the wishlist, corrects and completes the information the requester provided using the Packager notes in the template for guidance packages the fonts: using our spec template, following our official font packaging policies, uploads the result somewhere for example on his fedorapeople space, requests a review fills a ticked in bugzilla, CC-ing the bugs list, adds the review request reference to the original packaging request in the wiki, changes the packaging request category to Category:In-progress fonts. notifies the SIG mailing list of the new review request (optional but recommended).	the full joining the fonts SIG list, if the packager is not a cvsextras member yet, the way his membership request will be acted on depends on the quality of the new package he proposes. Font packages are normal packages Most packaging steps are detailed on the general new fedora packager page.
	2.b	Reviewer	makes sure the steps outlined in previous phases have been completed including 1 if the packager is also the initial font requester reviews the package ask the requester fix eventual problems	membership of the fedorabugs group. good knowledge of font packaging policies, general Fedora reviewer requirements.
	2.c	Packager	acts on reviewer requests
	2.d	Reviewer	checks the fixes approves the package
Birth	3.a	Packager	publishes his package in the fedora-devel branch, then in other branches (stable release, EPEL branch, etc) completes the distribution comps files adds the koji and pkgdb references to the original wiki packaging request changes its category to Category:Packaged fonts notifies the SIG mailing list of the new package (optional but recommended)
	3.b	Requester	thanks the packager publicly. Small things count too.
Life	4.a	Packager	monitors new upstream releases, new fedora bugs, updates his package in fedora-devel accordingly, pushes the updates to other Fedora branches when they're worth it Be conservative Users to not like continuous updates for small changes. Update in fedora-devel (rawhide) early and often. Think twice before pushing changes to other branches.	Don't leave now Please avoid fire and forget packaging.
	4.b	Users	report new issues in Bugzilla	a bugzilla account Bugzilla is required Packagers are not psychic, they don't monitor the whole web for problems, if you want them to address yours, please use our bugzilla.
Death	5	Fedora QA	A change in Fedora policies or a problem missed earlier may cause a font package to be retired.

Fonts in Fedora
The Fonts SIG takes loving care of Fedora fonts. Please join this special interest group if you are interested in creating, improving, packaging, or just suggesting a font. Any help will be appreciated.