This Confluence has been LDAP enabled, if you are an ASF Committer, please use your LDAP Credentials to login. Any problems file an INFRA jira ticket please.

Page tree
Skip to end of metadata
Go to start of metadata

FINAL do not edit

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.

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 7 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 OpenWhisk. A couple of podlings failed to realise that they can submit their own reports rather than having to reply on their mentors. DLab, for instance almost failed to report for the second month, although they did have draft reports on their mailing list for previous missed reports. Three podlings Amaterasu, Livy and Tuweni didn't submit a report and have been asked to do so next month. Three other reports currently do not have sign off BatchEE, DataSketches and DLab.

There was one IP clearance.

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 of the 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. Last months proposal to do just this 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 that 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 releases 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 by the IPMC, 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 and the conversation is now focused on this.

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 ASF policy documentation is heavy on the compliance side. This situation also had 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 recently created Incubator cookbook.

A couple of podlings have not been able to attract IPMC votes on their releases in the usual 72 hours.

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 PPMC members not been signed up to their private lists.

Community

New IPMC members:

None

People who left the IPMC:

None

New Podlings

None

Podlings that failed to report, expected next month

  • Amaterasu
  • Livy
  • Tuweni

Graduations

  • OpenWhisk

Releases

The following releases entered distribution during the month of June:

  • Apache Doris 0.10
  • Apache Tuweni 0.8.0
  • Apache Flagon UserALE.js 1.0.0
  • Apache Druid 0.15.0
  • Apache OpenWhisk Runtime Node.js v1.14.0
  • Apache Training - Navigating the ASF Incubator Process 1.0
  • Apache OpenWhisk runtimes version 1.1.3.0 Released

IP Clearance

ServiceComb Toolkit project contribution

Legal has confirmed how podlings releases need to comply with policy.

Infrastructure

Infra has confirmed how podlings releases need to comply with policy.

Miscellaneous

None

Table of Contents

Annotator
BatchEE
BRPC
DataSketches
DLab
Flagon
Gobblin
Hudi
Iceberg
Milagro
MXNet
Rya
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:

  1. Release initial versions
  2. Add active contributors
  3. Demonstrate good governance through voting on process improvements.

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

None at this time.

How has the community developed since the last report?

Participation on the mailing list and issues has increased. Overall architectural discussions for the API of the first official release are also underway. The project recently voted to adopt a new logo, with input from the community.

How has the project developed since the last report?

The project's API is being solidified for its first release. There has been active coding in the last month and and more related conversations on the mailing list. We still need to increase participation in the actual code activities of the project, but interest in general is growing again.

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:

None yet, but hopefully sooner than later.

When were the last committers or PPMC members elected?

No new committers nor PPMC members have been added since the last report.

Have your mentors been helpful and responsive?

Yes. Mentors have been helpful with recent questions.

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:

None (see below).

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?

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?

N/A

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?

N/A

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 unified header
  3. Plan to have a offline forum in 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?

No answer.

Have your mentors been helpful and responsive?

No answer.

Signed-off-by:

  •  (brpc) Kevin A. McGrail
    Comments: Love the forum idea to build the community.
  •  (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 the essential details of how to actually accomplish tasks are often missing.

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.
  3. I haven't heard from any of the mentors for the last week or so, perhaps they are all on vacation.

Signed-off-by:

  •  (datasketches) Liang Chen
    Comments:
  •  (datasketches) Kenneth Knowles
    Comments:
  •  (datasketches) Furkan Kamaci
    Comments:

IPMC/Shepherd notes:

Justin Mclean: Please ask your mentors for help, they can setup most things or direct yo to when you can get help. If your mentors can't help then ask on teh incubator general list.


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. Execute the SGA between EPAM and the ASF so code can be imported - done
  2. Complete on-boarding of initial committers - done
  3. Work toward an initial Apache release - release branch created – done

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

Not this time

How has the community developed since the last report?

All initial committers have completed on-boarding. Also we've added couple of new contributors (some of them are waiting for PPMC to be created). All new contributors are currently onboarding and doing initial work to prove contribution:

  • Andriy Yatskovets
  • Kirill Makhonin
  • Vitalii Solodilov
  • Dmitriy Karbyshev
  • Aliaksandr Semianets

Also a few new contributors will start submitting their .icla files soon:

  • Andrii Dumych
  • Mykola Bodnar

How has the project developed since the last report?

The team fully switched our work to Apache Infrastructure: JIRA, Git.

First release has been made https://github.com/apache/incubator-dlab/releases/tag/2.1-RC2

Team is actively working on release 2.2 features.

There will be many new features and conceptual changes introduced in upcoming release. We are introducing a concept of projects within DLab, which will allow to control permissions for groups of Dlab users, improve collaboration capabilities.

Major improvements will be made in terms of GCP platform deployment. GCP will support majority of the features, currently available in DLab for AWS and Azure Clouds.

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

When were the last committers or PPMC members elected?

2019-18-04

Have your mentors been helpful and responsive?

Yes, mentors have been helpful with onboarding and were providing all answers timely. We just wish the podling report submission process could be supported more timely.

Help needed by DLab team from Apache:

We would highly appreciate if following page could start being populated: https://incubator.apache.org/clutch/dlab.html, currently there are many URL’s missing and empty sections.

The team can provide all needed information, but unfortunately we don't ability to Edit this page.

Signed-off-by:

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

IPMC/Shepherd notes:


Flagon

Apache Flagon is a generalized user behavioural logging platform for web pages and thin-client applications

Apache Flagon has been incubating since 2016-07-13; Apache Flagon has officially changed its name from Apache SensSoft.

Three most important unfinished issues to address before graduating:

  1. Accelerate release frequency and reduce branch complexity in repos to reduce adoption, contributor disincentives.
  2. Grow the Apache Flagon Committer/Contributor/Community Base around our core product Apache UserALE.js (Incubating)
  3. Complete the issues highlighted at the Apache Flagon Roadmap [1]

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

Apache Flagon is currently suffering from unresponsive mentors:

  • Dave Meikle has been active and engaged, aside from a prolonged outage due to a long-term illness. We are grateful for Dave's help and assistance since then.
  • Lewis McGibbney has been uncharacteristically unresponsive on dev@, private@, and to PM. Note that Lewis has been a champion for us and have confidence that he will return to activity.
  • Atri Sharma has been wholly inactive. We tried to report this in our last Q1 report; when posted to dev@ for review, he maintained that he didn't the ability to cast binding VOTEs as an excuse for non-engagement. We softened the language in our Q1 report and encouraged him to participate by providing guidance, mentorship, and engaging in community VOTEs. We haven't heard from him since despite numerous requests for help and support posted to private@

As a result of long periods of mentor absence:

  • ReRelease of v1.0.0 (at IPMC ) was delayed until mentors (Dave) were available to guide us through a potential copyright issue (resolved).
  • Prolonged the process of our name change as we struggled to explore Apache documentation and understand what we had to change (in process; HUGE thanks to INFRA for assisting us with some of the details).
  • Is presently impeding our release process (not enough binding VOTES) after tightening release procedures, and working hard to clean up our branch structure to increase this cadence.
  • We have struggled to get timely IPMC sign-off on REPORTs and have been unable to post these ourselves to the incubator wiki for lack of permission.
  • We have had to abandon our prior NPM distribution as it was released by a non-responsive mentor on their personal NPM account (we don't have credentials). [2]

NOTE as of the date of REPORT (6/26/2019) our ReRelease of Apache Flagon UserALE.js (Incubating) v1.0.0 has been under VOTE on general@ for 9 days (6/17/2019). After community and PPMC VOTE, we needed +2 binding votes. We received helpful comments from Justin McLean, but despite numerous reminders to VOTE, we still have yet to receive the last +1 binding VOTE from IPMC. We are concerned that without active mentors, our release cadence will remain slow and unresponsive to user communities.

With Dave Meikle's help, we will be searching for two additional mentors so that our community is self sufficient. We recommend dropping Atri Sharma from the project for non-participation.

How has the community developed since the last report?

The community has:

  • improved release processes and code base to expedite future releases [3,4]
  • gathered a wide base of users that are eagerly anticipating UserALE.js v2.0.0 via NPM (under VOTE within the community as of this date).
  • discussed with external parties research applications with university research labs in machine learning and social computing.
  • the community has organically grown with a new contributor, who is participating in VOTEs
  • the community expects to complete major updates to documentation on website and READMEs, in early JUL 2019. Wiki updates will complete shortly thereafter.

Despite consistent challenges to our community throughout 2018, we are showing signs of growth, continue to have a relevant project, and are well postured to accelerate growth in the coming quarters. We remain committed to learning and adopting the Apache Way.

How has the project developed since the last report?

  • Completed migration to GitBox Repos
  • Project maturity roadmaps (Wiki) and version release plans (JIRA) continue to be maintained.
  • JIRA boards continue to be maintained.
  • Core product source code for front-end and back-end assets has been steadily maintained and modernized.

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

When were the last committers or PPMC members elected?

Arthi Vezhavendan was added to Committer base on 2017-01-24
Dave Meikle was added to PPMC on 2018-11-24
Atri Sharma was added to PPMC on 2018-11-24

Have your mentors been helpful and responsive or are things falling

through the cracks?

See mentorship issues above.

We are now aware that we can lean on general@ or INFRA for support without permission and have deepened our knowledge of Apache processes so that committers are more self-sufficient.

Signed-off-by:

  •  (flagon) Lewis John McGibbney
    Comments:
  •  (flagon) Dave Meikle
    Comments: Great to have two releases out post the name change. Now we need to work on improving the mentor situation and on building the community.
  •  (flagon) Atri Sharma
    Comments:

[1] https://cwiki.apache.org/confluence/display/FLAGON/Roadmaps
[2] https://www.npmjs.com/package/useralejs
[3] https://dist.apache.org/repos/dist/dev/incubator/flagon/
[4] https://cwiki.apache.org/confluence/display/FLAGON/UserALE.js+Release+Manage ment+Procedure

IPMC/Shepherd notes:

Justin Mclean: All PPMC members in the roster have permission to edit the incubator report, you don't need to rely on mentors for that. For extra mentors please ask on the incubator list.


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:

  1. Revisit Apache Maturity Model assessment. [In progress]
  2. Ensure heavy contributors are awarded committership. [In progress]
  3. Complete house-keeping tasks like revisiting website, podling namesearch. [In progress]

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?

  • 62% of commits were from non-committer contributors.
  • Healthy engagement and activity of committers and contributors.
  • Email stats since last report: user@gobblin.incubator.apache.org : 21 dev@gobblin.incubator.apache.org : 1744
  • There have been 82 Commits since last report: git log --format='%ci' | grep -cE '((2019-0(4|5|6|7)))'
  • 51 ie. 62% of those commits were by non-committers: git log --format='%ae %ci' | grep -E '((2019-0(4|5|6|7)))' | cut -d ' ' -f 1 | sort | uniq -c | sort -n
  • Community's proposal to present in ApacheCon NA 2019 was accepted. (joint presentation by Paypal and LinkedIn engineers).

How has the project developed since the last report?

  • Encryption support for Salesforce connector.
  • GobblinEventBuilder enhancements.
  • Metric reporter integration with dataset discovery.
  • Enhancement to RateBasedLimiter.
  • Dynamic config support in JobSpecs.
  • GaaS disaster recovery mode skeleton.
  • Addition of MySQL based DAG State store.
  • New filesystem based SpecProducer.
  • Auto-scalability in Gobblin on Yarn mode.
  • Container request and allocation optimizations.
  • New SQL dataset descriptor for JDBC sourced datasets.
  • Speculative safety checks in HiveWritable writer.
  • New Async loadable FlowSpecs.

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.

Have your mentors been helpful and responsive?

Yes.

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?

No Answer.

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: The issues mentioned above that needs board attention are probably just a question of updating the project page file with the proper done status/date. Please speakup if the community needs help from mentors updating the file.
  •  (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:

  1. Update build for Apache release, add LICENSE/NOTICE to Jars.
  2. Make the first Apache release. (https://github.com/apache/incubator-iceberg/milestone/1)
  3. Grow the Iceberg community

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

  • No issues that require attention.

How has the community developed since the last report?

  • Community growth has continued with several new contributors and reviewers
  • Community has decided on style and added checking to CI for most modules
  • Community has started work on extending the spec for new use cases

How has the project developed since the last report?

  • Much more content on iceberg.apache.org has been added
  • 74 pull requests have been merged, many reviewed by new community members
  • Work has begun to add row-level deletes and upserts to the format
  • Added support for Spark streaming, a catalog API, and numerous bug fixes
  • Contributors are reviewing code, submitting substantial features, and improving dev practices

How would you assess the podling's maturity?

Please feel free to add your own commentary.

  •  Initial setup (name clearance approval pending)
  •  Working towards first release
  •  Community building
  •  Nearing graduation
  •  Other:

Date of last release:

None yet

When were the last committers or PPMC members elected?

None yet

Have your mentors been helpful and responsive?

Yes.

Signed-off-by:

  •  (iceberg) Ryan Blue
    Comments: I wrote the first pass of the report.
  •  (iceberg) Julien Le Dem
    Comments:
  •  (iceberg) Owen O'Malley
    Comments: +1 from discussion on dev list
  •  (iceberg) James Taylor
    Comments:
  •  (iceberg) Carl Steinbach
    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:

  1. Continue to build relevant and useful crypto libs and applications for decentralized networks in order to grow the ecosystem of users and contributors to the project.
  2. Get all functions of the project in line with the Apache Way so we stay in compliance and can get a relase under our belts.
  3. Get a relase under our belts!

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're growing the list of potential new contributors and collaborators. We have added two new additional contributors and expect more soon as we get milagro-crypto-c in line for release.

How has the project developed since the last report?

The main contributors continue to get their feet wet with Apache processes and methodologies. Big shout out to the infra team who have been helpful in dealing with the paculiarities of our project. As an example, we have managed to migrate issue tracking to GitHub, but are still using JIRA for release management task tracking. Most importantly, we have now moved the website to the asf-site branch model and are ready to update the site with documentation. Qredo Ltd in London has signed a software contributor agreement that has been registered with legal office. Qredo is contributing its server code to become the Decentralized Trust Authority, the first "product" release after the crypto library 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:

XXXX-XX-XX

When were the last committers or PPMC members elected?

Last week.

Have your mentors been helpful and responsive?

Jean-Frederic Clere has been great, helpful and hopefully Nick will stay involved.

Signed-off-by:

  •  (milagro) Nick Kew
    Comments: This project has sprung to life! I'll post a note about specificity vs "Last week"!
  •  (milagro) Jean-Frederic Clere
    Comments:

IPMC/Shepherd notes:

  • Drew Farris (shepherd): Added a new mentor this month. Both mentors active on the mailing lists. Increased activity throughout the month of June.

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:

  • Drew Farris (shepherd): Very active project. One mentor observed on the mailing list, otherwise not a significant amount of mentor activity apparent - possibly due to the proximity toward graduation.
  • Justin Mclean: I'm not sure why the website redesign is an issue for the IPMC or board. Can you please give some more detail.

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?

Our two mentors are helpful and responsive.

Signed-off-by:

  •  (rya) Josh Elser
    Comments: Steady progress to graduation.
  •  (rya) Billie Rinaldi
    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:

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?

Mentors are very helpful in providing guidance.

Signed-off-by:

  •  (tvm) Byung-Gon Chun
    Comments:
  •  (tvm) Sebastian Schelter
    Comments:
  •  (tvm) Henry Saputra
    Comments: Working on migration or resources to ASF infra and managed resources. But the community still growing and active.
  •  (tvm) Timothy Chen
    Comments:
  •  (tvm) Furkan Kamaci
    Comments:
  •  (tvm) Markus Weimer 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?

No answer.

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?

Yes, they are very helpful. We learned a lot about Apache Way from them.

Signed-off-by:

  •  (weex) Willem Ning Jiang
    Comments: Weex is try hard to find solution for their issue, I agree with Myrle, they are nearing graduation.
  •  (weex) Myrle Krantz
    Comments: Weex is doing an excellent job of identifying their own issues, and seeking solutions in the broader foundation.
    I concur that they are nearing graduation.
  •  (weex) Jan Piotrowski
    Comments:

IPMC/Shepherd notes:

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

  • No labels