The only concern is that Wikidata is a single wiki and not all users on a given wiki will be concerned (except for adding interwiki links but technically ll is done on this subject). The rest is about data that will be used by tricky templates and whose readers would be more technical users than usual.

So if you add things about Wikidata, this should be generic enough to interest most people (notably contributors writing articles) and not just developers of tricky templates using Wikidata; such things could include some technical issues to discuss about translation and localisation of this data, creation of Wikidata user groups interested in some projects (such as adding reference IDs or supporting the integration of some data related to GLAM collections).

If this is just to discuss about migration of ontologies, and this does not require a large participation (if this can be done essentially by bots), then I think that these technical news should remain on Wikidata (and use a separate distribution for real developers of Wikidata): nothing forbids duplicating an announcement on both letters, but typically the annoucement in Tech News should be much shorter than the Wikidata technical news. If the tech news is just about the change of support of specific extensions used only by Wikidata, this should not be in Wikimedia Wiki Tech news which are really cross-project and should interest most users of Wikimedia sites contributing pages (and that's why the VisualEditor takes a good place in these Wikimedia Tech News).

Note also that most news related to Meta-Wiki and policies (or financement campaigns, or elections in the WMF comitees) are handled in a separate messaging system (currently using the old "Goings-on" system that should evolve later after the Main Page will be really fully translatable with the Translate tool) : they are also announced not primarily by MassMessage but by global site notifications (but some users may opt to receive these Wikimedia notifications by mail, notably for things like new global policies or guidelines, or opening of a new Wikimedia content project).

2014-06-22 13:10 GMT+02:00 Amir E. Aharoni amir.aharoni@mail.huji.ac.il:

What makes more sense at this point is to start adding a paragraph about Wikidata to the Tech News as they are rather than having a whole separate translatable newsletter. In the Tech News there's a whole paragraph every week about the VisualEditor, and there are short updates about CirrusSearch and MediaViewer almost every week. A weekly update about Wikidata can be there, too. If a whole paragraph is too long, a couple of the most important points would be a good beginning.

It takes me less than ten minutes a week to translate each whole Tech News issue. Adding a few sentences about Wikidata should add no more than two minutes to the time that the translators already invest. I think that it's perfectly doable.

-- Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי http://aharoni.wordpress.com ‪“We're living in pieces, I want to live in peace.” – T. Moore‬

2014-06-22 13:32 GMT+03:00 Bohdan Melnychuk base-w@yandex.ru:

...

Hello,

I want the subject's mailing list to be translatable and delivered the same way as it's with Tech news. I've asked about it on it's subscription page's talk page and faced there Lydia, who doesn't believe that there would be any volunteers (except for me in the current point) to translate it.

So if you would like to translate the newsletter when it would be set to be possible, could you leave a note in [[:m:Talk:Global_message_delivery/Targets/Wikidata#Multilingual distribution https://meta.wikimedia.org/wiki/Talk:Global_message_delivery/Targets/Wikidata#Multilingual%20distribution]] about your willing so we get Lydia convinced :) Poking friends who may do it is welcome as well ;)

Also it would be nice if Odder or/and Guillom leave a note about technical side of such delivery the same way as the latter was so kind to leave in Education newsletter's talk :)

Yours sincerely, --Base

---

Translators-l mailing list Translators-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/translators-l

---

Translators-l mailing list Translators-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/translators-l

2014-06-22 16:28 GMT+02:00 Amir E. Aharoni amir.aharoni@mail.huji.ac.il:

...

The only concern is that Wikidata is a single wiki and not all users on a given wiki will be concerned (except for adding interwiki links but technically ll is done on this subject). The rest is about data that will be used by tricky templates and whose readers would be more technical users than usual.

It's a single wiki used by a lot of other wikis. Quite like Commons, and news about tech updates on Commons do make it to Tech News.

Yes I know, but for now such usage, it is not enough friendly for most users as it is complicate to contribute there, except for adding translations of labels and adding interwikis.

Wikidata is severely underused by templates, even though templates are supposed to be Wikidata's biggest killer application, so more PR about it really won't hurt. Examples of successful use of Wikidata in templates in some projects, even without tricky technical details, can go a long way to furthering Wikidata adoption.

Most of the work for now involve technicians, and the tech news about wikidata will almost only interest them. That's why I still suggest developing your separate Wikidata Tech news, even if sometimes (rarely for now) there will be a shorter summary posted in the Wikimedia tech news. It could be useful for example if there are specific development in the VisualEditor or other new generic tools (such as a cross-wiki template transclusion namespace acting like the Image: namespace, and allowing Wikidata to be really used more widely across wikis.

Other news that will intererest anyone is about maintenance of Wikidata where it could get offline (because this affects existing functionalities like interwikis): they merit being in the Wikimedia Tech news as everyone will see the impact of such down times or failures.

This is my opinion.