incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mattmann, Chris A (388J)" <>
Subject Re: Basing Apache releases on releases from incubating projects
Date Wed, 01 Dec 2010 16:58:56 GMT
Hi Bertrand,

>> The difference is that the incubator code comes from
>> Apache, with all the ASF IP due diligence.  If we use
>> a third-party library that's under the AL, we mention
>> that it's not from Apache.  Our customers can then
>> decide for themselves how much they trust that other
>> source.  My understanding....
> It is common for podlings to import their code here and only then
> start cleaning up dependencies that do not comply with ASF
> requirements. So if another project release contains unreleased code
> from a podling, it might not be clean.

In what way would it be any more unclean compared with including unreleased ASLv2 licensed
code from e.g., Google Code or Sourceforge (which I've seen done before)? Why should we be
holding *our own ASF podlings* to a higher accord as downstream dependencies and limiting
the ability of downstream projects to include the great work being done in the Incubator?
I simply don't agree with that.


Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message