Gerrit/New repositories/Requests

You'll be telling us your wikitech/LDAP username, what code review model you want and what you want the project name in gerrit to be. Click request, then fill in the fields on the page creation screen:

{| class="wikitable sortable" ! Extension ! Developer ! Preferred model ! Comments ! Status


 * Example
 * Alison
 * Merge review
 * Early stages of development.
 * ✅ --Admin user 09:56, 14 February 2012 (UTC)
 * ✅ --Admin user 09:56, 14 February 2012 (UTC)


 * mediawiki/gadgets/convenient-discussions
 * Jack who built the house, Iniquity
 * Open push only for repo maintainers
 * Hi, we need to create a mirrow of CD repository (https://github.com/jwbth/convenient-discussions) on gerrit to work with localization directly from the Wikiproject. --Iniquity (talk) 01:55, 3 June 2020 (UTC)
 * By mirror, you mean "clone the repo once and then development will happen on Gerrit" or you mean "development happens on GitHub and Gerrit should keep itself updated from that repo"? (We can do the first, but not the second)
 * By mirror, you mean "clone the repo once and then development will happen on Gerrit" or you mean "development happens on GitHub and Gerrit should keep itself updated from that repo"? (We can do the first, but not the second)

Also, although there are currently only 2 repos underneath   they follow the CamelCase name conventions from. So would you be ok if I CamelCase the repo name to ? --QChrisNonWMF (talk) 20:00, 3 June 2020 (UTC)
 * Yes, I meant the second variant. It's a pity. Nothing can be done? :( Iniquity (talk) 11:22, 4 June 2020 (UTC)


 * Too bad :-( Unfortunately, nothing can be done. Gerrit is only good at pushing changes forward (e.g.: to GitHub), not so much with pulling changes from another remote. --QChrisNonWMF (talk) 12:47, 4 June 2020 (UTC)


 * A little clarification, I'm not talking about automatic updates by gerrit. We can do this on our own :) Iniquity (talk) 13:04, 4 June 2020 (UTC)


 * Maybe I got this whole thread wrong, but it is possible to develop code on GitHub and get it mirrored on Gerrit via Phabricator Diffusion "push" functionality. Granted, this is not encouraged because it's a weird setup. &mdash;MarcoAurelio (talk) 21:23, 4 June 2020 (UTC)


 * You're of course right. The setup you describe is technically possible. But while technically possible, this setup is not only "not encouraged" as you write, it's discouraged. The documentation for ORES setup even contains the word "dangerous", which might be over the top :-D The whole thing is a bit interwoven with many other things, so let me reach out a bit farther. Probably we should add this to a page about repo creation. Not sure. Regardless: The text below is not meant to lecture anyone, but just to provide more detail and context why we're typically not doing such setups (although they would technically be possible). The big picture is that at some point, each team in WMF decided which task tracker they wanted to use. There was a wide mix between Bugzilla, Trello, Mingle and what not. It was hard to find who did what and when, because everyone used a different system. Some teams even used more than one tracker. This was considered a serious enough issue that after some discussion, this was all switched to Phabricator (Phabricator RFC). Since we wanted all things at one place, one of they key arguments for many was that Phabricator will also include Code Reviews. That last part never materialized for several reasons. We ended up with not a single tool for Code Review, but two. Phabricator for the early adopters, and Gerrit for the rest--although we switched to Phabricator to have everything in one place. In order to get Code Review back into a single place another RFC was done to fully migrate Code Review to Phabricator. And it was declined. So we arrived at the point where we want to stop using Differential for code review . We want all in one place so people can easily find the authorative repo. People can easily find the place where to submit patches etc. Whether we like it or not, (at least for now) this single place is Gerrit for WMF. Not sure if I like that or not, but it is what it is. And if we end up having exceptions again and again, we end up having code in so many different places again, just as we did with Bugtrackers before. This is the very thing our community does not want :-) But even when ignoring all these social requirements, having repos elsewhere does also come with a support burden. For example, if the authorative repo is, say GitHub, and we get the code into Gerrit automatically through some means, what happens to localization updates that get applied automagically on Gerrit? Either Phabricator fails to push some commit due to a merge conflict sooner or later or it force pushes and thereby rewriting history. We've been there. We've received tickets for such breakage and we've seen accusations of undoing someone's commits etc. Although it was just a simple automated pull/push. So for all these reasons, I'll not set-up a GitHub repo pull/push to Gerrit. But as Iniquity said that it need not be automatic updates we can push the problem onto Inquity's shoulders (see below) --QChrisNonWMF (talk) 09:39, 5 June 2020 (UTC)


 * If you want to do the updates manually (You pull the code from GitHub yourself and you push onto Gerrit yourself), that's something you can do. Not that that's our prefered setup, but we definitely grant you push access, and then you can do what you suggested (And we already have plenty such repos, so there's no point in denying it :-) ). Then we're back to the naming question. Would  work for you as repo name? --QChrisNonWMF (talk) 09:39, 5 June 2020 (UTC)
 * Yes, this is not a problem, we can work with . And thanks for the detailed comment above :) Iniquity (talk) 14:53, 6 June 2020 (UTC)

✅ Created as mediawiki/gadgets/ConvenientDiscussions

(GitHub mirror)(Phabricator mirror) --QChrisNonWMF (talk) 19:59, 7 June 2020 (UTC)


 * mediawiki/extensions/Expressions
 * xxmarijnw
 * Merge review
 * Please import https://github.com/26/Expressions/ Thanks! --Xxmarijnw (talk) 17:14, 3 June 2020 (UTC)
 * ✅ and imported as requested. &mdash;MarcoAurelio (talk) 17:40, 3 June 2020 (UTC)
 * ✅ and imported as requested. &mdash;MarcoAurelio (talk) 17:40, 3 June 2020 (UTC)


 * mediawiki/extensions/CatTalk
 * naypta
 * Merge review
 * Thank you! --Naypta (talk) 15:45, 4 June 2020 (UTC)
 * ✅ Created as mediawiki/extensions/CatTalk. &mdash;MarcoAurelio (talk) 21:21, 4 June 2020 (UTC)
 * ✅ Created as mediawiki/extensions/CatTalk. &mdash;MarcoAurelio (talk) 21:21, 4 June 2020 (UTC)


 * mediawiki/extensions/GlobalWatchlist
 * DannyS712
 * Merge review
 * Thanks, --DannyS712 (talk) 05:21, 11 June 2020 (UTC)
 * Just to make sure: This request is not about extension Collab(orative)Watchlist that was once called Extension:GlobalWatchlist and that we should import it from SVN, but this is for a new extension. Right? (To avoid confusion, we'd normally not allow to re-use extension names and would hence deny repo creation. But in this case, I only found use of the name “GlobalWatchlist” on wiki, not in code. In code, I could only find use of the extension's “new” 2011 name “CollabWatchlist”.) --QChrisNonWMF (talk) 06:27, 11 June 2020 (UTC)
 * Just to make sure: This request is not about extension Collab(orative)Watchlist that was once called Extension:GlobalWatchlist and that we should import it from SVN, but this is for a new extension. Right? (To avoid confusion, we'd normally not allow to re-use extension names and would hence deny repo creation. But in this case, I only found use of the name “GlobalWatchlist” on wiki, not in code. In code, I could only find use of the extension's “new” 2011 name “CollabWatchlist”.) --QChrisNonWMF (talk) 06:27, 11 June 2020 (UTC)

Also, just to double-check, as you wrote the GlobalWatchlist gadget, you really want the repo name to be  and not. Right? --QChrisNonWMF (talk) 06:27, 11 June 2020 (UTC)
 * yes, this is for a brand-new extension (didn't know there was a previous one) And yes, I want this to be under extensions - I have a grant to write an extension, see m:Grants:Project/DannyS712/Create a global watchlist extension --DannyS712 (talk) 06:49, 11 June 2020 (UTC)
 * Regardless of grant or not: Thanks for clarifying, repo created as noted below. That said ... Congrats on the grant! :-) --QChrisNonWMF (talk) 09:19, 11 June 2020 (UTC)

✅ Created as mediawiki/extensions/GlobalWatchlist

(GitHub mirror)(Phabricator mirror) --QChrisNonWMF (talk) 09:19, 11 June 2020 (UTC)


 * labs/tools/rust-hello-world
 * legoktm
 * Merge review
 * thank you! --Legoktm (talk) 10:59, 17 June 2020 (UTC)
 * ✅ Created as labs/tools/rust-hello-world
 * ✅ Created as labs/tools/rust-hello-world

(GitHub mirror)(Phabricator mirror) --QChrisNonWMF (talk) 12:58, 17 June 2020 (UTC)


 * mediawiki/extensions/WSOAuth
 * Xxmarijnw
 * Merge review
 * Please import https://github.com/WikibaseSolutions/WSOAuth/. Thanks! --Xxmarijnw (talk) 14:30, 1 July 2020 (UTC)
 * ✅ Created as mediawiki/extensions/WSOAuth
 * ✅ Created as mediawiki/extensions/WSOAuth

(GitHub mirror)(Phabricator mirror) --QChrisNonWMF (talk) 14:07, 3 July 2020 (UTC)


 * Flex Diagrams
 * Yaron_Koren
 * Merge review
 * Please import this extension's code from https://github.com/yaronkoren/FlexDiagrams . Yaron Koren (talk) 18:03, 7 July 2020 (UTC)
 * ✅ Created as mediawiki/extensions/FlexDiagrams
 * ✅ Created as mediawiki/extensions/FlexDiagrams

(GitHub mirror)(Phabricator mirror) --QChrisNonWMF (talk) 09:41, 9 July 2020 (UTC)


 * WD_HumanEdits
 * GoranSMilovanovic
 * Merge review (preferred)
 * (1) This should go under analytics/wmde/WD/ (2) please just initialize an empty repository GoranSM (talk) 08:28, 8 July 2020 (UTC)
 * ✅ Created as analytics/wmde/WD/WD_HumanEdits
 * ✅ Created as analytics/wmde/WD/WD_HumanEdits

(GitHub mirror)(Phabricator mirror) --QChrisNonWMF (talk) 09:44, 9 July 2020 (UTC)


 * mediawiki-extensions-CognitiveProcessDesigner
 * rvogel
 * Merge review
 * This is an existing, but unmaintained extension Extension:Cognitive_Process_Designer. I have not requested "ownership" in Phabricator, as the code is not hosted by WMF. I have tried to contact the author, but did not get an answer Topic:Vhw85xgumox8wn9m. I'd like to publish a bugfixed version of that extension.
 * Thanks for trying to reach the author on-wiki. To be on the safe side, I've now also reached out to him by email. I'll create the repo once he confirmed. --QChrisNonWMF (talk) 10:01, 9 July 2020 (UTC)
 * Thanks for trying to reach the author on-wiki. To be on the safe side, I've now also reached out to him by email. I'll create the repo once he confirmed. --QChrisNonWMF (talk) 10:01, 9 July 2020 (UTC)

Emailing the author did not produce a response either. So I'm assume it's really unmaintained. --QChrisNonWMF (talk) 07:47, 17 July 2020 (UTC)

✅ Created as mediawiki/extensions/CognitiveProcessDesigner

(GitHub mirror)(Phabricator mirror) --QChrisNonWMF (talk) 07:47, 17 July 2020 (UTC)


 * mediawiki/extensions/OAuthRateLimiter
 * Ppchelko, Clarakosi
 * Merge review
 * For T257607. Owners: Core Platform Team. Thank you. PPchelko (WMF) (talk) 15:51, 10 July 2020 (UTC)
 * ✅ Created as mediawiki/extensions/OAuthRateLimiter
 * ✅ Created as mediawiki/extensions/OAuthRateLimiter

(GitHub mirror)(Phabricator mirror)

I've added Ppchelko, Clarakosi and wikimedia-core-platform as owners. The latter does not contain the whole Core Platform Team, but I figured it was the best match. Please adjust as needed, or ping me if you want me to adjust things for you. --QChrisNonWMF (talk) 18:44, 12 July 2020 (UTC)


 * wikimedia/security/landing-page (I think, based on the rest of the wikimedia/security type repos)
 * reedy
 * Merge review
 * For T257830 T257832. Please use wikimedia-security as owner/etc. Please don't create a .gitreview file etc, as I think we might be pushing an import of research/landing-page to create a fork from. Thanks! --Reedy (talk) 13:57, 13 July 2020 (UTC)
 * ✅ Created as wikimedia/security/landing-page
 * ✅ Created as wikimedia/security/landing-page

(GitHub mirror)(Phabricator mirror) --QChrisNonWMF (talk) 15:01, 13 July 2020 (UTC)


 * mediawiki/extensions/OnionsPorFavor
 * legoktm and Arlolra
 * Merge review
 * thanks! --Legoktm (talk) 10:35, 14 July 2020 (UTC)
 * I'm creating repos for WMF since some years now, but this repo request clearly comes with the best name ever! I've no clue what it's gonna do, but the name gets me interested already! My Spanish is very weak, but shouldn't it be OnionsPorFavor (capital „F”) if we follow CamelCase? Respond quickly, I cannot wait to create this repo and see what it'll be about :-) --QChrisNonWMF (talk) 19:20, 14 July 2020 (UTC)
 * Hopefully it can live up to the name :D And you're right, the F should be capitalized. Thanks again! Legoktm (talk) 22:02, 14 July 2020 (UTC)
 * Hopefully it can live up to the name :D And you're right, the F should be capitalized. Thanks again! Legoktm (talk) 22:02, 14 July 2020 (UTC)

✅ Created as mediawiki/extensions/OnionsPorFavor

(GitHub mirror)(Phabricator mirror) --QChrisNonWMF (talk) 22:09, 14 July 2020 (UTC)


 * operations/envoy-ratelimiter
 * hnowlan
 * Merge review
 * This repo is for the purposes of mirroring and (short term) tagging our own releases and Docker images of the Envoy ratelimiter. Please import https://github.com/envoyproxy/ratelimit --HNowlan (WMF) (talk) 13:50, 20 July 2020 (UTC)
 * Just double-checking, since the repo-name  stands out a bit: The suggested name comes without   as second name, while many mirrors under   have   as second component. Also, we already have the repo , where it's   not  . Those two items would lead me to think that maybe   or even   would better fit the hierarchy. But I'm of course fine with a plain   too. Just double-checking since we cannot move repos in Gerrit --QChrisNonWMF (talk) 07:58, 21 July 2020 (UTC)
 * I think you're right -  is probably the best option, thanks for checking! --HNowlan (WMF) (talk) 09:30, 21 July 2020 (UTC)
 * I think you're right -  is probably the best option, thanks for checking! --HNowlan (WMF) (talk) 09:30, 21 July 2020 (UTC)

✅ Created as operations/software/envoyproxy/ratelimiter

(GitHub mirror)(Phabricator mirror) --QChrisNonWMF (talk) 21:42, 21 July 2020 (UTC)


 * mediawiki/services/wikispeech/wikispeech_mockup
 * Karl Wettin (WMSE),
 * Merge review
 * This is a request to delete the repository, not create it. I couldn't find where to go for this. Request is a continuation of requesting repo ./wikispeech-server which is the new name of the project, to which we have pushed the history from ./wikispeech_mockup. Karl Wettin (WMSE) (talk) 13:48, 22 July 2020 (UTC)
 * ✅ We normally don't delete projects, but archive them. There's a form on phabricator to kick off the process https://phabricator.wikimedia.org/maniphest/task/edit/form/33/ I've filed it at and did all the tasks directly related to the repo itself. I'm not sure of some of the other items on that ticket (E.g.: translation integration) and I'll leave them to you as I assume you know more about that than I do. If you run into issues with that, need help or whatever, feel free to ping me again. --QChrisNonWMF (talk) 20:13, 3 August 2020 (UTC)
 * ✅ We normally don't delete projects, but archive them. There's a form on phabricator to kick off the process https://phabricator.wikimedia.org/maniphest/task/edit/form/33/ I've filed it at and did all the tasks directly related to the repo itself. I'm not sure of some of the other items on that ticket (E.g.: translation integration) and I'll leave them to you as I assume you know more about that than I do. If you run into issues with that, need help or whatever, feel free to ping me again. --QChrisNonWMF (talk) 20:13, 3 August 2020 (UTC)


 * analytics/wmde/TW/template-survey
 * awight
 * Merge review
 * Please import the initial repository from git@gitlab.com:adamwight/template-survey.git --Adamw (talk) 12:17, 28 July 2020 (UTC)
 * ✅ Created as analytics/wmde/TW/template-survey
 * ✅ Created as analytics/wmde/TW/template-survey

(GitHub mirror)(Phabricator mirror)

As the repo lacks a  branch, I assume things will still shift around a bit, and I did not create a   file for now to avoid the file being in the way. If you want me to add one, just let me know. But I of course imported the repo's  branch. --QChrisNonWMF (talk) 19:29, 3 August 2020 (UTC)

Please import from https://github.com/hallowelt/mediawiki-extensions-DrawioEditor
 * mediawiki-extensions-DrawioEditor
 * rvogel
 * Merge review
 * This is an existing unmaintained extension. I have requested maintainership of this extension on the official origin some month ago: https://github.com/mgeb/mediawiki-drawio-editor/issues/19
 * This is an existing unmaintained extension. I have requested maintainership of this extension on the official origin some month ago: https://github.com/mgeb/mediawiki-drawio-editor/issues/19
 * ✅ Created as mediawiki/extensions/DrawioEditor

(GitHub mirror)(Phabricator mirror) --QChrisNonWMF (talk) 19:19, 3 August 2020 (UTC)


 * WD_referenceHunt
 * GoranSMilovanovic
 * Merge review
 * (1) This should go under analytics/wmde/WD/ (2) please just initialize an empty repository GoranSM (talk) 18:07, 30 July 2020 (UTC)
 * ✅ Created as analytics/wmde/WD/WD_referenceHunt
 * ✅ Created as analytics/wmde/WD/WD_referenceHunt

(GitHub mirror)(Phabricator mirror) --QChrisNonWMF (talk) 19:31, 3 August 2020 (UTC)


 * operations/debs/karma
 * Filippo Giunchedi
 * Merge review
 * Please inherit perms from operations/debs --Filippo Giunchedi (talk) 12:27, 31 July 2020 (UTC)
 * ✅ &mdash;MarcoAurelio (talk) 11:52, 2 August 2020 (UTC)
 * ✅ &mdash;MarcoAurelio (talk) 11:52, 2 August 2020 (UTC)


 * wikimedia-ch/wmch-infrastructure
 * Valerio Bozzolan
 * Merge review
 * If you want you can do a first push from https://gitpull.it/source/wmch-infrastructure/. This request is the follow up of T256455 (it seems not possible anymore to request a Diffusion repository). --Valerio Bozzolan (talk) 06:22, 4 August 2020 (UTC)
 * We do not have a  hierarchy in our gerrit yet. IIRC, the only other chapter we have repos for is CZ, which are under , so I wondered if we could keep things alike in the hierarchy and start with   at the top level instead of  ? Underneath that, you can pick whatever you want. For example   (so default clones would end up in a   directory as with the name you luggested),   (which would give the same duplication of the name as with the name you suggested),   (no wikimedia-ch indicator, as it's part of the hierarchy), or some other scheme. --QChrisNonWMF (talk) 05:45, 6 August 2020 (UTC)
 * Thank you. I've updated this request to reflect your suggestions. --Valerio Bozzolan (talk) 07:52, 6 August 2020 (UTC)
 * Thank you. I've updated this request to reflect your suggestions. --Valerio Bozzolan (talk) 07:52, 6 August 2020 (UTC)

✅ Created as wikimedia-ch/wmch-infrastructure

(GitHub mirror)(Phabricator mirror)

I've granted  to both Project Owners and Jenkins-bot. If that's too permissive, either dial back yourself, or let me know and I'll make it more restrictive for you. --QChrisNonWMF (talk) 10:18, 6 August 2020 (UTC)


 * operations/debs/grafana-plugins
 * Filippo Giunchedi
 * Merge review
 * Please inherit permissions from operations/debs --Filippo Giunchedi (talk) 14:40, 5 August 2020 (UTC)
 * ✅ Created as operations/debs/grafana-plugins
 * ✅ Created as operations/debs/grafana-plugins

(GitHub mirror)(Phabricator mirror) --QChrisNonWMF (talk) 05:47, 6 August 2020 (UTC)


 * analytics/wmf-product/jobs
 * bearloga
 * Merge review
 * T230743 --MPopov (WMF) (talk) 15:25, 5 August 2020 (UTC)
 * ✅ Created as analytics/wmf-product/jobs
 * ✅ Created as analytics/wmf-product/jobs

(GitHub mirror)(Phabricator mirror) --QChrisNonWMF (talk) 05:51, 6 August 2020 (UTC)


 * mediawiki/extensions/RelMicroformat
 * legoktm
 * Merge review
 * This is an extension to make it more straightforward to use various rel attributes (but much simpler than the existing Extension:LinkAttributes and Extension:Link_Attributes). Please import from https://git.legoktm.com/legoktm/RelMicroformat, thanks! --Legoktm (talk) 04:33, 17 August 2020 (UTC)
 * ✅ Created as mediawiki/extensions/RelMicroformat
 * ✅ Created as mediawiki/extensions/RelMicroformat

(GitHub mirror)(Phabricator mirror) --QChrisNonWMF (talk) 21:34, 18 August 2020 (UTC)


 * mediawiki/extensions/WikibaseManifest
 * tarrow
 * Merge review
 * Could you please import the commit history from https://github.com/wmde/WikibaseManifest/? Could you also grant permissions for +2 to ldap/wmde and the "wikidata" gerrit group? Thanks! --T Arrow (talk) 11:01, 21 August 2020 (UTC)
 * ✅ Created as mediawiki/extensions/WikibaseManifest
 * ✅ Created as mediawiki/extensions/WikibaseManifest

(GitHub mirror)(Phabricator mirror)

I've added both  and   to the project owners. That's more permissive than what you asked for. If you want to grant them only +2 and nothing more, let me know and I'll re-adjust the project settings. --QChrisNonWMF (talk) 20:37, 22 August 2020 (UTC)


 * operations/software/wmfbackups
 * Jcrespo
 * Merge review
 * These are the set of scripts split from operations/software/wmfmariadbpy to backup WMF databases and other media. It should inherit permissions from its parent, and be equivalent to the previous one.
 * ✅ Created as operations/software/wmfbackups
 * ✅ Created as operations/software/wmfbackups

(GitHub mirror)(Phabricator mirror)

It sounded like you have some code prepared already, so I left the repo completely empty to ease importing. If you want me to import code for you or create a .gitreview, just let me know. --QChrisNonWMF (talk) 07:07, 27 August 2020 (UTC)


 * wvui
 * Nikki Nikkhoui
 * Merge review
 * Repo currently exists at https://github.com/wikimedia/wvui and would like if all commit history could be transferred to gerrit. Repo should be mirrored in the existing github repo. Related phab task: T253364
 * Cool! But let's find a good place in the Gerrit hierarchy for it. I assume this is completely separate from the existing [|wikibase/vuejs-components] repo, right? This code will be used (or be useful) outside of MediaWiki as well, right? Will there be any related repos (like for further extensions, plugins, ...)? Also, does it need to live at github as  or would another name do as well? (Asking as we try to keep names in sync between GitHub and Gerrit. We have a few exceptions. But as these exceptions get in the way every now and then, we try to keep their number an a minimum) --QChrisNonWMF (talk) 07:22, 27 August 2020 (UTC)
 * Cool! But let's find a good place in the Gerrit hierarchy for it. I assume this is completely separate from the existing [|wikibase/vuejs-components] repo, right? This code will be used (or be useful) outside of MediaWiki as well, right? Will there be any related repos (like for further extensions, plugins, ...)? Also, does it need to live at github as  or would another name do as well? (Asking as we try to keep names in sync between GitHub and Gerrit. We have a few exceptions. But as these exceptions get in the way every now and then, we try to keep their number an a minimum) --QChrisNonWMF (talk) 07:22, 27 August 2020 (UTC)

Yep it is completely separate from Wikibase's vuejs-components! This code ideally would be used outside of MediaWiki for external contribution as well as usage in other projects. However, I don't believe there are any related repos at the moment. As a first use case, it is intended to be used by the MediaWiki skin Vector (which has its own repo) although it doesnt seem like this would live under the Skins hierarchy. Keeping the names in sync between gerrit and github makes sense to me, as long as all the history can move along with it. Is it not ideal to have this be a top-level repo, just named wvui?


 * There is nothing wrong with having top-level repos. It's just that with >2000 repos in our gerrit, we try to use the hierarchy to structure things to make it easier to find repos. So I just wanted to see if there is any hierarchy we could use (or should build), or if a top-level repo makes sense. The way you described it, it seems to me a top level repo should be fine, so here we go :-) --QChrisNonWMF (talk) 07:03, 2 September 2020 (UTC)

✅ Created as wvui

(Phabricator mirror)

I've granted  to Jenkins, as I hope we'll be using CI on that repo. If you plan to do otherwise, either add some group to  yourself, or let me know and I'll adjust for you. --QChrisNonWMF (talk) 07:03, 2 September 2020 (UTC)


 * Thanks a bunch !


 * mediawiki/extensions/IPInfo
 * dbarratt
 * Merge review
 * New extension for the IP Info project. Owners: Anti-Harassment Tools. See T260611 --DBarratt (WMF) (talk) 16:22, 29 August 2020 (UTC)
 * ✅ Created as mediawiki/extensions/IPInfo
 * ✅ Created as mediawiki/extensions/IPInfo

(GitHub mirror)(Phabricator mirror) --QChrisNonWMF (talk) 07:28, 31 August 2020 (UTC)


 * mediawiki/extensions/MagicNumberedHeadings
 * mah
 * Merge review (preferred)
 * I missed and 's archiving of the extension on wiki and have been maintaining it on Github for a client.  Please import changes from the github repo: hexmode/mediawiki-MagicNumberedHeadings -- ☠ MarkAHershberger ☢ (talk) ☣ 20:49, 31 August 2020 (UTC)
 * Just to have it documented: I'm skipping the "contacting the author about code transferral", as the maintainer of the repo died in 2016 :-(
 * Just to have it documented: I'm skipping the "contacting the author about code transferral", as the maintainer of the repo died in 2016 :-(

Sure, but just to avoid doubt: Will you continue to maintain the extension, or is this just meant as one-off fix for the extension? (I assume the former, but I want to have it written down somewhere :-) ) --QChrisNonWMF (talk) 07:19, 2 September 2020 (UTC)


 * : Thanks for the info on the original auythor. The extension page has already been updated and, yes, I'll maintain it. -- ☠ MarkAHershberger ☢ (talk) ☣


 * Perfect. I've unarchived the repo itself and I've added a Phabricator task for this unarchiving in case there's need to track further things for this unarchiving. I've not merged your GitHub code in, as it seems the Gerrit repo had all of your fixes from GitHub (only naming differed in variables, like   vs.   for the MagicWordFactory), and the Gerrit repo had additional translation updates etc. --QChrisNonWMF (talk) 08:09, 3 September 2020 (UTC)

✅ Unarchived as mediawiki/extensions/MagicNumberedHeadings

(GitHub mirror)(Phabricator mirror) --QChrisNonWMF (talk) 08:09, 3 September 2020 (UTC)


 * WD_CurrentEvents
 * GoranSMilovanovic
 * Merge review
 * This should go under analytics/wmde/WD/ (2) please just initialize an empty repository GoranSM (talk) 21:05, 2 September 2020 (UTC)
 * ✅ Created as analytics/wmde/WD/WD_CurrentEvents
 * ✅ Created as analytics/wmde/WD/WD_CurrentEvents

(GitHub mirror)(Phabricator mirror) --QChrisNonWMF (talk) 08:29, 3 September 2020 (UTC)


 * mediawiki/extensions/StructuredNavigation
 * SamanthaNguyen
 * Merge review
 * After spending a long time thinking, I think it would be better to have my MediaWiki extension in the same space that the Wikimedia community exists, and hopefully it's more discoverable to those who may find it beneficial. Thank you! I would like to have the code and history imported from https://github.com/neoncitylights/StructuredNavigation.
 * ✅ Created as mediawiki/extensions/StructuredNavigation
 * ✅ Created as mediawiki/extensions/StructuredNavigation

(GitHub mirror)(Phabricator mirror) --QChrisNonWMF (talk) 08:34, 3 September 2020 (UTC)


 * wikimedia-language-team-scripts
 * amire80
 * Merge review
 * Export from https://gitlab.com/amire80/wikimedia-language-team-scripts . --Amir E. Aharoni &#123;{🌎🌍🌏}} 12:10, 8 September 2020 (UTC)
 * Sure, let's import it \o/ But I'm not fully sure, where it should go in our gerrit hierarchy. A top-level  would not fit the other hierarchies in Gerrit well. Can it be that we don't have a hierarchy part for repos from the language team? I failed to find one :-( What about  ? Like ,  ,  ,   or something linke that? (Otherwise we could also use something like  ? What do you think? --QChrisNonWMF (talk) 08:48, 9 September 2020 (UTC)
 * Sure, let's import it \o/ But I'm not fully sure, where it should go in our gerrit hierarchy. A top-level  would not fit the other hierarchies in Gerrit well. Can it be that we don't have a hierarchy part for repos from the language team? I failed to find one :-( What about  ? Like ,  ,  ,   or something linke that? (Otherwise we could also use something like  ? What do you think? --QChrisNonWMF (talk) 08:48, 9 September 2020 (UTC)


 * PageMagic
 * tosfos, vedmaka
 * Merge review
 * New extension --Ike Hecht 17:17, 9 September 2020 (UTC)
 * Done. &mdash;MarcoAurelio (talk) 16:30, 10 September 2020 (UTC)
 * Done. &mdash;MarcoAurelio (talk) 16:30, 10 September 2020 (UTC)

✅

--StarHeartHunt (talk) 11:23, 12 September 2020 (UTC)
 * mediawiki/extensions/HeadScript
 * StarHeartHunt
 * Merge review
 * Please import https://github.com/StarHeartHunt/HeadScript Thanks!
 * Please import https://github.com/StarHeartHunt/HeadScript Thanks!
 * Sorry for the slow turnaround. I've asked the extension's maintainer on https://www.mediawiki.org/wiki/Topic:Vu4or0usrdr6puaq if bringing the code to gerrit and maybe passing maintainership would be ok. Am I right to assume that you'd maintain the extension? --QChrisNonWMF (talk) 07:44, 17 September 2020 (UTC)

Yes, I'll maintain it.BTW, my username is StarHeartHunt.;-)--StarHeartHunt (talk) 15:56, 18 September 2020 (UTC)

Sorry for the typo in your username. I'll give the original maintainer a bit more time to respond and if no blocker turns up, I'll create the repo on the 24th (so the original maintainer had a week to respond). --QChrisNonWMF (talk)


 * performance/mobile-synthetic-monitoring-tests
 * phedenskog
 * Merge review
 * We are setting up a new performance device lab and want to have all synthetic monitoring tests in this repo, so it is easier for everyone to add new tests. Please create an empty repo and I will add the current tests. Phedenskog (talk) 08:04, 17 September 2020 (UTC)
 * ✅ Created as performance/mobile-synthetic-monitoring-tests
 * ✅ Created as performance/mobile-synthetic-monitoring-tests

(GitHub mirror)(Phabricator mirror) --QChrisNonWMF (talk) 20:37, 20 September 2020 (UTC)