Hi,
> Just so that we get it right the next time, can you verify that the current
> NOTICE is acceptable or does it require further changes?
Doesn’t look correct to me as you are including items that should be in LICENSE
not NOTICE. In general permissive licensed items don’t need to be mentioned
The process for transferring the rights to the name PredictionIO has
started at Salesforce. I'm optimistic but can't guarantee an outcome as I
am not empowered to make such a decision wearing any hat. I think we can
proceed with the proposal using the PredictionIO mark conditionally as the
desired
I am just waiting on an accept from Alex to be in the initial committers
list and will then update the proposal on the wiki.
On Mon, May 16, 2016 at 12:07 PM, Simon Chan wrote:
> Yes, it includes everyone who previously contributed code from PredictionIO
> before the acquisition and still want
Yes, it includes everyone who previously contributed code from PredictionIO
before the acquisition and still want to be involved in the project.
We may have missed "Alex Merritt", going to add him to the list soon.
Simon
On Mon, May 16, 2016 at 11:58 AM, Suneel Marthi wrote:
> I do have a que
I do have a question about the proposed list of committers.
Does the list also include all of those folks who were with PredictionIO
(and had contributed to the project) and then chose to leave when PIO was
acquired by Salesforce?
On Mon, May 16, 2016 at 1:13 PM, Jean-Baptiste Onofré
wrote:
+1 to integrating with Beam
On Mon, May 16, 2016 at 1:13 PM, Jean-Baptiste Onofré
wrote:
> Hi,
>
> I second Roman here.
>
> Using Beam to abstract the execution environment would provide a very
> flexible architecture for PredictionIO.
>
> It would benefit for both projects.
>
> Regards
> JB
>
By the way, we have some discussion about integrating Zeppelin with Beam ;)
Regards
JB
On 05/15/2016 02:32 AM, Roman Shaposhnik wrote:
Super excited to see this proposal! This will finally allow us to have
an ASF managed
backend for next generation data-driven apps that I see emerging quite rap
Hi,
I second Roman here.
Using Beam to abstract the execution environment would provide a very
flexible architecture for PredictionIO.
It would benefit for both projects.
Regards
JB
On 05/15/2016 02:32 AM, Roman Shaposhnik wrote:
Super excited to see this proposal! This will finally allow
+1 (binding)
Regards
JB
On 05/13/2016 08:22 PM, Billie Rinaldi wrote:
Since discussion has died down, I would like to call a VOTE on accepting
Fluo into the Apache Incubator.
Proposal: http://wiki.apache.org/incubator/FluoProposal
[ ] +1 Accept Fluo into the Apache Incubator
[ ] +0 Abstain.
[
Hi Alan/Justin,
Just so that we get it right the next time, can you verify that the current
NOTICE is acceptable or does it require further changes?
https://git-wip-us.apache.org/repos/asf?p=incubator-ranger.git;a=blob;f=NOTICE.txt;h=3130ce2dd60bd148aa74e13610a218704dc3e1a7;hb=refs/heads/ranger-0
+1 (binding)
Billie Rinaldi wrote:
Since discussion has died down, I would like to call a VOTE on accepting
Fluo into the Apache Incubator.
Proposal: http://wiki.apache.org/incubator/FluoProposal
[ ] +1 Accept Fluo into the Apache Incubator
[ ] +0 Abstain.
[ ] -1 Do not accept Fluo into the Ap
11 matches
Mail list logo
