Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: reflow and final

FINAL DO NOT EDIT

NOTE e'cNOTE that the content for this month report is in markdown format- please do not remove any formatting characters when adding your reports.

...

Shepherd Assignments

Dave FisherS2Graph
Dave FisherTraining
Drew FarrisRatis
Drew FarrisSDAP
Justin McleanToree
P. Taylor GoetzDoris
P. Taylor GoetzPageSpeed
P. Taylor GoetzTuweni
Timothy ChenDataSketches
Timothy ChenEdgent
Timothy ChenTamaya

ECharts

Heron

Pinot

Livy

Amaterasu


Markdown
# Incubator PMC report for August 2019

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

This monthly report is in markdown so that it's easier to read. If you are 
not viewing this in that format, it can be seen here:   
https://cwiki.apache.org/confluence/display/INCUBATOR/August2019

There are presently 47 podlings incubating. In July, podlings executed X9
distinct releases. We added five IPMC members and no IPMC members retired. 
We have no new podlings this month, but there have been a couple of enquires
about new projects, and some proposals are being worked on. A couple of 
podlings are heading towards graduation in the next few months, including 
Druid.

Some podlings *list names* Amaterasu, SDAP, Tamaya, Toree didn't submit a report and have 
been asked to do 
so next month.

Two podlings that failed to report last month reported this month. However, 
Amaterasu(?) didn't report for a second time. A couple of podlings had 
trouble getting previous months reports signed off have attracted new 
mentors.

TVM also gained a new mentor. Some podlings are  reporting on or after the
dealinedeadline and not allowing time to discussing the content on list. The 
quality of those reports may suffer as a result.

There were three IP clearances.

Apache Druid has brought up it graduation and may have an issue with its 
name being the same as a project by another company. The problem is being
dealt with, but this may delay graduation depending on the outcome of those
discussions.

The Incubator made a podling release (MXNet) that contained stock photos of 
unknown origin and licensing. Another release (from Tuweini) included 
Category
 X (GPL) licensed software.

The incubator policy page has been cleaned up and updated to be easier to
understand. Anything that was guidelines and not policy has been removed. 
This material was included elsewhere in the incubator and ASF websites, and 
there was no need for the duplication. Podlings can always request to do 
things
 in a different way as long as it is in line with the Apache Way.

Further work was done on a page outlining some of the issues are that 
podlings might encounter during incubation and on the Incubator cookbook. 
The 
incubator homepage was also updated to be more friendly and service 
orientated.

There were several lengthy discussions of the role of the Incubator, and 
its purpose, and while they were a little heated in a few places, they
were constructive.

There seems to be consensus on how the Incubator should handle podling 
releases (see
 proposal below). It's thought that education of mentors 
and podlings on the Apache
 Way is lacking. The Incubator will discuss what 
can be done 
about that.

A couple of podlings have not been able to attract IPMC votes on their
releases in the usual 72 hours.

The missing incubator report wiki pages have been transferred to the new 
wiki.

Based on several months discussion, the Incubator has a proposal for the 
Board to consider.

*Summary*

The Incubator PMC has been discussing allowing podlings to make releases 
which are not fully compliant with the ASF release policies.

Such releases would include a DISCLAIMER-WIP statement of being a "work in 
progress", pointing to the specific issues that make them non-compliant.

The IPMC is seeking approval from the Board to proceed based on the details 
of this proposal, below.

*Some Background*

The IPMC requires clarity from the Board if podlings need to follow ASF's 
release policy and distribution policy while in incubation. This question 
has been asked before, and the answer was unclear or strongly suggested 
that podling releases must follow ASF policy. What is happening in practice 
is that the IPMC allows releases with minor issues to go ahead and assumes 
they will be fixed in a later release (before graduation) and stops 
releases with any serious problem from going ahead (with an IPMC member or 
two voting -1). A -1 vote is not a veto but usually stops a release, 
there's only been a handful of successful releases with -1 votes. We have 
consensus among IPMC members that allowing podling releases with 
minor issues is a correct approach even it doesn't follow ASF policy. 
Serious problems, such as; including GPL licensed software, including
compiled  code, or copyright violations, in a release are currently seen as
a reason to vote -1 on a release. Podlings do try and do the right thing
but about 1 in 5 podling releases has a problem like this. Historically
there's been a few releases with serious issues that have got legal and
Incubator VP approval to make a release on a one by one, once-off basis.
The Incubator wants to allow podling to make non compliant releases to
ease their progress through the incubating process. We've come up with
an alternate disclaimer that clearly states that the release may not be
compliant with ASF release or distribution policy and lists known issues.
The legal committee have confirmed that the the Incubator as a TLP needs
to follow release policy and can only make releases with issues if it
considered to be special in some way.

*Proposal*

The IPMC can allow non-compliant releases to be distributed without IPMC VP 
or legal VP approval, based on a documented list of issues which are 
acceptable for such non-compliant incubating releases. Such releases will
include an alternative "work in progress" DISCLAIMER-WIP to make users aware
of the issues . When this occurs, podlings document the issues as blocking
graduation and carry on incubating. They will not be allowed to graduate 
until
 all such release issues have been fixed.

*Notes*

The IPMC and legal committee have come up with a well-defined list of those
issues. See https://issues.apache.org/jira/browse/LEGAL-469

This list will be distributed to mentors, IPMC members and podlings so
that everyone's expectations are clear. This proposal does not change the
need for an IPMC vote on podling releases, which will be considered
separately.

The new DISPLACMER-WIP disclaimer can be found here:
https://incubator.apache.org/policy/incubation.html#disclaimers

## Community

### New IPMC members:
  - Julian Feinauer
  - Jamie Mark Goodyear
  - Venkat Ranganathan
  - Tianqi Chen
  - Tim Allison 

### People who left the IPMC:
  None

## New Podlings
  None

## Podlings that failed to report, expected next month
  - Amaterasu
  - SDAP
  - Tamaya
  - Toree

## Graduations
  - Druid?

## Releases

  The following releases entered distribution during the month of
  July:
  - TODO

## IP ClearanceFlagon UserALE.JS 2.0.0
  - Celix - TCP pubsub adminWeex 0.26.0
  - Daffodil 2.4.0
  - Celix - HTTP adminDubbo 2.6.7 [1]
  - ServiceComb Mesher

## Legal / TrademarksMxnet 1.5.0
  - Rya 4.0.0
  Legal- has confirmed how podlings releases need to comply with policy.

## Infrastructure
  None.

## Miscellaneous
  - An IPMC member, Sharan Foga, completed a cultural analysis paper 
    Heron 0.20.1
  - OpenWhisk Catalog 0.10.0
  - Apache Doris 0.10.0

  1. Has graduated so not sure why it was placed there, will follow up.

## IP Clearance
  - Celix - TCP pubsub admin
  - Celix - HTTP admin
  - ServiceComb Mesher

## Legal / Trademarks
  Legal has confirmed how podlings releases need to comply with policy.

## Infrastructure
  None.

## Miscellaneous
  - An IPMC member, Sharan Foga, completed a cultural analysis paper 
    featuring several Apache Incubator projects. https://s.apache.org/8uaw3
  - It was confirmed that only VPs of TLP need to subscribe to board@
  - New cross-project IoT mailing list has been created

|----------------------------------------------------------------------
                       Table of Contents

