Re: [circle] GPL Violatin - no I wont

[David Irvine]

On Thu, 2006-01-19 at 13:24 +0500, Faried Nawaz wrote:
> On 1/19/06, address@hidden <address@hidden> wrote:
>
> > On the GPL part, as I understand it you can sell copies for whatever you
> > want, but you can't close the source or disallow other people from
> > redistributing it.  If you want to carry out your plan, you'd have
> > to write your own code instead of modifying an existing GPL'ed project.
>
> Actually, I think you can.  If you own the copyrights to all the code,
> you can change the license at any time.  However, you can't stop
> distributing the already publicly available GPL'd code, nor prevent
> others from distributing it.
>
> Since this person wants to develop it openly, and close its source
> once it's developed, it's unlikely that he'd be able to get anyone to
> pay for the closed version.  The GPL'd code will do everything the
> closed code will do, or will be easy to modify to match the closed
> version's featureset.
>
>
> _______________________________________________
> Circle-discuss mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/circle-discuss
Thanks guys. I understand the GPL / BSD issues. What I may do is recode some of this as GPL (as I would have no choice as that's what it is) and then keep it separate from the code base I will close (for a wee while) and run them as two independently running programs therefor not breaking GPL (linked code must be GPL). I would then output from one system to this and back again. It just makes it not so good for the usr but then when I do open source my bit they can be linked at the code level. The only issue is I would be stuck with a GPL thing and I am not sure about doing that.

Many thanks for your time.

David

signature.asc
Description: This is a digitally signed message part