Commit access requests



This page serves as a central location for users to request commit access to SVN. Please note that just because you've listed your name here doesn't mean that you'll get access. Final approval for access still lies with Brion and Tim.

'''Quick warning -- we haven't established a schedule for looking at this queue yet, so don't be worried if it takes a while to respond. --brion 22:16, 28 April 2009 (UTC)'''

Request format
Copy and paste the following text to the bottom of the list. Of course you can add extra information you think is relevant, but try to keep it simple and to the point.

User name

 * Requested commit name: abcd
 * Expected area to work in: extensions, localization, etc
 * link to public key
 * Patches you've contributed already, if any

Completed requests

 * 1) /Archive 1

Happy-melon

 * Requested commit name: happy-melon
 * Expected area to work in: I generally do little tweaks, usually page layout and display of system messages.
 * link to public key
 * |\_)melon%40(hotmail\.co\.uk|live\.com)&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Patches, |\_)melon%40(hotmail\.co\.uk|live\.com)&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= bugs. I even managed to get a broken patch far enough through code review to bork the live wikis :D. But I now have a test wiki all to myself to destroy test patches on, so that shouldn't be a problem now... honest... Happy ‑ melon 17:36, 22 April 2009 (UTC)

Tidan

 * Requested commit name: tidan
 * Expected area to work in: I've done a number of special query pages that I would like to contribute
 * link to public key
 * I've created the following SpecialPage extensions for page/category viewing and contribution statistics. Planning to contribute them all.
 * # Views per category
 * # Breakdown of views per category
 * First and most recent contributors to the most popular pages

Church of emacs
Thanks, --Church of emacs 15:23, 30 April 2009 (UTC)
 * Requested commit name: churchofemacs
 * Expected area to work in: Bug fixes and new features; implementing the ideas I get on Wikipedia
 * public key on Wikipedia (alternative)
 * I've filed quite some bugs (as church.of.emacs.ml with my gmail account), and commited patches to six bug reports (both trivial and non-trivial ones)

InforMedic

 * Requested commit name: informedic
 * Expected area to work in: extensions, localization, skinning
 * 
 * 

Jaime Prilusky

 * Requested commit name: jprilusky
 * Expected area to work in: extensions
 * Public Key
 * Working on Extension:ContributionCredits and other extensions at Proteopedia

Commit names should be all lowercase and can't contain spaces. Try something like "jaime" or "jprilusky" or whatnot. —Simetrical (talk • contribs) 13:56, 19 May 2009 (UTC)

algorithmix

 * Requested commit name: algorithmix
 * Expected area to work in: extensions
 * I am the primary maintainer of Extension:DynamicPageList. At the moment I publish new releases on my own website. Somebody was so kind to upload the latest version of DPL to the MW svn. Now I want commit access there to make the MW svn repository the master place for further publications of DPL.
 * link to my Public Key
 * link to DynamicPageList at MediaWiki svn
 * I think that my extension could be very useful on wikipedia installations. I understand that some people might be afraid of DPL being critical in terms of performance. What can I do to prove that you can get the benefits of DPL without risk? Algorithmix 07:45, 21 May 2009 (UTC)

Jidanni
--Thanks. Jidanni 15:58, 26 May 2009 (UTC)
 * Requested commit name: jidanni
 * Expected area to work in: basic blemishes
 * link to public key
 * Patches