Page MenuHomePhabricator

Celenduin (Michael Große)
User

Projects

User does not belong to any projects.

Today

  • Clear sailing ahead.

Tomorrow

  • Clear sailing ahead.

Wednesday

  • Clear sailing ahead.

User Details

User Since
Sep 7 2020, 5:08 PM (241 w, 6 d)
Availability
Available
LDAP User
Unknown
MediaWiki User
Zvpunry [ Global Accounts ]

I work for WMDE. This is my private account, used for volunteering work. My work account is @Michael.

Recent Activity

Jun 8 2024

Celenduin added a comment to T107693: Add "Create new item" link to property value drop-down menu (particularly when no item matches) in Wikidata.

I had another go at a userscript for this. See https://www.wikidata.org/wiki/User:Zvpunry/CreateNewItem for instructions how to use it.

Jun 8 2024, 5:24 PM · Google-Code-in-2017, Wikidata-Gadgets, MediaWiki-extensions-WikibaseRepository, Wikidata

Dec 3 2023

Celenduin closed T351462: Question: Volunteer and WMDE staff work with two separate GitLab accounts or with a combined one? as Resolved.

Thanks! That helps, I think.

Dec 3 2023, 6:04 PM · GitLab (Account Approval)

Nov 16 2023

Celenduin created T351462: Question: Volunteer and WMDE staff work with two separate GitLab accounts or with a combined one?.
Nov 16 2023, 8:09 PM · GitLab (Account Approval)

Sep 28 2023

Celenduin added a comment to T344542: Lookup menu "stuck" in scrolling Dialog.

Thank you so much to the entire team! 🙏
I look forward to using it 😊

Sep 28 2023, 6:08 AM · Design-System-Team (Design-Systems-Sprint-8), Codex 1.0, Codex

Sep 6 2023

Celenduin added a comment to T344541: Dialog open on mount does not prevent background from scrolling.

We don't have any demos of dialogs open on mount, so I'm skipping design review and moving straight to pending release. This fix will go out with the Codex release next week @Celenduin!

Sep 6 2023, 2:25 PM · Design-System-Team (Design-Systems-Sprint-7), Codex

Aug 23 2023

Celenduin added a comment to T344541: Dialog open on mount does not prevent background from scrolling.

[...]

I'm writing a Statement editing interface for mobile Wikidata, which means adding edit-buttons in a lot of places that open the same dialog with different data. It doesn't seem like a great idea to already mount the whole app in a lot of different places just to have the button there that might or might not be clicked.

Is your concern that creating lots of copies of this dialog in the DOM would be wasteful if the dialog is never opened? If that's the main issue, would it be helpful if we changed the Dialog component so that it didn't render itself unless it was open (i.e. if it applied v-if="open" to its contents)? Alternatively, would there be a way that all these buttons could all share one dialog instance?

Aug 23 2023, 8:10 PM · Design-System-Team (Design-Systems-Sprint-7), Codex

Aug 19 2023

Celenduin created T344543: Lookup: allow showing initial menu items on focus before typing.
Aug 19 2023, 7:26 AM · Design-System-Team, Codex
Celenduin created T344542: Lookup menu "stuck" in scrolling Dialog.
Aug 19 2023, 7:16 AM · Design-System-Team (Design-Systems-Sprint-8), Codex 1.0, Codex
Celenduin created T344541: Dialog open on mount does not prevent background from scrolling.
Aug 19 2023, 7:01 AM · Design-System-Team (Design-Systems-Sprint-7), Codex

Jan 8 2023

Celenduin added a comment to T288466: [QS-GUI] Port Wikidata Query UI to a modern build system.

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

Jan 8 2023, 10:04 PM · [Archived]Wikidata Dev Team, wmde-wikidata-tech, Wikidata Query UI, Technical-Debt, [DEPRECATED] wdwb-tech, Wikidata

Oct 29 2022

Celenduin updated Celenduin.
Oct 29 2022, 2:09 PM
Celenduin updated Celenduin.
Oct 29 2022, 2:09 PM
Celenduin added a comment to T116762: Notifications in Echo on Wikidata should display label as well as Q id.

I forked @Lectrician1's userscript and made a first working version: https://www.wikidata.org/wiki/User:Zvpunry/WikibaseEcho.js

Oct 29 2022, 2:03 PM · wmde-wikidata-tech, Growth-Team-Filtering, Growth-Team, Notifications (Echo), MediaWiki-extensions-WikibaseRepository, Wikidata

Oct 30 2020

Celenduin added a comment to T266673: Fix Math extension to not require JS parser.

@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

Oct 30 2020, 5:51 PM · MW-1.36-notes (1.36.0-wmf.18; 2020-11-17), Wikidata-Campsite (Wikidata-Campsite-Iteration-∞ (On Hold)), Wikimedia-production-error, Math, Wikidata

Sep 7 2020

Celenduin renamed T262215: Create proof of concept of static web app for Phabricator tech task prioritization from Create proof of concept for tech task prioritization web app to Create proof of concept of static web app for tech task prioritization.
Sep 7 2020, 9:32 PM
Celenduin added a comment to T262215: Create proof of concept of static web app for Phabricator tech task prioritization.

as the "public" phabricator conduit API is missing the Access-Control-Allow-Origin header and [browsers care about such a thing nowadays]

Please help me understand why that's relevant and why browsers are mentioned if you plan to have some code running somewhere to pull stuff via the API.

Sep 7 2020, 8:02 PM
Celenduin closed T262215: Create proof of concept of static web app for Phabricator tech task prioritization as Invalid.

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*

Sep 7 2020, 6:10 PM
Celenduin added a comment to T262215: Create proof of concept of static web app for Phabricator tech task prioritization.

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.

Sep 7 2020, 5:57 PM
Celenduin created T262215: Create proof of concept of static web app for Phabricator tech task prioritization.
Sep 7 2020, 5:12 PM