| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Declined | Aklapper | T103465 Global user pages should propagate to phabricator profiles | |||
| Declined | None | T103466 Phabricator profiles should be localizable | |||
| Resolved | • Nikerabbit | T225 Use translatewiki.net to localize Phabricator | |||
| Resolved | Aklapper | T136071 Get Phabricator i18n ready for translatewiki.net | |||
| Resolved | • mmodell | T184459 Test phabricator translations on phab.wmflabs.org |
Event Timeline
To have a unified profile across Wikimedia sites, so that if I would like to add something new then I don't have to add it by hand in a global profile and in a phabricator profile.
I see. That makes sense, but your Wikimedia user profile is only one click away from your Phabricator user profile via the "MediaWiki User" link and I don't think that profile content changes happen so often that this would justify writing custom code (to parse and embed global userpage content in Phabricator) and maintaining that custom code.
Hence proposing status declined.
Where a feature requires too much effort, is it not usually given low priority? So that if a volunteer wants to write such code, they have an opportunity.
Already reflected by the priority in this task. Also see mw:Phabricator/Project management#Setting task priorities and its discussion page.
[...]
I don't think that profile content changes happen so often that this would justify writing custom code (to parse and embed global userpage content in Phabricator) and maintaining that custom code.
Hence proposing status declined.
If someone volunteers to write such code and maintain it, it is my understanding that they can do so.
As this is a valid feature request, please do not decline it. Lower the priority and leave it open.
Phabricator user profiles already include a link to the user page in mediawiki.org, which should already offer the global profile unless the user has created a specific page.
I don't see much usefulness in this feature. A significant amount of developer work (paid or volunteer, it doesn't matter) put on a patch that we should maintain, only to save one click to whoever is interested in user profile info.
I'm declining per T103465#1396064 and the disproportional code maintenance and deployment costs we'd have for every update, in order to just save one single mouse click.