DRAFT DRAFT DRAFT
NOTE that the content for this month report is in markdown format- please do not remove any formatting characters when adding your reports.
It also best to:
- Do not change existing formatting. Especially do not change the formatting of the sign-off area.
Keep all lines under 76 characters long.
All content under the ### headings should be indented by two spaces. Do not use tabs.
- Please don't change the text in the headings or add new ones.
- Include one space after a bullet point or full stop on a numbered list.
- Use [X] (X and no spaces) to sign off reports.
- Do not include long URLs and use the apache URL shortener https://s.apache.org.
- Please note that some lines have two spaces at the end. Do not remove these spaces.
Please make sure you use the current report and don't copy an old one, the headings do change from time to time.
A script will be run on this report before it is submitted to the board. If your lines are too long it may insert line breaks in unexpected places.
fold -w 76 -s $1 | cat -s
Timeline
Wed January 06 | Podling reports due by end of day |
Sun January 10 | Shepherd reviews due by end of day |
Sun January 10 | Summary due by end of day |
Tue January 12 | Mentor signoff due by end of day |
Wed January 13 | Report submitted to Board |
Wed January 20 | Board meeting |
Shepherd Assignments
Dave Fisher | Teaclave |
---|---|
Dave Fisher | Weex |
Drew Farris | Liminal |
Drew Farris | NuttX |
Justin Mclean | Milagro |
P. Taylor Goetz | Flagon |
P. Taylor Goetz | Gobblin |
P. Taylor Goetz | Pony Mail |
Timothy Chen | DataLab |
Timothy Chen | Pegasus |
Timothy Chen | Toree |
Annotator | |
BlueMarlin | |
Hop | |
Livy | |
MXNet | |
TubeMQ | |
YuniKorn |
Incubator PMC report for January 2021
The Apache Incubator is the entry path into the ASF for projects and codebases wishing to become part of the Foundation's efforts.
TODO add narrative
Community
New IPMC members:
People who left the IPMC:
New Podlings
Podlings that failed to report, expected next month
Graduations
- list podling here
The board has motions for the following:
- Your podling here?
Releases
The following releases entered distribution during the month of December:
IP Clearance
Legal / Trademarks
Infrastructure
Miscellaneous
Credits
Table of Contents
Annotator
BlueMarlin
brpc
DataLab
Flagon
Gobblin
Hop
Liminal
Livy
Milagro
MXNet
NuttX
Pegasus
PonyMail
Teaclave
TubeMQ
Wayang
Weex
YuniKorn
Annotator
Annotator provides annotation enabling code for browsers, servers, and humans.
Annotator has been incubating since 2016-08-30.
Three most important unfinished issues to address before graduating:
Are there any issues that the IPMC or ASF Board need to be aware of?
How has the community developed since the last report?
How has the project developed since the last report?
How would you assess the podling's maturity?
Please feel free to add your own commentary.
- Initial setup
- Working towards first release
- Community building
- Nearing graduation
- Other:
Date of last release:
XXXX-XX-XX
When were the last committers or PPMC members elected?
Have your mentors been helpful and responsive?
Are things falling through the cracks? If so, please list any open issues that need to be addressed.
Is the PPMC managing the podling's brand / trademarks?
Are 3rd parties respecting and correctly using the podlings name and brand? If not what actions has the PPMC taken to correct this? Has the VP, Brand approved the project name?
Signed-off-by:
- (annotator) Nick Kew
Comments: - (annotator) Tommaso Teofili
Comments: - (annotator) Benjamin Young
Comments:
IPMC/Shepherd notes:
BlueMarlin
BlueMarlin will develop a web service to add intelligence functionality to a plain ad system.
BlueMarlin has been incubating since 2020-06-09.
Three most important unfinished issues to address before graduating:
Are there any issues that the IPMC or ASF Board need to be aware of?
How has the community developed since the last report?
How has the project developed since the last report?
How would you assess the podling's maturity?
Please feel free to add your own commentary.
- Initial setup
- Working towards first release
- Community building
- Nearing graduation
- Other:
Date of last release:
XXXX-XX-XX
When were the last committers or PPMC members elected?
Have your mentors been helpful and responsive?
Are things falling through the cracks? If so, please list any open issues that need to be addressed.
Is the PPMC managing the podling's brand / trademarks?
Are 3rd parties respecting and correctly using the podlings name and brand? If not what actions has the PPMC taken to correct this? Has the VP, Brand approved the project name?
Signed-off-by:
- (bluemarlin) Craig Russell
Comments: - (bluemarlin) Jean-Baptiste Onofré
Comments: We don't have lot of interaction with BlueMarlin team. I will ping them a new time. - (bluemarlin) Von Gosling
Comments: - (bluemarlin) Junping Du
Comments: - (bluemarlin) Uma Maheswara Rao G
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:
Are there any issues that the IPMC or ASF Board need to be aware of?
How has the community developed since the last report?
How has the project developed since the last report?
How would you assess the podling's maturity?
Please feel free to add your own commentary.
- Initial setup
- Working towards first release
- Community building
- Nearing graduation
- Other:
Date of last release:
XXXX-XX-XX
When were the last committers or PPMC members elected?
Have your mentors been helpful and responsive?
Are things falling through the cracks? If so, please list any open issues that need to be addressed.
Is the PPMC managing the podling's brand / trademarks?
Are 3rd parties respecting and correctly using the podlings name and brand? If not what actions has the PPMC taken to correct this? Has the VP, Brand approved the project name?
Signed-off-by:
- (brpc) Kevin A. McGrail
Comments: - (brpc) Jean-Baptiste Onofré
Comments: - (brpc) Von Gosling
Comments:
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:
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?
We have a new committer (java-developer) - Yurii Kinash.
How has the project developed since the last report?
- We are working towards the release 2.5.0
- Migration to Py3 (in progress)
- Edge node recreation capability (in progress)
- Support of Spark v.3.x.x (open)
- Localization (done)
- Switch to modular architecture (in progress)
- Augment an administrative page (in progress)
- 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:
2020-17-09
When were the last committers or PPMC members elected?
The last committer was elected on December 10, 2020.
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. New name was approved and our team changed all references to DLab that are publicly accessible to DataLab, including code base, presentations, documentation, etc.
Signed-off-by:
- (datalab) P. Taylor Goetz
Comments: - (datalab) Henry Saputra
Comments: - (datalab) Konstantin I Boudnik
Comments: - (datalab) Furkan Kamaci
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:
Are there any issues that the IPMC or ASF Board need to be aware of?
How has the community developed since the last report?
How has the project developed since the last report?
How would you assess the podling's maturity?
Please feel free to add your own commentary.
- Initial setup
- Working towards first release
- Community building
- Nearing graduation
- Other:
Date of last release:
XXXX-XX-XX
When were the last committers or PPMC members elected?
Have your mentors been helpful and responsive?
Are things falling through the cracks? If so, please list any open issues that need to be addressed.
Is the PPMC managing the podling's brand / trademarks?
Are 3rd parties respecting and correctly using the podlings name and brand? If not what actions has the PPMC taken to correct this? Has the VP, Brand approved the project name?
Signed-off-by:
- (flagon) Lewis John McGibbney
Comments: - (flagon) David Meikle
Comments: - (flagon) Tim Allison
Comments: - (flagon) Furkan Kamaci
Comments:
IPMC/Shepherd notes:
Gobblin
Gobblin is a distributed data integration framework that simplifies common aspects of big data integration such as data ingestion, replication, organization and lifecycle management for both streaming and batch data ecosystems.
Gobblin has been incubating since 2017-02-23.
Three most important unfinished issues to address before graduating:
- Discuss and Vote in progress in general@incubator mailing list for graduation to TLP.
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?
- Email stats since last report: dev@gobblin.incubator.apache.org : 505 (Oct), 324 (Nov), 313 (Dec)
- There have been 63 Commits since last report: git log --format='%ci' | grep -cE '((2020-1(0|1|2)))'
- 29 ie. 46% of those commits were by non-committers: git log --format='%ae %ci' | grep -E '(2020-1(0|1|2))' | cut -d ' ' -f 1 | sort | uniq -c | sort -n
How has the project developed since the last report?
- Vote within community for graduation to TLP was passed after a discussion. Discuss and vote was started in general@incubator.
- Roster, project page, documentation, website, and wiki were reviewed and updated.
- Evaluation under Apache maturity model for graduation was done.
- Podling name search was done.
- New version (0.15.0) was approved and released.
On technical side, the following was added:
- Support for Kafka 1.1.
- Decimal type support in GobblinORCWriter.
- LDAP based group ownership support.
- New Groups ownership service.
- Azkaban OAuth token support.
- Gradle version was upgraded.
- Auto-tune of ORC writer params.
- Support for multiple DFS tokens fetch for HDFS federation.
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-10
When were the last committers or PPMC members elected?
Tamás Németh and Sudarshan Vasudevan for PPMC in June, 2020.
Have your mentors been helpful and responsive?
Yes.
Is the PPMC managing the podling's brand / trademarks?
Yes.
Signed-off-by:
- (gobblin) Jean-Baptiste Onofre
Comments: - (gobblin) Olivier Lamy
Comments: - (gobblin) Owen O'Malley
Comments:
IPMC/Shepherd notes:
Hop
Hop is short for the Hop Orchestration Platform. Written completely in Java it aims to provide a wide range of data orchestration tools, including a visual development environment, servers, metadata analysis, auditing services and so on. As a platform, Hop also wants to be a reusable library so that it can be easily reused by other software.
Hop has been incubating since 2020-09-24.
Three most important unfinished issues to address before graduating:
- identify and resolve the last remaining incompatibly licensed dependencies (if any)
- create a first release
- grow the community
Are there any issues that the IPMC or ASF Board need to be aware of?
No known significant issues at this moment
How has the community developed since the last report?
- 3 additional committers, lots of committer and community activity in the last month
- 14 new registered chat members (108->122)
- 1 new subscriber to dev (21->22), 0 to users mailing lists (11)
- significant follower growth on LinkedIn (309->321), Twitter (233->253) and YouTube (40->50)
How has the project developed since the last report?
Two releases candidates (0.50-rc1, 0.50-rc2) were created but failed to get enough positive votes. Hop will take the feedback and lessons learned from 0.50-rc1 and 0.50-rc2 to build a new 0.60-rc1. Summary of the 2 RCs: https://s.apache.org/06hws
December was a very active month, with continued activity over the holiday period:
- metadata perspective
- look and feel updates
- new transform plugins (UDJC, Token Replacement)
- partitioned stream lookup
- docker included, community activity on kubernetes
- jandex-based plugins
- integration testing
- community activity on Hop Web
- documentation updates
Full details are available in the December monthly roundup: https://hop.apache.org/blog/2021/01/roundup-2021-01/
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?
2020-12-2
Have your mentors been helpful and responsive?
Julian Hyde and François Papon regularly check in and provide valuable input. We're sure our other mentors will step in for RCs after the holiday period.
Is the PPMC managing the podling's brand / trademarks?
There are no known brand and naming issues. The PPMC only uses "Apache Hop (Incubating)" as the official project name and has explicitly called "Project Hop" deprecated as of the moment of acceptance in the Incubator.
Signed-off-by:
- (hop) Tom Barber
Comments: - (hop) Julian Hyde
Comments: Good report! I'd say you are through 'initial setup' and can uncheck that box next time. The community is going great, and I'm sure that the first release will happen very soon. One concern: the difference in the number of people on chat vs the dev list (122 vs 22). The traffic on chat is benign (e.g. no major decisions being made) but I am concerned that with so few of the regulars on the dev list, chat will become the de facto place to make decisions. Also I couldn't find a public archive of chat. I'll raise this issue on the dev list. - (hop) Maximilian Michels
Comments: I'm continuing to be amazed by the progress of the Hop project. There is a constant flow of incoming pull requests and the first release is nearing completion. It might not be clear to all community members but I've tried to only step in when necessary, e.g. give feedback to unblock the release process. - (hop) Francois Papon
Comments: The community is still very active and starting to learn the release process. For now, the only issue in the release is the license part and the team is focused on it to prepare a new vote. - (hop) Kevin Ratnasekera
Comments:
IPMC/Shepherd notes:
Liminal
Apache Liminal is an end-to-end platform for data engineers and scientists, allowing them to build, train and deploy machine learning models in a robust and agile way.
Liminal has been incubating since 2020-05-23.
Three most important unfinished issues to address before graduating:
- First release (due to next week)
- Build a community
- Define 2021 roadmap
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 had a successful meetup and a presentation on Data & AI summit Europe. Discussing with few companies to join the effort.
How has the project developed since the last report?
The first release candidate is ready and verified, planning to have a formal release next week.
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
The first release candidate is ready and verified, planning to have a formal release next week
When were the last committers or PPMC members elected?
NA
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.
JB & Davor have been 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? No.
Signed-off-by:
- (liminal) Jean-Baptiste Onofre
Comments: - (liminal) Henry Saputra
Comments: - (liminal) Uma Maheswara Rao G
Comments: - (liminal) Davor Bonaci
Comments: - (liminal) Liang Chen
Comments:
IPMC/Shepherd notes:
Justin Mclean: Individuals contribute to ASF projects not companies. I'm sure you know that, you just might want to be more careful with your language in future reports.
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:
Are there any issues that the IPMC or ASF Board need to be aware of?
How has the community developed since the last report?
How has the project developed since the last report?
How would you assess the podling's maturity?
Please feel free to add your own commentary.
- Initial setup
- Working towards first release
- Community building
- Nearing graduation
- Other:
Date of last release:
XXXX-XX-XX
When were the last committers or PPMC members elected?
Have your mentors been helpful and responsive?
Are things falling through the cracks? If so, please list any open issues that need to be addressed.
Is the PPMC managing the podling's brand / trademarks?
Are 3rd parties respecting and correctly using the podlings name and brand? If not what actions has the PPMC taken to correct this? Has the VP, Brand approved the project name?
Signed-off-by:
- (livy) Bikas Saha
Comments: - (livy) Luciano Resende
Comments: - (livy) Jean-Baptiste Onofre
Comments:
IPMC/Shepherd notes:
Milagro
Milagro is core security infrastructure and crypto libraries for decentralized networks and distributed systems.
Milagro has been incubating since 2015-12-21.
Three most important unfinished issues to address before graduating:
- Continue to build relevant and useful crypto libraries and applications for decentralized networks in order to grow the ecosystem of users and contributors to the project.
- Continue to improve compliance with the Apache Way. In particular to update the Milagro website and other project sites (e.g. Whimsy) in accordance with Apache policies.
- Further releases to increase the scope of the Milagro project, extend the capability of existing releases and to demonstrate improved compliance with the Apache Way.
Are there any issues that the IPMC or ASF Board need to be aware of?
No significant issues, however some administrative tasks around the project are still outstanding but are being addressed. In particular, a PPMC meeting has been proposed for 3rd February to discuss outstanding issue with a follow on meeting for the entire Milagro community to discuss the project's roadmap.
How has the community developed since the last report?
No change.
How has the project developed since the last report?
Work continues on the C and Rust versions of the core cryptographic library and on preparing the Multi Party Computation library for its first official Apache release.
How would you assess the podling's maturity?
Please feel free to add your own commentary.
- Initial setup
- Working towards first release
- [*] Community building
- Nearing graduation
- Other:
Date of last release:
2020-02-10
When were the last committers or PPMC members elected?
February 2020
Have your mentors been helpful and responsive?
No issues.
Is the PPMC managing the podling's brand / trademarks?
No known issues, but further investigation is still required by the Milagro community.
Signed-off-by:
- (milagro) Nick Kew
Comments: - (milagro) Jean-Frederic Clere
Comments:
IPMC/Shepherd notes:
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:
Are there any issues that the IPMC or ASF Board need to be aware of?
How has the community developed since the last report?
How has the project developed since the last report?
How would you assess the podling's maturity?
Please feel free to add your own commentary.
- Initial setup
- Working towards first release
- Community building
- Nearing graduation
- Other:
Date of last release:
XXXX-XX-XX
When were the last committers or PPMC members elected?
Have your mentors been helpful and responsive?
Are things falling through the cracks? If so, please list any open issues that need to be addressed.
Is the PPMC managing the podling's brand / trademarks?
Are 3rd parties respecting and correctly using the podlings name and brand? If not what actions has the PPMC taken to correct this? Has the VP, Brand approved the project name?
Signed-off-by:
- (mxnet) Markus Weimer
Comments: - (mxnet) Bob Paulin
Comments: - (mxnet) Jason Dai
Comments: - (mxnet) Furkan Kamaci
Comments:
IPMC/Shepherd notes:
NuttX
NuttX is a mature, real-time embedded operating system (RTOS).
NuttX has been incubating since 2019-12-09.
Three most important unfinished issues to address before graduating:
- Clear any potential infringing use of the NuttX trademark
- Make more releases under Apache
- Continue to grow the community with people from different background
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?
- Most communications have moved from old venues to dev@nuttx.apache.org.
The dev list contains 210 subscribers, an increase of 6% since our
previous report, and is the home of all development discussions and
user questions. - Github's PRs and Issues also have their own discussions.
- We are seeing new contributors to the project through Github.
- One new committer has been added since the last report.
How has the project developed since the last report?
- We have made significant steps toward license clearing, needed for
graduation: In this quarter, we have secured 34 ICLAs and 7 SGAs,
the most of any quarter so far, from past and present contributors. - We have successfully made our third, fourth, and fifth releases
under the ASF umbrella: NuttX-10.0 followed by security fix releases
NuttX-9.1.1 and NuttX-10.0.1. - Contributions are flowing regularly as PRs in GitHub with occasional
patches in the dev list. - Many technical improvements, bug fixes, and new architectures have
been collaborated and work continues with an average of 6 and
sometimes as many as a dozen pull requests merged per day. - We have listened to the valuable feedback received during our
previous releases and continue to improve our documentation. This can
be found at https://nuttx.apache.org/docs/latest/. - We've implemented additional automatic checks on PRs. This has
helped us to improve our review process.
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:
NuttX-10.0.1 and NuttX-9.1.1 were released on 2020-12-08.
When were the last committers or PPMC members elected?
Last elected PPMC: 2020-01-10
Last committer added: 2020-12-30
Have your mentors been helpful and responsive?
Mentors are helpful and responsive.
Is the PPMC managing the podling's brand / trademarks?
Podling name was approved on May 17th 2020: https://s.apache.org/4hfzx
Signed-off-by:
- (nuttx) Duo Zhang
Comments: Glad to see that we have made good progress on license clearing. - (nuttx) Junping Du
Comments: - (nuttx) Justin Mclean
Comments: - (nuttx) Mohammad Asif Siddiqui
Comments: - (nuttx) Flavio Paiva Junqueira
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:
- Attract more contributors and committers.
- Make more releases in ASF policy regularly.
- Resolve the license problems.
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?
We have recently attracted a new contributor empiredan, who have merged 2 PRs until now.
How has the project developed since the last report?
We are still actively working towards the next big release, which may be called 2.2.0. We have open-sourced 3 subprojects that were temporarily maintained outside the Apache orgnization:
- https://github.com/pegasus-kv/admin-cli
- https://github.com/pegasus-kv/pegic
- https://github.com/pegasus-kv/meta-proxy
Those are tiny tools but also considered as very important complement to the Pegasus ecosystem. pegic
and meta-proxy
are still in the initial stage. Developing under the "pegasus-kv" orgnization gets us full control of the Github settings so that we can move faster. admin-cli
is nearly completed and license-cleared and will soon be migrated to Apache. The three projects will all eventually be moved to Apache.
How would you assess the podling's maturity?
Please feel free to add your own commentary.
- Initial setup
- Working towards first release
- Community building
- Nearing graduation
- Other:
Date of last release:
2020-11-30
When were the last committers or PPMC members elected?
N/A
Have your mentors been helpful and responsive?
Are things falling through the cracks? If so, please list any open issues that need to be addressed.
Yes
Is the PPMC managing the podling's brand / trademarks?
Are 3rd parties respecting and correctly using the podlings name and brand? If not what actions has the PPMC taken to correct this? Has the VP, Brand approved the project name?
Yes
Signed-off-by:
- (pegasus) Kevin A. McGrail
Comments: Short report but accurate. - (pegasus) Duo zhang
Comments: - (pegasus) Liang Chen
Comments: - (pegasus) Von Gosling
Comments:
IPMC/Shepherd notes:
Justin Mclean: I like to see some explanation on why the sub-projects are being maintained outside of the project. There are branding and trademark issues and it may be best to consider moving them in-house. Also please list 3 unfinished issues that you still need to do to graduate.
Justin Mclean: Thanks for the explanation, if might be better if you you worked with Infra on the GitHub settings, developing code outside the ASF is likely to cause a number of issues in the future when the code is moved.
PonyMail
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:
Are there any issues that the IPMC or ASF Board need to be aware of?
How has the community developed since the last report?
How has the project developed since the last report?
How would you assess the podling's maturity?
Please feel free to add your own commentary.
- Initial setup
- Working towards first release
- Community building
- Nearing graduation
- Other:
Date of last release:
XXXX-XX-XX
When were the last committers or PPMC members elected?
Have your mentors been helpful and responsive?
Are things falling through the cracks? If so, please list any open issues that need to be addressed.
Is the PPMC managing the podling's brand / trademarks?
Are 3rd parties respecting and correctly using the podlings name and brand? If not what actions has the PPMC taken to correct this? Has the VP, Brand approved the project name?
Signed-off-by:
- (ponymail) John D. Ament
Comments: - (ponymail) Sharan Foga
Comments:
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:
Are there any issues that the IPMC or ASF Board need to be aware of?
How has the community developed since the last report?
How has the project developed since the last report?
How would you assess the podling's maturity?
Please feel free to add your own commentary.
- Initial setup
- Working towards first release
- Community building
- Nearing graduation
- Other:
Date of last release:
XXXX-XX-XX
When were the last committers or PPMC members elected?
Have your mentors been helpful and responsive?
Are things falling through the cracks? If so, please list any open issues that need to be addressed.
Is the PPMC managing the podling's brand / trademarks?
Are 3rd parties respecting and correctly using the podlings name and brand? If not what actions has the PPMC taken to correct this? Has the VP, Brand approved the project name?
Signed-off-by:
- (teaclave) Felix Cheung
Comments: - (teaclave) Furkan Kamaci
Comments: - (teaclave) Jianyong Dai
Comments: - (teaclave) Matt Sicker
Comments: - (teaclave) Zhijie Shen
Comments:
IPMC/Shepherd notes:
TubeMQ
TubeMQ is a distributed messaging queue (MQ) system.
TubeMQ has been incubating since 2019-11-03.
Three most important unfinished issues to address before graduating:
1.Adjust project goal && project name 2.Keep growing the community, attract more contributors and committers 3.Release Apache standard releases regularly
Are there any issues that the IPMC or ASF Board need to be aware of?
We hope more IPMCs will pay attention to our project and give more suggestions.
How has the community developed since the last report?
Since the last report, the TubeMQ community has continued to improve its functions as well as external publicity and communication; at the same time, we PPMCs conducted a discussion on adjusting project objectives and project names. We hope to provide a complete one-stop streaming data service platform: the system integrates a series of components in the form of plug-ins for collection, aggregation, storage and forwarding to build a complete data reporting service; based on this platform, users only need to publish and subscribe to data, and they can easily build analysis and applications based on streaming data; and TubeMQ will continue to develop in this project.
How has the project developed since the last report?
At this stage, we released the SDK of the Python language and the tubemq-manager module for cluster management. The tubemq-manager module is used for cross-cluster control to make the project more usable; we have also made a number of improvements in the function of the project, for details information, please refer to our project issues: https://issues.apache.org/jira/projects/TUBEMQ/issues.
How would you assess the podling's maturity?
Please feel free to add your own commentary.
- Initial setup
- Working towards first release
- Community building
- Nearing graduation
- Other:
Date of last release:
2020-12-04
When were the last committers or PPMC members elected?
- yuanboliu was added as committer on 2020-12-10
- dockerzhang was added as PPMC on 2020-12-15
Have your mentors been helpful and responsive?
In the recent period, the mentors have given us a lot of help and guidance; We hope that the mentors can continue to pay attention to the development of our project and continue to provide more help and suggestions to the project.
Is the PPMC managing the podling's brand / trademarks?
Yes, all good here.
Signed-off-by:
- (tubemq) Junping Du
Comments: - (tubemq) Justin Mclean
Comments: Don't forget you can reach out to your mentors if you need help. Keeping discussions on the mailing list also helps. - (tubemq) Sijie Guo
Comments: - (tubemq) Zhijie Shen
Comments: - (tubemq) Jean-Baptiste Onofre
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:
Are there any issues that the IPMC or ASF Board need to be aware of?
How has the community developed since the last report?
How has the project developed since the last report?
How would you assess the podling's maturity?
Please feel free to add your own commentary.
- Initial setup
- Working towards first release
- Community building
- Nearing graduation
- Other:
Date of last release:
XXXX-XX-XX
When were the last committers or PPMC members elected?
Have your mentors been helpful and responsive?
Are things falling through the cracks? If so, please list any open issues that need to be addressed.
Is the PPMC managing the podling's brand / trademarks?
Are 3rd parties respecting and correctly using the podlings name and brand? If not what actions has the PPMC taken to correct this? Has the VP, Brand approved the project name?
Signed-off-by:
- (wayang) Christofer Dutz
Comments: - (wayang) Lars George
Comments: - (wayang) Bernd Fondermann
Comments: - (wayang) Jean-Baptiste Onofré
Comments:
IPMC/Shepherd notes:
Weex
Weex is a framework for building Mobile cross-platform high performance UI.
Weex has been incubating since 2016-11-30.
Three most important unfinished issues to address before graduating:
Are there any issues that the IPMC or ASF Board need to be aware of?
How has the community developed since the last report?
How has the project developed since the last report?
How would you assess the podling's maturity?
Please feel free to add your own commentary.
- Initial setup
- Working towards first release
- Community building
- Nearing graduation
- Other:
Date of last release:
XXXX-XX-XX
When were the last committers or PPMC members elected?
Have your mentors been helpful and responsive?
Are things falling through the cracks? If so, please list any open issues that need to be addressed.
Is the PPMC managing the podling's brand / trademarks?
Are 3rd parties respecting and correctly using the podlings name and brand? If not what actions has the PPMC taken to correct this? Has the VP, Brand approved the project name?
Signed-off-by:
- (weex) Willem Ning Jiang
Comments: - (weex) Myrle Krantz
Comments:
IPMC/Shepherd notes:
YuniKorn
YuniKorn is a standalone resource scheduler responsible for scheduling batch jobs and long-running services on large scale distributed systems running in on-premises environments as well as different public clouds.
YuniKorn has been incubating since 2020-01-21.
Three most important unfinished issues to address before graduating:
- Gain more contributors and active committers.
- Establish a release cadence based on roadmap.
- Improve the ease of deployment and documentation quality.
Are there any issues that the IPMC or ASF Board need to be aware of?
No issues at this point in time.
How has the community developed since the last report?
New committer vote is in progress (delayed due to Christmas break).
Two new large features started. Driven by different parts of the community: gang scheduling and open tracing.
New release planned for the end of January 2021 and the search for a new release manager has started.
How has the project developed since the last report?
Major scheduler core code update rewrite committed.
Upgrades to build tools to the latests supported tool versions.
Testing matrix updated to support latest versions of Kubernetes.
Some statistics for the report period (2020-10-01 till 2021-12-31)
JIRA: 67 created, 56 resolved
PRs: 55 opened, 58 resolved
10 unique active code contributors (cumulative for all repos)
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-08-26
When were the last committers or PPMC members elected?
New committer vote is in progress (delayed due to Christmas break).
Have your mentors been helpful and responsive?
Yes, review of PRs and part of the community syncs
Is the PPMC managing the podling's brand / trademarks?
No issues that we are aware of.
Signed-off-by:
- (yunikorn) Junping Du
Comments: - (yunikorn) Felix Cheung
Comments: - (yunikorn) Jason Lowe
Comments: - (yunikorn) Holden Karau
Comments: