Wikidata:Property proposal/Wikimedia Phabricator project

Wikimedia Phabricator project PHID

Originally proposed at Wikidata:Property proposal/Generic

   On hold

Description	PHID of the Wikimedia Phabricator project for the subject
Data type	External identifier
Example 1	Wikibase Repository (Q21679301) → vumw5jyyw4r3fv52k34y
Example 2	Extension:Wikibase Client (Q21679293) → 46yqqwzqvnxmbabmz3tc
Example 3	Pywikibot (Q15169668) → orw42whe2lepxc7gghdq
Formatter URL	https://phabricator.wikimedia.org/maniphest/?project=PHID-PROJ-$1&statuses=open()&order=newest#R
See also	issue tracker URL (P1401), Wikimedia Incubator URL (P9748)

Motivation

Most MediaWiki software uses https://phabricator.wikimedia.org/ as its issue tracker. Currently the issue trackers are linked via issue tracker URL (P1401), which is however a bit messy since there are many different ways to link to a project on Phabricator:

• by project slug, e.g: https://phabricator.wikimedia.org/tag/pywikibot/
• by numeric id, e.g: https://phabricator.wikimedia.org/project/board/87/
• by PHID, e.g: https://phabricator.wikimedia.org/maniphest/?project=PHID-PROJ-orw42whe2lepxc7gghdq

While project slugs are the most human-friendly of these, project slugs can change and one project can have multiple slugs, making them suboptimal for a Wikidata identifier property. So the choice remains between the numeric ids and the PHIDs. I think PHIDs are the clear winner because the Phabricator API to search tasks maniphest.query only accepts PHIDs for projects and we don't want to force data consumers to do a project.query lookup to translate the id to the PHID every time they want to query the tasks of a project.

How to find the PHID? If you are at a project page, click on Open Tasks and then you can find the PHID in the URL.

A bot could be written to import these identifiers from https://www.mediawiki.org/, because it has the project slugs in various templates:

• mw:Template:Ptag
• mw:Template:Extension#phabricator
• mw:Template:Wikimedia engineering project information
• mw:Template:Software

Cheers, --Push-f (talk) 16:09, 21 November 2022 (UTC)

Discussion

• julle (talk) wd-Ryan (talk/edits) Arlo Barnes (talk) WT20 (talk) Zblace (talk) applsdev RampantSpirit (talk)
  Notified participants of WikiProject Websites. --Push-f (talk) 16:12, 21 November 2022 (UTC)
• Note the project name is not stable, but the ID is. Consider linking to e.g. https://phabricator.wikimedia.org/project/profile/114/ --GZWDer (talk) 17:13, 21 November 2022 (UTC)

  Thanks for bringing that up! I have updated this proposal to use PHIDs instead of project slugs (see the updated motivation for my reasoning). --Push-f (talk) 17:49, 21 November 2022 (UTC)

•  Support -wd-Ryan (Talk/Edits) 18:05, 21 November 2022 (UTC)
•  Comment Would there be a way to use a prefix to make this useful more generically, for other Phab/Phorge instances? Arlo Barnes (talk) 18:58, 21 November 2022 (UTC)

  Yes we could of course introduce more generic properties e.g:

  • Wikibase Repository (Q21679301)issues tracked in (P01)Wikimedia Phabricator (Q42156541)Phabricator project PHID (P02)vumw5jyyw4r3fv52k34y
  • Wikimedia Phabricator (Q42156541)URL (P2699)https://phabricator.wikimedia.org/
  • Wikimedia Phabricator (Q42156541)software engine (P408)Phabricator (Q16509734)

  And then making use of my proposed serves resource scheme:

  • Phabricator (Q16509734)serves resourceissue list (Q03)URL suffix formatter/maniphest/?project=PHID-PROJ-$1&statuses=open()&order=newest#RURL parameterPhabricator project PHID (Q04)

  And the new property would have: Phabricator project PHID (P02)Wikidata item of this property (P1629)Phabricator project PHID (Q04).

  This would be flexible enough to be used for any Phabricator instance. Figuring out the issue tracker URL (P1401) for Wikibase Repository (Q21679301) from these statements however is a bit more involved.

  I think that could be addressed by introducing a bot that automatically derives the issue tracker URL (P1401) from these statements and updates e.g. Wikibase Repository (Q21679301) accordingly when they are changed.

  --Push-f (talk) 10:27, 23 November 2022 (UTC)

•  Support. Nomen ad hoc (talk) 07:05, 22 November 2022 (UTC).
•  Comment Not that I oppose this, but aren't wikimedia projects moving from Phabricator to Gitlab sometime soon? ArthurPSmith (talk) 19:27, 29 November 2022 (UTC)

  No, the plan is to move the code review from Gerrit to GitLab, Phabricator will as far as I know be kept for issue tracking, see phab:T264231, phab:T265617 and mw:GitLab/Roadmap. --Push-f (talk) 20:03, 29 November 2022 (UTC)

• On hold I want to know opinions if we should instead introduce a more general property that can also be used for other Phabricator instances, as suggested by Arlo Barnes above. --Push-f (talk) 20:06, 29 November 2022 (UTC)