Hi @srodlund! I took another look.
As far as I understand it, is this going to be a tech blog primarily about developments for the Wikimedia communites? Then there is actually not too much overlap. We (the MWStakeholders) would like to start a MediaWiki blog that works as a group blog, has sysadmins, developers and maintainers as a target group, to make developments and actors inside and outside (!) WMF visible and to promote MediaWiki as software and bring people and projects together. There would also be room for Semantic MediaWiki, Meza, skin and extension developers and many others who, in my opinion, won't find room in a Wikimedia Tech Blog.
The overlap would be that we would also like to promote developments of Wikimedia. But these topics would then tend to end up in your project. That's a pity, but also okay. Of course we would have loved to have included this and created a lot of space for it. But we can refer to interesting posts.
We also didn't know that Wikimedia itself is starting a new blog here. Then we could have contacted us early and agreed on something. At the moment everything seems already to be fixed on the WMF side and we have to adjust our content concept a bit. But of course our project will always open for all stakeholders in the big MediaWiki universe. I think anything that helps to make the work of developers visible and create different points of contact is essential for the future of MediaWiki. You start first and we follow. :-) We are only terribly behind schedule.

The MW stakeholders are also planning a MediaWiki blog. This will be launched in the next few months. The scope of the content would be broader, but there would also be many overlaps in content. Could we make a call to explore whether there are synergies. It makes little sense to duplicate infrastructures. Obviously several people have the same idea. Who would be the contact person here?

I found this page at MediaWiki.org: https://www.mediawiki.org/wiki/GDPR_(General_Data_Protection_Regulation)_and_MediaWiki_software

You can find a description here: https://en.help.bluespice.com/wiki/Extensions/CheckList

Made an internal ticket at Hallo Welt.

@Qgil that sounds great. I didn't mean to set somebody under pressure, but we would support you, whenever necessary. :-)

Thank you André. I don't have specific proposals. This task is now three years old. Quim put it on the recent annual plan and my question is, if there is any help for the realization needed or some feedback. Maybe we can contribute.

Hi Quim. What are the next steps? Do we need ressources for that? Or is any approval necessary?

Here one blog post by Markus Glaser: https://blog.bluespice.com/2017/05/23/a-culture-of-knowledge-sharing-impressions-from-the-wikimedia-hackathon-2017/
Another one for the MW Stakeholders blog is planned.

Thank you for the reminder.
I'm planning a blog post for our Hallo Welt! Blog: https://blog.hallowelt.com/
and / or BlueSpice Blog: https://blog.bluespice.com

Would be a great support for new developers

Added the MediaWiki-Stakeholders-Group tag, because this meets a requirement of the MediaWiki Usage Report 2015: skinning

Meets a requirement of the MediaWiki Usage Report 2015: extension management

Meets an important requirement of the MediaWiki Usage Report 2015: extension management :-)

Meets a requirement of the MediaWiki Usage Report 2015: Developer support, skinning and UI

Meets a requirement of the MediaWiki Usage Report 2015: Developer support

Today a fork is not at the agenda. We had many discussions in the last months and in my opinion it would already helpfull to get an special release for third-party users. Which means:

Checked it. Great!
You have my OK :-))

+1 one year would be great. should we try to get the data of from 1. 1. 2014 to 31. 12. 2014?

We planned to make a survey of Stakeholder members as a basis for a MediaWiki Usage Report.
Here is an example for a result.