User talk:Pintoch

• User talk:Pintoch/Flow

EditGroups

Hello @Pintoch, I'm one of the developers of a new QuickStatements version and we would like to include it in EditGroups. We already have everything ready and would need access to the database to insert it. I know Django and maybe I could do that, if I have access to the toolforge instance. Could you help us out? We plan to publicly launch it on Feb 24th, on Wikidata Lab XLIV. Best regards, Arcstur (talk) 18:34, 14 February 2025 (UTC)

@Arcstur: hi! Amazing that you know Django and are willing to get involved in the administration of this tool :) I have added you as admin of the tool both in Toolforge and in the tool itself (you need to first login like a normal user and then go to https://editgroups.toolforge.org/admin/). Would you also be happy to add further tools when requested by others? I would be keen to add you as a point of contact at Wikidata:Edit_groups/Adding_a_tool. If you have any interest in getting involved in other improvements and maintenance of the tool, I'd really appreciate, as I don't have much bandwidth to take care of it. − Pintoch (talk) 08:55, 15 February 2025 (UTC)

Hello @Pintoch, thanks for this! Yes, I would like to get involved in maintenance and improvements, it's an important tool for the ecosystem and I think I can help :D, how can I advance on this?

Yes, I can add further tools, is there a protocol for accepting (like having a minimum time of existance, etc)? I was already diving into the code on GitHub hahah.

Also, one question: when I add the tool, it will be able to recognize batches that already happened or only the new ones?

Best regards, Arcstur (talk) 17:23, 15 February 2025 (UTC)

@Arcstur: fantastic, thank you so much!

About accepting new tools: EditGroups does not retrospectively scan older edits when a tool is added, so it is recommended to register the tool in EditGroups as early as possible. You can see the information I have been asking tool authors for in the page about adding a tool. This information pretty much reflects the form that you'll get in Django's admin interface to create a new Tool object (at https://editgroups.toolforge.org/admin/store/tool/add/, which somehow seems to have CSS issues at the moment, not sure why). So as an admin, all you need to do is to create this Tool object.

If you're interested in getting familiar with the code base, I hope the documentation of the architecture can be somewhat of a help. The list of issues should be mostly up to date with the state of the tool. I'm available to discuss any aspects of it in writing or over a call as you prefer. Thanks again! − Pintoch (talk) 08:50, 16 February 2025 (UTC)

Hello again @Pintoch, since we'll be at the Wikimedia Hackathon, what do you think about helping me explore the codebase? I also saw that you want to work on social sustainability and that is awesome, by the way. Best, Arcstur (talk) 23:50, 26 March 2025 (UTC)

Hi Arcstur, amazing that you'll be there too, really looking forward to it! And congrats for the QSv3 launch, it looks like adoption is ramping up. I was actually thinking of trying to schedule a call with you, and was thinking of two formats:

• one to help you get started with the codebase/deployment, tackling a small task together (such as removing the "maintainer needed" banner, fixing the django admin interface…)
• one with WMDE folks (since there is some lukewarm interest in deploying it on Wikibase.Cloud). The goal of the call would be to check up on their plans and on your own interest as a maintainer. To deploy it for Wikibase.Cloud instances, they will need to do some changes to it (primarily recent changes polling).

I wonder if you'd be interested in doing any of those ahead of the hackathon already? I guess the first one could work in person quite well. For the second, I am not sure if anyone from the relevant WMDE teams will be at the hackathon (I wouldn't count on it), so it's perhaps better suited for a call. − Pintoch (talk) 08:03, 27 March 2025 (UTC)

Awesome, those are great ideas. I think both could be made before the Hackathon, if it is possible. Can we schedule the first call already? My first desire would be to know how you fix when EG is too far behind. Some days ago I saw that it was 4 hours lagged behind and I have no idea how that is fixed. And those two small tasks seem a good starting point for coding. Arcstur (talk) 14:05, 27 March 2025 (UTC)

@Arcstur: yes, let's do that. Would you like to just pick a time at https://app.simplymeet.me/antonin-d ? − Pintoch (talk) 15:01, 29 March 2025 (UTC)

@Pintoch: done! Arcstur (talk) 12:44, 31 March 2025 (UTC)

Requested P7476 for deletion

Hello, I've proposed a property you created (iFixit teardown ID (P7476) for deletion. If you have any comments about this, please respond there. BasilicumTree (talk) 10:21, 8 March 2025 (UTC)

P6288

Hi! I have proposed ICCD ID - CG form (P6288) (which you created in 2018) for deletion at Wikidata:Properties for deletion/P6288, since it has been superseded by ICCD site ID (P9050). Bye, --Epìdosis 17:47, 28 March 2025 (UTC)

Wikidata:Properties for deletion#Property:P6326

Hello Pintoch, pursuant to the instruction given at Wikidata:Properties for deletion I would like to notify you of this discussion: Wikidata:Properties for deletion#Property:P6326. Greetings, --UV (talk) 21:14, 1 April 2025 (UTC)

Hi! Proposing LEGO element ID (P6248) for deletion (no usage)

Hi, I am a LEGO fan, but I have noticed this property has not been used on Wikidata not even once. I am wondering if it should be deleted, then, so I proposed the deletion on Wikidata:Properties for deletion/P6248. I noticed you created it on 2018, so you might have thoughts on that. I hope it is okay! Cheers, TiagoLubiana (talk) 19:23, 11 April 2025 (UTC)

Wikidata:Properties for deletion/P6307

This is notice that a property you created, Wikibase Registry ID (P6307), has been nominated for deletion. Harej (talk) 20:17, 2 September 2025 (UTC)