fold -w 76 -s $1 | cat -s

Incubator PMC report for April 2021

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

The Apache Incubator is the entry path into the ASF for projects and codebases wishing to become part of the Foundation's efforts. There are presently 36 podlings incubating. In March, podlings executed 6 distinct releases. We added 2 new IPMC members, and none retired. There was one IP clearance in March, and there were no new podlings. DolphinScheduler graduated last month. This month we were missing reports from Livy, Milagro, PageSpeed, Spot, and Weex. Livy, PageSpeed, and Spot have missed multiple reports, and roll calls will be taken to check these projects are still viable. Weex is in the process of retiring. Annotator and BlueMarlin do not have signoff by mentors and will also be asked to report next month. Pinot made a process error in making a release but will make sure it doesn't happen again. As with last month, MXNet still has outstanding trademark and branding issues, but they are working on it. As noted in the previous report, they are also having trouble getting IPMC votes on releases. Some old Incubator JIRA issues were cleared up, and some Incubator web pages updated. Further cleanup was done in removing old releases from retired podlings. As usual, most discussions on the mailing list were around releases, new project proposal and finding new mentors.

Community

New IPMC members:

• Atri Sharma
• Juan Pan

People who left the IPMC:

• None

New Podlings

• None

Podlings that failed to report, expected next month

• Livy
• Milagro
• PageSpeed
• Spot
• Weex

Graduations

• DolphinScheduler

The board has motions for the following:

• None

Releases

The following releases entered distribution during the month of March:

• Liminal 0.0.1
• MXnet 1.8.0
  • MXnet 2.0.0
• Pinot 0.7.0
• Teaclave 0.2.0
• TubeMQ 0.8.0

IP Clearance

• dubbo-go-pixiu

Legal / Trademarks

N/A

Infrastructure

N/A

Miscellaneous

N/A

Table of Contents

Annotator
BlueMarlin
DataLab
EventMesh
Flagon
Hivemall
Liminal
MXNet
NLPCraft
NuttX
Pegasus
PonyMail
Teaclave
Toree
TubeMQ
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. Add active contributors
2. Stabilize a release cadence
3. Continue to demonstrate good governance

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

Community building has been very slow and it has been a long time since the project added new committers or PPMC members. After a period of relative inactivity and a conversion of the codebase to TypeScript, the project is long overdue for a second release. The IPMC should expect to see the project vote on a second release before the next board report to demonstrate forward momentum.

How has the community developed since the last report?

There have been some one-off contributions to project documentation and questions raised by people evaluating the project for use, but there have not been sustained contributions or involvement from new folks yet.

How has the project developed since the last report?

The project is now making continuous development packages to make it easier for developers to test upcoming releases. There is now tooling in place for generating API documentation, with plans to integrate the generated documentation into the website. The existing interfaces have all been documented. These efforts are all focused around the current goal of building community by making it easier for developers to become familiar with the project.

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:

2020-07-11

When were the last committers or PPMC members elected?

2018-09-04

Have your mentors been helpful and responsive?

Yes. Mentors have been as available when needed, but the project will reach out to get advice on what else could be done to make the project more accessible to new contributors and to grow the community.

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

There are no branding issues that the PPM is aware of.

Signed-off-by:

•  (annotator) Nick Kew
  Comments:
•  (annotator) Tommaso Teofili
  Comments:
•  (annotator) Benjamin Young
  Comments:

IPMC/Shepherd notes:

Justin Mclean: With no sign-offs, it might be time to see if you can find an additional mentor.

---

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. Migrate issues from https://github.com/Futurewei-io/blue-marlin repository to https://github.com/apache/incubator-bluemarlin
2. Prepare a new Release
3. Clarify the policies to maintain the code and accept pull-requests from contributors

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?

No answer.

How has the project developed since the last report?

1. Bug fix for Lookalike Model project
2. Add tests for Lookalike Model project
3. Bug fix for Lookalike Application

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:

NA

When were the last committers or PPMC members elected?

None yet.

Have your mentors been helpful and responsive?

No answer.

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

No answer.

Signed-off-by:

•  (bluemarlin) Craig Russell
  Comments:
•  (bluemarlin) Jean-Baptiste Onofré
  Comments:
•  (bluemarlin) Von Gosling
  Comments:
•  (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:

1. 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 new PPMC members (Yurii Kinash, Mykola Bodnar, Leonid Frolov) and a new committer (Yurii Tykhun).

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 (done)
• Implement possibility of GPU usage for Jupyter and Dataproc on GCP (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
•  Nearing graduation
•  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 February 26, 2021.

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.

Signed-off-by:

•  (datalab) P. Taylor Goetz
  Comments:
•  (datalab) Henry Saputra
  Comments:
•  (datalab) Konstantin I Boudnik
  Comments:
•  (datalab) Furkan Kamaci
  Comments:

IPMC/Shepherd notes:

---

EventMesh

EventMesh is a dynamic cloud-native basic service runtime used to decouple the application and middleware layer.

EventMesh has been incubating since 2021-02-18.

Three most important unfinished issues to address before graduating:

1. Make more releases in ASF policy regularly.
2. Building community.

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

None

How has the community developed since the last report?

Preparing for some open talks, such as EDASubbmit and ApacheCon Asia.

How has the project developed since the last report?

Waiting for code migration to apache, and ready for first release of 1.2.2.

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:

None

When were the last committers or PPMC members elected?

None

Have your mentors been helpful and responsive?

Yes, Our mentors are very helpful and responsive.

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

The VP, Brand has approved the project name.

Signed-off-by:

•  (eventmesh) Francois Papon
  Comments:
•  (eventmesh) Junping Du
  Comments:
•  (eventmesh) Jean-Baptiste Onofre
  Comments:
•  (eventmesh) Justin Mclean
  Comments: Already working towards first release, well done!
•  (eventmesh) Von Gosling
  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. Currently discussing Graduation path (TLP, other TLP (e.g., Superset))
2. Continue VOTE thread for Graduation on general@incubator
3. (see commentary under podling maturity section)

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

None at this time.

How has the community developed since the last report?

We have seen increased user and contributor engagement:

• in development, this quarter we have contributed 60 new commits to UserALE.js alone, 15 of those were from 7 contributor PRs.
• we have seen an increase in visits to our GitHub UserALE.js from unique users (https://tinyurl.com/4cmcnn9a)
• we have seen a marked increase in contributor/user issue discussion (https://tinyurl.com/88wafvhk)
• we have also seen user/contributor participation in VOTEs (2.2.0 RC and new PPMC VOTEs)

We have also included and are now onboarding a new committer and PPMC member (see below).

How has the project developed since the last report?

We added a range of new features and hardened our core product (e.g., UserALE.js). Development has been consistent.

New features in the last quarter will frame an upcoming release candidate for UserALE.js v.2.2.0, and include:

• Redesigned logging pipelines
• Journey Tests
• Modernized Unit Tests
• Updated build pipeline

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:

We anticipate reviving a VOTE for graduation in 2021 Q2. We have addressed most issues raised by IPMC during last graduation VOTE (2020 Q4):

•  Add DISCLAIMER to subprojects to be retired (TAP, STOUT, UserALE.pyqt5, user-ale)
•  Make subprojects to be retired Read Only (in progress, but non-blocking)
•  Add logo to https://apache.org/logos/?#flagon
•  Update UserALE.js release processes for consistency with Apache policies for NPM Package Releases (see 2.1.1 release)
•  Get all committers subscribed to appropriate lists (might still be missing one, but have contacted all)

Date of last release:

2020-03-27 (UserALE.js 2.1.0)

Note: UserALE.js 2.1.1 has passed a successful release VOTE. 2.1.1 Release announcement is pending website update. Artifacts are currently available on mirrors, GitHub, and NPM.

When were the last committers or PPMC members elected?

2021-03-26 (Gedd Johnson). ICLA has been received by Secretary. He originates from one of our core user communities.

Have your mentors been helpful and responsive?

Mentors are supportive.

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

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

Signed-off-by:

•  (flagon) Lewis John McGibbney
  Comments:
•  (flagon) David Meikle
  Comments: Great to see the community engagement.
•  (flagon) Tim Allison
  Comments:
•  (flagon) Furkan Kamaci
  Comments: Thanks for the detailed report!

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?

PPMCs are considering exit approaches including retiring.

How has the community developed since the last report?

• Few traffics on mailing lists including requests to join the project from a Hive committer.
• 2-3 users issued JIRA tickets

How has the project developed since the last report?

• not so active. Only applied minor hotfixes.

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:

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?

Yes

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

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

Signed-off-by:

•  (hivemall) Daniel Dai
  Comments:
•  (hivemall) Koji Sekiguchi
  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. Grow developers community.
2. Adoption of the project by a few companies.
3. More releases - provide out-of-the-box usability for common use-cases.

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 started to engage with Airflow community (https://airflow.apache.org/ecosystem/). We plan to push the first release through social media.

How has the project developed since the last report?

We have released our first official Apache version + notes on running it on AWS. We have planned the timeline and content of the second version (due to May 2021).

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:

2021-03-16

When were the last committers or PPMC members elected?

NA

Have your mentors been helpful and responsive?

J.B. and Davor have been super helpful in approving the first release and in pushing infra issues.

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

NA

Signed-off-by:

•  (liminal) Jean-Baptiste Onofre
  Comments:
•  (liminal) Henry Saputra
  Comments:
•  (liminal) Uma Maheswara Rao G
  Comments:
•  (liminal) Davor Bonaci
  Comments: Very happy to see the first release completed!
•  (liminal) Liang Chen
  Comments:

IPMC/Shepherd notes:

Dave Fisher - I sent a note to the PPMC suggesting that they start their Suitable Name Search soon.

---

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 release issues, improve automation for license checks, and make it easier for auditing.
   • DONE
2. 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 fixed the issues in INCUBATOR-253 and will continue to perform regular trademark and branding review.
2. Following the completion of license and release issue fixes, MXNet had difficulty finishing the releases votes in Incubator. Here are the stats for the two recent successful releases:

	1.8.0	2.0.0.alpha
duration	39 days	27 days
issues uncovered (fixed after release)	5	2
mentor participation	50%	25%

We have one mentor who indicated the desire to step down if we can find more mentors. We will request for a few more active mentors to help us smoothly finish the last mile before graduation.

1. We conduct regular brand management review as part of the regular reporting. From recent brand usage review for MXNet third-party distributions, we found several listings on AWS marketplace that need update. The PPMC reached out to the publishers of these listings for correction. See status in brand management section.

How has the community developed since the last report?

• The number of GitHub contributors increased to currently 955

• 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.39k subscriber (+4.5% since last report)
  • Chinese YouTube channel (https://www.youtube.com/channel/UCjeLwTKPMlDt2segkZzw2ZQ) w/ 6.55k subscribers (+1.8%)
  • (in China) bilibili space (https://space.bilibili.com/209599371) w/ 28k subscriber (+7.6% since last report)

• Highlights in MXNet ecosystem

  • Dive into Deep Learning has 67K 30-day active users, and has attracted 31.3K stars & 350 contributors on GitHub. It has been adopted as a textbook or reference book by 180+ universities from 40 countries, such as Stanford, MIT, UC Berkeley, CMU, UCambridge.
  • GluonCV v0.10.0 release (https://github.com/dmlc/gluon-cv/releases/tag/v0.10.0)
  • GluonNLP MX2 NumPy version (https://github.com/dmlc/gluon-nlp/tree/master)
  • GluonTS v0.6.7 release (https://github.com/awslabs/gluon-ts/releases/tag/v0.6.7)
  • DeepInsight (https://github.com/deepinsight/insightface)
  • Sockeye 2.3.14 release (https://github.com/awslabs/sockeye)

How has the project developed since the last report?

1. 1.8.0 is released: https://github.com/apache/incubator-mxnet/releases/tag/1.8.0 with 100+ patches of new features, improvements, and fixes.
2. 2.0.0 alpha is released: https://github.com/apache/incubator-mxnet/projects/18 https://github.com/apache/incubator-mxnet/releases/tag/2.0.0.alpha
3. Github statistics of last month:
   • March 7, 2021 – April 7, 2021: Excluding merges, 18 authors have pushed 33 commits to master and 67 commits to all branches. On master, 10 files have changed and there have been 206 additions and 71 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
•  Nearing graduation
•  Other:

Date of last release:

2021-03-24

When were the last committers or PPMC members elected?

2021-02-03

Have your mentors been helpful and responsive?

Yes. Furkan has helped with all our recent releases (thanks!). Markus 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. From recent brand usage review for MXNet third-party distributions, we found several listings on AWS marketplace that need update. The PPMC reached out to the publishers of these listings for correction. Here we report the status of these items.

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

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

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

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

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

https://aws.amazon.com/marketplace/search/results?x=0&y=0&searchTerms=%22MX (pending)

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

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

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

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

Signed-off-by:

•  (mxnet) Markus Weimer
  Comments:
•  (mxnet) Bob Paulin
  Comments:
•  (mxnet) Jason Dai
  Comments:
•  (mxnet) Furkan Kamaci
  Comments:

IPMC/Shepherd notes:

---

NLPCraft

Apache NLPCraft is an open source library for adding natural language Interface to modern applications. Apache NLPCraft has been incubating since 2020-02-13.

Three most important unfinished issues to address before graduating:

1. Community growth & outreach.
2. Multiple release managers.
3. Presenting the project at ApacheCon 2021.

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?

Project have several new contributors that we are expecting to formally join the project/ASF in the future. These are individuals outside of the original NLPCraft community. We are also getting number of offline contributions when it comes to ideas, testing and website. We are working on promoting these contributions and inviting these individuals to be more active. We need, however, to get much better at the general project outreach via meetups, conferences, etc.

Project has 8 forks on the Github.

How has the project developed since the last report?

Project produced 2 releases. Both releases were an interim, bug fix releases. So far, they were produced by the same release manager (Aaron Radzinski). The community is working on the major release 0.7.5 right now that should go GA in the April 2021 with significant changes and improvements (all of which are relfected in JIRA tickets for 0.7.5 version). At this point, the community does not have a formalized roadmap with many internal discussions happening on Slack channels. We are generally expecting to formalize the long-term roadmap towards 1.0.0 release with hopefully a larger community around the project.

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:

NLPCraft 0.7.4 released on Jan 31, 2021.

When were the last committers or PPMC members elected?

Aug, 2020 - Gleb Zernov (ifropc), committer.

Have your mentors been helpful and responsive?

We have some problems with getting attention from mentors. Release voting can go for weeks without attention from mentors that is slowing down the progress on the project. However, the mentors' participation has improved lately. We've also identified some of the communication inefficiencies that would help us to engage mentors better going forward.

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

Yes, no issues to report.

Signed-off-by:

•  (nlpcraft) Roman Shaposhnik
  Comments:
•  (nlpcraft) Furkan Kamaci
  Comments: Thanks for giving so much time to this month's report.
•  (nlpcraft) Evans Ye
  Comments:
•  (nlpcraft) Paul King
  Comments:
•  (nlpcraft) Konstantin I Boudnik
  Comments:
•  (nlpcraft) Dave Fisher
  Comments: Thanks for the more detailed report.

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 230 subscribers, an increase of 9% 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.
• No new committer(s) have been added since the last report.

How has the project developed since the last report?

• We have made significant steps toward license clearing, needed for
  graduation: In this quarter, thousands of files have been cleared
  and changed to the Apache 2.0 License through the large effort of
  our volunteers. Since joining the Incubator, more than 10,000 files
  have been changed to the Apache 2.0 License with the permission of
  more than 60 individuals and 16 organizations who signed ICLAs, CCLAs,
  and SGAs to assist us in getting closer to graduation. We are
  grateful to everyone for their invaluable support through this
  important process.
• We continue to secure ICLAs and SGAs from from past and present
  contributors and have secured 8 new ICLAs and 3 new SGAs this
  quarter.
• 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 9 and
  sometimes more than a dozen pull requests merged per day.
• We have not made any new releases during this quarter but have begun
  discussing the next release, tentatively set for next month.
• 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 are working to streamline our GitHub PR checks to use fewer
  resources while still giving providing early feedback of potentially
  disruptive problems. The GitHub PR checks have helped us immensely in
  improving our code quality and compliance to project standards.

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:

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:

•  (nuttx) Duo Zhang
  Comments: Glad to see the big step on license clearing!
•  (nuttx) Junping Du
  Comments:
•  (nuttx) Justin Mclean
  Comments: Great work on the license, ICLA and SGA work. You could graduate without that 100% done as long at the 3rd party licenses are ALv2 compatible.
•  (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. Make roadmap of Pegasus annually.
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?

Not significantly.

How has the project developed since the last report?

We have prepared to raise voting for the release 2.2.0 as we have well-tested the beta version in Xiaomi.

The changes were summarized here: https://github.com/apache/incubator-pegasus/issues/696.

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:

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:

•  (pegasus) Kevin A. McGrail
  Comments:
•  (pegasus) Duo zhang
  Comments: I think we'd better add 'Growing the community' to our important issues.
•  (pegasus) Liang Chen
  Comments:
•  (pegasus) Von Gosling
  Comments:

IPMC/Shepherd notes:

---

PonyMail

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

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

Three most important unfinished issues to address before graduating:

1. Further grow community
2. Work towards foal 1.0

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 community welcomes Sean Palmer to the committers roster, and appreciates his work on DKIM parsing for Pony Mail and Foal.

How has the project developed since the last report?

Work is underway for a release-worthy edition of Foal.

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:

2019-04-02

When were the last committers or PPMC members elected?

Sean Palmer was elected committer on April 2nd, 2021.

Have your mentors been helpful and responsive?

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

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

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

Signed-off-by:

•  (ponymail) John D. Ament
  Comments:
•  (ponymail) Sharan Foga
  Comments: Great to see a new committer added to the project. Community size is still small so hope that the work around the Foal release may help attract new users or contributors.

IPMC/Shepherd notes:

---

Teaclave

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

Teaclave has been incubating since 2019-08-20.

Three most important unfinished issues to address before graduating:

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

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

None.

How has the community developed since the last report?

Since the last report, we have started monthly virtual meetups for three times. Many people from the community share their usage experience of Teaclave. Also, we invited some contributors to talk about some technical details of the design and implementation. For each meetup, we have minutes write-up published on the Teaclave blog.

• Teaclave Meetup #1: https://teaclave.apache.org/blog/2021-01-27-teaclave-meetup-1/
• Teaclave Meetup #2: https://teaclave.apache.org/blog/2021-02-24-teaclave-meetup-2/
• Teaclave Meetup #3: https://teaclave.apache.org/blog/2021-03-24-teaclave-meetup-3/

In addition, we have one more project (Crust Network) powered by Teaclave joined in our "Powered By" page on the Teaclave homepage.

• https://teaclave.apache.org/powered-by/

How has the project developed since the last report?

During this period, we also accepted the Rust OP-TEE TrustZone SDK project to Teaclave as a sub-project, named as Teaclave TrustZone SDK. Similar to Teaclave SGX SDK, Teaclave TrustZone SDK will be the foundation of the Teaclave FaaS platform to support multiple trusted execution environments.

• Welcome Rust OP-TEE TrustZone SDK TO Teaclave: https://teaclave.apache.org/blog/2021-03-14-welcome-rust-optee-trustzone-sdk /

We published a project roadmap in 2021:

• Roadmap in 2021: Project Maturity and Community Buildup: https://teaclave.apache.org/blog/2021-01-19-roadmap-in-2021-project-maturity -and-community-buildup/

We also announce the 0.2.0 release. In 0.2.0, we focus on various components including built-in functions, SDKs in different languages, docker, command line interface, documents, etc.

• Announcing Apache Teaclave (incubating) 0.2.0: https://teaclave.apache.org/blog/2021-03-01-announcing-teaclave-0-2-0/

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:

2021-03-02: Apache Teaclave (incubating) 0.2.0

When were the last committers or PPMC members elected?

2020-10-22, Ran Duan (rduan), Committer

Have your mentors been helpful and responsive?

Yes, our mentors work responsively to help us with accepting new project donation into Teaclave.

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) Matt Sicker
  Comments:
•  (teaclave) Zhijie Shen
  Comments:

IPMC/Shepherd notes:

---

Toree

Toree provides applications with a mechanism to interactively and remotely access Apache Spark.

Toree has been incubating since 2015-12-02.

Three most important unfinished issues to address before graduating:

1.Increase active contributors 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?

It has been a quiet few months, with a few bug reported related to Apache Spark 3.x. The community also needs to update the latest RC to conform to the changes on release requirements for python packages.

How has the project developed since the last report?

Quiet few months with work needed to be done on the failed RC.

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:

2020-07-31

When were the last committers or PPMC members elected?

Kevin Bates was added to the PPMC on 2019-08-14

Have your mentors been helpful and responsive?

There was nothing requiring mentor intervention on the last quarter.

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

No Trademark issues

Signed-off-by:

•  (toree) Luciano Resende
  Comments:
•  (toree) Julien Le Dem
  Comments:
•  (toree) Ryan Blue
  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.Complete the project rename task 2.Improve and optimize the system to solve system Short board 3.Promote the system, to let more people to use and participate in the community

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

One, Our rename implementation Jira[1] still has no clear completion time. Since the new name passed and mentor JB submitted the rename Jira[1] on March 11, after the priority of the jira was adjusted from Major to Minor on March 13, the mentors has pinged several times, but still no more movement.

https://issues.apache.org/jira/projects/INFRA/issues/INFRA-21558?filter=allo penissues

How has the community developed since the last report?

We have recently deployed the community TubeMQ 0.8.0 version in our environment, from the comparison of before and after the gray-scale, the performance of the version is at least 5% higher than before, especially the metric of the number of disks written has dropped significantly, and the problems found have been reported back to the community for repair.

At the same time, we have conducted three times offline technical exchanges with the technical teams of other different companies (the relevant communication documents have been placed on the external website for other business review and analysis). Through the comparison of the environmental issues of different companies in the big data scenario, TubeMQ has relatively good cost advantages and technical characteristics. We will continue to choose to cooperate with companies with similar scenario requirements to let more people, company, who need this ability uses this component, and participates in the operation of the community.

In addition to using email to synchronize information, we created an "inlong" channel in ASF on Slack to meet and solve the needs of users for timely communication.

How has the project developed since the last report?

When we were preparing for the release of TubeMQ 0.8.0 without the "-WIP" tag, we discovered that the BDB component that the project metadata management module relies on has a license authorization problem, we are refactoring this part to meet Apache's license requirements.

At the same time, our project has submitted an application for name change and has been approved by Apache. We are currently preparing for the content of the project after the name change, including the project homepage, Logo, modules to be open sourced, documentation, etc, and some of the content has been completed and is waiting to be applied online after the name change is completed; the name change implementation Jira [1] has been submitted by Mentor JB on March 11, and is still in pending status without clear implementation completion time.

https://issues.apache.org/jira/projects/INFRA/issues/INFRA-21558?filter=allo penissues

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:

2021-03-05

When were the last committers or PPMC members elected?

yuanboliu - was added as committers on 2020-12-10

dockerzhang - was added as PPMC on 2020-12-15

Have your mentors been helpful and responsive?

Yes, the mentors Justin and JB in the project improvement stage gave us a lot of help.

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

Yes, all good here.

Signed-off-by:

•  (tubemq) Junping Du
  Comments:
•  (tubemq) Justin Mclean
  Comments: Rename issue has been resolved.
•  (tubemq) Sijie Guo
  Comments:
•  (tubemq) Zhijie Shen
  Comments:
•  (tubemq) Jean-Baptiste Onofre
  Comments:

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. Release regularly, split large changes over multiple releases.
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?

Added one new committer, and several new contributors.
Delivered two large features in new release v0.10.
Release v0.10 has been approved by the community and is up for a vote in the IPMC.

How has the project developed since the last report?

New release with a new release manager (3rd for 3 releases) voted on by community. Voting thread just created for a IPMC vote.
Major new functionality gang scheduling delivered.
New community members tested pre-release code and were active in the development phase.

Some statistics for the report period (2021-01-01 till 2021-03-31):
JIRA: 125 created, 99 resolved
PRs: 86 opened, 84 resolved
12 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
•  Community building
•  Nearing graduation
•  Other:

Date of last release:

2020-08-26

When were the last committers or PPMC members elected?

2021-02-04 committer added

Have your mentors been helpful and responsive?

yes

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

No issues that we are aware of.

Signed-off-by:

•  (yunikorn) Junping Du
  Comments:
•  (yunikorn) Felix Cheung
  Comments:
•  (yunikorn) Jason Lowe
  Comments:
•  (yunikorn) Holden Karau
  Comments:

IPMC/Shepherd notes: