You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 27 Next »

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:

  • 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 a space after a bullet point or full stop on a numbered list.
  • Use [X] (X and no spaces) to sign off reports.

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 January 01Podling reports due by end of day
Sun January 05Shepherd reviews due by end of day
Sun January 05Summary due by end of day
Tue January 07Mentor signoff due by end of day
Wed January 08

Report submitted to Board

Wed January 15Board meeting


Shepherd Assignments

Dave FisherHudi
Dave FisherTubeMQ
Drew FarrisAnnotator
Drew FarrisTVM
Justin McleanWeex
P. Taylor GoetzGobblin
P. Taylor GoetzStreamPipes
P. Taylor GoetzTaverna
Timothy ChenDLab
Timothy ChenIceberg
Timothy ChenLivy

APISIX

DolphinScheduler

Flagon

MXNet

Milagro

Myriad

NuttX

Pony Mail

Teaclave

Incubator PMC report for January 2020

The Apache Incubator is the entry path into the ASF for projects and codebases wishing to become part of the Foundation's efforts.

TODO add arrative

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

Infrastructure

Miscellaneous

Credits

Table of Contents Annotator
APISIX
DLab
Flagon
Gobblin
Hudi
Iceberg
Livy
Milagro
MXNet
Myriad
NuttX
PonyMail
Taverna
Teaclave
TubeMQ
TVM
Weex


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) Steve Blackmon
    Comments:
  •  (annotator) Tommaso Teofili
    Comments:

IPMC/Shepherd notes:


APISIX

APISIX is a cloud-native microservices API gateway, delivering the ultimate performance, security, open source and scalable platform for all your APIs and microservices.

APISIX is based on Nginx and etcd. Compared with traditional API gateways, APISIX has dynamic routing and plug-in hot loading, which is especially suitable for API management under micro-service system.

APISIX has been incubating since 2019-10-17.

Three most important unfinished issues to address before graduating:

  1. More Apache Releases and more committers act as release manager to release a version.
  2. More committers and PPMC members.
  3. Branding issues in the documentation, code, website, etc.

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

None

How has the community developed since the last report?

  • We have some talks about the best practices of high-performance API gateway on COSCon 2019, Dec 8th and OpenTalk, Dec 8th.
  • We have solved the Apache APISIX major brand issues in documentation, code, website, etc.
  • We have 13 committers and 50 contributors (including 13 committers) contributing to Apache APISIX.
  • Over 19 company users have announced that they are using APISIX and more than 50% of them also submitted code or fixed the documentation for APISIX : https://github.com/apache/incubator-apisix/issues/487

How has the project developed since the last report?

The project has been quite health, with more than 29 pull requests, 25 of them have being merged in December. These pull requests are authored by a diverse set of contributors. We also suggest and guide users from QQ group to make issues at Apache APISIX mailing list, which is helpful for people who have the same issue and tracking bugs.

This month's Pull Request is mainly divided into three aspects:

  • Fixing Apache APISIX bug.
  • Supporting more configuration items and optimizing the experience on Apache APISIX Dashboard.
  • Supplement Apache APISIX function manual

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:

Mon Nov 25 2019 (0.9)

When were the last committers or PPMC members elected?

At Nov 28 2019 PPMC members elected a new commiter @lilien1010 who worked for HelloTalk.

Have your mentors been helpful and responsive?

Mentors are responsive and helpful. Things tend to be on the right way.

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

Yes, We keep tracking podling's brand / trademarks.

Signed-off-by:

  •  (apisix) Willem Ning Jiang Comments:
  •  (apisix) Justin Mclean Comments:
  •  (apisix) Kevin Ratnasekera Comments:
  •  (apisix) Von Gosling Comments:

IPMC/Shepherd notes:


DLab

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

DLab has been incubating since 2018-08-20.

Three most important unfinished issues to address before graduating:

  1. Come up with a new name for DLab.
  2. Extend the amount of committers.
  3. After release 2.2 is made, the team will have to do major refactoring of the code, updating of product documentation, which might potentially slow down the process of releasing version 2.3.

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?

Following committers have been added:

  • Mykola Bodnar (ICLA file was signed off and submitted in previous Sep 2019 report and Apache ID was created later on September 12th, 2019)
  • Dmytro Gnatyshyn

How has the project developed since the last report?

  • The team has released v.2.2 and now it is working on release v.2.3
  • Web site was created and moved to apache servers

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

When were the last committers or PPMC members elected?

The last committer was elected on December 2, 2019.

Have your mentors been helpful and responsive?

Yes our mentors are super helpful. We do receive answers to all our questions timely. Special thanks for Furkan, who was super helpful and provided the majority of responses.

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

Out team has finally chosen a name. We'll soon create for a JIRA ticket for Podling name search. If no conflict found (preliminary there are zero conflicts), we'll have to reflect this in our codebase/documentation in upcoming release.

Signed-off-by:

  •  (dlab) P. Taylor Goetz
    Comments:
  •  (dlab) Henry Saputra
    Comments:
  •  (dlab) Konstantin I Boudnik
    Comments:
  •  (dlab) Furkan Kamaci
    Comments:

IPMC/Shepherd notes:


DolphinScheduler

Dolphin Scheduler is a distributed and easy-to-expand visual DAG workflow scheduling system dedicated to solving the complex dependencies in data processing, making the scheduling system out of the box for data processing.

Dolphin Scheduler has been incubating since 2019-8-29.

Three most important unfinished issues to address before graduating:

  1. Make first Apache releases. (In 3rd round voting progress)
  2. Develop more committers and contributors.
  3. Clean up the license issue on JS lib.

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. Developed 13 more contributors from 42 to 55 who contributes codes to github.
  2. Successfully held a co-meetup with Sharding Sphere in Dec, 8th in Beijing, more than 70 people attended the meet up.
  3. E-mail discussion was accepted by community step by step: about 9 proposals and many discussion were communicated by e-mail since the training on the last meet-up.
  4. Many contributors were devleloped and found while overcoming the difficulty on Apache release, and some of them would be voted to committers next month.

How has the project developed since the last report?

  1. Apache 1.2.0 release was still in progress. Committers fix the commercial problems on fonts and icons, and was cleaning up the dependencies on JS libs.

  2. Formal auto CI/CD was accepted by community with UT 60%.

  3. 1.2.x was developing and there is a proposal to refactor some key part of the project for better concurrent perfomance.

How would you assess the podling's maturity?

Please feel free to add your own commentary.

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

Date of last release:

No answer.

When were the last committers or PPMC members elected?

2019-11-11

Have your mentors been helpful and responsive?

Yes, our mentors help a lot on our firtst Apache Release.

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

Yes, We keep tracking podling's brand / trademarks.

Signed-off-by:

  •  (dolphinscheduler) Sheng Wu Comments: Mail list communications become more active. Good to see this.
  •  (dolphinscheduler) ShaoFeng Shi Comments:
  •  (dolphinscheduler) Liang Chen Comments:
  •  (dolphinscheduler) Furkan KAMACI Comments:
  •  (dolphinscheduler) Kevin Ratnasekera 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:

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?

  • 84% of commits were from non-committer contributors. (Active contributors are being discussed for being voted as committers)
  • Healthy engagement and activity of committers and contributors.
  • Email stats since last report: user@gobblin.incubator.apache.org : 23 dev@gobblin.incubator.apache.org : 2010
  • There have been 94 Commits since last report: git log --format='%ci' | grep -cE '((2019-1(0|1|2)))'
  • 79 ie. 84% of those commits were by non-committers: git log --format='%ae %ci' | grep -E '((2019-1(0|1|2)))' | cut -d ' ' -f 1 | sort | uniq -c | sort -n

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:

2018-12-09

When were the last committers or PPMC members elected?

Sudarshan Vasudevan in January, 2019. (Active contributors are being discussed for being voted as committers)

Have your mentors been helpful and responsive?

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?

Signed-off-by:

  •  (gobblin) Jean-Baptiste Onofre
    Comments:
  •  (gobblin) Olivier Lamy
    Comments:
  •  (gobblin) Jim Jagielski
    Comments:

IPMC/Shepherd notes:


Hudi

Hudi provides atomic upserts and incremental data streams on Big Data

Hudi has been incubating since 2019-01-17.

Three most important unfinished issues to address before graduating:

  1. Making sufficient number of releases in the Apache way

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?

630 conversations on dev ML across ~50 topics 20-30 participants for each one month period ~40 support issues opened on GitHub

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:

  •  (hudi) Thomas Weise
    Comments:
  •  (hudi) Luciano Resende
    Comments:
  •  (hudi) Kishore Gopalakrishnan
    Comments:
  •  (hudi) Suneel Marthi
    Comments:

IPMC/Shepherd notes:


Iceberg

Iceberg is a table format for large, slow-moving tabular data.

Iceberg has been incubating since 2018-11-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:

  •  (iceberg) Ryan Blue
    Comments:
  •  (iceberg) Julien Le Dem
    Comments:
  •  (iceberg) Owen O'Malley
    Comments:
  •  (iceberg) James Taylor
    Comments:
  •  (iceberg) Carl Steinbach
    Comments:

IPMC/Shepherd notes:


Livy

Livy is web service that exposes a REST interface for managing long running Apache Spark contexts in your cluster. With Livy, new applications can be built on top of Apache Spark that require fine grained interaction with many Spark contexts.

Livy has been incubating since 2017-06-05.

Three most important unfinished issues to address before graduating:

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) Brock Noland
    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:

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:

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

  1. Address past release issues. Successfully and smoothly make releases
  • ONGOING.
  1. Improve development process and tooling to help reduce the overhead of releases
  • ONGOING.

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

  1. MXNet 2.0 has started: https://github.com/apache/incubator-mxnet/projects/18 RFC: https://github.com/apache/incubator-mxnet/issues/16167

How has the community developed since the last report?

How has the project developed since the last report?

  1. 1.5.1 patch release and 1.6.0 in progress: https://github.com/apache/incubator-mxnet/releases/tag/1.5.1 https://github.com/apache/incubator-mxnet/releases/tag/1.6.0 with over 830+ patches of new features, improvements, and fixes.
  2. 2.0 project: https://github.com/apache/incubator-mxnet/projects/18
  3. Many ongoing projects:
  4. Github statistics of last month:
  • Nov 30, 2019 – Dec 30, 2019: Excluding merges, 45 authors have pushed 109 commits to master and 131 commits to all branches. On master, 314 files have changed and there have been 20,474 additions and 3,842 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:

2019-10-01

When were the last committers or PPMC members elected?

2019-11-24

Have your mentors been helpful and responsive?

Yes, mentors have been responsive and helpful as usual

Signed-off-by:

  •  (mxnet) Henri Yandell Comments:
  •  (mxnet) Markus Weimer Comments:
  •  (mxnet) Michael Wall Comments:
  •  (mxnet) Bob Paulin Comments:
  •  (mxnet) Jason Dai Comments:

IPMC/Shepherd notes:


Myriad

Myriad enables co-existence of Apache Hadoop YARN and Apache Mesos together on the same cluster and allows dynamic resource allocations across both Hadoop and other applications running on the same physical data center infrastructure.

Myriad has been incubating since 2015-03-01.

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:

  •  (myriad) Benjamin Hindman
    Comments:
  •  (myriad) Ted Dunning
    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:

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:

  •  (nuttx) Junping Du
    Comments:
  •  (nuttx) Justin Mclean
    Comments:
  •  (nuttx) Mohammad Asif Siddiqui
    Comments:
  •  (nuttx) Flavio Paiva Junqueira
    Comments:

IPMC/Shepherd notes:


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:

  1. Growing contributor base
  2. Getting release processes nailed to a tee
  3. Expanding unit tests

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

How has the community developed since the last report?

Not much progress although we did get a question on the user list which was responded to quickly. Progress is slow paced as usual although any reports of issues is dealt with in a timely manner.

How has the project developed since the last report?

We have had a couple bug reports that have been worked on 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:

2019-04-20

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:


Taverna

Taverna is a domain-independent suite of tools used to design and execute data-driven workflows.

Taverna has been incubating since 2014-10-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:

  •  (taverna) Stian Soiland-Reyes
    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:

  1. Improving project structure and documentation
  2. Grow the community (committers, contributors, users)
  3. Publish Apache 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?

  • Since last report, we planned to schedule an online meetup recently.
  • We have also received contributions of two new contributors.
  • We draft a roadmap RFC for discussion.
  • We use GitHub issues to track bugs, features, enhancements. Issues labeled with "good first issues" is more approachable for newcomers.

How has the project developed since the last report?

  • Resolve all renaming issues of INFRA (INFRA-19532)
  • Refactor four core components
  • Rewrite README.md to clearly explain the project's highlights in security, functionality, and usability.
  • Start to use protobuf for RPC definition
  • SGX SDK starts to use Intel SGX SDK v2.7.1

How would you assess the podling's maturity?

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

Date of last release:

N/A

When were the last committers or PPMC members elected?

We haven't started new committers or PPMC members elections yet. Currently, our work focus on improving the design and documents to make the project more approachable for newcomers.

Have your mentors been helpful and responsive?

Yes. Last month, we changed name from MesaTEE to Teaclave. There are a lot of changes need to be done. The mentors and infra teams help us a lot on the transfer.

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

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

Signed-off-by:

  •  (teaclave) Felix Cheung
    Comments:
  •  (teaclave) Furkan Kamaci
    Comments:
  •  (teaclave) Jianyong Dai
    Comments:
  •  (teaclave) Luciano Resende
    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:

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:

  •  (tubemq) Junping Du
    Comments:
  •  (tubemq) Justin Mclean
    Comments:
  •  (tubemq) Sijie Guo
    Comments:
  •  (tubemq) Zhijie Shen
    Comments:
  •  (tubemq) Jean-Baptiste Onofre
    Comments:

IPMC/Shepherd notes:


TVM

TVM is a full stack open deep learning compiler stack for CPUs, GPUs, and specialized accelerators. It aims to close the gap between the productivity- focused deep learning frameworks, and the performance- or efficiency- oriented hardware backends.

TVM has been incubating since 2019-03-06.

Three most important unfinished issues to address before graduating:

  1. Keep growing the community
  2. Make a few more Apache releases
  3. Improve documentations

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?

TVM community has welcomed two new committers/PPMC members since last report. There are also two on-going new committer nomination that will close in a week. The community hosted many meetups and an annual developer conference with more than 200+ attendees. These contents are made publically available as per apache way.

This has been a great year for us doing the Apache way and grow the community. The community has grown 70% in terms of number of contributors and committers, while these statistics do not necessarily indicate success, they suggest we are on the right track.

How has the project developed since the last report?

We made our first Apache release. Thanks to the help of IPMC members, in particular Justin, we were able to hold the Apache standard and release without using the WIP disclaimer

A lot of improvements have been made. Including TensorCore support, embedded system support and performance improvements

See also our monthly report for detailed improvements

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

When were the last committers or PPMC members elected?

Dec 1 2019

Have your mentors been helpful and responsive?

Our mentors are super helpful.

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

We have yet check with the VP. Given the long history of the project, we want to keep the name, will reach out to brand formally.

Signed-off-by:

  •  (tvm) Byung-Gon Chun
    Comments: Great progress! Good job on the first Apache release!
  •  (tvm) Sebastian Schelter
    Comments:
  •  (tvm) Henry Saputra
    Comments:
  •  (tvm) Timothy Chen
    Comments:
  •  (tvm) Furkan Kamaci
    Comments:
  •  (tvm) Tianqi Chen
    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:

  1. Branding issues. There are about 10 git repos violating the trademark of Apache Weex, together with their NPM/Maven artifact.
  2. Community diversity. Apache Weex needs more PPMCs and committers from community, no employees from a single company shall have majority vote in PPMC and committer.

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

NO

How has the community developed since the last report?

  • Four Committers joined us, excalibur, tw93, cnryb and teining.
  • The project weex-ui join us.

How has the project developed since the last report?

  • Released a new version (v0.28.0) of Weex.
  • We have 135 incoming pull request, and 132 of them are merged.
  • We have 57 threads in Weex mailing list .
  • We have solved 135 Github issues.

How would you assess the podling's maturity?

Please feel free to add your own commentary.

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

Date of last release:

2019-10-23

When were the last committers or PPMC members elected?

2019-12-05

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. Mentors are very 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?

  • We are collecting a list of branding issues, and we shall fix the problem one by one.
  • We have not done Podling name search.

Signed-off-by:

  •  (weex) Willem Ning Jiang
    Comments:
  •  (weex) Myrle Krantz
    Comments:
  •  (weex) Jan Piotrowski
    Comments:

IPMC/Shepherd notes:

  • No labels