User avatar None

String updated in the repository

  1. fedora-docs-l10n/package-maintainers
  2. master/pages/How_to_Sponsor_a_New_Contributor
  3. English
Provenpackagers are approved on at least 3 positive votes with no negative votes. In the event of negative votes, the decision will be made by FESCo at their next meeting. See the xref:fesco::Provenpackager_policy.adoc[provenpackager description] for more information.
Provenpackagers are approved on at least 3 positive votes with no negative votes. In the event of negative votes, the decision will be made by FESCo at their next meeting. See the xref:fesco::Provenpackager_policy.adoc[provenpackager description] for more information.
6 months ago
User avatar None

String updated in the repository

  1. fedora-docs-l10n/package-maintainers
  2. master/pages/How_to_Sponsor_a_New_Contributor
  3. English
By granting membership into the provenpackager group for a maintainer you are confirming that (at least in your mind) they meet the criteria for that group, and that you would trust them fully with any of the packages you either maintain or even just use.
By granting membership into the provenpackager group for a maintainer you are confirming that (at least in your mind) they meet the criteria for that group, and that you would trust them fully with any of the packages you either maintain or even just use.
6 months ago
User avatar None

String updated in the repository

  1. fedora-docs-l10n/package-maintainers
  2. master/pages/How_to_Sponsor_a_New_Contributor
  3. English
xref:fesco::Provenpackager_policy.adoc[Provenpackagers] have access to most packages. FESCo members should forward requests for provenpackagers to the sponsors mailing list where sponsors can give their advice on the provenpackager request. Provenpackagers may nominate themselves, but having a sponsor endorse the nomination or proposing the packager to become a provenpackager (the packager should agree) is certainly a good thing.
xref:fesco::Provenpackager_policy.adoc[Provenpackagers] have access to most packages. FESCo members should forward requests for provenpackagers to the sponsors mailing list where sponsors can give their advice on the provenpackager request. Provenpackagers may nominate themselves, but having a sponsor endorse the nomination or proposing the packager to become a provenpackager (the packager should agree) is certainly a good thing.
6 months ago
User avatar None

String updated in the repository

  1. fedora-docs-l10n/package-maintainers
  2. master/pages/How_to_Sponsor_a_New_Contributor
  3. English
Sponsoring Someone for provenpackagers
Sponsoring Someone for provenpackagers
6 months ago
User avatar None

String updated in the repository

  1. fedora-docs-l10n/package-maintainers
  2. master/pages/How_to_Sponsor_a_New_Contributor
  3. English
So what's the downside to sponsoring someone? Your sponsoree will likely have questions about processes; one of your responsibilities as a sponsor is to help them with the answers. A sponsor isn't expected to be omniscient, though, so you can feel free to ask for others' advice and opinions if you get a really hard question. xref:fesco::Packager_sponsor_policy.adoc[Sponsor responsibilities are detailed here].
So what's the downside to sponsoring someone? Your sponsoree will likely have questions about processes; one of your responsibilities as a sponsor is to help them with the answers. A sponsor isn't expected to be omniscient, though, so you can feel free to ask for others' advice and opinions if you get a really hard question. xref:fesco::Packager_sponsor_policy.adoc[Sponsor responsibilities are detailed here].
6 months ago
User avatar None

String updated in the repository

  1. fedora-docs-l10n/package-maintainers
  2. master/pages/How_to_Sponsor_a_New_Contributor
  3. English
A new packager cannot, at this time, make changes to packages he does not own or comaintain until he applies to become a xref:fesco::Provenpackager_policy.adoc[provenpackager] but you should still keep an eye on them. Generally the easiest way to do this is for them to become comaintainers of at least the initial package they review. You should be sure to review their commits to the Git repository for how they look, and consider watching their Bugzilla activity at least for a while (Preferences→Email Preferences→https://bugzilla.redhat.com/userprefs.cgi?tab=email[User Watching]). Respond with any comments that you might have and guide them, providing assistance as they need it for any tasks. A provenpackager can step in if necessary.
A new packager cannot, at this time, make changes to packages he does not own or comaintain until he applies to become a xref:fesco::Provenpackager_policy.adoc[provenpackager] but you should still keep an eye on them. Generally the easiest way to do this is for them to become comaintainers of at least the initial package they review. You should be sure to review their commits to the Git repository for how they look, and consider watching their Bugzilla activity at least for a while (Preferences→Email Preferences→https://bugzilla.redhat.com/userprefs.cgi?tab=email[User Watching]). Respond with any comments that you might have and guide them, providing assistance as they need it for any tasks. A provenpackager can step in if necessary.
6 months ago
User avatar None

String updated in the repository

  1. fedora-docs-l10n/package-maintainers
  2. master/pages/How_to_Sponsor_a_New_Contributor
  3. English
Add any comment for changes to the review request on Bugzilla which look as though they'd be needed for compliance as well as the fact that you're volunteering to sponsor them. Once they've made those changes, you can approve the package and sponsor the user in the Fedora account system. Before you approve the user, please make sure that his/her email in https://accounts.fedoraproject.org/[Fedora Account system] is the same as in https://bugzilla.redhat.com[Red Hat Bugzilla]. After that, go to https://accounts.fedoraproject.org/group/packager/, log in, then add the username in the 'add user' field located to the right of the top of the "Members" section, then press enter.
Add any comment for changes to the review request on Bugzilla which look as though they'd be needed for compliance as well as the fact that you're volunteering to sponsor them. Once they've made those changes, you can approve the package and sponsor the user in the Fedora account system. Before you approve the user, please make sure that his/her email in https://accounts.fedoraproject.org/[Fedora Account system] is the same as in https://bugzilla.redhat.com[Red Hat Bugzilla]. After that, go to https://accounts.fedoraproject.org/group/packager/, log in, then add the username in the 'add user' field located to the right of the top of the "Members" section, then press enter.
6 months ago
User avatar None

String updated in the repository

  1. fedora-docs-l10n/package-maintainers
  2. master/pages/How_to_Sponsor_a_New_Contributor
  3. English
Bugzilla will send a notification mail for the new review request to the fedora-package-review mailing list. Take a look at their package and review it. If it looks reasonable and it seems that the comply with the xref:packaging-guidelines::index.adoc[Packaging Guidelines], then they are probably a good candidate to be sponsored.
Bugzilla will send a notification mail for the new review request to the fedora-package-review mailing list. Take a look at their package and review it. If it looks reasonable and it seems that the comply with the xref:packaging-guidelines::index.adoc[Packaging Guidelines], then they are probably a good candidate to be sponsored.
6 months ago
User avatar None

String updated in the repository

  1. fedora-docs-l10n/package-maintainers
  2. master/pages/How_to_Sponsor_a_New_Contributor
  3. English
Sponsoring someone for access to Fedora Package Collection is relatively simple. If you are looking for someone to sponsor, take a look at the https://accounts.fedoraproject.org/[Fedora Account system] for contributors who are currently searching for a sponsor. Note that they should also have submitted a package review request for a package which they are proposing to add to Fedora on https://bugzilla.redhat.com[Red Hat Bugzilla]. In this request they should write that they need a sponsor.
Sponsoring someone for access to Fedora Package Collection is relatively simple. If you are looking for someone to sponsor, take a look at the https://accounts.fedoraproject.org/[Fedora Account system] for contributors who are currently searching for a sponsor. Note that they should also have submitted a package review request for a package which they are proposing to add to Fedora on https://bugzilla.redhat.com[Red Hat Bugzilla]. In this request they should write that they need a sponsor.
6 months ago
User avatar None

String updated in the repository

  1. fedora-docs-l10n/package-maintainers
  2. master/pages/How_to_Sponsor_a_New_Contributor
  3. English
Sponsoring Someone for Fedora Package Collection
Sponsoring Someone for Fedora Package Collection
6 months ago
User avatar None

String updated in the repository

  1. fedora-docs-l10n/package-maintainers
  2. master/pages/How_to_Sponsor_a_New_Contributor
  3. English
Votes will be collected in the ticket for a week. At the end of that time, if the differential between positive and negative votes stands at +3 or greater, your request will be approved and you'll be promoted to sponsor status immediately. If not, your request will be closed. You may reapply anytime you feel you have more support. After waiting an hour or so for the new permissions to propagate through the system, you will be able to sponsor new packagers.
Votes will be collected in the ticket for a week. At the end of that time, if the differential between positive and negative votes stands at +3 or greater, your request will be approved and you'll be promoted to sponsor status immediately. If not, your request will be closed. You may reapply anytime you feel you have more support. After waiting an hour or so for the new permissions to propagate through the system, you will be able to sponsor new packagers.
6 months ago
User avatar None

String updated in the repository

  1. fedora-docs-l10n/package-maintainers
  2. master/pages/How_to_Sponsor_a_New_Contributor
  3. English
If you're a packager and feel that you are ready and would like to move up to sponsor status, simply file a ticket in the https://pagure.io/packager-sponsors/issues[packager sponsors ticket system]. These tickets are automatically sent to the sponsors list. A report will be added containing information on your reviewed and owned/comaintained packages, but feel free to provide additional information that can't easily be found such as informal reviews done or prospective packagers you would like to sponsor.
If you're a packager and feel that you are ready and would like to move up to sponsor status, simply file a ticket in the https://pagure.io/packager-sponsors/issues[packager sponsors ticket system]. These tickets are automatically sent to the sponsors list. A report will be added containing information on your reviewed and owned/comaintained packages, but feel free to provide additional information that can't easily be found such as informal reviews done or prospective packagers you would like to sponsor.
6 months ago
User avatar None

String updated in the repository

  1. fedora-docs-l10n/package-maintainers
  2. master/pages/How_to_Sponsor_a_New_Contributor
  3. English
These are still somewhat vague to allow for flexibility but should provide a reasonable idea of how much experience is required.
These are still somewhat vague to allow for flexibility but should provide a reasonable idea of how much experience is required.
6 months ago
User avatar None

String updated in the repository

  1. fedora-docs-l10n/package-maintainers
  2. master/pages/How_to_Sponsor_a_New_Contributor
  3. English
Have been members of the packager group for at least one release cycle (generally six months) so that they have seen the process of branching for a new release.
Have been members of the packager group for at least one release cycle (generally six months) so that they have seen the process of branching for a new release.
6 months ago
User avatar None

String updated in the repository

  1. fedora-docs-l10n/package-maintainers
  2. master/pages/How_to_Sponsor_a_New_Contributor
  3. English
Have done five high quality, nontrivial package reviews.
Have done five high quality, nontrivial package reviews.
6 months ago
User avatar None

String updated in the repository

  1. fedora-docs-l10n/package-maintainers
  2. master/pages/How_to_Sponsor_a_New_Contributor
  3. English
Maintain at least three packages.
Maintain at least three packages.
6 months ago
User avatar None

String updated in the repository

  1. fedora-docs-l10n/package-maintainers
  2. master/pages/How_to_Sponsor_a_New_Contributor
  3. English
The Fedora Package Collection has been setup so to encourage "learning by doing" and the development of cooperative relationships between Fedora packagers. Once packagers have acquired sufficient packaging knowledge to help others through the process, they may apply for sponsor status. As "sufficient knowledge" is unworkably vague, the following guidelines have been established. Prospective sponsors should:
The Fedora Package Collection has been setup so to encourage "learning by doing" and the development of cooperative relationships between Fedora packagers. Once packagers have acquired sufficient packaging knowledge to help others through the process, they may apply for sponsor status. As "sufficient knowledge" is unworkably vague, the following guidelines have been established. Prospective sponsors should:
6 months ago
User avatar None

String updated in the repository

  1. fedora-docs-l10n/package-maintainers
  2. master/pages/How_to_Sponsor_a_New_Contributor
  3. English
Becoming a Fedora Package Collection Sponsor
Becoming a Fedora Package Collection Sponsor
6 months ago
User avatar None

String updated in the repository

  1. fedora-docs-l10n/package-maintainers
  2. master/pages/How_to_Sponsor_a_New_Contributor
  3. English
How to Sponsor a New Contributor
How to Sponsor a New Contributor
6 months ago
User avatar None

Resource updated

  1. fedora-docs-l10n/package-maintainers
  2. master/pages/Reporting_Issues
  3. French
The “po/fr/master/pages/Reporting_Issues.po” file was changed. 6 months ago

Search