Incubator PMC report for November 2021

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 37 podlings incubating. In June and August, podlings executed 10 distinct releases. We added 2 new IPMC members, and none retired.

There was 4 IP clearance in June and August. A couple of new podlings are under discussion, and Kyuubi and Linkis have joined the Incubator. Pinot graduated last month.

A couple of podlings are heading towards graduation in the next few months. This month we were missing reports from Annotator, Milagro and Toree, and they will be asked to report next month.

There was a lengthy discussion on the IP clearance for Terraform as information around the donation, IP and licensing was initially unclear but was eventually resolved.

There was also a discussion about IP provenance of files in the Tuweni release and the Hop release.

Some updates were made to the podling retirement guide. As usual, most discussions on the mailing list were around graduations, releases, new project proposals and new mentors.

Community

New IPMC members:

• none

People who left the IPMC:

• none

New Podlings

• none

Podlings that failed to report, expected next month

• Livy
• PageSpeed
• SDAP
• Toree
• Training

Graduations

• None

The board has motions for the following:

• None

Releases

The following releases entered distribution during the months of October and September:

• BRPC 1.0.0
• Hop 1.0.0
• InLong 0.10.0
• Kyuubi 1.3.0
• Kyuubi 1.3.1
• Sedona 1.1.0
• Shenyu 2.4.1  

IP Clearance

• Apache AsterixDB - JDBC Driver
• Apache Daffodil VSCode Debugger

Legal / Trademarks

N/A

Infrastructure

N/A

Table of Contents

DataLab
Doris
EventMesh
Heron
Kyuubi
MXNet
NLPCraft
Sedona
Spot
Tuweni

DataLab

DataLab is a platform for creating self-service, exploratory data science environments in the cloud using best-of-breed data science tools.

DataLab has been incubating since 2018-08-20.

Three most important unfinished issues to address before graduating:

1. Finish preparing all artifacts necessary for graduation

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

No issues

How has the community developed since the last report?

It’s not completed yet. We have just started two processes of voting for the new committers.

How has the project developed since the last report?

• We are working towards the release 2.5.1
• Bug fixing

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: working towards next release

Date of last release:  

2021-09-08

When were the last committers or PPMC members elected?

The last committer was elected on June 22, 2021

Have your mentors been helpful and responsive?

Yes, our mentors are very helpful and responsive.

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

There are no known brand and naming issues.

Signed-off-by:

•  (datalab) P. Taylor Goetz
  Comments:
•  (datalab) Henry Saputra
  Comments:
•  (datalab) Konstantin I Boudnik
  Comments:
•  (datalab) Furkan Kamaci
  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:

1. Code refactor to reduce references to other project code.
2. The official website need to be updated to meet the requirement of ASF.
3. Some unofficial code repos or mirrors names related to Doris need to be processed.

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

The main branding issue has been addressed(DorisDB renamed to StarRocks).

How has the community developed since the last report?

Since the last report, we have added 30 contributors. There are currently 213 contributors and 29 committers.

How has the project developed since the last report?

1. We are working on release 0.15

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

When were the last committers or PPMC members elected?

1. zhangjiafeng, committer, 2021-09-24
2. lihaopeng, committer, 2021-11-08
3. xuyang, committer, 2021-09-24

Have your mentors been helpful and responsive?

All mentors are very helpful!

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

Yes

Signed-off-by:

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

IPMC/Shepherd notes:

EventMesh

EventMesh is a dynamic cloud-native basic service runtime used to decouple the application and middleware layer.

EventMesh has been incubating since 2021-02-18.

Three most important unfinished issues to address before graduating:  

1. Gain more active contributors/committers to build a diverse community
2. Make Apache releases regularly and keep the quality for all releases
3. Improve project structure and documentation

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?

1. Serveral new contributors added
2. Participated in several online and offline conferences to share eventmesh
3. One-week meeting is scheduled for serveral months by tencent meeting
4. Serveral blogs were delivered on wechat public account、infoq、思否、csdn、开源中国等

How has the project developed since the last report?

v1.3.0 is nearing 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:

2021-08-11

When were the last committers or PPMC members elected?

2021-02

Have your mentors been helpful and responsive?

yes

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

yes

Signed-off-by:

•  (eventmesh) Francois Papon
  Comments:
•  (eventmesh) Junping Du
  Comments:
•  (eventmesh) Jean-Baptiste Onofré
  Comments:
•  (eventmesh) Justin Mclean
  Comments:
•  (eventmesh) Von Gosling
  Comments:

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. Fixing the OSX build (ease of use/adoption)
3. Add new convenience binaries to be distributed after a successful release. E.g. Helm charts, CentOS Docker image

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.
• We had a few more discussions about kubernetes support and made some progress in having new people contribute code

How has the project developed since the last report?

• Heron has had many improvements to the help the project be more cloud native.
• Many improvements have been related to kubernetes support.

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/05/26: 0.20.4-incubating

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?

• We’ve recently added Ming and Kevin to help with mentorship. They have been extremely helpful.

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: The PPMC is managing the brand and the name was approved years ago
•  (heron) Ming Wen
  Comments:
•  (heron) Kevin Ratnasekera
  Comments:

IPMC/Shepherd notes:

Kyuubi

Kyuubi is a distributed multi-tenant Thrift JDBC/ODBC server for large-scale data management, processing, and analytics, built on top of Apache Spark and designed to support more engines.

Kyuubi has been incubating since 2021-06-21.

Three most important unfinished issues to address before graduating:

1. Gain more active contributors/committers to build a diverse community
2. Make Apache releases regularly and keep the quality for all releases
3. Improve project structure and 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?

1. 4 new contributors participate in the community since the last one. There are currently 50 contributors and 9 committers.
2. 26 authors have pushed 99 commits to master and 113 commits to all branches. On master, 227 files have changed and there have been 7,240 additions and 2,676 deletions.
3. Several discussions/bug reports on the GitHub Issues/WeChat groups, etc.
4. Participate in 1 off line meetup (Apache Hadoop Meetup 2021, Beijing, China) to promote the project.

How has the project developed since the last report?

1. We have released 1.3.1-incuabating in 2021 Oct 25
2. the community is working on implementation of RESTful API
3. Z-Order Support under dev
4. Flink engine support in progress

How would you assess the podling's maturity?

Please feel free to add your own commentary.

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

Date of last release:

2021-10-25

When were the last committers or PPMC members elected?

No new committer added yet

Have your mentors been helpful and responsive?

No answer.

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

No answer.

Signed-off-by:

•  (kyuubi) Willem Ning Jiang
  Comments:
•  (kyuubi) Jeff Zhang
  Comments:
•  (kyuubi) Duo Zhang
  Comments:
•  (kyuubi) Akira Ajisaka
  Comments:

IPMC/Shepherd notes:

MXNet

A Flexible and Efficient Library for Deep Learning

MXNet has been incubating since 2017-01-23.

Three most important unfinished issues to address before graduating:

1. Successfully and smoothly make releases without WIP disclaimer.
   • ONGOING.

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

No blocking issue.

How has the community developed since the last report?

• The number of GitHub contributors increased to currently 967

• Active blogs and social media presence

  • Medium (https://medium.com/apache-mxnet) w/ 2k followers (+1%)

• Active video channels

  • YouTube channel (https://www.youtube.com/apachemxnet) w/ 1.49k subscriber (+2% since last report)
  • Chinese YouTube channel (https://www.youtube.com/channel/UCjeLwTKPMlDt2segkZzw2ZQ) w/ 6.96k subscribers (+3%)

• Highlights in MXNet ecosystem

  • GluonCV v0.10.0 release (https://github.com/dmlc/gluon-cv/releases/tag/v0.10.0)
  • GluonNLP MX2 NumPy version (https://github.com/dmlc/gluon-nlp/tree/master)
  • GluonTS v0.8.1 release (https://github.com/awslabs/gluon-ts/releases/tag/v0.8.1)
  • DeepInsight (https://github.com/deepinsight/insightface)
  • Sockeye 2.3.24 release (https://github.com/awslabs/sockeye)

How has the project developed since the last report?

1. 1.9.0 release is in progress. 1.9.0 release is going through rc8 after a thorough review on the licenses from the community and PPMC. https://github.com/apache/incubator-mxnet/releases/tag/1.9.0.rc8 with 100+ patches of new features, improvements, and fixes. This will be the first recent release without DISCLAIMER-WIP.
2. 2.0.0 development is close to completion. MXNet 2.0 features interoperable ML and DL programming with Array API standard implementation. This project aims to make array libraries like NumPy, MXNet, Pytorch more interoperable. Besides standardized operators, new methods and mechanism will be introduced to improve the interoperability. 1) in MXNet2.0, Context class and some related array methods like as_in_ctx will be replaced by Device and to_device to reduce the learning curve for new users. 2) The improved DLPack API in MXNet leverages the syncobject introduced in Async GPU dependency engine and can well handle the cuda stream to improve the array libraries interoperability on different devices.
3. Github statistics of last month:
   • October 6, 2021 – November 6, 2021: Excluding merges, 17 authors have pushed 49 commits to master and 58 commits to all branches. On master, 466 files have changed and there have been 17,398 additions and 11,371 deletions.

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

When were the last committers or PPMC members elected?

2021-11-03

Have your mentors been helpful and responsive?

Yes.

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

Yes. From past brand usage review for MXNet third-party distributions, we found several listings on AWS marketplace that needed update. The PPMC reached out to the publishers of these listings for correction and fixed them. In recent review, we found the following three entries to have regression in branding and have reached out to them again.

https://aws.amazon.com/marketplace/pp/prodview-7nxhayhlbxwam (pending update) https://aws.amazon.com/marketplace/pp/prodview-wktuc2vochjwe (pending update) https://aws.amazon.com/marketplace/pp/prodview-dpniaffpcxfhc (pending update)

Signed-off-by:

•  (mxnet) Markus Weimer
  Comments:
•  (mxnet) Bob Paulin
  Comments:
•  (mxnet) Jason Dai
  Comments:
•  (mxnet) Furkan Kamaci
  Comments:
•  (mxnet) Kezhen Xu
  Comments:
•  (mxnet) Atri Sharma
  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. Stable 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?

We had several active collaborators since the last report, specifically working on our Python support. We expect them to reach the committer level soon. However, the Python support in NLPCraft will like undergo the architectural change that may delay this process.

How has the project developed since the last report?

NLPCraft community decided to make a deep refactoring in the project based on the initial user feedback. The primary goal here is to significantly simplify the usage patterns and provide better support for human curation and dialog support. The design & planning for this refactoring resulted in low commit activity in the last 60 days.

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?

Same as the last report - no new committers.

Have your mentors been helpful and responsive?

Mentors feedback delay is improving but still takes about a week to get responses on vote emails.

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

No issues here.

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:

SDAP

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

SDAP has been incubating since 2017-10-22.

Three most important unfinished issues to address before graduating:

1. Make official SDAP (Incubating) Release

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 continue.

How has the project developed since the last report?

Completed Issues:  

• SDAP-217 Add ingest processor to flip tiles vertically
• SDAP-343 Fix reading of time stamp in GPM data
• SDAP-351 Fix reading of data with cftime.datetime.Gregorian type
• SDAP-354 Add initial version of in situ data services to Apache GitHub
• SDAP-327 New multivariable reading processors missing from granule ingester module
• SDAP-355 Update matchup parameter and output to use primary and secondary
• SDAP-353 Update match-up output to only return variables that are provided by the source e.g. for ASCAT only return winds variables
• SDAP-338 Update match up implementation to support multi-variable tiles
• SDAP-315 Update match up algorithm for satellite to satellite
• SDAP-311 Collect performance metrics in current match-up algorithm
• SDAP-312 Optimize reprojection to UTM in matchup algorithm
• SDAP-305 Get current match up working with AVHRR OI data that is currently ingested in the bigdata cluster

New/Updated Issues:

• SDAP-303 Add Elasticsearch support for metadata store in Nexus webapp & ningester
• SDAP-347 Add day_of_year_i field in Tile class
• SDAP-162 Create build for nexus-webapp
• SDAP-352 Fix tile artifact in GPM time averaged map
• SDAP-326 Make ingest processors optional in incubator-sdap-ingestor
• SDAP-319 Fix misleading comment in helm/values.yaml
• SDAP-318 TimeSeriesSpark returns empty list for bounding box larger than a hemisphere.
• SDAP-316 Update webapp to python version 3 in helm chart.
• SDAP-346 PySpark environment variables incorrectly set
• SDAP-345 Add ability to read time stamp from the filename
• SDAP-344 Add ability to read time stamp from global attributes
• SDAP-342 Update webapp to use spark 3.1.1
• SDAP-321 Allow wildcards in S3 paths for collections
• SDAP-350 Question about described bug in aiomultiprocess
• SDAP-324 Kelvin to Celsius processor not working during ingest after adding support for multiple variables
• SDAP-323 Update summarizing processor and Solr schema to support multiple variables
• SDAP-322 Add support for ingestion of data with multiple variables
• SDAP-332 Add OpenAPI specification for data matchup related endpoints
• SDAP-339 Granule ingestion pod needs a way to fetch new AWS access key for reading data from Earthdata Cloud archive
• SDAP-349 Inefficient swath tile causes memory issues
• SDAP-341 Terraform deployment of Kubernetes and Spark cluster
• SDAP-320 Integrate 1.1.0-SNAPSHOT work into SDAP
• SDAP-357 As an administrator, I would like SDAP to support multiple s3 buckets, with different credential for each
• SDAP-356 ingress does not find loadbalancer on AWS, 404 error
• SDAP-340 allow null when standard_name is missing

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?

One new member was invited to the PPMC in August 2021.

Have your mentors been helpful and responsive?

Trevor has been a very helpful mentor

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

PPMC is not aware of any issues

Signed-off-by:

•  (sdap) Jörn Rottmann
  Comments:
•  (sdap) Trevor Grant
  Comments: Looking good- this note is to the board are there any other Python first projects we can look to for guidance on Python releases. IF this project had versions, it would be v1+ as it is in prod at various US Government agencies.

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. Inviting new committers and PMC members
2. Find alternative release manager

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

All good here

How has the community developed since the last report?

The community is growing fast. Our releases under the ASF brand now have reached 400k downloads per month.

How has the project developed since the last report?

We published one more release 1.1.0-incubating in October.

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

When were the last committers or PPMC members elected?

N/A

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

1. Revive community activity (Discussion in mailing lists, increase frequency of commits)
2. Create a new roadmap and release plan that will improve adoption
3. Make it easier to contribute to the project (eg, documentation, framework)

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

We last reported on June 2021. Our ordinarily scheduled quarterly report was due in October 2021. The ASF board meeting notes for October 2021 noted that the report reminders did not go out, and so we did not report as expected. We were expected to report for November 2021. On November 6, 2021, we were informed that our quarterly report was due to be completed on November 3, 2021. Therefore, this report is being done quickly, to do as much as possible to comply with ASF expectations. Regrettably this means this is being done with minimum community discussion.

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 for 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?

Our mentor has been helpful. However, we notice the board has suggested we request an additional mentor to help us keep on top of things. We will undertake this for the next quarter.

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

Yes

Signed-off-by:

•  (spot) Uma Maheswara Rao G
  Comments: I don't think this project is anywhere near to graduation. And I don't see any noticeable activities in mailing lists. This project needs additional mentors.

IPMC/Shepherd notes:

ShenYu

ShenYu is a high performance Microservices API gateway in Java ecosystem, compatible with a variety of mainstream framework systems, supports hot plug. Users can write their own plugin meet the current requirement and future needs in a variety of scenarios, especially in large-scale scenes.

ShenYu has been incubating since 2021-05-03.

Three most important unfinished issues to address before graduating:

1. Make an Apache Release.
2. Build new website document.
3. Building a diverse community with open governance.

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 and 1+ new PPMC participate in the community since entered the last report. There are currently 211 contributors and 26 committers.
• 50+ pull request since entered the last report
• There is regular traffic on the mailing list (~40+ mailing list discussions/month).
• Number of GitHub stars increased (last report: 5341, currently: 5440).
• Held 2 community meetings to discuss development tasks and how to build an open governance community.

How has the project developed since the last report?

• release 2.4.1.
• Support external cross filter config.
• Implement the async dubbo invoking for alibaba-dubbo.
• Refactor shenyu client.
• Add uri plugin.
• Add agent classloader.

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:

Oct 2021.

When were the last committers or PPMC members elected?

Oct 2021.

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:

•  (shenyu) Willem Ning Jiang
  Comments:
•  (shenyu) Jincheng Sun
  Comments:
•  (shenyu) Duo Zhang
  Comments:
•  (shenyu) Kevin Ratnasekera
  Comments:
•  (shenyu) Atri Sharma
  Comments:
•  (shenyu) Justin Mclean
  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:

1. More contributors!
2. Getting started, docs, videos
3. 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?

Some development happened, mainly a new JSON-RPC proxy module for Ethereum clients.

How has the project developed since the last report?

The project is under active development.

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

When were the last committers or PPMC members elected?

Nicolas Melendez as committer on 2021-05-06.

Have your mentors been helpful and responsive?

No problems.

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

No problems reported.

Signed-off-by:

•  (tuweni) Jean-Baptiste Onofré
  Comments:
•  (tuweni) Furkan Kamaci
  Comments:
•  (tuweni) Antoine Toulme
  Comments:

IPMC/Shepherd notes: