bpDRAFT 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 September 07Podling reports due by end of day
Sun September 11Shepherd reviews due by end of day
Sun September 11Summary due by end of day
Tue September 13 Mentor signoff due by end of day
Wed September 14

Report submitted to Board

Wed September 21Board meeting


Shepherd Assignments

XXXXXX






















































Incubator PMC report for September 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 34 podlings incubating. Podlings made 5 distinct releases.

This month we were missing reports from Livy, SDAP, Spot, Teaclave, and Toree. All will be asked to report next month. Marvin-AI and PonyMaill don't have mentors' signoff and will also be asked to report next month. PonyMail has only one mentor and had three missed signoffs.

StreamPark has joined the Incubator, although have some X category dependencies issues, it's nice that the team has preliminary plans to address them. Hivemall has passd retired VOTE. Some other podlings, like Livy, will retire next few months.  

The SkyWalking community released a tool called skywalking-eyes. It's a full-featured license tool to check and fix license headers and resolve dependencies' licenses. Besides, it offers various language support. but be careful， automated tools could help the project a lot and be a time saver for this work. but they can't fit all problems.

MxNet is about to graduate and it has tackled some branding issues on the eve of graduation.

Community

New IPMC members:

  • Zhongyi Tan

People who left the IPMC:

  • None

New Podlings

  • StreamPark

Podlings that failed to report, expected next month

  • Livy
  • Marvin-AI
  • PonyMail
  • SDAP
  • Spot
  • Teaclave
  • Toree

Graduations

  • MXNet The board has motions for the following:
  • MXNet

Releases

The following releases entered distribution during the month of August:

  • Sedona 1.2.1
  • EventMesh 1.6.0
  • DevLake 0.1.2.0
  • SeaTunnel 2.1.3
  • Kvrocks 2.1.0  

IP Clearance

  • None

Legal / Trademarks

Infrastructure

Miscellaneous

Credits

Calvin Kirs

Table of Contents

Annotator
brpc
DataLab
EventMesh
Flagon
Kvrocks
Kyuubi
Milagro
Nemo
PageSpeed
Pegasus
PonyMail
Sedona
StreamPipes
Training
Uniffle
Wayang

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:

  1. Incubation issues found by Whimsy. Some look correct (i.e. are pending action from us). Others are things we did when we joined the Incubator.
    • No Software Grant and No IP Clearance Filed - this was done at the onset of incubation iirc.
    • No Release Yet/Missing ASF Copyright Headers on Source Code - we have made releases, but apparently missed getting headers on everything.
    • No Release Yet/Binary has licensing issues - this is likely caused by the above.
    • No Podling Name Search on file - we're looking into how to initiate that process.
  2. We need more (active) mentors...still.
  3. Our release process is still cumbersome/lengthy, so we release rarely.

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

We would like to initial the podling name search if possible. Additional mentors would also be helpful.

How has the community developed since the last report?

We've added Richard Eckart de Castilho (rec) to the PPMC to help with voting and hopefully liaison with UIMA in which is also a member.

How has the project developed since the last report?

We are working to release an 0.3.0 release. The code has been ready for sometime, but we face cross-platform build issues and other annoyances which have held it back.

