/!\ FINAL /!\

Incubator PMC report for December 2015

Timeline

Wed December 02

Podling reports due by end of day

Sun December 06

Shepherd reviews due by end of day

Sun December 06

Summary due by end of day

Tue December 08

Mentor signoff due by end of day

Wed December 09

Report submitted to Board

Wed December 16

Board meeting

Shepherd Assignments

Drew Farris

Cotton

John Ament

Taverna

John Ament

Unomi

Justin Mclean

MRQL

P. Taylor Goetz

Atlas

P. Taylor Goetz

MADlib

P. Taylor Goetz

Zeppelin

Timothy Chen

Myriad

Timothy Chen

Sirona

Timothy Chen

Streams

Drew Farris

Brooklyn

[none]

CommonsRDF

[none]

Concerted

[none]

Corinthia

[none]

HAWQ

[none]

HORN

[none]

HTrace

[none]

Johnzon

[none]

Mynewt

[none]

Ranger

[none]

Ripple

[none]

Rya

[none]

SAMOA

[none]

Sentry

[none]

Singa

[none]

SystemML

[none]

Trafodion

[none]

Wave

[none]

log4cxx2

Report content

Incubator PMC report for December 2015

The Apache Incubator is the entry path into the ASF for projects and
codebases wishing to become part of the Foundation's efforts.

The Incubator continues to grow, reaching 50 podlings this month for the
first time since April 2012.

* Community

  New IPMC members:

  - Todd Lipcon

* New Podlings

  - Impala
  - Kudu
  - Metron
  - S2Graph
  - Torii (formerly proposed as Spark-Kernel)

* Graduations

  None this month.

* Releases

  The following releases entered distribution during the month of
  November:

  - 2015-11-10 Apache Kylin 1.1.1-incubating
  - 2015-11-14 Apache DataFu (incubating) 1.3.0
  - 2015-11-16 Apache Sirona 0.3-incubating
  - 2015-11-16 Apache Apex Malhar 3.2.0-incubating
  - 2015-11-17 Apache Zeppelin 0.5.5-incubating
  - 2015-11-24 Apache TinkerPop 3.1.0-incubating

  The Wave PPMC has approved a release candidate which hit general@incubator
  on November 3rd.  Over a month later, it only has one IPMC +1 vote.

  The Incubator has been much better about approving releases in a timely
  manner since new processes were negotiated in late 2013, but Wave's
  experience shows that there is room yet for improvement.

* IP Clearance

  - Nicholas Peltier donated the Sling Pipes module, which provides a set of
    bulk content transformation tools for Apache Sling.

  - S.A.S. Ubik-Ingenierie and Decathlon SA donated JMeter Dashboard/Report,
    which allows generation of a report for a Load Test at end of Load Test
    or on an existing CSV result file.

* Legal / Trademarks

  - The registered trademark for the retiring podling Ripple is still held
    by Blackberry.  As the small Ripple community prepares to relocate to
    Github, they are exploring obtaining permission to use the trademark in
    their new home.

  - The name for a proposed podling was changed from "OpenMiracl" to
    "Milagro" to avoid marketplace confusion with the current copyright
    owner, Miracl (formerly Certivox).

* Infrastructure

  - It was brought to light that podling websites can be accessed by
    "podling.apache.org" in addition to "podling.incubator.apache.org".  A
    discussion about what remedy to pursue is ongoing.

* Miscellaneous

  - Driven by several new incubation proposals, traffic on general@incubator
    was extremely high in November -- at 915 messages, second only to the
    colossal Open Office proposal month in June 2011 (2013 messages).

  - A lengthy discussion on CTR vs. RTC (commit-then-review vs.
    review-then-commit) took place on general@incubator.  The debate
    continues with regards to what commit policy the incoming Impala podling
    will adopt.

  - The Kudu and Impala incubation proposal VOTEs were both contended, with
    a handful of -1 votes -- something which has not happened at any time in
    recent memory.  The VOTEs passed because they were interpreted as
    "procedural" under ASF voting rules and thus subject to majority
    rule.  This has implications for how graduation votes are interpreted,
    since objections to graduation by individual IPMC members have at times
    been given significant weight by the Board when considering graduation
    recommendations.

  - The new Metron podling is seeded with an ALv2 codebase for which the
    existing community is dormant/unresponsive.  There is no guarantee that
    an SGA can be obtained from the current copyright holder.  We anticipate
    no legal problems with this, nor social problems, but some efforts are
    underway to pursue an SGA regardless.

  - The Ripple, Corinthia, and Cotton podlings are all retiring.

* Credits

  - Report Manager: Marvin Humphrey

-------------------- Summary of podling reports --------------------

* Still getting started at the Incubator

  - Concerted
  - Eagle
  - SystemML
  - Unomi

* Not yet ready to graduate

  No release:

  - HAWQ
  - HORN
  - HTrace
  - MADlib
  - Mynewt
  - Myriad
  - Rya
  - Trafodion
  - Wave

  Community growth:

  - Atlas
  - CommonsRDF
  - MRQL
  - Ranger
  - SAMOA
  - Singa
  - Streams
  - Taverna
  - Zeppelin

* Nearing graduation

  - Johnzon
  - Sentry

* Retired or considering retirement

  - Corinthia
  - Cotton
  - Ripple

* Did not report, expected next month

  - Sirona (2 months late)

* No Mentor signoff, to be resubmitted next month

  - log4cxx2

----------------------------------------------------------------------
                       Table of Contents
Atlas
CommonsRDF
Concerted
Corinthia
Cotton
Eagle
HAWQ
HORN
HTrace
Johnzon
MADlib
MRQL
Mynewt
Myriad
Ranger
Rya
SAMOA
Sentry
Singa
Streams
SystemML
Taverna
Trafodion
Unomi
Wave
Zeppelin

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

--------------------
Atlas

Apache Atlas is a scalable and extensible set of core foundational
governance services that enables enterprises to effectively and efficiently
meet their compliance requirements within Hadoop and allows integration with
the complete enterprise data ecosystem

Atlas has been incubating since 2015-05-05.

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

  1. Podling name search is pending
  2. Expand the community and add more committers

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

  * Everything seems to be smooth, nothing specific at this time.

How has the community developed since the last report?

  1. We have added a new Committer/PPMC to the project.
  2. The user/dev community show increasing interests. The average number of
     messages in a month is over 500 as compared to 400 from the previous
     report.
  3. A lot of new contributors have been added, about 21 since the last
     report.

How has the project developed since the last report?

  1. Some of the main limitations with type and entity mutations have been
     addressed and the dashboard has many more features added.
  2. We are preparing for the second release, 0.6-incubating by Dec 2015.
     This release should include about 85 jiras.
  3. A total of 76 issues were created and about 53 of them are resolved in
     Nov 2015.

Date of last release:

  * 2015-07-15 - 0.5.0-incubating

When were the last committers or PMC members elected?

  * Suma Shivaprasad was elected as a committer on 10/02/2015.

Signed-off-by:

  [ ](atlas) Arun Murthy
  [X](atlas) Chris Douglas
  [ ](atlas) Jakob Homan
  [ ](atlas) Vinod Kumar Vavilapalli

Shepherd/Mentor notes:



--------------------
CommonsRDF

Commons RDF is a set of interfaces and classes for RDF 1.1 concepts and
behaviours.  The commons-rdf-api module defines interfaces and testing
harness.  The commons-rdf-simple module provides a basic reference
implementation to exercise the test harness and clarify API contracts.

CommonsRDF has been incubating since 2015-03-06.

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

  1. Re-engage and grow the Commons RDF community base
  2. Work with key target communities (initially within Apache) to ensure
     Commons RDF meets potential user requirements and expectations towards
     next versions of the Commons API.

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?

  Sleeper community in the last months; just few mails and commits.

How has the project developed since the last report?

  Development has seen a drop in engagement across the board. Internal
  discussions about the scope and target audience/consumers has affected the
  community, loosing in the way one of the project founders and main contact
  with a primary target project. Therefore next months are critical to find
  the project fit or decide to wrap up this venture.  Some discussions in
  this direction are taking place: http://s.apache.org/SFA

  On a brighter note one thing for the CommonsRDF PPMC to consider is that
  in the beginning there was a small group of 5 core committers. Recently
  the number of subscribers to the dev@ list was 22. It is not all down and
  gloom. The PPMC has actually done pretty well in attracting new community
  to join the community ML.

Date of last release:

  2015-05-07

When were the last committers or PMC members elected?

  n/a (no PPMC or Committers have been elected yet)

Signed-off-by:

  [X](commonsrdf) Lewis John McGibbney
  [X](commonsrdf) Rob Vesse
  [X](commonsrdf) John D Ament
  [ ](commonsrdf) Gary Gregory

Shepherd/Mentor notes:

  John D. Ament (johndament):
  
    Podling activity still appears to be on the low side.  I hope that more
    releases may help get more visibility into the podling, but the active
    group is active enough.

--------------------
Concerted

Apache Concerted is a Do-It-Yourself toolkit for building in-memory data
engines.

Concerted has been incubating since 2015-10-14.

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

  1. First release
  2. Establish a consistent development process and release rhythm.
  3. Expanding the community and continuing to add new committers.

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?

  Latest Additions:

  * PMC addition:           NA
  * Contributor addition:   NA

  Issue backlog status since last report:

  * Created:   3
  * Resolved:  0

  Mailing list activity since last report:

  * @dev      32 messages
  * @issues   7 messages
  * @commits  1   messages

How has the project developed since the last report?

  - Project has been focused on getting the first release candidate
    ready.
  - Working on scripts to automate the release process for our first
    Apache Concerted release candidate.
  - Website is created and is under review before it is published.
  - Old Tests improved and new automated tests added.

Date of last release:

  - Working towards our first release candidate.

Signed-off-by:

  [X](concerted) Chris Nauroth
  [ ](concerted) Daniel Dai
  [x](concerted) Jake Farrell
  [x](concerted) Julian Hyde
  [ ](concerted) Lars Hofhansl

Shepherd/Mentor notes:



--------------------
Corinthia

Corinthia is a toolkit/application for converting between and editing common
office file formats, with an initial focus on word processing. It is
designed to cater for multiple classes of platforms - desktop, web, and
mobile - and relies heavily on web technologies such as HTML, CSS, and
JavaScript for representing and manipulating documents. The toolkit is
small, portable, and flexible, with minimal dependencies. The target
audience is developers wishing to include office viewing, conversion, and
editing functionality into their applications.

Corinthia has been incubating since 2014-12-08.

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

  [none]  The IPMC Vote to retire Corinthia was approved on 2015-11-19

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 effectively disbanded by withdrawal of the primary
  developers on 2015-09-05.  The community crisis mentioned on the
  2015-09-02 report was not resolved.

How has the project developed since the last report?

  Development ceased at the time of the last report.

Date of last release:

  2015-08-28 Release 0.1

When were the last committers or PMC members elected?

  2015-08-31 Gavin McDonald
  2015-06-12 Ian Cunningham

Signed-off-by:

  [ ](corinthia) Daniel Gruno
  [ ](corinthia) Jan Iversen
  [x](corinthia) Dave Fischer

Shepherd/Mentor notes:



--------------------
Cotton

Cotton is an Apache Mesos framework for running MySQL instances.

Shepherd/Mentor notes:

  Drew Farris (drew):

    Development on hold. The Cotton PPMC has called for a vote for
    retirement from the incubator as of 12/4/2015 with a 72 hour window for
    closure.

--------------------
Eagle

Apache Eagle is a real time Data Activity Monitoring Framework to
instantly identify access to sensitive data, recognize attacks/
malicious activity and block access in real time.

Eagle has been incubating since 2015-10-25.

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

  1. Infrastructure Migration: We moved the code to Apache Github,
     started using Apache JIRA for tracking purposes, Eagle external
     site transitioned to incubator and Jenkins projects to build binary
     and created docker images for easy installation.
  2. Expand the community, Increase dev list activity with new
     contributors.
  3. Existing committers are getting familiarized with the apache
     tools and process.

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

  Nothing urgent at this time. Our mentors have been helpful in
  guiding us thru various stages.

How has the community developed since the last report?

  1. All core contributors/committers have started working on the
     Apache repository.
  2. We presented about Apache Eagle in the Data governance meetup
     meeting (Topic: Apache Eagle - Secure your hadoop data). We received
     good feedback on the use cases and scalable design of Eagle.
  3. Dev community showed increasing interests. In Nov, there have been
     507 messages on dev@ mailing list.
  4. There were increased participation in the dev mailing list
     pertaining to new feature development and roadmap.

  The development community is very active in terms of new features,
  bugs closed etc. This month we are putting more emphasis on community
  development and getting the interests from developers in the hadoop
  ecosystem.

How has the project developed since the last report?

  1. Main features/improvements added include:
     a) Support for Docker [EAGLE-53]
     b) New design for Alert dashboard [EAGLE-29]
     c) Eagle internal metric framework design [EAGLE-50]
     d) Bug fixes & documentation improvement
  2. 58 new JIRAs filed, 25 resolved (In Nov 2015)
  3. 82 code commits (In Nov 2015)

Date of last release:

  We have not had a release yet.

When were the last committers or PMC members elected?

  No new committers/members from initial.

Signed-off-by:

  [x] (eagle) P. Taylor Goetz
  [x] (eagle) Amareshwari Sriramdasu
  [x] (eagle) Henry Saputra
  [x] (eagle) Julian Hyde
  [ ] (eagle) Owen O’Malley

Shepherd/Mentor notes:

  Julian Hyde (jhyde):
  
    Good activity and discussion, work is underway on meaningful features,
    and also some preparation for a release. They got late notice that a
    report was needed this month and sprang into action quickly to complete
    one.

--------------------
HAWQ

Apache HAWQ is a Hadoop native SQL query engine that combines the key
technological advantages of MPP database with the scalability and
convenience of Hadoop. HAWQ reads data from and writes data to HDFS
natively.  HAWQ delivers industry-leading performance and linear
scalability. It provides users the tools to confidently and successfully
interact with petabyte range data sets. HAWQ provides users with a complete,
standards compliant SQL interface.

HAWQ has been incubating since 2015-09-04.

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

  1. Produce our first Apache Release
  2. Expand the community, increase dev list activity and adding new
     contributors
  3. Infrastructure migration: create Jenkins projects that build HAWQ
     binary, source tarballs and docker images, and run feature tests
     including at least installcheck-good tests for each commit (HAWQ-127).

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

  Everything seems to be smooth, nothing urgent at this time.

How has the community developed since the last report?

  1. All core contributors/committers have started working on Apache
     repository
  2. One HAWQ Nest community meeting (topic: HAWQ architecture introduction)
  3. Both user & dev community show increasing interests. In Nov, there have
     been 438 messages on dev@ and 75 on user@, compared with 357 messages
     on dev@ and 21 messages on user@ in Oct.

How has the project developed since the last report?

  1. Main features/improvements added include:
     a) Support HA for libyarn [HAWQ-38]
     b) Dynamic statement level resource usage [HAWQ-47]
     c) Support Kerberos for libyarn [HAWQ-51]
     d) Dependent component version upgrade & Bug fixes & documentation
        improvement
  2. First release has been proposed and most issues have been finished (115
     issues resolved in the release). (<http://s.apache.org/T3P>)
     Left thing is to do the PPMC & IPMC voting)
  3. 85 new JIRAs filed, 74 resolved (In Nov 2015)
  4. 76 code commits (In Nov 2015)

Date of last release:

  We have not had a release yet.

When were the last committers or PMC members elected?

  No new committers/members from initial.

Signed-off-by:

  [X](hawq) Alan Gates
  [X](hawq) Konstantin Boudnik
  [ ](hawq) Justin Erenkrantz
  [ ](hawq) Thejas Nair
  [X](hawq) Roman Shaposhnik

Shepherd/Mentor notes:



--------------------
HORN

HORN is a neuron-centric programming APIs and execution framework for large-
scale deep learning, built on top of Apache Hama.

HORN has been incubating since 2015-09-04.

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

  1. Continue to build out API
  2. Continue to gain and attract contributors
  3. Produce a first Apache release

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

  Google's TensorFlow is getting a lot of media attention, but it's not
  entirely clear yet what this means for us long term.

How has the community developed since the last report?

  35 subscribers to the dev list, +3 since last report

How has the project developed since the last report?

  - Continued to expand the API
  - Research to assert model is on track for best computing

Date of last release:

  N/A

When were the last committers or PMC members elected?

  Zachary Jaffee elected as a committer on 11/15/15

Signed-off-by:

  [ ](horn) Luciano Resende
  [ ](horn) Robin Anil
  [X](horn) Edward J. Yoon
  [ ](horn) Rich Bowen

Shepherd/Mentor notes:


--------------------
HTrace

HTrace is a tracing framework intended for use with distributed systems.

HTrace has been incubating since 2014-11.

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

  1. Continue to grow the HTrace community
  2. Continue to develop and release stable HTrace incubating artifacts
  3. Continue to explore the integration of the HTrace framework into
     other Apache products

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?

  39 subscribers to dev@ (up from 38) and about 200 messages
  since last report (up from 55 in previous period though many
  are build 'failures')

How has the project developed since the last report?

  About 65 issues resolved since last report contributed
  by 5 different contributors.

Date of last release:

  htrace-incubating-4.0.0 on Sept 14th, 2015
  htrace-incubating-4.0.1 on Sept 27th, 2015

When were the last committers or PMC members elected?

  None this period. Last added committer: Abraham Elmahrek - 2.11.15

Signed-off-by:

  [X](htrace) Jake Farrell
  [ ](htrace) Todd Lipcon
  [ ](htrace) Lewis John Mcgibbney
  [ ](htrace) Andrew Purtell
  [X](htrace) Billie Rinaldi
  [X](htrace) Michael Stack

Shepherd/Mentor notes:



--------------------
Johnzon

Implementation of JSR-353 JavaTM API for JSON Processing.

Johnzon has been incubating since 2014-06-09.

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

  1. Expanding the community, increase dev list activity and adding new
     committers/pmc members
  2. Complete the project incubation status page
  3. Add and improve documentation

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

  * PPMC has voted for graduation

How has the community developed since the last report?

  There are new people on the dev list and the project got contributions
  from non-committers.  On the dev list there are approx. 21 msgs (on
  average) messages per month. We have presented Johnzon at ApacheCon
  Europe.

How has the project developed since the last report?

  The project did its 9th incubator release.
  During the last three month 4 jira issues were reported and fixed.
  Project has also started to implement the upcoming JSR-374 specification.

Date of last release:

  2015-OCT-5 (0.9.2-incubating)

When were the last committers or PMC members elected?

  Last committer was elected 2014-08-23, last PMC member was elected
  2015-04-09 (Hendrik Saly)

Signed-off-by:

  [X](johnzon) Justin Mclean
  [ ](johnzon) Daniel Kulp

Shepherd/Mentor notes:

  Justin Mclean (jmclean):

    Issues re branding has been brought up on incubator list
    (<http://s.apache.org/3NU>) - this will be addressed.

--------------------
MADlib

Big Data Machine Learning in SQL for Data Scientists.

MADlib has been incubating since 2015-09-15.

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

  1. Produce a first Apache (incubating) release.
  2. Expand the community, increase dev list activity and add new
     committers/pmc members.
  3. Execute and manage the project according to governance model required
     by the "Apache Way”.

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. First community call held 11/20/15.  There were approximately 10
     attendees, about half were from outside of the current group of MADlib
     contributors.  This will be a monthly call, possibly moving to 2x per
     month in the future.
  2. Meetup 12/3/15 @ Pivotal Labs, San Francisco:  “MADlib and HAWQ for
     Advanced SQL Machine Learning on Hadoop”.  One goal of this meetup is
     to invite new community participation in MADlib.
  3. Material technical conversations are now happening on the dev mailing
     lists and in the appropriate JIRAs.  E.g., 53 emails on dev in Nov
     compared with 7 in Oct.

How has the project developed since the last report?

  1. 31 JIRAs created and 7 resolved in last 30 days.
  2. Mailing list subscribers: user - 19, dev - 20
  3. Proposed scope for first Apache MADlib release has been described to
     the community for comment.  This release includes IP cleanliness and
     new features.
  4. The MADlib wiki <http://s.apache.org/0lQ> has been updated with new
     content, including a new contributors guideline, an FAQ and a page
     listing suggestions for first time contributors (these have also been
     labeled “starter” in the JIRAs).

Date of last release:

  No release yet.

When were the last committers or PMC members elected?

  No new members added on top of the initial committer list.

Signed-off-by:

  [X](madlib) Konstantin Boudnik
  [X](madlib) Ted Dunning
  [X](madlib) Roman Shaposhnik

Shepherd/Mentor notes:



--------------------
MRQL

MRQL is a query processing and optimization system for large-scale,
distributed data analysis, built on top of Apache Hadoop, Hama, Spark, and
Flink.

MRQL has been incubating since 2013-03-13.

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

  1. Increase the number of active committers
  2. Increase adoption, expand user community, and increase user list
     activity

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?

  There were no new developers or new committers since our last report.
  There are 3 new UTA students who are planning to contribute to the MRQL
  projects as part of their Master's thesis in Spring'16, but they have not
  participated in the MRQL community yet. We hope to get more
  contributions/committers from the Flink and Spark communities to help us
  fine-tune the MRQL evaluation engine on these platforms.

How has the project developed since the last report?

  Very little activity on JIRA since the last report (only 2 issues reported
  that were both fixed). One of the JIRA issues was related to a major
  extension to MRQL to support incremental query processing (to convert any
  stream-based MRQL query to an incremental query that merges the previous
  query results with the results of applying the query to the new data
  batches only). This was based on an idea presented at ApacheCon'15 as a
  future plan for MRQL. It works on Spark Streaming mode for now, but it
  will soon support Flink Streaming too.

Date of last release:

  2015-02-25

When were the last committers or PMC members elected?

  2014-04-17

Signed-off-by:

  [ ](mrql) Alan Cabrera
  [X](mrql) Edward J. Yoon
  [ ](mrql) Mohammad Nour El-Din

Shepherd/Mentor notes:



--------------------
Mynewt

Mynewt is a real-time operating system for constrained embedded systems like
wearables, lightbulbs, locks and doorbells. It works on a variety of 32-bit
MCUs (microcontrollers), including ARM Cortex-M and MIPS architectures.

Mynewt has been incubating since 2015-10-20.

  1. Do a first Apache release capable of producing a downloadable RTOS
     image with support for multiple peripherals and network connectivity.
  2. Expand community - attract new project contributors and users & grow
     committer base
  3. Develop a roadmap and release schedule for the Mynewt Operating System

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. Mailing list activity since last report:
     @dev      48 messages, 2 new subscribers
     @commits  140 messages
  2. Committer workflow was tested on documentation site.
  3. Participation on the @dev mailing list covered a range of topics
     including feature priorities, coding practices, Go package handling
     options, and logo discussions.

How has the project developed since the last report?

  1. Feature support: 12 JIRA issues were created and are in various stages
     of progress after discussion about relative priorities on @dev mailing
     list.
  2. Documentation support: non-committer workflow discussed and tested on
     site.
  3. Progress towards self-governance: We have a potential new committer
     already, and the community is discussing its policy/culture about
     adding committers and PMC members.

Date of last release:

  No release yet.

When were the last committers or PMC members elected?

  At the start of the project (2015-10-20)

Signed-off-by:

  [X](mynewt) Sterling Hughes
  [ ](mynewt) Jim Jagielski
  [X](mynewt) Justin Mclean
  [X](mynewt) Greg Stein
  [X](mynewt) P. Taylor Goetz

Shepherd/Mentor notes:


--------------------
Myriad

Myriad enables co-existence of Apache Hadoop YARN and Apache Mesos together
on the same cluster and allows dynamic resource allocations across both
Hadoop and other applications running on the same physical data center
infrastructure.

Myriad has been incubating since 2015-03-01.

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

  1. Release Myriad 0.1.0 under Apache. Currently awaiting IPMC feedback.
     http://s.apache.org/lft
  2. Add more content to our new website http://myriad.incubator.apache.org
     and drive traffic to it.
  3. Grow our user base. We're hoping to find more (enterprise)
     users/testers after we have an actual versioned release and a website.

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

  Please vote for the Myriad 0.1.0 release!

How has the community developed since the last report?

  - Mailing list traffic has increased to 381 messages (20 authors) in
    October and then 326 messages (22 authors) in November, up from 227
    messages (17 authors) in September.
  - Our biweekly community syncs get around 8-12 participants lately, up
    from the 7-11 we were getting in August-September. See minutes at:
    http://s.apache.org/8kF
  - Freenode #myriad IRC channel saw a lot of activity during release
    planning, but has since calmed down. Archived by ASFBot at:
    http://wilderness.apache.org/channels/#logs-#myriad
  - Wiki space has grown from 24 to 29 pages since the last report.
    https://cwiki.apache.org/confluence/display/MYRIAD/Myriad+Home
  - Website is live! http://myriad.incubator.apache.org

How has the project developed since the last report?

  - Resolved 53 "Fixed" JIRAs since Oct 7 (plus 19 Duplicate/Won't Fix).
    Some of this was pre-release JIRA cleanup to match the truth of which
    PRs had already been merged. See <http://s.apache.org/1nw>.
  - Merged 8 PRs from old github repo, no new PRs allowed anymore. See
    https://github.com/mesos/myriad/pulls?q=closed%3A%3E2015-10-07
  - Merged 49 PRs from new github mirror. See <http://s.apache.org/Cqg>.
    
Date of last release:

  The PPMC just passed the vote for apache-myriad-0.1.0-incubating (rc3) on
  Nov 29th, and now we are awaiting our second round of feedback from the
  IPMC (1 binding +1 so far). <http://s.apache.org/lft>

When were the last committers or PMC members elected?

  We elected Darin and Swapnil in October and got IPMC/Board approval,
  accounts/permissions/etc. setup by early November. We plan to nominate
  more committer candidates after the 0.1.0 release.

Signed-off-by:

  [ ](myriad) Benjamin Hindman
  [ ](myriad) Danese Cooper
  [x](myriad) Ted Dunning
  [ ](myriad) Luciano Resende

Shepherd/Mentor notes:

  Timothy Chen (tnachen):
  
    Myriad release is currently being voted and seeing good discussions
    around jira about release process. Seeing slight increase of contributor
    on mailing list and code. 

  Marvin Humphrey (marvin):

    Happily, the release has now been approved by the IPMC.

--------------------
Ranger

The Ranger project is a framework to enable, monitor and manage
comprehensive data security across the Hadoop platform.

Ranger has been incubating since 2014-07-24.

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

  1. Increase the community participants for Apache Ranger
  2. Re-organize documentation for easier access to end-users, new users and
     contributors.
  3. Integration of Apache Ranger with other Apache Security Initiatives

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. Added one new contributor: (Varun Rao)
  2. Mailing list activity since last report (Sep-01-2015 to Nov-30-2015):
            @dev          1068
            @user          188
            @commit        463
  3. Issues (JIRAs) created/resolved since last report (after Sep-01-2015
     before Nov-30-2015):
            Created:       121
            Resolved:       96

How has the project developed since the last report?

  1. Members have been working on a next major release of 0.6.0
  2. Also, as we have a lot of bug-fixes on top of 0.5.0 release, we are
     working towards a 0.5.1 release.
  3. Working with new contributors to add HSM support for Apache Ranger KMS.

Date of last release:

  JUNE-10-2015

When were the last committers or PMC members elected?

  1. Gautam Borad has been added as committer on June-29-2015

Signed-off-by:

  [X](ranger) Alan Gates
  [ ](ranger) Daniel Gruno
  [X](ranger) Devaraj Das
  [X](ranger) Jakob Homan
  [ ](ranger) Owen O'Malley

Shepherd/Mentor 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. Populate the website for the project
  2. Expand the "how to" document to explain the ways new contributors can
     become involved in the project, so we increase the size of the
     community.
  3. Become familiar with the release process and have a first release as
     part of the Apache Foundation

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 started having questions and some traffic on the dev list generated
    by non-committers. There are 33 subscribers to the dev list, about half
    of them non-committers.
  - We started a discussion and created an initial draft of a document about
    how new contributers can contribute to the project and what should be
    the workflow.
  - The initial committers continue to learn to use the Apache
    infrastructure and processes.

How has the project developed since the last report?

  - Started working on updating the licence headers and poms to prepare for
    an Apache release.
  - Modified the Rya manual to markdown and linked it from the readme file,
    so the documentation is easier to access.
  - Working on new features: inconsistency detection, cloning, delete
    support for secondary indices.
  - Still working on creating a website for the project.

Date of last release:

  Not applicable

When were the last committers or PMC members elected?

  Not applicable

Signed-off-by:

  [x](rya) Josh Elser
  [X](rya) Edward J. Yoon
  [X](rya) Sean Busbey
  [X](rya) Venkatesh Seetharam

Shepherd/Mentor notes:

  Sean Busbey (busbey):

    Good community discussion this month. PPMC proactively reaching out to
    mentors about ASF questions, which is great.

  Josh Elser (elserj):

    Steady progress being made by members. Nothing concerning to me.

--------------------
SAMOA

SAMOA provides a collection of distributed streaming algorithms for the most
common data mining and machine learning tasks such as classification,
clustering, and regression, as well as programming abstractions to develop
new algorithms that run on top of distributed stream processing engines
(DSPEs).  It features a pluggable architecture that allows it to run on
several DSPEs such as Apache Flink, Apache Storm, Apache S4, and Apache
Samza.

SAMOA has been incubating since 2014-12-15.

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

  1. Grow the community
  2. Elect new PMC members
  3. Following up our first release with further 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?

  Mailing list activity (September-October-November 2015):
  * @dev: 120 messages

  Jira issues backlog (September-October-November 2015):
  * Created:  8
  * Resolved: 6

  Our main goal is to grow the community, which is still pretty small.  We
  are doing a large amount of dissemination work in conferences and events
  to promote SAMOA.  For example, we had two talks at technical conferences:

  1) A talk at the Apache Conference BigData, in Budapest, Hungary, during
     the week of September 28-30, 2015.
  2) A talk at the Flink Forward, a conference for the Apache Flink DSPE, in
     Berlin, Germany, October 12-13, 2015

  We have had contributions from outside the PPMC. In particular, we have
  had contributions for:

  1) integrating Apache Avro input with Apache Samoa,
  2) a proposal for integrating Apache APEX as a new DSPE,
  3) continued the collaboration with the Apache Flink community.

