[Wikimedia-l] Thoughts on Admin Rights on WMF Wiki (and other things)

2013-05-22 Thread Gayle Karen Young
* Hi folks! I felt like Sue did a nice job earlier of responding in an earlier thread of http://lists.wikimedia.org/pipermail/wikimedia-l/2013-May/125807.html, but here’s my response as well. Wikimedia Foundation wiki has always been uniquely governed among the family of Wikimedia wikis, with de

Re: [Wikimedia-l] making tech journalism easier to read

2013-05-22 Thread Tilman Bayer
I would like to remind everyone that many blog posts are now drafted in public at https://meta.wikimedia.org/wiki/Wikimedia_Blog/Drafts . Pre-publication copyedits or comments on better structuring etc. are welcome there, so don't feel restricted to posting armchair advice on mailing lists ;) For

Re: [Wikimedia-l] New design for the list info page?

2013-05-22 Thread Quim Gil
Version 1.0 is out: https://lists.wikimedia.org/mailman/listinfo/wikitech-announce Source: https://github.com/quimgil/mailman-templates Propagation is welcome. Thank you TheHelpfulOne for the original push and to the other feedback reporters! On Mon, May 20, 2013 at 11:09 PM, Quim Gil wrote:

Re: [Wikimedia-l] making tech journalism easier to read

2013-05-22 Thread Federico Leva (Nemo)
Quim Gil, 22/05/2013 18:48: [...] We can probably add "The Microblogging Sharing Test" to our headlines. :) [...] I believe this is one of the methods used by the fundraising team (unless I'm confused by someone else's campaign; perhaps the German anti-AFTA campaign). Nemo _

Re: [Wikimedia-l] making tech journalism easier to read

2013-05-22 Thread Quim Gil
On 05/22/2013 08:39 AM, Florence Devouard wrote: My main suggestion (valid for all posts, technical or not) would be to start with a clearly identified cap as summary. And put an extra effort so that this cap is written in simple and straightforward message. Yes! Don't assume readers will reach

Re: [Wikimedia-l] making tech journalism easier to read

2013-05-22 Thread Florence Devouard
Hi My main suggestion (valid for all posts, technical or not) would be to start with a clearly identified cap as summary. And put an extra effort so that this cap is written in simple and straightforward message. In that regards, this post is pretty good generally http://blog.wikimedia.org/20

Re: [Wikimedia-l] making tech journalism easier to read

2013-05-22 Thread Federico Leva (Nemo)
Quim Gil, 21/05/2013 23:15: [...] Good journalism is mostly about a lead paragraph for the masses followed by an increasingly dense body text (aka the 5 Ws and the inverted pyramid). You can adapt and change these rules at will, as long as you are aware of them. Paying more editorial attention t

Re: [Wikimedia-l] The case for supporting open source machine translation

2013-05-22 Thread Federico Leva (Nemo)
Erik Moeller, 24/04/2013 08:29: [...] Could open source MT be such a strategic investment? I don't know, but I'd like to at least raise the question. I think the alternative will be, for the foreseeable future, to accept that this piece of technology will be proprietary, and to rely on goodwill f

Re: [Wikimedia-l] making tech journalism easier to read

2013-05-22 Thread Jane Darnell
I agree with everyone here and would add that no matter how hard to read, *any blog entry at all* on this Tech stuff is highly welcome, because it also serves as a written record to refer back to in various ongoing technical projects. Any documentation at all is better than none. I find myself regu

Re: [Wikimedia-l] making tech journalism easier to read

2013-05-22 Thread Lodewijk
I think what is even more helpful to people, is to avoid abbreviations as much as possible, or explain them. For example: * Up-Goer 5 (but there was a link next to it - which allows you to guess what it means) * SMOG (the stuff that is in the air, right?) * FKT Usually this kind of abbreviations (