From Fedora Project Wiki

No edit summary
(Redirect Package Maintainer wiki links to docs.fp.o)
 
(12 intermediate revisions by 6 users not shown)
Line 9: Line 9:




{|
{|class="wikimedia sortable" style="t1" rowclass="th" border="1"
|+ A font package lifecycle
|+ A font package lifecycle
|-
|-
Line 28: Line 28:
{{Admon/caution | Don't stop there |
{{Admon/caution | Don't stop there |
This is a simplistic summary, '''do''' read our [[Legal_considerations_for_fonts| legal page]] before proposing new fonts.}}
This is a simplistic summary, '''do''' read our [[Legal_considerations_for_fonts| legal page]] before proposing new fonts.}}
* fills a packaging request in the wiki using the current [[Font_description_template|template]]
* fills a [[:Category:Font wishlist|packaging request]] in the wiki using the current [[Font_description_template|template]]
** a complete and accurate request will increase packaging and adoption potential
** a complete and accurate request will increase packaging and adoption potential
* notifies the SIG [[Fonts_SIG_mailing_lists | mailing list]] of the new packaging request (optional but recommended)
* notifies the SIG [[Fonts_SIG_mailing_lists | mailing list]] of the new packaging request (optional but recommended)
Line 43: Line 43:
** using the ''Packager'' notes in the [[Font_description_template|template]] for guidance
** using the ''Packager'' notes in the [[Font_description_template|template]] for guidance
* packages the fonts:
* packages the fonts:
** using our [[Annotated_fonts_spec_template|spec template]],
** following our official [[:Category:Fonts_packaging| font packaging policies]],
** following our official [[:Category:Fonts_packaging| font packaging policies]],
* uploads the result somewhere
** using our fonts spec templates ([[Simple fonts spec template|1]],[[Fonts spec template for multiple_fonts|2]]),
# dnf install fontpackages-devel
* self-checks the result:
** builds the package in [[Projects/Mock|Mock]] or (if he's already a packager) in a [[Koji]] scratch build
** checks the resulting packages with [[Common_Rpmlint_issues|rpmlint]]
# dnf install rpmlint
$ rpmlint package1.rpm … packageN.rpm
** checks the resulting packages with repo-font-audit:
# dnf install fontpackages-tools createrepo
$ mkdir /tmp/testrepo
$ mv package1.rpm … packageN.rpm /tmp/testrepo
$ createrepo /tmp/testrepo
$ repo-font-audit testrepo file:///tmp/testrepo
* uploads the fixed packages somewhere
** for example on his [http://fedorapeople.org/ fedorapeople] space,
** for example on his [http://fedorapeople.org/ fedorapeople] space,
* requests a review
* requests a review
** fills a ticked in [https://bugzilla.redhat.com/bugzilla/enter_bug.cgi?product=Fedora&format=extras-review bugzilla], CC-ing the [[Fonts_SIG_mailing_lists | bugs list]],
** fills a ticked in [https://bugzilla.redhat.com/bugzilla/enter_bug.cgi?product=Fedora&format=fedora-review bugzilla], CC-ing the [[Fonts_SIG_mailing_lists | bugs list]],
** adds the review request reference to the original packaging request in the wiki,
** adds the review request reference to the original packaging request in the wiki,
** changes the packaging request category to [[:Category:In-progress fonts]].
** changes the packaging request category to [[:Category:In-progress fonts]].
Line 54: Line 66:
|
|
* the full [[Joining_the_Fonts_SIG|joining the fonts SIG]] list,
* the full [[Joining_the_Fonts_SIG|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.
* if the packager is not a ''packager'' member yet, the way his membership request will be acted on depends on the quality of the new package he proposes.




Line 64: Line 76:
|
|
* makes sure the steps outlined in previous phases have been completed, [[#1|1]] included
* makes sure the steps outlined in previous phases have been completed, [[#1|1]] included
* [[Package_Review_Process|reviews]] the package
* [https://docs.fedoraproject.org/en-US/package-maintainers/Package_Review_Process/ reviews] the package
* ask the requester fix eventual problems
* ask the requester fix eventual problems
|
|
* membership of the [https://admin.fedoraproject.org/accounts/group/view/fedorabugs fedorabugs] group.
* membership of the [https://admin.fedoraproject.org/accounts/group/view/fedorabugs fedorabugs] group.
* good knowledge of [[:Category:Fonts_packaging| font packaging policies]],
* good knowledge of [[:Category:Fonts_packaging| font packaging policies]],
* general Fedora [[Package_Review_Process#Reviewer| reviewer]] requirements.
* general Fedora [https://docs.fedoraproject.org/en-US/package-maintainers/Package_Review_Process/#_reviewer  reviewer] requirements.
|- valign="top"
|- valign="top"
| {{Anchor|2.c}}[[#2.c|2.c]]
| {{Anchor|2.c}}[[#2.c|2.c]]
Line 86: Line 98:
| Packager
| Packager
| colspan="2" |
| colspan="2" |
* requests a [[PackageMaintainers/CVSAdminProcedure|VCS root]] for his package, declaring the [[pkgdbu:fonts-sig|fonts-sig]] user in the default CC list.
* requests a [[Package SCM admin requests|VCS root]] for his package, declaring the [[pkgdbu:fonts-sig|fonts-sig]] user in the default CC list.
* [[PackageMaintainers/Join#Check_out_the_module|publishes]] his package in the fedora-devel branch, then in other branches (stable release, EPEL branch, etc)
* [[PackageMaintainers/Join#Check_out_the_module|publishes]] his package in the fedora-devel branch, then in other branches (stable release, EPEL branch, etc)
* completes the distribution [[PackageMaintainers/CompsXml#Fonts | comps files]]
* completes the distribution [[PackageMaintainers/CompsXml#Fonts | comps files]]
Line 92: Line 104:
* changes its category to [[:Category:Packaged fonts]]
* changes its category to [[:Category:Packaged fonts]]
* notifies the SIG mailing list of the new package (optional but recommended)
* notifies the SIG mailing list of the new package (optional but recommended)
* notifies the font upstream its font has been packaged in Fedora (optional but recommended)
|- valign="top"
|- valign="top"
| {{Anchor|3.b}}[[#3.b|3.b]]
| {{Anchor|3.b}}[[#3.b|3.b]]
Line 126: Line 139:
|}
|}


{{:Fonts_SIG_signature}} [[Category:Fonts and text QA|Lifecycle, font packages]]
{{:Fonts_SIG_signature}} [[Category:Fonts packaging|Lifecycle, font packages]]

Latest revision as of 11:11, 9 October 2021

A page of the Fonts Special Interest Group

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)
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:
# dnf install fontpackages-devel
  • self-checks the result:
    • builds the package in Mock or (if he's already a packager) in a Koji scratch build
    • checks the resulting packages with rpmlint
# dnf install rpmlint
$ rpmlint package1.rpm … packageN.rpm
    • checks the resulting packages with repo-font-audit:
# dnf install fontpackages-tools createrepo
$ mkdir /tmp/testrepo
$ mv package1.rpm … packageN.rpm /tmp/testrepo
$ createrepo /tmp/testrepo
$ repo-font-audit testrepo file:///tmp/testrepo
  • uploads the fixed packages somewhere
  • requests a review
  • 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 packager 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, 1 included
  • reviews the package
  • ask the requester fix eventual problems
2.c Packager
  • acts on reviewer requests
2.d Reviewer
  • checks the fixes
  • approves the package
Birth 3.a Packager
  • requests a VCS root for his package, declaring the fonts-sig user in the default CC list.
  • 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)
  • notifies the font upstream its font has been packaged in Fedora (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
  • 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.