John Peacock wrote:
> Miller, Eric wrote:
>> Is anyone working on, or interested in working on bringing the perl
>> swig bindings up to date?
>> They look like they are well past their expiration date.
> Nik Clayton was working with adding named parameter support (but I've
> lost track of where that stands). Mattias Engdegard recently submitted
> a patch to add a bunch more client functions, but it doesn't appear to
> have been committed. I don't think your characterization of the code is
> really all that accurate. It's clear that the core committers need to
> get back to the practice of keeping on top of submitted patches.
My patches are still around, but not applied. No one on the list stepped up
to review them, and although I sent them to clkao and firstname.lastname@example.org for
review too I've not heard back from them either.
Lest this be interpreted as whining, it's not. I'm fully aware of how open
source development works, and how we all have our own lives to lead too, I'm
as guilty of that as the next man.
The root problem seems to be that we have a number of non-committers who are
interested in improving the state of the Perl bindings, but no committers
who have the time and the Perl knowledge necessary to provide a sensible
review of the changes that we're proposing.
So it's something of a chicken/egg situation.
I'm not entirely sure how we break this deadlock. My preferred approach
would be for those of us who have expressed an interest (that would be at
least you John, me, and Mattias Engdegard) to be given a commit bit for a
*branch* of the repo expressly for the purpose of working on the Perl
bindings so we can get some of these changes in front of a wider audience.
That plus a dev-perl mailing list is probably all we need to start with.
That is, of course, entirely at the discretion of the Subversion maintainers.
For what it's worth I'll be at the UK Subversion User Group meeting next
I note that C. Michael Pilato will also be there. Are any other
Subversion committers attending? Perhaps we could discuss this over a drink
after the meeting?
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Fri Jan 12 12:28:21 2007