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
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
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 os
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
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/
