User:Wraeth/PM MaintBug User

Previously the process for claiming maintainership of a package was haphazard with no real guidelines on how to request a package and nothing, aside from parsing the tree, to list maintainers and the packages they maintained. This caused problems from time to time, such as two people claiming a package at the same time, unaware of each other, or packages getting neglected when a maintainer became absent. To address this, the Proxy Maintainers project has implemented a standard process for claiming a package, and have introduced Maintainer Bugs - the equivalent of a developer bug.

Claiming a Package
If you wish to claim maintainership of a package, begin by searching Bugzilla for bugs with the summary Maintainership request: (where is the name of the package you wish to maintain. If any bugs are open with a status of  or, add a comment stating that you wish to maintain the package. If there are no bugs in either of those states, create a new one.

Once a maintainership request is filed, a developer will CC themselves to the bug and guide you through the rest of the process to claiming maintainership. This may include resolving any open bugs for the package (which will be linked in the field) or, if none exist, beginning a timeout procedure before assigning the package to you. The developer will take the opportunity to get to know you a little and will make an assessment of whether the package is suitable to be proxy maintained. Any questions or concerns you have about the maintainership should be directed to the developer managing your request (the one that is CC'd to the bug).

If that developer is unable to continue managing the request (for example, if they are going to be away for a time) they will remove themselves from the bug and set it back to an status to indicate that it needs another developer to manage it.

If the maintainership request is granted, a Maintainer Bug (described below) will be created for you and the request will be set to and linked to your maintainer bug. Additional packages you wish to maintain should follow this same process, resulting in all packages you actively maintain having an open request bug linked to your maintainer bug.

Dropping Maintainership
If you wish to cease maintainership of a package, either due to someone else requesting maintainership, or because you don't use the package any more, or even if you simply don't have time, add a comment on the request bug for the package noting that you want to drop it. You will then be removed from for the package and the bug will be  showing that you are no longer responsible for it.

Rejected Requests
It is not often that maintainership requests are rejected, however if this does happen, the developer managing the request will explain why the request was rejected. Requests that have been refused will be closed with a state of.

Maintainer Bug
When you begin maintainership of your first package, you will have a Maintainer Bug created. This can be considered your lifeline to the Proxy Maintainers project and will have the maintainership request of each package you maintain, past and present, linked in the field. Your maintainer bug will also be a general record of your proxied maintenance, and can also be beneficial if you choose to continue on to recruitment in order to become a Gentoo Developer.

You can use this bug to note if you are going to be away for a period of time, or if you wish to cease proxied maintainership altogether. Gentoo developers may also use this bug to contact you (a "ping") if they are unsure that you are still active.

When you cease maintainership, either by leaving the Proxy Maintainers project or continuing on to recruitment, each maintainership request will be closed with a brief not describing the reason. Once all maintainership requests are closed, your maintainer bug will also have a brief note added and be closed.