Thu, Sep 19
Presentation written and given.
Wed, Sep 18
In that case, I suggest getting said deduplication flag. It's bad that we're spamming people.
Looks good to me.
Sorry, my misunderstanding. I'd still not link to English Wikipedia, unless we're specifically showing it in an instance where the user is trying to edit English Wikipedia while blocked on English Wikipedia – i.e. not in our suggested edits, where they actually edit Wikidata.
I would avoid linking to the https://en.wikipedia.org/wiki/Help:I_have_been_blocked page – it's specific for English Wikipedia in some ways, with links to appeal to the decision that will be confusing since they're not blocked in that sense, they just can't use this specific workflow in the app.
@bd808 added it to Wikitech too.
Tue, Sep 17
Mon, Sep 16
Also, Ukrainian Wikipedia hasn't got Tech News since September 4. This is limiting our ability to communicate any technical changes to editors: what's happening, what do they need to prepare for, what can they give feedback on – leading to tools having bigger potential to remain unused, preparations not being taken, and risk of conflict when they were not invited to discuss things that might change their workflows. Is that likely to be caused by T232392?
Have we seen any arguments against a new deduplication flag so far?
Hadn't planned for meetings that late on the Wednesday so I think I might be passing through some tunnels south of Stockholm around that time, but I'll join you if the connection allows me to.
Thu, Sep 12
I see no reason why this would be an area of conflict. If we can make sure this doesn't happen in the future in a way that wouldn't have other adverse effects, I'm sure most folks would agree that's great. If we can't address without adverse effects – is this a common problem? No one wants the content obscured. The template was promptly removed by one editor for getting in the way, and another editor pointed out on the talk page that it's not supposed to be used in articles.
Wed, Sep 11
Something like this for Tech News?
This didn't happen.
Slides sent to the organisers.
Tue, Sep 10
I think Wikidata diffs are useful enough that we could link to them, but they're not something we can depend on will have the information that a newcomer will need to get what's wrong. It's an additional tool rather than the explanation.
I'd ask around, to be on the safe side.
Aug 21 2019
@Marostegui Thanks! The one additional detail some people keep asking about where it'd be great if I could give them a good answer would be what in our setup creates this problem, when they can't remember it happening for other websites.
@Marostegui Something that would be helpful would be if we could have a simplified technical explanation (aimed at fairly non-technical audience) explaining why we need the read-only periods, so that we could explain to the communities what's happening and why they can't edit. Would you have the time to do that?
I've added this to Tech News #36 which will go out on September 2 (no issue on Monday, all the usual writers are travelling and no one else picked up the torch). I've also posted on Project Chat on Wikidata as that is fairly soon.
Aug 19 2019
Aug 15 2019
I think having the trial open to non-WMF-staff might mean better future chances of adoption if we come to the conclusion that we like it, if it's not just limited to a specific subgroup of Wikimedians?
(This has already been reported more than once.)
@Daimona So I tried to write a summary in Tech News, but there's enough information that I think people actually need to read the ticket. But something like this?
Aug 14 2019
It would probably have been more visible if we had printed it a proper print shop, and not printed it ourselves with an ordinary office printer that can handle A3.
Aug 13 2019
@Bugreporter No, this isn't a task, and I can see why you closed it.
Thank you. I'll make sure it gets printed.
Jul 30 2019
Jul 29 2019
Tried to save some of the previous translations, but ... there's no way around the fact that this is largely a new text, so I failed.
Jul 22 2019
I've got no spontaneous better suggestion.
For community communication outside of the app, this should be fairly easy, something like this:
- Mentioning it in Tech News.
- Posting on update in the documentation.
Jul 17 2019
I talked to @Trizek-WMF about banners. Since edits coming from other wikis will be run after the read-only period which hopefully will be rather short I don't think we need to do a banner for all Wikimedia wikis, but we'll set up one for Wikidata.
Jul 15 2019
So far posted in:
@hoo Shouldn't happen, as in "won't happen, we're worrying unnecessarily"?
Jul 12 2019
Jul 11 2019
We'll make a new round of announcements next week, to remind the community this is happening.
We're looking over the new survey, involving María as this is outside my area of expertise.
Sent them a suggestion for a title (The open process – User involvement in Wikipedia's software development) and photo now.
Thanks! And since UpdateRepoOnMoveJob doesn't fail and won't try again, the page move wouldn't actually be reflected in Wikidata? Or am I missing what function it has?
My first thought is that we'd might not want to try to leverage that, but build something new. The existing structures are tied to specific types of translations: if you hang out at Translatewiki, it's to translate software. The translators-l translators typically act on occasional requests, people who translate e.g. Meta might translate what they stumble over. When looking at the content of the blog, a lot of this is the kind of material we've not been very successful at translating. By trying to leverage what hasn't been working well for this kind of material in the past, I think we'd be setting us up for disappointment. I wonder if we'd not be better off a) trying to build something new and b) using that as a base for our later work with translators.
Jul 10 2019
Could someone confirm what @Lucas_Werkmeister_WMDE is saying about the job retry? (Asking since he's hedging with "unless I'm mistaken".) Would prefer this to be clear when we communicate this.
Jul 9 2019
@Multichill: Here's where we posted back when we announced things. Is there anywhere in particular you'd expect this to be posted where it hasn't been so we can include it next time?