Subject: Re: Licensing question
From: Rodrigo Barbosa <rodrigob@suespammers.org>
Date: Wed, 9 Nov 2005 16:04:54 -0200

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wed, Nov 09, 2005 at 08:21:22AM -0800, Ben Tilly wrote:
> > 1) I want to develop an application
> > 2) I want PARTS of it to be open source
> > 3) I want to keep 'control' of the application, both financially and legally
> > 4) I don't want to keep 'control' of any PARTS that are open source,
> > just the bits that aren't.
> >
> > Is this at all possible?
> 
> Yes.
> 
> Use the BSD license (or equivalent) for the open source bits.  Make
> the rest proprietary.  The open source bits will be open source.  The
> rest won't.  And the fact that you have contributed open source code
> makes you pro-open source. :-)
> 
> An alternate strategy is to use a dual license, GPL/other, for the
> open source bits.  That will discourage contribution to those bits,
> but it will also discourage competitors for your main product.

LGPL might also me an option.
I have used it in the past for mixed open/closed source products.

[]s

- -- 
Rodrigo Barbosa <rodrigob@suespammers.org>
"Quid quid Latine dictum sit, altum viditur"
"Be excellent to each other ..." - Bill & Ted (Wyld Stallyns)

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFDcjpGpdyWzQ5b5ckRAhH9AKCzFzQ+vB8aEZk4SwOBHS2qvR7f4gCfSAxE
ZaDwPxQxqcPgeevXrCqdQvQ=
=mSry
-----END PGP SIGNATURE-----