DRAFT DRAFT DRAFT

NOTE that the content for this month report is in markdown format- please do not remove any formatting characters when adding your reports.

It also best to:

Do not change existing formatting. 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 May 05	Podling reports due by end of day
Sun May 09	Shepherd reviews due by end of day
Sun May 09	Summary due by end of day
Tue May 11	Mentor signoff due by end of day
Wed May 12	Report submitted to Board
Wed May 19	Board meeting

Shepherd Assignments

Dave Fisher	Sedona
Dave Fisher	Toree
Drew Farris	SDAP
Drew Farris	Tuweni
Justin Mclean	NLPCraft
P. Taylor Goetz	Livy
P. Taylor Goetz	Spot
P. Taylor Goetz	Training
Timothy Chen	Hivemall
Timothy Chen	PageSpeed
Timothy Chen	Pinot
	Doris
	Heron
	Weex

Incubator PMC report for May 2021

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

TODO add narrative

Podlings that failed to report, expected next month

Graduations

list podling here

The board has motions for the following:

Your podling here?

Releases

The following releases entered distribution during the month of April:

Annotator

Annotator provides annotation enabling code for browsers, servers, and humans.

Annotator has been incubating since 2016-08-30.

Three most important unfinished issues to address before graduating:

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

How has the community developed since the last report?

How has the project developed since the last report?

How would you assess the podling's maturity?

Please feel free to add your own commentary.

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

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:

(annotator) Nick Kew
Comments:
(annotator) Tommaso Teofili
Comments:
(annotator) Benjamin Young
Comments:

Doris

Doris is a MPP-based interactive SQL data warehousing for reporting and analysis.

Doris has been incubating since 2018-07-18.

Three most important unfinished issues to address before graduating:

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

How has the community developed since the last report?

How has the project developed since the last report?

How would you assess the podling's maturity?

Please feel free to add your own commentary.

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

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:

(doris) Willem Ning Jiang
Comments:
(doris) Shao Feng Shi
Comments:
(doris) Ming Wen
Comments:

Heron

A real-time, distributed, fault-tolerant stream processing engine.

Heron has been incubating since 2017-06-23.

Three most important unfinished issues to address before graduating:

Building the community
Making releases
Make Heron easier to adopt

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

N/A

How has the community developed since the last report?

The community has remained consistent. New presentations in the monthly meetups. Increasing the community should be one of the major goals for the project.

How has the project developed since the last report?

Bug/issue fixes
Feature and documentation improvements
Tried to Build the first convenience docker image

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:

When were the last committers or PPMC members elected?

The last two new committers voted in: Oliver Bristow (July 22, 2020) Windham Wong (July 3, 2020)

Have your mentors been helpful and responsive?

Mentors have been helpful for the new release and answering questions.

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

Yes

Signed-off-by:

(heron) Jake Farrell
Comments:
(heron) Julien Le Dem
Comments:
(heron) P. Taylor Goetz
Comments:
(heron) Dave Fisher
Comments:
(heron) Ming Wen
Comments:
(heron) Kevin Ratnasekera
Comments:

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:

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

How has the community developed since the last report?

How has the project developed since the last report?

How would you assess the podling's maturity?

Please feel free to add your own commentary.

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

Date of last release:

XXXX-XX-XX

When were the last committers or PPMC members elected?

Have your mentors been helpful and responsive?

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

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

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

Signed-off-by:

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

IPMC/Shepherd notes:

Justin Mclean: Can you please remove your old releases from the list release area.

Milagro

Milagro is core security infrastructure and crypto libraries for decentralized networks and distributed systems.

Milagro has been incubating since 2015-12-21.

Three most important unfinished issues to address before graduating:

Continue to build relevant and useful crypto libraries and applications for decentralized networks in order to grow the ecosystem of users and contributors to the project.
Continue to improve compliance with the Apache Way. In particular to update the Milagro website and other project sites (e.g. Whimsy) in accordance with Apache policies.
Further releases to increase the scope of the Milagro project, extend the capability of existing releases and to demonstrate improved compliance with the Apache Way.

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

No significant issues, however some administrative tasks around the project are still outstanding largely due to the pandemic but are now being addressed. In particular, a PPMC meeting to discuss the project roadmap needs to be arranged, old releases need to be deleted, confirmation that the project's Whimsy, Clutch, SVN, Confluence & Committers pages are all current, and the code signing keys needs countersigning.

