/!\ FINAL /!\

Incubator PMC report for May 2017

Timeline

Wed May 03

Podling reports due by end of day

Sun May 07

Shepherd reviews due by end of day

Sun May 07

Summary due by end of day

Tue May 09

Mentor signoff due by end of day

Wed May 10

Report submitted to Board

Wed May 17

Board meeting

Shepherd Assignments

Drew Farris

S2Graph

Drew Farris

SystemML

John Ament

DistributedLog

John Ament

iota

Justin Mclean

Ratis

P. Taylor Goetz

BatchEE

P. Taylor Goetz

Edgent

P. Taylor Goetz

Joshua

Timothy Chen

Impala

Timothy Chen

Slider

Timothy Chen

Toree

[none]

Blur

[none]

Fluo

[none]

Gobblin

[none]

Guacamole

[none]

HORN

[none]

MXNet

[none]

PredictionIO

[none]

Sirona

[none]

Tamaya

[none]

Unomi

[none]

Weex

Report content

Incubator PMC report for May 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 presently 59 podlings incubating.  Podlings executed seven releases
in April, including the first release from ODF Toolkit in a long time.  One
IPMC member stepped down in April, and one new member joined.

* Community

  New IPMC members:

  - Larry McCay
  - Ryan Blue

  People who left the IPMC:

  - Marvin Humphrey

* New Podlings

  - None

* Retired Podlings

  - Pirk

* Podlings that failed to report, expected next month

  - Gobblin
  - Horn
  - iota
  - Joshua
  - Sirona
  - Slider
  - Tamaya
  - Toree

* Graduations

  The board has motions for the following:

  - None

* Releases

  The following releases entered distribution during the month of
  April:

  - 2017-04-01 Apache Guacamole    0.9.12
  - 2017-04-02 Apache Gossip       0.1.2
  - 2017-04-10 Apache ODF Toolkit  0.6.2
  - 2017-04-13 Apache Mnemonic     0.6.0
  - 2017-04-24 Apache PredictionIO 0.11.0
  - 2017-04-28 Apache Gearpump     0.8.3
  - 2017-04-28 Apache Juneau       6.2.0

* Legal / Trademarks

  - Podlings struggle with their first releases.  There has been growing asks
    to revisit the binaries in source releases policy as a number of newer
    build tools rely on including a small JAR to ease the build process.
    Several IPMC members have voiced interest in following up with legal in
    this area.

* Infrastructure

  - There were small hiccups with the Metron graduation that may need some
    refinement between IPMC, Infrastructure and Trademarks/Press.
  - The other graduations and Pirk's retirement went smoothly.
  - In addition, thanks to some strong collaboration with Infrastructure we
    now have a podlings [AT] incubator DOT apache DOT org to better
    communicate with the podlings as a whole.

* Miscellaneous

  - The new podling logo has been announced to all podlings.  Some have
    already implemented the new logo and it looks much better on websites.
  - The new incubator website is being worked on, slowly.  We may start by
    simply porting the existing content and then refining policies.
  - We have refined our processes to communicate out that rosters should be
    maintained in Whimsy going forward.  A formal announcement should happen
    by ApacheCon.

* Credits

  - Report Manager: John D. Ament

----------------------------------------------------------------------
                       Table of Contents
BatchEE
Blur
DistributedLog
Edgent
Fluo
Guacamole
Impala
MXNet
PredictionIO
Ratis
S2Graph
SystemML
Unomi
Weex

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

--------------------
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. Update documentation
  2. Better communicate around the project (and its independance of TomEE)
  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?

Not much but since there is not yet a new version of the spec it was expected.

How has the project developed since the last report?

Not much but since there is not yet a new version of the spec it was expected.

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?

  2015-12-02

Signed-off-by:

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

--------------------
Blur

Blur is a search platform capable of searching massive amounts of data
in a cloud computing environment.

Blur has been incubating since 2012-07-24.

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

  We have started a discussion thread to talk about retiring Blur due to lack of growth and activity.


How has the community developed since the last report?

  Subscriptions: user@ - 61[0]; dev@ - 76[-1]

How has the project developed since the last report?

  None

How would you assess the podling's maturity?
Please feel free to add your own commentary.

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

