Version control support call for help

[Kai Willadsen <kai willadsen gmail com>]

Hi all,

Meld supports a wide range of version control systems, which is great
[0]. However, while these modules by-and-large work, most of them are
not actively maintained. I maintain Git fairly actively, and try to
pay attention to Mercurial and Subversion, but if our Bazaar support
suddenly broke it would take me months to notice. Darcs or CVS could
stop working and I'd never know.

In the 1.7.x series, there's a new (optional) APIs for getting files
from version control, and more recently for giving VC modules more
control over how actions like update, add, revert and commit behave.
There's also been enhancements to launch three-way merge comparisons
for conflicted files from within Meld, and most recently additions for
unpushed commit notification and pre-filled commit messages. All of
these work great... for Git. For anything else, what works is a
toss-up. Which brings us to the main point of this mail...

Meld needs people interested in taking ownership of VC modules.

Owning a VC module means making sure that things work as expected,
from the level of 'can I commit a change' down to checking that
sensitivity setting works correctly (right now it doesn't work
properly anywhere). It also means making sure that new internal APIs
work well with that VC, and getting Meld to expose whatever hooks are
needed to improve integration.

If you're interested in helping out, feel free to hassle me
personally, post to the list, or just start filing and fixing bugs.
Any assistance is appreciated.

cheers,
Kai

[0] And looking through things, I've now noticed that we still
'support' Codeville and Arch, neither of which really exist anymore,
so that's... nice. Expect these plugins to disappear Real Soon Now
unless someone steps up to take them.