13 messages in com.mysql.lists.communityRe: The MySQL FOSS Exception v0.1| From | Sent On | Attachments |
|---|---|---|
| Zak Greant | 12 Mar 2004 03:39 | |
| Andres Salomon | 16 Mar 2004 00:00 | |
| Jan Wieck | 17 Mar 2004 05:36 | |
| Zak Greant | 17 Mar 2004 15:00 | |
| Zak Greant | 17 Mar 2004 15:05 | |
| Andres Salomon | 17 Mar 2004 15:31 | |
| Jan Wieck | 18 Mar 2004 20:43 | |
| Zak Greant | 18 Mar 2004 21:22 | |
| Steve Langasek | 20 Mar 2004 14:41 | |
| Zak Greant | 20 Mar 2004 15:38 | |
| Zak Greant | 21 Mar 2004 09:14 | |
| Jan Wieck | 09 Apr 2004 09:11 | |
| Zak Greant | 22 Apr 2004 17:31 |
| Subject: | Re: The MySQL FOSS Exception v0.1 |
|---|---|
| From: | Jan Wieck (JanW...@Yahoo.com) |
| Date: | 04/09/2004 09:11:00 AM |
| List: | com.mysql.lists.community |
Zak Greant wrote:
On Mar 18, 2004, at 21:43, Jan Wieck wrote:
There is the problem. At the first place in the chain, where it is not made totally clear that "this binary version of BAZBAR is FOOBAR licensed but contains differently licensed libraries, inherited from the included FOOFOO package, that are not fully compliant to the FOOBAR license distribution terms! Please refer to the MyFOO license terms for details of redistributing any rebundled, relinked or otherwise combined packages containing this binary BAZBAR package", the whole thing goes belly up.
Hrm. Now that I think about this a bit more, how is this that different from dealing with any other software package. You always need to check out the licensing requirements. For example, you don't see big warnings on PHP that says:
I see that MySQL has announced and published the FOSS exception already. Did this point cause any changes to it?
Jan
-- #======================================================================# # It's easier to get forgiveness for being wrong than for being right. # # Let's break this rule - forgive me. # #================================================== JanW...@Yahoo.com #