Anoop kumar V wrote:
> No, you do not have to "open source" your application. At the very
> least, you would have to include the note (copyright notice and/or
> disclaimer) and a pointer where the latest source code can be obtained
> from.
...
> As I understand, you will be a client to the SVNKit libraries - and
> not really modifying the source code of SVNKit ie., you will only be
> calling the API from within your web application.
That all sounds good, but unfortunately that's not what the SVNKit
license at http://svnkit.com/license.html says. In particular:
"Redistributions in any form must be accompanied by information on how
to obtain complete source code for the software that uses SVNKit and any
accompanying software that uses the software that uses SVNKit."
It doesn't matter whether I'm modifying the SVNKit source code or not.
If I redistribute SVNKit, I must provide access to the source code of my
"software that uses SVNKit". In fact, I even have to open-source
"software that uses the software that uses SVNKit".
It is unclear whether deploying a web application using SVNKit is
"redistribution" of SVNKit under the license, as the license does not
define "redistribution". But either way, I don't see how the text of the
license can support your interpretation above.
Garret
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Dec 31 17:13:51 2007