<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.science.linguistics.wikipedia.technical">
    <title>gmane.science.linguistics.wikipedia.technical</title>
    <link>http://blog.gmane.org/gmane.science.linguistics.wikipedia.technical</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.science.linguistics.wikipedia.technical/70347"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.science.linguistics.wikipedia.technical/70344"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.science.linguistics.wikipedia.technical/70343"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.science.linguistics.wikipedia.technical/70334"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.science.linguistics.wikipedia.technical/70330"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.science.linguistics.wikipedia.technical/70327"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.science.linguistics.wikipedia.technical/70325"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.science.linguistics.wikipedia.technical/70323"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.science.linguistics.wikipedia.technical/70321"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.science.linguistics.wikipedia.technical/70308"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.science.linguistics.wikipedia.technical/70291"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.science.linguistics.wikipedia.technical/70283"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.science.linguistics.wikipedia.technical/70273"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.science.linguistics.wikipedia.technical/70257"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.science.linguistics.wikipedia.technical/70252"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.science.linguistics.wikipedia.technical/70248"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.science.linguistics.wikipedia.technical/70239"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.science.linguistics.wikipedia.technical/70238"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.science.linguistics.wikipedia.technical/70232"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.science.linguistics.wikipedia.technical/70231"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://comments.gmane.org/gmane.science.linguistics.wikipedia.technical/70347">
    <title>Finding redirects in file namespace on Commons via API?</title>
    <link>http://comments.gmane.org/gmane.science.linguistics.wikipedia.technical/70347</link>
    <description>&lt;pre&gt;Hi,

to improve duplicate detection for the Open Access Media Importer, we
would like to include redirects in the file namespace, but they do not
come up in searches like
https://commons.wikimedia.org/w/api.php?action=query&amp;amp;list=search&amp;amp;srnamespace=6&amp;amp;srsearch=pone.0008793.s004&amp;amp;srredirects=1
.

For example,
http://commons.wikimedia.org/wiki/File:Animal-behavior-pone.0008793.s004.ogv
redirects to
http://commons.wikimedia.org/wiki/File:A_group_of_50_Drosophila_melanogaster_interacting_in_an_observation_chamber_-_pone.0008793.s004.ogv
.

Thanks for any pointers.

Cheers,

Daniel

_______________________________________________
Wikitech-l mailing list
Wikitech-l&amp;lt; at &amp;gt;lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l&lt;/pre&gt;</description>
    <dc:creator>Daniel Mietchen</dc:creator>
    <dc:date>2013-05-25T20:17:14</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.science.linguistics.wikipedia.technical/70344">
    <title>Architecture guidelines and RFCs</title>
    <link>http://comments.gmane.org/gmane.science.linguistics.wikipedia.technical/70344</link>
    <description>&lt;pre&gt;Hi folks,

Many of us met at the Amsterdam Hackathon to discuss architecture
guidelines (almost everyone with +2 in MediaWiki core, plus other
knowledgeable people), and generally about the need to have more
substantive conversations about MediaWiki architecture.  It was a
really productive discussion, and had a number of outcomes:

1.  RFC review: we agreed that RFCs need more diligent review.  Brion
and Tim are planning to pull together the architects for regular
discussions (weekly? TBD) to at least touch all of the outstanding
RFCs, with the goal of clearing the current backlog of RFCs.  If y'all
don't see substantial movement on this in a couple of weeks, please
point this out.

2.  RFC use: right now, RFCs aren't used in many cases where they
should be.  Assuming we get into a good flow with RFCs, we can then
reasonably expect people to actually write them when they're making
significant changes to the MediaWiki architecture.

3.  Architecture guidelines: we now have a rough beginning draft of
architecture guidelines[2] we plan to use as guiding principles for
RFC review.  This is a document that we plan to discuss on wiki in c2
wiki style[3].  Please participate!  This is a living document, which
will be referenced in RFCs and responses to RFCs.  We will use this
mailing list to discuss the more contentious issues and generally
ensure we continue to move forward refining this document.

4.  A general agreement that we need to make sure that we have similar
conversations at every substantial gathering of +2 developers.  For
example, we plan to figure something out for Wikimania.

We have raw notes from both days of meetings, available here:
https://www.mediawiki.org/wiki/Amsterdam_Hackathon_2013/Architectural_principles_document

Rob

[1] http://www.mediawiki.org/wiki/Requests_for_comment
[2] https://www.mediawiki.org/wiki/Architecture_guidelines
[3] "c2 wiki style" is with inline comments similar to the c2 Design
Patterns wiki: http://c2.com/cgi/wiki?DesignPatterns

_______________________________________________
Wikitech-l mailing list
Wikitech-l&amp;lt; at &amp;gt;lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l&lt;/pre&gt;</description>
    <dc:creator>Rob Lanphier</dc:creator>
    <dc:date>2013-05-25T13:50:04</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.science.linguistics.wikipedia.technical/70343">
    <title>Major take-away from architecture meeting at Hackathon: RFCs will be reviewed by architecture group by Wikimania</title>
    <link>http://comments.gmane.org/gmane.science.linguistics.wikipedia.technical/70343</link>
    <description>&lt;pre&gt;For those of you not at the hackathon, there is one very major result
from the meeting that I wanted to publicize.  (There are other action
items which I'll let other people expand but this one seems most
important to me.)  If I misunderstood or mis-state something, Robla and
others can correct me.

Our RFC process has been broken till now.  WMF's architecture group has
just committed to review and respond to all RFCs by WikiMania.  This
will probably involve clarifying the process that RFCs are reviewed and
providing better documentation for architectural and design direction.

I expect there will be more coming out of this meeting, but I wanted to
post this note so I would remember to ask Brion about the RFCs he has
reviewed next Friday.

Mark.

&lt;/pre&gt;</description>
    <dc:creator>Mark A. Hershberger</dc:creator>
    <dc:date>2013-05-25T13:10:42</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.science.linguistics.wikipedia.technical/70334">
    <title>Information on MW and Redis?</title>
    <link>http://comments.gmane.org/gmane.science.linguistics.wikipedia.technical/70334</link>
    <description>&lt;pre&gt;Hello all,

I keep seeing references in WMF documents to using Redis for session storage and as the storage for the job queue going forward. However, LocalSettings doesn't have any references to Redis. It looks like the session changes for Redis were in 1.20, and I thought that the change for the job queue to be backed by Redis was coming in 1.21. It also seems that Notifications (Echo) may require Redis, but that's not real clear.

I'm wondering what the general status of this is? As a 3rd party mediawiki admin, I'm eager to get redis going primarily for the job queue improvements, but with nothing noted in local settings documentation I'm wondering what the plan is for these redis based features? Will $wgMainCacheType be getting a CACHE_REDIS option?

Jamie Thingelstad
jamie&amp;lt; at &amp;gt;thingelstad.com
mobile: 612-810-3699
find me on AIM Twitter Facebook LinkedIn

_______________________________________________
Wikitech-l mailing list
Wikitech-l&amp;lt; at &amp;gt;lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l&lt;/pre&gt;</description>
    <dc:creator>Jamie Thingelstad</dc:creator>
    <dc:date>2013-05-24T19:39:23</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.science.linguistics.wikipedia.technical/70330">
    <title>Publish-staying-in-editmode feature for WikiEditor</title>
    <link>http://comments.gmane.org/gmane.science.linguistics.wikipedia.technical/70330</link>
    <description>&lt;pre&gt;Hello!

I have implemented an idea for WikiEditor extension: replace 
"step-by-step publish" feature with another one - "publish staying in 
edit mode via AJAX". You can see a demo at http://wiki.4intra.net/ if 
you want. It works simply by sending an API save article request while 
NOT closing the article being edited. Also it handles section edits 
correctly via re-requesting section content after editing, so you'll 
stay with consistent edit form even if you add sections.

The idea is to give authors the ability to save intermediate results.

My question is - does anyone really need "step-by-step publishing" 
feature that is in WikiEditor? I think it's useless because it just 
duplicates the existing functionality, just submits the form using 
normal POST request, and makes editing harder as you have to do more 
clicks. I would submit a patch to Gerrit if you're interested in 
replacing it with "publish-staying-in-editmode".

&lt;/pre&gt;</description>
    <dc:creator>vitalif&lt; at &gt;yourcmc.ru</dc:creator>
    <dc:date>2013-05-24T11:26:20</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.science.linguistics.wikipedia.technical/70327">
    <title>database encoding for field with mathematicalexpressions</title>
    <link>http://comments.gmane.org/gmane.science.linguistics.wikipedia.technical/70327</link>
    <description>&lt;pre&gt;Hi,

I'm a testing a new rendering option for the &amp;lt;math /&amp;gt; element and had
problems to store MathML elements in the database field
math_mathml which is of type text.
The MathML elements contain a wide range of Unicode characters like the
INVISIBLE TIMES that is encoded as 0xE2 0x81 0xA2 in UTF-8 or even 4 byte
chars like MATHEMATICAL BOLD CAPITAL A  0xF0 0x9D 0x90 0x80 .
In some rar cases I had problem to retrieve the stored value correctly from
MySQL.
To fix that problem I'm now using the PHP functions utf8_encode /decode to
which is not a very intuitive solution.
Do you know a better method to solve this issue without to change the
database layout.

Best
Physikerwelt




_______________________________________________
Wikitech-l mailing list
Wikitech-l&amp;lt; at &amp;gt;lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l&lt;/pre&gt;</description>
    <dc:creator>physik&lt; at &gt;physikerwelt.de</dc:creator>
    <dc:date>2013-05-24T03:31:18</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.science.linguistics.wikipedia.technical/70325">
    <title>pt.wp Mentorship Program</title>
    <link>http://comments.gmane.org/gmane.science.linguistics.wikipedia.technical/70325</link>
    <description>&lt;pre&gt;On pt.wikipedia there is a lack of local tech people who can do simple
things like fixing a .js gadget (or creating one for a specific and local
utility), or a simple bot script, and when it comes to lua modules, it's
easy to guess... After a discussion, we've decided to implement our own
local version of wmf mentorship programs like LevelUp, but instead of
competing with them, complement where we can.[0] It basically intents to
fill the gap between those who would like to know some js to deal with
gadjets or lua to create nice modules, or even python to write some basic
bots, and then those who wish to go further, they'll always have global
programs.

We'll basically start slowly on Python, we've created some doc, mostly to
introduce and inform where to find the info, both on web or on mw. We're
trying not to replicate information, just stick to fill the blanks, and
mapping the disperse info (Gil and Sumana had gave a lot of good advices,
by the way).

So now that we're trying to get it to work, is there any similar program on
other wm project to share experiences, or specially for those who had been
mentors on global projects, any suggestion or advice? As far as i know,
none of us have participated on a similar project, so we're accepting free
( a(s|nd) free bee r) suggestions :D


Now, a second question. We're starting on python, more precisely python +
pywpbot, and i was wondering what would be the most appropriated place
where this scripts could be tested. It could be on pt.wp, but people can be
afraid of breack something, at least when i cooked my first py script, i
only got confident once i got the bot flag on test, could test it on a few
pages there. Could http://test.wikipedia.org/ this purpose, or is there any
other place where they wount feel the "elephant in a *porcelain store"
syndrome? (This is a common Portuguese *saying, i believe you got the
message)


Cheers,
&lt;/pre&gt;</description>
    <dc:creator>Alchimista</dc:creator>
    <dc:date>2013-05-23T23:18:09</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.science.linguistics.wikipedia.technical/70323">
    <title>Need help with a Jenkins PHPUnit build failure</title>
    <link>http://comments.gmane.org/gmane.science.linguistics.wikipedia.technical/70323</link>
    <description>&lt;pre&gt;In trying to submit https://gerrit.wikimedia.org/r/#/c/63907/18, I get a
Jenkins build failure due to PHPUnit failing, due to a Fatal being thrown:
https://integration.wikimedia.org/ci/job/mwext-MobileFrontend-testextensions-master/898/console

The fatal:

PHP Fatal error:  Class 'MFMockRevision' not found in
/srv/ssd/jenkins/workspace/mwext-MobileFrontend-testextensions-master/extensions/MobileFrontend/tests/MobileContextTest.php
on line 500


The thing is, 'MFMockRevision' should be made available by it's file
being included in efExtMobileFrontendUnitTests() (our hook handler for
UnitTestsList.


Unit tests execute fine for me and at least one other person on the
mobile team. I do not want to manually merge that patchset since I
imagine it would cause build failures on subsequent patchset +2's.
Anyone know what might be going on?


&lt;/pre&gt;</description>
    <dc:creator>Arthur Richards</dc:creator>
    <dc:date>2013-05-23T20:59:38</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.science.linguistics.wikipedia.technical/70321">
    <title>jQuery.IME extensions for Firefox and Chrome</title>
    <link>http://comments.gmane.org/gmane.science.linguistics.wikipedia.technical/70321</link>
    <description>&lt;pre&gt;Hello,
Resolved and Committed on the Issue 163:Adding Keyboard navigation in
jQuery.IME's language selection dropdown
list.https://github.com/wikimedia/jquery.ime/issues/163

Here is the
Commit:https://github.com/kaushalsingh11/jquery.ime/commit/3ba4a427f8b50432300e7081a4502197e84728b0

Have also sent the pull request.

Have already posted on BugZilla on 18th May
&lt;/pre&gt;</description>
    <dc:creator>KAUSHAL SINGH</dc:creator>
    <dc:date>2013-05-23T13:28:34</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.science.linguistics.wikipedia.technical/70308">
    <title>Querying the database</title>
    <link>http://comments.gmane.org/gmane.science.linguistics.wikipedia.technical/70308</link>
    <description>&lt;pre&gt;I do a lot of maintenance tasks on Commons, and many tasks require some sort of database query to find the oddball cases. The queries can be done through one of several ways:
1) Using CatScan and CatScan2[2] tools
2) Database query service [3]
3) Weekly Database reports [4]

Unfortunately lately some of those ways are breaking down. CatScan and CatScan2 rarely work failing in many different ways: usually due to exceeding the 'max_user_connections' (30 for magnus's CatScan2, and 15 for Daniel's CatScan), but otherwise with some timeout or no-connection errors, or can work on a query for hours (or days if you let it) and never returns anything. I developed some CatScan2 based queries for Creator template maintenance, that worked fine 2-3 years ago, but always time-out since. That might be due more and more images on Commons.  Similarly, Database query service seems also very inactive. There are many requests and few replies, like my request from April 2 [5]. 

For example, lately I was searching for images on Commons that do not have any license templates (sometimes since 2007 or earlier), see [5]. At some point 
Magnus was helping me with that query, however after it  failed several times with "server not found" error we gave up. It seems like less and less can be done with current infrastructure.

So are there any non-toolserver based alternatives for database queries? I was trying to read about Wikimedia Labs looking for tools based on them. Ideally there would be some CatScan2 like tool that is based on different database, with higher number of users allowed. 

Jarek T.
User:jarekt [6]

[1] http://toolserver.org/~daniel/WikiSense/CategoryIntersect.php 
[2] http://toolserver.org/~magnus/catscan_rewrite.php 
[3] https://jira.toolserver.org/browse/DBQ 
[4] http://commons.wikimedia.org/wiki/Commons:Database_reports 
[5] https://jira.toolserver.org/browse/DBQ-201 
[6] http://commons.wikimedia.org/wiki/User:Jarekt 
_______________________________________________
Wikitech-l mailing list
Wikitech-l&amp;lt; at &amp;gt;lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l&lt;/pre&gt;</description>
    <dc:creator>Tuszynski, Jaroslaw W.</dc:creator>
    <dc:date>2013-05-22T20:03:48</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.science.linguistics.wikipedia.technical/70291">
    <title>Loading MediaWiki from some script</title>
    <link>http://comments.gmane.org/gmane.science.linguistics.wikipedia.technical/70291</link>
    <description>&lt;pre&gt;Hey,

I'd like to load MediaWiki from some PHP script and have not been able to
find a way to do this so far.

After someone suggested trying to do this as a maintenance script, I tried
http://pastebin.com/scKFxF2J

That however does not work as there is a check in doMaintenance.php
(shouldExecute) that makes sure initialization is only done when no
function calls are present in the call stack. My script is getting called
by some other library and thus there will clearly be function calls in the
call stack when doMaintenance.php is included. Is it even possible to load
MediaWiki in such a case? And what is this restriction in shouldExecute
good for?

Cheers

--
Jeroen De Dauw
http://www.bn2vs.com
Don't panic. Don't be evil.
--
_______________________________________________
Wikitech-l mailing list
Wikitech-l&amp;lt; at &amp;gt;lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l&lt;/pre&gt;</description>
    <dc:creator>Jeroen De Dauw</dc:creator>
    <dc:date>2013-05-22T15:16:12</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.science.linguistics.wikipedia.technical/70283">
    <title>Hackathon idea: How about a live bug triage and codereview hour ?</title>
    <link>http://comments.gmane.org/gmane.science.linguistics.wikipedia.technical/70283</link>
    <description>&lt;pre&gt;I was thinking about the past hackathons and I realized that the interaction with eachother is often the best way to learn during these events, it's so much quicker than using gerrit/bugzilla/email/IRC.
I also remember that a lot of the time, we do a lot of informal review and assessment of problems during these events.

This time we have a very nice "How to get your code deployed on Wikimedia" workshop. Perhaps in addition to that, it might be a nice idea to do a live "office hour" dedicated to bug assessment and code review ?

People could submit bug reports and gerrit changesets (etherpad?) and then we pick one hour, where a group of us simply try to help people with these issues in any form. We'd have multiple disciplines and areas of expertise being able to chip in, which should be great for the attendees with "why does no one pay attention to my bugreport/patch"-issues.

Does anyone else think something like that might be a nice idea ?
We'd need to find a timeslot though, that's probably gonna be the hardest part. I'm guessing that many WMF folks will have quite a few meetings again.

DJ
_______________________________________________
Wikitech-l mailing list
Wikitech-l&amp;lt; at &amp;gt;lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l&lt;/pre&gt;</description>
    <dc:creator>Derk-Jan Hartman</dc:creator>
    <dc:date>2013-05-21T20:28:12</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.science.linguistics.wikipedia.technical/70273">
    <title>Pre-Release Announcement for MediaWiki 1.19.7 and1.20.6</title>
    <link>http://comments.gmane.org/gmane.science.linguistics.wikipedia.technical/70273</link>
    <description>&lt;pre&gt;This is a notice that on Tuesday, May 21st between 20:00-21:00 UTC
(1-2pm PDT) Wikimedia Foundation will release security updates for
current and supported branches of the MediaWiki software. Downloads
and patches will be available at that time, with the git repositories
updated later that afternoon. Although MediaWiki does not have the
vulnerable feature enabled by default, most wiki using common advanced
features will want to patch for this issue.

_______________________________________________
Wikitech-l mailing list
Wikitech-l&amp;lt; at &amp;gt;lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l&lt;/pre&gt;</description>
    <dc:creator>Chris Steipp</dc:creator>
    <dc:date>2013-05-20T23:01:00</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.science.linguistics.wikipedia.technical/70257">
    <title>Bugzilla Weekly Report</title>
    <link>http://comments.gmane.org/gmane.science.linguistics.wikipedia.technical/70257</link>
    <description>&lt;pre&gt;MediaWiki Bugzilla Report for May 13, 2013 - May 20, 2013

Status changes this week

Reports changed/set to UNCONFIRMED:  0                                   
Reports changed/set to NEW        :  0                                   
Reports changed/set to ASSIGNED   :  0                                   
Reports changed/set to REOPENED   :  0                                   
Reports changed/set to RESOLVED   :  0                                   
Reports changed/set to VERIFIED   :  0                                   

Total reports still open              : 10296                               
Total bugs still open                 : 5642                                
Total non-lowest prio. bugs still open: 5463                                
Total enhancements still open         : 4654                                

Reports created this week: 229                                 

Resolutions for the week:

Wikimedia Bugzilla report (FAILED), Query failure FAILED

Query failure

_______________________________________________
Wikitech-l mailing list
Wikitech-l&amp;lt; at &amp;gt;lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l&lt;/pre&gt;</description>
    <dc:creator>reporter</dc:creator>
    <dc:date>2013-05-20T03:00:02</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.science.linguistics.wikipedia.technical/70252">
    <title>GSoC Virtual Keyboard</title>
    <link>http://comments.gmane.org/gmane.science.linguistics.wikipedia.technical/70252</link>
    <description>&lt;pre&gt;Hi!

