From 969f7647c57f08ed7a151083c2fc9aef27336389 Mon Sep 17 00:00:00 2001 From: Otto Urpelainen Date: Nov 18 2021 20:48:26 +0000 Subject: Discuss unorphaning as a way of getting sponsored Orphaning of a package is naturally a moment where a new contributor can join Fedora package maintenance: There is obviously a vacancy for maintaining that package. The topic also regularly comes up on devel when potential packagers ask if and how they could adopt an orpahed package. Add discussion of this route to the How to Get Sponsored page, so that newcomers can be directed to instructions. --- diff --git a/modules/ROOT/pages/How_to_Get_Sponsored_into_the_Packager_Group.adoc b/modules/ROOT/pages/How_to_Get_Sponsored_into_the_Packager_Group.adoc index dc5748e..e56c650 100644 --- a/modules/ROOT/pages/How_to_Get_Sponsored_into_the_Packager_Group.adoc +++ b/modules/ROOT/pages/How_to_Get_Sponsored_into_the_Packager_Group.adoc @@ -23,6 +23,18 @@ with some aspects of packaging and the submission process but will expect you to read about the process and https://docs.fedoraproject.org/en-US/packaging-guidelines/[guidelines for packages] for a large amount of your understanding of how things work. +[#requesting_sponsorship] +== Requesting sponsorship + +There are two ways of requesting sponsorship: + +. If you are submitting a new package for review in Bugzilla, +you can make the review request block the +https://bugzilla.redhat.com/show_bug.cgi?id=FE-NEEDSPONSOR[FE-NEEDSPONSOR] tracking bug. + +. Otherwise, you can file a ticket in the +https://pagure.io/packager-sponsors/[sponsors ticketing system]. + [#convincing_someone_to_sponsor_you] == Convincing someone to sponsor you @@ -93,11 +105,11 @@ Basically, the more information that you make available, the quicker you will find a sponsor. -If you have accepted packagesand still have not managed to find a sponsor, +If you have accepted packages and still have not managed to find a sponsor, feel free to file a ticket in the https://pagure.io/packager-sponsors/[sponsors ticketing system]. -[#show_your_expertise_by_commenting_on_other_review_requests] -=== Show Your Expertise by Commenting on other Review Requests +[#commenting_on_other_review_requests] +=== Commenting on other Review Requests To show you familiarity with Fedora's guidelines, perform unofficial (also called preliminary) reviews @@ -125,10 +137,10 @@ for review requests to comment on. If you want to work on review requests that nobody else officially reviews, see the http://fedoraproject.org/PackageReviewStatus/reviewable.html[list of unassigned review requests]. -[#show_your_expertise_by_opening_pull_requests] -=== Show Your Expertise by Opening Pull Requests +[#opening_pull_requests] +=== Opening Pull Requests -The https://pagure.io[Pagure] based https://src.fedoraproject.org[src.fedoraproject.org] system +The https://src.fedoraproject.org[Package Sources] site allows you to Fork, modify, and open Pull Requests for packages even if you are not yet part of the package maintainer's group. This is an excellent way to help other package maintainers, @@ -140,7 +152,7 @@ and get you sponsored. More on that in the next section. [#become_a_co_maintainer] -=== Become a co-maintainer +=== Becoming a co-maintainer Another way to enter the `packager` group is by co-maintaining a package that is already in Fedora. @@ -175,6 +187,43 @@ since they are not sponsors themselves. A sponsor will add you to the `packager` group once that agreement for mentorship exists. +[#adopting_orphaned_packages] +=== Adopting orphaned packages + +Adopting a package that has been xref:Package_Orphaning_Process.adoc[orpahaned] +is a good way to become a packager. + +Notifications about orphaned packages are sent to the +https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/[devel] mailing list. +If you notice an orphaned package that you are willing to maintain, +post to devel, +explaining that you are not in the packager group yet, +but that after you have completed the sponsoring process, +you are interested in adopting or co-maintaining the package. +The kind of replies you may get include: + +* A warning to reconsider this plan, +due to serious problems with the package. + +* A note that the package has already been adopted, +possibly with an invitation to contribute in its maintenance +(which itself may lead to eventual sponsoring through the co-maintenance route.) + +* An offer to help with the process, +perhaps from the previous maintainer or a potential sponsor. + +Then do what you consider to be enough for +xref:convincing_someone_to_sponsor_you[Convincing someone to sponsor you] +and submit a ticket +to the https://pagure.io/packager-sponsors/[sponsors ticketing system]. +Creating a pull request on the orphaned package is a good start: +Orphaned packages are commonly behind in updates, +fail to build from source +or have other issues, +so very likely there is something to fix there, +and when you become the maintainer, +you have to fix the package anyhow. + [#other_paths] === Other paths