Page History

# Incubator PMC report for April 2020

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

TODO 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
  March:


## IP Clearance


## Legal / Trademarks


## Infrastructure


## Miscellaneous


## Credits

Table of Contents  
[Annotator](#Annotator)  
[APISIX](#APISIX)  
[DLab](#DLab)  
[DolphinScheduler](#DolphinScheduler)
[Flagon](#Flagon)  
[Gobblin](#Gobblin)  
[Hivemall](#Hivemall)  
[Hudi](#Hudi)  
[Iceberg](#Iceberg)  
[Livy](#Livy)  
[Milagro](#Milagro)  
[MXNet](#MXNet)  
[NLPCraft](#NLPCraft)  
[NuttX](#NuttX)  
[Pony Mail](#ponymail)  
[Teaclave](#teaclave)  
[TubeMQ](#TubeMQ)  
[TVM](#TVM)  
[Weex](#Weex)  
[YuniKorn](#YuniKorn)  


--------------------
## 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. Release initial versions
  2. Add active contributors
  3. Demonstrate good governance through voting on process improvements.

### 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 had increased mentor activity and increased participation on our
  weekly calls which have both helped improve our momentum.

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

  We walked through the process of cutting a release (0.1.0) and putting that
  release up for a vote. The first vote attempt failed due to a process mistake--we
  sent it to `general@` before we passed it to `dev@`. We then attempted a second
  vote which passed at the project level, but failed when sent to the Incubator list. 
  However, we received valuable feedback from Justin Mclean which we are now
  acting upon. We plan to attempt another release and vote early this month.

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

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

### Date of last release:

  None yet (due to issues with release process and/or voting), but hopefully early
  this month.

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

  No new committers nor PPMC members have been added since the last report.

### Have your mentors been helpful and responsive?

  Nick Kew has been more involved over email and has also been
  in attendance to at least one of the weekly community calls. We have greatly
  appreciated the involvement and look forward to more!

### Signed-off-by:

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

### IPMC/Shepherd notes:



This monthly report is in markdown so that it's easier to read. If you are 
not viewing this in that format, it can be seen here:

https://cwiki.apache.org/confluence/display/INCUBATOR/April2020
There are presently 45 podlings incubating. In March, podlings executed 7 
distinct releases. We added one new IPMC member, and there are a couple of 
outstanding requests, no IPMC members retired.

There was one requested IP clearance. There are four new podlings under 
discussion or VOTE; they are AgenisGraph, BlueMarlin, HBlock and Rainbow. 
No projects graduated or retired last month. At least one podling is 
heading towards graduation in the next few months, and ShardingSphere has a 
resolution to graduate. All projected reported this month which is a 
rarity, but one podling Gobblin failed to get sign off from it's mentors
and will be asked to report again next month.

It's nice to see that due to the covid-19 situation world-wide that things
are operating mostly as usual.

Three podlings MXNet, SDAP and Spot still need to sort out their roster and 
private mailing list subscriptions and look lite they need to be reminded 
again to correct this.

One IPMC member removed by the recent board proposal asked to join again 
and was added back to the IPMC roster.

There was a discussion on graduating Apache ShardingSphere to become a Top 
Level Project and the project corrected some minor branding and trademark 
issues.

Regarding ShardingSphere, there was a discussion "Fork me on Github" the
outcome  of which is that wording should not be used, and the link to
GitHub be a no-follow one.

It was discovered that some podling download pages were not following 
policy (in minor ways). Also, there has been a recent change to use 
download.apache.org rather than using apache.org.dist for .sha and .asc 
links. Some podlings have fixed these issues. However, in most cases, 
podlings will fix this when they make a new release.

A number of podlings have also made releases but are missing download pages 
on their web site; this issue is currently unresolved, and the podlings 
need to be contacted.

The (reasonably frequent) topic on distributing binaries came up again, 
once again underlining the need to have a clear policy around this.

## Community

### New IPMC members:
  - Steve Blackmon

### People who left the IPMC:
  - None

## New Podlings
  - None, but several under discussion.

## Podlings that failed to report, expected next month
  - None

## Graduations
  - none

  The board has motions for the following:
  - ShardingSphere

## Releases

  The following releases entered distribution during the month of
  March:
  - ECharts 4.7.0
  - Flagon useraleJS 2.1.0
  - Hudi 0.5.2
  - Nemo 0.2
  - Pinot 0.3.0
  - ShardingSphere 4.0.1
  - Tuweni 1.0.0

## IP Clearance
  - DotPulsar

## Legal / Trademarks
  - No issues

## Infrastructure
  - No issues

## Miscellaneous
  - None

Table of Contents  
[Annotator](#Annotator)  
[APISIX](#APISIX)  
[DLab](#DLab)  
[DolphinScheduler](#DolphinScheduler)  
[Flagon](#Flagon)  
[Gobblin](#Gobblin)  
[Hivemall](#Hivemall)  
[Hudi](#Hudi)  
[Iceberg](#Iceberg)  
[Livy](#Livy)  
[Milagro](#Milagro)  
[MXNet](#MXNet)  
[NLPCraft](#NLPCraft)  
[NuttX](#NuttX)  
[Pony Mail](#ponymail)  
[Teaclave](#teaclave)  
[TubeMQ](#TubeMQ)  
[TVM](#TVM)  
[Weex](#Weex)  
[YuniKorn](#YuniKorn)  

--------------------
## APISIXAnnotator

APISIXAnnotator isprovides aannotation cloud-nativeenabling microservicescode APIfor gatewaybrowsers, deliveringservers, the
ultimate performance, security, open source and scalable platform for
all your APIs and microservicesand
humans.

APISIX is based on Nginx and etcd. Compared with traditional API
gateways, APISIX has dynamic routing and plug-in hot loading, which is
especially suitable for API management under micro-service system.

APISIX has Annotator has been incubating since 20192016-1008-1730.

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

  1. MoreRelease Apacheinitial Releasesversions
 and more2. committersAdd actactive ascontributors
 release manager3. to
Demonstrate releasegood agovernance version.
 2. More committers and PPMC members.
 3. Branding issues in the documentation, code, website, etc.

through voting on process improvements.

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

 None Not at this time.

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

 - weWe releasedhave threehad Apacheincreased releasesmentor (activity APISIX 1.0, APISIX 1.1 and 
 apisix-dashboard 1.0 ). the APISIX 1.0 is import for us with a lot
 enhancement in the core of Apache APISIX, also fixed many bugs come from
 users's production enviroment. more and more company choose using Apache
 APISIX and feedback experience to the community and we're happy to see 
 that feedback. 4 Apache releases by 4 different release managers till now. 
 - We have 18 committers and 70 contributors (including 18 committers) now.
 since the last report, 5 commiters was elected ( including one core 
 contributor on Openresty and the first committer in Europe @sshniro who 
 introduced Apache APISIX into the EU's industrial Internet Project and 
 made a lot of optimization and improvement , showing the diversity of the
 community ). we also elected first non-initial PPMC member @lilien1010. 
 - We strengthen interaction/cooperation with other Apache project. E.g. 
 Apache skywalking. we also elected @Sheng Wu ( from the PMC of Apache 
 skywalking ) as a member of our PPMC. then he can help us a lot on 
 community building.
 - the official docker image library migrated to Apache.
 - 4 committers of APISIX signed up as mentor of Google summer of code, 
 and add some tasks for it

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

 The project has been quite health, with more than 255 pull requests, 120
 of them have being merged since the last report. on the mail list, 310 
 emails sent by 35 people, divided into 61 topics since the last report.
 Compare to the last report, the number of pull requests have 779% increase
 and the number of merged requests have 380% increase. These pull requests
 are authored by a diverse set of contributors. In order to guide more
 users to get started, we have added a quick start guide and enriched more
 documents. Continue to remind people to communicate via the Apache APISIX
 mailing list. 

 During the peroid，the Pull Request is mainly divided three aspects:
 - Fixing Apache APISIX bug.
 - add new feature and strengthen the stability of the code.
 - enrich more documents.

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

  Fri Feb 24 2020 (1.1)

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

 - At Mar 15 2020 PPMC members elected a new PPMC member @Sheng Wu who help
 us a lot on the mail list. he also share the experience on the apache
 community.  
 - At Mar 24 2020 PPMC members elected a new commiter @Akayeshmantha ( from
 the PMC of Apache Juneau ) who contributed a lot for some new features.

### Have your mentors been helpful and responsive?

 Mentors are responsive and helpful. Things tend to be on the right way.

### 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:  
  - [ ] (apisix) Justin Mclean  
     Comments:  
  - [x] (apisix) Kevin Ratnasekera  
     Comments:  
  - [ ] (apisix) Von Gosling  
     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. Extend the amount of committers.
  3. The team is working towards the release 2.3 and is going to do
this release in the first half of April.

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

  Leonid Frolov has been added as a new committer.

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

  The team is working towards the release v.2.3 which contains 
a lot of new improvements. And the main feature of this 
release is multi-Cloud orchestration for AWS, Azure and GCP. 
Now, a single DLab instance can connect to all Clouds, 
by means of respective set of API's, deployed on cloud endpoints. 
Release 2.3 is planned for Apriland increased participation on our
  weekly calls which have both helped improve our momentum.

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

  We walked through the process of cutting a release (0.1.0) and putting 
  that
  release up for a vote. The first vote attempt failed due to a process 
  mistake we
  sent it to `general@` before we passed it to `dev@`. We then attempted a 
  second
  vote which passed at the project level, but failed when sent to the 
  Incubator list. 
  However, we received valuable feedback from Justin Mclean which we are now
  acting upon. We plan to attempt another release and vote early this month.

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

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

### Date of last release:

  None yet (due to issues with release process and/or voting), but 
  hopefully early this month.

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

  No new committers nor PPMC members have been added since the last report.

### Have your mentors been helpful and responsive?

  Nick Kew has been more involved over email and has also been
  in attendance to at least one of the weekly community calls. We have 
  greatly appreciated the involvement and look forward to more!

### Signed-off-by:

  - [X] (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 is based on Nginx and etcd. Compared with traditional API
gateways, APISIX has dynamic routing and plug-in hot loading, which is
especially suitable for API management under micro-service system.

APISIX has been incubating since 2019-10-17.

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

  1. More Apache Releases and more committers act as release manager to
  release a version.
  2. More committers and PPMC members.
  3. Branding issues in the documentation, code, website, etc.

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

  None

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

  - we released three Apache releases ( APISIX 1.0, APISIX 1.1 and 
  apisix-dashboard 1.0 ). the APISIX 1.0 is import for us with a lot
  enhancement in the core of Apache APISIX, also fixed many bugs come from
  users's production enviroment. more and more company choose using Apache
  APISIX and feedback experience to the community and we're happy to see 
  that feedback. 4 Apache releases by 4 different release managers till now. 
  - We have 18 committers and 70 contributors (including 18 committers) now.
  since the last report, 5 commiters was elected ( including one core 
  contributor on Openresty and the first committer in Europe @sshniro who 
  introduced Apache APISIX into the EU's industrial Internet Project and 
  made a lot of optimization and improvement , showing the diversity of the
  community ). we also elected first non-initial PPMC member @lilien1010. 
  - We strengthen interaction/cooperation with other Apache project. E.g. 
  Apache skywalking. we also elected @Sheng Wu ( from the PMC of Apache 
  skywalking ) as a member of our PPMC. then he can help us a lot on 
  community building.
  - the official docker image library migrated to Apache.
  - 4 committers of APISIX signed up as mentor of Google summer of code, 
  and add some tasks for it

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

  The project has been quite health, with more than 255 pull requests, 120
  of them have being merged since the last report. on the mail list, 310 
  emails sent by 35 people, divided into 61 topics since the last report.
  Compare to the last report, the number of pull requests have 779% increase
  and the number of merged requests have 380% increase. These pull requests
  are authored by a diverse set of contributors. In order to guide more
  users to get started, we have added a quick start guide and enriched more
  documents. Continue to remind people to communicate via the Apache APISIX
  mailing list. 

  During the peroid，the Pull Request is mainly divided three aspects:
  - Fixing Apache APISIX bug.
  - add new feature and strengthen the stability of the code.
  - enrich more documents.

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

### Date of last release:

  2019-10-12Fri Feb 24 2020 (1.1)

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

  The- lastAt committerMar was15 elected2020 onPPMC Februarymembers 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.

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

### Signedelected a new PPMC member @Sheng Wu who help
  us a lot on the mail list. he also share the experience on the apache
  community.  
  - At Mar 24 2020 PPMC members elected a new commiter @Akayeshmantha ( from
  the PMC of Apache Juneau ) who contributed a lot for some new features.

### Have your mentors been helpful and responsive?

  Mentors are responsive and helpful. Things tend to be on the right way.

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

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

### Signed-off-by:

  - [ X] (dlabapisix) P.Willem TaylorNing GoetzJiang  
     Comments:  It's good to see APISIX brings more and more PPMC aboard. 
  - [ X] (dlabapisix) HenryJustin SaputraMclean  
     Comments: Good progress here and nice report.
  - [ X] (dlabapisix) KonstantinKevin IRatnasekera Boudnik  
     Comments:  
  - [X] (dlabapisix) FurkanVon KamaciGosling  
     Comments:  

### IPMC/Shepherd notes:



--------------------
## DolphinSchedulerDLab

DolphinDLab Scheduler is a distributedplatform for andcreating 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 Schedulerself-service, exploratory data science
environments in the cloud using best-of-breed data science tools.

DLab has been incubating since 20192018-808-2920.

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

  1. Develop more committers and contributors.
Come up with a new name for DLab.
  2. MakeExtend the architecture easily to expand for plug-ins. 
3. Make intallation more easily to useamount of committers.
  3. The team is working towards the release 2.3 and is going to do
  this release in the first half of April.

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

  NoneNo issues.

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

1. Github codeLeonid contributorsFrolov grewhas frombeen 62added to 71.
2. More articles were written by users and contributors initiativelyas a new committer.

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

1.  SupportThe Apacheteam Ambariis installworking andtowards DataXthe datarelease ETLv.

2.3 which Refactorcontains worker
 architecture fora betterlot performanceof andnew augmentabilityimprovements.

3. AddAnd resourcethe managementmain tree structure.

  feature of this 
  release  

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

Please feel free to add your is multi-Cloud orchestration for AWS, Azure and GCP. 
  Now, a single DLab instance can connect to all Clouds, 
  by means of respective set of API's, deployed on cloud endpoints. 
  Release 2.3 is planned for April.

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

### Date of last release:

  20202019-210-2412

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

  2020-1-24

### Have your mentors been helpful The last committer was elected on February 2, 2020.

### Have your mentors been helpful and responsive?

  Yes, our mentors helpare a lot on our progress on restructionsuper helpful.

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

  Yes,We Wehave keepa trackingcouple podling'sof brandnaming / trademarks.

### Signed-off-by:

- [ ] (dolphinscheduler) Sheng Wu
  Comments:  
- [ ] (dolphinscheduler) ShaoFeng Shi
  Comments:  
- [ ] (dolphinscheduler) Liang Chen
  Comments:  
- [X] (dolphinscheduler) Furkan KAMACI 
  Comments: 
- [ ] (dolphinscheduler) Kevin Ratnasekera
  Comments: 

### IPMC/Shepherd notes:



--------------------
## 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. Grow the Flagon Committer/Contributor/Community Base
  2. Refine release processes for core analytic 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?

  * None at this time.
  * Flagon will likely draft and vote on a graduation resolution this year.

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

  1. Continued improving release processes and code base
  2. Continued to generate a wide user base
  3. Discussing collaborations for R&D applications
  4. New potential committers are identified and will be introduced soon

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

  1. Project maturity roadmaps & release plans are maintained
  2. Sub-projects are being migrated to Git Issues
  3. Core product source code is well maintained
  4. Analytical products are being refactored to grow user base
  5. Continued attention and improvement in Apache Process

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

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

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

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

  * Our mentors have been very supportive 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?

  * 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  
     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:  
  - [X] (dlab) Henry Saputra  
     Comments:  
  - [X] (dlab) Konstantin I Boudnik  
     Comments:  
  - [X] (dlab) Furkan   
     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. Develop more committers and contributors.
  2. Make the architecture easily to expand for plug-ins. 
  3. Make intallation more easily to use.

### 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 62 to 71.
  2. More articles were written by users and contributors initiatively.

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

  1. Support Apache Ambari install and DataX data ETL.
  2. Refactor worker architecture for better performance and augmentability.
  3. Add resource management tree structure.

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

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

  2020-1-24

### 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:  
  - [ ] (dolphinscheduler) ShaoFeng Shi  
    Comments:  
  - [X] (flagondolphinscheduler) DavidLiang MeikleChen  
     Comments:  
  - [ X] (flagondolphinscheduler) TimFurkan Allison  
     Comments:  
  - [ X] (flagondolphinscheduler) FurkanKevin KamaciRatnasekera  
     Comments:  

### IPMC/Shepherd notes:



--------------------
## GobblinFlagon

GobblinFlagon is a distributedsoftware datatool integrationusability 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 testing platform

Flagon has been incubating since 2016-07-13.

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

  1. RevisitGrow Apachethe Maturity Model assessment. [In progress since last report]Flagon Committer/Contributor/Community Base
  2. Complete house-keeping tasks like revamp website, podling namesearch. 
     [In progress since last report]Refine release processes for core analytic 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?

No.

### How  * None at this time.
  * Flagon will likely draft and vote on a graduation resolution this year.

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

*  New1. committersContinued Leiimproving Sunrelease (lesun)processes and code Kuaibase
 Yu (kuyu).
* Email stats since last report: user@gobblin.incubator.apache.org : 9 dev@gobblin.incubator.apache.org : 1689
* There have been 76 Commits since last report: git log 
  --format='%ci' | grep -cE '((2020-0(1|2|3)))'
* 43 ie. 56% of those commits were by non-committers: git log 
  --format='%ae %ci' | grep -E '((2020-0(1|2|3)))' | cut -d ' ' -f 1 | sort | uniq -c | sort -n

### How has the project developed since the last report?
* Handle orphaned Yarn containers in Gobblin-on-Yarn clusters
* Track and report histogram of observed lag from Gobblin Kafka pipeline
* Refresh flowgraph when templates are modified
* HighLevelConsumer re-design by removing references to ConsumerConnector and KafkaStream
* Add SFTP DataNode type in Gobblin-as-a-Service
* Optimize unnecessary RPCs in distcp-ng
* Supporting Avro logical type recognition in Avro-to-ORC transformation
* Support for direct Avro and Protobuf formats through Parquet writer

### 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 2. Continued to generate a wide user base
  3. Discussing collaborations for R&D applications
  4. New potential committers are identified and will be introduced soon

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

  1. Project maturity roadmaps & release plans are maintained
  2. Sub-projects are being migrated to Git Issues
  3. Core product source code is well maintained
  4. Analytical products are being refactored to grow user base
  5. Continued attention and improvement in Apache Process

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

  20182020-1203-0917

### When were the last committers or PPMC members elected?
Kuai Yu in January 2020 and Lei Sun in February 2020
  * Furkan  (Mentor) 2019-07-24
  * Tim Allison (Mentor) 2019-07-17
  * Arthi Vezhavendan (PPMC) 2017-01-24

### Have your mentors been helpful and responsive?
Yes
  * Our mentors have been very supportive and responsive.

### Is the PPMC managing the podling's brand / trademarks?
Yes,
  but* weTo havedate, tothere performare podling namesearch.

### Signed-off-by:

  - [ ] (gobblin) Jean-Baptiste Onofre  
     Comments:  
  - 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:

  - [ ] (gobblinflagon) Lewis OlivierJohn LamyMcGibbney  
     Comments:  
  - [X] ] (gobblin) Jim Jagielski(flagon) David Meikle  
     Comments: 
  - [ ] (flagon) Tim Allison  
     Comments:  
  - [X] (flagon) Furkan Kamaci  
     Comments:  

### IPMC/Shepherd notes:



--------------------
## HivemallGobblin

HivemallGobblin is a librarydistributed fordata machineintegration learningframework implementedthat assimplifies Hive
UDFs/UDAFs/UDTFs.

Hivemall 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 20162017-0902-1323.

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

  1. Community growth (committers and users) Revisit Apache Maturity Model assessment. [In progress since last 
  report]
  2. One or more Apache Releases as an Incubator project Complete house-keeping tasks like revamp website, podling namesearch. 
     [In progress since last report]

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

- No enough progress since the last report due to changes in PPMC member job roles.
- Makoto is not active since he is taking paternity leave.
- Github watchers/stars are gradually increasing: 252 stars as of April 1 (was 243 on Dec 2)No.

### How has the community developed since the last report?
  * New committers Lei Sun (lesun) and Kuai Yu (kuyu).
  * Email stats since last report: user@gobblin.incubator.apache.org : 9 
  dev@gobblin.incubator.apache.org : 1689
  * There have been 76 Commits since last report: git log 
    --format='%ci' | grep -cE '((2020-0(1|2|3)))'
  * 43 ie. 56% of those commits were by non-committers: git log 
    --format='%ae %ci' | grep -E '((2020-0(1|2|3)))' | cut -d ' ' -f 1 | 
    sort | uniq -c | sort -n

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

The development [has been calmed down](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) since the last Apache release on Dec 2019.

Created 5 minor tickets and resolved 3 issues.

Need to set some major target with new major features to activate the development. 
Also, we need to discuss about exit strategy of the project with PPMCs.

### 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.
Finished [polding name search](https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-176).

### Signed-off-by:

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

### 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, due to recent time constraints, several administrative aspects
of the project have not been dealt with (updating Whimsy, countersigning code signing keys, checking download
links, confirming brand/trademark compliance etc.)

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

Kirk Baird accepted as a new committer and he's now contributing to the Rust version of the Milagro Crypto Library

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

A second official Apache release of the Crypto-C library (2.0.1) was released in February

A new "Multi Party Computation" (MPC) library has been accepted from Qredo Ltd into the Apache Milagro project. 
The new repository is: https://github.com/apache/incubator-milagro-MPC
The code is being optimised, bug fixed, documented and tested (including a proposed external code review by 
the NCC Group) in preparation for its first official Apache release.

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

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

### Date of last release: 
  
2020-2-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:
  - [X] (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 past release issues. Successfully and smoothly make releases
  - ONGOING.
  2. 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. MXNet 2.0 has started (10 projects completed):
     https://github.com/apache/incubator-mxnet/projects/18
     RFC: https://github.com/apache/incubator-mxnet/issues/16167
  2. There have been stability issues and high cost associated with the CI
     system due to complexity and high load.
      * We are sufferring from high failure rate in CI due to technical
      debts such as flaky tests.
      * Efforts on reducing waste in time and cost on CI:
      https://github.com/apache/incubator-mxnet/projects/19
      * We intend to update our toolchain and improve engineering practices
      to address technical debts and improve the development experiences.
      * We want to improve automation and address licensing issues to reduce
      release overhead.
      * We seek experiences from other projects with extensive C/C++
      development on validating for a diverse set of platforms,
      and experiences on reducing the test complexity and runtime.
      We appreciate any lessons other projects can share in these aspects.

### 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.5K registered users (+8.7%)
      and 7.7K posts (+4.0%))
      * https://discuss.gluon.ai/ (Chinese, 8.1K registered users (+6.9%)
      and 21.9K posts(+1.3% since last report))
  * Active blogs and social media presence
    * Medium (https://medium.com/apache-mxnet) w/ 1.8k followers (+5.9%)
    * Twitter account (https://twitter.com/ApacheMXNet) w/ 2.4k followers
   	(+5.4%)

  * Active video channels
    * YouTube channel  (https://www.youtube.com/apachemxnet) w/ 1.04k
    subscriber (+9.6% since last report)
    * Chinese YouTube channel
    (https://www.youtube.com/channel/UCjeLwTKPMlDt2segkZzw2ZQ) w/ 5.71k
     subscribers (+5.7%)
    * (in China) bilibili space (https://space.bilibili.com/209599371) w/
    22k subscriber (+4.8% since last report)

  * Highlights in MXNet ecosystem
    * Dive into Deep Learning has 50.5K 28-day active users, and has
      attracted 20.7K stars & 230+ contributors on GitHub. It has been
      adopted as a textbook or reference book by 70+ universities from 21
      countries, such as MIT, UC Berkeley, CMU, UPenn, IIT Bombay, and NUS.
    * GluonCV v0.6.0 release
      (https://github.com/dmlc/gluon-cv/releases/tag/v0.6.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)
    * MXNet Model Server v1.1.0 release
      (https://github.com/awslabs/mxnet-model-server/releases/tag/v1.1.0)
    * 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:
  * Feb 28, 2019 – March 28, 2019: Excluding merges, 40 authors have pushed
  75 commits to master and 78 commits to all branches. On master, 404
  files have changed and there have been 17,944 additions and 6,344
  deletions  * Handle orphaned Yarn containers in Gobblin-on-Yarn clusters
  * Track and report histogram of observed lag from Gobblin Kafka pipeline
  * Refresh flowgraph when templates are modified
  * HighLevelConsumer re-design by removing references to ConsumerConnector 
  and KafkaStream
  * Add SFTP DataNode type in Gobblin-as-a-Service
  * Optimize unnecessary RPCs in distcp-ng
  * Supporting Avro logical type recognition in Avro-to-ORC transformation
  * Support for direct Avro and Protobuf formats through Parquet writer

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

### When were the last committers or PPMC members elected?
  Kuai Yu in January 2020 and Lei Sun in February 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) Jim Jagielski  
     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?

  - No enough progress since the last report due to changes in PPMC member 
  job roles.
  - Makoto is not active since he is taking paternity leave.
  - Github watchers/stars are gradually increasing: 252 stars as of April 1 
  (was 243 on Dec 2)

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

  The development [has been calmed down) since the last Apache 
  release on Dec 2019.

  Created 5 minor tickets and resolved 3 issues.

  Need to set some major target with new major features to activate the 
  development. 
  Also, we need to discuss about exit strategy of the project with PPMCs.

### 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.
  Finished [polding name search]
  (https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-176).

### Signed-off-by:

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

### IPMC/Shepherd notes:

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

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

Iceberg has been incubating since 2018-11-16.

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

  1. Grow the Iceberg community
  2. Add more committers and PPMC members

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

  - The community added a committer and PPMC member, Ratandeep Ratti.
    Ratandeep is the 4th new PPMC member.
  - In the 3 months since the last report, 76 pull requests were merged,
    for an average of 25 per month so the contribution rate is still
    active and healthy
  - The community had a video sync with about 20 attendees. These will
    be held about every 3 weeks at alternating times so that contributors
    in Europe and Asia can attend
  - The community is working toward an 0.8.0 release in mid-April

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

  - The community is building support for the upcoming Spark 3.0 release
    and working on moving this to master
  - More Parquet vectorization PRs have been merged, showing significant
    progress
  - A contributor has built support for Spark streaming, which is under
    review
  - Members of the Apache Flink community have been discussing integration
    and have contributed an early Flink sink
  - Support for ORC files is nearly done. Schema evolution, type promotion,
    and support for generics have been recently added
  - Support for cherry-picking append snapshots was added
  - Added new metadata table

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

  - 0.7.0-incubating was released 25 October 2019

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

  - Ratandeep Ratti was added 30 August 2019

### Have your mentors been helpful and responsive?

  Yes.

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

  Yes, the podling is managing the brand and is not aware of any issues.
  The project name has been approved.

### Signed-off-by:

  - [X] (iceberg) Ryan Blue  
     Comments:  
  - [ ] (iceberg) Julien Le Dem  
     Comments:  
  - [X] (iceberg) Owen O'Malley  
     Comments:  
  - [ ] (iceberg) James Taylor  
     Comments:  
  - [X] (iceberg) Carl Steinbach  
     Comments:  

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

## 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, due to recent time constraints, several 
  administrative aspects
  of the project have not been dealt with (updating Whimsy, countersigning 
  code signing keys, checking download
  links, confirming brand/trademark compliance etc.)

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

  Kirk Baird accepted as a new committer and he's now contributing to the 
  Rust version of the Milagro Crypto Library

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

  A second official Apache release of the Crypto-C library (2.0.1) was 
  released in February

  A new "Multi Party Computation" (MPC) library has been accepted from 
  Qredo Ltd into the Apache Milagro project. 
  The new repository is: https://github.com/apache/incubator-milagro-MPC
  The code is being optimised, bug fixed, documented and tested (including 
  a proposed external code review by 
  the NCC Group) in preparation for its first official Apache release.

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

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

### Date of last release: 
  
  2020-2-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:

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

## 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 past release issues. Successfully and smoothly make releases
  - ONGOING.
  2. 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. MXNet 2.0 has started (10 projects completed):
     https://github.com/apache/incubator-mxnet/projects/18
     RFC: https://github.com/apache/incubator-mxnet/issues/16167
  2. There have been stability issues and high cost associated with the CI
     system due to complexity and high load.
      * We are sufferring from high failure rate in CI due to technical
      debts such as flaky tests.
      * Efforts on reducing waste in time and cost on CI:
      https://github.com/apache/incubator-mxnet/projects/19
      * We intend to update our toolchain and improve engineering practices
      to address technical debts and improve the development experiences.
      * We want to improve automation and address licensing issues to reduce
      release overhead.
      * We seek experiences from other projects with extensive C/C++
      development on validating for a diverse set of platforms,
      and experiences on reducing the test complexity and runtime.
      We appreciate any lessons other projects can share in these aspects.

### 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.5K registered users (+8.7%)
      and 7.7K posts (+4.0%))
      * https://discuss.gluon.ai/ (Chinese, 8.1K registered users (+6.9%)
      and 21.9K posts(+1.3% since last report))
  * Active blogs and social media presence
    * Medium (https://medium.com/apache-mxnet) w/ 1.8k followers (+5.9%)
    * Twitter account (https://twitter.com/ApacheMXNet) w/ 2.4k followers
   	(+5.4%)

  * Active video channels
    * YouTube channel  (https://www.youtube.com/apachemxnet) w/ 1.04k
    subscriber (+9.6% since last report)
    * Chinese YouTube channel
    (https://www.youtube.com/channel/UCjeLwTKPMlDt2segkZzw2ZQ) w/ 5.71k
     subscribers (+5.7%)
    * (in China) bilibili space (https://space.bilibili.com/209599371) w/
    22k subscriber (+4.8% since last report)

  * Highlights in MXNet ecosystem
    * Dive into Deep Learning has 50.5K 28-day active users, and has
      attracted 20.7K stars & 230+ contributors on GitHub. It has been
      adopted as a textbook or reference book by 70+ universities from 21
      countries, such as MIT, UC Berkeley, CMU, UPenn, IIT Bombay, and NUS.
    * GluonCV v0.6.0 release
      (https://github.com/dmlc/gluon-cv/releases/tag/v0.6.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)
    * MXNet Model Server v1.1.0 release
      (https://github.com/awslabs/mxnet-model-server/releases/tag/v1.1.0)
    * 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:
  * Feb 28, 2019 – March 28, 2019: Excluding merges, 40 authors have pushed
  75 commits to master and 78 commits to all branches. On master, 404
  files have changed and there have been 17,944 additions and 6,344
  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, mentors have been responsive and helpful as usual

### Signed-off-by:

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

### IPMC/Shepherd notes:

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

## NLPCraft

A Java API to convert natural language into actions.

NLPCraft has been incubating since 2020-02-13.

### Three most important unfinished issues to address before graduating:
  1. Finish migration to Apache process. DONE
  2. Grow an active and healthy community around Apache NLPCraft product.
  ONGOING
  3. Have a stable release schedule and 3 successful product releases.
  ONGOING

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

  No open issues to make IPMC/ASF board aware of. 

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

  No community development as we are in the midst of infra migration trying
  to get the 1st ASF release out.

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

In the first 30 days the project has developed in the following ways:
  - Project infra bootstrap is complete.
  - All three repos have been migrated to ASF infra.
  - GitHub Issues have been migrated to ASF JIRA.
  - All ICLAs have been filed.
  - All new committers accounts are created
  - All code migration is completed & all work on the project is happening
    on ASF infra & using ASF way.
  - NLPCraft 0.5.0 release voting is underway.

### How would you assess the podling's maturity?
  - [ ] Initial setup
  - [X] Working towards first release
  - [ ] Community building
  - [ ] Nearing graduation
  - [ ] Other:

### Date of last release:

  N/A

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

  2020-02-13

### Have your mentors been helpful and responsive?

  Yes, mentors have been responsive and helpful as usual

### Signed-off-by:

  - [X] (wave) Dave Fisher  
    Comments:  
  - [X] (evansye) Evans Ye  
    Comments:  
  - [X] (kamaci) Furkan Kamaci  
    Comments:  
  - [X] (cos) Konstantin I Boudnik  
    Comments:  
  - [X] (paulk) Paul King  
    Comments:  
  - [ ] (rvs) Roman Shaposhnik  

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

## 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. Determine the form and location of NuttX releases
  3. Make the first release under Apache

### 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 extended invitations to two new committers.  
  * One of the new invited committers, Yamamoto Takashi, has accepted,  
    filed an ICLA with the ASF, and has been added to the roster  
    successfully.  
  * The other new invited committer has accepted but is still  
    currently undergoing the ICLA and account creation process.  
  * We continue to see new contributors to the project through GitHub.  
  * Most communications have moved from old venues to  
    dev@nuttx.apache.org. Currently this list is the primary home of  
    all development discussions and users questions. Some users  
    continue to post questions to the old Google Group but we let them  
    know about the move, so as to consolidate the project in one  
    place.  
  * GitHub's PRs and Issues also have their own discussions.

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

  * Regarding making our first release as Apache NuttX (Incubating),  
    the community has agreed on a branch date (April 6th) and a  
    tentative release date of end of April. Furthermore, we have  
    agreed to reinstate the bimonthly releases that NuttX was making  
    prior to becoming a Podling, subsequent to this first release.  
  * One of our PPMC members, Brennan Ashton, has volunteered to be  
    Release Manager (RM) for this first release, provided that we make  
    progress on licensing. To that end, several community members have  
    invested considerable time with Fossology to qualify license  
    headers of various files. As we have nearly 90,000 files in our  
    repository, we expect this work to continue for quite some time,  
    but the goal is to make additional progress at each release.  
  * The nightly build is up and running: https://s.apache.org/wnv2u    
    Our Continuous Integration (CI) system continues to receive  
    various tweaks and fixes. Currently, our automated nightly tests  
    are showing various failures but this is gradually improving.  
  * The community continues to collaborate on various technical  
    improvements, bug fixes, and new architectures. Contributions are  
    flowing regularly as Pull Requests (PRs) in GitHub and as patches  
    emailed to the dev list.  

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

Please feel free to add your own commentary.

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

### Date of last release:

  Still working towards making the first Apache release.

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

  Last elected PPMC: 2020-01-10  
  Last elected Committers: 2020-03-27

### Have your mentors been helpful and responsive?

  Mentors are helpful and responsive.

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

  Some concerns and actions regarding podling's brand were noted in  
  the past reports, however, trademarks issues will be dealt with when  
  graduation draws near.

### Signed-off-by:

  - [ ] (nuttx) Junping Du  
     Comments:  
  - [X] (nuttx) Justin Mclean  
     Comments: Nice detailed report, good to see progress.
  - [ ] (nuttx) Mohammad Asif Siddiqui  
     Comments:  
  - [X] (nuttx) Flavio Paiva Junqueira  
     Comments:  

### IPMC/Shepherd notes:

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

## PonyMail

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

Annotator has been incubating since 2016-05-27.

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

  1. Grow community
  2. Work on release scheduled
  3. 

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

### How has the community developed since the last report?
  The project is discussing graduating from the incubator.
  Feedback is positive, and we are drafting a resolution to the fact.

### How has the project developed since the last report?
  See above.

### 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
  - [xX] Nearing graduation
  - [ ] Other:

### Date of last release:

  20202019-0204-20

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

  2020-03-02

### Have your mentors been helpful and responsive?

  Yes, mentors have been responsive and helpful as usual

### Signed-off-by:

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

### IPMC/Shepherd notes:



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

## PonyMail

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

Annotator has been incubating since 2016-05-27.

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

  1. Grow community
  2. Work on release scheduled
  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?
The project is discussing graduating from the incubator.
Feedback is positive, and we are drafting a resolution to the fact.

### How has the project developed since the last report?
See above.

### 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?
Sebastian Bazley was added as committer on 2017-06-10

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

All good here.

### Signed-off-by:

  - [x] (ponymail) Sharan Foga
     Comments:  Good to see the project starting the graduation process. Increasing the community especially additional developers is challenging, but as a key tool within the ASF, there is a standard user base that may simply need to become engaged.
  - [ ] (ponymail) John D Ament
     Comments:  

### IPMC/Shepherd notes:

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

## Teaclave

Teaclave is a universal secure computing platform.

Teaclave has been incubating since 2019-08-20.

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

  1. Improving project structure and documentation
  2. Grow the community (committers, contributors, users)
  3. Publish 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 last report, one external contributor has became our regular
    contributor.
  - Compared to the last report, we have seen more pull request from external
    contributors.
  - We received emails from some companies which are interested in the
    project and willing to make some contributions for the secure computing
    community.
  - Since we are mainly working on GitHub, with the help of the INFRA team,
    we can sync the notifications of GitHub with our mailing list.

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

  - Since last report, the whole project has been refactored to be more
    functional, as well as readable and approachable for new contributors.
  - We have rewrote the framework for implementing enclave services. Also, we
    have redesigned current services into seven core services
including access control,
    authentication, execution, frontend, management, scheduler, and storage
    service. Communication protocols between services are defined in protobuf.
  - RPC between services has been redesigned to supported TLS-based attestation.
  - We have added DCAP attestation algorithm in the platform so that people can
    deploy the system in environments without Intel's attestation service.
  - Communication between app and enclave has been also redesigned
with better APIs.
  - All updates is currently in the `develop` branch. We plan to merge
into `master`
    when main refactoring is done.

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

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

### Date of last release:

N/A

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

We haven't started new committers or PPMC members elections yet. Currently, our
work focus on improving the design and documents to make the project more
approachable for newcomers.

### Have your mentors been helpful and responsive?

Yes, our mentors help use to resolve the mailing list moderator 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:  
  - [ ] (teaclave) Furkan Kamaci  
     Comments:  
  - [ ] (teaclave) Jianyong Dai  
     Comments:  
  - [ ] (teaclave) Luciano Resende  
     Comments:  
  - [ ] (teaclave) Matt Sicker  
     Comments:
  - [ ] (teaclave) Zhijie Shen  
     Comments:  

### IPMC/Shepherd notes:

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

## Hudi

Hudi provides atomic upserts and incremental data streams on Big Data

Hudi has been incubating since 2019-01-17.

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

  1. Project is ready to graduate from incubator.
  2.
  3.

### 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. 683 conversations on dev ML across 130 topics [1]
2. 75 participants during this period


### How has the project developed since the last report?
1. ~180 Commits in gitbox [2]
2. ~260 issues opened on Jira [3]. ~140 issues resolved in Jira [4]
3. Hudi 0.5.1 released on Jan 31, 2020
4. Hudi 0.5.2 released on March 26, 2020
5. Work in progress for Hudi 0.6.0 planned for Apr 2020.
6. 2 new committers - Sivabalan Narayanan, Lamber-ken
7. 3 new PPMCs - Leesf, Vino Yang, Bhavani Sudha Saktheeswaran
8. Completed the Apache Maturity Matrix for the project [5]
9. Apache Hudi talk at Hadoop Summit Bangalore [6]
10. Apache Hudi & Apache Kylin Online Meetup, China [7] [8]Sebastian Bazley was added as committer on 2017-06-10

### Have your mentors been helpful and responsive?
  No Answer

### Is the PPMC managing the podling's brand / trademarks?
  All good here.

### Signed-off-by:

  - [X] (ponymail) Sharan Foga  
     Comments:  Good to see the project starting the graduation process. 
     Increasing the community especially additional developers is challenging, 
     but as a key tool within the ASF, there is a standard user base that may 
     simply need communication and engagement to become involved.
  - [ ] (ponymail) John D Ament  
     Comments:    

### IPMC/Shepherd notes:

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

## Teaclave

Teaclave is a universal secure computing platform.

Teaclave has been incubating since 2019-08-20.

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

  1. Improving project structure and documentation
  2. Grow the community (committers, contributors, users)
  3. Publish 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 last report, one external contributor has became our regular
    contributor.
  - Compared to the last report, we have seen more pull request from 
    external contributors.
  - We received emails from some companies which are interested in the
    project and willing to make some contributions for the secure computing
    community.
  - Since we are mainly working on GitHub, with the help of the INFRA team,
    we can sync the notifications of GitHub with our mailing list.

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

  - Since last report, the whole project has been refactored to be more
    functional, as well as readable and approachable for new contributors.
  - We have rewrote the framework for implementing enclave services. Also, 
    we have redesigned current services into seven core services
    including access control, authentication, execution, frontend, 
management,
    scheduler, and storage service. Communication protocols between services
    are defined in protobuf.
  - RPC between services has been redesigned to supported TLS-based 
    attestation.
  - We have added DCAP attestation algorithm in the platform so that people 
    can deploy the system in environments without Intel's attestation service.
  - Communication between app and enclave has been also redesigned
    with better APIs.
  - All updates is currently in the `develop` branch. We plan to merge
    into `master` when main refactoring is done.

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

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

### Date of last release:

  N/A

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

  We haven't started new committers or PPMC members elections yet. 
  Currently, our
  work focus on improving the design and documents to make the project more
  approachable for newcomers.

### Have your mentors been helpful and responsive?

  Yes, our mentors help use to resolve the mailing list moderator 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:

  - [X] (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:

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

## Hudi

Hudi provides atomic upserts and incremental data streams on Big Data

Hudi has been incubating since 2019-01-17.

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

  1. Project is ready to graduate from incubator.
  2.
  3.

### 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. 683 conversations on dev ML across 130 topics [1]
  2. 75 participants during this period

### How has the project developed since the last report?
  1. ~180 Commits in gitbox [2]
  2. ~260 issues opened on Jira [3]. ~140 issues resolved in Jira [4]
  3. Hudi 0.5.1 released on Jan 31, 2020
  4. Hudi 0.5.2 released on March 26, 2020
  5. Work in progress for Hudi 0.6.0 planned for Apr 2020.
  6. 2 new committers - Sivabalan Narayanan, Lamber-ken
  7. 3 new PPMCs - Leesf, Vino Yang, Bhavani Sudha Saktheeswaran
  8. Completed the Apache Maturity Matrix for the project [5]
  9. Apache Hudi talk at Hadoop Summit Bangalore [6]
  10. Apache Hudi & Apache Kylin Online Meetup, China [7] [8] 
  11. Steve Blackmon was added as a mentor on April 3, 2020

  [1] https://lists.apache.org/trends.html?dev@hudi.apache.org:lte=3M  
  [2] git log  --since="2019-12-25" --no-merges | grep -e 'commit  
  [a-zA-Z0-9]*' | wc -l  
  [3] project = HUDI AND created >= 2019-12-25 AND created <=now()  
  [4] project = HUDI AND status = Closed AND status changed to Closed  
  DURING ("2019/12/25",now())  
  [5] https://cwiki.apache.org/confluence/display/HUDI/Apache+Hudi  
  +Maturity+Matrix  
  [6] https://www.slideshare.net/SyedKather/building-robust-cdc-  
  pipeline-with-apache-hudi-and-debezium  
  [7] https://drive.google.com/open?id=1dmH2kWJF69PNdifPp37QBgjivOHaSLDn  
  [8] https://drive.google.com/open?id=1Pk_WdFxfEZxMMfAOn0R8-m3ALkcN6G9e  

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

  1. The project now has a diverse developer and user community, and 
  excellent community traction.
  2. The project’s committers and PPMC members are drawn from diverse 
  places - Tencent, Uber, Confluent, Snowflake, Lyft, Shopify, Double Verify.
  3. Apache Hudi is being used across various industries for creating data 
  lakes and also for managing Machine Learning feature stores.
 	 - AWS, Alibaba, Uber, Tencent, Kyligence, EMIS Health, 
  Tathastu.ai, Logical Clocks  


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

### Date of last release:

  2020-03-26 Apache Hudi-incubating 0.5.2 Release
  2020-01-31 Apache Hudi-incubating 0.5.1 Release

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

  Sivabalan Narayanan was made committer on Feb 15, 2020
  Vino Yang and Leesf were added to PPMC on Feb 15, 2020
  Bhavani Sudha was added to PPMC on April 1, 2020
  Lamber-ken was made a committer on March 31, 2020

### Have your mentors been helpful and responsive?

  Yes, very helpful

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

### Signed-off-by:

  - [X] (hudi) Suneel Marthi
     Comments: The project is ready to graduate incubator. 
  - [X] (hudi) Thomas Weise
     Comments: Ready for graduation. 
  - [ ] (hudi) Luciano Resende
     Comments:  's brand / trademarks?

  Yes.

### Signed-off-by:

  - [ X] (hudi) Suneel KishoreMarthi Gopalakrishnan 
     Comments: The project 
is 

### IPMC/Shepherd notes:

[1] https://lists.apache.org/trends.html?dev@hudi.apache.org:lte=3M
[2] git log  --since="2019-12-25" --no-merges | grep -e 'commit [a-zA-Z0-9]*' | wc -l
[3] project = HUDI AND created >= 2019-12-25 AND created <=now()
[4] project = HUDI AND status = Closed AND status changed to Closed  DURING ("2019/12/25",now())
[5] https://cwiki.apache.org/confluence/display/HUDI/Apache+Hudi+Maturity+Matrix
[6]https://www.slideshare.net/SyedKather/building-robust-cdc-pipeline-with-apache-hudi-and-debezium
[7] https://drive.google.com/open?id=1dmH2kWJF69PNdifPp37QBgjivOHaSLDn
[8] https://drive.google.com/open?id=1Pk_WdFxfEZxMMfAOn0R8-m3ALkcN6G9e


ready to graduate incubator.  
  - [X] (hudi) Thomas Weise  
     Comments: Ready for graduation.  
  - [ ] (hudi) Luciano Resende  
     Comments:   
  - [ ] (hudi) Kishore Gopalakrishnan  
     Comments:  
  - [X] (hudi) Steve Blackmon  
     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. Launch the first Apache release.
  2. Grow community
  3. Make development document more easily to read

### 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 are applying TubeMQ to the actual environment, at this stage 
  we have discovered and fixed some bugs; at the same time, we are 
  learning and preparing for the first release. It is expected that 
  in the next stage we will release the first release

### How has the project developed since the last report?
  Near the first Apache release launch.

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

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

### Date of last release:
  None

### When were the last committers or PPMC members elected?
  Aloys Zhang was added as committer on 2020-02-20

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

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

### Signed-off-by:

  - [X] (tubemq) Junping Du  
     Comments:  Better to be more active for community activities.  
  - [ X] (tubemq) Justin Mclean  
     Comments: Looking froward to the first release. 
  - [ ] (tubemq) Sijie Guo  
     Comments:  
  - [ ] (tubemq) Zhijie Shen  
     Comments:  
  - [ ] (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
  2. Improve documentations

### 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 two 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 343.
  
  The community also actively worked on items under the guide of the Apache 
  maturity model
  
  https://docs.google.com/document/d/18nyAH-fcptVezAxPQe6H3FeTKPRkujOp1tc1YRSPLokfcptVezAxPQe6H3FeTKPRkujOp1tc1Y
  RSPLok/edit?usp=sharing

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

  A lot of improvements have been made. Including major improvements to 
  the unified IR and Pytorch support.

  See also our monthly reports for detailed improvements
  - Jan https://discuss.tvm.ai/t/tvm-monthly-january-2020/5589
  - Feb https://discuss.tvm.ai/t/tvm-monthly-february-2020/5935
  - Mar https://discuss.tvm.ai/t/tvm-monthly-march-2020/6199
  

### 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
  - [xX] Nearing graduation
  - [ ] Other:

### Date of last release:

  2019-12-1

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

  Feb 20 2020

### Have your mentors been helpful and responsive?

  Our mentors are super helpful.

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

   Yes, we have completed the name search.

### Signed-off-by:

  - [X] (tvm) Byung-Gon Chun  
     Comments:  
  - [ ] (tvm) Sebastian Schelter  
     Comments:  
  - [ X] (tvm) Henry Saputra  
     Comments:  
  - [ ] (tvm) Timothy Chen  
     Comments:  
  - [X] (tvm) Furkan Kamaci  
     Comments:  
  - [X] (tvm) Tianqi Chen  
     Comments:  
  - [X] (tvm) Markus Weimer  

### 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. [Branding issues]
  (https://cwiki.apache.org/confluence/display/WEEX/Branding+issues). 
  There are about 10 git repos violating the trademark of Apache Weex, 
  together with their NPM/Maven artifact.
  2. [Community diversity]
  (https://cwiki.apache.org/confluence/display/WEEX/Communtiy+diversity).
  Apache Weex needs more PPMCs and committers from community, no 
  employees from a single company shall have majority vote in PPMC and 
  committer.

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

### How has the project developed since the last report?
  * We have 14 incoming pull request, and 8 of them are merged.  
  * We have 5 threads in Weex mailing list .  
  * We have solved 21 Github issues.  

### How would you assess the podling's maturity?
Please feel free to add your own commentary.
  - [ ] Initial setup
  - [ ] Working towards first release
  - [ ] Community building
  - [X] Nearing graduation
  - [ ] Other:

### Date of last release:
  2019-10-23

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

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

### 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? 
No.
We are collecting a list of [branding issues],
  (https://cwiki.apache.org/confluence/display/WEEX/Branding+issues), 
  and we shall fix the problem one by one.

#### Has the VP, Brand approved the project name?
  No yet. We have not done Podling name search.

### Signed-off-by:
  - [ X] (weex) Willem Ning Jiang  
     * Comments:  
  - [ ] (weex) Myrle Krantz  
     * Comments:  
  - [ ] (weex) Jan Piotrowski  
     * Comments:  

### IPMC/Shepherd notes:

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

Apache YuniKorn (incubating) 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:

  - Gain more contributors and active committers.
  - Launch the first Apache release.
  - Improve documentation and provide a 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 held its first sync-up. English sync up scheduled
  bi-weekly, Mandarin sync up every 4 weeks from this time forward.
  - Added 3 new contributors to the project.

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

  - started working on the first release (version 0.8)
  - notification for JIRA and GitHub setup finished
  - website development has started (including build process)

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

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

### Date of last release:

  N.A.

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

  No new committers or PPMC members have been added since starting
  incubation.

### Have your mentors been helpful and responsive?

  Yes, gave guidance on email list usage and provided valuable
  input during the community sync up.

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

  No issues that we are aware of

### Signed-off-by:

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

  Comments:

### IPMC/Shepherd notes: