Nigel, I was looking forward to your answers. They are well thought out. :-)
But this part isn't true: "Whereas Apache is currently just ALv2 or ALv2 +
some permissive license with a attribution clause." Read our NOTICE files
(such as they currently exist), or browse the public archives of our
contributions and our aggregations, or run code scans. The current policy
allows "exceptions" to that policy you paraphrased:
https://www.apache.org/legal/ramblings.html
http://www.apache.org/legal/resolved.html
OTOH, the draft proposal is less than a page long and fits easily in an
email. (See attached.)
Under the current rambled Apache policy there is a Legal-JIRA that is
supposed to be posted for every question about what is "an exception."
We're in the 200's in that archive. And the responses there do not benefit
from any of the analytical skills [like Nigel's and many others!] here at
OSI's license-discuss@.
So help Apache! If there is a set of OSI-approved licenses that adequately
scope "aggregations," including of course the EPL and MPL and the like, that
you think are appropriate for an Apache project to include in an Apache
aggregation, I'd much rather that OSI identify those licenses than that
Apache's engineers JIRA it to death.
The statement that you "use [GPL] where applicable" is right-on! I
occasionally recommend that license too (as at CAVO@ here at OSI). But
please don't forget the final paragraph in the draft Apache proposal:
You may influence the inclusion or exclusion of specific third party
contributions under OSI-approved licenses by joining the Apache project. All
such decisions are made by Apache projects in public.
Under the Apache Way, I'd rather trust an OSI-blessed list of acceptable
FOSS licenses, and have Apache projects give you a NOTICE file and let you
decide. Remember, under ALv2 our Apache distributed aggregations are ALL
always FOSS.
Finally, please, I'd rather hear the following statement from another brave
lawyer here besides me.
Nobody who modifies and redistributes software should accept the safety of
Apache or any other FOSS software in a "brain-dead" way (quoting another
email here). Be aware that we live in a commercial open source software
world that includes the legal doctrine of "willful blindness
<http://en.wikipedia.org/wiki/Willful_blindness> ."
/Larry
Lawrence Rosen
"If this were legal advice it would have been accompanied by a bill."
From: Tzeng, Nigel H. [mailto:[email protected]]
Sent: Thursday, May 28, 2015 9:40 AM
To: Lawrence Rosen; 'License Discuss'
Subject: Re: [License-discuss] Proposal: Apache Third Party License Policy
Larry,
We're not afraid of GPL and use it where applicable. The "where applicable"
part is the issue. Same with "ALL other" OSI-approved licenses since each
package would have to be reviewed as to whether it would be okay.
Whereas Apache is currently just ALv2 or ALv2 + some permissive license with
a attribution clause. It is easy for a Project Manager or Legal to say "if
it's from Apache it's okay to use". It's a known quantity and you can trust
the brand. Muddy the waters and this is no longer true and a huge step
backwards.
Show me the case law to prove what you term aggregation is not what the FSF
calls derivative and provide indemnification against copyright infringement
if it isn't aggregation.
THEN the concerns are mitigated. Otherwise inclusion of any copyleft
licensed code in Apache projects is a huge issue for users.
From: Lawrence Rosen <[email protected] <mailto:[email protected]> >
Reply-To: Lawrence Rosen <[email protected] <mailto:[email protected]>
>, License Discuss <[email protected]
<mailto:[email protected]> >
Date: Wednesday, May 27, 2015 at 2:17 PM
To: License Discuss <[email protected]
<mailto:[email protected]> >
Subject: Re: [License-discuss] Proposal: Apache Third Party License Policy
Nigel, your answer echoes many others:
> If I have to start checking every Apache package for GPL code I'll have to
> strongly recommend that we approach all Apache packages with caution.
If we amended the proposal to leave out the GPL licenses, would that calm
your concerns?
I'd really hate to do that at Apache for that set of generous FOSS licenses,
but fear is fear.... Apache didn't cause this fear of "infection" and Apache
can't cure it. There is a group of attorneys that is drafting an appropriate
"exception" that would allow at least some GPL software to be aggregated
with Apache software.
But are ALL other OSI-approved licenses OK with you?
/Larry
From: Tzeng, Nigel H. [mailto:[email protected]]
Sent: Wednesday, May 27, 2015 9:42 AM
To: [email protected] <mailto:[email protected]> ; [email protected]
<mailto:[email protected]> ; 'License Discuss'
Subject: Re: [License-discuss] Proposal: Apache Third Party License Policy
Thanks, without the context it was somewhat harder to follow on
license-discuss.
Consider this a vote in the negative as a non-member user of Apache
software. If I have to start checking every Apache package for GPL code I'll
have to strongly recommend that we approach all Apache packages with
caution.
Becoming a "universal acceptor" significantly impacts your ability to be a
"universal donor". I have no desire to accidentally be the cause of any
organization I work for becoming the test case for what is an aggregation vs
what is a derivative. If Apache was willing to indemnify downstream
users.yah, I didn't think so.
Nice try though.
From: "[email protected] <mailto:[email protected]> "
<[email protected] <mailto:[email protected]> >
Reply-To: "[email protected] <mailto:[email protected]> "
<[email protected] <mailto:[email protected]> >, "[email protected]
<mailto:[email protected]> " <[email protected]
<mailto:[email protected]> >, License Discuss
<[email protected] <mailto:[email protected]> >
Date: Tuesday, May 26, 2015 at 10:16 PM
To: License Discuss <[email protected]
<mailto:[email protected]> >
Subject: [License-discuss] Proposal: Apache Third Party License Policy
[This has been a hellishly long thread on private Apache lists before the
board cut off discussion on revised policies. Below was the short start of
it I submitted over two weeks ago. Apache board members don't want to revise
current policy. Many Apache members don't want it. Still, it is a serious
proposal to bring some more freedom and cooperation to open source. Please
treat this as a political document for license-discuss@. /Larry]
.
--- Begin Message ---
[This has been a hellishly long thread on private Apache lists before the
board cut off discussion on revised policies. Below was the short start of
it I submitted over two weeks ago. Apache board members don't want to revise
current policy. Many Apache members don't want it. Still, it is a serious
proposal to bring some more freedom and cooperation to open source. Please
treat this as a political document for license-discuss@. /Larry]
**********************
DRAFT: Apache Third Party License Policy (May 10, 2015)
Apache projects have long been universal donors to many other software
projects around the world. We are proud of that. We intend to continue that
tradition by requiring that all software aggregations distributed by Apache
Software Foundation will be licensed to the public under the Apache License
2.0. This means that all of our licensees around the world are free to:
* Use Apache software for any purpose.
* Make and distribute copies.
* Create and distribute derivative works.
* Access and use the source code.
* Combine Apache and other software.
In order to foster our Foundation community ethic to ensure the widest free
participation in the open source software community, Apache has now decided
to become also a universal acceptor of other open source software licensed
to us from around the world.
When technically appropriate for that software in the judgment of the PMC,
Apache projects may accept contributions under ANY OSI-approved open source
license. Such software may now be included in Apache aggregations that, as
described above, will be licensed to the public under Apache License 2.0.
Because Apache projects may now incorporate third party open source software
into our software aggregations, we have added the following procedures for
Apache software releases:
* Because all Apache project contributions will be licensed to Apache
under an OSI-approved open source license, the above list of five
fundamental software freedoms continues to apply to all Apache software.
Downstream users and re-distributors of Apache software can continue to
incorporate all of our open source software into their own products
unmodified without incurring any special derivative work reciprocity
obligations.
* All releases containing any non-Apache open source licensed
contributions will be explicitly identified in a NOTICE file that our
projects will create. The PMC is responsible to ensure that the text in the
NOTICE file expressly satisfies the notice and disclosure requirements of
all relevant contribution licenses.
* Modifiers and re-distributors of Apache software will now need to
read the NOTICE files to determine whether they have any derivative work
reciprocity requirements for specific contributions.
You may influence the inclusion or exclusion of specific third party
contributions under OSI-approved licenses by joining the Apache project. All
such decisions are made by Apache projects in public.
--- End Message ---
_______________________________________________
License-discuss mailing list
[email protected]
http://projects.opensource.org/cgi-bin/mailman/listinfo/license-discuss
