Andre, from what im gathering from this thread thats not what I understand, so i redact the part of my last email about toolforge, however my point on this policy change should of been put to a community vote/consensus is valid.
-- Devin “Zppix” CCENT Volunteer Wikimedia Developer Africa Wikimedia Developers Member and Mentor Volunteer Mozilla Support Team Member (SUMO) Quora.com Partner Program Member enwp.org/User:Zppix **Note: I do not work for Wikimedia Foundation, or any of its chapters. I also do not work for Mozilla, or any of its projects. ** > On Mar 16, 2019, at 1:13 PM, Andre Klapper <[email protected]> wrote: > >> On Sat, 2019-03-16 at 12:40 -0500, Zppix wrote: >> So your basically telling me, I can’t decide who gets the power to +2 >> on for example a toolforge tool I actively am the primary maintainer >> of? Instead it has to be requested. I do not disagree with a lot of >> the changes to technical policies, but with this change it seems to >> restrict ability to scale projects. I also do believe that this >> change should of be taken under RfC or some sort of consensus-gaining >> measure. I respect the intentions, but I absolutely think the change >> needs reverted then voted on by the technical community. > > Did you read https://www.mediawiki.org/wiki/Gerrit/Privilege_policy ? > > It says "For extensions (and other projects) not deployed to the > Wikimedia cluster, the code review policy is up to the maintainer or > author of the extension." > > andre > -- > Andre Klapper | Bugwrangler / Developer Advocate > https://blogs.gnome.org/aklapper/ > > > > _______________________________________________ > Wikitech-l mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/wikitech-l _______________________________________________ Wikitech-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikitech-l
