I'm not sure what to do with community incidents. In the past days @Aklapper and me had to intervene in a couple of tasks. Featuring them might help to increase the awareness about problems and their solutions. It might be counterproductive to solve those specific problems too. In case of doubt, not featuring them is probably better.

@Lydia_Pintscher @JohnLewis any lessons learned you would like to share? Your weekly summary looks great. I wonder how much time it takes to produce it.

(I'm fairly familiar with Tech News, but let me still CC @Johan just in case) :)

When I did them actively, it took about 30-60 minutes to prepare going through all the channels we use for communication (on wiki, mailing lists, twitter, email chat etc.). The only lessons I learn was keeping things simple and concise were best, especially in a weekly update feed. Updates grow quickly, especially in long sentences and explanations and people don't like have to read something the size of an entire singpost just for a weeks brief update.

• Yeah 30 to 60 minutes a week for the Wikidata news. Though a lot of that is helped by me already posting the most important things to Twitter for example during the week making it easier to summarize later. Also the sending out process we have is still a bit of a pita as I have to format it in different ways for different media. Can be steamlined probably but I need to take the time to do it...
• Automate as much as you can. I had help from Lego who wrote a bot that updates one part of it automatically.
• Have a page where people can fill in things during the week so it doesn't just depend on you to see things.
• Have a dependable schedule. (I let it slip over the past 2 weeks -.-). If you're late publish anyway.
• Spread it through different media. We do talk pages, village pump, social media, mailing list.

Thank you for the feedback!

Alright, following the calendar proposed, I have finished drafting at https://www.mediawiki.org/wiki/Developer_Relations/Weekly_summary. Tomorrow morning I'll check whether anybody else added anything (quite a theoretical scenario, but who knows) :) and I will send an email to wikitech-l only (for starters) asking for feedback.

Then I will start the cycle for next week's summary, seeing what can be improved both in content and distribution.

https://lists.wikimedia.org/pipermail/wikitech-l/2015-October/083525.html has passable presentation in plain text, on HTML looks exactly like the wiki page.

Much of what I see in the draft now could be done with a template set sparing both typing and translators time.

Some strings will be quite stable and might be used with templates, yes. However, let's wait to compile a few summaries in order to see what is the structure that remains stable.

Is this redundant? Should anything be added to Tech/News?

It might be redundant, and we might want to ask the Tech News contributors their opinion about merging efforts. @Johan, what is your opinion, and could you help grasping the opinion of the Tech News project?

I will still force myself to this weekly schedule. :) Whether I post on a wiki page or another is secondary when it comes to editorial effort.

https://www.mediawiki.org/wiki/Developer_Relations/Weekly_summary#2015-10-15 is ready for distribution tomorrow. My humble goal will be to create an HTML email that renders well, just like the Wikidata weekly summary.

I'm still not sure about the redundancy between this weekly summary and Tech News.

I think they have different audiences, actually, and should therefore remain separate. Maybe every so often there will be a point that overlaps, but overall they serve different user needs. That being said, finding best practices in formatting between the two would be most excellent (I have to say though, Tech/News's format and cadence seems pretty easy to translate and digest, so we'd need a good reason to modify it :)

I just sent another weekly summary. The novelties were a Software section and a new /Next page to create the next edition

So this is happening, I think it is being useful, and it can improve every week without needing a task for this. Closing.