|(10 intermediate revisions by 6 users not shown)|
past, every regular Fedora packager having more than 5 packages (as maintainer) was able to request membership in the provenpackager group (former known as uberpackager group). This initial seeding of the group got changed into manual FAS requests later. Those requests can be approved by a single existing provenpackager-sponsor. |+|
In the , able to in the as of .
| || |
|−|== Policy == |+|
| || |
|−|At the FESCo meeting on 2009/03/06, it was decided that the provenpackager group would be emptied and only existing sponsors would automatically gain admittance, as they had already been vetted by FESCo. This took place on Monday, 2009/03/08. Any future sponsor would also be added to the group if not already a member. |+|
| || |
|−|Any non-sponsor member of provenpackager would need to follow the below procedure in order to gain membership. |+|
member of provenpackagerthe procedure the :
a ticket the [https://fedorahosted.org/fesco ] you to .
|−|* 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 email@example.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. |+|
The FESCo chair will send an e-mail to the sponsors list for the packager group.
|−|* 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 perriod of one week normally. |+|
FESCo will vote at weekly on .
|−|* FESCo will vote at it's weekly meeting on the proposals. | |
| || |
Revision as of 09:25, 17 April 2012
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 packaging guidelines and package maintainer policies, as well as acutely aware of release schedule and freeze policies.
Provenpackagers lend a hand when help is needed, always with a desire to improve the quality of Fedora. Provenpackagers should try to communicate with owners of a package in bugzilla, irc or email prior to making changes. 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 the policy explaining who is allowed to modify which packages. To exclude a package from provenpackagers access, you have to open a ticket at FESCo issue tracker and explain why provenpackagers should not have access to it. FESCo will discuss and vote on one of its weekly meetings about your request.
To become a member of the 'provenpackager' group, the procedure is the following:
- File a ticket in the FESCo issue tracker indicating why you wish to become a provenpackager.
- The FESCo chair will send an e-mail to the sponsors list for the packager group.
- You must get at least 3 positive votes with no negative votes.
- In case of negative votes, FESCo will vote at one of its weekly meetings on your request and then notify you if your request has been approved.