public inbox for
 help / color / mirror / Atom feed
From: "Davies, Mike" <>
Subject: RE: SN backend GPL or LGPL?  (was: SourceNav release...)
Date: Wed, 13 Feb 2002 10:38:00 -0000	[thread overview]
Message-ID: <50D13214B9CBD41180800008C7CFB62C45F4D5@AZTEC> (raw)

Hi Robert,

IANAL,  but :

> If we did have the back end torn off of SN, would that make everything
> that used also GPL?

Yes, if it was an extension of GPLed code

> Can we take SN type GPL code, turn it into a library, and 
> then use it in
> an LGPL way?


> What if we had some sort of Corba type middle ware that provided a
> decent distributed API, without actually linking the code in. 
>  Would any
> application that connected to it still be bound by the GPL?

Any changes you made to the Sourcenav Code would be GPLed and you would have
to provide them in the usual ways,  however it seems to me that any
application that used the CORBA interface would be effectively dynamically
linked to it and so might escape the GPL.

> I am trying to find out here if there is any room for commercial
> developers to contribute to SN.  It would be a shame to let 
> it all go to
> waste.

Well,  many commercial firms contribute to GPLed SW,  there is nothing
stopping you from doing that.  If you are trying to make a proprietry
version of SourceNav then this is prohibited by the licence.  That is quite
apart from the implications for the feelings of people who contributed their
efforts freely for the common good.

Mike Davies

             reply	other threads:[~2002-02-13 17:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-13 10:38 Davies, Mike [this message]
2002-02-13 10:50 ` Robert Hartley
2002-02-13 11:25   ` Ian Roxborough
  -- strict thread matches above, loose matches on Subject: below --
2002-02-15  9:43 Doug Fraser
2002-02-13 11:55 Doug Fraser
2002-02-13 12:49 ` Robert Hartley
2002-02-13  9:06 Robert Hartley
2002-02-13 12:19 ` Syd Polk

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=50D13214B9CBD41180800008C7CFB62C45F4D5@AZTEC \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).