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

Shepherd Assignments

Dave Fisher	AGE
Dave Fisher	Weex
Drew Farris	DolphinScheduler
Drew Farris	PageSpeed
Justin Mclean	ECharts
P. Taylor Goetz	Sedona
P. Taylor Goetz	Toree
P. Taylor Goetz	Warble
Timothy Chen	Doris
Timothy Chen	Heron
Timothy Chen	Pinot
	Annotator
	BlueMarlin
	DataSketches
	Liminal
	Livy
	NLPCraft
	Pegasus
	Ratis
	S2Graph
	SDAP
	Training
	Tuweni

Incubator PMC report for August 2020

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

The PPMC continues to make progress in resolving license and branding issues. During the a recent release vote on 1.7.0, with the help from Justin, a few more source distribution and branding issues were found. Here is the status on the issues, tracked in INCUBATOR-253. As of now, the PPMC resolved 12 issues, with 11 still left.

Most of the outstanding issues hinge on one key outstanding question, which is whether the components in MXNet that are produced by CUDA NVCC constitutes Category X code. PPMC member employed by Nvidia helped connect Nvidia's representatives including Michael O'Connor, Director of Deep Learning, who have been supportive in the efforts of clarification. Progress is tracked in LEGAL-516.

MXNet 1.7.0 release vote was put on hold for addressing the branding issues in third-party releases and for an IP clearance process.

So far, PPMC members from Intel (Tao), Nvidia (Dick), and Amazon (Leonard, Henri, Qing, Sheng) have acted to help resolve the issues.

Status

Source and convenance binary releases containing Category X licensed code. (pending)

Source code releases do not contain Category X code, no issue.
Takedown of binary releases on repository.apache.org is on hold, pending resolution on LEGAL-516.
PyPI releases are considered to be third-party and are discussed in the branding/trademark section.

Website giving access to downloads of non released/unapproved code. (resolved)

Website contained links to nightly development builds which have been removed 5;

Website giving access to releases containing Category X licensed code. (resolved)

Website contained links to third-party distributions incorporating Category X components (see summary from license review above). Disclaimers were added to the website clarifying the third-party status of the releases and their licenses. 5

Web site doesn't given enough warning to users of the issues with non-(P)PMC releases or making it clear that these are not ASF releases. (resolved)

Website contained links to third-party distributions incorporating Category X components (see summary from license review above). Disclaimers were added to the website clarifying the third-party status of the releases and their licenses. 5

Maven releases containing Category X licensed code. (pending)

Takedown of binary releases on repository.apache.org initiated 6. The scope depends on the resolution of LEGAL-516.

PyPI releases containing Category X licensed code. (pending)

There are no PyPI releases by the PPMC. Whether the releases are compliant with branding guidelines depend on the resolution of LEGAL-516.

Docker releases containing Category X licensed code. (pending)

There are no Docker releases by the PPMC. Whether the releases are compliant with branding guidelines depend on the resolution of LEGAL-516.

Docker releases containing unreleased/unapproved code. (resolved)

There are no Docker releases by the PPMC. The PPMC verified that all releases are based on unmodified commits in MXNet, which is approved from brand management 3.

Trademark and branding issues with PyPI and Docker releases. (pending)

There are no PyPI or Docker releases by the PPMC. In addition, as they all contain binary from unmodified MXNet code, the whether they are compliant in branding now solely depends on whether they contain Category X licensed code. Refer to item 6, 7, 8.

Trademark and brand issues with naming of releases. (pending)

There are no binary releases by the PPMC besides the repository.apache.org releases in item 5.

Developer releases available to users and public searchable https://repo.mxnet.io / https://dist.mxnet.io (resolved)

Links to the nightly development builds were removed from the MXNet website and a robot.txt file was added to prevent indexing of the sites. These websites are removed from Google search index.

Releases and other nightly builds on https://repo.mxnet.io / https://dist.mxnet.io containing Category X licensed code (pending)

Neither of the two site contains releases. Whether the binaries there contain Category X components depends on the resolution of LEGAL-516.

Lack of clarity on all platforms for what is an ASF release and what is not. (resolved)

https://github.com/apache/incubator-mxnet/releases?after=1.2.0 previously did not distinguish MXNet releases prior to MXNet joining the Incubator. Disclaimers were added. Other PPMC platforms do not contain references to non-ASF releases (MXNet releases made prior to MXNet joining the ASF). The PPMC is aware of old third-party releases created prior to MXNet joining the ASF which are still available, but can be clearly separated from the ASF MXNet releases due to the lack of reference to the Apache foundation. PPMC was able to find an exemplar such release at 7. If there are concerns from the Incubator, PPMC can request the third-parties to take down these releases, as editing their Description to include references to events (MXNet joining Apache) is not supported due to immutability constraints. 8

to 23. Branding and release of 3rd parties containing unreleased code. (pending)

Known pages with issues:

https://docs.nvidia.com/deeplearning/frameworks/mxnet-release-notes/rel_20-03.html (item 14, pending)
- PPMC reached out to Nvidia. Pending action from Nvidia on branding compliance and replying on whether unreleased code was included.
https://sourceforge.net/projects/apache-mxnet.mirror/ (item 15, pending)
- PPMC reached out to SourceForge. SourceForge added (incubating) in name.
- The mirror is automatic, which happens to contain MXNet release candidate in voting which is an artifact of MXNet's release process 9
- PPMC granted SourceForge's request for more time for engineering to filter out non-release tags. In any case, after completion of release process, the RC will be automatically removed.
DJL related links.
- The following constitutes nominative use of MXNet and is approved by brand management committee 10:
  - https://repo.gradle.org/gradle/simple/repo/ai/djl/mxnet/mxnet-native-mkl/1.7.0-b/ (item 16, resolved)
  - https://mvnrepository.com/artifact/ai.djl.mxnet (item 17, resolved)
  - https://aur.archlinux.org/packages/?O=0&SeB=nd&K=mxnet&SB=v&SO=d&PP=50&do_Search=Go (item 18, resolved)
- https://djl.ai (item 19, resolved)
  - the DJL project have updated their language with regards to Apache MXNet 11
AWS Marketplace related links
- https://aws.amazon.com/marketplace/pp/NVIDIA-MXNet-by-NVIDIA/B07KLFW54D (item 20, resolved)
  - Per request from PPMC, NVIDIA removed this listing.
- https://aws.amazon.com/marketplace/pp/prodview-yex2xx5kgdhea?qid=1595741035764&sr=0-1&ref_=srh_res_product_title (item 21, resolved)
  - Per request from PPMC, Intel removed this listing.
- https://aws.amazon.com/marketplace/pp/B07YW8HVLD?qid=1595741035764&sr=0-4&ref_=srh_res_product_title (item 22, pending)
  - PPMC reached out to AWS through internal channel to try to establish contact with the listing owner.
- https://aws.amazon.com/marketplace/search/results?x=0&y=0&searchTerms=%22MXNet (item 23, pending)
  - PPMC reached out to AWS through internal channel to try to establish contact with the listing owner.

Background on MXNet License and Trademark Issue Discovery

(also in last board podling report, attached for completeness)

In May 2020 The MXNet PPMC has proactively initiated a ASF policy compliance review 1 and a license review 2 with the Apache Legal team.

The license review uncovered that

Building unmodified MXNet release source code with the optional Nvidia GPU support enabled may result in a binary subject to restrictions of Nvidia EULA (clarification in progress in LEGAL-516).
Some of the convenience releases that the PPMC members and committers uploaded to repository.apache.org contain potential Category X components.

The policy review uncovered that:

Prior ASF guidance to the PPMC (December 2018 legal review 3) was incomplete and did not include a reference to the "unwritten" rule that convenience binary distributions created by third-parties using ASF Trademarks must not include Category X components. Based on this discovery, the Draft Downstream Distribution Branding Policy was updated in June 2020 to include the "unwritten" requirement. Based on the updated guidance, PPMC discovered various third-party branding guideline incompliances.

The policy review did not yet conclude on the questions if

The PPMC may create nightly development builds (audience restricted to dev list subscribers as per Release policy 4) for the purpose of testing and developing MXNet;

Background on Nvidia CUDA EULA components by third-parties

(also in last board podling report, attached for completeness)

PPMC members note that the issue of "Nvidia CUDA EULA infecting any application built with CUDA support" is an industry-wide problem. PPMC is not aware of any individual or corporation correctly labeling their binary distributions subject to the Nvidia CUDA EULA. Instead, PPMC found that for example Facebook claims distribution of PyTorch under BSD License (BSD-3) and Google claims distribution of Tensorflow under Apache 2.0 License, despite both being subject to the CUDA EULA. Thus, PPMC has contacted Nvidia Corporation and requested Nvidia Corporation to add clarifying language that applications based on the CUDA SDK with material additional functionality may be licensed under a license of the application owner's choice, consistent with existing industry "practice".

The issue was also discussed with Nvidia and other Deep Learning Framework implementers during the Nvidia Deep Learning Framework Developer Council meeting, during which Nvidia promised to conclude their internal review and follow-up with the PPMC.

PPMC thus recommends to give Nvidia the chance to clarify and improve their license. As Nvidia employs a team for working on MXNet, the PPMC is optimistic about receiving a detailed clarification and resolution from Nvidia.

If Nvidia fails to clarify their license or the resolution is unsatisfactory within Q3 2020, the PPMC intends to notify any third-parties about their license infringement and ask them to take down or rename their redistributions as containing Category X pieces.

Reference links

Infrastructure

Miscellaneous

Credits

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:

Complete the Apache AGE Website development and infrastructure setup.
First Apache based release.
Build Healthy community around 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?

Current focus is to complete the rest of few tasks of Podling bootstrapping process and move working on our first Apache based release.

How has the project developed since the last report?

We submitted ICLAs/CCLA/SGA for the project and completed the Repo migration to Apache. Worked on an internal 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:

We are currently working on our first Apache release.

When were the last committers or PPMC members elected?

None.

Have your mentors been helpful and responsive?

Yes, they have been helpful and responsive.

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

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:

IPMC/Shepherd notes:

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:

Communicate a clear roadmap
Add active contributors
Demonstrate good governance through voting on process improvements.

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?

Community calls continue. A few new developers and projects have reached out with interest in using the project. Developing this community is the highest priority of the project right now.

How has the project developed since the last report?

The project has made its first release. In the month since, the community has converted the project to TypeScript, added a DOM/HTML text highlighting capability to the public API, and expanded the automated test suite.

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:

July 11, 2020

When were the last committers or PPMC members elected?

June 6, 1028

Have your mentors been helpful and responsive?

Yes.

Signed-off-by:

(annotator) Nick Kew
Comments:
(annotator) Steve Blackmon
Comments:
(annotator) Tommaso Teofili
Comments:

IPMC/Shepherd notes:

BlueMarlin

TODO

BlueMarlin has been incubating since 2020-09-06.

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:

(bluemarlin) TODO
Comments:

IPMC/Shepherd notes:

DataSketches

DataSketches is an open source, high-performance library of stochastic streaming algorithms commonly called "sketches" in the data sciences. Sketches are small, stateful programs that process massive data as a stream and can provide approximate answers, with mathematical guarantees, to computationally difficult queries orders-of-magnitude faster than traditional, exact methods.

DataSketches has been incubating since 2019-03-30.

Three most important unfinished issues to address before graduating:

Adding more committers. We have just added our first new committer since incubation! We have a few more individuals that have been consistent contributors to the project that we will soon want to go through the new committer election process. This is a big change from our last report where we had no candidates at all.
Fill out the Maturity Model
Prepare for Graduation.

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

We could use some help in finding people who would find working in the sketching algorithms area really interesting and would want to work with us to become committers.

How has the community developed since the last report?

The word is getting out! We presented talks at the USPTO 2020 tech conference and the Spark & AI 2020 conference, mentioned in the last report, with lots of good feedback.

We will be co-authors in a tutorial on sketching technology at the upcoming ACM-KDD conference in August with one of the world's leading scientists in streaming algorithms and sketching.

We have been invited to give a keynote talk at the upcoming DataCon2020 in Taiwan in early September.

We have been accepted for a talk at ApacheCon again this year.

We also are seeing a big increase in the number of single PRs coming from a number of different people, especially for our C++ components, which is very good news. This proves that there is growing interest in the project and there are folks out there that want to contribute to the project.

How has the project developed since the last report?

See the releases since the last report below.

In addition we have made significant improvements to our website thanks to some external contributors!

To the best of our knowledge all of our licensing and website issues have been addressed and have been implemented in formal releases or are in master-branch staging, awaiting the next 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-07-06 incubating-datasketches-hive 1.1.0
2020-06-19 incubating-datasketches-cpp 2.0.0
2020-05-07 incubating-datasketches-java 1.3.0

When were the last committers or PPMC members elected?

August, 2020

Have your mentors been helpful and responsive?

Yes, in general. However, we do have to prod them with reminders to check-off our releases. Our releases have been taking longer and longer to get through the voting process especially when it is in the 2nd IPMC phase. A little help here would be appreciated.

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

To the best of our knowledge, yes.

Are 3rd parties respecting and correctly using the podlings name and brand?

As far as we know, yes.
If not what actions has the PPMC taken to correct this?

We have not had to face this issue yet.
Has the VP, Brand approved the project name?

Yes, and it is clearly stated as such on http://incubator.apache.org/projects/datasketches.html

Signed-off-by:

(datasketches) Liang Chen
Comments:
(datasketches) Kenneth Knowles
Comments:
(datasketches) Furkan Kamaci
Comments:
(datasketches) Dave Fisher
Comments:
(datasketches) Evans Ye
Comments:

IPMC/Shepherd notes:

DolphinScheduler

DolphinScheduler is a distributed ETL scheduling engine with powerful DAG visualization interface..

DolphinScheduler has been incubating since 2019-08-29.

Three most important unfinished issues to address before graduating:

1.Guide community to commit code and code review using Apache way. 2.Develop more committers and 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?

GitHub code contributors grew from 100 to 116.
Hold a co-meetup with Apache Doris and 1900 people join the on-line meetup on July, 25.

How has the project developed since the last report?

Apache Dolphin Schedule1.3.1 has released and 1.3.2 is ready for voting.
Maven Plugin 1.0.0 is in voting 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-7-13

When were the last committers or PPMC members elected?

2019-5-28

Have your mentors been helpful and responsive?

Our mentors were very helpful, help us to refine release process and how to release a plug-in.

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:

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:

We have not released a release version without WIP, we are preparing it.
We need a more stringent code access and testing environment to ensure code quality and project stability.

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?

Since the last report, we have added 16 contributors and 2 committers. There are currently 100 contributors and 19 committers.
We upgraded our website. Now we can understand the characteristics of Doris more intuitively on the website.
We joined a co-meetup with Apache DolphineScheduler and 1900 people join the on-line.

How has the project developed since the last report?

Since last report(2020-06-01), a total of 262 commits were merged. The community contributed a lot of new features and helped Doris fix many bugs. We are working hard to prepare the next release version(0.13)

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-24: Apache Doris (incubating) 0.12.0-rc03

When were the last committers or PPMC members elected?

Zhengguo Yang: New Committer, 2020-06-22

Yunfeng Wu: New Committer, 2020-08-05

Have your mentors been helpful and responsive?

All mentors are helpful.

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

Yes. 3rd parties are using the podlings name and brand correctly. And the project name is approved.

Signed-off-by:

(doris) Dave Fisher
Comments:
(doris) Willem Ning Jiang
Comments: It's good to see the meetup across with the ASF incubating projects.
(doris) Shao Feng Shi
Comments:

IPMC/Shepherd notes:

ECharts

ECharts is a charting and data visualization library written in JavaScript.

ECharts has been incubating since 2018-01-18.

Three most important unfinished issues to address before graduating:

Ensure Mentors and IPMC have no remaining issues for graduating We are currently discussing graduation related topics under podling's dev mailing list and make sure PPMC and mentors have no remaining issues before we start discussing under general@incubator.
Prepare a resolution
Propose votes in incubator and general mailing list

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

We have solved the CDN issue in China by providing a Cloud Service account that can be accessed by PPMCs and found the donor for the CDN fees. The donor Ming Zu is a senior manager of Baidu and fan of ECharts.

How has the community developed since the last report?

The community has grown fast and more people are contributing to the project. 73 people have contributed to the project during incubation. Committers work for more than 6 different companies and from 3 different countries. We elected two committers to be PPMC members since last report.

How has the project developed since the last report?

We have released a new version 4.8.0 and an alpha version 5.0.0-alpha.1 and we are working toward the official release of 5.0.0.

How would you assess the podling's maturity?

Please feel free to add your own commentary.

We have made the maturity assessment 1 and are currently discussing in the project's dev mailing list about it.

Initial setup
Working towards first release
Community building
Nearing graduation
Other: reviewing and discussing graduation requirements

1 https://cwiki.apache.org/confluence/display/ECHARTS/Apache+Maturity+Model+As sessment+for+ECharts

Date of last release:

2020-05-28

When were the last committers or PPMC members elected?

2020-07-27

Have your mentors been helpful and responsive?

Yes. Mentors have been very helpful and responsive.

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

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? The PPMC is managing the brand and trademarks. No problems found about this.

Signed-off-by:

(echarts) Kevin A. McGrail
Comments: ECharts is doing well.
(echarts) Dave Fisher
Comments: I expect that ECharts will graduate in the next month or two.
(echarts) Ted Liu
Comments:
(echarts) Sheng Wu
Comments: Expect the echarts will be ready for TLP soon.

IPMC/Shepherd notes:

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:

Community building
Improving the release process
Improving documentation

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?

Two new committers were elected. Discussions are increasing across slack. Need to work on reporting the conversations in slack to the mailing list.

How has the project developed since the last report?

There have been bug fixes and feature improvements. Some to note are:

Python 3 upgrade
Bazel upgrade

How would you assess the podling's maturity?

Please feel free to add your own commentary.

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

Date of last release:

2019-11-14 0.20.2-incubating. Community is currently working on a new release.

When were the last committers or PPMC members elected?

Two new committers where voted in:

Oliver Bristow (July 22, 2020)
Windham Wong (July 3, 2020)

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 responsive when needed.

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:

(heron) Jake Farrell
Comments:
(heron) Julien Le Dem
Comments:
(heron) P. Taylor Goetz
Comments:
(heron) Dave Fisher
Comments: The podling seems to be working as a team better.

IPMC/Shepherd notes:

Liminal

TODO

Liminal has been incubating since 2020-05-23.

Three most important unfinished issues to address before graduating:

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

How has the community developed since the last report?

How has the project developed since the last report?

How would you assess the podling's maturity?

Please feel free to add your own commentary.

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

Date of last release:

XXXX-XX-XX

When were the last committers or PPMC members elected?

Have your mentors been helpful and responsive?

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

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

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

Signed-off-by:

(liminal) TODO
Comments:
(liminal) TODO
Comments:

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:

Start preparing towards graduation

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?

Moderate activity on mailing lists and code as well

How has the project developed since the last report?

Currently the community is working on HA feature and support for Spark on Kubernetes. Spark 3.0 support was added recently and a new release will be started once it has been more thought tested

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?

Yes

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

Yes

Signed-off-by:

(livy) Bikas Saha
Comments:
(livy) Brock Noland
Comments:
(livy) Luciano Resende
Comments:
(livy) Jean-Baptiste Onofre
Comments: Still planning to contribute what I proposed on the mailing list while ago. I think we are pretty close to graduation. Maybe worth to start a discussion.

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:

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:

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

IPMC/Shepherd notes:

PageSpeed

PageSpeed represents a series of open source technologies to help make the web faster by rewriting web pages to reduce latency and bandwidth.

PageSpeed has been incubating since 2017-09-30.

Three most important unfinished issues to address before graduating:

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?

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?

The first incubator release has been announced after field-testing. Furthermore, small enhancements are being contributed from people outside of the initial committer group. Major changes have landed on master: the build system has been refreshed to leverage bazel, c++17, abseil and Envoy. All dependencies have been refreshed and sanitized where possible. As a side-effect, some of the remaining issues from the WIP-DISCLAIMER have been addressed.

MPL licensed source code for http date parsing replaced with our own version which leans on abseil. That part is all Apache licensed now.
The no longer contains compiled code pulled in from dependencies.

A simple PoC port to Envoy has landed, as a first step towards running PageSpeed as a stand-alone sidecar service (where traffic of arbitrary servers can be routed through it via transparent proxying or L7 routing).

How would you assess the podling's maturity?

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

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?

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

Yes.

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?

As far as we know the brand is respected by third parties. We-Amp mirrors the incubator site over at modpagespeed.com - but will work on transferring the domain name to the ASF this quarter.
It's not known if the VP, brand has explicitly approved, so that is something we need to make sure about and resolve.

Signed-off-by:

(pagespeed) Jukka Zitting
Comments:
(pagespeed) Leif Hedstrom
Comments:
(pagespeed) Nick Kew
Comments:

IPMC/Shepherd notes:

Pegasus

Pegasus is a distributed key-value storage system which is designed to be simple, horizontally scalable, strongly consistent and high-performance.

Pegasus has been incubating since 2020-06-28.

Three most important unfinished issues to address before graduating:

Project code donation
First release
Building community

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?

N/A.

How has the project developed since the last report?

ICLA/SGA are all submitted. Accounts created. JIRA/DNS/LDAP/mail-lists created. The website repo has been migrated to Apache Github.

How would you assess the podling's maturity?

Please feel free to add your own commentary.

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

Date of last release:

None

When were the last committers or PPMC members elected?

None yet.

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, they are very nice and helpful.

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, We keep tracking podling's brand / trademarks.

Signed-off-by:

(pegasus) Kevin A. McGrail
Comments: I am just getting involved with this podling and look forward to guiding them more.
(pegasus) Duo zhang
Comments:
(pegasus) Liang Chen
Comments:
(pegasus) Von Gosling
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 2019-03-01.

Three most important unfinished issues to address before graduating:

None

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 have 470+ users on slack - all slack discussions are forwarded to the project mailing list.

How has the project developed since the last report?

Released 0.4.0
Voted Ting Chen and Kartik Khare as a new committer.
Voted Jackie and Xiang Fu to PPMC

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

When were the last committers or PPMC members elected?

July 2020

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: What's the next step towards graduation?

IPMC/Shepherd notes:

Ratis

Ratis is a java implementation for RAFT consensus protocol

Ratis has been incubating since 2017-01-03.

Three most important unfinished issues to address before graduating:

Work on the graduation template.
Expand the community, committers and PPMC.

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?

4 new contributors. 47 total contributors.

How has the project developed since the last report?

~60 commits.
Apache Ratis 1.0.0 (GA) released in July.
Apache Ratis Thirdparty 0.5.0 released.
Ratis is now using GitHub pull requests and GitHub Actions for pre-commit checks for a better contributor experience.
Jakob Homan stepped down as podling mentor
Arpit Agarwal volunteered to be a mentor

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:
The community has grown since inception and more importantly we have more diversity of committer affiliations. The recent GA release indicates that the project has reached a level of stability and it is very close to graduation.

Date of last release:

2020-07-20 - Apache Ratis 1.0.0
2020-06-26 - Apache Ratis Thirdparty 0.5.0

When were the last committers or PPMC members elected?

2020-02-21 - Siddharth Wagle added as committer.

Have your mentors been helpful and responsive?

Mentors are helpful

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

Name is approved. https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-160

Signed-off-by:

(ratis) Uma Maheswara Rao G
Comments:
(ratis) Arpit Agarwal
Comments: Active development and regular releases. Nearing graduation.
(ratis) Devaraj Das
Comments:

IPMC/Shepherd notes:

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:

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:

(s2graph) Sergio Fernández
Comments:
(s2graph) Woonsan Ko
Comments:

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:

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:

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

Podling bootstrap: initial code import, name search
New website and branding
Community growth

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?

N/A

How has the project developed since the last report?

Good progress on bootstrap, LDAP and DNS created, JIRA created, git repo created, mailing lists created. 5 PPMC CLA submitted, account created and added to the roster of Sedona. We have removed all incompatible 3rd party library dependencies in the old codebase. Now we are waiting for another committer to submit the CLA and then the code will be imported to ASF Git repo.

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 still bootstrapping.

When were the last committers or PPMC members elected?

N/A

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?

Not yet, we are still doing the initial setup.

Signed-off-by:

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

I have started updating the podling related artifacts such as project page, etc and will try to start graduation discussions before the next report.

1.Increase active contributors 2. 3.

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?

The project has worked on the 0.4.0-incubating release, and is adding support for Spark 3.0 which will be available on the 0.5.0-incubating 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-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?

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

There was nothing requiring mentor intervention on the last quarter.

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 Trademark issues

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:

Promote the information about Apache Training Project with increased participation from community
Create a tutorial on how the tools provided by this project can be used to create own content
Review current policies around contribution review and releases to find a pragmatic compromise

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

Due to recent changes in work being done remote has led to change of format for many conferences and trainings. The Training project can be very valuable in dissemination of knowledge in this situation. We hope to adapt to new format of learning in this situation.

How has the community developed since the last report?

Activity has increased since the last report. There were 71 posts in last 3 months. We have received contributions from other Apache projects like COMDEV and other individual contributors.

How has the project developed since the last report?

New training slides were added on three topics:

Apache Hadoop
Apache Hive
Apache COMDEV

PR activity has picked up momentum since the last report.

How would you assess the podling's maturity?

There are currently some issues with this podling that we are working to address, we believe that the issues are not yet critical and can be turned around from within the community but want to make the board aware of this early on.

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

When were the last committers or PPMC members elected?

February 2020

Have your mentors been helpful and responsive?

Mentors have been responsive and helpful when reached out to.

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

The name search process has not yet been started, as there is still time to do that if and when graduation draws nearer. The PPMC is actively monitoring usage of the Podlings current name on other sites. The Podling is not directly affiliating with any sponsors donating content and presenting an independent image on the webpage.

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:

Finish export notice for cryptographic elements
Vote in a few more committers
Keep release pace and adoption

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

No issues to report at this time.

How has the community developed since the last report?

We are seeing a few contributions in the bug reports and pull requests offered on the repository. The project is starting to gain good traction.

We have seen adoption of the project downstream and a couple of fixes contributed as direct result.

How has the project developed since the last report?

We voted 1.1.0, with a set of new features. The roadmap is on Github and more accessible. The project is also using Github actions to help kick faster CI for pull requests.

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

When were the last committers or PPMC members elected?

Danno Ferrin as committer on 2020-06-08.

Have your mentors been helpful and responsive?

Absolutely.

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

Yes. At present, there are no issues nor concerns with the Tuweni mark. We do not anticipate any issues with the mark regarding graduation.

Signed-off-by:

(tuweni) Jean-Baptiste Onofré
Comments:
(tuweni) Michael Wall
Comments:
(tuweni) Furkan Kamaci
Comments:

IPMC/Shepherd notes:

Warble

a distributed endpoint monitoring solution where the agent is hosted on your own hardware.

Warble has been incubating since 2018-06-11.

Three most important unfinished issues to address before graduating:

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

How has the community developed since the last report?

How has the project developed since the last report?

How would you assess the podling's maturity?

Please feel free to add your own commentary.

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

(warble) Chris Lambertus
Comments:

Branding issues. There are about 10 git repos violating the trademark of Apache Weex, together with their NPM/Maven artifact.
[Community diversity](https://cwiki.apache.org/confluence/display/WEEX/Communtiy+divers ity). Apache Weex needs more PPMCs and committers from community, no employees from a single company shall have majority vote in PPMC and committer.

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?

Working towards releasing new version

How has the project developed since the last report?

We have 8 incoming pull request, and 7 of them are merged.
We have 1 threads in Weex mailing list .
We have solved 10 Github issues.

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 are collecting a list of branding issues, and we shall fix the problem one by one.

Page tree

Timeline

Shepherd Assignments