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. 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 December 02 Podling reports due by end of day
Sun December 06Shepherd reviews due by end of day
Sun December 06Summary due by end of day
Tue December 08Mentor signoff due by end of day
Wed December 09

Report submitted to Board

Wed December 16Board meeting


Shepherd Assignments

Dave FisherSamoa
Dave FisherToree
Drew FarrisSpot
Drew Farrisbrpc
Justin McleanNemo
P. Taylor GoetzCrail
P. Taylor GoetzDaffodil
P. Taylor GoetzLiminal
Timothy ChenAnnotator
Timothy ChenHivemall
Timothy ChenLivy

Incubator PMC report for December 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 41 podlings incubating. In November, podlings executed 10 distinct releases. We added one new IPMC member, and none retired. There were two IP clearances in November. We have no new projects, although a couple are under discussion, including Wayang. Superset and TVM graduated last month and Warble was retired.

This month we were missing reports from Annotator, BRPC and Liminal. Annotator has reached out to the IPMC, added a new mentor and will report next month.

BlueMarlin report mentions an unexpected release, and they still seem to be having trouble operating as an Apache project. One mentor has given up on them due to lack of communication.

Liminal has failed to report several times, but there is ongoing activity in the project. It also seems they are making unapproved releases which the IPMC will follow up on.

There was still no response from S2Graph, and unless there any objections they will be retired shortly.

Weex, who was considering retirement, tried to make a release and brought the release to the IPMC without the needed 3 +1 votes. They were asked to find the needed PPMC votes. It may be that they do not have enough of an active PPMC to do this.

SAMOA currently has no mentors, and little or no activity and the IPMC is considering retiring the project.

TubeMQ is considering renaming itself to something else.

NuttX made a release that was voted on the IPMC private list as it contained some critical security fixes.

There was no visible progress made on MXNet issues, and this will be discussed at the board meeting. An active mentor retired, and a new mentor was added to help them.

Most discussions on the mailing list were around releases and graduations. There were graduation discussions around ECharts, Flagon, DataSketches and Goblin.

Community

New IPMC members:

  • Lars George

People who left the IPMC:

  • none

New Podlings

  • none

Podlings that failed to report, expected next month

  • Annotator
  • BRPC
  • Liminal

Graduations

  • Superset
  • TVM

The board has motions for the following:

  • DataSketches
  • ECharts

Releases

The following releases entered distribution during the month of November:

  • Daffodil 3.0.0
  • DolphinScheduler 1.3.3
  • NLPCraft 0.7.1
  • NLPCraft 0.7.2
  • NuttX 10.0.0
  • Pegasus 2.1.0
  • Pinot 0.6.0
  • Superset 0.38.0
  • TubeMQ 0.7.0
  • Tuweni 1.3.0

IP Clearance

  • Apache APISIX ingress controller
  • Apache Arrow Julia library
  • MXNet issues still unresolved.

Infrastructure

  • N/A

Miscellaneous

  • N/A

Table of Contents

AGE
BlueMarlin
Crail
Daffodil
Hivemall
Hop
Livy
Marvin-AI
Nemo
SAMOA
Spot
StreamPipes
Toree


AGE

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

AGE has been incubating since 2020-04-29.

Three most important unfinished issues to address before graduating:

  1. First release
  2. Grow developers community
  3. Schedule release cycles

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 do have two new contributors that are also interested to become Committers of AGE project.

How has the project developed since the last report?

The project has been actively developed and new development has been pushed actively. The website has been deployed and it is available.

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

When were the last committers or PPMC members elected?

None for now, but we do have two new people contributing to the project and willing to become committers.

Have your mentors been helpful and responsive?

Yes, they have been helpful and very responsive.

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

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

Signed-off-by:

  •  (age) Kevin Ratnasekera
    Comments:
  •  (age) Von Gosling
    Comments:
  •  (age) Raphael Bircher
    Comments:
  •  (age) Felix Cheung
    Comments:

IPMC/Shepherd notes:


BlueMarlin

BlueMarlin will develop a web service to add intelligence functionality to a plain ad system.

BlueMarlin has been incubating since 2020-06-09.

Three most important unfinished issues to address before graduating:

  1. DL-based performance forecasting
  2. DL-based spend recommendation
  3. DL-based Inventory allocation

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?

The following features were added to predictor_dl_model:

  1. We added new features of user residency and user IPL (IP location).

  2. We added pipeline and product tags to config file. Config file has placeholders to resolve the names of intermediate tables instead of having user to fill them up.

  3. We pushed model-stats into Hive instead of Elasticsearch. This makes the pipeline to create one set of coherent tables that are associates with a pipeline run instead of having the artifacts into different types of data storage.

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:

Plan to have a release in Jan, 2021

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:

  •  (bluemarlin) Craig Russell
    Comments: The podling has not yet done anything on list. The SGA was filed late October 2020 so they are just starting. They do not have a repository or a web page. They claim in this report to have done a release but there is no evidence of this.
  •  (bluemarlin) Jean-Baptiste Onofré
    Comments:
  •  (bluemarlin) Von Gosling
    Comments:
  •  (bluemarlin) Junping Du
    Comments:
  •  (bluemarlin) Uma Maheswara Rao G
    Comments:

IPMC/Shepherd notes:

Dave Fisher - I resigned from mentoring this podling. They refuse to discuss activity on the mailing list. They do not communicate. They claim to make a release. This report is the first time we've heard of it.

Justin Mclean - The issues to be resolved before graduation need to be ones related to the community and how Apache operates not functionality. I'm concerned about the release and comments by other mentors. There are also section in this report that are unanswered. What can be done to get this project back on track?

Dave Fisher - There is no back. This podling has never been on track.


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. Convincing use cases
  3. Steady release cycles

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

No reply.

How has the community developed since the last report?

We got one new contributors. We are looking forward to see him applying as a committer.

How has the project developed since the last report?

A new contributor was working in the field of adding elasticity.

Elastic scaling is a needed pre-requisite to use Apache Crail as an efficient ephemeral data store for serverless frameworks. We expect pull requests for code integration in the coming weeks. With added elasticity, a new release would be due.

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?

Yes, our mentors have been supportive and responsive.

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

There are no known cases of a 3rd party podling name/brand incorrect use.

Podling name search has been completed - see https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-138

Signed-off-by:

  •  (crail) Julian Hyde
    Comments: Activity is very low. Crail are trying to find ways to stimulate activity by bringing in a new contributor.
  •  (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:

  1. Increase community growth and participation beyond Owl (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 contributors (one non-Owl)
  • Continued involvement in mailing lists
  • dev: 167 emails sent by 22 people, divided into 43 topics, 49 subscribers (+17)
  • users: 14 emails sent by 5 people, divided into 9 topics, 59 subscribers (+16)
  • Owl is continuing to encourage other companies with known Daffodil interests to make public contributions and increase involvement
  • Smooks (https://www.smooks.org) 2.0.0-M2 has been released with Daffodil integration

How has the project developed since the last report?

  • Released Daffodil 3.0.0
  • 44 commits merged from 10 different contributors
  • 55 issues created, 54 issues resolved
  • Changes include SAX support, ability to stream data larger than available memory, reduced memory usage, improved diagnostics, and numerous bug fixes
  • Upcoming changes include support for parser/unparser code generation and improved validation with new APIs and plugability

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

When were the last committers or PPMC members elected?

  • 2020-06-15 - John Interrante (PPMC)
  • 2019-11-26 - Olabusayo Kilo (Committer)
  • 2019-06-20 - Brandon Sloane (PPMC)

Have your mentors been helpful and responsive?

  • Yes, recently helped to find a third mentor which should help the release process.

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

Signed-off-by:

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

  1. Community growth (committers and users)
  2. One or more Apache Releases as an Incubator project

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

PPMCs are considering exit approaches including retiring.

How has the community developed since the last report?

No particular topic.

How has the project developed since the last report?

No 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:

2019-12-19

When were the last committers or PPMC members elected?

Elected Jerome Banks as a committer on April 2, 2018.

Have your mentors been helpful and responsive?

Yes

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

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

Signed-off-by:

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

IPMC/Shepherd notes:


Hop

Hop is short for the Hop Orchestration Platform. Written completely in Java it aims to provide a wide range of data orchestration tools, including a visual development environment, servers, metadata analysis, auditing services and so on. As a platform, Hop also wants to be a reusable library so that it can be easily reused by other software.

Hop has been incubating since 2020-09-24.

Three most important unfinished issues to address before graduating:

  1. identify and resolve the last remaining incompatibly licensed dependencies (if any)
  2. create a first release
  3. grow the community

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

No known significant issues at this moment

How has the community developed since the last report?

  • 2 additional committers, committers are increasingly active
  • 9 new registered chat members (99 -> 108)
  • 21 subscribers to dev, 11 to user mailing list
  • significant follower growth on social media, mainly on LinkedIn (+46) and Twitter (+15)

How has the project developed since the last report?

  • After JIRA and the website, code and documentation repositories have been migrated.
  • For the code migration, a copyright header related fix was required, which was delivered and accepted.
  • All existing builds have been recreated and updated to run on ASF Jenkins
  • new functionality has been created (new transform and action plugins, UI updates and more)
  • significant documentation updates
  • discussion of and preparation for a first release (0.50) has started

Full details are available in the November monthly roundup: https://hop.apache.org/blog/2020/12/roundup-2020-12/

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:

No releases so far

When were the last committers or PPMC members elected?

2020-11-18

Have your mentors been helpful and responsive?

We have mainly been working on infrastructure and or software items over the last month. Mentor input will become more important now we've started working towards a first release. Julian Hyde regularly checks in and provides valuable input.

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

There are no known brand and naming issues. The PPMC only uses "Apache Hop (Incubating)" as the official project name and has explicitly called "Project Hop" deprecated as of the moment of acceptance in the Incubator.

Signed-off-by:

  •  (hop) Tom Barber
    Comments:
  •  (hop) Julian Hyde
    Comments: Plenty of work on features, good cooperation on dev list, appointing the first committers since incubation, and pushing hard for the first release. Hop is doing great.
  •  (hop) Maximilian Michels
    Comments:
  •  (hop) Francois Papon
    Comments: Community is growing well (new committer, dev list, mattermost channel) and a great work is done on the source code for the first release. The Hop team is very active.
  •  (hop) Kevin Ratnasekera
    Comments: Significant progress has been made through out past time period, with related to first release and community growth.

IPMC/Shepherd notes:


Livy

Livy is web service that exposes a REST interface for managing long running Apache Spark contexts in your cluster. With Livy, new applications can be built on top of Apache Spark that require fine grained interaction with many Spark contexts.

Livy has been incubating since 2017-06-05.

Three most important unfinished issues to address before graduating:

  1. Start preparing towards graduation

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

Apache Livy is a stable project that is used widely in conjuction with Apache Spark. It seems to have met its project goals and there is not much active development going on as a result. 2020 may definitely not be the best year for community activity and Livy certainly seems to have taken a hit on this aspect. Seeking guidance from the IPMC/Board on what could be next steps for the project. Its not very active but at the same time its not a defunct/unused project.

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:

2020-01-07

When were the last committers or PPMC members elected?

2019-01-22

Have your mentors been helpful and responsive?

No reply

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

No Reply

Signed-off-by:

  •  (livy) Bikas Saha
    Comments:
  •  (livy) Luciano Resende
    Comments:
  •  (livy) Jean-Baptiste Onofre
    Comments:

IPMC/Shepherd notes:

Justin Mclean: As long as there is an active PPMC with at last 3 PPMC members providing oversight the project should be fine. Is anything else needed to graduate the project? Have you looked at the ASF maturity model? I am concerned that users questions are going unanswered on the dev 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. Finish the new version of Toolbox.
  3. Release a new version.

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.

We had an online meeting to discuss architectural approaches, we also found out about new members joining the community, some of them are utilizing the platform in their companies.

How has the project developed since the last report?

  1. Minor bug fix;
  2. Last adjustments on the new toolbox version;
  3. Preliminary version of AutoML wrapper (Marvin AutoML);
  4. Organization of the structure of a documentation for the new toolbox;
  5. Architectural discussions on dev mailing list and online meeting about integrating TFX and Apache Beam.

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:


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. Address a few remaining items in the Apache Project Maturity model
  2. Grow the community
  3. Create another release

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

None.

How has the community developed since the last report?

  • Attracted new contributions
  • Actively involved in addressing the items in the Apache Project Maturity model
  • Applied the project for a global-scale streaming system

How has the project developed since the last report?

  • Release 0.3 in progress
  • Improved streaming support in Nemo
  • Added combiners in streaming
  • Added in-process data communication optimization
  • Made Nemo run on geo-distributed datacenters
  • Dynamic task scheduling 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:

2020-03-06 (Release 0.2)

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: There is another release in flight as this report is prepared.

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: 4 messages

How has the project developed since the last report?

We are working in an implementation of adaptive random forests.

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?

There are no mentors since June.

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:

IPMC/Shepherd notes:

Justin Mclean: I suggest you reach out the the IPMC general list and ask for more mentors. Given the low activity it may be hard to attract one. Can the project point to me to where this development on adaptive random forests is? There doesn't seem to be any commits for almost a year.


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:

  1. Increase community activity in mailing list and commits
  2. Make the product more approachable for new contributors and users
  3. Develop a roadmap that focuses on delivering one use case effectively

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

Not at this time.

How has the community developed since the last report?

We're continuing to work on a roadmap with the community that will allow more contributors to focus and work on different levels of the project (i.e. data modeling and schema design, use-cases, ingestion, ml, ui, dev ops, docs, etc).

How has the project developed since the last report?

We've started regular weekly discussions around several topics, including configuration management, authentication, and authorization models within Spot so that we have a better backbone for adding more features and can also backport existing functionality to a stronger foundation. These discussions were delayed this quarter due to COVID and getting schedules aligned relative to other workloads so we don't have any proposals documented yet, but that is our next step.

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?

2020-08-24 - We removed PPMC members who were not subscribed to the private mailing list and who did not respond to an email asking them to subscribe

Have your mentors been helpful and responsive?

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

Our mentors have been helpful in onboarding new contributors, and in getting us the Whimsy and Clutch reports and updating the website so we more completely conform to ASF policy requirements for podlings.

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

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

We have no knowledge of any issues with the brand or trademark.

Signed-off-by:

  •  (spot) Uma Maheswara Rao G
    Comments: This community needs few more mentors.

IPMC/Shepherd notes:

Justin Mclean: Where are these weekly discussion taking place? Is what is discussed in them brought back to the mailing list?


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. Grow the community
  2. Attract more users
  3. Complete maturity assessment

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?

  • First of all, we are quite happy with the current community-driven development and all major things are being discussed on the mailing lists
  • We gave several talks at meetups and events during the past months
    • Two talks at ApacheCon @Home
    • SF Big Analytics Meetups
    • StreamPipesWebinar Brazil
    • several industry-focused talks
    • All the talks are available on YouTube
  • A large german computer magazine published an article about StreamPipes (https://www.linux-magazin.de/ausgaben/2020/12/apache-streampipes/)
  • We had several remote training sessions to show users how to use StreamPipes
  • There is a continuous flow of messages on the mailing list and more people are contributing to discussions and give feedback
  • Several new people showed up on the mailing list asking for support or reporting problems
  • We updated the installation guide to ease the first steps with StreamPipes
  • Number of Twitter followers increased (last report: 148, currently: 156)
  • Number of Github stars increased (last report: 163, currently: 186)

How has the project developed since the last report?

  • We released version 0.67.0, our second release in the ASF
  • Currently, most contributors are working on issues around stability bug fixing
  • The community currently discusses the future roadmap and there are some new features community members are working on
    • mqtt support
    • pipeline monitoring
    • python wrapper
    • externally exposed REST APIs for pipelines and pipeline elements
  • We are currently discussing the integration of incubator-streampipes-extensions into the core project to ease future release processes

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-10-28

When were the last committers or PPMC members elected?

2020-05-22, but we expect several new committers and PPMC members to being elected soon

Have your mentors been helpful and responsive?

Yes, mentors are helpful and responsive. We get quick feedback in case there are any questions. Thanks to all mentors and IPMC members who took the time to vote on our last release.

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

Yes, we are actively managing the brand. New logo is still an open issue that is being discussed in the community. The project name has been approved.

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:


Toree

Toree provides applications with a mechanism to interactively and remotely access Apache Spark.

Toree has been incubating since 2015-12-02.

Three most important unfinished issues to address before graduating:

In my opinion, I believe Toree is one of those small but useful projects that, except for being very active, would be ready to graduate. Having said that, where there is an important issue or for voting new members and releases the PPMC show up and participate (see example of last committer/release thread).

The project will likely start graduation process on the next couple months.

  1. Increase active contributors

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?

Similar pattern with a few Q&A on both Gitter and mailing list. We also saw increased flow of questions related to Spark 3.0.

How has the project developed since the last report?

We attempted a new release, but while waiting for vote process to complete the Incubator release process changed and we are working on adapting to the new rules.

How would you assess the podling's maturity?

Please feel free to add your own commentary.

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

Date of last release:

2020-07-31

When were the last committers or PPMC members elected?

Kevin Bates was added to the PPMC on 2019-08-14

Have your mentors been helpful and responsive?

There was nothing requiring mentor intervention on the last quarter.

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

No Trademark issues

Signed-off-by:

  •  (toree) Luciano Resende
    Comments:
  •  (toree) Julien Le Dem
    Comments:
  •  (toree) Ryan Blue
    Comments:

IPMC/Shepherd notes:

  • No labels