Differences between revisions 75 and 76
Revision 75 as of 2019-02-12 20:45:02
Size: 40140
Comment: final version
Revision 76 as of 2019-02-12 21:20:03
Size: 40249
Comment: reflow and minor edit
Deletions are marked like this. Additions are marked like this.
Line 49: Line 49:
One podling failed to report this month BRPC and one poplin failed to get One podling failed to report this month BRPC and one podling failed to get
Line 67: Line 67:
Three of the projects Doris, Pinot and Sharding Sphere responded quickly and
removed the releases. SDAP is addressing the issue. ECharts is a little
Three of the projects Doris, Pinot and Sharding Sphere responded quickly
and removed the releases. SDAP is addressing the issue. ECharts is a little
Line 70: Line 70:
project and is trying to find another way of resolving the situation. Mentors
are working with them to resolve the situation.
project and is trying to find another way of resolving the situation.
Mentors are working with them to resolve the situation.
Line 108: Line 108:
 - Tamaya
Line 217: Line 218:
     Comments: The podling is making progress towards an Apache Release. There is a candidate and VOTE thread on general@.      Comments: The podling is making progress towards an Apache Release.
There is a candidate and VOTE thread on general@.
Line 248: Line 250:
  2. Currently, the latest version on npm is an rc version. We are working on retagging or deprecating it.   2. Currently, the latest version on npm is an rc version. We are working
     
on retagging or deprecating it.
Line 288: Line 291:
     Comments:I will continue to work with the podling to improve things especially regarding unofficial releases.      Comments:I will continue to work with the podling to improve things
especially regarding unofficial releases.
Line 290: Line 294:
     Comments: We have provided guidance to the podling about pre-Apache releases and unapproved releases.
           There is a thread which discusses an issue where code was inspired by code another a different license,
           but this was not a copy. If there is no conclusion on legal-discuss@ then we will need to ask on a
     Comments: We have provided guidance to the podling about pre-Apache
           
releases and unapproved releases.
           There is a thread which discusses an issue where code was             inspired by code another a different license,
           but this was not a copy. If there is no conclusion on
           
legal-discuss@ then we will need to ask on a
Line 424: Line 431:
  Streamlet API, Heron Spouts and Bazel upgration.In November 2018 the first
  Apache release was done following the Apache process and we are working on
  the next release with artifacts to make Heron easier for users to access.
  Streamlet API, Heron Spouts and Bazel upgration.In November 2018 the
  first Apache release was done following the Apache process and we are
 
working on the next release with artifacts to make Heron easier for
  users to access.
Line 465: Line 473:
     Comments: The podling needs to discuss more community activity on the dev list. They recently
          responded to a ping to start mentioning and advertising monthly Meetups on list.
     Comments: The podling needs to discuss more community activity on the
          
dev list. They recently
          responded to a ping to start mentioning and advertising monthly
          
Meetups on list.
Line 527: Line 537:
  The mentors have been very helpful in getting this podling established. No    open issues.   The mentors have been very helpful in getting this podling established.
  
No open issues.
Line 627: Line 637:
  to help new developers.     to help new developers.
Line 717: Line 727:
  of us feeling that we wanted to land a certain bug-fix. This release process
  will be re-spun and we should have a first incubator release candidate ready
  for review somewhere in the next couple of weeks.
  of us feeling that we wanted to land a certain bug-fix. This release
  process will be re-spun and we should have a first incubator release
  candidate ready for review somewhere in the next couple of weeks.
Line 993: Line 1003:
  this and we are in the process of rolling the RC back. Lewis (SDAP champion)
 
and the release manager are working to resolve this and get the first
 
incubating release candidate finished.
  this and we are in the process of rolling the RC back. Lewis (SDAP
  
champion) and the release manager are working to resolve this and get the
 
first incubating release candidate finished.
Line 1043: Line 1053:
    Dave Fisher: Most of the PPMC listed in Whimsy is not subscribed to private@.
        The number of developers on the dev list is small. A little too soon to be
       
thinking about graduation if you ask me.
    Justin Mclean: The IPMC usually likes to see 2 or 3 releases happen before
       
