On Fri, 2015-03-27 at 14:42 +0100, Adrian Schröter wrote:
For the package I care that strongly, I set myself as reviewer.
Project maintainers do have the power to ignore this, but so far I have to say, I didn't see anybody doing this (which is good).
My recommendation is:
- Project maintainers are there to maintain the ENTIRE project
(meta data incl. packages)
- Package maintainers are limited to a specific package / group of
packages. But they are not on their own
- If a package maintainer commits sufficiently to be 'the only
responsible', he should mark himself as reviewer of the package
I do not understand that part, you want to be the maintainer additionaly be reviewer in a package in some devel project? What does this help you? Isn't it more a burden to accept first the review and afterwards the request?
In some cases this makes sense; e.g vlc in multimedia:libs: whereas I like the fact that other people contribute, this has much more impact than people tend to see. so I added myself as reviewer, despite being maintainer.
It gives the project maintainers, which do a fabulous job accepting packages, a hint that 'ey, this is NOT something I should accept without asking back'
if I want to check it in, I am perfectly happy in taking the extra step to either accept the review first or confirm on checkin that there are open reviews.
OBS could actually improve there: if the only open reviews to handle are of the user that is performing the accept, it is of little use to ask him...
Maybe this is a special case setup; but it has the exact effect people are looking for.