Orphaned package that need new maintainers

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
m (Claiming Ownership of a Retired Package)
(s/retire/deprecate because of https://fedorahosted.org/packagedb/ticket/200)
Line 1: Line 1:
== About Orphan and Retired Packages ==
+
== About Orphan and Deprecated Packages ==
  
When Fedora maintainers do not want or are not able to maintain a package any longer, they can orphan or retire the package. When they think that the package is still useful for Fedora, they should orphan it. Then other maintainers that are interested in maintaining it, can take ownership of this package. In case the package is no longer useful for Fedora, e.g. because it was renamed, upstream does not exist anymore, then it should be retired.
+
When Fedora maintainers do not want or are not able to maintain a package any longer, they can orphan or deprecate the package. When they think that the package is still useful for Fedora, they should orphan it. Then other maintainers that are interested in maintaining it, can take ownership of this package. In case the package is no longer useful for Fedora, e.g. because it was renamed, upstream does not exist anymore, then it should be deprecated.
  
 
== Orphaning Procedure ==
 
== Orphaning Procedure ==
Line 19: Line 19:
 
{{admon/warning|Re-review required for older packages|If a package was last updated more than three months ago (running git log *.spec can show you this information), you will need to submit a review request (a new bugzilla ticket) and have the package approved by a reviewer as if it were new to Fedora.  See [[Package Review Process|  the package review process]]  for more information. There are a couple of small changes though, be sure to submit a 'update' request to the SCM, and before you will be able to run the final 'make build' commands you will need to file a ticket w/ release engineering to unblock your package https://fedorahosted.org/rel-eng/newticket}}
 
{{admon/warning|Re-review required for older packages|If a package was last updated more than three months ago (running git log *.spec can show you this information), you will need to submit a review request (a new bugzilla ticket) and have the package approved by a reviewer as if it were new to Fedora.  See [[Package Review Process|  the package review process]]  for more information. There are a couple of small changes though, be sure to submit a 'update' request to the SCM, and before you will be able to run the final 'make build' commands you will need to file a ticket w/ release engineering to unblock your package https://fedorahosted.org/rel-eng/newticket}}
  
== Claiming Ownership of a Retired Package ==
+
== Claiming Ownership of a Deprecated Package ==
  
If you really want to maintain a retired package, you need to be aware that fixing release critical bugs etc becomes your responsibility. This is to ensure the high quality and standards of packaging remain for Fedora package collection. There may be additional issues with retired packages. Consult with the former maintainer for more information.  The process is a bit different from unorphaning a package
+
If you really want to maintain a deprecated package, you need to be aware that fixing release critical bugs etc becomes your responsibility. This is to ensure the high quality and standards of packaging remain for Fedora package collection. There may be additional issues with deprecated packages. Consult with the former maintainer for more information.  The process is a bit different from unorphaning a package
  
# See if you can figure out why the package was retired including searching for information about orphaned packages on [https://lists.fedoraproject.org/mailman/listinfo/devel devel mailing list] or emailing the former maintainer
+
# See if you can figure out why the package was deprecated including searching for information about orphaned packages on [https://lists.fedoraproject.org/mailman/listinfo/devel devel mailing list] or emailing the former maintainer
 
# Announce on [https://lists.fedoraproject.org/mailman/listinfo/devel devel]  which packages you would like to become the owner of.
 
# Announce on [https://lists.fedoraproject.org/mailman/listinfo/devel devel]  which packages you would like to become the owner of.
## At the moment, most retired packages fall under the "orphaned for more than three months" rule so they need a rereview.
+
## At the moment, most deprecated packages fall under the "orphaned for more than three months" rule so they need a rereview.
 
# Open a [[package SCM admin requests|package SCM admin request]] (if applicable, after the rereview, in the new rereview ticket) to assign ownership to you.
 
# Open a [[package SCM admin requests|package SCM admin request]] (if applicable, after the rereview, in the new rereview ticket) to assign ownership to you.
# When the cvsadmin assigns the package to you it should unretire the package as well.  If the package status still says "Deprecated", "Retired", or "Orphaned" instead of "Approved", you could have encountered a bug.  Please open a ticket on https://fedorahosted.org/fedora-infrastructure/ and assign it to "toshio" or contact toshio via irc:  abadger1999, or one of the mailing lists ([https://lists.fedoraproject.org/mailman/listinfo/infrastructure infrastructure list] or [https://lists.fedoraproject.org/mailman/listinfo/devel devel list])
+
# When the cvsadmin assigns the package to you it should undeprecate the package as well.  If the package status still says "Deprecated" or "Orphaned" instead of "Approved", you could have encountered a bug.  Please open a ticket on https://fedorahosted.org/fedora-infrastructure/ and assign it to "toshio" or contact toshio via irc:  abadger1999, or one of the mailing lists ([https://lists.fedoraproject.org/mailman/listinfo/infrastructure infrastructure list] or [https://lists.fedoraproject.org/mailman/listinfo/devel devel list])
  
== Lists of Orphan and Retired Packages ==
+
== Lists of Orphan and Deprecated Packages ==
  
* Currently [https://admin.fedoraproject.org/pkgdb/acls/orphans orphan packages]  (also contains some retired packages).
+
* Currently [https://admin.fedoraproject.org/pkgdb/acls/orphans orphan packages]  (also contains some deprecated packages).
* [[PackageMaintainers/RetiredPackages|  Retired packages (wiki)]]  (not up to date, may not contain packages that are in the orphan package list, but are actually retired).
+
* [[Deprecated packages]]  (not up to date, may not contain packages that are in the orphan package list, but are actually deprecated).
  
 
{{Anchor|core}}
 
{{Anchor|core}}
  
 
[[Category:Package Maintainers]] [[Category:Policy]]
 
[[Category:Package Maintainers]] [[Category:Policy]]

Revision as of 12:33, 21 April 2011

Contents

About Orphan and Deprecated Packages

When Fedora maintainers do not want or are not able to maintain a package any longer, they can orphan or deprecate the package. When they think that the package is still useful for Fedora, they should orphan it. Then other maintainers that are interested in maintaining it, can take ownership of this package. In case the package is no longer useful for Fedora, e.g. because it was renamed, upstream does not exist anymore, then it should be deprecated.

Orphaning Procedure

  1. Announce on devel which package you want to orphan.
  2. Log into the Package Database and select the package you want to orphan.
  3. Press the "Release Ownership" button for each active branch that you want to orphan.

Claiming Ownership of an Orphaned Package Procedure

  1. Check why the package was orphaned by looking for the email to devel and checking dead.package in the SCM (url like: https://pkgs.fedoraproject.org/gitweb/?p=orphaned_package_name_here.git;a=blob;f=dead.package ).
  2. Announce on devel which packages you would like to become the owner of.
  3. Log into the Package Database and select the package you want to become the owner of.
  4. Press the "Take Ownership" button for each active branch that you want to maintain.
  5. Take over and join (or re-assign to you) open bug reports in bugzilla where package owner's attention is needed.
Warning (medium size).png
Re-review required for older packages
If a package was last updated more than three months ago (running git log *.spec can show you this information), you will need to submit a review request (a new bugzilla ticket) and have the package approved by a reviewer as if it were new to Fedora. See the package review process for more information. There are a couple of small changes though, be sure to submit a 'update' request to the SCM, and before you will be able to run the final 'make build' commands you will need to file a ticket w/ release engineering to unblock your package https://fedorahosted.org/rel-eng/newticket

Claiming Ownership of a Deprecated Package

If you really want to maintain a deprecated package, you need to be aware that fixing release critical bugs etc becomes your responsibility. This is to ensure the high quality and standards of packaging remain for Fedora package collection. There may be additional issues with deprecated packages. Consult with the former maintainer for more information. The process is a bit different from unorphaning a package

  1. See if you can figure out why the package was deprecated including searching for information about orphaned packages on devel mailing list or emailing the former maintainer
  2. Announce on devel which packages you would like to become the owner of.
    1. At the moment, most deprecated packages fall under the "orphaned for more than three months" rule so they need a rereview.
  3. Open a package SCM admin request (if applicable, after the rereview, in the new rereview ticket) to assign ownership to you.
  4. When the cvsadmin assigns the package to you it should undeprecate the package as well. If the package status still says "Deprecated" or "Orphaned" instead of "Approved", you could have encountered a bug. Please open a ticket on https://fedorahosted.org/fedora-infrastructure/ and assign it to "toshio" or contact toshio via irc: abadger1999, or one of the mailing lists (infrastructure list or devel list)

Lists of Orphan and Deprecated Packages

  • Currently orphan packages (also contains some deprecated packages).
  • Deprecated packages (not up to date, may not contain packages that are in the orphan package list, but are actually deprecated).