From 780fd2083e30f8c8e1a49fcd9a29c7e9d4edc0a1 Mon Sep 17 00:00:00 2001 From: Zbigniew Jędrzejewski-Szmek Date: Jun 17 2024 19:54:48 +0000 Subject: provenpackagers: use semantic line breaks and adjust formatting No semantic changes. --- diff --git a/fesco/modules/ROOT/pages/Provenpackager_policy.adoc b/fesco/modules/ROOT/pages/Provenpackager_policy.adoc index d6c9429..20fabfb 100644 --- a/fesco/modules/ROOT/pages/Provenpackager_policy.adoc +++ b/fesco/modules/ROOT/pages/Provenpackager_policy.adoc @@ -1,20 +1,27 @@ = Policy for provenpackagers -Provenpackagers are members of the 'provenpackager' group. In addition to the rights granted to members of 'packager', provenpackagers are able to commit changes to packages they do not own or maintain. They are a group of skilled package maintainers who are experienced in a wide variety of package types and who are familiar with the link:https://docs.fedoraproject.org/en-US/packaging-guidelines/[packaging guidelines] and xref:Package_maintainer_responsibilities.adoc[package maintainer policies], as well as acutely aware of link:https://fedoraproject.org/wiki/Releases/Schedule[release schedule] and link:https://fedoraproject.org/wiki/ReleaseEngineering#Freeze_Policies[freeze policies]. +Provenpackagers are members of the `provenpackager` group. +In addition to the rights granted to members of `packager`, +provenpackagers are able to commit changes to packages they do not own or maintain. +They are a group of skilled package maintainers who are experienced in a wide variety of package types +and who are familiar with the link:https://docs.fedoraproject.org/en-US/packaging-guidelines/[packaging guidelines] +and xref:Package_maintainer_responsibilities.adoc[package maintainer policies], +as well as acutely aware of link:https://fedoraproject.org/wiki/Releases/Schedule[release schedule] +and link:https://fedoraproject.org/wiki/ReleaseEngineering#Freeze_Policies[freeze policies]. Provenpackagers lend a hand when help is needed, always with a desire to improve the quality of Fedora. Prior to making changes, provenpackagers should try to communicate with owners of a package -in bugzilla, dist-git pull request, IRC, matrix, or email. +in bugzilla, dist-git pull requests, IRC, matrix, or email. They should be careful not to change other people's packages needlessly and try to do the minimal changes required to fix problems, -as explained more in depth in xref:Who_is_allowed_to_modify_which_packages.adoc[Who is Allowed to Modify Which Packages]. +as explained more in depth in +xref:Who_is_allowed_to_modify_which_packages.adoc[Who is Allowed to Modify Which Packages]. To exclude a package from provenpackagers access, you have to open a ticket at link:https://pagure.io/fesco/new_issue[FESCo issue tracker] and explain why provenpackagers should not have access to it. -xref:index.adoc[FESCo] will discuss about and vote on your request -in one of its weekly meetings. +xref:index.adoc[FESCo] will discuss about and vote on your request in one of its weekly meetings. == Becoming provenpackager @@ -28,6 +35,9 @@ To become a member of the 'provenpackager' group, the procedure is the following == Maintaining provenpackager status -Around the branch day in each release cycle, the Fedora Program Manager will audit the membership of the 'provenpackager' group. -Members of the group who have not submitted a koji build in the last six months will be contacted via their @fedoraproject.org email address to verify that they should remain in the provenpackager group. -If they do not acknowledge within two weeks, they will be removed from the provenpackager group. +Around the branch day in each release cycle, +the Fedora Program Manager will audit the membership of the `provenpackager` group. +Members of the group who have not submitted a koji build in the last six months +will be contacted via their `@fedoraproject.org` email address +to verify that they should remain in the the group. +If they do not acknowledge within two weeks, they will be removed from the `provenpackager` group.