has been proposed for 3rd February to discuss outstanding issue with a follow on meeting for the entire Milagro community to discuss the project's roadmap. Old releases also need to be removed.

How has the community developed since the last report?

No change.

How has the project developed since the last report?

Works is progressing preparing the MPC library for its first official 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:

2020-02-10

When were the last committers or PPMC members elected?

February 20202

Have your mentors been helpful and responsive?

No issues

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

No known issues, but further investigation is still required by the Milagro community.

Signed-off-by:

(Milagro) Nick Kew
Comments:
(Milagro) Jean-Frederic Clere
Comments:

IPMC/Shepherd notes:

Justin Mclean: Can you please remove your old releases from the list release area.

NLPCraft

Apache NLPCraft is an open source library for adding natural language Interface to modern applications. Apache NLPCraft has been incubating since 2020-02-13.

Three most important unfinished issues to address before graduating:

Community growth & outreach.
Get to the point with multiple release managers.
Presenting the project at ApacheCon/ApacheAsia 2021.

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

Project have several new contributors that we are expecting to formally join the project/ASF in the future. These are individuals outside of the original NLPCraft community. We are also getting number of offline contributions when it comes to ideas, documentation and website. We are working on promoting these contributions and inviting these individuals to be more active. We need, however, to get much better at the general project outreach via meetups, conferences, etc. Some of the conversations happen on Gitter.

Project has 8 forks on the Github.

How has the community developed since the last report?

Project produced 2 releases. Both releases were an interim, bug fix releases. So far, they were produced by the same release manager (Aaron Radzinski). The community is working on the major release 0.7.5 right now that should go GA in the April 2021 with significant changes and improvements (all of which are reflected in JIRA tickets for 0.7.5 version). At this point, the community does not have a formalized roadmap with many internal discussions happening on Slack channels. We are generally expecting to formalize the long-term roadmap towards 1.0.0 release with hopefully a larger community around the project.

Community is actively working on 0.7.5 release that should be sent for a vote in the coming days.

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:

NLPCraft 0.7.4 released on Jan 31, 2021.

When were the last committers or PPMC members elected?

Aug, 2020 - Gleb Zernov (ifropc), committer.

Have your mentors been helpful and responsive?

We have had some problems with getting attention from mentors - however this has been largely resolved as of now. We've also identified some of the communication inefficiencies that would help us to engage mentors better going forward.

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

Yes, no issues to report.

Signed-off-by:

(nlpcraft) Roman Shaposhnik
Comments:
(nlpcraft) Furkan Kamaci
Comments:
(nlpcraft) Evans Ye
Comments:
(nlpcraft) Paul King
Comments:
(nlpcraft) Konstantin I Boudnik
Comments:
(nlpcraft) Dave Fisher
Comments:

IPMC/Shepherd notes:

Justin Mclean: Can you please remove your old releases from the list release area.

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:

Grow the number of active developers
Enhance the release process: switch to github tagged release to simplify.

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

While there is a healthy user base, the number of active developers remains persistently low. This seems to be a hard to address challenge.

How has the community developed since the last report?

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

How has the project developed since the last report?

Minor activity, updating deps on the 2.0-alpha.

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:

We'll be blogging about the 2.0 Envoy PoC, hopefully that will get some developer interest as we pivot into the service mesh world

Date of last release:

The week of May 11th, 2020

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.

Signed-off-by:

(pagespeed) Jukka Zitting
Comments:
(pagespeed) Leif Hedstrom
Comments:
(pagespeed) Nick Kew
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:

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

How has the community developed since the last report?

How has the project developed since the last report?

How would you assess the podling's maturity?

Please feel free to add your own commentary.

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

Date of last release:

XXXX-XX-XX

When were the last committers or PPMC members elected?

Have your mentors been helpful and responsive?

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

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

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

Signed-off-by:

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

IPMC/Shepherd notes:

Justin Mclean: Can you please remove your old releases from the list release area.

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:

Make official SDAP (Incubating) Release
Improve committer participation
Improve/create user guide documentation

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 Committers and PPMC members elected

How has the project developed since the last report?

Completed:

Migrated SDAP to Python 3.

New efforts and features:

Working on Elasticsearch integration.
Adding Apache Parquet support for in situ data
Integration with AWS Athena
Enhancements to support multispectral data

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 March 2021.

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.

Have not heard from Jörn in a while.

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

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

Not aware of any issues

Signed-off-by:

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

IPMC/Shepherd notes:

Sedona

Sedona is a big geospatial data processing engine. It provides an easy to use APIs for spatial data scientists to manage, wrangle, and process geospatial data.

Sedona has been incubating since 2020-07-19.

Three most important unfinished issues to address before graduating:

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

How has the community developed since the last report?

How has the project developed since the last report?

How would you assess the podling's maturity?

Please feel free to add your own commentary.

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

Date of last release:

XXXX-XX-XX

When were the last committers or PPMC members elected?

Have your mentors been helpful and responsive?

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

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

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

Signed-off-by:

(sedona) Felix Cheung
Comments:
(sedona) Jean-Baptiste Onofré
Comments:
(sedona) George Percivall
Comments:
(sedona) Von Gosling
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?

Not at this time

How has the community developed since the last report?

We're continuing to solidify a short term and long term 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). These discussions have been delayed this quarter due to COVID and getting schedules aligned relative to other workloads.

How has the project developed since the last report?

The master branch of Apache Spot was largely developed on commercial
but freely available Hadoop software (i.e. Cloudera, Hortonworks) that now have been either End of Life’d (or will be in 2022) in favor of the newer Cloudera Data Platform (CDP), or have been put behind a paywall to get updates. The cloud provider landscape has also changed drastically in the last few years and it's time that we start looking at better support for Quickstart options in each major cloud providers so we can further develop the project for the community with wider platform support, and give committers better options for creating development environments to more efficiently contribute to the project.

The following topics are planned for the next set of discussions with the community to determine what we focus on for the next several quarters:

Add more native support on cloud infrastructure and software (i.e. AWS, Azure, GCP)
- In the short-term we can focus on AWS EMR on standing up Spot and fixing any issues related to getting the software installed and working.
- In the long term we will want to support several cloud providers and on-premise options depending on the interest of the community.
Add an infrastructure module to Spot to automate creating clusters in each providers we plan to support.
- Initially we can focus on Cloudformation support with AWS EMR.
- Our goal will be to generalize further in the long term with Terraform across each provider.
Investigate and explore alternative replacement for Spot UI (i.e. Apache Supersets)
- In the short-term Apache Supersets may give us a basic authentication and visualization layer into the data landed and processed by Spot.
- In the long-term we will need to develop a more comprehensive security and use-case roadmap for the UI and determine if it makes sense to develop something from scratch.

The next step will be to create Jira Epic’s and tasks for these items so we can start to distribute the work across the community.

How would you assess the podling's maturity?

Please feel free to add your own commentary.

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

Date of last release:

2017-09-08

When were the last committers or PPMC members elected?

2019-09-02

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.

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?

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?

Yes.

Signed-off-by:

(spot) Uma Maheswara Rao G
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:

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

How has the community developed since the last report?

How has the project developed since the last report?

How would you assess the podling's maturity?

Please feel free to add your own commentary.

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

Date of last release:

XXXX-XX-XX

When were the last committers or PPMC members elected?

Have your mentors been helpful and responsive?

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

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

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

Signed-off-by:

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

IPMC/Shepherd notes:

Training

The Training project aims to develop resources which can be used for training purposes in various media formats, languages and for various Apache and non-Apache target projects.

Training has been incubating since 2019-02-21.

Three most important unfinished issues to address before graduating:

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

How has the community developed since the last report?

How has the project developed since the last report?

How would you assess the podling's maturity?

Please feel free to add your own commentary.

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

Date of last release:

XXXX-XX-XX

When were the last committers or PPMC members elected?

Have your mentors been helpful and responsive?

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

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

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

Signed-off-by:

(training) Craig Russell
Comments:
(training) Christofer Dutz
Comments:
(training) Justin Mclean
Comments:
(training) Lars Francke
Comments:

IPMC/Shepherd notes:

Tuweni

Tuweni is a set of libraries and other tools to aid development of blockchain and other decentralized software in Java and other JVM languages.

Tuweni has been incubating since 2019-03-25.

Three most important unfinished issues to address before graduating:

More contributors!
Getting started, docs, videos
Finishing the Ethereum client

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?

Community is increasing in size a bit, just with a bit more interest. The dev list increased to 29 subscribers.

How has the project developed since the last report?

The project is under active development.

We have added crucial features to the project such as an Ethereum Virtual Machine, a proxy subprotocol and a network crawler.

We need to cut another release but keep pushing it back, too much work.

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-27

When were the last committers or PPMC members elected?

Nicolas Melendez as committer on 2021-04-29.

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.

All good, need a release out.

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?

No problems reported.