I work for WMDE. This is my private account, used for volunteering work. My work account is @Michael.
User Details
- User Since
- Sep 7 2020, 5:08 PM (168 w, 21 h)
- Availability
- Available
- LDAP User
- Unknown
- MediaWiki User
- Zvpunry [ Global Accounts ]
Thu, Nov 16
Sep 28 2023
Thank you so much to the entire team! 🙏
I look forward to using it 😊
Sep 6 2023
Aug 23 2023
Aug 19 2023
Jan 8 2023
I volunteered some time and created a first version that uses rollup to build the main code: https://gerrit.wikimedia.org/r/c/wikidata/query/gui/+/875993
Oct 29 2022
I forked @Lectrician1's userscript and made a first working version: https://www.wikidata.org/wiki/User:Zvpunry/WikibaseEcho.js
Feb 17 2022
Feb 15 2022
Feb 14 2022
Feb 12 2021
Oct 30 2020
@Physikerwelt I spent a lunch-time and a bit and made a user script that allows you to create new math statements on items: https://www.wikidata.org/wiki/User:Zvpunry/MathWorkaround.js
Sep 14 2020
Sep 10 2020
Sep 7 2020
But I guess this is quickly answered as apparently not feasable as the "public" phabricator conduit API is missing the Access-Control-Allow-Origin header and browsers care about such a thing nowadays. Also, this doesn't even seem to be a configuration issue on the wikimedia side of things, but adding that header is a WONTFIX in phabricator itself: https://secure.phabricator.com/T7304. *throws hands up in the air in resignation*
Hi @Aklapper, problem to solve is that prioritizing non-product tasks (e.g. refactorings, cleanup tasks, writing docs, etc.) consistently and transparently can be non-trivial. One possible approach to this would be to score the task along some dimensions (e.g. developer impact, did it cause issues before, how many extensions would it affect) and rank task according to that score. This is inspired by a concept called user pain.