Hi David!
I've seen in a comment you've been using yarn besides npm. I'm investigating the possibility of using Pnpm and Yarn 2, currently using mostly pnpm for development.
Both can co-exist with npm, thus there's no migration pressure. The only thing I had to do is to add some missing peer dependencies and custom resolutions.
Is there an interest in making these tools an option on the developer side in the future?
Interesting! I used Yarn for a hot minute, but then npm added package-lock.json and that was really the only reason I was using Yarn in the first place. I think it's good to have competition for npm (and I'm glad deno decided to not include a package manager). I hope these improvements make their way back into npm.
It seems like the task is a little stalled; who is able to setup Wikimedia wikis on phabricator ? Or anyone I should subscribe to the task ?
To answer your original question, anyone can setup a Cloud VPS, once created, would just need to install MediaWiki and Wikibase. It would not be a production Wiki, but would be a good place to test things out.
or are you asking how to get a new project in phabricator? You could also request a new production wiki (i.e. a clone of test.wikidata.org)
I don't think having a Structured Wikiquote is as simple as creating a copy of test.wikidata.org
The setup and extensions are exactly the same; the only differences are properties.
True. I mean I think there might be some UI changes... for instance, the description and alias are no longer needed, so the label can be brought full-width, not too dissimilar from Common's new structured file captions.
I think it would be better if this new project (when ready) replaced Wikiquote, otherwise it will become a situation like Wikidata's Lexemes, where Wikidata takes over Wiktionary.
WD UI also lacks support of paragraph.
I see that test wiki as an Incubator for multilingual/structured Wikiquote; that might one day become a real Wikiquote (and even replace other WQ ?)
