acutely aware of [[Releases/Schedule|release schedule]] and [[ReleaseEngineering#Freeze_Policies|freeze policies]]. They lend a hand when help is needed, always with a desire to improve the quality of Fedora. They should be careful not to change other people packages needlessly and try to do the minimal changes in packages to fix problems, as explained more in depth on [[Who_is_allowed_to_modify_which_packages|the policy explaining when one is allowed to modify a package]].

acutely aware of [[Releases/Schedule|release schedule]] and [[ReleaseEngineering#Freeze_Policies|freeze policies]]. They lend a hand when help is needed, always with a desire to improve the quality of Fedora. They should be careful not to change other people packages needlessly and try to do the minimal changes in packages to fix problems, as explained more in depth on [[Who_is_allowed_to_modify_which_packages|the policy explaining when one is allowed to modify a package]].

−

To become a member of the provenpackager group you have to open a ticket on [[https://fedorahosted.org/fesco| https://fedorahosted.org/fesco]] and setting the ticket type to 'provenpacker request'. In the Ticket you should explain why you want to get the provenpacker status.

+

To become a member of the provenpackager, the procedure is the following:

−

+

* Make desire known to [[Development/SteeringCommittee|FESCo]]. This can be done in any fashion - private mail to the chair, on [https://www.redhat.com/mailman/listinfo/fedora-devel-list fedora-devel-list], via IRC (probably not really recommended), via mail to fedora-extras-steering@redhat.com, filing a ticket at the [https://fedorahosted.org/fesco Trac] instance, applying to the group, carrier pigeon, etc. It is helpful if you specify what you plan to do with the access in the communication.

−

FESCo will ask the sponsors for advice and discuss and vote your request on one of thier meetings. if you are fullfill the requirements to become a member of the provenpackager group you will get a notification after your request will been approved.

+

* If reason for access is not stated, the FESCo chair may ask for clarification from the individual requesting access what they plan to do with the access.

+

* The FESCo chair will send an e-mail to the sponsors list for the packager group. Debate will take place on the list for a period of one week normally.

+

* FESCo will vote at it's weekly meeting on the proposals.

+

* If you are fullfill the requirements to become a member of the provenpackager group you will get a notification after your request will been approved.

== Reviewing Packages ==

== Reviewing Packages ==

Revision as of 19:47, 30 March 2009

Contents

Getting Sponsored

Get a Fedora Account

You should already have a Fedora Account or you did not follow the Join the Fedora Package Collection Maintainers Guide. Please read the guide first and come back here later. If you do not want to become a package maintainer in the Fedora Project, you do not need to be sponsored.

Why Get Sponsored?

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 before getting this access to Fedora to ensure that they have sufficient knowledge to maintain Fedora packages properly including understanding of the Fedora packaging guidelines by for example, reviewing other packages.

Sponsorship model

The Fedora package submission process requires that new package submitters be sponsored before they are granted access to the 'packager' group. Members of this group are able to own packages and to check in changes to packages which you own. It is the person who needs to be get sponsored and not the packages. Note that sponsorship is not automatic and requires that you find a willing sponsor. A sponsor will assist you with some aspects of packaging and the submission process but will expect you to be able to handle the bulk of this process. Because of this, it is necessary for you to show that you have an understanding of the process and of the packaging guidelines.

The best ways for you to illustrate your understanding of the packaging guidelines are to submit quality packages and to assist with package reviews. Prospective sponsors will want to see what reviews you have done, so go ahead and tell them when you submit your first package review request and add comments to your open review ticket with information about your activities. If you like, you can include other information about your involvement with the community 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.

Basically, the more information that you make available, the quicker you will find a sponsor.

Note that if you follow the proper procedure when submitting your first review request, including the all-important blocking of the FE-NEEDSPONSOR ticket, then all of the sponsors will be able to see your sponsorship request. Note also that you should not submit your sponsorship request to the account system until after you have been given the go-ahead from a sponsor.

To find a sponsor go to the (list of packager sponsors) and look for one that could sponsor you. The list of sponsors is only visible to contributors with a Fedora Account.

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. It is possible for a maintainer to deny access to provenpackagers for his particular package, but the vast, vast majority of packages can be changed by provenpackagers. To exclude a package from provenpackagers access you have open a ticket at [https://fedorahosted.org/fesco] and explain why provenpackagers should not have access to it. FESCo will discuss and vote on one of the weekly meetings about your request.

To become a member of the provenpackager, the procedure is the following:

Make desire known to FESCo. This can be done in any fashion - private mail to the chair, on fedora-devel-list, via IRC (probably not really recommended), via mail to fedora-extras-steering@redhat.com, filing a ticket at the Trac instance, applying to the group, carrier pigeon, etc. It is helpful if you specify what you plan to do with the access in the communication.

If reason for access is not stated, the FESCo chair may ask for clarification from the individual requesting access what they plan to do with the access.

The FESCo chair will send an e-mail to the sponsors list for the packager group. Debate will take place on the list for a period of one week normally.

FESCo will vote at it's weekly meeting on the proposals.

If you are fullfill the requirements to become a member of the provenpackager group you will get a notification after your request will been approved.

Reviewing Packages

It is true that before you have been sponsored you will not have the ability to assign review tickets to yourself, but you can still make comments and the quality of those comments can go a long way towards convincing a sponsor. They will also help out the other reviewers, which will be much appreciated. Please restrict yourself to only make comments and add yourself to the CC list, until you are familiar with other possible changes of a bug's status. Please do not change the fedora-review flag as this may make it difficult for other reviewers to tell that the package still needs a final review.

Reviews follow the 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.