incubator-flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Carol Frampton <>
Subject [Mentor] review NOTICE and LICENSE files
Date Fri, 18 May 2012 19:41:50 GMT

I did some work on the NOTICE and LICENSE files this afternoon.  I'd appreciate it if you
could take a quick look and provide feedback on what doesn't look right or is the wrong format,
what's missing etc?

The LICENSE file goes into the source distribution.
The LICENSE.bin file gets concatenated to the LICENSE file for the binary distribution.


 1.  If we incorporate code into our project that is from another Apache project covered by
an Apache v2 license do we still call out that we've taken the code or does the Apache license
at the top of the LICENSE file cover all Apache code, not just Flex code?
 2.  Same question, but we're incorporating code covered by an Apache 1.1 license.
 3.  Many of the jars we use have their own LICENSE and NOTICE files. Right now they are all
in the lib directory right next to their jar.  I've seen other projects put them all in a
legal, LICENSE or NOTICE directory.  What is the proper way to organize these and how do you
refer to them in the Apache Flex LICENSE file?
 4.  If we include a jar that includes other stuff and has NOTICES and LICENSES from its dependencies
to we pull them all up into our LICENSE?  I've seen lots of questions about this and I still
don't understand what the right way to do this is.

Depending on the answers to the above questions I'm sure I still need to make some changes
to get everything right.

If you know of any projects that you think are good examples I would be happy to take a look.
 Last time I tried to look for examples I didn't find a consistent way of doing things so
I couldn't tell what was the preferred way.


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message