Also committed to the June agenda and all updates committed back to the
wiki.
Incubator PMC report for June 2015
The Apache Incubator is the entry path into the ASF for projects and
codebases wishing to become part of the Foundation's efforts.
With 4 new podlings and no graduations, the Incubator has grown to 43
podlings this month -- up from 31 one year ago, but still well shy of the
record 57 set in 2012.
We had some issues this month with Sentry's latest release and
engagement. See the miscellaneous section for more details.
There are several podlings that seem to be having trouble coming
together. These include log4cxx2 and kalumet. We will keep an eye on
these for now and initiate discussions about retiring the podlings as
appropriate.
Otherwise, there are no particular issues that warrant board
attention.
* Community
New IPMC members:
Jarek Jarcec Cecho
Bill Rowe (rejoining)
* New Podlings
Atlas
CMDA (Climate Model Diagnostic Analyzer)
MySOS
Trafodion
* Graduations
None this month.
* Releases
The following releases were made since the last Incubator report:
johnzon-0.8
kylin-0.7.1
ranger-0.5.0
TinkerPop 3.0.0.M9
* IP Clearance
Sebastien Goasguen, Ian Duffy, and Darren Brogan donated gstack to
Cloudstack. gstack is an API wrapper that maps the Google Cloud Platform
compute engine (GCE) API to the CloudStack API.
Sebastien Goasguen, Ian Duffy, and Darren Brogan donated ec2stack to
Cloudstack. ec2stack is an API wrapper that maps the AWS Elastic Compute
Cloud (EC2) API to the CloudStack API.
Adobe donated the Sling HApi Tools, which provide a set of Hypermedia API
tools for Sling.
* Legal / Trademarks
There was much debate about the name of the new MySOS podling on Incubator
lists and elsewhere. The Incubator voted to accept the podling, since
project name choice does not block entry into incubation.
* Miscellaneous
Several mentors for Sentry have expressed concerns about the
podling's engagement with the incubating process. Mentors are in
dissent with the podling's self-report, and are recommending that
the podling be moved to monthly reporting until concerns are
addressed. Since the self-report was not signed off by the mentors,
we have not included it in this report and will include it in
subsequent reports as the mentors synchronize with the community.
A proposal to incubate the Freemarker template engine is under discussion.
The question of whether or not podlings may have official blogs came up
and was discussed with both Press and Infrastructure. Past rulings have
been inconsistent. The situation was resolved by establishing that
podling Mentors must review posts prior to publication.
-------------------- Summary of podling reports --------------------
* Still getting started at the Incubator
asterixdb
atlas
geode
myriad
trafodion
* Not yet ready to graduate
No release:
corinthia
groovy
log4cxx2
taverna
Community growth:
* Ready to graduate
The Board has motions for the following:
* Did not report, expected next month
batchee
climate model diagnostic analyzer (CMDA)
kalumet
----------------------------------------------------------------------
Table of Contents
AsterixDB
Atlas
BatchEE
Brooklyn
Climate Model Diagnostic Analyzer
CommonsRDF
Corinthia
Geode
Groovy
HTrace
Ignite
Johnzon
Kalumet
log4cxx2
MRQL
Myriad
Ranger
REEF
SAMOA
Sentry
Singa
Sirona
Streams
Taverna
Trafodion
Wave
Zeppelin
----------------------------------------------------------------------
--------------------
AsterixDB
Apache AsterixDB is a scalable big data management system (BDMS) that
provides
storage, management, and query capabilities for large collections of semi-
structured data.
AsterixDB has been incubating since 2015-02-28.
Three most important issues to address in the move towards graduation:
1. Do an Apache release.
2. Migrate issues from Google Code
3. Grow community
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
No, moving steadily.
How has the community developed since the last report?
Some activity on the users list.
First interest by developers (but site makes it hard).
How has the project developed since the last report?
First version of the site is up.
Development is ongoing.
Date of last release:
No Releases yet.
When were the last committers or PMC members elected?
No elected PMC and/or committers
Signed-off-by:
[X](asterixdb) Ate Douma
[ ](asterixdb) Chris Mattmann
[ ](asterixdb) Henry Saputra
[X](asterixdb) Jochen Wiedmann
[x](asterixdb) Ted Dunning
Shepherd/Mentor notes:
AsterixDB has provided monthly reports for March, April, and May. So,
it should be in group 3 (quarterly reports), shouldn't it?
--------------------
Atlas
Apache Atlas is a scalable and extensible set of core foundational
governance
services that enables enterprises to effectively and efficiently meet their
compliance requirements within Hadoop and allows integration with the
complete
enterprise data ecosystem
Atlas has been incubating since 2015-05-05.
Three most important issues to address in the move towards graduation:
1. Push the code from a private repo into apache-git
2. Podling name search pending
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?
* A few users have signed up for the dev ML
How has the project developed since the last report?
* Development activity has not started yet - we plan to start it in a week
Date of last release:
* None, plan to have one by mid june
When were the last committers or PMC members elected?
* None after incubation
Signed-off-by:
[ ](atlas) Arun Murthy
[X](atlas) Chris Douglas
[x](atlas) Jakob Homan
[ ](atlas) Vinod Kumar Vavilapalli
Shepherd/Mentor notes:
--------------------
--------------------
Brooklyn
Brooklyn is a framework for modelling, monitoring, and managing applications
through autonomic blueprints.
Brooklyn has been incubating since 2014-05-01.
Three most important issues to address in the move towards graduation:
1. Grow the community
2. More diversity of the committers/PPMC (currently biased towards
employees of a single organization)
3. Following up our first release with further, regular, 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?
Our community continues to grow slowly but surely, and every month
receives interest and contributions from new community members. In
particular, Brooklyn's recent integrations with Cloud Foundry have
brought some interest from that community into ours.
How has the project developed since the last report?
Code continues to be proposed and merged at a high rate. We are
satisfied with our technical velocity.
We plan to follow up our December release with a further release
as soon as we can, and following this up with regular releases.
We plan to add binary convenience bundles to our next release and
have been working on complying with the appropriate licensing
documentation for this purpose.
Date of last release:
2014-12-23 (apache-brooklyn-0.7.0-M2-incubating)
When were the last committers or PMC members elected?
No change since 2014-07-02.
Signed-off-by:
[ ](brooklyn) Matt Hogstrom
[ ](brooklyn) Alex Karasulu
[ ](brooklyn) David Nalley
[ ](brooklyn) Marcel Offermans
[ ](brooklyn) Jean-Baptiste Onofré
[ ](brooklyn) Olivier Lamy
[ ](brooklyn) Chip Childers
[ ](brooklyn) Andrei Savu
[X](brooklyn) Joe Brockmeier
[ ](brooklyn) Jim Jagielski
Shepherd/Mentor notes:
--------------------
--------------------
CommonsRDF
Commons RDF is a set of interfaces and classes for RDF 1.1 concepts and
behaviours. The commons-rdf-api module defines interfaces and testing
harness. The commons-rdf-simple module provides a basic reference
implementation to exercise the test harness and clarify API contracts.
CommonsRDF has been incubating since 2015-03-06.
Three most important issues to address in the move towards graduation:
1. Build community.
2. Further engage the podling with the nuances of the Apache
Incubation process
3.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
See community section.
How has the community developed since the last report?
The community still needs to find a discussion mode based on
consensus and compromise. Certain techncial issues in RDF
lead to entrenched positions (this is not unique to the podling;
there are such long discussions outside ASF).
This has lead to a lack of energy and one person stepping back
from the project in this reporting period.
How has the project developed since the last report?
The project made its first release on 2015-05-15.
Date of last release:
2015-05-15
When were the last committers or PMC members elected?
None added so far.
Signed-off-by:
[x](commonsrdf) Rob Vesse
[x](commonsrdf) John D Ament
[ ](commonsrdf) Gary Gregory
Shepherd/Mentor notes:
rvesse - The strong differences of opinion over some aspects of RDF are
as reported by the podling causing some issues and they have yet to find a
satisfactory way to build consensus and move forward on some of these. As
noted this is not unusual in the wider world, even within the ASF we have
5 different TLPs that use RDF who between them use 3 different APIs each
with very different world views so building that cross project consensus
and moving forward on releases has the potential to be a blocker to
progress and graduation.
--------------------
Corinthia
Corinthia is a toolkit/application for converting between and editing common
office file formats, with an initial focus on word processing. It is
designed
to cater for multiple classes of platforms - desktop, web, and mobile - and
relies heavily on web technologies such as HTML, CSS, and JavaScript for
representing and manipulating documents. The toolkit is small, portable, and
flexible, with minimal dependencies. The target audience is developers
wishing
to include office viewing, conversion, and editing functionality into their
applications.
Corinthia has been incubating since 2014-12-08.
Three most important issues to address in the move towards graduation:
1. Discuss and decide on a medium-term roadmap
2. Finalize source structure change (easy access for new developers)
3. Get the first release out
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?
Discussion are now taking place between more people, signalling that
the knowledge on the code base is being distributed.
The period has in general been a bit quit, where people have developed
more than discussing.
How has the project developed since the last report?
The ODF filter is well underway.
The 64bit windows version is going through the last round of polishing.
The Qt edtitor interface is starting to take shape.
Date of last release:
XXXX-XX-XX
When were the last committers or PMC members elected?
2015-03-03 Gabrialle Gibson
2015-04-02 Franz de Copenhague
Signed-off-by:
[ ](corinthia) Daniel Gruno
[x](corinthia) Jan Iversen
[ ](corinthia) Dave Fischer
Shepherd/Mentor notes:
DrewFarris - Mentor active on mailing list, new committer added in April,
with possibly another in the works for June. After cursory examination,
no
release discussions were observed on mailing lists.
--------------------
Geode
Geode is a data management platform that provides real-time, consistent
access
to data-intensive applications throughout widely distributed cloud
architectures.
Geode has been incubating since 2015-04-27.
Three most important issues to address in the move towards graduation:
1. Expanding the community to include contributors and committers
outside of Pivotal
2. Execute and manage the project according to governance model
required by the "Apache Way"
3. Have our first Apache (incubating) release (currently blocked
on us solving JGroups licensing issues)
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 project had around 350 messages and around a 100 different people
joined the discussions on the mailing lists, covering all sorts of
topics, from development model to new features.
ICLAs for initial committers are filled and processed.
The wiki has been kept up to date based on mailing list discussions,
with processes for:
- Code Review and submissions
- Branching and versioning
- Code of Conduct
- Social Media guidelines and accounts
- Twitter account (https://twitter.com/apachegeode)
- Slideshare account (http://www.slideshare.net/ApacheGeode)
- Gravatar/Wordpress (https://en.gravatar.com/apachegeode)
There are 46 open issues on JIRA, 5 resolved.
Several external pull requests. Review process is in place and has
been done using ASF ReviewBoard.
Community events and conferences:
- ApacheCon Austin 2015
- Implementing a Highly-Scalable Stock Prediction System with R,
Geode and Spring XD - Fred Melo, Pivotal and William Markito,
Pivotal(April 15)
- Unleashing the Silicon Forest Fire - the Open Sourcing of
GemFire - Brian Dunlap, Southwest Airlines; Sudhir Menon; Pivotal;
Jags Ramnarayan, Pivotal; Dan Smith, Pivotal (Wednesday, April 15)
- PJUG - Portland JUG (25 attended)
- Unleashing the Silicon Forest Fire: the open sourcing of GemFire
- Hands-on Virtual Meetup for Apache Geode (incubating) #1 (Tuesday,
June 2, 2015 9:00 am)
- IMCSummit, 6/30
- Implementing a Highly Scalable In-Memory Stock Prediction
System with Apache Geode, R and Spring XD
(Tuesday, June 30 2015 1:50 PM – 2:30 PM)
- Pivotal Toronto User Group - 06/24
- Introducing Apache Geode -
http://www.meetup.com/Toronto-Pivotal-User-Group/events/222239293/
- Pune/India Meetup - 6/6 3:30 PM to 6:30 PM
- Discussion on Apache Geode -
http://www.meetup.com/TechNext/events/222608288/
- SpringOne, 9/14 - 9/17
- Building Highly Scalable Spring Applications with In-Memory
Distributed
- Data Grids
- Implementing a highly scalable Stock prediction system with R,
Geode and Spring XD
How has the project developed since the last report?
- Initial SGA from Pivotal has been received and processed including the
initial code drop.
- Source code packages will also be renamed from com.gemstone to
org.apache.geode in order to allow an easier path to become a TLP.
- Pivotal is going to deliver the final code drop by end of June
adding important features to the project such as:
- Off Heap support
- HDFS Integration
- Command line utilities
- JVSD - Statistic visualization tool
- The main command line interface will be renamed from GFSH (GemFire
Shell) to GEODE, as per community voting.
- The project decided (mailing lists) to follow the RTC
(Review-Then-Commit) policy initially and re-evaluate after some
iterations.
- Jenkins nightly builds are setup
- DockerHub account with a nightly build
- https://registry.hub.docker.com/repos/apachegeode/
- ASF Infrastructure setup:
- Wiki
- JIRA
- Jenkins
- GitHub integration
Date of last release:
N/A - Just nightly builds.
When were the last committers or PMC members elected?
As part of the initial incubation process - 2015-04-27
Signed-off-by:
[ ](geode) Konstantin Boudnik
[ ](geode) Chip Childers
[X](geode) Justin Erenkrantz
[X](geode) Jan Iversen
[ ](geode) Chris Mattmann
[X](geode) William A. Rowe Jr.
[ ](geode) Henry Saputra
[X](geode) Roman Shaposhnik
Shepherd/Mentor notes:
--------------------
Groovy
Apache Groovy is a multi-faceted programming language for the Java platform.
Groovy is a powerful, optionally typed and dynamic language, with static-
typing and static compilation capabilities, aimed at multiplying developers’
productivity thanks to a concise, familiar and easy to learn syntax. It
integrates smoothly with any Java program, and immediately delivers to your
application powerful features, including scripting capabilities, Domain-
Specific Language authoring, runtime and compile-time meta-programming and
functional programming.
Groovy has been incubating since 2015-03-24
Three most important issues to address in the move towards graduation:
1. We still have to get our new release process ready for making our
first release under the incubator banner, but progress has been made
towards that goal already.
2. We need to continue encouraging our users to use our new resources
at Apache instead of using the old ones at Codehaus, but most
remaining resources or assets from Codehaus have been moved or
closed.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
No particular issue right now.
How has the community developed since the last report?
The community seems to have followed the move to our new home, as
for example we're not seeing emails on the old lists anymore.
How has the project developed since the last report?
Ongoing incremental improvements and bug fixes.
Date of last release:
No release yet, but progress being made to make our build process to
comply with Apache rules.
When were the last committers or PMC members elected?
One new committer has joined the team: Andrés Almiray.
And we are inviting two other committers to join us, so hopefully
next month, we should further expand our community.
Signed-off-by:
[ ](groovy) Andrew Bayer
[ ](groovy) Konstantin Boudnik
[ ](groovy) Bertrand Delacretaz
[ ](groovy) Jim Jagielski
[X](groovy) Emmanuel Lecharny
[X](groovy) Roman Shaposhnik
Shepherd/Mentor notes:
The project is in good shape! The new committers addition is a good sign.
Two remarks though :
- The web site is still not linked to Apache, there is a bit of work
to do in this area.
- There is not a lot of discussion on the dev list. If some of those
discussions are conducted on a side channel, it's important to move
such discussions to the dev list. Otherwise, I think that the
current committers are quite busy with their new day job, that would
explain this.
Thanks, keep going the good job!
--------------------
HTrace
HTrace is a tracing framework intended for use with distributed systems
written in java.
HTrace has been incubating since 2014-11.
Three most important issues to address in the move towards graduation:
1. Continue to grow the HTrace community
2. Continue to develop and release stable HTrace incubating artifacts
3. Continue to explore the integration of the HTrace framework into
other Apache products
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?
A few new folks have showed up on the dev and user lists of late.
Lively dev discussion on lists about:
* The 3.2.0 release.
* HTrace and CI
* HTrace and JDK7 minimum
* A meeting and discussion of GUI going forward
* How to accommodate github pull requests
Apache HTrace (Incubating) was presented at HBaseCon, May 7th in
San Francisco by Colin McCabe and Abraham Elmahrek
32 subscribers on dev@ and 120 messages since last report.
How has the project developed since the last report?
About 36 JIRAs resolved since our last report.
Date of last release:
htrace-3.2.0 Jun 2, 2015 The release was release managed
by Abraham Elmahrek
When were the last committers or PMC members elected?
Abraham Elmahrek was elected to become an HTrace committer
on Wed, 11 Feb, 2-15.
Signed-off-by:
[X](htrace) Jake Farrell
[ ](htrace) Todd Lipcon
[ ](htrace) Lewis John Mcgibbney
[ ](htrace) Andrew Purtell
[X](htrace) Billie Rinaldi
[x](htrace) Michael Stack
Shepherd/Mentor notes:
jda: Not a ton of traffic on the mailing list, but active enough for
a podling. Considering how new they are, I think they're in good shape
and may want to begin thinking about graduation.
--------------------
Ignite
A unified In-Memory Data Fabric providing high-performance,
distributed in- memory data management software layer between various
data sources and user applications.
Ignite has been incubating since 2014-10-01.
Three most important issues to address in the move towards graduation:
1. Finish migration to Apache process (DONE)
2. Grow active and healthy community around Apache Ignite product
(Community is healthy and growing).
3. Get on a stable release schedule and have 3 successful product
releases (DONE).
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
None at the moment.
How has the community developed since the last report?
- Ignite currently has 19 active contributors.
- In the process of adding 6 more committers (currently in votes).
- Latest list of committers and contributors can be found here:
https://ignite.incubator.apache.org/community.html#list
How has the project developed since the last report?
- Released Apache Ignite 1.0-RC3
- Released Apache Ignite 1.0
- Released Apache Ignite 1.1
- Passed JCache (JSR107) TCK suite
- Started user mailing list at u...@ignite.incubator.apache.org
- Created Wiki for the developer community:
https://cwiki.apache.org/confluence/display/IGNITE/
- Fully automated the build and release process via maven
Date of last release:
2015-05-28
When were the last committers or PMC members elected?
01/20/2015 Added 3 additional committers
06/04/2015 PPMC approved 6 additional committers (invitations are being
sent)
Signed-off-by:
[X](ignite) Branko Čibej
[ ](ignite) Konstantin Boudnik
[X](ignite) Roman Shaposhnik
[ ](ignite) Michael Stack
Shepherd/Mentor notes:
Branko Čibej (brane):
The Ignite community has progressed very nicely in recent months.
The dev@ list has become the main communication channel, new
contributors
are arriving and many have been invited to the PPMC. Apart from a few
minor teething problems, the latest release has gone smoothly.
I'm hoping that we'll be able to report successful graduation by the
time the next board report is due.
--------------------
Johnzon
Implementation of JSR-353 JavaTM API for JSON Processing.
Johnzon has been incubating since 2014-06-09.
Three most important issues to address in the move towards graduation:
1. Expanding the community, increase dev list activity and adding new
committers/pmc members
2. Complete the project incubation status page
3. Add and improve documentation
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
* Nothing
How has the community developed since the last report?
There are new people on the dev list and the project got contributions
from non-committers. On the dev list there are approx. 32 msgs (on
average) messages per month.
How has the project developed since the last report?
The project did its 5th incubator release.
During the last three month 8 jira issues were reported and fixed.
Date of last release:
2015-04-06 (0.7-incubating)
When were the last committers or PMC members elected?
Last committer was elected 2014-08-23, last PMC member was elected
2015-04-09 (Hendrik Saly)
Signed-off-by:
[X](johnzon) Justin Mclean
[ ](johnzon) Daniel Kulp
Shepherd/Mentor notes:
--------------------
log4cxx2
Logging for C++
log4cxx2 has been incubating since 2013-12-09.
Three most important issues to address in the move towards graduation:
1. Create a release
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?
Not grown. However, the project aims to become a sub project of Apache
Logging again. Community growth is not much a matter for this podling, as
long as there are a few active contributors.
How has the project developed since the last report?
Not much: There currently doesn't seem to be any public development,
though
support is given and bugs are tracked.
Date of last release:
2008-04-03 was the last official, pre-incubation 0.10.0
When were the last committers or PMC members elected?
Signed-off-by:
[X](log4cxx2) Christian Grobmeier
[ ](log4cxx2) Scott Deboy
Shepherd/Mentor notes:
P. Taylor Goetz (ptgoetz):
It appears the attempt to reboot the lo4cxx2 project by re-incubating is
failing, and the podling is not making any progress in terms of releases
and community development.
The primary stated goal of the last few reports has been to produce a
release, but the dev@ mailing list is largely devoid of any release
discussions (the last mention of a release was 12 Dec 2014 [1]). The
current report is a word-for-word copy of the last report, and there has
been only one email from a mentor in the last 5 months (to discuss the
incubator report).
I noticed that the podling does not appear to have (that I could find) a
private mailing list (possibly an oversight from when it returned to the
incubator?), which I think it would need for discussing new
committers/PPMC
members, retiring, etc. I'm assuming they are relying on private@logging
for private discussions, which may not be appropriate for a podling.
[1] http://s.apache.org/SfR
--------------------
MRQL
MRQL is a query processing and optimization system for large-scale,
distributed data analysis, built on top of Apache Hadoop, Hama, Spark, and
Flink.
MRQL has been incubating since 2013-03-13.
Three most important issues to address in the move towards graduation:
1. Increase the number of active committers
2. Increase adoption, expand user community, and increase user list
activity
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?
There were no new developers or new committers since our last report.
We have presented our project at ApacheCon NA in April. The talk was
well-attended and some developers from other Apache projects expressed
some interest in collaboration, which resulted in discussions at the
dev@mrql list and new JIRA issues.
How has the project developed since the last report?
We have created a GitHub mirror and synchronized it with the existing
Apache git repository and with JIRA. The GitHub mirror allows to
merge git branches easier and provides a better integration with JIRA.
We have added more features to MRQL Streaming (such as, new input
stream formats) and have fixed various bugs.
Date of last release:
2015-02-25
When were the last committers or PMC members elected?
2014-04-17
Signed-off-by:
[X](mrql) Alan Cabrera
[ ](mrql) Alex Karasulu
[ ](mrql) Mohammad Nour El-Din
Shepherd/Mentor notes:
There are members of MRQL who are enthusiastic about keeping the
project around and have taken steps to attract new committers to the
project.
--------------------
Myriad
Myriad enables co-existence of Apache Hadoop YARN and Apache Mesos together
on
the same cluster and allows dynamic resource allocations across both Hadoop
and other applications running on the same physical data center
infrastructure.
Myriad has been incubating since 2015-03-01.
Three most important issues to address in the move towards graduation:
1. Fill out ip-clearance form and donate the Myriad code to ASF.
2. Grant committers karma, migrate the code and issues from github.
3. Figure out how and when to release a new "version" of Myriad.
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?
About 75 emails on dev@ from 15 individuals since last
month. Continuing community-wide meetings/hangouts.
All initial committers and their organizations have now submitted
ICLAs/CCLAs.
Zhongyue gave a presentation at first China Mesos User
Group. Upcoming presentations at first Hamburg Mesos User Group and
at MesosCon in August.
How has the project developed since the last report?
Significant recent commits/PRs include:
1. Committed: Dockerizing the Scheduler/ResourceManager (PR#95)
2. Committed: Web UI Dashboard (PR#82)
3. In review: Multi-project build (PR#77)
4. In review: Fine-grained scaling (PR#91)
5. In progress: High availability for the Scheduler/RM (PR#94)
6. In progress: Integration into Mesosphere DCOS
Date of last release:
No releases yet. Still at 0.0.1 in the source. Will plan a release
after we migrate to Apache git.
When were the last committers or PMC members elected?
Need to grant Apache git karma to initial committers. Then we will
vote in new committers from the existing developer community.
Signed-off-by:
[ ](myriad) Benjamin Hindman
[ ](myriad) Danese Cooper
[x](myriad) Ted Dunning
[ ](myriad) Luciano Resende
Shepherd/Mentor notes:
P. Taylor Goetz(ptgoetz):
Myriad is still ramping up. Mentors are engaged in the process.
--------------------
Ranger
The Ranger project is a framework to enable, monitor and manage
comprehensive
data security across the Hadoop platform.
Ranger has been incubating since 2014-07-24.
Three most important issues to address in the move towards graduation:
1. Increase the community participants within Apache Ranger
2. Establish a automated git check-in process to validate the check-in
patches for quality control (similar to Hadoop QA)
3. Provide easier user guide/documentation to support new users and
contributors.
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. More users/contributors are contributing to Apache Ranger
2. Mailing list activity since last report (March-01-2015 to
June-01-2015) :
@dev 335
@user 135
@commit 538
3. Issues (JIRAs) created/resolved since last report (after March-01-2015
before June-01-2015):
Created: 239
Resolved: 232
How has the project developed since the last report?
1. Project is working towards second major release of Apache Ranger -
0.5.0
2. Added more contributors from the community
Date of last release:
NOV-17-2014
When were the last committers or PMC members elected?
1. Alok Lal has been added as committer on May-14-2015
Signed-off-by:
[X](ranger) Alan Gates
[ ](ranger) Daniel Gruno
[ ](ranger) Devaraj Das
[X](ranger) Jakob Homan
[ ](ranger) Owen O'Malley
Shepherd/Mentor notes:
P. Taylor Goetz (ptgoetz):
Project looks healthy. 2 of 5 mentors actively engaged with the
community.
--------------------
REEF
REEF (Retainable Evaluator Execution Framework) is a scale-out computing
fabric that eases the development of Big Data applications on top of
resource
managers such as Apache YARN and Mesos.
REEF has been incubating since 2014-08-12.
Three most important issues to address in the move towards graduation:
1. Improve Group Communication for machine learning
2. .Net Evaluator re-write to clean up code and use Tang properly
3. Intergrade vstest on build machine for code check-in
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?
* We have seen significant activities from the community since last report
- 219 JIRA issues created
- 168 JIRA issues resolved
- 2000+ emails on dev (including auto-generated messages)
* New committers have been added to the team
- Joo Seong Jeong and Gyewon Lee from Seoul National University
* We will participate Hadoop Summit in June in San Jose
How has the project developed since the last report?
* 0.11.0-incubating is released
- release date: May 21, 2015
- Vote: 3 +1 binding votes and 0 -1 votes
- 149 issues, tasks, features were resolved in this release.
* Ported REEF .Net to Apache GIT with all build scripts
integrated/automated between Java and .Net
* Made first REEF .Net release to NuGet.org including 11 NuGet packages
* Developed/released Group Communication with Tree topology and Pipeline
fashion
* Defined API for the REEF .Net Clients
Date of last release:
2015-05-21
(0.11.0-incubating)
When were the last committers or PMC members elected?
None Yet
Signed-off-by:
[X](reef) Chris Douglas
[ ](reef) Chris Mattmann
[ ](reef) Ross Gardler
[ ](reef) Owen O'Malley
Shepherd/Mentor notes:
--------------------
SAMOA
SAMOA provides a collection of distributed streaming algorithms for the most
common data mining and machine learning tasks such as classification,
clustering, and regression, as well as programming abstractions to develop
new
algorithms that run on top of distributed stream processing engines (DSPEs).
It features a pluggable architecture that allows it to run on several DSPEs
such as Apache Storm, Apache S4, and Apache Samza.
SAMOA has been incubating since 2014-12-15.
Three most important issues to address in the move towards graduation:
1. Roll an Apache release
2. Elect new PMC members
3. Grow the community
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
Two of our current PMC members (Olivier and Matthieu) have new jobs
and have declared that they will not be able to actively contribute to
the project for the moment being. This leaves 4 active PMC members.
How has the community developed since the last report?
Mailing list activity (March-April-May 2015):
* @dev 375 messages
Jira issues backlog (March-April-May 2015):
* Created: 14
* Resolved: 19
We have had contributions from outside the PMC.
In particular, we have been collaborating with the Apache Flink community.
Our main goal is still to grow the community, which is still pretty
small. To achieve this goal, we are doing a large amount of
dissemination work in conferences and events to promote SAMOA.
How has the project developed since the last report?
We are fully operational on the new infrastructure:
* Completed migration of issues from old GitHub repository.
* Completed migration of documentation from old wiki.
* Created new Confluence wiki with roadmap and contribution
instruction:
https://cwiki.apache.org/confluence/display/SAMOA/Samoa+Home
Main developments:
* New adaptor for Flink integrated.
* Simplified the website and solved several bugs.
* Preparing for our first release in June.
We should increase the rate of technical contribution to the project
and move to less incremental ones. Codebase still need cleanup to
ease adoption by new contributors.
Date of last release:
None, plan to have one in June.
When were the last committers or PMC members elected?
None.
Signed-off-by:
[ ](samoa) Alan Gates
[ ](samoa) Ashutosh Chauhan
[ ](samoa) Enis Soztutar
[x](samoa) Ted Dunning
Shepherd/Mentor notes:
--------------------
Singa
Singa is a distributed platform for deep learning that is easy to use,
extensible and scalable.
Singa has been incubating since 2015-03-17.
Three most important issues to address in the move towards graduation:
1. Finish the features planed for first release.
2. Grow the community of developers and users.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
N/A.
The project Incubation Status file is NOT yet up to date
Updated.
How has the community developed since the last report?
The community is growing slowly with some individual users and developers
joining.
We are trying to get the first release ready as soon as possible to
interest more developers and users.
What has been done since the last report?
1. We have set up the incubator website at
singa.incubator.apache.org. The next step is to update and add
documentations.
2. We have finished 1/3 of the features planned for first release
http://singa.incubator.apache.org/develop/schedule.html. The rest
should be done in this month. The JIRA tickets and pull requests are
increasing.
3. We gave a talk in Danac (http://danac.org/) at Sigmod 2015 to
publicize Singa .
Date of last release:
N/A.
Signed-off-by:
[ ](Singa ) Daniel Dai
[ ](Singa ) Alan Gates
[x](Singa ) Ted Dunning
[ ](Singa ) Thejas Nair
--------------------
Sirona
Monitoring Solution.
Sirona has been incubating since 2013-10-15.
Three most important issues to address in the move towards graduation:
1. Increase community
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
Nothing.
How has the community developed since the last report?
Not a lot.
How has the project developed since the last report?
Ongoing incremental improvements and bug fixes.
Discussing/preparing a new release.
Date of last release:
2014-06-26
When were the last committers or PMC members elected?
None added since project has started
Signed-off-by:
[x](sirona) Olivier Lamy
[ ](sirona) Henri Gomez
[ ](sirona) Jean-Baptiste Onofre
[ ](sirona) Tammo van Lessen
[ ](sirona) Mark Struberg
Shepherd/Mentor notes:
--------------------
Streams
Apache Streams is a lightweight server framework for ActivityStreams.
Streams has been incubating since 2012-11-20.
Three most important issues to address in the move towards graduation:
1. Community growth and PMC maturity.
2. Demonstrate a consistent release schedule.
3. Collaborate with other Apache projects to improve integrations with
their software.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
# of contributors submitting and reviewing pull requests dropped this
quarter.
How has the community developed since the last report?
# of contributors submitting and reviewing pull requests dropped this
quarter.
How has the project developed since the last report?
1. second comprehensive source release
2. official examples source repository contains 6 well-documented
ready-to-run streams
3. official examples source repository in vote for release
4. 40 issues created / 6 resolved / 13 in pull request this quarter
Date of last release:
2015-04-26
When were the last committers or PMC members elected?
2015-02-23: Robert Douglas elected as committer / PMC member
Signed-off-by:
[ ](streams) Matt Franklin
[ ](streams) Ate Douma
[ ](streams) Craig McClanahan
Shepherd/Mentor notes:
--------------------
Taverna
Taverna is a domain-independent suite of tools used to design and execute
data-driven workflows.
Taverna has been incubating since 2014-10-20.
Three most important issues to address in the move towards graduation:
1. First Apache release
2. Motivate community activity
3. Growing 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?
3 active GSOC students.
How has the project developed since the last report?
While the GSOC projects are progressing well, this has
taken some focus away from the general progress
towards our first release.
The PPMC will focus on community engagement and
motivation and push forwards the first release
during June.
Date of last release:
n/a
When were the last committers or PMC members elected?
n/a
Signed-off-by:
[x](taverna) Andy Seaborne
[ ](taverna) Chris Mattmann
[ ](taverna) Suresh Srinivas
[ ](taverna) Suresh Marru
[x](taverna) Marlon Pierce
Shepherd/Mentor notes:
Justin Mclean (jmclean):
Mentors active, but slow progress towards first release (as noted on
list).
--------------------
Trafodion
Trafodion is a webscale SQL-on-Hadoop solution enabling transactional
or operational workloads on Hadoop.
Trafodion has been incubating since 2015-05-24.
Four most important issues to address in the move towards graduation:
1. Software Grant so can migrate code to Apache
2. Podling name search pending
3. Get rest of the project infrastructure in place. Migrate git
repositories, migrate from LaunchPad to JIRA, set up webpage and
builds
4. Develop 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?
This is the first board report for Trafodion in incubator less than
two weeks. There have been some sign-ups on the dev list.
How has the project developed since the last report?
At this time, some of the basic project infrastructure is set up (git
repo, JIRA on Wednesday of this week, and wiki). Some committers
(also PPMC members) have their accounts and are subscribed to the dev,
commits and private lists.
Date of last release:
We have not done a release of Trafodion since incubation.
When were the last committers or PMC members elected?
None since incubation.
Signed-off-by:
[ ](trafodion) Andrew Purtell
[ ](trafodion) Devaraj Das
[ ](trafodion) Enis Söztutar
[ ](trafodion) Lars Hofhansl
[x](trafodion) Michael Stack
[x](trafodion) Roman Shaposhnik
Shepherd/Mentor notes:
--------------------
Wave
A wave is a hosted, live, concurrent data structure for rich communication.
It
can be used like email, chat, or a document.
Wave has been incubating since 2010-12-04.
Three most important issues to address in the move towards graduation:
1. We are still working on first release. Several votes were
attempted, however, we were slowed down due to unfamiliarity with
release process and last second technical issues with the code.
2. Need to grow up community.
3. Make effort to lower entrance barrier for new contributors which
is pretty high due to steep learning curve.
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? While people
are in general interested in the software - we see traffic on demo
servers and bug reports, but we have only limited contribution by new
members.
How has the project developed since the last report?
We had a few votes on the release - each time issues were found and
fixed. We are working on a new wiki for the project to allow new
contributors a better access to the project information. Also we
cleaned up the issues in Jira and categorized them in order to allow
potential contributors to find a potential task easier.
Date of last release:
N/A
When were the last committers or PMC members elected?
July 2014
Signed-off-by:
[X](wave) Christian Grobmeier
[ ](wave) Upayavira
Shepherd/Mentor notes:
--------------------
Zeppelin
A collaborative data analytics and visualisation tool for distributed,
general-purpose data processing systems such as Apache Spark, Apache Flink,
etc.
Zeppelin has been incubating since 2014-12-23.
Three most important issues to address in the move towards graduation:
1. Do an Apache release
2. Community growth: more committers from different organisations
3. Increase adoption
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?
12 patches has been merged and 15 patches has been submitted from 17
different contributors.
Traffic in users@ grew last month with new users asking and new
contributors answering questions: +16 subscribers in dev@, +27 subscribers
in users@ since last month.
How has the project developed since the last report?
Integration to Apache Flink, Apache Ignite, Apache Lens, Apache Hbase,
Prestodb are started and work in progress. Community had discussions
about managing branch and managing interpreter submodules.
Date of last release:
None
When were the last committers or PMC members elected?
2015-03-27
Signed-off-by:
[ ](zeppelin) Konstantin Boudnik
[ ](zeppelin) Henry Saputra
[X](zeppelin) Roman Shaposhnik
[x](zeppelin) Ted Dunning
[ ](zeppelin) Hyunsik Choi
Shepherd/Mentor notes:
