What the board has decided about this committee or office, and the reports it filed, most recent first. Generated from the published minutes.
These categorised views are best effort. They are read from the published minutes by a program, and what it can attribute to a committee depends on how each resolution happens to be worded — so a page may be incomplete, and nothing here overrides the minutes themselves. The raw minutes are the source of truth.
Please note. The board approves the minutes of a meeting at the meeting after it, and they are published then - so the most recent meeting is not usually here. ASF Members can read the draft in the board's own repository until it is.
[raw] the published minutes, which are the record. [main index]
| Date | Action | Decided by |
|---|---|---|
| 2026-05-20 | Appointed Jean-Baptiste Onofré | the board, by resolution |
| Date | Decision | Item | Outcome |
|---|---|---|---|
| 2026-05-20 | Establish the Apache Livy Project | special order | approved |
## Description: The mission of Apache Livy is the creation and maintenance of software related to 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 ## Project Status: Current project status: Ongoing, second month as a Top-Level Project Issues for the board: No ## Membership Data: Apache Livy was founded 2026-05-20 (2 months ago) There are currently 25 committers and 21 PMC members in this project. The Committer-to-PMC ratio is roughly 7:6. Community changes, past quarter: - No new PMC members (project graduated recently). - No new committers were added. ## Project Activity: Releases: We are still working on the first TLP release. It should happen soon. Development: Spark 3.5.x support: merged prior to / around graduation. Spark 4.x support work started. JDK 17 support PR has been merged. Migration from reload4j to log4j2 SASL/TLS support in Zookeeper Post-graduation infrastructure migration: The migration off the incubator namespace has been done. The website, mailing lists, git, Jira references migration is now complete. ## Community Health: We are still chasing several PMC members who are not following the private@/dev@ mailing lists. Now that the resources "post graduation" have been migrated, we will start to focus on the community expansion and promote the project.
# Description Apache Livy is a service that enables easy interaction with an Apache Spark cluster over a REST interface. It supports easy submission of Spark jobs or snippets of Spark code, synchronous or asynchronous result retrieval, as well as Spark Context management, all via a simple REST interface or an RPC client library. Apache Livy also simplifies the interaction between Spark and application servers, thus enabling the use of Spark for interactive web/mobile applications. # Project Status Current project status: Ongoing (first report as Top-Level Project) Issues for the board: none # Membership Data Apache Livy graduated from the Apache Incubator on 2026-06-04 (incubating since 2017-06-05). There are currently 25 committers and 21 PMC members in this project. The Committer-to-PMC ratio is roughly 5:4. Community changes, past quarter: Initial PMC and committer roster established at graduation from the Apache Incubator. # Project Activity - Apache Livy 0.9.0-incubating was released on 2026-01-09: this was the final release made during the incubation period, providing Spark 3.x support (Spark 3.0+ required) and binary distributions for Scala 2.11 and 2.12. - The graduation resolution was submitted to the board by JB Onofré following a successful IPMC vote (7 binding +1, 1 non-binding +1). - Apache Livy is now a Top-Level Project, announced by the ASF on 2026-06-04. - The PMC is planning the first TLP (1.0) release to remove the -incubating suffix from artifact names and align the release infrastructure with TLP requirements. Discussion is ongoing on the dev@ mailing list. # Community Health - The dev@ and user@ mailing lists are active with discussions around the post-graduation release roadmap and ongoing user support. - The PMC is working on updating the project website and documentation to reflect TLP status. - Repository migration from apache/incubator-livy to apache/livy is in progress. - The community is focused on growing the contributor base beyond the existing incubation community now that the project has full TLP visibility.
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 unfinished issues to address before graduating: 1. Revitalization of the Community 2. Dependable Release Cadence 3. Keep the project up to date with security fixes and in terms of Spark support ### Are there any issues that the IPMC or ASF Board need to be aware of? None at this time. ### How has the community developed since the last report? New mailing list activity around project graduation. Automatic closure of inactive PRs was implemented to help clean up abandoned PRs. ### How has the project developed since the last report? A new release is available and some new fixes and improvements are merged for the upcoming 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 - [X] Nearing graduation - [ ] Other: ### Date of last release: 2026-02-11 ### When were the last committers or PPMC members elected? October 2023 ### Have your mentors been helpful and responsive? Yes ### Is the PPMC managing the podling's brand / trademarks? No answer ### Signed-off-by: - [ ] (livy) Bikas Saha Comments: - [ ] (livy) Luciano Resende Comments: - [X] (livy) Jean-Baptiste Onofré Comments: Clearly Livy is ready to graduate. Discussion started. - [ ] (livy) Madhawa Kasun Gunasekara Comments: - [ ] (livy) Larry McCay Comments: - [X] (livy) Gyorgy Gal 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 unfinished issues to address before graduating: 1. Revitalization of the Community 2. Dependable Release Cadence 3. Keep the project up to date with security fixes and in terms of Spark support ### Are there any issues that the IPMC or ASF Board need to be aware of? None at this time. Currently working on releasing a new version, RC voting will be restarted in a few days. ### How has the community developed since the last report? We have received PRs and merged several PRs, dev mailing list is more active. ### How has the project developed since the last report? PRs merged including JDK 17 upgrade, Spark 2 and Python 2 decommission. New release branch and RC has been created. ### 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 - [X] Nearing graduation - [ ] Other: ### Date of last release: 2023-10-10 ### When were the last committers or PPMC members elected? October 2023 ### Have your mentors been helpful and responsive? Yes ### Is the PPMC managing the podling's brand / trademarks? No answer ### Signed-off-by: - [ ] (livy) Bikas Saha Comments: - [ ] (livy) Luciano Resende Comments: - [X] (livy) Jean-Baptiste Onofré Comments: I think it's worth to start discussion graduation. - [ ] (livy) Madhawa Kasun Gunasekara Comments: - [ ] (livy) Larry McCay Comments: - [X] (livy) Gyorgy Gal 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 unfinished issues to address before graduating:
1. Revitalization of the Community
2. Dependable Release Cadence
3. Keep the project up to date with security fixes and in terms of Spark
support
### Are there any issues that the IPMC or ASF Board need to be aware of?
None at this time. There was a ping of the PPMC to make sure there were
enough folks monitoring the pivate@ list which resulted in 5 +1's and a
couple 0's.
### How has the community developed since the last report?
We have received PRs and merged the upgrade to Spark 3.5.
### How has the project developed since the last report?
The PR to support for the latest Spark 3.5.x has been merged. A new PR is
raised to support JDK17. We are preparing a new version that we may need
help with.
### 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
- [X] Nearing graduation
- [ ] Other:
### Date of last release:
2023-10-10
### When were the last committers or PPMC members elected?
October 2023
### Have your mentors been helpful and responsive?
Yes.
### Is the PPMC managing the podling's brand / trademarks?
No answer
### Signed-off-by:
- [ ] (livy) Bikas Saha
Comments:
- [ ] (livy) Luciano Resende
Comments:
- [X] (livy) Jean-Baptiste Onofré
Comments: I think we should move forward on a discussion about
graduation.
- [ ] (livy) Madhawa Kasun Gunasekara
Comments:
- [ ] (livy) Larry McCay
Comments:
- [X] (livy) Gyorgy Gal
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 unfinished issues to address before graduating: 1. Revitalization of the Community 2. Dependable Release Cadence 3. Keep the project up to date with security fixes and in terms of Spark support ### Are there any issues that the IPMC or ASF Board need to be aware of? None at this time. There was a recent ping of the PPMC to make sure there were enough folks monitoring the pivate@ list which resulted in 5 +1's and a couple 0's. ### How has the community developed since the last report? We have received PRs and merged mostly bug fixes and smaller enhancements. ### How has the project developed since the last report? A new PR for the upcoming release is support for the latest Spark 3.5.x has been submitted and is currently waiting for reviews. We will need to spin up the next release within this next quarter. ### 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: 2023-10-10 ### When were the last committers or PPMC members elected? October 2023 ### Have your mentors been helpful and responsive? Yes ### Is the PPMC managing the podling's brand / trademarks? No answer ### Signed-off-by: - [ ] (livy) Bikas Saha Comments: - [ ] (livy) Luciano Resende Comments: - [X] (livy) Jean-Baptiste Onofré Comments: I think it would be great to have a kind of roadmap about releases (0.8.0-incubating is two years old) and community growth (blog post, ...). - [ ] (livy) Madhawa Kasun Gunasekara Comments: - [X] (livy) Larry McCay Comments: - [X] (livy) György Gál 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 unfinished issues to address before graduating: 1. Revitalization of the Community 2. Dependable Release Cadence 3. Keep the project up to date with security fixes and in terms of Spark support ### Are there any issues that the IPMC or ASF Board need to be aware of? None ### How has the community developed since the last report? We have received a number of PRs and merged mostly bug fixes and smaller enhancements. Kubernetes support has also been added which is a major new feature. ### How has the project developed since the last report? Kubernetes support has been added as a major deliverable for the next release. Another feature we are working on to add in the upcoming release is support for the latest Spark 3.5. ### 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: 2023-10-10 ### When were the last committers or PPMC members elected? October 2023 ### Have your mentors been helpful and responsive? Yes ### Is the PPMC managing the podling's brand / trademarks? No answer ### Signed-off-by: - [ ] (livy) Bikas Saha Comments: - [ ] (livy) Luciano Resende Comments: - [X] (livy) Jean-Baptiste Onofré Comments: I think it would be great to have a kind of roadmap about releases (0.8.0-incubating is two years old) and community growth (blog post, ...). - [ ] (livy) Madhawa Kasun Gunasekara Comments: - [X] (livy) Larry McCay Comments: - [X] (livy) György Gál 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 unfinished issues to address before graduating: 1. Revitalization of the Community 2. Dependable Release Cadence 3. Focus on Contributors rather than primarily on Users (Docs for processes) ### Are there any issues that the IPMC or ASF Board need to be aware of? None ### How has the community developed since the last report? There have been a number of PRs from the community and some activity on the mailing lists. The overall activity is still rather low as to be expected with a mature project even if a podling. Activity should pick up again as we begin to plan our next release. ### How has the project developed since the last report? There have been minor improvements and bug fixes. Most activity would be considered maintenance during this period. Again, once we start the plan for the next release, I believe activity will pick up. ### 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: 2023-10-10 ### When were the last committers or PPMC members elected? October 2023 ### Have your mentors been helpful and responsive? No answer. ### Is the PPMC managing the podling's brand / trademarks? No answer. ### Signed-off-by: - [ ] (livy) Bikas Saha Comments: - [ ] (livy) Luciano Resende Comments: - [X] (livy) Jean-Baptiste Onofré Comments: Great to see new potential contributors joining the Slack channel and mailing list :) - [ ] (livy) Madhawa Kasun Gunasekara Comments: - [X] (livy) Larry McCay 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 unfinished issues to address before graduating: 1. Revitalization of the Community 2. Dependable Release Cadence 3. Focus on Contributors rather than primarily on Users (Docs for processes) ### Are there any issues that the IPMC or ASF Board need to be aware of? None ### How has the community developed since the last report? New PPMC, committers and contributors have emerged through the 0.8.0 release effort. Focus on security fixes and CI processes in github as well as reviews and merges of contributions from other contributors have been most active. 0.8.0 Release was security and bug fix oriented with CVEs and log4j being a lot of the recent work but with meaningful features as well. ### How has the project developed since the last report? Apache Livy 0.8.0 was released and addressed the previously stated goals of security and log4j related fixes as well as numerous improvements and features from the community that were long awaited due to lack of community and recently added. ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [X] Initial setup - [X] Working towards first release (with revitalized community) - [X] Community building - [ ] Nearing graduation - [X] Other: Nearing graduation in code stability but with a re-emerging a dev community supporting it and working toward 0.8.0 release ### Date of last release: 2023-10-10 ### When were the last committers or PPMC members elected? October 2023 ### Have your mentors been helpful and responsive? No issues with mentors to report. ### Is the PPMC managing the podling's brand / trademarks? No issues to report. Signed-off-by: - [ ] (livy) Bikas Saha Comments: - [ ] (livy) Luciano Resende Comments: - [X] (livy) Jean-Baptiste Onofré Comments: The activity has restarted, mostly maintenance. I think we can have new features and improvements soon, helping to extend the community. - [ ] (livy) Madhawa Kasun Gunasekara Comments: - [X] (livy) Larry McCay Comments: - [ ] (livy) Sunil Govindan 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 unfinished issues to address before graduating: 1. Get 0.8.0 release out and release process clearly documented 2. More community engagement 3. ### Are there any issues that the IPMC or ASF Board need to be aware of? None at this time. ### How has the community developed since the last report? The community has been growing with new ### How has the project developed since the last report? ### How would you assess the podling's maturity? Please feel free to add your own commentary.contributors and - [ ] Initial setup - [ ] Working towards first release - [ ] Community building - [ ] Nearing graduation - [ ] Other: ### Date of last release: 2021-02-04 ### When were the last committers or PPMC members elected? 2023-02-10 ### Have your mentors been helpful and responsive? No issues at the moment. ### Is the PPMC managing the podling's brand / trademarks? No answer. ### Signed-off-by: - [ ] (livy) Bikas Saha Comments: - [ ] (livy) Luciano Resende Comments: - [ ] (livy) Jean-Baptiste Onofré Comments: - [ ] (livy) Madhawa Kasun Gunasekara Comments: - [X] (livy) Larry McCay 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 unfinished issues to address before graduating: 1. Revitalization of the Community 2. Dependable Release Cadence 3. Focus on Contributors rather than primarily on Users (Docs for processes) ### Are there any issues that the IPMC or ASF Board need to be aware of? None ### How has the community developed since the last report? New PPMC, committers and contributors have been working towards the 0.8.0 release goals. Focus on security fixes and CI processes in github as well as reviews and merges of contributions from other contributors have been most active. ### How has the project developed since the last report? log4j remediation is underway and nearly complete Numerous dependency related CVEs have been addressed. A number of bug and improvements patches have been merged. 0.8.0 release will be ready in coming weeks. ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [X] Initial setup - [X] Working towards first release (with revitalized community) - [X] Community building - [ ] Nearing graduation - [X] Other: Nearing graduation in code stability but with a re-emerging a dev community supporting it and working toward 0.8.0 release ### Date of last release: 2021-02-02 ### When were the last committers or PPMC members elected? December 2022 ### Have your mentors been helpful and responsive? No issues with mentors to report. ### Is the PPMC managing the podling's brand / trademarks? No issues to report. Signed-off-by: - [ ] (livy) Bikas Saha Comments: - [ ] (livy) Luciano Resende Comments: - [X] (livy) Jean-Baptiste Onofré Comments: The activity has restarted, mostly maintenance. I think we can have new features and improvements soon, helping to extend the community. - [ ] (livy) Madhawa Kasun Gunasekara Comments: - [X] (livy) Larry McCay Comments: - [ ] (livy) Sunil Govindan 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 unfinished issues to address before graduating: 1. Revitalization of the Community 2. Dependable Release Cadence 3. Focus on Contributors rather than primarily on Users (Docs for processes) ### Are there any issues that the IPMC or ASF Board need to be aware of? None ### How has the community developed since the last report? A proposal to revitalize the PPMC and committers was accepted and execution has begun. A number of new mentors and committers have been added to the Livy podling. ### How has the project developed since the last report? An initial strategic direction was part of the proposal and details the steps toward the iniital from the new community and the migration of innovations from the external forks back into the project. A set of JIRAs have been identified for the next release (0.8.0) which consist of low hanging fruit from previously stranded pull requests, meta tasks for empowering contributors and CVE remediation process and tasks. ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [ ] Initial setup - [ ] Working towards first release - [ ] Community building - [ ] Nearing graduation - [X] Other: Nearing graduation in code stability but without a dev community supporting it, the devs have moved to working on forks due to lack of PPMC availability. Dev community is emerging and working toward an 0.8.0 release. ### Date of last release: 2021-02-02 ### When were the last committers or PPMC members elected? December 2022 ### Have your mentors been helpful and responsive? No issues with mentors to report. ### Is the PPMC managing the podling's brand / trademarks? No issues to report. ### Signed-off-by: - [ ] (livy) Bikas Saha Comments: - [ ] (livy) Luciano Resende Comments: - [X] (livy) Jean-Baptiste Onofré Comments: The activity has restarted, mostly maintenance. I think we can have new features and improvements soon, helping to extend the community. - [ ] (livy) Madhawa Kasun Gunasekara Comments: - [X] (livy) Larry McCay Comments: - [ ] (livy) Sunil Govindan 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 unfinished issues to address before graduating:
1. Reinvigorate project with new committers and PPMC
2. Update support to latest Spark
3. Revitalize the community
### Are there any issues that the IPMC or ASF Board need to be aware of?
There is a proposal on the incubator email lists to revitalize the Livy
project around an updated set of goals with the addition of new mentors,
PPMCs, and committers.
As the PPMC has seemed to have moved on, Jean-Baptiste Onofre and
Alex Bozarth are the only members "active" on the private list and Alex
has stated he does not have bandwidth to work on Livy currently, there
is not a quorum available to vote on the proposal. As such we would like
the IPMC to aid in passing the proposal to revitalize the project.
### How has the community developed since the last report?
The community has been stagnant outside of the above proposal
### How has the project developed since the last report?
There has been no development due to a lack of active PPMC/committers
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [ ] Working towards first release
- [ ] Community building
- [ ] Nearing graduation
- [X] Other: Nearing graduation in code stability but without a dev
community supporting it, the devs have moved to working on forks
due to lack of PPMC availability
### Date of last release:
2021-02-02
### When were the last committers or PPMC members elected?
2019-01-22
### Have your mentors been helpful and responsive?
No answer.
### Is the PPMC managing the podling's brand / trademarks?
No answer.
### Signed-off-by:
- [ ] (livy) Bikas Saha
Comments:
- [X] (livy) Luciano Resende
Comments:
- [X] (livy) Jean-Baptiste Onofré
Comments: Livy "new" community bring the podling back to live. It's
on the way.
### 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 unfinished issues to address before graduating: 1. Cut a new release 2. Fill maturity matrix 3. Discuss about graduation ### Are there any issues that the IPMC or ASF Board need to be aware of? No real issue, the podling is mature, and I think we can discuss about graduation. ### How has the community developed since the last report? Several messages have been seen showing an interest for the podling. ### How has the project developed since the last report? Not a lot of activity as the podling is mature. ### 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 - [X] Nearing graduation - [ ] Other: ### Date of last release: Not provided. ### When were the last committers or PPMC members elected? ### Have your mentors been helpful and responsive? No answer. ### Is the PPMC managing the podling's brand / trademarks? No answer. ### Signed-off-by: - [X] (livy) Bikas Saha Comments: - [ ] (livy) Luciano Resende Comments: - [X] (livy) Jean-Baptiste Onofré Comments: I think the podling (in term of features) is mature, so, moving forward to new release and graduation would make sense. ### IPMC/Shepherd notes: Justin Mclean : Please make sure to provide all information asked for in the report.
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 unfinished issues to address before graduating: 1. Decision to graduate or retire 2. 3. ### Are there any issues that the IPMC or ASF Board need to be aware of? The project is stable and being used for its desired purpose by a many organizations and users. Without any pressing need for new features there is no active development happening. If the project retires then its unclear how users would be able to get security fixes like the one that got release in Feb 21. Seeking the boards guidance on this situation. ### How has the community developed since the last report? Community is quiet with some user activity. ### How has the project developed since the last report? We have new users, but the dev community activity is pretty low. ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [ ] Initial setup - [ ] Working towards first release - [ ] Community building - [ ] Nearing graduation - [X] Other: ### Date of last release: Feb 3 2021 ### When were the last committers or PPMC members elected? ### Have your mentors been helpful and responsive? Are things falling through the cracks? If so, please list any open issues that need to be addressed. ### Is the PPMC managing the podling's brand / trademarks? Are 3rd parties respecting and correctly using the podlings name and brand? If not what actions has the PPMC taken to correct this? Has the VP, Brand approved the project name? ### Signed-off-by: - [X] (livy) Bikas Saha Comments: - [ ] (livy) Luciano Resende Comments: - [X] (livy) Jean-Baptiste Onofré Comments: I've been in touch with some potential new users/contributors. ### IPMC/Shepherd notes: Justin Mclean: I'm not sure why that question is directed at the board and I'm not sure they could answer it. IMO It would depend on if the project continues development or not outside of Apache and how that group of people handle security.
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 unfinished issues to address before graduating: 1. Start preparing towards graduation 2. 3. ### Are there any issues that the IPMC or ASF Board need to be aware of? Apache Livy is a stable project that is used widely in conjuction with Apache Spark. It seems to have met its project goals and there is not much active development going on as a result. 2020 may definitely not be the best year for community activity and Livy certainly seems to have taken a hit on this aspect. Seeking guidance from the IPMC/Board on what could be next steps for the project. Its not very active but at the same time its not a defunct/unused project. ### How has the community developed since the last report? ### How has the project developed since the last report? ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [ ] Initial setup - [ ] Working towards first release - [ ] Community building - [X] Nearing graduation - [ ] Other: ### Date of last release: 2020-01-07 ### When were the last committers or PPMC members elected? 2019-01-22 ### Have your mentors been helpful and responsive? No reply ### Is the PPMC managing the podling's brand / trademarks? No Reply ### Signed-off-by: - [X] (livy) Bikas Saha Comments: - [X] (livy) Luciano Resende Comments: - [ ] (livy) Jean-Baptiste Onofre Comments: ### IPMC/Shepherd notes: Justin Mclean: As long as there is an active PPMC with at last 3 PPMC members providing oversight the project should be fine. Is anything else needed to graduate the project? Have you looked at the ASF maturity model? I am concerned that users questions are going unanswered on the dev list.
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 unfinished issues to address before graduating: 1. Start preparing towards graduation 2. 3. ### Are there any issues that the IPMC or ASF Board need to be aware of? None ### How has the community developed since the last report? Moderate activity on mailing lists and code as well ### How has the project developed since the last report? Currently the community is working on HA feature and support for Spark on Kubernetes. Spark 3.0 support was added recently and a new release will be started once it has been more thought tested ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [ ] Initial setup - [ ] Working towards first release - [ ] Community building - [X] Nearing graduation - [ ] Other: ### Date of last release: 2020-01-07 ### When were the last committers or PPMC members elected? 2019-01-22 ### Have your mentors been helpful and responsive? Yes ### Is the PPMC managing the podling's brand / trademarks? Yes ### Signed-off-by: - [ ] (livy) Bikas Saha Comments: - [ ] (livy) Brock Noland Comments: - [X] (livy) Luciano Resende Comments: - [ ] (livy) Jean-Baptiste Onofre Comments: Still planning to contribute what I proposed on the mailing list while ago. I think we are pretty close to graduation. Maybe worth to start a discussion. ### 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 unfinished issues to address before graduating: 1. Start preparing towards graduation 2. 3. ### Are there any issues that the IPMC or ASF Board need to be aware of? None ### How has the community developed since the last report? Moderate activity on mailing lists and code as well ### How has the project developed since the last report? 0.7.0 was released. Currently the community is working on HA feature and support for Spark on Kubernetes. ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [ ] Initial setup - [ ] Working towards first release - [ ] Community building - [X] Nearing graduation - [ ] Other: ### Date of last release: 2020-01-07 ### When were the last committers or PPMC members elected? 2019-01-22 ### Have your mentors been helpful and responsive? Yes ### Is the PPMC managing the podling's brand / trademarks? Yes ### Signed-off-by: - [X] (livy) Bikas Saha Comments: - [ ] (livy) Brock Noland Comments: - [X] (livy) Luciano Resende Comments: - [X] (livy) Jean-Baptiste Onofre Comments: Still planning to contribute what I proposed on the mailing list while ago. I think we are pretty close to graduation. Maybe worth to start a discussion. ### 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 unfinished issues to address before graduating: 1. Grow the community to get more reviews and content. However, at this point, the community might want to consider that it is a stable project that has met its initial functional goals. With multiple public releases under its belt, it might be worth discussing a time to graduate. A substantial increase in community activity in terms of code contribution and related community growth might occur after a new set of functionality/scope is identified for the project. But to date, the existing community and code are following the Apache way. 2. 3. ### Are there any issues that the IPMC or ASF Board need to be aware of? None ### How has the community developed since the last report? Moderate activity on mailing lists and code ### How has the project developed since the last report? Livy thrift JDBC part is GA now. Currently the community is working on HA feature. And 0.7.0 release is ongoing. ### 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 - [x] Nearing graduation - [ ] Other: ### Date of last release: 2019-04-01 ### When were the last committers or PPMC members elected? 2019-01-22 ### Have your mentors been helpful and responsive? Yes ### Is the PPMC managing the podling's brand / trademarks? Yes ### Signed-off-by: - [ ] (livy) Bikas Saha Comments: - [ ] (livy) Brock Noland Comments: - [X] (livy) Luciano Resende Comments: - [X] (livy) Jean-Baptiste Onofre Comments: Still planning to contribute what I proposed on the mailing list while ago ### IPMC/Shepherd notes:
Livy is a service for managing long running Apache Spark contexts in your cluster. It exposes both a REST interface and a JDBC server. 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 unfinished issues to address before graduating: 1. Grow the community to get more reviews and content. However, at this point, the community might want to consider that it is a stable project that has met its initial functional goals. With multiple public releases under its belt, it might be worth discussing a time to graduate. A substantial increase in community activity in terms of code contribution and related community growth might occur after a new set of functionality/scope is identified for the project. But to date, the existing community and code are following the Apache way. 2. 3. ### Are there any issues that the IPMC or ASF Board need to be aware of? None ### How has the community developed since the last report? Moderate activity on mailing lists and code ### How has the project developed since the last report? Working on feature development and bug fix, planning to have a 0.7.0 release this year. ### 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: 2019-04-01 ### When were the last committers or PPMC members elected? 2019-01-22 ### Have your mentors been helpful and responsive? Yes. ### Signed-off-by: - [X] (livy) Bikas Saha Comments: Worthwhile to consider a discussion on graduation. - [ ] (livy) Brock Noland Comments: - [X] (livy) Luciano Resende Comments: - [X] (livy) Jean-Baptiste Onofre Comments: Maybe it's time to concretely move forward on graduation. ### 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 unfinished issues to address before graduating: 1. Grow the community to get more reviews and content 2. Improve the code quality and expand its scope 3. Get more content ### Are there any issues that the IPMC or ASF Board need to be aware of? None ### How has the community developed since the last report? There're not so many activities since the last report. But we do saw some new contributors were start working on this project. ### How has the project developed since the last report? Working on feature development and bug fix, planning to hive a 0.7.0 release this year. ### 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: 2019-04-01 ### When were the last committers or PPMC members elected? 2019-01-22 ### Have your mentors been helpful and responsive? Yes. Are things falling through the cracks? If so, please list any open issues that need to be addressed. ### Signed-off-by: - [ ] (livy) Bikas Saha Comments: - [ ] (livy) Brock Noland Comments: - [x] (livy) Luciano Resende Comments: - [ ] (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. 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? The user email list has kept a consistent flow of discussion around the project. How has the project developed since the last report? Version 0.6 was released How would you assess the podling's maturity? Mailing lists and project development follow the Apache way. The user community is active but lately the rate of change in the project code is lower. This may not be a cause for concern since it might indicate relative maturity in achieving the desired functionality of the project. [ ] Initial setup [ ] Working towards first release [x] Community building [ ] Nearing graduation [ ] Other: Date of last release: 2019-04-02 When were the last committers or PPMC members elected? 2019-01-22 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. Our mentors are regularly quick to respond on the dev list when addressed. Signed-off-by: [x](livy) Bikas Saha Comments: [ ](livy) Brock Noland Comments: [x](livy) Luciano Resende Comments: [X](livy) Jean-Baptiste Onofre Comments: IPMC/Shepherd notes: Justin Mclean: Asked the podling to provide more detail.
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:
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
support is being added for Apache Spark 2.4 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-06
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
IPMC/Shepherd notes:
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
support is being added for Apache Spark 2.4 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-06
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
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 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: