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. That is if you
cannot include the source code itself. But the source code keeps changing
with new release, so a pointer / link would work best - IMO.
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. If that is the case purely (and I am
not a lawyer) then I think you should be good to go with the above.
On Dec 31, 2007 9:54 AM, Mark Phippard <email@example.com> wrote:
> On Dec 31, 2007 9:16 AM, Garret Wilson <firstname.lastname@example.org> wrote:
> > Awesome! Although it won't help me create a repository remotely, it will
> > allow me to create a local repository, which is a short-medium-term
> > solution.
> > I had shied away from SVNKit before because its license forced me to
> > effectively open-source my application. After reading the license at
> > http://svnkit.com/license.html, though, it doesn't appear that
> > "redistribution" covers web applications. As I understand it, then,
> > simply depoying a web application that uses SVNKit wouldn't require me
> > to release the source code of the web application---would it?
> Couldn't you just as easily shell out and run the svnadmin command?
> If not, then the Subversion JavaHL bindings also have this ability.
> Just look at the SVNAdmin class. Of course this also means the
> Subversion libraries themselves also have an API for this as JavaHL
> simply consumes the library API.
> Mark Phippard
Received on Mon Dec 31 16:47:02 2007