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.
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 a 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 apache URL shortener https://s.apache.org.

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 March 04	Podling reports due by end of day
Sun March 08	Shepherd reviews due by end of day
Sun March 08	Summary due by end of day
Tues March 10	Mentor signoff due by end of day
Wed March 11	Report submitted to Board
Wed March 18	Board meeting

Shepherd Assignments

Dave Fisher	IoTDB
Dave Fisher	TubeMQ
Drew Farris	SAMOA
Drew Farris	StreamPipes
Justin Mclean	Nemo
P. Taylor Goetz	Daffodil
P. Taylor Goetz	ShardingSphere
P. Taylor Goetz	brpc
Timothy Chen	NuttX
Timothy Chen	PageSpeed
Timothy Chen	YuniKorn
	Crail
	Hivemall
	Marvin-AI
	Spot
	Superset
	Warble

Incubator PMC report for March 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 February:

Credits

Table of Contents
brpc
Crail
Daffodil
Hivemall
IoTDB
Marvin-AI
Nemo
NuttX
PageSpeed
SAMOA
ShardingSphere
Spot
StreamPipes
Superset
TubeMQ
Warble
YuniKorn

brpc

brpc is an industrial-grade RPC framework for building reliable and high- performance services.

brpc has been incubating since 2018-11-13.

Three most important unfinished issues to address before graduating:

release apache standard release reguarly
attract more contributors and committers
clean branding issue

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

No big issues

How has the community developed since the last report?

we added three new commmitters, they are helei, cai Daojin, mu gaidong. they are all from iqiyi company , using brpc for their business, and contributing a lot to brpc projects, including bugfix/feature/code review/evangelism.

How has the project developed since the last report?

vote for release 0.97 rc2 failed due to some license issue
vote for release 0.97 rc3 is still ongoing, with WIP disclaimer, hopefully will be done next week

How would you assess the podling's maturity?

Please feel free to add your own commentary.

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

Date of last release:

2020-01-16

When were the last committers or PPMC members elected?

2019-12-24

Have your mentors been helpful and responsive?

von helped a lot with the release discussion, and JB/kevin also help to vote for new committers.

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? Not ready for the branding issue, will check it next time.

Signed-off-by:

(brpc) Kevin A. McGrail
Comments:
(brpc) Jean-Baptiste Onofré
Comments:
(brpc) Von Gosling
Comments: As we get closer to the first apache release, the community needs to further strengthen the building and increase developer activity.

IPMC/Shepherd notes:

Crail

Crail is a storage platform for sharing performance critical data in distributed data processing jobs at very high speed.

Crail has been incubating since 2017-11-01.

Three most important unfinished issues to address before graduating:

1. Community building: Increase on number of active contributors and users.
2. Establish new use cases in the community

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

With Patrick currently unavailable for the project, we lost our main contributor. We need help from new active contributors to drive things forward.

How has the community developed since the last report?

Interest from the community in native C++ client for Crail integration with ML frameworks such as TensorFlow. New users from academia.

How has the project developed since the last report?

• Release 1.2 is out.
• Working towards releasing new elasticity extensions of Crail.

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-01-14

When were the last committers or PPMC members elected?

December 4th, 2018

Have your mentors been helpful and responsive?

Our mentors are very helpful.

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

Yes, others are using the podling's name correctly (e.g. Samsung Research, Stanford University)

Signed-off-by:

(crail) Julian Hyde
Comments:
(crail) Luciano Resende
Comments:
(crail) Felix Cheung
Comments:

IPMC/Shepherd notes:

Daffodil

Apache Daffodil is an implementation of the Data Format Description Language (DFDL) used to convert between fixed format data and XML/JSON.

Daffodil has been incubating since 2017-08-27.

Three most important unfinished issues to address before graduating:

Increase community growth and participation beyond Tresys (main priority)
Work with other Apache projects where Daffodil could provide extra functionality (NiFi and Drill are current priorities)
Continue frequent release schedule

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?

Continued mailing lists discussions, with a handful of new faces asking questions on the users@ mailing list, hopefully some of these can be converted to developers
Struggling to get active involvement outside of Tresys. We are actively working with known users of Daffodil to encourage contributions, including virtual meetings and making time to help spin up with the codebase
An outside developer has shown interest in contributing to the code-generation runtime. Hoping to spin up that user shortly and start getting contributions.

How has the project developed since the last report?

Released Daffodil 2.5.0
29 commits merged from 5 different contributors
44 issues created, 29 issues resolved, focus was primarily on large features rather than bug burn down.
Significant improvement to DFDL schema compilation time
Incorporated SonarCloud static analysis to help verify code quality
Lots of refactoring to improve code quality and type safety
Created a container to streamline a repeatable release process
Looking like next release will be sometime in March

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-01-12

When were the last committers or PPMC members elected?

2019-11-26 - Olabusayo Kilo (Committer)
2019-06-20 - Brandon Sloane (PPMC)

Have your mentors been helpful and responsive?

Yes

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

No known cases of a 3rd party incorrectly using the Daffodil name/brand.
Podling name search has been completed and approved by Brand Management Committee: https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-147

Signed-off-by:

(daffodil) Dave Fisher
Comments:
(daffodil) Christofer Dutz
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:

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:

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

IPMC/Shepherd notes:

IoTDB

IoTDB is a data store for managing large amounts of time series data such as timestamped data from IoT sensors in industrial applications.

IoTDB has been incubating since 2018-11-18.

Three most important unfinished issues to address before graduating:

Get more user feedbacks to the community
More committers should know how to release a version. And more PPMC should join to vote.
make sure the private mailing list is consistent with the PPMC list.

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?

According to the statistics of https://lists.apache.org/, there are 1079 emails sent by 87 people, divided into 564 topics in these 3 months.
6 new committers are added into the community.
6 GSoC2020 ideas are published.

How has the project developed since the last report?

IoTDB v0.9.1, which contains 11 bug-fix, was released on 11 Jan 2020. It is finished by the 4th RM in the community.
124 Pull requests are merged
Now IoTDB docker images and Python client lib are available on dockerHub and pipy.org.

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-01-11 (v0.9.1)

When were the last committers or PPMC members elected?

2020-02-01

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.

Very helpful.

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

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

Required Name Search is done. A google search didn’t show any major branding issues that the PPMC needs to deal with.

Signed-off-by:

(iotdb) Justin Mclean
Comments:
(iotdb) Christofer Dutz
Comments:
(iotdb) Willem Ning Jiang
Comments:
(iotdb) Kevin A. McGrail
Comments:

IPMC/Shepherd notes:

Marvin-AI

Marvin-AI is an open-source artificial intelligence (AI) platform that helps data scientists, prototype and productionalize complex solutions with a scalable, low-latency, language-agnostic, and standardized architecture while simplifies the process of exploration and modeling.

Marvin-AI has been incubating since 2018-08-21.

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:

(marvin-ai) Luciano Resende
Comments:
(marvin-ai) William Colen
Comments:

IPMC/Shepherd notes:

Nemo

Nemo is a data processing system to flexibly control the runtime behaviors of a job to adapt to varying deployment characteristics.

Nemo has been incubating since 2018-02-04.

Three most important unfinished issues to address before graduating:

Grow the community (committers, contributors, users)
Create releases

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

None

How has the community developed since the last report?

New committer added: Haeyoon Cho
Committers actively involved in improving code quality
Committers started to work on interesing features such as dynamic task scheduling and offheap computation

How has the project developed since the last report?

Release 0.2 PPMC vote passed on March 3, 2020
Developing a job simulator that estimates stage execution time
Started to work on dynamic task scheduling (DTS) that changes task sizes to choose parallelism better
Developing offheap computation that executes UDF functions with offheap data natively
Supported Java 1.11
Fixed code smells throughout the code base

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:

Release 0.1 on Dec. 31, 2018

When were the last committers or PPMC members elected?

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

Our mentors have been 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 PPMC manages the podling's brand / trademarks.

Signed-off-by:

(nemo) Hyunsik Choi
Comments:
(nemo) Byung-Gon Chun
Comments:
(nemo) Jean-Baptiste Onofre
Comments:
(nemo) Markus Weimer
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:

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:

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

IPMC/Shepherd notes:

PageSpeed

PageSpeed represents a series of open source technologies to help make the web faster by rewriting web pages to reduce latency and bandwidth.

PageSpeed has been incubating since 2017-09-30.

Three most important unfinished issues to address before graduating:

Produce a release
Increase the number of active developers

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

After a series of release candidates, a first incubator release was approved by both the developer group and the IPMC. However, while doing the final release preparation a blocking issue was observed: the scripts that package the product would still point to dl.google.com as a repo source. This is being addressed.

How has the community developed since the last report?

Mailing lists and git issues are active. The number of active developers is steady.

How has the project developed since the last report?

A first WIP incubator release made it through the voting rounds, but needs some small changes to address a blocking issue observed during finalization. Those have been made, and another vote is in progress.

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?

May 27 2019 (Longinos Ferrando, elected as both committer and PMC member)

Have your mentors been helpful and responsive?

Yes

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

As far as we know the brand is respected by third parties It's not known if the VP, brand has explicitly approved, so that is something we need to make sure about and resolve.

Signed-off-by:

(pagespeed) Jukka Zitting
Comments:
(pagespeed) Leif Hedstrom
Comments:
(pagespeed) Nick Kew
Comments:

IPMC/Shepherd notes:

SAMOA

SAMOA provides a collection of distributed streaming algorithms for the most common data mining and machine learning tasks such as classification, clustering, and regression, as well as programming abstractions to develop new algorithms that run on top of distributed stream processing engines (DSPEs). It features a pluggable architecture that allows it to run on several DSPEs such as Apache Storm, Apache S4, and Apache Samza.

SAMOA has been incubating since 2014-12-15.

Three most important unfinished issues to address before graduating:

Revitalize the project by resuming development
Enlarge the user base and contributing 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?

Mailing list activity:
@dev: 31 messages

How has the project developed since the last report?

With the help of the new commiter Corey Sterling, we prepared a new release of Apache SAMOA, that is already being discussed and voted (RC3).

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:

2016-09-30

When were the last committers or PPMC members elected?

August 2019

Have your mentors been helpful and responsive?

Yes, the mentors have been helpful and responsive.

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

Yes. There are no 3rd parties incorrectly using the podling‘s name and brand for now.

Signed-off-by:

(samoa) Alan Gates
Comments:

IPMC/Shepherd notes:

ShardingSphere

ShardingSphere is an ecosystem of transparent distributed database middleware, focusing on data sharding, distributed transaction and database orchestration.

ShardingSphere has been incubating since 2018-11-10.

Three most important unfinished issues to address before graduating:

Doing podling name search now, the JIRA ticket here[1]
Clear issues which indicate by incubator status page[2]

[1] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-178 [2] https://incubator.apache.org/clutch/shardingsphere.html

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

There is a user wall page[3] to show all user lists. The URL of page may generate confusion with apache powered by policy. Can we keep this page and change the url to [4]?

[3] https://shardingsphere.apache.org/community/en/poweredby/ [4] https://shardingsphere.apache.org/community/en/users/

How has the community developed since the last report?

Wen Ouyang, ZongLei Dong, Xiaofeng Jiang have been voted and joined as committer. There are 110 people to contribute codes to the main repo, there are 21 new contributors during last report. We are happy to see the community are growing up. Prepare for graduation, discussion mail list is [5]. The main resolved issues are:

Major contributors sign ICLA
Confirm PMC and committer list
IP Clearance for OpenSharding GitHub repo[6]
Remove author information in java code

[5] https://lists.apache.org/thread.html/r885653f36d76c9d842b52f0ba2576dd962efd2e9a24acc03515c9e24%40%3Cdev.shardingsphere.apache.org%3E [6] https://github.com/OpenSharding

How has the project developed since the last report?

Release 4.0.0 last month, it is the stable version of 4.0.0-RC1, 4.0.0-RC2 and 4.0.0-RC3. Preparing to release 4.0.1 version now.

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-01-13

StreamPipes

StreamPipes is a self-service (Industrial) IoT toolbox to enable non- technical users to connect, analyze and explore (Industrial) IoT data streams.

StreamPipes has been incubating since 2019-11-11.

Three most important unfinished issues to address before graduating:

Make a first Apache release
Grow the community
Diversify PPMC members & committers

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

There are no issues right now.

How has the community developed since the last report?

We gave a talk about StreamPipes at Bosch Connected World 2020 (~100 participants in the talk)
We gave several IIoT demos involving Apache StreamPipes at FZI Open House (~300 participants)
There was a lot more communication on the mailing list concerning the discussion on upcoming features and improvements
An external company mentioned their usage of StreamPipes in one of their upcoming products
Some new contributions/pull requests from external contributors
The number of Twitter followers has increased (currently at 113)
The number of Github stars has increased (currently at 117)

How has the project developed since the last report?

The community is currently working on the final steps concerned with the preparation of the first ASF release
We performed an upgrade of the UI components to Angular 9, which improves performance
We implemented a new live dashboard
We refactored the code base and removed/rewrote components which relied on non-ASF conformant licenses, e.g., kafka-rest
LICENSE and NOTICE files have been created for the incubator-streampipes project

The first release is planned within the next few weeks.

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?

No new committers have been added so far.

Have your mentors been helpful and responsive?

Our mentors are very responsive and provide good feedback.

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

Currently, no issues are known related to brand misuse, but there are still some open issues concerning the transition to the ASF infrastructure (e.g., shutting down the old streampipes organization on Github to avoid confusion)
We started to contact external websites who provided links to the old streampipes.org website and asked them (or created pull requests) to change this to the new streampipes.apache.org domain.

Signed-off-by:

(streampipes) Christofer Dutz
Comments:
(streampipes) Jean-Baptiste Onofré
Comments:
(streampipes) Julian Feinauer
Comments:
(streampipes) Justin Mclean
Comments:
(streampipes) Kenneth Knowles
Comments:

IPMC/Shepherd notes:

Superset

Apache Superset (incubating) is a modern, enterprise-ready business intelligence web application.

Three most important unfinished issues to address before graduating:

Keep producing a steady stream of approved Apache releases
Produce a project charter
Seek a positive recommendation from the IPMC

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?

Suitable name search was approved by Apache legal!
The first Superset Meetup took place, hosted by Preset, on 2020-02-11, with talks by Maxime Beauchemin, Beto Dealmeida, and Evan Rusackas
Organic growth of our Github Contributors: -- Stars (27,034 → 27,885) -- Forks (5,400 → 5636) -- Watchers (1245 → 1,241)
Added 225 commits (Dec 1, 2019 to Feb 24, 2020)
Grew Superset slack users to (1,023→ 1,309)

How has the project developed since the last report?

Release 0.35.1
Release 0.35.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:

2020-01-06

When were the last committers or PPMC members elected?

2020-02-24 - Evan Rusackas
2020-01-30 - Ville Brofeldt
2019-12-06 - Craig Rueda

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.

Alan Gates and Jakob Homan approved the prior Podling report

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:

Alan Gates
Jakob Homan
Ashutosh Chauhan

Comments:

IPMC/Shepherd notes:

TubeMQ

TubeMQ is a distributed messaging queue (MQ) system.

TubeMQ has been incubating since 2019-11-03.

Three most important unfinished issues to address before graduating:

1.Launch the first Apache release. 2.Make development document more easily to read. 3.Grow the community to involve more contributors and increase the diversity.

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?

At this stage, no community activities were initiated, but we internally initiated a vote for the project committer and selected the first committer of the project. I believe this will promote the subsequent development of the project community.

How has the project developed since the last report?

The project is nearing completion of the migration to the Apache incubator: at this stage, we have completed the change of the project's package name, the standardization of file's LICENSE, and the launch of the project home page, but the documentation and project home page content relatively lacking, this part needs to be improved in the next stage.