You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@livy.apache.org by Pat Ferrel <pa...@occamsmachete.com> on 2019/04/08 23:32:08 UTC

Why not a Top Level Project?

To slightly over simplify, all it takes to be a TLP for Apache is:
1) clear community support
2) a couple Apache members to sponsor (Incubator members help)
3) demonstrated processes that follow the Apache way
4) the will of committers and PMC to move to TLP

What is missing in Livy?

I am starting to use Livy but like anyone who sees the “incubator” will be
overly cautious. There is a clear need for this project beyond the use
cases mentioned. For instance we have a Machine Learning Server that tries
to be compute engine neutral but practically speaking uses Spark and HDFS
for several algorithms. We would have a hard time scaling a service that
runs the Spark Driver in the server process. The solution may well be Livy.

Here’s hoping Livy becomes a TLP

- Pat

Re: Why not a Top Level Project?

Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi,

Graduation is a fair question and I think it makes sense.

More than community support, they key thing is a diverse and active
community, and I think we are not so far.

I'm proposing the start the "maturity assessment matrix". It's a first
step. I'm volunteer to start to prepare this.

Thoughts ?

Regards
JB

On 09/04/2019 01:32, Pat Ferrel wrote:
> To slightly over simplify, all it takes to be a TLP for Apache is:
> 1) clear community support
> 2) a couple Apache members to sponsor (Incubator members help)
> 3) demonstrated processes that follow the Apache way
> 4) the will of committers and PMC to move to TLP
> 
> What is missing in Livy?
> 
> I am starting to use Livy but like anyone who sees the “incubator” will be
> overly cautious. There is a clear need for this project beyond the use
> cases mentioned. For instance we have a Machine Learning Server that tries
> to be compute engine neutral but practically speaking uses Spark and HDFS
> for several algorithms. We would have a hard time scaling a service that
> runs the Spark Driver in the server process. The solution may well be Livy.
> 
> Here’s hoping Livy becomes a TLP
> 
> - Pat
> 

-- 
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com