For T218639: Make language-data installable as a proper library the language team developers need access to the wikimedia namespace in packagist to create wikimedia/language-data.
I'm requesting access for:
This may be the wrong place to request it, but after searching wikitech/officewiki/phabricator I found exactly zero documentation about it. One page in officewiki shows that SRE has been asked to do this before.
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| mariadb: Add db2137 to s4+s5 | operations/puppet | production | +10 -4 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T213072 Language tools maintenance intervention: Improve processes for i18n support to be more fluent | |||
| Open | None | T32956 Make ResourceLoader a standalone library | |||
| Open | None | T190129 Consolidate language metadata into a 'language-data' library and use in MediaWiki | |||
| Resolved | abi_ | T218639 Make language-data installable as a proper library | |||
| Resolved | Request | bd808 | T252987 Requesting access to wikimedia namespace in packagist |
Packagist does not have an "org account" concept to make multi-user access easy (https://github.com/composer/packagist/issues/461). Instead we have a shared username and password for both https://packagist.org/users/mediawiki and https://packagist.org/users/wikimedia. These were created to "own" the 'mediawiki' and 'wikimedia' namespaces at Packagist following Packagist making it possible at all to control what is admitted to a namespace.
There are two paths forward for T218639: Make language-data installable as a proper library which seems to be the inspiration for this request:
@Nikerabbit which of these is more appealing to you? Do you want a new hat or just to fix the problem you have today?
Regardless of which path @Nikerabbit chooses, this task is a great reminder that we have documentation gaps. This minor essay should really be on Wikitech or mediawiki.org somewhere that folks can find along with clear docs on how to either ask for a new package registration or access to the shared password (and ideally what responsibilities come along with the password access).
Claiming this so that the fine folks triaging SRE-Access-Requests know that I'm on the hook for working things out one way or the other.
Thanks @bd808! It doesn't sound like there's presently anything for the SRE clinic-duty person to do here, so I'm optimistically removing SRE-Access-Requests, but feel free to add it back if you need anything from me (or subsequent clinicians).
I can confirm we have access to both the mediawiki and wikimedia account passwords in pwstore (in the file packagist.org) so it's possible for us to be in the loop here by sharing those passwords with the appropriate folks, but we'd want some kind of criteria documented so that we know who that is (and ideally a written procedure for sharing the password securely). SRE_Clinic_Duty#Access_requests would be a good place to add, or link, those instructions.
I went ahead and did this part while I was thinking about it: https://packagist.org/packages/wikimedia/language-data. I also setup the webhook so that Packagist will be notified of updates to the repo.
@Nikerabbit which of these is more appealing to you? Do you want a new hat or just to fix the problem you have today?
It seems that option 2 allows us to do everything we need.
Change 597524 had a related patch set uploaded (by Kormat; owner: Kormat):
[operations/puppet@production] mariadb: Add db2137 to s4+s5
Change 597524 merged by Kormat:
[operations/puppet@production] mariadb: Add db2137 to s4+s5
Change 598736 had a related patch set uploaded (by Kormat; owner: Kormat):
[operations/puppet@production] mariadb: Add db2138 to s2+s4