We have also learned that Apache Annotator (despite it's pre-1.0 release status) is already in use in a production ereader web app for epubs.

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 - we believe we could be close to this in a few months pending clarifying the items above.
  •  Other:

Date of last release:

2022-05-05

When were the last committers or PPMC members elected?

2022-08-17

Have your mentors been helpful and responsive?

Voting involvement is still too low for us to easily turn around a release or the addition of a committer without personally hunting folks down. Similarly, getting mentor involvement looks similar--direct requests for input made via additional emails or IRC pings.

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

There are no known branding uses of any kind--good or bad.

Signed-off-by:

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

IPMC/Shepherd notes:

brpc

brpc is an industrial-grade RPC framework for building reliable and high- performance services.

brpc has been incubating since 2018-11-13.

Three most important unfinished issues to address before graduating:

  1. Attract more committer
  2. Regular Apache Release by more release manager
  3. Fix Branding Issue

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?

We add two committers， they are Wang Xiaofeng，Hu Xiguo。
And we add 3 PPMC members ，they are Cai Daojin，Helei，Lilei.

we particpated in ApacheCon Asia 2022, PPMC Wang Weibing was the co-chair of the RPC track.
there were about 3 sessions in that track.

How has the project developed since the last report?

brpc 1.2.0 has been released by a new release manager ---liu shuai,
which add apple m1 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:

2022-08-03

When were the last committers or PPMC members elected?

2022-07-18

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.

we invited our mentor Pan Juan to join our offline dinner meeting on Oct 4th, she gave me many suggestion about graduation, including discussing more in the mail list. we quite appreciate these ideas, and follows her suggestion accordingly.

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?

I create an issue to registe brpc's branding, here it is.   https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-202 but there is no reply for it.

Signed-off-by:

  •  (brpc) Jean-Baptiste Onofré
    Comments:
  •  (brpc) Von Gosling
    Comments:
  •  (brpc) Juan Pan
    Comments: It looks that we have more fellow joined, nice!

IPMC/Shepherd notes:

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 graduation as a TLP.

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?

We have a new committers Oleksandr Polishchuk and Tetiana Polyvana.

How has the project developed since the last report?  

  • We are working towards next release.
  • Support of image management (in progress).
  • Adding a new Compute Engine - Azure HDInsight(in progress).
  • Filter function enchantment for image page(done).
  • Update third-parties like Jupyter, TensorFlow (done).
  • 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:

2022-01-27

When were the last committers or PPMC members elected?

The last committer was added on July 22, 2022.

Have your mentors been helpful and responsive?

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) Furkan Kamaci
    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.More frequent code contributions

2.A steady release process   3.Growing the community: more committers, more use cases

 

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?

About 90 contributors involved till now

GSoc,OSPP,and 8 SIG are in progressing

How has the project developed since the last report?

1.6.0 released

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

When were the last committers or PPMC members elected?

2022-09-05

Have your mentors been helpful and responsive?

Mentors were all very nice and helpful.  

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:

Flagon

Flagon is a software tool usability testing platform

Flagon has been incubating since 2016-07-13.

Three most important unfinished issues to address before graduating:

  1. Continue VOTE thread for Graduation on general@incubator

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

None at this time.

How has the community developed since the last report?

  1. Enrolled new committers (x4), including one new PPMC
  2. Completed new CCLA, SW grant from University of Maryland
  3. Addressed lingering issues raised in graduation VOTE (deprecated projects, unsubscribed PPMC)

How has the project developed since the last report?

  1. Onboarding new SW Grant (Distill) into project, driving toward release
  2. New community driven developments
  3. Continued Maintenance

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-05-19 Apache Flagon UserALE.js 2.3.0

When were the last committers or PPMC members elected?

  • Kelsey Rassmann (6/2022)
  • Kymani Brown (6/2022)
  • Amir Ghaemi (6/2022)
  • Austin Bennett (5/2022)

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.

Generally, Mentors remain supportive. Although JUL report was not signed by Mentors (was posted to Dev).

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:

  •  (flagon) Lewis John McGibbney
    Comments:
  •  (flagon) David Meikle
    Comments:
  •  (flagon) Tim Allison
    Comments:
  •  (flagon) Furkan Kamaci
    Comments: I was on summer vacation and did not have a chance to check the JUL report. It may be the reason for the other mentors as well.

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.

Three most important unfinished issues to address before graduating:

Promote the project and grow the user and dev 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?

We got 5 new contributors since the last report. Also, in order to let more guys know Kvrocks community, we had a share on ApacheCon Asia 2022 and are preparing a promotional article that will be published on the OSCHINA platform.

How has the project developed since the last report?

  1. We completed the first Kvrocks release at Apache.
  2. We created the Apache Kvrocks website and added some documents to help users study Kvrocks.
  3. Our focus is still on improvements and bug fixes, which included optimizing CI and using LuaJIT to improve performance of the Lua script. We've also added a new data type STREAM and added some new commands which have been supported since Redis 6.2.  

How would you assess the podling's maturity?

Please feel free to add your own commentary.

  •  Initial setup
  •  Completed first release
  •  Community building
  •  Nearing graduation
  •  Other: working towards next release

We just completed the first release and need to keep working on improving Kvrocks to make it more stable and easy to use.

Date of last release:

2022-08-03 We made the firsts Apache release with version 2.1.0.

When were the last committers or PPMC members elected?

2022-06-13 We elected PragmaTwice 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 do many contributions to Kvrocks.

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

No 3rd parties used the podling and brand. Will move forward to send the project name audit request.

Signed-off-by:

  •  (kvrocks) Jean-Baptiste Onofre
    Comments:
  •  (kvrocks) Xiaoqiao He
    Comments:
  •  (kvrocks) tison
    Comments:
  •  (kvrocks) Von Gosling
    Comments:
  •  (kvrocks) Liang Chen
    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?

  • Adds three new Committers, there are currently 88 contributors and 17 committers, 9 PPMC members.
  • Several discussions/bug reports on the GitHub Issues/WeChat groups, etc.
  • Our PPMC member, Fei Wang, participated ApacheCon Asia 2022 and gave a talk about kyuubi's success @eBay

How has the project developed since the last report?

  • Released v1.5.2-incubating on 2022-06-18
  • Voting v1.6.0-incubating in the general list which resolves about 700 tickets

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

When were the last committers or PPMC members elected?

  • 2022-06-21 Shaoyun Chen
  • 2022-07-20 Min Zhao
  • 2022-07-26 Qingbo Jiao

Have your mentors been helpful and responsive?

  • Mentors are helpful and always responsive.

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

Yes

Signed-off-by:

  •  (kyuubi) Willem Ning Jiang
    Comments:
  •  (kyuubi) Jeff Zhang
    Comments:
  •  (kyuubi) Duo Zhang
    Comments:
  •  (kyuubi) Akira Ajisaka
    Comments: It's great to add new PPMC members. I agreed with the report that Kyuubi is nearing graduation.

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?

 Administrative tasks are still outstanding due to members' other  commitments and the pandemic. These include in particular, a PPMC  meeting to discuss the project roadmap needs to be arranged,  confirmation that the project's Whimsy, Clutch, SVN, Confluence  & Committers pages are all current, and the code signing keys  needs countersigning. Investigations into a redirect on Milagro's  home page is still outstanding.

How has the community developed since the last report?

No change.

How has the project developed since the last report?  

Swagger site on the Milagro homepage has been updated to solve an XSS issue. MPC repo's readme has been updated to simplify build and test instructions in preparation for its first Apache Release. Investigation into a Travis issue is ongoing.

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?

No issues except previous report sign off was missed.

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:

Nemo

Nemo is a data processing system to flexibly control the runtime behaviors of a job to adapt to varying deployment characteristics.

Nemo has been incubating since 2018-02-04.

Three most important unfinished issues to address before graduating:

  1. Complete the remaining items in the Apache Maturity model
  2. Grow the 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?

  • Hosting a GSoC student working on stream processing
  • Working on a new release

How has the project developed since the last report?

  • Added installation scripts for ease of use
  • Improved stream processing metrics
  • Added additional stream application examples
  • Added network profiling scripts
  • Updated library versions
  • Upgraded the CI with new platforms

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-12-07

When were the last committers or PPMC members elected?

September 28, 2021

Have your mentors been helpful and responsive?

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

Our mentors have been helpful and responsive.

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 manages the podling's brand / trademarks.

