This Confluence has been LDAP enabled, if you are an ASF Committer, please use your LDAP Credentials to login. Any problems file an INFRA jira ticket please.

Page tree
Skip to end of metadata
Go to start of metadata

Incubator PMC report for October 2018

** FINAL ** ** DO NOT EDIT **

Timeline

Wed October 03

Podling reports due by end of day

Sun October 07

Shepherd reviews due by end of day

Sun October 07

Summary due by end of day

Tue October 09

Mentor signoff due by end of day

Wed October 10

Report submitted to Board

Wed October 17

Board meeting

Shepherd Assignments

Dave Fisher

DLab

Dave Fisher

ODF Toolkit

Drew Farris

Livy

Drew Farris

SensSoft

John Ament

MXNet

John Ament

ServiceComb

Justin Mclean

Milagro

P. Taylor Goetz

Gobblin

P. Taylor Goetz

Rya

P. Taylor Goetz

Zipkin

Timothy Chen

BatchEE

Timothy Chen

Doris

Timothy Chen

Weex

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="51af5892-02db-4f82-bd43-a216f878bfc5"><ac:plain-text-body><![CDATA[

[none]

Airflow

]]></ac:plain-text-body></ac:structured-macro>

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="7336eae5-7dd1-49a3-897a-3123f9b35ef1"><ac:plain-text-body><![CDATA[

[none]

Amaterasu

]]></ac:plain-text-body></ac:structured-macro>

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="a7c06aef-a158-428b-b90b-7e03e9bfd7d5"><ac:plain-text-body><![CDATA[

[none]

Annotator

]]></ac:plain-text-body></ac:structured-macro>

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="0b06168c-b145-4cc6-ac04-a2cc68ef10c5"><ac:plain-text-body><![CDATA[

[none]

Marvin-AI

]]></ac:plain-text-body></ac:structured-macro>

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="f2f087a7-710a-49b4-aa49-a955bb15662b"><ac:plain-text-body><![CDATA[

[none]

NetBeans

]]></ac:plain-text-body></ac:structured-macro>

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="373cb8b3-e3f3-46f8-b4f4-c71cbf390f6f"><ac:plain-text-body><![CDATA[

[none]

PLC4X

]]></ac:plain-text-body></ac:structured-macro>

Report content

Incubator PMC report for October 2018

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 presently 52 podlings incubating. During the month of September,
podlings executed 10 distinct releases and there are several ongoing votes
on releases for October. We added 2 new IPMC members.

In September one podling Pulsar graduated and one podling Gearpump retired.

BatchEE still seems stuck in performing the last graduation steps and needs
some nudging over the line. Several other podlings are heading towards
graduation or retirement. There was one IP clearance.

The number of podlings (one) that didn't report has fallen from last month.
They have been asked to report next month. Of concern is Weex who failed to
respond to queries on both the dev and private list. There seem to be
little activity on the dev list other than GitHub traffic. One podling
Warble failed to get sign off from it's single mentor.

The situation with Milagro is concerning as they missed reporting many
times, the PPMC are inactive or didn't realise that they were on the PPMC
(they do now). Despite yet another strong suggestion to retire, they still
want to restart the project. It may be  difficult to do so as the project
never really got started at Apache and most of the initial committers
haven't signed ICLAs. They did however report this month.

The Superset podling (as reported last month) seems to have a few other
issues (see mailing list), but they are responding and fixing the issues
and a mentor (Jim) was sorting the situation out. However they are
continuing to make unapproved releases and Jim has retired as a mentor.
It's currently unclear if any of the other mentors are active.

MXNext had several new mentors added to help with diversity among it's
mentors.

An email was sent out to all inactive mentors and we've had 60% respond,
most of those who responded have indicated that will step down. So far 24
mentors have asked to be removed and it's likely that most of the 26 who
haven't responded are inactive and will need to be removed. Good news is 9
have asked to continue. This has left several podlings with only a one or
two active mentors, which is no change from before but now we know the true
situation. We have had a few people ask to be a mentor and several mentors
who were inactive, and who asked to stay on, have showed signs of increased
activity.

I just want to thank all the mentors for their past work and for those who
recognised that the best thing that they could do for their podling was to
step aside. Missing signing off 3 board reports in a row turns out to be a
useful metric as a proxy for mentor activity (about an 85% correlation).

In the discussion on what to do about podlings tasked with writing bylaws /
guidelines in their graduation proposal, there's general consensus that
podlings should be not asked to do this. A draft minimal default set of
guidelines has been created. This will be brought to the boards attention
in the next few weeks.

A new question has been added to the report asking podlings if they are
getting enough support from their mentors, hopefully this will identify
missing mentors earlier. A number of podling just copied and pasted from
previous reports and didn't notice this new question.

A small change to the incubator proposal template should help with podlings
taking too long to incubate or at least frame their expectations.

* Community

  New IPMC members:
  - Jason Dai
  - Xiangrui Meng

  People who left the IPMC:
  - None

* New Podlings

 - Marvin-AI
 - Zipkin

* Podlings that failed to report, expected next month

 - Weex (did not respond to queries)

* Graduations

  The board has motions for the following:
  - Joshua (to be posted)
  - ServiceComb

* Releases

  The following releases entered distribution during the month of
  September:

  Tephra 0.15.0
  Daffodil 2.2.0
  Griffin 0.3.0
  Dubbo 2.6.3
  Mxnet 1.3.0
  Pulsar 2.1.0
  Skywalking 5.0.0
  Unomi 1.1.0
  Openwhisk 0.9.8 and 1.12.0

* IP Clearance

  Arrow Gandiva library

* Legal / Trademarks

  Due to a trademark issue, SensSoft has decided to change it's name.

* Infrastructure

  N/A.

* Miscellaneous

  release checklist created

* Credits

  None

----------------------------------------------------------------------
                       Table of Contents
Airflow
Amaterasu
Annotator
BatchEE
DLab
Doris
Gobblin
Livy
Marvin-AI
Milagro
MXNet
NetBeans
ODF Toolkit
PLC4X
Rya
SensSoft
ServiceComb
Warble
Zipkin

----------------------------------------------------------------------

--------------------
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. Once we make a release with the licensing fix we will move forward with
  graduation.
  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?
  1. Since our last podling report 1 month ago (i.e. between September 4 &
  October 1, inclusive), we grew our contributors from 548 to 580 (32 new
  contributors)
  2. Since our last podling report 1 month ago (i.e. between September 4 &
  October 1, inclusive), we resolved 151 pull requests (currently at 3114
  closed PRs)
  3. Since being accepted into the incubator, the number of companies
  officially using Apache Airflow has risen from 193 to 206, 13 new from
  the last podling report 1 month ago.

How has the project developed since the last report?
  See above : 151 PRs resolved, 32 new contributors, & 13 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:

  2018-08-27

When were the last committers or PPMC members elected?
  Tao Feng on Aug 3

Have your mentors been helpful and responsive or are things falling
through the cracks? In the latter case, please list any open issues
that need to be addressed.
  One of our mentors is pretty active and helpful, one of our mentors has
  never been involved, and one is in the middle.

Signed-off-by:

  [ ](airflow) Chris Nauroth
     Comments:
  [x](airflow) Hitesh Shah
     Comments:
  [x](airflow) Jakob Homan
     Comments:

IPMC/Shepherd notes:

--------------------
Amaterasu

Apache Amaterasu is a framework providing configuration management and
deployment for Big Data Pipelines.

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, the 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. Grow up user and contributor communities
  2. Prepare documentation

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

  A concern was raised by a mentor that the community is too small and not
  active enough and that Amaterasu should consider retiring. We did a roll
  call, and identified a total of 5 individuals willing to contribute as
  volunteers.
  We'll keep tracking the activity and reassess whether to retire within a
  few months.

How has the community developed since the last report?

  N/A

How has the project developed since the last report?

  * Since the last report Amaterasu has hit it's first major milestone -
  the project's first release as an Apache Project.
  * Out of 27 issues for the next version 11 are done and 2 are in progress.
  * One organisation we are aware of have decided to start a project using
  Amaterasu with the intention of using it in production.

Date of the last release:

  12 July 2018

When were the last committers or PMC members elected?

  N/A

Have your mentors been helpful and responsive or are things falling
through the cracks? In the latter case, please list any open issues
that need to be addressed.

Signed-off-by:

  [X](amaterasu) Jean-Baptiste Onofré
     Comments: Please provide answer to the question about mentors help
  [X](amaterasu) Olivier Lamy
     Comments: enough activity? big users community?
  [X](amaterasu) Davor Bonaci
     Comments: tracking activity/viability of graduation.

IPMC/Shepherd notes:

--------------------
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. Grow the PPMC
  2. Grow community activity
  3. Build collaboration with downstream users

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

  The project has lost mentors and would invite help from interested
  mentors.
  This report is a return to regular cadence; it reflects only the month of
  September.

How has the community developed since the last report?

  The PPMC has begun to reach out to the communities of predecessor
  projects, communicate their deprecation, and shepherd users towards
  the ASF home.

How has the project developed since the last report?

  Continuous Integration infrastructure has been set up.

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:

  N/A

When were the last committers or PPMC members elected?

  Last committer was added in August.

Have your mentors been helpful and responsive or are things falling
through the cracks? In the latter case, please list any open issues
that need to be addressed.

  Mentors have been helpful and attentive and are working to set
  expectations for project development and address recent stagnation.

Signed-off-by:

   [X](annotator) Nick Kew
      Comments: The team have responded well to recent hiatus.
                They have also put out a call for new mentors
                following recent resignations.

IPMC/Shepherd notes:

--------------------
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. Do the graduation :)
  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?

  Community is stable.

How has the project developed since the last report?

  No strong change. We are starting back to work on the graduation, hoping
  to do it before the end of the year if conferences and work load enable us
  to do so.

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-12-01

When were the last committers or PPMC members elected?

  2015-12-01 Reinhard Sandtner

Have your mentors been helpful and responsive or are things falling
through the cracks? In the latter case, please list any open issues
that need to be addressed.

Signed-off-by:

  [X](batchee) Jean-Baptiste Onofré
     Comments:
  [X](batchee) Olivier Lamy
     Comments:
  [ ](batchee) Mark Struberg
     Comments:

IPMC/Shepherd notes:

--------------------
DLab

DLab is a platform for creating self-service, exploratory data science
environments in the cloud using best-of-breed data science tools.

DLab has been incubating since 2018-08-20.

Three most important issues to address in the move towards graduation:

  1. Exectute the SGA between EPAM and the ASF so code can be imported.
  2. Complete on-boarding of initial committers.
  3. Work toward an initial Apache release.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

  Not at this time.

How has the community developed since the last report?

  This is our first report.

How has the project developed since the last report?

  A number of committers have submitted ICLAs, had their Apache
  accounts created, and subscribed to appropriate mailing lists.

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:

  N/A

When were the last committers or PPMC members elected?

  We are still operating with the set of initial committers.

Have your mentors been helpful and responsive or are things falling
through the cracks? In the latter case, please list any open issues
that need to be addressed.

Signed-off-by:

  [X](dlab) P. Taylor Goetz
     Comments:
  [X](dlab) Henry Saputra
     Comments:
  [X](dlab) Konstantin I Boudnik
     Comments:

IPMC/Shepherd notes:
Dave Fisher - Podling starting up slowly. There is mentor engagement.

--------------------
Doris

Doris is a MPP-based interactive SQL data warehousing for reporting and
analysis.

Doris has been incubating since 2018-07-18.

Three most important issues to address in the move towards graduation:

  1. Finished configuration for each Apache ID, it means each committer
  could commit their patches to new repo and then we are going to set up
  a CI system.
  2. Set up the podling website for Doris and then we will continue to
  complete the website, include write guide to new user.
  3. Committed some patches for bug fix and something else, and then we
  will make the new commit rules, and prepare to fix license header and etc.

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?

  Finished configuration for each Apache ID, it means each committer could
  commit their patches to new repo.
  Set up the podling website for Doris and we will continue to complete the
  website.

How has the project developed since the last report?
  Committed some patches for bug fix and something else, and then we will
  make the new commit rules, and prepare to fix license header.

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:

  N/A.

When were the last committers or PPMC members elected?

  N/A.

Have your mentors been helpful and responsive or are things falling
through the cracks? In the latter case, please list any open issues
that need to be addressed.

  Yes.

Signed-off-by:

  [X](doris) Dave Fisher
     Comments: Setup progress is slow, but steady.
  [X ](doris) Luke Han
     Comments:
  [ ](doris) Willem Jiang
     Comments:

IPMC/Shepherd notes:

--------------------
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:

  Nothing at this time.

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?

  * 74% of commits were from non-committer contributors.
  * Email stats since last report:
    user@gobblin.incubator.apache.org : 10
    dev@gobblin.incubator.apache.org : 243
  * There have been 61 Commits since last report:
    git log --format='%ci' | grep -cE '((2018-0(7|8|9))|(2018-10))'
  * 45 ie. 74% of those commits were by non-committers:
    git log --format='%ae %ci' | grep -E '((2018-0(7|8|9))|(2018-10))'|
    cut -d ' ' -f 1 | sort | uniq -c | sort -n
  * Recurring video conference based meet-up has been happening every
    month with a healthy attendance.
  * Gobblin had a presentation in ApacheCon NA 2018, and has independently
    been featured in various meet-ups / conferences around the world.

How has the project developed since the last report?

  * Gobblin's evolution as Platform-as-a-Service is near GA - driven by
    couple of non-committers.
  * Comprehensive work to stabilize Gobblin cluster at extreme scale by
    non-committer contributor.
  * Streaming pipeline simplification and enhancements.
  * New ElasticSearch support.
  * Gobblin - Azkaban integration.
  * Job quotas in Gobblin cluster mode through Apache Helix.
  * Couchbase integration enhancement.
  * New optimized Config store implementation.
  * Block level distcp-ng in progress.
  * Release 0.13.0 done.

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:

  2018-09-20

When were the last committers or PPMC members elected?

  Joel Baranick in December, 2017.

Have your mentors been helpful and responsive or are things falling
through the cracks? In the latter case, please list any open issues
that need to be addressed.

  Yes.

Signed-off-by:

  [X](gobblin) Jean-Baptiste Onofre
     Comments: Great presentation at ApacheCon (which convince me again to
     contribute on the codebase).
  [X](gobblin) Olivier Lamy
     Comments:
  [X](gobblin) Jim Jagielski
     Comments:

IPMC/Shepherd notes:

--------------------
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 have more activities.
  2. Grow more contributors and committers.
  3. Regular release.

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?

  Activity on the dev and user mailing lists as well as the rate of reported
  JIRA issues has stayed steady. There has been an uptick of development
  activity around adding a new feature to the project (a Hive-compatible
  Thrift server implementation).

How has the project developed since the last report?

  A new feature (Hive-compatible Thrift server) is being implemented, and
  some code to support legacy releases of Java, Scala and Spark have been
  removed.

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:

  2018-02-06

When were the last committers or PPMC members elected?

  2017-09-18

Have your mentors been helpful and responsive or are things falling
through the cracks? In the latter case, please list any open issues
that need to be addressed.

  We have not asked much of our mentors, but they are active on the email
  lists.

Signed-off-by:

  [ ](livy) Bikas Saha
     Comments:
  [ ](livy) Brock Noland
     Comments:
  [x](livy) Luciano Resende
     Comments:
  [X](livy) Jean-Baptiste Onofre
     Comments:

IPMC/Shepherd notes:

--------------------
Marvin-AI

Marvin-AI is an open-source artificial intelligence (AI) platform that helps
data scientists, prototype and productionalize complex solutions with a
scalable, low-latency, language-agnostic, and standardized architecture
while
simplifies the process of exploration and modeling.

Marvin-AI has been incubating since 2018-08-21.

Three most important issues to address in the move towards graduation:

  1.Move development infrastructure to Apache
  2.Build Community
  3.Build Releases

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?

  * Slowly discussing how to move development to Apache Infrastructure

How has the project developed since the last report?

  * N/A

Have your mentors been helpful and responsive or are things falling
through the cracks? In the latter case, please list any open issues
that need to be addressed.

  * At least one of the mentors is active

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:

  XXXX-XX-XX

When were the last committers or PPMC members elected?

  * N/A

Have your mentors been helpful and responsive or are things falling
through the cracks? In the latter case, please list any open issues
that need to be addressed.

Signed-off-by:

  [X](marvin-ai) Jim Jagielski
     Comments:
  [x](marvin-ai) Luciano Resende
     Comments:
  [ ](marvin-ai) William Colen
     Comments:

IPMC/Shepherd notes:

--------------------
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. Rebuild the team
  2. Edit the code for the first release
  3. Expand the community

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

  We need support to restart the project management and to make the code
  released.

  This project have been stalled for several month because initial
  committers from Miracl unfortunately stopped activities from external
  reasons.
  We already have a set of codes that will work as the initial product, and
  it will need some editorial (and possibly legal?) efforts to release.
  The idea of retirement was put to the vote and was rejected, and we are
  working for restarting.

How has the community developed since the last report?

  No new committers.
  Some people are joining the conversation at the dev mailing list to help
  the restart.

How has the project developed since the last report?

  We are worked for the first release of the crypt library part, and the
  code seems technically stable enough to release.

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:

  XXXX-XX-XX

When were the last committers or PPMC members elected?

  n/a

Have your mentors been helpful and responsive or are things falling through
the cracks? In the latter case, please list any open issues that need to be
addressed.

  Mentors are helpful in starting the restart.
  Sometimes the members lack very basic information about the management in
  ASF, so we will be work better if more input is given.
  It may lack the continuous help and responsive support in getting the
  things done.

  The project's open issues are:
  (1) List committer candidates with ICLA status,
  (2) Give access to the official repository for committers who already
  signed ICLA,
  (3) List all the repositories that contain codes for this project,
  (4) Analyze status of each repository, possibly including legal status
  (5) Edit and merge the code and push to the official repository.
  (6) Release

  We need help and guide by mentors to address the issues from the
  following aspects:
  (A) Input on Apache's process, source of information, or use of the
  toolset,
  (B) Helpful facilitation for communication with PMCs and the community,
  (C) Guide how the output code/document should be.

  Mentors are requested to submit a ping message on the mailing list
  regularly that asks any blockers to encourage the communication among
  mentors, PMCs and the community.

Signed-off-by:

  [ ](milagro) Sterling Hughes
     Comments:
  [X](milagro) Nick Kew
     Comments:  This podling needs attention if it is to progress.
                My own efforts have been insufficient.  I intend to
                open a discussion on the subject, but am procrastinating.

IPMC/Shepherd notes:

--------------------
MXNet

A Flexible and Efficient Library for Deep Learning

MXNet has been incubating since 2017-01-23.

Three most important issues to address in the move towards graduation:

  1. Establish a predictable release process consistent with Apache Way --
  ESTABLISHED.
  2. Grow the community -- ONGOING.
  3. Identify remaining ICLAs or SGAs that need signing – NEAR COMPLETION.

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?
  * We have active contributors from companies like Intel, Nvidia, Wolfram
  Design  and more. The number of github contributors increased from 506
  (3/31/2018) to currently 592 (9/28/2018, 2.4% MoM),
  * Active discussions on https://discuss.mxnet.io/ (English) and
  https://discuss.gluon.ai/ (Chinese)
  * We developed an active blog on Medium
  (https://medium.com/apache-mxnet). We have posted 28 blogs YTD
  (12.0% MoM), and have 891 (16.3% MoM) followers.
  * We established a YouTube channel (https://www.youtube.com/apachemxnet)
  and have 370 subscriber (+32.1% MoM) and 32 videos published.
  * We are tweeting to promote new content and community events such as
  meetups and conferences. Our Twitter account has 1,510 followers on
  https://twitter.com/ApacheMXNet (3.6% MoM).
  * 62 new public tutorials about MXNet have been published YTD in
  addition to the Medium blogs. Details available at
https://lists.apache.org/thread.html/52f88e9dc7a6a2a1dfa5ad41c469fe2cdd1209a
0be2eb345bc2f9a96@%3Cuser.mxnet.apache.org%3E
https://lists.apache.org/thread.html/dea9184350f2fe87ce450722ead28072f763196
045f39859190f83f8@%3Cuser.mxnet.apache.org%3E
  https://discuss.mxnet.io/t/apache-mxnet-digest-august-2018
  * We established a global MXNet meetup group with 4 groups in 3
  countries and 833 member.
  https://www.meetup.com/pro/deep-learning-with-apache-mxnet/
  * Community members participated at conferences and other venues,
  staffing booths and giving a total of nine presentations about MXNet:
  ACNA18 (Montréal, total 4 presentations about MXNet from community
  members), Linux Foundation Open Source Summit (Vancouver), AI Meetup
  (Toronto), MXNet Meetup (Seattle, San Francisco), Open Data Science
  Conference (London), Big Data Summit (Boston), AI  and Neural Networks
  on Arm Summit at Linaro conference (Vancouver),O'Reilly AI conference
  https://www.oreilly.com/ideas/machine-learning-in-the-cloudm

How has the project developed since the last report?
  1) v1.3 release notes:
  https://github.com/apache/incubator-mxnet/releases/tag/1.3.0
  2) Community updated MXNet backend for Keras to v2.2.2
  3) Github statistics
  Statistics are captured at the end of each month from
  https://github.com/apache/incubator-mxnet/pulse/monthly
  July 2018
  * Excluding merges, 62 authors have pushed 180 commits to master and 188
  commits to all branches. On master, 614 files have changed and there
  have been 29,908 additions and 26,648 deletions.
  * 273 issues got closed and 154 new issue created during the reporting
  period.
  August 2018:
  * Excluding merges, 68 authors have pushed 217 commits to master and 234
  commits to all branches. On master, 463 files have changed and there
  have been 20,882 additions and 6,404 deletions.
  * 200 issues got closed and 98 new issue created during the reporting
  period.
  September 2018:
  * Excluding merges, 47 authors have pushed 132 commits to master and 141
  commits to all branches. On master, 439 files have changed and there
  have been 13,797 additions and 5,871 deletions.
  * 124 issues got closed and 87 new issue created during the reporting
  period.

