Ladsgroup added a comment.
In T114772#6509151 <https://phabricator.wikimedia.org/T114772#6509151>, @WMDE-leszek wrote: > @Addshore @Ladsgroup: > Having look at this task with developers we were not clear about certain details which are probably obvious but we didn't find answers just looking at this task. Incomplete list below: > > - While the task provides quite detailed outline of the contract of the requested service, we didn't find any details on where/how the service should be used. I suspect it might be in one of 200+ linked tasks, but I didn't get to digest them. More than everything, it's about wikis that have a different dbname and dns record. For example, be_x_oldwiki is actually be-tarask.wikipedia.org and editors of this wiki have to enter be_x_oldwiki in wikidata to be able to enter their articles (while in paper, they might not even know what be_x_old is). This is also blocks renaming further wikis (e.g. zh-classical.wikipedia.org to lzh.wikipedia.org). It gets even worse as the language code for zh-classical is lzh (in termbox for example) but the sitelinks has to stay zh_classical if we rename the wiki and don't fix this issue in wikidata. Here's an example of a bug this task would tackle T112426: [Bug] Querying Wikipedia for langlinks doesn't work for be-tarask, but works for be-x-old <https://phabricator.wikimedia.org/T112426> > - It is unclear whether the said service should be implemented in Wikibase (with further possibility of upstreaming to MediaWiki later on), or should it be implemented straight away in MediaWiki? I personally think it should be in Wikibase, our narrow usecase for this is that we would have a php service in data access that takes a language code and a sitelink group and returns a dbname for it e.g. for ("fa", "wikipedia") returning "fawiki", "be-tarask", "wikipedia" returning "be_x_oldwiki" and "de", "wikiquote" returning "dewikiquote" (I assume exceptions like be-x-old to be-tarask would be configurable hard coded values). This would simplify and centralize the logic that have spread out too. > - I personally didn't catch how this task connects to Wikibase/Wikidata. Those "Sites" seem to me like a generic MediaWiki concept, and the service as a generic MediaWiki thing. Is this correct? A comment above (T114772#6214993 <https://phabricator.wikimedia.org/T114772#6214993>) mentions this blocking wiki renames, which, in my ignorance, sounds to me like something WMF does, not Wikidata/WMDE. It's blocking renaming wikis due to renamed wikis not being accessible under new name in Wikidata. Fixing that I assume is our job. > - Rephrasing the above: Why WMDE should implement this and not the relevant WMF team? What is the WMDE's use case for this service? As I explained above, this is an issue with wikibase codebase that assumes there is strict mapping between language code and db name (e.g. fa,wikipedia -> fawiki) while such thing doesn't exist in reality 100% of the time (be-tarask, wikipedia -> be_x_oldwiki) > I am not sure if i didn't any other essential question. Possibly @Pablo-WMDE @Lucas_Werkmeister_WMDE @Michael who were active in the conversation on this remember something extra. HTH TASK DETAIL https://phabricator.wikimedia.org/T114772 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Ladsgroup Cc: Addshore, Lucas_Werkmeister_WMDE, Pablo-WMDE, Michael, Ladsgroup, Lydia_Pintscher, WMDE-leszek, darthmon_wmde, hoo, Liuxinyu970226, StudiesWorld, Aklapper, daniel, Akuckartz, Nandana, lucamauri, Lahi, Gq86, GoranSMilovanovic, QZanden, LawExplorer, _jensen, rosalieper, Scott_WUaS, Jonas, Wikidata-bugs, aude, Mbch331
_______________________________________________ Wikidata-bugs mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
