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

Report submitted to Board

Wed November 16Board meeting


Shepherd Assignments

Dave FisherPony Mail
Dave FisherTraining
Drew FarrisKvrocks
Drew FarrisNLPCraft
Justin McleanToree
P. Taylor GoetzPageSpeed
P. Taylor GoetzStreamPark
P. Taylor GoetzTuweni
Timothy ChenBaremaps
Timothy ChenLivy
Timothy ChenSedona

Incubator PMC report for November 2022

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 36 podlings incubating. Podlings made 11 distinct releases. This month we are only missing a report from Marvin-AI. This project has massed several reports. We held roll calls for projects that had difficulty reporting or low activity, and some are discussing retirement. Some may need to be encouraged further. Several projects that had been incubating for some time were reminded that it was time to graduate or retire. There are discussions or votes on graduation for bRPC, Flagon, Kyuubi, Linkis, Nemo, Nuttx, StreamPipes and Tuweni. Other projects are discussing graduation or retirement on their lists. Livy now has a new PPMC and has avoided retirement. SDAP has determined they need to make a release before graduating. Pekko (a fork of the Akka project) has joined the Incubator. Following the recent board decision, we have removed the 72-hour waiting time to add PPMC members.

Community

New IPMC members:

  • Claus Ibsen

People who left the IPMC:

None

New Podlings

  • Celeborn
  • Baremaps

Podlings that failed to report, expected next month

  • Marvin-AI.

Graduations

  • None

The board has motions for the following:

  • NuttX
  • StreamPipes

Releases

The following releases entered distribution during the month of October:

  • Brpc 1.3.0
  • Devlake 0.14.0
  • Heron 0.20.5
  • Linkis 1.3.0
  • Nuttx 11.0.0
  • Pegasus 2.4.0
  • Seatunnel 2.2.0-beta
  • Seatunnel 2.3.0
  • Streampipes 0.70.0
  • Tuweni 2.3.0
  • Uniffle 0.6.0

IP Clearance

None

N/A

Infrastructure

N/A

Miscellaneous

N/A

Table of Contents

Baremaps
Celeborn
DevLake
Heron
Kvrocks
Linkis
Livy
Milagro
NLPCraft
PageSpeed
SDAP
Sedona
StreamPark
Teaclave
Toree
Training
Tuweni


Baremaps

Apache Baremaps is a toolkit and a set of infrastructure components for creating, publishing, and operating online maps.

Baremaps has been incubating since 2022-10-10.

Three most important unfinished issues to address before graduating:

  1. Learning the apache way, getting the code in compliance with Apache standards
  2. Making our first release
  3. Growing the community

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?

  • This is our first report.

How has the project developed since the last report?

  • This is our first 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:

  • N/A

When were the last committers or PPMC members elected?

  • 2022-10-14, when the project was accepted into the incubator.

Have your mentors been helpful and responsive?

  • The mentors have been super helpful.
  • The meeting with mentors, committers and stakeholders was an excellent way to kick off the project.

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

  • we are in progress

Signed-off-by:

  •  (baremaps) Bertrand Delacretaz
    Comments: All looks good so far, great energy and collaboration!
  •  (baremaps) Martin Desruisseaux
    Comments:
  •  (baremaps) Julian Hyde
    Comments: Project has gotten off to a great start. Good positive energy on the dev list. The kickoff meeting was fun, with good attendance by mentors and initial committers.
  •  (baremaps) Calvin Kirs
    Comments:
  •  (baremaps) George Percivall
    Comments:
  •  (baremaps) Martin Desruisseaux
    Comments:

IPMC/Shepherd notes:


Celeborn

Celeborn is an intermediate data service for big data computing engines to boost performance, stability, and flexibility.

Celeborn has been incubating since 2022-10-18.

Three most important unfinished issues to address before graduating:

  1. Finish the process of Initial Code Import
  2. Publish our first release
  3. Grow the community

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?

  • This is our first report.

How has the project developed since the last report?

  • This is our first 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:

  • N/A

When were the last committers or PPMC members elected?

  • 2022-10-18, when the project was accepted into the incubator.

Have your mentors been helpful and responsive?

  • Our mentors have been very helpful and responsive.

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

  • We are in process of designing our LOGO.

