On March 27, 2015 6:42:46 AM EDT, Dimstar / Dominique Leuenberger firstname.lastname@example.org wrote:
On Fri, 2015-03-27 at 11:33 +0100, Takashi Iwai wrote:
At Fri, 27 Mar 2015 02:50:08 -0400, Robert Schweikert wrote:
I know we have had this discussion/appeal before but it appears it has not reached everyone yet.
To those that have the power to accept SRs on the behalf of others please be so kind and give package maintainers at least a few days before you accept submit request.
What is the point of having individual package maintainers when those at the project maintainer or higher level simply accept submit requests for package that they do not really maintain?
This is a discouraging practice and unless as a project maintainer you have the intention to maintain all those packages in the project yourself I suggest you exercise restraint for a few days before you run that accept command.
Well, I don't think waiting for a few days unconditionally is good, it'd just slow down the process without much gain. Majority of people assigned as package maintainer still ignore the requests unless they are project maintainers.
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
- project maintainers that don't care for the content of the entire
project should add themselves as maintainer of the packages they care for and remove themselves from the list of project maintainers.
- a package maintainer, that did not ask for explicit review by
himself, once something 'against his ideas' is checked in, is free/welcome to discuss with the sumitter/accepter and revert the change (webui makes that terribly easy: revisions view, revert to this revision)
Some projects have 20 project maintainers, and each cares for one package... That's misleading in every aspect.
If the reviewer flag is easily automated into the review notification process (or already has been) I strongly endorse more active use of that flag.
Particularly when I was a newbie maintainer I would be a package maintainer of new packages I submitted but I would not have felt comfortable reviewing other's SRs.
Thus the idea of having an actively used flag saying I review SRs for a package separate from the maintainer flag makes a tremendous amount of sense to me.