Page History

# Incubator PMC report for July 2020

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

TODOThere add narrative

## Community

### New IPMC members:


### People who left the IPMC:


## New Podlings


## Podlings that failed to report, expected next month


## Graduations
  - list podling here

  The board has motions for the following:

  - Your podling here?

## Releases

  The following releases entered distribution during the month of
  June:


## IP Clearance


## Legal / Trademarks


## Infrastructure


## Miscellaneous


## Credits

## Table of Contents  
[AGE](#age)  
[Annotator](#annotator)  
[APISIX](#apisix)  
[BlueMarlin](#bluemarlin)  
[DolphinScheduler](#dolphinscheduler)
[DLab](#dlab)  
[Flagon](#flagon)  
[Gobblin](#gobblin)  
[Hivemall](#hivemall)  
[Liminal](#liminal)  
[Livy](#livy)  
[Milagro](#milagro)  
[MXNet](#mxnet)  
[NuttX](#nuttx)  
[PonyMail](#ponymail)  
[Spot](#spot)  
[Teaclave](#teaclave)  
[TubeMQ](#tubemq)  
[TVM](#tvm)  
[Warble](#warble)  
[Weex](#weex)  
[YuniKorn](#yunikorn)  


--------------------
## AGE

AGE is a multi-model database that enables graph and relational models built
on PostgreSQL.

AGE has been incubating since 2020-04-29.

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

### Is the PPMC managing the podling's brand / trademarks?
Are 3rd parties respecting and correctly using the podlings
name and brand? If not what actions has the PPMC taken to
correct this? Has the VP, Brand approved the project name?

### Signed-off-by:

  - [ ] (age) Jim Jagielski  
     Comments:  
  - [ ] (age) Kevin Ratnasekera  
     Comments:  
  - [ ] (age) Von Gosling  
     Comments:  
  - [ ] (age) Raphael Bircher  
     Comments:  
  - [ ] (age) Felix Cheung  
     Comments:  

### IPMC/Shepherd notes:



--------------------
## Annotator

Annotator provides annotation enabling code for browsers, servers, and
humans.

Annotator has been incubating since 2016-08-30.

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

### Is the PPMC managing the podling's brand / trademarks?
Are 3rd parties respecting and correctly using the podlings
name and brand? If not what actions has the PPMC taken to
correct this? Has the VP, Brand approved the project name?

### Signed-off-by:

  - [ ] (annotator) Nick Kew  
     Comments:  
  - [ ] (annotator) Tommaso Teofili  
     Comments:  

### IPMC/Shepherd notes:



--------------------
## APISIX

APISIX is a cloud-native microservices API gateway, delivering the ultimate
performance, security,open source and scalable platform for all your APIs
and microservices.

APISIX has been incubating since 2019-10-17.

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

 APISIX have already completed all issue, here is a review since the last report.
  1. We released APISIX 1.2, APISIX 1.3, those release are done by twenty-eight contributors
  2. We added five committers and two PPMC members
  3. Resolved branding issues, such as:
    - The website(http://apisix.apache.org/) shows more clearly that it is an Apache incubator project
  	- The APISIX luarocks package site shows more clearly that itis an Apache incubator project
  	- Removed external links in github's readme document

### 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 have released APISIX 1.2, APISIX 1.3, 
which brings more new features to APISIX and makes APISIX more user-friendly,
such as support for ETCD cluster, support for CORS, etc.,
 please check CHANGELOG for details
- Since the last report, APISIX has elected two PPMC members and five committers. 
Now APISIX has a total of 23 committers and 85 contributors.


### How has the project developed since the last report?
APISIX developed very quickly in the first half of 2020.
 We elected two PPMC members and five commiters,
 as well as a large number of new features and performance improvements,
 such as support for etcd clusters, support for CORS, etc.
 For details, please see CHANGELOG.
Currently, APISIX is ready to release APISIX 1.4, 
and prepare for APISIX 1.5.
At the same time, APISIX's new Dashboard is also under
 development and will soon be put into production.
 It will bring a more stable and easier-to-use management experience for APISIX.

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

 Fri Jun 19 2020 (1.3)

### When were the last committers or PPMC members elected?
- At May 3 are presently 45 podlings incubating. In June, podlings executed 8 
distinct releases. We added no new IPMC members and two retired.

There was one IP clearance in June. There is one new podling Pegasus, 
HBlock is still being discussed, and one new proposal is being prepared. No 
projects graduated last month.

This month we were missing reports from AGE, Annotator, Livy, Warble
and  Weex. All will be asked to report next month. This is the second time 
that Warble has failed to report. It's uncertain why a large number of
podling failed to report but it's likely to be related to current external
events.

As reported last month, MXNet podling releases and download page were not 
in line with ASF release and distribution policy. Since then, further 
issues have been found, as well as trademark and branding issues. The 
project has taken steps to correct these issues, but there are still some 
outstanding concerns. There may not be an active PPMC, as only two people 
seem to be dealing with the issues.

There is currently an ongoing conversation on providing clear guidance to 
podlings who want to distribute releases on various platforms. This 
guidance has existed for some time but has been marked draft.

The Incubator will organise a track at the upcoming Apache@home conference.

A couple of mentors have been added and removed from projects.

Most discussions on the mailing list were around releases and release and 
header policy graduations and new proposals.

Two podlings SDAP and Spot still need to sort out their roster and private 
mailing list subscriptions. They have been reminded again to correct this.

## Community

### New IPMC members:
  None

### People who left the IPMC:
  - Alan Gates
  - Henri Yandell

## New Podlings
  - Pegasus

## Podlings that failed to report, expected next month
  - AGE
  - Annotator
  - Livy
  - Warble
  - Weex

## Graduations
  - None

  The board has motions for the following:

  - APISIX

## Releases

  The following releases entered distribution during the month of
  June:
  - TubeMQ 0.3.0
  - Pinot 0.4.0
  - DataSketches cpp 2.0.0
  - Pagespeed 1.14.36.1
  - DolphinScheduler 1.3.0 
  - IoTDB 0.10.0
  - APISIX 1.4
  - Ratis 0.5.0

## IP Clearance
  - ShardingSphere ElasticJob

## Legal / Trademarks
  - MXNet has multiple trademark issues
  - There are several legal JIRAs about MXNet releases

## Infrastructure
 - N/A

## Miscellaneous
 -  N/A

## Table of Contents  
[AGE](#age)  
[Annotator](#annotator)  
[APISIX](#apisix)  
[BlueMarlin](#bluemarlin)  
[DolphinScheduler](#dolphinscheduler)
[DLab](#dlab)  
[Flagon](#flagon)  
[Gobblin](#gobblin)  
[Hivemall](#hivemall)  
[Liminal](#liminal)  
[Livy](#livy)  
[Milagro](#milagro)  
[MXNet](#mxnet)  
[NuttX](#nuttx)  
[PonyMail](#ponymail)  
[Spot](#spot)  
[Teaclave](#teaclave)  
[TubeMQ](#tubemq)  
[TVM](#tvm)  
[Warble](#warble)  
[Weex](#weex)  
[YuniKorn](#yunikorn)  

--------------------
## APISIX

APISIX is a cloud-native microservices API gateway, delivering the ultimate
performance, security,open source and scalable platform for all your APIs
and microservices.

APISIX has been incubating since 2019-10-17.

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

  APISIX have already completed all issue, here is a review since the last 
  report.
  1. We released APISIX 1.2, APISIX 1.3, those release are done by 
  twenty-eight contributors
  2. We added five committers and two PPMC members
  3. Resolved branding issues, such as:
    - The website(http://apisix.apache.org/) shows more clearly that it is 
    an Apache incubator project
  	- The APISIX luarocks package site shows more clearly that itis an 
    Apache incubator project
  	- Removed external links in github's readme document

### 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 have released APISIX 1.2, APISIX 1.3,
  which brings more new features to APISIX and makes APISIX more 
  user-friendly,
  such as support for ETCD cluster, support for CORS, etc.,
  please check CHANGELOG for details
  - Since the last report, APISIX has elected two PPMC members and five 
  committers.
  Now APISIX has a total of 23 committers and 85 contributors.

### How has the project developed since the last report?
  APISIX developed very quickly in the first half of 2020.
  We elected two PPMC members and five commiters,
  as well as a large number of new features and performance improvements,
  such as support for etcd clusters, support for CORS, etc.
  For details, please see CHANGELOG.
  Currently, APISIX is ready to release APISIX 1.4,
  and prepare for APISIX 1.5.
  At the same time, APISIX's new Dashboard is also under
  development and will soon be put into production.
  It will bring a more stable and easier-to-use management experience for 
  APISIX.

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

  Fri Jun 19 2020 (1.3)

### When were the last committers or PPMC members elected?
  - At May 3 2020 PPMC members elected a new PPMC member @Nirojan 
  Selvanathan
  - At May 29 2020 PPMC members elected a new commiter @ShiningRush
  - At May 3 2020 PPMC members elected a new PPMC member @Akayeshmantha
  - At Jun 8 2020 PPMC members elected a new commiter @qiujiayu
  - At Jun 8 2020 PPMC members elected a new commiter @gxthrj
  - At Jun 9 2020 PPMC members elected a new commiter @LiteSun
  - At Jun 10 2020 PPMC members elected a new PPMC member @Nirojan Selvanathan
- At May 29 2020 PPMC members elected a new commiter @ShiningRush
- At May 3 2020 PPMC members elected a new PPMC member @Akayeshmantha
- At Jun 8 2020 PPMC members elected a new commiter @qiujiayu
- At Jun 8 2020 PPMC members elected a new commiter @gxthrj
- At Jun 9 2020 PPMC members elected a new commiter @LiteSun
- At Jun 10 2020 PPMC members elected a new commiter @dabue

### Have your mentors been helpful and responsive?
Yes, mentors are very helpful.

### Is the PPMC managing the podling's brand / trademarks?
 Yes, We keep tracking podling's brand / trademarks.

### Signed-off-by:

  - [ ] (apisix) Willem Ning Jiang  commiter @dabue

### Have your mentors been helpful and responsive?
  Yes, mentors are very helpful.

### Is the PPMC managing the podling's brand / trademarks?
  Yes, We keep tracking podling's brand / trademarks.

### Signed-off-by:

  - [ ] (apisix) Willem Ning Jiang  
     Comments:  
  - [X] (apisix) Justin Mclean  
     Comments:  
  - [ X] (apisix) JustinKevin McleanRatnasekera  
     Comments:  
  - [ X] (apisix) KevinVon RatnasekeraGosling  
     Comments:  

### IPMC/Shepherd - [ ] (apisix) Von Gosling  
     Comments:  

### IPMC/Shepherd notes:



---notes:

--------------------
## BlueMarlin

TODO
BlueMarlin will develop a web service to add intelligence functionality to 
a plain ad system.

BlueMarlin has been incubating since 2011-12-23.

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

  1. Project bootstrap and code donation
  2. First release
  3. Building community

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

  BlueMarlin is in the early incubator stage.

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

  The resources creation are on the way (gitbox, Jira, ...) and code 
  donation as well.

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

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

### Date of last release:

  XXXX-XX-XXNone.

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

  None yet.

### Have your mentors been helpful and responsive?

Are  thingsJB fallingis throughcreating the cracks? If so, please list any
open issues that need to be addressedresources to bootstrap project and he's helping on 
  code review heading to code donation.

### Is the PPMC managing the podling's brand / trademarks?
Are 3rd parties respecting and correctly using the podlings
name and brand? If not what actions has the PPMC taken to
correct this? Has the VP, Brand approved the project name?No Answer.

### Signed-off-by:

  - [ X] (bluemarlin) TODOJB Onofré  
     Comments:  

### IPMC/Shepherd notes:



--------------------
## DolphinScheduler

Dolphin Scheduler is a distributed and easy-to-expand visual DAG workflow 
scheduling system dedicated to solving the complex dependencies in data 
processing, making the scheduling system out of the box for data processing.

Dolphin Scheduler has been incubating since 2019-8-29.

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

  1. Guide community to commit code and code reivew using Apache way.

  2. Develop more commiters and contributors.

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

  1. Github code contributors grew from 86 to 100, and document contributor 
  grew to 27.
  2. Dolphin Scheduler's users wrote their success use case and spread on 
  Internet.
 
 3. Hold a live telecast about new feature of Dolphin Scheduler with local 
  media, and about 400 people join the on-line event.

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

  1. License re-check due to find a conflicts code license announcement by 
  contributor.
  2. 1.3.1 was ready to release.

### How would you assess the podling's maturity?

  Please feel free to add your own commentary.

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

### Date of last release:

  2020-2-24

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

  2020-5-28

### Have your mentors been helpful and responsive?

  Yes, our mentors help a lot on our progress on restruction.

### Is the PPMC managing the podling's brand / trademarks?

  Yes, We keep tracking podling's brand / trademarks.

### Signed-off-by:

  - [ x] (dolphinscheduler) Sheng Wu  
     Comments: Good to see some PPMC member could identify the LICENSE issue even after release.
  - [ ] (dolphinscheduler) ShaoFeng Shi  
     Comments:
  
- [ ] (dolphinscheduler) Liang Chen  
     Comments:
  
- [ X] (dolphinscheduler) Furkan KAMACI  
     Comments:
  
- [ X] (dolphinscheduler) Kevin Ratnasekera  
     Comments: 

### IPMC/Shepherd notes:




--------------------
## DLab

  DLab is a platform for creating self-service, exploratory data science
  environments in the cloud using best-of-breed data science tools.

  DLab has been incubating since 2018-08-20.

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

  1. Come up with a new name for DLab.
  2. Start graduation steps.
  3.

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

  No issues.

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

  We have a new contributor (jave-developer), who is working 
  to become a committer.

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

  - The team has released v.2.3.0.
  - Now our team is working towards the release v.2.4.0 which 
  contains a lot of new features: bucket browser, audit, support
  
different versions of library installation, custom image for
 
 GCP (previously it has been implemented for AWS and Azure).
 
 On top of that the current release is focused towards software updating.


### 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
  - [X] Other: working towards next release

### Date of last release:

  2020-24-04

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

  The last committer was elected on February 2, 2020.

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

  Yes, our mentors are super helpful and responsive.

### Is the PPMC managing the podling's brand / trademarks?

Are 3rd parties respecting and correctly using the podlings
name and brand? If not what actions has the PPMC taken to
correct this? Has the VP, Brand approved the project name?

  We have a couple of naming options for the product. 
  We agreed we need a name for the umbrella of our accelerators,
 
 rather than providing all products, implemented by our teams
 
 with different names. Process of approving of the new name
  
for the suite of the products is undergoing an internal
 
 review and approval process.

### Signed-off-by:

  - [X] (dlab) P. Taylor Goetz  
     Comments:  
  - [ ] (dlab) Henry Saputra  
     Comments:  
  - [ ] (dlab) Konstantin I Boudnik  
     Comments:  
  - [X] (dlab) Furkan Kamaci  
     Comments:  

### IPMC/Shepherd notes:
  Justin Mclean: Last reports question on the name change was not answered.


--------------------
## Flagon

Flagon is a software tool usability testing platform

Flagon has been incubating since 2016-07-13.

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

  1.
  2. Grow the Flagon Committer/Contributor/Community Base
  32.

### AreRefine thererelease anyprocesses issuesfor thatcore theanalytic IPMC or ASF Board need product (Distill)
  3. Finalize (through vote) Flagon logo, get marketing approvals (e.g swag)

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


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


  * Despite COVID impacts on our community, Flagon remains active
  * No other issues 

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


### How would* youCOVID assesshas theaffected 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.

### Is the PPMC managing the podling's brand / trademarks?
Are 3rd parties respecting and correctly using the podlings
name and brand? If not what actions has the PPMC taken to
correct this? Has the VP, Brand approved the project name?

### Signed-off-by:community engagement and onboarding new committers
  * User base remains strong
  * The community has rallied to participate in ApacheCon@Home

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

  * Project maturity roadmaps & release plans are maintained
  * Sub-projects are being migrated to Git Issues
  * Core product source code is well maintained
  * The community has begun experimenting with OpenTelemetry to expand 
  interest
  * We continue to develop our analytical produce to expand interest

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

  - [ ] (flagon) Lewis John McGibbney  
     Comments:  Initial setup
  - [ ] Working towards first release
  - [ X] (flagon) David Meikle  Community building
  - [ ] Comments:Nearing  graduation
  - [ ] (flagon) Tim Allison  
     Comments:  
  - [ ] (flagon) Furkan Kamaci  
     Comments:  

### IPMC/Shepherd notes:



--------------------
## Gobblin

Gobblin is a distributed data integration framework that simplifies common
aspects of big data integration such as data ingestion, replication,
organization and lifecycle management for both streaming and batch data
ecosystems.

Gobblin has been incubating since 2017-02-23.

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

  1. Review of maturity model and associated tasks (in progress). 
  2. Address gaps identified on whimsy, podling namesearch (in progress).

### 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?
  - Email stats since last report: dev@gobblin.incubator.apache.org : 410 (May), 561 (June)
  - There have been 64 Commits since last report: git log --format='%ci' | grep -cE '((2020-0(5|6)))'
  - 41 ie. 64% of those commits were by non-committers: git log --format='%ae %ci' | grep -E '((2020-0(5|6)))' | cut -d ' ' -f 1 | sort | uniq -c | sort -n

### How has the project developed since the last report?
  - Owen O'Malley joined the Gobblin community as a mentor. 
  - Discussion about graduation has started, and community is working towards it. 
  - Two PPMC members were voted in.
  - Work on new release has started. 

On technical side: 
  - Compaction suite was revamped to make action configurable. 
  - Flow remove feature for Spec executors was added. 
  - LogCopier was improved for long running jobs. 
  - New API for proxy users in Azkaban. 
  - Support for common properties in Helix job scheduler. 
  - Hive Distcp support filter on partitioned or snapshot tables. 
  - Generic wrapper producer client added for Kafka. 
  - Autocommit added in JDBCWriters. 
  - Metrics added in all SpecStore implementations. 
  - Support in GobblinYarnAppLauncher to detach from Yarn app. 
  - Support for overprovisioning Gobblin Yarn containers. 
  - Enabled dataset cleaner to emit Kafka events. 
  - Several other enhancements and bug fixes.

### 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-12-09 
(work on new release has started) 

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

Tamás Németh and Sudarshan Vasudevan for PPMC in June, 2020.

### Have your mentors been helpful and responsive?
Yes.

### Is the PPMC managing the podling's brand / trademarks?
Yes, but we have to perform podling namesearch.

### Signed-off-by:

  - [ ] (gobblin) Jean-Baptiste Onofre  
     Comments:  
  - [ ] (gobblin) Olivier Lamy  
     Comments:  
  - [ ] (gobblin) Owen O'Malley  
     Comments:  

### IPMC/Shepherd notes:



--------------------
## Hivemall

Hivemall is a library for machine learning implemented as Hive
UDFs/UDAFs/UDTFs.

Hivemall has been incubating since 2016-09-13.

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

  1. Community growth (committers and users)
  2. One or more Apache Releases as an Incubator project

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

  PPMC need to consider exit approaches (retiring or graduate as Hive subproject).

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

  Not active. 

  Had an inquiry from a Hive PMC member to be a committer but no contribution made so far.

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

  The development has been calmed down since the last Apache release.

  [Created 2 tickets and resolved 2 issues](https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOrFilterId=project-12320630&periodName=monthly&daysprevious=100&cumulative=true&versionLabels=major&selectedProjectId=12320630&reportKey=com.atlassian.jira.jira-core-reports-plugin%3Acreatedvsresolved-report&Next=Next), mainly hotfixes.

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

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

  Elected Jerome Banks as a committer on April 2, 2018.

### Have your mentors been helpful and responsive?

  Koji is active at mentoring.

### Is the PPMC managing the podling's brand / trademarks?

  Yes, we keep tracking podling's brand / trademarks.

### Signed-off-by:

  - [X] (hivemall) Daniel Dai  
     Comments:  
  - [x] (hivemall) Koji Sekiguchi  
     Comments:  

### IPMC/Shepherd notes:



--------------------
## Liminal

TODO

Liminal has been incubating since 2020-05-23.

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

### Date of last release:

  2020-03-17

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

  * Furkan (Mentor) 2019-07-24
  * Tim Allison (Mentor) 2019-07-17
  * Arthi Vezhavendan (PPMC) 2017-01-24

### Have your mentors been helpful and responsive?

  * Our mentors have been very supportive and responsive

### Is the PPMC managing the podling's brand / trademarks?

  * To date, there are no known issues of 3rd Party misuse of brand
  * 'Flagon' was cleared through the Apache PODLINGNAMESEARCH workflow.
  * 'Flagon' branded graphics will conform to Apache's Trademark and 
  Branding policies.

### Signed-off-by:

  - [ ] (flagon) Lewis John McGibbney  
     Comments:  
  - [ ] (flagon) David Meikle  
     Comments:  
  - [ ] (flagon) Tim Allison  
     Comments:  
  - [X] (flagon) Furkan Kamaci  
     Comments:  

### IPMC/Shepherd notes:

--------------------
## Gobblin

Gobblin is a distributed data integration framework that simplifies common
aspects of big data integration such as data ingestion, replication,
organization and lifecycle management for both streaming and batch data
ecosystems.

Gobblin has been incubating since 2017-02-23.

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

  1. Review of maturity model and associated tasks (in progress). 
  2. Address gaps identified on whimsy, podling namesearch (in progress).

### 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?
  - Email stats since last report: dev@gobblin.incubator.apache.org : 410 
  (May), 561 (June)
  - There have been 64 Commits since last report: git log --format='%ci' | 
  grep -cE '((2020-0(5|6)))'
  - 41 ie. 64% of those commits were by non-committers: git log 
  --format='%ae %ci' | grep -E '((2020-0(5|6)))' | cut -d ' ' -f 1 | sort |
  uniq -c | sort -n

### How has the project developed since the last report?
  - Owen O'Malley joined the Gobblin community as a mentor. 
  - Discussion about graduation has started, and community is working 
  towards it.
  - Two PPMC members were voted in.
  - Work on new release has started. 

  On technical side:
  - Compaction suite was revamped to make action configurable. 
  - Flow remove feature for Spec executors was added. 
  - LogCopier was improved for long running jobs. 
  - New API for proxy users in Azkaban. 
  - Support for common properties in Helix job scheduler. 
  - Hive Distcp support filter on partitioned or snapshot tables. 
  - Generic wrapper producer client added for Kafka. 
  - Autocommit added in JDBCWriters. 
  - Metrics added in all SpecStore implementations. 
  - Support in GobblinYarnAppLauncher to detach from Yarn app. 
  - Support for overprovisioning Gobblin Yarn containers. 
  - Enabled dataset cleaner to emit Kafka events. 
  - Several other enhancements and bug fixes.

### 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-12-09 (work on new release has started)

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

  Tamás Németh and Sudarshan Vasudevan for PPMC in June, 2020.

### Have your mentors been helpful and responsive?
  Yes.

### Is the PPMC managing the podling's brand / trademarks?
  Yes, but we have to perform podling name search.

### Signed-off-by:

  - [X] (gobblin) Jean-Baptiste Onofre  
     Comments:  
  - [ ] (gobblin) Olivier Lamy  
     Comments:  
  - [ ] (gobblin) Owen O'Malley  
     Comments:  

### IPMC/Shepherd notes:

--------------------
## Hivemall

Hivemall is a library for machine learning implemented as Hive
UDFs/UDAFs/UDTFs.

Hivemall has been incubating since 2016-09-13.

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

  1. Community growth (committers and users)
  2. One or more Apache Releases as an Incubator project

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

  PPMC need to consider exit approaches (retiring or graduate as Hive 
  subproject).

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

  Not active. 

  Had an inquiry from a Hive PMC member to be a committer but no 
  contribution made so far.

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

  The development has been calmed down since the last Apache release.

  [Created 2 tickets and resolved 2 

  issues](https://issues.apache.org/jira/secure/ConfigureReport.jspa?projectOr

  FilterId=project-12320630&periodName=monthly&daysprevious=100&cumulative=tru

  e&versionLabels=major&selectedProjectId=12320630&reportKey=com.atlassian.jir
  a.jira-core-reports-plugin%3Acreatedvsresolved-report&Next=Next), mainly
  hotfixes.

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

  XXXX2019-XX12-XX19

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

  Elected Jerome Banks as a committer on April 2, 2018.

### Have your mentors been helpful and responsive?

Are things fallingKoji throughis theactive cracks? If so, please list any
open issues that need to be addressedat mentoring.

### Is the PPMC managing the podling's brand / trademarks?
Are
 3rd partiesYes, respectingwe andkeep correctly using the podlings
name andtracking podling's brand? If not what actions has the PPMC taken to
correct this? Has the VP, Brand approved the project name?/ trademarks.

### Signed-off-by:

  - [ X] (liminalhivemall) TODODaniel Dai  
     Comments:  
  - [ X] (liminalhivemall) Koji TODOSekiguchi  
     Comments:  

### IPMC/Shepherd notes:



--------------------
## LivyLiminal

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

### Is the PPMC managing the podling's brand / trademarks?
Are 3rd parties respecting and correctly using the podlings
name and brand? If not what actions has the PPMC taken to
correct this? Has the VP, Brand approved the project name?

### Signed-off-by:

  - [ ] (livy) Bikas Saha  
     Comments:  an end-to-end platform for data engineers & scientists, 
allowing them to build, train and deploy machine learning models in a 
robust and agile way. The platform provides the abstractions and 
declarative capabilities for data extraction & feature engineering followed 
by model training and serving. Apache Liminal's goal is to operationalise 
the machine learning process, allowing data scientists to quickly 
transition from a successful experiment to an automated pipeline of model 
training, validation, deployment and inference in production, freeing them 
from engineering and non-functional tasks, and allowing them to focus on 
machine learning code and artifacts.

Liminal has been incubating since 2020-05-23.

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

  1. Bootstrapping resources and code donation
  2. Building community
  3. First release

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

  Liminal is in early incubator stage, creation of resources has been done 
  (gitbox, jira, etc).
  The initial committer list submits ICLA and we are preparing the code 
  donation.

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

  This is the first report for Liminal.

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

  - [X] Initial setup
  - [ ] Working towards first release
  - [ ] (livy) Luciano Resende  Community building
  - [ ] Comments:Nearing  graduation
  - [ ] (livy) Jean-Baptiste Onofre  Other:

### Date of last release:

     Comments:  None yet.

### IPMC/Shepherd notes:



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

Milagro is core security infrastructure and crypto libraries for
decentralized 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 libraries and
applications for decentralized networks in order to grow the
ecosystem of users and contributors to the project.
  2. Continue to improve compliance with the Apache Way. In
particular to update the Milagro website and other project
sites (e.g. Whimsy) in accordance with Apache policies.
  3. Further releases to increase the scope of the Milagro
project, extend the capability of existing releases
and to demonstrate improved compliance with the Apache Way.

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

No significant issues, however, similar to the last report, several
administrative aspects of the project still have not been dealt with
(updating Whimsy, countersigning code signing keys, checking download
links, confirming brand/trademark compliance etc.).  In addition to
this, the private mailing list subscriber list needs clearing of any
non-PPMC members and Kirk Baird still needs to be officially added
to the list of committers.

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

No change.

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

Development has progressed on the Multi Party Computation (MPC) library
working towards an official release.  The library has been successfully
reviewed by the NCC Group and renowned cryptographer Dr. Michael Scott.
Their recommendations have been implemented and their reports will be
added to the library prior to release.  There are plans to improve upon
the library post release - in particular to extend the capability from
a 2 of 2 threshold to an arbitrary m of n threshold.

Development has also progressed on the version of the core cryptographic
library written in Rust.  More work is required for this to be in a
release ready state.

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

  2020-02-10

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

February 2020

### Have your mentors been helpful and responsive?

No issues.

### Is the PPMC managing the podling's brand / trademarks?

No known issues, but further investigation is still required by
the Milagro community.

### Signed-off-by:

  - [ ] (milagro) Nick Kew  
     Comments:  
  - [ ] (milagro) Jean-Frederic Clere  
     Comments:  

### IPMC/Shepherd notes:



--------------------
## MXNet

A Flexible and Efficient Library for Deep Learning

MXNet has been incubating since 2017-01-23.

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

  1. Address licensing and trademark issues for the binary releases in the
community.
  - ONGOING. See update in the next section.
  2. Address release issues. Successfully and smoothly make releases
without WIP disclaimer.
  - ONGOING.
  3. Improve development process and tooling to help reduce the overhead of
releases
  - ONGOING.

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

  1. Binary Distribution Licensing Issue
  2. MXNet 2.0 first public beta, interoperable with NumPy, is on the way:
     https://github.com/apache/incubator-mxnet/projects/18
     RFC: https://github.com/apache/incubator-mxnet/issues/16167

#### Issues with releases and distributions

##### Background
In May 2020 The MXNet PPMC has proactively initiated a ASF policy compliance
review [1] and a license review [2] with the Apache Legal team.

The license review uncovered that

- Building unmodified MXNet release source code with the optional NVidia GPU
  support enabled results in a binary subject to restrictions of NVidia
EULA.
- PPMC members and committers uploaded convenience releases to
  repository.apache.org which contain Category-X components. Both GPL and
  NVidia EULA components were found.

The policy review uncovered that:

- Prior ASF guidance to the PPMC (December 2018 legal review [3]) was
incomplete
  and did not include a reference to the "unwritten" rule that convenience
  binary distributions created by third-parties using ASF Trademarks must
not
  include Category-X components. Based on this discovery, the Draft
Downstream
  Distribution Branding Policy was updated in June 2020 to include the
  "unwritten" requirement. Based on the updated guidance, PPMC discovered
  various third-party trademark infringements.

The policy review did not yet conclude on the questions if

- The PPMC may create nightly development builds (audience restricted to dev
  list subscribers as per Release policy [4]) for the purpose of testing and
  developing MXNet;

##### List of issues and their status

Justin classified the issues into 14 items.

1) Source and convenance binary releases containing Category X licensed
code.

See summary from license review in Background section. Source code releases
do
not contain Category X code; Takedown of binary releases on
repository.apache.org is pending on Apache Infra. (Trademark infringements
of
3rd-parties such as on pypi are discussed separately)

2. Website giving access to downloads of non released/unapproved code.

Website contained links to nightly development builds which have been
removed [5];
Going forward the PPMC intends to begin periodical voting on Alpha and Beta
Releases which will then be linked from the website.

3. Website giving access to releases containing Category X licensed code.

Website contained links to third-party distributions incorporating
Category-X
components (see summary from license review above). Disclaimers were added
to
the website clarifying the third-party status of the releases and their
licenses. [5]

4. Web site doesn't given enough warning to users of the issues with non
(P)PMC releases or making it clear that these are not ASF releases.

Website contained links to third-party distributions incorporating
Category-X
components (see summary from license review above). Disclaimers were added
to
the website clarifying the third-party status of the releases and their
licenses. [5]

5. Maven releases containing Category X licensed code.

When were the last committers or PPMC members elected?Warble

  None yet.

### Have your mentors been helpful and responsive?

  JB has created the resources and now he's helping on code review and 
  donation.

### Is the PPMC managing the podling's brand / trademarks?

  No answer.

### Signed-off-by:

  - [X] (liminal) JB Onofré  
     Comments:  
  - [X] (liminal) Davor Bonaci  
     Comments: the project is in the setup phase.

### IPMC/Shepherd notes:

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

Milagro is core security infrastructure and crypto libraries for
decentralized 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 libraries and
  applications for decentralized networks in order to grow the
  ecosystem of users and contributors to the project.
  2. Continue to improve compliance with the Apache Way. In
  particular to update the Milagro website and other project
  sites (e.g. Whimsy) in accordance with Apache policies.
  3. Further releases to increase the scope of the Milagro
  project, extend the capability of existing releases
  and to demonstrate improved compliance with the Apache Way.

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

  No significant issues, however, similar to the last report, several
  administrative aspects of the project still have not been dealt with
  (updating Whimsy, countersigning code signing keys, checking download
  links, confirming brand/trademark compliance etc.).  In addition to
  this, the private mailing list subscriber list needs clearing of any
  non-PPMC members and Kirk Baird still needs to be officially added
  to the list of committers.

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

  No change.

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

  Development has progressed on the Multi Party Computation (MPC) library
  working towards an official release.  The library has been successfully
  reviewed by the NCC Group and renowned cryptographer Dr. Michael Scott.
  Their recommendations have been implemented and their reports will be
  added to the library prior to release.  There are plans to improve upon
  the library post release - in particular to extend the capability from
  a 2 of 2 threshold to an arbitrary m of n threshold.

  Development has also progressed on the version of the core cryptographic
  library written in Rust.  More work is required for this to be in a
  release ready state.

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

  2020-02-10

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

  February 2020

### Have your mentors been helpful and responsive?

  No issues.

### Is the PPMC managing the podling's brand / trademarks?

  No known issues, but further investigation is still required by
  the Milagro community.

### Signed-off-by:

  - [X] (milagro) Nick Kew  
     Comments:  
  - [X] (milagro) Jean-Frederic Clere  
     Comments:  

### IPMC/Shepherd notes:
  Justin Mclean: What's the hold up with administrative aspects of the
  project? Is the PPMC active?

--------------------
## MXNet

A Flexible and Efficient Library for Deep Learning

MXNet has been incubating since 2017-01-23.

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

  1. Address licensing and trademark issues for the binary releases in the
  community.
  - ONGOING. See update in the next section.
  2. Address release issues. Successfully and smoothly make releases
  without WIP disclaimer.
  - ONGOING.
  3. Improve development process and tooling to help reduce the overhead of
  releases
  - ONGOING.

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

  1. Binary Distribution Licensing Issue
  2. MXNet 2.0 first public beta, interoperable with NumPy, is on the way:
     https://github.com/apache/incubator-mxnet/projects/18
     RFC: https://github.com/apache/incubator-mxnet/issues/16167

#### Issues with releases and distributions

##### Background
  In May 2020 The MXNet PPMC has proactively initiated a ASF policy 
  compliance
  review [1] and a license review [2] with the Apache Legal team.

  The license review uncovered that

  - Building unmodified MXNet release source code with the optional NVidia 
  GPU
  support enabled results in a binary subject to restrictions of NVidia 
  EULA.
  - PPMC members and committers uploaded convenience releases to
  repository.apache.org which contain Category-X components. Both GPL and
  NVidia EULA components were found.

  The policy review uncovered that:

  - Prior ASF guidance to the PPMC (December 2018 legal review [3]) was
  incomplete
  and did not include a reference to the "unwritten" rule that convenience
  binary distributions created by third-parties using ASF Trademarks must 
  not
  include Category-X components. Based on this discovery, the Draft 
  Downstream
  Distribution Branding Policy was updated in June 2020 to include the
  "unwritten" requirement. Based on the updated guidance, PPMC discovered
  various third-party trademark infringements.

  The policy review did not yet conclude on the questions if

  - The PPMC may create nightly development builds (audience restricted to 
  dev
  list subscribers as per Release policy [4]) for the purpose of testing and
  developing MXNet;

##### List of issues and their status

  Justin classified the issues into 14 items.

  1) Source and convenance binary releases containing Category X licensed
  code.

  See summary from license review in Background section. Source code 
  releases
 do
  not contain Category X code; Takedown of binary releases on
  repository.apache.org is pending on Apache Infra. [6] (Trademark infringements
infringements  of
 3rd-parties such as on pypi are discussed separately)

6  2. PyPIWebsite releasesgiving containingaccess Categoryto X licenseddownloads of non released/unapproved code.

There are noWebsite PiPycontained releaseslinks byto thenightly PPMC.development Pleasebuilds referwhich tohave thebeen
 trademark
infringement section of the report.

7. Docker releases containing Category X licensed code.

There are no Docker releases by the PPMC. Please refer to the trademark
infringement section of the report.

8. Docker releases containing unreleased/unapprovedremoved [5];
  Going forward the PPMC intends to begin periodical voting on Alpha and 
  Beta Releases which will then be linked from the website.

  3. Website giving access to releases containing Category X licensed code.

There are noWebsite Dockercontained releaseslinks byto the PPMC. The existence of third-party
releases
containing unreleased code was approved in [3] and is also in line with the
current Downstream Distribution Branding Draft Policy. ("using any
particular
revision from the development branch is OK" [3])

9. Trademark and branding issues with PiPy and Docker releases.

There are no PiPy releases by the PPMC. Please refer to the trademark
infringement section of the report.

10. Trademark and brand issues with naming of releases.

There are no binary releases by the PPMC besides the repository.apache.org
releases discussed above, which are being removed.
Please refer to the trademark infringement section of
the report.

11. Developer releases available to users and public searchable
https://repo.mxnet.io / https://dist.mxnet.io

Links to the nightly development builds were removed from the MXNet website
and
a robot.txt file was added to prevent indexing of the sites. These websites
are
removed from Google search index.

12. Releases and other nightly builds on
https://repo.mxnet.io / https://dist.mxnet.io containing category X
licensed code.

Neither of the two site contains Releases. It is an open question of the
policy
review (see Background section above) if nightly development builds may or
may
not contain Category X components.

13. Lack of clarity on all platforms for what is an ASF release and what is
not.

https://github.com/apache/incubator-mxnet/releases?after=1.2.0 previously
did
not distinguish MXNet releases prior to MXNet joining the Incubator.
Disclaimers
were added.

14. Branding and release of 3rd parties containing unreleased code.
(e.g.
https://docs.nvidia.com/deeplearning/frameworks/mxnet-release-notes/rel_20-0
3.html)

third-party distributions incorporating
  Category-X
  components (see summary from license review above). Disclaimers were added
  to the website clarifying the third-party status of the releases and their
  licenses. [5]

  4. Web site doesn't given enough warning to users of the issues with non
  (P)PMC releases or making it clear that these are not ASF releases.

  Website contained links to third-party distributions incorporating
  Category-X
  components (see summary from license review above). Disclaimers were added
  to the website clarifying the third-party status of the releases and their
  licenses. [5]

  5. Maven releases containing Category X licensed code.

  See summary from license review in Background section. Source code 
  releases do
  not contain Category X code; Takedown of binary releases on
  repository.apache.org is pending on Apache Infra. [6] (Trademark
  infringements of 3rd-parties are discussed separately)

  6. PyPI releases containing Category X licensed code.

  There are no PiPy releases by the PPMC. Please refer to the trademark
  infringement section of the report.

  7. Docker releases containing Category X licensed code.

  There are no Docker releases by the PPMC. Please refer to the trademark
  infringement section of the report.

[1]: https://issues.apache.org/jira/browse/LEGAL-515
[2]: https://issues.apache.org/jira/browse/LEGAL-516
[3]: https://s.apache.org/flvug
[4]: http://www.apache.org/legal/release-policy.html#publication
[5]:
  8. Docker releases containing unreleased/unapproved code.

  There are no Docker releases by the PPMC. The existence of third-party
  releases
  containing unreleased code was approved in [3] and is also in line with 
  the current Downstream Distribution Branding Draft Policy. ("using any
  particular revision from the development branch is OK" [3])

  9. Trademark and branding issues with PiPy and Docker releases.

  There are no PiPy releases by the PPMC. Please refer to the trademark
  infringement section of the report.

  10. Trademark and brand issues with naming of releases.

  There are no binary releases by the PPMC besides the repository.apache.org
  releases discussed above, which are being removed.
  Please refer to the trademark infringement section of
  the report.

  11. Developer releases available to users and public searchable
  https://repo.mxnet.io / https://dist.mxnet.io

  Links to the nightly development builds were removed from the MXNet 
  website and
  a robot.txt file was added to prevent indexing of the sites. These 
  websites are removed from Google search index.

  12. Releases and other nightly builds on
  https://repo.mxnet.io / https://dist.mxnet.io containing category X
  licensed code.

  Neither of the two site contains Releases. It is an open question of the
  policy
  review (see Background section above) if nightly development builds may or
  may not contain Category X components.

  13. Lack of clarity on all platforms for what is an ASF release and what 
  is not.

  https://github.com/apache/incubator-mxnet/commit/b6b40878f0aba2ba5509f3f3a4c
d517a654847ce#diff-19bc831c1dab6d92d2efc3b87ec5c740
[6]: https://issues.apache.org/jira/browse/INFRA-20442

##### Is the PPMC managing the podling's brand / trademarks?

Are 3rd parties respecting and correctly using the podlings name and brand?
If
not what actions has the PPMC taken to correct this? Has the VP, Brand
approved
the project name?

PPMC notes that there are multiple trademark infringements based on both the
redistribution of MXNet with addition of unreleased code and the
redistribution
of MXNet with Category-X GPL and Category-X NVidia components. PPMC intends
to
handle both issues separately:

##### Unauthorized redistribution of unreleased code by third-parties

PPMC members have reached out to the offending third parties (Nvidia
Corporation
and Amazon Web Services) via inofficial channels and notified them of the
problem. If the problem is not resolved by the end of July 2020, PPMC will
request guidance from the Brand Management Team on how to formally notify
the
offenders of their trademark infrigement.

##### Unauthorized redistribution of Category-X GPL and NVidia CUDA EULA
components by third-parties

PPMC members note that the issue of "NVidia CUDA EULA infecting any
application
built with CUDA support" is an industry-wide problem. PPMC is not aware of
any
individual or corporation correctly labeling their binary distributions
subject
to the NVidia CUDA EULA. Instead, PPMC found that for example Facebook
claims
distribution of PyTorch under BSD License (BSD-3) and Google claimns
distribution of Tensorflow under Apache 2.0 License, despite both being
subject
to the CUDA EULA. Thus, PPMC has contacted NVidia Corporation and requested
NVidia Corporation to add clarifying language that applications based on the
CUDA SDK with material additional functionality may be licensed under a
license
of the application owner's choice, consistent with existing industry
"practice".
The issue was also discussed with NVidia and other Deep Learning Framework
implementers during the Nvidia Deep Learning Framework Developer Council
meeting,
during which NVidia promised to conclude their internal review and follow-up
with the PPMC.

Due the substantial overhead of trademark-infringement takedown notices for
any
involved party, PPMC is awaiting NVidia's license clarification. As NVidia
employs a team for working on MXNet, the PPMC is optimistic about receiving
a
detailed clarification and resolution from NVidia.

If NVidia fails to clarify their license or the resolution is unsatisfactory
within Q3 2020, the PPMC will notify any third -parties about their license
infringement and ask them to take down or rename their redistributions
containing Category-X pieces.

Due the substantial overhead of trademark-infringement takedown notices for
any
involved party, PPMC is further awaiting NVidia's clarification prior to
contacting third-parties about trademark infringement due to inclusion of
GPL
components. This is to avoid sending two separate takedown notices in case
of
an unsatisfactory response by NVidia.

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

  * The number of GitHub contributors increased to currently 781
  (2019-03-28; +2.4% since last report)
  * Active discussions on user forums
      * https://discuss.mxnet.io/ (English, 2.8K registered users (+10.5%)
      and 8.1K posts (+5.2%))
      * https://discuss.gluon.ai/ (Chinese, 8.3K registered users (+2.5%)
      and 22.2K posts(+1.3% since last report))
  * Active blogs and social media presence
    * Medium (https://medium.com/apache-mxnet) w/ 1.8k followers
    * Twitter account (https://twitter.com/ApacheMXNet) w/ 2.6k followers
   	(+8.3%)

  * Active video channels
    * YouTube channel  (https://www.youtube.com/apachemxnet) w/ 1.18k
    subscriber (+13.5% since last report)
    * Chinese YouTube channel
    (https://www.youtube.com/channel/UCjeLwTKPMlDt2segkZzw2ZQ) w/ 6.05k
     subscribers (+6.0%)
    * (in China) bilibili space (https://space.bilibili.com/209599371) w/
    24k subscriber (+9.0% since last report)

  * Highlights in MXNet ecosystem
    * Dive into Deep Learning has 73K 28-day active users, and has
      attracted 23.9K stars & 295 contributors on GitHub. It has been
      adopted as a textbook or reference book by 100+ universities from 27
      countries, such as Stanford, MIT, UC Berkeley, CMU.
    * GluonCV v0.7.0 release
      (https://github.com/dmlc/gluon-cv/releases/tag/v0.7.0)
    * GluonNLP v0.9.1 release
      (https://github.com/dmlc/gluon-nlp/releases/tag/v0.9.1)
    * GluonTS v0.5.0 release
      (https://github.com/awslabs/gluon-ts/releases/tag/v0.5.0)
    * Multi-Model Server v1.1.1 release
      (https://github.com/awslabs/mxnet-model-server/releases/tag/v1.1.1)
    * DeepInsight (https://github.com/deepinsight/insightface)
    * Sockeye (https://github.com/awslabs/sockeye)

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

  1) 1.6.0 was released:
  https://github.com/apache/incubator-mxnet/releases/tag/1.6.0
  with over 830+ patches of new features, improvements, and fixes.
  2) 2.0 project: https://github.com/apache/incubator-mxnet/projects/18
  3) Github statistics of last month:
  * May 28, 2020 – June 28, 2020: Excluding merges, 59 authors have
    pushed 79 commits to master and 107 commits to all branches.
    On master, 2,010 files have changed and there have been 10,897
    additions and 274,406 deletions.

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

  2020-02-20

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

  2020-03-02

### Have your mentors been helpful and responsive?

  Yes. Bob has provided guidance on the license issue.

### Signed-off-by:

  - [ ] (mxnet) Henri Yandell
     Comments:
  - [ ] (mxnet) Markus Weimer
     Comments:
  - [ ] (mxnet) Michael Wall
     Comments:
  - [ ] (mxnet) Bob Paulin
     Comments:
  - [ ] (mxnet) Jason Dai
     Comments:

### IPMC/Shepherd notes:



--------------------
## NuttX

NuttX is a mature, real-time embedded operating system (RTOS).

NuttX has been incubating since 2019-12-09.

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

  1. Clear any potential infringing use of the NuttX trademark
  2. Make more releases under Apache
  3. Continue to grow the community with people from different background

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

  * Most communications have moved from old venues to dev@nuttx.apache.org.  
	The dev list contains 168 subscribers, an increase of 30% since our  
    previous report, and is the home of all development discussions and  
    user questions.  
  * Github's PRs and Issues also have their own discussions.  
  * We are seeing new contributors to the project through Github.
  * Three new committers and one mentor have joined the team.

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

  * We have successfully made our first release under the ASF umbrella,  
    NuttX-9.0.  
  * We are already working on our second release.  
  * Contributions are flowing regularly as PRs in GitHub and as patches  
    in the dev list.  
  * Many technical improvements, bug fixes, and new architectures have  
    been collaborated and work continues with upwards of a dozen pull  
    requests on some days.  
  * The nightly build is up and running: https://s.apache.org/wnv2u  
	This has helped us to improve our review process.  
  * The community is currently discussing ideas for a new logo design.  

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

  NuttX-9.0 was released on 2020-05-11.

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

  Last elected PPMC: 2020-01-10

  Last committer added: 2020-05-17

  We have added one new mentor since the last report: Duo Zhang on
  2020-06-01.

### Have your mentors been helpful and responsive?

  Mentors are helpful and responsive.  

### Is the PPMC managing the podling's brand / trademarks?
	
  Podling name was approved on May 17th 2020: https://s.apache.org/4hfzx

### Signed-off-by:

  - [ ] (nuttx) Duo Zhang  
     Comments:  
  - [ ] (nuttx) Junping Du  
     Comments:  
  - [ ] (nuttx) Justin Mclean  
     Comments:  
  - [ ] (nuttx) Mohammad Asif Siddiqui  
     Comments:  
  - [ ] (nuttx) Flavio Paiva Junqueira  
     Comments:  

### IPMC/Shepherd notes:



--------------------
## Pony Mail

Pony Mail is a mail-archiving, archive viewing, and interaction service,
that can be integrated with many email platforms.

Pony Mail has been incubating since 2016-05-27.

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

  1. Grow the community (that's about it)
  2.
  3.

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

### How has the community developed since the last report?
Discussion about graduation has been ongoing, but stagnated in the summer months.
Something to pick up later, no rush on graduationreleases?after=1.2.0 previously
  did not distinguish MXNet releases prior to MXNet joining the Incubator.
  Disclaimers
  were added. Other PPMC platforms do not contain references to non-ASF
  releases
  (MXNet releases made prior to MXNet joining the ASF). The PPMC is aware of
  old third-party releases created prior to MXNet joining the ASF which are
  still
  available, but can be clearly separated from the ASF MXNet releases due to
  the lack of reference to the Apache foundation. PPMC was able to find an
  exemplar
  such release at [7]. If there are concerns from the Incubator, PPMC can
  request
  the third-parties to take down these releases, as editing their 
  Description to include
  references to events (MXNet joining Apache) is not
  supported due to immutability constraints. [8]

  14. Branding and release of 3rd parties containing unreleased code.
  (e.g.


  https://docs.nvidia.com/deeplearning/frameworks/mxnet-release-notes/rel_20-0
  3.html)

  Please refer to the trademark infringement section of the report.

  [1]: https://issues.apache.org/jira/browse/LEGAL-515
  [2]: https://issues.apache.org/jira/browse/LEGAL-516
  [3]: https://s.apache.org/flvug
  [4]: http://www.apache.org/legal/release-policy.html#publication
  [5]:


  https://github.com/apache/incubator-mxnet/commit/b6b40878f0aba2ba5509f3f3a4c
  d517a654847ce#diff-19bc831c1dab6d92d2efc3b87ec5c740
  [6]: https://issues.apache.org/jira/browse/INFRA-20442
  [7]: https://pypi.org/project/mxnet/0.9.5/
  [8]:
  https://mail.python.org/pipermail/distutils-sig/2017-December/031826.html

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

  * The number of GitHub contributors increased to currently 781
  (2019-03-28; +2.4% since last report)
  * Active discussions on user forums
      * https://discuss.mxnet.io/ (English, 2.8K registered users (+10.5%)
      and 8.1K posts (+5.2%))
      * https://discuss.gluon.ai/ (Chinese, 8.3K registered users (+2.5%)
      and 22.2K posts(+1.3% since last report))
  * Active blogs and social media presence
    * Medium (https://medium.com/apache-mxnet) w/ 1.8k followers
    * Twitter account (https://twitter.com/ApacheMXNet) w/ 2.6k followers
   	(+8.3%)

  * Active video channels
    * YouTube channel  (https://www.youtube.com/apachemxnet) w/ 1.18k
    subscriber (+13.5% since last report)
    * Chinese YouTube channel
    (https://www.youtube.com/channel/UCjeLwTKPMlDt2segkZzw2ZQ) w/ 6.05k
     subscribers (+6.0%)
    * (in China) bilibili space (https://space.bilibili.com/209599371) w/
    24k subscriber (+9.0% since last report)

  * Highlights in MXNet ecosystem
    * Dive into Deep Learning has 73K 28-day active users, and has
      attracted 23.9K stars & 295 contributors on GitHub. It has been
      adopted as a textbook or reference book by 100+ universities from 27
      countries, such as Stanford, MIT, UC Berkeley, CMU.
    * GluonCV v0.7.0 release
      (https://github.com/dmlc/gluon-cv/releases/tag/v0.7.0)
    * GluonNLP v0.9.1 release
      (https://github.com/dmlc/gluon-nlp/releases/tag/v0.9.1)
    * GluonTS v0.5.0 release
      (https://github.com/awslabs/gluon-ts/releases/tag/v0.5.0)
    * Multi-Model Server v1.1.1 release
      (https://github.com/awslabs/mxnet-model-server/releases/tag/v1.1.1)
    * DeepInsight (https://github.com/deepinsight/insightface)
    * Sockeye (https://github.com/awslabs/sockeye)

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

  1) 1.6.0 was released:
  https://github.com/apache/incubator-mxnet/releases/tag/1.6.0
  with over 830+ patches of new features, improvements, and fixes.
  2) 2.0 project: https://github.com/apache/incubator-mxnet/projects/18
  3) Github statistics of last month:
  * May 28, 2020 – June 28, 2020: Excluding merges, 59 authors have
    pushed 79 commits to master and 107 commits to all branches.
    On master, 2,010 files have changed and there have been 10,897
    additions and 274,406 deletions.

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

  2020-02-20

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

  2020-03-02

### Have your mentors been helpful and responsive?

  Yes. In particular, Bob has provided guidance on the license and 
  trademark issue.

### Is the PPMC managing the podling's brand / trademarks?

  PPMC notes that there are multiple trademark infringements based on both 
  the redistribution of MXNet with addition of unreleased code and the
  redistribution of MXNet with Category-X GPL and Category-X NVidia
  components. PPMC intends to handle both issues separately.

#### Unauthorized redistribution of unreleased code by third-parties

  PPMC members have reached out to the offending third parties (Nvidia
  Corporation
  and Amazon Web Services) via inofficial channels and notified them of the
  problem. If the problem is not resolved by the end of July 2020, PPMC will
  request guidance from the Brand Management Team on how to formally notify
  the offenders of their trademark infringement.

#### Unauthorized redistribution of Category-X GPL and NVidia CUDA EULA 
  components by third-parties

  PPMC members note that the issue of "NVidia CUDA EULA infecting any
  application
  built with CUDA support" is an industry-wide problem. PPMC is not aware of
  any individual or corporation correctly labeling their binary 
  distributions
  subject
  to the NVidia CUDA EULA. Instead, PPMC found that for example Facebook
  claims distribution of PyTorch under BSD License (BSD-3) and Google claims
  distribution of Tensorflow under Apache 2.0 License, despite both being
  subject to the CUDA EULA. Thus, PPMC has contacted NVidia Corporation and 
  requested
  NVidia Corporation to add clarifying language that applications based on 
  the CUDA SDK with material additional functionality may be licensed under
  a license
  of the application owner's choice, consistent with existing industry
  "practice".
  The issue was also discussed with NVidia and other Deep Learning Framework
  implementers during the Nvidia Deep Learning Framework Developer Council
  meeting,
  during which NVidia promised to conclude their internal review and 
  follow-up with the PPMC.

  PPMC thus recommends to give NVidia the chance to clarify and improve 
  their
  license. As NVidia employs a team for working on MXNet, the PPMC is
  optimistic
  about receiving a detailed clarification and resolution from NVidia.

  If NVidia fails to clarify their license or the resolution is 
  unsatisfactory
  within Q3 2020, the PPMC will notify any third-parties about their license
  infringement and ask them to take down or rename their redistributions
  containing Category-X pieces.

  Due the substantial overhead of trademark-infringement takedown notices 
  for any
  involved party, PPMC is further awaiting NVidia's clarification prior to
  contacting third-parties about trademark infringement due to inclusion of
  GPL
  components. This is to avoid sending two separate takedown notices in case
  of an unsatisfactory response by NVidia.

  The following downstream software distributors are known to the PPMC to be
  using the name MXNet while redistributing Category-X components

  - pypi.org
  - hub.docker.com
  - ngc.nvidia.com
  - aws.amazon.com

### Signed-off-by:

  - [X] (mxnet) Henri Yandell  
     Comments: Kudos to the project on the licensing review; respect to Bob 
     and Justin for their work as well.
  - [ ] (mxnet) Markus Weimer  
     Comments:
  - [X] (mxnet) Michael Wall  
     Comments: Good progress on the issues.  They are complex but important.
  - [X] (mxnet) Bob Paulin  
     Comments: Team is making thoughtful process on the issues.  Lots of 
     good support and experiance coming from VPs of Brand and Incubator PMC.
  - [ ] (mxnet) Jason Dai  
     Comments:

### IPMC/Shepherd notes:
  Justin Mclean: Good to see progress on these issues. But I have two concerns
  a) you may not have an active PPMC b) branding all release as "3rd party" may
  not be the best way to solve the issue. Hopefully the license discussion will
  be fruitful.

--------------------
## NuttX

NuttX is a mature, real-time embedded operating system (RTOS).

NuttX has been incubating since 2019-12-09.

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

  1. Clear any potential infringing use of the NuttX trademark
  2. Make more releases under Apache
  3. Continue to grow the community with people from different background

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

  * Most communications have moved from old venues to dev@nuttx.apache.org. 

  The dev list contains 168 subscribers, an increase of 30% since our
    previous report, and is the home of all development discussions and  
    user questions.  
  * Github's PRs and Issues also have their own discussions.  
  * We are seeing new contributors to the project through Github.
  * Three new committers and one mentor have joined the team.

### How has the project developed since the last report?
A new Web UI is being proposed donated to the project. As things are slow during summer,
this might take a while to sort out.

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

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

### Date of last release:

  2019-04-20

### When were the last committers or PPMC members elected?
Sebb was added to the roster in July of 2017.


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

### Is the PPMC managing the podling's brand / trademarks?
Are 3rd parties respecting and correctly using the podlings
name and brand? If not what actions has the PPMC taken to
correct this? Has the VP, Brand approved the project name?

### Signed-off-by:

  - [ ] (ponymail) John D. Ament  
     Comments:  
  - [x] (ponymail) Sharan Foga  
     Comments:  Work did start on the graduation process but this has now slowed. Community building is key and the proposal for the new UI might help bring in some new volunteers

### IPMC/Shepherd notes:



--------------------
## Spot

Apache Spot is a platform for network telemetry built on an open data model
and Apache Hadoop.

Spot has been incubating since 2016-09-23.

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

  1. Increase community activity in mailing list and commits 
  2. Make the product more approachable for new contributers and users 
  3. Develop a roadmap that focuses on delivering one use case effectively

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

  Not at this time.

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

  We have onboarded new contributers in the past quarter, who are very
  excited to help us increase our capacity to address issues and move
  us to a new level of maturity.  One of the new contributers has adopted
  the responsibility of secretary and ensuring process compliance and 
  improvement for the project facing Apache leadership. 

  We have continued to make further strides towards compliance with all
  Apache Software Foundation requirements for incubating projects,
  particularly ensuring that all contributers are on the private list
  * We have successfully made our first release under the ASF umbrella,  
    NuttX-9.0.  
  * We are already working on our second release.  
  * Contributions are flowing regularly as PRs in GitHub and as patches  
    in the dev list.  
  * Many technical improvements, bug fixes, and new architectures have  
    been collaborated and work continues with upwards of a dozen pull  
    requests on some days.  
  * The nightly build is up and running: https://s.apache.org/wnv2u  
    This has helped us to improve our review process.
  * The community is currently discussing ideas for a new logo design.  

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

  NuttX-9.0 was released on 2020-05-11.

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

  Last elected PPMC: 2020-01-10

  Last committer added: 2020-05-17

  We have added one new mentor since the last report: Duo Zhang on
  2020-06-01.

### Have your mentors been helpful and responsive?

  Mentors are helpful and responsive.  

### Is the PPMC managing the podling's brand / trademarks?

  Podling name was approved on May 17th 2020: https://s.apache.org/4hfzx

### Signed-off-by:

  - [ ] (nuttx) Duo Zhang  
     Comments:  
  - [ ] (nuttx) Junping Du  
     Comments:  
  - [X] (nuttx) Justin Mclean  
     Comments:  
  - [X] (nuttx) Mohammad Asif Siddiqui  
     Comments:  
  - [ ] (nuttx) Flavio Paiva Junqueira  
     Comments:  

### IPMC/Shepherd notes:

--------------------
## Pony Mail

Pony Mail is a mail-archiving, archive viewing, and interaction service,
that can be integrated with many email platforms.

Pony Mail has been incubating since 2016-05-27.

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

  1. Grow the community (that's about it)
  2.
  3.

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

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

  AsDiscussion theabout projectgraduation has abeen largeongoing, backlogbut ofstagnated issuesin inheritedthe from beforesummer its
  contribution,months.
 we continueSomething to emphasizepick findingup issueslater, thatno arerush stillon graduation.

### How relevanthas andthe blockingproject progress,developed andsince addressingthe them.  We have engaged last report?
  withA anew dozenWeb issuesUI andis resolvedbeing quiteproposed adonated fewto ofthe themproject. As things Thereare isslow work
  thatduring issummer,
 ongoing tothis remove a third party dependency which is a major
  impediment to installing the productmight take a while to sort out.

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

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

### Date of last release:

  20172019-0904-08 20

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

  2020-05-14 - Jeremy Nelson  Sebb was added to the roster in July of 2017.

### Have your mentors been helpful and responsive?
  Our mentors have been helpful in onboarding new contributers, and
  in getting us the Whimsy and Clutch reports and updating the website
  so we more completely conform to ASF policy requirements for podlings.

### Is the PPMC managing the podling's brand / trademarks?
  Yes

### Signed-off-by:

  - [ ] (spot) Uma Maheswara Rao G  
     Comments:   No answer.

### Is the PPMC managing the podling's brand / trademarks?
  No answer.

### Signed-off-by:

  - [ ] (ponymail) John D. Ament  
     Comments:  
  - [X] (ponymail) Sharan Foga  
     Comments:  Work did start on the graduation process but this has now 
     slowed. Community building is key and the proposal for the new UI might
     help bring in some new volunteers

### IPMC/Shepherd notes:



--------------------
## TeaclaveSpot

TeaclaveApache Spot is a universalplatform securefor computingnetwork platform,telemetry makingbuilt computation
on privacy-sensitivean open data safemodel
and andApache simpleHadoop.

TeaclaveSpot has been incubating since 20192016-0809-2023.

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

  1. Improve project structure Increase community activity in mailing list and documentationcommits 
  2. GrowMake the community (attracting more committers, contributors, users)product more approachable for new contributers and users 
  3. Publish Apache releases (resolving logistics on Apache release) Develop a roadmap that focuses on delivering one use case effectively

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

No  Not at this time.

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

  We have onboarded new contributers in the past quarter, who are very
  excited to help us increase our capacity to address issues and move
  us to a new level of maturity.  One of the new contributers has adopted

Since the last report, we started to reach out to people using the
project and collect suggestions and encourage them to join in the
community. We have found four organizations and eight projects that
are using either the Teaclave platform and Teaclave's Rust SGX SDK.

We also created a website for the project:
https://teaclave.apache.org/, which contains project description,
community, contributors, documentations and blog posts.

We started a thread to discuss the logo design, but haven't received
any proposal for now. We will drive this issue in the next few weeks.

We observed more people posting feature suggestions and
build/deployment issues. More than five new contributors begin to
contribute bug fixes and introduce new examples.

We started preparing the first Apache release such as logistics on
licenses of third-party libraries  the responsibility of secretary and ensuring process compliance and 
  improvement for the project facing Apache leadership. 

  We have continued to make further strides towards compliance with all
  Apache Software Foundation requirements for incubating projects,
  particularly ensuring that all contributers are on the private list.

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

  As the project has a large backlog of issues inherited from before its
  contribution, we continue to emphasize finding issues that are still 
  relevant and blocking progress, and addressing them.  We have engaged 
  with a dozen issues and resolved quite a few of them.  There is work
  that is ongoing to remove a third party dependency which is a major
  impediment to installing the product.

### How haswould theyou project developedassess since the lastpodling's reportmaturity?

Since the lastPlease report,feel wefree haveto completedadd theyour developmentown roadmapcommentary.

towards  the- first[X] publicInitial release
(https://github.com/apache/incubator-teaclave/issues/121) proposed
last year. We began to put more efforts on improving documents and
building community.

We wrote many documents in recent weeks including:
setup
  - [X] Working towards first release
  - [X] Community building
  - [ ] Nearing graduation
  - Try:[ Tutorials on using the Teaclave platform.] Other:

### Date of last release:

  2017-09- Design: Some explanations of design choices we made.
  - Contribute: Documents on contributing to Teaclave, such as
debugging tips and Rust development guideline.
  - Codebase: Documents for each sub-directory (i.e., libraries in Teaclave).
  - API Docs: Generated API documentations like APIs of Client SDK.

We also provided more examples to help beginners to understand the
basic usages of the projects.

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

N/A

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

We haven't started new committers or PPMC members elections yet.
Currently, our work focuses on improving the documents to make the
project more approachable for newcomers. Additionally, we see some
regular contributors recently mainly focus on helping to improve
examples, SDK, etc.

### Have your mentors been helpful and responsive?

Yes, our mentors help us with the website development and logo design.
Also, our mentors provided valuable thoughts regarding Intel's recent
security issues.

### Is the PPMC managing the podling's brand / trademarks?

We don't find any 3rd parties incorrectly using the podling's name and
brand. The VP, Brand has approved the project name.
(PODLINGNAMESEARCH-175)

### Signed-off-by:

  - [ ] (teaclave) Felix Cheung  
     Comments:  
  - [X] (teaclave) Furkan Kamaci  
     Comments:  
  - [ ] (teaclave) Jianyong Dai  
     Comments:  
  - [ ] (teaclave) Luciano Resende  
     Comments:  
  - [ ] (teaclave) Matt Sicker  
     Comments:  
  - [ ] (teaclave) Zhijie Shen  
     Comments:  

### IPMC/Shepherd notes:



--------------------
## TubeMQ

TubeMQ is a distributed messaging queue (MQ) system.

TubeMQ has been incubating since 2019-11-03.

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

  1.Keep growing the community
  2.Improve documentation, including document translation
  3.Continuously improve system performance and increase system features

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

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

  2020-05-14 - Jeremy Nelson

### Have your mentors been helpful and responsive?
  Our mentors have been helpful in onboarding new contributers, and
  in getting us the Whimsy and Clutch reports and updating the website
  so we more completely conform to ASF policy requirements for podlings.

### Is the PPMC managing the podling's brand / trademarks?
  Yes

### Signed-off-by:

  - [X] (spot) Uma Maheswara Rao G  
     Comments:  Recently project improved on mailing list activities and 
     project needs few more mentors.

### IPMC/Shepherd notes:

--------------------
## Teaclave

Teaclave is a universal secure computing platform, making computation
on privacy-sensitive data safe and simple.

Teaclave has been incubating since 2019-08-20.

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

  1. Improve project structure and documentation
  2. Grow the community (attracting more committers, contributors, users)
  3. Publish Apache releases (resolving logistics on Apache release)

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

  Since the last report, we started to reach out to people using the
  project and collect suggestions and encourage them to join in the
  community. We have found four organizations and eight projects that
  are using either the Teaclave platform and Teaclave's Rust SGX SDK.

  We also created a website for the project:
  https://teaclave.apache.org/, which contains project description,
  community, contributors, documentations and blog posts.

  We started a thread to discuss the logo design, but haven't received
  any proposal for now. We will drive this issue in the next few weeks.

  We observed more people posting feature suggestions and
  build/deployment issues. More than five new contributors begin to
  contribute bug fixes and introduce new examples.

  We started preparing the first Apache release such as logistics on
  licenses of third-party libraries.

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

  Since the last report, we have completed the lastdevelopment report?roadmap
Since the lasttowards report,the TubeMQfirst communitypublic hasrelease
 welcomed one new committer member: the project community has continued to be active,
attracting many contributors for extensive cooperation and contributions,the total number of contributors has increased to 53(code:39,website:14).
At the same time,we have adapted to the project operation style of the Apache community:we move project-related communications,program discussions,
and task implementation to e-mail, transparentize the entire project process, and operate according to community standards.

### How has the project developed since the last report?
We successfully released the first release version according to the Apache process: the project has made a lot of usability improvements under 
the contribution of everyone,including document finishing,support based on Docker and K8S container operation,
and data reporting pipeline support upstream and downstream (Including data access based on Flume,source and sink based on Flink and Spark), etc; 
at the same time, we have also made a lot of adjustments in functions and performance.
For details, please refer to our project issue: https://issues.apache.org/jira/projects/TUBEMQ/issues.

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

  2020-06-08

### When were the last committers or PPMC members elected?
Technoboy- was added as committer on 2020-04-21

### Have your mentors been helpful and responsive?
Yes (https://github.com/apache/incubator-teaclave/issues/121) proposed
  last year. We began to put more efforts on improving documents and
  building community.

  We wrote many documents in recent weeks including:

  - Try: Tutorials on using the Teaclave platform.
  - Design: Some explanations of design choices we made.
  - Contribute: Documents on contributing to Teaclave, such as
  debugging tips and Rust development guideline.
  - Codebase: Documents for each sub-directory (i.e., libraries in 
  Teaclave).
  - API Docs: Generated API documentations like APIs of Client SDK.

  We also provided more examples to help beginners to understand the
  basic usages of the projects.

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

  N/A

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

  We haven't started new committers or PPMC members elections yet.
  Currently, our work focuses on improving the documents to make the
  project more approachable for newcomers. Additionally, we see some
  regular contributors recently mainly focus on helping to improve
  examples, SDK, etc.

### Have your mentors been helpful and responsive?

  Yes, our mentors help us with the website development and logo design.
  Also, our mentors provided valuable thoughts regarding Intel's recent
  security issues.

### Is the PPMC managing the podling's brand / trademarks?
Yes, all good here.



  We don't find any 3rd parties incorrectly using the podling's name and
  brand. The VP, Brand has approved the project name.
  (PODLINGNAMESEARCH-175)

### Signed-off-by:

  - [X] (teaclave) Felix Cheung  
     Comments:  good progress!
  - [X] (tubemqteaclave) JunpingFurkan DuKamaci  
     Comments:  
  - [ ] (tubemqteaclave) JustinJianyong McleanDai  
     Comments:  
  - [ X] (tubemqteaclave) SijieLuciano GuoResende  
     Comments:  
  - [ ] (tubemqteaclave) ZhijieMatt ShenSicker  
     Comments:  
  - [ ] (tubemqteaclave) Jean-BaptisteZhijie OnofreShen  
     Comments:  

### IPMC/Shepherd notes:



--------------------
## TVMTubeMQ

TVMTubeMQ is a fulldistributed stackmessaging openqueue deep learning compiler stack for CPUs, GPUs, and
specialized accelerators. It aims to close the gap between the productivity-
focused deep learning frameworks, and the performance- or efficiency-
oriented hardware backends.

TVM(MQ) system.

TubeMQ has been incubating since 2019-11-03-06.

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

  1. Keep growing the community
  2. Improve documentation, including document translation
  3. Continuously improve system performance and increase system features

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

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

TVM  Since the last report,the TubeMQ community has welcomed fourone new committers/PPMCcommitter members
 since lastmember: report.the Thereproject arecommunity alsohas on-goingcontinued newto committer nominations. 
The community is active and vibrate, with wide collaborations from many contributors. Thebe active,
  attracting many contributors for extensive cooperation and 
  contributions,the total number of contributors has grownincreased to 387.

The community actively works to resolve the items under the guide of the Apache maturity model

https://docs.google.com/document/d/18nyAH-fcptVezAxPQe6H3FeTKPRkujOp1tc1YRSPLok/edit?usp=sharing


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

A lot of improvements have been made. Including wasm/webgpu backend, performance improvement, 
operator/backend coverage, codebase refactor

See also our monthly reports for detailed improvements

- Mar https://discuss.tvm.ai/t/tvm-monthly-march-2020/6199
- Apr https://discuss.tvm.ai/t/tvm-monthly-april-2020/6570
- May https://discuss.tvm.ai/t/tvm-monthly-may-2020/6992

### How would you assess the podling's maturity?

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

### Date of last release:

	2019-12-1

    The community is voting on a new release now

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


### Have your mentors been helpful and responsive?

Our mentors are super helpful.


### Is the PPMC managing the podling's brand / trademarks?

yes

### Signed-off-by:

  - [X] (tvm) Byung-Gon Chun  
     Comments:  
  - [ ] (tvm) Sebastian Schelter  
     Comments:  
  - [X] (tvm) Henry Saputra  
     Comments: Community is growing and healthy
  53(code:39,website:14).
  At the same time,we have adapted to the project operation style of the 
  Apache community:we move project-related communications,program 
  discussions,
  and task implementation to e-mail, transparentize the entire project 
  process, and operate according to community standards.

### How has the project developed since the last report?
  We successfully released the first release version according to the 
  Apache process: the project has made a lot of usability improvements under
  the contribution of everyone,including document finishing,support based 
  on Docker and K8S container operation,
  and data reporting pipeline support upstream and downstream (Including 
  data access based on Flume,source and sink based on Flink and Spark), etc;
  at the same time, we have also made a lot of adjustments in functions and 
  performance.
  For details, please refer to our project issue: 
  https://issues.apache.org/jira/projects/TUBEMQ/issues.

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

  - [ ] (tvm) Timothy Chen  
     Comments:  Initial setup
  - [ ] Working towards first release
  - [X] (tvm) Furkan Kamaci  Community building
  - [ ] Comments:Nearing  graduation
  - [x ] (tvm) Tianqi Chen  
     Comments:  
  - [X] (tvm) Markus Weimer  
     Comments: Looking forward to graduation soon.  

### IPMC/Shepherd notes:



--------------------
## Warble

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

Warble has been incubating since 2018-06-11.

### Three most important 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.

### Is the PPMC managing the podling's brand / trademarks?
Are 3rd parties respecting and correctly using the podlings
name and brand? If not what actions has the PPMC taken to
correct this? Has the VP, Brand approved the project name?

### Signed-off-by:

  - [ ] (warble) Chris Lambertus  
     Comments:  

### IPMC/Shepherd notes:



--------------------
## Weex

Weex is a framework for building Mobile cross-platform high performance UI.

Weex has been incubating since 2016-11-30.

### Three most important 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?


Other:

### Date of last release:

  2020-06-08

### When were the last committers or PPMC members elected?
  Technoboy- was added as committer on 2020-04-21

### Have your mentors been helpful and responsive?
  Yes.

### Is the PPMC managing the podling's brand / trademarks?
  Yes, all good here.

### Signed-off-by:

  - [ ] (tubemq) Junping Du  
     Comments:  
  - [X] (tubemq) Justin Mclean  
     Comments:  
  - [ ] (tubemq) Sijie Guo  
     Comments:  
  - [ ] (tubemq) Zhijie Shen  
     Comments:  
  - [X] (tubemq) Jean-Baptiste Onofre  
     Comments:  

### IPMC/Shepherd notes:

--------------------
## TVM

TVM is a full stack open deep learning compiler stack for CPUs, GPUs, and
specialized accelerators. It aims to close the gap between the productivity-
focused deep learning frameworks, and the performance- or efficiency-
oriented hardware backends.

TVM has been incubating since 2019-03-06.

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

  1. Keep growing the community

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

  TVM community has welcomed four new committers/PPMC members since last 
  report. There are also on-going new committer nominations.
  The community is active and vibrate, with wide collaborations from many 
  contributors. The total number of contributors has grown to 387.

  The community actively works to resolve the items under the guide of the 
  Apache maturity model


  https://docs.google.com/document/d/18nyAH-fcptVezAxPQe6H3FeTKPRkujOp1tc1YRSP
  Lok/edit?usp=sharing

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

  A lot of improvements have been made. Including wasm/webgpu backend, 
  performance improvement,
  operator/backend coverage, codebase refactor

  See also our monthly reports for detailed improvements

  - Mar https://discuss.tvm.ai/t/tvm-monthly-march-2020/6199
  - Apr https://discuss.tvm.ai/t/tvm-monthly-april-2020/6570
  - May https://discuss.tvm.ai/t/tvm-monthly-may-2020/6992

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

  XXXX2019-XX-XX12-1

  The community is voting on a new release now

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

  No answer.

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

### Is the PPMC managing the podling's brand / trademarks?
Are 3rd parties respecting and correctly using the podlings
name and brand? If not what actions has the PPMC taken to
correct this? Has the VP, Brand approved the project name?

### Signed-off-by:

  - [ ] (weex) Willem Ning Jiang
  Our mentors are super helpful.

### Is the PPMC managing the podling's brand / trademarks?

  yes

### Signed-off-by:

  - [X] (tvm) Byung-Gon Chun  
     Comments:  
  - [ ] (tvm) Sebastian Schelter  
     Comments:  
  - [X] (tvm) Henry Saputra  
     Comments: Community is growing and healthy
  - [ ] (tvm) Timothy Chen  
     Comments:  
  - [X] (tvm) Furkan Kamaci  
     Comments:  
  - [X] (tvm) Tianqi Chen  
     Comments:  
  - [ X] (weextvm) MyrleMarkus KrantzWeimer  
     Comments: Looking forward to graduation soon.  

### IPMC/Shepherd notes:



--------------------
## YuniKorn

YuniKorn is a standalone resource scheduler responsible for scheduling batch
jobs and long-running services on large scale distributed systems running in
on-premises environments as well as different public clouds.

YuniKorn has been incubating since 2020-01-21.

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

  1. Gain more contributors and active committers.
  2. Improve documentation and access to the documentation.
  3. Establish a release cadence based on roadmap

### 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 community has provided new use cases and pain points which helped
  shape the roadmap.
  A new website build was contributed to help improve access to the
  documentation.

  The project has presented at two virtual conference receiving great
  feedback. We're now trying to convert the feedback into an expanded
  community.

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

  A large number of changes have been made specifically to the deployment
  and testing side of the project:
  - moved to full Travis CI build
  - added e2e tests
  - provide convenience deployment via helm charts and ASF docker hub

  Beside the deployment and test changes the project has worked on
  stabilising the first release and adding a number of new features.
  Planning for a second release has just begun.

  Some statistics for the report period (2020-04-01 till 2020-06-30)  
  JIRA: 194 created, 133 resolved  
  PRs: 197 resolved, 11 unique contributors (cumulative for all repos)  

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

  2020-05-04

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

  A new committer was voted in and accepted on 16 June 2020.
  No new PPMC members.

### Have your mentors been helpful and responsive?

  Yes, votes and guidance on the release

### Is the PPMC managing the podling's brand / trademarks?

  No issues that we are aware of

### Signed-off-by:

  - [ ] (yunikorn) Junping Du  
     Comments:  
  - [ X] (yunikorn) Felix Cheung  
     Comments:  
  - [ X] (yunikorn) Jason Lowe  
     Comments:  
  - [ ] (yunikorn) Holden Karau  
     Comments:  

### IPMC/Shepherd notes: