On Thu, Dec 11, 2008 at 2:34 PM, David Weintraub <qazwart_at_gmail.com> wrote:
> On Thu, Dec 11, 2008 at 11:05 AM, Andy Levy wrote:
>> Why would you have to license SVNKit? If you're a "consumer"
>> of it, or distributing an Open Source project that uses it,
>> it's Open Source. If you want to integrate it into a non-Open
>> Source application, then you have to license it.
>>
>> http://svnkit.com/licensing.html
>
> The license could be read in two ways:
>
> * If you have a proprietary commercial application, and you
> redistribute SVNKit with your application, you need to pay a licensing
> fee.
>
> * If you used SVNKit while developing your proprietary commercial
> application, you need to pay a licensing fee.
>
> I read it the second way because it doesn't make much sense to read it
> the first way for open source applications. Most open source licenses
> wouldn't allow the project to have a proprietary component like SVNKit
> to be distributed as part of the application.
>
> Besides, if the first example this was the case, how many licenses
> would TMate Software be selling? Only commercial proprietary
> applications that were written in Java and needed access to Subversion
> would have to pay a licensing fee. So, you are pretty much limiting it
> to Java based, proprietary IDEs.
You are reading their license incorrectly. Feel free to email
support_at_svnkit.com for clarification.
The intent of their license is basically that it is OK to use it in
open source applications, but they also offer a commercial license so
that people that want to embed SVN functionality in commercial
applications have to license it from them.
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=983002
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2008-12-11 20:50:58 CET