Jump to content

Gerrit/New repositories/Requests

From mediawiki.org
Request new repository


/mediawiki/extensions/LinkCards

[edit]
Extension /mediawiki/extensions/LinkCards
Developer samwilson
Preferred model Merge review (default)
Phabricator project MediaWiki-extensions-LinkCards

Please import https://github.com/Wikimedia-AU/MediaWiki-extension-LinkCards/

--Sam Wilson 02:02, 5 July 2024 (UTC)[reply]

Yes Done Created as mediawiki/extensions/LinkCards

(GitHub mirror)(Phabricator mirror)

The main branch got renamed to master, as the main branch is prohibited for extensions

--QChrisNonWMF (talk) 13:08, 5 July 2024 (UTC)[reply]

@QChrisNonWMF: Great, thanks! Sam Wilson 13:13, 5 July 2024 (UTC)[reply]

mediawiki/extensions/UserVerification

[edit]
Extension mediawiki/extensions/UserVerification
Developer thomas-topway-it
Preferred model Merge review (default)
Phabricator project Phabricator project, or create a new Phabricator project.

Please create the gerrit repository. Thank you in advance!


UserVerification provides a framework to manage verified users through different methods and to restrict performing actions to verified or email-authenticated users.


--Thomas-topway-it (talk) 05:44, 8 July 2024 (UTC)[reply]

Yes Done Created as mediawiki/extensions/UserVerification

Mirrors: GitHub and Phabricator


Antoine "hashar" Musso (talk) 16:09, 8 July 2024 (UTC)[reply]

/extensions/Analytics

[edit]
Extension /extensions/Analytics
Developer Sophivorus
Preferred model Merge review (default)
Phabricator project Phabricator project, or create a new Phabricator project.

Thanks! Sophivorus (talk) 12:31, 20 July 2024 (UTC)[reply]

Hi Sophivorus, I feel like Analytics might be too generic and not specific enough, maybe you can come up with a more specific name? What would be the extension about? It could help to have a description for it when creating the repository. Antoine "hashar" Musso (talk) 10:30, 22 July 2024 (UTC)[reply]
@Hashar Hi! The extension adds a special page that displays edit and traffic analytics for the wiki, as well as for specific pages. I'm still developing it but you can already see it at https://www.appropedia.org/Special:Analytics I think the extension is actually quite general so a general name may be appropriate, but maybe you can suggest a better one? Kind regards, Sophivorus (talk) 12:12, 22 July 2024 (UTC)[reply]
@Hashar I think I would use such an extension. Want (talk) 13:17, 22 July 2024 (UTC)[reply]
@Sophivorus: While we do have some extensions with unspecific names, I agree with Hashar that the name is quite broad. Since your extensions is about showing metrics, would AnalyticsDashboard, AnalyticsPages, MetricsDisplay or something along these lines work as extension name for you? --QChrisNonWMF (talk) 07:53, 23 July 2024 (UTC)[reply]
@QChrisNonWMF @Hashar AnalyticsDashboard and MetricsDisplay seem inappropriate because the extension now includes a Lua library that exposes the data to Lua modules and templates, and REST API endpoints that expose the data to other scripts. AnalyticsPages (or PageAnalytics) is also limited because the extension can output analytics not only for pages, but for categories and for the site as a whole. I guess it could be named "WikiAnalytics". Seems unnecessary to me, but would that make any difference to you? (please let me know your thoughts before creating any repo) In the meantime, I started documenting at Extension:Analytics and uploaded the code to https://github.com/Appropedia/Analytics Ping to @Want and @Willyedoo because they showed interest in the extension. Cheers! Sophivorus (talk) 15:19, 31 July 2024 (UTC)[reply]
@Sophivorus: Sorry for the delay and thanks for your response. Given your explanation and also that we have other rather generic repo names, I'm fine with mediawiki/extensions/Analytics.
@Hashar: Since you also raised concerns, what do you think about the above explanation --QChrisNonWMF (talk) 12:11, 8 August 2024 (UTC)[reply]

Since there was no other reply to Sophivorous message from more than 10 days ago, I've been bold and went ahead with mediawiki/extensions/Analytics. --QChrisNonWMF (talk) 20:16, 11 August 2024 (UTC)[reply]

Yes Done Created as mediawiki/extensions/Analytics

(GitHub mirror)(Phabricator mirror)

I've imported the code from Appropedia's GitHub repo, but the main branch got renamed to master, as the main branch is prohibited for extensions --QChrisNonWMF (talk) 20:16, 11 August 2024 (UTC)[reply]

Sorry I was in vacations in August and could not reply. Thank you for having created and imported the repository! Antoine "hashar" Musso (talk) 18:44, 14 September 2024 (UTC)[reply]


mediawiki/extensions/EmailNotifications

[edit]
Extension mediawiki/extensions/EmailNotifications
Developer thomas-topway-it
Preferred model Merge review (default)
Phabricator project Phabricator project, or create a new Phabricator project.

Please create the gerrit repository. Thank you in advance!

EmailNotifications allows to notify user groups with the content of an article, based on a specific frequency. It also supports Symfony mailer.


--Thomas-topway-it (talk) 18:35, 27 July 2024 (UTC)[reply]

@Thomas-topway-it: Given the extension's name, I would not have guessed the functionality. Since you describe it as periodically sending article content. Would something like PeriodicArticleEmails, or PeriodicArticleSender be more descriptive? --QChrisNonWMF (talk) 12:21, 28 July 2024 (UTC)[reply]
@QChrisNonWMF the description I have provided was only a sketch and may not yet reflect the features of the extension. The extension aims to offer to users an interface to manage notifications (mainly email notifications) where the article content is an easy and non-exhaustive way to set the content of the notification. It would be great if you can use the proposed name since it is deliberately generic insofar as I plan to use the extension as a requirement for a number of extensions (namely Extension:UserVerification from which I plan to move the mailer interface) and can be used as an alternative or replacement for Extension:SwiftMailer (which makes indeed use of the hook onAlternateUserMailer). Thanks a lot Thomas-topway-it (talk) 14:34, 28 July 2024 (UTC)[reply]
Thank you for the explanation! Then, let's move forward with the name you suggested :-) --QChrisNonWMF (talk) 19:54, 28 July 2024 (UTC)[reply]

Yes Done Created as mediawiki/extensions/EmailNotifications

(GitHub mirror)(Phabricator mirror) --QChrisNonWMF (talk) 19:54, 28 July 2024 (UTC)[reply]

mediawiki/extensions/NotifyMe

[edit]
Extension mediawiki/extensions/NotifyMe
Developer rvogel
Preferred model Merge review (default)
Phabricator project -

Please set gerrit group bluespice as owner.


--Osnard (talk) 07:00, 31 July 2024 (UTC)[reply]

Please put on halt. I just found out that MediaWiki\Extension\Notifications namespace is already in use by Extension:Echo. We will most likely need to rename this extension.

--Osnard (talk) 13:19, 1 August 2024 (UTC)[reply]

Renamed to MediaWiki\Extension\NotifyMe. Please proceed. Thanks!

--Osnard (talk) 12:54, 3 September 2024 (UTC)[reply]

Yes Done Created as mediawiki/extensions/NotifyMe

(GitHub mirror)(Phabricator mirror) --QChrisNonWMF (talk) 13:07, 4 September 2024 (UTC)[reply]

mediawiki/extensions/CommunityConfigurationExample

[edit]
Extension mediawiki/extensions/CommunityConfigurationExample
Developer Growth Team
Preferred model Merge review (default)
Phabricator project MediaWiki-extensions-CommunityConfiguration

Requesting this repository is an outcome of T373114 Enable CommunityConfiguration Example in CI. The plan is to have it enabled in CI, where it would be depending on CommunityConfiguration and CommunityConfiguration would be depending on it. And also, the plan is to have it enabled on a beta-wiki, but NOT in production.

We will probably migrate the content of https://gitlab.wikimedia.org/repos/growth/community-configuration-example there and then largely replace that with what is currently in https://gerrit.wikimedia.org/r/plugins/gitiles/mediawiki/extensions/CommunityConfiguration/+/refs/heads/master/example/.

If possible, it would be great if we could initialize the repository with code that is currently on GitLab: https://gitlab.wikimedia.org/repos/growth/community-configuration-example, but if not, then also alright. That code will be going through some sweeping changes anyway.

--MGrosse-WMF (talk) 10:12, 10 September 2024 (UTC)[reply]

Yes Done Created as mediawiki/extensions/CommunityConfigurationExample

(GitHub mirror)(Phabricator mirror)

The main branch got renamed to master, as the main branch is prohibited for extensions --QChrisNonWMF (talk) 08:36, 11 September 2024 (UTC)[reply]

Thank you! 🙏 MGrosse-WMF (talk) 12:11, 11 September 2024 (UTC)[reply]

design/codex-php

[edit]
Extension design/codex-php
Developer Eric Gardner (egardner@wikimedia.org)
Preferred model Merge review (default)
Phabricator project Codex

Requesting a new Gerrit repo for the Codex PHP project. This repo should have the same permissions model as `design/codex` (the same people should have +2 rights in both codebases).

This project will be maintained by the Design System Team with participation from volunteer developers, especially Doğu Abaris (abaris@null.net) the initial author of this code.

Once a repo is created, I will submit a patch to `integration/config` to get basic PHP CI tasks set up here.

--EGardner (WMF) (talk) 19:02, 23 September 2024 (UTC)[reply]

Yes Done Created as design/codex-php

(GitHub mirror)(Phabricator mirror) --QChrisNonWMF (talk) 22:21, 24 September 2024 (UTC)[reply]

Thanks! EGardner (WMF) (talk) 21:24, 26 September 2024 (UTC)[reply]
I have a few follow-up questions if you have a moment–
  1. Is it possible to make the default branch `main` instead of `master`, the same as the `design/codex` repo?
  2. I need some help with CI/Jenkins configuration and I'm not sure where to go. I'd like to set up a standard workflow similar to what exists in most MediaWiki extensions, where PHPCS and PHPUnit tests are run automatically, and +2 in code review causes a patch to be merged. I just +2ed a test commit but nothing happened.
I understand that I need to submit a patch in the integration/config to set up CI jobs, but I thought that +2ing a patch would merge it regardless, so maybe there is something I'm missing. EGardner (WMF) (talk) 22:46, 26 September 2024 (UTC)[reply]
If there is no CI setup, changes won't get merged automatically upon voting CodeReview+2.
And about using PHPUnit/PHPCS ... I've started a corresponding Gerrit Change let's continue there.
I've updated the default branch to main for now. But some parts of our Jenkins setup rely on the master branch. So I'm not sure, if we'll have to revert. QChrisNonWMF (talk) 10:13, 27 September 2024 (UTC)[reply]
@QChrisNonWMF, it looks like the default branch on GitHub is master. Can we update it to main please? Doğu (talk) 00:01, 28 September 2024 (UTC)[reply]
@Doğu: Whoops. I missed GitHub. I'm sorry. I've now updated the default branch in GitHub. --07:51, 28 September 2024 (UTC)[reply]

mediawiki/skins/Freo

[edit]
Extension mediawiki/skins/Freo
Developer samwilson
Preferred model Merge review (default)
Phabricator project Phabricator project, or create a new Phabricator project.

New skin for freopedia.org. No existing repo to import, this is a new project. —Sam Wilson 01:08, 30 September 2024 (UTC)[reply]

Yes Done Created as mediawiki/skins/Freo

(GitHub mirror)(Phabricator mirror) --QChrisNonWMF (talk) 07:10, 30 September 2024 (UTC)[reply]

@QChrisNonWMF: Thanks! Sam Wilson 09:17, 30 September 2024 (UTC)[reply]

operations/software/opensearch/plugins

[edit]
Extension operations/software/opensearch/plugins
Developer ebernhardson
Preferred model Merge review (default)
Phabricator project Discovery-Search

This is intended as a replacement for renaming the operations/software/elasticsearch/plugins repo. The underlying software is switching to opensearch and we think it would be too confusing going forward for the plugins to be in a mis-named repo.

Intending to import the history from the old repo into the new one, and archive the old once once we finish migration.

--EBernhardson (WMF) (talk) 18:02, 10 October 2024 (UTC)[reply]

Yes Done Created as operations/software/opensearch/plugins

(GitHub mirror)(Phabricator mirror) --QChrisNonWMF (talk) 20:30, 11 October 2024 (UTC)[reply]

/mediawiki/extensions/CookieConsent

[edit]
Extension /mediawiki/extensions/CookieConsent
Developer xxmarijnw
Preferred model Merge review (default)
Phabricator project Phabricator project, or create a new Phabricator project.

Please import https://github.com/WikibaseSolutions/CookieConsent.


--Xxmarijnw (talk) 15:02, 29 October 2024 (UTC)[reply]

Yes Done Created as mediawiki/extensions/CookieConsent

(GitHub mirror)(Phabricator mirror) --QChrisNonWMF (talk) 14:02, 30 October 2024 (UTC)[reply]

mediawiki/libs/string-utils

[edit]
Extension mediawiki/libs/string-utils
Developer abaris (gerrit) abaris@null.net
Preferred model Merge review (default)
Phabricator project Phabricator project, or create a new Phabricator project.

Please see: T88484

--Doğu (talk) 13:45, 5 November 2024 (UTC)[reply]

@Doğu: Most (but not all) repos under mediawiki/libs use CamelCase. So I wondered, whether mediawiki/libs/StringUtils would work for you as well? (If not, I'll create it with the name you suggested) --QChrisNonWMF (talk) 10:16, 6 November 2024 (UTC)[reply]

@QChrisNonWMF, mediawiki/libs/StringUtils works well. I might also need mediawiki/libs/UUID. Doğu (talk) 11:31, 6 November 2024 (UTC)[reply]
@Doğu: Ok, I'll run with mediawiki/libs/StringUtils then. And about the UUID repo ... sure. Once the "I might (...) need" becomes "I need", let me know and we'll get it created :-) --QChrisNonWMF (talk) 22:02, 7 November 2024 (UTC)[reply]
@QChrisNonWMF, Yes, I need it to push initial code :) Doğu (talk) 22:04, 7 November 2024 (UTC)[reply]
@Doğu: See the below request for mediawiki/libs/UUID --QChrisNonWMF (talk) 22:51, 7 November 2024 (UTC)[reply]

Yes Done Created as mediawiki/libs/StringUtils

(GitHub mirror)(Phabricator mirror) --QChrisNonWMF (talk) 22:02, 7 November 2024 (UTC)[reply]

mediawiki/libs/UUID

[edit]
Extension mediawiki/libs/UUID
Developer abaris (gerrit) abaris@null.net
Preferred model Merge review (default)
Phabricator project Phabricator project, or create a new Phabricator project.

Per mediawiki/libs/string-utils request above. --QChrisNonWMF (talk) 22:49, 7 November 2024 (UTC)[reply]

Yes Done Created as mediawiki/libs/UUID

(GitHub mirror)(Phabricator mirror) --QChrisNonWMF (talk) 22:49, 7 November 2024 (UTC)[reply]

mediawiki/libs/Message

[edit]
Extension mediawiki/libs/Message
Developer abaris (gerrit) abaris@null.net
Preferred model Merge review (default)
Phabricator project task T227447 comment 10351271


--Doğu (talk) 16:24, 24 November 2024 (UTC)[reply]

Yes Done Created as mediawiki/libs/Message

(GitHub mirror)(Phabricator mirror) --QChrisNonWMF (talk) 15:42, 25 November 2024 (UTC)[reply]

mediawiki/extensions/PagePort

[edit]
Extension mediawiki/extensions/PagePort
Developer Labster
Preferred model Merge review (default)
Phabricator project mediawiki-extensions-PagePort once it exists, task T381557

Please import from https://github.com/WikiTeq/PagePort

This repo was already approved and created back in 2021 as an empty repository, and belongs to the extension-PagePort group which is all correct. However, no one actually pushed the code over there. I would prefer not to have to squash 50 commits, so I'm hoping someone here has push access.

--BrentLaabs (talk) 09:53, 5 December 2024 (UTC)[reply]

Yes Done I've merged in the GitHub repo for you. --QChrisNonWMF (talk) 11:31, 6 December 2024 (UTC)[reply]

mediawiki/libs/ParamValidator

[edit]
Extension mediawiki/libs/ParamValidator
Developer abaris (gerrit) abaris@null.net
Preferred model Merge review (default)
Phabricator project task T382170


--Doğu (talk) 19:53, 13 December 2024 (UTC)[reply]

Yes Done Created as mediawiki/libs/ParamValidator

(GitHub mirror)(Phabricator mirror) --QChrisNonWMF (talk) 16:37, 14 December 2024 (UTC)[reply]

Retrieved from "https://www.mediawiki.org/w/index.php?title=Gerrit/New_repositories/Requests&oldid=6932483"