The final version of the report has been submitted - https://wiki.apache.org/incubator/October2017
On Fri, Oct 13, 2017 at 1:52 PM John D. Ament <johndam...@apache.org> wrote: > All, > > I plan to submit the below report to the board tomorrow, barring any major > changes to the contents. I have removed the completely non reporting > podlings (Gossip, Myriad), but left in the two that reported without sign > off (BatchEE, Milagro). I hope that their mentors can review. Thank you > to everyone else for your diligence in getting the contents together. > > John > > ------- > > Incubator PMC report for October 2017 > > The Apache Incubator is the entry path into the ASF for projects and > codebases wishing to become part of the Foundation's efforts. > > There are currently 54 podlings incubating. Podlings executed seven > releases last month. Two new IPMC members joined our fold and one new > podling joined. We presently have two or three podlings preparing to > graduate this month. > > * Community > > New IPMC members: > > - Davor Bonaci > - Jacques Le Roux > > * New Podlings > > - PageSpeed > > * Podlings that failed to report, expected next month > > - BatchEE (report filed, not signed off by mentors) > - Gossip > - Milagro (report filed, not signed off by mentors) > - Myriad > > * Graduations > > The board has motions for the following: > > - Mnemonic > - PredictionIO > - Juneau > > * Releases > > The following releases entered distribution during the month of > September: > > - 2017-09-04 Apache Airflow 1.8.2 > - 2017-09-05 Apache MXNet 0.11.0 > - 2017-09-13 Apache Impala 2.10.0 > - 2017-09-13 Apache Mnemonic 0.9.0 > - 2017-09-21 Apache Tephra 0.13.0 > - 2017-09-27 Apache PredictionIO 0.12.0 > - 2017-09-29 Apache Unomi 1.2.0 > > * Legal / Trademarks > > - Multiple podlings have pending requests in to legal to clarify SGAs, > ICLAs. Prompt responses would be appreciated. > > * Infrastructure > > - A change to the mlreq process caused delays in creation of mailing > lists for PageSpeed. Work is on going to migrate to a new process for > these requests that is agreeable for IPMC members to execute on. > > ---------------------------------------------------------------------- > Table of Contents > Airflow > Amaterasu > Annotator > BatchEE > Daffodil > DataFu > FreeMarker > Gobblin > Gossip > HAWQ > Heron > Juneau > Livy > Milagro > MXNet > Myriad > NetBeans > ODF Toolkit > Rya > SensSoft > Spot > Traffic Control > Weex > > ---------------------------------------------------------------------- > > -------------------- > Airflow > > Airflow is a workflow automation and scheduling system that can be used to > author and manage data pipelines. > > Airflow has been incubating since 2016-03-31. > > Three most important issues to address in the move towards graduation: > > 1. We are working on our 4th apache release 1.9.0 and are getting better > at releases > 2. > 3. > > 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? > 1. We had our third official release 1.8.2 on Aug 7th 2017. > 2. Since our last podling report 3 months ago (i.e. between July > 5 & Sept 25, inclusive), we grew our contributors from 280 to 315 > 4. Since our last podling report 3 months ago (i.e. between July > 5 & Sept 25, inclusive), we resolved 167 pull requests (currently at > 1797 closed > PRs) > 5. Since being accepted into the incubator, the number of companies > officially using Apache Airflow has risen from 30 to 114, 16 new from > the last podling report. > > > > How has the project developed since the last report? > See above : 167 PR resolved, 35 new contributors, & 16 new companies > officially using it. > > > 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: > > 2017-08-07 > > When were the last committers or PPMC members elected? > > 2017-01-01 fokko a.k.a Fokko Driespong (committer/PMC) > > Signed-off-by: > > [ ](airflow) Chris Nauroth > Comments: > [x](airflow) Hitesh Shah > Comments: > [ ](airflow) Jakob Homan > Comments: > > IPMC/Shepherd notes: > A quick look at this month's email and it looks like Airflow is ready to > graduate. > Dave Fisher > > -------------------- > Amaterasu > > Apache Amaterasu is a framework providing continuous deployment for Big > Data > pipelines. > > Amaterasu has been incubating since 2017-09-07. > > It provides the following capabilities: > > Continuous integration tools to package pipelines and run tests. > A repository to store those packaged applications: the applications > repository. > A repository to store the pipelines, and engine configuration (for > instance, location of the Spark master, etc.): per environment - the > configuration repository. > A dashboard to monitor the pipelines. > A DSL and integration hooks allowing third parties to easily integrate. > > Amaterasu has been incubating since 2017-09. > > Three most important issues to address in the move towards graduation: > > 1. Prepare first release > 2. Grow up user and contributor communities > 3. Prepare documentation > > 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? > > * Talks have been given in different events to promote and give > visibility to Amaterasu > > How has the project developed since the last report? > > * Resources creation is in progress (website, Jira, git & github mirror, > ...) > * The code donation is in preparation (rename packages, check legal, ...) > * The website has been published and is online. > > Date of last release: > > N/A > > When were the last committers or PMC members elected? > > N/A > > Signed-off-by: > > [X](amaterasu) Jean-Baptiste Onofré > Comments: > [X](amaterasu) Davor Bonaci > Comments: Completing code donation and moving development to Apache > repository is the next step. > [ ](amaterasu) Olivier Lamy > Comments: > > IPMC/Shepherd notes: > > - Drew Farris (shepherd): Still in project setup phrase, one mentor > observed active on mailing list. > > -------------------- > Annotator > > Annotator provides annotation enabling code for browsers, servers, and > humans. > > Annotator has been incubating since 2016-08-30. > > Three most important issues to address in the move towards graduation: > > 1. Release initial versions > 2. Add active contributors > 3. Demonstrate good governance through voting on process improvements. > > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be > aware of? > > None at this time. > > > How has the community developed since the last report? > > Community has been pretty stable, with a trickle of new stars, forks, > and watchers on the GitHub repo. Committers and other interested parties > have made plans to meet in person over the next month and to work on > contributions. > > > How has the project developed since the last report? > > Significant code developments took place to establish the foundation of > the project through August and September. A simple demonstration of the > most basic functionality is now included in a working build. > > > How would you assess the podling's maturity? > Please feel free to add your own commentary. > > [ ] Initial setup > [X] Working towards first release > [X] Community building > [ ] Nearing graduation > [ ] Other: > > Date of last release: > > We are still coding toward our first release. > > When were the last committers or PPMC members elected? > > We are still working to add all initial committers to the project. > > Signed-off-by: > > [ ](annotator) Nick Kew > Comments: > [ ](annotator) Brian McCallister > Comments: > [ ](annotator) Daniel Gruno > Comments: > [X](annotator) Jim Jagielski > Comments: > > -------------------- > BatchEE > > BatchEE projects aims to provide a JBatch implementation (aka JSR352) and a > set of useful extensions for this specification. > > BatchEE has been incubating since 2013-10-03. > > Three most important issues to address in the move towards graduation: > > 1. Still increase the community (but hard since it is quite stable and > between new specification releases) > 2. - > 3. - > > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be > aware of? > > No > > How has the community developed since the last report? > > No much since no new specification version was released. > > How has the project developed since the last report? > > Not much since it is stable. > > 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: > > 2016-09-22 > > When were the last committers or PPMC members elected? > > 2016-12-18 > > Signed-off-by: > > [ ](batchee) Jean-Baptiste Onofré > Comments: > [ ](batchee) Olivier Lamy > Comments: > [ ](batchee) Mark Struberg > Comments: > > IPMC/Shepherd notes: > There is no activity and they are waiting until a new spec arrives. > On the four year anniversary as a podling I think that BatchEE should be > looking how to become a low activity TLP. > Dave Fisher. > > -------------------- > Daffodil > > Apache Daffodil is an implementation of the Data Format Description > Language > (DFDL) used to convert between fixed format data and XML/JSON. > > Daffodil has been incubating since 2017-08-27. > > Three most important issues to address in the move towards graduation: > > 1. obtaining SGAs > 2. establishing new apache-centric infrastructure > 3. broadening base of contributors > > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be > aware of? > > - Only that chasing the SGAs down is going to take some time, though > this may be typical. > > How has the community developed since the last report? > > - Users: > (1) The Open Grid Forum's DFDL workgroup mailing list has had inquiries > and questions about Daffodil - using it and creating DFDL schemas. > We will start redirecting such to our incubator users mailing list, > as soon as we're ready. > (2) A large software company has demonstrated a prototype integration of > Daffodil into their commercial product. Of note: they did this without > any support contact to Daffodil developers. > > - Developers/Contributors: One new outside developer has been setup, and > has > started a project modifying the Daffodil code-base. This is still in the > pre-Apache > context, and we've no idea if they'll want to contribute back. But it does > show > both interest and that the technical barriers to entry for new developers > to be > productive are surmountable. > > How has the project developed since the last report? > > - A final consistent release/build of the legacy (pre-Apache) code-base > is over, all project efforts going forward can be Apache focused > once we have infrastructure setup. > - Progress is being made on obtaining the individual and organizational > SGAs. > > 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: > > (none yet) XXXX-XX-XX > > When were the last committers or PPMC members elected? > > - No changes yet - same as at our project incubator inception > > Signed-off-by: > > [X](daffodil) John D. Ament > Comments: Podling is still bootstrapping, looking for some feedback > from legal on approaches due to public sector relationship. > [X](daffodil) David Fisher > Comments: > > -------------------- > DataFu > > DataFu provides a collection of Hadoop MapReduce jobs and functions in > higher > level languages based on it to perform data analysis. It provides functions > for common statistics tasks (e.g. quantiles, sampling), PageRank, stream > sessionization, and set and bag operations. DataFu also provides Hadoop > jobs > for incremental data processing in MapReduce. > > DataFu has been incubating since 2014-01-05. > > Three most important issues to address in the move towards graduation: > > 1. Positive IPMC recommendation vote for graduation > 2. Address any IPMC feedback regarding graduation > 3. Continue 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? > > No new developments > > How has the project developed since the last report? > > Added support for Pig macros distributed in JAR. > Added a couple counting macros and TFIDF. > Started graduation discussion in general list. > > 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: > > 2017-03-10 > > When were the last committers or PPMC members elected? > > July 2016 (Eyal Allweil) > > Signed-off-by: > > [ ](datafu) Ashutosh Chauhan > Comments: > [ ](datafu) Roman Shaposhnik > Comments: > [X](datafu) Ted Dunning > Comments: > > IPMC/Shepherd notes: > > johndament: The podling is attempting to graduate, however there are > some concerns raised within the discussion over how big the actual PMC is. > There have also been concerns raised over the removal of committer status. > > -------------------- > FreeMarker > > FreeMarker is a template engine, i.e. a generic tool to generate text > output > based on templates. FreeMarker is implemented in Java as a class library > for > programmers. > > FreeMarker has been incubating since 2015-07-01. > > Three most important issues to address in the move towards graduation: > > We have a large user base but a rather small group of committers. > This was actually expected, given the maturity (and topic) of the > project. > While the FreeMarker 3 branch, which was started 8 month ago, will be > much > more appealing for contributors, development and growth due to that will > certainly take a long time. In other respects the project is mature and > ready for graduation. > > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be > aware of? > > We are eager to graduate but we're afraid that the number of active > contributors will prevent that in the foreseeable future. But remaining > in > the incubator for serveral years is obviosly a problem as well. > > How has the community developed since the last report? > > There were no changes since the last report. > > How has the project developed since the last report? > > Most activity was in the FreeMarker 3 branch. > The FreeMarker 2 branch was less active, but had some fixes and new > features. > At the moment we are nearing the next release from the 2 branch. > > 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: > > 2017-03-25 > > When were the last committers or PPMC members elected? > > 2017-02-13 Woonsan Ko, committer (non-PMC) > > Signed-off-by: > > [X](freemarker) Jacopo Cappellato > Comments: > [X](freemarker) Jean-Frederic Clere > Comments: > [X](freemarker) David E. Jones > Comments: > [X](freemarker) Ralph Goers > Comments: > [ ](freemarker) Sergio Fernández > Comments: > > IPMC/Shepherd notes: > > johndament: What is stopping Freemarker from graduating? > > -------------------- > Gobblin > > 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. > > Gobblin has been incubating since 2017-02-23. > > Three most important issues to address in the move towards graduation: > > 1. Cut our first release. > 2. Elect new Committer(s) / PPMC. > 3. Update links on website and documentation. > > 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? > > * 15+ major companies, startups, universites and research institutes are > now using Gobblin (refer to Powered-by section [1] here: > https://gobblin.apache.org/ ) > * Email stats for last month: > u...@gobblin.incubator.apache.org : 25 > d...@gobblin.incubator.apache.org : 163 > * There have been 40 Commits in last month: > git log --format='%ci' | grep -cE '2017-0(9)' > * 29 of those commits were by non-committers: > git log --format='%ae %ci' | grep -E '2017-0(9)' | cut -d ' ' -f 1 | > sort | uniq -c | sort -n > * Another video conference based meetup happened last month with good > attendance and interest. > * We are continuing to work towards our first release. > > [1] This data was collected before incubation via a survey. It was > expanded to include more companies as and when requested by respective > contributors. > > How has the project developed since the last report? > > * Continued active development. > * Progress continues to be tracked via JIRA / Sprint dashboard. > > How would you assess the podling's maturity? > > There is an all around progress, and the podling is working towards its > first release. > > [ ] Initial setup > [X] Working towards first release > [X] 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: > > [ ](gobblin) Jean-Baptiste Onofré > Comments: > [ ](gobblin) Olivier Lamy > Comments: > [X](gobblin) Jim Jagielski > Comments: > > IPMC/Shepherd notes: > > johndament: The podling has the right notion of next steps, website is > probably the biggest area of work needed. > > -------------------- > Gossip > > Signed-off-by: > > [ ](gossip) P. Taylor Goetz > Comments: > [ ](gossip) Josh Elser > Comments: Podling missed creating a report this month. In general, > the podling remains low-volume, but has had some repeat contributions from > GSOC students in the past 3-months. It's unclear if these contributors will > be preserved past the monetary-perks of GSOC. > [ ](gossip) Drew Farris > Comments: > > -------------------- > HAWQ > > HAWQ is an advanced enterprise SQL on Hadoop analytic engine built around a > robust and high-performance massively-parallel processing (MPP) SQL > framework > evolved from Pivotal Greenplum Database. > > HAWQ has been incubating since 2015-09-04. > > Three most important issues to address in the move towards > graduation: > > 1. Continue to improve the project's release cadence. To this > end we plan on expanding automation services to support > increased developer participation. > > > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need > to be aware of? > > Nothing urgent at this time. > > How has the community developed since the last report? > > 1. Conference Talks (2): > > * Big Data Technology Trends. China Big Data Industry Ecosystem > Conference (Speaker: Lei Chang, August 2, 2017) > > * Future Data Warehouse. China CIO Conference (Speaker: Lei Chang, Sep > 16, 2017) > > 2. Active contributions from approximately 20 different community > contributors since the last report (July 2017). > > 3. Yi JIN volunteered as the release manager for 2.3 release. > > 4. Three committer candidates are under voting process: > > 1) Amy BAI > 2) ChunLing WANG > 3) Hongxu MA > > > How has the project developed since the last report? > > 1. Apache HAWQ 2.2.0.0 was released. HAWQ 2.2 is the first binary release. > > Release information: > > 1) Release page: > > https://cwiki.apache.org/confluence/display/HAWQ/Apache+HAWQ+2.2.0.0-incubating+Release > > 2) Issues/tasks fixed (80): > https://issues.apache.org/jira/issues/?filter=12339844 > > > 2. The scope of 2.3 release is finalized: > > 1) New Feature: HAWQ Ranger supports RPS HA. (Done) > 2) New Feature: HAWQ Ranger supports Kerberos authentication. > (Done) > 3) New Feature: HAWQ Core supports plugable external storage > framework. (On going HAWQ-786) > 4) New Feature: HAWQ Core supports HDFS TDE (Transparent Data > Encryption) through libHdfs3. (Done, HAWQ-1193) > > 5) Licenses: Fix PXF license files located in PXF jar files. (Not > started HAWQ-1496) > 6) Licenses: Check Apache HAWQ mandatory libraries to match LC20, > LC30 license criteria. (Not started HAWQ-1512) > 7) Build: Release build project (On going HAWQ-127) > 8) Bug fixes. (On going) > > Project page link: > https://cwiki.apache.org/confluence/display/HAWQ/Apache+HAWQ+2.3.0.0-incubating+Release > > > 3. Project mail list activity: > > Between July 1, 2017 and Sep 25, 2017: > > d...@hawq.apache.org & u...@hawq.apache.org > 155 emails sent > 53 participants > > > 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: > > 2017-07-12, Apache HAWQ 2.2.0.0 > > When were the last committers or PPMC members elected? > > Podling committers (1) added: > Xiang Sheng (https://github.com/stanlyxiang), May 16, 2017 > > Signed-off-by: > > [X](hawq) Alan Gates > Comments: > [ ](hawq) Konstantin Boudnik > Comments: > [ ](hawq) Justin Erenkrantz > Comments: > [ ](hawq) Thejas Nair > Comments: > [ ](hawq) Roman Shaposhnik > Comments: > > -------------------- > Heron > > A real-time, distributed, fault-tolerant stream processing engine. > > Heron has been incubating since 2017-06-23. > > Three most important issues to address in the move towards graduation: > > 1. Finish bootstrapping project, IP clearance, initial website > 2. Expanding the community and adding new committers > 3. 1st ASF release > > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be > aware of? > > Migration to Apache infrastructure is waiting on the SGA from Twitter > which has not provided an ETA. There was a discussion on the general > incubator and Heron dev lists[1] about whether an SGA was required, but > consensus was not reached. LEGAL-339 [2] has been filed to get > clarification. > > 1 - > https://lists.apache.org/thread.html/a5c3ea63e8a07aeb2fb3e3627646198bd35db12b590f71e437130a98@%3Cdev.heron.apache.org%3E > 2 - https://issues.apache.org/jira/browse/LEGAL-339 > > How has the community developed since the last report? > > * Developer discussions have moved from Google groups and Slack to the > Heron Apache dev list. > > How has the project developed since the last report? > > * Development has been active, despite limited progress migrating to > Apache infra. > > 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: > > No Apache releases as of yet. Working on code import. > > When were the last committers or PPMC members elected? > > N/A, still bootstrapping the project. > > Signed-off-by: > > [ ](heron) Jake Farrell > Comments: > [ ](heron) Jacques Nadeau > Comments: > [ ](heron) Julien Le Dem > Comments: > [X](heron) P. Taylor Goetz > Comments: > > -------------------- > Juneau > > Apache Juneau is a toolkit for marshalling POJOs to a wide variety of > content > types using a common framework, and for creating sophisticated self- > documenting REST interfaces and microservices using VERY little code. > > Juneau has been incubating since 2016-06-24. > > Three most important issues to address in the move towards graduation: > > 1. Complete Podling Name Search (currently unresolved). > 2. Continue to grow community. > 3. > > 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? > > Two new PPMC members: > 1) Steve Blackmon > 2) Raphi D. Lee > > How has the project developed since the last report? > > 1 new release - Juneau 6.3.1, 08/01/2017 > 1 release currently in vote - Juneau 6.4.0 > > Currently undergoing internal graduation discussions within the PPMC. > > 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: > > 2017-08-01 > > When were the last committers or PPMC members elected? > > 2017-07-25 > > Signed-off-by: > > [x](juneau) Craig Russell > Comments: Juneau has made great progress and I believe is ready to > graduate. > [ ](juneau) Jochen Wiedmann > Comments: > [X](juneau) John D. Ament > Comments: Podling is ready to graduate. They understand the Apache > Way and have grown to multiple contributors. Great progress. > > -------------------- > 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 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: > > -------------------- > Milagro > > Distributed Cryptography; M-Pin protocol for Identity and Trust > > Milagro has been incubating since 2015-12-21. > > Three most important issues to address in the move towards graduation: > > 1. Improve project communication > 2. Define clear commit guidelines > 3. Building the Milagro community – engaging developers and > cryptographers, > raising awareness and helping to secure future of internet. > > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be > aware of? > > How has the community developed since the last report? > > We moved all of the crypto code to a new organisation on GitHub called > milagro-crypto ( https://github.com/milagro-crypto ). > It is hoped this will enable further engagement with the community and > specifically their involvement in developing the crypto code in other > languages. > Since the last report, two new committers were added. > > How has the project developed since the last report? > > The development was focused on Milagro Crypto C and Milagro Crypto > JavaScript. Milgaro can now support multiple curves and security levels in > a single binary. > > > How would you assess the podling's maturity? > Please feel free to add your own commentary. > > [ ] 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: > > [ ](milagro) Sterling Hughes > Comments: > [ ](milagro) Jan Willem Janssen > Comments: > [ ](milagro) Nick Kew > Comments: > > IPMC/Shepherd notes: > > johndament: Dave Fisher raised an issue, as noted in the report, that > much of Milagro's work seems to have moved to a private GitHub > organization. The podling has not responded to questions in this area. > > -------------------- > MXNet > > Apache MXNet is an open-source deep learning framework that allows you to > define, train, and deploy deep neural networks on a wide array of devices, > from cloud infrastructure to mobile devices. It is highly scalable, > allowing for fast model training, and supports a flexible programming model > and multiple languages. MXNet allows you to mix symbolic and imperative > programming flavors to maximize both efficiency and productivity. MXNet is > built on a dynamic dependency scheduler that automatically parallelizes > both symbolic and imperative operations on the fly. A graph optimization > layer on top of that makes symbolic execution fast and memory efficient. > The MXNet library is portable and lightweight, and it scales to multiple > GPUs and multiple machines. > > > Apache MXNet has been incubating since 2017-01-23. > > The most important issues to address in the move towards graduation: > > 1. Establish a predictable release process consistent with Apache Way -- > Ongoing. > 2. Grow the Community - Ongoing > 3. Update project website to Apache standards - In Progress > 4. Identify remaining ICLAs and SGAs that need to be addressed - in > progress > > 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? > > a) Various Slack channels and dev@ mailing lists are being used > actively. New user support and discussion forum created with the guidance > of Apache members at: http://discuss.mxnet.io > > b) O’Reilly published a series of blogs about MXNet, including ones with > step-by-step instructions to implement a convolutional neural network to > classify traffic signs with Apache MXNet: > > https://www.oreilly.com/ideas/classifying-traffic-signs-with-mxnet-an-introduction-to-computer-vision-with-neural-networks > > https://www.oreilly.com/ideas/apache-mxnetthe-fruit-of-cross-institutional-collaboration > > https://www.oreilly.com/ideas/self-driving-trucks-enter-the-fast-lane-using-deep-learning > > c) A new blog post published on 28-July showing users how to exploit the > unique features of Apache MXNet with a cheat sheet: > https://aws.amazon.com/blogs/ai/exploiting-the-unique-features-of-the-apache-mxnet-deep-learning-framework-with-a-cheat-sheet/ > > d) New Blog series by Viacheslav Kovalevskyi on Apache MxNet in Depth > published on Medium > https://blog.kovalevskyi.com/mxnet-distributed-training-explained-in-depth-part-1-b90c84bda725 > > e) Members of the community have conducted open meetups to share > information on Apache MXNet: > https://www.meetup.com/Apache-MXNet-learning-group/ > > f) Talks on Apache MXNet have been held in various universities and > conferences across the world including US, China, etc.: > https://www.youtube.com/watch?v=GBkOMtc9BIk > https://www.youtube.com/watch?v=kGktiYF5upk > > g) Presently working towards an upcoming 0.12.0 release targeted for > October or November 2017. > > > How has the project developed since the last report? > > a) The code base was migrated from http://github.com/dmlc/mxnet to > https://github.com/apache/incubator-mxnet on 28-July, 2017. The website > has also been migrated to this repository. > > b) From a statistics perspective, in July 2017, 54 authors pushed 140 > commits to master, with updates to 358 files including 22K additions and 3K > deletions. In Sep 2017, 62 authors pushed 171 commits to master, with > updates to 467 files including 26K additions and 7K deletions. > > c) Documentation- Architecture guides, How To’s, Tutorials, and APIs > continue to be improved. > > d) More features (e.g. operators, algorithms) and bug-fixes requested by > the user community continue to be added. > > > How would you assess the podling's maturity? > > Podling is still being established in Apache - hence maturity == Low, but > the project has a very diverse set of contributors. > > Please feel free to add your own commentary. > > [ ] Initial setup > [ ] Working towards first release > [X] Community building > [ ] Nearing graduation > [ ] Other: > > Date of last release: > > A maintenance release Apache MXNet-incubating 0.11.0 with few bug-fixes > was released on 05-Sep, 2017. > https://github.com/apache/incubator-mxnet/releases/tag/0.11.0 > > A maintenance release Apache MXNet-incubating 0.10.0 Post 2 with few > bug-fixes was released on 17-July, 2017. > https://github.com/apache/incubator-mxnet/releases/tag/0.10.0.post2 > > > When were the last committers or PPMC members elected? > > Ly Nguyen, Haibin Lin and Madan Jampani were added as committers and > PPMC members in June 2017. > > Signed-off-by: > > [X](mxnet) Sebastian Schelter > Comments: Second Suneel's comment that the project should work > towards more communication on its mailinglists. > [X](mxnet) Suneel Marthi > Comments: Plenty of activity on the project, would love to see more > discussions happening on mail lists or Slack. > [ ](mxnet) Markus Weimer > Comments: > [X](mxnet) Henri Yandell > Comments: Noting acknowledgement that Infra JIRA requests will be > going via mentors due to both the reported > volume of requests and the requests coming from > contributors and not committers. Also noting that > I've been active on legal-discuss@ regarding MXNet > ICLA/source headers, and in discussion offline > with an employer of contributors who has concerns with ICLA > signing. > > IPMC/Shepherd notes: > > johndament: The podling has come under fire recently for what is > perceived to be an over abundant amount of requests coming from > non-committers. If nothing else, it's a sign that they are anxious to get > going here at Apache and perhaps they need to look at their communication > model, moving more discussion on list, as well as potentially voting in new > committers. > > -------------------- > Myriad > > Signed-off-by: > > [ ](myriad) Benjamin Hindman > Comments: > [ ](myriad) Danese Cooper > Comments: > [ ](myriad) Ted Dunning > Comments: I am concerned about viability here. > [ ](myriad) Luciano Resende > Comments: > > > -------------------- > NetBeans > > NetBeans is a development environment, tooling platform and application > framework. > > NetBeans has been incubating since 2016-10-01. > > Three most important issues to address in the move towards graduation: > > 1. Relicensing of files to ASF. > 2. Completion of NOTICE and LICENSE files. > 3. Increase the involvement of the community in release tasks. > > 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? > > - Various discussions ongoing on Apache NetBeans dev mailing list. > - First pull requests have been received and community has been reviewing > them. > - At NetBeans meetup in Munich, Sven Reimers, an Apache NetBeans > committer, demoed Java 9 features (e.g., Jigsaw, JShell, JLink) in Apache > NetBeans. > > How has the project developed since the last report? > > - SGA has been provided by Oracle and accepted by Apache. > - Apache Git repo now contains the 1st code donation, 2 more being worked > on, consisting of around 45,000 files and 4 million LOC. > - Mirroring has been set up via GitHub. > - Around 29000 files have been relicensed to Apache via a converter tool > created by Jan Lahoda, an Apache NetBeans committer. > - Repo has been set up for tools, e.g., the converter tool referenced > above: https://github.com/apache/incubator-netbeans-tools > - Initial README, NOTICE, and LICENSE have been created and pushed. > - Jenkins build jobs have been set up and are working. > - Rat integration has been set up and is working as part of the build > process. > > How would you assess the podling's maturity? > Please feel free to add your own commentary. > > [X] Initial setup > [X] Working towards first release > [X] Community building > [ ] Nearing graduation > [ ] Other: > > Date of last release: > > No release yet. > > When were the last committers or PPMC members elected? > > Only initial committers, no additional voting has been done. > > Signed-off-by: > > [X](netbeans) Ate Douma > Comments: > [X](netbeans) Bertrand Delacretaz > Comments: > [ ](netbeans) Daniel Gruno > Comments: > [ ](netbeans) Mark Struberg > Comments: > > IPMC/Shepherd notes: > > johndament: Now that they have their first SGA, podling is getting their > feet wet in true ASF processes to get a release out the door. On list > activity is great. > > -------------------- > ODF Toolkit > > Java modules that allow programmatic creation, scanning and manipulation of > OpenDocument Format (ISO/IEC 26300 == ODF) documents > > ODF Toolkit has been incubating since 2011-08-01. > > Three most important issues to address in the move towards graduation: > > 1. Attract more developers > 2. Have frequent releases > 3. Fulfil the 1.0 version > > 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? > > Michael Stahl was voted as new committer/PMC member. Being OASIS > ODF TC member and LibreOffice developer. > Patches had been provided by other new developers. > > How has the project developed since the last report? > > Svante Schubert received sponsorship by German government prototype fund > to develop a new collaboration feature for the ODF Toolkit within upcoming > 6 months. > Developer vote has passed to move from SVN to GIT to improve visibility > on GitHub and archive better mergeability for feature branches. > > Date of last release: > > 2017-04-10 > > When were the last committers or PMC members elected? > > 2017-08-02 > > Signed-off-by: > > [ ](odftoolkit) Nick Burch > Comments: > [ ](odftoolkit) Yegor Kozlov > Comments: > [X](odftoolkit) Tom Barber > Comments: Some positive steps this month, activity has certainly > picked up and the SVN to Git swap will certainly help things. There were > plenty of +1's on the mailing list to show people are watching, but gaining > active members is clearly a struggle for the project. New PMC member will > help that also. > > -------------------- > Rya > > Rya (pronounced "ree-uh" /rēə/) is a cloud-based RDF triple store that > supports SPARQL queries. Rya is a scalable RDF data management system > built on > top of Accumulo. Rya uses novel storage methods, indexing schemes, and > query > processing techniques that scale to billions of triples across multiple > nodes. > Rya provides fast and easy access to the data through SPARQL, a > conventional > query mechanism for RDF data. > > Rya has been incubating since 2015-09-18. > > Three most important issues to address in the move towards graduation: > > 1. Have more releases as part of the Apache Foundation > 2. Increase diversity of contributors. > > > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be > aware of? > > No > > How has the community developed since the last report? > > * PPMC and IPMC voted to release 3.2.11 > > How has the project developed since the last report? > > * Implemented new types of inferences: owl:hasValue, owl:unionOf, > owl:equivalentClass, owl:allValuesFrom, owl:intersectionOf, owl: oneOf, > owl:someValuesFrom, owl:ReflexiveProperty, owl:hasSelf > * Added documentation and examples for the use of shell, Prospector, and > Pre-computed joins updater > * Removed/replaced code that used incompatible license (e.g. org.json, > jcalendar) - use ALv2 compatible license now > > 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: > > 2017-10-10 > > When were the last committers or PPMC members elected? > > * PPMC member Caleb Meier elected on Jan 3rd, 2017 > > Signed-off-by: > > [x](rya) Josh Elser > Comments: Podling continues to show increased maturity (recently, > handling some licensing issues during a release with very little guidance). > [ ](rya) Edward J. Yoon > Comments: > [ ](rya) Venkatesh Seetharam > Comments: > [x](rya) Billie Rinaldi > Comments: > > -------------------- > SensSoft > > SensSoft is a software tool usability testing platform > > SensSoft has been incubating since 2016-07-13. > > Three most important issues to address in the move towards graduation: > > 1. Moving towards the first Incubating release of the source code and > other > release artifacts to NPM/Bower, etc. > 2. Grow the Apache SensSoft (Incubating) community. > 3. Complete the issues highlighted at the SensSoft Roadmap > https://cwiki.apache.org/confluence/display/SENSSOFT/Roadmap > > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be > aware of? > > No > > How has the community developed since the last report? > > The community continues development via the scrum method, > sprinting towards the generation of the first release candidate > for UserALE.js. No new community members have come onboard with > development swamping the mailing lists. > > How has the project developed since the last report? > > The project is making sustainable progress. Project members > are driving towards generation of a release candidate for > UserALE.js 0.1.0. > > How would you assess the podling's maturity? > Please feel free to add your own commentary. > > [X] Initial setup > [X] Working towards first release > [X] Community building > [ ] Nearing graduation > [ ] Other: > > Date of last release: > > XXXX-XX-XX > > When were the last committers or PPMC members elected? > > Arthi Vezhavendan was added to PPMC and Committer base on 2017-01-24 > > Signed-off-by: > > [ ](senssoft) Paul Ramirez > Comments: > [X](senssoft) Lewis John McGibbney > Comments: > [ ](senssoft) Chris Mattmann > Comments: > > IPMC/Shepherd notes: > > - Drew Farris (shepherd): One mentor active on the mailing lists. > > > -------------------- > Spot > > Apache Spot is a solution stack that provides the capability to ingest IT > related telemetry (network flows, domain name service DNS, and proxy server > logs) and provide unsupervised machine learning capabilities to identify > suspicious activity. The information is organized and presented using > operational analytics so that a security analyst can investigate the most > suspicious connections. Apache Spot is built on and using Apache Spark and > Apache Hadoop. > > Spot has been incubating since 2016-09-23. > > Three most important issues to address in the move towards graduation: > > 1. Build diverse community > 2. Continue building a strong and diverse body of PPMC members for long > term project continuity > 3. Demonstrate ability to create releases > > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be > aware of? > * Recently Facebook decided to re-license React under MIT license, to > enable compatibility with Apache licensed projects and many others. If > there are not other indications from Incubator board we’ll call out a vote > to keep it for now: > https://code.facebook.com/posts/300798627056246/relicensing-react-jest-flow-and-immutable-js/ > > > How has the community developed since the last report? > > * Committers that are specialized on Ingest functions are merging > branches for Open Data Model (ODM) development. > * Same case for views in order to simplify the process of normalization > through the UI. > * Datasets with both benign and malicious traffic have been crafted to > allow community to test/evaluate ML executions, and facilitate > visualization exercises when doing Threat Hunting . > * Number of issues and discussion have increased with both feedback/RFE > and bug fixes, which probes adoption, of course Community growth also > consists on continue expanding the Committer baseline. > > > How has the project developed since the last report? > > * The Spot project completed the first official Apache release for Spot > v1.0, approved and voted by Incubator PMC. > * Open Data Model, development efforts continue over its branch in both > directions specification and code pushes. > > > 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: > > Comments: > > * Completion of the first Apache release was a significant milestone. The > focus now needs to be converting the large number of project observers into > project committers to foster a more diverse community, creating project > awareness through technology blog posts, and Meetups is a significant > effort that needs to happen for project evangelization > > Date of last release: > > 2017-09-08 > > When were the last committers or PPMC members elected? > > 2017-06-02 > > Signed-off-by: > > [X](spot) Jarek Jarcec Cecho > Comments: > [ ](spot) Brock Noland > Comments: > [ ](spot) Andrei Savu > Comments: > [X](spot) Uma Maheswara Rao G > Comments: > > IPMC/Shepherd notes: > Project is active and moving forward well. They do use ReactJS and will > need to upgrade and release as soon as the relicensed version is available. > Dave Fisher > > > -------------------- > Traffic Control > > Traffic Control is a set of components that can be used to build, monitor, > configure, and provision a large scale content delivery network (CDN). > > Traffic Control has been incubating since 2016-07-12. > > Three most important issues to address in the move towards graduation: > > 1. Enhance automation to make it easier to build, install, and configure > each component. > 2. Improve documentation to ease ramp-up time for new community members > and make it easier for existing community members to find what they are > looking for. > 3. Grow the community. > > 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 community took a vote and decided to move to full GitHub for source > code management and to use github for issue tracking instead of Jira. > > Traffic Control will be holding its fall summit on October 17th and 18th > in Atlanta, GA. There are currently over 20 participants from 5 different > companies registered to join. > > How has the project developed since the last report? > > Since the last report (July 2017), we have > > * Merged 93 Pull Requests with 609 commits from 21 contributors > * Opened 284 Github/Jira issues > * Closed 83 Github/Jira issues > * 284 emails sent by 39 people on the dev@ list > * 5 emails sent by 2 people on the users@ list > > How would you assess the podling's maturity? > Please feel free to add your own commentary. > > At our next summit (Oct 2017), we will be discussing what steps we need to > take to get to graduation. We still have some hurdles to clear, but it’s > good that we have recognized we need to start the discussion. > > [ ] Initial setup > [ ] Working towards first release (wip) > [x] Community building (wip) > [ ] Nearing graduation > [ ] Other: > > Date of last release: > > Traffic Control 2.0 was released on July 7th, 2017. > > When were the last committers or PPMC members elected? > > In August, Traffic Control added 3 new committers from 2 different > companies: Derek Gelinas (Comcast), Rob Butts (Comcast) , and Peter Ryder > (Cisco) > > Signed-off-by: > > [X](trafficcontrol) Phil Sorber > Comments: > [](trafficcontrol) Eric Covener > Comments: > [X](trafficcontrol) Leif Hedstrom > Comments: > > IPMC/Shepherd notes: > > johndament: It's great to see a community driven in person event being > scheduled. However, the podling should be cautious and ensure that all > information discussed in person is brought back to the list when complete. > > -------------------- > Weex > > Weex is a framework for building Mobile cross-platform high-performance UI. > > Weex has been incubating since 2016-11-30. > > Three most important issues to address in the move towards graduation: > > 1. Move the whole workflow and infra into Apache (not the codebase only). > 2. Develop more contributors and committers. > 3. More releases while in Incubator. > 4. Improve the developer's activity in JIRA and mailing list. > > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be > aware of? > > No. > > How has the community developed since the last report? > > • We voted two new committers: gurisxie, Hanks > • Our Github has growth contributors (131), forks (760), watchers (296) > and stars (5522) > • We have encouraged people to discuss more in the JIRA and dev mailing > list. Up to now, 76 issues have been reported on JIRA and 37 of them are > resolved or closed. > • WebSite Trends Month Active, PV(393698), UV(64096), IP(53712), New > Unique Visitor(36155) , Session(103184) > > How has the project developed since the last report? > > • 21 authors have pushed 284 commits to master and 285 commits to all > branches since last month. > • We are replacing Facebook's Yoga with Google's FlexboxLayout for our > layout system. > • Several new features including pseudo-class, box-shadow in Android, > 3d rotate were proposed and developed 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-06-08 > > When were the last committers or PPMC members elected? > > • gurisxie, 13 Sep 2017 > • Hanks, 9 Aug 2017 > > Signed-off-by: > > [ ](weex) Luke Han > Comments: > [ ](weex) Willem Jiang > Comments: > [ ](weex) Stephan Ewen > Comments: > [X](weex) Raphael Bircher > Comments: The community still learning the Apache Way. Also we have > to work on the diversity. > But we make progress. An additional active Mentor would be good. >
