Hi, when we edit Zero configuration, it would be very beneficial to flush
any cached pages in varnish that are related to the change.
For example, if I edit Beeline's banner settings, any objects with the
header X-CS=250-99 should be purged, hopefully without any additional
manual interaction. Without this purge, the cache will be stale for the
next 30 days for the most common articles.
Now, according to the
http://giantdorks.org/alain/exploring-methods-to-purge-varnish-cache/,
varnish has an extensive matching support, and the author provides some
PHP-based code to perform the cache flushing. What would we need to
implement secure, automated partial varnish flushing in production?
Thanks!
Hello all,
This message is for those of you who do deployments to the WMF cluster.
On the [[How to deploy code]] wikitech page, there is a section on
Testing your live code:
https://wikitech.wikimedia.org/wiki/How_to_deploy_code#Test_your_code_live
That's a pretty basic overview of it and it could be greatly improved
with information like:
* How to monitor specific parts of the cluster that are relevant to what
you deployed
* What general monitoring should be looked at after you deploy
I know many of you already do much of this after you deploy, but the
lack of documentation on *how* to do it was a recurring theme in the
initial interviews I did with engineering teams when I first started.
https://wikitech.wikimedia.org/wiki/Deployments/Features_Process/General_Fe…
== "The Ask" ==
I'm asking you ("you" being those of you who have experience doing
post-deploy monitoring) to please add more documentation to this section
of the How to deploy code page:
https://wikitech.wikimedia.org/wiki/How_to_deploy_code#Test_your_code_live
I expect people from both engineering and ops will have feedback here.
Also, those of you who don't know how to monitor/log things post deploy
but you have specific questions, please ask here so that someone who
does know can answer on the wiki.
Thanks,
Greg
--
| Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E |
| identi.ca: @greg A18D 1138 8E47 FAC8 1C7D |
We have to switch our database from mysql to Oracle or msSql. We notice that there is a DatabaseOracle.php in the db folder. Is Oracle or MsSQL supported well with mediaWiki?
Below is our current versions:
MediaWiki<http://www.mediawiki.org/>
1.15.3
PHP<http://www.php.net/>
5.2.8 (cgi-fcgi)
MySQL<http://www.mysql.com/>
5.5.19
We know we are not current with our mediaWiki version. From the little we read the older versions may work better than the newer versions. We are willing to switch to whichever version of the software that works the best with Oracle or MsSQL.
Could you also point me to documentation on the databases? At this time we are not concerned about the 3rd party extensions that we have installed. We are more concerned about the core code.
Thanks,
Mary Beebe
Battelle - Charlottesville, VA
Office: 434- 951-2149
Hi Sumana,
Thanks for replying to my query. I am pleased to let you know that I have
some experience of PHP, Javascript , CSS and MySQL.
Currently I'm exploring MediaWiki and working on a few bugs.
On Thu, May 9, 2013 at 8:17 AM, Sumana Harihareswara
<sumanah(a)wikimedia.org>wrote:
> On 05/03/2013 03:48 PM, Puneet Kaur wrote:
> > Hi all ,
> >
> > I know its late but still.
> >
> > I wished to let you all know that I have applied for the Wikidata
> Features
> > Project Idea in GSOC 2013.
> >
> > I have a bit of experience in website development and designing, but I am
> > not sure whether all of my present knowledge would be sufficient for the
> > project.
> >
> > I shall be exploring my hands on wikidata, the online knowledge base for
> > the rest of days.
> >
> > Do let me know if I am expected of anything else than that mentioned
> above.
> >
> >
> > Regards,
> > Puneet
> > _______________________________________________
> > Wikitech-l mailing list
> > Wikitech-l(a)lists.wikimedia.org
> > https://lists.wikimedia.org/mailman/listinfo/wikitech-l
> >
>
> Puneet, thanks for the email, but *linking* to your proposal would have
> been helpful. https://www.mediawiki.org/wiki/User:Puneet_kaur :-)
>
> Have you ever worked in PHP before? Have you worked on MediaWiki before?
> Have you started the steps in
> https://www.mediawiki.org/wiki/How_to_become_a_MediaWiki_hacker and
> potentially worked on a small bug suitable for novices?
> --
> Sumana Harihareswara
> Engineering Community Manager
> Wikimedia Foundation
>
Hello,
My name is Jeremy Coffman. I am a second year student studying Computer Science at Brandeis University, with a possible focus on natural language processing. I have decided to apply to work on the Incremental Data Dumps project. My proposal can be found here:
http://www.mediawiki.org/wiki/User:J.a.coffman/GSoc_2013_Proposal
I know I'm rather close to the deadline, but I welcome any feedback you may have.
Thank you,
Jeremy Coffman
Hi all ,
I know its late but still.
I wished to let you all know that I have applied for the Wikidata Features
Project Idea in GSOC 2013.
I have a bit of experience in website development and designing, but I am
not sure whether all of my present knowledge would be sufficient for the
project.
I shall be exploring my hands on wikidata, the online knowledge base for
the rest of days.
Do let me know if I am expected of anything else than that mentioned above.
Regards,
Puneet
Zeljiko,
I have updated my proposal with your suggestions, plus added a timeline
and more info under "About Me". Let me know if you have other suggestions.
Here is my update proposal for OPW:
https://www.mediawiki.org/wiki/User:Rachel99/OPW_proposal
Thank you.
-Rachel
On Tue, Apr 30, 2013 at 5:45 PM, Rachel Thomas <rachelthomas_99(a)yahoo.com>wrote:
> Here is my proposal for OPW:
> https://www.mediawiki.org/wiki/User:Rachel99/OPW_proposal
>
Hi Rachel,
I have left a couple of comments on the talk page[1].
Željko
--
1: https://www.mediawiki.org/wiki/User_talk:Rachel99/OPW_proposal
>________________________________
> From: "wikitech-l-request(a)lists.wikimedia.org" <wikitech-l-request(a)lists.wikimedia.org>
>To: wikitech-l(a)lists.wikimedia.org
>Sent: Wednesday, May 8, 2013 12:38 PM
>Subject: Wikitech-l Digest, Vol 118, Issue 34
>
>
>Send Wikitech-l mailing list submissions to
> wikitech-l(a)lists.wikimedia.org
>
>To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>or, via email, send a message with subject or body 'help' to
> wikitech-l-request(a)lists.wikimedia.org
>
>You can reach the person managing the list at
> wikitech-l-owner(a)lists.wikimedia.org
>
>When replying, please edit your Subject line so it is more specific
>than "Re: Contents of Wikitech-l digest..."
>
>
>Today's Topics:
>
> 1. Re: OPW Browser Test Automation - Proposal Summary
> (Željko Filipin)
> 2. Re: OPW browser test automation for Visual Editor
> (Željko Filipin)
> 3. Re: APIStrat conference, San Francisco, October 23, 24, 25
> (Marc A. Pelletier)
> 4. How to get permission to view deleted revision information
> via API? (Claudia Müller-Birn)
> 5. Re: How to get permission to view deleted revision
> information via API? (Chad)
> 6. Re: GSoC / OPW mentors README (Quim Gil)
> 7. Re: APIStrat conference, San Francisco, October 23, 24, 25
> (Mathieu Stumpf)
> 8. Re: GLAM Wiki Toolset code review (Sumana Harihareswara)
> 9. Git for idiots (Petr Bena)
> 10. Re: Git for idiots (Chad)
>
>
>----------------------------------------------------------------------
>
>Message: 1
>Date: Wed, 8 May 2013 14:42:22 +0200
>From: Željko Filipin <zfilipin(a)wikimedia.org>
>To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
>Subject: Re: [Wikitech-l] OPW Browser Test Automation - Proposal
> Summary
>Message-ID:
> <CABfBeAohS5ruwePTARpZ6yU1aOrkVOqhAxEnzHVa2WLGGYcyXw(a)mail.gmail.com>
>Content-Type: text/plain; charset=UTF-8
>
>On Tue, Apr 30, 2013 at 2:25 PM, Indrani Sen <i.sen(a)se12.qmul.ac.uk> wrote:
>
>> I am summarizing here my proposal idea for OPW MediaWiki projects.
>
>
>I have noticed that you did not provide the link to your proposal[1]. In
>addition to the comments that I have posted here, I have left a few
>comments on the talk page[2].
>
>Željko
>--
>1: http://www.mediawiki.org/wiki/User:Indranisen
>2: http://www.mediawiki.org/wiki/User_talk:Indranisen
>
>
>------------------------------
>
>Message: 2
>Date: Wed, 8 May 2013 14:57:10 +0200
>From: Željko Filipin <zfilipin(a)wikimedia.org>
>To: Rachel Thomas <rachelthomas_99(a)yahoo.com>, Wikimedia developers
> <wikitech-l(a)lists.wikimedia.org>
>Subject: Re: [Wikitech-l] OPW browser test automation for Visual
> Editor
>Message-ID:
> <CABfBeArREv5M6y22igQYCnNXB9GWjh=DsWO-ETzK0sCB0+55Zg(a)mail.gmail.com>
>Content-Type: text/plain; charset=UTF-8
>
>On Tue, Apr 30, 2013 at 5:45 PM, Rachel Thomas <rachelthomas_99(a)yahoo.com>wrote:
>
>> Here is my proposal for OPW:
>> https://www.mediawiki.org/wiki/User:Rachel99/OPW_proposal
>>
>
>Hi Rachel,
>
>I have left a couple of comments on the talk page[1].
>
>Željko
>--
>1: https://www.mediawiki.org/wiki/User_talk:Rachel99/OPW_proposal
>
>
>------------------------------
>
>Message: 3
>Date: Wed, 08 May 2013 09:09:17 -0400
>From: "Marc A. Pelletier" <marc(a)uberbox.org>
>To: wikitech-l(a)lists.wikimedia.org
>Subject: Re: [Wikitech-l] APIStrat conference, San Francisco, October
> 23, 24, 25
>Message-ID: <518A4E7D.6000708(a)uberbox.org>
>Content-Type: text/plain; charset=UTF-8
>
>On 05/07/2013 05:33 PM, Juliusz Gonera wrote:
>> Seems interesting. Is there anyone who'd be interested in giving a talk
>> or participating in a panel there?
>
>Given that it's very close to me, and that I have quite a bit of
>experience with the API, this is something I could do.
>
>I actually had an API talk planned for WM 2012 that I never got a chance
>to present, I could dust it off and see how well it fits in their scope.
>Do you know when their CFP opens?
>
>-- Marc
>
>
>
>
>------------------------------
>
>Message: 4
>Date: Wed, 8 May 2013 15:35:19 +0200
>From: Claudia Müller-Birn <clmb(a)inf.fu-berlin.de>
>To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
>Subject: [Wikitech-l] How to get permission to view deleted revision
> information via API?
>Message-ID: <63F3F3F4-938C-49BA-8BFD-8C5156C0A292(a)inf.fu-berlin.de>
>Content-Type: text/plain; charset="windows-1252"
>
>Hi all,
>
>I don't know whether this is the correct mailing list to ask such question but it is the one I am reading regularly…
>
>Does anyone know about the adequate procedure to get permission to request deleted revision information from the MediaWiki API?
>
>I just stumbled over this problem...
>
>{
> "servedby": "mw1140",
> "error": {
> "code": "drpermissiondenied",
> "info": "You don't have permission to view deleted revision information"
> }
>}
>
>Many thanks.
>
>Best, Claudia
>
>
>
>------------------------------
>
>Message: 5
>Date: Wed, 8 May 2013 09:46:35 -0400
>From: Chad <innocentkiller(a)gmail.com>
>To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
>Subject: Re: [Wikitech-l] How to get permission to view deleted
> revision information via API?
>Message-ID:
> <CADn73rNf5P6p2FWkqE20ezagXmBFOKQ1N+r16JD6-VNGAgCVWg(a)mail.gmail.com>
>Content-Type: text/plain; charset=UTF-8
>
>On Wed, May 8, 2013 at 9:35 AM, Claudia Müller-Birn
><clmb(a)inf.fu-berlin.de> wrote:
>> Hi all,
>>
>> I don't know whether this is the correct mailing list to ask such question but it is the one I am reading regularly…
>>
>> Does anyone know about the adequate procedure to get permission to request deleted revision information from the MediaWiki API?
>>
>> I just stumbled over this problem...
>>
>> {
>> "servedby": "mw1140",
>> "error": {
>> "code": "drpermissiondenied",
>> "info": "You don't have permission to view deleted revision information"
>> }
>> }
>>
>
>For a personal wiki, this means you need the 'deletedhistory' and 'deletedtext'
>permissions (which is by default assigned to the admin group).
>
>On WMF wikis, this requires being an administrator (although I think there's
>some exception for researchers handed out via Meta).
>
>-Chad
>
>
>
>------------------------------
>
>Message: 6
>Date: Wed, 08 May 2013 07:41:18 -0700
>From: Quim Gil <qgil(a)wikimedia.org>
>To: wikitech-l(a)lists.wikimedia.org
>Subject: Re: [Wikitech-l] GSoC / OPW mentors README
>Message-ID: <518A640E.8030404(a)wikimedia.org>
>Content-Type: text/plain; charset=UTF-8; format=flowed
>
>On 05/03/2013 04:22 PM, Matthew Flaschen wrote:
>> On 04/27/2013 07:58 PM, Quim Gil wrote:
>>> SELECTING CANDIDATES
>>>
>>> After the deadline we will meet to prioritize GSoC and OPW candidates.
>>
>> When is this meeting?
>
>It seems that we won't need a meeting to discuss candidates. So far the
>discussions of the proposals in Google Melange are enough.
>
>What we will do is a hangout for mentors next week to discuss anything
>except candidates: questions about the program and your work,
>expectations, tips & tricks...
>
>And some questions that came from a student:
>
>> 1. May I know how selection of the most suitable candidate for each
>> GSoC project will be like?
>
>It is described at
>https://www.mediawiki.org/wiki/Mentorship_programs/Selection_process but
>if anybody has more specific questions just ask.
>
>> 2. Would it depend on technical knowledge and research?
>
>It's a combination of many factors. There is a short term question (do
>we trust this candidate can complete this project) and a mid term
>question (do we believe this candidate will stick around, contributing
>after the internship?).
>
>There is no scientific way to predict the answers. Own initiative,
>social/communication skills or personal context may play a role as
>important as the declared technical knowledge (which in many cases we
>can't even evaluate properly because on many cases there is not much
>code and history to look at - which is relatively expected in these
>types of internship programs.
>
>
>> 3. Will there be more than one successful candidate for one specific
>> project or is it strictly the best (only one) candidate for the
>> specific project?
>
>GSoC / OPW allow this, but we are aiming to have only one candidate per
>project. The main motivation is to give more chances to more projects.
>We try to define project ideas that can be accomplished by one person
>during the internship.
>
>--
>Quim Gil
>Technical Contributor Coordinator @ Wikimedia Foundation
>http://www.mediawiki.org/wiki/User:Qgil
>
>
>
>------------------------------
>
>Message: 7
>Date: Wed, 08 May 2013 17:14:53 +0200
>From: Mathieu Stumpf <psychoslave(a)culture-libre.org>
>To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
>Subject: Re: [Wikitech-l] APIStrat conference, San Francisco, October
> 23, 24, 25
>Message-ID: <1368026093.6376.21.camel(a)tarasque.omnix.fr>
>Content-Type: text/plain; charset="UTF-8"
>
>Le mercredi 08 mai 2013 à 09:09 -0400, Marc A. Pelletier a écrit :
>> On 05/07/2013 05:33 PM, Juliusz Gonera wrote:
>> > Seems interesting. Is there anyone who'd be interested in giving a talk
>> > or participating in a panel there?
>>
>> Given that it's very close to me, and that I have quite a bit of
>> experience with the API, this is something I could do.
>>
>> I actually had an API talk planned for WM 2012 that I never got a chance
>> to present, I could dust it off and see how well it fits in their scope.
>> Do you know when their CFP opens?
>>
>> -- Marc
>
>Will the event be recorded and broadcasted? This may be an interesting
>document to add on meta where efforts are done to make developers
>involvement more attractive.
>
>>
>>
>> _______________________________________________
>> Wikitech-l mailing list
>> Wikitech-l(a)lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>
>
>
>
>------------------------------
>
>Message: 8
>Date: Wed, 08 May 2013 12:23:30 -0400
>From: Sumana Harihareswara <sumanah(a)wikimedia.org>
>To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
>Cc: Geer Oskam <Geer.Oskam(a)KB.nl>
>Subject: Re: [Wikitech-l] GLAM Wiki Toolset code review
>Message-ID: <518A7C02.4020908(a)wikimedia.org>
>Content-Type: text/plain; charset=UTF-8
>
>On 04/17/2013 02:51 AM, Mathieu Stumpf wrote:
>> Le 2013-04-16 18:25, Geer Oskam a écrit :
>>> Hi all,
>>>
>>> the GLAM Wiki Toolset-code is ready for its initial review.
>>> It can be found at: https://gerrit.wikimedia.org/r/#/c/59405/
>>>
>>> Please help us by taking a look at it.
>>>
>>> Cheers,
>>> Geer Oskam
>>>
>>> Europeana
>>
>> For those like me which are wondering "what is it?", here is an
>> informative copy of the README:
>>
>> GWToolset
>> =========
>>
>> A MediWiki extension that allows GLAMs the ability to mass upload
>> content based on an xml file conta
>> ining respective metadata about the content. The intent is to allow for
>> a variety of xml schemas; se
>> e the [extension page](
>> http://www.mediawiki.org/wiki/Extension:GWToolset ) for further
>> information.
>>
>>
>>
>>
>>
>> (All apologies if this was obvious to all other readers of this list)
>
>Thanks to Siebrand, Reedy, and Peachey88 for their reviews. There's a
>new patchset up as of today in case anyone wants to take a fresh look.
>
>--
>Sumana Harihareswara
>Engineering Community Manager
>Wikimedia Foundation
>
>
>
>------------------------------
>
>Message: 9
>Date: Wed, 8 May 2013 18:34:15 +0200
>From: Petr Bena <benapetr(a)gmail.com>
>To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
>Subject: [Wikitech-l] Git for idiots
>Message-ID:
> <CA+4EQ5f2dNbRgoKxhg0jGpwGArCBTEJ8ikbKTMv8WyAxMMXqEQ(a)mail.gmail.com>
>Content-Type: text/plain; charset=ISO-8859-1
>
>Hi,
>
>Long time ago when I started learning with git I decided to create a
>simple guide (basically I was just taking some notes of what is
>needed). I never thought that it could be useful to anyone so I never
>announced it anywhere. However I got some feedback to it, so I decided
>to inform you too.
>
>The basic idea is to create a TOTALLY SIMPLE guide that git
>illiterates like me can understand and thanks to which they would find
>out how to do stuff in wikimedia git / gerrit.
>
>Link is here: www.mediawiki.org/wiki/User:Petrb/Git_for_idiots
>
>It doesn't contain so much and there are some mistakes / feel free to fix them.
>
>Since wikimedia switched to gerrit from svn I have yet met a tons of
>people who had problems adapting to it, so this could eventually help
>some.
>
>
>
>------------------------------
>
>Message: 10
>Date: Wed, 8 May 2013 12:37:56 -0400
>From: Chad <innocentkiller(a)gmail.com>
>To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
>Subject: Re: [Wikitech-l] Git for idiots
>Message-ID:
> <CADn73rPtPwAnZ7sZxK3gODSHD5jB1tyaFxkT778MBhdA5-RbOA(a)mail.gmail.com>
>Content-Type: text/plain; charset=UTF-8
>
>On Wed, May 8, 2013 at 12:34 PM, Petr Bena <benapetr(a)gmail.com> wrote:
>> Hi,
>>
>> Long time ago when I started learning with git I decided to create a
>> simple guide (basically I was just taking some notes of what is
>> needed). I never thought that it could be useful to anyone so I never
>> announced it anywhere. However I got some feedback to it, so I decided
>> to inform you too.
>>
>> The basic idea is to create a TOTALLY SIMPLE guide that git
>> illiterates like me can understand and thanks to which they would find
>> out how to do stuff in wikimedia git / gerrit.
>>
>> Link is here: www.mediawiki.org/wiki/User:Petrb/Git_for_idiots
>>
>> It doesn't contain so much and there are some mistakes / feel free to fix them.
>>
>> Since wikimedia switched to gerrit from svn I have yet met a tons of
>> people who had problems adapting to it, so this could eventually help
>> some.
>>
>
>We've got [[Git/Workflow]], [[Git/Tutorial]] and [[Git/Getting
>started]] (in decreasing
>order of complexity/depth), so I would be hesitant to add yet another
>howto page.
>Considering this is supposed to be quick-and-easy docs, I'd suggest folding any
>unique content into the getting started doc.
>
>-Chad
>
>
>
>------------------------------
>
>_______________________________________________
>Wikitech-l mailing list
>Wikitech-l(a)lists.wikimedia.org
>https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>
>
>End of Wikitech-l Digest, Vol 118, Issue 34
>*******************************************
>
>
>
Hi all,
Our current release note strategy is clearly not working.
Too many times do people omit it. Either because they consider the
commit not important enough for release notes or because it is a pain
to do due to the continuous merge conflicts. Not to mention fix-ups
and small clarifications are often annoying to do. It also often
results in inconsistent formatting of the notes as everybody does it
differently.
For this and other reasons[1], I'd recommend we stop updating release
notes through git commits in a separate file.
For more details see Proposal 2 on this page:
https://www.mediawiki.org/wiki/Requests_for_comment/Release_notes_automatio…
It is important that we settle quickly and perfect later since this is
affecting our current release cycle already.
In case people worry about the scalability of the approach, I'm
willing to take this on for the near future. However I'm convinced we
have enough people who care and will filter the incoming stream on the
wiki page. Simply look at the git history of release notes files (I
expect at least Reedy and hexmode will naturally be drawn to this).
-- Krinkle
[1] Other reasons include keeping the change atomic and easy to
backport. For what its worth, Git[2], Nodejs[3] and many jQuery
projects such as QUnit[4] already maintain release notes this way.
[2] https://github.com/git/git/commit/v1.8.2.2
[3] https://github.com/joyent/node/commit/v0.10.5
[4] https://github.com/jquery/qunit/commit/v1.11.0
Hi all,
the GLAM Wiki Toolset-code is ready for its initial review.
It can be found at: https://gerrit.wikimedia.org/r/#/c/59405/
Please help us by taking a look at it.
Cheers,
Geer Oskam
Europeana
GSoC / OPW mentors are facing 10 intense days selecting our next group
of interns.
Some suggestions:
ALWAYS
* Be nice and welcoming, especially in your first messages exchanged.
There will be time for wikitech-style blunt straightforwardness. ;)
* Rely as much as possible in public channels to discuss with the
candidates. Any proposal is a community project, not your pet project.
BEFORE THE SUBMISSION DEADLINE
* Get a second co-mentor for the proposals you want to see accepted.
It's not easy but the success rate is remarkably higher, and the
workload for each remarkably lower. Could be a profile complementary to
yours: technical vs community, professional vs volunteer, maintainer vs
power user, East vs West... The candidate and the project will benefit a
lot.
* You are supposed to be very responsive these days. Say 24h max for an
answer. Failing to do so will diminish the chances of your candidates /
proposals. As said, a second co-mentor always helps.
* Help your candidates, within certain limits. Candidates must have the
skills to prepare a proper plan for their own proposals.
* Asses the capacity of the candidate to complete the project. A nice
written proposal is important but don't rely on this alone.
* Assess the availability of the candidates. This is like a full time
job, with certain margin of flexibility for regular studies (but still).
SELECTING CANDIDATES
After the deadline we will meet to prioritize GSoC and OPW candidates.
* If you have more than one candidate be ready to prioritize them. One
mentor can take only one project, unless there is a good justification
for taking two (e.g. strong co-mentors in both).
* Read also the rest of proposals and pencil your own ranking with a
Wikimedia / MediaWiki wide agenda in mind.
* Be ready to negotiate the place of your candidates in the general
ranking. In other words, don't push blindly for "your" proposals.
Needless to say, you must read the official GSoC manual for mentors:
http://en.flossmanuals.net/GSoCMentoring/
There is more good reading at
https://www.mediawiki.org/wiki/Mentorship_programs/Possible_mentors
If you are a good mentor your know that 20 minutes reading docs can save
you a lot more time and energies. ;)
--
Quim Gil
Technical Contributor Coordinator @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil