Frequence Asked questions about the TreeCleaner Project
1.
Gentoo TreeCleaner Frequently Asked Questions
I'm a Gentoo Developer. Will TreeCleaners remove my package for me?
Short answer: no. The TreeCleaner project encourages maintainers to remove
their own packages. If you no longer wish to maintain a package, you should
consider reassigning it to maintainer-needed, to indicate its unmaintained
status.
TreeCleaners are removing a package I use! What should I do?
Please comment on the removal bug (it should be apparent in the masking).
If there isn't one, please tell us in #gentoo-qa on irc.freenode.org.
If you are interested in maintaining the package, you should contact the
proxy-maintainer project by emailing proxy-maint@gentoo.org.
What resources do TreeCleaners provide?
TreeCleaners provide some documentation on their policy. We also provide
some tools to aid package maintainer who wish to mask/remove a package. We
have an overlay where removed packages are moved to and we hope to have a
database containing treecleaner information (package removal history etc)
available soon.
Cool. Where can I get these scripts?
Here.
How to get files out of the cvs attic
Take a look at
http://sources.gentoo.org/viewcvs.py/gentoo-x86/?hideattic=0
I'm a Gentoo dev. I want to fix a maintainer-needed package.
Do I have to support it forever now?
Not at all. While the 'you clean up your own mess' rule applies, it
only applies to that commit - you are not expected to look after that
package any more.
I'm a Gentoo dev, and want to join the TreeCleaner project
Great! Please read up on TreeCleaner policy and then drop into
#gentoo-qa on irc.freenode.org and talk to antarus (project lead).
I don't understand something in this FAQ!
Please join #gentoo-qa on irc.freenode.org, or mail
treecleaner@gentoo.org if you want clarification on any of
TreeCleaner's policies, or any decisions that have been made by TreeCleaners.
The contents of this document, unless otherwise expressly stated, are licensed under the CC-BY-SA-2.5 license. The Gentoo Name and Logo Usage Guidelines apply.
|