@Rfarrand Hey :) Here's something we'd like to organize during the hackathon. Do you need more info from us?

No worries :)

The ping was certainly for @Lea_WMDE :)

Thanks @Charlotte, I added a link to the FAQ page on the next Wikidata newsletter.

@RexxS Thanks! Feel free to update the description to reflect the prerequisites you expect from participants.
@Mike_Peel I'm fine merging this proposal with another one if there's duplicate - just want to make sure that we have a session where people can have time to try and experiment :)

Hey @RexxS, we didn't talk about this idea... yet ;) But I was thinking, this would be a different usecase from the Lua workshop, if people don't want to learn Lua from scratch but just how to reuse and adapt your infobox. Would you be willing to give such a workshop at the hackathon?
Feel free to edit the task, what I added there is just suggestions.

@Rfarrand Here's a workshop that we would like to include during the hackathon.
Do you think it's feasible?
Do we have options for video recording or should we take care of it with volunteers (eg as the wonderful @Fuzheado?)
Do you need any more info from us at that point?

That sounds reasonable. I think we should ask the community first, what do you think @Lydia_Pintscher?

@Lydia_Pintscher Since the issue of multiple links doesn't seem to be a real problem, since Wikisource links should be added to different items anyway (different editions), can we move forward with this? Or is this anything else blocking?

Existing doc on Wikidata: https://www.wikidata.org/wiki/Help:Monolingual_text_languages
Task that should be added as a parent for new requests: https://phabricator.wikimedia.org/T144272

@Envlh We're working on generating one for this week. It should appear on Saturday.

This should be deployed on July 11th. I'll take care of the announcement.

Announcement made onwiki, to wikidata, wikidata-tech and xmldumps MLs, also on Telegram.

Announced ✅ on Wikidata, on the wikidata, wikidata-tech, wikitech-l, xmldatadumps-l mailing-lists, on Weekly Summary and TechNews.

@ArielGlenn just to be sure, are you going to rename only the new dumps to come, or also the previous ones?

@ArielGlenn OK for me, I'll make sure that it's announced asap.

I believe this is the same as what is discussed on the ML at the moment.

@Smalyshev Can you have a look at this? Is it maybe related to the recent changes on json output format?

Pinging @hoo @Envlh @Hydriz @Maxlath FYI

Seems enough for people to change their code if needed.

I take care of Wikidata newsletter and TechNews. Any idea when this change will take place?

Update: we are about to start migrating property terms this week. The original planned date was 19th of June. Due to WMF US Staff holiday, there will be no deployments today. Therefore, we are going to switch the migration on (write both stage) of property terms one day later than planned, on Thursday the 20th of June. All other dates regarding migration remain the same for the moment.

@Michael Yes, for now I'll add a "documentation draft" section in "development" and later, when we have a product ready, I'll create a proper "documentation" section.

The change is now deployed on wikidata.org!

Hey! I don't have a lot of information about who helped with the labeling campaigns, but I think you could talk to @Sjoerddebruin, @abian and @matej_suchanek.

The current status would be to change the current behaviour and stop automatically jumping from a field to another. Yet to be confirmed by @Lydia_Pintscher (and maybe deserves a new task)

Hello all,

Update: because Operations team have their offsite next week, the deployment on wikidata.org is postponed to June 17th.

Update: because Operation team have their offsite next week, the deployment on wikidata.org is postponed to June 17th.

So, can this ticket be closed?

Yes!

Update: the test system is now in place: https://wikidata-termstore.wmflabs.org/index.php/Main_Page
To access to its database, you need to get the access granted. Feel free to add a comment to this ticket if you need it.

FYI we removed " E3300 - Human.shex - basic scheme for Q5" as Q3300 is probably not the kind of human we want to highlight with an Easter Egg. We replaced it with E10.

Thanks for your suggestions! I updated the task. (I added only one extra sandbox, I think having two of them is enough)
Since we have to implement this list before deployment happens next weeks, we are now closing this suggestion list :)

Hey @Lydia_Pintscher could you have a look at this and see if we can help?

@Andrawaag What do you think? :)

The script is here: https://www.wikidata.org/wiki/User:Danmichaelo/Gadget-externalitemsuggester.js

@Lydia_Pintscher Do you have any idea how this could be done, and who could help?

Hey @Stas, can we add the https:// before the URL on the Query Service? It would be more efficient for the users because Mediawiki doesn't recognize the w.wiki links.

@Lydia_Pintscher @Smalyshev Somehow related to the results of the drop-down menu when creating a specific statement. Do you have any idea/ suggestion to help?

Here's an update regarding the dates of test environment and migration of wb_terms table replacement solution.

Breaking change process running:

• May 14th: announcement
• May 28th or earlier: bugfix deployed on beta
• June 17th: bugfix deployed on wikidata.org

Breaking change process running:

• May 14th: announcement
• May 28th or earlier: bugfix deployed on beta
• June 17th: bugfix deployed on wikidata.org

Edit: after talking with Lea, we decided to go for a breaking change, just to be safe and make sure that we don't accidentally change the behaviour of editors' tools.

@Nikki @Envlh Thanks for your feedback. We will take the opportunity of this revert to consider other options.

Reopened as we reverted the change that apparently caused T222346

Closing again as the discussion continues in T222426

Check, we now have two steps with different labels.