From 89e30742e38b59e57cada35da72cb6dd5d4823af Mon Sep 17 00:00:00 2001 From: Otto Urpelainen Date: Sep 29 2021 18:34:46 +0000 Subject: Link to docs.fp.o instead of wiki Package Maintainer Docs have moved from wiki to docs.fedoraproject.org. Update links to point to the new location. Packaging Guidelines have been on docs.fp.o for a long time already. Update links to them, too. --- diff --git a/fesco/modules/ROOT/pages/Bundled_Software_policy.adoc b/fesco/modules/ROOT/pages/Bundled_Software_policy.adoc index 2a0e65f..f218c65 100644 --- a/fesco/modules/ROOT/pages/Bundled_Software_policy.adoc +++ b/fesco/modules/ROOT/pages/Bundled_Software_policy.adoc @@ -10,7 +10,7 @@ All packages whose upstreams have no mechanism to build against system libraries All packages whose upstreams have no mechanism to build against system libraries may opt to carry bundled libraries, but if they do, they must include `Provides: bundled() =` in their RPM spec file. The FPC will maintain the list of bundled provides, please consult with them when adding new provides or in case of disputes. -Packages that bundle libraries must follow the link:https://fedoraproject.org/wiki/Packaging:AutoProvidesAndRequiresFiltering#Private_Libraries[AutoProvides filtering guidelines] for private libraries. +Packages that bundle libraries must follow the link:https://docs.fedoraproject.org/en-US/packaging-guidelines/AutoProvidesAndRequiresFiltering/#_private_libraries[AutoProvides filtering guidelines for private libraries]. == References diff --git a/fesco/modules/ROOT/pages/Package_maintainer_responsibilities.adoc b/fesco/modules/ROOT/pages/Package_maintainer_responsibilities.adoc index bca2271..1fb49b8 100644 --- a/fesco/modules/ROOT/pages/Package_maintainer_responsibilities.adoc +++ b/fesco/modules/ROOT/pages/Package_maintainer_responsibilities.adoc @@ -2,7 +2,7 @@ :experimental: :toc: -link:https://fedoraproject.org/wiki/Category:Package_Maintainers[Package maintainers] take care of the packages in Fedora. +link:https://docs.fedoraproject.org/en-US/package-maintainers/[Package maintainers] take care of the packages in Fedora. This includes both the packaging of upstream software into Fedora rpms and working with upstream to improve the software in various ways. == How long to maintain? @@ -34,7 +34,7 @@ This can include: * Get an account on upstream bug trackers. * Forward severe bugs upstream when possible for assistance. -Refer to link:https://fedoraproject.org/wiki/Staying_close_to_upstream_projects[staying close to upstream projects] for more information on this. +Refer to link:https://docs.fedoraproject.org/en-US/package-maintainers/Staying_Close_to_Upstream_Projects/[Staying Close to Upstream Projects] for more information on this. == Work with Testing @@ -73,8 +73,8 @@ So do be available to answer questions that the co-maintainers may have and also Watching over the changes to your package also goes for changes made by people who are not explicit co-maintainers if you have opened your package for any packager to commit to. -You can also take on co-maintainers that are not yet sponsored into the packager group provided that you agree to mentor them in the ways of packaging for Fedora: teaching them both about the tools we use and the link:https://fedoraproject.org/wiki/Packaging:Guidelines[ packaging guidelines] they need to follow. -See the link:https://fedoraproject.org/wiki/How_to_get_sponsored_into_the_packager_group#Become_a_comaintainer[ How to get sponsored page] for details on getting a new packager sponsored if you are not a sponsor yourself. +You can also take on co-maintainers that are not yet sponsored into the packager group provided that you agree to mentor them in the ways of packaging for Fedora: teaching them both about the tools we use and the link:https://docs.fedoraproject.org/en-US/packaging-guidelines/[packaging guidelines] they need to follow. +See the link:https://docs.fedoraproject.org/en-US/package-maintainers/How_to_Get_Sponsored_into_the_Packager_Group/#become_a_co_maintainer[How to Get Sponsored page] for details on getting a new packager sponsored if you are not a sponsor yourself. == Track dependency issues in a timely manner diff --git a/fesco/modules/ROOT/pages/Packager_sponsor_responsibilities.adoc b/fesco/modules/ROOT/pages/Packager_sponsor_responsibilities.adoc index 1dec926..5837bc2 100644 --- a/fesco/modules/ROOT/pages/Packager_sponsor_responsibilities.adoc +++ b/fesco/modules/ROOT/pages/Packager_sponsor_responsibilities.adoc @@ -8,7 +8,7 @@ The following is an outline of some of the expectations of what a sponsor should Packager sponsors should be available to their sponsored maintainers to answer questions. It's up to the sponsor if they wish to be available via IRC, email, bugzilla, mailing list posts, phone or the like. In the event a sponsor is unable to answer a question, they should escalate it to the appropriate mailing list, xref:index.adoc[FESCo], link:https://docs.fedoraproject.org/en-US/council/[Fedora Council] or the like and get an answer passed back. -Questions sponsors should answer in particular are all the questions related with practical aspects of Fedora (link:https://fedoraproject.org/wiki/Packaging:Guidelines[Packaging Guidelines], link:https://fedoraproject.org/wiki/Using_the_Koji_build_system[Build system], link:https://fedoraproject.org/wiki/Package_maintenance_guide[VCS], FAS, updates...). +Questions sponsors should answer in particular are all the questions related with practical aspects of Fedora (link:https://docs.fedoraproject.org/en-US/packaging-guidelines/[Packaging Guidelines], link:https://docs.fedoraproject.org/en-US/package-maintainers/Using_the_Koji_Build_System/[Build system], link:https://docs.fedoraproject.org/en-US/package-maintainers/Package_Maintenance_Guide/[VCS], FAS, updates...). == Guide the sponsored maintainer in the Fedora Project @@ -34,4 +34,4 @@ Sponsorship of a maintainer ends when that sponsorship is revoked or when that m == Who Sponsors the Sponsors? -Once a maintainer has been granted sponsorship status (via a vote of existing sponsors), that Sponsor will be held accountable by FESCO and not their previous Sponsor. link:https://fedoraproject.org/wiki/How_to_sponsor_a_new_contributor#Becoming_a_Fedora_Package_Collection_Sponsor[More on becoming a sponsor]. +Once a maintainer has been granted sponsorship status (via a vote of existing sponsors), that Sponsor will be held accountable by FESCO and not their previous Sponsor. link:https://docs.fedoraproject.org/en-US/package-maintainers/How_to_Sponsor_a_New_Contributor/#becoming_a_fedora_package_collection_sponsor[More on becoming a sponsor]. diff --git a/fesco/modules/ROOT/pages/Policy_for_nonresponsive_package_maintainers.adoc b/fesco/modules/ROOT/pages/Policy_for_nonresponsive_package_maintainers.adoc index 258e339..8849373 100644 --- a/fesco/modules/ROOT/pages/Policy_for_nonresponsive_package_maintainers.adoc +++ b/fesco/modules/ROOT/pages/Policy_for_nonresponsive_package_maintainers.adoc @@ -15,10 +15,10 @@ reduce open bugs on non-maintained packages, and increase the overall quality of This policy covers existing Fedora packages, containers, and modules; for non-responsive package submitters or reviewers, see the -link:https://fedoraproject.org/wiki/Policy_for_stalled_package_reviews[Policy for stalled package reviews]. +xref:Package_review_policy.adoc#stalled[Policy for stalled package reviews]. If you are a *not* an existing Fedora contributor, you can follow this procedure too. If you want to take over maintainership, you must find a sponsor following the rules specified in -link:https://fedoraproject.org/wiki/How_to_get_sponsored_into_the_packager_group[How to get sponsored into the packager group]. +link:https://docs.fedoraproject.org/en-US/package-maintainers/How_to_Get_Sponsored_into_the_Packager_Group/[How to get sponsored into the packager group]. [[steps]] == Steps diff --git a/fesco/modules/ROOT/pages/Provenpackager_policy.adoc b/fesco/modules/ROOT/pages/Provenpackager_policy.adoc index 32fc221..6a3367c 100644 --- a/fesco/modules/ROOT/pages/Provenpackager_policy.adoc +++ b/fesco/modules/ROOT/pages/Provenpackager_policy.adoc @@ -1,6 +1,6 @@ = 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://fedoraproject.org/wiki/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.