the project consider graduation.
    Dave Fisher: Most of the PPMC listed in Whimsy is not subscribed to
        
private@.
        The number of developers on the dev list is small. A little too
        soon to be
thinking about graduation if you ask me.
    Justin Mclean: The IPMC usually likes to see 2 or 3 releases happen
        
before the project consider graduation.
Line 1069: Line 1080:
  [1] https://lists.apache.org/thread.html/879089eb1dba43f6f159f8c3fde96c2a56d03edc9804f70dd7b94b6b@%3Cdev.shardingsphere.apache.org%3E   [1] https://lists.apache.org/thread.html/879089eb1dba43f6f159f8c3fde96c2a56d03ed
c9804f70dd7b94b6b@%3Cdev.shardingsphere.apache.org%3E
Line 1185: Line 1197:
   https://lists.apache.org/thread.html/91835c4e5b5e7d0cbe8be640e0878d8a3ac95dc    
https://lists.apache.org/thread.html/91835c4e5b5e7d0cbe8be640e0878d8a3ac95dc
Line 1252: Line 1265:
specification currently being worked on by the OASIS Context Server Technical
Committee. It provides a high-performance user profile and event tracking
server.
specification currently being worked on by the OASIS Context Server
Technical Committee. It provides a high-performance user profile and event
tracking server.

Incubator PMC report for February 2019

* FINAL DO NOT EDIT *

Timeline

Wed February 06

Podling reports due by end of day

Sun February 10

Shepherd reviews due by end of day

Sun February 10

Summary due by end of day

Tue February 12

Mentor signoff due by end of day

Wed February 13

Report submitted to Board

Wed February 20

Board meeting

Shepherd Assignments

Dave Fisher

SDAP

Dave Fisher

Tamaya

Drew Farris

Heron

Drew Farris

S2Graph

John Ament

Doris

John Ament

PageSpeed

Justin Mclean

Ratis

P. Taylor Goetz

IoTDB

P. Taylor Goetz

Pinot

P. Taylor Goetz

Unomi

Timothy Chen

Hudi

Timothy Chen

Iceberg

[none]

BRPC

[none]

ECharts

[none]

Edgent

[none]

ShardingSphere

[none]

Toree

Report content

Incubator PMC report for February 2019

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 51 podlings incubating. During the month of January,
podlings executed 3 distinct releases. We added no new IPMC members and 
had no IPMC members retire.

We have one new podling Hudi. No project graduated last month but several 
podlings are heading towards graduation in the next few months.

BatchEE took a vote to go to Apache Geronimo or TLP and decided on TLP and 
are back to being stuck in trying to graduate.

One podling failed to report this month BRPC and one podling failed to get
sign off from it mentors Tamaya. They been asked to report next month.

There was one IP clearance.

The mentor situation is continuing to improve. One of the mentors for the 
new Hudi project realised he didn't have the time be be able to give to the 
project and stood down. Thanks to him for being able to recognising that he 
wasn't going to be an effective mentor. Other mentors stepped forward to do 
the job.

We have a problem with unapproved releases. A spot check on some (not all) 
projects reporting this month showed that five projects were making 
unapproved releases. Hopefully that's a statical aberration, but it seems 
likely that we probably have more codlings making unapproved releases than 
this. This has been brought up one the general list and I see a few 
projects have taken note of it.

Three of the projects Doris, Pinot and Sharding Sphere responded quickly 
and removed the releases. SDAP is addressing the issue. ECharts is a little 
reluctant to remove the releases due to the high use and popularity of the 
project and is trying to find another way of resolving the situation. 
Mentors are working with them to resolve the situation.

ECharts was also found to hosting a Chinese version of their incubating 
site at echarts dot baidu dot com. The PPMC is also dealing with this.

A reminder to all incubating projects and mentors that all releases
and distributions advertised to the general public need to be approved by
the PPMC and IPMC. This includes docker, github, PyPi, npm and any
other platform for publishing releases, and also covers release candidates.
Nightly builds for project-internal use clearly marked as "snapshot" or
"prerelease" (or similar) can be made available to project contributors.
If in doubt please ask your mentors or on the incubator general list.

Superset has not made an Apache release but is making progress towards one. 
They accidentally published a release candidate to GitHub but sorting 
that out.

There was also an interesting discussion on binary releases on 
legal-discuss that could have some impact on the incubator.

New new project creating ASF training material may either go to straight to 
TLP or via the incubator. This did raise a few questions about how initial 
committers are selected.

* Community

  New IPMC members:
  - None

  People who left the IPMC:
  - None

* New Podlings
  - Hudi

* Podlings that failed to report, expected next month
 - BRPC
 - Tamaya

* Graduations

  The board has motions for the following:
  - Unomi?

* Releases

  The following releases entered distribution during the month of
  January:
  - Apache Dubbo 2.7.0
  - Apache SkyWalking 6.0.0-GA
  - Apache Dubbo Spring Boot 0.2.1 and 0.1.2

* IP Clearance
  - Apache Arrow Rust DataFusion

* Legal / Trademarks
  N/A

* Infrastructure
  N/A

* Miscellaneous
  - vote to shut down some old unused incubator lists
  - discussion on what to do with retired podling repositories

----------------------------------------------------------------------
                       Table of Contents
Doris
ECharts
Edgent
Heron
Hudi
Iceberg
IoTDB
PageSpeed
Pinot
Ratis
S2Graph
SDAP
ShardingSphere
Tamaya
Toree
Unomi

----------------------------------------------------------------------
--------------------
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. Resolve IP and Build Issues.
  2. Make a Successful First Apache Release.
  3. Grow the community encouraging patches and recognizing sustained 
  contributions by adding as Committers and PPMC members.

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

  None.

How has the community developed since the last report?

  A new mentor will add to Doris community.

How has the project developed since the last report?

  Excluding merges, 9 authors have pushed 21 commits to master and 26 
  commits to all branches. 
  On master, 240 files have changed and there have been 8,984 additions and 
  2,191 deletions.

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:

  Still working towards an Apache Release. 
  Made 0.9.0 legacy releases just after entering the Incubator on 
  2018-07-18 and it failed to approve due to license and build issues.
  We have fixed all license issues and improved building scripts, also 
  provide a docker environment for building.
  We Will now focus on making a successful Apache Release.

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, our mentors have been helpful and responsive.

Signed-off-by:

  [X](doris) Dave Fisher
     Comments: The podling is making progress towards an Apache Release. 
There is a candidate and VOTE thread on general@.
  [ ](doris) Luke Han
     Comments:
  [X](doris) Willem Ning Jiang
     Comments:
  [ ](doris) Shaofeng Shi
     Comments:

IPMC/Shepherd notes:
  Justin Mclean: Please addd something about the unapproved releases.
    Thanks for quickly fixing this, but going through my notes I can see
    this is the second time this has happened. What can be done to stop
    a third?

--------------------
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. Initiating a new release candidate (v4.2.1-rc1) on 2019-01-25.
  2. Discussing having a new committer.
  3. Discussing develop and release workflow.

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

  1. The entrance of Website with Chinese version is under discussion.
  2. Currently, the latest version on npm is an rc version. We are working 
     on retagging or deprecating it.
  3. Legal problems are under discussion about third party license header.

How has the community developed since the last report?

  More issues are in English now due to our encouragement.

How has the project developed since the last report?

  The project has been improved and we issued a new release candidate on 
  2019-01-25.

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?

  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.

  Yes.

Signed-off-by:

  [ ](echarts) John D. Ament
     Comments:
  [X](echarts) Kevin A. McGrail
     Comments:I will continue to work with the podling to improve things 
especially regarding unofficial releases.
  [X](echarts) Dave Fisher
     Comments: We have provided guidance to the podling about pre-Apache 
           releases and unapproved releases.
           There is a thread which discusses an issue where code was 
           inspired by code another a different license,
           but this was not a copy. If there is no conclusion on 
           legal-discuss@ then we will need to ask on a
           LEGAL JIRA.

IPMC/Shepherd notes:
  Justin Mclean: I think this report could have more detail and misses a
    number of things that are report worthy. Next time carefully go
    though the mail list and add anything that the IPMC (and board) would
    want to know about.

--------------------
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 very few activity in the project
  There have been a hand full of Emails from external peoples in the
  last 3 months but the activity in the project has been solely by me 
  (Julian) and Christofer Dutz writing emails without getting any form
  of response from the rest of the committers, PPMCs or mentors

  The main problem we have is that the only active people in the project 
  came in Late and are not that firm with the codebase. Currently, we
  have a codebase for which we have a detailed understanding of the build,
  but almost none of the code itself. Furthermore, there has been a lot of 
  activity in other projects and generally edge processing has developed
  further in the recent years.
  Thus, there is some discussion going on about the core or the aim of the 
  project to keep its significance and uniqueness.

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 has been one questions asked by users and little
      discussions about these issues on the list
  *   Julian Feinauer has joined the PPMC on 2018-11-29
  *   On April, 4th, Julian Feinauer will Talk about Edgent on the building 
      iot 2019

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
  *   The repositories were migrated to gitbox
  *   2 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.
  Currently we try to re-gain the focus of edgent to
  Start to rebuild the community and resume development.

  [ ] 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.
  In November 2018, we added Julian Feinauer 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. Christofer Dutz
  joined as new Mentor and is active in the project.

Signed-off-by:

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

IPMC/Shepherd notes:

--------------------
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 a new release (0.20.1). Formalize the release CI jobs under 
  Apache infra.
  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?

  None at this time.

How has the community developed since the last report?

  The community has been growing. Monthly meetups have been regularly and 
  successfully organized. We have seen new users interested in Heron and 
  community has been discussing and working on different ideas such as 
  Streamlet API, Heron Spouts and Bazel upgration.In November 2018 the 
  first Apache release was done following the Apache process and we are
  working on the next release with artifacts to make Heron easier for
  users to access.

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 with binaries and artifacts. Currently 
    fixing build scripts and jobs.
  * New functions in Streamlet API
  * Community initiated a new Heron-Spouts project
  * Fixes for Helm Charts specific to AWS clusters
  * Current work in progress to support the newest version of Bazel

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

  [ ] Initial setup
  [X] Working towards first release (binaries & artifacts)
  [X] Community building
  [ ] Nearing graduation
  [ ] Other:

Date of last release:

 Dec 2018(0.20.0-incubating, source only release)

When were the last committers or PPMC members elected?

  3 new committers were elected and invited in Dec 2018. Welcome Ali Ahmed, 
  Boyang Jerry Peng and Ning Wang.

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 responsive and helpful.

Signed-off-by:
  [X](heron) Dave Fisher
     Comments: The podling needs to discuss more community activity on the 
          dev list. They recently
          responded to a ping to start mentioning and advertising monthly 
          Meetups on list.
  [ ](heron) Jake Farrell
     Comments:
  [ ](heron) Jacques Nadeau
     Comments:
  [ ](heron) Julien Le Dem
     Comments:
  [ ](heron) P. Taylor Goetz
     Comments:

IPMC/Shepherd notes:

--------------------
Hudi

Hudi provides atomic upserts and incremental data streams on Big Data

Hudi has been incubating since 2019-01-17.

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

  1. Make frequent releases as per Apache guidelines
  2. Grow community
  3. 

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

  None so far

How has the community developed since the last report?

  Project's still being setup

How has the project developed since the last report?

  1. Initial set of committers have filed ICLA
  2. Jira and Github repo have been setup
  3. Mailing lists have been setup

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:

  Project's still being established

When were the last committers or PPMC members elected?

  Initial set of committers added to the project

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

  The mentors have been very helpful in getting this podling established. 
  No open issues.

Signed-off-by:

  [X](hudi) Thomas Weise
     Comments:
  [X](hudi) Luciano Resende
     Comments:
  [ ](hudi) Kishore Gopalakrishnan
     Comments:
  [X](hudi) Suneel Marthi
     Comments:

IPMC/Shepherd notes:

--------------------
Iceberg

Iceberg is a table format for large, slow-moving tabular data.

Iceberg has been incubating since 2018-11-16.

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

  1. Update build for Apache release, add LICENSE/NOTICE to Jars.
  2. Make the first Apache release.
  (https://github.com/apache/incubator-iceberg/milestone/1)
  3. Grow the Iceberg community

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

  * No issues that require attention.

How has the community developed since the last report?

  * Pull requests from 6 contributors were merged, 7 new contributors

How has the project developed since the last report?

  * Submitted evidence for podling name search: PODLINGNAMESEARCH-163
  * Netflix submitted a revised trademark agreement for counter-signing
  * Abstracted data file locations for community use cases
  * Reviewing proposed API update for file stream encryption plugins
  * New contributor highlights:
    - A new contributor is fixing case sensitivity in expressions
    - A new contributor opened a PR to add a startsWith predicate
    - A new contributor reviewed 4 pull requests and opened another

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

  [X] Initial setup (name clearance approval pending)
  [X] Working towards first release
  [X] Community building
  [ ] Nearing graduation
  [ ] Other:

Date of last release:

  None yet

When were the last committers or PPMC members elected?

  None yet

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](iceberg) Ryan Blue
     Comments: dev list traffic appears to be increasing also
  [ ](iceberg) Julien Le Dem
     Comments:
  [ ](iceberg) Owen O'Malley
     Comments:
  [x](iceberg) James Taylor
     Comments:
  [X](iceberg) Carl Steinbach
     Comments: From dev list: "Looks good to me. +1"

IPMC/Shepherd notes:

--------------------
IoTDB

IoTDB is a data store for managing large amounts of time series data such as
timestamped data from IoT sensors in industrial applications.

IoTDB has been incubating since 2018-11-18.

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

  1. Release the first version;
  2. Complement the left English documents and supply more design documents 
     to help new developers. 
  3. Attract more contributors;

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

  - no. 

How has the community developed since the last report?

  - The code repository has been transferred to the 
`   apache/incubator-iotdb` repository.
  - The website of `iotdb.apache.org` is updated: 
    (1) Document with English version is available;
    (2) Other introduction pages, such as `Tools`, `Community` and 
`   Development` are updated.
  - Mail list:
    (1) 490 emails sent by 26 people, divided into 350 topics; (318 mails 
    are from GitBox, for notifying code-review results).
    (2) a new mail list reviews@iotdb.apache.org is created;
    (3) two new contributors are involved: Jiaye Wu, Felix Cheung;
  - The community begin to use JIRA issues and Confluence.
 
How has the project developed since the last report?

  - All source codes are re-organized: 
    (1) package names are changed to `org.apache.iotdb.*`;
    (2) All textual files are attached with ASF header;
  - Apache Jenkins Pipeline was firstly passed at 2019.01.22
  - 13 issues are opened on JIRA, 3 of them are closed;
  - hundreds of vulnerabilities and thousands of code smells are detected 
    by Sonar, 2/3 of them are fixed;
  - 34 PR are submitted on Github, 24 of them are closed; 10 of them are in 
    code-review process.

How would you assess the podling's maturity?
  - newborn.

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.
  - very Helpful

Signed-off-by:

  [X](iotdb) Justin Mclean
     Comments:
  [X](iotdb) Christofer Dutz
     Comments:
  [X](iotdb) Willem Ning Jiang
     Comments:
  [ ](iotdb) Joe Witt
     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 was suggested that a release 
  may help attract community members. This was started, but stalled because
  of us feeling that we wanted to land a certain bug-fix. This release 
  process will be re-spun and we should have a first incubator release
  candidate ready for review somewhere in the next couple of weeks.

How has the community developed since the last report?

  One new developer was invited to be added as a committer, but ended up
  declining.

How has the project developed since the last report?

  There have been significant contributions to the core product, which is
  an improvement. Frequency is still low.

How would you assess the podling's maturity?

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

Date of last release:

  XXXX-XX-XX (First release being prepared, finally)

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.

  Mentors have been helpful.

Signed-off-by:

  [ ](pagespeed) Jukka Zitting
     Comments:
  [ ](pagespeed) Leif Hedstrom
     Comments:
  [*](pagespeed) Nick Kew
     Comments: As ever, ample git activity, very little discussion on-list.
  [ ](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:

  1.Improving documentation
  2.Cutting a release
  3.Building community contribution

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

  None

How has the community developed since the last report?

  We have had interest from Slack to contribute to 
  https://github.com/apache/incubator-pinot/issues/2798

How has the project developed since the last report?
  We are preparing for a release in Feb.
  - Source file headers have been updated to include Apache licenses.
  - Package names moved from com.linkedin to org.apache.
  - Additional work related to this effort can be tracked via 
    https://github.com/apache/incubator-pinot/pull/3722

  The website (https://pinot.apache.org/) has been updated. Primary changes 
  include updated landing page and documentation now links to updated 
  read-the-docs.

  All previously released bits have been removed.

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

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

Date of last release:

  N/A

When were the last committers or PPMC members elected?

  I believe this was soon after our incubation. @kishoreg may have more 
  information on this. (kishoreg confirmed no new committer)

Have your mentors been helpful and responsive or are things falling
through the cracks? In the latter case, please list any open issues
that need to be addressed.
  
  Yes, the mentors have been very helpful and have responded in a timely 
  manner. 

Signed-off-by:

  [ ](pinot) Kishore Gopalakrishna
     Comments:
  [ ](pinot) Jim Jagielski
     Comments:
  [ ](pinot) Roman Shaposhnik
     Comments:
  [X](pinot) Olivier Lamy
     Comments:
  [X](pinot) Felix Cheung
     Comments: dev@ discussions are picking up, great job!

IPMC/Shepherd notes:
  Justin Mclean: Please mention the issue of unapproved releases.
    Thanks for resolving this quickly.

--------------------
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. Have a GA release.
  2. Complete graduation template.
  3. Need name search.

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?

  5 new contributors have been added. Total 58 contributors currently.
  20 committers.

How has the project developed since the last report?
  50 new patches committed.
  Active work on multiple projects.

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

Date of last release:

  2018-08-15: Ratis-0.2.0
  2018-12-06: Ratis Thirdparty 0.2.0
  2019-01-31: Last snapshot release

When were the last committers or PPMC members elected?

 2018-12-05: Rajeshbabu Chintaguntla added as a committer.
 2018-12-10: Sergey Soldatov added as a committer.
 2018-12-26: Vladimir Rodionov added as a committer.
 

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

  Mentors have been helpful.

Signed-off-by:

  [x](ratis) Jakob Homan
     Comments:
  [ ](ratis) Uma Maheswara Rao G
     Comments:
  [x](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 the 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 be aware
of?

  None

How has the community developed since the last report?

  * Adding two committer. 
  * One more mentor has joined.
  * There were some questions and answers from the community about the 
    deployment of S2Graph.

How has the project developed since the last report?

  * We are overhauling documentation(S2GRAPH-246)
    - Integrate gitbook into the project.
  * New HTTP interface integration(S2GRAPH-248)

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?

  * 2018-12: Jong Wook Kim
  * 2018-12: Hyunsung Jo

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 mentor is very helpful and responsive.

Signed-off-by:

  [ ](s2graph) Sergio Fernández
     Comments:
  [X](s2graph) Woonsan Ko
     Comments:

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

  A member of the SDAP podling stepped up to the release manager role which
  is great. It shows the the podling is maturing.
  Unfortunately, the release candidate which was produced was not in
  compliance with the ASF release policy, thankfully Justin highlighted
  this and we are in the process of rolling the RC back. Lewis (SDAP 
  champion) and the release manager are working to resolve this and get the
  first incubating release candidate finished.

How has the community developed since the last report?

  Two VOTE's have been made over on private@sdap regarding extending
  PPMC and Committership to two community contributors. This is very
  positive.

How has the project developed since the last report?

  SDAP is on the verge of it's first release. With some persistence
  the podling will have a release candidate for community VOTE soon.

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

  [X] Initial setup
  [X] Working towards first release
  [X] Community building
  [ ] Nearing graduation
  [X] Other: One the release management process is documented we will be
       pushing for graduation.

Date of last release:

  XXXX-XX-XX

When were the last committers or PPMC members elected?

  Elizabeth Lam was elected on 2019-02-06
  Maya DeBellis was elected on 2019-02-06

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 mentors have been responsive providing answers.

Signed-off-by:

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

IPMC/Shepherd notes:
    Dave Fisher: Most of the PPMC listed in Whimsy is not subscribed to 
        private@.
        The number of developers on the dev list is small. A little too 
        soon to be thinking about graduation if you ask me.
    Justin Mclean: The IPMC usually likes to see 2 or 3 releases happen 
        before the project consider graduation.

--------------------
ShardingSphere

Sharding-Sphere is an ecosystem of transparent distributed database
middleware, focusing on data sharding, distributed transaction and database
orchestration.

ShardingSphere has been incubating since 2018-11-10.

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

  1. Prepare for the first ASF release.
  2. Fix bugs and develop new features.

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

  Remove unapproved legacy release before repo transfer. Add release 
  description of legacy releases. The details of email is [1].

  [1] https://lists.apache.org/thread.html/879089eb1dba43f6f159f8c3fde96c2a56d03ed
c9804f70dd7b94b6b@%3Cdev.shardingsphere.apache.org%3E

How has the community developed since the last report?

  Good. There are more and more contributors actually participating in 
  project development. 

How has the project developed since the last report?

  The github repository has been transferred to Apache.
  The official website has been deployed to asf-site and add Apache brand.

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:

  Not finished for the 1st apache release yet.

When were the last committers or PPMC members elected?

  28 Jan 2019

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](shardingsphere) Craig L Russell
     Comments:
  [ ](shardingsphere) Benjamin Hindman
     Comments:
  [X](shardingsphere) Willem Ning Jiang
     Comments:
  [ ](shardingsphere) Von Gosling
     Comments:

IPMC/Shepherd notes:
  Justin Mclean: Thanks for resolving the unapproved release issue quickly.

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

How has the community developed since the last report?

  * elected 2 new committers and onboarded them
  * discussions/we benefited from the Gitbox migration as it makes 
  contribution much easier

How has the project developed since the last report?

  * frequent bugreports and discussions via Jira/mailing list
  * new external contributions (code improvements, Jira issues, OSGi 
  bugfixes)
  * homepage overhaul

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

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

Date of last release:

   2017-05-28 0.3-incubating

When were the last committers or PPMC members elected?

  * 2018-12: Aaron Coburn
  * 2018-12: William Lieurance

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 the project needs a wider audience, maybe mentors with interest in 
  Tamaya would be welcome.

Signed-off-by:

  [ ](tamaya) John D. Ament
     Comments:
  [ ](tamaya) David Blevins
     Comments:

IPMC/Shepherd notes:
   Dave Fisher - sent an email regarding following release distribution 
   policy.
   
https://lists.apache.org/thread.html/91835c4e5b5e7d0cbe8be640e0878d8a3ac95dc
f9d2e1d91d13b28fb@%3Cdev.tamaya.apache.org%3E

--------------------
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.3.0-incubating release and after
  that overall work slowed down. 

How has the project developed since the last report?

  * Regular cadence of community activity, with slow down due
  to 'after-release' and holidays.

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

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:
  [x](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. Conclude IPMC graduation vote
  2. Complete Podling Name Search
  3. Submit graduation to Apache Board once the IPMC vote and PNS are 
  completed.

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 are seeing more activity on the relatively new user mailing list
  and continuing to support existing community members finalize some
  large projects.

How has the project developed since the last report?

  We have now started the graduation process and hope to complete it in
  the next month.

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 mentor is very helpful and responsive and is doing his best to
  assist the project when asked. He is alone but the project has now
  matured and is less dependent on mentors as it is in the graduation
  process.

Signed-off-by:

  [X](unomi) Jean-Baptiste Onofre
     Comments: I'm really frustrated to see how long is the graduation 
     process. Some reasons are obviously true, some we wasted time for
     "mistake" and inaccurate details.

IPMC/Shepherd notes:

February2019 (last edited 2019-02-12 21:20:03 by Justin Mclean)