December2019

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

This monthly report is in markdown so that it's easier to read. If you are not viewing this in that format, it can be seen here: https://cwiki.apache.org/confluence/display/INCUBATOR/December2019

There are presently 45 podlings incubating. In December, podlings executed XX distinct releases. We added no new IPMC members and no IPMC members retired. There were one IP clearances.

We have one new podling this month StreamPipes; other is under discussion NuttX and two others a possibility. No projects graduated last month. Omin and Tephra exited the Incubator and became subprojects of Phoenix. BatchEE is trying to complete becoming a subproject of Geronimo. At least one podling is heading towards graduation in the next few months. XXX podlings did not submit reports and will be asked to report again next month.

Weex is actively working on its branding issues mentioned last month.

Further work was done on cleaning up the incubator web site, including the cookbook.

Podlings, have continued to use the new disclaimer policy, and this seems to be working well. TVM asked the Incubator to review a release candidate before making a release, and several issues were identified and fixed. PageSpeeed, which joined the Incubator in October 2017, also put its first release up for a vote. A couple of releases needed IPMC prodding to get votes, but most were quickly voted on.

Some statistics were generated, showing how many project enter and leave and how long they stay in incubating to see if any trends were visible. While the overall trend is up, there has been a decrease in podlings joining the Incubator in the last couple of years. There may be a number of reasons for this, including the outside perception of the ASF. It is likely that the carrying capacity of the Incubator had been exceeded in years before this. There have been 315 projects helped by the Incubator, and 77% of them have graduated, most spend 1 1/2 years in incubation. There's been more than a 1000 mentors.

The Incubator release area was cleaned up and old releases from retired and graduated projects removed.

A new branding/trademark question was added the podling report and the podling proposal as a few podling have not realised the importance of this.

A new top level project called Petri, was approved by the board. It's goal is to help external projects go straight to TLP, not using the Incubating process.

Community

New IPMC members:

• None

People who left the IPMC:

• None

New Podlings

• StreamPipes

Podlings that failed to report, expected next month

TODO

Graduations

• None

The board has motions for the following:

• None

Releases

The following releases entered distribution during the month of November:

TODO

IP Clearance

• Weex UI

Legal / Trademarks

• New podling branding/trademark questions

Infrastructure

• No issues

Miscellaneous

Table of Contents Batchee
brpc sha Crail
Daffodil
Druid
Hivemall
IoTDB
Marvin-AI
MesaTEE
Nemo
SAMOA
ShardingSphere
Spot
StreamPipes
Superset
Warble

BatchEE

BatchEE projects aims to provide a JBatch implementation (aka JSR352) and a set of useful extensions for this specification.

BatchEE has been incubating since 2013-10-03.

Three most important unfinished issues to address before graduating:

1. Project needs to finish its migration to Geronimo and exit incubator.

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?

No change

How has the project developed since the last report?

Minor dependency upgrades

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: exiting incubation in favor of a Geronimo subproject

Date of last release:

2017-12-01

When were the last committers or PPMC members elected?

2019-24-01

Have your mentors been helpful and responsive?

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

Signed-off-by:

•  (batchee) Kevin A. McGrail
  Comments: I do not think I am supposed to be a BatchEE mentor.
•  (batchee) Jean-Baptiste Onofré
  Comments: BatchEE is discussing move into Geronimo project, and I think it makes sense.
•  (batchee) Von Gosling
  Comments:

IPMC/Shepherd notes:

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:

1. make more apache release
2. attract more committer
3. 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?

1. Website for brpc has been setup, https://brpc.apache.org
2. Organized brpc workshop on coscon 2019 Shanghai, more than 30 people attended

How has the project developed since the last report?

1. released 0.97 rc1
2. vote for apache release 0.97 rc1 failed ，due to some minor problem
3. working on 0.97rc2 release, will call for vote in one week

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:

still on first apache release

When were the last committers or PPMC members elected?

No new committer , will search for some candidate next.

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 mentor von pointed out some minor problem for 0.97 rc1， and gave some detail instruction through phone calls.

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 that

Signed-off-by:

•  (brpc) Kevin A. McGrail
  Comments: None
•  (brpc) Jean-Baptiste Onofré
  Comments:
•  (brpc) Von Gosling
  Comments:

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:

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:

•  (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:

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:

•  (daffodil) Dave Fisher
  Comments:
•  (daffodil) Christofer Dutz
  Comments:

IPMC/Shepherd notes:

Druid

Druid is a high-performance, column-oriented, distributed data store.

Druid has been incubating since 2018-02-28.

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:

•  (druid) Julian Hyde
  Comments:
•  (druid) P. Taylor Goetz
  Comments:
•  (druid) Jun Rao
  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) Xiangrui Meng
  Comments:
•  (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:

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:

•  (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:

MesaTEE

MesaTEE is the next-gen solution to enable general computing service for security-critical scenarios. It will allow even the most sensitive data to be securely processed to enable offshore businesses without leakage.

MesaTEE has been incubating since 2019-08-19.

Three most important unfinished issues to address before graduating:

1. Finish the initial setup for MesaTEE and its sub-repos.
2. Choose a suitable name for MesaTEE and rename the repos.
3. Make the access control mechanism and RPC framework more scalable and ergonomic.

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

Regarding to the CI system, we do have some problem with migrating the webhooks. MesaTEE definitely requires CI runs on customized hardware. However, the Apache INFRA team is pretty conservative on adopting novel CI systems which support customized hardware and self-hosted agent, such as Github Action, Drone etc. We observed that Apache projects depending on CI running on customized hardware, such as incubator-tvm, experienced difficulty to migrate its webhooks and was challenged several times on the reason of using customized hardware in CI. Besides, we observed that Apache Spark is using Github Action, while we are blocked on it (see INFRA-19381).

The bootstrapping process seems slow due to the above problem. We have a temporary workaround to use our Drone CI system. It leverages a sync bot which automatically sync up incubator-mesatee and a testing fork and triggers the webook of the testing fork. For management, we force the developers to put the link of CI status for each PR in their PR message. It works, but we really desire the integration to new CI and self-hosted CI agents.

For the renaming, we found a new name "Teaclave" which is not used anywhere.

How has the community developed since the last report?

MesaTEE has one more contributor this month, and merged 50+ PRs from 13 contributors.

How has the project developed since the last report?

We implemented the new access control system in MesaPy, and merged into MesaTEE. The new access control system is much more powerful and flexible than traditional user/role/group based access control system, and is memory-safe and trusted with the help of MesaPy and MesaTEE.

We improved the MesaTEE infrastructure to make it k8s-friendly. We refactored parts of the MesaTEE system and are doing on others.

We improved the build system. We deprecated the old-fashioned Makefile, and only kept the cmake system.

We figured out a temporary solution for integrating the Drone CI system and self-hosted agents by syncing up incubator-mesatee and testing fork, and triggering tests on the testing fork.

We are improving the built-in RPC framework to use prost to automatically generate Rust source codes from protobuf's protocol definitions.

We fixed a couple of bugs reported from the open source community.

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?

N/A

Have your mentors been helpful and responsive?

We received instructions on the project renaming process from our mentors. Thanks to every one!

Signed-off-by:

•  (MesaTEE) Felix Cheung Comments:
•  (MesaTEE) Furkan Kamaci Comments:
•  (MesaTEE) Jianyong Dai Comments:
•  (MesaTEE) Luciano Resende Comments:
•  (MesaTEE) Matt Sicker Comments:
•  (MesaTEE) Zhijie Shen 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:

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:

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

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:

•  (samoa) Alan Gates
  Comments:
•  (samoa) Ashutosh Chauhan
  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:

1. Clear Brand issues with other ecosystem projects.
2. Further ASF culture and processes.
3. Make more apache releases.

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

No. Right now, the brand issues are under control, so we think board or IPMC may do not need do any actions for now.

There are still several related project on GitHub org in ShardingSphere ecosystem, before or during project joined the ASF incubator, such as extension modules, extension module examples and acceptance test are not in Apache repo. We have already moved some extension modules into into Apache repo, and plan to transfer all of them soon.

How has the community developed since the last report?

1. Ya Li, Zhiyi Yan have been voted and joined as committer.
2. There are 89 people to contribute codes to the main repo, there are 15 new contributors during last report. We are happy to see the community are growing up.
3. Over 100 companies have confirmed they are using ShardingSphere through issue report, and show at powered-by page[1]. Some companies has already provided patches to feedback the community.
4. Share a topic for Apache way and how to join ShardingSphere community in Apache meetup at Tsinghua University.
5. Finish Podling Maturity Assessment for ShardingSphere[2].
6. Plan to establish a co-meetup with Apache DolphinScheduler(incubator) in Beijing at Dec 8th.

[1]https://shardingsphere.apache.org/community/en/poweredby/ [2]https://cwiki.apache.org/confluence/display/SHARDINGSPHERE/Podling+Maturity+Assessment+for+ShardingSphere

How has the project developed since the last report?

1. Release 4.0.0-RC3 last month, main features are UI and SQL92 supported.
2. Accept donated sharding-scaling project and will merge to trunk before next release.
3. Plan to release 4.0.0 stable version soon.

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-11-22

When were the last committers or PPMC members elected?

2019-11-13

Have your mentors been helpful and responsive?

Mentors are responsive and helpful. Things tend to be on the right way.

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

Yes. We don't find any 3rd parties incorrectly using the podling‘s name and brand for now.

Signed-off-by:

•  (shardingsphere) Craig L Russell Comments:
•  (shardingsphere) Benjamin Hindman Comments:
•  (shardingsphere) Willem Ning Jiang Comments:
•  (shardingsphere) Von Gosling

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:

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:

•  (spot) Uma Maheswara Rao G
  Comments:

IPMC/Shepherd notes:

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:

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:

•  (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

Superset is an enterprise-ready web application for data exploration, data visualization and dashboarding.

Superset has been incubating since 2017-05-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:

•  (superset) Ashutosh Chauhan
  Comments:
•  (superset) Alan Gates
  Comments:
•  (superset) Jakob Homan
  Comments:

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) Daniel Takamori
  Comments:
•  (warble) Chris Lambertus
  Comments:

IPMC/Shepherd notes: