FOR APPROVAL - Python License Changes

Henrik Ingo henrik.ingo at
Thu May 26 06:35:57 UTC 2011

On Thu, May 26, 2011 at 6:17 AM, John Cowan <cowan at> wrote:
> This is a general problem with permissive licenses: if I incorporate
> BSD-licensed code into a more restrictively licensed file by way of
> merger rather than mere aggregation, the terms of the BSD code demand
> that its license be copied with the source even though it is no longer
> the controlling license of the source.  The result is potentially very
> confusing.

Case in point, MySQL README file:

(See lines from 50 to 1288 :-)

Actually, the README was updated with that long list of licenses
during due diligence for the Oracle acquisition. (Which actually
happened after the acquisition, a deal done over a weekend between
Larry and Scott...) Current versions of MySQL apparently have again
omitted the long list of licenses.

I was once answering a Request for Proposals with a question whether
Sun has or owns all the rights in MySQL. I've forgotten what the exact
terminology was (something more obscure than "intellectual property")
but anyway asked our in-house lawyer who told me it basically means we
own all the code in MySQL. So I told her that's not the case and
generally is not the case for any software. She was stunned to hear
this news. I never got an answer to the question beyond that, but
answered "yes" on the RfP :-) It seems that during the Oracle Due
Diligence some lawyer actually realized how MySQL was created over the

Why they later felt those 1200+ lines could be removed from the
README, I don't know.

henrik.ingo at
+358-40-8211286 skype: henrik.ingo irc: hingo

My LinkedIn profile:

More information about the License-discuss mailing list