Fedora

Font package lifecycle

From FedoraProject

Revision as of 19:46, 27 June 2008 (view source) Nim (Talk | contribs) ← Older edit		Revision as of 11:02, 6 July 2008 (view source) Nim (Talk | contribs) Newer edit →
Line 13:		Line 13:
	|-		|-
	! Phase		! Phase
		+	! #
	! Who		! Who
	! Actions		! Actions
Line 18:		Line 19:
	|-		|-
	| [[:Category:Font_wishlist|Conception]]		| [[:Category:Font_wishlist|Conception]]
		+	| 1
	| Requester		| Requester
	|		|
Line 34:		Line 36:
	|-		|-
	| rowspan="2" | [[:Category:In-progress fonts|Gestation]]		| rowspan="2" | [[:Category:In-progress fonts|Gestation]]
		+	| 2.a
	| Packager		| Packager
	|		|
Line 57:		Line 60:
	Most packaging steps are detailed on the general [[PackageMaintainers/Join|new fedora packager]] page.}}		Most packaging steps are detailed on the general [[PackageMaintainers/Join|new fedora packager]] page.}}
	|-		|-
		+	| 2.b
	| Reviewer		| Reviewer
	|		|
Line 67:		Line 71:
	|-		|-
	| rowspan="2" | Birth		| rowspan="2" | Birth
		+	| 3.a
	| Packager		| Packager
	| colspan="2" |		| colspan="2" |
Line 75:		Line 80:
	* notifies the SIG mailing list of the new package (optional but recommended)		* notifies the SIG mailing list of the new package (optional but recommended)
	|-		|-
		+	| 3.b
	| Requester		| Requester
	| colspan="2" |		| colspan="2" |
Line 81:		Line 87:
	|-		|-
	| rowspan="2" | [[:Category:Packaged fonts|Life]]		| rowspan="2" | [[:Category:Packaged fonts|Life]]
		+	| 4.a
	| Packager		| Packager
	|		|
Line 92:		Line 99:
	Please avoid fire and forget packaging.}}		Please avoid fire and forget packaging.}}
	|-		|-
		+	| 4.b
	| Users		| Users
	|		|
Line 101:		Line 109:
	|-		|-
	| [[:Rejected and retired fonts|Death]]		| [[:Rejected and retired fonts|Death]]
		+	| 5
	| Fedora QA		| Fedora QA
	| colspan="2" | A change in Fedora policies or a problem missed earlier may cause a font package to be retired.		| colspan="2" | A change in Fedora policies or a problem missed earlier may cause a font package to be retired.

---

Revision as of 11:02, 6 July 2008

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	reviews the package makes the requester fix eventual problems approves the package	good knowledge of font packaging policies, general Fedora reviewer requirements.
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.

Copyright © 2013 Red Hat, Inc. and others. All Rights Reserved. For comments or queries, please contact us.

The Fedora Project is maintained and driven by the community and sponsored by Red Hat. This is a community maintained site. Red Hat is not responsible for content.

• Content is available under Attribution-Share Alike 3.0 Unported.

• Privacy policy
• About FedoraProject
• Disclaimers
• Sponsors
• Legal
• Trademark Guidelines