| |
@@ -5,13 +5,16 @@
|
| |
[[purpose]]
|
| |
== Purpose
|
| |
|
| |
- The purpose for this policy is to provide a mechanism within Fedora to handle situations when a package maintainer becomes unavailable to continue maintainership, often referred to as non-responsive.
|
| |
- The end goal is to help prevent packages becoming stale through non-maintenance, reduce open bugs on non-maintained packages and assist in the overall quality of Fedora.
|
| |
+ The purpose for this policy is to provide a mechanism within Fedora to handle situations
|
| |
+ when a package maintainer becomes unavailable to continue maintainership, often referred to as "non-responsive".
|
| |
+ The end goal is to help prevent packages becoming stale through non-maintenance,
|
| |
+ reduce open bugs on non-maintained packages, and increase the overall quality of Fedora.
|
| |
|
| |
[[coverage]]
|
| |
== Coverage
|
| |
|
| |
- This policy covers existing Fedora packages, containers, and modules; for non-responsive package submitters or reviewers, see the
|
| |
+ This policy covers existing Fedora packages, containers, and modules;
|
| |
+ for non-responsive package submitters or reviewers, see the
|
| |
link:https://fedoraproject.org/wiki/Policy_for_stalled_package_reviews[Policy for stalled package reviews].
|
| |
If you are a *not* an existing Fedora contributor, you can follow this procedure too.
|
| |
If you want to take over maintainership, you must find a sponsor following the rules specified in
|
| |
@@ -61,6 +64,7 @@
|
| |
8. With no further reply for the original owner, FESCo closes its ticket and the bugzilla ticket.
|
| |
If maintainership was requested in the FESCo ticket, the reporter will be assigned as the main maintainer of the package, and the package will be orphaned otherwise.
|
| |
All other packages are orphaned too, and may be picked up by co-maintainers or other packagers.
|
| |
+ The original owner is removed as co-maintainer (admin/commit/ticket access) or "watcher" from all other packages.
|
| |
|
| |
Once the final reassignment happens, the new owner must also reassign all open bugs for this package to themselves.
|
| |
|
| |
@@ -77,16 +81,23 @@
|
| |
* Edit the Vacation page to indicate when you will be away.
|
| |
|
| |
[[notes-for-invalid-email-addresses]]
|
| |
- == Notes for invalid email addresses
|
| |
+ == Invalid email addresses
|
| |
|
| |
link:https://bugzilla.redhat.com[Bugzilla] uses the email address in the Fedora Account System to send messages to the package maintainer.
|
| |
- If it becomes known that this email address no longer goes to the package maintainer, this should be noted in the mailing list post and FESCo ticket, but the policy outline above will still be followed.
|
| |
+ If it becomes known that this email address no longer goes to the package maintainer,
|
| |
+ and there is already an open non-responsive maintainer procedure open,
|
| |
+ the issue with the email address should be noted in the mailing list post and FESCo ticket.
|
| |
+ Otherwise, the non-responsive maintainer procedure should be opened for this maintainer.
|
| |
|
| |
Situations where it becomes known that an email address is no longer going to go to the maintainer are:
|
| |
|
| |
. Email to the address bounces (to differentiate from temporary bounces like a mailbox full, this should go on for a period of 7 days).
|
| |
. Red Hat lets us know that an email address is no longer valid for the package maintainer (usually because the person has left Red Hat).
|
| |
|
| |
+ In the special case where an account does not have a valid email address connected in bugzilla,
|
| |
+ and does not maintain any packages and is not part of `packager` group,
|
| |
+ it can be dropped from package "watchers" immediately.
|
| |
+
|
| |
[[exception-procedure]]
|
| |
== Exception procedure
|
| |
|
| |
