[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [CONTRIB] remove-zombie-locks.py, workaround for Issue #2507

From: Nathan Kidd <nathan-svn_at_spicycrypto.ca>
Date: 2007-01-09 23:44:17 CET

C. Michael Pilato wrote:
> Nathan Kidd wrote:
>> c) I didn't think this script should have long-term use or need to be
>> migrated out of contrib/ into svn proper (i.e. as you mentioned svnadmin
>> should eventually know how to clean a repository, and the code should
>> eventually be fixed to remove need for a hook-script.)
>>
>> Do you expect it to be a problem? (Or turned around, in what ways would
>> it be helpful if it was BSD-ish?)
>
> Besides the fact that this community has a history of encourage less
> restrictive licenses,
*ouch* /me resists "restrictive" debate :)

> the concern on my mind was with that item (c)
> above. Your algorithm is the obvious one, but it feels like shady
> business "copying" (with Python-to-C translation, of course) your GPLed
> logic into svnadmin.

(If in a strict legal sense implementing the same *algorithm* was
copyright infringement no software development could go on at all! The
same restrictions apply to changing a *license* from GPL -> 'Subversion
5 clause' as e.g. APL -> 'Subversion 5 clause', if it is a matter of
adding code to svnadmin.)

However, we have had a huge benefit from CollabNet's Subversion
sponsorship, so if you really think you'll get a tangible benefit from
it I don't mind to use the Subversion license.

-Nathan

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jan 9 23:43:20 2007

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.