You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@incubator.apache.org by "John D. Ament" <jo...@apache.org> on 2017/04/09 23:41:50 UTC
Draft - Incubator PMC Board Report - April 2017
All,
Below is the current draft. Unlike most months, most of the reports are
already signed off, just waiting for sign off from Weex. Thanks for
getting this done quickly!
John
Incubator PMC report for April 2017
The Apache Incubator is the entry path into the ASF for projects and
codebases wishing to become part of the Foundation's efforts.
There are presently 64 podlings incubating. We have had 1 IPMC member
resign. There were a total of 16 releases during this period.
* Community
New IPMC members:
- None
People who left the IPMC:
- Gianugo Rabellino
* New Podlings
- None
* Podlings that failed to report, expected next month
- BatchEE
- HORN
- MXNet
- Sirona
* Graduations
The board has motions for the following:
- Fineract
- Log4cxx2 (as a subproject to Logging)
- Metron
* Releases
The following releases entered distribution during the month of
March:
- 2017-03-03 Apache SystemML 0.13.0
- 2017-03-07 Apache TrafficControl 1.8.0
- 2017-03-10 Apache MADLib 1.10.0
- 2017-03-10 Apache DataFu 1.3.2
- 2017-03-13 Apache Mnemonic 0.5.0
- 2017-03-16 Apache Metron 0.3.1
- 2017-03-16 Apache Tephra 0.11.0
- 2017-03-17 Apache Atlas 0.8.0
- 2017-03-19 Apache Airflow 1.8.0
- 2017-03-19 Apache Streams 0.5
- 2017-03-20 Apache Edgent 1.1.0
- 2017-03-21 Apache Mynewt 1.0.0
- 2017-03-23 Apache Slider 0.92.0
- 2017-03-25 Apache Freemarker 2.3.26
- 2017-03-25 Apache Quickstep 0.1.0
- 2017-03-30 Apache Toree 0.1.0
* Legal / Trademarks
- A new incubator logo has been selected. We plan to roll out to
podlings starting in April.
* Infrastructure
* Miscellaneous
- We've begun the process to reflect usage of the roster tool in podling
processes.
* Credits
- Report Manager:
----------------------------------------------------------------------
Table of Contents
Airflow
Annotator
DataFu
FreeMarker
Gobblin
Gossip
Griffin
HAWQ
Juneau
MADlib
Metron
Milagro
Mynewt
NetBeans
ODF Toolkit
Pony Mail
Ratis
RocketMQ
Rya
SensSoft
Traffic Control
Weex
----------------------------------------------------------------------
--------------------
Airflow
Airflow is a workflow automation and scheduling system that can be used to
author and manage data pipelines.
Airflow has been incubating since 2016-03-31.
Three most important issues to address in the move towards graduation:
1. We are working on our second apache release 1.8.1 to get more
experience
with the process
2.
3.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
None
How has the community developed since the last report?
1. We had our first official release. 1.8.0 on March 19th 2017.
2. We elected 1 new PPMC Member/Committer: Alex Guziel (a.k.a saguziel)
3. Since our last podling report 3 months ago (i.e. between Jan 1 and Mar
31, inclusive), we grew our contributors from 224 to 256
4. Since our last podling report 3 months ago (i.e. between Jan 1 and Mar
31, inclusive), we resolved 216 pull requests (currently at 1479 closed
PRs)
5. Three meet-ups, one in San Francisco, CA hosted by Clover Health, one
in
New York, NY hosted by Blue Apron and one in San Jose, CA hosted by
PayPal
were held by the community.
6. Since being accepted into the incubator, the number of companies
officially using Apache Airflow has risen from 30 to 83.
How has the project developed since the last report?
1. As noted above, 216 pull requests were merged since our last report
(i.e. between Jan 1 and Mar 31, inclusive).
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:
The Airflow community continues to grow, and we have successfully created
our first Apache release. We want to continue on this momentum and create
another release to solidify our process and tools around it, but we feel
we are nearing graduation. We are open to feedback and guidance to make
sure we can do so.
Date of last release:
2017-03-19
When were the last committers or PPMC members elected?
As mentioned on
https://cwiki.apache.org/confluence/display/AIRFLOW/Announcements#Announcements-Mar14,2017
Alex Guziel joined the Apache Airflow PPMC/Committer group.
Signed-off-by:
[ ](airflow) Chris Nauroth
Comments:
[x](airflow) Hitesh Shah
Comments:
[x](airflow) Jakob Homan
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 issues to address in the move towards graduation:
1. Developer/community engagement/growth
2. Research and planning
3. Shipping a "promising demo"
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
None at this time.
How has the community developed since the last report?
Minimal mailing list activity. Little from new people. It seems (mostly)
that folks are waiting on "someone to code something" before they state
opinions, get involved, etc. We've used the wiki a bit--in hopes of
getting
feedback/input, but since mailing list folks can't edit/comment by default
there's been lag/disinterest caused by that hurdle being particularly
high.
How has the project developed since the last report?
The two most active developers (randall & bigbluehat) have a plan (on the
wiki) which they hope to deliver code for before May. There are two events
in May (I Annotate and ApacheCon) which we hope to demo/present at to
increase awareness/interest/contribution.
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[x] 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?
We've not added any new committers since the beginning. We're still
waiting
on all the initial committers to join the list and/or participate.
Signed-off-by:
[ ](annotator) Nick Kew
Comments:
[ ](annotator) Brian McCallister
Comments:
[ ](annotator) Daniel Gruno
Comments:
[X](annotator) Jim Jagielski
Comments:
IPMC/Shepherd notes:
--------------------
DataFu
DataFu provides a collection of Hadoop MapReduce jobs and functions in
higher
level languages based on it to perform data analysis. It provides functions
for common statistics tasks (e.g. quantiles, sampling), PageRank, stream
sessionization, and set and bag operations. DataFu also provides Hadoop jobs
for incremental data processing in MapReduce.
DataFu has been incubating since 2014-01-05.
Three most important issues to address in the move towards graduation:
1. Complete maturity evaluation checklist
2. Draft graduation resolution
3. Continue releases
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
None
How has the community developed since the last report?
No changes
How has the project developed since the last report?
Version 1.3.2 was released. This addressed an issue with released
convenience binaries not including LICENSE, NOTICE, and DISCLAIMER
in META-INF of JARs. This was considered an important item to
tackle before graduation.
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[x] Initial setup
[x] Working towards first release (released 1.3.0, 1.3.1, and 1.3.2)
[x] Community building (4 committers added since incubuation, 24
contributors in total)
[x] Nearing graduation (maturity evaluation is nearly complete)
[ ] Other:
Date of last release:
2017-03-10
When were the last committers or PPMC members elected?
July 2016 (Eyal Allweil)
Signed-off-by:
[ ](datafu) Ashutosh Chauhan
Comments:
[x](datafu) Roman Shaposhnik
Comments: I believe the podling is ready for graduation
[ ](datafu) Ted Dunning
Comments:
IPMC/Shepherd notes:
--------------------
FreeMarker
FreeMarker is a template engine, i.e. a generic tool to generate text output
based on templates. FreeMarker is implemented in Java as a class library for
programmers.
FreeMarker produces releases from its current stable branch since 2004 (and
is started in 1999).
FreeMarker has been incubating since 2015-07-01.
Three most important issues to address in the move towards graduation:
The project is constantly exploring new ways to "convert" active
users into committers, since we have a very large user base and a
rather small group of committers. This was actually expected, given
the age (and topic) of the project. While the FreeMarker 3 line,
which was started quite recently, will be much more appealing for
contributors, development on that direction will certainly take a
long time. In other respects the project is mature and ready for
graduation.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
We are eager to graduate but we were hoping to increase the number
of active contributors more before the graduation. However, since
the community is slowly growing and we have completed all the
Incubation tasks, we are now more inclined to discuss the graduation
and then proceed as a top level project. One of the practical
problems with being stuck in the Incubator is that many users stick
to the last non-incubating release as that has no "-incubating" in
the Maven coordinates, missing out on fixes and features done in the
recent two years. We brought up the issue with the Maven coordinate
on general@incubator.apache.org (saying that because our Maven
coordinate doesn't contain "apache", "incubating" is meaningless
there), but there was no consensus.
How has the community developed since the last report?
We have welcomed a new committer (non-PMC), Woonsan Ko.
A few new people has shown up to help out with our Twitter channel
(such as making a new logo for it, and helping to make it more
active), and to work on modernizing our build scripts.
The starting of the FreeMarker 3 branch has generated more technical
discussions than usual.
How has the project developed since the last report?
We have created a Project Maturity Model page at
https://cwiki.apache.org/confluence/display/FREEMARKER/Apache+Freemarker+Project+Maturity+Model
We have started the FreeMarker 3 branch, whose goal is to get rid of
backward compatibility burden that holds back the project quite much
at this point, and doesn't allow us to fully capitalize on the
experiences of the last 15 years. In our current situation it's also
very important that the new branch, as it advances, will be
technically far more appealing than the legacy branch for
contributors. Also, the new branch uses org.apache packages and
Maven coordinates (which FreeMarker 2 can't do).
We have received a bigger contribution from Kenshoo, the source code
of an online template evaluator service, which we plan to use on our
home page, helping users to try and learn the template language.
We have released a new micro version (2017-03-25, 2.3.26), focuses
on fixes and smaller improvements. This is the third stable release
issued during the incubation.
We have added a How-To page for committers
(http://freemarker.org/committer-howto.html), which gives detailed
instructions on making releases, handling pull requests, updating
the project home page, and more.
We have worked some on our Twitter channel, such as we have a new
logo and some posts.
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:
Comment: The project is mature and ready for graduation, unless the
problem
with the number of active committers is considered as a blocker.
Date of last release:
2017-03-25
When were the last committers or PPMC members elected?
2017-02-13 Woonsan Ko, committer (non-PMC)
Signed-off-by:
[X](freemarker) Jacopo Cappellato
Comments:
[ ](freemarker) Jean-Frederic Clere
Comments:
[X](freemarker) David E. Jones
Comments:
[ ](freemarker) Ralph Goers
Comments:
[X](freemarker) Sergio Fernández
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.
Few first steps has been made:
* mailing list setup
* jira setup
* few Apache account creation for new committers.
Three most important issues to address in the move towards graduation:
1. Code import. Still need agreement from LinkedIn/Microsoft
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
None
How has the community developed since the last report?
We are very first steps of the project
How has the project developed since the last report?
First report :-)
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[X] 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?
N/A
Signed-off-by:
[X](gobblin) Olivier Lamy
[X](gobblin) Jean-Baptiste Onofre
Comments:
[X](gobblin) Jim Jagielski
Comments:
IPMC/Shepherd notes:
--------------------
Gossip
Gossip is an implementation of the Gossip Protocol.
Gossip has been incubating since 2016-04-28.
Three most important issues to address in the move towards graduation:
1. A project leveraging Apache Gossip such as
https://issues.apache.org/jira/browse/IGNITE-4837
2. Two additional active committers to handle management tasks like code
review
3. Continued releases
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
Two students are submitting proposals for Google Summer of Code. Both have
already contributed features which were committed to the project. We are
hopefully they both proposals will be accepted.
How has the community developed since the last report?
The mailing list has been active with several people who were drawn to the
project by GSOC 17 labels placed on our tickets. Two of them have
contributed features that have been committed, and a third person (who
will
not be doing GSOC) has asked to be assigned a ticket. Our last release had
roughly 5 different contributors, The mailing list is fairly active as we
review GSOC proposals. We have more than 50 stars on github which shows
that visibility is making a steady climb.
How has the project developed since the last report?
A release 0.1.1 was completed right before our last report. We made an
aggressive list of features for 0.1.2. We de-prioritized some of the
items,
but we completed far more than we expected. We had improvements in
performance, testing, and features. CRDT support seemed to be the biggest
'splash' feature.
How would you assess the podling's maturity?
I am happy with the continued feature development and code/test
improvement. We are attracting interest of some new developers who seem
likely to stay involved and potentially be committers in the future. While
the majority of management and reviews is done by a few, others are
beginning to help with tasks like code reviews. As pointed out in the
"move
towards graduation" section, having a couple other highly active
reviewers/committers would be a positive next step.
Please feel free to add your own commentary.
[ ] Initial setup
[ ] Working towards first release
[x] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
2017-04-02 (April 02)
When were the last committers or PPMC members elected?
Chandresh Pancholi added as a committer in February 2017
Signed-off-by:
[ ](gossip) P. Taylor Goetz
Comments:
[x](gossip) Josh Elser
Comments:
The podling is still working to attract new members, but those
involved so far are doing well.
[x](gossip) Drew Farris
Comments:
It is great to see the interest driven by GSOC participation.
Kudos to the team for engaging with GSOC.
IPMC/Shepherd notes:
--------------------
Griffin
Griffin is a open source Data Quality solution for distributed data systems
at
any scale in both streaming or batch data context
Griffin has been incubating since 2016-12-05.
Three most important issues to address in the move towards graduation:
1.Setup website, wiki, plan, milestone.
2.Make the first release.
3.Grow the community.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
None
How has the community developed since the last report?
Two new contributors on-boarded, several developers had contacted us for
plan, milestones, status and use cases.
How has the project developed since the last report?
- Active development started in the community. 24 commits in last month.
- The project setup is going quite well. Initial committers are
onboarding,
JIRA, Website, mailing list were successfully done.
- Work toward next gen version (general enough) is progressing
substantially.
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
[ ] Nearing graduation
[ ] Other:
Date of last release:
N/A
When were the last committers or PPMC members elected?
- Initial set of committers / PPMC.
Signed-off-by:
[X](griffin) Henry Saputra
Comments:
[ ](griffin) Kasper Sørensen
Comments:
[ ](griffin) Uma Maheswara Rao Gangumalla
Comments:
[ ](griffin) Luciano Resende
Comments:
IPMC/Shepherd notes:
--------------------
HAWQ
Apache HAWQ is a Hadoop native SQL query engine that combines the key
technological advantages of MPP database with the scalability and
convenience
of Hadoop. HAWQ reads data from and writes data to HDFS natively. HAWQ
delivers industry-leading performance and linear scalability. It provides
users the tools to confidently and successfully interact with petabyte range
data sets. HAWQ provides users with a complete, standards compliant SQL
interface.
HAWQ has been incubating since 2015-09-04.
Three most important issues to address in the move towards graduation:
1. Continue to improve the project's release cadence. To this end we
plan on expanding automation services to support increased
developer participation.
2. Continue to expand the community, by adding new contributors and
focusing on making sure that there's a much more robust level of
conversations and discussions happening around roadmaps and
feature development on the public dev mailing list.
3. Expand release artifacts to include the delivery of binary
artifacts. We expect the project to significantly refine the
binary release process in several key areas.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
1. Nothing urgent at this time.
How has the community developed since the last report?
1. Two Meetups took place in Beijing, China:
* HAWQ Meetup (January 12, 2017)
- HAWQ2.X New Features - Yanqing Wen, Pivotal HAWQ Senior
Engineer
- HAWQ Elasticity - Huan Zhang, Pivotal HAWQ Senior Engineer
- Data Lake and HAWQ Integration - Wenbin Lu, EMC Big Data
Senior Engineer
* HAWQ Meetup (March 23, 2017)
- Apache HAWQ Exploration Step by Step - Configuration, Build,
Deployment and Debug by Xiang Sheng, Pivotal Software
Engineer
- Transaction Management in Apache HAWQ by Ming Li, Pivotal
Senior Software Engineer
- Max Compute - A SQL engine based on Apache HAWQ by Chen Xia,
Database Expert in Alibaba Cloud
2. A significant push by the dev community has been made to review
and merge the project's Pull Requests (PR). As of March 30, 2017,
eight of the nine open PRs have been opened in the last ten
days. The PR opened on Sep 2016 is targeted to be merged after
the Apache 2.2.0.0 release.
3. Community contribution highlight(s):
* Leveraging the extensible PXF design, a JDBC PXF plugin
was contributed by Devin Jia (github id: jiadexin). This
contribution came from the community and not from the
company which originally donated HAWQ to the ASF.
4. Recent porting efforts:
- Persistent Systems Engineers are actively engaging the dev
community on their HAWQ porting efforts to RHEL 7.1 on S390
platform.
- Ubuntu 16.04.2 LTS (Xenial Xerus) porting notes have been
published on dev list.
5. Ruilong Huo has volunteered to be the Release Manager (RM) for
the upcoming 2.2.0.0 release
How has the project developed since the last report?
1. Apache HAWQ 2.1.0.0 (source code only) has been released.
2. Apache HAWQ 2.2.0.0 release proposed (source code and first
binary release). This is the 3rd release as an incubating
project. The binaries will be Hadoop vendor agnostic providing
support for the Apache Bigtop 1.2.0 distribution.
Release page:
https://cwiki.apache.org/confluence/display/HAWQ/Apache+HAWQ+2.2.0.0-incubating+Release
Release hightlights:
* CentOS 7.x Support
* Ranger Integration
* PXF ORC Profile
* Bug Fixes
3. Paul Guo (paulguo@gmail.com - committer and recent HAWQ PPMC
member) is publishing (to dev email list) a regular HAWQ Graduation
update for the project.
* HAWQ graduation update (January, 17, 2017)
https://lists.apache.org/thread.html/cd37e2b48d4bbc9fe4a9cea47f8247a2a614fa9643171937db9568ed@%3Cdev.hawq.apache.org%3E
* Apache HAWQ graduation update (Mar 1st, 2017)
https://lists.apache.org/thread.html/3a1e454f8c706dd71b1690c3ae74a157ef42eefde2185c780e2a57a2@%3Cdev.hawq.apache.org%3E
4. The Apache HAWQ website has been updated:
* Provide clearer (more user-friendly) home page with good
access to downloadable release artifacts.
* The Apache HAWQ doc set is opened sourced and accessible
from website's nav bar.
5. Significant updates to the Apache HAWQ wiki:
* Add more community activities and recorded videos:
https://cwiki.apache.org/confluence/display/HAWQ/Community
* Add design documents for certain components:
https://cwiki.apache.org/confluence/display/HAWQ/Tech+Documents
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:
2017-02-28
When were the last committers or PMC members elected?
Podling committers (3) added:
Lisa Owen: January 31, 2017
Jane Beckman: February 1, 2017
Kyle Dunn: March 2, 2017
PPMC member (1) added:
Paul Guo: March 10, 2017
Signed-off-by:
[X](hawq) Alan Gates
Comments:
[X](hawq) Konstantin Boudnik
Comments:
[ ](hawq) Justin Erenkrantz
Comments:
[ ](hawq) Thejas Nair
Comments:
[x](hawq) Roman Shaposhnik
Comments:
Podling seems to be a few months away from fulfilling all of
the
graduation requirements.
IPMC/Shepherd notes:
--------------------
HORN
IPMC/Shepherd notes:
johndament: No email activity on the list in 3 months,
--------------------
Juneau
Apache Juneau is a toolkit for marshalling POJOs to a wide variety of
content
types using a common framework, and for creating sophisticated self-
documenting REST interfaces and microservices using VERY little code.
Juneau has been incubating since 2016-06-24.
Three most important issues to address in the move towards graduation:
1. Build up community with non-IBM and non-Salesforce contributors.
2. Solicit user feedback/usage
3. Grow awareness of the project
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
None.
How has the community developed since the last report?
The Juneau community has teamed with the Streams community to
replace Jackson (and other libraries) in Apache Streams.
Ongoing collaboration is going on between the teams.
How has the project developed since the last report?
6.0.1 minor release delivered on Jan 3, 2017.
6.1.0 major release delivered on Feb 25, 2017.
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:
2017-02-25
When were the last committers or PPMC members elected?
- Initial committers only.
Signed-off-by:
[ ](juneau) Craig Russell
Comments:
[ ](juneau) Jochen Wiedmann
Comments:
[X](juneau) John D. Ament
Comments: The podling's struggling a bit with community growth. The
Streams podling has recently begun leveraging Juneau for serialization, so
I'm hopeful to see more interaction.
IPMC/Shepherd notes:
--------------------
MADlib
Big Data Machine Learning in SQL for Data Scientists.
MADlib has been incubating since 2015-09-15.
Three most important issues to address in the move towards graduation:
1. Continue to produce regular Apache (incubating) releases.
2. Continue to execute and manage the project according to governance
model
of the "Apache Way".
3. Continue to build community.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?
1. The next release v1.11 will be the 5th as an incubating project. We
believe this release will meet all requirements for a clean ASF
release,
based on listening to guidance from the IPMC over the previous
releases.
After that, the community would ideally like to move towards top level
status.
2. The licensing issues have been resolved. Should anyone want to review,
we have summarized the issue and resolution with relevant links on the
MADlib wiki at
https://cwiki.apache.org/confluence/display/MADLIB/ASF+Licensing+Guidance
How has the community developed since the last report?
1. Some related events in Q1 2017:
* Feb 4, 2017 - Presentation at FOSDEM’17 Graph devroom. Topic: Graph
Analytics on Massively Parallel Processing Databases (Frank
McQuillan)
* Feb 2, 2017 - Greenplum meetup in SF. Topic: Machine Learning and
Cyber Security with Greenplum and Apache MADlib (Anirudh Kondaveeti,
Frank McQuillan)
* Mar 23, 2017 - MADlib community call. Topic: New Features in Apache
MADlib 1.10 (Frank McQuillan)
2. See material technical conversations on user/dev mailing lists and in
the appropriate JIRAs and pull requests.
How has the project developed since the last report?
1. Build infra set up on Apache infra
https://builds.apache.org/job/madlib-master-build/
2. Docker image with necessary dependencies required to compile and test
MADlib on PostgreSQL 9.6
https://cwiki.apache.org/confluence/display/MADLIB/Quick+Start+Guide+for+Developers#QuickStartGuideforDevelopers-Dock
3. Active work in progress for 5th ASF release MADlib v1.11 scheduled for
Apr 2017. Features include: PageRank, connected components, stratified
sampling, improvements to decision tree & random forest, array & sparse
vector output for pivot
4. Mailing list activity in Q1 to date: 274 postings to dev, 111 postings
to user.
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:
MADlib v1.10 on 3/10/17.
When were the last committers or PMC members elected:
Orhan Kislal on 9/7/16 and Nandish Jayaram on 9/7/16.
Signed-off-by:
[X](madlib) Konstantin Boudnik
Comments:
[ ](madlib) Ted Dunning
Comments:
[x](madlib) Roman Shaposhnik
Comments: we hope to submit a TLP resolution next month
IPMC/Shepherd notes:
--------------------
Metron
Metron is a project dedicated to providing an extensible and scalable
advanced
network security analytics tool. It has strong foundations in the Apache
Hadoop ecosystem.
Metron has been incubating since 2015-12-06.
Three most important issues to address in the move towards graduation:
1. All issues have been addressed.
2. Community graduation discussion and vote have been initiated and passed
3. Incubator graduation discussion and vote have been initiated and passed
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
NA
How has the community developed since the last report?
Most of the community and IPMC will transition to the Metron PMC once we
establish it. Two of our Mentors chose to stay on with the project.
How has the project developed since the last report?
We produced a 0.3.1 build
The project is in the process of graduating into a TLP
How would you assess the podling's maturity?
I think our community is very mature and we will make a great Apache TLP
project
Please feel free to add your own commentary.
[x] Initial setup
[x] Working towards first release
[x] Community building
[x] Nearing graduation
[x] Other: graduation vote passed
Date of last release:
2017-03-17
When were the last committers or PPMC members elected?
Two committers were voted in on 3/15.
Signed-off-by:
[x](metron) Billie Rinaldi
Comments:
[ ](metron) Chris Mattmann
Comments:
[ ](metron) Owen O'Malley
Comments:
[ ](metron) P. Taylor Goetz
Comments:
[ ](metron) Vinod Kumar Vavilapalli
Comments:
IPMC/Shepherd notes:
--------------------
Milagro
Distributed Cryptography; M-Pin protocol for Identity and Trust
Milagro has been incubating since 2015-12-21.
Three most important issues to address in the move towards graduation:
1. Develop MILAGRO toolbox
2. Creating full working MILAGRO ecosystem, based on MILAGRO crypto
library
– further research and development (IoT, blockchain, fractions etc.)
3. Building the MILAGRO community – engaging developers and
cryptographers,
raising awareness and helping to secure future of internet.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
We are having issues with Apache repos, and syncing two-way with Github,
which becomes annoying, as developers reports. We’re facing issues in
logging in to Apache Wiki page (
https://wiki.apache.org/incubator/April2017
<https://wiki.apache.org/incubator/April2017> )
<https://wiki.apache.org/incubator/April2017)> - error messages are poping
here and there, so it’s impossible to work directly on Apache tools (while
users names and passwords, are 100% correct), we still can not access
those, and we are having issues with accessing SVN.
How has the community developed since the last report?
MILAGRO community, sadly isn’t currently growing, most likely cause of
technical issues, few interested folks were unable to login, so they are
working directly on Github repo, while we still can not have two-way
syncing with Apache account.
How has the project developed since the last report?
In past few months, MILAGRO community was focused on developing MILAGRO
Crypto C Library, the most important parts were:
- enabling the solution to use different curves at the same time
- adding Golang wrappers for RSA and ECDSA
- adding tests and working examples for the Golang wrappers
- adding benchmarks
- finally splitting the library into proper logical components
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?
n/a
Signed-off-by:
[ ](milagro) Sterling Hughes
Comments:
[*](milagro) Jan Willem Janssen
Comments:
I do see some ongoing development, like new repositories being
created, but there's not a lot of discussion happening on the MLs and
as such I do not have a clear picture where the project currently
stands, what problems they have, and how we can improve on that.
[*](milagro) Nick Kew
Comments:
Nothing seems to have happened since last time. This report
describes
technical difficulties: loss of certain github functionality in
moving
to apache, and others I find harder to grasp. I will again post a
followup to this to the project's dev list.
IPMC/Shepherd notes:
Drew Farris (shepherd): There should be more effort to move development
and
communication on Milagro to Apache infrastructure. I don't see much
evidence of project activity looking at the mailing lists and repos
alone. I feel that technical issues should be communicated about and
resolved on the mailing lists - not in the incubator report. I don't
see a
dedicated effort from the project members to communicate and resolve
these problems. The lack of progress leads me to question whether
the Milagro community at large is truly interested in running an
Apache
project.
--------------------
MXNet
Signed-off-by:
[ ](mxnet) Sebastian Schelter
Comments:
[ ](mxnet) Suneel Marthi
Comments: Its been 4 months since this project has been proposed for
Apache Incubator and so far nothing's been done to move the project to
Apache. All activity is still happening on the original project github -
http://github.com/dmlc/mxnet and all conversations still happen on the
project's Gitter channel. Since the last report from March 2017 (which btw
was drafted and filed by me) there's been ZERO traction on moving the
project to Apache. There are upcoming talks in various confs like -
https://conferences.oreilly.com/artificial-intelligence/ai-ny/public/schedule/detail/58186
that make no reference to the fact that the project is now 'Apache'. The
reason me and Hen have not filed a report yet for April 2017 is due to the
fact we would rather one of the committers on the project took the
initiative to do it as opposed to a mentor covering for the project.
[ ](mxnet) Markus Weimer
Comments:
[ ](mxnet) Henri Yandell
Comments:
IPMC/Shepherd notes:
JM: No report yet. Slow to start up but at least one Mentor active.
--------------------
Mynewt
Mynewt is a real-time operating system for constrained embedded systems like
wearables, lightbulbs, locks and doorbells. It works on a variety of 32-bit
MCUs (microcontrollers), including ARM Cortex-M and MIPS architectures.
Mynewt has been incubating since 2015-10-20.
Three most important issues to address in the move towards graduation:
1. Demonstrate the capability to do point and major releases that can be
used to build downloadable RTOS images for multiple MCU architectures,
peripherals, and network connectivity protocols. The goal of having a
first major (1.0) release in the first quarter of 2017 was met. The
releases are intended to demonstrate and solidify the repeatability,
usability, and maturity of process.
2. Continue to develop and execute policies that enable project
contributors to achieve self-governance.
3. Expand community - attract new project contributors, get users with
diverse backgrounds applying project to new use cases and encouraging
adoption, grow committer base.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
None
How has the community developed since the last report?
1. Active mailing lists with increasing numbers of subscribers. 19 new
subscribers on dev@ mailing list since last report resulting in a total
of 160 subscribers.
2. Increased participation by several new contributors through pull
requests for new MCU support, merges by new committers, new BSP
support,
connectivity features, and test cases and test results. There is a
measurable increase in usage of the project for 3rd-party products and
demos. Outreach continues via conferences, exhibits, one on one
meetings, tutorials, beta testers, prototype and performance testing
with multiple organizations. For example, 255 Pull Requests have been
closed on GitHub.
3. Vigorous discussions, feature proposals, optimizations, code behavior
analysis, user interface improvements, and implementation debates on
@dev mailing list. Activity on dev@ list averaged 192 msgs/month in
2016
How has the project developed since the last report?
1. The first major release (1.0) was successfully completed on March 22nd.
Two beta releases led up to the first major release - first on December
13, 2016, the second on Feb 24, 2017, with the final month before the
release (between beta2 and 1.0) focusing on bug fixes, performance
tuning, and code cleanup for a robust first release. An example of
policy developed and executed is the Release Policy:
https://cwiki.apache.org/confluence/display/MYNEWT/Release+and+Support+Policy
2. Planning: Issues including bug reports, features, and wish list
captured
and tracked in ASF JIRA by members of the community. Proposals for new
features are posted on the dev@ mailing list and voted on by community
members.
3. Effort towards self governance: Voting successfully completed to grant
committer status to five new candidates since last report. New
committer
acceptance policy defined and followed:
https://cwiki.apache.org/confluence/display/MYNEWT/New+Committer+Acceptance+Process
Another example of policy developed and executed is the Release Policy:
https://cwiki.apache.org/confluence/display/MYNEWT/Release+and+Support+Policy
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:
2017-03-22
When were the last committers or PPMC members elected?
2017-03-28
Signed-off-by:
[ ](mynewt) Sterling Hughes
Comments:
[X](mynewt) Jim Jagielski
Comments:
[X](mynewt) Justin Mclean
Comments:
[ ](mynewt) Greg Stein
Comments:
[ ](mynewt) P. Taylor Goetz
Comments:
IPMC/Shepherd notes:
--------------------
NetBeans
NetBeans is a development environment, tooling platform and application
framework.
NetBeans has been incubating since 2016-10-01.
Three most important issues to address in the move towards graduation:
1. Licensing, i.e., identifying and solving GPL-related code.
2. Coming up with a process of contributing code that makes sense to
everyone.
3. Working on roadmaps, features, and plans together as a community.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
None.
How has the community developed since the last report?
- Several new entries added to Who's Who page:
https://cwiki.apache.org/confluence/display/NETBEANS/Who%27s+Who
- Ongoing discussions on the Apache NetBeans mailing list.
- Several updates to http://incubator.apache.org/projects/netbeans.html
have been done.
- Meetups planned in April: Athens, Bangalore, London
How has the project developed since the last report?
- All repos relating to Java SE NetBeans IDE have been audited on Oracle's
side (
https://cwiki.apache.org/confluence/display/NETBEANS/Apache+Transition).
- Only the code that has been written since the audit started needs to be
reviewed, of the Java SE NetBeans IDE.
- Regular updates on process to Apache NetBeans mailing list.
How would you assess the podling's maturity?
No releases yet, though active discussions and community enthusiasm.
Please feel free to add your own commentary.
[X] 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?
No one has been elected so far.
Signed-off-by:
[X](netbeans) Ate Douma
Comments:
[X](netbeans) Bertrand Delacretaz
Comments:
[ ](netbeans) Daniel Gruno
Comments:
[X](netbeans) Mark Struberg
Comments:
IPMC/Shepherd notes:
--------------------
ODF Toolkit
Java modules that allow programmatic creation, scanning and manipulation of
OpenDocument Format (ISO/IEC 26300 == ODF) documents
ODF Toolkit has been incubating since 2011-08-01.
Three most important issues to address in the move towards graduation:
1. Get companies backing up the project as part of a commercial story, to
get a long-term momentum
2. Do recurrent releases - some semi-automation would be helpful - for the
3rd party users
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
How do we get people to test our release on the incubation list?
A general issue of the project is that it 'just' a toolkit of an office
file format, which in addition is far from leading the business market,
so likely never being used by the mass market - a very niche product.
Still, the toolkit seems to be working well for most common use cases, but
is repeatedly updated by developers on changes of the ODF, like Red Hat
developers enhancing the ODF validator as part of LibreOffice regression
tests (e.g. out-of-the-box running on http://odf-validator.rhcloud.com/)
most often quite ahead of one of the international ODF Plugfests -
http://odfplugfest.org/2016-paris/programme/.
There are some game-changing features in the pipeline (e.g.
collaboration) which are expected to strengthen the acceptance and develop
the community.
How has the community developed since the last report?
We received with Tom Barber a new active Mentor
How has the project developed since the last report?
Update of documentation and bug fixing.
Our release candidate is currently on a vote on the general incubator
list.
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:
2014-06-02
When were the last committers or PPMC members elected?
2015-10-05 - Damjan Jovanovic for Committer/PPMC
Signed-off-by:
[ ](odftoolkit) Nick Burch
Comments:
[ ](odftoolkit) Yegor Kozlov
Comments:
[X](odftoolkit) Tom Barber
Comments:
Svante is still pretty much the sole developer but there are people
testing and voting on releases. We'll ship this release and figure
out
how best to market it once the IPMC signs off on the release.
IPMC/Shepherd notes:
--------------------
Pony Mail
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 issues to address in the move towards graduation:
1. Growing the community, especially contributors
2. Grow awareness within Apache, we are eating our own dog food
3. Start getting more releases out.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
How has the community developed since the last report?
Not much to report here. Community remains the same size. We are
discussing releasing a new version soon(ish).
How has the project developed since the last report?
Many bug fixes, but no new release yet. TBD.
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:
2016-08-02
When were the last committers or PPMC members elected?
Sebb, 2016-09-10.
Signed-off-by:
[ ](ponymail) Andrew Bayer
Comments:
[X](ponymail) John D. Ament
Comments:
IPMC/Shepherd notes:
--------------------
Ratis
Ratis is a Java implementation for RAFT consensus protocol
Ratis has been incubating since 2017-01-03.
Three most important issues to address in the move towards graduation:
1. Setup jenkins.
2. Make the first release. Snapshot release was made available, work in
progress for 0.1.0 release.
3. Grow the community
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
- None
How has the community developed since the last report?
- One new contributor joined.
How has the project developed since the last report?
- A Snapshot release was made available.
- One new contributor.
- 25 new commits.
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup - Need jenkins setup.
[X] Working towards first release - Snapshot release available. Work in
progress for the first release.
[ ] Community building - One new contributor.
[ ] Nearing graduation
[ ] Other:
Date of last release:
- None
When were the last committers or PPMC members elected?
- Initial set of committers/PPMC.
Signed-off-by:
[ ](ratis) Chris Nauroth
Comments:
[ ](ratis) Devaraj Das
Comments:
[x](ratis) Jakob Homan
Comments:
[ ](ratis) Uma Maheswara Rao G
Comments:
IPMC/Shepherd notes:
--------------------
RocketMQ
RocketMQ is a fast, low latency, reliable, scalable, distributed, easy to
use
message-oriented middleware, especially for processing large amounts of
streaming data.
RocketMQ has been incubating since 2016-11-21.
Three most important issues to address in the move towards graduation:
1. Vote in our first PMC members
2. Moving sub-projects from GitHub into the ASF
3. Grow the community
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
* None
How has the community developed since the last report?
* Increased mailing list activity: solutions and milestone plan are
discussed and decided in mailing list.
* Organized the second hackathon in community, The mainly purpose is to
foster users and contributors to use mail list to ask or discuss
problems.
* Star has increased from 516 to 854 since the latest report.
* Moving mature sub-projects into Apache repository, these projects
including RocketMQ-Console, RocketMQ-JMS,RocketMQ Docker and
RocketMQ-Spark PR. Contributors in this repository have over 15+
* Polish RocketMQ various wikis, including example guide, architecture
guide, dev-ops guide etc.
* Up to now, RocketMQ community have finished the several external
integration projects, including RocketMQ-Flume, RocketMQ-Ignite,
RocketMQ-Storm, RocketMQ-Spark.
How has the project developed since the last report?
* Up to now, 140+ issues have been reported on JIRA site and 59 have been
resolved or closed. Since November 85+ pull requests have been created
and 56+ pull requests have been closed.
* Teams are sparing no effort in RocketMQ 4.1 development, which will
introduce a new client api. It covers messaging and streaming solutions
in the finance, e-commerce, Iot and big-data area.
* Received a batch message PR, that is a great enhance for RocketMQ
big-data area.
* Received a message filter PR, that is a new idea for RocketMQ filter
feature.
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup - The initial setup went pretty well with assistance
from
John Ament and his Incubator documentation improvement efforts.
[ ] Working towards first release - The podling has performed its first
release as noted below
[X] Community building - Some contributors are beginning to participate.
So
far users have been slow to show up, so more effort on this front will
be encouraged.
[ ] Nearing graduation - Making progress, not there yet.
[ ] Other:
Date of last release:
2017-02-21
When were the last committers or PPMC members elected?
Last elected committers as following:
* 27 Feb 2017 - Roman Shtykh
* 27 Feb 2017 - Zhen Dong Liu
Signed-off-by:
[X](rocketmq) Bruce Snyder
Comments:
[ ](rocketmq) Brian McCallister
Comments:
[ ](rocketmq) Willem Ning Jiang
Comments:
[ ](rocketmq) Luke Han
Comments:
[X](rocketmq) Justin McLean
Comments:
IPMC/Shepherd notes:
JM: There has been discussion on list re community building and activities
happening e.g. external hackathon but translating that into new committers
seems hard.
I think part of this is process (new to Apache and the way we do things)
and perhaps
PR review process / the committer bar has been set a little too high.
Perhaps the PMC
should look at voting in people that contribute to the project a little
earlier?
--------------------
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 issues to address in the move towards graduation:
1. Have more releases as part of the Apache Foundation
2. Increase diversity of contributors.
3. Continue to harden and develop core Rya features to improve user
experience
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?
No
How has the community developed since the last report?
* Talk on Rya accepted at Apache Big Data, May 18, 2017
* PRs from non-committers (14 contributions from 6 non-committers) which
are integrated into the repository continue to be received
How has the project developed since the last report?
* Resolved a handful of issues that users have encountered
* Committed features: Added support for select * {?s ?p ?o} queries
(select
all triples). Implemented MongoDB based entity secondary index. Added
MongoDB column visibility. Fixed column visibilities in Fluo. Added
GeoWave, in addition to GeoMesa, to the optional rya.geoindexing. Added
statement metadata optimizer so that reified queries can be issued in
an
efficient way.
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:
Oct 28, 2016
When were the last committers or PMC members elected?
New committer and PPMC member David Lotts elected on Oct 25, 2016
New PPMC member Caleb Meier elected on Jan 3rd, 2017
Signed-off-by:
[x](rya) Josh Elser
Comments:
Things seem to be going well. Relatively quiet, but not a problem.
[ ](rya) Edward J. Yoon
Comments:
[ ](rya) Venkatesh Seetharam
Comments:
[x](rya) Billie Rinaldi
Comments:
IPMC/Shepherd notes:
--------------------
SensSoft
SensSoft is a software tool usability testing platform
SensSoft has been incubating since 2016-07-13.
Three most important issues to address in the move towards graduation:
1. Moving towards the first Incubating release of the source code and
other
release artifacts.
2. Grow the Apache SensSoft (Incubating) community.
3. Complete the issues highlighted at the SensSoft Roadmap
https://cwiki.apache.org/confluence/display/SENSSOFT/Roadmap
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
No
How has the community developed since the last report?
The community has been stable and working well towards
the commons goals identified within the Roadmap.
How has the project developed since the last report?
The project has reached a stage where our first Incubating
VOTE'ing process is very close. The community has been working
well towards strategic release-oriented goals.
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:
XXXX-XX-XX
When were the last committers or PPMC members elected?
Arthi Vezhavendan was added to PPMC and Committer base on 2017-01-24
Signed-off-by:
[ ](senssoft) Paul Ramirez
Comments:
[X](senssoft) Lewis John McGibbney
Comments:
[ ](senssoft) Chris Mattmann
Comments:
IPMC/Shepherd notes:
--------------------
Traffic Control
Traffic Control allows you to build a large scale content delivery network
using open source.
Traffic Control has been incubating since 2016-07-12.
Three most important issues to address in the move towards graduation:
1. Enhance automation to facilitate committer voting on new releases.
2. Enhance documentation to ease ramp-up time for new community members.
3. Grow the community.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
How has the community developed since the last report?
Several new people have become active on the project. A 2 week hackathon
was organized to on-board some new contributors from Qwilt.
How has the project developed since the last report?
Traffic Control 1.8 was released on 3/7/2017 after a lot of cleanup of
licenses and dependencies! Traffic Control 2.0 is converging on the first
release candidate.
Since the last report (January 2017), we have
* Merged 232 Pull Requests with 441 commits from 16 contributors
* Opened 135 JIRA issues
* Closed 68 JIRA issues
* Seen 105 messages on the dev@ list.
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup
[ ] Working towards first release (wip)
[ ] Community building (wip)
[ ] Nearing graduation
[ ] Other:
Date of last release:
Traffic Control 1.8 was released on 3/7/2017.
When were the last committers or PPMC members elected?
No new committers or PPMC members yet.
Signed-off-by:
[X](trafficcontrol) Phil Sorber
Comments:
[ ](trafficcontrol) Eric Covener
Comments:
[ ](trafficcontrol) Daniel Gruno
Comments:
[ ](trafficcontrol) J. Aaron Farr
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 issues to address in the move towards graduation:
1. Move the whole workflow and infra into Apache (not the codebase only).
2. Develop more contributors and committers.
3. Clear the ICLA issues.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
No
How has the community developed since the last report?
* 1,510 stars and 229 forks in our new Apache repo in GitHub.
* 600+ mails in dev channel
* Developed one new committer: Yuan Shen
How has the project developed since the last report?
* Enhanced accessibility
* Supported iPad screen
* Supported more features like: "waterfall" component, prefetch,
"expression binding", box-shadow, etc.
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[x] Initial setup
[ ] Working towards first release (wip)
[ ] Community building (wip)
[ ] Nearing graduation
[ ] Other:
Date of last release:
No
When were the last committers or PPMC members elected?
We invited Yuan Shen as a new committer in 2017-02-23.
Signed-off-by:
[ ](weex) Luke Han
Comments:
[ ](weex) Willem Jiang
Comments:
[ ](weex) Stephan Ewen
Comments:
[ ](weex) Niclas Hedhman
Comments:
IPMC/Shepherd notes:
Re: Draft - Incubator PMC Board Report - April 2017
Posted by "P. Taylor Goetz" <pt...@gmail.com>.
Just a quick FYI: Just returned from a week of travel so I'm late with sign offs, but will do them tomorrow.
-Taylor
> On Apr 9, 2017, at 7:41 PM, John D. Ament <jo...@apache.org> wrote:
>
> All,
>
> Below is the current draft. Unlike most months, most of the reports are
> already signed off, just waiting for sign off from Weex. Thanks for
> getting this done quickly!
>
> John
>
> Incubator PMC report for April 2017
>
> The Apache Incubator is the entry path into the ASF for projects and
> codebases wishing to become part of the Foundation's efforts.
>
> There are presently 64 podlings incubating. We have had 1 IPMC member
> resign. There were a total of 16 releases during this period.
>
> * Community
>
> New IPMC members:
>
> - None
>
> People who left the IPMC:
>
> - Gianugo Rabellino
>
> * New Podlings
>
> - None
>
> * Podlings that failed to report, expected next month
>
> - BatchEE
> - HORN
> - MXNet
> - Sirona
>
> * Graduations
>
> The board has motions for the following:
>
> - Fineract
> - Log4cxx2 (as a subproject to Logging)
> - Metron
>
> * Releases
>
> The following releases entered distribution during the month of
> March:
>
> - 2017-03-03 Apache SystemML 0.13.0
> - 2017-03-07 Apache TrafficControl 1.8.0
> - 2017-03-10 Apache MADLib 1.10.0
> - 2017-03-10 Apache DataFu 1.3.2
> - 2017-03-13 Apache Mnemonic 0.5.0
> - 2017-03-16 Apache Metron 0.3.1
> - 2017-03-16 Apache Tephra 0.11.0
> - 2017-03-17 Apache Atlas 0.8.0
> - 2017-03-19 Apache Airflow 1.8.0
> - 2017-03-19 Apache Streams 0.5
> - 2017-03-20 Apache Edgent 1.1.0
> - 2017-03-21 Apache Mynewt 1.0.0
> - 2017-03-23 Apache Slider 0.92.0
> - 2017-03-25 Apache Freemarker 2.3.26
> - 2017-03-25 Apache Quickstep 0.1.0
> - 2017-03-30 Apache Toree 0.1.0
>
> * Legal / Trademarks
>
> - A new incubator logo has been selected. We plan to roll out to
> podlings starting in April.
>
> * Infrastructure
>
>
>
> * Miscellaneous
>
> - We've begun the process to reflect usage of the roster tool in podling
> processes.
>
> * Credits
>
> - Report Manager:
>
> ----------------------------------------------------------------------
> Table of Contents
> Airflow
> Annotator
> DataFu
> FreeMarker
> Gobblin
> Gossip
> Griffin
> HAWQ
> Juneau
> MADlib
> Metron
> Milagro
> Mynewt
> NetBeans
> ODF Toolkit
> Pony Mail
> Ratis
> RocketMQ
> Rya
> SensSoft
> Traffic Control
> Weex
>
> ----------------------------------------------------------------------
>
> --------------------
> Airflow
>
> Airflow is a workflow automation and scheduling system that can be used to
> author and manage data pipelines.
>
> Airflow has been incubating since 2016-03-31.
>
> Three most important issues to address in the move towards graduation:
>
> 1. We are working on our second apache release 1.8.1 to get more
> experience
> with the process
> 2.
> 3.
>
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware of?
>
> None
>
> How has the community developed since the last report?
>
> 1. We had our first official release. 1.8.0 on March 19th 2017.
> 2. We elected 1 new PPMC Member/Committer: Alex Guziel (a.k.a saguziel)
> 3. Since our last podling report 3 months ago (i.e. between Jan 1 and Mar
> 31, inclusive), we grew our contributors from 224 to 256
> 4. Since our last podling report 3 months ago (i.e. between Jan 1 and Mar
> 31, inclusive), we resolved 216 pull requests (currently at 1479 closed
> PRs)
> 5. Three meet-ups, one in San Francisco, CA hosted by Clover Health, one
> in
> New York, NY hosted by Blue Apron and one in San Jose, CA hosted by
> PayPal
> were held by the community.
> 6. Since being accepted into the incubator, the number of companies
> officially using Apache Airflow has risen from 30 to 83.
>
> How has the project developed since the last report?
>
> 1. As noted above, 216 pull requests were merged since our last report
> (i.e. between Jan 1 and Mar 31, inclusive).
>
> 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:
>
> The Airflow community continues to grow, and we have successfully created
> our first Apache release. We want to continue on this momentum and create
> another release to solidify our process and tools around it, but we feel
> we are nearing graduation. We are open to feedback and guidance to make
> sure we can do so.
>
> Date of last release:
>
> 2017-03-19
>
> When were the last committers or PPMC members elected?
>
> As mentioned on
>
> https://cwiki.apache.org/confluence/display/AIRFLOW/Announcements#Announcements-Mar14,2017
> Alex Guziel joined the Apache Airflow PPMC/Committer group.
>
> Signed-off-by:
>
> [ ](airflow) Chris Nauroth
> Comments:
> [x](airflow) Hitesh Shah
> Comments:
> [x](airflow) Jakob Homan
> 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 issues to address in the move towards graduation:
>
> 1. Developer/community engagement/growth
> 2. Research and planning
> 3. Shipping a "promising demo"
>
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware of?
>
> None at this time.
>
> How has the community developed since the last report?
>
> Minimal mailing list activity. Little from new people. It seems (mostly)
> that folks are waiting on "someone to code something" before they state
> opinions, get involved, etc. We've used the wiki a bit--in hopes of
> getting
> feedback/input, but since mailing list folks can't edit/comment by default
> there's been lag/disinterest caused by that hurdle being particularly
> high.
>
> How has the project developed since the last report?
>
> The two most active developers (randall & bigbluehat) have a plan (on the
> wiki) which they hope to deliver code for before May. There are two events
> in May (I Annotate and ApacheCon) which we hope to demo/present at to
> increase awareness/interest/contribution.
>
> How would you assess the podling's maturity?
> Please feel free to add your own commentary.
>
> [x] 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?
>
> We've not added any new committers since the beginning. We're still
> waiting
> on all the initial committers to join the list and/or participate.
>
> Signed-off-by:
>
> [ ](annotator) Nick Kew
> Comments:
> [ ](annotator) Brian McCallister
> Comments:
> [ ](annotator) Daniel Gruno
> Comments:
> [X](annotator) Jim Jagielski
> Comments:
>
> IPMC/Shepherd notes:
>
>
>
> --------------------
>
> DataFu
>
> DataFu provides a collection of Hadoop MapReduce jobs and functions in
> higher
> level languages based on it to perform data analysis. It provides functions
> for common statistics tasks (e.g. quantiles, sampling), PageRank, stream
> sessionization, and set and bag operations. DataFu also provides Hadoop jobs
> for incremental data processing in MapReduce.
>
> DataFu has been incubating since 2014-01-05.
>
> Three most important issues to address in the move towards graduation:
>
> 1. Complete maturity evaluation checklist
> 2. Draft graduation resolution
> 3. Continue releases
>
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware of?
>
> None
>
> How has the community developed since the last report?
>
> No changes
>
> How has the project developed since the last report?
>
> Version 1.3.2 was released. This addressed an issue with released
> convenience binaries not including LICENSE, NOTICE, and DISCLAIMER
> in META-INF of JARs. This was considered an important item to
> tackle before graduation.
>
> How would you assess the podling's maturity?
> Please feel free to add your own commentary.
>
> [x] Initial setup
> [x] Working towards first release (released 1.3.0, 1.3.1, and 1.3.2)
> [x] Community building (4 committers added since incubuation, 24
> contributors in total)
> [x] Nearing graduation (maturity evaluation is nearly complete)
> [ ] Other:
>
> Date of last release:
>
> 2017-03-10
>
> When were the last committers or PPMC members elected?
>
> July 2016 (Eyal Allweil)
>
> Signed-off-by:
>
> [ ](datafu) Ashutosh Chauhan
> Comments:
> [x](datafu) Roman Shaposhnik
> Comments: I believe the podling is ready for graduation
> [ ](datafu) Ted Dunning
> Comments:
>
> IPMC/Shepherd notes:
>
>
>
> --------------------
> FreeMarker
>
> FreeMarker is a template engine, i.e. a generic tool to generate text output
> based on templates. FreeMarker is implemented in Java as a class library for
> programmers.
>
> FreeMarker produces releases from its current stable branch since 2004 (and
> is started in 1999).
>
> FreeMarker has been incubating since 2015-07-01.
>
>
> Three most important issues to address in the move towards graduation:
>
> The project is constantly exploring new ways to "convert" active
> users into committers, since we have a very large user base and a
> rather small group of committers. This was actually expected, given
> the age (and topic) of the project. While the FreeMarker 3 line,
> which was started quite recently, will be much more appealing for
> contributors, development on that direction will certainly take a
> long time. In other respects the project is mature and ready for
> graduation.
>
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware of?
>
> We are eager to graduate but we were hoping to increase the number
> of active contributors more before the graduation. However, since
> the community is slowly growing and we have completed all the
> Incubation tasks, we are now more inclined to discuss the graduation
> and then proceed as a top level project. One of the practical
> problems with being stuck in the Incubator is that many users stick
> to the last non-incubating release as that has no "-incubating" in
> the Maven coordinates, missing out on fixes and features done in the
> recent two years. We brought up the issue with the Maven coordinate
> on general@incubator.apache.org (saying that because our Maven
> coordinate doesn't contain "apache", "incubating" is meaningless
> there), but there was no consensus.
>
> How has the community developed since the last report?
>
> We have welcomed a new committer (non-PMC), Woonsan Ko.
>
> A few new people has shown up to help out with our Twitter channel
> (such as making a new logo for it, and helping to make it more
> active), and to work on modernizing our build scripts.
>
> The starting of the FreeMarker 3 branch has generated more technical
> discussions than usual.
>
> How has the project developed since the last report?
>
> We have created a Project Maturity Model page at
>
> https://cwiki.apache.org/confluence/display/FREEMARKER/Apache+Freemarker+Project+Maturity+Model
>
> We have started the FreeMarker 3 branch, whose goal is to get rid of
> backward compatibility burden that holds back the project quite much
> at this point, and doesn't allow us to fully capitalize on the
> experiences of the last 15 years. In our current situation it's also
> very important that the new branch, as it advances, will be
> technically far more appealing than the legacy branch for
> contributors. Also, the new branch uses org.apache packages and
> Maven coordinates (which FreeMarker 2 can't do).
>
> We have received a bigger contribution from Kenshoo, the source code
> of an online template evaluator service, which we plan to use on our
> home page, helping users to try and learn the template language.
>
> We have released a new micro version (2017-03-25, 2.3.26), focuses
> on fixes and smaller improvements. This is the third stable release
> issued during the incubation.
>
> We have added a How-To page for committers
> (http://freemarker.org/committer-howto.html), which gives detailed
> instructions on making releases, handling pull requests, updating
> the project home page, and more.
>
> We have worked some on our Twitter channel, such as we have a new
> logo and some posts.
>
> 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:
>
> Comment: The project is mature and ready for graduation, unless the
> problem
> with the number of active committers is considered as a blocker.
>
> Date of last release:
>
> 2017-03-25
>
> When were the last committers or PPMC members elected?
>
> 2017-02-13 Woonsan Ko, committer (non-PMC)
>
> Signed-off-by:
>
> [X](freemarker) Jacopo Cappellato
> Comments:
> [ ](freemarker) Jean-Frederic Clere
> Comments:
> [X](freemarker) David E. Jones
> Comments:
> [ ](freemarker) Ralph Goers
> Comments:
> [X](freemarker) Sergio Fernández
> 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.
>
> Few first steps has been made:
>
> * mailing list setup
> * jira setup
> * few Apache account creation for new committers.
>
> Three most important issues to address in the move towards graduation:
>
> 1. Code import. Still need agreement from LinkedIn/Microsoft
>
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware of?
>
> None
>
> How has the community developed since the last report?
>
> We are very first steps of the project
>
> How has the project developed since the last report?
>
> First report :-)
>
> How would you assess the podling's maturity?
> Please feel free to add your own commentary.
>
> [X] 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?
>
> N/A
>
> Signed-off-by:
>
> [X](gobblin) Olivier Lamy
> [X](gobblin) Jean-Baptiste Onofre
> Comments:
> [X](gobblin) Jim Jagielski
> Comments:
>
> IPMC/Shepherd notes:
>
>
>
> --------------------
> Gossip
>
> Gossip is an implementation of the Gossip Protocol.
>
> Gossip has been incubating since 2016-04-28.
>
> Three most important issues to address in the move towards graduation:
>
> 1. A project leveraging Apache Gossip such as
> https://issues.apache.org/jira/browse/IGNITE-4837
> 2. Two additional active committers to handle management tasks like code
> review
> 3. Continued releases
>
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware of?
>
> Two students are submitting proposals for Google Summer of Code. Both have
> already contributed features which were committed to the project. We are
> hopefully they both proposals will be accepted.
>
> How has the community developed since the last report?
>
> The mailing list has been active with several people who were drawn to the
> project by GSOC 17 labels placed on our tickets. Two of them have
> contributed features that have been committed, and a third person (who
> will
> not be doing GSOC) has asked to be assigned a ticket. Our last release had
> roughly 5 different contributors, The mailing list is fairly active as we
> review GSOC proposals. We have more than 50 stars on github which shows
> that visibility is making a steady climb.
>
> How has the project developed since the last report?
>
> A release 0.1.1 was completed right before our last report. We made an
> aggressive list of features for 0.1.2. We de-prioritized some of the
> items,
> but we completed far more than we expected. We had improvements in
> performance, testing, and features. CRDT support seemed to be the biggest
> 'splash' feature.
>
> How would you assess the podling's maturity?
>
> I am happy with the continued feature development and code/test
> improvement. We are attracting interest of some new developers who seem
> likely to stay involved and potentially be committers in the future. While
> the majority of management and reviews is done by a few, others are
> beginning to help with tasks like code reviews. As pointed out in the
> "move
> towards graduation" section, having a couple other highly active
> reviewers/committers would be a positive next step.
>
> Please feel free to add your own commentary.
>
> [ ] Initial setup
> [ ] Working towards first release
> [x] Community building
> [ ] Nearing graduation
> [ ] Other:
>
> Date of last release:
>
> 2017-04-02 (April 02)
>
> When were the last committers or PPMC members elected?
>
> Chandresh Pancholi added as a committer in February 2017
>
> Signed-off-by:
>
> [ ](gossip) P. Taylor Goetz
> Comments:
> [x](gossip) Josh Elser
> Comments:
> The podling is still working to attract new members, but those
> involved so far are doing well.
> [x](gossip) Drew Farris
> Comments:
> It is great to see the interest driven by GSOC participation.
> Kudos to the team for engaging with GSOC.
>
> IPMC/Shepherd notes:
>
>
>
> --------------------
> Griffin
>
> Griffin is a open source Data Quality solution for distributed data systems
> at
> any scale in both streaming or batch data context
>
> Griffin has been incubating since 2016-12-05.
>
> Three most important issues to address in the move towards graduation:
>
> 1.Setup website, wiki, plan, milestone.
> 2.Make the first release.
> 3.Grow the community.
>
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware of?
>
> None
>
> How has the community developed since the last report?
>
> Two new contributors on-boarded, several developers had contacted us for
> plan, milestones, status and use cases.
>
> How has the project developed since the last report?
> - Active development started in the community. 24 commits in last month.
> - The project setup is going quite well. Initial committers are
> onboarding,
> JIRA, Website, mailing list were successfully done.
> - Work toward next gen version (general enough) is progressing
> substantially.
>
> 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
> [ ] Nearing graduation
> [ ] Other:
>
> Date of last release:
>
> N/A
>
> When were the last committers or PPMC members elected?
>
> - Initial set of committers / PPMC.
>
>
> Signed-off-by:
>
> [X](griffin) Henry Saputra
> Comments:
> [ ](griffin) Kasper Sørensen
> Comments:
> [ ](griffin) Uma Maheswara Rao Gangumalla
> Comments:
> [ ](griffin) Luciano Resende
> Comments:
>
> IPMC/Shepherd notes:
>
>
>
> --------------------
> HAWQ
>
> Apache HAWQ is a Hadoop native SQL query engine that combines the key
> technological advantages of MPP database with the scalability and
> convenience
> of Hadoop. HAWQ reads data from and writes data to HDFS natively. HAWQ
> delivers industry-leading performance and linear scalability. It provides
> users the tools to confidently and successfully interact with petabyte range
> data sets. HAWQ provides users with a complete, standards compliant SQL
> interface.
>
> HAWQ has been incubating since 2015-09-04.
>
> Three most important issues to address in the move towards graduation:
>
> 1. Continue to improve the project's release cadence. To this end we
> plan on expanding automation services to support increased
> developer participation.
>
> 2. Continue to expand the community, by adding new contributors and
> focusing on making sure that there's a much more robust level of
> conversations and discussions happening around roadmaps and
> feature development on the public dev mailing list.
>
> 3. Expand release artifacts to include the delivery of binary
> artifacts. We expect the project to significantly refine the
> binary release process in several key areas.
>
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware of?
>
> 1. Nothing urgent at this time.
>
> How has the community developed since the last report?
>
> 1. Two Meetups took place in Beijing, China:
>
> * HAWQ Meetup (January 12, 2017)
>
> - HAWQ2.X New Features - Yanqing Wen, Pivotal HAWQ Senior
> Engineer
> - HAWQ Elasticity - Huan Zhang, Pivotal HAWQ Senior Engineer
> - Data Lake and HAWQ Integration - Wenbin Lu, EMC Big Data
> Senior Engineer
>
> * HAWQ Meetup (March 23, 2017)
>
> - Apache HAWQ Exploration Step by Step - Configuration, Build,
> Deployment and Debug by Xiang Sheng, Pivotal Software
> Engineer
> - Transaction Management in Apache HAWQ by Ming Li, Pivotal
> Senior Software Engineer
> - Max Compute - A SQL engine based on Apache HAWQ by Chen Xia,
> Database Expert in Alibaba Cloud
>
> 2. A significant push by the dev community has been made to review
> and merge the project's Pull Requests (PR). As of March 30, 2017,
> eight of the nine open PRs have been opened in the last ten
> days. The PR opened on Sep 2016 is targeted to be merged after
> the Apache 2.2.0.0 release.
>
> 3. Community contribution highlight(s):
>
> * Leveraging the extensible PXF design, a JDBC PXF plugin
> was contributed by Devin Jia (github id: jiadexin). This
> contribution came from the community and not from the
> company which originally donated HAWQ to the ASF.
>
> 4. Recent porting efforts:
>
> - Persistent Systems Engineers are actively engaging the dev
> community on their HAWQ porting efforts to RHEL 7.1 on S390
> platform.
>
> - Ubuntu 16.04.2 LTS (Xenial Xerus) porting notes have been
> published on dev list.
>
> 5. Ruilong Huo has volunteered to be the Release Manager (RM) for
> the upcoming 2.2.0.0 release
>
> How has the project developed since the last report?
>
> 1. Apache HAWQ 2.1.0.0 (source code only) has been released.
>
> 2. Apache HAWQ 2.2.0.0 release proposed (source code and first
> binary release). This is the 3rd release as an incubating
> project. The binaries will be Hadoop vendor agnostic providing
> support for the Apache Bigtop 1.2.0 distribution.
>
> Release page:
>
>
> https://cwiki.apache.org/confluence/display/HAWQ/Apache+HAWQ+2.2.0.0-incubating+Release
>
> Release hightlights:
>
> * CentOS 7.x Support
> * Ranger Integration
> * PXF ORC Profile
> * Bug Fixes
>
> 3. Paul Guo (paulguo@gmail.com - committer and recent HAWQ PPMC
> member) is publishing (to dev email list) a regular HAWQ Graduation
> update for the project.
>
> * HAWQ graduation update (January, 17, 2017)
>
> https://lists.apache.org/thread.html/cd37e2b48d4bbc9fe4a9cea47f8247a2a614fa9643171937db9568ed@%3Cdev.hawq.apache.org%3E
>
> * Apache HAWQ graduation update (Mar 1st, 2017)
>
> https://lists.apache.org/thread.html/3a1e454f8c706dd71b1690c3ae74a157ef42eefde2185c780e2a57a2@%3Cdev.hawq.apache.org%3E
>
> 4. The Apache HAWQ website has been updated:
> * Provide clearer (more user-friendly) home page with good
> access to downloadable release artifacts.
> * The Apache HAWQ doc set is opened sourced and accessible
> from website's nav bar.
>
> 5. Significant updates to the Apache HAWQ wiki:
>
> * Add more community activities and recorded videos:
> https://cwiki.apache.org/confluence/display/HAWQ/Community
>
> * Add design documents for certain components:
> https://cwiki.apache.org/confluence/display/HAWQ/Tech+Documents
>
> 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:
>
> 2017-02-28
>
> When were the last committers or PMC members elected?
>
> Podling committers (3) added:
> Lisa Owen: January 31, 2017
> Jane Beckman: February 1, 2017
> Kyle Dunn: March 2, 2017
>
> PPMC member (1) added:
> Paul Guo: March 10, 2017
>
> Signed-off-by:
>
> [X](hawq) Alan Gates
> Comments:
> [X](hawq) Konstantin Boudnik
> Comments:
> [ ](hawq) Justin Erenkrantz
> Comments:
> [ ](hawq) Thejas Nair
> Comments:
> [x](hawq) Roman Shaposhnik
> Comments:
> Podling seems to be a few months away from fulfilling all of
> the
> graduation requirements.
>
> IPMC/Shepherd notes:
>
>
>
> --------------------
> HORN
>
> IPMC/Shepherd notes:
>
> johndament: No email activity on the list in 3 months,
>
> --------------------
> Juneau
>
> Apache Juneau is a toolkit for marshalling POJOs to a wide variety of
> content
> types using a common framework, and for creating sophisticated self-
> documenting REST interfaces and microservices using VERY little code.
>
> Juneau has been incubating since 2016-06-24.
>
> Three most important issues to address in the move towards graduation:
>
> 1. Build up community with non-IBM and non-Salesforce contributors.
> 2. Solicit user feedback/usage
> 3. Grow awareness of the project
>
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware of?
>
> None.
>
> How has the community developed since the last report?
>
> The Juneau community has teamed with the Streams community to
> replace Jackson (and other libraries) in Apache Streams.
> Ongoing collaboration is going on between the teams.
>
> How has the project developed since the last report?
>
> 6.0.1 minor release delivered on Jan 3, 2017.
> 6.1.0 major release delivered on Feb 25, 2017.
>
> 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:
>
> 2017-02-25
>
> When were the last committers or PPMC members elected?
>
> - Initial committers only.
>
> Signed-off-by:
>
> [ ](juneau) Craig Russell
> Comments:
> [ ](juneau) Jochen Wiedmann
> Comments:
> [X](juneau) John D. Ament
> Comments: The podling's struggling a bit with community growth. The
> Streams podling has recently begun leveraging Juneau for serialization, so
> I'm hopeful to see more interaction.
>
> IPMC/Shepherd notes:
>
>
>
> --------------------
> MADlib
>
> Big Data Machine Learning in SQL for Data Scientists.
>
> MADlib has been incubating since 2015-09-15.
>
> Three most important issues to address in the move towards graduation:
>
> 1. Continue to produce regular Apache (incubating) releases.
> 2. Continue to execute and manage the project according to governance
> model
> of the "Apache Way".
> 3. Continue to build community.
>
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
> of?
>
> 1. The next release v1.11 will be the 5th as an incubating project. We
> believe this release will meet all requirements for a clean ASF
> release,
> based on listening to guidance from the IPMC over the previous
> releases.
> After that, the community would ideally like to move towards top level
> status.
> 2. The licensing issues have been resolved. Should anyone want to review,
> we have summarized the issue and resolution with relevant links on the
> MADlib wiki at
>
> https://cwiki.apache.org/confluence/display/MADLIB/ASF+Licensing+Guidance
>
> How has the community developed since the last report?
>
> 1. Some related events in Q1 2017:
> * Feb 4, 2017 - Presentation at FOSDEM’17 Graph devroom. Topic: Graph
> Analytics on Massively Parallel Processing Databases (Frank
> McQuillan)
> * Feb 2, 2017 - Greenplum meetup in SF. Topic: Machine Learning and
> Cyber Security with Greenplum and Apache MADlib (Anirudh Kondaveeti,
> Frank McQuillan)
> * Mar 23, 2017 - MADlib community call. Topic: New Features in Apache
> MADlib 1.10 (Frank McQuillan)
> 2. See material technical conversations on user/dev mailing lists and in
> the appropriate JIRAs and pull requests.
>
> How has the project developed since the last report?
>
> 1. Build infra set up on Apache infra
> https://builds.apache.org/job/madlib-master-build/
> 2. Docker image with necessary dependencies required to compile and test
> MADlib on PostgreSQL 9.6
>
> https://cwiki.apache.org/confluence/display/MADLIB/Quick+Start+Guide+for+Developers#QuickStartGuideforDevelopers-Dock
> 3. Active work in progress for 5th ASF release MADlib v1.11 scheduled for
> Apr 2017. Features include: PageRank, connected components, stratified
> sampling, improvements to decision tree & random forest, array & sparse
> vector output for pivot
> 4. Mailing list activity in Q1 to date: 274 postings to dev, 111 postings
> to user.
>
> 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:
>
> MADlib v1.10 on 3/10/17.
>
> When were the last committers or PMC members elected:
>
> Orhan Kislal on 9/7/16 and Nandish Jayaram on 9/7/16.
>
> Signed-off-by:
>
> [X](madlib) Konstantin Boudnik
> Comments:
> [ ](madlib) Ted Dunning
> Comments:
> [x](madlib) Roman Shaposhnik
> Comments: we hope to submit a TLP resolution next month
>
> IPMC/Shepherd notes:
>
>
>
> --------------------
> Metron
>
> Metron is a project dedicated to providing an extensible and scalable
> advanced
> network security analytics tool. It has strong foundations in the Apache
> Hadoop ecosystem.
>
> Metron has been incubating since 2015-12-06.
>
> Three most important issues to address in the move towards graduation:
>
> 1. All issues have been addressed.
> 2. Community graduation discussion and vote have been initiated and passed
> 3. Incubator graduation discussion and vote have been initiated and passed
>
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware of?
>
> NA
>
> How has the community developed since the last report?
>
> Most of the community and IPMC will transition to the Metron PMC once we
> establish it. Two of our Mentors chose to stay on with the project.
>
> How has the project developed since the last report?
>
> We produced a 0.3.1 build
>
> The project is in the process of graduating into a TLP
>
> How would you assess the podling's maturity?
>
> I think our community is very mature and we will make a great Apache TLP
> project
>
> Please feel free to add your own commentary.
>
> [x] Initial setup
> [x] Working towards first release
> [x] Community building
> [x] Nearing graduation
> [x] Other: graduation vote passed
>
> Date of last release:
>
> 2017-03-17
>
> When were the last committers or PPMC members elected?
>
> Two committers were voted in on 3/15.
>
> Signed-off-by:
>
> [x](metron) Billie Rinaldi
> Comments:
> [ ](metron) Chris Mattmann
> Comments:
> [ ](metron) Owen O'Malley
> Comments:
> [ ](metron) P. Taylor Goetz
> Comments:
> [ ](metron) Vinod Kumar Vavilapalli
> Comments:
>
> IPMC/Shepherd notes:
>
>
>
> --------------------
> Milagro
>
> Distributed Cryptography; M-Pin protocol for Identity and Trust
>
> Milagro has been incubating since 2015-12-21.
>
> Three most important issues to address in the move towards graduation:
>
> 1. Develop MILAGRO toolbox
> 2. Creating full working MILAGRO ecosystem, based on MILAGRO crypto
> library
> – further research and development (IoT, blockchain, fractions etc.)
> 3. Building the MILAGRO community – engaging developers and
> cryptographers,
> raising awareness and helping to secure future of internet.
>
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware of?
>
> We are having issues with Apache repos, and syncing two-way with Github,
> which becomes annoying, as developers reports. We’re facing issues in
> logging in to Apache Wiki page (
> https://wiki.apache.org/incubator/April2017
> <https://wiki.apache.org/incubator/April2017> )
> <https://wiki.apache.org/incubator/April2017)> - error messages are poping
> here and there, so it’s impossible to work directly on Apache tools (while
> users names and passwords, are 100% correct), we still can not access
> those, and we are having issues with accessing SVN.
>
> How has the community developed since the last report?
>
> MILAGRO community, sadly isn’t currently growing, most likely cause of
> technical issues, few interested folks were unable to login, so they are
> working directly on Github repo, while we still can not have two-way
> syncing with Apache account.
>
> How has the project developed since the last report?
>
> In past few months, MILAGRO community was focused on developing MILAGRO
> Crypto C Library, the most important parts were:
>
> - enabling the solution to use different curves at the same time
> - adding Golang wrappers for RSA and ECDSA
> - adding tests and working examples for the Golang wrappers
> - adding benchmarks
> - finally splitting the library into proper logical components
>
> 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?
>
> n/a
>
> Signed-off-by:
>
> [ ](milagro) Sterling Hughes
> Comments:
> [*](milagro) Jan Willem Janssen
> Comments:
> I do see some ongoing development, like new repositories being
> created, but there's not a lot of discussion happening on the MLs and
> as such I do not have a clear picture where the project currently
> stands, what problems they have, and how we can improve on that.
> [*](milagro) Nick Kew
> Comments:
> Nothing seems to have happened since last time. This report
> describes
> technical difficulties: loss of certain github functionality in
> moving
> to apache, and others I find harder to grasp. I will again post a
> followup to this to the project's dev list.
>
> IPMC/Shepherd notes:
>
> Drew Farris (shepherd): There should be more effort to move development
> and
> communication on Milagro to Apache infrastructure. I don't see much
> evidence of project activity looking at the mailing lists and repos
> alone. I feel that technical issues should be communicated about and
> resolved on the mailing lists - not in the incubator report. I don't
> see a
> dedicated effort from the project members to communicate and resolve
> these problems. The lack of progress leads me to question whether
> the Milagro community at large is truly interested in running an
> Apache
> project.
>
> --------------------
> MXNet
>
> Signed-off-by:
>
> [ ](mxnet) Sebastian Schelter
> Comments:
> [ ](mxnet) Suneel Marthi
> Comments: Its been 4 months since this project has been proposed for
> Apache Incubator and so far nothing's been done to move the project to
> Apache. All activity is still happening on the original project github -
> http://github.com/dmlc/mxnet and all conversations still happen on the
> project's Gitter channel. Since the last report from March 2017 (which btw
> was drafted and filed by me) there's been ZERO traction on moving the
> project to Apache. There are upcoming talks in various confs like -
> https://conferences.oreilly.com/artificial-intelligence/ai-ny/public/schedule/detail/58186
> that make no reference to the fact that the project is now 'Apache'. The
> reason me and Hen have not filed a report yet for April 2017 is due to the
> fact we would rather one of the committers on the project took the
> initiative to do it as opposed to a mentor covering for the project.
> [ ](mxnet) Markus Weimer
> Comments:
> [ ](mxnet) Henri Yandell
> Comments:
>
> IPMC/Shepherd notes:
>
> JM: No report yet. Slow to start up but at least one Mentor active.
>
> --------------------
> Mynewt
>
> Mynewt is a real-time operating system for constrained embedded systems like
> wearables, lightbulbs, locks and doorbells. It works on a variety of 32-bit
> MCUs (microcontrollers), including ARM Cortex-M and MIPS architectures.
>
> Mynewt has been incubating since 2015-10-20.
>
> Three most important issues to address in the move towards graduation:
>
> 1. Demonstrate the capability to do point and major releases that can be
> used to build downloadable RTOS images for multiple MCU architectures,
> peripherals, and network connectivity protocols. The goal of having a
> first major (1.0) release in the first quarter of 2017 was met. The
> releases are intended to demonstrate and solidify the repeatability,
> usability, and maturity of process.
> 2. Continue to develop and execute policies that enable project
> contributors to achieve self-governance.
> 3. Expand community - attract new project contributors, get users with
> diverse backgrounds applying project to new use cases and encouraging
> adoption, grow committer base.
>
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware of?
>
> None
>
> How has the community developed since the last report?
>
> 1. Active mailing lists with increasing numbers of subscribers. 19 new
> subscribers on dev@ mailing list since last report resulting in a total
> of 160 subscribers.
> 2. Increased participation by several new contributors through pull
> requests for new MCU support, merges by new committers, new BSP
> support,
> connectivity features, and test cases and test results. There is a
> measurable increase in usage of the project for 3rd-party products and
> demos. Outreach continues via conferences, exhibits, one on one
> meetings, tutorials, beta testers, prototype and performance testing
> with multiple organizations. For example, 255 Pull Requests have been
> closed on GitHub.
> 3. Vigorous discussions, feature proposals, optimizations, code behavior
> analysis, user interface improvements, and implementation debates on
> @dev mailing list. Activity on dev@ list averaged 192 msgs/month in
> 2016
>
> How has the project developed since the last report?
>
> 1. The first major release (1.0) was successfully completed on March 22nd.
> Two beta releases led up to the first major release - first on December
> 13, 2016, the second on Feb 24, 2017, with the final month before the
> release (between beta2 and 1.0) focusing on bug fixes, performance
> tuning, and code cleanup for a robust first release. An example of
> policy developed and executed is the Release Policy:
>
> https://cwiki.apache.org/confluence/display/MYNEWT/Release+and+Support+Policy
> 2. Planning: Issues including bug reports, features, and wish list
> captured
> and tracked in ASF JIRA by members of the community. Proposals for new
> features are posted on the dev@ mailing list and voted on by community
> members.
> 3. Effort towards self governance: Voting successfully completed to grant
> committer status to five new candidates since last report. New
> committer
> acceptance policy defined and followed:
>
> https://cwiki.apache.org/confluence/display/MYNEWT/New+Committer+Acceptance+Process
> Another example of policy developed and executed is the Release Policy:
>
> https://cwiki.apache.org/confluence/display/MYNEWT/Release+and+Support+Policy
>
> 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:
>
> 2017-03-22
>
> When were the last committers or PPMC members elected?
>
> 2017-03-28
>
> Signed-off-by:
>
> [ ](mynewt) Sterling Hughes
> Comments:
> [X](mynewt) Jim Jagielski
> Comments:
> [X](mynewt) Justin Mclean
> Comments:
> [ ](mynewt) Greg Stein
> Comments:
> [ ](mynewt) P. Taylor Goetz
> Comments:
>
> IPMC/Shepherd notes:
>
>
>
> --------------------
> NetBeans
>
> NetBeans is a development environment, tooling platform and application
> framework.
>
> NetBeans has been incubating since 2016-10-01.
>
> Three most important issues to address in the move towards graduation:
>
> 1. Licensing, i.e., identifying and solving GPL-related code.
> 2. Coming up with a process of contributing code that makes sense to
> everyone.
> 3. Working on roadmaps, features, and plans together as a community.
>
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware of?
>
> None.
>
> How has the community developed since the last report?
>
> - Several new entries added to Who's Who page:
> https://cwiki.apache.org/confluence/display/NETBEANS/Who%27s+Who
> - Ongoing discussions on the Apache NetBeans mailing list.
> - Several updates to http://incubator.apache.org/projects/netbeans.html
> have been done.
> - Meetups planned in April: Athens, Bangalore, London
>
> How has the project developed since the last report?
>
> - All repos relating to Java SE NetBeans IDE have been audited on Oracle's
> side (
> https://cwiki.apache.org/confluence/display/NETBEANS/Apache+Transition).
> - Only the code that has been written since the audit started needs to be
> reviewed, of the Java SE NetBeans IDE.
> - Regular updates on process to Apache NetBeans mailing list.
>
> How would you assess the podling's maturity?
>
> No releases yet, though active discussions and community enthusiasm.
>
> Please feel free to add your own commentary.
>
> [X] 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?
>
> No one has been elected so far.
>
> Signed-off-by:
>
> [X](netbeans) Ate Douma
> Comments:
> [X](netbeans) Bertrand Delacretaz
> Comments:
> [ ](netbeans) Daniel Gruno
> Comments:
> [X](netbeans) Mark Struberg
> Comments:
>
> IPMC/Shepherd notes:
>
>
>
> --------------------
> ODF Toolkit
>
> Java modules that allow programmatic creation, scanning and manipulation of
> OpenDocument Format (ISO/IEC 26300 == ODF) documents
>
> ODF Toolkit has been incubating since 2011-08-01.
>
> Three most important issues to address in the move towards graduation:
>
> 1. Get companies backing up the project as part of a commercial story, to
> get a long-term momentum
> 2. Do recurrent releases - some semi-automation would be helpful - for the
> 3rd party users
>
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware of?
>
> How do we get people to test our release on the incubation list?
>
> A general issue of the project is that it 'just' a toolkit of an office
> file format, which in addition is far from leading the business market,
> so likely never being used by the mass market - a very niche product.
>
> Still, the toolkit seems to be working well for most common use cases, but
> is repeatedly updated by developers on changes of the ODF, like Red Hat
> developers enhancing the ODF validator as part of LibreOffice regression
> tests (e.g. out-of-the-box running on http://odf-validator.rhcloud.com/)
> most often quite ahead of one of the international ODF Plugfests -
> http://odfplugfest.org/2016-paris/programme/.
>
> There are some game-changing features in the pipeline (e.g.
> collaboration) which are expected to strengthen the acceptance and develop
> the community.
>
> How has the community developed since the last report?
>
> We received with Tom Barber a new active Mentor
>
> How has the project developed since the last report?
>
> Update of documentation and bug fixing.
> Our release candidate is currently on a vote on the general incubator
> list.
>
> 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:
>
> 2014-06-02
>
> When were the last committers or PPMC members elected?
>
> 2015-10-05 - Damjan Jovanovic for Committer/PPMC
>
> Signed-off-by:
>
> [ ](odftoolkit) Nick Burch
> Comments:
> [ ](odftoolkit) Yegor Kozlov
> Comments:
> [X](odftoolkit) Tom Barber
> Comments:
> Svante is still pretty much the sole developer but there are people
> testing and voting on releases. We'll ship this release and figure
> out
> how best to market it once the IPMC signs off on the release.
>
> IPMC/Shepherd notes:
>
>
>
> --------------------
> Pony Mail
>
> 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 issues to address in the move towards graduation:
>
> 1. Growing the community, especially contributors
> 2. Grow awareness within Apache, we are eating our own dog food
> 3. Start getting more releases out.
>
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware of?
>
>
>
> How has the community developed since the last report?
>
> Not much to report here. Community remains the same size. We are
> discussing releasing a new version soon(ish).
>
> How has the project developed since the last report?
>
> Many bug fixes, but no new release yet. TBD.
>
> 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:
>
> 2016-08-02
>
> When were the last committers or PPMC members elected?
>
> Sebb, 2016-09-10.
>
> Signed-off-by:
>
> [ ](ponymail) Andrew Bayer
> Comments:
> [X](ponymail) John D. Ament
> Comments:
>
> IPMC/Shepherd notes:
>
>
>
> --------------------
> Ratis
>
> Ratis is a Java implementation for RAFT consensus protocol
>
> Ratis has been incubating since 2017-01-03.
>
> Three most important issues to address in the move towards graduation:
>
> 1. Setup jenkins.
> 2. Make the first release. Snapshot release was made available, work in
> progress for 0.1.0 release.
> 3. Grow the community
>
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware of?
>
> - None
>
> How has the community developed since the last report?
>
> - One new contributor joined.
>
> How has the project developed since the last report?
>
> - A Snapshot release was made available.
> - One new contributor.
> - 25 new commits.
>
> How would you assess the podling's maturity?
> Please feel free to add your own commentary.
>
> [ ] Initial setup - Need jenkins setup.
> [X] Working towards first release - Snapshot release available. Work in
> progress for the first release.
> [ ] Community building - One new contributor.
> [ ] Nearing graduation
> [ ] Other:
>
> Date of last release:
>
> - None
>
> When were the last committers or PPMC members elected?
>
> - Initial set of committers/PPMC.
>
> Signed-off-by:
>
> [ ](ratis) Chris Nauroth
> Comments:
> [ ](ratis) Devaraj Das
> Comments:
> [x](ratis) Jakob Homan
> Comments:
> [ ](ratis) Uma Maheswara Rao G
> Comments:
>
> IPMC/Shepherd notes:
>
>
>
> --------------------
> RocketMQ
>
> RocketMQ is a fast, low latency, reliable, scalable, distributed, easy to
> use
> message-oriented middleware, especially for processing large amounts of
> streaming data.
>
> RocketMQ has been incubating since 2016-11-21.
>
> Three most important issues to address in the move towards graduation:
>
> 1. Vote in our first PMC members
> 2. Moving sub-projects from GitHub into the ASF
> 3. Grow the community
>
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware of?
>
> * None
>
> How has the community developed since the last report?
>
> * Increased mailing list activity: solutions and milestone plan are
> discussed and decided in mailing list.
> * Organized the second hackathon in community, The mainly purpose is to
> foster users and contributors to use mail list to ask or discuss
> problems.
> * Star has increased from 516 to 854 since the latest report.
> * Moving mature sub-projects into Apache repository, these projects
> including RocketMQ-Console, RocketMQ-JMS,RocketMQ Docker and
> RocketMQ-Spark PR. Contributors in this repository have over 15+
> * Polish RocketMQ various wikis, including example guide, architecture
> guide, dev-ops guide etc.
> * Up to now, RocketMQ community have finished the several external
> integration projects, including RocketMQ-Flume, RocketMQ-Ignite,
> RocketMQ-Storm, RocketMQ-Spark.
>
> How has the project developed since the last report?
>
> * Up to now, 140+ issues have been reported on JIRA site and 59 have been
> resolved or closed. Since November 85+ pull requests have been created
> and 56+ pull requests have been closed.
> * Teams are sparing no effort in RocketMQ 4.1 development, which will
> introduce a new client api. It covers messaging and streaming solutions
> in the finance, e-commerce, Iot and big-data area.
> * Received a batch message PR, that is a great enhance for RocketMQ
> big-data area.
> * Received a message filter PR, that is a new idea for RocketMQ filter
> feature.
>
> How would you assess the podling's maturity?
> Please feel free to add your own commentary.
>
> [ ] Initial setup - The initial setup went pretty well with assistance
> from
> John Ament and his Incubator documentation improvement efforts.
> [ ] Working towards first release - The podling has performed its first
> release as noted below
> [X] Community building - Some contributors are beginning to participate.
> So
> far users have been slow to show up, so more effort on this front will
> be encouraged.
> [ ] Nearing graduation - Making progress, not there yet.
> [ ] Other:
>
> Date of last release:
>
> 2017-02-21
>
> When were the last committers or PPMC members elected?
>
> Last elected committers as following:
> * 27 Feb 2017 - Roman Shtykh
> * 27 Feb 2017 - Zhen Dong Liu
>
> Signed-off-by:
>
> [X](rocketmq) Bruce Snyder
> Comments:
> [ ](rocketmq) Brian McCallister
> Comments:
> [ ](rocketmq) Willem Ning Jiang
> Comments:
> [ ](rocketmq) Luke Han
> Comments:
> [X](rocketmq) Justin McLean
> Comments:
>
> IPMC/Shepherd notes:
>
> JM: There has been discussion on list re community building and activities
> happening e.g. external hackathon but translating that into new committers
> seems hard.
> I think part of this is process (new to Apache and the way we do things)
> and perhaps
> PR review process / the committer bar has been set a little too high.
> Perhaps the PMC
> should look at voting in people that contribute to the project a little
> earlier?
>
> --------------------
> 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 issues to address in the move towards graduation:
>
> 1. Have more releases as part of the Apache Foundation
> 2. Increase diversity of contributors.
> 3. Continue to harden and develop core Rya features to improve user
> experience
>
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
> of?
>
> No
>
> How has the community developed since the last report?
>
> * Talk on Rya accepted at Apache Big Data, May 18, 2017
> * PRs from non-committers (14 contributions from 6 non-committers) which
> are integrated into the repository continue to be received
>
> How has the project developed since the last report?
>
> * Resolved a handful of issues that users have encountered
> * Committed features: Added support for select * {?s ?p ?o} queries
> (select
> all triples). Implemented MongoDB based entity secondary index. Added
> MongoDB column visibility. Fixed column visibilities in Fluo. Added
> GeoWave, in addition to GeoMesa, to the optional rya.geoindexing. Added
> statement metadata optimizer so that reified queries can be issued in
> an
> efficient way.
>
> 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:
>
> Oct 28, 2016
>
> When were the last committers or PMC members elected?
>
> New committer and PPMC member David Lotts elected on Oct 25, 2016
> New PPMC member Caleb Meier elected on Jan 3rd, 2017
>
> Signed-off-by:
>
> [x](rya) Josh Elser
> Comments:
> Things seem to be going well. Relatively quiet, but not a problem.
> [ ](rya) Edward J. Yoon
> Comments:
> [ ](rya) Venkatesh Seetharam
> Comments:
> [x](rya) Billie Rinaldi
> Comments:
>
> IPMC/Shepherd notes:
>
>
>
> --------------------
> SensSoft
>
> SensSoft is a software tool usability testing platform
>
> SensSoft has been incubating since 2016-07-13.
>
> Three most important issues to address in the move towards graduation:
>
> 1. Moving towards the first Incubating release of the source code and
> other
> release artifacts.
> 2. Grow the Apache SensSoft (Incubating) community.
> 3. Complete the issues highlighted at the SensSoft Roadmap
> https://cwiki.apache.org/confluence/display/SENSSOFT/Roadmap
>
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware of?
>
> No
>
> How has the community developed since the last report?
>
> The community has been stable and working well towards
> the commons goals identified within the Roadmap.
>
> How has the project developed since the last report?
>
> The project has reached a stage where our first Incubating
> VOTE'ing process is very close. The community has been working
> well towards strategic release-oriented goals.
>
> 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:
>
> XXXX-XX-XX
>
> When were the last committers or PPMC members elected?
>
> Arthi Vezhavendan was added to PPMC and Committer base on 2017-01-24
>
> Signed-off-by:
>
> [ ](senssoft) Paul Ramirez
> Comments:
> [X](senssoft) Lewis John McGibbney
> Comments:
> [ ](senssoft) Chris Mattmann
> Comments:
>
> IPMC/Shepherd notes:
>
>
>
> --------------------
> Traffic Control
>
> Traffic Control allows you to build a large scale content delivery network
> using open source.
>
> Traffic Control has been incubating since 2016-07-12.
>
> Three most important issues to address in the move towards graduation:
>
> 1. Enhance automation to facilitate committer voting on new releases.
> 2. Enhance documentation to ease ramp-up time for new community members.
> 3. Grow the community.
>
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware of?
>
>
>
> How has the community developed since the last report?
>
> Several new people have become active on the project. A 2 week hackathon
> was organized to on-board some new contributors from Qwilt.
>
> How has the project developed since the last report?
>
> Traffic Control 1.8 was released on 3/7/2017 after a lot of cleanup of
> licenses and dependencies! Traffic Control 2.0 is converging on the first
> release candidate.
>
> Since the last report (January 2017), we have
>
> * Merged 232 Pull Requests with 441 commits from 16 contributors
> * Opened 135 JIRA issues
> * Closed 68 JIRA issues
> * Seen 105 messages on the dev@ list.
>
>
> How would you assess the podling's maturity?
> Please feel free to add your own commentary.
>
> [ ] Initial setup
> [ ] Working towards first release (wip)
> [ ] Community building (wip)
> [ ] Nearing graduation
> [ ] Other:
>
> Date of last release:
>
> Traffic Control 1.8 was released on 3/7/2017.
>
> When were the last committers or PPMC members elected?
>
> No new committers or PPMC members yet.
>
> Signed-off-by:
>
> [X](trafficcontrol) Phil Sorber
> Comments:
> [ ](trafficcontrol) Eric Covener
> Comments:
> [ ](trafficcontrol) Daniel Gruno
> Comments:
> [ ](trafficcontrol) J. Aaron Farr
> 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 issues to address in the move towards graduation:
>
> 1. Move the whole workflow and infra into Apache (not the codebase only).
> 2. Develop more contributors and committers.
> 3. Clear the ICLA issues.
>
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware of?
>
> No
>
> How has the community developed since the last report?
>
> * 1,510 stars and 229 forks in our new Apache repo in GitHub.
> * 600+ mails in dev channel
> * Developed one new committer: Yuan Shen
>
> How has the project developed since the last report?
>
> * Enhanced accessibility
> * Supported iPad screen
> * Supported more features like: "waterfall" component, prefetch,
> "expression binding", box-shadow, etc.
>
> How would you assess the podling's maturity?
> Please feel free to add your own commentary.
>
> [x] Initial setup
> [ ] Working towards first release (wip)
> [ ] Community building (wip)
> [ ] Nearing graduation
> [ ] Other:
>
> Date of last release:
>
> No
>
> When were the last committers or PPMC members elected?
>
> We invited Yuan Shen as a new committer in 2017-02-23.
>
> Signed-off-by:
>
> [ ](weex) Luke Han
> Comments:
> [ ](weex) Willem Jiang
> Comments:
> [ ](weex) Stephan Ewen
> Comments:
> [ ](weex) Niclas Hedhman
> Comments:
>
> IPMC/Shepherd notes:
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org