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

FINAL REPORT - NO 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. Especially do not change the formatting of the sign-off area.
  • Keep all lines under 76 characters long.

  • All content under the ### headings should be indented by two spaces. Do not use tabs.

  • Please don't change the text in the headings or add new ones.
  • Include one space after a bullet point or full stop on a numbered list.
  • Use [X] (X and no spaces) to sign off reports.
  • Do not include long URLs and use the apache URL shortener https://s.apache.org.
  • Please note that some lines have two spaces at the end. Do not remove these spaces.

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

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

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


Timeline

Wed June 03Podling reports due by end of day
Sun June 07Shepherd reviews due by end of day
Sun June 07Summary due by end of day
Tues June 09Mentor signoff due by end of day
Wed June 10

Report submitted to Board

Wed June 17Board meeting


Shepherd Assignments

Dave FisherMarvin-AI
Dave FisherStreamPipes
Drew FarrisIoTDB
Drew FarrisSpot
Justin Mcleanbrpc
P. Taylor GoetzDaffodil
P. Taylor GoetzNLPCraft
P. Taylor GoetzSuperset
Timothy ChenCrail
Timothy ChenHivemall
Timothy ChenSAMOA

AGE

Liminal

Nemo

Pinot

S2Graph

SDAP

Warble

Incubator PMC report for June 2020

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

There are presently 43 podlings incubating. In May, podlings executed nine distinct releases. We added one new IPMC members and three retired.

There was one IP clearance in May. There are still two new podlings under discussion or VOTE, and they are HBlock and Pegasus. Two projects, Hudi and Iceberg, graduated last month.

At least one podling is heading towards graduation in this or the next board report, the next one to graduate is likely to be APISIX. This month we were missing reports from Liminal, Spot, Hivemall and Warble. Liminal and Spot asked to report next month. Hivemall and Warble didn't report and will be asked to report next month.

It was found that the MXNet podling's releases and download page were not in line with ASF release and distribution policy. The project had been distributing releases with Category X code and distributing unreleased code. There has been a lengthy discussion both on legal-dicusss and the incubator general list on this. The project has taken some small steps to correct the issues but seems to be hesitant to do so and currently. These issues are still publically unresolved. The Incubator PMC may need to take further action on this.

A couple of established podlings seem to be having trouble following the correct process for adding PPMC members. It's not clear why this is the case as the process is well documented and simple.

Huddi graduated, but there was a small issue with its proposed PMC list that was corrected. Iceberg also graduated, there was some discussion about some issues with its license and notice files in its releases.

A couple of mentors have been added and removed from projects. Most on list traffic was around releases and graduations.

Two podlings SDAP and Spot still need to sort out their roster and private mailing list subscriptions.

Community

New IPMC members:

  • Wangda Tan

People who left the IPMC:

  • Alan Gates
  • Joe Witt
  • Jakob Homan

New Podlings

  • BlueMarlin

Podlings that failed to report, expected next month

  • Liminal
  • Hivemall
  • Spot
  • Warble

Graduations

  • Iceberg
  • Hudi

The board has motions for the following:

  • None

Releases

The following releases entered distribution during the month of May:

  • APISIX 1.3
  • DLab 2.3.0
  • DataSketches 1.3.0
  • ECharts 4.8.0
  • Iceberg 0.8.0
  • IoTDB 0.9.3
  • Nuttx 9.0.0
  • StreamPipes 0.66.0
  • Yunikorn 0.8.0

IP Clearance

  • ShardingSphere ElasticJob

Discussion on releases containing Category X code.

Infrastructure

None.

Miscellaneous

None.

Table of Contents

AGE
brpc
Crail
Daffodil
Dolphin Scheduler
IoTDB
Marvin-AI
Nemo
NLPCraft
Pinot
S2Graph
SAMOA
SDAP
StreamPipes
Superset


AGE

AGE is a multi-model database that enables graph and relational models built on PostgreSQL. This project is a new generation of a multi-model graph database for the modern complex data environment.

AGE has been incubating since 2020-04-29.

Three most important unfinished issues to address before graduating:

  1. Complete infrastructure Setup for Podling.
  2. Make official AGE (Incubating) Release.
  3. Build Community around the AGE project.

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?

This is our first report after AGE project is accepted for Apache Incubator.

How has the project developed since the last report?

This is our first report after AGE project is accepted for Apache Incubator.

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:

We are currently working towards our first Apache based release.

When were the last committers or PPMC members elected?

We are currently working infrastructure setup for migrate repo to Apache.

Have your mentors been helpful and responsive?

Yes, always responsive and helpful.

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

VP, Brand has approved the project name on PODLINGNAMESEARCH-181. PPMC is not managing the podling's brand / trademarks yet.

Signed-off-by:

  •  (age) Kevin Ratnasekera
    Comments:
  •  (age) Von Gosling
    Comments:
  •  (age) Raphael Bircher
    Comments:
  •  (age) Felix Cheung
    Comments: Welcome and looking forward to it!

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. release Apache standard releases 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 organized a meeting to listen to Apache ShardingSphere's chair -zhangliang, he shared his experience on how to develop his project's community and how to graduate. we learned a lot.

How has the project developed since the last report?

we discussed about the release schedule of brpc, maybe a quarter per release will be ok for now. And new PPMC member helei will participate into the work of release.

How would you assess the podling's maturity?

Please feel free to add your own commentary.

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

Date of last release:

2020-01-16

When were the last committers or PPMC members elected?

2019-12-24

Have your mentors been helpful and responsive?

Kevin reminded us for our incubator report, thanks for his reminder.

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: No comments just keep trucking.
  •  (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:

  1. Grow developers community
  2. Grow Crail use base
  3. More steady release cycle

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?

We see increasing traffic on the dev mailing list from Crail users. A recent proposal from Adrian to add elastic scaling got positive feedback from other committers.

How has the project developed since the last report?

Crail went through a phase of limited visible activities on the code base. It is critical the Crail developers community resumes to be more active to keep the project making decent progress. Using Crail as an ephemeral data store for serverless computing emerges as a very suitable use case. Pushing this forward, aiming at inclusion in a next release is of common interest among the committers.

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 have been supportive and responsive.

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

No Answer.

Signed-off-by:

  •  (crail) Julian Hyde
    Comments: The up-tick in dev activity is encouraging.
  •  (crail) Luciano Resende
    Comments:
  •  (crail) Felix Cheung
    Comments: This seems like a good plan to get more interests and grow the community.

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 Owl (formerly Tresys) (main priority)
  2. Work with other Apache projects where Daffodil could provide extra functionality
  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?

  • Pull requests merged from three first-time non-Owl contributors
  • Continued involvement in the mailing lists
    • dev: 78 postings, 5 new subscribers
    • users: 96 postings, 4 new subscribers
  • Owl is actively encouraging other companies with known Daffodil interests to make contributions and increase involvement.
  • Nteligen has two student summer interns starting Daffodil-related projects next week. Anticipating initial on-list activity to begin soon
  • Daffodil has been integrated into Smooks (https://www.smooks.org) by outside developers

How has the project developed since the last report?

  • Released Daffodil 2.6.0
  • 56 commits merged from 7 different contributors
  • Changes include thread-safe API improvements, cleanups based on SonarCloud scans, improved validation of of input XML, newVariableInstance feature, and many important misc bug fixes
  • 59 issues created, 61 issues resolved
  • Initial discussions and planning/ramping up on the proposed code-generation runtime.
  • New proposals and plans in place to improve Daffodil streaming capabilities and memory requirement reduction--main focus for the next release

How would you assess the podling's maturity?

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

Date of last release:

2020-04-24

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: A new PPMC member is being added which increases the diversity of the podling.
  •  (daffodil) Christofer Dutz
    Comments: Would love to see some more content on the mailing list that would implicate what some people are currently working on. From an outside view it is sometimes difficult where movement is currently happening.

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. Polish the document and let user more easily to find their questions.
  3. Guide community discuss more complicated topic via e-mail instead of other channel.

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. 5 committers was voted.
  2. Github code contributors grew from 77 to 86.
  3. Organized 1 on-line communication about Apache Dolphin Scheduler 1.3, about 700 people watch the program and a few of them asked questions.

How has the project developed since the last report?

  1. Support DATAx,sqoop tranfomation and Apache Ambari plug-in installation.
  2. Support condition module on etl process.
  3. Support K8s deployment.

How would you assess the podling's maturity?

Please feel free to add your own commentary.

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

Date of last release:

2020-2-24

When were the last committers or PPMC members elected?

2020-5-28

Have your mentors been helpful and responsive?

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

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

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

Signed-off-by:

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

IPMC/Shepherd notes:


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:

  • More active PPMC/Committers to join votes in the mailing list;
  • Get more user feedback;
  • More technical communications are welcomed to attract more committers joining the project deeply.

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. Suggested by Mentor Christofer, we moved the JIRA notifications to a new mailing list notifications@. After that, there are 609 emails sent by 80 people, divided into 254 topics in these 3 months.

  2. 4 new committers are elected (Dawei Liu, Wangminhao Gou, Yuyuan Kang, and XinWang), who come from 3 different companies/organizations.

  3. A new PPMC is elected (Jincheng Sun).

  4. Many new contributors joining us. For example, Giorgio Zoppi is working for TsFIle/IoTDB C++, Robinet integrated IoTDB with Apache Karaf, Xin Wang and Jincheng integrated IoTDB with Flink etc..

  5. The website is refactored.

  • Now Google Search Engine can index it.
  • The website provides a detailed User Guide and some System Designs both in English and Chinese.
  • Meetup and other talk materials (slides and videos) are shared on the website.
  • More documents to let users joining us (like Code of Conduct, How to be a committer, how to release, how to vote new committers, etc..) are provided on the website or the wiki.
  1. Dave Fisher shepherded us and pointed out some issues, and all of them are fixed.

How has the project developed since the last report?

  • Two versions (v0.9.2 and v0.9.3) are released. They are done by two new Release Managers from the community.

  • The project keeps active, there are 553 commits submitted by 43 authors in these 3 months. (using the gitstats tool to get the result: gitstats -c start_date=2020-03-01 REPO_NAME OUTPUT)

  • IoTDB is integrated with Apache Karaf and Apache Flink.

  • IoTDB supports MQTT protocol.

  • IoTDB's cluster module is almost done. A PR is submitted.

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

When were the last committers or PPMC members elected?

2020-05-18 for the last committer, 2020-05-14 for the last PPMC.

Have your mentors been helpful and responsive?

Yes, helpful and responsive.

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: Thanks for the detailed report. Some of the stats in the report don't mean much to people outside you project. If you do include please explain why or what they illustrate.
  •  (iotdb) Christofer Dutz
    Comments: I am also happy with the progress the project is making.
  •  (iotdb) Willem Ning Jiang
    Comments:
  •  (iotdb) Kevin A. McGrail
    Comments: +1000

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:

  1. Increase activity from current contributors and community.
  2. Finish the new version of Toolbox.
  3. Update old examples

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?

We have expanded "Marvin-lab" at the university and several postgraduate students in the artificial intelligence field are using marvin as their research tool.

How has the project developed since the last report?

  1. Minor bug fix
  2. Refactoring the toolbox to allow the architecture change (Marvin Daemon).
  3. Discussions about architectural changes and a plugin system to make the code less bloated.

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?

Yes.

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

Yes.

Signed-off-by:

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

IPMC/Shepherd notes:

Dave Fisher: There are discussions and it looks like Luciano is providing guidance. If there were another mentor involved it might help the podling.


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?

  • Two GSoC students working on dynamic task sizing and automatic caching
  • Committers continuing to improve code quality

How has the project developed since the last report?

  • Release 0.2 announced on March 6, 2020
  • Implemented a simulator estimating job completion time
  • Improved task, job metric collection methods
  • Implemented task execution time estimators

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-03-06

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:

IPMC/Shepherd notes:


NLPCraft

A Java API for NLU applications

NLPCraft has been incubating since 2020-02-13.

Three most important unfinished issues to address before graduating:

  1. Stable release process for all sub-projects involved.
  2. Community growth.

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

None.

How has the community developed since the last report?

We've got a new committer joined the project:

  • Gleb Ifropc

How has the project developed since the last report?

  • Working through release process for the Java Client sub-project.
  • In release vote for the NLPCraft 0.6.0 that contains number of improvement and new features.
  • Significant updates to the documentation on https://nlpcraft.apache.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-04-29

When were the last committers or PPMC members elected?

2020-05-24

Have your mentors been helpful and responsive?

Core group of mentors is active and involved.

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

No issues.

Signed-off-by:

  •  (nlpcraft) Furkan Kamaci
    Comments:
  •  (nlpcraft) Evans Ye
    Comments:
  •  (nlpcraft) Paul King
    Comments:
  •  (nlpcraft) David Fisher
    Comments: A good start with discussions occurring on the dev list.
  •  (nlpcraft) Konstantin I Boudnik
    Comments:

IPMC/Shepherd notes:


Pinot

Pinot is a distributed columnar storage engine that can ingest data in real- time and serve analytical queries at low latency.

Pinot has been incubating since 2018-10-17.

Three most important unfinished issues to address before graduating:

  1. What's the criteria on the mailing list activity for graduation? We have 350+ users on slack (almost doubled since last report), and have avg ~10 threads per month in the mailing list since Feb.

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

No answer.

How has the community developed since the last report?

  1. The usage of Pinot kept growing. We have 350+ users on slack (almost doubled since last report), and the usage of the mailing list also increased.
  2. Voted Haibo Wang as a new committer.
  3. Number of Pinot contributors crossed 100.
  4. Held the first ever Pinot meetup. LinkedIn, Uber and startups shared their stories with 100+ online attendees.
  5. Added Jim Jagielski as new Mentor.

How has the project developed since the last report?

  1. 200+ commits in the last 3 months.
  2. Lots of new features were added and working towards 1.0 release.

How would you assess the podling's maturity?

Please feel free to add your own commentary.

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

Date of last release:

2020-03-25

When were the last committers or PPMC members elected?

2020-04-10

Have your mentors been helpful and responsive?

No answer.

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

No answer.

Signed-off-by:

  •  (pinot) Kishore Gopalakrishna
    Comments:
  •  (pinot) Jim Jagielski
    Comments:
  •  (pinot) Olivier Lamy
    Comments:
  •  (pinot) Felix Cheung
    Comments:

IPMC/Shepherd notes:

Justin Mclean: 3 of the questions asked were not answered. Please answer them next report.


S2Graph

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

S2Graph has been incubating since 2015-11-29.

Three most important unfinished issues to address before graduating:

  1. Make the third release
  2. Attract more users and contributors
  3. Build the developer community in both size and diversity
  4. Supporting the mordern ecosystem

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?

Not much activities

How has the project developed since the last report?

  1. One new contributor joined in community by submitting the PR(S2GRAPH-255)
  2. Create issue to support Scala ecosystem (S2GRAPH-258)
  3. Several bug fixes PR
  • S2GRAPH-257: SafeUpdateCache#withCache method incorrect behavior
  • S2GRAPH-259: column_metas miss default_value
  • S2GRAPH-253: adding more api docs; rename deleteLabel to deleteLabelReally
  • S2GRAPH-256: Spelling mistakes
  • S2GRAPH-255: Enable incremental processing of s2jobs

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-08-26

When were the last committers or PPMC members elected?

2019-02-05

Have your mentors been helpful and responsive?

Our mentor is very helpful and responsive.

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

No Answer.

Signed-off-by:

  •  (s2graph) Sergio Fernández
    Comments:
  •  (s2graph) Woonsan Ko
    Comments: Thanks to Daewon Jung for drafting report and asking for reviews this time.

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:

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

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-04-23

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: Good to see an initial release.

IPMC/Shepherd notes:


SDAP

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

SDAP has been incubating since 2017-10-22.

Three most important unfinished issues to address before graduating:

  1. Make official SDAP (Incubating) Release
  2. Improve committer participation
  3. Improve/create user guide documentation

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

Subscription of PPMC members to the @private mailing list should be resolved. All PPMC members should now be subscribed to @private. If this is not accurate, please advise.

How has the community developed since the last report?

New committers have been added.

How has the project developed since the last report?

  1. Integrated SDAP analytics with Esri ArcGIS front end.
  2. Added new temporal variance (2D map) analytic algorithm.
  3. Further improvements in Kubernetes-based deployment procedures.

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?

Two new committers were elected in April 2020.

Have your mentors been helpful and responsive?

Mentors have been helpful.

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

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

Signed-off-by:

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

IPMC/Shepherd notes:

Justin Mclean: Can I ask why the PPMC is not managing the podlings brand and trademarks? Also there still 1/3 of of your PPMC members not signed up to your private list. Also please include a date of your last release in your next report.


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. Multiple Apache releases
  2. Grow the developer community
  3. Attract more users

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?

In the past three months, the community developed rather well: New users appeared on the mailing lists, and we were able to elect the first external committers. The mailing list activity has increased and many discussions on development-related tasks were done on the developer mailing list. Overall, we feel that the community is more and more following the Apache way.

Some specific community development activities include:

  • We updated the wiki with developer information, getting started guides and step-by-step manuals for release management (see https://s.apache.org/ocz7t)
  • Updated website to include better overview of existing pipeline elements
  • Intensified work with manufacturing company to use StreamPipes for IIoT analytics
  • We published a blog post on how to run StreamPipes on Kubernetes, we now plan to publish blog posts at regular intervals
  • Added "communication channels & strategy" page in the wiki and gathered potential communication channels in close exchange with our mentors planning to intensify community growth
  • Took part in webinar series about open source for small and medium sized companies (video on YouTube, currently only in German)
  • Number of Twitter followers increased (last report: 103, currently: 128)
  • Number of Github stars increased (last report: 109, currently: 144)

How has the project developed since the last report?

  • We successfully released our first official Apache release (version 0.66.0) including several improvements (see release notes https://s.apache.org/2grsk), to name the most prominent changes: completely new dashboard and notification design in UI, more pipeline elements and improved connectors
  • Many new pipeline elements have been added by newly elected committers
  • Both documentation and website were improved in order to increase the adoption of Apache StreamPipes and grow the user base

In the next month, we plan to add better support for edge computing and improve the UI.

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-05-19 (Version 0.66.0)

When were the last committers or PPMC members elected?

Four new committers were elected and joined the team since the last report aiding in contributing/maturing the project.

  • Florian Micklich (2020-03-26)
  • Daniel Ebi (2020-05-12)
  • Felix John (2020-05-12)
  • Grainier Perera (2020-05-22)

Have your mentors been helpful and responsive?

Our mentors provided very good support in preparing and performing our first Apache release. We would like to thank them for very helpful advice, also for some licensing questions we had on the list.

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

Yes, we started to prepare a wiki page to develop a communication strategy, which also includes brand management. The next step is to create a new logo that will be voted on by the community. We are constantly monitoring the usage of the Apache StreamPipes name in external websites and posts.

Signed-off-by:

  •  (streampipes) Christofer Dutz
    Comments: Looking forward to them starting to use the normal incubation disclaimer as they are on a pretty good path with their release.
  •  (streampipes) Jean-Baptiste Onofré
    Comments:
  •  (streampipes) Julian Feinauer
    Comments: I think the project really adopts the Apache Way and I am happy to see that more and more Comitters are added to the lineup!
  •  (streampipes) Justin Mclean
    Comments: Congratulations on the new committers.
  •  (streampipes) Kenneth Knowles
    Comments:

IPMC/Shepherd notes:

Dave Fisher: Podling looks to be very much on track!


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:

  1. Keep producing a steady stream of approved Apache releases
  2. Produce a project charter
  3. 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?

  1. Superset Virtual Meetup was a success!
  2. Organic growth of our Github Contributors:
  • Stars (27,885 → 28,870)
  • Forks (5,636 → 5,909)
  • Watchers (1,241 → 1,255)
  1. Added 349 commits (Feb 24, 2020 to June 1, 2020)
  2. Grew Superset slack users to (1,309 → 1,665)

How has the project developed since the last report?

  1. Released 0.36.0 on 2020-04-02

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-04-02

When were the last committers or PPMC members elected?

  • 2020-05-21 Bogdan Kyryliuk
  • 2020-05-27 Tai Dupree
  • 2020-05-27 Aaron Sudjian
  • 2020-05-29 Jesse Yang

Have your mentors been helpful and responsive?

Open issues:

  • Asked Jim Jagielski for help with a Tai's problematic JIRA account. (He has access to someone's preexisting account. Issue remains open but work is proceeding on it)
  • There was an open question about if/how steps for onboarding committers might be streamlined and/or automated. Any advice on that front is welcomed, as the process is seemingly error prone. Sorry for any confusing missteps as we continue to learn to navigate this.
  • Asked about Bogdan Kyryliuk's process, no answer
  • Generally experencing glitches when onboarding committers & PMCs

Other interactions of note:

  • We have a new mentor! Welcome to the team, Jim Jagielski!
  • Mentor Justin Mclean helped us with font licensing.
  • Mentor Justin Mclean provided clarity on report formatting. (Hope this one works!)
  • Jakob is stepping down. Thanks for everything!

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

All is well. Name has been approved.

Signed-off-by:

  •  (superset) Alan Gates
    Comments: An account has been created now for Bogdan, I'm not sure what caused the delay.
  •  (superset) Jim Jagielski
    Comments:

IPMC/Shepherd notes:

Justin Mclean: Just a note that I'm not a mentor of this project. If you need help with on-boarding new PPMC members or committers just ask your mentors but it can be easily done with Whimsey.

  • No labels