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

Re: Subversion 1.1.0 Release Candidate 1 released.

From: Mark Phippard <MarkP_at_softlanding.com>
Date: 2004-07-15 03:06:39 CEST

Also found this page:

http://www.winterspeak.com/columns/102901.html

Which contains a lot of the interpretation info for the Sleepycat license.
 Interestingly I found it in a message from Ben Reser on another mailing
list archive.

One interesting point was that you could use the free license if you only
used it on one physical server, regardless of the purpose. Obviously that
is over simplifying it, the article has more details.

Mark

Mark Phippard <MarkP@softlanding.com> wrote on 07/14/2004 08:54:19 PM:

> Robert Koberg <rob@koberg.com> wrote on 07/14/2004 08:11:09 PM:
>
> >
> > Our case is probably too unique and I may have over-genralized. We are

> > an application service provider content management system. I would use

> > subversion to manage paying clients file based config, content and
> > templates. I would also use it to version our CMS app.
> >
> >
> > But really I was still confused. I presented different scenarios that
I
> > thought met the license requirements, but the gist I got was that the
> > only way to use XMLDB was to have an open source app (or have all the
> > contributors develop in vi on the remote server...). I don't mind
paying
>
> > (though Tamino was much more feature rich and was much more willing to

> > reduce price for our non-profit client...).
> >
> > I had been hoping (obviously not following very closely) that the file

> > system version of Subversion would not use BDB. Is it necessary? In
> > other words are there plans to *not* use BDB? This is not a major
issue
> > for us as CVS is working fine for our needs -- just interested in
using
> > the better technology.
> >
>
> Subversion 1.1 includes a new native file system option that does not
use
> BDB at all, so yes, that is an option.
>
> Let's say you wanted to use BDB though, obviously at some point you need

> to contact a lawyer and/or Sleepycat but I will give you my
> interpretation:
>
> 1) If you are just offering Subversion hosting as a service, say an ISP

> for example, I do not think you would need a license from Sleepycat.
>
> 2) If you are just using Subversion to manage a commercial application
or
> files for a customer you are getting paid to manage, again, I do not
think
> you would need a license from Sleepycat.
>
> 3) If you were using Subversion as the engine for a commercial CMS then

> it is likely you would have to buy a license. I think an exception
would
> be if your application had an open source license, even if it is not
free.
>
> http://www.sleepycat.com/download/licensinginfo.shtml
>
> Anyway, sounds like the new file system would be the best answer so you
> could just avoid the issue altogether.
>
> Mark
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jul 15 03:07:01 2004

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

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