DRAFT DRAFT DRAFT

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

It also best to:

Do not change existing formatting. Especially do not change the formatting of the sign-off area.
Keep all lines under 76 characters long.
All content under the ### headings should be indented by two spaces. Do not use tabs.
Please don't change the text in the headings or add new ones.
Include one space after a bullet point or full stop on a numbered list.
Use [X] (X and no spaces) to sign off reports.
Do not include long URLs and use the apache URL shortener https://s.apache.org.
Please note that some lines have two spaces at the end. Do not remove these spaces.

Please make sure you use the current report and don't copy an old one, the headings do change from time to time.

A script will be run on this report before it is submitted to the board. If your lines are too long it may insert line breaks in unexpected places.

Reflow

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

Timeline

Wed July 01	Podling reports due by end of day
Sun July 05	Shepherd reviews due by end of day
Sun July 05	Summary due by end of day
Tue July 07	Mentor signoff due by end of day
Wed July 08	Report submitted to Board
Wed July 15	Board meeting

Shepherd Assignments

Dave Fisher	Flagon
Dave Fisher	SDAP
Drew Farris	NuttX
Drew Farris	S2Graph
Justin Mclean	Annotator
P. Taylor Goetz	APISIX
P. Taylor Goetz	TVM
P. Taylor Goetz	Teaclave
Timothy Chen	MXNet
Timothy Chen	NLPCraft
Timothy Chen	Pony Mail
	DLab
	Gobblin
	Livy
	Milagro
	Pinot
	TubeMQ
	Weex
	YuniKorn

Incubator PMC report for July 2020

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

TODO add narrative

Podlings that failed to report, expected next month

Graduations

list podling here

The board has motions for the following:

Your podling here?

Releases

The following releases entered distribution during the month of June:

AGE

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

AGE has been incubating since 2020-04-29.

Three most important unfinished issues to address before graduating:

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:

When were the last committers or PPMC members elected?

Have your mentors been helpful and responsive?

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

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

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

Signed-off-by:

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

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:

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:

When were the last committers or PPMC members elected?

Have your mentors been helpful and responsive?

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

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

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

Signed-off-by:

(annotator) Nick Kew
Comments:
(annotator) Tommaso Teofili
Comments:

APISIX

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

APISIX has been incubating since 2019-10-17.

Three most important unfinished issues to address before graduating:

APISIX have already completed all issue, here is a review since the last report.

We released APISIX 1.2, APISIX 1.3, those release are done by twenty-eight contributors
We added five committers and two PPMC members
Resolved branding issues, such as:

The website(http://apisix.apache.org/) shows more clearly that it is an Apache incubator project
The APISIX luarocks package site shows more clearly that itis an Apache incubator project
Removed external links in github's readme document

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

None

How has the community developed since the last report?

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

How has the project developed since the last report?

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

How would you assess the podling's maturity?

Please feel free to add your own commentary.

Initial setup
Working towards first release
Community building
Nearing graduation
Other:

Date of last release:

Fri Jun 19 2020 (1.3)

When were the last committers or PPMC members elected?

At May 3 2020 PPMC members elected a new PPMC member @Nirojan Selvanathan
At May 29 2020 PPMC members elected a new commiter @ShiningRush
At May 3 2020 PPMC members elected a new PPMC member @Akayeshmantha
At Jun 8 2020 PPMC members elected a new commiter @qiujiayu
At Jun 8 2020 PPMC members elected a new commiter @gxthrj
At Jun 9 2020 PPMC members elected a new commiter @LiteSun
At Jun 10 2020 PPMC members elected a new commiter @dabue

Have your mentors been helpful and responsive?

Yes, mentors are very helpful.

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

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

Signed-off-by:

(apisix) Willem Ning Jiang
Comments:
(apisix) Justin Mclean
Comments:
(apisix) Kevin Ratnasekera
Comments:
(apisix) Von Gosling
Comments:

IPMC/Shepherd notes:

BlueMarlin

TODO

BlueMarlin has been incubating since 2011-12-23.

Three most important unfinished issues to address before graduating:

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) TODO
Comments:

IPMC/Shepherd notes:

DolphinScheduler

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

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

Three most important unfinished issues to address before graduating:

Guide community to commit code and code reivew using Apache way.
Develop more commiters and contributors.

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

None

How has the community developed since the last report?

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

How has the project developed since the last report?

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

How would you assess the podling's maturity?

Please feel free to add your own commentary.

Initial setup
Working towards first release
Community building
Nearing graduation
Other:

Date of last release:

2020-2-24

When were the last committers or PPMC members elected?

2020-5-28

Have your mentors been helpful and responsive?

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

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

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

Signed-off-by:

(dolphinscheduler) Sheng Wu Comments:
(dolphinscheduler) ShaoFeng Shi Comments:
(dolphinscheduler) Liang Chen Comments:
(dolphinscheduler) Furkan KAMACI Comments:
(dolphinscheduler) Kevin Ratnasekera Comments:

IPMC/Shepherd notes:

DLab

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

DLab has been incubating since 2018-08-20.

Three most important unfinished issues to address before graduating:

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

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

No issues.

How has the community developed since the last report?

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

How has the project developed since the last report?

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

How would you assess the podling's maturity?

Please feel free to add your own commentary.

Initial setup
Working towards first release
Community building
Nearing graduation
Other: working towards next release

Date of last release:

2020-24-04

When were the last committers or PPMC members elected?

The last committer was elected on February 2, 2020.

Have your mentors been helpful and responsive?

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

Yes, our mentors are super helpful and responsive.

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

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

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

Signed-off-by:

(dlab) P. Taylor Goetz
Comments:
(dlab) Henry Saputra
Comments:
(dlab) Konstantin I Boudnik
Comments:
(dlab) 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:

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:

(flagon) Lewis John McGibbney
Comments:
(flagon) David Meikle
Comments:
(flagon) Tim Allison
Comments:
(flagon) Furkan Kamaci
Comments:

IPMC/Shepherd notes:

Gobblin

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

Gobblin has been incubating since 2017-02-23.

Three most important unfinished issues to address before graduating:

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

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

No.

How has the community developed since the last report?

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

How has the project developed since the last report?

Owen O'Malley joined the Gobblin community as a mentor.
Discussion about graduation has started, and community is working towards it.
Two PPMC members were voted in.
Work on new release has started.

On technical side:

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

How would you assess the podling's maturity?

Please feel free to add your own commentary.

Initial setup
Working towards first release
Community building
Nearing graduation
Other:

Date of last release:

2018-12-09 (work on new release has started)

When were the last committers or PPMC members elected?

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

Have your mentors been helpful and responsive?

Yes.

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

Yes, but we have to perform podling namesearch.

Signed-off-by:

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

IPMC/Shepherd notes:

Hivemall

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

Hivemall has been incubating since 2016-09-13.

Three most important unfinished issues to address before graduating:

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

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

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

How has the community developed since the last report?

Not active.

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

How has the project developed since the last report?

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

Created 2 tickets and resolved 2 issues, mainly 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?

Koji is active at mentoring.

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

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

Signed-off-by:

(hivemall) Daniel Dai
Comments:
(hivemall) Koji Sekiguchi
Comments:

IPMC/Shepherd notes:

Liminal

TODO

Liminal has been incubating since 2020-05-23.

Three most important unfinished issues to address before graduating:

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:

(liminal) TODO
Comments:
(liminal) TODO
Comments:

IPMC/Shepherd notes:

Livy

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

Livy has been incubating since 2017-06-05.

Three most important unfinished issues to address before graduating:

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:
(livy) Luciano Resende
Comments:
(livy) Jean-Baptiste Onofre
Comments:

IPMC/Shepherd notes:

Milagro

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

Milagro has been incubating since 2015-12-21.

Three most important unfinished issues to address before graduating:

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.
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.
Further releases to increase the scope of the Milagro project, extend the capability of existing releases and to demonstrate improved compliance with the Apache Way.

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

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

How has the community developed since the last report?

No change.

How has the project developed since the last report?

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

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

How would you assess the podling's maturity?

Please feel free to add your own commentary.

Initial setup
Working towards first release
Community building
Nearing graduation
Other:

Date of last release:

2020-02-10

When were the last committers or PPMC members elected?

February 2020

Have your mentors been helpful and responsive?

No issues.

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

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

Signed-off-by:

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

IPMC/Shepherd notes:

MXNet

A Flexible and Efficient Library for Deep Learning

MXNet has been incubating since 2017-01-23.

Three most important unfinished issues to address before graduating:

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:

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

IPMC/Shepherd notes:

NuttX

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

NuttX has been incubating since 2019-12-09.

Three most important unfinished issues to address before graduating:

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

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

None

How has the community developed since the last report?

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

How has the project developed since the last report?

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

How would you assess the podling's maturity?

Please feel free to add your own commentary.

Initial setup
Working towards first release
Community building
Nearing graduation
Other:

Date of last release:

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

When were the last committers or PPMC members elected?

Last elected PPMC: 2020-01-10

Last committer added: 2020-05-17

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

Have your mentors been helpful and responsive?

Mentors are helpful and responsive.

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

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

Signed-off-by:

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

IPMC/Shepherd notes:

Pony Mail

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

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

Three most important unfinished issues to address before graduating:

Grow the community (that's about it)

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

None at present.

How has the community developed since the last report?

Discussion about graduation has been ongoing, but stagnated in the summer months. Something to pick up later, no rush on graduation.

How has the project developed since the last report?

A new Web UI is being proposed donated to the project. As things are slow during summer, this might take a while to sort out.

How would you assess the podling's maturity?

Please feel free to add your own commentary.

Initial setup
Working towards first release
Community building
Nearing graduation
Other:

Date of last release:

2019-04-20

When were the last committers or PPMC members elected?

Sebb was added to the roster in July of 2017.

Have your mentors been helpful and responsive?

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

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

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

Signed-off-by:

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

IPMC/Shepherd notes:

Spot

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

Spot has been incubating since 2016-09-23.

Three most important unfinished issues to address before graduating:

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

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

Not at this time.

How has the community developed since the last report?

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

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

How has the project developed since the last report?

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

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

2017-09-08

When were the last committers or PPMC members elected?

2020-05-14 - Jeremy Nelson

Have your mentors been helpful and responsive?

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

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

Yes

Signed-off-by:

(spot) Uma Maheswara Rao G
Comments:

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:

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

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

No.

How has the community developed since the last report?

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

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

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

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

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

How has the project developed since the last report?

Since the last report, we have completed the development roadmap towards the first public release (https://github.com/apache/incubator-teaclave/issues/121) proposed last year. We began to put more efforts on improving documents and building community.

We wrote many documents in recent weeks including:

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

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

How would you assess the podling's maturity?

Initial setup
Working towards first release
Community building
Nearing graduation
Other:

Date of last release:

N/A

When were the last committers or PPMC members elected?

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

Have your mentors been helpful and responsive?

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

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

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

Signed-off-by:

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

IPMC/Shepherd notes:

TubeMQ

TubeMQ is a distributed messaging queue (MQ) system.

TubeMQ has been incubating since 2019-11-03.

Three most important unfinished issues to address before graduating:

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

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

None.

How has the community developed since the last report?

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

How has the project developed since the last report?

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

How would you assess the podling's maturity?

Please feel free to add your own commentary.

Initial setup
Working towards first release
Community building
Nearing graduation
Other:

Date of last release:

2020-06-08

When were the last committers or PPMC members elected?

Technoboy- was added as committer on 2020-04-21

Have your mentors been helpful and responsive?

Yes.

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

Yes, all good here.

Signed-off-by:

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

IPMC/Shepherd notes:

TVM

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

TVM has been incubating since 2019-03-06.

Three most important unfinished issues to address before graduating:

1.Keep growing the community

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

no

How has the community developed since the last report?

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

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

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

How has the project developed since the last report?

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

See also our monthly reports for detailed improvements

How would you assess the podling's maturity?

Initial setup
Working towards first release
Community building
Nearing graduation
Other:

Date of last release:

2019-12-1

The community is voting on a new release now

When were the last committers or PPMC members elected?

Have your mentors been helpful and responsive?

Our mentors are super helpful.

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

yes

Signed-off-by:

(tvm) Byung-Gon Chun
Comments:
(tvm) Sebastian Schelter
Comments:
(tvm) Henry Saputra
Comments: Community is growing and healthy
(tvm) Timothy Chen
Comments:
(tvm) Furkan Kamaci
Comments:
(tvm) Tianqi Chen
Comments:
(tvm) Markus Weimer
Comments: Looking forward to graduation soon.

IPMC/Shepherd notes:

Warble

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

Warble has been incubating since 2018-06-11.

Three most important unfinished issues to address before graduating:

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

How has the community developed since the last report?

How has the project developed since the last report?

How would you assess the podling's maturity?

Please feel free to add your own commentary.

Initial setup
Working towards first release
Community building
Nearing graduation
Other:

Date of last release:

XXXX-XX-XX

When were the last committers or PPMC members elected?

Have your mentors been helpful and responsive?

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

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

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

Signed-off-by:

(warble) Chris Lambertus
Comments:

IPMC/Shepherd notes:

Weex

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

Weex has been incubating since 2016-11-30.

Three most important unfinished issues to address before graduating:

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:

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:

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

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

No critical issues at this point in time

How has the community developed since the last report?

The community has provided new use cases and pain points which helped shape the roadmap. A new website build was contributed to help improve access to the documentation.

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

How has the project developed since the last report?

A large number of changes have been made specifically to the deployment and testing side of the project:

moved to full Travis CI build
added e2e tests
provide convenience deployment via helm charts and ASF docker hub

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

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

How would you assess the podling's maturity?

Please feel free to add your own commentary.

Initial setup
Working towards first release
Community building
Nearing graduation
Other:

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

Page tree

Timeline

Shepherd Assignments