Incubator PMC report for November 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 October,
podlings executed 4 distinct releases (a low number) and there are a couple 
of outstanding votes on releases for November. We added 3 new IPMC members.

Several podlings are heading towards graduation and several look like they 
may retire. ServiceComb and Joshua graduated last month and we will welcome 
several new podlings with votes or discussion underway for IotDB, Pinot, 
Sharding-Sphere, Brpc and Iceburg. Annotator had a discussion where they
decided not to retire. BatchEE still seems stuck in performing the last
graduation steps.

Doris is taking steps to address its lack of discussion on the mailing list 
and working on its first release.

MXNet had an excellent discussion around diversity and what it means to be 
a committer.

Superset is slowly addressing its issues, but has not yet made an Apache 
release and has continued to make unofficial releases. Its (new) mentor is 
helping out with this and it has pointed out if they don't try a little 
harder they may be removed from the incubator.

Unomi started graduation discussions, but run into some issues with PPMC 
members missing ICLAs and its roster. It may be that IP clearance still 
needs to be done.

Weex has improved with more discussion on the mailing list and discussion 
and action about how to improve community growth.

Skywalking put up a discussion to graduation, but it may of been too soon, 
given some irregularities with its roster and that they have only added one 
committer/PPMC member during incubation but have had a large number of 
contributions from many people.

Thanks to Edgenet for an honest and open assessment of where it is at.

Senssoft got a bit carried away and submitted a report when it didn't
need to. :-)

There were 6 IP clearances.

No podlings failed to report which is great to see.

The remaining missing mentors were contacted and those who didn't reply 
were removed from the podlings roster. We currently have about half of the 
podlings (23) with less than 3 mentors and 5 podlings only having one 
mentor. To get all podlings back to 3 mentors (which seems the ideal 
number) we would need 29 mentors volunteer. We're in the process of 
drafting an email to the members list, to see if we can get more members to 
step forward and become mentors. Several podlings have requested new 
mentors but so far we've only had a few IPMC members step forward and take 
on the role. (Podlings include Annotator, Dubbo, Hivemall, Superset and 
Warble).

In September several incubator PMC members visited China to speak at the 
Huawei Connect and COSCon'18 (where 3 different ASF incubator/Apache Ways 
talks were given). Many of the talks had moderate attendance but were 
streamed live to large numbers of people; one was live streamed to more than
1,000 people. Both conferences had ASF booths and we spoke to 100's of 
people and gave away countless ASF stickers, pamphlets and other swag.

IPMC and board members also visited several companies; Alibaba, Huawei and 
Tencent, to give talks, meet with developers contributing to ASF projects 
and meet with executives to find out how these companies and the ASF can 
work together. I was impressed to see Alibaba reached out to other people 
contributing to the Apache Dubbo project and invited them along to the 
meetings as well.

As a result of this a number of projects have a far better idea of how to 
operate as an Apache project and the steps towards graduation. We are 
likely to see several new (8-10) incubating projects arrive over the next 
few months.

Thanks to Huawei, Alibaba and Kaiyuanshe for making this possible. Thanks 
to Craig, Dave, Justin, Roman and Ross and others who gave up their time to 
do this and also many thanks to the many local people who helped out at the 
ASF booths, with translation of our talks and acting as guides to sometimes 
bewildered and slightly confused ASF people.

Several podlings have not kept their rosters up-to-date, and this has 
caused some graduation and access issues. Several of these podlings have 
been contacted and asked to correct their rosters and a couple have done 
so. The IPMC will keep an eye on podling reports and check that new 
committers/PPMC have been added to the roster, but it would be best if the 
podlings (and their mentors) take a more active role in doing this.

Some podlings are still having issues with creating initial accounts and 
signing ICLAs. A proof of concept system for easy ICLA signing was made by 
Daniel here https://icla.live/ .

What to do about podlings tasked with writing bylaws/guidelines is still 
outstanding.

* Community

 New IPMC members:
 - Ioannis Canellos
 - Koji Sekiguchi 
 - Jason Dai

 People who left the IPMC:

 - None

* New Podlings

 - Pinot	

* Podlings that failed to report, expected next month

 - None

* Graduations

 - Apache Griffin

* Releases

 The following releases entered distribution during the month of
 October:
 - Apache Plc4x 0.1.0
 - Apache Dubbo 2.6.4	
 - Apache Skywalking 5.0.0 GA
 - Apache Weex 0.19.0

* IP Clearance

 - Apache Arrow Parquet Ruby Library
 - Apache Arrow C# Library
 - Apache Beam Euphoria API
 - Apache Beam Dataflow Java Worker
 - Arrow Parquet GLib Library	
 - Mojohaus Maven Utilities, for the NetBeans podling

* Legal / Trademarks

 Discussion of what needed re ICLAs, CCLA and software grants 
 (LEGAL-420).	

* Infrastructure

 No issues.

* Miscellaneous
 - Discussion with UNICEF’s about bringing a project to the ASF.
 - Discussion on reviewing binary releases.
 - Question on mirror sites (redirection preferred).
 - Update to web site with guidelines for publicity for incubating projects.

----------------------------------------------------------------------
                       Table of Contents
DLab
Doris
ECharts
Edgent
Heron
Livy
Marvin-AI
PageSpeed
Pinot
Ratis
S2Graph
SDAP
Tamaya
Toree
Unomi
Warble
Weex
Zipkin
Senssoft

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

--------------------
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. Execute the SGA between EPAM and the ASF so code can be imported.
  2. Move bug tracking system including project backlog to Apache issue 
  tracking system.
  3. Work toward an initial Apache release.

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

  Nothing at this point of time.

How has the community developed since the last report?

  We are not at the stage of building community so far.

How has the project developed since the last report?

 Initial committers have submitted their Apache ICLA, subscribed to all 
 mailing lists and created Jira accounts. Functionality added:
  - Administrative Web UI for roles management
  - Fixed libraries installation for RStudio
  - Restrict usage of EC2 instances of certain shapes to different groups 
  of users
  - Fixed a bug on MS Azure when instance creation failed because of same 
  IP allocation to different instances
  - Added support of Dex authentication
  - Work in progress towards deployment into two VPC’s (SSN and Edge Node 
  into one VPC, notebooks and computational resources into separate VPC)
  - Work in progress implementing Java libraries support from WebUI

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

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

Date of last release:

  This is going to be our first release.

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.

  Mentors were very responsive and provided a good overview of incubation 
  process in general. Helped a lot providing detailed instructions on how 
  to get subscribed, submit ICLA application and certainly provided a
  vector for next steps. The team has immediate support and can ask for
  any questions.

Signed-off-by:

  [X](dlab) P. Taylor Goetz
     Comments: To give some context regarding the mentor question above,
               I'm employed by the same company as the initial committers
               and have working with them since before the proposal to
               prep them for Apache.

               Currently we're waiting on the SGA (I'm working on pushing it
               through) which is blocking code import. Meanwhile the podling
               is starting to use the mailing list and populating JIRA.
  [X](dlab) Henry Saputra
     Comments:
  [ ](dlab) Konstantin I Boudnik
     Comments:

IPMC/Shepherd notes:

--------------------
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. Move discussion to the mailing list;
  2. Make our first ASF release;
  3. Work on the web site.

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?

  New added a contributor who contribute a feature.

How has the project developed since the last report?

  Start to test the feature of streaming import and prepare to commit;

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

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

Date of last release:

  N/A.

When were the last committers or PPMC members elected?

  N/A.

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: Still in the getting started stage ... 
               I did meet with Reed in person in Shenzhen.
  [ ](doris) Luke Han
     Comments:
  [X](doris) Willem Jiang
     Comments: Project team is getting used to have discussion in the 
     mailing list. 

IPMC/Shepherd notes:

--------------------
ECharts

ECharts is a charting and data visualization library written in JavaScript.

ECharts has been incubating since 2018-01-18.

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

  1. Have merged several pull request from community. 
  2. Received ICLA files from new contributors.
  3. Preparing version 4.2.0 release.

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?

  Several new contributors joined community, sending PR and helping answer 
  questions.

How has the project developed since the last report?

  Preparing the 4.2.0 release and add some new features and fixed bugs.

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

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. They helped a lot and solved many of our problems.

Signed-off-by:

  [X](echarts) John D. Ament
     Comments:
  [ ](echarts) Kevin A. McGrail
     Comments:
  [X](echarts) Dave Fisher
     Comments: I met with Wenli in Shenzhen.
               None of the PPMC had subscribed to the private email list.
               We discussed and this was corrected.
               More work is coming to the dev@ list and a new release is 
               being Voted on.
               Looking forward to more discussion on dev@.
               Next report should have a better discussion about steps to
               graduation.

IPMC/Shepherd notes:

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

  Apache Edgent is a programming SDK 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.  Re-creating a working community
  2.  Re-populating the PPMC
  3.  Replenishing the group of mentors

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

  For the past months, there has been absolutely no activity in the project
  Even if there has been an occasional Email from an external entity in the
  last 3 months, the activity in the project has been solely me (Christofer)
  writing emails without getting any form of response from the rest of the
  committers, PPMCs or mentors

  The main problem here is, that when being voted into the project, I had
  been working on the build, but before I was able to start digging in the 
  code the rest of the team disappeared without me having had the chance to
  do a reasonably significant amount of know-how transfer. Currently, we
  have a codebase for which we have a detailed understanding of the build,
  but almost none of the code itself.

How has the community developed since the last report?

  *   Total, we have 82 subscribers to our mailing list, an increase of 5 
      since the last report.
  *   There have been two questions asked by users and two little 
      discussions about these issues on the list
  *   Discussions started on the private list have been left unresponded
  *   On 19th September 2018 Christofer had a talk about Apache Edgent on 
      the Solutions.Hamburg TechCamp

How has the project developed since the last report?

  *   According to JIRA, 0 new issue were added and none were resolved in 
      the last 90 days
  *   0 commits were made in the last 90 days.

How would you assess the podling's maturity?

  After the withdrawal of most of the active committers and PPCM members 
  currently a new committer, PPMC and mentor-base has to be built. Being
  working hard on the PLC4X podling, I am currently evaluating if I am
  going to be willing and able to achieve this goal.

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

Date of last release:

  2017-12-14  Apache Edgent 1.2.0

When were the last committers or PPMC members elected?

  In August 2017, we added Christofer Dutz as a new committer
  and PPMC member.

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.

  I just double checked, but it seems our mentors are not existent
  there had been one or two issues where feedback was explicitly 
  asked for, but both the PPMC as well as all mentors remained silent.
  Except Justin mentioning the absence of mentors.

Signed-off-by:

  [x](edgent) Luciano Resende
     Comments:
  [X](edgent) Justin Mclean
     Comments:

IPMC/Shepherd notes:
      Dave Fisher: If the project is to be rebooted then the PPMC needs to 
          be grown. 
          I think you might find at least one candidate from dev@ activity.
          Also I noticed a JIRA - EDGENT-450 about creating an Edge 
          Connector for Apache Pulsar. 
          I've sent a note to dev@pulsar suggesting they join at dev@edgent 
          to help.

--------------------
Heron

A real-time, distributed, fault-tolerant stream processing engine.

Heron has been incubating since 2017-06-23.

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

  1. Making the fist Apache Release. Vote for RC5 is currently on 
  general@incubator
  2. Making several Releases
  3. Continuing to grow the community

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?

  The community has been growing.  Two more monthly meetups have been 
  successfully organized so far after the initial one in April 2018.  We 
  have also seen more interests in the Heron from different channels and 
  getting more ideas from the community.  In October 2018 there was a
  presentation given at BazelCon in New York city on building Apache Heron.

How has the project developed since the last report?

    There have been mainly bug fixes and improvements to existing features.
    Some to note are
    * Works towards Apache release and five release candidates have been 
    created.
    * Updates for the licenses
    * Updates to the documentation
    * New integration tests
    * New designs/works for the Streamlet API(Heron’s high level DSL)

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

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

Date of last release:

  No Apache releases as of yet. Latest RC was done on Oct 15th. [this might 
  change if our Apache release succeeds]

When were the last committers or PPMC members elected?

  Ning Wang was elected a committer on accepted on 11/1/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.

    Mentors have been very responsive and helpful.

Signed-off-by:

  [ ](heron) Jake Farrell
     Comments:
  [ ](heron) Julien Le Dem
     Comments:
  [ ](heron) P. Taylor Goetz
     Comments:
  [X](heron) David Fisher
     Comments: Heron has switched its 2x monthly offline hangout for a 
     twice weekly "what am I up to" on dev@heron.

IPMC/Shepherd notes:

--------------------
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 
  support is being added for Apache Spark 2.4 release.

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

Signed-off-by:

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

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?

  * The community has already migrated most of the infrastructure to
  Apache. After weeks of discussion, the community has finally come to a 
  consensus on the backlog for the first Apache release.

How has the project developed since the last report?

  * Code infrastructure is mostly migrated, new features are being 
  discussed.

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?

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 two of the mentors are sometimes active.

Signed-off-by:

  [x](marvin-ai) Jim Jagielski
     Comments: Request to submit report was sent by Luciano
  [x](marvin-ai) Luciano Resende
     Comments:
  [ ](marvin-ai) William Colen
     Comments:

IPMC/Shepherd notes:

--------------------
PageSpeed

PageSpeed represents a series of open source technologies to help
make the  web faster by rewriting web pages to reduce latency and
bandwidth.

PageSpeed has been incubating since 2017-09-30.

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

  1. The project needs more active developers.
  2. Create a first release
  3.

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

  The number of active developers is low. 
  It looks like we cannot leave this up to organic growth and would like to 
  brainstorm on ways to engage more developers.   

How has the community developed since the last report?

  One new developer was proposed to be added as a committer, but nobody
  voted, so the vote failed. This vote may have been initiated too early.
  In terms of users the project seems to be growing slightly still, but in 
  terms  of developers we seem to be stalled.

How has the project developed since the last report?

  A docker image for Alpine support was merged, which constitutes a non-
  trivial contribution.

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

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

Date of last release:

  XXXX-XX-XX

When were the last committers or PPMC members elected?

  Feb 2 2018 (Huibao Lin, elected as both committer and PMC member)

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.

Signed-off-by:

  [ ](pagespeed) Jukka Zitting
     Comments:
  [ ](pagespeed) Leif Hedstrom
     Comments:
  [X](pagespeed) Nick Kew
     Comments: Iterating my comment from the last report: this looks like
               a healthy github project but the Apache part is less clear.
  [ ](pagespeed) Phil Sorber
     Comments:

IPMC/Shepherd notes:

--------------------
Pinot

Pinot is a distributed columnar storage engine that can ingest data in real-
time and serve analytical queries at low latency.

Pinot has been incubating since 2018-10-17.

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

  We are just starting the incubation and don't have much to report. Few 
  things we are working on:
  1. Migrate the code base from LinkedIn GitHub to Apache GitHub
  2. Finish the initial tasks to set up the podling - website, mailing 
  lists, developer icla's etc 

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

How has the community developed since the last report?

How has the project developed since the last report?

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?

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](pinot) Kishore Gopalakrishna
     Comments:
  [ ](pinot) Jim Jagielski
     Comments: Very, very early in process.
  [ ](pinot) Roman Shaposhnik
     Comments:
  [x](pinot) Olivier Lamy
     Comments:  

IPMC/Shepherd notes:

--------------------
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. Work towards a GA release.
  2. Start working on graduation template.
  3. Complete name search process.

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?

  2 New PPMC members have been added. 
  3 new contributors have been added. Total 53 contributors currently.

How has the project developed since the last report?

  Rapid progress being made towards stabilization for a GA release.
  53 new patches committed.

How would you assess the podling's maturity?

Please feel free to add your own commentary.

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

When were the last committers or PPMC members elected?
  2018-11-03

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.

Signed-off-by:

  [X](ratis) Jakob Homan
     Comments:
  [X](ratis) Uma Maheswara Rao G
     Comments: IMO, this project is doing well and going towards graduation.
  [ ](ratis) Devaraj Das
     Comments:

IPMC/Shepherd notes:

--------------------
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 third 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 beaware
of?

  None

How has the community developed since the last report?

  * In ACNA 2018, we announced S2Graph as the title of the Apache
  S2Graph(incubating) with the build data management platform and audience
  targeting online application system using Graph Database.
  https://apachecon.dukecon.org/acna/2018/#/scheduledEvent/835a6adcab1ce83a0

  * There were some questions from the community about the introduction of
  S2Graph.

How has the project developed since the last report?

  * We have received some inquiries from the community and created an issue
  that does not solve it yet.
    - 5 issues are created and 0 of them are resolved since the last
    report (Sep 2018).

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-08-26

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: Incubating for three years; 
               we may need to discuss the
               podling future sooner than
               later.

IPMC/Shepherd notes:

--------------------
SDAP

SDAP is an integrated data analytic center for Big Science problems.

SDAP has been incubating since 2017-10-22.

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

  1. Make formal SDAP (Incubating) Release
  2. Improve/create user guide documentation
  3. Grow Community

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

  None

How has the community developed since the last report?

  Added 2 new developers that are becoming familiar with the project and 
  will soon become committers. 
  SDAP has been heavily advertised at/in many Earth Science technology 
  forums. 
  SDAP was featured at the CUAHSI Biennial Colloquium with an aim towards 
  growing the community.

How has the project developed since the last report?

  Development is still underway to push towards the first incubating 
  release of SDAP and each of its subcomponents.

How would you assess the podling's maturity?

Podling's still getting established.

  [] 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?

  Kevin M Gill was elected on 2018-03-05

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.

As mentors, we have not been very actively involved - but there's nothing ye
t that required the mentor's attention (the project is in good hands under L
ewis :-)).
Mentors are available nevertheless to help with releases and guiding the pod
ling. 

Signed-off-by:

  [X](sdap) Jörn Kottmann
     Comments:
  [X](sdap) Suneel Marthi
     Comments:

IPMC/Shepherd notes:

--------------------
Tamaya

Tamaya is a highly flexible configuration solution based on an modular,
extensible and injectable key/value based design, which should provide a
minimal but extendible modern and functional API leveraging SE, ME and EE
environments.

Tamaya has been incubating since 2014-11-14.

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

  1. Grow the PPMC from the existing community.
  2. Make another Release
  3. Blog about Tamaya

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

  * We'd like to graduate soon and plan some reworks to access a broader
  audience and collect new contributors/people interested in the project.

How has the community developed since the last report?

  * frequent bugreports and discussions via Jira/mailing list
  * new external contributions

How has the community developed since the last report?

  * frequent bugreports and discussions via Jira/mailing list
  * new external contributions

How has the project developed since the last report?

  * Bugfixes, changes, discussions going on

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

Date of last release:

  2017-05-28 0.3-incubating

When were the last committers or PPMC members elected?

  * P. Ottlinger at 2016-04-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.

  * John is and was the onliest active mentor and answers questions or gives
  hints for quite a while.
  * As the project needs a wider audience, maybe mentors with interest in Ta
  maya would be welcome.

Signed-off-by:

  [X](tamaya) John D. Ament
     Comments: The podling hasn't executed a release in over a year, has 
     limited on list discussions.  I would be cautious about graduating, 
     considering how small the community is.
  [ ](tamaya) David Blevins
     Comments:

IPMC/Shepherd notes:
  Dave Fisher: They are currently looking to add committers.
               Assuming that they show more community and make one or two
               releases then they are close to graduation.

--------------------
Toree

Toree provides applications with a mechanism to interactively and remotely
access Apache Spark.

Toree has been incubating since 2015-12-02.

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

  1.More discussion and engagement on the mailing list as opposed to 
  "gitter"

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 released the 0.2.0-incubating release and
  is currently voting the release 0.3.0-incubating. 

How has the project developed since the last report?

  * Regular cadence of community activity, with some increase on
  mailing list activity.
  * Several issues have been reported/addressed and a new
  release is being voted.

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-08-15

When were the last committers or PPMC members elected?

  * Ryan Blue was added to the PMC on 2017-04-03

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](toree) Luciano Resende
     Comments:
  [ ](toree) Julien Le Dem
     Comments:
  [ ](toree) Ryan Blue
     Comments:

IPMC/Shepherd 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. Clarify IP clearance (on-going)
  2. Finalized graduation proposal draft
  3. Podling graduation vote once step 1 and 2 are complete

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 have added a new committer and PPMC member : François Papon and we
  have prepared a list of PMC members for post-graduation.

How has the project developed since the last report?

  After the release of Apache Unomi 1.3.0, we are now focused on
  graduation. The maturity model report has been completed, the website
  has been greatly expanded to clarify community joining and
  communication, and a draft of the graduation proposal is being
  discussed right now.

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

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

Date of last release:

  2018-09-10

When were the last committers or PPMC members elected?

  2018-09-19

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 mentors are very helpful and responsive and are doing their best
  to assist the project when asked.

Signed-off-by:

  [x](unomi) Bertrand Delacretaz
     Comments: I agree that Unomi is mostly ready to graduate
  [X](unomi) Jean-Baptiste Onofre
     Comments: I'm helping to finalize the pending actions for the 
     graduation.

IPMC/Shepherd notes:

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

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

Warble has been incubating since 2018-06-11.

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 (IPMC) or ASF Board wish/need to be
aware of?
  Chris Lambertus has moved from the PMC to a mentor role. This was done to 
  give us some redundancy in mentorship and Chris said his time would be 
  better spent in that role.

How has the community developed since the last report?
  We've had some interest from outside people that are asking about 
  contributing and what they can do for the project.

How has the project developed since the last report?
  With Chris' move to mentor, we've been working on solidifying the change.

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

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

Date of last release:

  NA

When were the last committers or PPMC members elected?

  NA

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.

  NA

Signed-off-by:

  [X](warble) Chris Lambertus
     Comments: Community building and documentation of the framework 
     continue to be the core focus of Warble.

IPMC/Shepherd notes:

--------------------
Weex

Weex is a framework for building high-performance mobile apps with modern
web development experience.

Weex has been incubating since 2016-11-30.

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

  1. Propose more open discussions in the mailing list, improve the 
  activity.
  2. Establish a regular release schedule and a clear roadmap.
  3. Develop more committers and PPMCs, stay focused on the community.

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

  Apologize for missing the last podling report.

  The main reason for it is the PPMC and committers does not pay enough 
  attention in the mailing list. We have realized this mistake and decide 
  to take more efforts on building the community.

  Here are some actions:
  1. Hold meetings regularly among core contributors of Weex and publish 
  the summary to the mailing list.
  2. Take turns on duty for each release and podling reports.

How has the community developed since the last report?
  * Released a new version (v0.19.0) of Weex. 
  https://lists.apache.org/thread.html/3e7bfe9e3f79a8d4b46dbe668bfb559e4e539
bd7c5f4143107e6af00@%3Cgeneral.incubator.apache.org%3E
  * Hold a meetup in Shanghai at 2018-09-15, discussed technologies about 
  the new render pipeline and interactive experience of Weex.
  * Migrate the source code from (git-wip-us.apache.org) to 
  (gitbox.apache.org) and enabled the issue panel on the GitHub.

How has the project developed since the last report?

  * In average, more than 10 PRs or commits were merged to the main branch 
  each week. The Github repository now has 162 contributors (8 new since 
  the last report) and 1451 forks (130 new).
  * Weex has developed a new render pipeline and used it in production, but 
  it still needs more improvement.
  * A more CSS-friendly Weex Renderer is under discussing, it can fix many 
  cross-platform inconsistency problems.

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

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

Date of the last release:

  2018-10-08 (v0.19.0)

When were the last committers or PPMC members elected?

  New PPMC member: jondong (Jonathan Dong)

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 are helpful, but we still need more active mentors.

Signed-off-by:
   [X](Weex) Willem Ning Jiang
   Comments: The dev mailing list has 211 subscriptions and there is a 
   roadmap discussion in the mailing list. We need more mentors for this 
   project. 

IPMC/Shepherd notes:

--------------------
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 the migration of the GitHub repositories
 2. Finalize the migration of website
 3. Assess the migration to Apache CI infrastructure (Jenkins)

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

  The podling is presently blocked on INFRA-16989.

How has the community developed since the last report?
 
  The workshop has been held on 29th of October, 2018.

How has the project developed since the last report?

  The team started to look at Apache CI infrastructure (Jenkins) and assess 
  the fit to the  project needs (comparing to Travis CI). The Zipkin web
  site has been already migrated to Jenkins job and automatically rebuilds
  in case of changes.

How would you assess the podling's maturity?

  The IP rights/SGA and Git repository migration are still ongoing.

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?
  
  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.

  Mick was instrumental in getting us "in the nick of time" progressed on 
  the otherwise block on SGA. He encouraged me towards sending a message
  to the secretary and escalated later which allowed a last minute progress.

  Andriy helped with keeping spirit alive on dev list, review of wiki 
  content and also progressed our new committer Raja towards steps needed
  for committership.

Signed-off-by:

  [X](zipkin) Michael Semb Wever
     Comments: I would have listed the blockage on migrating the code 
     (INFRA-16989) under "issues that the Incubator PMC (IPMC) or ASF
     Board wish/need to be aware of" as even though it's moving again,
     this podling has barely moved for months because of it.
  [X](zipkin) John D. Ament
     Comments: I agree with the issues around the code import and don't 
     understand how we can help them move past it.  It seems that infra has 
     suddenly put a burden on secretary that isn't typical.
  [X](zipkin) Willem Ning Jiang
     Comments: As we already get iCLAs and SGA, can we move the code in to 
     Apache?
  [X](zipkin) Andriy Redko
     Comments:  The project struggles for a few months now to get the SGA 
     approved or/and accepted 
(https://issues.apache.org/jira/browse/INFRA-16989)
     by Apache. This is a significant source of frustration among the PPMCs 
     and community in general as the any further efforts are blocked.

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 submitted 12 nominations for new Podling names. The names 
  are collected for easy reference on our confluence space [1].
  JIRA tickets have been written to track progress on research on
  PODLINGNAMESEARCH board [2]. 

How has the community developed since the last report?

  The community has been:

  -discussing reaching out to other open source projects to identify other 
  potential  communities (analytical technologies) to drive developments,
  as well as increase interest in the Podling.
  -discussing research applications with university research labs in 
  machine learning and social computing.

How has the project developed since the last report?

  Project maturity roadmaps (Wiki) and version release plans (JIRA) 
  continue to be maintained. JIRA boards 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?

  Chris Mattmann and Paul Ramirez have been removed as mentors in the last 
  month.

  Lewis McGibbney has been extremely helpful and has actively participated 
  in our NAMESEARCH.

Signed-off-by:

  [X](senssoft) Lewis John McGibbney Comments:

  [1] 
https://cwiki.apache.org/confluence/display/SENSSOFT/PODLINGNAMESEARCH 
  [2] 
https://issues.apache.org/jira/projects/SENSSOFT/issues/SENSSOFT-308?filter=
allopenissues