I'm interested by that, in order to define a better scope for T112864: Create a newsletter about Collaboration team products. I'll probably release newsletters before you work on that task though.

fwiw

In T123538#2425816, @Qgil wrote:

I think T137825: Recommendations for publishing project updates is kind of a blocker of this task. Let's agree how WMF Product teams should keep communities up to date, having in mind specific cases like the Collaboration. As far as I know the rest of verticals have similar problems, and it is better to think on good general solutions rather than Collaboration's in isolation.

This task welcomes an owner...

Not sure whether this is the right place to note it, but FYI that Editing now puts "updates" at https://www.mediawiki.org/wiki/Editing#Progress_on_annual_plan.2C_quarterly_goals_and_other_work .

Paging @Deskana to see whether he has thoughts on this. https://meta.wikimedia.org/wiki/VisualEditor/Newsletter/2017/May is what the newsletter now looks like.

In T139305#3363728, @Elitre wrote:

Paging @Deskana to see whether he has thoughts on this. https://meta.wikimedia.org/wiki/VisualEditor/Newsletter/2017/May is what the newsletter now looks like.

What is the intended purpose of a VisualEditor-specific newsletter? "Keeping stakeholders up to date" is the obvious answer, but is there more history than that? Did it start as a result of the troubled deployment history? As a result of user misconceptions about the product?

Where we go from here depends on these questions. I have a few ideas, but I want to hear the reason things are the way they are before assuming I know how to make it better. ;-)

See https://en.wikipedia.org/wiki/Wikipedia:VisualEditor/Updates if you want to see all (almost all?) of them. The early ones were mostly lists of bugs that got resolved.

The purpose of this conversation is to determine what the (current) purpose is.

As you can see, despite the page title, it is actually already featuring more general Editing info.
I think the historical purpose was that there is just so much work behind the product and continuous updates to it, that the community needs a place that collects them all, presents them in a language that humans can understand, shows progress over time, flags the most interesting and useful new features, gives a heads-up about major changes. Tech News wasn't enough for this, whatever page Audiences was using for updates was also not good enough, and this format (hundreds of subscribers across wikis, and translated in 20+ languages) seems to work so far. (It's also been used as a model for other product newsletters.)

Tagging with Editing Team then.

Yeah, it probably wouldn't hurt to have a broader conversation, but given that this is the end of a quarter, and the so many recent changes, ... it's probably not the best moment - it should stay in the radar though.

We should also bear T104131 in mind.

Also, we'll want to investigate related answers in https://meta.wikimedia.org/wiki/Community_Engagement_Insights/2016-17_Report/Technical_Collaborations#Key_Findings_from_the_Technical_Collaboration_team .

I had inquired about using the new Newsletter extension at mw.org, but this may be premature or just not worth it. Tasks such as https://phabricator.wikimedia.org/T174664 and https://phabricator.wikimedia.org/T110645 apply.

We did something similar last time. https://meta.wikimedia.org/wiki/VisualEditor/Newsletter/2017/May#Future_changes has two items about the old wikitext editors.