Hello all,
You can watch the iconathon here:
http://youtu.be/sei9SeoObJA
If you would like to participate in the hangout, please email me, Pau Giner
(pginer(a)wikimedia.org) or Vibha Bamba (vbamba(a)wikimedia.org).
Thanks!
Munaf
Sumana,
SMC is one of the oldest open source projects from India focused on improving Indic language computing. Also Santhosh Thottingal of Wikimedia's I18n team is one of the founding members of SMC :-)
Looking forward to a great GDoC summer ahead!
Alolita
__
Alolita Sharma
Wikimedia Foundation
----- Reply message -----
From: "Sumana Harihareswara" <sumanah(a)wikimedia.org>
To: "Wikimedia developers" <wikitech-l(a)lists.wikimedia.org>
Subject: [Wikitech-l] GSoC: accepted! Mentors: apply, please
Date: Mon, Apr 8, 2013 6:19 pm
On 04/08/2013 07:40 PM, Quim Gil wrote:
> It's official! Today Wikimedia has been accepted into Google Summer of
> Code together with other 176 organizations:
Thank you, Quim! I'm glad you're able to take over administering our
GSoC this year and that we are (in my opinion) on our way to a
fulfilling Summer of Code.
Also: Wikimedia uses lots of open source software, and I hope we will
benefit from GSoC students' work on Debian, LibreOffice, Nmap, OWASP,
Python, Linux, WordPress, and more. Through GSoC I've learned of other
FLOSS projects I hadn't heard of before, such as Swathanthra Malayalam
Computing https://www.google-melange.com/gsoc/org/google/gsoc2013/smc
which works on Malayalam-related software internationalisation. So, yay
for new contributors to our larger community as well.
--
Sumana Harihareswara
Engineering Community Manager
Wikimedia Foundation
_______________________________________________
Wikitech-l mailing list
Wikitech-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Hi.
I'm concerned that Gerrit actively discourages discussion currently. I see
a few issues:
* auto-collapsing all comments except the most recent;
* no reply feature or support for quoting (similar to what Bugzilla uses);
and
* the "add comment" feature doesn't allow you to write a comment while
viewing the code or viewing the other comments, resulting in an awful
workflow for me when attempting to write a comment.
Is there some way to address these issues? Would it make sense to move all
discussion back to Bugzilla? Is there some way to adjust Gerrit's behavior
here? Or perhaps I'm the only one who finds this problematic.
MZMcBride
Hi, I need to use the localization framework - wfMessage() to translate my
own custom messages. I have a message dictionary in the form of
{languageCode => message, ...}, and looking for a way to inject those
messages into the message cache. The actual messages dictionary is stored
as a custom setting as part of a json blob, and cannot be added to the
regular $message['xx'] = '...'; for translatewiki. Thanks!
Usage scenario:
// Array is generated from an external source and will look like this:
$messageMap = array('en'=>'aaa', 'fr'=>'b {{SITENAME}} b', ...);
// Some magic method to add the entire message map into message cache
messageCache->Add('custom-key1', $messageMap);
// Process message
// Note that in case 'fr' is not defined, it should fallback using default
resolution rules.
$result = wfMessage('custom-key1')->inLanguage('fr')->text();
I came across http://www.whatcanidoformozilla.org/ today, and
proceeded to register whatcanidoforwikipedia.org :)
Thoughts on what to put there? I cal already think of the following
languages to put up:
1. PHP
2. JS
3. Lua
4. Python
5. Java
6. Obj-C
7. 'Design'
I'll start a wiki page sometime to collect content, and then spend
some time writing the code - we can even fork the original site's code
and use it.
Thoughts?
P.S. Can we *please* not bikeshed on the domain name? Domain names are cheap
--
Yuvi Panda T
http://yuvi.in/blog
In case y'all missed this:
----- Forwarded Message -----
> From: "PRIVACY Forum mailing list" <privacy(a)vortex.com>
> To: privacy-list(a)vortex.com
> Sent: Saturday, April 6, 2013 3:10:01 PM
> Subject: [ PRIVACY Forum ] French homeland intelligence threatens a volunteer sysop to delete a Wikipedia Article
> French homeland intelligence threatens a volunteer sysop to delete a
> Wikipedia Article
>
> http://j.mp/16C8Cxn (Wikimedia France)
>
> "Unhappy with the Foundation's answer, the DCRI summoned a Wikipedia
> volunteer in their offices on April 4th. This volunteer, which was one
> of those having access to the tools that allow the deletion of pages,
> was forced to delete the article while in the DCRI offices, on the
> understanding that he would have been held in custody and prosecuted
> if he did not comply. Under pressure, he had no other choice than to
> delete the article, despite explaining to the DCRI this is not how
> Wikipedia works. He warned the other sysops that trying to undelete
> the article would engage their responsability before the law. This
> volunteer had no link with that article, having never edited it and
> not even knowing of its existence before entering the DCRI offices. He
> was chosen and summoned because he was easily identifiable, given his
> regular promotional actions of Wikipedia and Wikimedia projects in
> France."
>
> - - -
>
> The return of "Vichy France" mentalities, apparently.
>
> --Lauren--
> Lauren Weinstein (lauren(a)vortex.com): http://www.vortex.com/lauren
> Co-Founder: People For Internet Responsibility:
> http://www.pfir.org/pfir-info
> Founder:
> - Network Neutrality Squad: http://www.nnsquad.org
> - PRIVACY Forum: http://www.vortex.com/privacy-info
> - Data Wisdom Explorers League: http://www.dwel.org
> - Global Coalition for Transparent Internet Performance:
> http://www.gctip.org
> Member: ACM Committee on Computers and Public Policy
> Lauren's Blog: http://lauren.vortex.com
> Google+: http://vortex.com/g+lauren / Twitter:
> http://vortex.com/t-lauren
> Tel: +1 (818) 225-2800 / Skype: vortex.com
>
> _______________________________________________
> privacy mailing list
> http://lists.vortex.com/mailman/listinfo/privacy
--
Jay R. Ashworth Baylink jra(a)baylink.com
Designer The Things I Think RFC 2100
Ashworth & Associates http://baylink.pitas.com 2000 Land Rover DII
St Petersburg FL USA #natog +1 727 647 1274
<Tron>Greetings, Programs!</Tron>
So, not many updates for a while, as things have been progressing at a
fair clip in the "oh, my god boring gruntwork" front.
The biggest news is the addition of Petr Bena to the tools project
sysadmin team as its first volunteer. Petr has been very involved in
the setup and administration of the Tool Labs' predecessor projects, and
will continue to steer the bots project where the rules are a little
more relaxed to facilitate more experimental development.
He's also joining me on the tools project proper, to help provide
support to maintainers over a wider range of times, and to increase
availability of sysadmins. You can find him hanging around
#wikimedia-labs, often at times where I am not available.
There is some documentation-in-progress that give a lot of information
on how to set up your tools on the Labs architecture at:
https://www.mediawiki.org/wiki/Wikimedia_Labs/Tool_Labs/Help
Please don't hesitate to comment if you see missing information, or if
parts of it are less clear than idea.
On the other fronts, the wikitech management interface is now in place
for self-serve of tool account creation by Labs users; this requires
moving already-existing tool accounts to the new scheme, and a brief
outage for that purpose later this week (see note below)
Experiments with a bulletproof replacement for gluster are well on their
way; with NFS from a highly redundant server as the currently favored
option. With a bit of luck, I'll use the opportunity given by the
outage for the tool account switchover to move the shared tools
filesystem to NFS as a trial run.
The database replication is also well on its way; you can find the
current roadmap at:
https://wikitech.wikimedia.org/wiki/Tool_Labs/Database_plan
=== Planned outage ===
In order to move the extant tool accounts to the new, final scheme, and
(progress permitting) move the shared filesystems to a new storage
server, there will be a brief outage of the Tool Labs infrastructure
this Thursday April 11 starting at 16:00 UTC. The outage is expected to
last 20 minutes during which service will be intermittently unavailable.
Announcements will be sent by email, on IRC and on the servers 30
minutes before the start of maintenance, at its start, and upon completion.
Impact:
* Jobs running on the grid engine will be stopped then restarted
automatically at the end of the maintenance window. If you are running
a job that cannot or should not be restarted automatically without
intervention from its maintainers, please make certain that it has been
stopped before the start of the maintenance window;
* The login server will be restarted during the window, ending active
sessions;
* The web service will be intermittently unavailable; and
* Running processes not scheduled through the grid engine will be killed.
Recovery plan:
In case of unplanned failure during the maintenance window,
configuration will be rolled back to the current version and a new
window will be planned after postmortem. Disruption of services will
take place as noted and an announcement will be sent.
-- Marc