Signed-off-by:

  •  (celeborn) Becket Qin
    Comments:
  •  (celeborn) Lidong Dai
    Comments:
  •  (celeborn) Willem Ning Jiang
    Comments:
  •  (celeborn) Duo Zhang
    Comments:
  •  (celeborn) Yu Li
    Comments: Podling bootstrap almost done, repository migration in progress. PPMC is very cooperative and responsive.

DevLake

DevLake is a development data platform, providing the data infrastructure for developer teams to analyze and improve their engineering productivity.

DevLake has been incubating since 2022-04-29.

Three most important unfinished issues to address before graduating:

  1. Grow the community, add committers and PPMC members
  2. Grow the ecosystem, support more data sources and use cases

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

No issues at the moment.

How has the community developed since the last report?

  1. 10 new contributors have joined the community (56 committers in total)
  2. One new committer was elected
  3. Hosted five community meetups

How has the project developed since the last report?

  1. Made one release per month
  2. Support DORA metrics, a well-publicized framework for measuring software delivery performance
  3. Add incoming webhook for users to actively push deployment data to DevLake. This allows DevLake to work with any CI/CD system when it comes to calculating DORA.
  4. Differentiate between Scrum and Non-Scrum boards in Jira for more accurate data aggregation
  5. Prompts users to confirm DB migration during upgrade through Config-UI

How would you assess the podling's maturity?

Please feel free to add your own commentary.

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

Date of last release:

2022-10-14

When were the last committers or PPMC members elected?

2022-09-22

Have your mentors been helpful and responsive?

Yes, the mentors helped tremendously throughout version releases and community governance.

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

There are no known brand and naming issues.

Signed-off-by:

  •  (devlake) Felix Cheung
    Comments:
  •  (devlake) Liang Zhang
    Comments:
  •  (devlake) Lidong Dai
    Comments:
  •  (devlake) Sijie Guo
    Comments:
  •  (devlake) Jean-Baptiste Onofré
    Comments:
  •  (devlake) Willem Ning Jiang
    Comments: The project status goes well with the new release and new PPMC members.

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:

1.Growing the community, 2.make Heron easier to use 3.Improving our release process

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 current community has stayed consistent and stable.

How has the project developed since the last report?

There has been lots of work in addressing issues of running Heron in k8s (move “cloud native”).

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:

2022-10-23

When were the last committers or PPMC members elected?

Saad Ur Rahman, 2021/11/29

Have your mentors been helpful and responsive?

Yes.

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

Yes.

Signed-off-by:

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

IPMC/Shepherd notes:


Kvrocks

Kvrocks is a distributed key-value NoSQL database, supporting the rich data structure.

Kvrocks has been incubating since 2022-04-23.

A list of the three most important issues to address in the move

towards graduation

  1. Promote the project and grow the user and dev community
  2. Need more further releases by multiple release manager

Any issues that the Incubator PMC or ASF Board might wish/need to be

aware of

None

How has the community developed since the last report?

  1. We got 7 new contributors since the last report
  2. We finished a promotional article that has been published on the OSCHINA platform.
  3. Pliops tests Kvrocks on their XDP hardware, and gained great performance improvements.

How has the project developed since the last report?

  1. We added some documents to help users study Kvrocks.
  2. Support TLS mode to secure the connection.
  3. Our focus is still on improvements and bug fixes, which included moving tcl test to go cases, and improve modern code style.

How does the podling rate their own maturity?

As mentioned in mentor's sign-off-by section, the active Kvrocks commnunity is more and more better now, but we still need more further releases to involve in multi release managers.

Please feel free to add your own commentary.

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

Date of last release:

We completed the first Kvrocks release at 2022.08.03.

When were the last committers or PPMC members elected?

  1. 2022-09-08 We eleted PragmaTwice as a Kvrocks PMC member
  2. 2022-09-17 We elected Torwig as a Kvrocks committer
  3. 2022-10-18 we elected tanruixiang as a Kvrocks committer

Have your mentors been helpful and responsive?

Yes, they mentored us a lot on how to maintain the community, and also did many contributions for Kvrocks.

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

No 3rd parties used the podling and brand.

Signed-off-by:

  •  (kvrocks) Jean-Baptiste Onofre
    Comments: The team is doing a great job. It would be great to grow the community though (by doing more release, documentation, announcements, ...)
  •  (kvrocks) Xiaoqiao He
    Comments:
  •  (kvrocks) tison
    Comments: The community can spend more time on further releases by multiple release manager. Discussions-1031 is a good start.
  •  (kvrocks) Von Gosling
    Comments: More community activity, more releases, more health.
  •  (kvrocks) Liang Chen
    Comments:

IPMC/Shepherd notes:


Linkis

Apache Linkis is a computation middleware project, which decouples the upper applications and the underlying data engines, provides standardized interfaces (REST, JDBC, WebSocket etc.) to easily connect to various underlying engines (Spark, Presto, Flink, etc.).

Linkis has been incubating since 2021-08-02.

Three most important unfinished issues to address before graduating:

  1. Make Apache releases regularly and keep the quality for all releases
  2. Gain more active contributors and committers to build a diverse community
  3. Prepare graduation process

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 committers and 20+ contributors increased. There are currently 120+ contributors and 32 committers.
  • 627 issues and 563 pull requests since last report (2022/08/22). (issues: total/closed/open 1923/1688/235, pr: total/closed/open 1732/1712/20)
  • Since the last report, we have held 5 bi-weekly meetings to discuss the progress and needs of the developing versions of Apache Linkis, and conducted once Apache Linkis community meetups.
  • Our PPMC member, Shuai Di and committer Meng Li both participated ApacheCon Asia 2022 and gave two talks on Linkis.
  • Community committers actively participated in china apache hadoop 2022 online and offline meetup and coscon 2022 meetup

How has the project developed since the last report?

  • Apache linkis 1.1.3 released on 2022-08-01. This release mainly integrates Prometheus to provide the basic capability of monitoring on linkis microservice; add task retries parameter for task submission; add records for the relationship between tasks and execution EC;upgrade some security vulnerability components, etc.
  • Apache Linkis 1.2.0 released on 2022-09-06. This release mainly supports Presto and ElasticSearch engines for Linkis 1.X architecture, enhances JDBC engine to support configuration multiple data source, reduced and optimized Linkis modules, improved test cases for some engines, and made a lot of bug fixes and feature improvements.
  • Apache Linkis 1.3.0 released on 2022-10-26. The release of Linkis 1.3.0 mainly merge some services in the PES(Public Enhancement Services) service group; supports distributed deployment of gateway services; supports the deployment of Linkis services in the Kubernetes environment, including unified image construction, complete Helm Charts, and complete testing peripherals based on Kind.
  • Fix CVE-2022-39944: The Apache Linkis JDBC EngineConn module has a RCE Vulnerability

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:

2022-10-26

When were the last committers or PPMC members elected?

  • 2022-10-22 New PPMC: Ling Xu
  • 2022-10-22 New PPMC: HuaJin Zhang
  • 2022-10-14 New Committer: Zhiqiang Tao
  • 2022-10-12 New Committer: Meng Li
  • 2022-09-27 New Committer: Lin Wukang
  • 2022-09-16 New Committer: Yang Bao
  • 2022-09-16 New PPMC: Longping Jie

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:

  •  (linkis) Duo Zhang
    Comments: Congratulations to the new PPMC members and committers!
  •  (linkis) Lidong Dai
    Comments:
  •  (linkis) Shaofeng Shi
    Comments:
  •  (linkis) Saisai Shao
    Comments:
  •  (linkis) Junping Du
    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:

  1. Reinvigorate project with new committers and PPMC
  2. Update support to latest Spark
  3. Revitalize the community

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

There is a proposal on the incubator email lists to revitalize the Livy project around an updated set of goals with the addition of new mentors, PPMCs, and committers.

As the PPMC has seemed to have moved on, Jean-Baptiste Onofre and Alex Bozarth are the only members "active" on the private list and Alex has stated he does not have bandwidth to work on Livy currently, there is not a quorum available to vote on the proposal. As such we would like the IPMC to aid in passing the proposal to revitalize the project.

How has the community developed since the last report?

The community has been stagnant outside of the above proposal

How has the project developed since the last report?

There has been no development due to a lack of active PPMC/committers

How would you assess the podling's maturity?

Please feel free to add your own commentary.

  •  Initial setup
  •  Working towards first release
  •  Community building
  •  Nearing graduation
  •  Other: Nearing graduation in code stability but without a dev community supporting it, the devs have moved to working on forks due to lack of PPMC availability

Date of last release:

2021-02-02

When were the last committers or PPMC members elected?

2019-01-22

Have your mentors been helpful and responsive?

No answer.

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

No answer.

Signed-off-by:

  •  (livy) Bikas Saha
    Comments:
  •  (livy) Luciano Resende
    Comments:
  •  (livy) Jean-Baptiste Onofré
    Comments: Livy "new" community bring the podling back to live. It's on the way.

IPMC/Shepherd notes:


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:

  1. 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.
  2. 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.
  3. 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?

Mentors missed signing off last month's podling report but have committed to signing of this report. A roll call of the PPMC was requested by Justin McLean to judge ongoing interest in the project following recent inactivity with 5 out of 9 responding and expressing interest in reviving the project. A vote is being preared to add a new PPMC member to help with outstanding administrative tasks, defining the project's roadmap and building the community.

How has the community developed since the last report?

No change.

How has the project developed since the last report?

Second round voting for the MPC release is underway with currently 3 binding +1 votes from IPMC members. Result to be announced presently.

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 2020

Have your mentors been helpful and responsive?

Missing podling report sign offs as mentioned above, but both have responded recently.

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:


NLPCraft

A Java API for NLU applications

NLPCraft has been incubating since 2020-02-13.

Three most important unfinished issues to address before graduating:

  1. Community growth.
  2. Releasing a stable 1.0 version.

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 development has seemingly stalled in the last few months. The main reason is probably due to core committers engaged in a 1.0 release tests and website update.

How has the project developed since the last report?

The project tests were significantly extended, documentation updated.

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:

2021-7-30

When were the last committers or PPMC members elected?

August of 2021.  

Have your mentors been helpful and responsive?

No issues with mentors to report.

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

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:


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.

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

The project has been in the incubator for a long time.

While the project enjoys a strong user base that has grown during this time, the project has not succeeded to grow a strong developer base to match this. Therefore we think the project should withdraw from the incubator.

Signed-off-by:

  •  (pagespeed) Leif Hedstrom
    Comments:
  •  (pagespeed) Nick Kew
    Comments:
  •  (pagespeed) Atri Sharma
    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:

  1. Nominate RM (release manager) and collect source into tarball
  2. Create release notes, instructions for building SDAP from above source, confirm appropriate headers and licenses are in place.
  3. Make official SDAP (Incubating) Release

Our target is to graduate by early December, 2022.

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?

Discussion and development is active.

An Apache SDAP talk was given at ApacheCon in October 2022.

SDAP has gained a new mentor, Julian Hyde.

How has the project developed since the last report?

Completed issues:

  • SDAP-398: CDMS API Tests
  • SDAP-407: Return depth in CSV and NetCDF outputs
  • SDAP-406: Time series comparison stats issues
  • SDAP-405: Update matchup endpoint to use SPURS API in AWS
  • SDAP-403: Catch ReadTimeout exception when adding remote collections
  • SDAP-402: Update match-up algorithm to return all variables at the same lat,lon,time for matchOnce=true
  • SDAP-399: Update SDAP quickstart guide to include instructions for both docker and k8s installation

New/Updated Issues:

  • SDAP-401: Add support for additional JSON outputs for ease of generating plots
  • SDAP-392: Have a distributed configuration for a federation of SDAPs
  • SDAP-391: For proxied collections, improve level of metadata in the /list end-point
  • SDAP-389: publish SDAP helm chart in an helm repo

How would you assess the podling's maturity?

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

Date of last release:

No official releases of Apache SDAP have been made.

When were the last committers or PPMC members elected?

One new member was invited to join in October 2022.

Have your mentors been helpful and responsive?

Mentors have been helpful and responsive. Our new mentor, Julian Hyde, has been very helpful in providing guidance regarding graduation.

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

PPMC is not aware of any issues.

Signed-off-by:

  •  (sdap) Julian Hyde
    Comments: * The initial draft of the report said that there has been a release, which highlights a mismatch between SDAP's and ASF's idea of a release; education is needed. * SDAP's number 1 problem is their use of dev@. There is activity in the project (including commit messages going to dev@) but questions asked on dev@ go unanswered, and therefore conversations don't happen. Even the report is drafted on private@ rather than dev@. I think I can work with SDAP and get them to graduate but only if they engage on dev@. * I have given notice that I will resign as a mentor by Dec 31st if I don't see activity, namely a plan to graduate, and activity to carry out that plan.
  •  (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:

  1. Make sure all PPMC vote the next release with detailed items
  2. Make sure all PPMC have their GitHub account connected to ASF ID>

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 continue to receive lots of traction from users and we keep answering questions in Gitter chat and mailing list

How has the project developed since the last report?

We made a release in August and have added lots of new features since then. We plan to release the next version this month.

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:

2022-08-30

When were the last committers or PPMC members elected?

2022-08-31

Have your mentors been helpful and responsive?

All good here

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

All good here

Signed-off-by:

  •  (sedona) Felix Cheung
    Comments: Community has gone through two rounds of graduation votes - it will be a good idea to set out the plan on getting to graduation, laying out the items to be resolved etc.
  •  (sedona) Jean-Baptiste Onofré
    Comments:
  •  (sedona) George Percivall
    Comments:
  •  (sedona) Von Gosling
    Comments: near to graudation, come on.
  •  (sedona) Sunil G
    Comments:

IPMC/Shepherd notes:


StreamPark

StreamPark is a streaming application development platform.

StreamPark has been incubating since 2022-09-01.

Three most important unfinished issues to address before graduating:

  1. fix X-category dependencies issues and Make first StreamPark release at Apache
  2. Establish better development specifications and improve official website documentation
  3. Attract more active contributors and committers to build a diverse 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?

  1. added 2 new committer, added 9 new contributors, the total contributors is 82 now
  2. Important issues have been discussed in email list
  3. preparing tow topics for the meetup (Flink forward 2022)

How has the project developed since the last report?

Since the last report, Many new features have been added, the front-end of the project has been refactored based on vue3, the new ui has been unanimously affirmed by the community members, Now we are preparing for the first Apache release, many features will be released in our first Apache release.

How would you assess the podling's maturity?

Please feel free to add your own commentary.

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

Date of last release:  

No release yet

When were the last committers or PPMC members elected?

2022-10-24 We elected Rui Fan as a StreamPark committer 2022-10-24 we elected Sizhu Wang as a StreamPark committer

Have your mentors been helpful and responsive?

Yes, always responsive and helpful.

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

We are starting

Signed-off-by:

  •  (streampark) tison
    Comments:
  •  (streampark) Willem Ning Jiang
    Comments:
  •  (streampark) Stephan Ewen
    Comments:
  •  (streampark) Thomas Weise
    Comments:
  •  (streampark) Duo Zhang
    Comments: Let's try to make our first release!

IPMC/Shepherd notes:


Teaclave

Teaclave is a universal secure computing platform.

Teaclave has been incubating since 2019-08-20.

Three most important unfinished issues to address before graduating:

  1. Improve project structure and documentation.
  2. Grow the community. (attracting more committers, contributors, users)
  3. Publish Apache releases. (resolving logistics on Apache 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?

Since the last report, we are pleased to receive project donation proposals from external teams. They want to donate their JavaEnclave project to Teaclave. We are facilitating the donation process.

We also have two new PPMC members elected since the last report:

  • 2022-08-16: Yuan Zhuang (volcano0dr)
  • 2022-08-17: Ran Duan DemesneGH)

How has the project developed since the last report?

Here are the summaries of recent progress of our three sub-projects:

Teaclave Faas Platform

v0.4.0 new changes:

  • Merged PRs:

<https://github.com/apache/incubator-teaclave/pulls?q=is%3Apr+is%3Aclosed+me rged%3A2022-05-01..2022-10-23+base%3Amaster+>

Teaclave TrustZone SDK

v0.2.0 new changes:

  • Add tls server/client example
  • Add signature verification example
  • Add Building Rust CA as Android ELF documentation
  • Add Expanding TA Secure Memory on QEMUv8 documentation
  • Merged PRs:

<https://github.com/apache/incubator-teaclave-trustzone-sdk/pulls?q=is%3Apr+ is%3Aclosed+merged%3A2022-05-01..2022-10-23+base%3Amaster+>

Teaclave SGX SDK

Since the last report, this project is developing v2.0 and maintaining v1.1.

v2.0 is a revamped version. It is much more developer friendly compared to v1.1.

  • Supports cargo build + no_std, xargo build and cargo-std-aware mode.
  • Refactored Intel's SDK using Rust. Only a small portion of Intel's SDK is required.
  • Improved testing framework. sgx_tstd is well tested now.
  • No need to maintain 100+ 3rd party dependencies. Most dependencies are use-able without any change.
  • Branch: https://github.com/apache/incubator-teaclave-sgx-sdk/tree/v2.0.0-preview

v1.1 new changes:

  • Version bump to 1.1.6
  • Support rust-nightly-2022-10-22
  • Version bump to 1.1.5
  • Support intel sgx sdk 2.17.1 and and DCAP 1.14
  • Support rust-nightly-2022-02-23
  • Fix thread_local macro
  • Merged PRs:

<https://github.com/apache/incubator-teaclave-sgx-sdk/pulls?q=is%3Apr+is%3Ac losed+merged%3A2022-05-01..2022-10-23+base%3Amaster+>

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:

2022-04-18

When were the last committers or PPMC members elected?

  • 2022-08-16: Yuan Zhuang (Apache ID: yuanz), PPMC
  • 2022-08-17: Ran Duan (Apache ID: rduan), PPMC

Have your mentors been helpful and responsive?

Yes, our mentors work responsively to help us with electing new mentors, developing new features, fixing bugs, and expanding the community.

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

We don't find any 3rd parties incorrectly using the podling's name and brand. The VP, Brand has approved the project name. (PODLINGNAMESEARCH-175)

Signed-off-by:

  •  (teaclave) Felix Cheung
    Comments:
  •  (teaclave) Furkan Kamaci
    Comments:
  •  (teaclave) Jianyong Dai
    Comments:
  •  (teaclave) Matt Sicker
    Comments:
  •  (teaclave) Zhijie Shen
    Comments:
  •  (teaclave) Gordon King
    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:

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?

With the release of Apache Toree 0.5.0-incubating we have had a few questions about the removal of the support for Python/R and we have explained the reason before that a couple more times.

We still see much of the users asking questions in the gitter channel rather than using the mailing lists.

How has the project developed since the last report?

After support for Scala 2.12 and Spark 3.x we will need to start looking ahead for supporting Scala 2.13.x as some users have been already asking for that on the project gitter channel.

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:

2022-04-11

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?

None

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

No Trademark issues

Signed-off-by:

  •  (toree) Luciano Resende
    Comments: With my contributor hat, I am planning to try to move Toree trough graduation on the next couple months
  •  (toree) Julien Le Dem
    Comments:
  •  (toree) Ryan Blue
    Comments:
  •  (toree) Weiwei Yang
    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:

  1. Restart the Community
  2. Start doing releases
  3. Make Apache Training more well known

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

Currently the activity dropped to an all-time low. We even missed a number of reports. We had a discussion on the mailinglist, if we should aim for giving up, however the responses encouraged us to give it a new try and we are currently trying to restart the project as there is indeed some interest in the project.

How has the community developed since the last report?

It hasn't developed well, but we're hoping to change that with few players willing to participate more recently.

How has the project developed since the last report?

We had one talk at ApacheCon NA 2022 and it was pretty well attended … however not very many new folks showed up here.

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-03 Presenation on NavigatingASFIncubation

When were the last committers or PPMC members elected?

2020-11-23 Gautam Gupta (Comitter)

Have your mentors been helpful and responsive?

Admittedly nothing has happened, so nothing has been falling through any cracks, however we missed some board reports, which are now being written by one of the mentors.

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

No issues.

Signed-off-by:

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

IPMC/Shepherd notes:

DF. Why not graduate?


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:

  1. Getting the community informed about TLPs and charters

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

None.

How has the community developed since the last report?

The community has been relatively quiet. One bug report made by an end user, and several patches came together to create a nice new release.

We have had two threads on graduation on private list, and about to kick an official graduation vote on the dev list.

How has the project developed since the last report?

Some changes to the modules, specifically moving some code to Kotlin.

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:

2022-10-08

When were the last committers or PPMC members elected?

Stefan Pingel and Sally MacFarlane are both elected as committers on 2022-05-12.

Have your mentors been helpful and responsive?

All good.

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

No problems.

Signed-off-by:

  •  (tuweni) Jean-Baptiste Onofré
    Comments: Tuweni is discussing graduation, I think it makes sense.
  •  (tuweni) Furkan Kamaci
    Comments:
  •  (tuweni) Antoine Toulme
    Comments:
  •  (tuweni) Dave Fisher
    Comments:

IPMC/Shepherd notes:


 






  • No labels