On Mon, 26 Feb 2007 11:00:43 -0700, Kevin Fenzi wrote: > Yeah, there needs to be periodic 'culling' of the orphans. > If they haven't been picked up in a while (how long?) they should get: > > - removed from the repository (all branches?) Of course! All branches! Else it creates broken upgrades and bug reports that go to "orphan owner". We've had a few cases where somebody run into such a case. The "orphan owner" in bugzilla is like /dev/null when nobody monitors that address and answers in bugzilla. It is easy to re-add a package to an active branch when a new maintainer is found. > - all open bugs closed with 'this package isn't maintained anymore, > sorry' Plus the obligatory pointer to the documentation on how to sign up as a contributor in case there is interest in becoming the new package maintainer. > - bugzilla component removed? Would that be limited to components which don't contain any tickets yet? > - cvs rm'ed and dead.package put in place. > > Perhaps that could be automated somehow? > Of course it's possible that removing an orphan will break a non orphan > package, so what do we do there? Let it be broken and the maintainer > can bring the orphan back if they want? Is that a problem? Removing the orphans would create a broken deps report in that case and mail all package owners that depend on the orphan. If it happens early enough, there should be plenty of time to find a new owner and rebuild the package. -- Fedora-maintainers mailing list Fedora-maintainers@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-maintainers -- Fedora-maintainers-readonly mailing list Fedora-maintainers-readonly@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-maintainers-readonly
