Sun, Aug 2
Sat, Aug 1
Mon, Jul 27
@Mohammed_Sadat_WMDE FYI, to check if it doesn't happen with the Weekly Summary
Thu, Jul 16
Jun 29 2020
Thanks for the ping, we will have a look more in details and come back to you.
Jun 12 2020
Jun 5 2020
May 28 2020
Another case where a user is confused by the error message: https://www.wikidata.org/w/index.php?title=Wikidata:Project_chat&oldid=1191761458#Could_not_save_due_to_an_error._Malformed_input
Can we keep the task open a few more days? I just sent the announcement to the community https://www.wikidata.org/wiki/Wikidata:Project_chat#Special:FewestRevisions_to_be_disabled and I just want to make sure that there's no strong veto. But everything should be fine.
May 27 2020
May 26 2020
May 18 2020
@Charlie_WMDE Are you OK with that change? Could you make some suggestion for the sentence where "incorrect" would appear two times?
May 13 2020
Some news got posted here: https://lists.wikimedia.org/pipermail/wikitech-ambassadors/2020-May/002298.html
May 10 2020
I have a question about the hackathon showcase :) https://etherpad.wikimedia.org/p/wmhackshowcase2020
Who's going to present? (we can only allow one person)
You indicated that you don't want to be recorded: however, the situation changed a bit, as we will stream the whole thing directly online. Is it fine if you don't share your camera, only your screen, and your voice so you can present?
If not, you could also prepare a video that we would broadcast for you during the showcase.
Thanks for your understanding!
May 7 2020
Thanks! You will announce it on Wikidata right?
Apr 28 2020
Apr 27 2020
Apr 24 2020
I'll copy the answer I provided on the "contact the development team" page:
Apr 20 2020
Apr 15 2020
@MarkTraceur Awesome, thanks for the quick answer.
Just to make sure I understand correctly: does that mean that wikis who didn't touch the current code will have their graphs working again after these 3-4 weeks? Or do they have to change something in the code?
Apr 14 2020
Hi @MarkTraceur, is there any fresh update to share about the maintenance of the Graph extension? :)
Apr 9 2020
@Amire80 Indeed, this is due to caching. Usually, purging the page or a null edit fixes the problem.
Apr 3 2020
Do we have a rule regarding merging new tasks into old tasks?
Apr 1 2020
Thanks for the quick fix!
Mar 30 2020
Since these two languages have been added as monolingual language code, we can move forward with Lexemes as well.
Mar 19 2020
Mar 18 2020
Mar 12 2020
No comment has been added, we can move forward with this and enable nrf-gg and nrf-je.
Mar 10 2020
Mar 9 2020
Mar 6 2020
@Ladsgroup Do you know where the Wikidata conversion table is stored and how to add new entries?
Mar 5 2020
@Salgo60 Please remember that Phabricator is a public space, and personal data of other people should probably not be exposed there.
As for Neo4j, we had a look at it but it does not match with our product at the moment, as it's not handling triple endpoint and sparql.
Mar 4 2020
@Ayack The issue should now be fixed: can you try it from your side and let us know if you encounter further issues?
Mar 3 2020
Thanks a lot \o/
So I guess it has not been deployed yesterday?
Feb 27 2020
Yes please :) It's a low percentage but it's still far from zero. Can we also look at the example queries?
Feb 24 2020
Reviving this old ticket, I wanted to ask if there are still objections to move forward with implementing nrf-gg and nrf-je codes for monolingual text. @Amire80, @GerardM, @jhsoby could you have a look and let us know what you think?
This code could be used for example in this case.
The recent request comes from here.
@Mrjohncummings No problem, I removed the line from the newsletter.
Feb 20 2020
Thanks a lot for your work! I'll add a note in the next newsletter.
Feb 19 2020
Feb 17 2020
@dcausse Is there anything that you need from the Wikidata team/ that is blocking you to continue with this patch?
Feb 13 2020
@NavinoEvans As far as I understand, nothing prevents you to add MediaWiki:Guidedtour-lib2.js to wikidata.org yourself, right?
Hello all, thanks for preparing this ticket.
We're going to look into it as soon as possible. However, what I can say for sure is that this is not just an easy bug to fix, and we won't be able to change anything before Monday. I'm sorry for that.
I'll share more information with you when I can.
Since the change we perform didn't have the expected results, we're going to revert it today, and keep looking for sustainable solutions.
Thanks all for your feedback. Since the change we perform didn't have the expected results, we're going to revert it today, and keep looking for sustainable solutions.
Feb 12 2020
We just increased the factor to 180. If you are running a bot and still encountering issues frequently, please let us know.
Feb 10 2020
@Lydia_Pintscher I just discussed with @WMDE-leszek about how we should move forward with this. The ticket should probably be evaluated again, and then prioritize. Basically, nothing prevents us to move forward with linking Schemas in statements.
Here are some news: we are going to try and increase the maxlag connected to the WDQS to 15min, to see how it goes and if most of the problems you encounter still occurs. This change should be applied later this week.
Also, as it seems that the issue with accessing data comes from Pywikibot, we suggested the developers to remove this limit.
@Dvorapa @Xqt Would you consider removing the limit for accessing the data, since this doesn't have an impact on the WDQS lag? This would be a huge relief for people using tools based on Pywikibot that can be blocked when the WDQS lag is high. Thanks a lot :)
Feb 7 2020
Feb 6 2020
Over the past weeks, we noticed a huge increase of content in Wikidata. Maybe that's something worth looking at?
@MarkTraceur Thanks for the update!
What would you advise to the projects who currently use the tool? Should they already start removing or replacing their currently broken graphs, or wait for more information?
Feb 5 2020
Unfortunately, there is not much Lydia or me can do about it, as the initial and now unmaintained tool was not under the responsibility of WMDE's development team. I'm regularly poking people around, trying to figure out who's responsible and who can help. I'll try once again to get someone to provide a more satisfying answer :)
I think it would be great if we had aligned policies and processes. For changes performed by WMDE related to Wikidata, we apply our policy with, in the case of a breaking change, a certain process to follow and a minimum amount of time between announcement and deployment. On the other hand, mediawiki-api-announce ML is not part of this process and should probably be.
Feb 4 2020
Jan 30 2020
@Mrjohncummings Here's the list of interface admins on Wikidata: https://www.wikidata.org/w/index.php?title=Special:ListUsers&group=interface-admin
Jan 27 2020
@Addshore Do you think this is something we could take on Campsite?
The lack of this feature is causing problems on Wikipedia when a vandalism occurs: the vandalized Wikidata description will appear on the Wikipedia page on mobile, and Wikipedians can't easily spot it because the edits don't show up in their Wikipedia watchlist. (see a recent discussion on French Wikipedia here).
Jan 21 2020
Indeed, this project is owned by the Core Platform Team at WMF.
Jan 15 2020
Jan 6 2020
After a discussion with Lydia, we decided to drop the ticket :) We don't change the link.
Dec 19 2019
Dec 16 2019
The reason from our side is: Help:Sources is very broad (it's a general documentation page about references) and is not providing any information about tainted references (because the feature is not an official feature on Wikidata yet - later we should probably add something in the doc).
So people looking for help or info about the tainted reference notification will find no help on this page. That's why we want to link to Wikidata:Mismatched reference notification input where they will find a presentation of the feature.
Dec 12 2019
I'd not close this task until we're absolutely sure that the issue got fixed.
As far as I understand, the issue exists for a long time, and I don't see any piece of code that was deployed to solve it. What makes you think that the problem is solved?
Dec 11 2019
Yes, the fact that the language doesn't appear in the list is a known bug and we have a ticket for that.
Dec 10 2019
@Bugreporter That seems unlikely. QuickStatementsBot is blocked since October 28th, and daily users of the tool only started reporting this issue yesterday.
So basically the API is sending wrong information? Weird. @Ladsgroup could you have a quick look and see if you can reproduce?
Thanks all for your feedback. Can you somehow check, in your QS interface, if the edits are about to be made with your individual account or the QuickStatementsBot account? Eg if the OAuth authentication worked or not?