+1. Jarcec
> On Feb 25, 2016, at 1:41 PM, Mike Percy <[email protected]> wrote: > > +1 > > Thanks for writing it up, Todd. > > Mike > > On Thu, Feb 25, 2016 at 11:17 PM, Todd Lipcon <[email protected]> wrote: > >> Here's a draft. I might update the numbers later this weekend and see >> if our commit/mailing list stats look more like January. Otherwise let >> me know if there's any edits you think we should make before posting. >> >> ----- >> Kudu >> >> Kudu is a distributed columnar storage engine built for the Apache Hadoop >> ecosystem. >> >> Kudu has been incubating since 2015-12-03. >> >> Three most important issues to address in the move towards graduation: >> >> 1. Build a more diverse developer and user community >> 2. Migrate our web site under apache.org >> 3. Continue to make regular Apache releases >> >> 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? >> >> - In February, we only received one patch from a new contributor (3 total >> from >> non-committers). We're continuing to focus on building a more diverse >> developer community. >> >> Although recruiting new contributors to Kudu itself have been slow, we >> had >> community members report beginnings of a Presto integration, an Apache >> Flume >> sink, and Rust language bindings. We are considering whether it makes >> sense >> to develop these things within the Kudu project or external locations. >> >> - Overall development velocity continues to be pretty good: 86 patches >> committed >> since the last report, representing about 3kloc of new code and >> 3kloc of changes. >> This is slightly down from last month, as we spent a bit more time on >> managing >> our first release and fixing bugs rather than adding new features. >> >> Dev list traffic is also slightly reduced from January, likely due >> to a similar >> reason (898 messages so far vs 1144 in Jan). >> >> - Community members continue to give public talks about Kudu at various >> conferences and meetups. Talks were delivered at conferences or meetups >> in >> Tokyo (x2), Sunnyvale, Krakow, San Francisco (x2), and Seattle. More are >> planned for March. >> >> We are also encouraged that at least two Kudu meetup talks were delivered >> by new members of the community outside the core development team. We >> hope >> to see the "grassroots community" trend continue. >> >> - The public Kudu Slack channel continues to be popular. It has grown from >> 116 members last month to 144 this month. Discussion between users and >> devs is quite active, with daily participation from a global community >> (USA, China, Poland, Japan, et al). Many users seem to prefer this method >> over the traditional user mailing list. >> >> >> How has the project developed since the last report? >> >> Since the last report, we've accomplished the following milestones: >> >> - We successfully migrated our issue tracking to the Apache JIRA. Special >> thanks to Gavin on the infra team and Mike Percy on the Kudu project for >> hard >> work on this transition. >> >> - We cleaned up our license documentation and successfully published our >> first official release as an incubating project (0.7.0)! >> >> >> Date of last release: >> >> Feb 25, 2016: Apache Kudu 0.7.0-incubating >> >> When were the last committers or PMC members elected? >> >> None since initial incubation. >> >> On Thu, Feb 25, 2016 at 11:21 AM, Todd Lipcon <[email protected]> wrote: >>> Time flies by, and another podling report is due next week. Since this >>> is our third report on the monthly cadence, I think we move to a >>> quarterly reporting cadence after this one. >>> >>> I'll write up an initial draft again and post to the list for commentary. >>> >>> -Todd >>> >>> ---------- Forwarded message ---------- >>> From: Marvin Humphrey <[email protected]> >>> Date: Thu, Feb 25, 2016 at 11:13 AM >>> Subject: March 2016 Report >>> To: [email protected] >>> >>> >>> Greetings, {podling} developers! >>> >>> This is a reminder that your report is due next Wednesday, March >>> 2nd. Details below. >>> >>> Best, >>> >>> Marvin Humphrey, Report Manager for March, on behalf of the >>> Incubator PMC >>> >>> --------------- >>> >>> 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 March 2016, 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, March 2nd). >>> >>> 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. >>> >>> 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. >>> >>> This should be appended to the Incubator Wiki page at: >>> >>> http://wiki.apache.org/incubator/March2016 >>> >>> Note: This is manually populated. You may need to wait a little before >>> this page is created from a template. >>> >>> 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 >>> >>> -- >>> Todd Lipcon >>> Software Engineer, Cloudera >> >> >> >> -- >> Todd Lipcon >> Software Engineer, Cloudera >>