As had been planned I have started making the keyboards and first I
implemented the Hebrew language.

I have created a new repository[1].

Links:

GitHub link for Hebrew Keyboard:
[1] https://github.com/SiddhaGanju/Hebrew-Keyboard

&lt;/pre&gt;</description>
    <dc:creator>Siddha Ganju</dc:creator>
    <dc:date>2013-05-19T05:31:31</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.science.linguistics.wikipedia.technical/70248">
    <title>State of MediaWiki's render action (parameter toindex.php)</title>
    <link>http://comments.gmane.org/gmane.science.linguistics.wikipedia.technical/70248</link>
    <description>&lt;pre&gt;Hi.

https://www.mediawiki.org/w/index.php?diff=597288&amp;amp;oldid=579490

https://www.mediawiki.org/w/index.php?diff=691576&amp;amp;oldid=686908


These two diffs explain what happened better than I could. I think this
was the best outcome, but I'm posting on this list in case I missed some
other discussion about the render action and it is, in fact, now
deprecated. I checked the talk page, but didn't see anything.

MZMcBride



_______________________________________________
Wikitech-l mailing list
Wikitech-l&amp;lt; at &amp;gt;lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l&lt;/pre&gt;</description>
    <dc:creator>MZMcBride</dc:creator>
    <dc:date>2013-05-18T19:40:50</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.science.linguistics.wikipedia.technical/70239">
    <title>Hiring Community Liaisons (Contract)</title>
    <link>http://comments.gmane.org/gmane.science.linguistics.wikipedia.technical/70239</link>
    <description>&lt;pre&gt;*

Hey all,

For the last 18 months, the Engineering &amp;amp; Product Development department
has been experimenting with the role of “Community Liaison, Product
Development” - a staff member embedded in the Product team and tasked with
factoring community concerns into our software development process, keeping
editors informed about what we’re doing, and maintaining a dialogue between
those who write code and those who write articles.

While there is always room for improvement, I think this role has shown a
lot of promise.  We have a number of large projects coming down the
pipeline (e.g., visual editor, discussion systems) and we need more help
reaching out to our contributor communities, especially our non-English
speaking projects, as our outreach there has traditionally been challenged.
 We’d like to recruit a small number of English-speaking or multilingual
editors to do the Community Liaison job with different development teams
and focuses.

In particular we’re looking for people with a strong history of
contributions to our projects who can provide sound and reasoned judgment
and are trusted to do so by their community. Speaking other languages in
addition to English is a major plus, as one of the objectives here is to
ensure we can properly interact with and support non-English projects.
 I’ve included the full job description below.

Our immediate need is for help with the Visual Editor.  We’d like to hire a
few community liaisons to help inform different Wikipedia language
communities of the upcoming launch, create spaces for feedback and
discussion, synthesize feedback for the Visual Editor team, and other
activities required to support the Visual Editor launch later this year.

If this is a role that would interest you, please e-mail Philippe Beaudette
at pbeaudette&amp;lt; at &amp;gt;wikimedia.org&amp;lt;https://mail.google.com/mail/?view=cm&amp;amp;fs=1&amp;amp;tf=1&amp;amp;to=pbeaudette&amp;lt; at &amp;gt;wikimedia.org&amp;gt;.
 And if you know someone else who might fit the role, let them know about
it :-). We’re provisionally interested in hiring 2-3 liaisons, at an hourly
rate commensurate with experience.  This can be a part-time role, but we’ll
need at least 15 hours/week for the length of the engagement (minimum 3
months).  Please do apply if you think it’s a role that suits you, and if
you find places we haven’t notified, spread the word!

Thanks.


Howie
*
_________________________
Howie Fung
Director of Product Development
Wikimedia Foundation


*

Community Liaison Job Description

Background Information and Statement of Purpose

The Wikimedia Foundation’s Engineering &amp;amp; Product Development Department is
looking at ways to more effectively incorporate broad community
perspectives in decisions and hold dialogues with our editors about the
scope, pace and features of upcoming changes to Wikimedia projects. As part
of this, it is hiring additional Community Liaisons from our volunteer
community.

Scope of Work

Support and improve our ongoing software development projects, in
particular:

   -

   Building up a network of volunteers from both English language and
   non-English language wikis, increasing the number of projects we can
   interact with;
   -

   Engaging the community in the software development process, by acting as
   a conduit for community questions, bugs and and feature requests, talking
   to editors about our work and how they can participate in it effectively,
   and recruiting them for workgroups and studies;
   -

   Being available from time to time to provide expertise and knowledge
   about our projects, including but not limited to training
   externally-sourced staff in the way our projects work, answering their
   questions, and providing expert advice on an ad-hoc basis;
   -

   Ensuring that our community is represented in the decision-making
   process and that our planned software adequately reflects user needs;
   -

   Monitoring Wikimedia projects, with the assistance of a network of
   volunteers, for emerging issues that have an impact on Engineering
   programmes; and
   -

   Other duties as needed.


Requirements

Effective Community Liaisons will be:

   -

   Experienced users of Wikimedia projects, capable of representing our
   community within the Foundation and vice-versa.
   -

   Strong communicators (both verbally and with the written word), able to
   explain our products to different groups of users with different levels of
   technical understanding.
   -

   Able to focus on the larger picture, understanding which concerns and
   views are widespread and which are marginal or individual.
   -

   Approachable, as both users and product developers must be able to trust
   these people for the relationship to function.
   -

   Self-motivated - they will be given important projects and expected to
   execute with little to no supervision.
   -

   Strongly empathetic - they excel at understanding the perspectives of
   others and bridging the gap between different approaches to the world.
   -

   Willing and able to remain resilient in the face of frustration from our
   users, in order to get the job done.


Pluses

Other positive attributes or areas of knowledge include:

   -

   Diverse language skills. While the Wikimedia Foundation communicates
   internally in English, we aim to be able to talk to our different
   communities natively.
   -

   Experience with the software development process. You will be thrown
   into teams that are actively working on new features; having a background
   that reduces the slope of your learning curve is a plus.
   - Familiarity with multiple Wikimedia projects is a major plus; we are
   about more than just Wikipedia.

*
_______________________________________________
Wikitech-l mailing list
Wikitech-l&amp;lt; at &amp;gt;lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l&lt;/pre&gt;</description>
    <dc:creator>Howie Fung</dc:creator>
    <dc:date>2013-05-18T06:00:44</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.science.linguistics.wikipedia.technical/70238">
    <title>Code review for someone who knows OCaml</title>
    <link>http://comments.gmane.org/gmane.science.linguistics.wikipedia.technical/70238</link>
    <description>&lt;pre&gt;If you know OCaml, would you mind taking a look at
https://gerrit.wikimedia.org/r/#/c/64263/ .  Specifically, it looks from
https://gerrit.wikimedia.org/r/gitweb?p=mediawiki/extensions/Math.git;a=blob;f=math/texvc.ml;h=33a14b7be714ae38721fa863c337440b1e4d7115;hb=e3ac067f2bc37289fa46a63bfc996de269cbb8de
like it only prints extra information (beyond the single-letter error
code) for Texutil.Illegal_tex_function .

