From 62cb3d57436446d62c3119a39e8f415f496cc94b Mon Sep 17 00:00:00 2001 From: Otto Urpelainen Date: May 24 2022 11:56:55 +0000 Subject: Simplify How to Get Sponsored page Fesco docs have a new, updated Packager Sponsor Policy which contains the policy aspects of the sponsorship process. Thus, there is no need to repeat the same information here. Everything that just duplicates the Fesco policy is removed, and only additional material that does not fit into the policy itself, such as practical tips, it kept. --- 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 bceba0f..6483dfc 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 @@ -1,198 +1,16 @@ = How to Get Sponsored into the Packager Group -[#sponsorship_model] -== Sponsorship model +xref:fesco::Packager_sponsor_policy.adoc[Packager sponsor policy] +governs sponsorship for the _packager_ group. +This page contains some additional tips that are not part of the policy. -Getting sponsored allows anyone interested to become a Fedora maintainer -and get direct commit and upload access to their proposed software packages. -We require people to get sponsored into the `packager` group -before getting this access to Fedora -to ensure that they have someone that they can go to with questions. -Sponsorship is *not* automatic -and requires that you find a willing sponsor. -Depending on the sponsor and how much time they have to spend with you, -they may require that you demonstrate -that you have the knowledge to maintain Fedora packages properly -(including an understanding of the Fedora packaging guidelines) -or they may be willing to take you on -if you just show that you are eager and willing -to learn those things from them. -A sponsor will assist you -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. +[#discovering] +== Discovering packages that need maintenance -[#requesting_sponsorship] -== Requesting sponsorship +[#adopting] +=== Orphaned packages -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 - -There are several ways to get sponsored into the `packager` group -depending on your interest. -In many cases doing a mixture of different things -will increase your chances of being sponsored. - -[#submitting_quality_new_packages] -=== Submitting quality new packages - -Until you are sponsored into the `packager` group -you are not able to own packages -or to check in changes to packages which you own. -However, you can still create an initial package -and submit it for review -as talked about at xref:Joining_the_Package_Maintainers#adding_a_new_package[Joining the Package Maintainers]. -When you open your review request in bugzilla, -you should block the https://bugzilla.redhat.com/show_bug.cgi?id=FE-NEEDSPONSOR[FE-NEEDSPONSOR] tracking bug, -that way all of the sponsors -will be able to see your sponsorship request. -Although `FE-NEEDSPONSOR` is set on the package's review request, -it is the person that needs to be sponsored into the `packager` group, -not the package. -The package undergoes a xref:Package_Review_Process.adoc[ review and approval] -that is separate from someone sponsoring you. -Note that it is possible to have accepted packages -which you cannot import because you have not been sponsored. -See below. - -When submitting a new package, -usually a sponsor finds you, -but you can take a look at the https://docs.pagure.org/fedora-sponsors/[list of packager sponsors] -for someone you know. -Sending bulk requests to the list is discouraged. -If you can't find anyone that you have a connection with, -you may want to try hanging out in the https://fedoraproject.org/wiki/How_to_communicate_using_IRC[#fedora-devel IRC channel] -to get to know some people. -Also you might find a sponsor in a that fits to your submitted package. - -Sponsors who work with people submitting new packages -are looking to see how well you are going to be able to maintain this package -which is primarily about whether you can package according to Fedora's https://docs.fedoraproject.org/en-US/packaging-guidelines/[Packaging Guidelines] -but they'll also take into account -how you'll be able to respond to bugs against the code itself. -If you like, -you can include other information about your involvement with the Fedora and upstream communities -that you think might help the sponsors in their decision. -If you are an upstream author of the package you are submitting -or if you are active in the community that surrounds it, -please say so. -If you can line up one or more existing Fedora contributors -who are willing to maintain the package along with you, -even if they are not sponsors, -please indicate that as well. - -The sponsors that look at new package submissions -often ask new packagers to do some package reviews -in order to further show that they know what they're doing. -If you do some reviews ahead of time, -you can show the sponsors that you've both read these pages -and understand the guidelines. -Go ahead and link to other package review requests -where you've left comments and reviews -(More on reviews link:#show_your_expertise_by_commenting_on_other_review_requests[below]). - -Basically, -the more information that you make available, -the quicker you will 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]. - -[#commenting_on_other_review_requests] -=== Commenting on other Review Requests - -To show your familiarity with Fedora's guidelines, -perform unofficial (also called preliminary) reviews -in other maintainers' package review request. -Please clearly state when doing these reviews, -that these are yet unofficial, -and do not change the review requests status -except for adding you to the CC list. -To let sponsors know of your preliminary reviews, -link to them in your review request. -The quality of your reviews help convincing a sponsor of your knowledge. -They will also help out the other reviewers, -which will be much appreciated. -After you got sponsored, you can finish your unofficial reviews. - -Reviews follow the https://docs.fedoraproject.org/en-US/packaging-guidelines/ReviewGuidelines/[review guidelines]. -Note that it's not strictly necessary -for you to work through the entire checklist, -but please do as much as you can; -the more you indicate that you understand, -the better your chances of being sponsored. - -You can search in the https://fedoraproject.org/PackageReviewStatus/in_progress.html[list of reviews in progress] -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]. - -[#opening_pull_requests] -=== Opening Pull Requests - -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, -and demonstrate your expertise. -When requesting sponsorship, you should list these PRs. -In many cases, -maintainers will also be happy to co-maintain the package with you, -and get you sponsored. -More on that in the next section. - -[#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. -To get sponsored this way -you need to convince the current owner of that package -to let you co-maintain the package and to act as your mentor --- teaching you how to package properly in Fedora -and how to use the tools available for building and distributing packages. -To get an owner to agree to this, -you may need to demonstrate -that you have some understanding of packaging already -or at least, that you are eager to learn. -Submitting patches on bug reports, -preparing updated packages if the maintainer is behind on creating an update, -or otherwise communicating with the maintainer that you are willing to help -are ways to show -that you are worth the package owner's investment to train you. - -In some cases the package owner is a sponsor in the `packager` group -and can sponsor you themselves. -If they are not a sponsor, -they can get another existing sponsor to do so, -either by contacting a sponsor personally -and asking them to proxy the sponsorship -or by opening a ticket in the https://pagure.io/packager-sponsors/[packager sponsors pagure instance] -stating that they are a package owner -who would like you to co-maintain their package. -They agree to be responsible for mentoring you in how to follow the https://docs.fedoraproject.org/en-US/packaging-guidelines/[Fedora Packaging Guidelines] -and how to use the tools Fedora provides for building and pushing packages, -but need someone to sponsor you -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[orphaned] -is a good way to become a packager. - -Notifications about orphaned packages are sent to the +You can find orphaned packages in need of maintenance in notifications 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, @@ -211,50 +29,20 @@ possibly with an invitation to contribute in its maintenance * 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 - -Sponsors can decide to sponsor you for any other reason as well. -For example, -you may be upstream for a package -and want to maintain that package in Fedora, -or a sponsor may know your work and packaging history -and deem you worthy of sponsorship -with no further information. -The sponsorship decision is left up to the sponsor. - -== Provenpackagers +[#commenting] +=== Review requests -https://docs.fedoraproject.org/en-US/fesco/Provenpackager_policy/[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. - -[#how_to_sponsor] -== How to sponsor - -If you are looking for information on sponsoring someone, -take a look at xref:How_to_Sponsor_a_New_Contributor.adoc[how to sponsor a new contributor]. +If you plan to comment on review requests to demonstrate your level of understanding, +you can search the https://fedoraproject.org/PackageReviewStatus/in_progress.html[list of reviews in progress] +and the http://fedoraproject.org/PackageReviewStatus/reviewable.html[list of unassigned review requests] +for review requests to comment on. [#how_to_find_a_sponsor] == How to find a sponsor +Usually, a sponsor finds you through your sponsorship request in Bugzilla +or the packager sponsors pagure instance. In case you are waiting to be sponsored for longer than desirable, take a look at https://docs.pagure.org/fedora-sponsors/[Sponsors page]. It will help you find the right sponsor for you -(based on the used programming language, -domain of the project, -native language of the packager, -and other criteria). +based on programming language preference, domains of interest, native language, and other criteria.