How has the project developed since the last report?

  Main developments:

  * Performed development and testing of the VHT module.
  * Fixed various bugs and improved ensemble and bagging methods.
  * Worked on the integration of new data sources like Apache Avro.
  * Improved the website to include more material for new contributors.

Date of last release:

  2015-07-21

When were the last committers or PMC members elected?

  None

Signed-off-by:

  [X](samoa) Alan Gates
  [ ](samoa) Ashutosh Chauhan
  [ ](samoa) Enis Soztutar
  [x](samoa) Ted Dunning

Shepherd/Mentor notes:



--------------------
Sentry

Sentry is a highly modular system for providing fine grained role based
authorization to both data and metadata stored on an Apache Hadoop cluster.

Sentry has been incubating since 2013-08-08.

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

  1. Review PPMC election policy, if committers will become PPMC on
     graduation. Community is right now discussing this.

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

  Graduation discussions have started. There seems to be some disagreement
  on graduation readiness which led to a broad discussion on general@. Seems
  like most of it is resolved but still need mentors agreement. The Sentry
  community did a number of things since last report to address the
  concerns/suggestions around the open communication.

  1. Community monthly hangout, IRC channel that's just been setup.
  2. Community members presented Sentry at the ApacheCon
  3. Sentry meetup at NY during HadoopWorld

How has the community developed since the last report?

  1. We had ~260 messages on dev list in the past two months. (Got number
     from http://markmail.org/list/org.apache.sentry.dev)

How has the project developed since the last report?

  1. About 71 issues were created and about 58 resolved in the past 2
  months(Numbers from jira).

Date of last release:

  2015-09-22

When were the last committers or PMC members elected?

  Anne Yu was added as committers on 11/27/2015. No new PPMC members have
  been added since the project has entered the incubator, although PPMC
  election policies are being discussed in the community.

Signed-off-by:

  [X](sentry) Arvind Prabhakar
  [ ](sentry) Joe Brockmeier
  [ ](sentry) David Nalley
  [ ](sentry) Olivier Lamy
  [X](sentry) Patrick Hunt
  [X](sentry) Thomas White

Shepherd/Mentor notes:



--------------------
Singa

Singa is a distributed deep learning platform.

Singa has been incubating since 2015-03-17.

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

  1. Expand the community, both in its size and its diversity. 
  2. Improve training efficiency by supporting GPUs, and improve scalability
     by reducing communication cost.
  2. Improve the usability by providing more built-in models and python
     binding.

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

  The Github repository has scored 400+ stars and 150 forks. The developer
  community is growing slowly: the total number now is 14 developers. After
  the second release (with GPU) in December, it is expected that more
  developers will come.

How has the community developed since the last report?

  The community has been active with the development for the next release.
  Since September, there've been 296 and 369 new emails in the dev@ and
  commit@ mailing list respectively.  

How has the project developed since the last report?

  The first version was released shortly after the last report. We are
  implementing features using the following schedule:
  http://singa.apache.org/develop/schedule.html.

  The planned features shall be finished soon. The second version is set to
  be released in December.

Date of last release:

  2015-10-08

When were the last committers or PMC members elected?



Signed-off-by:

  [ ](singa) Daniel Dai
  [X](singa) Alan Gates
  [x](singa) Ted Dunning
  [ ](singa) Thejas Nair

Shepherd/Mentor notes:



--------------------
Streams

Apache Streams (incubating) is a lightweight (yet scalable) framework for
ActivityStreams.  Streams contains a commons for Rest API connectors and
data schemas, and support normalization of digital events and entities into
the industry-standard Activity Streams format.

Streams has been incubating since 2012-11-20.

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

  1. Community growth and PMC maturity.
  2. Demonstrate a consistent release schedule.
  3. Collaborate with other Apache projects to improve integrations
     with their software.

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

  # of contributors submitting and reviewing pull requests has remained
  low this quarter. mentor participation has been low. the last PPMC vote
  for a release had no -1's but failed to gain the necessary support for
  submission to the IPMC.

How has the community developed since the last report?

  ~25 ApacheCon Europe attendees came to project presentation, but otherwise
  no measurable progress in community growth.

How has the project developed since the last report?

  34 issues created / 21 merged / 1 in pull request this quarter

Date of last release:

   2015-04-26

When were the last committers or PMC members elected?

  2015-02-23: Robert Douglas elected as committer / PMC member

Signed-off-by:

  [ ](streams) Matt Franklin
  [X](streams) Ate Douma
  [ ](streams) Craig McClanahan

Shepherd/Mentor notes:

  Ate Douma (ate):
 
    As reported above, mentor support has been too low, including my own.
    I find the dwindling down of participation and contributions other than
    from only one (very) active committer (Steve Blackmon) worrisome.
    More or even primary focus should be turned towards community
    development instead of only churning out code.
    I've suggested some concrete steps for this and propose to give the
    project a bit more time to try building up a community and more
    contributor involvement. As a mentor I'll try to help out more as well. 
    However, if there is no substantial improvement within one or two
    reporting periods, it might be better to consider retirement instead.

  Timothy Chen (tnachen): 

    Seems like there is one active committer as mentioned, and the majority
    of the mailing list activity is from JIRA and github from the same
    committer as well.  Also second that will need to consider retirement if
    this continues.

--------------------
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 and PyDML algorithm scripts, respond to
     user feedback to ensure SystemML meets the requirements of real-world
     situations, write papers, and present SystemML at conferences.
  2. Core library improvements, including Apache Spark integration.
  3. Improved SystemML documentation to lower the learning curve.
  4. Produce a release

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

  The community is blocked, and expects that the SystemML Apache JIRA
  site will be available shortly, as detailed in INFRA-10714.

How has the community developed since the last report?

  We have started to see few non original committers ask questions on the
  dev list, and the existing committers are actively helping these
  contributors.

How has the project developed since the last report?

  All infrastructure, except for JIRA, are in place and in use by the
  community.

Date of last release:

  NONE

When were the last committers or PMC members elected?

  NONE

Signed-off-by:

  [x](systemml) Luciano Resende
  [ ](systemml) Patrick Wendell
  [ ](systemml) Reynold Xin
  [ ](systemml) Rich Bowen

Shepherd/Mentor notes:



--------------------
Taverna

Taverna is a domain-independent suite of tools used to design and execute
data-driven workflows.

Taverna has been incubating since 2014-10-20.

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

  1. Community growth
  2. Release more of the imported code to create engagement
  3. Move to a sustainable development pattern

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?

  Vote on new committer. Passed by Apache Taverna, needs acceptance by IPMC.
  Mailing list activity Sep/Oct/Nov
    - dev 33/9/31
    - users 2/5/4
    - commits 50/103/16

How has the project developed since the last report?

  Fixed build problem in command-line package
  https://issues.apache.org/jira/browse/TAVERNA-874

Date of last release:

  2015-08-11 taverna-language-0.15.0-incubating

When were the last committers or PMC members elected?

  n/a

Signed-off-by:

  [x](taverna) Andy Seaborne
  [ ](taverna) Chris Mattmann
  [ ](taverna) Suresh Srinivas
  [ ](taverna) Suresh Marru
  [x](taverna) Marlon Pierce

Shepherd/Mentor notes:

  Andy Seaborne (andy):

    Dev discussions have slowed right down this quarter.  Developer
    effort was strong for GSoC but there is now a minimum with no
    prospect of a change until Jan/Feb next year. A worry I have
    is that this was not communicated until considerable prompting
    applied.

    There are only 2 active mentors.

  Marlon Pierce (mpierce):

    +1 for Andy's comments. After a very promising summer, the project has
    come to a halt.  Despite mentor prompting, the project did not take the
    opportunity to grow its community from active GSOC participants.

  John D. Ament (johndament):

    Reading through the report, it seems that there may be some issues to be
    raised up.

--------------------
Trafodion

Trafodion is a webscale SQL-on-Hadoop solution enabling transactional or
operational workloads on Hadoop.

Trafodion has been incubating since 2015-05-24.

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

  1. Develop and diversify community and a deeper understanding of the
     Apache Way.
  2. Resolve remaining license conflicts and make our first Apache
     (incubating) release.
  3. Streamline incubator website, so that it is easy for new contributors
     to get started.

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?

  * Presented a talk at Apache: Big Data, 2015 in Budapest
  * Presented at NY Hadoop user group meetup
  * Roberta Marton has volunteered as Release Manager, for our first Apache
    release. The release is planned for the second half of December.
  * JIRAs being created by end users.
  * 14 new members filed an iCLA indicating interest to contribute to
    Trafodion, during the previous three months
  * User participation in public lists remains steady. 612@codereview,
    430@commits, 435@dev & 1364@issues during previous three months.
  * In the last month alone we had 137@codereview, 105@commits, 204@dev &
    370@issues.
  * Distinct culture shift -- discussions have moved out from private
    distribution lists into public Apache distribution lists

How has the project developed since the last report?

  * Wiki migration complete. New pages added regularly.
    https://cwiki.apache.org/confluence/display/TRAFODION/
  * A website revamp is in progress
  * 18 authors have made 145 commits to master during previous three months.
    45,084 line additions, 109,035 deletions. 18 authors made 51 commits
    during November alone.
  * 177 JIRAs created and 262 resolved during September-November 2015, with
    83 created/42 resolved in November alone
  * Held our first IPMC vote for a release, for which we got much valuable
    feedback. We are currently addressing the issues and getting ready to
    try again
  * Much effort has gone into simplifying the install and build processes

Date of last release:

  We have not done a release of Trafodion since incubation.

When were the last committers or PMC members elected?

  Selvaganes Govindarajan, Anoop Sharma and Hans Zeller elected as
  committers and PPMC members in November, 2015.

Signed-off-by:

  [x](trafodion) Devaraj Das
  [x](trafodion) Enis Söztutar
  [ ](trafodion) Lars Hofhansl
  [x](trafodion) Michael Stack

Shepherd/Mentor notes:


--------------------
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. Complete website to add "Getting started section"
  2. Make some incubating releases
  3. Grow the community 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?

  We are in the process to promote the project. A first talk has been given
  at ApacheCon EU. The community starts to grow up now that the resources
  are available.

How has the project developed since the last report?

  We have a website in place at http://unomi.incubator.apache.org . The
  source code has been imported into Apache Git. We are working on providing
  a first release.

Date of last release:

  no release yet. We are in the process of preparing the first
  2.0.0-incubating release.

When were the last committers or PMC members elected?

  It's the first podling report.

Signed-off-by:

  [X](unomi) Jean-Baptiste Onofré
  [ ](unomi) Bertrand Delacretaz
  [ ](unomi) Roman Shaposhnik
  [X](unomi) Chris Mattmann

Shepherd/Mentor notes:

  John D Ament (johndament):
  
    Podling is off to a good start.  No concerns at this time.

--------------------
Wave

A wave is a hosted, live, concurrent data structure for rich communication.
It can be used like email, chat, or a document.

Wave has been incubating since 2010-12-04.

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

  1. Finalizing the first release
  2. Growing community
  3. Improving code base.

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

  The Wave project put its first release on the Incubator PMC, however, it
  looks like the review takes a long time and we didn't get any
  communication back.

How has the community developed since the last report?

  Not much, even though we managed to get a release and proceed with voting.

How has the project developed since the last report?

  There some additional code developments in the process.

Date of last release:

  NA

When were the last committers or PMC members elected?

  July 2014

Signed-off-by:

  [ ](wave) Christian Grobmeier
  [x](wave) Upayavira

Shepherd/Mentor notes:

  Upayavira:

    Firstly, I believe Christian has resigned as a mentor, leaving just
    myself.

    As noted above, having struggled for a long time to pass a vote on a
    release artifact, the Wave PPMC has now done this, and is waiting on the
    members of the Incubator PMC to step forward and review the release.
    Please review this release!

    I myself have deliberately postponed voting, as my involvement at the
    ASF has not involved much by way of release reviewing.

--------------------
Zeppelin

A collaborative data analytics and visualization tool for distributed,
general-purpose data processing systems such as Apache Spark, Apache Flink,
etc.

Zeppelin has been incubating since 2014-12-23.

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

  1. Do an Apache release
  2. Community growth: more committers from different organisations
  3. Increase adoption

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

  There is an ongoing discussion [1] about speed of the patch landing being
  low, as project gets more popular and attracts more contributions.

  This issue, raised by one of the mentors, is acknowledged by the community
  and there is work in progress on how the speed of the patch processing and
  acceptance can be increased: by clarifying the contribution process [2],
  discussing and documenting guidelines and best practices [3]

  [1] http://markmail.org/message/74247pqyc4bwtntj
  [2] https://issues.apache.org/jira/browse/ZEPPELIN-477
  [3] http://markmail.org/thread/542sigkdhbcvugwt

How has the community developed since the last report?

  Traffic in users@ and dev@ grew and +42 subscribers in @dev, +109
  subscribers in users@ since last report.

  Several talks about Zeppelin were presented at ApacheCon Eu, Spark Summit
  Eu, and Flink Forward.

How has the project developed since the last report?

  140 patches has been merged from 41 different contributors since last
  report.  Made 0.5.5-incubation release under Apache incubation.

Date of last release:

  2015-11-18

When were the last committers or PMC members elected?

  2015-10-03

Signed-off-by:

  [X](zeppelin) Konstantin Boudnik
  [X](zeppelin) Henry Saputra
  [X](zeppelin) Roman Shaposhnik
  [X](zeppelin) Ted Dunning
  [ ](zeppelin) Hyunsik Choi

Shepherd/Mentor notes:

  Konstantin Boudnik (cos):

    The issue of slow(er) adoption of some PRs is being discussed and the
    community looks into the ways of improving the situation.

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

December2015 (last edited 2015-12-13 22:36:25 by MarvinHumphrey)