Given that, I removed parameters from the other ones
(https://gerrit.wikimedia.org/r/#/c/64263/8/MathTexvc.php).  It looks
straightforward, but another set of eyes might help, since I don't know
OCaml.

Thanks,

Matt Flaschen

_______________________________________________
Wikitech-l mailing list
Wikitech-l&amp;lt; at &amp;gt;lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l&lt;/pre&gt;</description>
    <dc:creator>Matthew Flaschen</dc:creator>
    <dc:date>2013-05-18T05:56:29</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.science.linguistics.wikipedia.technical/70232">
    <title>Server reboots now through next week</title>
    <link>http://comments.gmane.org/gmane.science.linguistics.wikipedia.technical/70232</link>
    <description>&lt;pre&gt;This past week there was an important security release for the Linux
kernel. As such, we will be updating and rebooting ALL of our machines
ASAP.

This may affect you.

ALL WMF services will experience some downtime of up to 10 or so minutes
(including Bugzilla, Gerrit, etc).

== SPECIAL CONSIDERATIONS ==

Some machines are OK for us to just reboot as needed but others are
being utilized by others for various tasks (scripts, cronjobs, etc).

If you have jobs running on any machine that you do not have puppetized
(ie: it won't just magically start up again after a reboot) you will
want to restart your jobs after the reboot.

There is, unfortunately, not set schedule of when any particular machine
will be rebooted, but Ops will be giving ~30 minutes notice in the
#wikimedia-operations IRC channel on Freenode. You can watch the public
Server Admin Log at &amp;lt;https://wikitech.wikimedia.org/wiki/Server_admin_log&amp;gt; 
for the warnings and the reboot notice.

Sorry for the invonvenience,

Greg

&lt;/pre&gt;</description>
    <dc:creator>Greg Grossmeier</dc:creator>
    <dc:date>2013-05-17T19:00:35</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.science.linguistics.wikipedia.technical/70231">
    <title>Deployment Highlights - Week of May 20th, 2013</title>
    <link>http://comments.gmane.org/gmane.science.linguistics.wikipedia.technical/70231</link>
    <description>&lt;pre&gt;Hello and welcome to the latest installment of the Deployment Highlights
email.

The full calendar for next week lives at:
https://wikitech.wikimedia.org/wiki/Deployments#Week_of_May_20th

For the week of May 6th we have the following interesting deployments:

== All Week ==

* Due to a security update to the Linux kernel, we will be upgrading and
  rebooting ALL machines throughout the week. This may affect your
  experience with some services, but it should be minimal.


== Monday ==

* VisualEditor will be deploy a new extension, TemplateData, to all
  Wikipedias (&amp;lt;https://bugzilla.wikimedia.org/show_bug.cgi?id=44444&amp;gt;) in
  addition to a VisualEditor configuration change on mediawiki.org
  (&amp;lt;https://bugzilla.wikimedia.org/show_bug.cgi?id=48430&amp;gt;).

* English Wikipedia will be updated to MediaWiki version 1.22wmf4, in
  addition to a WikiData client update on English Wikipedia. See
  &amp;lt;https://www.mediawiki.org/wiki/MediaWiki_1.22/Roadmap&amp;gt;

* An update to HTCP purging will be rolled out by the WMF Operations
  team which might create momentary issues with some thumbnails. Please
  report any issues you experience.


== Wednesday ==

* The rest of the Wikipedias will be updated to MediaWiki 1.22wmf4, thus
  completing the roll out of that version. The next version, 1.22wmf5,
  will start on Monday May 27th. See
  &amp;lt;https://www.mediawiki.org/wiki/MediaWiki_1.22/Roadmap&amp;gt;


== Thursday ==

* The Editor Engagement team (E2) will rollout bugfixes to Notifications
  (Echo). See &amp;lt;http://etherpad.wikimedia.org/echo-release&amp;gt;.


Best,

Greg

&lt;/pre&gt;</description>
    <dc:creator>Greg Grossmeier</dc:creator>
    <dc:date>2013-05-17T18:51:22</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.science.linguistics.wikipedia.technical/70224">
    <title>don't show certain links with the help ofSpecial:AllMessages</title>
    <link>http://comments.gmane.org/gmane.science.linguistics.wikipedia.technical/70224</link>
    <description>&lt;pre&gt;Hi everyone!

I think that Special:AllMessages and the idea that every message in the
wiki has its own wikipage is just _awesome_.
So, I can Replace the "disclaimer" label to smth different
using MediaWiki:Disclaimers. That's great.

However I haven't found the way to HIDE the element. For instance I don't
need the "policy" link in my footer. Is that possible of should I use CSS?
-----
Yury Katkov, WikiVote
_______________________________________________
Wikitech-l mailing list
Wikitech-l&amp;lt; at &amp;gt;lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l&lt;/pre&gt;</description>
    <dc:creator>Yury Katkov</dc:creator>
    <dc:date>2013-05-17T10:08:04</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.science.linguistics.wikipedia.technical">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.science.linguistics.wikipedia.technical</link>
  </textinput>
</rdf:RDF>
