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

Timeline

Wed July 03Podling reports due by end of day
Sun July 07Shepherd reviews due by end of day
Sun July 07Summary due by end of day
Tue July 09Mentor signoff due by end of day
Wed July 10Report submitted to Board
Wed July 17Board meeting


Shepherd Assignments

Dave FisherLivy
Dave FisherTVM
Drew FarrisMXNet
Drew FarrisMilagro
Justin McleanTuweni
P. Taylor GoetzAmaterasu
P. Taylor GoetzDataSketches
P. Taylor GoetzGobblin
Timothy ChenBRPC
Timothy ChenBatchEE
Timothy ChenDLab

Annotator

Flagon

Hudi

Iceberg

Rya

Weex

Incubator PMC report for July 2019

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

The Apache Incubator is the entry path into the ASF for projects and codebases wishing to become part of the Foundation's efforts. This monthly report is in markdown so that it's easier to read. If you are viewing this not in that format, it can be seen here: https://cwiki.apache.org/confluence/display/INCUBATOR/July2019

There are presently 48 podlings incubating. In June, podlings executed XX distinct releases. We added no new IPMC members and no IPMC members retired. We have no new podlings this month. A couple of other podlings are heading towards graduation in the next few months including OpenWisk. Two podlings, DLad and Iceberg, failed to report for the second month. (TODO fix as they may still report) Podlings XXX, YYY and ZZZ didn't submit a report and have been asked to do so next month.

There were was one IP clearances.

Milagro is trying to reboot themselves, and it's good to see lots of new activity, this seems a successful attempt so far, and they are working on a release.

BatchEE has decided to leave the incubator and join the Geronimo project as that seems a better fit for them than becoming their own TLP.

OpenWisk has brought up graduation and has a few minor issues around releases, communication and branding to address. This again points out the challenges the incubator has when ASF policy may not be in line with modern development workflows.

Zikin decided that the incubator wasn't a good fit for them culturally and left the incubator returning back to be OpenZipkin. They had a large amount of work to do before they could graduate and some issues they faced would have been difficult to solve. It would be fair to say that their expectations were not correctly managed when entering the incubator. There was some debate if a vote needed to be held by the IPMC to record this, with some people objecting in strong terms.

The IPMC is still working on if podlings need to follow ASF's release policy and distribution policy while in incubation. It seems that more people think that the incubator does not have to follow policy. However, the board has never granted an exception to the incubator for this, it's not in it's the original charter or documented anywhere and last months proposal to do so didn't get IPMC consensus. In these threads, there were a number of good suggestions that could be implemented to smooth the progression from podling to top level project for some podlings. As usual, it's then difficult to get consensus on and implement these ideas. Hopefully, all this will coalesce into some action(s) and a new proposal (assuming one is needed) to be put forward to the board next month.

It was clarified with Infra than they will allow distribution of artifacts that don't follow policy, or rather that won't check and assume anything voted on by the IPMC is OK to be distributed. In other words, it's the IPMC responsibility.

Legal also clarified what they expected, and it's possibly a bit awkward as they (perhaps unsurprisingly) expect a TLP to follow all release policy, which includes any release made by the IPMC. We have not been doing this. They went further saying if the incubator is not considered a TLP, or is somehow special then the legal committee has indicated what they would allow in releases. This list is less restrictive than what has previously been followed, but still includes some situations where the incubator shouldn't approve a release. It's considered that the incubator is a TLP so this still needs to be resolved in some way.

Possibly getting a bit ahead of itself, the incubator made two releases that included issues that it would not usually release; inclusion of compiled source code and dependency on Category X software.

Until this issue is resolved, I don't see an end to this issue re-occurring every few years as it has done previously. This is confusing for podlings as they get mixed or contradictory answers to their questions depending on who they ask, and the documentation is heavy on the compliance side. This situation also has a part to play in Zipkin leaving.

The IPMC needs to be clear up front to some podlings may need major changes to how they operate, and they need to consider carefully if the ASF is, in fact, a good fit for them. The incubator has started work on a page outline the expectations and what some of the issues are that they might encounter. there may be some overlap with the cookbook here. A discussion has been started on change the incubator DISCLAIMER text to more accurately reflect that podling releases may not be in line with policy. This has no legal standing but is informational.

Serval podlings talks and talks about the incubator were accepted for ApacheCon North America.

Some of the incubator wiki pages were missed in the transfer and infra are looking into why.

A few more podlings have corrected people not been signed up to their private lists.

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 June:

IP Clearance

Legal / Trademarks

Infrastructure

Miscellaneous

Credits

Table of Contents

Amaterasu
Annotator
BatchEE
BRPC
DataSketches
DLab
Flagon
Gobblin
Hudi
Iceberg
Livy
Milagro
MXNet
Rya
Tuweni
TVM
Weex

Amaterasu

Apache Amaterasu is a framework providing continuous deployment for Big Data pipelines.

Amaterasu has been incubating since 2017-09-07.

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.

Signed-off-by:

  •  (amaterasu) Jean-Baptiste Onofré Comments:
  •  (amaterasu) Olivier Lamy Comments:
  •  (amaterasu) Davor Bonaci Comments:

IPMC/Shepherd notes:

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.

Signed-off-by:

  •  (annotator) Nick Kew Comments:
  •  (annotator) Steve Blackmon Comments:
  •  (annotator) Tommaso Teofili Comments:

IPMC/Shepherd notes:

BatchEE

BatchEE projects aims to provide a JBatch implementation (aka JSR352) and a set of useful extensions for this specification.

BatchEE has been incubating since 2013-10-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?

Not much and we agreed to move the project under geronimo responsability to exit the incubator.

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: exiting the incubator as a subproject of Apache Geronimo.

Date of last release:

2017-12-01

When were the last committers or PPMC members elected?

2019-24-01

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.

Signed-off-by:

  •  (batchee) Jean-Baptiste Onofré Comments:
  •  (batchee) Olivier Lamy Comments:
  •  (batchee) Mark Struberg 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. Check all third-party dependency, and remove unused NSPR files
  2. update all source files to add unify header
  3. plan to have a offline forum on Shanghai to prompt brpc

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?

It is very near to its first apache release.

How has the project developed since the last report?

We have made a large progress toward apache release, and planed a forum to attract more users.

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:

Still working on the first release

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.

Signed-off-by:

  •  (brpc) Kevin A. McGrail Comments:
  •  (brpc) Jean-Baptiste Onofré Comments:
  •  (brpc) Von Gosling Comments:

IPMC/Shepherd notes:

DataSketches

DataSketches is an open source, high-performance library of stochastic streaming algorithms commonly called "sketches" in the data sciences. Sketches are small, stateful programs that process massive data as a stream and can provide approximate answers, with mathematical guarantees, to computationally difficult queries orders-of-magnitude faster than traditional, exact methods.

DataSketches has been incubating since 2019-03-30.

Three most important unfinished issues to address before graduating:

  1. Complete a successful 1st snapshot release of Memory repo to DIST and Nexus. This is a blocking issue.
  2. Finish refactoring/snapshot releasing the other repos, which depend on #1.
  3. Move, refactor Website.

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

For the IPMC: As a newbie podling, my experience so far has been exasperating. Finding how to accomplish key tasks is difficult. The information is spread all over and seems to always be couched in language written by lawyers not developers. As a result the essential details of how to actually accomplish tasks are often missing.

For example: I have been trying to setup an initial landing page (similar to what Druid had before they moved their website). Just a single page to allow external users find our original website and be notified that we are in incubation, etc.

I have searched through the following documents to find out how to get this done, to no avail:

I have run into multiple roadblocks, especially with regards to permissions.
I have to keep filing new tickets with INFRA to setup access to infrastructure and they reply that the Mentors need to do this. When I ask on general@incubator, the replies I get suggest I need to file tickets with INFRA. So I am confused.

How has the community developed since the last report?

Not much. I wish I could spend more time on this, but I need to get the migration done.

How has the project developed since the last report?

We continue to evolve the project's functionality with commits to our GitHub 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:

No releases yet.

When were the last committers or PPMC members elected?

At the initial incubation date.

Have your mentors been helpful and responsive?

  1. I have opened INFRA issues that have not yet been addressed and there will be more to come.
  2. I could REALLY use some 1:1 help from an experienced release engineer (perhaps from another project), that is very familiar with the Apache/Maven release process and POM to get us off the ground. Once we have created our first release, we can continue from there. But getting this first one is out is turning out to be quite a challenge. I don't think we need more than an hour with an experienced Apache release engineer, our project just isn't that complicated.

Signed-off-by:

  •  (datasketches) Liang Chen Comments:
  •  (datasketches) Kenneth Knowles Comments:
  •  (datasketches) Furkan Kamaci 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:

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.

Signed-off-by:

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

Signed-off-by:

  •  (flagon) Lewis John McGibbney Comments:
  •  (flagon) David Meikle Comments:
  •  (flagon) Atri Sharma 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?

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.

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
  2. Legal/IP Clearance of software artifacts (LEGAL-461)
  3. Growing community further by grooming contributors to committers

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

  1. PODLINGNAMESEARCH-162 has been completed. But not reflected on whimsy
  2. Software grant has been signed by Uber. But not reflected on whimsy

How has the community developed since the last report?

  1. Mailing list subs grown to >50, 65 new mailing list threads
  2. Slack is about 99 signups total (20-30 WAU), 39 total contributors on github, ~25 support issues closed on GitHub
  3. 3 new organizations reported usage onto the Hudi site

How has the project developed since the last report?

  1. ~66 commits from ~15 contributors/committers, across 2 releases
  2. All development now happening on ASF infrastructure, with source code being prepared for ASF release
  3. External talks on DataCouncil SF19 and SF BigAnalytics Meetup

How would you assess the podling's maturity?

Please feel free to add your own commentary.

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

Date of last release:

N/A

When were the last committers or PPMC members elected?

During inception into incubator

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.

Signed-off-by:

  •  (hudi) Thomas Weise Comments: Nice work on the collaboration side. Are there new contributors that could become committer candidates?
  •  (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.

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.

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.

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. Increase diversity in contributors, committers, and PMC members — NEAR COMPLETION.
  2. Identify remaining ICLAs or SGAs that need signing – NEAR COMPLETION.
  3. Revisit Apache Maturity Model Assessment — TODO.

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

  1. Based on usability feedback from users, community has started a redesign of the website.

How has the community developed since the last report?

How has the project developed since the last report?

  1. 1.4.1 patch release: https://github.com/apache/incubator-mxnet/releases/tag/1.4.1
  2. 1.5.0 release in progress (pre-release v1.5.0.rc1): https://github.com/apache/incubator-mxnet/releases/tag/1.5.0.rc1 with over 750 patches of new features, improvements, and fixes.
  3. Roadmap discussion on 2.0 in progress https://github.com/apache/incubator-mxnet/issues/9686
  4. Code donation from dmlc/mshadow in progress.
  5. Many ongoing projects:
  6. Github statistics of last month:
  • May 24, 2019 – June 24, 2019: Excluding merges, 16 authors have pushed 88 commits to master and 140 commits to all branches. On master, 250 files have changed and there have been 12,939 additions and 9,919 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-04-29

When were the last committers or PPMC members elected?

2019-05-20

Have your mentors been helpful and responsive?

Mentors have been providing helps per requests from community.

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:

Rya

Rya (pronounced "ree-uh" /rēə/) is a cloud-based RDF triple store that supports SPARQL queries. Rya is a scalable RDF data management system built on top of Accumulo. Rya uses novel storage methods, indexing schemes, and query processing techniques that scale to billions of triples across multiple nodes. Rya provides fast and easy access to the data through SPARQL, a conventional query mechanism for RDF data.

Rya has been incubating since 2015-09-18.

Three most important unfinished issues to address before graduating:

  1. Working through the graduation procedure steps.

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?

  • The community is moving towards graduation: name search completed, project status file updated, the Apache Project maturity model evaluation almost done, proposed PMC list finalized
  • "SPARQL at Scale with Apache Rya" accepted for presentation at ApacheCon Las Vegas, Sept 2019

How has the project developed since the last report?

  • working on a major release in the next few months

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:

2108-03-04

When were the last committers or PPMC members elected?

  • PPMC member Caleb Meier elected on Jan 3rd, 2017

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 two mentors are helpful and responsive.

Signed-off-by:

  •  (rya) Josh Elser Comments:
  •  (rya) Billie Rinaldi Comments:

IPMC/Shepherd notes:

Tuweni

Tuweni is a set of libraries and other tools to aid development of blockchain and other decentralized software in Java and other JVM languages.

Tuweni has been incubating since 2019-03-25.

Three most important unfinished issues to address before graduating:

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.

Signed-off-by:

  •  (tuweni) Jim Jagielski Comments:
  •  (tuweni) Dave Fisher Comments:
  •  (tuweni) Kenneth Knowles Comments:
  •  (tuweni) Jean-Baptiste Onofré Comments:
  •  (tuweni) Michael Wall Comments:
  •  (tuweni) Furkan Kamaci 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. Source code and website migration to ASF infra
  2. Make the first Apache release
  3. Continue to grow the community

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

N/A

How has the community developed since the last report?

TVM community has welcomed one committer in the past month.

How has the project developed since the last report?

Summary statistics: In the past month authors have pushed 142 commits to master and 142 commits to all branches. On master, 421 files have changed and there have been 22,680 additions and 5,388 deletions.

Some highlights of recent developments:

  • Robust coverage of windows support.
  • Improvements in the integer simplifier interface.
  • Major improvements in high level ir(relay) support
  • For detailed information about the project development, please refer to the monthly TVM community's monthly summary:

How would you assess the podling's maturity?

Please feel free to add your own commentary.

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

Date of last release:

N/A

When were the last committers or PPMC members elected?

June 13 2019

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 in providing guidance.

Signed-off-by:

  •  (tvm) Byung-Gon Chun Comments:
  •  (tvm) Sebastian Schelter Comments:
  •  (tvm) Henry Saputra Comments:
  •  (tvm) Timothy Chen Comments:
  •  (tvm) Furkan Kamaci 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. The binary convenience library of Weex should exclude the LGPL runtime(Webkit).
  2. A collection of Weex's tools should be donated to ASF, as they are essential part of building Weex App
  3. The Java package name in Weex starts with com.taobao.xxx, which should be renamed to org.apache.xxx with a low-cost upgrading way for Weex users.

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

How has the community developed since the last report?

  • Weex has participated ASOC(Alibaba summer of Code)[4] program and there will be a postgraduate from ASOC joined Weex community in this summer(July to August)
  • There is a new committer joined Weex since last report.
  • We are learning Apache Way (IP/License/Governance Model) and figured out issues that may block graduation.

How has the project developed since the last report?

  • We have 197 incoming pull request and 164 of them are merged
  • We have 55 threads in Weex mailing list
  • We have solved 200 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-05-23

When were the last committers or PPMC members elected?

2019-04-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. Yes, they are very helpful. We learned a lot about Apache Way from them.

Signed-off-by:

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

IPMC/Shepherd notes:

  • No labels