Signed-off-by:

  •  (nemo) Hyunsik Choi
    Comments:
  •  (nemo) Byung-Gon Chun
    Comments:
  •  (nemo) Jean-Baptiste Onofré
    Comments:
  •  (nemo) Markus Weimer
    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:

1.Grow the number of active developers

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

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

How has the community developed since the last report?

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

How has the project developed since the last report?

Minor activity. notably, ngx_pagespeed's build broke as of nginx 1.23, a fix was contributed addressing this in a backwards compatible manner.

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:

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.

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.

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:

  1. Grow the community(attracting more committers, contributors, users).
  2. Make more releases in ASF policy regularly.
  3. Improve the Pegasus project performance, stability, and usage scenarios.

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

None

How has the community developed since the last report?

  • Attracted more active contributors.
  • Invited a new committer(Dan Wang).
  • Made two Pegasus related speeches on ApacheCon Asia 2022.

How has the project developed since the last report?

The underlying library (XiaoMi/rDSN) project has been migrated to the main repository, and we have resolved all the license problems we found, it has been fully discussed on maillist.

We are planning to release 2.4.0.

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

When were the last committers or PPMC members elected?

2022-7-8, Dan Wang(GitHub ID: empiredan)

Have your mentors been helpful and responsive?

Yes, our mentors gave us a lot of help, including IP clearance, version release, and etc.

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

No issues that we are aware of.

Signed-off-by:

  •  (pegasus) Duo zhang
    Comments:
  •  (pegasus) Liang Chen
    Comments:
  •  (pegasus) Von Gosling
    Comments:
  •  (pegasus) Liu Xun
    Comments:

IPMC/Shepherd notes:

Pony Mail

Pony Mail is a mail-archiving, archive viewing, and interaction service, that can be integrated with many email platforms.

Pony Mail has been incubating since 2016-05-27.

Three most important unfinished issues to address before graduating:

  1. Growing 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?

No material change.

How has the project developed since the last report?

No change of note.

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

When were the last committers or PPMC members elected?

Sean Palmer was added as committer on 2021-04-02

Have your mentors been helpful and responsive?

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

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:

  •  (ponymail) John D. Ament
    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. All issues are fixed.

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

Our last release in general@incubator took 3 weeks to pass. Not many people are casting their votes.

How has the community developed since the last report?

Our monthly downloads have reached over 800K. We now have 82 contributors and 10 PPMC members.

How has the project developed since the last report?

We had 1 more release (1.2.1) and 1 more release manager.

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

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 Jean-Baptiste Onofré and Von Gosling are little too busy and hence are not very responsive. But since we will graduate soon, this is not an issue.

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

Yes, the VP has approved the project name.

Signed-off-by:

  •  (sedona) Felix Cheung
    Comments:
  •  (sedona) Jean-Baptiste Onofré
    Comments: I was busy during summer vacation time. I will be more active in this podling in the future.
  •  (sedona) George Percivall
    Comments:
  •  (sedona) Von Gosling
    Comments: It's lucky to cast the last vote in the latest release

IPMC/Shepherd notes:

StreamPipes

StreamPipes is a self-service (Industrial) IoT toolbox to enable non- technical users to connect, analyze and explore (Industrial) IoT data streams.

StreamPipes has been incubating since 2019-11-11.

Three most important unfinished issues to address before graduating:

  1. Release version 0.70.0
  2. Prepare graduation process

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

There are no issues right now.

How has the community developed since the last report?

  1. We had increased traffic on the mailing list during the last months
  2. Also, the user mailing list had more traffic with serveral users asking for help
  3. Several contributions and PRs from new contributors were made
  4. Number of Github stars increased (last report: 315, current: 338)  
  5. We will have a talk at ApacheCon NA

How has the project developed since the last report?

  1. The community has worked on several new features and improvements towards release 0.70.0
  2. For this release, we focused on bug fixes and improvements towards production usage
  3. Release 0.70. is currently under vote
  4. After the release, we plan to start discussion on graduation

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

When were the last committers or PPMC members elected?

2022-03-16

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, mentors are 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?

Name is approved and we are actively monitoring the brand.

Signed-off-by:

  •  (streampipes) Christofer Dutz
    Comments:
  •  (streampipes) Jean-Baptiste Onofré
    Comments: No report filled yet
  •  (streampipes) Julian Feinauer
    Comments:
  •  (streampipes) Justin Mclean
    Comments:
  •  (streampipes) Kenneth Knowles
    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. Reengaging the community
  2. Growing the community

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

Currently the activity in the project is almost not existent. We have tried getting people engaged with low hanging fruit, but without success. If this level of activity continues after ApacheCon (wehre we have a talk), we will probably initiate the process of retiring this posling.

How has the community developed since the last report?

Not at all.

How has the project developed since the last report?

Not at all. Some minor updates, but nothing noteworthy.

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:

training-tools 1.0.0: 14.09.2020

When were the last committers or PPMC members elected?

10.11.2020: Gautam Gupta (Committer)

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.

Nothing is happening, but we have been missing previous reports. We'll try to keep reporting on time till we possibly reactivate the community or build a new crowd, or we decide to retire the project,

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

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

We haven't started the name-search yet, however we'll do that as soon as we gain more activity.

Signed-off-by:

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

IPMC/Shepherd notes:

Uniffle

Uniffle is an unified Remote Shuffle Service

Uniffle has been incubating since 2022-06-06.

Three most important unfinished issues to address before graduating:

  1. Building the infrastructures, like website, documents, guidance for new contributors, etc.
  2. Doing a thorough license check.
  3. kicking off a first release.

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?

  1. 25 contributors from different affiliations contributed to Uniffle project.
  2. 55 issues have beed created, among this 24 were discussed and resolved.
  3. 4 discussions were occurred.

How has the project developed since the last report?

  1. 55 issues has been created, among this 24 issues were closed. 142 PRs has been created, among this 128 PRs were merged.
  2. Uniffle website has been created and published.
  3. The first release is undergone.

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:

NA

When were the last committers or PPMC members elected?

NA

Have your mentors been helpful and responsive?

Yes, they're very helpful in guiding the podling project.

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?

Yes.

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:

  •  (uniffle) Felix Cheung
    Comments:
  •  (uniffle) Junping Du
    Comments:
  •  (uniffle) Liu Xun
    Comments:
  •  (uniffle) Weiwei Yang
    Comments:
  •  (uniffle) Zhankun Tang
    Comments:

IPMC/Shepherd notes:

Wayang

Wayang is a cross-platform data processing system that aims at decoupling the business logic of data analytics applications from concrete data processing platforms, such as Apache Flink or Apache Spark. Hence, it tames the complexity that arises from the "Cambrian explosion" of novel data processing platforms that we currently witness. Wayang has been incubating since 2020-12-16.

Three most important unfinished issues to address before graduating:

  1. Simplifying and documenting the release process
  2. Drive growth and community building
  3. Slow contribution rate

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

™ “Wayang” as ™ is not solved yet, no response so far from the trademark team.

How has the community developed since the last report?

Slow adaption, but increasing interest and adoption.

How has the project developed since the last report?

Python integration progressing, SQL support in hibernation

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-12-13

When were the last committers or PPMC members elected?

2022-01-18: Calvin Kirs

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, the mentors are helpful, nevertheless, two of them have prolonged inactivity.

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 name is under the process of "ASF's trademark counsel.”

Signed-off-by:

  •  (wayang) Christofer Dutz
    Comments: It's been quite quiet on the list and on the code repo.
  •  (wayang) Lars George
    Comments:
  •  (wayang) Bernd Fondermann
    Comments:
  •  (wayang) Jean-Baptiste Onofré
    Comments: I think we are on track for graduation.

IPMC/Shepherd notes:

--------------------        

  • No labels