[DataSketches](#DataSketches)  
[Doris](#Doris)  
[ECharts](#ECharts)  
[Edgent](#Edgent)  
[Heron](#Heron)
[MilagroLivy](#Milagro#Livy)
[Milagro](#Milagro)
[PageSpeed](#PageSpeed)  
[Pinot](#Pinot)  
[Ratis](#Ratis)  
[S2Graph](#S2Graph)  
[SDAP](#SDAP)  
[Tamaya](#Tamaya)  
[Toree](#Toree)  
[Training](#Training)  
[Tuweni](#Tuweni)  
[Livy](#Livy)
  

|----------------------------------------------------------------------

--------------------
## DataSketches

DataSketches is an open source, high-performance library of stochastic
streaming algorithms commonly called "sketches" in the data sciences.
Sketches are small, stateful programs that process massive data as a stream
and can provide approximate answers, with mathematical guarantees, to
computationally difficult queries orders-of-magnitude faster than
traditional, exact methods.

DataSketches has been incubating since 2019-03-30.

### Three most important unfinished issues to address before graduating:

  1. Our vote letter on general@ had no responses from anyone (not just IPMC
 members) 
   IPMC members) for the first 73 hours. After sending a pleading
     reminder email I finally got 
     3 +1 binding votes. I'm trying to be
     polite and not needle folks, 
     but I need guidance on how to get IPMC
     members' attention.  I realize the vote
     must stay open for at least
     72 hours, but having to wait until the last minute 
get any response
   get any response is very aggravating. Would it be fair to send out reminder
 notices on
   notices on 24 hour intervals?
  2. Continue to perfect the release process.
  3. After we get this first release, we need to finish migrating the 
     remaining repos.

### Are there any issues that the IPMC or ASF Board need to be aware of?
  1. Yes. In addition to #1 above, not all of our Mentors have been 
     involved. Why do Mentors sign up if they do not or cannot mentor?

### How has the community developed since the last report?
  Not too much at the committer level. We have drawn the
  interest of a few new scientists in our work, but they did not
  learn of our work from Apache.
  It is still very early.  I am speaking at ApacheCon
  In September, hopefully we can attract some interest there.
  I am hoping to attract some committers.

### How has the project developed since the last report?
  We continue to evolve the project and make commits to the code base.
  We are also heavily integrated into the Druid platform.

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

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

### Date of last release:

  2019-08-02 Our First release of our first component!
  Thanks to: Kenneth Knowles, Furkan Kamaci, Paul King and 
  Justin Mclean for their help.

### When were the last committers or PPMC members elected?
  When we entered incubation.

### Have your mentors been helpful and responsive?
  Two (of 3) of our Mentors have been responsive when they are not 
  otherwise unavailable (vacation, work, etc.)

### Signed-off-by:

  - [X] (datasketches) Liang Chen  
     Comments:  
  - [ ] (datasketches) Kenneth Knowles  
     Comments:  
  - [X] (datasketches) Furkan Kamaci  
     Comments:  

### IPMC/Shepherd notes:
  Justin Mclean: 72 hours is a minimum and a podling may not attract
  all needed votes in that time. I understand it may be frustrating
  but remember IPMC member are volunteers and mostly do this work
  unpaid in their spare time. If you need more Mentors just ask on
  the incubator general list.

--------------------
## 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 unfinished issues to address before graduating:

  1. Develop communities and involve more people
  2. Make version release more frequent
  3. Podling name search

### Are there any issues that the IPMC or ASF Board need to be aware of?

  None

### How has the community developed since the last report?

  Now we have 43 contributors, and 1 more committers.

### How has the project developed since the last report?

  250+ PR have been merged into code base. 0.10.0 version has been released.

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

  2019-07-02

### When were the last committers or PPMC members elected?

  2019-07-02

### Have your mentors been helpful and responsive?

  All mentors have been helpful.

### Signed-off-by:

  - [ X] (doris) Dave Fisher  
     Comments:  
  - [ X] (doris) Willem Ning Jiang  
     Comments:  
  - [ ] (doris) Shao Feng Shi  
     Comments:  

### 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 unfinished issues to address before graduating:

  1. Redirecting echarts.baidu.com to echarts.apache.org. Because we found 
  some speed problem of Apache CDN in China, we haven't done the redirecting
  job yet. We will do more test and ask for help if necessary.
  2. Podling name search. We will try to complete it within this month.
  3. Releasing new versions more frequently.

### Are there any issues that the IPMC or ASF Board need to be aware of?

  No.

### How has the community developed since the last report?

  Two new committers are accepted.

### How has the project developed since the last report?

  We received more pull requests from the community.

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

  2019-03-21

### When were the last committers or PPMC members elected?

  2019-06-11

### Have your mentors been helpful and responsive?

  Yes.

### Signed-off-by:

  - [ ] (echarts) John D. Ament  
     Comments:  
  - [ X] (echarts) Kevin A. McGrail  
     Comments: I 
agree with -Dave. [ ]I (echarts)saw Davethe Fisherclose to 
graduation and it 
  Comments:  
 surprised -me [as ]well. (echarts) TedHow Liuis the 
CDN solution working so we Comments: can 

### IPMC/Shepherd notes:



--------------------
## Edgent

Apache Edgent isunblock athe programmingwebsite SDKtransition?
 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 unfinished issues to address before graduating:

  1. Re-creating a working community
  2. Re-populating the PPMC
  3. Replenishing the group of mentors

### Are there any issues that the IPMC or ASF Board 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).

  Julian started an Approach for „Edgent Next“. This is a suggestion to re-activate activities in the edgent community and integrate it as a middle layer between several other IoT or Edge relared Projects.

  This was also announced on the new iot@apache.org<mailto:iot@apache.org> Mailing list but on both lists no feedbackl was responded yet.

  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 have been four questions asked by users and little discussions about these issues on the list
  * On April, 4th, Julian Feinauer has Talked about Edgent on the building iot 2019
  * On July 16th Julian Feinauer started a discussion About „Edgent Next“ on the edgent and iot Mailing lists[X] (echarts) Dave Fisher  
     Comments:  I don't think that the polling is close to graduation at 
     all. I missed any communication about the CDN issues. There needs
     to be more communication on dev@.
  - [ ] (echarts) Ted Liu  
     Comments:  

### 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 unfinished issues to address before graduating:

  1. Re-creating a working community
  2. Re-populating the PPMC
  3. Replenishing the group of mentors

### Are there any issues that the IPMC or ASF Board 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).

  Julian started an Approach for „Edgent Next“. This is a suggestion to 
  re-activate activities in the edgent community and integrate it as a 
  middle layer between several other IoT or Edge relared Projects.

  This was also announced on the new iot@apache.org<mailto:iot@apache.org> 
  Mailing list but on both lists no feedbackl was responded yet.

  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 projectcommunity developed since the last report?

  According* to JIRATotal, 0we newhave issue82 weresubscribers addedto andour nonemailing werelist, resolvedan inincrease theof last 905 days

### How would yousince assess the podling's maturity?
last report.
  After* theThere withdrawalhave ofbeen mostfour ofquestions theasked activeby committersusers and little PPCMdiscussions members
  currentlyabout these aissues newon committer,the PPMClist
 and mentor-base* hasOn toApril, 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?

  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:  
  - [ ] (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 unfinished issues to address before graduating:

  * Fixing issues with licensing in the repo. 
  * Making several Releases
  * Updating the heron documentation site

### Are there any issues that the IPMC or ASF Board need to be aware of?

- n/a
### How has the community developed since the last report?

The community is gradually growing. Monthly meetups have been regularly and successfully organized.

### How has the project developed since the last report?
There have been bug fixes and feature improvements. Some to note are:
* More memory leak fixes
* Documentation updates
* License fixes
* UI improvements
* Kryo serializer support
* Spouts improvements


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

  2019-07-29

### When were the last committers or PPMC members elected?

March 2019

### Have your mentors been helpful and responsive?
Are things falling through the cracks? If so, please list any
open issues that need to be addressed.

Dave has been helpful and responsive, but other mentors have been much less responsive

### Signed-off-by:

  - [ ] (heron) Jake Farrell  
     Comments:  
  - [ ] (heron) Julien Le Dem  
     Comments:  
  - [ ] (heron) P. Taylor Goetz  
     Comments:  
  - [ ] (heron) Dave Fisher  
     Comments:  

### IPMC/Shepherd notes:

--------------------
## Milagro

Milagro is core security infrastructure and crypto libraries for
decentralised networks and distributed systems.

Milagro has been incubating since 2015-12-21.

### Three most important unfinished issues to address before graduating:

  1. Continue to build relevant and useful crypto libs 
     and applications for decentralised networks in order 
     to grow the ecosystem of users and contributors to the project. 
  2. Get all functions of the project in line with the Apache Way
     so we stay in compliance and can get a release under our belts. 
  3. Get a release under our belts!

### Are there any issues that the IPMC or ASF Board need to be aware of?

  No.

### How has the community developed since the last report?

We continue to garner a lot of interest in the project from the
crypto community.

### How has the project developed since the last report?

We're going to move to have the IPMC vote to approve a release 
of the crypto-c and crypto-js libraries next week. 

We will be scheduling releases of the Decentralized Trust Authority, along
with an upgrade of the website and documentation site this month.

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

  XXXX-XX-XX

### When were the last committers or PPMC members elected?

  Last month.

### Have your mentors been helpful and responsive?

  Yes.

### Signed-off-by:

  - [ ] (milagro) Nick Kew  
     Comments: 
  - [ ] (milagro) Jean-Frederic Clere  
     Comments:  
  - [ ] (milagro) Drew Farris   
     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 unfinished issues to address before graduating:

  1. Produce a release
  2. Grow more active contributors
  3.

### Are there any issues that the IPMC or ASF Board need to be aware of?

  What has been falling through the cracks is actually producing a release
  for review. That has been looked into [1] but the artifact needs a few
  tweaks to get it right according to ASF standards before it makes sense to
  enter the process.

  [1] http://people.apache.org/~oschaaf/mod_pagespeed/

### How has the community developed since the last report?

  One new committer/ppmc member was voted in after contributing
  a series of code changes to the core product.

### How has the project developed since the last report?

  A significant effort is in progress to modernize some aspects of 
  the project as well as simplify the build and dependency management
  by porting the build system from gyp to bazel.
  This is a first step towards the PageSpeed 2.0 plan that was initially
  proposed when entering the incubator.

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

  May 27 2019 (Longinos Ferrando, elected as both committer and PMC member)

### Have your mentors been helpful and responsive?
Are things falling through the cracks? If so, 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:  
  - [ ] (pagespeed) Phil Sorber4th, Julian Feinauer has Talked about Edgent on the building 
  iot 2019
  * On July 16th Julian Feinauer started a discussion About „Edgent Next“ 
  on the edgent and iot Mailing lists

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

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

  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:

  - [x] (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 unfinished issues to address before graduating:

  * Fixing issues with licensing in the repo. 
  * Making several Releases
  * Updating the heron documentation site

### Are there any issues that the IPMC or ASF Board need to be aware of?

  - n/a

### How has the community developed since the last report?

  The community is gradually growing. Monthly meetups have been regularly 
  and successfully organized.

### How has the project developed since the last report?
  There have been bug fixes and feature improvements. Some to note are:
  * More memory leak fixes
  * Documentation updates
  * License fixes
  * UI improvements
  * Kryo serializer support
  * Spouts improvements

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

  2019-07-29

### When were the last committers or PPMC members elected?

  March 2019

### Have your mentors been helpful and responsive?

  Dave has been helpful and responsive, but other mentors have been much 
less 
  responsive

### Signed-off-by:

  - [ ] (heron) Jake Farrell  
     Comments:  
  - [ ] (heron) Julien Le Dem  
     Comments:  
  - [ ] (heron) P. Taylor Goetz  
     Comments:  
  - [X] (heron) Dave Fisher  
     Comments:  

### IPMC/Shepherd notes:

--------------------
## Livy

Livy is web service that exposes a REST interface for managing long running
Apache Spark contexts in your cluster. With Livy, new applications can be
built on top of Apache Spark that require fine grained interaction with many
Spark contexts.

Livy has been incubating since 2017-06-05.

### Three most important unfinished issues to address before graduating:

  1. Grow the community to get more reviews and content
  2. Improve the code quality and expand its scope 
  3. Get more content

### Are there any issues that the IPMC or ASF Board need to be aware of?

  None

### How has the community developed since the last report?

  There're not so many activities since the last report. But we do saw some 
  new contributors were start working on this project.

### How has the project developed since the last report?

  Working on feature development and bug fix, planning to hive a 0.7.0 
  release this year.

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

  2019-04-01

### When were the last committers or PPMC members elected?

  2019-01-22

### Have your mentors been helpful and responsive?

  Yes.

Are things falling through the cracks? If so, please list any
open issues that need to be addressed.

### Signed-off-by:

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

### IPMC/Shepherd notes:

--------------------
## Milagro

Milagro is core security infrastructure and crypto libraries for
decentralised networks and distributed systems.

Milagro has been incubating since 2015-12-21.

### Three most important unfinished issues to address before graduating:

  1. Continue to build relevant and useful crypto libs 
     and applications for decentralised networks in order 
     to grow the ecosystem of users and contributors to the project. 
  2. Get all functions of the project in line with the Apache Way
     so we stay in compliance and can get a release under our belts. 
  3. Get a release under our belts!

### Are there any issues that the IPMC or ASF Board need to be aware of?

  No.

### How has the community developed since the last report?

  We continue to garner a lot of interest in the project from the
  crypto community.

### How has the project developed since the last report?

  We're going to move to have the IPMC vote to approve a release 
  of the crypto-c and crypto-js libraries next week. 

  We will be scheduling releases of the Decentralized Trust Authority, along
  with an upgrade of the website and documentation site this month.

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

  XXXX-XX-XX

### When were the last committers or PPMC members elected?

  Last month.

### Have your mentors been helpful and responsive?

  Yes.

### Signed-off-by:

  - [X] (milagro) Nick Kew  
     Comments: OK, 

### I need to post to dev list about detail in the report!
  - [ ] (milagro) Jean-Frederic Clere  
     Comments:  
  - [ ] (milagro) Drew Farris   
     Comments: 

### IPMC/Shepherd notes:



--------------------
## PinotPageSpeed

PinotPageSpeed isrepresents a distributedseries columnarof storageopen enginesource thattechnologies canto
help ingestmake datathe in real-
time and serve analytical queries at low latency.

Pinotweb faster by rewriting web pages to reduce
latency and bandwidth.

PageSpeed has been incubating since 20182017-1009-1730.

### Three most important unfinished issues to address before graduating:

  1. IncreasingProduce frequencya of release 
  2. AddingGrow more committers from open source communityactive contributors
  3. Getting word out from community (blogs, etc.)

### Are there any issues that the IPMC or ASF Board need to be aware of?

  What has been falling through Pinotthe releasecracks is scheduled to happen quarterly but actually producing a release
  for review. That has been delayedlooked dueinto to[1] abut bugthe weartifact foundneeds ina helixfew
  tweaks thatto get wasit veryright hardaccording to trackASF down. https://github.com/apache/helix/issues/331. We finally standards before it makes sense to
  foundenter the issue, and should be cutting the next release shortly.process.

  [1] http://people.apache.org/~oschaaf/mod_pagespeed/

### How has the community developed since the last report?

  WeOne havenew had open-source contributions to integrate Calcite SQL parser, support for transforms in
  selections and filters, support for kafka-2.0, and several other bug fixes and performance
  enhancements. Other contributions on upsert feature, and deep-store commit are in the design process.
  Contributions from outside of Linkedin:
   - UDF support in filter predicates: https://github.com/apache/incubator-pinot/pull/4365
   - Kafka 2.0 support (work authored across open source community): https://github.com/apache/incubator-pinot/pull/4397
   - Variable length bytes dictionary support: https://github.com/apache/incubator-pinot/pull/4321
   - PQL to SQL enhancement Phase-1 :  https://github.com/apache/incubator-pinot/pull/4216
   - Ideas and discussions on null value support: https://github.com/apache/incubator-pinot/issues/4230
   - Ideas and discussions on SQL support: https://github.com/apache/incubator-pinot/issues/4219
  

### How has the project developed since the last report?
  1. Support for Kafka-2.0 added
  2. Work in progress to move closer to SQL syntax and semantics for constructs supported.
  3. Helix and Pinot controller separation in final phase of development.

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

  2019-02-15

### When were the last committers or PPMC members elected?

  No new PPMC members or committers since incubation

### Have your mentors been helpful and responsive?

 Yes, mentors have been super-helpful and respond to questions in a timely manner.

### Signed-off-by:

  - [ ] (pinot) Kishore Gopalakrishnacommitter/ppmc member was voted in after contributing
  a series of code changes to the core product.

### How has the project developed since the last report?

  A significant effort is in progress to modernize some aspects of 
  the project as well as simplify the build and dependency management
  by porting the build system from gyp to bazel.
  This is a first step towards the PageSpeed 2.0 plan that was initially
  proposed when entering the incubator.

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

  May 27 2019 (Longinos Ferrando, elected as both committer and PMC member)

### Have your mentors been helpful and responsive?

  Mentors have been helpful. 

### Signed-off-by:

  - [x] (pagespeed) Jukka Zitting  
     Comments: The community needs more help from mentors to get the first 
     ASF release out. Unfortunately my availability continues to be fairly 
     limited, to the point where I might need to resign and ask someone else
     to fill in. I'll try to help push things along before our next report,
     and will re-evaluate my usefulness as mentor then.
  - [ ] (pagespeed) Leif Hedstrom  
     Comments:  
  - [X] (pinotpagespeed) JimNick JagielskiKew  
     Comments:  
  - [ ] (pinotpagespeed) Roman Shaposhnik  
     Comments:  
  - [ ] (pinot) Olivier Lamy  
     Comments:  
  - [ ] (pinot) Felix CheungPhil Sorber  
     Comments:  

### IPMC/Shepherd notes:



--------------------
## RatisPinot

RatisPinot is a javadistributed implementationcolumnar forstorage RAFTengine consensus protocol

Ratisthat can ingest data in real-
time and serve analytical queries at low latency.

Pinot has been incubating since 20172018-0110-0317.

### Three most important unfinished issues to address before graduating:

  1. Increasing Establishfrequency aof release cadence.
  2. Podling name search. Adding more committers from open source community
  3. Complete graduation template Getting word out from community (blogs, etc.)

### Are there any issues that the IPMC or ASF Board need to be aware of?

   None

### How has the community developed since the last report?

  2 new contributors, 61 contributors in total.
  20 committers and PPMC members.


### How has the project developed since the last report?
  50 commits, 0.4.0 version RC is out for voting.


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

  - [X] Initial setup
  - [X] Working towards a release cadence.
  - [X] Community building
  - [ ] Nearing graduation
  - [ ] Other:

### Date of last release:

  2019-04-26

### When were the last committers or PPMC members elected?
  2018-12-05

### Have your mentors been helpful and responsive?
  
  Mentors are helpful.

### Signed-off-by:

  - [x] (ratis) Jakob Homan  
     Comments:  
  - [X] (ratis) Uma Maheswara Rao G  
     Comments:  
  - [ ] (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 unfinished issues to address before graduating:

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

### Are there any issues that the IPMC or ASF Board need to be aware of?

None

### How has the community developed since the last report?

- There were some questions and answers from the community about how to getting started.
- New feature requests are opened on JIRA.

### How has the project developed since the last report?

- Providing OpenAPI documentation for REST API is pending since there was lack of discussion.
- It has been very quiet since the last report(only 1 JIRA issue opened).

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

  2019-02-05

### Have your mentors been helpful and responsive?

Our mentor is very helpful and responsive.

### Signed-off-by:

  - [ ] (s2graph) Sergio Fernández  
     Comments:  
  - [ ] (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 unfinished issues to address before graduating:

  1.
  2.
  3.

### Are there any issues that the IPMC or ASF Board 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.

  - [ ] 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?
Are things falling through the cracks? If so, please list any
open issues that need to be addressed.


### Signed-off-by:

  - [ ] (sdap) Jörn Rottmann  
     Comments:  
  - [ ] (sdap) Trevor Grant  
     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 unfinished issues to address before graduating:

  1.
  2.
  3.

### Are there any issues that the IPMC or ASF Board 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.

  - [ ] 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?
Are things falling through the cracks? If so, please list any
open issues that need to be addressed.


### Signed-off-by:
Pinot release is scheduled to happen quarterly but has been delayed due 
  to a bug we found in helix that was very hard to track down. 
  https://github.com/apache/helix/issues/331. We finally 
  found the issue, and should be cutting the next release shortly.

### How has the community developed since the last report?
  We have had open-source contributions to integrate Calcite SQL parser, 
  support for transforms in selections and filters, support for kafka-2.0,
  and several other bug fixes and performance enhancements. Other 
  contributions on upsert feature, and deep-store commit are in the design
  process.
  Contributions from outside of Linkedin:
   - UDF support in filter predicates: 
   https://github.com/apache/incubator-pinot/pull/4365
   - Kafka 2.0 support (work authored across open source community): 
   https://github.com/apache/incubator-pinot/pull/4397
   - Variable length bytes dictionary support: 
   https://github.com/apache/incubator-pinot/pull/4321
   - PQL to SQL enhancement Phase-1 :  
   https://github.com/apache/incubator-pinot/pull/4216
   - Ideas and discussions on null value support: 
   https://github.com/apache/incubator-pinot/issues/4230
   - Ideas and discussions on SQL support: 
   https://github.com/apache/incubator-pinot/issues/4219
  

### How has the project developed since the last report?
  1. Support for Kafka-2.0 added
  2. Work in progress to move closer to SQL syntax and semantics for 
  constructs supported.
  3. Helix and Pinot controller separation in final phase of development.

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

  2019-02-15

### When were the last committers or PPMC members elected?

  No new PPMC members or committers since incubation

### Have your mentors been helpful and responsive?

 Yes, mentors have been super-helpful and respond to questions in a timely 
  manner.

### Signed-off-by:

  - [ ] (pinot) Kishore Gopalakrishna  
     Comments:  
  - [X] (pinot) Jim Jagielski  
     Comments:  
  - [ ] (pinot) Roman Shaposhnik  
     Comments:  
  - [ ] (tamayapinot) John D. AmentOlivier Lamy  
     Comments:  
  - [ X] (tamayapinot) DavidFelix BlevinsCheung  
     Comments:  
Nice improvements -to [the ] (tamaya) Kanchana Pradeepika Welagedara  
project. Agreed next steps would 
     be Comments:on community building.

### IPMC/Shepherd notes:



--------------------
## ToreeRatis

Toree provides applications withRatis is a mechanismjava toimplementation interactivelyfor andRAFT remotely
access Apache Spark.consensus protocol

ToreeRatis has been incubating since 20152017-1201-0203.

### Three most important unfinished issues to address before graduating:

  1. Establish a release cadence.
  12.
 Podling name 2search.
  3. Complete graduation template

### Are there any issues that the IPMC or ASF Board need to be aware of?

  None

### How has the community developed since the last report?

  2 new contributors, 61 contributors in total.
  20 committers and PPMC members.

### How has the project developed since the last report?
  50 commits, 0.4.0 version RC is out for voting.

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

  - [ X] Initial setup
  - [ X] Working towards firsta release cadence.
  - [ X] Community building
  - [ ] Nearing graduation
  - [ ] Other:

### Date of last release:

  XXXX2019-XX04-XX26

### When were the last committers or PPMC members elected?
  2018-12-05

### Have your mentors been helpful and responsive?
Are things falling through the cracks? If so, please list any
open issues that need toMentors beare addressedhelpful.


### Signed-off-by:

  - [ x] (toreeratis) LucianoJakob ResendeHoman  
     Comments:  
  - [ X] (toreeratis) Uma JulienMaheswara LeRao DemG  
     Comments:  
  - [ ] (toreeratis) RyanDevaraj BlueDas  
     Comments:  

### IPMC/Shepherd notes:



--------------------
## Training S2Graph

TheS2Graph Trainingis projecta aimsdistributed toand developscalable resourcesOLTP whichgraph candatabase bebuilt usedon forApache
HBase trainingto purposessupport infast varioustraversal mediaof formats,extremely languages and for various Apache and non-Apache target projects. 

Traininglarge graphs.

S2Graph has been incubating since 20192015-0211-2129.

### Three most important unfinished issues to address before graduating:

  1. GrowMake the communitythird torelease.
 get more2. &Attract fastermore reviewsusers and contentcontributors.
  23. ImproveBuild the technologydeveloper stack
community in 3.both Getsize moreand contentdiversity.

### Are there any issues that the IPMC or ASF Board need to be aware of?

  - no critical issues at this point in timeNone

### How has the community developed since the last report?

  - TheThere devwere mailingsome listquestions activityand hasanswers diedfrom downthe acommunity bit.about Thehow totalto number of
 posts in May was 165, June 66, July 36getting started.
  - TotalNew numberfeature of subscribersrequests toare theopened dev list is 31 (-1 since last report)on JIRA.

### How has the project developed since the last report?

  - Providing -OpenAPI Wedocumentation havefor deliveredREST ourAPI firstis releasepending duringsince whichthere wewas ironed
 out alack few issues: https://s.apache.org/jclr6of discussion.
  - It Wehas decidedbeen uponvery aquiet logosince whichthe waslast createdreport(only by1 DanielJIRA Gruno after we reached out to Central Services. Thank you very much for your help!issue opened).

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

  - We had more content donations (ZooKeeper, Ignite, GitHub, Spark)[ ] Initial setup
  - [ ] Working towards first release
  - The ZooKeeper community helped us review the ZooKeeper contribution which was greatly improved due to their reviews. Thank you!
  - A few of the Training members will be present at both ApacheCons this year and there will be multiple talks about the project

### How would you assess the podling's maturity?
Please feel free to add your own commentary.
[x] Community building
  - [ ] Nearing graduation
  - [ ] Other:

### Date of last release:

  2017-08-26

### When were the last committers or PPMC members elected?

  2019-02-05

### Have your mentors been helpful and responsive?

  Our mentor is very helpful and responsive.

### Signed-off-by:

  - [ ] (s2graph) Sergio Fernández  
     Comments:  
  - [X] ](s2graph) InitialWoonsan setupKo  
  - [ ] WorkingComments: towards first release  
  - [X] Community building  
  - [ ] Nearing graduation  
  - [ ] Other:  

### Date of last release:

  2019-07-13: Apache Training (incubating) - Navigating the ASF Incubator Process 1.0, Announcement: https://s.apache.org/h8bct
  It can be viewed online here: https://s.apache.org/wl3w2


### When were the last committers or PPMC members elected?

  n.a.

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

### Signed-off-by:

  - [X] (training) Justin Mclean  
     Comments:   
  - [X] (training) Craig Russell  
     Comments:  
  - [ ] (training) Christofer Dutz  
     Comments:  
  - [X] (training) Lars Francke  
     Comments:  

### IPMC/Shepherd notes:



--------------------
## Tuweni

Tuweni is a set of libraries and other tools to aid development of
blockchain and other decentralized software in Java and other JVM languages.

Tuweni has been incubating since 2019-03-25.

### Three most important unfinished issues to address before graduating:

  1. address some issues in releases and fix pushing to Maven central
  2. attract more committers
  3. build a better community

### Are there any issues that the IPMC or ASF Board need to be aware of?
  None

### How has the community developed since the last report?
  We invited a new committer over to the project, 
  based on their contributions.

### How has the project developed since the last report?
  We voted successfully on release 0.8.1 and are ironing out 
  issues raised in the release vote.

### IPMC/Shepherd notes:

--------------------
## Training 

The Training project aims to develop resources which can be used for 
training purposes in various media formats, languages and for various 
Apache and non-Apache target projects. 

Training has been incubating since 2019-02-21.

### Three most important unfinished issues to address before graduating:

  1. Grow the community to get more & faster reviews and content
  2. Improve the technology stack
  3. Get more content

### Are there any issues that the IPMC or ASF Board need to be aware of?

  - no critical issues at this point in time

### How has the community developed since the last report?

  - The dev mailing list activity has died down a bit. The total number of 
  posts in May was 165, June 66, July 36
  - Total number of subscribers to the dev list is 31 (-1 since last report)

### How has the project developed since the last report?

  - We have delivered our first release during which we ironed out a few 
  issues: https://s.apache.org/jclr6
  - We decided upon a logo which was created by Daniel Gruno after we 
  reached out to Central Services. Thank you very much for your help!
  - We had more content donations (ZooKeeper, Ignite, GitHub, Spark)
  - The ZooKeeper community helped us review the ZooKeeper contribution 
  which was greatly improved due to their reviews. Thank you!
  - A few of the Training members will be present at both ApacheCons this 
  year and there will be multiple talks about the project

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

  2019-07-13: Apache Training (incubating) - Navigating the ASF Incubator 
  Process 1.0, Announcement: https:

  2019-07-24//s.apache.org/h8bct
  It can be viewed online here: https://s.apache.org/wl3w2

### When were the last committers or PPMC members elected?

  no elections yet, we have an invite out to a new committer.
  n.a.

### Have your mentors been helpful and responsive?

  Yes, no problemNot answered.

### Signed-off-by:

  - [X] (tuwenitraining) Jim Jagielski  
     Comments:  
  - [ ] (tuweni) Dave Fisher  
     Comments:  
  - [ ] (tuweni) Kenneth Knowles  
     Comments:Justin Mclean  
     Comments:   
  - [ X] (tuwenitraining) Jean-BaptisteCraig OnofréRussell  
       Comments Comments:  
  - [X] (tuwenitraining) MichaelChristofer WallDutz  
       Comments:  Congrats on your first release!! Comments:  
  - [X] (tuwenitraining) FurkanLars KamaciFrancke  
       Comments Comments:  

### IPMC/Shepherd notes:


--------------------
## LivyTuweni

LivyTuweni is web service that exposes a RESTset interfaceof forlibraries managingand longother running
Apachetools Sparkto contextsaid in your cluster. With Livy, new applications can be
built on top of Apache Spark that require fine grained interaction with many
Spark contexts.

Livydevelopment of
blockchain and other decentralized software in Java and other JVM languages.

Tuweni has been incubating since 20172019-0603-0525.

### Three most important unfinished issues to address before graduating:

  1. address Growsome issues thein communityreleases toand getfix morepushing reviewsto andMaven contentcentral
  2. Improveattract the code quality and expand its scope more committers
  3. build Geta morebetter contentcommunity

### Are there any issues that the IPMC or ASF Board need to be aware of?

  None

### How has the community developed since the last report?

  We There'reinvited nota sonew manycommitter activitiesover sinceto the last report. But we do saw some new contributors were start working on this projectproject, 
  based on their contributions.

### How has the project developed since the last report?

  We voted Workingsuccessfully on feature developmentrelease 0.8.1 and are ironing bugout fix,
 planning toissues hiveraised a 0.7.0in the release this yearvote.

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

  2019-0407-0124

### When were the last committers or PPMC members elected?
  no elections yet, we have an invite out to a new committer.

### Have your mentors been helpful and responsive?
  Yes, no  2019-01-22

### Have your mentors been helpful and responsive?

  Yes.

Are things falling through the cracks? If so, please list any
open issues that need to be addressed.


### Signed-off-by:

problem.

### Signed-off-by:

  - [X] (tuweni) Jim Jagielski  
     Comments:  
  - [X] (tuweni) Dave Fisher  
     Comments:  I don't think that this podling is near graduation.
  - [ ] (livytuweni) BikasKenneth SahaKnowles  
     Comments:  
  - [ ] (livytuweni) BrockJean-Baptiste NolandOnofré  
     Comments:  
  - [ X] (livytuweni) LucianoMichael ResendeWall  
     Comments:  Congrats on your first release!!
  - [ X] (livytuweni) Jean-BaptisteFurkan OnofreKamaci  
     Comments:   

### IPMC/Shepherd notes: