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.
Mon, Jul 15
So far posted in:
@hoo Shouldn't happen, as in "won't happen, we're worrying unnecessarily"?
Fri, Jul 12
Thu, Jul 11
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.
Wed, Jul 10
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.
Tue, Jul 9
@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?
Mon, Jul 8
Fri, Jun 28
Thu, Jun 27
Wed, Jun 26
Tue, Jun 25
Suggestion for a note belatedly sent.
Mon, Jun 24
Thu, Jun 20
OK! Please just move it to the "Announce in next Tech/News" column on the user-notice board when it's ready to be announced. (:
Wed, Jun 19
Jun 13 2019
@kostajh: Thanks! But it's not yet decided this will go into production? (If it is: do you know when?)
Jun 12 2019
Met with Olga to discuss next steps. We've deployed the new renderer, which seems to be working. We'll take a look at the feedback, but honestly, we don't have that much resources we can assign to this. Pediapress are working on the books. In general, there won't be much we can say. We'll write up a note, but generally phase this out.
Yes, Commons and Testcommmons.
Jun 10 2019
Jun 4 2019
Jun 3 2019
If we think it's worth the time.
OK. We could list a number of categories if we wanted, I suppose, to diminish risks; they'd not cover everything but it'd be something to help avoid serving an execution to someone who hadn't been specifically looking for that kind of material as they're helping out on their commute to work.
The Tech News issue involving this has been delivered.
(This is probably cultural, but personally I'd be more concerned about without warning people asking them to caption violence/mutilations/executions than e.g. nudity, as a worst case scenario.)
Yes, it had crossed my mind. And I'm not overjoyed at the idea of (worst case scenario) showing nudes to a kid or something. So let's please update the API as soon as the NSFW scoring system is online, but meanwhile I think it's an acceptable risk - especially since we are going to prioritise images that are associated with articles, which are not likely to be NSFW. (I mean, there's a nonzero chance, but it is lower than if we just showed a random image from a pool of literally everything.)
May 31 2019
I've suggested a watchlist notice now:
I would also love to get your input for the “Suggested edits“ support page, which is, let’s formulate it positively, pretty minimalistic right now. Feel free to edit the hell out of this page ;).
May 29 2019
Keegan also suggested we request a watchlist notice:
@Trizek-WMF What are our capabilities for a CentralNotice on Commons when it comes to how to serve the notice in different languages on one wiki? We can't use user settings for logged-in users, right?
So I see no reason not to get rid of the waiting period and observe what happens, but just so we're aware of it: from a vandal-fighting perspective, we'd need to keep this in mind long-term and keep track of what's happening here and remember that the waiting period is an option, in case the app becomes more popular (especially for editing) or vandals find it a convenient way to vandalise things.
I mean, I really do see the point in not having someone be invited an hour after they started editing if the only reason is that their edits haven't been reverted yet, but that seems like it'd be necessary mainly if it's actually a problem, not just theoretically.
Plan for how to engage with the community:
Do we have any numbers for what difference it would make, so far?
May 28 2019
@matmarex Added to https://meta.wikimedia.org/wiki/Tech/News/2019/23 with some restructuring to make the sentences simpler and shorter. Please take a look and make sure it still makes sense, and feel free to edit as necessary.
Would it be possible to use this space for a short explanation, or would that make it too cluttered? How much copy do we have room for?
I think the main problem here would be that you're adding a caption we're not showing in the article unless you tap the image, which could be potentially confusing, unless I'm misunderstanding something. On the other hand, there's a value in surfacing the editing capabilities in the app. I have no strong opinion either way.