I agree completely - it's hard to manage code and commit patches to
extensions like this - version control is very powerful thing.
I was hesitant to add my extensions to MW repository for it's lack of
tagging and branching (obviously it's limited because it's one big repo for
all code). That's why I just created Google Code Hosting account and
creating repos for each of my extensions there.
I think it's reasonable to expect this and many developers do use Source
Forge or Google Code Hosting - I think overall extension management policy /
best practices should keep this in mind.
--
Sergey Chernyshev
http://www.sergeychernyshev.com/
On Thu, May 8, 2008 at 4:51 AM, Gerard Meijssen
gerard.meijssen@gmail.com
wrote:
> Hoi,
> Can we talk about how we can even better support MediaWiki extensions..
> Betawiki and SVN are only two aspects to make extensions work properly..
> Tomorrow I am back home, currently in Milan Italy..
> Thanks,
> Gerard
>
> On Thu, May 8, 2008 at 10:42 AM, DanTMan
dan_the_man@telus.net wrote:
>
> > 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.
> >
> > --
> > ~Daniel Friesen(Dantman) of:
> > -The Gaiapedia (
http://gaia.wikia.com)
> > -Wikia ACG on Wikia.com (
http://wikia.com/wiki/Wikia_ACG)
> > -and Wiki-Tools.com (
http://wiki-tools.com)
>