+1 binding
Regards,
Tim
On 26/08/16 13:37, Ellison Anne Williams wrote:
> Hi All,
>
> The PPMC vote for the Apache Pirk 0.1.0-incubating release has passed after
> updating the cryptographic export information; it is a source-only release
> (no binary artifacts). We kindly request that the IPMC
Since Common Workflow code appears to be under ALv2, it might be worth
contacting that community and asking them to re-license the logo under
ALv2 as well and explain how the current logo licensing makes ALv2
consumption more difficult if they want their logo included in downstream
releases.
My 2
Indeed, I find it wholly unthinkable that we'd include any LGPL bits in
an Apache product release, even if it's an ambiguous choice of licenses.
There is no ambiguity in what types of licenses are allowed in Apache
releases.
The only way to do this (IMO, I'm not VP, Legal) is to make clear that
w
+1 (binding)
Checked:
- NOTICE, DISCLAIMER, LICENSE are there
- ASF headers
- version includes incubating
Regards
JB
On 08/26/2016 02:37 PM, Ellison Anne Williams wrote:
Hi All,
The PPMC vote for the Apache Pirk 0.1.0-incubating release has passed after
updating the cryptographic export infor
