@kostajh But it's not yet decided this will go into production? (If it is: do you know when?)

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.

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.)

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 ;).

Keegan also suggested we request a watchlist notice;
https://commons.wikimedia.org/w/index.php?title=Help:Watchlist_messages/Wizard&withJS=MediaWiki:WatchlistMessageCreator.js#step0

I've posted on Commons:
https://commons.wikimedia.org/wiki/Commons:Village_pump#No_editing_for_up_to_30_minutes_on_June_19

@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 do really 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?

@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.

@Ebe123 OK! When you're ready, feel free to go to https://phabricator.wikimedia.org/tag/user-notice/ and drag this ticket from "Not ready to announce" to "Announce in next Tech/News" and ping me here, and we'll make sure the communities get to know what's happening. (:

The one thing we'll need to make sure we do is to properly contextualise this so folks know they're not supposed to just copy and paste the description (which almost never is, but could be copyrightable).

If we're doing this.

@thiemowmde Please let us know (for Tech News purposes) when the deployment has been scheduled. (:

I like that idea a lot in principle; but it's important to bear in mind here that the image captions shown in-article are entirely local to the article itself and stored in the article wikitext, and have nothing to do with the Commons captions (structured or otherwise).

Makes sense for an announcement?

@Krinkle @Ebe123 Do you know what a rough timeline for this hitting production might be?

We'll meet with some of the Structured Data folks on Tuesday to discuss this.

Assuming this was kept form the parent task without any specific need for this subtask to be announced. If that's a mistake, please re-add it.

Have you considered strategies for identifying candidates for caption addition/translation based on their usage in Wikipedia articles of interest, rather than attempting to identify random image candidates directly from Commons based on their captions and work back to Wikipedia articles? One idea that comes to mind is that we could populate caption addition/translation suggestions by querying caption info for articles the user visits as the user browses. Another idea is that we could do something like identify candidates used in (random members of) the top 100 or 1000 articles for a target wiki.

We met last week and worked on the next steps, which will include talking to relevant parties to set up a discussion where we can get a fair idea of what the community thinks. We want to avoid both editors' gut reaction without having read the relevant information, and overselling something.

Keeping the community informed has basically been relaying the information that the PDF renderer has been "a few weeks away" (which it consistently has been to best of our knowledge) which has always turned out to be another few weeks. Hopefully this will soon be done, for single articles.

This seems to have been smoothly launched.

Let's assume it was a temporary problem and call it resolved and I'll create a new ticket if it persists.

OK, maybe a temporary hickup, seems to be working again now – both a test run and the actual newsletter seem have been delivered.

This is currently keeping Tech News from being delivered.

Added to https://meta.wikimedia.org/wiki/Tech/News/2019/18

So will this be in production before or after Tech News goes out on Monday?

That's the tag to flag something for potential inclusion in Tech News, yes.