Lets see if we get any specific guidance from the Board based on the report.
Bikas ________________________________ From: Alex Bozarth <ajboz...@us.ibm.com> Sent: Tuesday, October 1, 2019 3:28 PM To: dev@livy.incubator.apache.org <dev@livy.incubator.apache.org> Subject: RE: Podling Report Reminder - October 2019 I agree based on the stability of the community over the past year that discussing a potential graduation has merit. Alex Bozarth Software Engineer Center for Open-Source Data & AI Technologies ________________________________ E-mail: ajboz...@us.ibm.com<mailto:ajboz...@us.ibm.com> GitHub: github.com/ajbozarth<https://github.com/ajbozarth> 505 Howard Street San Francisco, CA 94105 United States [Inactive hide details for Bikas Saha ---09/30/2019 08:18:38 PM---Hi, The issue seems to have resolved itself. Coming to why I s]Bikas Saha ---09/30/2019 08:18:38 PM---Hi, The issue seems to have resolved itself. Coming to why I started the edit. From: Bikas Saha <bi...@apache.org> To: "dev@livy.incubator.apache.org" <dev@livy.incubator.apache.org> Date: 09/30/2019 08:18 PM Subject: [EXTERNAL] Re: Podling Report Reminder - October 2019 ________________________________ Hi, The issue seems to have resolved itself. Coming to why I started the edit. Please see my note under the Livy section so that we can discuss if it makes sense or not. https://cwiki.apache.org/confluence/display/INCUBATOR/October2019#three-most-important-unfinished-issues-to-address-before-graduating-7 Essentially, IMO, I see the Apache Livy community and code practices following the tenets of the Apache way. The community also has multiple public releases following due process. There has been addition of new contributors and committers based on their participation. Based on that I feel we could start a conversation on whether the project is ready to graduate. There is no doubt that the code and community activity is not as voluminous as some of the larger projects like Apache Hadoop or Spark. But those projects also have a significantly larger scope in terms of features/functionality compared to Livy. So it may be that, as of now, Apache Livy is a stable project that meets its intended scope. Thus its ok for it to have moderate code and community activity until such time as new scope/features are identified which would spurt the next wave of high activity. With the above context, does it make sense to discuss whether the project is ready to graduate with its current (relative small) community. Thoughts? Bikas ________________________________ From: Jean-Baptiste Onofré <j...@nanthrax.net> Sent: Sunday, September 22, 2019 10:31 PM To: dev@livy.incubator.apache.org <dev@livy.incubator.apache.org> Subject: Re: Podling Report Reminder - October 2019 Hi, it works fine for me. Regards JB On 22/09/2019 18:47, Bikas Saha wrote: > Hi, > > I noticed the wiki page said this wiki has been enabled with LDAP and login > with Apache credentials. I did and it logged me in but reported an error on > every link saying I don't have permissions. Anyone else hitting this issue? > > Bikas > > ________________________________ > From: jmcl...@apache.org <jmcl...@apache.org> > Sent: Sunday, September 22, 2019 3:46 AM > To: dev@livy.incubator.apache.org <dev@livy.incubator.apache.org> > Subject: Podling Report Reminder - October 2019 > > 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, 16 October 2019, 10:30 am PDT. > 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, October 02). > > 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/October2019 > > 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 > -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com
