Jump to content

Talk:Developers/Maintainers

Add topic
From mediawiki.org
Latest comment: 1 month ago by SLong-WMF in topic Phabricator Tags?

Page moving/page renaming

[edit]

As far as I can see, core page moving/renaming functionality (covered by #MediaWiki-Page-rename in Phabricator) is not currently on this list. Unless it's covered under another code area that I haven't thought of (please tell me if it is!), should it be added? (If it should be added to the table, does it have a current maintainer?) Best, ‍—‍a smart kitten[meow] 18:13, 7 February 2025 (UTC)Reply

Added by @Krinkle in Special:Diff/7958088 :) ‍—‍a smart kitten[meow] 21:34, 25 October 2025 (UTC)Reply

Extension:EmailAuth

[edit]

@KHarlan (WMF) Thanks for adding EmailAuth! For completeness' sake, is there currently a WMF team taking stewardship of the EmailAuth extension (judging by the description of T390576, potentially Trust and Safety Product?), or should it be marked as unassigned (to match similar entries on the list), or something else? Best, ‍—‍a smart kitten[meow] 08:20, 10 April 2025 (UTC)Reply

Hi, we’re still figuring this out. It might take a few weeks. We could mark it as unassigned in the meantime. KHarlan (WMF) (talk) 08:49, 10 April 2025 (UTC)Reply
Thanks for the info! Maybe we could mark it as "Unassigned, stewardship currently being decided" for now? Then that could be updated as/when the extension’s stewardship is determined. Best, ‍—‍a smart kitten[meow] 09:33, 10 April 2025 (UTC)Reply
I've boldly done so. :) Quiddity (WMF) (talk) 23:07, 10 April 2025 (UTC)Reply
Hey @KHarlan (WMF), was just curious if there was an update to this? Best, ‍—‍a smart kitten[meow] 09:08, 2 July 2025 (UTC)Reply
Hey @KHarlan (WMF) & @Tgr (WMF), just wanted to check if there were any updates on EmailAuth's stewardship situation? Best, ‍—‍a smart kitten[meow] 11:51, 1 February 2026 (UTC)Reply
Hello @A smart kitten! I can confirm that Product Safety and Integrity has taken stewardship of EmailAuth. I've updated the table accordingly. RSilvola-WMF (talk) 18:07, 19 February 2026 (UTC)Reply
@RSilvola-WMF Thank you! I filed phab:T417936 as a potential follow-up regarding Phabricator's automatic team-tagging Herald rules. Best, ‍—‍a smart kitten[meow] 20:12, 19 February 2026 (UTC)Reply
(FTR, another [potential] follow-up @ gerrit:1245468 ‍—‍a smart kitten[meow] 21:48, 27 February 2026 (UTC))Reply

OOUI stewardship

[edit]

Developers/Maintainers currently lists the Design System Team as stewarding OOUI (oojs-ui). However, if I understand correctly, that team is now defunct and has been superseded by the Codex Steering Committee.
OOUI's stewardship information should therefore presumably be updated, but I don't know whether the Codex Steering Committee has also taken over the DST's former stewardship of OOUI, or if it's been taken on by another team (or if OOUI is now unstewarded).

Pinging CCiufo-WMF in case you might know :) Best, ‍—‍a smart kitten[meow] 19:25, 18 July 2025 (UTC)Reply

Hey @A smart kitten, this is a good catch -- thanks for flagging it. You're right that the Design System team should not be listed as owners anymore because the team doesn't exist, however long-term ownership for OOUI is still being figured out. I've listed the Codex Steering Committee as interim owners as the ones who will make the recommendation for future ownership. I've updated the table to reflect this. CCiufo-WMF (talk) 14:35, 28 July 2025 (UTC)Reply

WikiHiero

[edit]

Hey JDrewniak (WMF)! Given that your edit summary didn't mention it (but did mention the other components), I just wanted to check that it was intentional for Reader Experience to also take stewardship of (previously-unassigned) Extension:WikiHiero ? Just thought I should check, in order to avoid any potential maintainer-related confusion in the future if it wasn't intended :) Best, ‍—‍a smart kitten[meow] 13:33, 22 July 2025 (UTC)Reply

Merging from Wikimedia Product/Component responsibility

[edit]

@MusikAnimal (WMF) Thanks for getting this merge started!! I'm extremely happy to see this happening - thank you for doing the work to start it :)

As one point of feedback, to me it currently feels like maybe the new SLA information should be more specifically connected to a component's steward than to the (whole) component itself. E.g., the new table-row for Extension:3D kinda makes it seem (to me) like non-security patches won't be reviewed for that extension in general; when (IIUC) this is just the SLA that the Structured Data team has committed itself to as code stewards; and there's nothing to stop volunteers (or, I guess, staff members from other teams) from code-reviewing any patches that're submitted to that extension's repo.

(But seriously, thanks for getting the merge started :) /gen) Best, ‍—‍a smart kitten[meow] 19:33, 22 July 2025 (UTC)Reply

Thanks! Great point, indeed. I will remove the SLA column and nest that information in the "Steward" column instead. MusikAnimal (WMF) (talk) 20:17, 22 July 2025 (UTC)Reply
Yes Done, and noting that I removed the 14-day SLA for TimedMediaHandler as it has no code steward. MusikAnimal (WMF) (talk) 20:29, 22 July 2025 (UTC)Reply
I should ping @Brooke Vibber (WMF) who is listed as the maintainer. Did that SLA apply to you, Brooke? If so, I can add it to the maintainer column instead. MusikAnimal (WMF) (talk) 20:53, 22 July 2025 (UTC)Reply

Changes from Web -> Reader Growth/Reader Experience

[edit]

@GZWDer, do you mind if I ask whether you checked with (a member of) the Reader Growth/Reader Experience teams before making these four edits: [1] [2] [3] [4]? I'm only asking as - in my opinion - I don't think that we should be documenting teams as being the stewards/maintainers of certain components unless those teams have confirmed that they are indeed the stewards/maintainers of those components (given that this page is, as far as I'm aware, the authoritative/canonical list of which teams are responsible for what pieces of software). IMO, the problem with saying something like "presumed, revert if I am wrong" for this page is that e.g. the people that might know that it's wrong may well not be (and wouldn't be expected to be) actively watching this page for changes. Best, ‍—‍a smart kitten[meow] 11:22, 26 October 2025 (UTC)Reply

For chart, see phab:T399613#11030569. GZWDer (talk) 11:53, 26 October 2025 (UTC)Reply
@GZWDer Thanks for that link; though personally I'm not sure that the Reader Growth team's Phab project being added to a task for the Chart extension is (on its own) enough to say that the team is definitely that extension's steward (as the Reader Growth team may have e.g. just had an interest in that particular task). (As another example I'm aware of — in phab:T405760#11246716, the Reader Growth team's project was added to a TimedMediaHandler task, but I'm not personally aware that they steward that extension (and Developers/Maintainers currently lists it as being unassigned).)
If there wasn't confirmation from Reader Growth/Reader Experience regarding these updates, do you mind if I undo (most of) those changes, but mention within the relevant field for each component that the information is needing an update?/genq Best, ‍—‍a smart kitten[meow] 22:15, 26 October 2025 (UTC)Reply
Noting that I partially undid edits [1], [2] & [4] linked above. I left edit [3] for now, as it just made changes to the 'Maintainers', 'Consulted' & 'Informed' fields, rather than the 'Steward' field (though imo it still would've been better to check with the teams before adding them there). I added a note that the (now-reinstated) references to the Web team need updating, and I'll leave a note in T400607 & T401435 about them. Best, ‍—‍a smart kitten[meow] 18:05, 6 November 2025 (UTC)Reply

Re the out-of-date paths

[edit]

@SWilson (WMF), re Special:Diff/8058344; FYI, the reason I kept the out-of-date paths in my previous edit was to keep the Gerrit search links working for previous patches to a given component. (I'm not gonna revert you bc I don't feel that strongly about it - do with this information & the edit summary for my previous edit what you will :p) Best, ‍—‍a smart kitten[meow] 18:33, 6 December 2025 (UTC)Reply

Phabricator Tags?

[edit]

For the extensions and pieces that have owners, would it make sense to add in a line with what tag to use on Phabricator to bring something to the maintainer's attention? SLong-WMF (talk) 19:09, 2 April 2026 (UTC)Reply