I'd just like to let the many a non-committer extension developer here know that I am open for committing any sane extension (Yes, DPL does count as sane in this category ;) heh...) into Subversion.
Nothing beats revision management. Even if it's not Wikimedia's SVN. I even have my own repo for Wiki-Tools which I commit my variety of extensions into. Once I look over SSH keys and a bit more on security I'd even be willing to give other people commit access for those who can't take the long wait to being able to get commit access to Wikimedia's SVN. But wherever it's managed, there is nothing like being able to svn-update to grab all the new changes to extensions and keep yourself running with good code. I personally get a very bad taste in my mouth when I see an extension on MediaWiki.org which I am forced to use some manual method of grabbing the data just to install it. I tend to avoid installing those if possible. But not only does it ruin the taste of the extension, it also means there aren't as many people poking in the code and making sure it works right, and it's up to usable standards. Plus Wikimedia's SVN has Betawiki's support.
So, I'm here basically saying... "If you have a sane extension up on MediaWiki.org, I'd be happy to help commit it to Subversion so that myself and other people can poke at it, translate it, and keep it nicely working with MediaWiki. And also make it easier for people to get ahold of the code. And I'll even be happy to apply any patches you have to update your extension with new features you've made". Of course, I'm not going to commit something completely stupid, but there is a small bit of room for extensions which need a bit of standards tweaking after being committed. And yes, I'll probably periodically poke various developers as I find extensions I personally would like to install, and ask them if they would let me commit the extension to SVN, even just to make sure that I can use a reliable extension rather than something left on the wiki.