Hi JB - Here is my draft:
Livy Board Report Jan 2023 Livy 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 Cadance 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? Code level maturity is high while the renewed community is ramping up to be able to accept contributions, spin releases and innovate within the project again. Please feel free to add your own commentary. Initial setup Working towards first release Community building Nearing graduation 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? December 2022 Have your mentors been helpful and responsive? No issues with mentors to report. Are things falling through the cracks? If so, please list any open issues that need to be addressed. No issues to report. 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: (livy) Bikas Saha Comments: (livy) Luciano Resende Comments: (livy) Jean-Baptiste Onofré Comments: Discussing with Larry to know who will submit report. It should happen soon. (livy) Madhawa Kasun Gunasekara Comments: (livy) Larry McCay Comments: (livy) Sunil Govindan Comments: IPMC/Shepherd notes: On Sat, Dec 31, 2022 at 5:38 AM Jean-Baptiste Onofré <[email protected]> wrote: > Hi Larry, > > I can do it, or you can start a draft and I can help there, up to you. > > Regards > JB > > On Fri, Dec 30, 2022 at 6:32 PM larry mccay <[email protected]> wrote: > > > > @[email protected] <[email protected]> - I notice that you have done > > these in the past. > > Will you be doing this quarter's report? > > > > Going to be an interesting one given some of the questions in the > template. > > :) > > > > I can take a crack at it if you are not able and obviously will be happy > to > > review and sign off. > > > > On Thu, Dec 29, 2022 at 8:49 PM <[email protected]> wrote: > > > > > Dear podling, > > > > > > This email was sent by an automated system on behalf of the Apache > > > Incubator PMC. It is an initial reminder to give you plenty of time to > > > prepare your quarterly board report. > > > > > > The board meeting is scheduled for Wed, 18 January 2023. > > > The report for your podling will form a part of the Incubator PMC > > > report. The Incubator PMC requires your report to be submitted 2 weeks > > > before the board meeting, to allow sufficient time for review and > > > submission (Wed, January 04). > > > > > > Please submit your report with sufficient time to allow the Incubator > > > PMC, and subsequently board members to review and digest. Again, the > > > very latest you should submit your report is 2 weeks prior to the board > > > meeting. > > > > > > Candidate names should not be made public before people are actually > > > elected, so please do not include the names of potential committers or > > > PPMC members in your report. > > > > > > Thanks, > > > > > > The Apache Incubator PMC > > > > > > Submitting your Report > > > > > > ---------------------- > > > > > > Your report should contain the following: > > > > > > * Your project name > > > * A brief description of your project, which assumes no knowledge of > > > the project or necessarily of its field > > > * A list of the three most important issues to address in the move > > > towards graduation. > > > * Any issues that the Incubator PMC or ASF Board might wish/need to > be > > > aware of > > > * How has the community developed since the last report > > > * How has the project developed since the last report. > > > * How does the podling rate their own maturity. > > > > > > This should be appended to the Incubator Wiki page at: > > > > > > https://cwiki.apache.org/confluence/display/INCUBATOR/January2023 > > > > > > Note: This is manually populated. You may need to wait a little before > > > this page is created from a template. > > > > > > Note: The format of the report has changed to use markdown. > > > > > > Mentors > > > ------- > > > > > > Mentors should review reports for their project(s) and sign them off on > > > the Incubator wiki page. Signing off reports shows that you are > > > following the project - projects that are not signed may raise alarms > > > for the Incubator PMC. > > > > > > Incubator PMC > > > >
