Commit access requests/Archive 1

SPQRobin
Well, I sent my request to Wikitech-l just before this page was created, so I'll add my request here as well to be sure.
 * Commit name: robin (my wikiname is SPQRobin but uppercase appears to be not allowed)
 * I want to use it to commit and maintain my extension (see Extension:WikimediaIncubator) to be used on Wikimedia Incubator. Maybe I'll do some general work/maintenance as well, or fix bugs, when I see something I can fix.
 * My key: http://toolserver.org/~robin/publickey.txt
 * I have already worked on SpecialInterwiki extension but I didn't work on it further since I didn't have commit access.. I also used to work a bit on i18n through Translatewiki.net (for example, reporting unused messages, ...) although that's not so important for this :). Also, some patches I submitted, are and.

Thank you, SPQRobin 20:20, 17 April 2009 (UTC)


 * Done. --brion 18:59, 1 May 2009 (UTC)

Alexsh
I send my request to brion in April 18,2008/5/20 and 2008/3/23 and no response.Now I post my request in here.
 * Commit name: alexsh (same as my global account name)
 * I want to commit pywikipediabot and help to maintenance zhConversion.I alse works on i18n updates through translatewiki.net.
 * my public Key: http://alexsh.tw.googlepages.com/alexsh-key.pub

Thank you.--Alexsh 22:00, 21 April 2009 (UTC)


 * Done. --brion 18:59, 1 May 2009 (UTC)

GerardM

 * requested commit name:
 * Expected area to work in: testing
 * pubkey
 * Gerard keeps generating patches for me to commit. Please save me! :-)
 * Siebrand and I will be keeping an eye on him. I just worry that he might turn into another Siebrand.
 * --Kim Bruning 22:07, 6 June 2009 (UTC)
 * (Done... )

algorithmix

 * Requested commit name:
 * 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)

Beckr
Beckr 11:21, 7 July 2009 (UTC)
 * Requested commit name:
 * Expected area to work in: SlippyMap
 * link to public key
 * Past work on MediaWiki - I'm developing the new OSM SlippyMap with Aude & Avar. Our code has now made it into the Wikimedia trunk; my contributions here include externalizing the JavaScript code and making it object-oriented, adding support for image placeholders (i.e. click to get a dynamic map), and lots of refactoring (see our previous external repository).

Church of emacs
Thanks, --Church of emacs 15:23, 30 April 2009 (UTC)
 * Requested commit name:
 * 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 about eight bug reports (both trivial and non-trivial ones). My first extension: Extension:FlagArticle

Conrad.Irwin
Conrad.Irwin 23:04, 25 July 2009 (UTC)
 * Requested commit name:
 * Expected area to work in: extensions, particularly for Wiktionaries
 * id_rsa.pub
 * Past work on MediaWiki - MetaKeywords extension, Transliterator extension, Extension:CategoryLabel, plenty of javascript. I have a small wiki-farm which runs on a slightly tweaked codebase (mainly to make the category and search pages look nice, and a couple of unpublished extensions).

Flominator
Flominator 07:58, 11 June 2009 (UTC)
 * Requested commit name: flominator
 * Expected area to work in: WikiBlame (Siebrand told me that this svn might be a better place than this one)
 * pubkey
 * Past work on MediaWiki - some minor extensions, see User:Flominator

GreenReaper
GreenReaper 02:09, 28 July 2009 (UTC)
 * Requested commit name:
 * Expected area to work in: output/page rendering; skins/graphics (for things like this) and extensions (once I get Extension:MediaWikiAuth in order, plus fixes/tweaks like this)
 * ssh-key-greenreaper.pub
 * Past work on MediaWiki - the above, plus several picky efficiency patches, and I've submitted a few more bugs that were fixed.

Grant Slater
Firefishy 04:07, 9 July 2009 (UTC)
 * Requested commit name:
 * Expected area to work in: extensions, Slippymap
 * link to public key
 * Past work on MediaWiki - SlippyMap part author, OpenStreetMap sysadmin, OSM point of contact for Tile cache optimization testing.

Happy-melon

 * Requested commit name:
 * Expected area to work in: I generally do little tweaks, usually page layout and display of system messages. I'm having a play at a couple of extensions too: another special page to add to Oversight to allow old oversighted edits to be converted over to the new RevDelete format; and a total reboot of the DeleteQueue extension to make it a) work, and b) be suitable for consideration for use on enwiki.
 * 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  . 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)

Husky
Husky 12:50, 5 June 2009 (UTC)
 * Requested commit name:
 * Expected area to work in: Wikiportrait
 * Public key
 * See Wikiportrait for more information. Commiting this to SVN would make development and localisation easier, many chapters want the software to set up their own local versions.

Jeroen De Dauw
Jeroen De Dauw 13:27, 22 July 2009 (UTC)
 * Requested commit name:
 * Expected area to work in: extensions
 * Link to public key
 * Past work on MediaWiki: Maps, Semantic Maps (as GSoC student)
 * Your requested username doesn't meet required policy (1) and you need to publish a public key before it will be considered. Peachey88 08:29, 25 July 2009 (UTC)
 * Added my key --Jeroen De Dauw 19:47, 28 July 2009 (UTC)

Malvineous
Malvineous 22:38, 8 July 2009 (UTC)
 * Requested commit name:
 * Expected area to work in: extensions
 * link to public key
 * Past work on MediaWiki - I have received some requests to put my extensions (Extension:FlvHandler and Extension:MassEditRegex) into SVN. I would like to request commit access so that I can keep them up to date myself.

QuestPC
QuestPC 06:22, 4 June 2009 (UTC)
 * Requested commit name:
 * Expected area to work in: extensions
 * link to public key
 * Patch (Dmitriy is me), Extension:QPoll I just want to upload my own extension so it can be updated and localized.

Strainu
Strainu 18:11, 14 July 2009 (UTC)
 * Requested commit name:
 * Expected area to work in: romanian planet maintaining (see Planet Wikimedia/New language)
 * link to public key
 * Past work on MediaWiki - some Gadgets on the Romanian Wikipedia, bugs and patches using [mailto:crangasi2001@yahoo.com this email] as bugzilla account.

Jaime Prilusky

 * Requested commit name:
 * 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)

OverlordQ
OverlordQ 15:36, 15 June 2009 (UTC)
 * Requested commit name:
 * Expected area to work in: extensions, postgres support, trivial fixes
 * pubkey
 * Past work on MediaWiki - Slightly non-BC Exif Patch, assorted PG suggestions, bug 16720, Various contributions towards AntiSpoof and the API. Quite a few other minor patches: 19729197281972719726.

Nephele
Nephele 21:41, 26 June 2009 (UTC)
 * Requested commit name:
 * Expected area to work in: mediawiki patches, new extensions, improvements to existing extensions. (First expected commit is a significant upgrade to Extension:ProtectSection)
 * link to public key
 * Past work on MediaWiki - patches for 18751 and 8130 have been committed; patches for 2257 and 18609 need review. I've written several MediaWiki extensions (and modified several others) that are currently being used on UESP, the most significant of which is MetaTemplate.

Emufarmers
—Emufarmers(T 20:35, 4 August 2009 (UTC)
 * Requested commit name:
 * Expected area to work in: general/easyish bug fixes, extensions
 * link to public key
 * Past work on MediaWiki - bugs, patches, a small ConfirmEdit plugin

yar1
yaron.shapira@kaltura.com 11:45, 12 August 2009 (UTC)
 * Requested commit name:
 * Expected area to work in: video player, add media wizard, video editor
 * http://corp.kaltura.com/docs/yaron_pub.key

xqt
--Xqt 13:09, 7 September 2009 (UTC)
 * Requested commit name:
 * Expected area to work in: pywikipedia
 * My public SSH key
 * Working on pywikipedia:
 * I've developer status on Python Wikipedia Robot Framework:
 * my bug requests, partially solved on my local copy first
 * See also my fixes at pywikipedia trunk
 * I am running a pywikipedia bot w:de:User:Xqbot partially with my own scripts; bots edits and flags
 * I supported some bot owners with bug fixes and features. Examples:
 * w:de:User talk:Xqt/Archiv/2009-1
 * w:de:User talk:Xqt/Archiv/2009-1
 * Brion may still have my e-mail (sent few weeks ago).

Vouched by Siebrand. --brion 18:20, 5 October 2009 (UTC)

Kipcool
Kipmaster 07:45, 1 September 2009 (UTC)
 * Requested commit name:
 * Expected area to work in: OmegaWiki (so, maybe a bit of Wikidata as well)
 * link to public key
 * Past work on OmegaWiki - These patches are from me:, ,.
 * Of course I am working with GerardM and make him and other OW developers try my patches on my public test server before commiting them.

Vouched by GerardM & Siebrand. --brion 18:20, 5 October 2009 (UTC)

Fenzik
--Fenzik 15:02, 6 September 2009 (UTC)
 * Requested commit name:
 * Expected area to work in: core & extensions
 * this is my public ssh key
 * Past work on MediaWiki - co-ordinating and developing mediawiki integration with jasperforge.org, forge.openbravo.com & monitoringforge.org
 * Interests : Wish to participate as a hardcore developer in mediawiki community.
 * Done -- Tim Starling 06:08, 16 October 2009 (UTC)

MaxSem
Max Semenik 17:38, 8 September 2009 (UTC)
 * Requested commit name:
 * Expected area to work in: SQLite support. Due to its present state, I strongly doubt that I'll break anything beyond what is already broken :D I have some ideas how to fix many of these problems, but submitting a huge patch and seeing it bitrotting, waiting for review isn't particulary encouraging.
 * public key
 * Past work on MediaWiki - my patches committed by others: 1, 2, 3, 4, 5, 6, 7.
 * Done -- Tim Starling 06:08, 16 October 2009 (UTC)

Juliano
--Juliano 20:23, 3 September 2009 (UTC)
 * Requested commit name:
 * Expected area to work in: mainly extensions
 * My public SSH keys
 * Past work on MediaWiki:
 * Extension:Wikilog, Extension:KML Export -- I would like to host these extensions on MediaWiki servers.
 * My bug reports (patches only).
 * I also reported the useskin vulnerability, which granted the 1.12.1 and 1.13.2 security fix releases. Brion may still have my e-mail (sent to security at wikimedia on 2008-09-27).


 * Done -- Tim Starling 06:08, 16 October 2009 (UTC)

Tidan

 * Requested commit name:
 * 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


 * Is the code up somewhere to take a peek at first? --brion 21:19, 4 August 2009 (UTC)


 * I added it to a google repository. You can check it out here.  Thanks.
 * http://dansmediawikiextensions.googlecode.com/svn/trunk/ dansmediawikiextensions-read-only
 * Mail sent -- Tim Starling 08:24, 15 October 2009 (UTC)
 * Updated public key and confirmed e-mail address as requested. DanRinkes 16:46, 2 November 2009 (UTC)

InforMedic
--Thanks. InforMedic 17:13, 01 June 2009 (UTC)
 * Requested commit name:
 * Expected area to work in: extensions, localization, skinning
 * w:de:Benutzer:Informedic
 * Extension:FileTree
 * You need to publish an SSH public key. Happy ‑ melon 15:19, 1 June 2009 (UTC)


 * Your request has been denied at this time. If you still wish to have commit access, please submit another request, with an SSH public key. Also, please enable user-to-user email in your mediawiki.org preferences. -- Tim Starling 23:47, 4 November 2009 (UTC)

Bile
Bile 02:51, 22 July 2009 (UTC)
 * Requested commit name:
 * Expected area to work in: extensions
 * link to public key
 * Past work on MediaWiki - Extension:PDFThumbnails


 * This seems to do about the same as the PdfHandler extension; can you take a look and see if there are some different features in each that you might be able to merge into PdfHandler? --brion 21:10, 4 August 2009 (UTC)


 * Your request for commit access has been denied at this time. Please submit another request when you have another extension you wish to commit. -- Tim Starling 23:47, 4 November 2009 (UTC)

Matěj Grabovský
Matěj Grabovský 16:59, 12 August 2009 (UTC)
 * Requested commit name:
 * Expected area to work in: core, general, maybe some extensions and localisation
 * link to public key
 * Past work on MediaWiki: list of my patches on Bugzilla, localisations via Translatewiki.net, providing support on the Support desk, other stuff on my user page


 * Email sent. -- Tim Starling 15:22, 15 October 2009 (UTC)
 * Done -- Tim Starling 23:47, 4 November 2009 (UTC)

User:Michael Daly2
Michael Daly2 20:51, 28 August 2009 (UTC)
 * Requested commit name:
 * Expected area to work in: extension ImageMapConversion
 * User:Michael_Daly2/SSH2PublicKey In  tags.
 * Past work on MediaWiki - Extension:ImageMapConversion, Extension:ImageMap (Alternate) (now retired)
 * Since your request may not be handled by the 1st of setpember, May I suggest putting a copy of your key in your user space (eg: User:Michael Daly2/SSH2PublicKey) and getting that page protected. Peachey88 04:03, 29 August 2009 (UTC)


 * Done -- Tim Starling 23:47, 4 November 2009 (UTC)

Erich
Erich 11:51, 20 September 2009 (UTC) (signature with date)
 * Requested commit name:
 * Expected area to work in: extensions
 * link to public key
 * Past work on MediaWiki: Extension:News2 and some other useful extensions I'd like to share
 * Your request has been denied at this time. Please ensure that your extension meets MediaWiki's style and security guidelines. A larger amount of demonstration code would also be appreciated. -- Tim Starling 23:56, 4 November 2009 (UTC)

MacMed
MacMed 19:59, 1 October 2009 (UTC)
 * Requested commit name:
 * Expected area to work in: bug fixes, maybe some extensions later on
 * public key
 * bugs commented on and a patch I posted (another patch).
 * Your request has been denied at this time. Please continue to submit patches and extensions, and try again later. -- Tim Starling 23:56, 4 November 2009 (UTC)

Marco 27
Marco 27 14:15, 25 October 2009 (UTC)
 * Requested commit name:
 * Expected area to work in: Italian Planet maintenance (not existing yet)
 * Public key: User:Marco 27/SSHPublicKey
 * Past work on MediaWiki: Extension:FreenodeChat
 * Your request has been denied at this time. We're not currently giving out commit access for planet maintenance. -- Tim Starling 23:56, 4 November 2009 (UTC)

Reedy

 * Requested commit name:
 * Expected area to work in: api
 * link to public key
 * Past work on MediaWiki
 * patch
 * patch
 * all bugs reported

Note, User:Catrope suggested to apply for commit access with his support. Thanks, Reedy 14:36, 6 November 2009 (UTC)


 * Approved. -- Tim Starling 04:26, 18 November 2009 (UTC)

Abigor
Abigor 21:33, 11 November 2009 (UTC) (signature with date)
 * Requested commit name:
 * Expected area to work in: wikiportrait
 * link to public key
 * After irc conversation with husky


 * Approved. -- Tim Starling 04:26, 18 November 2009 (UTC)

happyday19c
Happyday19c 09:56, 13 November 2009 (UTC)
 * Requested commit name:
 * Expected area to work in: l18n, patch work.
 * link to public key
 * Past work on MediaWiki
 * bug report and suggested patch (but not yet commited)


 * Not approved at this time. -- Tim Starling 04:26, 18 November 2009 (UTC)

user:Bawolff
Bawolff 21:59, 17 December 2009 (UTC)
 * Requested commit name:
 * Expected to work in extensions
 * public key
 * list of bugs reported list of patches The biggest patch i submitted as of yet was in 21963. Also created a very small extension for use with a specific website - Extension:Whitelist Namespaces (thats a very minor extension though, and barely counts).
 * Past programming experiance: Not sure if this counts, but i handle a number of gadgets/other js stuff on wikinews (specifically most proud of Automated lead maker readyAlert, Wiktionary Lookup, easy peer review)


 * Approved. -- Tim Starling 05:28, 13 January 2010 (UTC)

user:JonathanWilliford
JonathanWilliford 05:10, 25 December 2009 (UTC)
 * Requested commit name:
 * Expect to work in extensions
 * public key
 * Most of my work has just been with creating extensions that I use at http://neurov.is/on. I have made some changes to the mediawiki wiki, although they have been minor (contributions).
 * I've worked in software engineering for many years, although mainly with C++. I have a Masters in computer science.  I have created several open source projects (http://code.google.com/p/synapse-lang/, http://code.google.com/p/biovis-lib/, http://code.google.com/p/mediawiki-refhelper/) and I have participated in WorldForge.org project a long time back.


 * Approved. -- Tim Starling 05:28, 13 January 2010 (UTC)

Platonides
Platonides 00:03, 29 December 2009 (UTC)
 * Requested commit name:
 * Expect to work in core and extensions
 * SSH key
 * wikitech-l posts · mediawiki-l posts · Naive bugzilla search · Captcha code commit (old) · math tag (recent)


 * Approved. -- Tim Starling 05:28, 13 January 2010 (UTC)

Conrad.Irwin (cirwin on IRC)

 * Requested commit name:
 * Expect to work in core, already have commit access in extensions.
 * Public key.
 * Maintain a small wiki farm with MediaWiki as a CMS, a few extensions for them, [1], and for en.wiktionary [2], [3]. A few patches, e.g. 1, 2, some committed, e.g. 3 4
 * Past programming experience, mainly involved with web stuff, 1, 2, 3, currently in year 3 of a computer science degree.


 * If you've already got commit access, you don't necessarily need to re-ask for core rights here. Probably can just poke Tim to tweak the authz file. ^demon 11:45, 29 December 2009 (UTC)
 * I don't think he has, though...? Happy ‑ melon 13:36, 29 December 2009 (UTC)
 * He does unless this conrad is someone else and Conrad here is confused about already having access. :) ^demon 01:09, 30 December 2009 (UTC)


 * That would be quite confused, I admit! Nothing wrong with having a marker here, though. Happy ‑ melon 09:58, 30 December 2009 (UTC)


 * Approved. -- Tim Starling 05:28, 13 January 2010 (UTC)

Ning Hu
11:29, 30 December 2009 (GMT+08:00)
 * Requested commit name:
 * Expected area to work in: extensions, core
 * Public key
 * Extension:Semantic_NotifyMe


 * What experience do you have working with the core? Happy ‑ melon 09:57, 30 December 2009 (UTC)
 * I've implemented a js framework solution, helping on solving js conflict in different extensions, e.g. jquery / prototype / yui / extjs. Ning 13:24, 13 January 2010 (GMT+08:00)


 * Approved for extensions only. -- Tim Starling 05:28, 13 January 2010 (UTC)

RobLa

 * Requested commit name:
 * Expected area to work in: core, extensions (current focus: bug 4421
 * Public key
 * Past work:
 * Minor patches to core. See list of all patches from robla@robla.net
 * Electowidget - MediaWiki extension for election theory nerds
 * EditOversight - editorial workflow plugin
 * Other private extensions
 * Past programming experience
 * Linden Lab's Second Life & Snowglobe client (commits)
 * See Advogato user page for more past stuff.
 * RobLa 17:24, 6 January 2010 (UTC)


 * Approved. -- Tim Starling 05:28, 13 January 2010 (UTC)

TOR
TOR 12:49, 1 February 2010 (UTC)
 * Requested commit name:
 * Expected area to work in: extensions, localization
 * link to public key
 * Past work on MediaWiki - 2.5 years at Wikia, bugfixes, stand-alone extensions (e.g. Extension:EditSimilar), i18n

Gabriel Wicke

 * Requested commit name: gwicke
 * Expected area to work in: extensions, core. First concrete need is publishing updates to my catfeed extension and open-sourcing client work.
 * Link to public key: http://dl.wikidev.net/id_dsa.pub
 * Past work on MediaWiki: Long ago (2003/04): Wrote the MonoBook skin, added user styles, Squid caching infrastructure, Parser fixes, user interface work. Since then: miscellaneous client work
 * Past programming experience: Basic pocket calculators, Zope/Plone, PHP content management systems, Squid, libevent/libev network programming, misc C and Python tools, AVR assembler, Haskell dabbling GWicke 09:25, 13 January 2010 (UTC)
 * Your previous commit name appears to be gabrielwicke. Max Semenik 09:47, 13 January 2010 (UTC)
 * Yep, but that was back in the CVS days, I did not request an SVN account after the switch. If you would prefer me to use the old name feel free to set that up instead. Thanks! GWicke 17:53, 14 January 2010 (UTC)

Nathanael Thompson

 * Requested commit name: than4213
 * Expected area to work in: parser. I'm interested in improving the architecture of the parser by iteratively seperating it into a data layer and parser engine. For all who's interested, I have a svn diff available for an initial change.
 * Link to public key: http://sites.google.com/site/natesprograms/Home/id_rsa.pub
 * Past work on MediaWiki: None, I'll work on bugs while I'm waiting for access.
 * Past programming experience: Bachelors in Computer Science and 5 years experience as a feature dev at Microsoft. Used the following in either a academic or professional setting: C++, Java, C#, Scheme, Scala, SQL, Batch, Bash, Perl, Javascript, Matlab, Latex.  As mentioned above I made a diff for an initial change to the parser and was able to pick up PHP pretty quickly.  Than4213 00:20, 15 January 2010 (UTC)
 * Please register on this wiki and enable email features in your preferences. Max Semenik 06:32, 15 January 2010 (UTC)
 * Do we have an auth group for "branch only"? Or is that supplied by the 'extension' auth?  Definitely support giving him some way to work on a new parser in a branch; such a thing would need hundreds of hours of testing before it gets into core anyway. And there are plenty of extension bugs to work on in the meantime. Happy ‑ melon 12:46, 15 January 2010 (UTC)
 * We have parser tests for a reason. If it can pass all of those, we can do the same as when Tim deployed the preprocessor and check common pages automatically, document any practical changes, etc.  However, Than4213, you should be aware that the parser is one of the most complicated and CPU-intensive parts of the code, and it has very stringent compatibility requirements.  To ever get accepted, your code would likely have to 1) noticeably change the output only a small fraction of a percent of the millions of pages on Wikimedia wikis (which can be pathologically baroque), and 2) either improve performance significantly or provide some other concrete benefit to Wikimedia. —Simetrical (talk • contribs) 14:42, 15 January 2010 (UTC)
 * I registered on this wiki and enabled email. I'm perfectly fine working in a branch and subjecting my changes to extensive parser tests.  I do not plan on changing the functionality of the parser. I just want to improve the architecture of the parser so that future changes to the parser won't be as complicated and error prone.  I'll work on changes to the functionality of the parser after fixing up the architecture of the parser :).  I also realize that a good overhall of the parser's architecture would take at least hundreds of hours and I'm willing to do so.  I think my change will benefit Wikimedia by making changes to the parser a much less daunting task.  --Than4213 17:21, 15 January 2010 (UTC)


 * It would be interesting having a link to your patch. Platonides 17:26, 15 January 2010 (UTC)
 * Sure thing. You can find it at http://sites.google.com/site/natesprograms/Home/WMParser1.txt.  --Than4213 18:34, 15 January 2010 (UTC)


 * I meant that it will take hundreds of hours, at least, to get any new parser to pass the tests. But if someone is genuinely prepared to take a crack at it, they have my full support. If he can write a parser that behaves the same as the existing one, has exactly the same performance characteristics as the exising one, but doesn't fill everyone apart from Tim with supernatural dread, that would definitely qualify as a concrete benefit to MediaWiki/Wikimedia in my book.  Have you seen the work at Markup spec/BNF?  That's the closest we've ever come to actually describing the parser's grammar. Happy ‑ melon 23:32, 15 January 2010 (UTC)
 * Thanks for the link, it should be helpful. The solution I'm thinking of will use something like bnf but will also use regular expressions for pattern matching.  I think this will make it so that some of the more dysfunctional syntax can still be represented.  --Than4213 17:05, 16 January 2010 (UTC)
 * Wow, the WikiText syntax is even stranger than I thought. I finally made a replacement for preprocessToXml that uses a simpler parser with a seperate engine and data layer.  The new parser passes all 545 tests that the old parser passed.  Also, I ran the old and new parser through the profiler and it looks like they take about the same amount of time (Although I should say that the times I was getting fluctuated quite a bit for each).  You can see my proposed change at http://sites.google.com/site/natesprograms/Home/WMParser2.txt.  When will I know if I can check this in?  Should I check this into main or a branch?  My next step is to integrate preprocessToObj into the new parser, but I'd like to check this in first.  --Than4213 23:11, 27 January 2010 (UTC)
 * Once this request is processed, you should check it into a branch so we can all have a proper look at it with syntax highlighting and all. Looks interesting, though. Give me a poke if it hasn't been done by the end of the week and I'll check it in for you. Happy ‑ melon 08:42, 28 January 2010 (UTC)
 * OK, will do. Thanks.  I updated the comments a little bit in the change, here is the new diff: http://sites.google.com/site/natesprograms/Home/MWParser2.txt  --Than4213 14:14, 28 January 2010 (UTC)
 * It looks like my commit access request has still not been processed. Could you check my change into a branch and let me know which branch.  I would greatly appreciate it.  --Than4213 20:12, 1 February 2010 (UTC)
 * I'll try and do it as soon as possible; I'm afraid I'm totally overloaded with RL work at the moment, but that should ease up by the end of the week. I'll race Tim to the appropriate buttons   Happy ‑ melon 22:50, 1 February 2010 (UTC)
 * I have created a branch at /mediawiki/branches/parser-work in Wikimedia's SVN repo, and applied your initial patch, in revs 62082-4. My commiserations that your access request is taking its time; hopefully you won't have to wait as long as I did   Happy ‑ melon 14:24, 7 February 2010 (UTC)
 * Just in time, I'm going home from vacation today :). Thank you. You have been very helpfull.  --Than4213 21:53, 7 February 2010 (UTC)

Gurch

 * Requested commit name:
 * Expected area to work in: API (core and extensions)
 * key
 * Past work on MediaWiki: a half-dozen one-line patches, a larger one that, to quote Tim, "may crash the site", some bug/feature requests, some documentation and a fair bit of general familiarity with the technical side of things on Wikimedia projects.
 * Past programming experience: I wrote Huggle, whether that's a good or bad thing is open to interpretation.

Roan and Reedy both insisted I request this. Gurch 13:00, 24 January 2010 (UTC)

User:HappyDog
HappyDog 14:34, 10 February 2010 (UTC)
 * Requested commit name:
 * Expected area to work in: CodeReview extension initially. I have a bunch of patches in my local copy, mostly related to using it with multiple repos, and would like to give them back to the community.  Also did some work on integrating the namespace manager but that has bit-rot now - would like to pick that up again.  In longer term would like to do some work on the core, in particular with relation to easing deployment for new users and simplifying general system management.  May also move some of my more stable extensions into the MW repo, if appropriate.
 * link to public key
 * Past work on MediaWiki - Long time hacker of MW (since v1.3) have written multiple extensions, have contributed massively to the documentation on this site, which involved a lot of in-depth investigation of the source code. Have submitted patches but they invariably got fixed by someone else before my patch was reviewed, so I stopped bothering.  However have a long-standing familiarity with the code base.  Am familiar with the communication channels (wikitech-l, #mediawiki, etc.) and the design philosophies behind the software and the directions it is going in.
 * Past programming experience - Degree in Computer Science. Professional programmer since 1998.  PHP main language since 2001.  Would class myself as a PHP expert (so not quite at guru level yet...).  Work full-time developing PHP-based web applications and use SVN and Bugzilla on a day-to-day basis for our in-house project management.  Very familiar with HTML/XHTML/XML and applicable standards, SQL, CSS, JavaScript and many other less-relevant technologies.