Page tree
Skip to end of metadata
Go to start of metadata

FINAL DO NOT EDIT

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

Report submitted to Board

Wed March 18Board meeting



Shepherd Assignments

Dave FisherIoTDB
Dave FisherTubeMQ
Drew FarrisSAMOA
Drew FarrisStreamPipes
Justin McleanNemo
P. Taylor GoetzDaffodil
P. Taylor GoetzShardingSphere
P. Taylor Goetzbrpc
Timothy ChenNuttX
Timothy ChenPageSpeed
Timothy ChenYuniKorn

Crail

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.

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/March2020

There are presently 45 podlings incubating. In February, podlings executed 9 distinct releases. We added no new IPMC members, but two will be added shortly, and 2 IPMC members retired, a further 72 were removed by a board resolution.

There was four requested IP clearance, some issue around previous IP clearances have been resolved. We have one new podling this month NLPCraft; another three are under discussion AgensGraph, HBlock and Rainbow. No projects graduated last month. Taverna has retired from the Incubator and Tamaya is discussing retirement. At least one podling is heading towards graduation in the next few months. PageSpeed which didn't report last month reported this month. Hivemall did not report and have indicated they will report next month.

Most podlings have sorted out their private mailing lists. Three podlings MXNet, SDAP and Spot are still working on it.

The board proposal to remove IPMC was passed, and they have been removed, everything went smoothly. When they were removed a few projects found themselves with fewer mentors, and a couple of people have put to hand up to help mentor them.

A discussion about the announce email format turned into a discussion about release pages. Several podling that have made releases were discovered not to have download pages, they have been asked to fix this. A script found several other podlings with incorrect download links on download pages and those podling are working on fixing those.

Community

New IPMC members:

  • None

People who left the IPMC:

  • 72 IPMC members in board proposal
  • Jacopo Cappellato
  • Naomi Slater

New Podlings

  • NLPCraft

Podlings that failed to report, expected next month

  • Hivemall

Graduations

  • None

The board has motions for the following:

  • None

Releases

The following releases entered distribution during the month of February:

  • APISIX 1.1
  • APISIX dashboard 1.0
  • BRPC 0.9.7
  • Dolphin Scheduler 1.2.1
  • Livy 0.7.0
  • MXNet 1.6.0
  • Milagro Crypto-C v2.0.1
  • PageSpeed 1.14.36.1
  • Ratis 0.5.0

IP Clearance

  • Pulsar - DotPulsar
  • OpenWhisk - wskdebug
  • Atomos Codebase
  • Maven Wrapper
  • N/A

Infrastructure

  • Changes to /dist link has an impact on podling download pages.

Miscellaneous

  • We also had a privacy request for the removal of personal information that was passed on to the privacy committee.

Table of Contents
brpc
Crail
Daffodil
DolphinScheduler 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:

  1. release apache standard release regularly
  2. attract more contributors and committers
  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?

We added three new committers, 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?

  1. vote for release 0.97 rc2 failed due to some license issue
  2. 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
  •  Working towards first release
  •  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?

Not ready for the branding issue, will check it next time.

Signed-off-by:

  •  (brpc) Kevin A. McGrail
    Comments: Nicely done this quarter.
  •  (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:

Justin Mclean: It seems your release has not been placed in the offical release area. Please do so.


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: Glad to hear about the new release. Sorry to hear of Patrick's departure.
  •  (crail) Luciano Resende
    Comments: We should make sure all development, including prototypes, happen at Apache repositories. New repos can be created when necessary.
  •  (crail) Felix Cheung
    Comments: Steady progress, would be great to get more community growth

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:

  1. Increase community growth and participation beyond Tresys (main priority)
  2. Work with other Apache projects where Daffodil could provide extra functionality (NiFi and Drill are current priorities)
  3. 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?

Signed-off-by:

  •  (daffodil) Dave Fisher
    Comments: Community growth is the main issue blocking graduation. Other than that the podling is in good shape following the Apache Way.
  •  (daffodil) Christofer Dutz
    Comments:

IPMC/Shepherd notes:


DolphinScheduler

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

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

Three most important unfinished issues to address before graduating:

  1. Develop more committers and contributors.
  2. Make development document more easily to read.
  3. make E-mail as an official discussion tool in our communities.

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?

  1. New committers is active in answer Jira issue and other contributions.
  2. More articles were written by users and contributors initiatively.

How has the project developed since the last report?

  1. Apache 1.2.1 without WIP has been released.
  2. Restructure the Master/Worker model for easily to expand.
  3. Refine CI/CD process for more contributors easily to join.

How would you assess the podling's maturity?

Please feel free to add your own commentary.

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

Date of last release:

2020-2-24

When were the last committers or PPMC members elected?

2020-1-24

Have your mentors been helpful and responsive?

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

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

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

Signed-off-by:

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

IPMC/Shepherd notes:


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:

  1. Get more user feedbacks to the community
  2. More committers should know how to release a version. And more PPMC should join to vote.
  3. 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?

  1. 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.
  2. 6 new committers are added into the community.
  3. 6 GSoC2020 ideas are published.

How has the project developed since the last report?

  1. 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.
  2. 124 Pull requests are merged
  3. 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?

Very helpful.

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

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: By far most email traffic generated by jira (hard to follow especially when trying to keep up to date while commuting)
  •  (iotdb) Willem Ning Jiang
    Comments:
  •  (iotdb) Kevin A. McGrail
    Comments: Discussing what's needed to graduate and the checklist.

IPMC/Shepherd notes:

Dave Fisher: There are a few small issues I noticed. I fixed one and sent an email to the dev@ list with a list.


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:

  1. Increase activity from current contributors and community.
  2. Build compatibility with all the mainstream storages for artifact persistence.
  3. Finish the new version of Toolbox.

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

  • A lot of conversations about the project in last few months happened in private channel, because of some contributing groups known to each other. We have already warned everyone about the importance of discussing on open lists.

How has the community developed since the last report?

  • in the last few months we have focused on development of university communities, we set up "Marvin-lab" at the university we have the partnership, and several postgraduate students in the artificial intelligence field started using marvin as their main tool for their research.

How has the project developed since the last report?

  • Minor bug fixes.
  • Compatibility with MS Azure Blob for artifact persistence.
  • New contents and structure improvements in project documentation.
  • AutoML module and integration with Apache Spark MLib in construction.

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-07-18

When were the last committers or PPMC members elected?

  • Wei Chen added as new PPMC member (2019-06-07)

Have your mentors been helpful and responsive?

  • At least two of the mentors are sometimes active.

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

  • yes

Signed-off-by:

  •  (marvin-ai) Luciano Resende
    Comments: Technical discussions need to happen on the dev list. Please ensure contributors submit their individual contributions.
  •  (marvin-ai) William Colen
    Comments:

IPMC/Shepherd notes:

Justin Mclean: There has been no traffic to your mailing list for the last 3 -4 months. Why is this the case? And why was it not mentioned in this report?


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:

  1. Grow the community (committers, contributors, users)
  2. 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?

Our mentors have been helpful and responsive.

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

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: Great work on the release!

IPMC/Shepherd notes:

Justin Mclean: It seems your release was placed in the release area before the vote was complete. This can only be done after the vote has finished.


NuttX

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

NuttX has been incubating since 2019-12-09.

Three most important unfinished issues to address before graduating:

  1. Clear any potential infringing use of the NuttX trademark
  2. Determine the form and location of NuttX releases
  3. Make the first release under Apache

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?

The dev list contains 128 subscribers and is the home of all development discussions and users questions.

  • Github's PRs and Issues also have their own discussions.
  • Some new names are contributing to the project through Github.

How has the project developed since the last report?

  • Contributions are flowing regularly as PRs in GitHub and as patches in the dev list.
  • A bunch of improvements, bug fixes and new architectures were collaborated.
  • The nightly build is up and running: https://s.apache.org/wnv2u
    This will improve our review process and push us forward towards making our first 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:

Still working towards making the first Apache release.

When were the last committers or PPMC members elected?

Last elected PPMC: 2020-01-10

Have your mentors been helpful and responsive?

Mentors are helpful and responsive.

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

Some concerns and actions regarding podling's brand were noted in the
past reports, however, trademarks issues will be dealt with when
graduation draws near.

Signed-off-by:

  •  (nuttx) Junping Du
    Comments:
  •  (nuttx) Justin Mclean
    Comments: I suggest you look at trademark issues before nearing graduation.
  •  (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:

  1. Produce a release
  2. 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:

Justin Mclean: It seems your release has not been placed in the offical release area. Please do so.


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:

  1. Revitalize the project by resuming development
  2. 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: With the election of the new committer it looks like the project is slowly making some progress. I'm happy to see it start moving forward.

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. Doing podling name search now, the JIRA ticket here[1]
  2. Clear issues which indicate by incubator status page[2]
  3. Finished discussion about graduation and start to vote to TLP[3]

[1] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-178

[2] https://incubator.apache.org/clutch/shardingsphere.html

[3] https://lists.apache.org/thread.html/r2272e5fb70044e07f8ff21e282d84ab88a 30eac6709a9d0981f6b2c1%40%3Cdev.shardingsphere.apache.org%3E

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

There is a user wall page[4] to show all user lists. The URL of page may generate confusion with apache powered by policy. We have already change the page url to [5].

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

[5] 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 115 people to contribute codes to the main repo, there are 26 new contributors during last report. We are happy to see the community are growing up. Prepare for graduation, finished discussion mail list is [6]. The main resolved issues are:

  1. Major contributors sign ICLA
  2. Confirm PMC and committer list
  3. IP Clearance for OpenSharding GitHub repo[7]
  4. Remove author information in java code
  5. Update incubator status site[8]

[6] https://lists.apache.org/thread.html/r885653f36d76c9d842b52f0ba2576dd962 efd2e9a24acc03515c9e24%40%3Cdev.shardingsphere.apache.org%3E

[7] https://github.com/OpenSharding

[8] https://incubator.apache.org/clutch/shardingsphere.html

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. Releasing and voting version 4.0.1 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

When were the last committers or PPMC members elected?

2020-01-08

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:

  •  (shardingsphere) Craig L Russell
    Comments: Graduation vote is underway on the dev list. I believe the project is ready to graduate.
  •  (shardingsphere) Willem Ning Jiang
    Comments: It's good to see the project is ready to graduate.
  •  (shardingsphere) Von Gosling
    Comments: Glad to see all necessary graducation affairs have been resolved.

IPMC/Shepherd notes:

Dave Fisher: The VP, Brand approved your name search on February 20.


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:

  1. Make a first Apache release
  2. Grow the community
  3. 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: Perhaps it would help assigning streampipes.org domain to apache and have auto-redirect?
  •  (streampipes) Jean-Baptiste Onofré
    Comments: The highest priority is a first release and it's planned in few weeks.
  •  (streampipes) Julian Feinauer
    Comments:
  •  (streampipes) Justin Mclean
    Comments:
  •  (streampipes) Kenneth Knowles
    Comments:

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:

  • Revive community activity (Discussion in mailing lists, increase frequency of commits)
  • Create a new roadmap and release plan that will improve adoption.
  • Make it easier to contribute to the project (e.g. documentation, framework).

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?

The number of active committers has increased over the past quarter, and we also have several new potential community members looking to become committers. We will work with our mentors to go through the process to onboard them.

Much of the activity from the community has been focused on stabilizing the codebase and fixing known issues in the documentation and Spot website. This will greatly benefit new users and reduce confusion when standing up the Spot different modules.

How has the project developed since the last report?

Several projects have been proposed, discussed, and completed during the past quarter. We're also working to close the remaining open PRs as soon once the community finishes its review. Additionally there were some Podling Website check failures in the Whimsy report that we began to look into and resolve. These should be mostly resolved by the next Podling report update.

We've also begun discussions on the second version of the Open Data Model (ODM v2). There were several problems seen in the implementation with ODM v1 that need to be resolved before substantial adoption of Apache Spot can take place. Its our goal to come to a decision on the design of ODM v2 this next quarter. Once a data model redesign is agreed upon this will serve as a catalyst to modernizing other Spot modules so everything is properly integrated.

How would you assess the podling's maturity?

Please feel free to add your own commentary.

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

Date of last release:

  • 2017-09-08

When were the last committers or PPMC members elected?

  • 2019-09-02 - Mark Schoeni

Have your mentors been helpful and responsive?

Yes our mentors have been helpful. We will be engaging them more soon for guidance on on-boarding new committers, as well as a few other items related to the Whimsy and Clutch reports and also updating the Apache Spot Podling website as this is missing a number of updates.

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

Yes

Signed-off-by:

  •  (spot) Uma Maheswara Rao G
    Comments: There is some improvement on mailing lists recently. IMO, Still needs improvement in community development.

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?

Alan Gates and Jakob Homan approved the prior Podling report

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

No answer

Signed-off-by:

  •  (superset) Alan Gates
    Comments:
  •  (superset) Jakob Homan
    Comments:
  •  (superset) 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.

How would you assess the podling's maturity?

Please feel free to add your own commentary.

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

Date of last release:

None

When were the last committers or PPMC members elected?

2020-02-20

Have your mentors been helpful and responsive?

Yes

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

Yes.

Signed-off-by:

  •  (tubemq) Junping Du
    Comments: I saw there are new committers get voted, good move!
  •  (tubemq) Justin Mclean
    Comments: Showing better progress than before.
  •  (tubemq) Sijie Guo
    Comments:
  •  (tubemq) Zhijie Shen
    Comments:
  •  (tubemq) Jean-Baptiste Onofre
    Comments: Podling is still in bootstrap phase but moving forward.

IPMC/Shepherd notes:


YuniKorn

Apache YuniKorn (incubating) 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.
  • Launch the first Apache release.
  • Improve documentation and provide a roadmap.

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

  • No critical issues at this point in time

How has the community developed since the last report?

This is the first report for YuniKorn. Migration and setup is not fully finialised.

How has the project developed since the last report?

  • source code repository moved to apache
  • JIRA setup and configured
  • community design for a new feature started

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?

No new committers or PPMC members have been added since starting incubation.

Have your mentors been helpful and responsive?

Yes, helped setup project page (Holden) and questions (Junping)

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

No issues that we are aware of

Signed-off-by:

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

Comments: Some projects choose to prepare a new release soon after becoming Apache incubator project. See if YuniKorn would like to follow.

IPMC/Shepherd notes:

  • No labels