Most people just install MySQL and use it.  They do not use MySQL to
create other software (derivetive).
As for jOpenDocument, it is a library, so would be better under the LGPL
or similar.

--
Darren Bell





-----Original Message-----
From: ViK Scrawl <[email protected]>
Reply-to: [email protected]
To: [email protected]
Subject: [jopendocument] Re: Several questions
Date: Fri, 15 May 2009 12:54:19 +0100


Darren,
> GPL is not Business-Unfriendly, it just seems that this library should 
> be using the LGPL.
> Selections of licenses is critical.  As jOpenDocument is a Library, 
> then it should be LGPL.
unfriendly does not mean impossible. Take a look at MySQL, business best 
friend ;)
I also think a license like LGPL is more appropriate for a library. 
Correct me if wrong, but I believe LGPL is more similar to Apache and 
EPL, since it allows using such components by other applications without 
re-licensing to GPL?

Cheers,
Víctor.

Darren Bell escribió:
> GPL is not Business-Unfriendly, it just seems that this library should 
> be using the LGPL.
> Selections of licenses is critical.  As jOpenDocument is a Library, 
> then it should be LGPL.
>
> Thoughts?
> --
> *Darren Bell*
>
>
>
> -----Original Message-----
> *From*: Guillaume Maillard <[email protected] 
> <mailto:guillaume%20maillard%20%[email protected]%3e>>
> *Reply-to*: [email protected]
> *To*: [email protected] 
> <mailto:[email protected]>
> *Subject*: [jopendocument] Re: Several questions
> *Date*: Fri, 15 May 2009 01:14:04 +0200
>
> Hi Victor,
>  
>
>
>     I would like to point out a problem I realized too late during my
>     investigation in this library. Unfortunately (for us) the
>     jOpenDocument is GPL licensed, which makes it impossible for us to
>     integrate in our product. Commercial license is neither an option
>     :P So I finally decided creating my own :( This is one of the
>     problems of business-unfriendly licenses like GPL. 
>
>
>
> I don't undestand your point, you want to integrate jOpenDocument in 
> your commercial application,
> so we can conclude you want to make money with your product. Only few 
> people could work for free, so it's perfectly fair.
>
> You don't want to comply to the GPL licence with your product because 
> you need to sell a closed product
> and you ask us to do the opposite of what you do ????
>
> I wonder why you are not following your advice by releasing your 
> product under GPL ou Apache licence...
> or the buy a commercial licence, which will cost you just a little 
> percentage of the revenue thatI hope you will get with your application.
>
> What a strange world :)
>
> Regards,
> Guillaume
> ------------------------------------------------------------------------
>
> *This message (including any attachments) may contain confidential 
> information intended for a specific individual and purpose. If you are 
> not the intended recipient, delete this message. If you are not the 
> intended recipient, disclosing, copying, distributing, or taking any 
> action based on this message is strictly prohibited. *
>

Reply via email to