On Freitag, 27. März 2015, 11:42:46 wrote Dimstar / Dominique Leuenberger:
On Fri, 2015-03-27 at 11:33 +0100, Takashi Iwai wrote:
At Fri, 27 Mar 2015 02:50:08 -0400, Robert Schweikert wrote:
Hi,
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
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?
- 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.
This is okay, if all of them do really take care of all packages. eg. KDE people work that way and that is quite okay from my POV. But, yes, people should not be project maintainer if they do not take care of all projects. Btw, while I think the OBS notification mails improved a lot last year, it is of course also okay to work via the pull model. You see always all open tasks for you in - the webui on top right (X tasks) or by running - osc my All open requests for you and also wanted maintenance updates are listed here. -- Adrian Schroeter email: adrian@suse.de SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org