Podling brand and trademark

2020-02-02 Thread Antoine Toulme
Hello folks,

The report has a new question that I am not sure Tuweni looked into: "Is the 
PPMC managing the podling's brand / trademarks?”
Pretty sure we haven’t done much in that department.

Is there a guideline or a process we can follow?

Thanks in advance!

Antoine


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



[ANNOUNCE] Apache Livy 0.7.0-incubating released

2020-02-02 Thread Saisai Shao
The Apache Livy team is proud to announce the release of Apache Livy
0.7.0-incubating.

Livy is web service that exposes a REST interface for managing long
running Apache Spark contexts in your cluster. Livy enables
programmatic, fault-tolerant, multi-tenant submission of Spark jobs
from web/mobile apps (no Spark client needed). So, multiple users can
interact with your Spark cluster concurrently and reliably.

Download Apache Livy 0.7.0-incubating:
http://livy.incubator.apache.org/download/

Release Notes:
http://livy.incubator.apache.org/history/

For more about Livy check our website:
http://livy.incubator.apache.org/

We would like to thank the contributors that made the release possible!

=
*Disclaimer*

Apache Livy (incubating) is an effort undergoing incubation at The
Apache Software Foundation (ASF), sponsored by the name of Apache
Incubator PMC. Incubation is required of all newly accepted projects
until a further review indicates that the infrastructure,
communications, and decision making process have
stabilized in a manner consistent with other successful ASF projects.
While incubation status is not necessarily a reflection of the
completeness or stability of the code, it does indicate that the
project has yet to be fully endorsed by the ASF.


Re: [VOTE] Release Apache PageSpeed 1.14.36.1-rc3

2020-02-02 Thread Otto van der Schaaf
Well, we include
https://github.com/chromium/chromium/blob/2ca8c5037021c9d2ecc00b787d58a31ed8fc8bcb/base/third_party/nspr/LICENSE
 [1]
Now I'm wondering: should that propagate to our top-level LICENSE?

[1] ~/rc-4/third_party/chromium/src/base/third_party/nspr$ ls -lah

-rw-r--r--  1 oschaaf oschaaf 1.7K Jan 31 19:52 LICENSE
.

Op zo 2 feb. 2020 om 11:17 schreef Justin Mclean :

> Hi,
>
> > which doesn’t contain any compiled code plus moves to DISCLAIMER-WIP to
> track the
> > remaining issues.
>
> Great!
>
> > The MPL licensed source code is still there
>
> Have you included it’s license?
>
> > Is this a blocking issue now that we have the WIP disclaimer in place?
>
> In general not, but you still need to abide by the MPL license terms.
>
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


Re: [VOTE] Release Apache PageSpeed 1.14.36.1-rc3

2020-02-02 Thread Justin Mclean
Hi,

> which doesn’t contain any compiled code plus moves to DISCLAIMER-WIP to track 
> the
> remaining issues.

Great!

> The MPL licensed source code is still there

Have you included it’s license?

> Is this a blocking issue now that we have the WIP disclaimer in place?

In general not, but you still need to abide by the MPL license terms.

Thanks,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



Re: [VOTE] Release Apache PageSpeed 1.14.36.1-rc3

2020-02-02 Thread Otto van der Schaaf
I staged another release candidate over at
http://people.apache.org/~oschaaf/mod_pagespeed/1.14.36.1-rc4/  which
doesn't
contain any compiled code plus moves to DISCLAIMER-WIP to track the
remaining issues. I'll try to move this to the right
staging location (https://dist.apache.org/repos/dist/dev/incubator/pagespeed)
but need to polish my subversion skills, it has been
quite a while since last using that :-)

The MPL licensed source code is still there, it gets pulled in via
Chromium. This involves nspr via our chromium dependency
https://github.com/chromium/chromium/blob/2ca8c5037021c9d2ecc00b787d58a31ed8fc8bcb/base/third_party/nspr/

I think we rely on prtime.cc/.h, possibly we can replace that. Is this a
blocking issue now that we have the WIP disclaimer in place?

Otto

Op wo 27 nov. 2019 om 01:36 schreef Justin Mclean :

> Hi,
>
> Is this a call for an IPMC vote on this podlings release? If so the
> release candidate isn't in the correct place [1] (but that's easily fixed
> without revoting).
>
> However, there seems to be some larger issues, so sorry but I’m -1
> (binding) as there category B code and compiled code in the source release.
>
> I checked:
> - incubating in name
> - hashes and signatures are fine
> - DISCLAIMER exists
> - LICENSE and NOTICE exist
> - The code base appears to contain MPL licensed source code, this is not
> allowed as it’s category B. This is OK if these are dependancies and not
> included.
> - The release contains compiled code.
> [3][4][5][7][8][9][10][11][12][13][14]
> - The release contains cryptography [6]. Has an export license been
> obtained for this? [17]
> - How is this file [15] licensed? from here? [16] I notice a number of
> other images are used in tests, how are these files licensed?
> - There are a large number of files without ASF headers, while not all of
> the files need ASF headers a large number will.
> - I didn’t try to compile
>
> It may be that the LICENSE file need some more work I’ve not done an
> exhaustive check but this to can be refined over time with the WIP
> DISCLAIMER in place. It is missing a few thing I think for example:
> - This MIT licensed file [19]
> - This MIT licensed file [20] which also includes sizzle.js
>
> You might also want to consider replacing the license text of each 3rd
> party bit in a seperate file in a single folder (called say licenses) and
> point to that from the LICENSE as it can be easier to read.
>
> What I suggest you do is move to using the WIP disclaimer [18], add the
> known issues above, make a new release (without any compiled code if
> possible), and then work on a way to resolve each of the issues in future
> releases.
>
> Thanks,
> Justin
>
> 1. https://dist.apache.org/repos/dist/dev/incubator/pagespeed
> 2. https://www.apache.org/legal/resolved.html#category-b
> 3. ./pagespeed/automatic/rewriter_speed_test.o
> 4. ./pagespeed/automatic/static_rewriter_main.o
> 5. ./pagespeed/automatic/static_rewriter.o
> 6 ./third_party/grpc/src/third_party/boringssl
> 7. ./third_party/libwebp/swig/libwebp.jar
> 8. ./third_party/libwebp/gradle/wrapper/gradle-wrapper.jar
> 9 ./pagespeed/automatic/static_rewriter
> 10 ./pagespeed/automatic/rewriter_speed_test
> 11 ./pagespeed/automatic/pagespeed_automatic.a
> 12 ./third_party/brotli/src/tests/testdata/bb.binast
> 13 ./third_party/libwebp/webp_js/test_webp_wasm.webp
> 14 ./third_party/libwebp/webp_js/test_webp_js.webp
> 15. ./install/mod_pagespeed_example/images/Beach.jpg
> 16. https://www.pexels.com/photo/dirt-road-dry-fence-footprints-210289/
> 17. http://www.apache.org/licenses/exports/
> 18. https://incubator.apache.org/policy/incubation.html#disclaimers
> 19 ./pagespeed/kernel/js/testdata/third_party/prototype.original
> 20 ./pagespeed/kernel/js/testdata/third_party/jquery.original
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>