FINAL FINAL FINAL - MENTOR SIGN OFF ONLY PLEASE- REPORT SUBMITTED - DO NOT EDIT
NOTE that the content for this month report is in markdown format- please do not remove any formatting characters when adding your reports.
...
| Markdown |
|---|
# 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.
This monthly report is in markdown so that it's easier to read. If you are
not viewing this in that format, it can be seen here:
https://cwiki.apache.org/confluence/display/INCUBATOR/January2020
There are presently 46 podlings incubating. In December, podlings executed
9 distinct releases. We added no new IPMC members and no IPMC members
retired. There was one requested IP clearance, but it has an outstanding
issue.
We have one new podling this month NuttX; another is under discussion
YuniKorn. The Druid project graduated last month. BatchEE exited the
incubator to become a subproject of Geronimo. At least one podling is
heading towards graduation in the next few months.
NuttX had a long useful discussion on it's entry into the incubator due to
a number of potential issues, all were discussed and sorted and the podling
has a good idea of what is expected to happen for it to graduate.
There was also discussion on YuniKorn name and if the ASF would get the
rights to that name. Cloudera's legal team have been involved.
New podlings are being asked to double check that they have permission to
use their name as it a lot of work for Infra to change podlings name.
Several podlings did not report and will be asked to report again next
month; they include Annotator, Milagro, Myriad and Taverna. Myriad is
discussing retirement. I would guess this is due to the holiday season,
despite warning being given and asking podling to get the reports in early.
We also had a large number of reports that needed manual fixing this month,
podlings in question have been reminded on how to format their reports.
Warble is in hibernation and has not been asked to report again as there's
nothing to report. At some point Infra will need to decide what to do with
this project.
TubeMQ is still having trouble bootstrapping and some of its mentors seem
missing, I've asked for mentors to respond on it private list and asked
what is happening on the dev list to move them forward. TubeMQ did report
late but the report wasn't accurate and was rejected and resubmitted.
The Incubator release area continued to be cleaned up.
The new branding/trademark question (added the podling report) has made
a number of podlings realise they were not paying attention to this and
has increased awareness of what is needed here. An open source site awarded
several podlings awards but had several branding and trademark issues.
These were quickly resolved.
## Community
### New IPMC members:
None
### People who left the IPMC:
None
## New Podlings
- NuttX
## Podlings that failed to report, expected next month
- Annotator
- Milagro
- Myriad
- Taverna
## Graduations
- Druid
The board has motions for the following:
- None
## Releases
The following releases entered distribution during the month of
December:
- Crail 1.2
- Dlab 2.2
- Druid 0.16.1
- ECharts 4.6.0
- Hivemall 0.6.0
- IOT DB 0.8.2
- IoTDB 0.9.0
- Tuweni 0.10.0
- Tvm v0.6.0
## IP Clearance
- airflow-on-k8s-operator to Airflow (not accepted yet)
## Legal / Trademarks
- An open source site awarded several podlings awards but had several
branding and trademark issues. These was quickly resolved.
## Infrastructure
- JIRA tickets and cloning issues issue
- Discussion about podling names and podlings changing names
## Miscellaneous
- None
|----------------------------------------------------------------------
Table of Contents
[APISIX](#APISIX)
[DLab](#DLab)
[Flagon](#Flagon)
[Gobblin](#Gobblin)
[Hudi](#Hudi)
[Iceberg](#Iceberg)
[Livy](#Livy)
[MXNet](#MXNet)
[NuttX](#NuttX)
[PonyMail](#PonyMail)
[StreamPipes](#StreamPipes)
[Teaclave](#Teaclave)
[TubeMQ](#TubeMQ)
[TVM](#TVM)
[Weex](#Weex)
|----------------------------------------------------------------------
--------------------
## 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
- [X] 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:
- [X] (apisix) Willem Ning Jiang
Comments:
- [X] (apisix) Justin Mclean
Comments:
- [X] (apisix) Kevin Ratnasekera
Comments:
- [X] (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
- [X] Working towards first release
- [X] Community building
- [X] 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:
- [X] (dlab) P. Taylor Goetz
Comments:
- [X] (dlab) Henry Saputra
Comments: Will urge the community to decide for new name ASAP
- [ ] (dlab) Konstantin I Boudnik
Comments:
- [X] (dlab) Furkan Kamaci
Comments:
### IPMC/Shepherd notes:
Justin Mclean: Is infra aware there is going to be a name change? It
might be best to change name on graduation rather than before.
Please discuss with infra first.
--------------------
## 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 developed 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 performance.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [x] 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 first Apache Release.
### Is the PPMC managing the podling's brand / trademarks?
Yes, We keep tracking podling's brand / trademarks.
### Signed-off-by:
- [x] (dolphinscheduler) Sheng Wu
Comments: Mail list communications become more active. Good to see
this.
- [ ] (dolphinscheduler) ShaoFeng Shi
Comments:
- [X] (dolphinscheduler) Liang Chen
Comments:
- [X] (dolphinscheduler) Furkan KAMACI
Comments:
- [X] (dolphinscheduler) Kevin Ratnasekera
Comments:
### IPMC/Shepherd notes:
--------------------
## Flagon
Flagon is a behavioral logging platform for web pages and apps
Flagon has been incubating since 2016-07-13.
### Three most important unfinished issues to address before graduating:
1. Grow the Flagon Committer/Contributor/Community Base
2. Refine release processes for core analytic product (Distill)
3. Finalize (through vote) Flagon logo, get marketing approvals (e.g swag)
### Are there any issues that the IPMC or ASF Board need to be aware of?
* None at this time. Following mentors' comments in last (Q3 2019)
report, Flagon will likely draft and vote on a graduation resolution in
the new year.
### How has the community developed since the last report?
* continued improving release processes and code base
* continued to generate a wide user base
* discussing collaborations for R&D applications
* new potential committers have been identified and will be introduced to
the community in the new year
### How has the project developed since the last report?
* Project maturity roadmaps & release plans (JIRA) are maintained
* JIRA boards continue to be maintained.
* Core product source code is well maintained
* Analytical products are being refactored to grow user base
* Continued attention and improvement in Apache Process
* Expect UserALE.js v 2.1.0 RC in Q1 2020
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [X] Initial setup
- [X] Working towards first release
- [X] Community building
- [X] Nearing graduation
- [ ] Other:
### Date of last release:
* 2019-08-21 Flagon UserALE.js (Incubating) 2.0.2
### When were the last committers or PPMC members elected?
* Furkan Kamaci (Mentor) 2019-07-24
* Tim Allison (Mentor) 2019-07-17
* Arthi Vezhavendan (PPMC) 2017-01-24
### Have your mentors been helpful and responsive?
* Our mentors have been very supportive and
responsive.
### Is the PPMC managing the podling's brand / trademarks?
* 'Flagon' was cleared through the Apache PODLINGNAMESEARCH
workflow.
* 'Flagon' branded images graphics are under development and
will conform to Apache's Trademark and Branding policies.
### Signed-off-by:
- [ ] (flagon) Lewis John McGibbney
Comments:
- [ ] (flagon) David Meikle
Comments:
- [ ] (flagon) Tim Allison
Comments:
- [X] (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:
1. Revisit Apache Maturity Model assessment. [In progress since last
report]
2. Ensure heavy contributors are awarded committership. [In progress
since last report]
3. Complete house-keeping tasks like revisiting website, podling
namesearch. [In progress since last report]
### 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?
* Add support to deploy GaaS in Azure.
* Converter to eliminate recursion in Avro schemas.
* Make token refresh mechanism pluggable for long running Gobblin-on-Yarn
applications.
* Refactor code for reporting Kafka Extractor stats to allow greater
reuse.
* Add support in GaaS to recognize Http and Hive based datasets.
* Add multi-dataset support in GaaS to allow movement of multiple
datasets in a single flow.
* Add support to recognize datasets with Unix timestamp based versions
for file based distcp.
* Custom progress reporting from jobs running in MR mode to enable
speculative execution.
* Source-based PK chunking for the Salesforce connector to use a single
PK chunking query to improve chunk distribution and conserve batch API
calls.
* Parquet support for complex types and support both apache parquet and
twitter parquet
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [ ] Working towards first release
- [ ] Community building
- [X] 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?
Yes.
### Signed-off-by:
- [X] (gobblin) Jean-Baptiste Onofre
Comments:
- [ ] (gobblin) Olivier Lamy
Comments:
- [X] (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 Apache releases.
2. Continue to grow the community.
3. Work towards graduation. Finish pending issues in the Maturity Matrix
document :
https://cwiki.apache.org/confluence/display/HUDI/Apache+Hudi+Maturity+Matrix
### 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. 630 conversations on dev ML across ~100 topics
2. 70 participants during this period
### How has the project developed since the last report?
1. ~130 Commits in gitbox
2. ~200 issues opened on Jira. ~80 issues resolved in Jira
3. Hudi 0.5.0 (first Apache Release) released. Next release 0.5.1 planned
for January 2020.
4. 3 new committers (vinoyang, leesf and bhavanisudha) added to project.
5. Apache Hudi is now packaged as part of AWS EMR. Apache Hudi talk in
AWS re:Invent was well received
6. Project took a first pass at assessing Apache Maturity Model for the
project.
### How would you assess the podling's maturity?
The project now has a diverse developer and user community, and seeing
increased adoption.
- [ ] Initial setup
- [ ] Working towards first release
- [X] Community building
- [X] Nearing graduation
- [ ] Other:
### Date of last release:
2019-10-24
### When were the last committers or PPMC members elected?
2019-11-08 - Bhavani Sudha Saktheeswaran, Vino Yang and Leesf.
### Have your mentors been helpful and responsive?
Yes. Very helpful!
### Is the PPMC managing the podling's brand / trademarks?
Yes
### Signed-off-by:
- [x] (hudi) Thomas Weise
Comments:
- [x] (hudi) Luciano Resende
Comments:
- [ ] (hudi) Kishore Gopalakrishnan
Comments:
- [X] (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. Grow the Iceberg community
2. Add more committers and PPMC members
### 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?
In the 4 months since the last report, 138 pull requests were merged for an
average of 34.5 per month. While this is down from the previous monthly
average of 49.6 per month for June through August, this contribution rate
is still very active and healthy. Contributions are coming from a regular
group of contributors outside of the initial set of committers, which is a
positive indication for adding new committers and PPMC members over the
next few months.
The community released the first version of Apache Iceberg,
0.7.0-incubating. This release used the "standard" incubator disclaimer and
included convenience binaries. The release candidate votes were very active
with community members testing out the release and reporting problems.
There was an Apache Iceberg talk at ApacheCon NA in September.
### How has the project developed since the last report?
- The community is building support for the upcoming Spark 3.0 release
- The first PR from the vectorization branch has been merged into master
- Support for IN and NOT IN predicates was contributed
- Python added support for Hive metastore tables and the read path is
near commit
- Flaky tests have been fixed
- Baseline checks (style, errorprone, findbugs) are now applied to all
modules
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [ ] Working towards first release
- [x] Community building
- [x] Nearing graduation
- [ ] Other:
### Date of last release:
- 0.7.0-incubating was released 25 October 2019
### When were the last committers or PPMC members elected?
- Anton Okolnychyi was added 30 August 2019
### Have your mentors been helpful and responsive?
Yes. 4 of 5 mentors voted on the 0.7.0-incubating IPMC vote. Thanks to our
mentors for being active!
### Is the PPMC managing the podling's brand / trademarks?
Yes, the podling is managing the brand and is not aware of any issues.
The project name has been approved.
### Signed-off-by:
- [x] (iceberg) Ryan Blue
Comments:
- [ ] (iceberg) Julien Le Dem
Comments:
- [X] (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:
1. Grow the community to get more reviews and content.
However, at this point, the community might want to consider that it
is a stable project that has met its initial functional goals. With
multiple public releases under its belt, it might be worth discussing a
time to graduate. A substantial increase in community activity in terms of
code contribution and related community growth might occur after a new set
of functionality/scope is identified for the project. But to date, the
existing community and code are following the Apache way.
2.
3.
### 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?
Moderate activity on mailing lists and code
### How has the project developed since the last report?
Livy thrift JDBC part is GA now. Currently the community is working on HA
feature. And 0.7.0 release is ongoing.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [ ] Working towards first release
- [x] Community building
- [x] Nearing graduation
- [ ] Other:
### Date of last release:
2019-04-01
### When were the last committers or PPMC members elected?
2019-01-22
### Have your mentors been helpful and responsive?
Yes
### Is the PPMC managing the podling's brand / trademarks?
Yes
### Signed-off-by:
- [ ] (livy) Bikas Saha
Comments:
- [ ] (livy) Brock Noland
Comments:
- [ ] (livy) Luciano Resende
Comments:
- [X] (livy) Jean-Baptiste Onofre
Comments: Still planning to contribute what I proposed on the mailing list while ago
### 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.
2. 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?
* The number of GitHub contributors increased to currently 763
(2019-12-31; +3.8% since last report)
* Active discussions on user forums
* https://discuss.mxnet.io/ (English, 2.3K registered users (+9.5%)
and 7.4K posts (+7.2%))
* https://discuss.gluon.ai/ (Chinese, 8.5K registered users (+10.4%)
and 21.6K posts(+2.3% since last report))
* Active blogs and social media presence
* Medium (https://medium.com/apache-mxnet) w/ 1.7k followers (+6.2%)
* Twitter account (https://twitter.com/ApacheMXNet) w/ 2.4k followers
(+4.3%)
* Meetup group
(https://www.meetup.com/pro/deep-learning-with-apache-mxnet/) w/ 10
groups in 8 countries, 2207 members
* Active video channels
* YouTube channel (https://www.youtube.com/apachemxnet) w/ 949
subscriber (+12.8% since last report)
* Chinese YouTube channel
(https://www.youtube.com/channel/UCjeLwTKPMlDt2segkZzw2ZQ) w/ 5.4k
subscribers (+8.2%)
* (in China) bilibili space (https://space.bilibili.com/209599371) w/
21k subscriber (+15.4% since last report)
* Highlights in MXNet ecosystem
* MXNet Gluon book published (https://zh.d2l.ai/) first 34k hard copies
* Dive into Deep Learning has 59K 28-day active users, and has
attracted 15K stars & 210+ contributors on GitHub. It has been adopted
as a textbook or reference book by 30+ universities in U.S., China,
Spain, Brazil, India, and Australia, such as MIT, UC Berkeley, CMU,
IIT Bombay, PKU, and SJTU.
* GluonCV v0.6.0 release
(https://github.com/dmlc/gluon-cv/releases/tag/v0.6.0)
* GluonNLP v0.8.2 release
(https://github.com/dmlc/gluon-nlp/releases/tag/v0.8.2)
* GluonTS v0.4.2 release
(https://github.com/awslabs/gluon-ts/releases/tag/v0.4.2)
* MXNet Model Server v1.0.9 release
(https://github.com/awslabs/mxnet-model-server/releases/tag/v1.0.9)
* GluonFace (https://github.com/THUFutureLab/gluon-face)
* DeepInsight (https://github.com/deepinsight/insightface)
### 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:
* numpy-compatbile deep learning:
https://github.com/apache/incubator-mxnet/projects/14
* CPU performance and quantization:
https://github.com/apache/incubator-mxnet/projects/15
* MKLDNN 1.0 upgrade:
https://github.com/apache/incubator-mxnet/projects/16
* New Website Launch:
https://github.com/apache/incubator-mxnet/projects/17
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
- [x] 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:
- [x] (mxnet) Michael Wall
Comments:
- [ ] (mxnet) Bob Paulin
Comments:
- [ ] (mxnet) Jason Dai
Comments:
### IPMC/Shepherd notes:
--------------------
## NuttX
NuttX is a mature, real-time embedded operating system (RTOS) with
emphasis on standards compliance and small footprint.
NuttX has been incubating since 2019-12-09.
### Three most important unfinished issues to address before graduating:
1. Clear any potential infringing use of the NuttX trademark
2. Grow the community outside the old project and around Apache
infrastructure
3. Make the first release under the Apache umbrella.
### Are there any issues that the IPMC or ASF Board need to be aware of?
Even though the project is in its early incubation stages, its maturity
allowed us to elect 3 new members:
Ken and Masayuki are both long time contributors to NuttX. They were
interested in becoming Committers/PPMC members and supposed to be in the
initial committers list but missed the window by few hours (the voting
had already started).
Brennan is also a long time contributor, and recently has put in some
crazy hours to convert our old DokuWiki to Confluence.
The project consists of two main repositories, _nuttx_ and _apps_.
These two repositories are hosted by Apache in
https://gitbox.apache.org/repos/asf?p=incubator-nuttx.git
and https://gitbox.apache.org/repos/asf?p=incubator-nuttx-apps.git
There are also 3 supporting repositories that have GPL licenses
and hence can't be released under the Apache license.
Nothing in these GPL repositories is ever delivered with NuttX releases.
There are only references in the documentation to aid in building and
installing the operating system.
It is unclear where these repositories should reside.
### How has the community developed since the last report?
The project used to have a google group where questions, patches and
technical issues were discussed.
Now, three mailing lists are in place: _dev_, _commit_ and _private_.
_dev_ has 100 subscribers and is getting quite heavy traffic as the
community is debating the next steps of the project.
In the meantime, some contributors have already submitted a few patches
and PRs.
However, as it was expected, user activity has dropped down a little
compared to the google group.
First, not all google group subscribers are subscribed to the _dev_
mailing list.
Additionally, moving to Apache required reviewing the previous workflow
and developing new requirements. This is currently the center of almost
all discussions in the mailing list.
Things are anticipated to settle down and get back to normal once
our new way of working is sorted out.
Regarding the project committee, it started with 12 members
(4 mentors and 8 initial committers).
Since incubation, 2 committers and 1 PPMC member have been added.
### How has the project developed since the last report?
The project is only in its early days of incubation.
The necessary resources are set up. The repositories have moved from
Bitbucket to GitHub/GitBox and the Wiki from DokuWiki to Confluence.
As noted above, the workflow requirements are still under development,
it is expected that the project will see more contributions once this
has been taken care of.
First version of the website is available in github.io
(https://apache-nuttx-website.github.io/). It will be moved to Apache
servers.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [X] Initial setup. Repositories, accounts and mailing lists are in
place.
- [ ] Working towards first release
- [ ] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
2019-11-16
This is the date of the last NuttX release.
There is yet to be a release for Apache NuttX.
### When were the last committers or PPMC members elected?
Last elected committers:
- Brennan Ashton: 2019-12-19
- Kenneth Pettit: 2019-12-22
Last elected PPMC:
- Masayuki Ishikawa: 2019-12-23
### Have your mentors been helpful and responsive?
Mentors are helpful and responsive.
### Is the PPMC managing the podling's brand / trademarks?
* Gregory Nutt registered the NuttX trademark in the US.
* Some projects are distributing modified versions of NuttX under the
name NuttX. These issues need to be addressed before graduation.
### Signed-off-by:
- [ ] (nuttx) Junping Du
Comments:
- [X] (nuttx) Justin Mclean
Comments:
- [ ] (nuttx) Mohammad Asif Siddiqui
Comments:
- [ ] (nuttx) Flavio Paiva Junqueira
Comments:
### IPMC/Shepherd notes:
Justin Mclean: While off to a good start the podling has run into several
issues, and seems to need a bit more focus before it has a functioning
PPMC.
Some of these issues are due to ignoring mentors/incubator advice. I'd
suggest the project focus on more immediate needs rather than hypothetical
issues that may or may not occur in the future.
--------------------
## 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?
No answer.
### 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
- [x] Community building
- [x] Nearing graduation
- [ ] Other:
### Date of last release:
2019-04-20
### When were the last committers or PPMC members elected?
2017-06-01 (Sebb). We should be looking for and encouraging more
candidates :)
### Have your mentors been helpful and responsive?
No answer.
### Is the PPMC managing the podling's brand / trademarks?
No answer.
### Signed-off-by:
- [ ] (ponymail) John D. Ament
Comments:
- [x] (ponymail) Sharan Foga
Comments: Good to see that responding to user queries has now
improved. Still need to formulate a more concrete engagement strategy for
building the community.
### IPMC/Shepherd notes:
Dave Fisher: Given the movement to lists.apache.org planned by
Infrastructure does it make sense to graduate this podling a PMC like
Whimsy? One that does not do releases?
--------------------
## StreamPipes
StreamPipes is a self-service (Industrial) IoT toolbox to enable non-
technical users to connect, analyze and explore (Industrial) IoT data
streams.
StreamPipes has been incubating since 2019-11-11.
### Three most important unfinished issues to address before graduating:
1. Finish license review of third-party dependencies
2. Make a first Apache release
3. Grow the community
### Are there any issues that the IPMC or ASF Board need to be aware of?
There are no issues right now.
### How has the community developed since the last report?
Although our priority in the last reporting period was on finishing the
initial setup, there are some notable things regarding community
development:
- A few new people appeared on the mailing list expressing their interest
to contribute to StreamPipes
- First pull requests from an external committer were merged
- Many users appeared on the Slack channel or sent emails and asked
questions around the installation/usage of StreamPipes, we hope that some
of them will consider to contribute in the future
- We met people from two companies and talked about the possibility to
contribute to StreamPipes
- The number of Twitter followers has increased (currently at 94)
- The number of Github stars has increased (currently at 102)
Community development will be the focus of the next reporting period.
### How has the project developed since the last report?
We finished the initial setup:
* The website is now online at streampipes.apache.org, and we added pages
that explain how to participate in the project
* All Git repos were transferred to the ASF
* Setup of several CI/CD pipelines based on Github Actions to build the
website and code
* Setup of a CI/CD pipeline in the ASF Jenkins to publish snapshots to
the ASF Nexus
* Finished setup of Jira and migrated old issues from the previous Gitlab
to Jira
* Finished setup of the StreamPipes Confluence space and moved existing
content to Confluence
* Currently, we are finishing a license review to properly create LICENSE
and NOTICE files
* Having completed the initial setup, we are now shifting the focus back
to feature development
In the next month, we plan to work towards the first Apache release and
also intensify work on community development.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [x] Working towards first release
- [x] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
No answer.
### When were the last committers or PPMC members elected?
No new committers were elected beyond the initial committers. Two people
mentioned on the mailing list that they might be willing to contribute to
StreamPipes.
### Have your mentors been helpful and responsive?
Our mentors are very responsive and provide good feedback. They provided
very good guidance during the initial setup phase of the project, thanks
a lot. We would also like to thank the people from INFRA who were very
responsive and helpful in getting some issues resolved during the
transition phase.
### Is the PPMC managing the podling's brand / trademarks?
* The project name StreamPipes got approved by VP, Brand on December 2nd.
### Signed-off-by:
- [X] (streampipes) Christofer Dutz
Comments:
- [X] (streampipes) Jean-Baptiste Onofré
Comments:
- [ ] (streampipes) Julian Feinauer
Comments:
- [X] (streampipes) Justin Mclean
Comments:
- [ ] (streampipes) Kenneth Knowles
Comments:
### IPMC/Shepherd notes:
Justin Mclean: There is more to managing the brand than just having
the project name approved.
--------------------
## 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
- [x] 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:
- [X] (teaclave) Furkan Kamaci
Comments:
- [ ] (teaclave) Jianyong Dai
Comments:
- [ ] (teaclave) Luciano Resende
Comments:
- [X] (teaclave) Matt Sicker
Comments: Thanks to some mailing list configuration updates,
communication is happening more often on-list.
- [ ] (teaclave) Zhijie Shen
Comments:
### IPMC/Shepherd notes:
--------------------
## TubeMQ
TubeMQ is a distributed messaging queue (MQ) system.
TubeMQ has been incubating since 2019-11-03.
### Three most important unfinished issues to address before graduating:
1. Bootstrap the Apache project and migrate repos to Apache.
2. Grow the community to involve more contributors and increase the
diversity.
3. Polish the code and document to satisfy the Apache way.
### Are there any issues that the IPMC or ASF Board need to be aware of?
Needs mentors and IPMCs to help to bootstrap the project and follow the
Apache way to grow the community.
### How has the community developed since the last report?
Currently the project is still on migrating, because of the migrating
gap, there's 60+ GH issues and 80+ GH PRs submitted,
and over 25 contributors on this project, but this was not happened in
Apache JIRA/repo, we will migrate them soon.
Also We hosted 3 meetups to promote this project.
### How has the project developed since the last report?
Towards migrating to Apache incubator, like building home pages, launch
first Apache release.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [x] Initial setup
- [x] Working towards first release
- [ ] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
None
### When were the last committers or PPMC members elected?
None
### Have your mentors been helpful and responsive?
Yes
### Is the PPMC managing the podling's brand / trademarks?
Still on migrating.
### Signed-off-by:
- [x] (tubemq) Junping Du
Comments: IPMCs and PPMCs need to work hard together towards the goal
of graduating.
- [X] (tubemq) Justin Mclean
Comments: Off to a slow start and needs to engage with mentors more,
more communication on the mailing list is needed.
- [ ] (tubemq) Sijie Guo
Comments:
- [ ] (tubemq) Zhijie Shen
Comments:
- [X] (tubemq) Jean-Baptiste Onofre
Comments: Slow bootstrapping, but it seems it moved forward.
I would be happy to help.
### IPMC/Shepherd notes:
Junping Du: The project get bootstrap a bit late due to misunderstanding
on Champion role of the project. The email list and JIRA are setup just
recently, so contributors and committers are still learning how to
communicate through JIRA and dev alias - it takes time but things are
getting better.
Justin Mclean: Your mentors can't help if you don't communicate on the
dev list. Your number one aim should be to move communication on list and
work with your mentors in the open to complete the bootstrap process. This
is the PPMC responsibility not just the mentors or the IPMC as mentioned in
the issues. Several mentors and IPMC requests have gone unanswered, please
make sure these are responded to.
Dave Fisher: It is important that PPMC Members drive the move with the
help of active Mentors. I feel that Junping is in a dual role but is less
experienced. Justin and JBO are the experienced mentors that will need to
step in with the guidance. Two months in including the year end holidays
the podling is actually doing OK.
--------------------
## 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
- Sep https://discuss.tvm.ai/t/tvm-monthly-september-2019/4219
- Oct https://discuss.tvm.ai/t/tvm-monthly-oct-2019/4587
- Nov https://discuss.tvm.ai/t/tvm-monthly-nov-2019/5038
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [ ] Working towards first release
- [x] Community building
- [x] 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:
- [x] (tvm) Byung-Gon Chun
Comments: Great progress! Good job on the first Apache release!
- [ ] (tvm) Sebastian Schelter
Comments:
- [X] (tvm) Henry Saputra
Comments: Community is healthy and congrats on the first release under ASF
- [ ] (tvm) Timothy Chen
Comments:
- [X] (tvm) Furkan Kamaci
Comments:
- [x] (tvm) Tianqi Chen
Comments:
- [x] (tvm) Markus Weimer
Comments: With the first release done, we should look towards
graduation.
### IPMC/Shepherd notes:
Justin Mclean: I think it may be a little too early to consider
graduation. Has the podling filling the the optional maturity model,
doing so may point out when there's still more work to do.
--------------------
## 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]
(https://cwiki.apache.org/confluence/display/WEEX/Branding+issues).
There are about 10 git repos violating the trademark of Apache Weex,
together with their NPM/Maven artifact.
2. [Community diversity]
(https://cwiki.apache.org/confluence/display/WEEX/Communtiy+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](https://github.com/apache/incubator-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
- [X] 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?
Mentors are very helpful.
### Is the PPMC managing the podling's brand / trademarks?
* We are collecting a list of
[branding issues]
(https://cwiki.apache.org/confluence/display/WEEX/Branding+issues),
and we shall fix the problem one by one.
* We have not done Podling name search.
### Signed-off-by:
- [X] (weex) Willem Ning Jiang
Comments: Weex made a great progress by inviting
more committers to join the community.
- [ ] (weex) Myrle Krantz
Comments:
- [ ] (weex) Jan Piotrowski
Comments:
### IPMC/Shepherd notes:
|
...