Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 317C5200D0B for ; Wed, 13 Sep 2017 03:34:10 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 30D851609C8; Wed, 13 Sep 2017 01:34:10 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 7A6021609B4 for ; Wed, 13 Sep 2017 03:34:08 +0200 (CEST) Received: (qmail 8262 invoked by uid 500); 13 Sep 2017 01:34:06 -0000 Mailing-List: contact general-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: general@incubator.apache.org Delivered-To: mailing list general@incubator.apache.org Received: (qmail 8244 invoked by uid 99); 13 Sep 2017 01:34:06 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Sep 2017 01:34:06 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id EF6C11A7293 for ; Wed, 13 Sep 2017 01:34:05 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -1.801 X-Spam-Level: X-Spam-Status: No, score=-1.801 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, KAM_ASCII_DIVIDERS=0.8, KAM_NUMSUBJECT=0.5, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-2.8, RCVD_IN_SORBS_SPAM=0.5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd2-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=comcast.net Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id VanFL_Ww6hTM for ; Wed, 13 Sep 2017 01:33:57 +0000 (UTC) Received: from resqmta-ch2-09v.sys.comcast.net (resqmta-ch2-09v.sys.comcast.net [69.252.207.41]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 12F0A5FC1C for ; Wed, 13 Sep 2017 01:33:57 +0000 (UTC) Received: from resomta-ch2-13v.sys.comcast.net ([69.252.207.109]) by resqmta-ch2-09v.sys.comcast.net with ESMTP id rwYddsgj5bvCErwYod4gzH; Wed, 13 Sep 2017 01:33:50 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20161114; t=1505266430; bh=I+H9wXZeidew5UTAY5tLsxsibhkvFEdxOp3dQnW8zYM=; h=Received:Received:From:Content-Type:Mime-Version:Date:Subject: Message-Id:To; b=HSlkmxTI/N6E3OMMYzRNJIEuYWGmLt51yVCmxhvlijF46+QYd33IB/Tb/6dJA9oMi vftQ68qLtt2lv2W5r5a5mvCLb+cXQmocuIn1wUPlarvuTUPJpHGZdH+qMEED1tAmC9 VznPG5j/ZzNol4dcltPko2OzHQNKo75HgoTusVybdzf0LDEzs/IWXp9WbCe5T73sEf +JBlM54bPQB271ViL/Nu3VdgWt7zns45yJ2t6YohBFavXNjH0qRchc52VYH8VBdm6K FjBsRBS2y/+ElPuGIuiSrXFBKl5p349lA9sPdu+X/J/dZAh1RE6I2S5mFZm6Sbgz7J quddCp00406Lg== Received: from [192.168.1.5] ([67.160.241.194]) by resomta-ch2-13v.sys.comcast.net with SMTP id rwYldJEoxZOPRrwYndp8rv; Wed, 13 Sep 2017 01:33:49 +0000 From: Dave Fisher Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (1.0) Date: Tue, 12 Sep 2017 18:33:46 -0700 Subject: Re: [DRAFT] Incubator PMC Board Report - September 2017 Message-Id: References: <78822C73-6422-4DF7-B597-98293466EF2B@comcast.net> In-Reply-To: To: general@incubator.apache.org X-Mailer: iPhone Mail (14G60) X-CMAE-Envelope: MS4wfGntwqfB3IcimlLI7cUxXbZfgyxYhFLaWn3hM8oJpeGNkZ81Zc+S60lf3hdmfEqOgQ4mSeYeVLaca/igS5K1z0eRX8L9ZGRKw3+DZnKrJroVBG6qvtQa 8MQF+AFZTEDop+dHI2QSo21sINsasu5pWYWopg5jEFhTMlZ12qwliR/baN4mrpKsHwd7WSqhGUaeRg== archived-at: Wed, 13 Sep 2017 01:34:10 -0000 Hi - It looks like they are still waiting for the SGA and have only setup mailing= lists. They are not really having discussions yet, but did three non-Apache= releases. A little slow ... Taylor was pushing on the slowness recently on private@ Regards, Dave Sent from my iPhone > On Sep 12, 2017, at 5:24 PM, John D. Ament wrote: >=20 >> On Tue, Sep 12, 2017 at 6:02 PM Dave Fisher wrote= : >>=20 >> Pulsar is now signed off and also shepherd notes done. >>=20 >> Heron is a little slow moving over should we keep them monthly until the >> repos is moved? >>=20 >=20 > Any thoughts on why Heron may be slow moving? I'd like to understand the > problem(s) first before condemning them to monthly reporting. >=20 >=20 >>=20 >> Regards, >> Dave >>=20 >>> On Sep 12, 2017, at 2:40 PM, Dave Fisher wrote: >>>=20 >>> I'll be signing Pulsar shortly. >>>=20 >>> Sent from my iPhone >>>=20 >>>> On Sep 12, 2017, at 2:38 PM, John D. Ament >> wrote: >>>>=20 >>>> All, >>>>=20 >>>> Below please find the revised report. I'm extremely happy to see two o= f >>>> the missing podlings reported. Hopefully we can get the remaining sign= >>>> offs in place (Griffin & Pulsar). Hopefully Spot can file a report as >> well. >>>>=20 >>>> Incubator PMC report for September 2017 >>>>=20 >>>> The Apache Incubator is the entry path into the ASF for projects and >>>> codebases wishing to become part of the Foundation's efforts. >>>>=20 >>>> There are currently 54 podlings incubating. We executed nine podling >>>> releases and have one podling planning to graduate this month. No >> changes >>>> to the PMC structure this month. >>>>=20 >>>> * Community >>>>=20 >>>> New IPMC members: >>>>=20 >>>> - None >>>>=20 >>>> People who left the IPMC: >>>>=20 >>>> - None >>>>=20 >>>> * New Podlings >>>>=20 >>>> - Amaterasu >>>> - Daffodil >>>>=20 >>>> * Podlings that Retired >>>>=20 >>>> - MRQL >>>>=20 >>>> * Podlings that failed to report, expected next month >>>>=20 >>>> - Myriad >>>> - Spot >>>>=20 >>>> * Reports Missing Sign off >>>>=20 >>>> - Griffin >>>> - Pulsar >>>>=20 >>>> * Graduations >>>>=20 >>>> The board has motions for the following: >>>>=20 >>>> - RocketMQ >>>> - Your podling here? >>>>=20 >>>> * Releases >>>>=20 >>>> The following releases entered distribution during the month of >>>> August: >>>>=20 >>>> - 2017-08-01 Apache Juneau 6.3.1 >>>> - 2017-08-01 Apache Tamaya 0.3.0 >>>> - 2017-08-05 Apache Tamaya Extensions 0.3.0 >>>> - 2017-08-08 Apache Pulsar 1.19.0 >>>> - 2017-08-16 Apache HTrace 4.3.0 >>>> - 2017-08-16 Apache Spot 1.0 >>>> - 2017-08-17 Apache Fluo 1.0.0 >>>> - 2017-08-23 Apache S2Graph 0.2.0 >>>> - 2017-08-29 Apache Livy 0.4.0 >>>>=20 >>>> * IP Clearance >>>>=20 >>>>=20 >>>>=20 >>>> * Legal / Trademarks >>>>=20 >>>>=20 >>>>=20 >>>> * Infrastructure >>>>=20 >>>>=20 >>>>=20 >>>> * Miscellaneous >>>>=20 >>>>=20 >>>>=20 >>>> * Credits >>>>=20 >>>> ---------------------------------------------------------------------- >>>> Table of Contents >>>> AriaTosca >>>> Daffodil >>>> Gearpump >>>> Gobblin >>>> Griffin >>>> Heron >>>> Hivemall >>>> HTrace >>>> Livy >>>> Mnemonic >>>> MRQL >>>> Myriad >>>> Omid >>>> OpenWhisk >>>> Pony Mail >>>> Pulsar >>>> Quickstep >>>> SAMOA >>>> SINGA >>>> Spot >>>> Superset >>>> Taverna >>>> Tephra >>>> Trafodion >>>> Wave >>>>=20 >>>> ---------------------------------------------------------------------- >>>>=20 >>>> -------------------- >>>> AriaTosca >>>>=20 >>>> ARIA TOSCA project offers an easily consumable Software Development >> Kit(SDK) >>>> and a Command Line Interface(CLI) to implement TOSCA(Topology and >>>> Orchestration Specification of Cloud Applications) based solutions. >>>>=20 >>>> AriaTosca has been incubating since 2016-08-27. >>>>=20 >>>> Three most important issues to address in the move towards graduation: >>>>=20 >>>> 1. Grow the community and enroll new committers. >>>> 2. Rotate Release Managers for future releases. >>>> 3. >>>>=20 >>>> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be >>>> aware of? >>>>=20 >>>>=20 >>>>=20 >>>> How has the community developed since the last report? >>>>=20 >>>> Seeing some contributions now from independent developers. >>>> Active discussions on mailing lists with potential users and >> contributors. >>>>=20 >>>> How has the project developed since the last report? >>>>=20 >>>> The project has had its first two releases in July 2017 - 0.1 and 0.1.1= >>>>=20 >>>> Important new features have been added: >>>> - Resumable workflows >>>> - Scaling nodes during service creation >>>> - AWS plugin support >>>> - Additional work towards being more TOSCA-compliant (e.g. interface >>>> inputs support) >>>> - Additional usage examples have been added, including ones that use >>>> IaaS plugins (Openstack, AWS), as well as one covering a real-life NFV >>>> use-case (Clearwater example) >>>> - More comprehensive tests, including for documentation generation, and= >>>> parallelization of test suites >>>> - Standardized the release process with automatic shell scripts, >>>> allowing anyone to easily create additional releases for the project >>>> - 64 JIRA issues have been resolved since the last report >>>>=20 >>>> How would you assess the podling's maturity? >>>> Please feel free to add your own commentary. >>>>=20 >>>> [ ] Initial setup >>>> [ ] Working towards first release >>>> [X] Community building >>>> [ ] Nearing graduation >>>> [ ] Other: >>>>=20 >>>> Date of last release: >>>>=20 >>>> July 17, 2017 >>>>=20 >>>> When were the last committers or PPMC members elected? >>>>=20 >>>> Project is still functioning with the initial set of committers. >>>>=20 >>>> Signed-off-by: >>>>=20 >>>> [X](ariatosca) Suneel Marthi >>>> Comments: >>>> [X](ariatosca) John D. Ament >>>> Comments: The project has started to see more community interest. >>>> Need to figure out how to drive development more on list to get more >>>> outside contributions. >>>> [ ](ariatosca) Jakob Homan >>>> Comments: >>>>=20 >>>> IPMC/Shepherd notes: >>>>=20 >>>>=20 >>>>=20 >>>> -------------------- >>>> Daffodil >>>>=20 >>>> Apache Daffodil is an implementation of the Data Format Description >>>> Language (DFDL) used to convert between fixed format data and XML/JSON.= >>>>=20 >>>> Daffodil has been incubating since 2017-08-27. >>>>=20 >>>> Three most important issues to address in the move towards graduation: >>>>=20 >>>> 1. Initial setup (finalize infrastructure setup, get SGAs in place, mov= e >>>> code/documentation/bugs/etc. over to Apache infrastructure, modify >> licenses) >>>> 2. Establish guidelines regarding release cycles, code reviews, bug >>>> management, etc. >>>> 3. Work to grow the community to establish a diversity of backgrounds >> and >>>> expertise >>>>=20 >>>> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be >>>> aware of? >>>>=20 >>>> None >>>>=20 >>>> How has the community developed since the last report? >>>>=20 >>>> N/A >>>>=20 >>>> How has the project developed since the last report? >>>>=20 >>>> N/A >>>>=20 >>>> How would you assess the podling's maturity? >>>> Please feel free to add your own commentary. >>>>=20 >>>> [X] Initial setup >>>> [ ] Working towards first release >>>> [ ] Community building >>>> [ ] Nearing graduation >>>> [ ] Other: >>>>=20 >>>> Date of last release: >>>>=20 >>>> N/A >>>>=20 >>>> When were the last committers or PPMC members elected? >>>>=20 >>>> N/A >>>>=20 >>>> Signed-off-by: >>>>=20 >>>> [X](daffodil) John D. Ament >>>> Comments: >>>> [X](daffodil) David Fisher >>>> Comments: Just starting off. >>>>=20 >>>> IPMC/Shepherd notes: >>>>=20 >>>>=20 >>>>=20 >>>> -------------------- >>>> Gearpump >>>>=20 >>>> Gearpump is a reactive real-time streaming engine based on the >>>> micro-service Actor model. >>>>=20 >>>> Gearpump has been incubating since 2016-03-08. >>>>=20 >>>> Three most important issues to address in the move towards graduation: >>>>=20 >>>> 1. Have frequent release cycles. >>>> 2. Continue to evolve community interest and support. >>>> 3. Increase user adoption. >>>>=20 >>>>=20 >>>> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be >> aware >>>> of? >>>> - None. >>>>=20 >>>>=20 >>>> How has the community developed since the last report? >>>> - Gearpump took part in Google Summer of Code 2017 project and it has >> been >>>> succeffully accompolished by student, Buddhi Ayesha, who is interested >> in >>>> making more contributions beyond the project. >>>>=20 >>>> How has the project developed since the last report? >>>> - 32 issues created and 20 issues resolved. >>>> - Gearpump Runner has been merged into Apache Beam trunk. >>>> - An experimental SQL support has been added and state management is >> under >>>> development. >>>>=20 >>>> How would you assess the podling's maturity? >>>>=20 >>>> [ ] Initial setup >>>> [ ] Working towards first release >>>> [ ] Community building >>>> [ ] Nearing graduation >>>> [ ] Other: >>>>=20 >>>> Date of last release: >>>> 2017-07-17 >>>>=20 >>>>=20 >>>> When were the last committers or PMC members elected? >>>> No new committers or PMC members elected yet. >>>>=20 >>>> Signed-off-by: >>>>=20 >>>> [X](gearpump) Jean-Baptiste Onofr=C3=A9 >>>> Comments: >>>> [ ](gearpump) Andrew Purtell >>>> Comments: >>>> [ ](gearpump) Jarek Jarcec Cecho >>>> Comments: >>>> [ ](gearpump) Reynold Xin >>>> Comments: >>>> [ ](gearpump) Todd Lipcon >>>> Comments: >>>> [ ](gearpump) Xuefu Zhang >>>> Comments: >>>>=20 >>>> IPMC/Shepherd notes: >>>>=20 >>>>=20 >>>> -------------------- >>>> Gobblin >>>>=20 >>>> Gobblin is a distributed data integration framework that simplifies >> common >>>> aspects of big data integration such as data ingestion, replication, >>>> organization and lifecycle management for both streaming and batch data= >>>> ecosystems. >>>>=20 >>>> Gobblin has been incubating since 2017-02-23. >>>>=20 >>>> Three most important issues to address in the move towards graduation: >>>>=20 >>>> 1. Cut our first release >>>>=20 >>>> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be >>>> aware of? >>>>=20 >>>> None >>>>=20 >>>> How has the community developed since the last report? >>>>=20 >>>> * We are working towards our first release. >>>> * Email stats for last month: >>>> user@gobblin.incubator.apache.org : 14 >>>> dev@gobblin.incubator.apache.org : 259 >>>> * There have been 54 Commits in last month: >>>> git log --format=3D'%ci' | grep -cE '2017-0(8)' >>>> * 30 of those commits were by non-committers: >>>> git log --format=3D'%ae %ci' | grep -E '2017-0(8)' | cut -d ' ' -f 1 | >>>> sort | uniq -c | sort -n >>>> * A video conference based meetup happened last month. >>>>=20 >>>> How has the project developed since the last report? >>>>=20 >>>> * Site has been setup. >>>> * Apache wiki has been populated with relevant content. >>>> * Code development is actively being tracked via JIRA / Sprint >> dashboard. >>>>=20 >>>> How would you assess the podling's maturity? >>>>=20 >>>> The podling is working towards its first release. Like last time, >> continued >>>> progress and activity on all fronts. >>>>=20 >>>> [ ] Initial setup >>>> [X] Working towards first release >>>> [X] Community building >>>> [ ] Nearing graduation >>>> [ ] Other: >>>>=20 >>>> Date of last release: >>>>=20 >>>> N/A >>>>=20 >>>> When were the last committers or PPMC members elected? >>>>=20 >>>> N/A >>>>=20 >>>> Signed-off-by: >>>>=20 >>>> [ ](gobblin) Jean-Baptiste Onofr=C3=A9 >>>> Comments: Waiting the board report. I will help/ping. >>>> [X](gobblin) Olivier Lamy >>>> Comments: >>>> [ ](gobblin) Jim Jagielski >>>> Comments: >>>>=20 >>>> IPMC/Shepherd notes: >>>>=20 >>>>=20 >>>>=20 >>>> -------------------- >>>> Griffin >>>>=20 >>>> Griffin is a open source Data Quality solution for distributed data >> systems >>>> at >>>> any scale in both streaming or batch data context >>>>=20 >>>> Griffin has been incubating since 2016-12-05. >>>>=20 >>>> Three most important issues to address in the move towards graduation: >>>>=20 >>>> 1. Continuous development of more dq dimensions for batch and streaming= >>>> mode. >>>> 2. Make the next release. >>>> 3. Grow the community. >>>>=20 >>>> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be >>>> aware of? >>>>=20 >>>> None >>>>=20 >>>> How has the community developed since the last report? >>>>=20 >>>> - Three new contributors on-board, some users had contacted us for use >>>> cases. >>>>=20 >>>> How has the project developed since the last report? >>>> - Active development is moving on well, 83 commits in last three months= . >>>>=20 >>>> - The first release of Griffin has been published. >>>>=20 >>>> - Accuracy measure for streaming mode has been developed. >>>>=20 >>>> - Griffin DSL has been optimized, to support accuracy and profiling >> cases >>>> well. >>>>=20 >>>> - Service module refined API, UI module upgrade to Angular 2. >>>>=20 >>>> - Work toward for next release version (general enough) to support >>>> streaming dq measure end to end. >>>>=20 >>>> How would you assess the podling's maturity? >>>> Please feel free to add your own commentary. >>>>=20 >>>> [ ] Initial setup >>>> [ ] Working towards first release >>>> [X] Community building >>>> [ ] Nearing graduation >>>> [ ] Other: >>>>=20 >>>> Date of last release: >>>>=20 >>>> 2017-07-17 >>>>=20 >>>> When were the last committers or PPMC members elected? >>>>=20 >>>> - Initial set of committers / PPMC. >>>>=20 >>>> Signed-off-by: >>>>=20 >>>> [ ](griffin) Kasper S=C3=B8rensen >>>> Comments: >>>> [ ](griffin) Uma Maheswara Rao Gangumalla >>>> Comments: >>>> [ ](griffin) Luciano Resende >>>> Comments: >>>> [ ](griffin) Henry Saputra >>>> Comments: >>>>=20 >>>> IPMC/Shepherd notes: >>>>=20 >>>>=20 >>>>=20 >>>> -------------------- >>>> Heron >>>>=20 >>>> A real-time, distributed, fault-tolerant stream processing engine. >>>>=20 >>>> Heron has been incubating since 2017-06-23. >>>>=20 >>>> Three most important issues to address in the move towards graduation: >>>>=20 >>>> 1. Finish bootstrapping project, IP clearance, initial website >>>> 2. Expanding the community and adding new committers >>>> 3. 1st ASF release >>>>=20 >>>> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be >>>> aware of? >>>>=20 >>>> None at this time >>>>=20 >>>> How has the community developed since the last report? >>>>=20 >>>> * Some issues encountered with new mailing list signups have been >>>> resolved. >>>> * All initial committers have submitted ICLAs and have gotten their ASF >>>> accounts setup. >>>>=20 >>>> How has the project developed since the last report? >>>>=20 >>>> * The project has made 3 non-Apache releases. >>>>=20 >>>> How would you assess the podling's maturity? >>>> Please feel free to add your own commentary. >>>>=20 >>>> [x] Initial setup >>>> [ ] Working towards first release >>>> [ ] Community building >>>> [ ] Nearing graduation >>>> [ ] Other: >>>>=20 >>>> Date of last release: >>>>=20 >>>> No Apache releases as of yet. Working on code import. >>>>=20 >>>> When were the last committers or PPMC members elected? >>>>=20 >>>> N/A, still bootstrapping the project. >>>>=20 >>>>=20 >>>> Signed-off-by: >>>>=20 >>>> [X](heron) Jake Farrell >>>> Comments: >>>> [ ](heron) Jacques Nadeau >>>> Comments: >>>> [ ](heron) Julien Le Dem >>>> Comments: >>>> [ ](heron) P. Taylor Goetz >>>> Comments: >>>>=20 >>>> IPMC/Shepherd notes: >>>>=20 >>>>=20 >>>>=20 >>>> -------------------- >>>> Hivemall >>>>=20 >>>> Hivemall is a library for machine learning implemented as Hive >>>> UDFs/UDAFs/UDTFs. >>>>=20 >>>> Hivemall has been incubating since 2016-09-13. >>>>=20 >>>> Three most important issues to address in the move towards graduation: >>>>=20 >>>> 1. Create the first Apache release >>>> 2. Community growth (committers and users) >>>> 3. Documentation improvements >>>>=20 >>>> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be >> aware >>>> of? >>>>=20 >>>> None >>>>=20 >>>> How has the community developed since the last report? >>>>=20 >>>> * Got contributions from new external contributors >>>> https://github.com/apache/incubator-hivemall/pull/91 >>>> https://github.com/apache/incubator-hivemall/pull/93 >>>> https://github.com/apache/incubator-hivemall/pull/111 >>>> https://issues.apache.org/jira/browse/HIVEMALL-124 >>>> * Udemy course featuring Hivemal was opened by someone outside PPMC >>>>=20 >>>>=20 >> https://www.udemy.com/new-in-big-data-apache-hivemall-machine-learning-wi= th-sql/ >>>> * Github watchers/stars are gradually increasing: >>>> 99 stars as of Sept 6 (was 79 on May 31) >>>> * Twitter account @ApacheHivemall followers are gradually increasing: >>>> 87 followers as of Sept 6 (was 70 on May 31) >>>>=20 >>>> How has the project developed since the last report? >>>>=20 >>>> * Approaching the first Apache release while the released delayed >>>> from Q2 to Q3 due to delay in merging large patches. >>>> - Waiting for incoming pull requests to review and merge >>>> https://github.com/apache/incubator-hivemall/pulls >>>> - Merging HIVEMALL-24 takes time more than expected >>>> https://github.com/apache/incubator-hivemall/pull/105 >>>> - Blocking issues are decreased >>>> https://issues.apache.org/jira/browse/HIVEMALL-21 >>>>=20 >>>> Since the last report, we have >>>> * In the last 90 days, we opened 29 JIRA issues and closed 21 JIRA >> issues >>>> as seen in https://goo.gl/88Qr11 (as of Sept 6) >>>> Created Resolved >>>> June 2017 7 8 >>>> July 2017 15 12 >>>> Aug 2017 5 0 >>>> Sept 2017 2 1 >>>> * Created 30 Pull Requests and merged 24 Pull Requests between June 01 >>>> and Aug 31. >>>>=20 >>>>=20 >> https://github.com/apache/incubator-hivemall/pulls?q=3Dis%3Apr%20created%= 3A2017-06-01..2017-08-31 >>>>=20 >>>>=20 >> https://github.com/apache/incubator-hivemall/pulls?q=3Dis%3Apr%20closed%3= A2017-06-01..2017-08-31 >>>>=20 >>>> How would you assess the podling's maturity? Please feel free to add >> your >>>> own >>>> commentary. >>>>=20 >>>> [ ] Initial setup >>>> [x] Working towards first release >>>> [x] Community building >>>> [ ] Nearing graduation >>>> [ ] Other: >>>>=20 >>>> Date of last release: >>>>=20 >>>> No release yet >>>> (planning the first Apache release in Q3, 2017) >>>>=20 >>>> When were the last committers or PPMC members elected? >>>>=20 >>>> * June 5: Invited Takuya Kitazawa to PPMC >>>>=20 >>>> Signed-off-by: >>>>=20 >>>> [ ](hivemall) Reynold Xin >>>> Comments: >>>> [X](hivemall) Markus Weimer >>>> Comments: >>>> [ ](hivemall) Xiangrui Meng >>>> Comments: >>>> [ ](hivemall) Daniel Dai >>>> Comments: >>>>=20 >>>> IPMC/Shepherd notes: >>>>=20 >>>>=20 >>>>=20 >>>> -------------------- >>>> HTrace >>>>=20 >>>> HTrace is a tracing framework intended for use with distributed systems= >>>> written in java. >>>>=20 >>>> HTrace has been incubating since 2014-11-11. >>>>=20 >>>> Three most important issues to address in the move towards graduation: >>>>=20 >>>> 1. Continue to grow the Apache HTrace community >>>> 2. Continue to explore projects integrating Apache HTrace >>>> 3. Continue to develop and release stable Apache HTrace incubating >>>> artifacts >>>>=20 >>>> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be >> aware >>>> of? >>>>=20 >>>> In a DISCUSSION thread on our dev list [1], one of us suggested >>>> moving the podling htrace to the attic because of inactivity. >>>>=20 >>>> A healthy back and forth suggested that we are not >>>> dead yet, that we cut back our scope radically, and >>>> that we give it another try before calling it quits. >>>>=20 >>>> 1. https://s.apache.org/9ybr >>>>=20 >>>> How has the community developed since the last report? >>>>=20 >>>> Mailing lists continue quiet (bar the above noted thread). >>>>=20 >>>> How has the project developed since the last report? >>>>=20 >>>> No development. >>>>=20 >>>> How would you assess the podling's maturity? Please feel free to add >> your >>>> own >>>> commentary. >>>>=20 >>>> [ ] Initial setup >>>> [ ] Working towards first release >>>> [x] Community building >>>> [ ] Nearing graduation >>>> [ ] Other: >>>>=20 >>>> Date of last release: >>>>=20 >>>> 2016-10-06 >>>>=20 >>>> When were the last committers or PPMC members elected? >>>>=20 >>>> 2016-10-03 >>>>=20 >>>> Signed-off-by: >>>>=20 >>>> [ ](htrace) Jake Farrell >>>> Comments: >>>> [ ](htrace) Todd Lipcon >>>> Comments: >>>> [x](htrace) Lewis John Mcgibbney >>>> Comments: I think the following comment resonates on the mailing list= >>>> "...A healthy back and forth suggested that we are not dead yet, >>>> that we cut back our scope radically, and that we give it another >>>> try before calling it quits." I think HTrace may have a good >>>> opportunity >>>> to come back to life if the above cut backs are implemented. >>>> [ ](htrace) Andrew Purtell >>>> Comments: >>>> [x](htrace) Billie Rinaldi >>>> Comments: >>>> [X](htrace) Michael Stack >>>> Comments: >>>>=20 >>>> IPMC/Shepherd notes: >>>>=20 >>>>=20 >>>>=20 >>>> -------------------- >>>> Livy >>>>=20 >>>> 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. >>>>=20 >>>> Livy has been incubating since 2017-06-05. >>>>=20 >>>> Three most important issues to address in the move towards graduation: >>>>=20 >>>> 1. Grow more committers to maintain the community >>>> 2. Expand the community, be more open to the newcomers >>>> 3. Have a regular release cadence >>>>=20 >>>> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be >>>> aware of? >>>>=20 >>>> N/A >>>>=20 >>>> How has the community developed since the last report? >>>>=20 >>>> We are seeing nascent activity on the new ASF mailing lists for users. >>>>=20 >>>> How has the project developed since the last report? >>>>=20 >>>> We released the first Apache release of Livy, and migrated all the >> assets >>>> including JIRA, website to ASF. >>>>=20 >>>> One big feature about support shared session across languages was >> merged. >>>>=20 >>>> How would you assess the podling's maturity? >>>> Please feel free to add your own commentary. >>>>=20 >>>> [ ] Initial setup >>>> [ ] Working towards first release >>>> [X] Community building >>>> [ ] Nearing graduation >>>> [ ] Other: >>>>=20 >>>> Date of last release: >>>>=20 >>>> 2017-09-01 >>>>=20 >>>> When were the last committers or PPMC members elected? >>>>=20 >>>> N/A >>>>=20 >>>> Signed-off-by: >>>>=20 >>>> [X](livy) Bikas Saha >>>> Comments: >>>> [ ](livy) Brock Noland >>>> Comments: >>>> [ ](livy) Luciano Resende >>>> Comments: >>>> [X](livy) Jean-Baptiste Onofr=C3=A9 >>>> Comments: >>>>=20 >>>> IPMC/Shepherd notes: >>>>=20 >>>>=20 >>>>=20 >>>> -------------------- >>>> Mnemonic >>>>=20 >>>> Apache Mnemonic is a transparent NVM hybrid memory oriented library >> that has >>>> created Durable Object Model (DOM), Durable Computing Model (DCM) and >>>> Durable Query Model (DQM) >>>> that bring many advantages to significantly improve the performance of >>>> massive real-time data processing/analytics. developers are able to use= >> this >>>> library to design their cache-less, SerDe-less and direct-native >>>> high-performance applications or frameworks. >>>>=20 >>>> Mnemonic has been incubating since 2016-03-03. >>>>=20 >>>> Three most important issues to address in the move towards graduation: >>>>=20 >>>> 1. Have elected new PPMC, Release Manager and committers >>>> 2. Have proposed Durable Query Model (DQM) based on DOM and DCM >>>> 3. Have prepared Apache maturity assessment checklist for review >>>>=20 >>>> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be >>>> aware of? >>>>=20 >>>> Not yet >>>>=20 >>>> How has the community developed since the last report? >>>>=20 >>>> Our last report was in Jun. Since then >>>>=20 >>>> * fulfilled the gaps from graduation >>>> * elected new release manager >>>> * elected new committers >>>> * introduce owner of CQEngine to our community >>>> * some contributors have started to vote for graduation >>>>=20 >>>> How has the project developed since the last report? >>>>=20 >>>> * improved Apache mnemonic official website >>>> * implemented durable query in memory service level >>>> * implemented pure Java volatile memory service >>>> * improved the documentation of project specific release process >>>> * released mnemonic-0.8.0-incubating >>>> * started to vote mnemonic-0.9.0-incubating >>>>=20 >>>> How would you assess the podling's maturity? >>>> Please feel free to add your own commentary. >>>>=20 >>>> [ ] Initial setup >>>> [ ] Working towards first release >>>> [ ] Community building >>>> [X] Nearing graduation >>>> [ ] Other: >>>>=20 >>>> Date of last release: >>>>=20 >>>> 2017-06-23 >>>>=20 >>>> When were the last committers or PPMC members elected? >>>>=20 >>>> Johnu George (PPMC on Aug. 04 2017) >>>> PeiLi Shen (Committer on Aug. 13 2017) >>>>=20 >>>> Signed-off-by: >>>>=20 >>>> [X](mnemonic) Patrick Hunt >>>> Comments: afaict ready to graduate (there is an active DISCUSS thread= >>>> going on now) >>>> [ ](mnemonic) Andrew Purtell >>>> Comments: >>>> [X](mnemonic) James Taylor >>>> Comments: >>>> [ ](mnemonic) Henry Saputra >>>> Comments: >>>>=20 >>>> IPMC/Shepherd notes: >>>>=20 >>>>=20 >>>> -------------------- >>>> Myriad >>>>=20 >>>> IPMC/Shepherd notes: >>>>=20 >>>> johndament: No report from podling. Discussion back in July indicated >>>> the podling did not want to retire and had enough active members to sta= y >>>> alive. No on list activity since then. >>>>=20 >>>> -------------------- >>>> Omid >>>>=20 >>>> Omid is a flexible, reliable, high performant and scalable ACID >>>> transactional >>>> framework that allows client applications to execute transactions on >> top of >>>> MVCC key/value-based NoSQL datastores (currently Apache HBase) providin= g >>>> Snapshot Isolation guarantees on the accessed data. >>>>=20 >>>> Omid has been incubating since 2016-03-28. >>>>=20 >>>> Three most important issues to address in the move towards graduation: >>>>=20 >>>> 1. Boost project dissemination in the Apache community. >>>> 2. Collaborate/integrate Omid with other Apache projects. >>>> 3. Get positive feedback from other projects currently in Apache. >>>>=20 >>>> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be >>>> aware of? >>>>=20 >>>> N/A >>>>=20 >>>> How has the community developed since the last report? >>>>=20 >>>> Started integration with Apache Phoenix >>>>=20 >>>> How has the project developed since the last report? >>>>=20 >>>> Several bugs discovered and fixed. >>>> Continue testing prod environment at Yahoo. >>>> Branch 0.9.0.0 started for next release >>>>=20 >>>> Quarter Stats (from: 2017-03-01 to: 2017-05-31): >>>>=20 >>>>=20 >>>> +---------------------------------------------+ >>>> | Metric | counts | >>>> +---------------------------------------------+ >>>> | # of msgs in dev list | 108 | >>>> | Active Contributors (incl mentors)| 8 | >>>> | Jira New Issues | 6 | >>>> | Resolved Issues | 6 | >>>> | Pull Requests merged | 3 | >>>> | Pull Requests proposed | 3 | >>>> +---------------------------------------------+ >>>>=20 >>>> How would you assess the podling's maturity? >>>> Please feel free to add your own commentary. >>>>=20 >>>> [ ] Initial setup >>>> [ ] Working towards first release >>>> [X] Community building >>>> [ ] Nearing graduation >>>> [ ] Other: >>>>=20 >>>> Date of last release: >>>>=20 >>>> 2016-06-24 >>>>=20 >>>> When were the last committers or PPMC members elected? >>>>=20 >>>>=20 >>>>=20 >>>> Signed-off-by: >>>>=20 >>>> [X](omid) Alan Gates >>>> Comments: Activity continues to be low but there has been a >>>> noticeable uptick since the last report, and there is now a consistent >> if >>>> low level of activity on the project. The big challenge now for Omid >> is to >>>> attract new contributors to the project. >>>> [ ](omid) Lars Hofhansl >>>> Comments: >>>> [ ](omid) Flavio P. Junqueira >>>> Comments: >>>> [ ](omid) Thejas Nair >>>> Comments: >>>> [X](omid) James Taylor >>>> Comments: >>>>=20 >>>> IPMC/Shepherd notes: >>>>=20 >>>> -------------------- >>>> OpenWhisk >>>>=20 >>>> OpenWhisk is an open source, distributed Serverless computing platform >> able >>>> to execute application logic (Actions) in response to events (Triggers)= >>>> from external sources (Feeds) or HTTP requests governed by conditional >>>> logic (Rules). It provides a programming environment supported by a RES= T >>>> API-based Command Line Interface (CLI) along with tooling to support >>>> packaging and catalog services. Additionslly, it now provides options >> to >>>> host the platform components as Docker containers on various Container >>>> Frameworks such as Mesos, Kunernetes, and Compose. >>>> OpenWhisk has been incubating since 2016-11-23. >>>>=20 >>>> Three most important issues to address in the move towards graduation: >>>>=20 >>>>=20 >>>> 1. Est. release process for ZIP of source code >>>> 2. Est. release process for Docker and other platform binaries >>>> 3. Increase additional company and individual Contributors to maintain= >>>> all project repos. >>>>=20 >>>> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be >>>> aware of? >>>>=20 >>>> - It had been our intent to have Apache host our staging (and move it >>>> out of disparate private builds within various companies). However, >> INFRA >>>> indicates they only typically allocate 1 VM per project for use with >> demos >>>> and minor things. They indicated that typically a donation is in order >>>> (ala. Spark). >>>> -- Note: the desire for this staging capability was expressed in the= >>>> Incubator submission where we anticipated needing ~12 VMs to host each >>>> platform component and be able to load balance/schedule Functional code= >> as >>>> part of the OpenWhisk Serverless (across multiple supported language >>>> runtimes). This would also be needed to effectively test >> auto-scaling/load >>>> balancing and container pools and to get accurate performance test >> measures. >>>> - Formal hand-off of OpenWhisk trademark/logo from IBM needs to be >>>> executed; need to identify process for this. >>>>=20 >>>> How has the community developed since the last report? >>>>=20 >>>> - First substantive design changes allowing for Service Provider >>>> Interfaces (SPIs) developed within Apache community (dev list, WIki, >> etc.). >>>> - Established bi-weekly Zoom "Technical Interchange" calls that have >>>> been well received. >>>> Complete videos posted to OW YouTube channel and detailed notes to= >>>> our CWIKI. >>>> - Kubernetes on OpenWhisk work hosted a few ad-hoc to continue design >>>> discussions (CWIKI has designs and comments) >>>> for how best to move away from Ansible deployments to >>>> self-configuring, autoscalable containers (for use in Kube, Mesos, >> Compose, >>>> etc.). >>>> - Increased interest/list/Slack traffic in general due to experiment >>>> Kube work, as it is applicable to Mesos, etc. >>>> - Increased community discussions (design topics, features) of >>>> substance moved to dev list. >>>>=20 >>>> How has the project developed since the last report? >>>>=20 >>>> - incubator-openwhisk Github stars: 1928 >>>> - incubator-openwhisk GitHub forks: 417 >>>> - Movement to become more "pluggable" via Service Provider Interfaces >>>> (SPI), several PRs that are ongoing. >>>> - So far there are now interfaces for MessagingProvider.scala, >>>> ArtifactStoreProvider.scala >>>> and proposals for others such as LogStore, ContainerFactory, >>>> LoadBalancer, >>>>=20 >>>> Sig. PRs: >>>>=20 >>>> - initial work on no root ansible #2669 >>>> This allows to deploy with no sudo/root access. Significant to >>>> enable Kube/Mesos deployments. >>>> - Simplify Spi implementations. #2663 >>>> Service Provider Interfaces (SPI) become more mature as patterns >>>> emerge. >>>> Healthy discussion/growth area for project to allow most >> components >>>> to become (eventually) pluggable >>>> (e.g., Log, Trace, Container build, Load Balancing, Scheduler, >>>> Routing, Message Queue, etc.) >>>> - Apply standard scala formatting #2650 >>>> Coding/linting standards debated/agreed to by community (and CI >>>> automated enforcement encoded) >>>> - Allow multiple controllers and invokers in local environments #2633 >>>> implement a ContainerPool which is completely independent of the >>>> underlying container driver to facilitate testing and extensibility. >>>> More improvements to allow different pooling of invoker containers= >>>> based upon different application use case >>>> (new ideas generated in community) including requirements for >> diff. >>>> scheduling/co-tenanting,/user responsiveness (http), etc. needs. >>>>=20 >>>> Sig. discussions (dev list): >>>>=20 >>>> - Release for OpenWhisk >>>> - Releases and SPI plans >>>> - OpenWhisk shell tool >>>> - authentication models for openwhisk >>>> - Performance tests for OpenWhisk >>>> - Adaption of hosts-files >>>> - Default handling for HTTP web actions >>>>=20 >>>> How would you assess the podling's maturity? Please feel free to add >> your >>>> own commentary. >>>>=20 >>>> [ ] Initial setup >>>> [X] Working towards first release >>>> [X] Community building >>>> [ ] Nearing graduation >>>> [ ] Other: >>>>=20 >>>>=20 >>>> Comments: >>>>=20 >>>> Need greater variety of contributors and contributing companies >>>>=20 >>>> Date of last release: >>>>=20 >>>> N/A >>>>=20 >>>> When were the last committers or PPMC members elected? >>>>=20 >>>> - Tyson Norris, Committer, 08/31/2017 >>>> - James Dubee, PPMC, Committer, 09/05/2017 >>>>=20 >>>> Signed-off-by: >>>>=20 >>>> [ ](openwhisk) Felix Meschberger >>>> Comments: >>>> [ ](openwhisk) Isabel Drost-Fromm >>>> Comments: >>>> [X](openwhisk) Sergio Fern=C3=A1ndez >>>> Comments: >>>>=20 >>>> IPMC/Shepherd notes: >>>>=20 >>>>=20 >>>> -------------------- >>>> Pony Mail >>>>=20 >>>> Pony Mail is a mail-archiving, archive viewing, and interaction service= , >>>> that >>>> can be integrated with many email platforms. >>>>=20 >>>> Pony Mail has been incubating since 2016-05-27. >>>>=20 >>>> Three most important issues to address in the move towards graduation: >>>>=20 >>>> 1. Work on the next release (0.10) >>>> 2. Work on expanding the community, be more open to newcomers >>>> 3. Resolve design strategies >>>>=20 >>>> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be >>>> aware of? >>>>=20 >>>> None that I am aware of. >>>>=20 >>>> How has the community developed since the last report? >>>>=20 >>>> No major development. A few more bug reports from outside contributors >>>> have been filed. >>>>=20 >>>> How has the project developed since the last report? >>>>=20 >>>> Work continues towards the next release, 0.10, which should be >>>> ready for a vote soon. >>>>=20 >>>> How would you assess the podling's maturity? >>>>=20 >>>> The podling is somewhat mature, but it is my assessment that >>>> more people are needed for it to be a fully viable community. >>>>=20 >>>> Please feel free to add your own commentary. >>>>=20 >>>> [X] Initial setup >>>> [X] Working towards first release >>>> [?] Community building >>>> [ ] Nearing graduation >>>> [ ] Other: >>>>=20 >>>> Date of last release: >>>>=20 >>>> 2016-08-02 >>>>=20 >>>> When were the last committers or PPMC members elected? >>>>=20 >>>> sebb as PMC, 2017-04-17. >>>> No new committers as of late. >>>>=20 >>>> Signed-off-by: >>>>=20 >>>> [ ](ponymail) Andrew Bayer >>>> Comments: >>>> [X](ponymail) John D. Ament >>>> Comments: >>>>=20 >>>> IPMC/Shepherd notes: >>>>=20 >>>>=20 >>>>=20 >>>> -------------------- >>>> Pulsar >>>>=20 >>>> Pulsar is a highly scalable, low latency messaging platform running on >>>> commodity hardware. It provides simple pub-sub semantics over topics, >>>> guaranteed at-least-once delivery of messages, automatic cursor >> management >>>> for >>>> subscribers, and cross-datacenter replication. >>>>=20 >>>> Pulsar has been incubating since 2017-06-01. >>>>=20 >>>> Three most important issues to address in the move towards graduation: >>>>=20 >>>> 1. Grow the community with new Committers/PPMC members. >>>> 2. Set up a test cluster to be able to run system tests >>>> 3. Improve release process by having more committers taking part in >>>> releases >>>>=20 >>>> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be >>>> aware of? >>>>=20 >>>> None >>>>=20 >>>> How has the community developed since the last report? >>>>=20 >>>> The community added 2 contributors. There is a healthy discuss on issue= s >>>> related >>>> to development, tools and processes among the community members. >>>>=20 >>>>=20 >>>> How has the project developed since the last report? >>>>=20 >>>> 8 authors have pushed 69 commits to master in the last 30 days. >>>> The project has made the first release from the Apache Incubator on >> August >>>> 9th. >>>> The next release is planned for mid-September. Several design documents= >>>> with >>>> improvement proposals have been submitted to the wiki and discussed in >> the >>>> mailing list. >>>>=20 >>>> How would you assess the podling's maturity? >>>> Please feel free to add your own commentary. >>>>=20 >>>> [ ] Initial setup >>>> [ ] Working towards first release >>>> [X] Community building >>>> [ ] Nearing graduation >>>> [ ] Other: >>>>=20 >>>> Date of last release: >>>>=20 >>>> 2017-08-09, 1.19.0-incubating >>>>=20 >>>> When were the last committers or PPMC members elected? >>>>=20 >>>> >>>>=20 >>>> Signed-off-by: >>>>=20 >>>> [ ](pulsar) Dave Fisher >>>> Comments: >>>> [ ](pulsar) Jim Jagielski >>>> Comments: >>>> [ ](pulsar) P. Taylor Goetz >>>> Comments: >>>> [ ](pulsar) Francis Liu >>>> Comments: >>>>=20 >>>> IPMC/Shepherd notes: >>>>=20 >>>>=20 >>>>=20 >>>> -------------------- >>>> Quickstep >>>>=20 >>>> Quickstep is a high-performance database engine. >>>>=20 >>>> Quickstep has been incubating since 2016-03-29. >>>>=20 >>>> Three most important issues to address in the move towards graduation: >>>>=20 >>>> 1. Building a Quickstep community >>>> 2. More adoption of the Quickstep technology >>>> 3. More releases >>>>=20 >>>> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be >>>> aware of? >>>>=20 >>>> None >>>>=20 >>>>=20 >>>> How has the community developed since the last report? >>>>=20 >>>> In the summer of 2017, we took efforts to spread awareness about the >>>> Quickstep project and technology. We had many talks, particularly in >>>> the San Francisco Bay Area. The talks/venues are listed here: >>>>=20 >>>> 1. SRI International in Menlo Park >>>> 2. A meetup hosted by H2O.ai in Mountain View >>>> 3. Hortonworks in Santa Clara (Thanks to our mentor Julian Hyde >>>> for hosting) >>>>=20 >>>> We had also applied for a talk at BigDataWisconsin meetup but the >>>> proposal was not selected. >>>>=20 >>>> How has the project developed since the last report? >>>>=20 >>>> During the summer, the development activity was slow. There are >>>> ongoing efforts to build a distributed version of Quickstep. >>>>=20 >>>>=20 >>>> How would you assess the podling's maturity? >>>> Please feel free to add your own commentary. >>>>=20 >>>> [ ] Initial setup >>>> [ ] Working towards first release >>>> [x] Community building >>>> [ ] Nearing graduation >>>> [ ] Other: >>>>=20 >>>> Date of last release: >>>>=20 >>>> 2017-03-25 >>>>=20 >>>> When were the last committers or PPMC members elected? >>>>=20 >>>> 2017-05-12 Tianrun Lee (committer) >>>>=20 >>>> Signed-off-by: >>>>=20 >>>> [ ](quickstep) Konstantin Boudnik >>>> Comments: >>>> [x](quickstep) Julian Hyde >>>> Comments: >>>> Community building remains the project's biggest challenge. >>>> The project has been putting considerable effort into talks >>>> and I hope this effort starts to pay off. >>>> [ ](quickstep) Roman Shaposhnik >>>> Comments: >>>>=20 >>>> IPMC/Shepherd notes: >>>>=20 >>>>=20 >>>>=20 >>>> -------------------- >>>> SAMOA >>>>=20 >>>> SAMOA provides a collection of distributed streaming algorithms for the= >> most >>>> common data mining and machine learning tasks such as classification, >>>> clustering, and regression, as well as programming abstractions to >> develop >>>> new >>>> algorithms that run on top of distributed stream processing engines >> (DSPEs). >>>> It features a pluggable architecture that allows it to run on several >> DSPEs >>>> such as Apache Storm, Apache Flink, and Apache Samza. >>>>=20 >>>> SAMOA has been incubating since 2014-12-15. >>>>=20 >>>> Three most important issues to address in the move towards graduation: >>>>=20 >>>> 1. Elect new PPMC members >>>> 2. Enlarge the community >>>> 3. >>>>=20 >>>> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be >>>> aware of? >>>>=20 >>>> None >>>>=20 >>>> How has the community developed since the last report? >>>>=20 >>>> Mailing list activity (June 2017 - August 2017): >>>> * @dev: 120 messages >>>>=20 >>>> Jira issues backlog (June 2017 - August 2017): >>>> * Created: 4 >>>> * Resolved: 5 >>>>=20 >>>> We saw the engagement of new contributors, who are plausible candidates= >>>> for the PPMC. >>>>=20 >>>> How has the project developed since the last report? >>>>=20 >>>> * Planning a new release in the next month. Work on the release was >>>> delayed due to summer holidays for most of the contributors. >>>>=20 >>>> * Integrated Apache Kafka support and support for JSON and Avro. >>>>=20 >>>> * Developed a new Boosting algorithm that will be integrated shortly. >>>>=20 >>>> * Integrated new version of the SAMOA instances. >>>>=20 >>>> * Integrated ability to store predictions on disk. >>>>=20 >>>>=20 >>>> How would you assess the podling's maturity? >>>> Please feel free to add your own commentary. >>>>=20 >>>> [ ] Initial setup >>>> [ ] Working towards first release >>>> [X] Community building >>>> [ ] Nearing graduation >>>> [ ] Other: >>>>=20 >>>> Date of last release: >>>>=20 >>>> 2016-09-30 >>>>=20 >>>> When were the last committers or PPMC members elected? >>>>=20 >>>> None >>>>=20 >>>>=20 >>>> Signed-off-by: >>>>=20 >>>> [X](samoa) Alan Gates >>>> Comments: >>>> [ ](samoa) Ashutosh Chauhan >>>> Comments: >>>> [ ](samoa) Enis Soztutar >>>> Comments: >>>> [ ](samoa) Ted Dunning >>>> Comments: >>>>=20 >>>> IPMC/Shepherd notes: >>>>=20 >>>>=20 >>>>=20 >>>> -------------------- >>>> SINGA >>>>=20 >>>> SINGA is a distributed deep learning platform. >>>>=20 >>>> SINGA has been incubating since 2015-03-17. >>>>=20 >>>> Three most important issues to address in the move towards graduation: >>>>=20 >>>> 1. Prepare all documentations and go through the graduation voting >>>> process. >>>> 2. >>>> 3. >>>>=20 >>>> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be >>>> aware of? >>>>=20 >>>> N/A >>>>=20 >>>>=20 >>>> How has the community developed since the last report? >>>>=20 >>>> A new committer (moaz) has been added into SINGA. >>>>=20 >>>>=20 >>>> How has the project developed since the last report? >>>>=20 >>>> 1. We extended SINGA Python support from Py2 to Py3. >>>> 2. We added CPack to generate debian packages for SINGA >>>> 3. Several example models (VGG and InceptionV3/V4) were added. >>>> 4. A couple of bugs were fixed and the documentation was updated. >>>>=20 >>>> How would you assess the podling's maturity? >>>> Please feel free to add your own commentary. >>>>=20 >>>> [ ] Initial setup >>>> [ ] Working towards first release >>>> [ ] Community building >>>> [X] Nearing graduation >>>> [ ] Other: >>>>=20 >>>> Date of last release: >>>>=20 >>>> 2017-12-02 >>>>=20 >>>> When were the last committers or PPMC members elected? >>>>=20 >>>> 2017-29-08 >>>>=20 >>>> Signed-off-by: >>>>=20 >>>> [ ](singa) Daniel Dai >>>> Comments: >>>> [X](singa) Alan Gates >>>> Comments: >>>> [ ](singa) Ted Dunning >>>> Comments: >>>> [ ](singa) Thejas Nair >>>> Comments: >>>>=20 >>>> IPMC/Shepherd notes: >>>>=20 >>>>=20 >>>>=20 >>>> -------------------- >>>> Spot >>>>=20 >>>> Apache Spot is a platform for network telemetry built on an open data >> model >>>> and Apache Hadoop. >>>>=20 >>>> Spot has been incubating since 2016-09-23. >>>>=20 >>>> Three most important issues to address in the move towards graduation: >>>>=20 >>>> 1. >>>> 2. >>>> 3. >>>>=20 >>>> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be >>>> aware of? >>>>=20 >>>>=20 >>>>=20 >>>> How has the community developed since the last report? >>>>=20 >>>>=20 >>>>=20 >>>> How has the project developed since the last report? >>>>=20 >>>>=20 >>>> How would you assess the podling's maturity? >>>> Please feel free to add your own commentary. >>>>=20 >>>> [ ] Initial setup >>>> [ ] Working towards first release >>>> [ ] Community building >>>> [ ] Nearing graduation >>>> [ ] Other: >>>>=20 >>>> Date of last release: >>>>=20 >>>> XXXX-XX-XX >>>>=20 >>>> When were the last committers or PPMC members elected? >>>>=20 >>>>=20 >>>>=20 >>>> Signed-off-by: >>>>=20 >>>> [ ](spot) Jarek Jarcec Cecho >>>> Comments: >>>> [ ](spot) Brock Noland >>>> Comments: >>>> [ ](spot) Andrei Savu >>>> Comments: >>>> [ ](spot) Uma Maheswara Rao G >>>> Comments: >>>>=20 >>>> IPMC/Shepherd notes: >>>>=20 >>>> - Drew Farris (shepherd): No mentor activity apparent from the mailing >>>> lists, >>>> ongoing project activity observed. >>>>=20 >>>> -------------------- >>>> Superset >>>>=20 >>>> Superset is an enterprise-ready web application for data exploration, >> data >>>> visualization and dashboarding. >>>>=20 >>>> Superset has been incubating since 2017-05-21. >>>>=20 >>>> Three most important issues to address in the move towards graduation: >>>>=20 >>>> 1. Address the challenge that React is no longer allowed in Apache >>>> projects >>>> 2. Grow the community and enroll new committers. >>>> 3. Plan and execute our first Apache release >>>>=20 >>>> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be >>>> aware of? >>>> * Superset is heavily reliant upon React, but React is no longer >> allowed in >>>> ASF projects ( >>>>=20 >> https://code.facebook.com/posts/112130496157735/explaining-react-s-licens= e/ >> ). >>>> We are currently evaluating Preact as an alternative. ( >>>> https://github.com/apache/incubator-superset/pull/3355) >>>>=20 >>>> How has the community developed since the last report? >>>> * Grace Guo and Riccardo Magliocchetti have been elected as Superset >>>> Committers >>>> * Organic growth of our Github contributors (160), forks (2,338), >> watchers >>>> (829) and stars (15,807) >>>>=20 >>>> How has the project developed since the last report? >>>> * We have completed all of the items on the Apache Incubation Checklist= >>>> * We have a healthy, constant flow of bug fixes, quality improvements >> and >>>> new features. Take a look at the project=E2=80=99s Pulse on Github for m= ore >> details >>>>=20 >>>> How would you assess the podling's maturity? >>>> Please feel free to add your own commentary. >>>>=20 >>>> [ ] Initial setup >>>> [X] Working towards first release >>>> [ ] Community building >>>> [ ] Nearing graduation >>>> [ ] Other: >>>>=20 >>>> Date of last release: >>>> * No official release yet since being voted into Apache >>>> Incubation. (Planning for the first Apache release in Q4, 2017) >>>>=20 >>>> When were the last committers or PPMC members elected? >>>> Grace Guo and Riccardo Magliocchetti were both elected on August 17, >> 2017 >>>>=20 >>>> Signed-off-by: >>>>=20 >>>> [X](superset) Ashutosh Chauhan >>>> Comments: >>>> [X](superset) Luke Han >>>> Comments: >>>> [ ](superset) Jim Jagielski >>>> Comments: >>>>=20 >>>> IPMC/Shepherd notes: >>>>=20 >>>>=20 >>>>=20 >>>> -------------------- >>>> Taverna >>>>=20 >>>> Taverna is a domain-independent suite of tools used to design and >> execute >>>> data-driven workflows. >>>>=20 >>>> Taverna has been incubating since 2014-10-20. >>>>=20 >>>> Three most important issues to address in the move towards graduation: >>>>=20 >>>> 1. Complete the remaining IP review (by retiring irrelevant git >>>> repositories) >>>> 2. Re-engage PMC to encourage regular activity >>>> 3. Graduate! >>>>=20 >>>> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be >>>> aware of? >>>>=20 >>>>=20 >>>>=20 >>>> How has the community developed since the last report? >>>>=20 >>>> Fairly quiet over the summer. Lack of progress towards graduation. Need= >>>> more active drive. >>>>=20 >>>> Email stats since 2017-07-01: >>>>=20 >>>> dev@taverna: 74 emails >>>> users@taverna: 4 emails >>>>=20 >>>>=20 >>>> How has the project developed since the last report? >>>>=20 >>>> Progress towards release of the Taverna Mobile Android App. >>>> Been in contact with legal/infra to figure out how to do code signing >> for >>>> Google Play store. >>>>=20 >>>>=20 >>>> How would you assess the podling's maturity? >>>> Please feel free to add your own commentary. >>>>=20 >>>> [ ] Initial setup >>>> [ ] Working towards first release >>>> [ ] Community building >>>> [x] Nearing graduation >>>> [ ] Other: >>>>=20 >>>> Date of last release: >>>>=20 >>>> 2016-07-01 >>>>=20 >>>> When were the last committers or PPMC members elected? >>>>=20 >>>> 2016-10-20 >>>>=20 >>>>=20 >>>> Signed-off-by: >>>>=20 >>>> [ ](taverna) Andy Seaborne >>>> Comments: >>>> [ ](taverna) Daniel J Debrunner >>>> Comments: >>>> [ ](taverna) Marlon Pierce >>>> Comments: >>>> [x](taverna) Stian Soiland-Reyes >>>> Comments: Mailing list has gone very quiet >>>> [ ](taverna) Suresh Marru >>>> Comments: >>>> [ ](taverna) Suresh Srinivas >>>> Comments: >>>>=20 >>>> IPMC/Shepherd notes: >>>>=20 >>>>=20 >>>>=20 >>>> -------------------- >>>> Tephra >>>>=20 >>>> Tephra is a system for providing globally consistent transactions on >> top of >>>> Apache HBase and other storage engines. >>>>=20 >>>> Tephra has been incubating since 2016-03-07. >>>>=20 >>>> Two most important issues to address in the move towards graduation: >>>>=20 >>>> 1. Improve community engagement >>>> 2. Increase adoption >>>>=20 >>>> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be >>>> aware of? >>>>=20 >>>> - None at this time. >>>>=20 >>>> How has the community developed since the last report? >>>>=20 >>>> - 1 new subscriber in dev mailing list since the last report >>>> - 16 new JIRAs filed since the last report >>>> - 2 external contributors submitted patches since the last report >>>> - 4 external contributor created a ticket in JIRA since the last report= >>>>=20 >>>> How has the project developed since the last report? >>>>=20 >>>> - Working on 0.13.0-incubating release >>>>=20 >>>> How would you assess the podling's maturity? >>>> Please feel free to add your own commentary. >>>>=20 >>>> [ ] Initial setup >>>> [ ] Working towards first release >>>> [x] Community building >>>> [ ] Nearing graduation >>>> [ ] Other: >>>>=20 >>>> Date of the last release: >>>>=20 >>>> 2017-05-30 >>>>=20 >>>> When were the last committers or PMC members elected? >>>>=20 >>>> - None since coming to incubation >>>>=20 >>>> Signed-off-by: >>>>=20 >>>> [X](tephra) Alan Gates >>>> Comments: >>>> [ ](tephra) Andrew Purtell >>>> Comments: >>>> [X](tephra) James Taylor >>>> Comments: >>>> [ ](tephra) Lars Hofhansl >>>> Comments: >>>>=20 >>>> IPMC/Shepherd notes: >>>>=20 >>>>=20 >>>>=20 >>>> -------------------- >>>> Trafodion >>>>=20 >>>> Apache Trafodion is a webscale SQL-on-Hadoop solution enabling >>>> transactional >>>> or operational workloads on Hadoop. Trafodion builds on the scalability= , >>>> elasticity, and flexibility of Hadoop. Trafodion extends Hadoop to >> provide >>>> guaranteed transactional integrity, enabling new kinds of big data >>>> applications to run on Hadoop. >>>>=20 >>>> Trafodion has been incubating since 2015-05-24. >>>>=20 >>>> Three most important issues to address in the move towards graduation: >>>>=20 >>>> 1. Develop the community and continue to grow the diversity. >>>> 2. Continue the momentum and become more integrated with the >>>> rest of the Apache community. >>>> 3. Continue to create software releases. >>>>=20 >>>> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be >> aware >>>> of? >>>>=20 >>>> * Two of our three remaining mentors, Devaraj Das and Enis S=C3=B6ztuta= r, >>>> resigned >>>> on July 21. >>>>=20 >>>> How has the community developed since the last report? >>>>=20 >>>> * Participation in the project remains healthy, with the usual small di= p >>>> due to the summer vacation season: >>>> - ML postings: 106 user, 273 dev, 389 coderev, 734 issues, 341 commits >>>> - Twitter: 221 followers, 72 tweets, 67 likes >>>> * We are working towards our next release, 2.2. Ming Liu is the Release= >>>> Manager. >>>> * Discussion regarding readiness to graduate continues. Diversity >> continues >>>> to grow. >>>>=20 >>>> How has the project developed since the last report? >>>>=20 >>>> * 162 commits from 18 contributors. >>>> * 100 JIRAs filed and 63 resolved. >>>>=20 >>>> How would you assess the podling's maturity? Please feel free to add >> your >>>> own >>>> commentary. >>>>=20 >>>> [ ] Initial setup >>>> [ ] Working towards first release >>>> [X] Community building >>>> [X] Nearing graduation >>>> [ ] Other: >>>>=20 >>>> Date of last release: >>>>=20 >>>> 2017-05-01 2.1 >>>>=20 >>>> When were the last committers or PMC members elected? >>>>=20 >>>> 2017-03-10 >>>>=20 >>>> Signed-off-by: >>>>=20 >>>> [x](trafodion) Michael Stack >>>> Comments: >>>>=20 >>>> IPMC/Shepherd notes: >>>>=20 >>>>=20 >>>>=20 >>>> -------------------- >>>> Wave >>>>=20 >>>> A wave is a hosted, live, concurrent data structure for rich >> communication. >>>> It >>>> can be used like email, chat, or a document. >>>>=20 >>>> Wave has been incubating since 2010-12-04. >>>>=20 >>>> Three most important issues to address in the move towards graduation: >>>>=20 >>>> 1. Appoint members of the PMC >>>> 2. Update release procedure >>>> 3. >>>>=20 >>>> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be >> aware >>>> of? >>>>=20 >>>> None >>>>=20 >>>> How has the community developed since the last report? >>>>=20 >>>> There were no relevant events regarding the community in this period. >>>>=20 >>>> How has the project developed since the last report? >>>>=20 >>>> Some members of community work on side projects - like UI improvements,= >>>> but overall we had a low level of activity. >>>>=20 >>>> How would you assess the podling's maturity? Please feel free to add >> your >>>> own commentary. >>>>=20 >>>> [ ] Initial setup >>>> [ ] Working towards first release >>>> [ ] Community building >>>> [X] Nearing graduation >>>> [ ] Other: >>>>=20 >>>> Date of last release: >>>>=20 >>>> March 2016 >>>>=20 >>>> When were the last committers or PPMC members elected? >>>>=20 >>>> March 2017 >>>>=20 >>>> Signed-off-by: >>>>=20 >>>> [X](wave) John D. Ament >>>> Comments: Reached out to get the dates fixed up. In order to >>>> graduate, we have to figure out how to get more activity. >>>> [ ](wave) Upayavira >>>> Comments: >>>>=20 >>>> IPMC/Shepherd notes: >>>>=20 >>>> Drew Farris (shepherd): Two mentors active. Light activity on the >>>> project in >>>> general, some discussion towards graduation a couple months back. >>>=20 >>=20 >>=20 --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org For additional commands, e-mail: general-help@incubator.apache.org