FYI.
---------- Forwarded message ----------
From: Erik Moeller <erik(a)wikimedia.org>
Date: Fri, Feb 21, 2014 at 2:35 PM
Subject: Language Engineering team changes
To: All Wikimedia Foundation Staff
Hi folks.
After some internal conversations, we've implemented the following
changes on the Language Engineering team:
- Amir Aharoni is currently the Acting Product Manager;
- Runa Bhattacharjee is the ScrumMaster.
Siebrand Mazeland is no longer part of the Wikimedia Language
Engineering team. We're maintaining a part-time contract relationship
with Siebrand to support MediaWiki developers with i18n/l10n-related
questions, to provide continuous review of MediaWiki changes from an
i18n/l10n perspective, and to support translatewiki.net requirements
which intersect with Wikimedia Foundation priorities and ongoing
localization updates.
I want to thank Siebrand for serving as the team's Product Manager
since July 2011, and for continuing to partner with us on i18n/l10n
issues and on translatewiki.net, which is an essential part of the
Wikimedia localization process.
Thanks,
Erik
--
Erik Möller
VP of Engineering and Product Development, Wikimedia Foundation
--
Erik Möller
VP of Engineering and Product Development, Wikimedia Foundation
An analysis of Syrian internet censorship shows Wikimedia sites among the
top 10 censored domains. See Table 5 on page 6.
The data they're analyzing is the filtering proxy logs from October 2011,
so a lot's changed in our systems since then; for instance, the section on
page 7 regarding HTTPS traffic might be completely inapplicable to us now.
But I figured it was worth passing around.
Paper: http://arxiv.org/pdf/1402.3401.pdf , found via
http://boingboing.net/2014/02/18/detailed-analysis-of-syrias.html .
"Censorship in the Wild: Analyzing Web Filtering in Syria" by Abdelberi
Chaabane, Mathieu Cunche, Terence Chen, Arik Friedman, Emiliano De
Cristofaro, and Mohammed-Ali Kafaar.
Sumana Harihareswara
Engineering Community Manager
Wikimedia Foundation
Hi All
FOSSASIA is an exciting free Open Technology event for students, developers
and start ups. It is a unique opportunity to share knowledge and experience
about open source technologies and meet interesting contributors.
This year FOSSASIA 2014 will be held at Norton University in Phnom Penh,
Cambodia from February 28 - March 2.
Event Page of FOSSASIA
https://www.mediawiki.org/wiki/Events/FOSSASIA
If you are near that place you can join with us.
Thanks
Harsh
--
Harsh Kothari
Intern at Google Summer of Code,
Wikimedia Foundation
Follow Me : harshkothari410 <https://twitter.com/harshkothari410/>
I'd like to transfer the github repo for Bingle to the organization
(currently it's associated with my personal github account). According to
https://help.github.com/articles/how-to-transfer-a-repository that means
I'll need administrative rights in order to do so. Can someone help me out
with this?
--
Arthur Richards
Software Engineer, Mobile
[[User:Awjrichards]]
IRC: awjr
+1-415-839-6885 x6687
Hello,I would like give a proposal for inclusion of Allow smoother and easier Wikimedia Commons pictures discovery of Bug:57805 in the Featured Project ideas Section of https://www.mediawiki.org/wiki/Summer_of_Code_2014 Page.
Thank YouAalekh Nigam"aalekhN"
Hi,
Do you have an understanding of python or C++? WE NEED YOU!
Huggle 3 is an antivandalism tool used on wikipedia and some other
wikimedia projects. It's written in C++ with use of Qt framework and
it also contains embedded python interpreter so that it can be
extended with python extensions (as well as with c/c++ extensions).
Currently the dev team consist only of 2 active developers (by active
we mean they push at least 1 commit per week) which makes the
development extremely slow.
Any help would be greatly appreciated. If you were interested in
joining our small & friendly dev team, join #huggle @freenode.net,
send an e-mail to our mailing list: huggle(a)lists.wikimedia.org or just
fork https://github.com/huggle/huggle3-qt-lx and start sending patches
:-).
Useful links for interested people
===========================
https://en.wikipedia.org/wiki/Wikipedia:Huggle/Feedback - huggle's
talk at english wikipeida
https://meta.wikimedia.org/wiki/Huggle - huggle main page on meta
http://tools.wmflabs.org/huggle/docs/head/ - documentation for developers
http://webchat.freenode.net/?channels=#huggle - IRC chat
https://bugzilla.wikimedia.org/buglist.cgi?component=Application&list_id=27…
Bugs that wants a fix :P
P.S. We will be at Zurich, so if you wish to hack huggle at hackaton,
come there!
Hi!
In a shameless copy of Sumana's August 2012 idea, I'd like to send
public thanks to some people who have helped me get some things done in
the past few weeks/days:
* Guillaume Paumier, for his overall amazingness and his help in
creating and distributing the weekly Tech News bulletin;
* Daniel Zahn (mutante) and Sam Reed (Reedy) for their help in getting
my Gerrit patches reviewed & merged (long overdue!);
* Ariel Glenn (apergos) for triaging my latest RT ticket and for being
so nice and understanding on a Sunday evening ;-)
So, if you'd like to thank someone, now is a good time and opportunity
to do so! Following Sumana's example, the rules are: "be kind, thank
someone, and say why you're thanking them."
Tomasz
I got permission from Reuben Smith of wikihow and WMF release manager Greg
Grossmeier to re-post this exchange.
Sumana Harihareswara
Engineering Community Manager
Wikimedia Foundation
Reuben Smith of wikiHow asked:
"We're having a hard time figuring out whether we should be basing our
wikiHow code off Mediawiki's external releases (such as the latest 1.22.2),
or off the branches that WMF uses for their internal infrastructure (latest
looks to be wmf/1.23wmf14).
Do you have any thoughts of guidance on that? We're leaning towards moving
to using the WMF internal branches, since we use MySQL as well, but I
wanted to hear from different people about the drawbacks."
Greg Grossmeier responded:
"The quick answer is:
Feel free to base it off of either. There shouldn't be any WMF-specific
things in those wmfXX branches. If there is, it is a commit called
something like "Commit of various WMF live hacks". That one commit can
be safely reverted.
The wmfXX branches are made every week on Thursday morning (Pacific)
before we deploy. As we get closer to the next release (1.23) the
MediaWiki Release Managers (our outside contractors, Mark and Markus,
not myself) will pick a wmfXX to call a Release Candidate.
Going with a 1.22.x would give you stability at the loss of getting
fixes faster and it means a bigger upgrade task when 1.23 is out.
Summary: If you want to keep closer to WMF, pick a wmfXX branch (this
assumes you'll follow at some pace behind WMF). If you don't want to be
that bleeding edge, stick with 1.22.x.
Hope that helps,
Greg
PS: To learn more about our deploy cycle, see:
https://wikitech.wikimedia.org/wiki/Deployments/One_week
PPS: To see where we are at any given point, wrt MediaWiki, see:
https://www.mediawiki.org/wiki/MediaWiki_1.23/Roadmap#Schedule_for_the_depl…"