Page History

DRAFT DRAFT DRAFTFINAL FINAL FINAL
NOTE that the content for this month report is in markdown format- please do not remove any formatting characters when adding your reports.
...
Dave Fisher	Teaclave
Dave Fisher	Weex
Drew Farris	Liminal
Drew Farris	NuttX
Justin Mclean	Milagro
P. Taylor Goetz	Flagon
P. Taylor Goetz	Gobblin
P. Taylor Goetz	Pony Mail
Timothy Chen	DataLab
Timothy Chen	Pegasus
Timothy Chen	Toree
	Annotator
	BlueMarlin
	Hop
	Livy
	MXNet
	TubeMQ
	YuniKorn
Markdown

# Incubator PMC report for January 2021

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

## IP Clearance

## Legal / Trademarks

## Infrastructure

## Miscellaneous

## Credits

## Table of Contents  
[Annotator](#annotator)  
[BlueMarlin](#bluemarlin)  
[brpc](#brpc)  
[DataLab](#datalab)  
[Flagon](#flagon)  
[Gobblin](#gobblin)  
[Hop](#hop)  
[Liminal](#liminal)  
[Livy](#livy)  
[Milagro](#milagro)  
[MXNet](#mxnet)  
[NuttX](#nuttx)  
[Pegasus](#pegasus)  
[PonyMail](#ponymail)  
[Teaclave](#teaclave)  
[TubeMQ](#tubemq)  
[Wayang](#wayang)  
[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. Communicate clear roadmap
  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?

  None

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

  Community calls continue. A few new developers have reached out with
  interest in using and contributing to the project.

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

  Significant code reorganisation has been undertaken to generalise the
  selector algorithms such that they could be applied to other document
  types/representations than the DOM.

  A performance issue has been resolved after feedback from early
  adopters.

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

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

### Date of last release:

  2020-07-11

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

  2018-09-04

### Have your mentors been helpful and responsive?

  As for a while only one mentor was active and responsive,
  Benjamin Young has been added as mentor to facilitate processes.

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

  No issues at this time.

### Signed-off-by:

  - [X] (annotator) Nick Kew  
     Comments:  Apologies for recent reporting hiatus.
                The project feels like it could be picking up momentum,
                though that has yet to translate into community growth.
  - [ ] (annotator) Tommaso Teofili  
     Comments:  
  - [X] (annotator) Benjamin Young  
     Comments:  

### IPMC/Shepherd notes:

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

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

BlueMarlin has been incubating since 2020-06-09.

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

  - [ ] (bluemarlin) Craig Russell  
     Comments:  
  - [ ] (bluemarlin) Jean-Baptiste Onofré  
     Comments: We don't have lot of interaction with BlueMarlin team. I 
     will ping them a new time.
  - [ ] (bluemarlin) Von Gosling  
     Comments: I couldn't receive the team any feedback which was a little disappointing. I have ping team again and like to see does the team still needs help?
  - [ ] (bluemarlin) Junping Du  
     Comments:  are presently 40 podlings incubating. In December, podlings executed 
9 distinct releases. We added three new IPMC members, and none retired. 
There was one IP clearance in December. We have one new project Wayang. 
ECharts and DataSketches graduated last month, and Ratis and Flagon should 
graduate next month.

Annotator and Liminal, which failed to report last month, have reported 
this month. BRPC did not report again, and a role-call will be carried out 
to see if there is still an active PMC. This month we were missing reports 
from BRPC, Livy, PonyMail and Weex.

BlueMarlin still seems to be having some difficulty communicating on their 
mailing lists. They have submitted a report this month which is a good 
start.

Liminal has corrected the issue with its unapproved releases.

S2Graph will be retired shortly.

Weex, who was considering retirement, has managed to get the needed 3 +1 
PPMC votes for a release and their release is now up for IPMC vote.

SAMOA currently has no mentors but given there's little, or no activity on 
the mailing list and no commits for 9 months that's not a big issue. The 
project will be encouraged to retire.

Andrew Wetmore went though and simplified the language on many incubator 
site pages, including the policy page. There's a couple of missing links 
that still need to be corrected.

The major licensing issue with MXNet has been resolved with permission 
given to distribute it under the Apache 2.0 license. There are still 
several trademark and branding issues that need to be resolved. The project 
states it's nearing graduation, but IMO some work still needs to be done 
before that can happen. Their last release failed to get the required 
number of IPMC votes due to the difficultly in reviewing it. The previous 
releases containing Category X code still have not been removed (see 
INFRA-20442).

Most discussions on the mailing list were around releases and graduations. 
There were graduation discussions around ECharts, Flagon, Ratis and Goblin.

## Community

### New IPMC members:
  - Ming Wen
  - Maximilian Michels
  - Francois Papon

### People who left the IPMC:
  - None

## New Podlings
  - Wayang

## Podlings that failed to report, expected next month
  - BRPC
  - Livy
  - PonyMail
  - Weex

## Graduations
  - ECharts
  - DataSketches

  The board has motions for the following:

  - Gobblin

## Releases

  The following releases entered distribution during the month of
  December:
  - DolphinScheduler 1.3.4
  - ECharts 5.0.0
  - Gobblin 0.15.0
  - NLPcraft java-client 0.7.2
  - Nemo 0.3
  - NuttX 10.0.0
  - NuttX 10.0.1
  - NuttX 9.1.1
  - TubeMQ 0.7.0

## IP Clearance
  - OpenWhisk IDE plugins

## Legal / Trademarks
  - MXNet license issue resolved
  - Trademark issues seem to be coming a more common issue with graduating 
projects

## Infrastructure
  - ASF's GitHub actions limits are causing some projects issues but this 
is being looked into by Infra.

## Miscellaneous
  - N/A

## Table of Contents  
[Annotator](#annotator)  
[BlueMarlin](#bluemarlin)   
[DataLab](#datalab)  
[Flagon](#flagon)  
[Gobblin](#gobblin)  
[Hop](#hop)  
[Liminal](#liminal)  
[Milagro](#milagro)  
[MXNet](#mxnet)  
[NuttX](#nuttx)  
[Pegasus](#pegasus)  
[Teaclave](#teaclave)  
[TubeMQ](#tubemq)  
[Wayang](#wayang)  
[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. Communicate clear roadmap
  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?

  None

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

  Community calls continue. A few new developers have reached out with
  interest in using and contributing to the project.

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

  Significant code reorganisation has been undertaken to generalise the
  selector algorithms such that they could be applied to other document
  types/representations than the DOM.

  A performance issue has been resolved after feedback from early
  adopters.

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

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

### Date of last release:

  2020-07-11

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

  2018-09-04

### Have your mentors been helpful and responsive?

  As for a while only one mentor was active and responsive,
  Benjamin Young has been added as mentor to facilitate processes.

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

  No issues at this time.

### Signed-off-by:

  - [X] (annotator) Nick Kew  
     Comments:  Apologies for recent reporting hiatus.
                The project feels like it could be picking up momentum,
                though that has yet to translate into community growth.
  - [ ] (bluemarlinannotator) Uma Maheswara Rao G Tommaso Teofili  
     Comments:  
  - [X] (annotator) Benjamin Young  
     Comments:  

### IPMC/Shepherd notes:

--------------------
## brpcBlueMarlin

brpcBlueMarlin will isdevelop ana industrial-gradeweb RPCservice frameworkto foradd buildingintelligence reliablefunctionality andto high-
performance servicesa
plain ad system.

brpcBlueMarlin has been incubating since 20182020-1106-1309.

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

  1. Bootstrap the project (code donation, legal files)
  2. Cut the first incubating release
  3. Grow up community

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

No issue

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

We are in the bootstrapping phase (take longer than expected)

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

This is the first report, bootstrapping in progress

### 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-XXNo release for now

### When were the last committers or PPMC members elected?
  N/A

### Have your mentors been helpful and responsive?
  AreJB thingsproposed falling through the cracks? If so, please list any
  open issues that need to be addressedto help.

### Is the PPMC managing the podling's brand / trademarks?
  AreYes, 3rdwe partiesare respecting and correctly using in the podlings
  name and brand? If not what actions has the PPMC taken to
  correct this? Has the VP, Brand approved the project name?
check phase.

### Signed-off-by:

  - [ ] (brpcbluemarlin) Kevin A. McGrailCraig Russell  
     Comments:  
  - [ X] (brpcbluemarlin) Jean-Baptiste Onofré  
     Comments: We 
don't have -lot [of ]interaction (brpc)with VonBlueMarlin Goslingteam. I 
     will Comments:ping them 

### IPMC/Shepherd notes:

--------------------
## DataLab

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

  DataLab has been incubating since 2018-08-20.

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

  Finish preparing all artifacts necessary for graduation

### 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 committer (java-developer) - Yurii Kinash.

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

  -  We are working towards the release 2.5.0
  -  Migration to Py3 (in progress)
  -  Edge node recreation capability (in progress)
  -  Support of Spark v.3.x.x (open)
  -  Localization (done)
  -  Switch to modular architecture (in progress)
  -  Augment an administrative page (in progress)
  -  Bug fixing

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

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

  The last committer was elected on December 10, 2020.

### Have your mentors been helpful and responsive?

  Yes, our mentors are very helpful and responsive.

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

  There are no known brand and naming issues. New name was approved and our 
  team changed all references to DLab that are publicly accessible to 
  DataLab, including code base, presentations, documentation, etc.

### Signed-off-by:

  - [ ] (datalab) P. Taylor Goetz  
     Comments:  
  - [ ] (datalab) Henry Saputra  
     Comments:  
  - [ ] (datalab) Konstantin I Boudnik  
     Comments:  
  - [a new time. Update: I have been pinged by BlueMarling 
guys, I will move forward with them.
  - [ ] (bluemarlin) Von Gosling  
     Comments: I couldn't receive the team any feedback which was a little 
disappointing. I have ping team again and like to see does the team still 
needs help?
  - [ ] (bluemarlin) Junping Du  
     Comments:  
  - [ ] (bluemarlin) Uma Maheswara Rao G  
     Comments:  

### IPMC/Shepherd notes:

--------------------
## DataLab

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

  DataLab has been incubating since 2018-08-20.

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

  Finish preparing all artifacts necessary for graduation

### 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 committer (java-developer) - Yurii Kinash.

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

  -  We are working towards the release 2.5.0
  -  Migration to Py3 (in progress)
  -  Edge node recreation capability (in progress)
  -  Support of Spark v.3.x.x (open)
  -  Localization (done)
  -  Switch to modular architecture (in progress)
  -  Augment an administrative page (in progress)
  -  Bug fixing

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

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

  The last committer was elected on December 10, 2020.

### Have your mentors been helpful and responsive?

  Yes, our mentors are very helpful and responsive.

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

  There are no known brand and naming issues. New name was approved and our 
  team changed all references to DLab that are publicly accessible to 
  DataLab, including code base, presentations, documentation, etc.

### Signed-off-by:

  - [ ] (datalab) P. Taylor Goetz  
     Comments:  
  - [ ] (datalab) Henry Saputra  
     Comments:  
  - [ ] (datalab) Konstantin I Boudnik  
     Comments:  
  - [X] (datalab) Furkan Kamaci  
     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. Work with IPMC to approve draft graduation resolution
  2. Add DISCLAIMER and make read-only subprojects to be retired (TAP, 
  STOUT, etc.)
  3. Add logo to appropriate Apache outlet (logos.apache.org)

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

  No issues at this time.

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

  Not significantly.

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

  -  We are working towards UserALE release 2.1.1
  -  We have been actively engaged with an expanding user base
  -  Core product source code is well maintained
  -  Preparing to complete outstanding graduation actions

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

### 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
  -  Our mentors have urged us to create a Graduation resolution

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

  - [X] (flagon) Lewis John McGibbney  
     Comments: Flagon was to do degree blokced from graduating within the 
     last ~3 months. I personally felt that the IMPC review of the DRAFT
     graduation resolution could have been better handled by the IPMC. There
     were a number of non-blocking items which were raised and which 
eventually
     impacted the motivation to graduate. It would be nice if Flagon could
     graduate as ther podling has shown excellent underatanding of the 
Apache
     Way and it's patience to mature as a podling. I will work with the 
Flagon
     PPMC on the next steps as highlightes in the above report.
  - [ ] (flagon) David Meikle  
     Comments:  
  - [ ] (flagon) Tim Allison  
     Comments:  
  - [X] (flagon) Furkan Kamaci  
     Comments:  

### IPMC/Shepherd notes:
  Justin Mclean: Looking at the email discussion I can't see how it was 
blocked,
  a few minor things were raised that were easily fixed. All of the proposed
  PMC members have still not signed up the the private list.

--------------------
## 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. Discuss and Vote in progress in general@incubator mailing list for 
  graduation to TLP.

### 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 : 505 
  (Oct), 324 (Nov), 313 (Dec)
  - There have been 63 Commits since last report: git log --format='%ci' | 
  grep -cE '((2020-1(0|1|2)))'
  - 29 ie. 46% of those commits were by non-committers: git log 
  --format='%ae %ci' | grep -E '(2020-1(0|1|2))' | cut -d ' ' -f 1 | sort |
  uniq -c | sort -n

### How has the project developed since the last report?
  1. Vote within community for graduation to TLP was passed after a 
  discussion. Discuss and vote was started in general@incubator.
  2. Roster, project page, documentation, website, and wiki were reviewed 
  and updated.
  3. Evaluation under Apache maturity model for graduation was done.
  4. Podling name search was done.
  5. New version (0.15.0) was approved and released.

  On technical side, the following was added:
  1. Support for Kafka 1.1.
  2. Decimal type support in GobblinORCWriter.
  4. LDAP based group ownership support.
  5. New Groups ownership service.
  6. Azkaban OAuth token support.
  7. Gradle version was upgraded.
  8. Auto-tune of ORC writer params.
  9. Support for multiple DFS tokens fetch for HDFS federation.

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

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

### Signed-off-by:

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

### IPMC/Shepherd notes:

--------------------
## Hop

Hop is short for the Hop Orchestration Platform. Written completely in Java
it aims to provide a wide range of data orchestration tools, including a
visual development environment, servers, metadata analysis, auditing
services and so on. As a platform, Hop also wants to be a reusable library
so that it can be easily reused by other software.

Hop has been incubating since 2020-09-24.

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

  1. identify and resolve the last remaining incompatibly licensed 
  dependencies (if any)
  2. create a first release
  3. grow the community

### Are there any issues that the IPMC or ASF Board need to be aware of?
  No known significant issues at this moment

### How has the community developed since the last report?
  - 3 additional committers, lots of committer and community activity in 
  the last month
  - 14 new registered chat members (108->122)
  - 1 new subscriber to dev (21->22), 0 to users mailing lists (11)
  - significant follower growth on LinkedIn (309->321), Twitter (233->253) 
  and YouTube (40->50)

### How has the project developed since the last report?
  Two releases candidates (0.50-rc1, 0.50-rc2) were created but failed to 
  get enough positive votes.
  Hop will take the feedback and lessons learned from 0.50-rc1 and 0.50-rc2 
  to build a new 0.60-rc1.
  Summary of the 2 RCs: https://s.apache.org/06hws

  December was a very active month, with continued activity over the 
  holiday period:
  - metadata perspective
  - look and feel updates
  - new transform plugins (UDJC, Token Replacement)
  - partitioned stream lookup
  - docker included, community activity on kubernetes
  - jandex-based plugins
  - integration testing
  - community activity on Hop Web
  - documentation updates

  Full details are available in the December monthly roundup: 
  https://hop.apache.org/blog/2021/01/roundup-2021-01/

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

  XXXX-XX-XX

### When were the last committers or PPMC members elected?
  2020-12-2

### Have your mentors been helpful and responsive?
  Julian Hyde and François Papon regularly check in and provide valuable 
  input. We're sure our other mentors will step in for RCs after the holiday
  period.

### Is the PPMC managing the podling's brand / trademarks?
  There are no known brand and naming issues. The PPMC only uses "Apache 
  Hop (Incubating)" as the official project name and has explicitly called
  "Project Hop" deprecated as of the moment of acceptance in the Incubator.

### Signed-off-by:

  - [X] (hop) Tom Barber  
     Comments:  I agree with Julian. The community is great, obviously a 
     lot 
     came from knowledge of the previous life and interest in seeing it 
     progress which is good. The chat vs mailing list stuff is true, I 
     don't 
     follow the chat too much, just lurk but there is a lot going on there, 
     not necessarily decision making but communication that could be missed 
     for 
     those who choose not to use it. Conversely I would say that a lot of 
     the 
     folk on the chat room are users as opposed to developers, and as such 
     don't 
     have to be treated in the same manner. Might be worth checking 
     committers vs 
     chat vs dev list? I suspect its probably pretty much up to date. Great 
     progress on the software front, good to see it coming together.
  - [X] (hop) Julian Hyde  
     Comments: Good report! I'd say you are through 'initial setup' and can 
     uncheck that box next time. The community is going great, and I'm sure 
     that
     the first release will happen very soon. One concern: the difference 
     in the
     number of people on chat vs the dev list (122 vs 22). The traffic on 
     chat
     is benign (e.g. no major decisions being made) but I am concerned that 
     with
     so few of the regulars on the dev list, chat will become the de facto 
     place
     to make decisions. Also I couldn't find a public archive of chat. I'll
     raise this issue on the dev list.
  - [X] (hop) Maximilian Michels  
     Comments: I'm continuing to be amazed by the progress of the Hop 
     project. There is a constant flow of incoming pull requests and the 
     first
     release is nearing completion. It might not be clear to all community
     members but I've tried to only step in when necessary, e.g. give 
     feedback
     to unblock the release process.
  - [X] (hop) Francois Papon  
     Comments: The community is still very active and starting to learn the 
     release process. For now, the only issue in the release is the license 
     part
     and the team is focused on it to prepare a new vote.
  - [X] (hop) Kevin Ratnasekera  
     Comments:  

### IPMC/Shepherd notes:

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

Apache Liminal is an end-to-end platform for data engineers and scientists,
allowing them to build, train and deploy machine learning models in a robust
and agile way.

Liminal has been incubating since 2020-05-23.

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

  1. First release (due next week)
  2. Build a community
  3. Define 2021 roadmap

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

### How has the community developed since the last report?
  We had a successful meetup and a presentation on Data & AI summit Europe.
  Discussing with few companies to join the effort.

### How has the project developed since the last report?
  The first release candidate is ready and verified, planning to have a 
  formal release next week.

### 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:
  The first release candidate is ready and verified, planning to have a 
  formal release next week.

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

### Have your mentors been helpful and responsive?
  JB & Davor have been helpful.

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

### Signed-off-by:

  - [X] (liminal) Jean-Baptiste Onofre  
     Comments:  First release has been done.
  - [ ] (liminal) Henry Saputra  
     Comments:  
  - [ ] (liminal) Uma Maheswara Rao G  
     Comments:  
  - [X] (liminal) Davor Bonaci  
     Comments: Looking forward to the community review of the first release!
  - [ ] (liminal) Liang Chen  
     Comments:  

### IPMC/Shepherd notes:
  Justin Mclean: Individuals contribute to ASF projects not companies. I'm 
  sure you know that, you just might want to be more careful with your
  language in future reports.

--------------------
## LivyMilagro

LivyMilagro is webcore servicesecurity thatinfrastructure exposesand acrypto RESTlibraries interfacefor
decentralized fornetworks managingand longdistributed runningsystems.

ApacheMilagro Sparkhas contextsbeen inincubating 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:

  1since 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 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:  
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 some administrative tasks around the
  project are still outstanding but are being addressed.  In particular,
  a PPMC meeting has been proposed for 3rd February to discuss
  outstanding issue with a follow on meeting for the entire Milagro
  community to discuss the project's roadmap.

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

  No change.

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

  Work continues on the C and Rust versions of the core cryptographic 
  library
  and on preparing the Multi Party Computation library for its first 
  official
  Apache release.

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

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

### IPMC/Shepherd notes Date of last release:

  2020--------------------
## 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 some administrative tasks around the
  project are still outstanding but are being addressed.  In particular,
  a PPMC meeting has been proposed for 3rd February to discuss
  outstanding issue with a follow on meeting for the entire Milagro
  community to discuss the project's roadmap.

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

  No change.

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

  Work continues on the C and Rust versions of the core cryptographic 
  library
  and on preparing the Multi Party Computation library 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-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:  
  - [ ] (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. Close to completion. See update in the next section.
  2. Address release issues, improve automation for license checks, and
  make it easier for auditing. Successfully and smoothly make releases
  without WIP disclaimer.
     - ONGOING.
  3. Improve brand management.
     - ONGOING.

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

  1. The community is fixing the remaining releases that have license
  issues. See summary below.
  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
  3. The community is including brand usage reviews as part of the
  quarterly report process to proactively manage our brand going forward.

#### Status on license and branding issues

  Most of the issues from last update hinged on the resolution of LEGAL-516.
  We are very glad that LEGAL-516 concluded that ASF projects compiled using
  NVIDIA’s CUDA compiler may be distributed under the Apache License 2.0,
  which unblocks many of the distribution practices that are essential to
  the
  wide adoption of software that utilizes GPU. We would like to thank for
  the
  help, the patience, and the leniency and flexibility that the incubator
  and
  legal granted us, and the numerous helps we received along the way from
  the
  ASF members and our community members from NVIDIA. Especially, I would
  like
  to thank Michael O’Conner and Triston Cao from NVIDIA for pushing this
  through within their organization.

  Based on the conclusion of LEGAL-516, binary distribution of CUDA-compiled
  Apache projects can be properly licensed as ALv2. In addition, the
  branding
  issues from distribution pages from Amazon, NVIDIA, and Intel have all
  been
  acted on. As a result, among the 9 pending issues from last update, 5 can
  be resolved. We are following up on the remaining items to resolve all
  issues in INCUBATOR-253.

  As part of our improvement in brand management, we are including
  third-party brand usage review in our quarterly reports and we will keep
  it
  as part of our regular practice beyond graduation.

  Status on open issues since last update:
  1. Source and convenance binary releases containing Category X licensed
  code. (pending item 5) * Source code releases by the PPMC do not contain
  Category X code.  Takedown and backfill of compliant binary releases by 
  the
  PPMC on repository.apache.org is in progress, see item 5.  PyPI releases
  are
  made by third-party. See item 8.

  5. Maven releases containing Category X licensed code. (pending) *
  Takedown
  of binary releases on repository.apache.org initiated (i.e. INFRA-20442).
  Based on the resolution of LEGAL-516, the takedown (and backfill) includes
  those that include GPL licensed components. We are working on this in the
  infra issue.

  6. PyPI releases containing Category X licensed code. (Resolved) * The
  third-party releases are compliant with branding guidelines since the
  releases are from official source code releases and are properly licensed
  with ALv2.

  7. Docker releases containing Category X licensed code. (Resolved) * The
  third-party releases are compliant with branding guidelines since the
  releases are from official source code releases and are properly licensed
  with ALv2.

  9. Trademark and branding issues with PyPI and Docker releases. (Resolved)
  * These release are compliant with trademark and branding requirements
  since they don’t contain Category X licensed code and are licensed with
  ALv2
  based on item 6 and 7.

  10. Trademark and brand issues with naming of releases. (Resolved) * There
  are no binary releases by the PPMC besides the repository.apache.org
  releases in item 5.

  14, 22, 23. Branding and release of 3rd parties containing unreleased
  code.
  Known pages with issues: *


  +https://docs.nvidia.com/deeplearning/frameworks/mxnet-release-notes/rel_20-
  03.html+ (item 14, Resolved)  NVIDIA switched to "NVIDIA Optimized Deep
  Learning Framework, powered by Apache MXNet” for naming.


  +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 administrative tasks are still outstanding?

--------------------
## 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. Close to completion. See update in the next section.
  2. Address release issues, improve automation for license checks, and
  make it easier for auditing. Successfully and smoothly make releases
  without WIP disclaimer.
     - ONGOING.
  3. Improve brand management.
     - ONGOING.

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

  1. The community is fixing the remaining releases that have license
  issues. See summary below.
  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
  3. The community is including brand usage reviews as part of the
  quarterly report process to proactively manage our brand going forward.

#### Status on license and branding issues

  Most of the issues from last update hinged on the resolution of LEGAL-516.
  We are very glad that LEGAL-516 concluded that ASF projects compiled using
  NVIDIA’s CUDA compiler may be distributed under the Apache License 2.0,
  which unblocks many of the distribution practices that are essential to
  the
  wide adoption of software that utilizes GPU. We would like to thank for
  the
  help, the patience, and the leniency and flexibility that the incubator
  and
  legal granted us, and the numerous helps we received along the way from
  the
  ASF members and our community members from NVIDIA. Especially, I would
  like
  to thank Michael O’Conner and Triston Cao from NVIDIA for pushing this
  through within their organization.

  Based on the conclusion of LEGAL-516, binary distribution of CUDA-compiled
  Apache projects can be properly licensed as ALv2. In addition, the
  branding
  issues from distribution pages from Amazon, NVIDIA, and Intel have all
  been
  acted on. As a result, among the 9 pending issues from last update, 5 can
  be resolved. We are following up on the remaining items to resolve all
  issues in INCUBATOR-253.

  As part of our improvement in brand management, we are including
  third-party brand usage review in our quarterly reports and we will keep
  it
  as part of our regular practice beyond graduation.

  Status on open issues since last update:
  1. Source and convenance binary releases containing Category X licensed
  code. (pending item 5) * Source code releases by the PPMC do not contain
  Category X code.  Takedown and backfill of compliant binary releases by 
  the
  PPMC on repository.apache.org is in progress, see item 5.  PyPI releases
  are
  made by third-party. See item 8.

  5. Maven releases containing Category X licensed code. (pending) *
  Takedown
  of binary releases on repository.apache.org initiated (i.e. INFRA-20442).
  Based on the resolution of LEGAL-516, the takedown (and backfill) includes
  those that include GPL licensed components. We are working on this in the
  infra issue.

  6. PyPI releases containing Category X licensed code. (Resolved) * The
  third-party releases are compliant with branding guidelines since the
  releases are from official source code releases and are properly licensed
  with ALv2.

  7. Docker releases containing Category X licensed code. (Resolved) * The
  third-party releases are compliant with branding guidelines since the
  releases are from official source code releases and are properly licensed
  with ALv2.

  9. Trademark and branding issues with PyPI and Docker releases. (Resolved)
  * These release are compliant with trademark and branding requirements
  since they don’t contain Category X licensed code and are licensed with
  ALv2
  based on item 6 and 7.

  10. Trademark and brand issues with naming of releases. (Resolved) * There
  are no binary releases by the PPMC besides the repository.apache.org
  releases in item 5.

  14, 22, 23. Branding and release of 3rd parties containing unreleased
  code.
  Known pages with issues: *

  
+https://docs.nvidia.com/deeplearning/frameworks/mxnet-release-notes/rel_20-
  03.html+ (item 14, Resolved)  NVIDIA switched to "NVIDIA Optimized Deep
  Learning Framework, powered by Apache MXNet” for naming.

  
+https://aws.amazon.com/marketplace/pp/B07YW8HVLD?qid=1595741035764&sr=0-4&r
  ef_=srh_res_product_title+ (item 22, pending) PPMC reached out to Bitnami
  directly regarding this listing [1]. Bitnami responded but the page still
  needs update. We followed up again with Bitnami this week.

  
+https://aws.amazon.com/marketplace/search/results?x=0&y=0&searchTerms=%22MX
  Net+ (item 23, pending) PPMC reached out to AWS through internal channel
  to
  fix branding issue. Amazon intends to use AWS MX powered by Apache MXNet
  naming convention [2]. The naming change is in progress.
  After last update, for item 15, SourceForge further added a disclaimer
  that
  the page is an automatic mirror of MXNet’s GitHub tags:
  +https://sourceforge.net/projects/apache-mxnet.mirror/+.
  In addition, MXNet PPMC identified several more listings that require
  correction according to the branding guideline on AWS marketplace that are
  related to AWS Deep Learning Container/DLAMI [3], and they have all been
  resolved.

  From recent brand usage review for MXNet third-party distributions,
  we found several listings on AWS marketplace that need update. The PPMC
  is reaching out to the publishers of these listings for correction.

  
https://aws.amazon.com/marketplace/pp/B079225XXC?qid=1609989161134&sr=0-14&r
  ef_=srh_res_product_title

  
https://aws.amazon.com/marketplace/pp/B07MP6Y8XT?qid=1609989161134&sr=0-17&r
  ef_=srh_res_product_title

  
https://aws.amazon.com/marketplace/pp/B073SHB43M?qid=1609989286506&sr=0-21&r
  ef_=srh_res_product_title

  
https://aws.amazon.com/marketplace/pp/B07YW8HVLDB01JJ31R8C?qid=15957410357641609989286506&sr=0-422&r
  ef_=srh_res_product_title+ (item 22, pending) PPMC reached out to Bitnami
  directly regarding this listing [1]. Bitnami responded but the page still
  needs update. We followed up again with Bitnami this week.


  +https://aws.amazon.com/marketplace/searchpp/resultsB07F3YBMT9?xqid=01609989286506&ysr=0-23&searchTerms=%22MXr
  Net+ (item 23, pending) PPMC reached out to AWS through internal channel
  to
  fix branding issue. Amazon intends to use AWS MX powered by Apache MXNet
  naming convention [2]. The naming change is in progress.
  After last update, for item 15, SourceForge further added a disclaimer
  that
  the page is an automatic mirror of MXNet’s GitHub tags:
  +https://sourceforge.net/projects/apache-mxnet.mirror/+.
  In addition, MXNet PPMC identified several more listings that require
  correction according to the branding guideline on AWS marketplace that are
  related to AWS Deep Learning Container/DLAMI [3], and they have all been
  resolved.

  From recent brand usage review for MXNet third-party distributions,
  we found several listings on AWS marketplace that need update. The PPMC
  is reaching out to the publishers of these listings for correction.


  https://aws.amazon.com/marketplace/pp/B079225XXC?qid=1609989161134&sr=0-14&r
  ef_=srh_res_product_title


  https://aws.amazon.com/marketplace/pp/B07MP6Y8XT?qid=1609989161134&sr=0-17&r
  ef_=srh_res_product_title


  https://aws.amazon.com/marketplace/pp/B073SHB43M?qid=1609989286506&sr=0-21&r
  ef_=srh_res_product_title


  https://aws.amazon.com/marketplace/pp/B01JJ31R8C?qid=1609989286506&sr=0-22&r
  ef_=srh_res_product_title


  https://aws.amazon.com/marketplace/pp/B07F3YBMT9?qid=1609989286506&sr=0-23&r
  ef_=srh_res_product_title


  https://aws.amazon.com/marketplace/pp/B084FXK9XH?qid=1609989286506&sr=0-24&r
  ef_=srh_res_product_title


  https://aws.amazon.com/marketplace/pp/B08L8H9NWD?qid=1609989286506&sr=0-28&r
  ef_=srh_res_product_title


  https://aws.amazon.com/marketplace/pp/B08G8VXC1Q?qid=1609989286506&sr=0-29&r
  ef_=srh_res_product_title


  https://aws.amazon.com/marketplace/pp/B07C49CVC1?qid=1609989286506&sr=0-30&r
  ef_=srh_res_product_title

  Reference links
  [1]:
  https://lists.apache.org/thread.html/r1fabd3c081286b06b6e9c9283cb5986450f07d
  52309db3b74bfe3a24%40%3Cprivate.mxnet.apache.org%3E

  [2] 
  https://lists.apache.org/thread.html/rad72c3b39170da16e34e77536c0e3134f93
  ed429b07ddd643a6fa5ba%40%3Cprivate.mxnet.apache.org%3E

  [3] 
  https://lists.apache.org/thread.html/r3f95f5766e8f1ee8fbd8183720804afdc16
  78f0149f56144da45f619%40%3Cprivate.mxnet.apache.org%3E

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

  * The number of GitHub contributors increased to currently 948
  (2019-10-08; +13% since last report)
  * Active blogs and social media presence
    * Medium (https://medium.com/apache-mxnet) w/ 2k followers (+3%)

  * Active video channels
    * YouTube channel  (https://www.youtube.com/apachemxnet) w/ 1.33k
    subscriber (+4.7% since last report)
    * Chinese YouTube channel
    (https://www.youtube.com/channel/UCjeLwTKPMlDt2segkZzw2ZQ) w/ 6.43k
     subscribers (+2.3%)
    * (in China) bilibili space (https://space.bilibili.com/209599371) w/
    26k subscriber (+4% since last report)

  * Highlights in MXNet ecosystem
    * Dive into Deep Learning has 50K 28-day active users, and has
  attracted 28.0K stars & 333 contributors on GitHub. It has been adopted as
  a textbook or reference book by 170+ universities from 40 countries, such
  as Stanford, MIT, UC Berkeley, CMU, UCambridge.
    * GluonCV v0.9.0 release
      (https://github.com/dmlc/gluon-cv/releases/tag/v0.9.0)
    * GluonNLP MX2 NumPy version
      (https://github.com/dmlc/gluon-nlp/tree/master)
    * GluonTS v0.6.4 release
      (https://github.com/awslabs/gluon-ts/releases/tag/v0.6.4)
    * DeepInsight (https://github.com/deepinsight/insightface)
    * Sockeye 2.3.2 release (https://github.com/awslabs/sockeye)

  * MXNet community held the "Apache MXNet Day" community meet-up on 12/14
    with NVIDIA and AWS as sponsors and Apache as community sponsor. At the
    meet-up, community members shared the latest progress in MXNet, and
    discussed topics such as array API standardization across frameworks,
    and the history and future of MXNet.

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

  1) 1.8.0 release is in progress:
  https://github.com/apache/incubator-mxnet/releases/tag/1.8.0.rc2
  with 100+ patches of new features, improvements, and fixes.
  2) 2.0 alpha release:
  https://github.com/apache/incubator-mxnet/projects/18
  3) Github statistics of last month:
     * Dec 5, 2020 – Jan 5, 2021: Excluding merges, 28 authors have pushed
  31 commits to master and 60 commits to all branches. On master, 175 files
  have changed and there have been 7,192 additions and 1,628 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-08-24

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

  2020-11-30

### Have your mentors been helpful and responsive?

  Yes. Michael stepped down as a mentor and we are grateful for his helps
  for our project.
  Markus also expressed desire to step down as a mentor if we find more
  mentors. Because of the large scope of the project and the several issues
  we faced so far, we definitely wish to have more mentors to help.

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

  Yes. The PPMC conducted more extensive branding and trademarks review,
  identified some violations and acted on resolving them with offenders, as
  described in "Status on license and branding issues" section. In addition,
  The community is including brand usage reviews as part of the quarterly
  report process to proactively manage our brand going forward.

### Signed-off-by:

  - [ ] (mxnet) Markus Weimer  
     Comments:
  - [ ] (mxnet) Bob Paulin  
     Comments:
  - [ ] (mxnet) Jason Dai  
     Comments:
  - [X] (mxnet) Furkan Kamaci  
     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 210 subscribers, an increase of 6% 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.  
  * One new committer has been added since the last report.  ef_=srh_res_product_title

  
https://aws.amazon.com/marketplace/pp/B084FXK9XH?qid=1609989286506&sr=0-24&r
  ef_=srh_res_product_title

  
https://aws.amazon.com/marketplace/pp/B08L8H9NWD?qid=1609989286506&sr=0-28&r
  ef_=srh_res_product_title

  
https://aws.amazon.com/marketplace/pp/B08G8VXC1Q?qid=1609989286506&sr=0-29&r
  ef_=srh_res_product_title

  
https://aws.amazon.com/marketplace/pp/B07C49CVC1?qid=1609989286506&sr=0-30&r
  ef_=srh_res_product_title

  Reference links
  [1]:
  
https://lists.apache.org/thread.html/r1fabd3c081286b06b6e9c9283cb5986450f07d
  52309db3b74bfe3a24%40%3Cprivate.mxnet.apache.org%3E

  [2] 
  https://lists.apache.org/thread.html/rad72c3b39170da16e34e77536c0e3134f93
  ed429b07ddd643a6fa5ba%40%3Cprivate.mxnet.apache.org%3E

  [3] 
  https://lists.apache.org/thread.html/r3f95f5766e8f1ee8fbd8183720804afdc16
  78f0149f56144da45f619%40%3Cprivate.mxnet.apache.org%3E

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

  * The number of GitHub contributors increased to currently 948
  (2019-10-08; +13% since last report)
  * Active blogs and social media presence
    * Medium (https://medium.com/apache-mxnet) w/ 2k followers (+3%)

  * Active video channels
    * YouTube channel  (https://www.youtube.com/apachemxnet) w/ 1.33k
    subscriber (+4.7% since last report)
    * Chinese YouTube channel
    (https://www.youtube.com/channel/UCjeLwTKPMlDt2segkZzw2ZQ) w/ 6.43k
     subscribers (+2.3%)
    * (in China) bilibili space (https://space.bilibili.com/209599371) w/
    26k subscriber (+4% since last report)

  * Highlights in MXNet ecosystem
    * Dive into Deep Learning has 50K 28-day active users, and has
  attracted 28.0K stars & 333 contributors on GitHub. It has been adopted as
  a textbook or reference book by 170+ universities from 40 countries, such
  as Stanford, MIT, UC Berkeley, CMU, UCambridge.
    * GluonCV v0.9.0 release
      (https://github.com/dmlc/gluon-cv/releases/tag/v0.9.0)
    * GluonNLP MX2 NumPy version
      (https://github.com/dmlc/gluon-nlp/tree/master)
    * GluonTS v0.6.4 release
      (https://github.com/awslabs/gluon-ts/releases/tag/v0.6.4)
    * DeepInsight (https://github.com/deepinsight/insightface)
    * Sockeye 2.3.2 release (https://github.com/awslabs/sockeye)

  * MXNet community held the "Apache MXNet Day" community meet-up on 12/14
    with NVIDIA and AWS as sponsors and Apache as community sponsor. At the
    meet-up, community members shared the latest progress in MXNet, and
    discussed topics such as array API standardization across frameworks,
    and the history and future of MXNet.

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

  * We have made significant steps toward license clearing, needed for  
    graduation: In this quarter, we have secured 34 ICLAs and 7 SGAs,  
    the most of any quarter so far, from past and present contributors.  
  * We have successfully made our third, fourth, and fifth releases  
    under the ASF umbrella: NuttX-10.0 followed by security fix releases  
    NuttX-9.1.1 and NuttX-10.0.1.  
  * Contributions are flowing regularly as PRs in GitHub with occasional  
    patches in the dev list.  
  * Many technical improvements, bug fixes, and new architectures have  
    been collaborated and work continues with an average of 6 and  
    sometimes as many as a dozen pull requests merged per day.  
  * We have listened to the valuable feedback received during our  
    previous releases and continue to improve our documentation. This can  
    be found at https://nuttx.apache.org/docs/latest/.  
  * We've implemented additional automatic checks on PRs.  This has  
    helped us to improve our review 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:

  NuttX-10.0.1 and NuttX-9.1.1 were released on 2020-12-08.

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

  Last elected PPMC: 2020-01-10

  Last committer added: 2020-12-30

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

  - [X] (nuttx) Duo Zhang  
     Comments: Glad to see that we have made good progress on license 
     clearing.
  - [ ] (nuttx) Junping Du  
     Comments:  
  - [X] (nuttx) Justin Mclean  
     Comments:  
  - [ ] (nuttx) Mohammad Asif Siddiqui  
     Comments:  
  - [ ] (nuttx) Flavio Paiva Junqueira  
     Comments:  

### IPMC/Shepherd notes:

--------------------
## Pegasus

Pegasus is a distributed key-value storage system which is designed to be
simple, horizontally scalable, strongly consistent and high-performance.

Pegasus has been incubating since 2020-06-28.

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

  1. Attract more contributors and committers.
  2. Make more releases in ASF policy regularly.
  3. Resolve the license problems.

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

  N/A1) 1.8.0 release is in progress:
  https://github.com/apache/incubator-mxnet/releases/tag/1.8.0.rc2
  with 100+ patches of new features, improvements, and fixes.
  2) 2.0 alpha release:
  https://github.com/apache/incubator-mxnet/projects/18
  3) Github statistics of last month:
     * Dec 5, 2020 – Jan 5, 2021: Excluding merges, 28 authors have pushed
  31 commits to master and 60 commits to all branches. On master, 175 files
  have changed and there have been 7,192 additions and 1,628 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-08-24

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

  2020-11-30

### Have your mentors been helpful and responsive?

  Yes. Michael stepped down as a mentor and we are grateful for his helps
  for our project.
  Markus also expressed desire to step down as a mentor if we find more
  mentors. Because of the large scope of the project and the several issues
  we faced so far, we definitely wish to have more mentors to help.

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

  Yes. The PPMC conducted more extensive branding and trademarks review,
  identified some violations and acted on resolving them with offenders, as
  described in "Status on license and branding issues" section. In addition,
  The community is including brand usage reviews as part of the quarterly
  report process to proactively manage our brand going forward.

### Signed-off-by:

  - [ ] (mxnet) Markus Weimer  
     Comments:
  - [ ] (mxnet) Bob Paulin  
     Comments:
  - [ ] (mxnet) Jason Dai  
     Comments:
  - [X] (mxnet) Furkan Kamaci  
     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 210 subscribers, an increase of 6% 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.  
  * One new committer has been added since the last report.  

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

  * We have recentlymade attractedsignificant asteps newtoward contributorlicense empiredanclearing, needed for  who
 have merged 2 
graduation: In PRsthis until now.

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

  We are still actively working towards the next big release, which may be 
  called 2.2.0.
  We have open-sourced 3 subprojects that were temporarily maintained 
  outside the Apache orgnization:

  - https://github.com/pegasus-kv/admin-cli
  - https://github.com/pegasus-kv/pegic
  - https://github.com/pegasus-kv/meta-proxy

  Those are tiny tools but also considered as very important complement to 
  the Pegasus ecosystem.
  `pegic` and `meta-proxy` are still in the initial stage. Developing under 
  the "pegasus-kv" orgnization gets us full control of the Github settings so
  that we can move faster.
  `admin-cli` is nearly completed and license-cleared and will soon be 
  migrated to Apache.
  The three projects will all eventually be moved to Apache.

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

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

  N/A

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

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

  Yes

### Signed-off-by:

  - [X] (pegasus) Kevin A. McGrail  
     Comments: Short report but accurate. 
  - [X] (pegasus) Duo zhang  
     Comments:  
  - [X] (pegasus) Liang Chen  
     Comments:  quarter, we have secured 34 ICLAs and 7 SGAs,  
    the most of any quarter so far, from past and present contributors.  
  * We have successfully made our third, fourth, and fifth releases  
    under the ASF umbrella: NuttX-10.0 followed by security fix releases  
    NuttX-9.1.1 and NuttX-10.0.1.  
  * Contributions are flowing regularly as PRs in GitHub with occasional  
    patches in the dev list.  
  * Many technical improvements, bug fixes, and new architectures have  
    been collaborated and work continues with an average of 6 and  
    sometimes as many as a dozen pull requests merged per day.  
  * We have listened to the valuable feedback received during our  
    previous releases and continue to improve our documentation. This can  
    be found at https://nuttx.apache.org/docs/latest/.  
  * We've implemented additional automatic checks on PRs.  This has  
    helped us to improve our review 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:

  NuttX-10.0.1 and NuttX-9.1.1 were released on 2020-12-08.

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

  Last elected PPMC: 2020-01-10

  Last committer added: 2020-12-30

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

  - [X] (pegasusnuttx) VonDuo GoslingZhang  
     Comments: Glad 

### IPMC/Shepherd notes:
  Justin Mclean: I like to see some explanation on why the sub-projects
  are being maintained outside of the project. There are branding and
  trademark issues and it may be best to consider moving them in-house.
  Also please list 3 unfinished issues that you still need to do to 
  graduate.

  Justin Mclean: Thanks for the explanation, if might be better if you you 
  worked with Infra on the GitHub settings, developing code outside the
  ASF is likely to cause a number of issues in the future when the code
  is moved.to see that we have made good progress on license 
     clearing.
  - [ ] (nuttx) Junping Du  
     Comments:  
  - [X] (nuttx) Justin Mclean  
     Comments:  
  - [ ] (nuttx) Mohammad Asif Siddiqui  
     Comments:  
  - [ ] (nuttx) Flavio Paiva Junqueira  
     Comments:  

### IPMC/Shepherd notes:

--------------------
## PonyMailPegasus

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

Pony Maildistributed key-value storage system which is designed to be
simple, horizontally scalable, strongly consistent and high-performance.

Pegasus has been incubating since 20162020-0506-2728.

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

  1. Attract more contributors and committers.
  2. Make more releases in ASF policy regularly.
  3. Resolve the license problems.

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

  N/A

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

  We have recently attracted a new contributor empiredan, who have merged 2 
  PRs until now.

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

  We are still actively working towards the next big release, which may be 

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

  called 2.2.0.
  We have open-sourced 3 subprojects that were temporarily maintained 
  outside the Apache orgnization:

  - https://github.com/pegasus-kv/admin-cli
  - https://github.com/pegasus-kv/pegic
  - https://github.com/pegasus-kv/meta-proxy

  Those are tiny tools but also considered as very important complement to 
  the Pegasus ecosystem.
  `pegic` and `meta-proxy` are still in the initial stage. Developing under 
  the "pegasus-kv" orgnization gets us full control of the Github settings 
so
  that we can move faster.
  `admin-cli` is nearly completed and license-cleared and will soon be 
  migrated to Apache.
  The three projects will all eventually be moved to Apache.

### 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
  - [ ] (ponymail) John D. Ament  
     Comments:  
  - [ ] (ponymail) Sharan Foga  
     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. Improve project structure and documentation
  2. Grow the community (attracting more committers, contributors, users)
  3. Publish more Apache releases

### 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 received contributions from a new external contributor.
  - We found a new project using Teaclave SGX SDK called Veracruz, which is 
  a
  framework for defining and deploying collaborative, privacy-preserving
  computations amongst a group of mutually mistrusting individuals.
  - We summarized the community and projects powered by Teaclave and 
  published
  a blog on our homepage.
  - Rust TrustZone SDK will be accepted in Teaclave as a subproject. The 
  community
  is discussing and voting the acceptance.
  - The community has accepted a new committer.

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

  - Add PCA function in the builtin executor.
  - Add exposed password checking function in the builtin executor.
  - Add the attestation subcommand to display attestation reports form the 
  Intel attestation service.
  - Add document to support deploying on Azure confidential computing VM.

### 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-10-09 (version 0.1.0)

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

  2020-10-22 (Ran Duan, commiter, rduan@apache)

### Have your mentors been helpful and responsive?

  Yes, our mentors are very helpful and responsive on our discussion about 
  security
  reporting and new projects acceptance voting.

### 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) 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.Adjust project goal && project name
  2.Keep growing the community, attract more contributors and committers
  3.Release Apache standard releases regularly

### Are there any issues that the IPMC or ASF Board need to be aware of?
  We hope more IPMCs will pay attention to our project and give more 
  suggestions.

### How has the community developed since the last report?
  Since the last report, the TubeMQ community has continued to improve its 
  functions
  as well as external publicity and communication; at the same time, we 
  PPMCs conducted
  a discussion on adjusting project objectives and project names.
  We hope to provide a complete one-stop streaming data service platform: 
  the system
  integrates a series of components in the form of plug-ins for collection, 
  aggregation,
  storage and forwarding to build a complete data reporting service; based 
  on this platform,
  users only need to publish and subscribe to data, and they can easily 
  build analysis and
  applications based on streaming data; and TubeMQ will continue to develop 
  in this project.

### How has the project developed since the last report?
  At this stage, we released the SDK of the Python language and the 
  tubemq-manager module for
  cluster management. The tubemq-manager module is used for cross-cluster 
  control to make
  the project more usable; we have also made a number of improvements in 
  the function of the project,
  for details information, please refer to our project issues: 
  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-12-04

### When were the last committers or PPMC members elected?
  1. yuanboliu was added as committer on 2020-12-10
  2. dockerzhang was added as PPMC on 2020-12-15

### Have your mentors been helpful and responsive?
  In the recent period, the mentors have given us a lot of help and 
  guidance;
  We hope that the mentors can continue to pay attention to the development 
  of our project and continue to provide more help and suggestions to the
  project.

### 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: Don't forget you can reach out to your mentors if you need 
     help. Keeping discussions on the mailing list also helps.
  - [ ] (tubemq) Sijie Guo  
     Comments:  
  - [ ] (tubemq) Zhijie Shen  
     Comments:  
  - [X] (tubemq) Jean-Baptiste Onofre  
     Comments:  

### IPMC/Shepherd notes:

--------------------
## Wayang

Wayang is a cross-platform data processing system that aims at decoupling
the business logic of data analytics applications from concrete data
processing platforms, such as Apache Flink or Apache Spark. Hence, it tames
the complexity that arises from the "Cambrian explosion" of novel data
processing platforms that we currently witness.

Wayang has been incubating since 2020-12-16.

### Three most important unfinished issues to address:

  1. Finishing the Software Grant paperwork
  2. Onboarding of the existing team at Apache 
  3. Getting Wayang setup on Apache infrastructure

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

There are no issues present at the moment

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

We are in the onboarding process, but got new developer requests which we process when the project is fully onboarded

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

We are in process to sort the software grant, getting the team on board and started code rebranding to fit the ASF regulatory framework

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

None yet

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

None yet

### Have your mentors been helpful and responsive?

Yes, the mentors are very responsive and helpful

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

We are managing the brand, to avoid conflict we renamed rheem into Wayang, the process is still ongoing

### Signed-off-by:

  - [X] (wayang) Christofer Dutz  
     Comments:  Seems getting the paperwork done takes a bit longer for universities and institues than for "normal" companies, but I'm hopeful that we'll sort out the remaining issues till the next report.
  - [ ] (wayang) Lars George  
     Comments:  
  - [X] (wayang) Bernd Fondermann  
     Comments:  cdutz signed off the report as Bernd had problems logging in (signoff on file in dev-list mail archive)
  - [X] (wayang) Jean-Baptiste Onofré  
     Comments:  Initial phase, but it moves forward anyway.

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

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

  - [ ] (weex) Willem Ning Jiang  
     Comments:  
  - [ ] (weex) Myrle Krantz  
     Comments:  Nearing graduation
  - [ ] Other:

### Date of last release:

  2020-11-30

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

  N/A

### Have your mentors been helpful and responsive?

  Yes

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

  Yes

### Signed-off-by:

  - [X] (pegasus) Kevin A. McGrail  
     Comments: Short report but accurate. 
  - [X] (pegasus) Duo zhang  
     Comments:  
  - [X] (pegasus) Liang Chen  
     Comments:  
  - [X] (pegasus) Von Gosling  
     Comments:  

### IPMC/Shepherd notes:
  Justin Mclean: I like to see some explanation on why the sub-projects
  are being maintained outside of the project. There are branding and
  trademark issues and it may be best to consider moving them in-house.
  Also please list 3 unfinished issues that you still need to do to 
  graduate.

  Justin Mclean: Thanks for the explanation, if might be better if you you 
  worked with Infra on the GitHub settings, developing code outside the
  ASF is likely to cause a number of issues in the future when the code
  is moved.

--------------------
## 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. Improve project structure and documentation
  2. Grow the community (attracting more committers, contributors, users)
  3. Publish more Apache releases

### 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 received contributions from a new external contributor.
  - We found a new project using Teaclave SGX SDK called Veracruz, which is 
  a
  framework for defining and deploying collaborative, privacy-preserving
  computations amongst a group of mutually mistrusting individuals.
  - We summarized the community and projects powered by Teaclave and 
  published
  a blog on our homepage.
  - Rust TrustZone SDK will be accepted in Teaclave as a subproject. The 
  community
  is discussing and voting the acceptance.
  - The community has accepted a new committer.

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

  - Add PCA function in the builtin executor.
  - Add exposed password checking function in the builtin executor.
  - Add the attestation subcommand to display attestation reports form the 
  Intel attestation service.
  - Add document to support deploying on Azure confidential computing VM.

### 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-10-09 (version 0.1.0)

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

  2020-10-22 (Ran Duan, commiter, rduan@apache)

### Have your mentors been helpful and responsive?

  Yes, our mentors are very helpful and responsive on our discussion about 
  security reporting and new projects acceptance voting.

### 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) 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.Adjust project goal && project name
  2.Keep growing the community, attract more contributors and committers
  3.Release Apache standard releases regularly

### Are there any issues that the IPMC or ASF Board need to be aware of?
  We hope more IPMCs will pay attention to our project and give more 
  suggestions.

### How has the community developed since the last report?
  Since the last report, the TubeMQ community has continued to improve its 
  functions
  as well as external publicity and communication; at the same time, we 
  PPMCs conducted
  a discussion on adjusting project objectives and project names.
  We hope to provide a complete one-stop streaming data service platform: 
  the system
  integrates a series of components in the form of plug-ins for collection, 
  aggregation,
  storage and forwarding to build a complete data reporting service; based 
  on this platform,
  users only need to publish and subscribe to data, and they can easily 
  build analysis and
  applications based on streaming data; and TubeMQ will continue to develop 
  in this project.

### How has the project developed since the last report?
  At this stage, we released the SDK of the Python language and the 
  tubemq-manager module for
  cluster management. The tubemq-manager module is used for cross-cluster 
  control to make
  the project more usable; we have also made a number of improvements in 
  the function of the project,
  for details information, please refer to our project issues: 
  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-12-04

### When were the last committers or PPMC members elected?
  1. yuanboliu was added as committer on 2020-12-10
  2. dockerzhang was added as PPMC on 2020-12-15

### Have your mentors been helpful and responsive?
  In the recent period, the mentors have given us a lot of help and 
  guidance;
  We hope that the mentors can continue to pay attention to the development 
  of our project and continue to provide more help and suggestions to the
  project.

### 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: Don't forget you can reach out to your mentors if you need 
     help. Keeping discussions on the mailing list also helps.
  - [ ] (tubemq) Sijie Guo  
     Comments:  
  - [ ] (tubemq) Zhijie Shen  
     Comments:  
  - [X] (tubemq) Jean-Baptiste Onofre  
     Comments:  

### IPMC/Shepherd notes:

--------------------
## Wayang

Wayang is a cross-platform data processing system that aims at decoupling
the business logic of data analytics applications from concrete data
processing platforms, such as Apache Flink or Apache Spark. Hence, it tames
the complexity that arises from the "Cambrian explosion" of novel data
processing platforms that we currently witness.

Wayang has been incubating since 2020-12-16.

### Three most important unfinished issues to address:

  1. Finishing the Software Grant paperwork
  2. Onboarding of the existing team at Apache 
  3. Getting Wayang setup on Apache infrastructure

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

  There are no issues present at the moment

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

  We are in the onboarding process, but got new developer requests which we 
  process when the project is fully onboarded

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

  We are in process to sort the software grant, getting the team on board and 
  started code rebranding to fit the ASF regulatory framework

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

  None yet

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

  None yet

### Have your mentors been helpful and responsive?

  Yes, the mentors are very responsive and helpful

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

  We are managing the brand, to avoid conflict we renamed rheem into Wayang, 
  the process is still ongoing

### Signed-off-by:

  - [X] (wayang) Christofer Dutz  
     Comments:  Seems getting the paperwork done takes a bit longer for 
     universities and institues than for "normal" companies, but I'm hopeful 
     that we'll sort out the remaining issues till the next report.
  - [X] (wayang) Lars George  
     Comments:  
  - [X] (wayang) Bernd Fondermann  
     Comments:  cdutz signed off the report as Bernd had problems logging 
     in (signoff on file in dev-list mail archive)
  - [X] (wayang) Jean-Baptiste Onofré  
     Comments:  Initial phase, but it moves forward anyway.

### 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. Establish a release cadence based on roadmap.
  3. Improve the ease of deployment and documentation quality.

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

  No issues at this point in time.

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

  New committer vote is in progress (delayed due to Christmas break).

  Two new large features started. Driven by different parts of the
  community: gang scheduling and open tracing.

  New release planned for the end of January 2021 and the search for a new
  release manager has started.

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

  Major scheduler core code update rewrite committed. 

  Upgrades to build tools to the latest supported tool versions.

  Testing matrix updated to support latest versions of Kubernetes.

  Some statistics for the report period (2020-10-01 till 2021-12-31)  
  JIRA: 67 created, 56 resolved  
  PRs: 55 opened, 58 resolved  
  10 unique active code 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-08-26

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

  New committer vote is in progress (delayed due to Christmas break).

### Have your mentors been helpful and responsive?

  Yes, review of PRs and part of the community syncs

### 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:  
  - [X] (yunikorn) Holden Karau  
     Comments:  

### IPMC/Shepherd notes:
Page tree

Versions Compared

Old Version 71

New Version Current

Key