Date of last release:

  2014-07-29

When were the last committers or PMC members elected?

  2014-07-28

Signed-off-by:

  [ ](blur) Doug Cutting
     Comments:
  [X](blur) Patrick Hunt
     Comments:
  [ ](blur) Tim Williams
     Comments:

--------------------
DistributedLog

DistributedLog is a high-performance replicated log service. It offers
durability, replication and strong consistency, which provides a fundamental
building block for building reliable distributed systems.

DistributedLog has been incubating since 2016-06-24.

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

  1. Continue to grow the community, and increase diversity of community.
  2. Improve documentation, including documentation of project and processes.
  3. Successful 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?


1. community

- Sijie gave a talk about DistributedLog at Strata+Hadoop San Jose.
- The DistributedLog paper is accepted at ICDE 2017.
- Leigh Stewart gave a presentation about DistributedLog at ICDE.

2. 44 people subscribed to dev mail list, 
   8 improvement proposal in progress,
   and 72 open issues.

How has the project developed since the last report?


- We have released the first Apache version : 0.4.0-incubating on April 25.
- We start the work on release 0.5.0-incubating.


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-04-25

When were the last committers or PPMC members elected?



Signed-off-by:

  [ ](distributedlog) Flavio Junqueira
     Comments:
  [ ](distributedlog) Chris Nauroth
     Comments:
  [X](distributedlog) Henry Saputra
     Comments:

--------------------
Edgent

Apache Edgent is a programming model and micro-kernel style runtime 
that can be embedded in gateways and small footprint edge devices enabling
local, real-time, analytics on the continuous streams of data coming
from equipment, vehicles, systems, appliances, devices and sensors of 
all kinds (for example, Raspberry Pis or smart phones). Working in 
conjunction with centralized analytic systems, Apache Edgent provides 
efficient and timely analytics across the whole IoT ecosystem: from the 
center to the edge.

Edgent has been incubating since 2016-02-29.

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

  1. Create and expand a diverse community of contributors and committers
     around the Edgent project.
  2. Checking of all items in the project's Maturity Model 
     (https://cwiki.apache.org/confluence/display/EDGENT/Apache+Maturity+Model+For+Edgent)
  3. Although not required to graduate, it might be good to attract at 
     least another independent committer/ppmc member.

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?

  * Three speakers will present their experience with Edgent at the 
    ApacheCon North America in May 2017:

    * Video Analytics at the Edge: Fun with Apache Edgent, OpenCV and a 
      Raspberry Pi - Dale LaBossiere and William Marshall, ppmc members and 
      committers for Edgent.

    * Having fun with Raspberry(s) and Apache Projects - Jean-Frederic Clere.

  * Since the last report, 2 individuals have subscribed to the Apache 
    Edgent dev mailing list.  There were 65 subscribers as of the end of 
    April 2017.

How has the project developed since the last report?

  * Release 1.1.0 of Edgent as part of the Apache incubator was created on 
    17 March 2017. This represented 26 bug fixes and improvements, 
    including more usage examples, application autoSubmit capability to 
    IotProvider, support for publishing WIoTP device events using HTTP, 
    and many others.
  * According to JIRA, 33 new issues were added to the project and 81 
    issues have been resolved or closed between February 2017 and April 2017.

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-03-17

When were the last committers or PPMC members elected?

  In May 2016, we added two new committers and PPMC members, 
  Kathy Saunders and Queenie Ma.

Signed-off-by:

  [ ](edgent) Daniel Debrunner
     Comments:
  [x](edgent) Luciano Resende
     Comments:
  [ X ](edgent) Katherine Marsden
     Comments:  Great product. Great Apache way attitude. Everything in place,
     but just need to focus community growth and diversity.  I am hoping the
     Apachecon presentations will help bring this great product and project on
     the radar.
  [ ](edgent) Justin Mclean
     Comments:

IPMC/Shepherd notes:



--------------------
Fluo

Fluo is a distributed system for incrementally processing large data sets
stored in Accumulo.

Fluo has been incubating since 2016-05-17.

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

  1. Make an additional release of Fluo and Fluo Recipes.
  2. Vote in a new committer.
  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?

  A non-committer has made multiple code contributions to the project recently.
  We are discussing a release soon.

How has the project developed since the last report?

  A few exciting new features were added that will be in the next release :

   * Writing Fluo applications is now easier.  Users only need to configure
     a single observer provider class, instead of configuring each observer 
     class separately.  This change makes it possible to use Java 8 Lambdas!
   * The scalability of Fluo was greatly improved by changing how it scans for
      notifications.  The work to find notifications was decreased from O(N^2)
      to O(N) where N is the number of nodes.
   * Multiple internal performance improvements were made.

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-10-28

When were the last committers or PPMC members elected?

 Never


Signed-off-by:

  [x](fluo) Billie Rinaldi
     Comments:
  [x](fluo) Drew Farris
     Comments:
  [x](fluo) Josh Elser
     Comments: Fluo is comprised of ASF "veterans" -- they operate themselves well. That "learn the Apache way"
               part of incubation was there from day #1 because they already "got it". However, they continue
               to struggle to attract new talent (it is niche software). There have been some publicity efforts from the devs, but
               growing the podling beyond themselves has not yet happened nor is on the horizon, IMO.

--------------------
Guacamole

Guacamole is an enterprise-grade, protocol-agnostic, remote desktop gateway.
Combined with cloud hosting, Guacamole provides an excellent alternative to
traditional desktops. Guacamole aims to make cloud-hosted desktop access
preferable to traditional, local access.

Guacamole has been incubating since 2016-02-10.

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

  1. https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-120
  2. Call community graduation VOTE
  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 activity on the mailing lists is strong and increasing, with the
  user@ list currently receiving an average of 164 posts per month. Overall:

          Report    |       Period       | Avg. posts (per month)
      --------------+--------------------+------------------------
       May 2016 (1) | (START) .. 2016-04 | 0 (Not yet migrated)
       Aug 2016 (2) | 2016-05 .. 2016-07 | 90
       Nov 2016 (3) | 2016-08 .. 2016-10 | 108
       Feb 2017 (4) | 2016-11 .. 2017-01 | 129
       May 2017 (5) | 2017-02 .. 2017-04 | 164

How has the project developed since the last report?

  The project has fallen into a nice rhythm with respect to releases and has
  gone through two additional releases since last report: 0.9.11-incubating
  and 0.9.12-incubating.

  The project website has been updated with documentation covering release
  procedures, the acceptance of new committers, and handling of code review
  via pull requests. Links to relevant ASF resources for PPMC members and
  committers have also been added.

  The development community continues to be engaged on the mailing lists, and
  a new committer, Nick Couchman, has been brought onto the project as of
  2017-02-09.

  Recent discussion on the mailing lists regarding graduation readiness has
  been positive. The podling status page for Guacamole has been brought
  up to date, and the suitable name search issue has been created:

    https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-120

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-04-01 (0.9.12-incubating)

When were the last committers or PPMC members elected?

  The following committers have been elected since Guacamole began incubation:

    * Nick Couchman - 2017-02-09
    * Frode Langelo - 2016-04-03

  As of the VOTE on 2016-12-09, all committers are implicitly members of the
  PPMC.

Signed-off-by:

  [ ](guacamole) Jean-Baptiste Onofre
     Comments:
  [ ](guacamole) Daniel Gruno
     Comments:
  [X](guacamole) Jim Jagielski
     Comments: So far, a well run PPMC with minimal issues.
  [ ](guacamole) Greg Trasuk
     Comments:

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

Impala

Impala is a high-performance C++ and Java SQL query engine for data stored in
Apache Hadoop-based clusters.

Impala has been incubating since 2015-12-03.

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

  1. Growth of the developer community
  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?

  There have been 267 Commits:
    git log --format='%ci' | grep -cE '2017-0(2|3|4)'

  42 of those commits were by non-committers:
    git log --format='%ae %ci' | grep -E '2017-0(2|3|4)' | cut -d ' ' -f 1 | sort | uniq -c | sort -n

  There were 114 emails to the user list. Of the top nine
  participants, six were not committers:
    https://lists.apache.org/trends.html?user@impala.apache.org:dfr=2017-2-1|dto=2017-4-30:

  There are six new committers:
    https://lists.apache.org/list.html?dev@impala.apache.org:dfr=2017-2-1|dto=2017-4-30:%22has%20invited%22

  Two new contributors have announced plans to take on large
  development efforts (JSON support and ppc64le support).

How has the project developed since the last report?

  Two of the "three most important issues to address in the move
  towards graduation" from our last report in February have been
  completed: The bug tracker was transitioned to issues.apache.org,
  and the documentation now describes Apache Impala specifically, not
  any non-Apache extensions. The documentation has also been posted to
  http://impala.incubator.apache.org/docs/build/html/index.html and
  http://impala.incubator.apache.org/docs/build/impala.pdf.

  Many commits have landed since our last report towards increasing
  the performance of metadata.

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:

  Once the developer community has grown a bit, Impala will be ready
  to contemplate graduation.

Date of last release:

  2017-01-22

When were the last committers or PPMC members elected?

  2017-04-24

Signed-off-by:

  [X](impala) Tom White
     Comments:
  [X](impala) Todd Lipcon
     Comments:
  [X](impala) Carl Steinbach
     Comments:
  [X](impala) Brock Noland
     Comments:


--------------------
Apache MXNet

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.

*   A list of the three most important issues to address in the move
towards graduation.

1.  Migrate code(GitHub) and website to Apache.     
2.  Grow the community:
2.1 Improving documentation including APIs & Tutorials.
2.2 Improving user-experience, for example improved error messages.
3   Establish a dependable, Apache-way consistent release process.
3.1 Features: New operators requested by user community.  
              Accelerate performance on CPUs and GPUs.

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

Code and website have taken time to get moving on. The plan is to discuss 
these with Apache Infra at ApacheCon and then get the code migrated in May.

*   How has the community developed since the last report.

1. The community was engaged for contributions to API documentation and
tutorials.
2. Slack channels have been created for the community to contribute
discussions to (though they need to move to the ASF Slack channel that 
was recently created).
3. In the last month, excluding merges, 51 authors have pushed 165 commits
to master and 180 commits to all branches. On master, 502 files have
changed and there have been 26,246 additions and 12,188 deletions. Count of
Closed Issues = 62, Count of New Issues = 146, Count of Merged Pull
Requests = 161, Count of Proposed Pull Requests = 27.

*   How has the project developed since the last report.

On GitHub:

1. The API Documentation has improved.
2. More features (e.g. operators) requested by the user community has been added.
3. Hardware acceleration like cuDDN6 integration and MKL ML package
integration was completed.
4. A new Perl language binding for MXNet was added.
5. Apache MxNet talk at Apache BigData North America on May 18, 2017 

*   How does the podling rate their own maturity.

Maturity = Low. Initial setup and adjusting community to Apache-style interactions.

Date of last release:

  No @Apache release yet.

When were the last committers or PPMC members elected?

  No new committers added yet.

Signed-off-by:

  [ ](mxnet) Sebastian Schelter
     Comments:
  [X](mxnet) Suneel Marthi
     Comments:  
  [ ](mxnet) Markus Weimer
     Comments:
  [X](mxnet) Henri Yandell
     Comments: Starting to see movement on moving things to Apache. 
               The dev@ list is beginning to see traffic.

--------------------
PredictionIO

PredictionIO is an open source Machine Learning Server built on top of state-
of-the-art open source stack, that enables developers to manage and deploy
production-ready predictive services for various kinds of machine learning
tasks.

PredictionIO has been incubating since 2016-05-26.

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

  1. Establish a formal release schedule and process, allowing for
dependable release cycles in a manner consistent with the Apache way.
  2. Grow the community to establish diversity of background.
  3. Transition remaining former PredictionIO users from google-groups to
ASF mailing lists.

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 have published the first release (0.11.0) that incorporates major
changes by non-committer contributors.
  2. There are new tutorials and online classes for PredictionIO by third
parties.
  3. The user mailing list has more activities than last report.
  4. GitHub stars keep growing.

How has the project developed since the last report?

  1. Released version 0.11.0 with major contributions from the
non-committer community.
  2. Established PMC documentation regarding release processes.
  3. In the process of preparing for top level graduation discussion.

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

  Apache PredictionIO 0.11.0-incubating on 2017-04-25

When were the last committers or PMC members elected?

  Naoki Takezoe was elected as committer and PMC member on Apr 28, 2017,
pending acceptance of invitation and status change.
  Shinsuke Sugaya was elected as committer and PMC member on Apr 28, 2017,
pending acceptance of invitation and status change.
  Takahiro Hagino was elected as committer and PMC member on Apr 28, 2017,
pending acceptance of invitation and status change.
  Takako Shimamoto was elected as committer and PMC member on Apr 28, 2017,
pending acceptance of invitation and status change.
  Sara Asher was elected as product manager and JIRA administrator on Apr
30, 2017.

Signed-off-by:

  [X](predictionio) Andrew Purtell
     Comments: The podling is planning a graduation vote soon. I have expressed
         concerns regarding community growth. There are several frequent contributors
         who were not invited to become committers until I asked about it. That said,
         I think this podling is maturing and nearing graduation. 
  [ ](predictionio) James Taylor
     Comments:
  [ ](predictionio) Lars Hofhansl
     Comments:
  [x](predictionio) Luciano Resende
     Comments:
  [ ](predictionio) Xiangrui Meng
     Comments:
  [ ](predictionio) Suneel Marthi
     Comments:


--------------------
Ratis

Ratis is a java implementation for RAFT consensus protocol

Ratis has been incubating since 2017-01-03.

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

  1. Setup jenkins.
  2. Make the first release. Release candidate for 0.1.0-alpha release is out for voting.
  3. Add new committers.

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?

  - 3 new contributors joined. Total 29 contributors now.
  - Ratis is now being used for a feature in Apache Hadoop, in a branch. That adds to user community. 

How has the project developed since the last report?

  - Ratis is now being used for a feature in Apache Hadoop, in a branch. That adds to user community.
  - Release candidate for 0.1.0-alpha release is out for voting.
  - 3 new contributors
  - 18 new commits

How would you assess the podling's maturity?
Please feel free to add your own commentary.

  [ ] Initial setup - - Need jenkins setup, and documentation
  [ ] Working towards first release - Release candidate out for voting.
  [ ] Community building - 3 new contributors. Apache Hadoop community experimenting with the snapshot release.
  [ ] Nearing graduation
  [ ] Other:

Date of last release:

  - None

When were the last committers or PPMC members elected?
  
  - Initial set of committers/PPMC.
  

Signed-off-by:

  [ ](ratis) Chris Nauroth
     Comments:
  [ ](ratis) Devaraj Das
     Comments:
  [x](ratis) Jakob Homan
     Comments:
  [ ](ratis) Uma Maheswara Rao G
     Comments:


--------------------
S2Graph

S2Graph is a distributed and scalable OLTP graph database built on Apache
HBase to support fast traversal of extremely large graphs.

S2Graph has been incubating since 2015-11-29.

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

  1. Make a second release.
  2. Attract more users and contributors.
  3. Build the developer community in both size and diversity.

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?

  * Mailing lists have been quiet.
    - one inquery on full text search feature support.

How has the project developed since the last report?

  * Development has been quiet.
    - Working on Integration with Apache TinkerPop3
      - StructureStandardSuite has been passed. 
      - ProcessStandardSuite has been begun. 325/582 passed, 257 failed.

  * Issues resolved/created: 0/1

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

When were the last committers or PPMC members elected?

  None

Signed-off-by:

  [ ](s2graph) Andrew Purtell
     Comments:
  [ ](s2graph) Seetharam Venkatesh
     Comments:
  [X](s2graph) Sergio Fernández
     Comments: The podling struggles to get out of the company that originated 
               the project and build a community.

IPMC/Shepherd notes:

    Drew Farris (shepherd): No apparent commit activity since December and very 
       little other activity on the mailing list. One mentor active. 

--------------------
SystemML

SystemML provides declarative large-scale machine learning (ML) that aims at
flexible specification of ML algorithms and automatic generation of hybrid
runtime plans ranging from single node, in-memory computations, to distributed
computations such as Apache Hadoop MapReduce and Apache Spark.

SystemML has been incubating since 2015-11-02.

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

  1. Grow SystemML community: increase mailing list activity,
   increase adoption of SystemML for scalable machine learning, encourage data
   scientists to adopt DML algorithm scripts, respond to user feedback to
   ensure SystemML meets the requirements of real-world situations, and present
   talks about SystemML.
  2. Continue to produce releases.
  3. Increase the diversity of our project's contributors and committers.

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?
 Our mailing list from February through April had 350 messages on a variety
 of topics. We gained 1 new contributor to the project since February 1. On
 GitHub, the project has been starred 487 times and forked 184 times.

How has the project developed since the last report?
 The main project has had 334 commits since February 1. 112 pull requests have
 been created since February 1, and 103 pull requests have been closed. Since
 February 1, 348 issues have been reported on our JIRA site and 249 of these
 have been resolved.

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-02 (version 0.13.0-incubating)

When were the last committers or PPMC members elected?
  2017-05-01 Felix Schüler (PPMC)

Signed-off-by:

  [x](systemml) Luciano Resende
     Comments:
  [X](systemml) Henry Saputra
     Comments:
  [ ](systemml) Patrick Wendell
     Comments:
  [ ](systemml) Reynold Xin
     Comments:
  [ ](systemml) Rich Bowen
     Comments:

IPMC/Shepherd notes:

    Drew Farris (shepherd): Healthy activity on the mailing lists. 
       Two mentors active. Looking good.


--------------------
Unomi

Unomi is a reference implementation of the OASIS Context Server specification
currently being worked on by the OASIS Context Server Technical Committee. It
provides a high-performance user profile and event tracking server.

Unomi has been incubating since 2015-10-05.

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

  1. New releases with extended tests and updates of used/included projects
     (Karaf, Cellar, ...)
  2. Grow up both dev and user communities. Encourage new people on the
     projects, increasing mix of features and bug fixes.

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 expect traction around the coming release and new updated on the
  website (factual use cases).
  
  Some Unomi committers will be present during ApacheCon. We plan some
  informal discussion about Unomi and next major steps.

How has the project developed since the last report?

  After the 1.1.0-incubating release, we are now preparing 1.2.0-incubating
  release. 

  We improved the tests coverage, including performance benchmark (tests
  have been performed with 5M of profiles, and 35M events for instance).

  We also plan to move 1.x series on a dedicated branch and update master to
  2.x, including major third parties updates.

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-10-03

When were the last committers or PMC members elected?

  2017-01-23




How would you assess the podling's maturity?
Please feel free to add your own commentary.

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

Signed-off-by:

  [ ](unomi) Bertrand Delacretaz
     Comments:
  [X](unomi) Jean-Baptiste Onofre
     Comments:

IPMC/Shepherd notes:



--------------------
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. First Release while in Incubator.

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

  We are worried that only 1 mentor is actively helping us, as this will put
  more burden on the rest of the Incubator to approve our releases.
  Especially, most of active committers are not good at dealing with
  license-related problem.

How has the community developed since the last report?

  * We voted in 3 new committer:TianYi Ma, Tancy and HaiBo Song.
  * There are 90+ new forks and 700+ new stars since last report.
  * We have encouraged people to discuss more in the JIRA and dev
     mail list. Up to now, 30 issues are reported on JIRA and 25 of them
      are resovled. 
  * We have redirect github's mails to the commits mail list to have a 
      clear overview of our activity  in the dev mail list. 

How has the project developed since the last report?

  * We are trying to release 0.12 this month. Both two RCs were failed due
    to the license issue. This is major issue of project.

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?
TianYi Ma,  5 April 2017
Tancy, 18 April 2017
HaiBo Song, 24 April 2017



Signed-off-by:

  [ ](weex) Luke Han
     Comments:
  [ ](weex) Willem Jiang
     Comments:
  [ ](weex) Stephan Ewen
     Comments:
  [x](weex) Niclas Hedhman
     Comments: Technical development and sheer momentum is still very high,
     and no concerns in that area. The move of GitHUb notifications to
     commits@ makes dev@ a more pleasant space. But I still have concerns that
     a lot of discussions of what to do happens in office or other channels.

May2017 (last edited 2017-05-12 01:03:25 by johndament)