On 06 Feb 2017, at 19:27, Thiago Macieira <[email protected]<mailto:[email protected]>> wrote:
On segunda-feira, 6 de fevereiro de 2017 18:39:19 PST Oswald Buddenhagen wrote: On Mon, Feb 06, 2017 at 02:54:53PM +0000, Alexander Blasche wrote: There were no objections and maintainer of a module implies approver, so could somebody do the honours and grant Mike the rights please? The necessary period has long since passed. I am sorry but being the maintainer does not imply approver rights. At most it implies approver rights for the component he is maintainer for. I agree that when you maintain a cross module component that this is somewhat harder to manage. selective approver rights are not implementable for a horizontal responsibility, so this is kind of moot. In any case I am sure that waiting for the required time does not make much of a difference. Then this discussion is over anyway. the previous thread already used the word approver without futher qualification (http://lists.qt-project.org/pipermail/development/2016-August/026909.html) and nobody objected, so i just gave mike the rights. Let's not quabble over this. Becoming maintainer of anything in a main module implies becoming Approver everywhere, if one is not so yet. Restricted maintainership rights should be used only for playground things. +1. Being maintainer of something that is part of Qt does of course imply approver rights. Cheers, Lars
_______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
