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 October 07	Podling reports due by end of day
Sun October 11	Shepherd reviews due by end of day
Sun October 11	Summary due by end of day
Tue October 13	Mentor signoff due by end of day
Wed October 14	Report submitted to Board
Wed October 21	Board meeting

Shepherd Assignments

Dave Fisher	Annotator
Dave Fisher	NuttX
Drew Farris	S2Graph
Drew Farris	Teaclave
Justin Mclean	DLab
P. Taylor Goetz	APISIX
P. Taylor Goetz	Weex
P. Taylor Goetz	YuniKorn
Timothy Chen	BlueMarlin
Timothy Chen	Livy
Timothy Chen	Warble
	AGE
	Flagon
	Gobblin
	Liminal
	MXNet
	Milagro
	Pegasus
	Pony Mail
	SDAP
	Sedona
	TVM
	TubeMQ

Report text goes here

Incubator PMC report for October 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 September:

AGE

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

AGE has been incubating since 2020-04-29.

Three most important unfinished issues to address before graduating:

1.Website Deployment. 2.Our first 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?

We are working on developing our community better by engaging more people and getting involved in different events such as outreach program.

How has the project developed since the last report?

The project has been actively developed. The new development has all been pushed actively.

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?

None.

Have your mentors been helpful and responsive?

Yes. They have been helpfull and very 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?

PPMC is not managing the podling's brand / trademarks.

Signed-off-by:

(age) Kevin Ratnasekera
Comments:
(age) Von Gosling
Comments: Very near to the first apache release, and needs to be more activity and voice in community, such as dev-mail list, new committers.
(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:

Add active contributors and grow the PPMC
Grow the community through clear communication and onramps
Demonstrate good governance

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?

Community calls have had regular attendance by committers and new users. New users consuming Annotator 0.1.0 have begun contributing feedback, bug reports, and use cases.

How has the project developed since the last report?

The project has finished its conversion to TypeScript, begun adding the infrastructure for generating documentation on the website, and is finalizing the feature set for 0.2.0.

How would you assess the podling's maturity?

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

When were the last committers or PPMC members elected?

June 6, 2018

Have your mentors been helpful and responsive?

Mentors have not been engaged recently, but there have not been any recent issues that have come up.

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

The project is not aware of any branding or trademark issues.

Signed-off-by:

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

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:

Bootstrap the podling
Make releases
Grow a community

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

None. We are just slow to start.

How has the community developed since the last report?

N/A

How has the project developed since the last report?

This is our first response

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?

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.

Bootstrapping fell through the cracks, but now is progressing.

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) Dave Fisher
Comments: I wrote this bare report.
(bluemarlin) Craig Russell
Comments:
(bluemarlin) Jean-Baptiste Onofré
Comments: Very slow bootstrapping, we will move forward now.
(bluemarlin) Von Gosling
Comments: Could not contact the core developers offline :-(
(bluemarlin) Junping Du
Comments:
(bluemarlin) Uma Maheswara Rao G
Comments:

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:

Alter all artifacts according to a new podling name.
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 committer (java-developer) - Pavel Papou and a new PPMC member - Oleg Fuks (java-developer).

How has the project developed since the last report?

The team has released v.2.4.0.
Our team is working towards the release 2.5.0 which contains migration to Py3, Edge node recreation capability, support of Spark v.3.x.x, localization, switch to modular architecture.

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

When were the last committers or PPMC members elected?

The last committer was elected on August 31, 2020 and the last PPMC member was elected on July 27, 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?

The new name has been approved. Now we are working in the direction of changing all references to DLab that are publicly accessible to Data Lab.

Signed-off-by:

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

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:

Work with IPMC to approve draft graduation resolution (blocking)
Update release practices to be consistent with NPM, Python registry (non-blocking)
Push new UserALE.js release (non-blocking)

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

No major issues at this time.
However, the community has been affected by COVID impacts on certain sectors.

How has the community developed since the last report?

COVID has affected community engagement and onboarding new committers
User base remains strong and continues to grow in specific markets
We continue to train and socialize new committers

How has the project developed since the last report?

Project maturity roadmaps & release plans are maintained
Sub-projects are being migrated to Git Issues
Core product source code is well maintained
We continue to develop our analytical produce to expand interest

How would you assess the podling's maturity?

Please feel free to add your own commentary.

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

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?

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

Our mentors have been very supportive and responsive
Our mentors have urged us to create a Graduation resolution

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

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

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

Signed-off-by:

(flagon) Lewis John McGibbney
Comments: Flagon is very close to graduation. The podling status page has been updated to reflect reality http://incubator.apache.org/projects/flagon.html This has also been posted to the IMPC general@ channel https://s.apache.org/q0k3q
(flagon) David Meikle
Comments:
(flagon) Tim Allison
Comments:
(flagon) Furkan Kamaci
Comments:

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:

Maturity model review and work on associated tasks (in progress).
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 : 625 (August), 314 (September)
There have been 47 Commits since last report: git log --format='%ci' | grep -cE '((2020-0(8|9))|(2020-10))'
15 ie. 32% of those commits were by non-committers: git log --format='%ae %ci' | grep -E '((2020-0(8|9))|(2020-10))' | cut -d ' ' -f 1 | sort | uniq -c | sort -n

How has the project developed since the last report?

Whimsy roster was fixed.
Graduation discussion has started, and community is working towards it.
RC1 for new release is in progress.

On technical side:

New multi event metadata generator.
Metrics for Jobstatus schema.
New workunit tracker for GaaS.
Lineage events for Gobblin streaming mode.
Dataset specific database registration.
Migration of pdsc schemas to pdl.
Better logging and debugging for GobblinHelixTask.
Compiler health awareness for scheduling flows.
New ORC writer.
Multiple bug fixes and performance improvements.

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 (RC1 for new release is in progress, after issues were identified in RC0)

When were the last committers or PPMC members elected?

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

Have your mentors been helpful and responsive?

Yes.

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

Yes, but we have to perform podling name search.

Signed-off-by:

(gobblin) Jean-Baptiste Onofre
Comments:
(gobblin) Olivier Lamy
Comments:
(gobblin) Owen O'Malley
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:

Building community
First release
Roadmap creation

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?

NA

How has the project developed since the last report?

Project bootstrap has been completed.

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

When were the last committers or PPMC members elected?

None yet.

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. JB & Davor have been assisting to complete the bootstrap.

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? NA.

Signed-off-by:

(liminal) Jean-Baptiste Onofre
Comments: Still bootstrapping but moving forward anyway
(liminal) Davor Bonaci
Comments: Bootstrapping finishing soon!

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: Not a lot of activity, I will ping the team.

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 some administrative tasks around the project are still outstanding. These will be addressed before the next podling report. To help address these issue, a PPMC meeting has been proposed. This meeting will be extended to all members of the milagro project to allow an open discussion on 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
[*] 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:

Address licensing and trademark issues for the binary releases in the community.

ONGOING. See update in the next section.

Address release issues. Successfully and smoothly make releases without WIP disclaimer.

ONGOING.

Improve development process and tooling to help reduce the overhead of releases

ONGOING.

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

The community continues to work towards resolving license and branding issues. See summary below.
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
We are adopting Github Discussions https://github.com/apache/mxnet/discussions in favor of Discourse forum for closer connection between users and developers. https://discuss.mxnet.apache.org/ (previously discuss.mxnet.io) will serve as an archive for past user discussions.

Status on license and branding issues

The PPMC continues to make progress in resolving license and branding issues. During the a recent release vote on 1.7.0, with the help from Justin, a few more source distribution and branding issues were found. Here is the status on the issues, tracked in INCUBATOR-253. As of now, the PPMC resolved 15 issues, with 9 still left.

Most of the outstanding issues hinge on one key outstanding question, which is whether the components in MXNet that are produced by CUDA NVCC constitutes Category X code. PPMC member employed by Nvidia helped connect Nvidia's representatives including Michael O'Connor, Director of Deep Learning, who have been supportive in the efforts of clarification. Progress is tracked in LEGAL-516. At the moment, NVIDIA's legal is actively exploring options on resolving this issue. Michael requested extension with MXNet PPMC to not treat the related component as Category-X and delay actions until Oct. board meeting.

Also, we discoveredd that there was confusion around MXNet's status around integration with Intel products. In MXNet, there has never been public distribution of MXNet where MKL was included. There was an initial inquiry around whether MKL builds can be enabled but was rejected, so this never came into practice. Also, to my knowledge Intel has not produced custom MXNet builds with closed-source components.

MXNet 1.7.0 release has completed.

So far, PPMC members from Intel (Tao), Nvidia (Dick), and Amazon (Leonard, Henri, Qing, Sheng) have acted to help resolve the issues.

Status on open issues since last update:

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

Source code releases by the PPMC do not contain Category X code, no issue. Takedown of binary releases by the PPMC on repository.apache.org is on hold, 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 [1]. The scope depends on the resolution of LEGAL-516 [2]. 6. PyPI releases containing Category X licensed code. (pending)

There are no official PyPI releases. Whether the third-party releases are compliant with branding guidelines depend on the resolution of LEGAL-516. 7. Docker releases containing Category X licensed code. (pending)

There are no official Docker releases. Whether the third-party releases are compliant with branding guidelines depend on the resolution of LEGAL-516. 9. Trademark and branding issues with PyPI and Docker releases. (pending)

There are no official PyPI or Docker releases. In addition, as they all contain binary from unmodified MXNet code, whether they are compliant in branding now solely depends on whether they contain Category X licensed code. Refer to item 6, 7. 10. Trademark and brand issues with naming of releases. (pending)

There are no binary releases by the PPMC besides the repository.apache.org releases in item 5. 12. Releases and other nightly builds on https://repo.mxnet.io / https://dist.mxnet.io containing Category X licensed code (resolved)

Neither of the two site contains releases. The binaries are only intended for testing pipelines and are made available only to MXNet developers. As part of the effort to resolve branding concern, public references to these sites are deleted [4]. 14. to 23. Branding and release of 3rd parties containing unreleased code. (pending)

Known pages with issues:

https://docs.nvidia.com/deeplearning/frameworks/mxnet-release-notes/rel_20-03.html (item 14, pending) PPMC reached out to Nvidia. Pending action from Nvidia on branding compliance and replying on whether unreleased code was included. https://sourceforge.net/projects/apache-mxnet.mirror/ (item 15, resolved)

PPMC reached out to SourceForge. SourceForge added (incubating) in name. As 1.7.0 release has completed, we removed release candidate tag from GitHub and the the mirror automatically deleted the it [3]. As such, the original issue is resolved. The PPMC will follow up with SourceForge on the functionality of filtering out non-release tags. AWS Marketplace related links https://aws.amazon.com/marketplace/pp/B07YW8HVLD?qid=1595741035764&sr=0-4&ref_=srh_res_product_title (item 22, pending)

PPMC reached out to Bitnami directly regarding this listing [5]. Bitnami responded and is working on the branding issues. https://aws.amazon.com/marketplace/search/results?x=0&y=0&searchTerms=%22MXNet (item 23, pending)

PPMC reached out to AWS through internal channel to fix branding issue. Will update in the next few days. 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 6, and are actively working on addressing them.

Reference links [1]: https://issues.apache.org/jira/browse/INFRA-20442 [2]: https://issues.apache.org/jira/browse/LEGAL-516 [3]: https://sourceforge.net/projects/apache-mxnet.mirror/ [4]: https://issues.apache.org/jira/browse/LEGAL-515?focusedCommentId=17174133&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17174133 [5]: https://lists.apache.org/thread.html/r1fabd3c081286b06b6e9c9283cb5986450f07d52309db3b74bfe3a24%40%3Cprivate.mxnet.apache.org%3E

How has the community developed since the last report?

The number of GitHub contributors increased to currently 836 (2019-10-08; +7.0% since last report)
Active discussions on user forums
- https://discuss.gluon.ai/ (Chinese, 8.5K registered users (+2.2%) and 22.4K posts(+1.0% since last report))
Active blogs and social media presence
- Medium (https://medium.com/apache-mxnet) w/ 1.94k followers (+7.8%)
- Twitter account (https://twitter.com/ApacheMXNet) w/ 2.7k followers (+2.7%)
Active video channels
- YouTube channel (https://www.youtube.com/apachemxnet) w/ 1.27k subscriber (+7.6% since last report)
- Chinese YouTube channel (https://www.youtube.com/channel/UCjeLwTKPMlDt2segkZzw2ZQ) w/ 6.28k subscribers (+1.4%)
- (in China) bilibili space (https://space.bilibili.com/209599371) w/ 25k subscriber (+4.1% since last report)
Highlights in MXNet ecosystem
- Dive into Deep Learning has 74K 28-day active users, and has attracted 26.5K stars & 322 contributors on GitHub. It has been adopted as a textbook or reference book by 100+ universities from 30 countries, such as Stanford, MIT, UC Berkeley, CMU, UCambridge.
- GluonCV v0.8.0 release (https://github.com/dmlc/gluon-cv/releases/tag/v0.8.0)
- GluonNLP v0.10.0 release (https://github.com/dmlc/gluon-nlp/releases/tag/v0.10.0)
- GluonTS v0.5.2 release (https://github.com/awslabs/gluon-ts/releases/tag/v0.5.2)
- Multi-Model Server v1.1.2 release (https://github.com/awslabs/mxnet-model-server/releases/tag/v1.1.2)
- DeepInsight (https://github.com/deepinsight/insightface)
- Sockeye 2.2.0 release (https://github.com/awslabs/sockeye)

How has the project developed since the last report?

1.7.0 was released: https://github.com/apache/incubator-mxnet/releases/tag/1.7.0 with over 492+ patches of new features, improvements, and fixes.
2.0 project: https://github.com/apache/incubator-mxnet/projects/18
Github statistics of last month:

Sept 7, 2020 – Oct 7, 2020: Excluding merges, 56 authors have pushed 66 commits to master and 118 commits to all branches. On master, 136 files have changed and there have been 4,393 additions and 1,154 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:

2020-08-24

When were the last committers or PPMC members elected?

2020-09-17

Have your mentors been helpful and responsive?

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

Signed-off-by:

(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 196 subscribers, an increase of 16% 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.
Four new committers have joined the team: Adam Feuer, Matias Nitsche,
Johannes Schock, and Sebastian Ene.
We organised the NuttX Online Workshop, a two-day event on August
15th and 16th. We had a bunch of interesting presentations of people
using NuttX around the world. Full videos of the online event have
been posted at https://www.youtube.com/watch?v=t49wq_ovT50 (day 1)
and https://www.youtube.com/watch?v=CIpa3_70PCY (day 2).

How has the project developed since the last report?

We have successfully made our second release under the ASF umbrella,
NuttX-9.1.
We are already working on our third release, NuttX-10.0.
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 per day.
We have listened to the valuable feedback received during our last
two releases and revamped our documentation. This can be found at
https://nuttx.apache.org/docs/latest/.
The nightly build is up and running: https://s.apache.org/wnv2u
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
Community building
Nearing graduation
Other:

Date of last release:

NuttX-9.1 was released on 2020-07-22.

When were the last committers or PPMC members elected?

Last elected PPMC: 2020-01-10

Last committer added: 2020-09-23

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:

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:

Attract more contributors and committers.

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've recently attracted two contributors, Venkat Datta and Sen Na. They are actively working on the new data version and deployment tool (in Golang).

How has the project developed since the last report?

The website has multilingual support now. This is the initial step for the translation afterwards.
Pegasus v2.1.0 is in the voting process. Soon will it be released.

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?

None yet.

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. They offered many useful advice towards the first release of Pegasus.

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:

(pegasus) Kevin A. McGrail
Comments:
(pegasus) Duo zhang
Comments:
(pegasus) Liang Chen
Comments:
(pegasus) Von Gosling
Comments: Good to see the RC3 voting start. and low barrier to attract more contributosr.

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, get more committers

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

Nope

How has the community developed since the last report?

We have gotten some very good activity from a new contributor working on ID generators and email parsing. The community briefly discussed graduating earlier this year, something we should pick up on again.

How has the project developed since the last report?

Work has begun on a next generation suite of tools for the project, as well as significant work being done on the email generators front and unit testing frameworks.

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 as committer on 2016-10-10

Have your mentors been helpful and responsive?

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

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

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

Signed-off-by:

(ponymail) John D. Ament
Comments:
(ponymail) Sharan Foga
Comments:
Good to see some significant activity happening in the last quarter. Community building has always been the challenge so to see a new contributor participating is great.

IPMC/Shepherd notes:

S2Graph

S2Graph is a distributed and scalable OLTP graph database built on Apache HBase to support fast traversal of extremely large graphs.

S2Graph has been incubating since 2015-11-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:

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:

(s2graph) Sergio Fernández
Comments:
(s2graph) Woonsan Ko
Comments:

IPMC/Shepherd notes:

SDAP

SDAP is an integrated data analytic center for Big Science problems.

SDAP has been incubating since 2017-10-22.

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:

(sdap) Jörn Rottmann
Comments:
(sdap) Trevor Grant
Comments:

IPMC/Shepherd notes:

Sedona

Sedona is a big geospatial data processing engine. It provides an easy to use APIs for spatial data scientists to manage, wrangle, and process geospatial data.

Sedona has been incubating since 2020-07-19.

Three most important unfinished issues to address before graduating:

1.The name change in the source code 2.The first release 3.

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?

The community has been active in the past month. We have received emails and Gitter chats from many users. The GitHub repo also received more stars. However, we notice that, since we close the "Issues" function on GitHub, many users seem not to post questions to JIRA and mailing list. Some of them chose to send emails directly to the committers. We would like to figure out a way to guide the users to the right channel.

How has the project developed since the last report?

Since the last report, we have published our new project website under the Apache domain: http://sedona.apache.org/

We have almost finished our first big PR under the new name, Sedona: https://github.com/apache/incubator-sedona/pull/484

The development progress was kind of blocked by this PR. We believe once this PR is accepted, we will move much faster.

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:

N/A

When were the last committers or PPMC members elected?

The last time when we added committers or PPMC is July 2020. It is when we submitted our proposal.

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, all good here.

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 haven't seen any ongoing issues regarding this matter.

Signed-off-by:

(sedona) Felix Cheung
Comments: good to see the progress in the community. I see source is imported
(sedona) Jean-Baptiste Onofré
Comments: Good progress on the bootstrapping and community build.
(sedona) George Percivall
Comments:
(sedona) Von Gosling
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?

None.

How has the community developed since the last report?

Since the last report, we received contributions from a new contributor. We also received many issue reports and questions regarding the usages, bugs, and roadmap of Teaclave. Also, we presented the Teaclave project in recent ApacheCon to the community and received some useful feedback.

How has the project developed since the last report?

The main goal of development since the last report is to resolve logistics towards the first Apache release. This includes license checking, building system improvement, documentation and write-ups. On Oct 6, the Teaclave community passed 0.1.0 release voting. The voting with the incubator community is still ongoing.

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:

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 the first Apache release. We'll switch to community building in the next quarter. Currently, we already have potential candidates for the new PPMC members election.

Have your mentors been helpful and responsive?

Yes. They have been helpful and very responsive for the first public release.

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, attract more contributors and committers 2.Release Apache standard releases regularly 3.Continuously improve system performance and increase system features

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 attracted many real users who have given feedback to the project many bugs, and enthusiastic contributors have made multilingual SDK contributions to the project and successfully applied them in the actual environment; the community periodically releases iteratively to provide stable and easy-to-use new features.

How has the project developed since the last report?

This stage is mainly for the development and implementation of multi-language SDKs: the C/C++ SDK delivery has been completed; at the same time, SDKs for Go, Python, Rust and other languages are under development. In addition to the new features of the multi-language SDKs, the project initiated the development of the tubemq-manager module for cross-cluster control to make the project more usable; for details, 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
Community building
Nearing graduation
Other:

Date of last release:

2020-07-22

When were the last committers or PPMC members elected?

dockerzhang was added as committer on 2020-07-13

Have your mentors been helpful and responsive?

The mentors gave us a lot of help and guidance at the beginning of the project, but as the project deepened, the mentors paid less attention. We hope that the mentors can continue to pay attention to the development of our project and continue to provide 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:
(tubemq) Justin Mclean
Comments:
(tubemq) Sijie Guo
Comments:
(tubemq) Zhijie Shen
Comments:
(tubemq) Jean-Baptiste Onofre
Comments: Effort is on the community building now, it's on the way.

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:

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 three 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 440.

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

How has the project developed since the last report?

A lot of improvements have been made. Including automatic scheduling, better documentations, command line support

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:

2020-07-10

The community is voting on a new release now

When were the last committers or PPMC members elected?

2020-09-28

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: Peak for graduation.
(tvm) Timothy Chen Comments:
(tvm) Furkan Kamaci Comments:
(tvm) Tianqi Chen Comments:
(tvm) Markus Weimer Comments: The project is ready for graduation.

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

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 given multiple presentations at ApacheCON@Home receiving good feedback.

One new committer was added and multiple new contributors were added.

Discussions around new or improved functionality have been started and are progressing in either jira or the mailing list.

How has the project developed since the last report?

A second release was finalised and released. Planning for the next release, based on community use cases, is well on its way for later this year.

A new website was released based on a community contribution using a new build system. The documentation was moved from separate repos to the website.

As part of the latest release the release tool has been improved to remove almost all manual steps.

Some statistics for the report period (2020-07-01 till 2020-09-30)
JIRA: 166 created, 129 resolved
PRs: 69 opened, 108 resolved
13 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:

(yunikorn) Junping Du
Comments:
(yunikorn) Felix Cheung
Comments:
(yunikorn) Jason Lowe
Comments:
(yunikorn) Holden Karau
Comments: I’m excited with the progress.

Page tree

Timeline