Robert Koberg <email@example.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
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.
Anyway, sounds like the new file system would be the best answer so you
could just avoid the issue altogether.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Thu Jul 15 02:54:39 2004