How would you assess the podling's maturity?
Please feel free to add your own commentary.
  Podling is still having difficulties to grow committer community.
  Maturity == Medium.

  [ ] Initial setup
  [ ] Working towards first release
  [X] Community building
  [ ] Nearing graduation
  [ ] Other:

Date of last release:

  2018-09-19 (v1.3) Apache MXNet-incubating 1.3.0 (major release)
  was published on September 19, 2018
  https://github.com/apache/incubator-mxnet/releases/tag/1.3.0

When were the last committers or PPMC members elected?
  2018-08-10 Carin Meier
  2018-09-27 additional mentors joined to help with diversity
  among MXNet's mentors:
  Jason Dai; Jim Jagielski; Bob Paulin; and Michael Wall.
  2018-09-27 Suneel Marthi retired as mentor

Have your mentors been helpful and responsive or are things falling
through the cracks? In the latter case, please list any open issues
that need to be addressed.
  We thank the mentors for ongoing support and guidance.

Signed-off-by:

  [ ](mxnet) Sebastian Schelter
     Comments:
  [X](mxnet) Jason Dai
     Comments:
  [X](mxnet) Henri Yandell
     Comments: Needs to work on converting contributors to committers.
  [ ](mxnet) Markus Weimer
     Comments:
  [X](mxnet) Jim Jagielski
     Comments:
  [ ](mxnet) Bob Paulin
     Comments:
  [X](mxnet) Michael Wall
     Comments:

IPMC/Shepherd notes:

--------------------
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. DNS handover, e.g., for netbeans.org and planetnetbeans.org, needs to
  be finalized on the Apache side, Oracle having handed everything related
  to domains over now.
  2. 3rd donation, focused on tutorials and images, and related ancillary
  items.
  3. 4th donation, focused on C/C++ features.

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?

  - Three virtual meetups have taken place to connect community members and
  discuss activities, all recorded and published on
  blogs.apache.org/netbeans.
  Around 20 in attendance at these, at the last one there were reps from
  Oracle, Apache infra, and Apache NetBeans, discussing the way forward
  with the domain handovers.
  - Currently 622 (588 in last report) on Apache NetBeans users mailing
  list and 438 (422 in last report) on Apache NetBeans dev mailing list.
  - Ken Fogel to represent Apache NetBeans at ACNA 2018:
  https://apachecon.dukecon.org/acna/2018/#/scheduledEvent/7e6b57d36ccd834f2
  - Several community members to be present and present at Oracle Code One
  2018:
  https://cwiki.apache.org/confluence/display/NETBEANS/Oracle+Code+One+2018

How has the project developed since the last report?

  - Final release of Apache NetBeans (incubating) 9.0 released:
  https://netbeans.apache.org/download/nb90/nb90.html
  - Article about status published on InfoQ:
  https://www.infoq.com/news/2018/08/netbeans-apache-update-aug18
  - Roadmap put together for the first time:

https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+Release
+Roadmap
  - Current focus is on Apache NetBeans 10:
  https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+10
  - Successfully completed cleaning up the root directory of GitHub repo:
  [[https://github.com/apache/incubator-netbeans (done together as a
  community, see
https://cwiki.apache.org/confluence/display/NETBEANS/Per-cluster+repository+
layout).
  - The legal title to the trademarks has passed in full to Apache, by the
  signing of the Trademark and Domain Assignment agreement.
  - i.e., brand and domain handover have been completed on the Oracle and
  Apache sides, aside from the DNS reassignment, see above.
  - Removed single point of failure of non-Apache released binaries from
  Oracle to Oregon State University Open Source Lab:
  https://github.com/apache/incubator-netbeans/pull/899

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:

  2018-09-29 Apache NetBeans (incubating) 9.0 final release

When were the last committers or PPMC members elected?

  * PPMC member Eirik Bakke elected on September 27, 2018
  * PPMC member Thilina Ranathunga elected on September 18, 2018
  * PPMC member Eric Barboni elected on September 4, 2018

Have your mentors been helpful and responsive or are things falling
through the cracks? In the latter case, please list any open issues
that need to be addressed.

  They have been very helpful as always.

Signed-off-by:

  [X](netbeans) Ate Douma
     Comments: I also think the project is about ready to graduate. The
     community is healthy and the PPMC members get it and have what it
     takes to be on their own feet.
  [X](netbeans) Bertrand Delacretaz
     Comments: I don't think the 2nd and 3rd donation block graduation,
     project is mostly ready, discussed on their dev list with a tentative
     goal to graduate by then end of this year.
  [ ](netbeans) Daniel Gruno
     Comments:
  [ ](netbeans) Mark Struberg
     Comments:

IPMC/Shepherd notes:

--------------------
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. Improve feature set to attract companies and refill the gap Sun/Oracle
  and IBM left behind
  2. New collaboration feature for companies needs further documentation,
  performance testing (and be merged) to attract companies.
  https://github.com/svanteschubert/odftoolkit/blob/odf-changes/README.md
  3. Fulfil the 1.0 version

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
  Traction of new developers (esp. from companies) goes slow.
  There had been repeated government sponsorship directly last winter:
  https://prototypefund.de/project/documents-for-democracy/
  and just started for this Winter on new feature sets:
  https://prototypefund.de/project/papierloser-alltag/

How has the community developed since the last report?
  New bug reports yet no new committers.
  Presentation for HTML based real-time editors has been created and held
  at LibreOffice Conference 2018 Tirana last week.
https://github.com/svanteschubert/odftoolkit/blob/odf-changes/LibOCon2018%20
%20-%20Interoperable%20Office%20Collaboration.pdf
  Providing information on how to become an ODF application with the new
  odf-change feature.
  	  	  	
How has the project developed since the last report?
  CKSource (developer of CKEdit5) have been visited, but yet without
  commitment yet.
  The documentation and performance (tests) of the ODF change
  interoperability feature has been improved, but still ongoing.
  His previous collaboration feature runs finally full-featured with
  green regression tests on his GitHub fork and was not yet merged into the
  main  branch.
  Merge needs to be done before October, so the new sponsorship can focus
  on source code generation from the ODF XML grammar loaded into Graph
  Database (Apache Tinkerpop).
	

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 the last release:

  2017-04-10

When were the last committers or PMC members elected?

  2017-08-02

Signed-off-by:

  [ ](odftoolkit) Nick Burch
     Comments:
  [X](odftoolkit) Tom Barber
     Comments: I agree with Dave's analysis although I did also pitch the
     Labs as an idea, but that got no traction. Sad to see it go, but there
     is no growth being shown.

IPMC/Shepherd notes:
  Dave Fisher - Svante Schubert is the only active developer. I have been
  having  conversations with him on the future with a push towards
  retirement.
  It is possible the project could move to the TDF.

--------------------
PLC4X

PLC4X is a set of libraries for communicating with industrial programmable
logic controllers (PLCs) using a variety of protocols but with a shared API.

Most important issues to address while moving towards graduation:

  Building the community: The PPMC and committer group has a large
  percentage of codecentric employees, we have been recruiting people
  from other companies, but will have to continue these efforts for
  establishing a healthy Apache community.
  Onboarding of new committers: With PLC4X several people on the team are
  not very familiar with the Apache Way. We have started and will continue
  our efforts on this onboarding.

Any Issues the Incubator PMC or ASF Board might wish/need to be aware of:

  Not at the moment.

How has the community developed since the last report?

  While the community activity had been quite low since the beginning of
  the project, things changed in August.
  Then we noticed not only new names appearing on the list, but the number
  of emails on the list grew by 400%-500%.
  Also did we get several pull requests from about 5 new names,
  contributing to multiple areas.
  Two of them got added to the Committers and PPMC groups.
  The others were one-shot contributions without any further communications.

In September Christofer Dutz had two talks on PLC4X at two conferences:

  *   Solutions Hamburg 2018
  *   ApacheCon NA 2018

  An article on PLC4X by Christofer Dutz was published in the German Tech
  Magazine: iX
  (Link to the article:
https://www.heise.de/select/ix/2018/8/1533352444905693)

  Also, just before ApacheCon we also had our first PLC4X Meetup where
  several current contributors as well as very interested new people were
  present.

  Also did we successfully vote in our first two new committers and PPMC
  members.

  *   Julian Feinauer (pragmatic industries)
  *   Andrey Skorikov (codecentric)

  Finally just before finishing this report we also finished our first
  release:
  Version 0.1.0

  Our mailing list subscriptions went up another 9 to currently 38
  subscribers.
  Our Twitter followers increased by 18 to 59 followers.

  On GitHub we now have 24 “Stars” and 14 “Forks”

  Business interest has increased dramatically as more and more companies
  are signalling their willingness to try out PLC4X and some are currently
  even in the transition phase of porting their products to PLC4X.

How does the podling rate their own maturity?

  We have a mix of new participants and experienced Apache people involved.
  So far, the new participants have shown great willingness and success in
  adopting the Apache Way.
  However, we still need to continue: the on-boarding increasing the
  diversity of the team.
  After our first official release, we will now fine-tune this release
  process and try to educate other people on the team to also be able to do
  releases.

Have your mentors been helpful and responsive or are things falling
through the cracks? In the latter case, please list any open issues
that need to be addressed.

  Yes. All of our mentors have been responsive and have helped.

Signed-off-by:

  [ ](plc4x) Greg Trasuk
     Comments:
  [X](plc4x) Justin Mclean
     Comments:
  [X](plc4x) Stefan Bodewig
     Comments:

IPMC/Shepherd notes:

--------------------
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. Increase diversity of committers

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 is moving towards graduation: restarted discussion on
  graduation and started to complete the items required for this step
  * We welcome new users and contributors from Semantic Web Company. A CCLA
  from Semantic Web Company is being worked on.
  * Received multiple logo proposals. Community discussed and voted a new
  logo
  * We lost two mentors, but the remaining two mentors are very responsive
  and helpful

How has the project developed since the last report?

  * Changed RdfFileInputTool to accept multiple input paths, so it can load
  RDF data from multiple folders
  * Changed from guava's iterators to Java collection's iterators to avoid
  versioning issues due to the recent change in Guava's
  Iterator.emptyIterator visibility
  * Minor improvements to code and documentation

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:

   2018-03-04

When were the last committers or PPMC members elected?

  * PPMC member Caleb Meier elected on Jan 3rd, 2017

Have your mentors been helpful and responsive or are things falling
through the cracks? In the latter case, please list any open issues
that need to be addressed.

  * Our two remaining mentors are very helpful and responsive.

Signed-off-by:

  [x](rya) Josh Elser
     Comments: Discussion on dev@ that may be missed here, interest from
     some new contributors ("semantic web company") seems to be genuine and
     helps bolster diverse podling population. Hoping that graduation will
     push to completion this  time and not run out of steam as the last
     times did.
  [x](rya) Billie Rinaldi
     Comments:

IPMC/Shepherd notes:

--------------------
SensSoft

Apache SensSoft is a generalized user behavioral logging platform for web
pages and thin-client applications

Apache SensSoft has been incubating since 2016-07-13.

Three most important issues to address in the move towards graduation:

  1. Extending release process to other parts of the SensSoft software
  stack.
  2. Grow the Apache SensSoft (Incubating) Committer/Community Base.
  3. Complete the issues highlighted at the SensSoft Roadmap
  https://cwiki.apache.org/confluence/display/SENSSOFT/Roadmaps

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

  The community will begin the process of voting on a new project name this
  month.

How has the community developed since the last report?

  Several community members have started new employment opening
  opportunities for community growth. No new community members have come
  onboard.

  How has the project developed since the last report?

  Project maturity roadmaps (Wiki) and version release plans (JIRA)
  continue to be maintained.

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
  [X] Nearing graduation
  [ ] Other:

Date of last release:

  2018-03-14

When were the last committers or PPMC members elected?

  Arthi Vezhavendan was added to PPMC and Committer base on 2017-01-24

Have your mentors been helpful and responsive or are things falling
through the cracks? In the latter case, please list any open issues
that need to be addressed.

Signed-off-by:

  [ ](senssoft) Paul Ramirez
     Comments:
  [X](senssoft) Lewis John McGibbney
     Comments: Hopefully this report has been submitted just in time for
     the deadline.
     The SensSoft Podling is coping well under pressing conditions with an
     ongoing activity which seeks to essentially rebrand the podling. Once
     we find a new identity,
     I will be working to drive the SensSoft towards graduation. I have
     also expressed my desire to onboard one other mentor. Hopefully the
     IPMC has the capacity to rise to that request.
  [X](senssoft) Chris Mattmann
     Comments: Approved.

IPMC/Shepherd notes:

--------------------
ServiceComb

ServiceComb is a microservice framework that provides a set of tools and
components to make development and deployment of cloud applications easier.

ServiceComb has been incubating since 2017-11-22.

Three most important issues to address in the move towards graduation:

  1. Community building:
  ServiceComb is building a health community by making the decision in
  Consensus way and the committer, PPMC member can present themselves
  independently.
  Please check out the Apache maturity model assessment for more information

https://cwiki.apache.org/confluence/display/SERVICECOMB/Apache+Maturity+Mode
l+Assessment+for+ServiceComb

  2. Project visibility:
  Now ServiceComb project is wildly used not only in Huawei, but also in
  20+ other companies.
  ServiceComb have the developer team from Huawei, Talend, Stealth,
  Hyperpilot, RedHat, JingDong,Tencent, Syswin, PICC, Changhong, Cainiao.

  3. Trademark transfer:
  Huawei is actively transfer the trade mark, and the VP of Market is happy
  about that.

https://lists.apache.org/thread.html/4dd251a1833e09d64f608546f18dea8d6c4192a
bf6f9a39fd34743a4@%3Cprivate.servicecomb.apache.org%3E

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?(2018-07)
  * The community get the third release out:
    service-center 1.0.0, java-chassis 1.0.0
  * The community is planning a meetup in Shanghai at Oct 12.

How has the project developed since the last report? (2018-07)
  * Java Chassis merged with 100 PRs by 15 contributors.
  * Service Center merged with 50 PRs by 5 contributors .
  * Saga merged with 60 PRs by 14 contributors.
  * 240 emails sent by 21 people, divided into 34 topics. (2018-07)
  * 202 emails sent by 30 people, divided into 37 topics.(2018-08)
  * 228 emails sent by 41 people, divided into 44 topics  (2018-09)

How would you assess the podling's maturity?
  "Graduate Apache ServiceComb (incubating) as a TLP" discussion was
  started:
https://lists.apache.org/thread.html/3fe85fb22cd1fd2c4e4a2370c03a453448a1ea1
2735d1e136cae6e79@%3Cdev.servicecomb.apache.org%3E
  The vote of "Graduate Apache ServiceComb (incubating)"
https://lists.apache.org/thread.html/233f234981b0f351681018f03061478920899fc
7143c9484c4bab726@%3Cdev.servicecomb.apache.org%3E
  The vote result of "Graduate Apache ServiceComb (incubating)"
https://lists.apache.org/thread.html/53f73695f8b504d1ed52e837cff9b8877e98c8a
9c88668fc25188aca@%3Cdev.servicecomb.apache.org%3E

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:

  2018-08-03 Java Chassis 1.0.0
  2018-08-03 Service Center 1.0.0

When were the last committers or PPMC members elected?
  2018-09-10 All the committer are added PPMC member as the vote result of
  graduation
  2018-09-05 Lin Zhinan, Yang Bo  was elected as committer.
  2018-07-25 Feng Zheng was elected as committer.

Have your mentors been helpful and responsive or are things falling through
the cracks?
In the latter case, please list any open issues that need to be addressed.

  Yes, they have been very helpful as always. They gave us lot of helps
  during the graduation process recently.

Signed-off-by:

  [X](servicecomb) Roman Shaposhnik
     Comments: the graduation vote has passed, this is likely to be the
     last Incubator report
  [X](servicecomb) Jean-Baptiste Onofre
     Comments: We are now pretty close to the graduation. Resolution is
     almost ready.
  [X](servicecomb) Timothy Chen
     Comments:

IPMC/Shepherd notes:

--------------------
Warble

Warble has been incubating since 2018-06-11

Warble is a distributed endpoint monitoring solution where the agent is
hosted on your own hardware.

Three most important issues to address in the move towards graduation.
  1. Engage initial committers.
  2. Set core design and feature set, avoid creep of new features before
  the core is complete.
  3. Expand committers and community

Any issues that the Incubator PMC or ASF Board might wish/need to be aware
of:
  none

How has the community developed since the last report?
  We've added 1 initial member and had to drop 3 as they haven't submitted
  their ICLA.

How has the project developed since the last report?
  Design and documentation have moved forward. Trying to
  on-board more contributors.

How would you assess the podling's maturity?
  Progress has been slow, but there is still interest and motivation to
  get this project moving toward an initial release.

  [X] Initial setup
  [ ] Working towards first release
  [X] Community building
  [ ] Nearing graduation
  [X] Other: Building initial designs and re-writing donated code

Date of last release:
  N/A

When were the last committers or PPMC members elected?
  N/A

Have your mentors been helpful and responsive or are things falling
through the cracks? In the latter case, please list any open issues
that need to be addressed.
  Mentors have been helpful in answering our questions and navigating
  the incubator. Due to time constraints, there have been no questions
  or processes to figure out this month really.

Signed-off-by:

  [ ](warble) Daniel Takamori
     Comments:

--------------------
Zipkin

Zipkin is a distributed tracing system. It helps gather timing data needed
to
troubleshoot latency problems in microservice architectures.

Zipkin has been incubating since 2018-08-29.

Three most important issues to address in the move towards graduation:

  1. Finalize committers ICLAs
  2. Migrate GitHub repositories
  3. Migrate website

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 workshop has been held on 20th of September, 2018. The existing
  community is slowly getting used to the new Zipkin home.

How has the project developed since the last report?

  The Confluence space has been created and large amount of content already
  published, including designs, features and workshops. The discussions
  around establishing the CI/CD processes are ongoing but currently on hold
  due to Git repositories migration.

How would you assess the podling's maturity?
  Currently in progress are conversations to finalize the IP rights and Git
  repository migration. The
  number of core PPMC members have been added, a few more ICLAs are on the
  way.

  [X] Initial setup
  [ ] Working towards first release
  [ ] Community building
  [ ] Nearing graduation
  [ ] Other:

Date of last release:

  N/A

When were the last committers or PPMC members elected?

  2018-09-24

Have your mentors been helpful and responsive or are things falling
through the cracks? In the latter case, please list any open issues
that need to be addressed.

  The team is quite happy with mentors involvement so far.

Signed-off-by:

  [X](zipkin) Michael Semb Wever
     Comments:
  [X](zipkin) John D. Ament
     Comments: The podling is struggling to get their code repos moved over
     to the ASF.  Presently blocked on a requirement to have all ICLAs and
     SGA present,  which isn't the norm for existing open source
     (non-commercially donated) entities.  Granted, we do this very
     infrequent but it may be time for the foundation to formalize this
     process a bit better so that other podlings don't run into similar
     issues.
  [X](zipkin) Willem Ning Jiang
     Comments:
  [X](zipkin) Andriy Redko
     Comments:

IPMC/Shepherd notes:

  • No labels