This was extracted (@ 2019-02-20 21:10) from a list of minutes
which have been approved by the Board.
Please Note
The Board typically approves the minutes of the previous meeting at the
beginning of every Board meeting; therefore, the list below does not
normally contain details from the minutes of the most recent Board meeting.
2018 | 2017 | 2016 | 2015 | 2014 | 2013 | 2012 | 2011 | 2010 | 2009 | 2008 | 2007 | 2006 | 2005 | 2004 | 2003 | 2002 | 2001 | 2000 | 1999 | Pre-organization meetings
Livy is web service that exposes a REST interface for managing long running
Apache Spark contexts in your cluster. With Livy, new applications can be
built on top of Apache Spark that requires fine grained interaction with
many
Spark contexts.
Livy has been incubating since 2017-06-05.
Three most important issues to address in the move towards graduation:
1. Grow the community to have more activities.
2. Grow more contributors and committers.
3. Regular release.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
None
How has the community developed since the last report?
Activity has waned a little bit since the last report. Most of new
activity has been to stabilize a new feature (Hive-compatible Thrift
server). Committer activity remains a bit low.
How has the project developed since the last report?
Mainly small bug fixes and stabilization of new code.
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup
[ ] Working towards first release
[X] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
2018-02-06
When were the last committers or PPMC members elected?
2017-09-18
Have your mentors been helpful and responsive or are things falling
through the cracks? In the latter case, please list any open issues
that need to be addressed.
We have not asked much of our mentors, but some are active on the email
lists.
Signed-off-by:
[ ](livy) Bikas Saha
Comments:
[ ](livy) Brock Noland
Comments:
[x](livy) Luciano Resende
Comments:
[X](livy) Jean-Baptiste Onofre
Comments:
IPMC/Shepherd notes:
Livy is web service that exposes a REST interface for managing long running
Apache Spark contexts in your cluster. With Livy, new applications can be
built on top of Apache Spark that require fine grained interaction with many
Spark contexts.
Livy has been incubating since 2017-06-05.
Three most important issues to address in the move towards graduation:
1. Grow the community to have more activities.
2. Grow more contributors and committers.
3. Regular release.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
None
How has the community developed since the last report?
Activity on the dev and user mailing lists as well as the rate of reported
JIRA issues has stayed steady. There has been an uptick of development
activity around adding a new feature to the project (a Hive-compatible
Thrift server implementation).
How has the project developed since the last report?
A new feature (Hive-compatible Thrift server) is being implemented, and
some code to support legacy releases of Java, Scala and Spark have been
removed.
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup
[ ] Working towards first release
[X] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
2018-02-06
When were the last committers or PPMC members elected?
2017-09-18
Have your mentors been helpful and responsive or are things falling
through the cracks? In the latter case, please list any open issues
that need to be addressed.
We have not asked much of our mentors, but they are active on the email
lists.
Signed-off-by:
[ ](livy) Bikas Saha
Comments:
[ ](livy) Brock Noland
Comments:
[x](livy) Luciano Resende
Comments:
[X](livy) Jean-Baptiste Onofre
Comments:
IPMC/Shepherd notes:
Livy is web service that exposes a REST interface for managing long running
Apache Spark contexts in your cluster. With Livy, new applications can be
built on top of Apache Spark that require fine grained interaction with many
Spark contexts.
Livy has been incubating since 2017-06-05.
Three most important issues to address in the move towards graduation:
1. Grow the community to have more activities.
2. Grow more contributors and committers.
3. Regular release.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
None
How has the community developed since the last report?
Activity on the dev and user mailing lists as well as the rate of reported
JIRA issues has stayed steady.
How has the project developed since the last report?
Two security issues are fixed and support version is upgraded to Spark 2.3.1.
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup
[ ] Working towards first release
[X] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
2018-02-06
When were the last committers or PPMC members elected?
2017-09-18
Signed-off-by:
[ ](livy) Bikas Saha
Comments:
[ ](livy) Brock Noland
Comments:
[ ](livy) Luciano Resende
Comments:
[X](livy) Jean-Baptiste Onofre
Comments:
IPMC/Shepherd notes:
Livy is web service that exposes a REST interface for managing long running Apache Spark contexts in your cluster. With Livy, new applications can be built on top of Apache Spark that require fine grained interaction with many Spark contexts. Livy has been incubating since 2017-06-05. Three most important issues to address in the move towards graduation: 1. Grow the community and continue to involve more users and contributors 2. Grow more committers to maintain the project 3. Solidify our release cadence Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? N/A How has the community developed since the last report? Activity on the dev and user mailing lists as well as the rate of reported JIRA issues has stayed steady. How has the project developed since the last report? The master branch has been updated to support Spark 2.3 in our next release. How would you assess the podling's maturity? Please feel free to add your own commentary. [ ] Initial setup [ ] Working towards first release [X] Community building [ ] Nearing graduation [ ] Other: Date of last release: 2018-02-05 When were the last committers or PPMC members elected? 2017-09-18 Signed-off-by: [ ](livy) Bikas Saha Comments: [ ](livy) Brock Noland Comments: [x](livy) Luciano Resende Comments: [X](livy) Jean-Baptiste Onofre Comments:
Livy is web service that exposes a REST interface for managing long running
Apache Spark contexts in your cluster. With Livy, new applications can be
built on top of Apache Spark that require fine grained interaction with many
Spark contexts.
Livy has been incubating since 2017-06-05.
Three most important issues to address in the move towards graduation:
1. Grow the community and continue to involve more users and contributors
2. Grow more committers to maintain the project
3. Solidify our release cadence
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
N/A
How has the community developed since the last report?
Activity on the dev mailing list increased.
How has the project developed since the last report?
We released Livy 0.5.0-incubating with features including:
- Code autocompletion
- Spark SQL support
- Sharing variables across jobs
- Multi-line output for statements
- Using multiple languages in a single session
- Building with Scala 2.11
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup
[ ] Working towards first release
[X] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
2018-02-05
When were the last committers or PPMC members elected?
2017-09-18
Signed-off-by:
[X](livy) Bikas Saha
Comments:
[ ](livy) Brock Noland
Comments:
[X](livy) Luciano Resende
Comments:
[X](livy) Jean-Baptiste Onofre
Comments:
Livy is web service that exposes a REST interface for managing long running
Apache Spark contexts in your cluster. With Livy, new applications can be
built on top of Apache Spark that require fine grained interaction with many
Spark contexts.
Livy has been incubating since 2017-06-05.
Three most important issues to address in the move towards graduation:
1. Grow the community to involve more users and contributors.
2. Grow more committers to maintain the project.
3.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
N/A
How has the community developed since the last report?
One new committer was elected, more users appeared in mailing list
How has the project developed since the last report?
Several new features including auto completion, get session by name were proposed and under review.
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup
[ ] Working towards first release
[X] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
2017-09-01
When were the last committers or PPMC members elected?
2017-09-18
Signed-off-by:
[x](livy) Bikas Saha
Comments:
[ ](livy) Brock Noland
Comments:
[ ](livy) Luciano Resende
Comments:
[ ](livy) Jean-Baptiste Onofre
Comments:
Livy is web service that exposes a REST interface for managing long running
Apache Spark contexts in your cluster. With Livy, new applications can be
built on top of Apache Spark that require fine grained interaction with many
Spark contexts.
Livy has been incubating since 2017-06-05.
Three most important issues to address in the move towards graduation:
1. Grow more committers to maintain the community
2. Expand the community, be more open to the newcomers
3. Have a regular release cadence
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
N/A
How has the community developed since the last report?
We are seeing nascent activity on the new ASF mailing lists for users.
How has the project developed since the last report?
We released the first Apache release of Livy, and migrated all the assets including JIRA, website to ASF.
One big feature about support shared session across languages was merged.
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup
[ ] Working towards first release
[X] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
2017-09-01
When were the last committers or PPMC members elected?
N/A
Signed-off-by:
[X](livy) Bikas Saha
Comments:
[ ](livy) Brock Noland
Comments:
[ ](livy) Luciano Resende
Comments:
[X](livy) Jean-Baptiste Onofré
Comments:
Livy is web service that exposes a REST interface for managing long running
Apache Spark contexts in your cluster. With Livy, new applications can be
built on top of Apache Spark that require fine grained interaction with many
Spark contexts.
Livy has been incubating since 2017-06-05.
Three most important issues to address in the move towards graduation:
N/A
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
N/A
How has the community developed since the last report?
The community is working on moving the project to Apache.
How has the project developed since the last report?
The community made a big progress moving the project to Apache (https://issues.cloudera.org/projects/LIVY/issues/LIVY-373).
Two new features (Livy Web UI and improve ACL) has merged.
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[X] Initial setup
[X] Working towards first release
[ ] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
N/A
When were the last committers or PPMC members elected?
N/A
Signed-off-by:
[ ](livy) Bikas Saha
Comments:
[ ](livy) Brock Noland
Comments:
[x](livy) Luciano Resende
Comments:
[ ](livy) Jean-Baptiste Onofre
Comments:
Livy is web service that exposes a REST interface for managing long running
Apache Spark contexts in your cluster. With Livy, new applications can be
built on top of Apache Spark that require fine grained interaction with many
Spark contexts.
Livy has been incubating since 2017-06-05.
Three most important issues to address in the move towards graduation:
N/A
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
N/A
How has the community developed since the last report?
The community is working on moving the project to Apache.
How has the project developed since the last report?
N/A
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[X] Initial setup
[ ] Working towards first release
[ ] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
N/A
When were the last committers or PPMC members elected?
N/A
Signed-off-by:
[ ](livy) Bikas Saha
Comments:
[ ](livy) Brock Noland
Comments:
[ ](livy) Luciano Resende
Comments:
[X](livy) Jean-Baptiste Onofre
Comments: