Index
Links: 2016 - All years
- Original The Apache Software Foundation
Board of Directors Meeting Minutes
March 16, 2016
1. Call to order
The meeting was scheduled for 10:30am Pacific and began at 10:32
when a sufficient attendance to constitute a quorum was
recognized by the chairman.
Other Time Zones: http://timeanddate.com/s/2yr0
The meeting was held via teleconference, hosted by Doug Cutting
and Cloudera.
IRC #asfboard on irc.freenode.net was used for backup purposes.
2. Roll Call
Directors Present:
Rich Bowen
Shane Curcuru
Bertrand Delacretaz
Chris Mattmann
David Nalley
Brett Porter
Sam Ruby
Greg Stein
Directors Absent:
Jim Jagielski
Executive Officers Present:
Ross Gardler
Craig L Russell
Executive Officers Absent:
Kevin A. McGrail
Guests:
Daniel Gruno
Gavin McDonald
Henri Yandell
Mark Thomas
Marvin Humphrey
Sean Kelly
Tom Pappas
3. Minutes from previous meetings
Published minutes can be found at:
http://www.apache.org/foundation/board/calendar.html
A. The meeting of February 17, 2016
See: board_minutes_2016_02_17.txt
Approved by General Consent.
4. Executive Officer Reports
A. Chairman [Brett]
The focus over the last month has been on preparations for the Annual
Members Meeting. I'm pleased to report that we have a healthy number
of nominations for new members, as well as candidates for the board.
Thanks to those who have helped with the agenda resolutions, and the
preparation of the new voting tool!
I am currently working with Sally on a write up for the upcoming
anniversary of the ASF.
As this is the last meeting of this particular board, I'd like to
express much gratitude to all of the directors for the time and
service they've dedicated to the ASF over the last year.
B. President [Ross]
Infrastructure
==========
Infrastructure has consumed most of my time over the last month.
Tony Stevenson has left our infrastructure ranks as a paid contractor
but remains as a volunteer. We wish him well in his new role.
This departure was not unexpected and David had previously
over-staffed in preparation. However, the team is now understaffed.
I've commenced an informal search and have a candidate to consider
(though this candidate did not come from my own search). I'll sync
with David on how to coordinate filling this role once we have decided
on the longer term strategy (see below).
Two projects (that I know of) have requested to join the Git
experiment. The infrastructure team are not yet confident enough to
extend this experiment, though good progress is being made. It would
be useful to have feedback from the board as to whether they see this
as a priority given the potential community impact.
The team have defined a JIRA SLA, the (tentative goal) is to have 90%
of new tickets resolved within the time specified in
https://status.apache.org/sla/jira/primer.html, current performance
metrics can be found at https://status.apache.org/sla/jira
Work has progressed well with respect to restructuring the VP Infra
role. As discussed last month the current plan is to create a new
Infrastructure Lead role who will be responsible for the day to day
operations of the infrastructure team, as discussed on the board@ list
this month I have added the responsibility to ensure infrastructure
is, wherever reasonable, responsive to and inclusive of community
self-serve activities. As a reminder, responsibilities are split as
follows (delegation is encouraged, this is just where the buck
stops)...
President with vendor or staff support
* Manage infra staff with respect to performance and work environment
* Negotiate contract renewals with infra contractors/staff
* Recruit infra staff as needed
VP Infra with vendor and staff support
* Approve infra purchasing decisions, including contract negotiation and
renewal with suppliers
* Ratify medium- to long-term strategy, along with SLA metrics, for ASF Infra
services in response to community demands (Critical, Core and Standard
services)
* Identify and prioritize community engagement with infrastructure services
through a clearly defined and document self-service program
* Set or advise on appropriate ASF policy as requested
* Enforce ASF Policies
* Be the voice of the infra team for the ASF President and thus the Board and
our Members (e.g. board reports)
Infra Lead (paid, also assists with all items under staff below)
* Set and manage annual infra budgets
* Identify suppliers, contract negotiation and renewal
* Coordinate staff and community input to medium- to long-term strategy, along
with SLA metrics, for ASF Infra services in response to community demands
(Critical, Core and Standard services)
* Identify and prioritize community engagement with infrastructure services
through a clearly defined and document self-service program
* Encourage collaboration between projects who are self-managing the
same/similar services
Staff/Contractors (including Lead)
* Implement the defined strategy for ASF Infra (Critical, Core and Standard
services
* Track against SLA targets and report at https://status.apache.org/sla
* Allocate resources (people's time) to ensure tickets are dealt with in a
timely way in addition to completing assigned project word
* Balance job assignments and project schedules to ensure the necessary work
is completed while fun new stuff is progressed
* Ensure projects are either provided with everything they need as a service,
or (wherever possible) are provided compute resources to self-host
* Support community self-service efforts wherever Infra Lead or VP Infra agree
there is sufficient benefit in doing so
* Monitor project adherence to appropriate ASF policies (e.g. release
management, version control, service use), addressing issues of concern and
escalating to the appropriate officer wherever necessary
Given the increasing formality and emphasis on performance I recommend
we create an annual merit reward system and bonus scheme for all infra
staff and contractors. At present there is little motivation for
individual contractors to perform "above and beyond" and while I don't
mean to imply any of our contractors are not performing well I would
like to reflect our increasing emphasis on SLAs and customer
satisfaction with a means to reward those who choose to go beyond what
they are required to do.
I've spoken with a number of organizations that can assist with the
items assigned to President. My recommendation is to either 1) extend
our relationship with Virtual, or 2) hire a lead who is also capable
of taking on this role. Finding a person suitably qualified for 2) is
a difficult ask, but it will be a cheaper option.
Using virtual will increase our costs by a maximum of $15k per year
(including recruitment fees, assuming new/replacement one hire per
year). This would mean that President (potentially delegated to VP
Infra) will remain responsible for final decisions relating to
staff/contractors, but the day to day activities informing these
decisions will be carried out by Virtual under contract.
We can also use Virtual to assist with contract negotiation (assigned
to lead) since such skills are not common in people with an operations
expertise. This would cost around $1,500 per contract negotiation
should we choose to use these services.
I have not added a discussion item for this topic, I intend to ask the
board for approval to take the actions described below. If there is a
need to discuss these actions I will request that we add a discussion
item to the agenda during the meeting.
Recommended actions:
1) Form a search committee for the Infra lead role
2) Spend one month conducting a search and interviewing candidates
3) If a candidate capable of taking on the HR role as well as
operations role is found hire them and delegate all items listed as
President to that individual, If no such candidate is found but an
operations lead is found then hire them and extend our agreement with
Virtual
4) Hire appropriate contractors or staff to fill remaining gaps in the infra
team
Note this will increase infra staffing budgets, possibly by a full
employee plus management fees, since the lead role may become a full
time role while demands on the existing infra contractors remain at
the same levels.
Executive Assistant
===============
EA continues to aid VPs wherever she can. Primary focus this month has
been TAC with some trademarks and fundraising issues along with the
regular monthly activities.
Brand Management
===============
The continued push to have PMCs take ownership of their trademark
management is going well, though this month an over zealous PMC took
action without consulting with Trademarks. No harm done, just a little
wasted time for all involved.
Fundraising
=========
A quiet month for fundraising this month.
We've identified a number of gaps in our records relating to
sponsorship renewals. Melissa is working with Virtual to help close
these gaps.
Marketing
========
Thank you to everyone providing content for the quarterly report in
the last month. This was the first month a potential sponsor asked me
for the latest report ahead of it being published. They informed me
that they've been monitoring this for three quarters and find the
information useful.
All other marketing and publicity activities are "business as usual"
Travel Assistance
==============
We have a record number of applications this time - 48. This is a
result of a number of initiatives to raise awareness of our TAC work.
One such initiative is TAC stories from past recipients:
http://www.apache.org/travel/stories/
As a consequence the team would like to request additional budget to
cover additional attendees. Since ApacheCon is in 2016 we will have an
underspend of circa $15k in 2015, therefore this request is actually
for the 2016 budget.
I've worked with Nick as VP TAC to ensure that any additional TAC
recipients are selected on a slightly modified criteria. We are still
using the existing criteria, but selecting others based on how much
impact the individuals and open source in general are likely to
benefit from their attendance at ApacheCon. The additional request, in
addition to the $15k available in 2015, is for a maximum of $15k
(though the final budget is expected to be closer to $10k). This will
increase the number of attendees from the currently accepted 9 (using
available budget) to 15. It is worth noting that if we were to use the
historic cut-off point in the evaluation we would be accepting 24
people, in other words, we believe the final selection of recipients
will see a greater impact on their own engagement in open source and
thus the open source ecosystem will benefit even more.
Additionally, please see Attachments 1 through 6.
C. Treasurer [Chris]
The Treasurer’s Office worked with Virtual to finalize and submit
our 990 with the CPA. We should be able to post our FY2015 taxes
online shortly.
The Office is currently working with Virtual to prepare our report
for the Annual Members meeting coming up.
I would like to take the opportunity to thank everyone as I do not
plan to stand for Treasurer beyond this Board cycle, whether I am
elected to serve on the Board or not. I have already worked to
identify a replacement and I plan on recommending that replacement
to the next Board. It’s been an honor being the Treasurer for the
past (almost) 4 years and I appreciate everything I have learned and
thank everyone for their positive contributions towards managing the
ASF’s finances. Thanks again.
Income and Expenses for February 2016 CASH BASIS
Current Balances:
Feb 2016
Citizens Checking $469,139
Citizens Money Market $500,127
Amazon- ASF Payments $-
Paypal - ASF $79,108
Wells Fargo Checking - ASF $333,767
Wells Fargo Savings $288,350
Total Checking/Savings $1,670,490
Income Summary:
Inkind Revenue $7,167
Public Donations $78,849
Sponsorship Program $57,000
Programs Income $-
Interest Income $150
Total Income $143,166
Expense Summary:
In Kind Expense $7,167
Infrastructure $62,914
Sponsorship Program $-
Programs Expense $-
Publicity $14,386
Brand Management $-
Conferences $-
Travel Assistance Committee $-
Tax and Audit $-
Treasury Services $3,108
General & Administrative $8,893
Total Expense $96,468
Net Income $46,698
D. Secretary [Craig]
The project to replace missing ICLAs is coming to an end. There are
now 66 entries in iclas.txt with no ICLA recorded. Half of these have
no valid forwarding address on file. The next step is for Secretary to
remove LDAP entries for the committers with no ICLA; and remove
notinavail entries with no iclas on file. It will be straightforward
to reinstate privileges for committers who subsequently file ICLAs.
In February, 90 iclas, two cclas, and one grant were received and
filed. Two of these were in response to my request to file a missing
ICLA.
E. Executive Vice President [Rich]
The schedule has been announced for ApacheCon Core -
https://s.apache.org/fgNC - and for Apache Big Data -
https://s.apache.org/rKyd - and registration is open for both
events. We would like to encourage all projects that have
content in the events (as well as those that don't) to promote
the event to their various communities.
ApacheCon North America will be held in Vancouver, Canada, May
9-14, 2016, at the Hyatt Regency, Vancouver.
Projects wishing to have ancillary events (summits, hackathons,
etc.) at the conference are encouraged to contact me as soon as
possible.
Meanwhile, the Linux Foundation have promised a decision
regarding ApacheCon Europe by some time this month, so expect
to hear about that in next month's report.
F. Vice Chairman [Greg]
Nothing to report this month.
Executive officer reports approved as submitted by General Consent.
5. Additional Officer Reports
A. VP of W3C Relations [Andy Seaborne / Chris]
No report was submitted.
B. Apache Legal Affairs Committee [Jim Jagielski]
See Attachment 8
C. Apache Security Team Project [Mark J. Cox / David]
See Attachment 9
Greg: How is the review of old reports/follow-through going?
Mark: The exercise is proving to be useful. I intend to keep
working back through the archive for as long as it continues
to be useful. So far I've gone back a year.
Additional officer reports approved as submitted by General Consent.
6. Committee Reports
Summary of Reports
The following reports required further discussion:
# Ant [bp]
# Archiva [bp]
# Axis [bp]
# Bloodhound [bp]
# Continuum [bp]
# Groovy [dn]
# Helix [bp]
# Hive [gs]
# Ignite [rb]
# Incubator [sc]
# Lucene.Net [bp]
# MRUnit [bp]
# SpamAssassin [bp]
# Synapse [bp]
# Tajo [bp]
# Tiles [sc]
# Tuscany [bp]
# Web Services [bp]
A. Apache Abdera Project [Ant Elder / Jim]
See Attachment A
B. Apache Allura Project [Dave Brondsema / Sam]
See Attachment B
C. Apache Ant Project [Conor MacNeill / Brett]
No report was submitted.
@Brett: pursue a report for Ant
D. Apache Any23 Project [Lewis John McGibbney / Bertrand]
See Attachment D
E. Apache Archiva Project [Olivier Lamy / Shane]
No report was submitted.
F. Apache Arrow Project [Jacques Nadeau / Rich]
See Attachment F
G. Apache Aurora Project [Bill Farner / Greg]
See Attachment G
H. Apache Axis Project [Deepal Jayasinghe / Sam]
No report was submitted.
I. Apache Bigtop Project [Andrew Purtell / David]
See Attachment I
J. Apache Bloodhound Project [Gary Martin / Shane]
No report was submitted.
@Shane: pursue a report for Bloodhound
K. Apache BookKeeper Project [Sijie Guo / Brett]
See Attachment K
L. Apache Buildr Project [Alex Boisvert / Chris]
See Attachment L
M. Apache BVal Project [Matt Benson / Jim]
See Attachment M
N. Apache Camel Project [Christian Mueller / Bertrand]
See Attachment N
O. Apache Cayenne Project [Andrus Adamchik / Rich]
See Attachment O
P. Apache Chemistry Project [Florian Müller / Greg]
See Attachment P
Q. Apache CloudStack Project [Sebastien Goasguen / Sam]
See Attachment Q
@Sam: Get more (actionable) information on github fork
R. Apache Commons Project [Gary D. Gregory / Rich]
See Attachment R
S. Apache Continuum Project [Brent Atkinson / Greg]
No report was submitted.
T. Apache Cordova Project [Shazron Abdullah / Shane]
See Attachment T
U. Apache cTAKES Project [Pei J Chen / David]
See Attachment U
V. Apache Curator Project [Jordan Zimmerman / Bertrand]
See Attachment V
W. Apache Etch Project [Martin Veith / Jim]
See Attachment W
X. Apache Falcon Project [Srikanth Sundarrajan / Brett]
See Attachment X
Y. Apache Felix Project [Carsten Ziegeler / Chris]
See Attachment Y
Z. Apache Flex Project [Alex Harui / Brett]
See Attachment Z
AA. Apache Flink Project [Stephan Ewen / Greg]
See Attachment AA
AB. Apache Groovy Project [Guillaume Laforge / Jim]
See Attachment AB
@Bertrand: Work with PMC to get a better report for next
quarter
AC. Apache Gump Project [Stefan Bodewig / David]
See Attachment AC
AD. Apache Helix Project [Kishore Gopalakrishna / Sam]
No report was submitted.
AE. Apache Hive Project [Ashutosh Chauhan / Rich]
See Attachment AE
@Rich: Work with PMC to get a better report next quarter
AF. Apache HttpComponents Project [Asankha Perera / Chris]
See Attachment AF
AG. Apache Ignite Project [Dmitriy Setrakyan / Bertrand]
See Attachment AG
@Rich: Communicate to the PMC that the competitive analysis
vs. hazelcast is inappropriate
AH. Apache Incubator Project [Ted Dunning / Shane]
See Attachment AH
AI. Apache Jackrabbit Project [Michael Dürig / Rich]
See Attachment AI
AJ. Apache Karaf Project [Jean-Baptiste Onofré / Jim]
See Attachment AJ
AK. Apache Labs Project [Jan Iversen / Bertrand]
See Attachment AK
AL. Apache Lucene Project [Michael McCandless / Sam]
See Attachment AL
AM. Apache Lucene.Net Project [Prescott Nasser / David]
No report was submitted.
AN. Apache MRUnit Project [Brock Noland / Shane]
No report was submitted.
AO. Apache OFBiz Project [Jacopo Cappellato / Brett]
See Attachment AO
AP. Apache Olingo Project [Christian Amend / Greg]
See Attachment AP
AQ. Apache OODT Project [Tom Barber / Chris]
See Attachment AQ
AR. Apache OpenNLP Project [Jörn Kottmann / Sam]
See Attachment AR
AS. Apache OpenWebBeans Project [Mark Struberg / Jim]
See Attachment AS
AT. Apache Perl Project [Philippe M. Chiasson / Shane]
See Attachment AT
AU. Apache Pig Project [Rohini Palaniswamy / Rich]
See Attachment AU
AV. Apache Pivot Project [Roger Whitcomb / David]
See Attachment AV
AW. Apache Portable Runtime (APR) Project [Jeff Trawick / Bertrand]
See Attachment AW
AX. Apache Portals Project [David Sean Taylor / Chris]
See Attachment AX
AY. Apache ServiceMix Project [Krzysztof Sobkowiak / Greg]
See Attachment AY
AZ. Apache Shiro Project [Les Hazlewood / Brett]
See Attachment AZ
BA. Apache Sling Project [Carsten Ziegeler / Chris]
See Attachment BA
BB. Apache SpamAssassin Project [Kevin A. McGrail / Rich]
No report was submitted.
BC. Apache Stanbol Project [Fabian Christ / Sam]
See Attachment BC
BD. Apache Storm Project [P. Taylor Goetz / Greg]
See Attachment BD
BE. Apache Synapse Project [Hiranya Jayathilaka / Shane]
No report was submitted.
BF. Apache Tajo Project [Hyunsik Choi / Brett]
No report was submitted.
BG. Apache Tiles Project [Mick Semb Wever / David]
See Attachment BG
@Shane: Suggest ways to improve the board report; especially
the "Health" section
BH. Apache Tomcat Project [Mladen Turk / Bertrand]
See Attachment BH
BI. Apache Tuscany Project [Jean-Sebastien Delfino / Jim]
No report was submitted.
BJ. Apache UIMA Project [Marshall Schor / Sam]
See Attachment BJ
BK. Apache VCL Project [Andy Kurth / Jim]
See Attachment BK
BL. Apache Web Services Project [Sagara Gunathunga / David]
No report was submitted.
BM. Apache Whimsy Project [Ross Gardler / Rich]
See Attachment BM
BN. Apache Wicket Project [Martijn Dashorst / Chris]
See Attachment BN
BO. Apache Wink Project [Luciano Resende / Bertrand]
See Attachment BO
BP. Apache Xerces Project [Michael Glavassevich / Shane]
See Attachment BP
BQ. Apache Yetus Project [Sean Busbey / Greg]
See Attachment BQ
BR. Apache Zest Project [Niclas Hedhman / Brett]
See Attachment BR
BS. Apache ZooKeeper Project [Michi Mutsuzaki / Shane]
See Attachment BS
Committee reports approved as submitted by General Consent.
7. Special Orders
A. Change the Apache Pig Project Chair
WHEREAS, the Board of Directors heretofore appointed Rohini Palaniswamy
(rohini) to the office of Vice President, Apache Pig, and
WHEREAS, the Board of Directors is in receipt of the resignation of
Rohini Palaniswamy from the office of Vice President, Apache Pig, and
WHEREAS, the Project Management Committee of the Apache Pig project has
chosen by vote to recommend Daniel Dai (daijy) as the successor to the
post;
NOW, THEREFORE, BE IT RESOLVED, that Rohini Palaniswamy is relieved and
discharged from the duties and responsibilities of the office of Vice
President, Apache Pig, and
BE IT FURTHER RESOLVED, that Daniel Dai be and hereby is appointed to
the office of Vice President, Apache Pig, to serve in accordance with
and subject to the direction of the Board of Directors and the Bylaws
of the Foundation until death, resignation, retirement, removal or
disqualification, or until a successor is appointed.
Special Order 7A, Change the Apache Pig Project Chair, was
approved by Unanimous Vote of the directors present.
B. Terminate the Apache Wookie Project
WHEREAS, the Project Management Committee of the Apache Wookie
project has chosen by vote to recommend moving the project to the
Attic; and
WHEREAS, the Board of Directors deems it no longer in the best
interest of the Foundation to continue the Apache Wookie project
due to inactivity;
NOW, THEREFORE, BE IT RESOLVED, that the Apache Wookie
project is hereby terminated; and be it further
RESOLVED, that the Attic PMC be and hereby is tasked with
oversight over the software developed by the Apache Wookie
Project; and be it further
RESOLVED, that the office of "Vice President, Apache Wookie is
hereby terminated; and be it further
RESOLVED, that the Apache Wookie PMC is hereby terminated.
Special Order 7B, Terminate the Apache Wookie Project, was
approved by Unanimous Vote of the directors present.
C. Change the Apache Whimsy Project Chair
WHEREAS, the Board of Directors heretofore appointed Ross Gardler
(rgardler) to the office of Vice President, Apache Whimsy, and
WHEREAS, the Board of Directors is in receipt of the resignation of
Ross Gardler from the office of Vice President, Apache Whimsy, and
WHEREAS, the Project Management Committee of the Apache Whimsy project
has chosen to recommend Sam Ruby (rubys) as the successor to the post;
NOW, THEREFORE, BE IT RESOLVED, that Ross Gardler is relieved and
discharged from the duties and responsibilities of the office of Vice
President, Apache Whimsy, and
BE IT FURTHER RESOLVED, that Sam Ruby be and hereby is appointed to the
office of Vice President, Apache Whimsy, to serve in accordance with
and subject to the direction of the Board of Directors and the Bylaws
of the Foundation until death, resignation, retirement, removal or
disqualification, or until a successor is appointed.
Special Order 7C, Change the Apache Whimsy Project Chair, was
approved by Unanimous Vote of the directors present.
D. Establish the Apache Sentry Project
WHEREAS, the Board of Directors deems it to be in the best
interests of the Foundation and consistent with the
Foundation's purpose to establish a Project Management
Committee charged with the creation and maintenance of
open-source software, for distribution at no charge to
the public, related to Fine grained authorization to data and
metadata in Hadoop.
NOW, THEREFORE, BE IT RESOLVED, that a Project Management
Committee (PMC), to be known as the "Apache Sentry Project",
be and hereby is established pursuant to Bylaws of the
Foundation; and be it further
RESOLVED, that the Apache Sentry Project be and hereby is
responsible for the creation and maintenance of software
related to Fine grained authorization to data and metadata in Hadoop;
and be it further
RESOLVED, that the office of "Vice President, Apache Sentry" be
and hereby is created, the person holding such office to
serve at the direction of the Board of Directors as the chair
of the Apache Sentry Project, and to have primary responsibility
for management of the projects within the scope of
responsibility of the Apache Sentry Project; and be it further
RESOLVED, that the persons listed immediately below be and
hereby are appointed to serve as the initial members of the
Apache Sentry Project:
* Ali Rizvi <ali@apache.org>
* Anne Yu <anneyu@apache.org>
* Arun Suresh <asuresh@apache.org>
* Brock Noland <brock@apache.org>
* Chaoyu Tang <ctang@apache.org>
* Colin Ma <colin@apache.org>
* Daisy Zhou <daisy@apache.org>
* Dapeng Sun <sdp@apache.org>
* David Nalley <ke4qqq@apache.org>
* Erick Tryzelaar <erickt@apache.org>
* Gregory Chanan <gchanan@apache.org>
* Guoquan Shen <gqshen@apache.org>
* Hadi Nahari <hadi@apache.org>
* Hao Hao <hahao@apache.org>
* Jarek Jarcec Cecho <jarcec@apache.org>
* Johnny Zhang <dreambird@apache.org>
* Karthik Ramachandran <kramachandran@apache.org>
* Mark Grover <mark@apache.org>
* Milo Polte <milo@apache.org>
* Lenni Kuff <lskuff@apache.org>
* Patrick Daly <daly@apache.org>
* Patrick Hunt <phunt@apache.org>
* Prasad Mujumdar <prasadm@apache.org>
* Raghu Mani <raghu_mani@apache.org>
* Sean Mackrory <mackrorysd@apache.org>
* Shreepadma Venugopalan <shreepadma@apache.org>
* Sravya Tirukkovalur <sravya@apache.org>
* Tuong Truong <tuongtruong@apache.org>
* Vamsee Yarlagadda <vamsee@apache.org>
* Xiaomeng Huang <xiaom@apache.org>
* Xuefu Zhang <xuefu@apache.org>
NOW, THEREFORE, BE IT FURTHER RESOLVED, that Sravya Tirukkovalur
be appointed to the office of Vice President, Apache Sentry, to
serve in accordance with and subject to the direction of the
Board of Directors and the Bylaws of the Foundation until
death, resignation, retirement, removal or disqualification,
or until a successor is appointed; and be it further
RESOLVED, that the initial Apache Sentry PMC be and hereby is
tasked with the creation of a set of bylaws intended to
encourage open development and increased participation in the
Apache Sentry Project; and be it further
RESOLVED, that the Apache Sentry Project be and hereby
is tasked with the migration and rationalization of the Apache
Incubator Sentry podling; and be it further
RESOLVED, that all responsibilities pertaining to the Apache
Incubator Sentry podling encumbered upon the Apache Incubator
Project are hereafter discharged.
Special Order 7D, Establish the Apache Sentry Project, was
approved by Unanimous Vote of the directors present.
E. Change the Apache ZooKeeper Project Chair
WHEREAS, the Board of Directors heretofore appointed Michi
Mutsuzaki (michim) to the office of Vice President, Apache
ZooKeeper, and
WHEREAS, the Board of Directors is in receipt of the resignation
of Michi Mutsuzaki from the office of Vice President, Apache
ZooKeeper, and
WHEREAS, the Project Management Committee of the Apache ZooKeeper
project has chosen by vote to recommend Flavio Junqueira (fpj) as
the successor to the post;
NOW, THEREFORE, BE IT RESOLVED, that Michi Mutsuzaki is relieved and
discharged from the duties and responsibilities of the office
of Vice President, Apache ZooKeeper, and
BE IT FURTHER RESOLVED, that Flavio Junqueira be and hereby is
appointed to the office of Vice President, Apache ZooKeeper, to
serve in accordance with and subject to the direction of the
Board of Directors and the Bylaws of the Foundation until
death, resignation, retirement, removal or disqualification, or
until a successor is appointed.
Special Order 7E, Change the Apache ZooKeeper Project Chair,
was approved by Unanimous Vote of the directors present.
F. Change the Apache Tapestry Project Chair
WHEREAS, the Board of Directors heretofore appointed Howard M. Lewis
Ship (hlship) to the office of Vice President, Apache Tapestry, and
WHEREAS, the Board of Directors is in receipt of the resignation of
Howard M. Lewis Ship from the office of Vice President, Apache Tapestry,
and
WHEREAS, the Project Management Committee of the Apache Tapestry project
has chosen by vote to recommend Thiago H. de Paula Figueiredo (thiagohp)
as the successor to the post;
NOW, THEREFORE, BE IT RESOLVED, that Howard M. Lewis Ship is relieved
and discharged from the duties and responsibilities of the office of
Vice President, Apache Tapestry, and
BE IT FURTHER RESOLVED, that Thiago H. de Paula Figueiredo be and hereby
is appointed to the office of Vice President, Apache Tapestry, to serve
in accordance with and subject to the direction of the Board of
Directors and the Bylaws of the Foundation until death, resignation,
retirement, removal or disqualification, or until a successor is
appointed.
Special Order 7F, Change the Apache Tapestry Project Chair,
was approved by Unanimous Vote of the directors present.
8. Discussion Items
A. Self Service and Infrastructure
An outstanding JIRA issue against the infrastructure "self service"
application was unilaterally assigned to the Whimsy PMC without
consultation, and another was initially closed as WONTFIX, triggering a
larger discussion that ended up on board@. Included in that discussion
was a comment by the current VP of Infrastructure that he would be open
to the infrastructure team "tak(ing) responsibility for Whimsy the
service", and as a part of that impose a release discipline upon the
Whimsy PMC.
Meanwhile, an ASF member legally changed her name. She and the
secretary were able to reflect that change in our records and on the
site without any assistance by paid contractors. New committers were
given accounts based on a highly automated process whereby the
infrastructure staff run scripts that access requests stored as
structured data in svn. This data was placed in svn by a tool that was
originally part of whimsy and essentially jointly owned by the whimsy
PMC and the infrastructure team.
This suggests a different division of responsibility:
1) The infrastructure team (consisting of contractors and volunteers)
maintain control over master copies of ASF data resources, including
but not limited to: Subversion, Git, LDAP, and mailing lists.
Some of these resources may be mirrored (in some cases,
bidirectionally).
2) Groups (such as PMCs and the secretarial team) are given access
control rights to resources that they can manage. Where this is not
directly practical for security or other reasons (e.g., the new
account example above), tools that process authenticated requests
stored in an open format will be developed and deployed.
3) Multiple tools ("let a thousand flowers bloom") that make use of
the access described above may be developed. One can imagine a
future where the Perl scripts that PMC chairs use today are phased
out in favor of Syncope and/or Whimsy. Or an alternate future where
a separate VM is provisioned for ssh use by pmc chairs to run these
scripts. Decisions made by the infrastructure team to maintain or
discontinue the current "self serve" (id.apache.org) tool can be
made either in consultation with, or entirely independent of, those
made by other PMCs.
Anti-patterns to watch out for: (1) requiring PMCs to issue JIRA requests
to select features for their projects, (2) requiring users to use a
particular user interface to make a request, without providing
authenticated users access to the underlying data, and (3) tools
deployed without runbooks or other documentation on how they work.
Now seems to be an opportune time to discuss how infra can implement
self-service as a strategy. Sam will work with Ross as infra
re-tools.
B. Another month when there appears to have been a number of PMCs that
didn't report, needed reminders and/or reported late. Not sure of
the cause, even less sure of the solution. But it seems to be
an increasing problem...?
Some stats:
* https://whimsy.apache.org/board/missing-reports
* of the 13 missing PMC reports this month; 3 of those PMCs missed
the previous month (and one of those is heading to the attic);
additionally 1 was not accepted the previous month
* 3 PMCs proactively stated that they will be reporting next month
9. Review Outstanding Action Items
* David: follow up with last PMC and committer additions.
[ Santuario 2015-05-20 ]
Status:
* David: Finalise move to the Attic
[ Tuscany 2015-06-17 ]
Status:
* Jim: work with counsel to review the bylaws and propose changes (if
necessary) to clarify how to apply "two-thirds majority" when counting
votes.
[ Discussion Items 2015-08-19 ]
Status: Complete
* Brett: pursue a report for Continuum
[ Continuum 2015-12-16 ]
Status: no response - suggest taking an Attic proposal to the dev list
(with an option to reject, otherwise put it on the agenda next
month)
* Ross: Notify PMC that tools are available to aid in the Apache Extras
[ Pivot 2015-12-16 ]
Status:
* Chris: pursue a report for Stanbol
[ Stanbol 2015-12-16 ]
Status: stanbol reported.
* Brett: Follow through discussion on move to the Attic
[ Wink 2015-12-16 ]
Status: addressed in report
* Rich: Event in late April might conflict with ApacheCon North America.
[ Cassandra 2016-02-17 ]
Status: Cassandra has rescheduled the time for the event to avoid any
ApacheCon dates. Many thanks.
* Shane: Contact PMC to get a better report next month; make sure to read
the guidelines
[ Web Services 2016-02-17 ]
Status:
* Brett: Add another reminder to tardy projects the Monday before the
meeting
[ Discussion Items 2016-02-17 ]
Status: Done. See further discussion item this month.
10. Unfinished Business
11. New Business
12. Announcements
13. Adjournment
Adjourned at 12:03 p.m. (Pacific)
============
ATTACHMENTS:
============
-----------------------------------------
Attachment 1: Report from the Executive Assistant [Melissa Warnkin]
ApacheCon and TAC: TAC
* Since the last board report, where TAC only had 14 submitted applications
and 4 pending, we closed out at 48 applications and 1 pending – a record!
Kudos to the TAC Team for the extensive PR coverage and pulling in more
applications!! This is the highest number of applications to date!!
*Awaiting budget approval from the board for increased budget, but to date
nine acceptance letters have been sent out, and all rejection letters have
been sent out.
*Preparing flight proposals and rooming assignments
*Working on a VERY tight timeline, so everything has to be done very quickly
and efficiently
Quarterly Report
*Melissa completed the missing section from Craig
Fundraising
*There are holes everywhere, we have no accurate records, sponsors are not
getting answers
* Melissa will look at how we can ensure we get clarity on this
Trademarks:
* Tracking of registrations and follow-up items continues
-----------------------------------------
Attachment 2: Report from the VP of Brand Management [Shane Curcuru]
A host of personal emergencies and a variety of new, complex issues in the
past month mean that there's a backlog on making improvements to brand how-to
policies and procedures, but looking forward to newfound free time to make
progress shortly.
Created a BRAND private JIRA to track internal tasks and make it easier for
other trademarks committee members to productively review and work on
improvements.
Unfortunately, a PMC sent a strongly worded infringement letter to a third
party who actually holds a registered trademark to their name locally. We
were lucky in that this only resulted in the third party having their legal
counsel email us back with a polite "We're not infringing, here's why, please
go away" letter. I'll need assistance reviewing the existing procedure and
improving it so it's easy to understand when PMCs may directly send
infringement letters, versus when they must work with the Trademarks
Committee.
A lot of attention was brought to poor third party usage of our HADOOP® name
in places where nary an Apache® can be found. Dealing with this effectively -
as long experience with some issues with the Hadoop PMC show - requires a much
more detailed naming guideline so that PMCs and third parties alike can have a
specific and dispassionate answer as to how often the Apache must be used
before the project name. We could use more thoughtful feedback on trademarks@
here.
Several PMC trademark registrations in the US and elsewhere, and a renewal are
outstanding, and will be processed (and billed by our counsel) in the next few
weeks.
-----------------------------------------
Attachment 3: Report from the VP of Fundraising [Hadrian Zbarcea]
This was a relatively slow month for Fundraising, not much to report.
The only notable events are us getting a new Bronze Sponsor, ChameleonJohn and
interest expressed by another foundation to become a Bronze sponsor as well.
-----------------------------------------
Attachment 4: Report from the VP of Marketing and Publicity [Sally Khudairi]
I. Budget: we remain within budget, with no outstanding invoices due
at this time.
II. Fundraising/Branding/Marketing/ComDev liaison: Sally Khudairi
published the ASF Third Quarter report (November 2015-January 2016) on
25 February. She continues to collect a list of outstanding items
needed for the ongoing rollout of the new ASF logo, and will endeavor
to complete as much as possible in time for the upcoming ApacheCon.
III. Press Releases: the following formal announcements were issued
via the newswire service, ASF Foundation Blog, and announce@apache.org
during this timeframe:
- 8 March 2016 --The Apache Software Foundation announces @ApacheFlink
v1.0
- 25 February 2016 --The Apache Software Foundation Operations
Summary: November 2015 - January 2016
- 17 February 2016 --The Apache Software Foundation Announces Apache
Arrow as a Top-Level Project
IV. Informal Announcements: 7 items were published on the ASF
"Foundation" Blog, and 29 items were tweeted on @TheASF. 6 Apache News
Round-ups were issued, with a total of 80 weekly summaries published
to date. No new videos have been added to the ASF YouTube channel.
V. Future Announcements: two announcements are currently in
development. Projects planning to graduate from the Apache Incubator
as well as PMCs wishing to announce major project milestones and "Did
You Know?" success stories are welcome to contact Sally at
<press@apache.org> for more information. Kindly provide at least
2-weeks' notice for proper planning and execution.
VI. Media Relations: Sally has been working with several vendors
regarding their involvement with various Apache projects in press
releases, presentations, and events. Sally is finalizing the details
for media/analyst trainings that will be offered during the week of
ApacheCon, and will be announcing these opportunities to the community
within the next week. She is also writing a post for OpenSource.com in
celebration of the ASF’s 17th Anniversary on 25 March. Since the last
report, the ASF received 1,095 press clips vs. last month's clip count
of 1,692.
VII. Analyst Relations: we will be working with RedMonk and 451
Research on analyst briefings during ApacheCon and Apache: Big Data.
Apache was mentioned in 20 reports by Gartner, 13 reports by
Forrester, 11 reports by 451 Research, and 17 reports by IDC.
VIII. ApacheCon liaison: Sally continues to help promote ApacheCon and
Apache: Big Data in partnership with the Linux Foundation.
IX. (Non-ASF) Industry Events and Outreach liaison: no formal
activities are taking place at this time.
X. Newswire accounts: we have 48 pre-paid press releases remaining
with NASDAQ GlobeNewswire through December 2017.
# # #
-----------------------------------------
Attachment 5: Report from the VP of Infrastructure [David Nalley]
New Karma:
==========
Finances:
==========
Operations Action Items:
========================
Short Term Priorities:
======================
- Ensuring/monitoring that the dual git repository setup works as intended.
- Provision an isolated test environment (including isolated LDAP) for
developing/testing services faster than is currently possible, under a
separate domain (asfplayground.org). We believe this separation will also help
projects and volunteers work on their ideas, such as the Syncope trial, as
they can then develop and test without interfering with production systems.
- Looking at deploying Apache Traffic Server to help alleviate the troubled
BugZilla instances and possibly JIRA.
Long Range Priorities:
======================
- Mailing list system switchover is expected to happen in the coming months. We
are aware of a few outstanding mail-search requests that we have concluded
could be solved out-of-the-box by this.
- VMs on Eirene, Nyx and Erebus to be moved in readiness for their decommission
- Further explore identity management proposals
- Further explore the MATT experiment (see General Activity)
General Activity:
=================
- Finished the initial design of git-dual.apache.org, intended for distributed
git repositories (Whimsy experiment). Things have been fully in sync for now.
Some discoveries and gotchas were made in setting this up, such as split-brain
issues and canonical source requirements for the setup to sync properly - in
particular, it seems that the 'origin' setting in each repository must be set
to GitHub for it to sync properly both ways. There is still the issue of a
discrepancy between emails for commits pushed to ASF and commits pushed to
GitHub, but this is being worked on.
- Adding new members to our GitHub organisation has been fully automated and
tied to LDAP. Any committer setting their githubUsername field through
id.apache.org will automatically be added as a member of our organisation
there. We are pleased to say this is/was the final step in fully automating
the MATT experiment from the committers' side of things. All adding/removing
of members for github repos is now automated completely, if delayed by a few
hours due to rate limits (in anticipation of 1000+ repositories, we have
decided to do slow updates).
- Added JIRA SLA guidelines (as well as a status page on status.apache.org, see
below)
- We had a bad disk on coeus, our central database server, causing many services
to be slow while we replaced the disk and resilvered the mirror over the
weekend.
Ticket Response and Resolution Targets:
=======================================
We have added a new SLA for tickets. We are still tweaking the parameters in
this SLA, but the preliminary ones have been applied to our new JIRA SLA page,
where stats for the current reporting cycle can be found at
https://status.apache.org/sla/jira/?cycle=2016-03
Tickets created on or after February 23rd are counted towards our new SLA. We
have a tentative goal of having at least 90% of all tickets fully handled
(responded to and resolved) in time.
Quick March reporting cycle summary:
- 178 tickets opened
- 216 tickets resolved
- 144 tickets applied towards our SLA (Feb 23rd onwards)
- Average time till first response: 7 hours
- Average time till resolution: 17 hours
- Tickets fully handled in time: 95% (118/124)
Uptime Statistics:
==================
Nothing out of the ordinary to report here (99.9% across the board). We
decommissioned the use of minoatur as a web space provider and have moved
people.apache.org to home.apache.org. This has caused a slight rise in uptime
for standard services as the old people.apache.org was frequently experiencing
issues.
BugZilla has seen less abuse than before, possibly because of the measures
taken previously. We are however exploring utilizing Apache Traffic Server to
further ensure its future stability.
Once again, the Moin wiki is, as always, experiencing hiccups, caused by the
general flaw in its design. We urge any project still using this to switch to
cwiki, if they experience slowness in the service.
For detailed statistics, see http://status.apache.org/sla/
-----------------------------------------
Attachment 6: Report from the Apache Travel Assistance Committee [Nick Burch]
ApacheCon Vancouver
-------------------
Applications closed several days late, after extensions to support late
speaker announcements, and judging has completed. It's going to be a very
tight timeline, but between volunteers and Melissa, we hope it'll still work
fine.
This has been a record event for TAC, I believe our best ever by a fair
margin. In total, we've had 48 Applications! Of those, just under half were
from people speaking in some way, 13 were from students, 26 were from
committers +, 22 were from non committers, and about 10% were from women.
The event dates mean the cost will be met from the 2015-2016 budget, of
which only $15k remains. See the President report for more on our request
for additional funding to cover some additional strong applicants.
As with previous events, details of non-accepted speakers have been passed
to the Linux Foundation, who have a small amount of funding for speakers.
Any accepted that way will be handled by TAC (with us looking after them,
booking flights etc, but also getting them to help!), with the LF paying the
bill.
Budget permitting, we expect a great event from the TAC front.
Changes for next time
---------------------
The big change for Vancouver was the launch of TAC Stories
<http://www.apache.org/travel/stories/>, and the associated related
publicity and targetted messaged. We think this is partly behind the record
applicant numbers.
From our experiences with these publicity changes, we intend to brainstorm
a lot in Vancouver on proposed scoring and question changes. The best ideas
will then be taken back to the list, refined, and taken forward. (The
difference with doing this for publicity, vs previous list-only change
attempts, was dramatic). We'll therefore take the same approach with the
planned scoring and question changes, to try to favour interesting and
impact-ful candidates over those purely ASF-involved, whilst also avoiding
the mis-steps of previous attemps in this area.
We'll also look to capture (find out for past recipients as best we can)
more "impact" data, such as (but not only) people helped who become
committers and members
Committee
---------
No change
Sponsor Relations
-----------------
Anyone talking with sponsors needing an example of where the sponsor cash
made an impact, is strongly suggested to review the TAC Stories and pick one
or two from a suitable background / area to show!
-----------------------------------------
Attachment 7: Report from the VP of W3C Relations [Andy Seaborne]
-----------------------------------------
Attachment 8: Report from the Apache Legal Affairs Committee [Jim Jagielski]
Confirmed with counsel that our bylaws, and our usage and interpretation
regarding majority, are correct and require no change. Specifically,
Section 3.9 of the bylaws tracks the relevant Delaware law (Section 215).
The bylaws take the traditional approach to voting that once you have a
quorum, the action of the members is determined by a vote of the members
present. For example, a "majority" is a majority of votes cast (where
one can ignore Abstain, ie: "more Yes than No"). 2/3rds is handled the
same way. Once we have a quorum, the action *of the quorum* is an action
of the membership.
There are no issues requiring board attention.
-----------------------------------------
Attachment 9: Report from the Apache Security Team Project [Mark J. Cox]
The team continues to answer requests to security@ and redirect
as appropriate.
For Feb 2016:
3 Security vulnerability question, but not a vulnerability report
3 Phishing/spam/proxy/attacks point to site "powered by Apache" or
Confused user due to Android licenses
7 Direct Vulnerability report to security@apache.org
2 [site] (both addressed)
1 [tomcat]
1 [commons]
1 [jackrabbit]
1 [xerces]
1 [httpd]
6 Vulnerabilities reported to projects
1 [sentry]
1 [struts]
2 [commons]
1 [openoffice]
1 [couchdb]
-----------------------------------------
Attachment A: Report from the Apache Abdera Project [Ant Elder]
Apache Abdera provides Java implementations of the IETF Atom Syndication
Format and Publishing Protocol specifications.
Abdera is in maintenance mode with minimal development activity. I believe
there are at least three PMC members providing oversight still. This quarter
the main activity was a user getting help with a problem upgrading their
application. Turned out to be an AXIOM bug that was fixed by a new AXIOM
release but the debugging was done in the Abdera JIRA which I think shows
again why retiring projects to the Attic is not ideal.
The last release was over two years ago, the last commiter / PMC member
addition was Nov 2011.
No board issues.
-----------------------------------------
Attachment B: Report from the Apache Allura Project [Dave Brondsema]
## Description:
Apache Allura is an open source implementation of a software forge, a web site
that manages source code repositories, bug reports, discussions, wiki pages,
blogs, and more for any number of individual projects.
## Issues:
- No issues needing board attention.
## Activity:
- Added a new committer & PMC member who has been making contributions in
advance of GSOC application.
- We posted some GSOC ideas, and got some comments by interested people.
- Some discussion and helping of users / installers of Allura. Fixes ready
for a next release.
- Ongoing discussion, tickets, development from the active committers.
## Health report:
- GSOC is bringing some new interest, hopefully we can capitalize on it.
- One frequent committer has moved along to other things.
## PMC changes:
- Currently 13 PMC members.
- Pranav Sharma was added to the PMC on Sun Feb 07 2016
## Committer base changes:
- Currently 13 committers.
- Pranav Sharma was added as a committer on Mon Feb 08 2016
## Releases:
- 1.3.2 was released on Tue Dec 08 2015
-----------------------------------------
Attachment C: Report from the Apache Ant Project [Conor MacNeill]
-----------------------------------------
Attachment D: Report from the Apache Any23 Project [Lewis John McGibbney]
## Description:
Anything To Triples (Any23) is a library, a web service and a command
line tool that extracts structured data in RDF format from a variety
of Web documents.
## Issues:
The community continues to remian quiet with few bugs logged and few fixed.
## Activity:
We have had a handful of users registering bugs some of which have been
fixed but some remain open. The project really needs to move towards another
release to keep some momentum going. We are planning on another GSoC project
this year so fingers crossed that this works out.
## Health report:
Any23 is a very quiet project. The mailing lists are typically very quiet.
The project is still alive as PMC and Committers use the Jira instance
to discuss fixing bugs and improving issues. There is no hiding the fact
however that the community is not really growing much at all.
## PMC changes:
- Currently 13 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Stephane Corlosquet on Sun Sep 07 2014
## Committer base changes:
- Currently 13 committers.
- No new committers added in the last 3 months
- Last committer addition was Stephane Corlosquet at Mon Aug 18 2014
## Releases:
- Last release was 1.1 on Tue Oct 28 2014
## Mailing list activity:
On a positive note, we have more people subscribed to both
user@ and dev@. We would like to see more contributions
however.
- dev@any23.apache.org:
- 35 subscribers (up 2 in the last 3 months):
- 70 emails sent to list (47 in previous quarter)
- user@any23.apache.org:
- 47 subscribers (up 2 in the last 3 months):
- 5 emails sent to list (14 in previous quarter)
## JIRA activity:
- 8 JIRA tickets created in the last 3 months
- 8 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment E: Report from the Apache Archiva Project [Olivier Lamy]
-----------------------------------------
Attachment F: Report from the Apache Arrow Project [Jacques Nadeau]
## Description:
- Arrow is a columnar in-memory analytics layer designed to accelerate big
data. It houses a set of canonical in-memory representations of flat and
hierarchical data along with multiple language-bindings for structure
manipulation. It also provides IPC and common algorithm implementations.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- A number of articles were posted about Arrow in the last month. This has
brought in a large number of interested parties and we've seen nice increase
in community engagement.
- There has been solid ideation and design discussions around IPC, metadata
and shared memory semantics.
- Development of the Python bindings is underway with a number of JIRAs
focused on that component.
- Since people have become aware of the project, we've seen a nice increase in
activity on the mailing list. Within that last month we've gone from 17
subscribers to 263 on the dev list and have seen 136 messages on the list.
## Health report:
- JIRAs are being opened and closed at a solid rate given the freshness of the
project.
- A number of design discussions have included great feedback and engagement
people outside the initial PMC/committers.
- We've seen several code contributions from first-time contributors.
- The final separation of code from the Drill codebase is up for review and
will likely move forward after the 1.6 Drill release (voting nearly underway).
## PMC changes:
- Currently 17 PMC members.
- No new PMC members since project was established.
## Committer base changes:
- Currently 20 committers.
- New committers:
- Ippokratis Pandis was added as a committer on Thu Feb 18 2016
- Wes McKinney was added as a committer on Mon Feb 01 2016
## Releases:
- No releases yet.
## JIRA activity:
- 41 JIRA tickets created in the last 3 months
- 20 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment G: Report from the Apache Aurora Project [Bill Farner]
## Description:
Apache Aurora lets you use an Apache Mesos cluster as a private cloud. It
supports running long-running services, cron jobs, and ad-hoc jobs.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
- Significant number of contributors in recent 0.11.0 and 0.12.0 releases.
- Positive feedback from prebuilt binary packages (including nightlies),
signs of many users taking advantage of this to build their own.
## Health report:
Aurora has been under active development for this period, with strong
community engagement. We have placed deliberate effort to build release
notes as we iterate towards future releases, which has received positive
feedback from users.
## PMC changes:
- Currently 17 PMC members.
- New PMC members:
- Joshua Cohen was added to the PMC on Tue Dec 22 2015
- John Sirois was added to the PMC on Sun Jan 03 2016
- Stephan Erb was added to the PMC on Wed Feb 03 2016
- Steve Niemitz was added to the PMC on Mon Jan 11 2016
## Committer base changes:
- Currently 18 committers.
- New commmitters:
- John Sirois was added as a committer on Mon Jan 04 2016
- Stephan Erb was added as a committer on Wed Feb 03 2016
- Steve Niemitz was added as a committer on Tue Jan 12 2016
## Releases:
- 0.11.0 was released on Wed Dec 23 2015
- 0.12.0 was released on Sun Feb 07 2016
## JIRA activity:
- 79 JIRA tickets created in the last 3 months
- 185 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment H: Report from the Apache Axis Project [Deepal Jayasinghe]
-----------------------------------------
Attachment I: Report from the Apache Bigtop Project [Andrew Purtell]
ISSUES FOR THE BOARD’S ATTENTION
There are no issues requiring board attention at this time.
RELEASES
1.1.0 was released on Fri Jan 29 2016
ACTIVITY
Evans Ye will be presenting "Dockerized Hadoop platform and recent
updates in Apache Bigtop" at Apache Big Data NA 2016[1]
Olaf Flebbe presented "Apache Bigtop" at FOSDEM '16 in the HPC,
Big Data and Data Science Devroom on Jan 31th in Brussels[2]
We have seen an uptick in requests or patches for inclusion of additional
big data components into the Bigtop Stack: Apache Apex (incubating)[3],
Druid[4], Apache Flink[5], Apache HAWQ (incubating)[6], QFS[7],
HiBench[8]. This speaks to others sharing our vision of Bigtop as the
"Debian of Big Data" and indicates continued if not increasing momentum
for the project.
Northwestern University and Boston University have four graduate
students working on Apache Flink packaging for Bigtop, and testing it
deployed on OpenStack.
The Bigtop 1.1.0 release expands the reach of the Bigtop Stack with
ppc64le (POWER8) platform support. We would like to extend this further
to ARM platform support in upcoming releases and would welcome any
contributions in that regard.
COMMUNITY
Nate D'Amico was added to the PMC on Thu Jan 21 2016
Last PMC addition: Thu Jan 21 2016 (Nate D'Amico)
No new committers in the last 3 months.
STATS
32 committers
24 PMC
139 subscribers to the dev list (up 9 in the last 3 months)
186 subscribers to the user list (up 14 in the last 3 months)
189 JIRA tickets created in the last 3 months
141 JIRA tickets closed/resolved in the last 3 months
1. http://events.linuxfoundation.org/events/apache-big-data-north-america
2. https://fosdem.org/2016/schedule/event/bigtop
3. https://issues.apache.org/jira/browse/BIGTOP-2313
4. https://issues.apache.org/jira/browse/BIGTOP-2348
5. https://issues.apache.org/jira/browse/BIGTOP-1927
6. https://issues.apache.org/jira/browse/BIGTOP-2320
7. https://issues.apache.org/jira/browse/BIGTOP-2283
8. https://github.com/intel-hadoop/HiBench
-----------------------------------------
Attachment J: Report from the Apache Bloodhound Project [Gary Martin]
-----------------------------------------
Attachment K: Report from the Apache BookKeeper Project [Sijie Guo]
BookKeeper is a distributed, reliable, and high performance logging service.
The project also includes Hedwig which is a highly scalable Pub/Sub service
built on top of ZooKeeper and BookKeeper with strong durability guarantees.
= Project Status =
Development has continued towards the 4.4.0 release, which is a feature
release. It will be including improvements on bookie storage, compaction and
ledger recovery, and new features about last-add-confirmed long poll. We will
cut 4.4.0 at this month and plan 4.5.0.
= Releases =
Our last release was 4.3.2, released on 2015-11-30. The next release will be
4.4.0.
= Community Status =
The last committer added was Matteo Merli (mmerli) on the 6th Jul 2015.
No infrastructure issues.
70 subscribers in dev@bookkeeper.apache.org
83 subscribers in user@bookkeeper.apache.org
890 issues opened to date, 20 since 2015-11-12
613 issues resolved to date, 15 since 2015-11-12
57 people have reported issues, 6 since 2015-11-12
31 people have contributed patches, 5 since 2015-11-12
-----------------------------------------
Attachment L: Report from the Apache Buildr Project [Alex Boisvert]
Apache Buildr is a Ruby-based build system for Java-based applications,
including support for Scala, Groovy and a growing number of JVM languages and
tools.
Our last release (v1.4.23) happened on June 12th, 2015.
Development and community activity (mailing lists, bug reports, etc.) remains
relatively low. Our last committer/PMC change happened in October 2013.
I (Alex Boisvert) have been thinking about stepping down as PMC Chair for the
Buildr project. I just haven't been actively involved in the project in a
while and I don't foresee this changing much in the future. I initiated a
discussion with other PMC members on our private mailing list.
Otherwise, we have no issues that require board attention
-----------------------------------------
Attachment M: Report from the Apache BVal Project [Matt Benson]
The Apache BVal project implements the Java EE Bean Validation
specifications (v1 and 1.1)
and related extensions, and became a top-level project of the foundation on
February 15, 2012.
### Releases ###
Last BVal release (v1.1.1) was released on Feb, 2016.
### Activity ###
Few direct activity but some indirect thanks to Apache TomEE mainly which
gave feedback on 1.1.x releases.
Since there is no new version of the Bean Validation specification the
project is until next one mainly in maintenance and enhancement modes.
### Community ###
No changes in community.
Last PMC member added Q4 2013
Last committer added Q3 2013
### Branding ###
Nothing to report.
### Legal ###
No concerns at present.
### Infrastructure ###
Nothing needed at the moment.
-----------------------------------------
Attachment N: Report from the Apache Camel Project [Christian Mueller]
Apache Camel is a powerful open source integration framework based on
known Enterprise Integration Patterns.
## Issues:
- There are no issues requiring board attention at this time
## Activity:
- CVE-2015-5344 (Apache Camel's XStream usage is vulnerable to Remote Code
Execution attacks) is fixed, released and published.
- CVE-2015-5348 (Apache Camel's Jetty usage is vulnerable to Java object
de-serialisation vulnerability) is fixed, released and published.
- We are focusing the development of the next minor release Apache Camel
2.17.0.
## Health report:
- The project is healthy, active and stays at a high level.
- We got 2 new contributors who signed the ICLA in this reporting periode.
## PMC changes:
- Currently 28 PMC members.
- Gregor Zurowski was added to the PMC on Fri Dec 04 2015
## Committer base changes:
- Currently 50 committers.
- Antonin Stefanutti was added as a committer on Wed Mar 02 2016
## Releases:
- 2.15.5 was released on Mon Nov 30 2015
- 2.16.2 was released on Wed Jan 27 2016
## Mailing list activity:
- users@camel.apache.org:
- 889 subscribers (up 6 in the last 3 months):
- 1374 emails sent to list (1345 in previous quarter)
- dev@camel.apache.org:
- 334 subscribers (up 5 in the last 3 months):
- 679 emails sent to list (557 in previous quarter)
- issues@camel.apache.org:
- 74 subscribers (up 4 in the last 3 months):
- 2027 emails sent to list (1804 in previous quarter)
- notifications@camel.apache.org:
- 7 subscribers (up 1 in the last 3 months)
## JIRA activity:
- 277 JIRA tickets created in the last 3 months
- 286 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment O: Report from the Apache Cayenne Project [Andrus Adamchik]
## Description:
User-friendly Java ORM with tools
## Issues:
There are no issues requiring board attention at this time.
## Activity:
Work on Cayenne 4.0 continues. Lots of ideas. An important M3 milestone was
released on Feb 11. There were user requests to patch certain issues in the
current 3.1 GA release, which we did. Activity on the mailing lists is up
significantly from the previous quarter. There were contributions from new
people. Some are candidate for committership.
## Health report:
The project is healthy, with the level of activity corresponding to the mature
state of the technology. Activity is normal. New users show up periodically.
No questions go unanswered and there are no significant bugs which require
attention.
## PMC changes:
- Currently 7 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was John Huss on Thu Dec 06 2012
## Committer base changes:
- Currently 20 committers.
- No new committers added in the last 3 months
- Last committer addition was Savva Kolbachev at Mon Jan 19 2015
## Releases:
- 4.0.M3 was released on Thu Feb 11 2016
## Mailing list activity:
Activity is up compared to the last quarter on both user and dev. M3 release
probably accounts for dev spike.
- dev@cayenne.apache.org:
- 121 subscribers (up 2 in the last 3 months):
- 140 emails sent to list (61 in previous quarter)
- user@cayenne.apache.org:
- 242 subscribers (up 3 in the last 3 months):
- 150 emails sent to list (119 in previous quarter)
## JIRA activity:
- 26 JIRA tickets created in the last 3 months
- 18 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment P: Report from the Apache Chemistry Project [Florian Müller]
## Description:
Apache Chemistry is an effort to provide an implementation of the CMIS
(Content Management Interoperability Services) specification in Java,
Python, PHP, .NET, Objective-C, and JavaScript (and possibly other
languages).
The project has graduated in February 2011.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- There is mainly maintenance activity with small improvements.
Mainly bug fixes and small improvements.
- A new OpenCMIS release is planned.
## Health report:
- The CMIS standard hasn't changed and the libraries are mature now.
There is no major code development expected.
- Questions and issue reports are processed.
## PMC changes:
- Currently 35 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Sanija Shabani on Thu Dec 11 2014
## Committer base changes:
- Currently 37 committers.
- No new committers added in the last 3 months
- Last committer addition was Sanija Shabani at Wed Nov 26 2014
## Releases:
- DotCMIS 0.7 was released on Mon Apr 13 2015
- ObjectiveCMIS 0.5 was released on Mon Mar 09 2015
- OpenCMIS 0.13.0 was released on Mon Apr 06 2015
## Mailing list activity:
- dev@chemistry.apache.org:
- 183 subscribers:
- 76 emails sent to list (145 in previous quarter)
## JIRA activity:
- 8 JIRA tickets created in the last 3 months
- 6 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment Q: Report from the Apache CloudStack Project [Sebastien Goasguen]
## Description:
Apache CloudStack is an IaaS (“Infrastracture as a Service”) cloud
orchestration platform.
## Issues:
- CloudStack community wants to experiment with a pure GitHub approach to our
version control and CI.
- We took control of https://github.com/cloudstack which we did not own before
(Github transferred ownership to members of the PMC).
- The PMC seeks guidance from the board on GitHub integration and would like
to know what the plan and timeline is (if there is one) on operating an ASF
project out of GitHub.
- The Whimsy experiment on Github appears totally opaque to us and we don’t
know what the status or plan is.
## Activity:
- Large increase of releases with 4 since December due to a new commit workflow
- CloudStack conference Brazil announced for Sept 29-30, no ASF conflicts as
we know it.
- Citrix CloudPlatform business was sold to Accelerite, this may impact
CloudStack
- Schuberg Philis as forked CloudStack (interim report sent to board on
February 16th) (Annex A).
- Increased focus on CI and investigation of solutions outside of ASF infra.
## Health report:
- Committee Health score: 9.60 (Super Healthy) from reporter.apache.org
- Slight increase of registered participants in all mailing lists
- Slight decrease in number of emails sent on MLs.
- Significant decrease in commits while we searched for a new RM
- Increase in speed of releases as we adopted new workflow
## PMC changes:
- Currently 41 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Erik Weber on Wed Nov 18 2015
## Committer base changes:
- Currently 108 committers.
- No new committers added in the last 3 months
- Last committer addition was Rafael Weingärtner at Wed Dec 09 2015
## Releases:
- 4.6.2 was released on Thu Dec 17 2015
- 4.7.0 was released on Thu Dec 17 2015
- 4.7.1 was released on Tue Jan 26 2016
- 4.8.0 was released on Tue Jan 26 2016
## Mailing list activity:
- users@cloudstack.apache.org:
- 1145 subscribers (up 9 in the last 3 months):
- 873 emails sent to list (848 in previous quarter)
- significant decrease in the last week
- dev@cloudstack.apache.org:
- 763 subscribers (up 13 in the last 3 months):
- 3996 emails sent to list (6360 in previous quarter)
- downward trend
## JIRA activity:
- 148 JIRA tickets created in the last 3 months
- 72 JIRA tickets closed/resolved in the last 3 months
Annex A
——————
This interim report was sent to the board on February 16th with no response:
Dear Board,
The CloudStack report is not due until next round of reports, but I wanted to
report two partially related items:
1. Schuberg-Philis a company where a significant number of CloudStack
committers happens to work has forked CloudStack. The fork has received media
attention [3], hence this interim report to let the board know that we are
indeed well aware of the situation.
A detail account of the company’s reasoning is described in [1]. Their fork
is available on Github at [2].
A fork by a company of an ASF software is a non-issue (there are other
cloudstack forks) and our community is very thankful to Schuberg Philis for
many years of strong support, either through community events (organizing and
sponsoring) or through their indirect commitment via committers who happens to
have a $dayjob at Schuberg.
2. Through private discussions with committers who happen to have a $dayjob
at SBP, our lack of privileges/control on our github mirror has played *some*
role in this fork and created frustration. ( It is not to say that better
github control would have prevented the fork, but it might have allowed us to
resolve short term issues giving us time to work on longer term ones).
There is a risk that similar frustration grows within our community and that
developers accustomed to working on github decide to work directly on the SBP
fork or their own, thereby fragmenting our community.
Actionable items for the board:
We have not heard any reports on the status of Whimsy’s testing of github but
we would welcome being allowed to join any testing phase or if the boards
sides in favor of operating an ASF project directly on Github, we would
quickly vote in our community to decide on such a move.
Best,
[1] https://www.cupfighter.net/2016/01/welcome-mission-critical-cloud
[2] https://github.com/MissionCriticalCloud/cosmic
[3] http://www.networkworld.com/article/3028065/hybrid-cloud/schuberg-philis-forks-cloudstack-what-happens-next.html
-----------------------------------------
Attachment R: Report from the Apache Commons Project [Gary D. Gregory]
The Apache Commons project focuses on all aspects of reusable Java components.
The Apache Commons components are widely used in many projects, both within
Apache and without. Any ASF committer can commit to Apache Commons.
The last report was on December 16 2015.
No issues require board attention at this time.
## Activity:
We had three (3) releases this period (see below).
We are considering adding a new Commons component called Commons Crypto
currently called Chimera (https://github.com/intel-hadoop/chimera). It is an
optimized cryptographic library. It provides Java API for both cipher level and
Java stream level to help developers implement high performance AES
encryption/decryption with the minimum code and effort.
## Health report:
Overall project health is decent to good with 3 releases this period.
We do not have too much action on the mailing lists but we do see JIRAs and
GitHub PRs come regularly in to Commons IO and Commons Lang. These are
usually addressed in a timely fashion.
## PMC changes:
- Phil Steitz resigned from this PMC Feb 05 2016.
- Thomas Neidhart resigned from this PMC, noted Feb 05 2016.
- No new PMC members added in the last 3 months
- Last PMC addition was Bernd Eckenfels on Sat Nov 21 2015
## Committer base changes:
- No new committers added in the last 3 months
- Last committer addition was Loic Guibert at Wed Oct 14 2015
## Releases:
- JEXL-3.0 was released on Sat Dec 26 2015
- MATH-3.6 was released on Mon Jan 04 2016
- WEAVER-1.2 was released on Mon Feb 01 2016
## JIRA activity:
- 172 JIRA tickets created in the last 3 months
- 110 JIRA tickets closed/resolved in the last 3 months
Gary Gregory, for Apache Commons
-----------------------------------------
Attachment S: Report from the Apache Continuum Project [Brent Atkinson]
-----------------------------------------
Attachment T: Report from the Apache Cordova Project [Shazron Abdullah]
## Description:
A platform for building native mobile applications using HTML, CSS and
JavaScript.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
Current releases have been voted on according to the Apache vote policy.
We had one major platform release, cordova-osx, which has been revived after a
2.5 year absence and comes with Cordova Platform API support.
The other releases have been minor patch releases for 5 other platforms. Of
note, cordova-ubuntu had several patch releases after a year of absence,
mainly updates to support newer releases of the ubuntu SDK. cordova-windows
had several patch releases, the major one being support for the Cordova
Platform API. cordova-android had a patch release where it has support for a
new Plugin API.
cordova-ios had several patch releases - the latest was to fix a serious app
freezing situation, and also to support the new 167x167 icon needed for iPad
support. cordova-browser had a patch release to replace the cordova-serve
implementation with an updated version that uses `express` instead of our own
implementation.
There were also 18 plugin releases, and a major cordova-cli release to 6.0.0,
which includes default plugin pinning, as well as a new template feature. We
also released a significant documentation update that addresses major pain
points in developing for Cordova based on feedback we got from a survey we put
out (where we got 900 responses).
## Health report:
The month of December was slower because of the holiday period but activity
picked up around the middle of January. Consequently, we had a slight decrease
in the number of releases from last quarter (34 vs 37). For this period, we
managed two overall plugins releases (up from one, from last quarter) when our
goal was to have one plugins release per week, although we had individual
plugin releases as well.
## PMC changes:
- Currently 77 PMC members.
- New PMC members:
- David Barth was added to the PMC on Mon Jan 04 2016
- Raghav Katyal was added to the PMC on Wed Feb 03 2016
## Committer base changes:
- Currently 80 committers.
- Raghav Katyal was added as a committer on Wed Feb 03 2016
## Releases:
- cordova-android@5.1.0 was released on Sun Jan 24 2016
- cordova-android@5.1.1 was released on Wed Mar 02 2016
- cordova-browser@4.1.0 was released on Tue Mar 08 2016
- cordova-cli@6.0.0 was released on Thu Jan 28 2016
- cordova-common@1.1.0 was released on Wed Feb 17 2016
- cordova-ios@4.0.1 was released on Tue Dec 15 2015
- cordova-ios@4.1.0 was released on Wed Mar 02 2016
- cordova-js@4.1.3 was released on Thu Jan 28 2016
- cordova-lib@6.0.0 was released on Thu Jan 28 2016
- cordova-osx@4.0.0 was released on Tue Feb 16 2016
- cordova-osx@4.0.1 was released on Tue Mar 08 2016
- cordova-plugin-camera@2.1.0 was released on Sat Jan 16 2016
- cordova-plugin-contacts@2.0.1 was released on Sat Jan 16 2016
- cordova-plugin-device@1.1.1 was released on Sat Jan 16 2016
- cordova-plugin-file-transfer@1.5.0 was released on Sat Jan 16 2016
- cordova-plugin-file@4.1.0 was released on Sat Jan 16 2016
- cordova-plugin-geolocation@2.1.0 was released on Sat Jan 16 2016
- cordova-plugin-inappbrowser@1.1.1 was released on Mon Dec 14 2015
- cordova-plugin-inappbrowser@1.2.0 was released on Sat Jan 16 2016
- cordova-plugin-inappbrowser@1.2.1 was released on Thu Feb 04 2016
- cordova-plugin-media-capture@1.2.0 was released on Sat Jan 16 2016
- cordova-plugin-media@2.1.0 was released on Sat Jan 16 2016
- cordova-plugin-network-information@1.2.0 was released on Sat Jan 16 2016
- cordova-plugin-splashscreen@3.1.0 was released on Sat Jan 16 2016
- cordova-plugin-statusbar@2.1.0 was released on Sat Jan 16 2016
- cordova-plugin-test-framework@1.1.1 was released on Sat Jan 16 2016
- cordova-plugin-vibration@2.1.0 was released on Sat Jan 16 2016
- cordova-plugin-whitelist@1.2.1 was released on Sat Jan 16 2016
- cordova-plugin-wkwebview-engine@1.0.1 was released on Mon Dec 14 2015
- cordova-plugman@1.1.0 was released on Thu Jan 28 2016
- cordova-ubuntu@4.3.2 was released on Tue Jan 05 2016
- cordova-ubuntu@4.3.3 was released on Mon Feb 08 2016
- cordova-windows@4.3.0 was released on Mon Jan 18 2016
- cordova-windows@4.3.1 was released on Wed Feb 03 2016
## Mailing list activity:
The number of subscribers to dev@ has been consistently decreasing (~3% loss
every quarter) but nothing significant. However during this quarter we had a
50% increase of issue@ activity which could be attributed to increased testing
during the holiday period when development at users' companies might have
slowed down, so users could test better.
- dev@cordova.apache.org:
- 492 subscribers (down -15 in the last 3 months):
- 4028 emails sent to list (3558 in previous quarter)
- issues@cordova.apache.org:
- 89 subscribers (down -1 in the last 3 months):
- 8299 emails sent to list (5557 in previous quarter)
## JIRA activity:
- 653 JIRA tickets created in the last 3 months
- 640 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment U: Report from the Apache cTAKES Project [Pei J Chen]
## Description:
Apache clinical Text Analysis and Knowledge Extraction System (cTAKES) is
an open-source natural language processing system for information extraction
from electronic medical record clinical free-text.
## Issues:
- There are no issues requiring board attention at this time
## Activity:
- There continues to be interest with integration with other ASF Projects
(New contributions from Tika committers (CTAKES-343), Spark
integration (CTAKES-374).
- The committee is active with local meetups. Last one was held in
Oct 2015 in Boston.
- The committee is actively preparing features for the next release
3.2.3.
## Health report:
- Community is active. There is an increase in usage based on
activity and questions asked on the dev mailing lists. The number of
mailing list subscribers to dev and user continue to increase.
- We have several new contributors to the de identification component.
## PMC changes:
- Currently 30 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Michelle Chen on Mon Feb 02 2015
## Committer base changes:
- Currently 31 committers.
- No new committers added in the last 3 months
- Last committer addition was Jim Gregoric at Sat Feb 28 2015
## Releases:
- Last release was 3.2.2 on Sat May 30 2015
- 3.2.1 was released on Dec 10 2014
- 3.2.0 was released on Jul 23 2014
## Mailing list activity:
There is a significant uptick in the mailing list subscribers. This
is a good indicator that there is growing interest in the community
and an increase in a user base. We have also noticed an increase in
user questions and interest in helping contributing to the codebase.
- dev@ctakes.apache.org:
- 197 subscribers (up 6 in the last 3 months):
- 147 emails sent to list (204 in previous quarter)
- user@ctakes.apache.org:
- 172 subscribers (up 10 in the last 3 months):
- 19 emails sent to list (63 in previous quarter)
## JIRA activity:
- 5 JIRA tickets created in the last 3 months
- 2 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment V: Report from the Apache Curator Project [Jordan Zimmerman]
## Description:
- The Apache Curator Java libraries make using Apache ZooKeeper much easier
and more reliable.
## Issues:
- there are no issues requiring board attention at this time
## Health report:
- Curator is a healthy, active project. We have consistent, quality input
from the community and Curator usage continues to grow.
- Curator's health is intimately tied to Apache ZooKeeper and, from our
perspective, Apache ZooKeeper is a very healthy project
## PMC changes:
- Currently 11 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Mike Drob on Wed Jul 22 2015
## Committer base changes:
- Currently 11 committers.
- No new committers added in the last 3 months
- Last committer addition was Mike Drob at Thu Jul 23 2015
## Releases:
- 2.10.0 was released on Sun Feb 14 2016
- 3.1.0 was released on Sun Feb 14 2016
## Mailing list activity:
- dev@curator.apache.org:
- 48 subscribers (up 3 in the last 3 months):
- 487 emails sent to list (602 in previous quarter)
- user@curator.apache.org:
- 152 subscribers (up 6 in the last 3 months):
- 32 emails sent to list (143 in previous quarter)
## JIRA activity:
- 21 JIRA tickets created in the last 3 months
- 19 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment W: Report from the Apache Etch Project [Martin Veith]
Apache Etch is a cross-platform, language- and transport-independent
RPC-like framework for building and consuming network services.
BOARD ISSUES
There are no Board-level issues at this time.
RELEASES
* Apache Etch 1.4.0 was released on August, 06 2014.
ACTIVITY
* No activity since last report on the user and developer mailing lists.
I will start a discussion on the Etch private list to move Etch to attic.
* Bug fix release 1.4.1 is currently on hold as no developer has had time to
finalize it
COMMITTERS OR PMC MEMBERS CHANGE
* No changes regarding PMC or committers composition since graduation
in January 2013.
* No changes in our committer and user base. We were able to get
exactly three binding PMC votes for the last release.
-----------------------------------------
Attachment X: Report from the Apache Falcon Project [Srikanth Sundarrajan]
ABOUT
Falcon is a data processing and management solution for Hadoop
designed for data motion, coordination of data pipelines,
lifecycle management, and data discovery. Falcon enables end
consumers to quickly onboard their data and its associated
processing and management tasks on Hadoop clusters.
ISSUES
There are no issues that require board's attention at this time.
STATUS
Since the last report, 0.9 was released. Features included in
0.9 has been covered in a recent blog
https://blogs.apache.org/falcon/entry/what_s_new_in_falcon. Key
features added in this release are Native scheduling - alpha version,
database import/export and further extensions to FalconUnit. The
next version is planned for release in early May 2016. Falcon
project is also participating the GSoC and sees this as an opportunity
to build some useful features while primarily focusing on building
the community further. Project moved from using review board to
github pull request model and this has been greatly helpful
in streamling the workflow. We are also in the process of moving
the falcon site to git branch from svn.
PMC CHANGES
- Currently 15 PMC members.
- Ajay Yadav was added to the PMC on Thu Dec 03 2015
COMMITTER CHANGES
- Currently 22 committers.
- New commmitters:
- Pavan Kumar was added as a committer on Tue Jan 26 2016
- Peeyush Bishnoi was added as a committer on Tue Jan 26 2016
RELEASES
- 0.9 was released on Tue Feb 16 2016
- 0.8 was released on Sun Nov 15 2015
MAILING LIST ACTIVITY
- dev@falcon.apache.org:
- 119 subscribers (down -1 in the last 3 months):
- 3312 emails sent to list (3061 in previous quarter)
- issues@falcon.apache.org:
- 6 subscribers (up 1 in the last 3 months)
- user@falcon.apache.org:
- 26 subscribers (up 2 in the last 3 months):
- 8 emails sent to list (6 in previous quarter)
JIRA ACTIVITY
- 199 JIRA tickets created in the last 3 months
- 169 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment Y: Report from the Apache Felix Project [Carsten Ziegeler]
Apache Felix is a project aimed at implementing specifications from the OSGi
Alliance as well as implementing other supporting tools and technologies
aligned with OSGi technology.
Community
PMC: No new PMC members have been added in this report period. The last
new PMC member was added in Jul. 2014.
Committers: One new committer (Thomas Watson) has been added in this
report period. The last new committer was added in Jan. 2016.
Steady mailing list activity.
There are no issues requiring board attention at this time.
Software
Apache Felix AutoConf resource processor 0.1.8 and
Felix DeploymentAdmin 0.9.10 released (January 20, 2016)
Apache Felix Utils 1.8.2, EventAdmin 1.4.6, and
FileInstall 3.5.2 (January 19, 2016)
Apache Felix Http Jetty 3.1.6, Apache Felix Http Bridge 3.0.6 and
Apache Felix Http Base 3.0.6 (January 9, 2016)
Project Branding
Nothing to report
Licensing and other issues
Nothing to report
-----------------------------------------
Attachment Z: Report from the Apache Flex Project [Alex Harui]
Apache Flex is an application framework for easily building Flash-based
applications for mobile devices, the browser and desktop.
RELEASES
-Apache Flex SDK 4.15.0 was released on 1/9/16.
-Apache FlexJS 0.5.0 was released on 11/14/15.
-Apache Flex FalconJX 0.5.0 was released on 11/14/15.
-Apache Flex BlazeDS 4.7.2 was released on 11/16/15.
-Apache Flex Tour De Flex Component Explorer 1.2 was released on 11/28/14.
-Apache Flex Tool API 1.0.0 was released on 11/20/14
-Apache Flex Squiggly 1.1 was released on 10/26/14
-Apache Flex Installer 3.2.0 was released on 6/23/15.
ACTIVITY
The past three months saw the release of Apache Flex SDK 4.15.0. Bug fix
activity continues on even after the release. There seems to be gradually
increasing interest in FlexJS, a version of Flex that is independent from
the Adobe Flash Platform. We continue to see new names with new
questions. Some potential committers are hopefully among them. Three
members of the PMC are hosting a FlexJS education and training event in
San Francisco on April 4. One committer is working on distributing FlexJS
as an NPM module. Work on Maven integration continues.
3 PMC members had presentations accepted for ApacheCon NA. The Flex
community tried to coordinate a Client Track for ApacheCon with folks from
the Cordova community, but apparently the Linux Foundation wasn't
interested in having such a track since some presentations were rejected.
A revamp of the flex.a.o website is underway. It isn't ready for branding
review just yet.
CODE ADOPTION
In the prior report we discussed the adoption of non-ASF code bases that
are already licensed under ALv2. I think the community will eventually
undertake one or more of the adoptions utilizing advice from the board but
it didn't happen this quarter simply from lack of a volunteer to make it
happen.
COMMUNITY
-Andy Dufilie was added as a committer.
-No new PMC members this quarter.
-Last PMC addition was Josh Tynjala on Wed Sep 16 2015
-A few PMC members were nominated for ASF membership.
-Latest analytics include a little over 1000 hits per day on the
website during the work week (less on weekends).
-There were more than 3000 installs of Apache Flex 4.15.0 since its
release in January.
-Almost 65,000 people have run the Tour De Flex application. Tour De Flex
is a set of examples folks use to learn how to develop Flex applications.
TRADEMARKS
-In the last report, we reported that a company is promoting a software
product called Flex that appears to be related to themes/styles for
website visuals. Despite several attempts to contact them, they have not
responded. We will start a thread on trademarks@ shortly to determine the
next steps.
-A trademark issue with a com.br website was handled and closed.
-----------------------------------------
Attachment AA: Report from the Apache Flink Project [Stephan Ewen]
DESCRIPTION
Flink is a distributed data streaming system for batch and streaming data
analysis on top of a streaming dataflow engine.
Flink's stack contains functional batch and streaming analysis APIs in
Java and Scala and libraries for various use cases.
Flink interacts and integrates with several Apache projects in the broader
ecosystem of technology around Apache Hadoop and Apache Kafka.
ISSUES
- There are no issues that require board attention.
STATUS AND ACTIVITY
- The recent months where dominated by the efforts to release Flink 1.0, which
was officially announced by the ASF on March, 8th.
- The 1.0 release was themed around backwards compatibility, and operational
features. A complex event processing library was added as well.
- A roadmap for the first half of 2016 has been published by the community on
the mailing lists end of December.
- Flink seems to get a decent amount of interest, several upcoming conference
talks (e.g., Strata, Hadoop Summit, Kafka Summit, OSCon, ApacheCon, and
several Meetups)
- The latest release (1.0.0) saw slightly fewer contributors (64 people) than
the previous one (0.10.0 had 79 contributors), because some features and
contributions were held off / delayed in order to establish the 1.0
relevant tools (like compatibility checks).
COMMUNITY
- There was no new PMC addition since the last report.
The latest PMC addition was July 2nd, 2015 (Maximilian Michels)
- There were two committers added since the last report
- ChengXiang Li was added on January, 20th, 2016
- Greg Hogan was added on March, 8th, 2016
Flink currently has 23 committers and 16 PMC members
RELEASES
The following releases were made since the last board report:
- 0.10.2 was released on February, 10th, 2016
- 1.0.0 was released on March, 8th, 2016
ACTIVITY ON JIRA / MAILING LISTS
Development speed continues to be healthy.
- 440 JIRA tickets created in the last 3 months
- 374 JIRA tickets closed/resolved in the last 3 months
Compared to previous quarters, there is a bit of a shift in mailing list
activity from the dev list to the users list.
- dev@flink.apache.org:
- 323 subscribers (up 68 in the last 3 months):
- 1266 emails sent to list (1617 in previous quarter)
- user@flink.apache.org:
- 414 subscribers (up 97 in the last 3 months):
- 1528 emails sent to list (1225 in previous quarter)
- issues@flink.apache.org:
- 54 subscribers (up 9 in the last 3 months):
- 8794 emails sent to list (11290 in previous quarter)
-----------------------------------------
Attachment AB: Report from the Apache Groovy Project [Guillaume Laforge]
## Description:
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.
## Issues:
There are no particular issues requiring board attention at this time.
## Activity:
The project is active, as usual.
We released a new version, with 2.4.6, that our users were eagerly awaiting.
We're thinking of cutting a first beta release of the future Groovy 2.5.
But there are still some improvements we want to make to our release process
to simplify the release management, to be able to release more often.
Looking at the "pulse" on Github [1], for the past month (sliding window),
the project received contributions from 17 authors who have pushed 76 commits
to master and 135 commits to all branches. On master, 133 files have changed
and there have been 1,708 additions and 575 deletions.
The subscribers to our mailing-lists have increased, even if the activity
seems to be a bit lower this month.
[1] https://github.com/apache/groovy/pulse/monthly
## Health report:
The project is healthy.
The recently created twitter handle, @ApacheGroovy,
has increased from 1200 followers to 1345, since last month.
For the third consecutive month, Apache Groovy is listed in the top 20
of the TIOBE programming language index.
The project is back at the 17th position.
Upcoming dedicated conferences are coming up:
- GR8Days in Poland in March
- Greach in Spain in April
- GR8Conf Europe in June
- GR8Conf US in July
- G3 Summit in December (new conference)
## PMC changes:
- Currently 9 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Andrew Bayer on Wed Nov 18 2015
## Committer base changes:
- Currently 16 committers.
- No new changes to the committer base since last report.
## Releases:
- 2.4.6 was released on Feb 22 2016
- 2.4.5 was released on Sept 17 2015
- 2.4.4 was released on Jul 09 2015
- 2.4.3 was released on Mar 23 2015
## Mailing list activity:
- TODO Please explain what the following statistics mean
for the project. If there is nothing significant in the figures, omit this
section.
- users@groovy.apache.org:
- 332 subscribers (up 32 in the last 3 months):
- 313 emails sent to list (384 in previous quarter)
- dev@groovy.apache.org:
- 197 subscribers (up 18 in the last 3 months):
- 303 emails sent to list (522 in previous quarter)
- issues@groovy.apache.org:
- 8 subscribers (up 1 in the last 3 months)
- notifications@groovy.apache.org:
- 24 subscribers (up 1 in the last 3 months):
- 901 emails sent to list (1092 in previous quarter)
## JIRA activity:
- 77 JIRA tickets created in the last 3 months
- 72 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AC: Report from the Apache Gump Project [Stefan Bodewig]
Apache Gump is a cross-project continuous integration server. Gump's
intention isn't so much to be a CI server but rather a vehicle that
makes people look beyond their project's boundaries and helps the
projects to collaborate.
Gump is written in Python and supports several build tools and version
control systems. The Apache installation of Gump builds ASF as well
as non-ASF projects and their dependencies. It started in the Java
part of the foundation but also builds projects like APR, HTTPd and
XMLUnit.NET.
== Summary ==
No development activity, Gump seems to create useful results for the
few projects that use it.
== Releases ==
Gump has never done any releases. One reason for this is that the ASF
installations of Gump work on the latest code base almost all of the
time following its "integrate everything continuously" philosophy.
== Activity ==
The projects that use Gump have occasionally modified their respective
configuration files. No other activity.
=== Mailing-List Statistics ===
general@gump.apache.org:
47 subscribers (down -1 in the last 3 months) (93 emails sent in the
past 3 months, 80 in the previous cycle)
commits@gump.apache.org:
21 subscribers (up 2 in the last 3 months) (19 emails sent in the past
3 months, 10 in the previous cycle)
== Changes to the Roster ==
All ASF committers have write access to the metadata that configure
the ASF installations.
The last changes to the PMC have seen Konstantin Kolinko and Mark
Thomas join in November 2014.
-----------------------------------------
Attachment AD: Report from the Apache Helix Project [Kishore Gopalakrishna]
-----------------------------------------
Attachment AE: Report from the Apache Hive Project [Ashutosh Chauhan]
## Description:
- The Apache Hive (TM) data warehouse software facilitates querying and
managing large datasets residing in distributed storage.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- Even as a mature project continues to see strong development in various
areas.
## PMC changes:
- Currently 29 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was John Pullokkaran on Mon Nov 23 2015
## Committer base changes:
- Currently 59 committers.
- Wei Zheng was added as a committer on Wed Mar 09 2016
## Releases:
- 2.0.0 was released on Mon Feb 15 2016
## Mailing list activity:
- dev@hive.apache.org:
- 822 subscribers (up 14 in the last 3 months):
- 1392 emails sent to list (1703 in previous quarter)
- issues@hive.apache.org:
- 13 subscribers (up 0 in the last 3 months):
- 7276 emails sent to list (8636 in previous quarter)
- user@hive.apache.org:
- 2120 subscribers (up 35 in the last 3 months):
- 1064 emails sent to list (1029 in previous quarter)
## JIRA activity:
- 613 JIRA tickets created in the last 3 months
- 454 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AF: Report from the Apache HttpComponents Project [Asankha Perera]
Status report for the Apache HttpComponents project - March 2016
The Apache HttpComponents project is responsible for creating and maintaining
a toolset of low-level Java components focused on HTTP and associated protocols.
* Status
Overall the project remains active. HttpCore 5.0 and HttpClient 5.0 are nearing
a major milestone of being compliant with mandatory requirements of RFC 7230,
RFC 7231 and RFC 7235.
* Releases
HttpComponents Core 5.0 alpha1 was released on the 5th of January 2016
HttpComponents Client 5.0 Alpha1 was released on the 28th of January 2016
HttpComponents Client 4.5.2 GA was released on the 2nd of March 2016
* Community
The community remains small but active, and has good user interaction on the
mailing lists.
-----------------------------------------
Attachment AG: Report from the Apache Ignite Project [Dmitriy Setrakyan]
## Description:
The Apache Ignite (TM) In-Memory Data Fabric is a high-performance,
integrated and distributed in-memory platform for computing and
transacting on large-scale data sets in real-time, orders of magnitude
faster than possible with traditional disk-based or flash technologies.
Apache Ignite (TM) provides many in-memory components to improve
performance and scalability of user applications, including in-memory
data grid (distributed caching), in-memory compute grid, in-memory
streaming, and more.
## Activity:
- The community has released 1.5.0 final version.
The release includes C++ and .NET/C# support, deadlock-free transactions,
compact binary marshalling protocol, OSGI support, integration with MQTT,
Flume, Camel, and Twitter streams, and many other features.
- The community is working towards version 1.6.0, which will include
ODBC support, and non-collocated SQL joins, as well as significant
performance improvements.
- Based on user requests, and given that one of the main features of Ignite
is performance, the community desided to start publishing transparent
reproducable performance comparisons to other products, beginning with
Hazelcast. The Hazelcast team questioned the validity of the test, and
Ignite community worked with Hazelcast on reproducing it. Ignite community
is planning to publish performance comparisons with other open source
projects, including Apache Cassandra, Infinispan, and Redis. The
comparisons will be published on the Ignite website with code and detailed
steps to reproduce the numbers on Amazon AWS.
## Health report:
- Ignite keeps attracting new contributors on the mailing list
- Ignite chatroom member list cintinously grows
## Issues:
- There are no outstanding issues.
## LDAP committee group/Committership changes:
→ Roman Shtykh was added as a committer on Fri Jan 29 2016
→ Currently 27 committers and 24 PMC members.
## Releases:
→ 1.5.0-b1 was released on Mon Dec 07 2015
→ 1.5.0.final was released on Mon Jan 04 2016
## Mailing list activity:
- dev@ignite.apache.org:
- 149 subscribers (up 18 in the last 3 months):
- 2276 emails sent to list (2611 in previous quarter)
- issues@ignite.apache.org:
- 18 subscribers (up 0 in the last 3 months):
- 5113 emails sent to list (4892 in previous quarter)
- user@ignite.apache.org:
- 206 subscribers (up 55 in the last 3 months):
- 1145 emails sent to list (774 in previous quarter)
## JIRA activity:
- 680 JIRA tickets created in the last 3 months
- 506 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AH: Report from the Apache Incubator Project [Ted Dunning]
Incubator PMC report for March 2016
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 52 podlings currently undergoing incubation.
* Community
New IPMC members:
- Kathey Marsden
- Daniel John Debrunner
* New Podlings
- Guacamole
- Joshua
- Quarks
* Graduations
The board has motions for the following:
- Sentry
* Releases
The following releases entered distribution during the month of
February:
2016-02-06 Apache Geode 1.0.0-incubating.M1
2016-02-07 Apache Apex v3.3.0-incubating
2016-02-11 Apache Wave 0.4.0-incubating
2016-02-11 Apache SystemML 0.9.0-incubating
2016-02-11 Apache TinkerPop 3.1.1-incubating
2016-02-20 Apache Johnzon 0.9.3-incubating
2016-02-25 Apache Kudu (incubating) 0.7.0
2016-02-26 Apache AsterixDB 0.8.8-incubating
* IP Clearance
- No podling related IP Clearances were processed during this time.
* Legal / Trademarks
- There was substantial discussion on general@incubator about how
challenging it is to produce compliant LICENSE and NOTICE files.
- A couple of podlings with runtime LGPL dependencies pledged to remove
those dependencies before graduation but were permitted to make
incubating releases in the meantime. There was uncertainty as to
whether VP Legal's approval was required; ultimately VP Legal appeared
on general@incubator and approved the plans.
* Infrastructure
- The Freemarker podling had a long standing request to use their existing
domain as the primary domain. This was approved by Shane Curcuru but
closed by infra without comment, see INFRA-10787.
- The Kudu podling is currently running its website as http://getkudu.io.
The standard webpage of http://kudu.incubator.apache.org does not work.
An infra ticket has been created to do the conversion INFRA-11407.
* Miscellaneous
- The Incubator's Retirement Guide has been substantially refreshed, and
it should now be easier for a Mentor or other volunteer to perform the
administrative steps to retire a podling.
- This month saw a large number of mentors resign from podlings.
- Brooklyn submitted an IP Clearance on the incubator mailing lists.
Last that was seen about the incubators role in IP Clearance was that
it shouldn't be the gatekeeper of top level projects.
- The current count of 52 podlings is likely the largest the incubator
has ever seen.
* Credits
- Report Manager: Marvin Humphrey
- Interim Report Manager: John D. Ament
-------------------- Summary of podling reports --------------------
* Still getting started at the Incubator
- Impala
- Joshua
- Milagro
* Not yet ready to graduate
No release:
- CMDA
- Fineract
- log4cxx2
- Metron
- Toree
Community growth:
- CommonsRDF
- Kudu
- Myriad
- SAMOA
- Singa
- Taverna
- Trafodion
- Zeppelin
* Ready to graduate
The Board has motions for the following:
- Sentry
* Did not report, expected next month
- HTrace
- iota
- Johnzon
- OpenAz
- Ranger
- Sirona
- Wave
----------------------------------------------------------------------
Table of Contents
Atlas
Climate Model Diagnostic Analyzer
CommonsRDF
Fineract
Impala
Joshua
Kudu
log4cxx2
Metron
Milagro
MRQL
Myriad
SAMOA
Sentry
Singa
Streams
Taverna
Toree
Trafodion
Zeppelin
----------------------------------------------------------------------
--------------------
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. Podling name search is pending
2. Expand the community and add more committers
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
* Everything seems to be smooth, nothing specific at this time.
How has the community developed since the last report?
1. The user/dev community show increasing interests.
The average number of messages in a month is around 400.
3. Around 10 contributors were added, number of contributors is at 42
currently.
How has the project developed since the last report?
1. Integrations with storm, falcon and sqoop were added. Tagging feature is
now available in the dashboard. Community is working on entity deletes,
business catalog, HA and improvements to existing integrations.
2. 0.6-incubating version was released in Dec, 2015.
3. A total of 143 issues were created and 48 of them were resolved since
Jan, 2016
Date of last release:
* 2015-12-31 - 0.6-incubating
When were the last committers or PMC members elected?
* Suma Shivaprasad was elected as a committer on 10/02/2015.
Signed-off-by:
[ ](atlas) Arun Murthy
[x](atlas) Chris Douglas
[x](atlas) Jakob Homan
[ ](atlas) Vinod Kumar Vavilapalli
--------------------
Climate Model Diagnostic Analyzer
CMDA provides web services for multi-aspect physics-based and phenomenon-
oriented climate model performance evaluation and diagnosis through the
comprehensive and synergistic use of multiple observational data, reanalysis
data, and model outputs.
Climate Model Diagnostic Analyzer has been incubating since 2015-05-08.
Three most important issues to address in the move towards graduation:
1. Moving project communication to the mailing list;
2. Moving development activities to be owned by Apache;
3. Working on community building.
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?
* Started using the mailing list dev@cmda.incubator.apache.org
to communicate project development issues;
* Created a Docker container that will be used for our future
development as well as deployment vehicle (in progress);
* Working on a unified git repository to host both the CMU and
the JPL code bases;
How has the project developed since the last report?
* The JPL team developed the following new services:
* Time series for multiple datasets
* Conditional probability density function calculation
* Empirical orthogonal function calculation
* Random forest feature importance calculation
* Anomaly calculation
* The JPL team improved these features:
* A new color scheme of data visualization of some services
* The URL for a RestFul service call has been constructed
* The JPL team is working on
* supporting a workflow with CMDA services. identified first examples to
work on.
* modifying the CMDA services to be “chainable” (callable in a
workflow).
* The CMU team created a unified github repository that
has both the CMU and JPL code bases. Needs cleanup;
* The CMU team created a new Docker container that has
the latest Ubuntu operating system and the run-time
environment for the CMU deployment;
* The JPL team installed the run-time environment in
the Docker container for the JPL deployment.
An integrated test is pending;
* The JPL team acquired a GPU server that will be used
as the testbed for speeding up their web services;
Date of last release:
XXXX-XX-XX
When were the last committers or PMC members elected?
Signed-off-by:
[X](climatemodeldiagnosticanalyzer) James W. Carman
[ ](climatemodeldiagnosticanalyzer) Chris Mattmann
[X](climatemodeldiagnosticanalyzer) Michael James Joyce
[ ](climatemodeldiagnosticanalyzer) Kim Whitehall
[ ](climatemodeldiagnosticanalyzer) Gregory D. Reddin
Shepherd/Mentor notes:
Great news! The community wrote the report this month! Thank you to
Lei Pan for pushing forward and I have high hopes over the next few months
we can light a fire under this project.
--------------------
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. Re-engage and grow the Commons RDF community base
2. Work with key target communities (initially within Apache) to ensure
Commons RDF meets potential user requirements and expectations towards
next versions of the Commons API.
3. Find lateral target goals that could make the project viable.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
n/a
How has the community developed since the last report?
Sleeper community in the last months; very few mails and no commits.
How has the project developed since the last report?
Project's development has completely stop in the last months. We expected
a different engagement from major RDF toolkits. But since that does not
happen, we have started to discuss options to find a viability for the
project https://s.apache.org/oxqb
By the next reporting period we should have something more concrete
towards the future, or we could think about a possible exit strategy.
Date of last release:
2015-05-07
When were the last committers or PMC members elected?
n/a (no PPMC or Committers have been elected yet)
Signed-off-by:
[ ](commonsrdf) Rob Vesse
[x](commonsrdf) John D Ament
[ ](commonsrdf) Gary Gregory
Shepherd/Mentor notes:
johndament: The report reflects current community engagement.
--------------------
Fineract
Fineract is an open source system for core banking as a platform.
Fineract has been incubating since 2015-12-15.
Three most important issues to address in the move towards graduation:
1. Inform the non-technical part of the existing Mifos.org community of
the change in project structure
2. Getting licensing issues figured out for our first release
3. Replacing dependencies that are not compliant with the license policies
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
None, currently.
How has the community developed since the last report?
Since the code was initially pushed over, the community is working on the
first release.
In addition to the initial committer new contributors started to work on
the project.
There is a technical conference in Amsterdam in the second week of March
during which some contributors and some community members will be
introduced to developing under the Apache model.
How has the project developed since the last report?
The initial code is now available and the work to meet the license
policies has started.
Date of last release:
N/A
When were the last committers or PMC members elected?
N/A
Signed-off-by:
[ ](fineract) Ross Gardler
[ ](fineract) Greg Stein
[X](fineract) Roman Shaposhnik
--------------------
Impala
Impala is a high-performance C++ and Java SQL query engine for data stored
in Apache Hadoop-based clusters.
Impala has been incubating since 2015-12-03.
Three most important issues to address in the move towards graduation:
1. Movement of existing JIRA / Git / wiki resources to Apache
equivalents
2. Initial release as incubating project.
3. Community growth
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 have been no additions to the committer or PMC lists since
incubation began. However, we have seen an uptick in external
contributions, both through code, and in discussion on the mailing list.
One contributor has been attempting to port Impala to PPC, and has
reported some success after asking many questions.
How has the project developed since the last report?
We have made some slow progress with our initial infrastructure tasks.
Code review traffic is now copied to dev@impala.incubator.apache.org,
which means that developer discussions are now happening on the mailing
lists.
We have a number of infrastructure tasks ahead of us which are blocked on
the current Impala team at Cloudera being very busy with an internal
release (this is one reason we look forward to a more diverse community!).
For example:
1. We would like to move our Git repository to .apache.org in short order,
but as it stands the existing repo is 10GB large and historically
contains many binary artifacts that, while acceptably licensed, have no
useful place in Impala's repository. We need to strip these artifacts
from the Git history, and then adjust Gerrit to commit to the new
branch in the new repo. This is not hard but takes some time.
2. We would also like to move our JIRA tickets from issues.cloudera.org to
issues.apache.org. Experience in a sister podling has shown that this
isn't straightforward if we wish to preserve existing release labels,
user assignments and so on, so requires some time.
We anticipate having much more time to work on these basic issues after
the end of February. We look forward to getting Impala into a position
where it is easier for the larger community to collaborate on these kinds
of project management issues.
Date of last release:
None since entering incubation.
When were the last committers or PMC members elected?
None since entering incubation.
Signed-off-by:
[X](impala) Tom White
[ ](impala) Todd Lipcon
[ ](impala) Carl Steinbach
[ ](impala) Brock Noland
--------------------
Joshua
Joshua is a statistical machine translation toolkit
Joshua has been incubating since 2016-02-13.
The INFRA bootstrap ticket has been opened[1], and the PPMC and INFRA
are active in working through the setup tasks.
No concerns for the board at this time.
[1] (https://issues.apache.org/jira/browse/INFRA-11264)
Signed-off-by:
[ ](joshua) Paul Ramirez
[X](joshua) Lewis John McGibbney
[X](joshua) Chris Mattmann
[ ](joshua) Tom Barber
[X](joshua) Henri Yandell
Shepherd/Mentor notes:
johndament: Report contents are very sparse. All sections
should be retained.
--------------------
Kudu
Kudu is a distributed columnar storage engine built for the Apache Hadoop
ecosystem.
Kudu has been incubating since 2015-12-03.
Three most important issues to address in the move towards graduation:
1. Build a more diverse developer and user community
2. Migrate our web site under apache.org
3. Continue to make regular Apache 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?
- In February, we only received one patch from a new contributor (3 total
from non-committers). We're continuing to focus on building a more
diverse developer community.
Although recruiting new contributors to Kudu itself have been slow, we
had community members report beginnings of a Presto integration, an
Apache Flume sink, and Rust language bindings. We are considering
whether it makes sense to develop these things within the Kudu project
or external locations.
- Overall development velocity continues to be pretty good: 94 patches
committed since the last report, representing about 3.5kloc of new code
and 4kloc of changes. This is slightly down from last month, as we
spent a bit more time on managing our first release and fixing bugs
rather than adding new features.
Dev list traffic is similar to January (1032 messages vs 1144 in Jan).
- Community members continue to give public talks about Kudu at various
conferences and meetups. Talks were delivered at conferences or meetups
in Tokyo (x2), Sunnyvale, Krakow, San Francisco (x2), and Seattle. More
are planned for March.
We are also encouraged that at least two Kudu meetup talks were
delivered by new members of the community outside the core development
team. We hope to see the "grassroots community" trend continue.
- The public Kudu Slack channel continues to be popular. It has grown from
116 members last month to 150 this month. Discussion between users and
devs is quite active, with daily participation from a global community
(USA, China, Poland, Japan, et al). Many users seem to prefer this
method over the traditional user mailing list.
How has the project developed since the last report?
Since the last report, we've accomplished the following milestones:
- We successfully migrated our issue tracking to the Apache JIRA. Special
thanks to Gavin on the infra team and Mike Percy on the Kudu project for
hard work on this transition.
- We cleaned up our license documentation and successfully published our
first official release as an incubating project (0.7.0)!
Date of last release:
Feb 25, 2016: Apache Kudu 0.7.0-incubating
When were the last committers or PMC members elected?
None since initial incubation.
Signed-off-by:
[ ](kudu) Jake Farrell
[ ](kudu) Brock Noland
[X](kudu) Michael Stack
[ ](kudu) Jarek Jarcec Cecho
[X](kudu) Chris Mattmann
[X](kudu) Julien Le Dem
[ ](kudu) Carl Steinbach
Shepherd/Mentor notes:
KUDU is very active. We need to get our website done and branded
as an Incubator and eventually TLP site. Good progress.
--------------------
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
2. Activate some community
3.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
There's an ongoing discussion to move the project to attic unless it is
able to release in the next few months.
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?
After the discussion about the activity of the project and the success of
the incubation process, there's currently a member willing to step through
the release process. The initial plan on incubation anyway was to primary
apply available patches and release those bug fixes.
Additionally, there's once more a discussion about the supported build
platforms, because currently the project heavily focusses on cpptasks,
which is not maintained and simply doesn't support current versions of all
formerly supported IDEs anymore. The current focus is on dropping
cpptasks and ANT for the build of the software and use autoconf and/or
cmake instead.
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) Ralph Goers
--------------------
Metron
Metron integrates a variety of open source big data technologies in order to
offer a centralized tool for security monitoring and analysis. Metron
provides capabilities for log aggregation, full packet capture indexing,
storage, advanced behavioral analytics and data enrichment, while applying
the most current threat-intelligence information to security telemetry
within a single platform.
Metron has been incubating since 12-08-2015
Three most important issues to address in the move towards
Graduation:
- Building a diverse community of developers for Metron
- Getting security practitioners to provide feedback on requirements
- Make an Apache release
Any issues that the Incubator PMC or ASF Board might wish/need to be
aware of?
- We are currently trying to produce the first Apache release of Metron
- We would like to request Apache infrastructure (a Jenkins server) for CI
How has the community developed since the last report?
- We voted to add one additional committer, Nick Allen
How has the project developed since the last report?
- We closed on 15 more Jiras and made our code base more compliant with
Apache Licenses. We are at the latest stages of cleaning up the code
base to come up with the Apache build.
Signed-off-by:
[X](metron) Billie Rinaldi
[ ](metron) Chris Mattmann
[ ](metron) Owen O'Malley
[X](metron) P. Taylor Goetz
[ ](metron) Vinod Kumar Vavilapalli
--------------------
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. Import main project repos
2. Work towards our first release
3. Broaden the community
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
The Initial Committer list is being revised (see below).
How has the community developed since the last report?
We have identified shortcomings in the Initial Committer list, and adopted
a fast-track process to add new members, valid for the project's first
three months (until March 20th). We have welcomed our first genuinely new
committer and are inviting another. Initial committers are familiarising
with Apache.
How has the project developed since the last report?
Both companies MIRACL and NTT are now readying their initial contributions
into the Milagro repositories.
Date of last release:
n/a
When were the last committers or PMC members elected?
We have no distinction between committers and PMC.
The following have accepted invitations during the period:
Peter Scanlon
Tomasz Matecki
Anthony Shaw
Vladislav Mitov
Nikolai Stoilov
All except Anthony Shaw are Miracl employees, and should have been on the
Initial Committer list. We anticipate improving diversity soon.
Signed-off-by:
[ ](milagro) Sterling Hughes
[ ](milagro) Jan Willem Janssen
[x](milagro) Nick Kew
--------------------
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.
How has the project developed since the last report?
We have released our fourth release under Apache incubation. There were
various bug fixes and performance improvements before the release. The
most important new feature in the new release is support for incremental
query processing in MRQL streaming, called Incremental MRQL.
Date of last release:
2016-03-02
When were the last committers or PMC members elected?
2014-04-17
Signed-off-by:
[ ](mrql) Alan Cabrera
[x](mrql) Edward J. Yoon
[ ](mrql) Mohammad Nour El-Din
--------------------
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. Grow the Myriad user base.
2. Expand the contributor community.
3. Release Myriad 0.2.0 in April/May, with focus on multitenancy,
security, and oversubscription.
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?
- Mailing list traffic went into a holiday lull after the 0.1.0 release.
Should pick up again as we plan the 0.2.0 release.
http://mail-archives.apache.org/mod_mbox/incubator-myriad-dev/
- Our biweekly community syncs still get 6-12 participants, including new
participants from Accenture. See minutes at: http://s.apache.org/8kF
- Freenode #myriad IRC channel has been mostly quiet since the 0.1.0
release, except for an occasional user question or discussion around a
community sync. Chatter should pick up again leading up to the 0.2.0
release, and moreso after we get a few more users. Archived by ASFBot
at: http://wilderness.apache.org/channels/#logs-#myriad
- Website and wiki were updated with the 0.1.0 release.
http://myriad.incubator.apache.org
- Presented at DockerConEU. Submitted talks for ApacheCon, MesosCon,
Hadoop Summit, Container World.
How has the project developed since the last report?
- Resolved 6 JIRAs and merged 6 PRs since Dec 2, 2015.
Date of last release:
2015-12-10 myriad-0.1.0-incubating
When were the last committers or PMC members elected?
2015-10-05 Darin J
2015-10-14 Swapnil Daingade
In the process of nominating the next committer.
Signed-off-by:
[ ](myriad) Benjamin Hindman
[ ](myriad) Danese Cooper
[x](myriad) Ted Dunning
[x](myriad) Luciano Resende
--------------------
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. Grow the community
2. Elect new PMC members
3. Release more often
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?
Mailing list activity (December 2015 - February 2016):
* @dev: 114 messages
Jira issues backlog (December 2015 - February 2016):
* Created: 7
* Resolved: 4
We have a number of new users showing up on the mailing list, which is
encouraging.
How has the project developed since the last report?
The community has decided to drop support for S4, which is now inactive.
There is also some continued interest by Apache Apex about a possible
integration. Internally, we have been working on strengthening our main
classifier (VHT). There has also been work on improving the connection
with Avro and Kafka. The adapted for Flink has been updated to the latest
stable version (0.10).
Date of last release:
2015-07-21
When were the last committers or PMC members elected?
None
Signed-off-by:
[X](samoa) Alan Gates
[ ](samoa) Ashutosh Chauhan
[ ](samoa) Enis Soztutar
[X](samoa) Ted Dunning
Shepherd/Mentor notes:
--------------------
Sentry
Sentry is a highly modular system for providing fine grained role based
authorization to both data and metadata stored on an Apache Hadoop cluster.
Sentry has been incubating since 2013-08-08.
Three most important issues to address in the move towards graduation:
1.Graduation vote has been passed, see below for details.
2.
3.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
1. Graduation vote has been passed and the resolution has been proposed to
the board for consideration in the board meeting.
References:
https://s.apache.org/dev_discuss
https://s.apache.org/dev_vote_result
https://s.apache.org/general_discuss
https://s.apache.org/Incubator_vote
Other:
https://s.apache.org/general_notify
https://s.apache.org/8rty (Maturity Model assessment)
2. Olivier Lamy resigned as a mentor.
How has the community developed since the last report?
1. We had ~500 messages on dev list in the past three months. (Got number
from http://markmail.org/list/org.apache.sentry.dev)
2. Community is continuing to do monthly hangouts.
How has the project developed since the last report?
About 131 issues were created and about 87 resolved in the past 3
months(Numbers from jira).
Date of last release:
2015-09-22, preparing for 1.7.0 release
When were the last committers or PMC members elected?
Hao Hao was added as committer on 01/29/2016. On 2015-12-21, community
voted to make Committer == PPMC.
Signed-off-by:
[X](sentry) Arvind Prabhakar
[ ](sentry) Joe Brockmeier
[ ](sentry) David Nalley
[X](sentry) Patrick Hunt
[X](sentry) Thomas White
--------------------
Singa
Singa is a distributed deep learning platform.
Singa has been incubating since 2015-03-17.
Three most important issues to address in the move towards graduation:
1. Improve the system, including performance and features like distributed
GPU training over GPU clusters, R binding, etc.
2. Add more examples and documentation to attach users
3. Grow the community. We have been trying to reach out to a more diverse
community of developers and users by presenting SINGA for various
audiences. Completing items 1 and 2 above would attract more
contributors and users.
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 Github repository has scored 540 stars and 190 forks.
There were 60, 180 and 7 commits in Dec 2015, Jan 2016 and Feb 2016
respectively.
There were 77, 105, 13 emails from dev@ list in Dec 2015, Jan 2016 and Feb
2016 respectively.
How has the project developed since the last report?
In Jan 2016, we released our second version, i.e., incubating-v0.2.0, with
the following major features:
* GPU support, which enables training of complex models on a single node
with multiple GPU cards.
* Hybrid neural net partitioning, which supports data and model
parallelism at the same time.
* Python wrapper, which makes it easy to configure the job, including
neural net and SGD algorithm.
* RNN model and BPTT algorithms, to support applications based on RNN
models, e.g., GRU.
* Cloud software integration includes Mesos, Docker and HDFS.
Date of last release:
2016-01-14
When were the last committers or PMC members elected?
N/A
Signed-off-by:
[ ](singa) Daniel Dai
[X](singa) Alan Gates
[X](singa) Ted Dunning
[ ](singa) Thejas Nair
--------------------
Streams
Apache Streams (incubating) unifies a diverse world of digital profiles
and online activities into common formats and vocabularies, and makes
these datasets accessible across a variety of databases, devices,
and platforms for streaming, browsing, search, sharing, and analytics use-cases.
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 has remained
low this quarter.
How has the community developed since the last report?
no demonstrable progress in community growth.
How has the project developed since the last report?
5 issues created / 1 resolved this quarter
at mentors suggestion, this quarter the project focused on
documenting project purpose, philosophies, place in ecosystem,
how to get started, etc... as part of a web site overhaul.
the new version is hosted at streams.staging.apache.org and will go
live at streams.incubator.apache.org soon.
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
[X](streams) Ate Douma
[ ](streams) Craig McClanahan
--------------------
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. Community growth
2. Release more of the imported code to create engagement
3. Move to a sustainable development pattern
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
Our mentors have reported they have little or no time
available as Taverna is picking up pace.
Dan Debrunner volunteered from the incubator list and
became a new mentor.
How has the community developed since the last report?
Welcomed new PPMC member.
GSOC 2016 project ideas are already getting interest.
dev@taverna mailing lists stats:
Dec 2015: 42
Jan 2016: 128
Feb 2016: 325
users@taverna:
Dec 2015: 2
Jan 2016: 0
Feb 2016: 2
JIRA issues over last 90 days:
50 created
32 resolved
How has the project developed since the last report?
Good buzz around release preparation, release candidate currently
under vote.
Date of last release:
2015-08-11 taverna-language-0.15.0-incubating
(new release currently under vote)
When were the last committers or PMC members elected?
2015-12-04
Signed-off-by:
[x](taverna) Andy Seaborne
[X](taverna) Chris Mattmann
[ ](taverna) Suresh Srinivas
[X](taverna) Suresh Marru
[X](taverna) Marlon Pierce
[ ](taverna) Dan Debrunner
Shepherd/Mentor notes:
Andy:: It would be good to have a second active mentor in addition to Dan.
Chris: I have to retire as a Taverna mentor. That said - what's stopping
Taverna from being ready to graduate? If it's just mentor activity then
consider graduating. The community looks active, looks like it's releasing,
looks like involved in GSoC, etc.
--------------------
Toree
Toree provides applications with a mechanism to interactively and remotely
access Apache Spark. It enables interactive workloads between applications
and a Spark cluster. As a Jupyter Notebook extension, it provides the user
with a preconfigured environment for interacting with Spark using Scala,
Python, R or SQL.
Toree has been incubating since 2015-12-02.
Three most important issues to address in the move towards graduation:
1. Removal of LGPL dependency
2. Ease of installation
3. Documentation of APIs
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
TOREE-262 - Progress on removal of LGPL dependency
How has the community developed since the last report?
1. Work with Jupyter community to update their docker stacks to include
the latest Toree
2. Blog post at http://www.spark.tc/announcing-apache-toree/ to announce
the incubation
3. Active communication in mailing list and gitter with early adopters
4. Work with Brunel project
(https://github.com/Brunel-Visualization/Brunel) to make technology
available on Toree
5. Still working on transitioning users from Spark Kernel project into
Toree.
How has the project developed since the last report?
1. Source package have been renamed to org.apache.toree
2. All original contributors are not actively developing and fixing issues
on the apache project
3. Project can be published and installed through Pypi (only snapshot/dev
packaged made available for testing)
4. Added a plug-in framework to enable integration of 3rd party code to
add capabilities
5. Create Spark Streaming example notebook to feature many of the
capabilities of Toree in collaboration with Jupyter ecosystem
(dashboards and widgets)
6. Misc bug fixes and features
7. Actively working with JeroMQ community to further their transition into
MPL v2 and away from LGPL.
Date of last release:
None since incubation.
When were the last committers or PMC members elected?
No new additions since incubation
Signed-off-by:
[x](toree) Luciano Resende
[ ](toree) Reynold Xin
[X](toree) Hitesh Shah
[X](toree) Julien Le Dem
Mentor notes:
lresende has started discussion with polling about what
should be priorities before graduation.
--------------------
Trafodion
Trafodion is a webscale SQL-on-Hadoop solution enabling transactional or
operational workloads on Hadoop.
Trafodion has been incubating since 2015-05-24.
Three most important issues to address in the move towards graduation:
1. Develop community and bring in more diverse contributors.
2. Work on our second release, including convenience binaries and
support for Apache HBase 1.x without a commercial distribution.
3. Continue the momentum and become more integrated with the
rest of the Apache community.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
* Lars Hofhansl and Andrew Purtell resigned as mentors.
How has the community developed since the last report?
* Participation in public lists has been increasing:
809 messages in the codereview forum, 1051@commits,
561@dev, 1377@issues and 320@user.
* Steve Varnau has agreed to be the release manager for
our next release.
* A logo for Apache Trafodion was adopted by vote in February.
How has the project developed since the last report?
* Completed our first release in incubation, Trafodion 1.3.0,
on Jan 11, 2016. Many thanks go to Roberta Marton, the release manager.
See http://trafodion.apache.org/release-notes-1-3-0.html for details.
* Completely redesigned the web page, http://trafodion.apache.org
and moved content from the wiki to the site, following the example
of other Apache projects.
* Published documentation in form of HTML and PDF manuals.
* 287 commits from 23 contributors.
* 200 JIRAs filed and 139 resolved in the last three months.
Date of last release:
2016-01-11
When were the last committers or PMC members elected?
RuoYu Zuo was announced as a new committer in February.
The last PMC members were announced in November 2015.
In both cases the election happened a few weeks earlier
but it took some time to get the necessary karma.
Signed-off-by:
[ ](trafodion) Devaraj Das
[ ](trafodion) Enis Söztutar
[x](trafodion) Michael Stack
--------------------
Zeppelin
A collaborative data analytics and visualization 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. Prove PPMC's maturity by handling dispute in community gracefully
2. Community growth: more committers from different organizations
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
Updating long term roadmap [1] to embrace community needs is in
discussion.
[1] https://s.apache.org/Ksgm
How has the community developed since the last report?
Traffic in users@ and dev@ grew: +38 subscribers in @dev, +83 subscribers
in users@ since last report.
Talks at several conferences are scheduled [2].
[2] https://cwiki.apache.org/confluence/display/ZEPPELIN/Community
How has the project developed since the last report?
209 patches have been merged from 42 different contributors since last
report.
Integration to JDBC, Apache HBase, Elasticsearch, Scalding, Tachyon has
been added.
Authentication and notebook authorization have implemented.
Date of last release:
2016-01-22
When were the last committers or PMC members elected?
2016-01-16
Signed-off-by:
[ ](zeppelin) Konstantin Boudnik
[X](zeppelin) Henry Saputra
[X](zeppelin) Roman Shaposhnik
[X](zeppelin) Ted Dunning
[ ](zeppelin) Hyunsik Choi
-----------------------------------------
Attachment AI: Report from the Apache Jackrabbit Project [Michael Dürig]
## Description:
The Apache Jackrabbit™ content repository is a fully conforming
implementation of the Content Repository for Java™ Technology API
(JCR, specified in JSR 170 and 283).
## Issues:
There are no issues requiring board attention at this time
## Activity:
Apache Jackrabbit Oak receives most attention nowadays. All
maintenance branches and the unstable development branch are
continuously seeing high activity. The PMC is currently in the
process of voting on the next major release (1.4).
Apache Jackrabbit itself is mostly in maintenance mode with most of
the work going into bug fixing and tooling.
## PMC changes:
- Currently 48 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Vikas Saurabh on Fri Nov 06 2015
## Committer base changes:
- Currently 48 committers.
- No new committers added in the last 3 months
- Last committer addition was Vikas Saurabh at Wed Nov 04 2015
## Releases:
- Jackrabbit-2.12.0 was released on Tue Feb 09 2016
- Jackrabbit-2.12.1 was released on Fri Feb 26 2016
- Oak-1.0.26 was released on Tue Jan 19 2016
- Oak-1.0.27 was released on Tue Feb 09 2016
- Oak-1.0.28 was released on Wed Mar 02 2016
- Oak-1.2.10 was released on Wed Jan 20 2016
- Oak-1.2.11 was released on Wed Feb 10 2016
- Oak-1.2.12 was released on Wed Mar 02 2016
- Oak-1.3.13 was released on Mon Jan 04 2016
- Oak-1.3.14 was released on Mon Jan 18 2016
- Oak-1.3.15 was released on Wed Feb 03 2016
- Oak-1.3.16 was released on Tue Feb 16 2016
- Oak-1.4 was released on Wed Mar 02 2016
- Vault-3.1.26 was released on Sat Jan 09 2016
## JIRA activity:
- 374 JIRA tickets created in the last 3 months
- 369 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AJ: Report from the Apache Karaf Project [Jean-Baptiste Onofré]
Apache Karaf provides a very modern and polymorphic container, multi-purpose
(microservices, OSGi, etc) powered by OSGi.
Community
=========
A completely brand new website has been promoted and announced. We are now
working on the polishing of the documentation.
Two new committers have been elected:
- Andrea Cosentino was added as a committer on Thu Jan 21 2016
- Fabian Lange was added as a committer on Sun Jan 10 2016
Last committer addition: Janueray 21, 2016
Last PMC addition: September 05, 2012
Several talks will stand at next ApacheCon:
- Tutorial: Apache Karaf and OSGi Basics - Tom Barber
- Messaging for the cloud with ActiveMQ and Karaf - Hadrian Zbarcea & Jamie
Goodyear
- Focus on business code with Apache Karaf Boot - Jean-Baptiste Onofré
- Monitoring and alerting with Apache Karaf Decanter - Jean-Baptiste Onofré
Messages on the dev mailing list (September, October, November): 510
Messages on the user mailing list (September, October, November): 101
Development
===========
The following new releases have been voted:
- 2.3.12 was released on Mon Jan 25 2016
- 2.4.4 was released on Mon Jan 25 2016
- 3.0.6 was released on Wed Feb 17 2016
- 4.0.4 was released on Thu Jan 14 2016
Jira activity:
- 224 JIRA tickets created in the last 3 months
- 178 JIRA tickets closed/resolved in the last 3 months
Issues for board consideration
==============================
None so far.
-----------------------------------------
Attachment AK: Report from the Apache Labs Project [Jan Iversen]
## Description
Apache Labs hosts small and emerging projects from ASF committers.
## Activity
Another typical quiet couple months for Labs. The PMC remains quiet
and healthy.
## Issues
None
## PMC/Committership changes:
- Currently 31 committers and 11 PMC members in the project.
- Last PMC addition was Jan Iversen at Sat Feb 15 2014
- Last committer addition was Jan Iversen at Thu Feb 27 2014
## Releases
The project does not make releases per definition.
-----------------------------------------
Attachment AL: Report from the Apache Lucene Project [Michael McCandless]
## Description:
- Lucene Core is a search-engine toolkit
- Solr is a search server built on top of Lucene Core
## Activity:
- The community is very active
## Issues:
- To follow up on the Subversion to GIT cutover from the last
report: after a long tail of many small issues, it has gone
smoothly, thanks to heavy efforts on Dawid Weiss' part to preserve
our elaborate source control history. We did our first release
(5.5.0) based on GIT and that also seems to have gone well.
- There are no new issues requiring board attention at this time
## PMC/Committership changes:
- Currently 59 committers and 38 PMC members in the project
- Added no new committers
- Added 1 new PMC member:
Cassandra Targett on Mon Dec 21 2015
## Releases:
- 5.4.0 was released on December 14, 2015
- 5.3.2 was released on January 23
- 5.5.0 was released on February 22, our first release based on GIT
- 6.0.0 will release shortly: we have a branch, and are aggressively
fixing nasty bugs that early adopter testing is uncovering
## Mailing list activity:
- dev@lucene.apache.org:
- 839 subscribers (down -6 in the last 3 months):
- 11966 emails sent to list (8214 in previous quarter)
- c-commits@lucene.apache.org:
- 18 subscribers (up 0 in the last 3 months):
- 0 emails sent to list (0 in previous quarter)
- c-dev@lucene.apache.org:
- 73 subscribers (down -7 in the last 3 months):
- 0 emails sent to list (2 in previous quarter)
- general@lucene.apache.org:
- 1006 subscribers (up 15 in the last 3 months):
- 40 emails sent to list (28 in previous quarter)
- java-commits@lucene.apache.org:
- 96 subscribers (up 0 in the last 3 months):
- 0 emails sent to list (0 in previous quarter)
- java-user@lucene.apache.org:
- 1099 subscribers (down -3 in the last 3 months):
- 243 emails sent to list (323 in previous quarter)
- pylucene-commits@lucene.apache.org:
- 10 subscribers (up 0 in the last 3 months):
- 1 emails sent to list (1 in previous quarter)
- pylucene-dev@lucene.apache.org:
- 126 subscribers (up 2 in the last 3 months):
- 2 emails sent to list (23 in previous quarter)
- ruby-dev@lucene.apache.org:
- 62 subscribers (down -7 in the last 3 months):
- 0 emails sent to list (2 in previous quarter)
- solr-commits@lucene.apache.org:
- 96 subscribers (up 1 in the last 3 months):
- 0 emails sent to list (0 in previous quarter)
- solr-user@lucene.apache.org:
- 3520 subscribers (up 4 in the last 3 months):
- 3174 emails sent to list (2959 in previous quarter)
## JIRA activity:
- 587 JIRA tickets created in the last 3 months
- 453 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AM: Report from the Apache Lucene.Net Project [Prescott Nasser]
-----------------------------------------
Attachment AN: Report from the Apache MRUnit Project [Brock Noland]
-----------------------------------------
Attachment AO: Report from the Apache OFBiz Project [Jacopo Cappellato]
## Description:
Apache OFBiz is an open source enterprise automation software project
## Issues:
there are no issues requiring board attention at this time
## Activity:
- new features, improvements and bug fixes have been contributed
and integrated into the official code base
- the community is active and friendly: there are discussions in the mailing
lists, community days (days in which contributors virtually meet and
work together at resolving as many tickets as possible) and activity
in Jira and Confluence
- the community is trying to define a roadmap for the refactoring
of the framework following an evolutionary step-by-step approach;
the framework represents a large portion of the OFBiz codebase and
some parts of it are rather old and may benefit from a renewal/upgrade;
since the framework is used by several applications, the
community is trying to find a way to minimize the impact on them
- the activity in the official blog and Twitter accounts is steady
and we have started to publish some videos on our official youtube
channel
- also this year the OFBiz project will be represented at ApacheCon:
in fact some OFBiz related presentations have been accepted
- we have some pending CVEs that we have partially addressed and we
are trying to finalize as soon as possible; for this reason we have
delayed our release dates but we are trying to complete this work in
the next few weeks
- finally, the sad news that shook our community:
on 1st January 2016, OFBiz Committer, former PMC member and friend
Adrian Crum passed away. Adrian joined the OFBiz project
during the incubation phase and in 2007 was invited to
become a committer. Later that year Adrian joined the
OFBiz PMC and participated until June 2014. Over the years
Adrian contributed around 5,000 postings to the mailing lists,
over 2,300 issues and comments to issues and over 2,000 commits.
The project has setup a memorial page for the community to
share their stories, and experiences of Adrian and the community
has also decided to dedicate our next OFBiz release to him.
## Health report:
the project seems to be in an healthy phase: medium traffic in the
mailing lists, good and friendly communication and collaboration; the
committers group is slowly growing; we are behind of our schedule on
releases because we are slowly progressing at making our system more
secure in its default configuration (once completed, this work will
address the CVEs reported)
## PMC changes:
- Currently 15 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Nicolas Malin on Mon Mar 23 2015
## Committer base changes:
- Currently 40 committers.
- Gregory Draperi was added as a committer on Mon Mar 07 2016
## Releases:
- Last release was 13.07.02 on Sat May 23 2015
- late schedule, upcoming releases
## Mailing list activity:
mailing list activity has been steady (in terms of number of
subscribers and number of emails) and similar to the ones in
previous quarters
## JIRA activity:
- 165 JIRA tickets created in the last 3 months
- 142 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AP: Report from the Apache Olingo Project [Christian Amend]
=== General ===
## Description:
Apache Olingo is a Java and JavaScript library that implements the Open
Data Protocol (OData). Apache Olingo serves client and server aspects of
OData. It currently supports OData 2.0 and OData 4.0. The latter is
the OASIS version of the protocol: OASIS Open Data Protocol (OData) TC.
## Olingo Status
Currently Olingo has no issues that would require board attention.
Based on the new release process the community provided the first minor release
with version 4.1.0 on December 21st, 2016. The next minor V4 release is
scheduled to be released at the end of march.
Additionally we provided a new patch release for the OData V2 code line on
January 29th, 2016.
Most of the work in the Olingo community is done in the OData V4 code line. We
saw an increasing number of JIRA issues form users of the library that also
contribute bug fixes in the form of patches. The number of questions on the
user mailing list seems to be constant with a mix of new and already known
users. All in all the project is healthy but would certainly benefit from
more regular contributors.
An initiative towards an easier API on the basis of JPA annotations was
discussed by users on the users mailing list but did not lead to any
contributions. As an experiment a repository was created at GitHub for easier
access from non Apache committers. The idea was to give the users a repository
they can work in without having to go through Apache processes in the beginning.
The eventual goal would have been to integrate the GitHub code into the Olingo
project once a certain maturity has been achieved. If there are any updates in
this direction I will include them within the next board report.
=== Statistics ===
## PMC changes:
- Currently 13 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Ramesh Reddy on Thu Oct 08 2015
## Committer base changes:
- Currently 23 committers.
- No new committers added in the last 3 months
- Last committer addition was Christian Holzer at Thu Feb 26 2015
## Releases:
- 4.1.0 was released on Mon Dec 21 2015
- V2 2.0.6 was released on Fri Jan 29 2016
## Mailing list activity:
- dev@olingo.apache.org:
- 78 subscribers (up 1 in the last 3 months):
- 489 emails sent to list (413 in previous quarter)
- user@olingo.apache.org:
- 133 subscribers (up 8 in the last 3 months):
- 167 emails sent to list (185 in previous quarter)
## JIRA activity:
- 63 JIRA tickets created in the last 3 months
- 69 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AQ: Report from the Apache OODT Project [Tom Barber]
DESCRIPTION
Apache OODT is a software framework as well as an architectural style for the
rapid construction of scientific data systems. It provides components for
data capture, curation, metadata extraction, workflow management, resource
management, and data processing.
RELEASES/DEVELOPMENT
- Last release was 0.12 on Feb 19th 2016
We resolved 4 issues for this release.
0.12 was a out of band release for OODT initially the scope was an emergency
patch for an API issue, but in preparing for the release we also addressed 3
major issues relating to the the Solr integration for OODT.
We have decided to switch to a rough quarterly release schedule to help keep
the code active and make sure that commits that get pushed to the project get
released in a timely manner, which will give contributors more confidence
about when their patches will end up in the stable codebase.
February was a busy month on the mailing list with a number of new users
showing up and triggering the Solr patches and general questions about OODT
usage.
The project is specific in its design but we have been working on advertising
to a larger crowd for less scientific based data management to draw a larger
audience and userbase.
At ApacheCon we have 1 presentation and 2 tutorials scheduled for Apache OODT
which we hope will drive awareness to wider audiences.
As ever it would be nice to see fresh blood on the project helping to increase
the development effort on the platform, but the software itself is stable and
well used.
COMMUNITY
Latest committers and PMC members
Radu Maonle(radumanole) on 28 Oct 2015 as committer and PMC member
Last committer and PMC member added on 28th October 2015.
-----------------------------------------
Attachment AR: Report from the Apache OpenNLP Project [Jörn Kottmann]
The Apache OpenNLP library is a machine learning based toolkit for the
processing of natural language text. It supports the most common NLP
tasks, such as tokenization, sentence segmentation, part-of-speech
tagging, named entity extraction, chunking, parsing, and coreference
resolution. These tasks are usually required to build more advanced text
processing services.
Development
------------------
The development team stayed active but with less activity. A language
model component was added and a few smaller bugs were fixed.
At the current pace we will probably finish the next minor
release before the next board report.
Community
---------------
The community stayed active with the usual amount of traffic on the user
mailing list and contributed a couple of patches to fix bugs.
Rodrigo Agerri was added to the PMC on Jul 09 2015
Mondher Bouazizi and Anthony Beylerian were added as a committer on
Fri Sep 04 2015.
Releases
------------
The last release OpenNLP 1.6.0 was released on Jul 09 2015.
Issues
--------
There are no board-level issues at this time.
-----------------------------------------
Attachment AS: Report from the Apache OpenWebBeans Project [Mark Struberg]
## Description:
Apache OpenWebBeans is an ALv2-licensed implementations of the
"Contexts and Dependency Injection for the Java EE platform"
specification which is defined as JSR-299 (CDI-1.0) and CDI-1.1
and CDI-1.2 (MR) specifications (JSR-346).
## Issues:
There are no issues requiring board attention at this time
## Activity:
Activity is fine. We did start with CDI-2.0 and are actively fixing and
enhancing the existing mainline.
A few OWB committers are actively contributing to the ALv2 licensed
CDI-2.0 specification. We also already incorporated a few of those
changes to the existing mainline (if changes are API compatible).
## Health report:
The project is a container library which is stable and actively
used and maintained. Due to the fact that most users are using
OWB as part of another project (e.g. TomEE) we get much feedback
in ‚indirect‘ ways.
## PMC changes:
- Currently 12 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Thomas Andraschko on Wed May 28 2014
## Committer base changes:
- Currently 19 committers.
- No new committers added in the last 3 months
- Last committer addition was Reinhard Sandtner at Fri Sep 26 2014
## Releases:
- Last release was 1.6.3 on 2016-02-20
## Mailing list activity:
- dev@openwebbeans.apache.org:
- 67 subscribers (up 0 in the last 3 months):
- 190 emails sent to list (98 in previous quarter)
- user@openwebbeans.apache.org:
- 91 subscribers (up 0 in the last 3 months):
- 18 emails sent to list (8 in previous quarter)
## JIRA activity:
- 22 JIRA tickets created in the last 3 months
- 20 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AT: Report from the Apache Perl Project [Philippe M. Chiasson]
-- mod_perl 1.0 --
The mod_perl 1.x is a maintenance track designed to work with httpd
1.3.x.
No new mod_perl 1.x releases since 2014-12.
--- mod_perl 2.0 --
mod_perl 2.X is designed to work with all httpd 2.X branches.
Following Steve Hay's release of mod_perl 2.0.9, there has been an increase
in interest and activity.
Major Linux distros were quick at picking it up as well, so it should be
making its way to a lot of users.
--- Apache-Test --
Apache-Test provides a framework which allows module writers to write
test suites that can query a running mod_perl enabled server. It is
used by mod_perl, httpd and several third party applications, and
includes support for Apache modules written in C, mod_perl, PHP
and Parrot.
Apache-Test 1.39 was released on Apr 21, 2015
No new Apache-Test releases since 2015-11.
--- Apache-SizeLimit --
Apache-SizeLimit is a popular component in most mod_perl production
environments. It is used to kill off large httpd child processes
based on various environmental triggers.
Apache-SizeLimit 0.97 was released on Apr 02, 2012
No new Apache-SizeLimit releases since 2015-11.
--- Apache-Bootstrap --
Apache-Bootstrap is a framework to make it easier to build perl
module distributions for different mod_perl versions. It encapsulates
code developed over the years by mod_perl developers to make
maintaining Apache::* and Apache2::* modules in the same distribution easy.
Apache-Bootstrap 0.07 was released on Jul 13, 2009
No new Apache-Bootstrap releases since 2015-11.
--- Apache-Reload --
Apache-Reload is a popular component in most mod_perl development
environments, used to refresh compiled code in the perl interpreter
without completely restarting httpd.
Apache-Reload 0.13 was released on May 09, 2015
No new Apache-Reloase releases since 2015-11.
-- Apache-DBI --
Apache-DBI is a popular component in many mod_perl deployments. It
is used to provide transparent database connection pooling to clients
using DBI.
Apache-DBI 1.12 was released on June 12nd, 2013
No new Apache-DBI releases since 2015-11.
-- Development --
mod_perl continues to be a healthy development community, though
as a mature and stable product development moves at a naturally
slower pace than in years past. Bugs are found and discussed and
fixes are applied with due consideration for our production userbase.
The 2.0.9 release has caused some more healthy activity, and development
is continuing.
-- Users --
The mod_perl users list is seeing little activity, with a bump in activity
following the 2.0.9 RCs and the final release.
Patches and bug reports are few, but keep on coming.
-- PMC --
No noteworthy PMC events happened since the last report.
The PMC has currently 11 members
-----------------------------------------
Attachment AU: Report from the Apache Pig Project [Rohini Palaniswamy]
## Description:
Apache Pig is a platform for analyzing large data sets on Hadoop. It
provides a high-level language for expressing data analysis programs,
coupled with infrastructure for evaluating these programs.
## Issues:
- There are no issues requiring board attention at this time
## Activity:
- Pig 0.16 which is a stabilization release for Pig on Tez will be targeted
for end of May as there are still bugs being reported and fixed. Pig
0.15.1 patch release is planned for early April to address critical
issues.
- Pig on Spark development is still under way in the spark branch
## Health report:
- Project activity in the community - mails, commits, jiras, etc is good and
is at the same levels as previous few quarters.
## PMC changes:
- The Pig PMC has voted for a new PMC chair candidate - Daniel Dai
- Currently 16 PMC members.
- Xuefu Zhang was added to the PMC on Tue Feb 23 2016
## Committer base changes:
- Currently 28 committers.
- No new committers added in the last 3 months
- Last committer addition was Praveen Rachabattuni at Mon Sep 08 2014
## Releases:
- Last release was 0.15.0 on Fri Jun 05 2015
## Mailing list activity:
- dev@pig.apache.org:
- 421 subscribers (up 0 in the last 3 months):
- 861 emails sent to list (870 in previous quarter)
- user@pig.apache.org:
- 1173 subscribers (down -9 in the last 3 months):
- 112 emails sent to list (95 in previous quarter)
## JIRA activity:
- 67 JIRA tickets created in the last 3 months
- 65 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AV: Report from the Apache Pivot Project [Roger Whitcomb]
Description:
Apache Pivot is an open-source platform for building installable Internet
applications (IIAs). It combines the enhanced productivity and usability
features of a modern user interface toolkit with the robustness of the
Java platform.
Issues:
- I do not think there are any board-level issues with Pivot at this time.
- We may need to have a discussion about moving to the Attic *soon*, but
not right now.
Activity:
Since our last report there has been a downtick in mailing list activity
but not to historic lows, but there has been a slight uptick in the
meta-activity around the project:
- I have volunteered to possibly be a mentor for GSOC in conjunction
with Airavata.
- An emeritus PMC member has rejoined to help with votes and
administrative issues.
- Several new users have shown up.
- We are close to a new release with only one (known) issue to resolve.
- Rich Bowen published the podcast he did with me last year at the
feathercast.apache.org site.
Health report:
- I would say the project is borderline at the moment, but no worse than
last report (in fact, maybe a bit better).
- With the final death blow to Java applets coming in September with the
release of Java 9, the traditional market for Pivot will shrink
dramatically.
- I am still trying to work within the ASF and elsewhere to move
into new areas. This is an ongoing effort.
- But, even with some new users, there are no new candidates for
committership or PMC membership, which remains a big issue.
PMC changes:
- Currently 4 PMC members.
- Niclas Hedhman was added back to the PMC on Wed Jan 13 2016.
Committer base changes:
- Currently 9 committers, of whom 2 are currently active.
- No changes to the committer base since last report.
- Last committer addition Piotr Kołaczkowski (pkolaczk) was in
May 2012.
Releases:
- Last release was 2.0.4 on Mon May 19 2014.
Mailing list activity:
- We have several new mailing list subscribers corresponding to the
new users, although activity has been slower this last quarter.
- dev@pivot.apache.org:
- 61 subscribers (up 3 in the last 3 months)
- 55 emails sent to list (77 in previous quarter)
- user@pivot.apache.org:
- 175 subscribers (up 3 in the last 3 months)
- 28 emails sent to list (43 in previous quarter)
JIRA activity:
- JIRA activity is a bit slow, but at least one critical Java 8
issue was resolved, meaning the 2.0.5 release is closer now.
- 5 JIRA tickets created in the last 3 months.
- 2 JIRA tickets closed/resolved in the last 3 months.
-----------------------------------------
Attachment AW: Report from the Apache Portable Runtime (APR) Project [Jeff Trawick]
## Short version of report:
No releases, no committee/committer changes, modest other activity
(Same summary as for the December 2015 report)
## Description:
The Apache Portable Runtime (APR) project creates and maintains
software libraries that provide a predictable and consistent interface
to underlying platform-specific implementations. The sub-projects
which are released somewhat regularly are APR and APR-util. In addition,
the APR-iconv sub-project is commonly used but has not had a release
since 2007.
## Activity:
- Commit activity has been modest, though much higher than in the previous
two quarters even discounting copyright changes. This brought some small
features and compatibility with a newer OpenSSL version.
- Mailing list activity has been relatively low.
- Six unique bugs were opened during the reporting period, and eight had
followup (closure or discussion).
## Health report:
- This is a mature project, and most of its development activity is
driven by the needs of the same small number of applications that have
used it for many years. The project members are more than able to
meet the requirements that arise from that use.
- The needs of the small number of other users are not met very well;
bug reports languish and mailing list posters may not receive timely
responses. The amount of help provided is probably not sufficient
to serve as encouragement to potential new users of APR.
## Issues:
- There are no issues requiring board attention at this time.
## LDAP committee group/Committership changes:
- Currently 65 committers and 39 LDAP committee group members.
- No new LDAP committee group members added in the last 3 months
- Last LDAP committee group addition was Yann Ylavic at Wed May 13 2015
- No new committers added in the last 3 months
- Last committer addition was Christophe Jaillet at Sat Mar 14 2015
## Releases:
- No releases in this quarter
- APR 1.5.2, released April 29, 2015
- APR-util 1.5.4, released September 22, 2014
- APR-iconv 1.2.1, released November 26, 2007
## Mailing list activity:
- dev@apr.apache.org:
- 360 subscribers
- 86 emails sent to list (103 in previous quarter)
- commits@apr.apache.org:
- 74 subscribers
- 59 emails sent to list (9 in previous quarter)
-----------------------------------------
Attachment AX: Report from the Apache Portals Project [David Sean Taylor]
Apache Portals exists to promote the use of open source portal technology. We
intend to build freely available and interoperable portal software in order to
promote the use of this technology. With the Pluto project, we provide a
reference implementation for the Java portlet standard. The Jetspeed project is
a full feature enterprise open source portal. The Portals Applications project
is dedicated to providing robust, full-featured, commercial-quality, and freely
available portlet applications.
## Activity:
Apache Portals released 0 releases since the last report.
Apache Portals Jetspeed team is actively working on version 2.3.1 release with
Security CVE fixes
Only 3 issues remain open and we expect to release soon
Apache Portals Pluto team is actively implementing Pluto 3.0 to support to the
Portlet Spec 3.0
We are planning on releasing the Portlet Spec 3.0 by September 2016
## Issues:
We have no board-level issues at this time.
## PMC/Committership changes:
Removed PMC members per PMC member request:
8 Feb 2016 - Jeremy Ford
8 Feb 2016 - Carsten Ziegeler
Last Added PMC Members:
4 May 2015 - Randy Watler
Last Added Committers:
11 Dec 2014 Martin Scott Nicklous
11 Dec 2014 Neil Griffin
## Releases:
none
Last Releases
28 July 2015 - Apache Portals Jetspeed 2.3.0
30 May 2015 - Apache Portals Applications Demo 1.3
8 May 2015 - Apache Portals Web Content 2.0
8 May 2015 - Apache Portals Gems 1.2
-----------------------------------------
Attachment AY: Report from the Apache ServiceMix Project [Krzysztof Sobkowiak]
Apache ServiceMix is a flexible, open-source integration container that
unifies the features and functionality of Apache ActiveMQ, Camel, CXF and
Karaf to provide a complete, enterprise-ready ESB powered by OSGi.
Project Status
==============
The project focus of Apache ServiceMix is the assembly of the integration
container, the actual functionality is being maintained in related projects
like Apache Karaf, Apache CXF, Apache Camel and Apache ActiveMQ.
Activity on the mailing lists and in JIRA has been a bit slow over the year
change, but is picking up again now that we're planning to do new releases.
We had also some new contributions.
We have focused on providing users with latest and greatest technology and
worked on upgrade of Apache Karaf, ActiveMQ, Camel and CXF versions.
During the last period the last maintenance version 5.4.3 has been released.
We have decided to stop further development on the branch 5.4.x. We have also
released the stable releases 5.5.2, 5.5.3 and 6.0.2 and the new release 5.6.0
from the development branch. During this period 4 sets of OSGi bundles and new
Specs has been released too.
We have focused on the development of ServiceMix 7 and released the first
preview of 7.0.0 which is based on Karaf 4.0.0 and includes numerous new
features. We are working now towards a 7.0.0 release. We are fixing first
issues reported by users for the preview release. In the new period we are
going to focus on the further development and stability of ServiceMix 7 to be
able to provide the community the first stable release.
We do plan to keep our release schedule going with the 5.5.x, 5.6.x, 6.0.x and
6.1.x releases. We plan to keep a steady release schedule and keep up with new
fix releases of our dependency projects.
There are no outstanding issues requiring board attention.
Community
=========
Currently 49 committers and 22 PMC members in the project. No new PMC members
nor committers were added in the last 3 months. Last committer addition was
Wim Verreydt on July 05 2014. Last PMC addition was Krzysztof Sobkowiak on
July 05 2014.
Releases
========
- Apache ServiceMix Bundles 2015.11 on December 03 2015
- Apache ServiceMix 5.5.2 on December 17 2015
- Apache ServiceMix 6.0.2 on December 17 2015
- Apache ServiceMix Bundles 2015.12 on January 07 2016
- Apache ServiceMix Specs 2.6.0 on January 25 2016
- Apache ServiceMix Bundles 2016.01 on February 06 2016
- Apache ServiceMix 7.0.0.M1 on February 12 2016
- Apache ServiceMix Bundles on February 18 2016
- Apache ServiceMix 5.4.3 on February 21 2016
- Apache ServiceMix 5.5.3 on February 21 2016
- Apache ServiceMix 5.6.0 on February 21 2016
Mailing list activity
=====================
- users@servicemix.apache.org:
- 420 subscribers (up 4 in the last 3 months):
- 55 emails sent to list (86 in previous quarter)
- dev@servicemix.apache.org:
- 208 subscribers (up 3 in the last 3 months):
- 241 emails sent to list (168 in previous quarter)
- issues@servicemix.apache.org:
- 8 subscribers (up 1 in the last 3 months):
- 766 emails sent to list (483 in previous quarter)
- commits@servicemix.apache.org:
- 56 subscribers (up 2 in the last 3 months):
- 1018 emails sent to list (1415 in previous period)
JIRA activity
=============
- 140 JIRA tickets created in the last 3 months
- 127 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AZ: Report from the Apache Shiro Project [Les Hazlewood]
Apache Shiro is a powerful and flexible open-source application security
framework that cleanly handles authentication, authorization, enterprise
session management and cryptography.
We have no issues that require Board assistance at this time.
Releases:
- We released the 1.2.4 bugfix/point release on July 7th.
Community & Project:
- 2.x work has slowed as of late. The hope is to resume significant work when
possible. Cleanup needs to occur before final release candidates can go out.
- It was a priority since the last board report to move to Git. This has been
completed.
- Project is mostly stable and in maintenance/bugfix mode until a 2.0 release
can be made. No significant feature development is planned on 1.x.
Last committer voted in: Jérôme LELEU on 4 Aug 2015
Last PMC Member voted in: Brian Demers on 20 May 2013
-----------------------------------------
Attachment BA: Report from the Apache Sling Project [Carsten Ziegeler]
Apache Sling is an OSGI-based scriptable web framework that uses a Java Content
Repository, such as Apache Jackrabbit, to store and manage content.
There are no issues which require board attention at the moment.
Community
Good activity level overall, contributions from different people continue.
No new committers (last committers change was in March 2015 with three new
committers elected), no new PMC member (last PMC change was in October 2015
with one new PMC member elected).
Releases
Apache Sling Background Servlets Engine 1.0.6,
Apache Sling Background Servlets Integration Test 1.0.0 (March 2, 2016)
Apache Sling NoSQL Generic Resource Provider 1.1.0,
Couchbase Client 1.0.2, Couchbase Resource Provider 1.1.0,
MongoDB Resource Provider 1.1.0 (February 27th, 2016)
Apache Sling Resource Resolver 1.4.4,
Apache Sling Scripting Sightly Engine 1.0.14 (February 26th, 2016)
Apache Sling JCR Base 2.3.2 (February 23rd, 2016)
Apache Sling Internationalization Support (I18N) 2.4.6 (February 22nd, 2016)
Apache Sling Resource Resolver 1.4.2,
Apache Sling JCR Resource 2.7.2,
and Apache Sling Servlets Resolver 2.4.2 (February 19th, 2016)
Apache Sling JCR Installer 3.1.18 (February 15th, 2016)
Apache Sling Resource Merger 1.3.0 (February 14th, 2016)
Apache Sling Scripting Core 2.0.36 (February 12th, 2016)
Apache Sling Slingstart Maven Plugin 1.4.2 (February 11th, 2016)
Apache Sling API 2.11.0, Apache Sling Resource Resolver 1.4.0,
Apache Sling JCR Resource 2.7.0, Apache Sling Servlets Resolver 2.4.0,
Apache Sling Testing OSGi Mock 1.7.2, OSGi Mock 2.0.2, JCR Mock 1.1.12,
Sling Mock 1.6.2, ResourceResolver Mock 1.1.12,
Servlet Helpers 1.0.0 (February 8th, 2016)
Apache Sling Discovery Oak 1.2.6 (February 8th, 2016)
Apache Sling HApi 1.0.0 (February 5th, 2016)
Apache Sling XSS Protection API 1.0.8,
Apache Sling Scripting Sightly Engine 1.0.12 (February 2nd, 2016)
Apache Sling Discovery Commons 1.0.10,
Apache Sling Discovery Oak 1.2.4
and Apache Sling Testing Tools 1.0.12 (February 1st, 2016)
Apache Sling Thread Support 3.2.6 (January 25th, 2016)
Apache Sling Models Impl 1.2.6 (January 23st, 2016)
Apache Sling Testing Utilities 2.0.24 (January 21st, 2016)
Apache Sling Commons Metrics 1.0.0 (January 15th, 2016)
Apache Sling Scripting Sightly Engine 1.0.10,
Apache Sling Scripting Groovy 1.0.2 (January 12th, 2016)
Apache Sling Slingstart Maven Plugin 1.4.0,
and Apache Sling Commons OSGi 2.4.0,
Apache Sling Engine Implementation 2.4.6 (January 8th, 2016)
Apache Sling Scripting JavaScript 2.0.28 (January 8th, 2016)
Apache Sling JUnit Tests Teleporter 1.0.6,
Apache Sling JUnit Core 1.0.16 (January 3rd, 2016)
Apache Sling Settings 1.3.8, Apache Sling Launchpad Base 2.6.10,
Apache Sling Scripting JSP 2.1.8, Apache Sling Commons Threads 3.2.4,
Apache Sling Discovery Standalone 1.0.2,
and Apache Sling Parent POM 26 (January 3rd, 2016)
Apache Sling Provisioning Model 1.4.2 (December 28th, 2015)
Apache Sling Commons Scheduler 2.4.14,
Apache Sling Servlets GET 2.1.14 (December 21st, 2015)
Apache Sling Scripting Java 2.0.14 (December 20th, 2015)
Apache Sling Models Impl 1.2.4,
Sling Testing OSGi Mock 2.0.0,
Apache Sling Commons Scheduler 2.4.12 (December 14th, 2015)
Apache Sling Launchpad Base 2.6.8 (December 11th, 2015)
Documentation and infrastructure
Nothing to report
Project Branding is tracked in SLING-2696.
-----------------------------------------
Attachment BB: Report from the Apache SpamAssassin Project [Kevin A. McGrail]
-----------------------------------------
Attachment BC: Report from the Apache Stanbol Project [Fabian Christ]
Apache Stanbol provides a set of reusable components for semantic content
management.
The project has proceeded to work on a new release. Since the project
did not release anything for two years now, there are some things to
catch up in order to make the release process more easy to handle.
The project is discussing to invite new PMC members and will start
a vote for new members soon.
Subscribers on the dev list: 231
Last new committer was
Cristian Petroaca on May 7th, 2015
No new PMC member was elected since the graduation of Apache Stanbol on
Sep 19th, 2012.
Last stack release was:
Apache Stanbol 0.12 on Mar 2nd, 2014
Last component release was:
Apache Stanbol Partial Security Release RC2 on June 5th, 2014
org.apache.stanbol.commons.security.reactor-20140602
-----------------------------------------
Attachment BD: Report from the Apache Storm Project [P. Taylor Goetz]
## Description:
- Apache Storm is a distributed real-time computation system.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- Preparation for the 1.0 release is winding down, and we expect the release
to take place this month (March).
- We expect to release 0.10.1 in the same timeframe as the 1.0 release.
- Work toward the 2.0 release (move from Clojure to Java and incorporate
Alibaba JStorm code contribution) is progressing rapidly.
## Health report:
- Activity on the dev list and new JIRAs have continued to increase in
response to the 1.0 release and Clojure to Java migration.
- The 1.0 release will represent a major milestone for the project, with
many new features and performance improvements.
## PMC changes:
- Currently 28 PMC members.
- New PMC members:
- Sanket Chintapalli was added to the PMC on Mon Feb 01 2016
- Haohui Mai was added to the PMC on Sun Jan 03 2016
- Zhuo Liu was added to the PMC on Wed Dec 16 2015
## Committer base changes:
- Currently 29 committers.
- New commmitters:
- Sanket Chintapalli was added as a committer on Fri Jan 29 2016
- Haohui Mai was added as a committer on Mon Jan 04 2016
- Zhuo Liu was added as a committer on Mon Dec 14 2015
## Releases:
- Version 0.10.0 was released on Tue Nov 03 2015
## Mailing list activity:
- Activity on the dev and user lists is steady and the number of subscribers
continues to increase.
- Dev list activity has continued to increase in response to the 1.0 and 2.0
release and planning efforts.
- dev@storm.apache.org:
- 514 subscribers (up 11 in the last 3 months):
- 9342 emails sent to list (8039 in previous quarter)
- user@storm.apache.org:
- 1365 subscribers (up 32 in the last 3 months):
- 683 emails sent to list (790 in previous quarter)
## JIRA activity:
- 232 JIRA tickets created in the last 3 months
- 205 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment BE: Report from the Apache Synapse Project [Hiranya Jayathilaka]
-----------------------------------------
Attachment BF: Report from the Apache Tajo Project [Hyunsik Choi]
-----------------------------------------
Attachment BG: Report from the Apache Tiles Project [Mick Semb Wever]
## Description:
Apache Tiles is a free open-sourced templating framework for Java applications.
Based upon the Composite pattern it is built to simplify the development of user
interfaces.
## Activity:
Activity in the Tiles community remains slow, slowing down further from last
quarter. Questions and issues are still generally addressed quickly. Otherwise
the majority of traffic remains on StackExchange and within the Spring
community.
## Health report:
The Apache Tiles project has dropped to the "urgent action required!" health
status. The significant issues with the health status are the low traffic on
the mailing lists, the lack of a release (despite one being promised), and no
new committers over the past two years. The few active members are aware of
the state of the project and most of our attention goes toward keeping a
stable project still communicating with users and developers that have
questions. Little time goes toward trying to increase the project's momentum.
## Issues:
There are no issues requiring board attention at this time.
## Releases:
No releases were made this quarter.
## Mailing list activity:
Mailing list activity has been quiet this quarter.
- users@tiles.apache.org:
- 148 subscribers (down -1 in the last 3 months):
- 8 emails sent to list (14 in previous quarter)
- dev@tiles.apache.org:
- 34 subscribers (up 2 in the last 3 months):
- 1 emails sent to list (10 in previous quarter)
-----------------------------------------
Attachment BH: Report from the Apache Tomcat Project [Mladen Turk]
## Description:
A Java Servlet, JavaServer Pages, Java WebSocket and Java
Unified Expression language specifications implementation.
## Issues:
- There are no issues requiring board attention at this time
## Activity:
- Continued healthy activity across multiple components and
responsiveness on both dev and user lists.
## PMC changes:
- Currently 24 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Felix Schumacher on Mon Oct 26 2015
## Committer base changes:
- Currently 40 committers.
- No new committers added in the last 3 months
- Last committer addition was Martin Tzvetanov Grigorov at Tue Oct 27 2015
## Releases:
- Apache Tomcat 6.0.45 was released on Feb 10 2016
- Apache Tomcat 7.0.67 was released on Dec 09 2015
- Apache Tomcat 7.0.68 was released on Feb 15 2016
- Apache Tomcat 8.0.32 was released on Feb 08 2016
- Apache Tomcat 9.0.0.M3 was released on Feb 05 2016
## Mailing list activity:
- TODO Please explain what the following statistics mean
for the project. If there is nothing significant in the figures, omit this
section.
- users@tomcat.apache.org:
- 3027 subscribers (up 6 in the last 3 months):
- 1190 emails sent to list (1034 in previous quarter)
- dev@tomcat.apache.org:
- 855 subscribers (up 11 in the last 3 months):
- 3126 emails sent to list (3585 in previous quarter)
- announce@tomcat.apache.org:
- 4033 subscribers (up 70 in the last 3 months):
- 16 emails sent to list (6 in previous quarter)
- taglibs-user@tomcat.apache.org:
- 357 subscribers (down -2 in the last 3 months):
- 2 emails sent to list (1 in previous quarter)
## Bugzilla Statistics:
- 73 Bugzilla tickets created in the last 3 months
- 89 Bugzilla tickets resolved in the last 3 months
## Trademark:
- Detailed status:
https://svn.apache.org/repos/private/pmc/tomcat/trademark-status.txt
## Security:
- Detailed status:
http://tomcat.apache.org/security.html
-----------------------------------------
Attachment BI: Report from the Apache Tuscany Project [Jean-Sebastien Delfino]
-----------------------------------------
Attachment BJ: Report from the Apache UIMA Project [Marshall Schor]
Apache UIMA's mission: the creation and maintenance of open-source
software related to the analysis of unstructured data, guided by the
UIMA Oasis Standard.
Dates:
15 Feb 2016 (new) last release - Apache UIMA RUTA 2.4.0
(Rules Text Language and workbench)
12 Mar 2013 (no change) last PMC addition
24 Jul 2015 (no change) last Committer addition
Releases:
15 Feb 2016 Apache UIMA RUTA 2.4.0 - this was a large-ish collection of new
features and bug fixes
Other Activity:
The experimental UIMA Version 3 core has advanced to having all but 3 of the
core test cases running. Next phase will involve compatibility testing and
building bridges from the current to the new version, a potentially non-trivial
task.
UIMA Ruta (Rules Text Language and workbench) and DUCC continue to be very
active. Work is also underway to do a release of UIMA-AS to upgrade several
of the components within it. One component, ActiveMQ, was identified as
having security issues, and the upgrade will resolve those.
We began work with Mark Thomas (of Apache) on two initiatives - code signing,
and looking at the results of the SRC CLR scanning for code vulnerabilities -
this is currently ongoing work.
A Committer and PMC member, Richard Eckart de Castilho, gave an Apache UIMA
lightning talk at the Apache Software Foundation Roadshow event in
Karlsruhe, Germany. http://jug-karlsruhe.de/content/apache-software-foundation/
We managed with help from various sources within Apache to guess the owner of
the Twitter account named Apache UIMA, and also managed to reclaim that account;
this was done without invoking trademark infringement claims.
it is now under control of Apache UIMA PMC members, and will be used to
tweet Apache UIMA significant events.
Community:
The community continues to be moderately active.
Issues:
No Board level issues at this time.
-----------------------------------------
Attachment BK: Report from the Apache VCL Project [Andy Kurth]
## Description:
VCL is a modular cloud computing platform which dynamically provisions and
brokers remote access to compute resources including virtual machines,
bare-metal computers, and resources in other cloud platforms. A self-service
web portal is used to request resources and for administration. VCL became a
TLP on June 20, 2012.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- Committers are trying to wrap up bug fixes and a few new features to be able
to get VCL 2.5 out in the next several weeks
- As discussed in the Health Report section, we are seeking ideas from the
community on how to get more people involved in the project [1][2].
## Health report:
Project activity has been down over the last year. We have created a thread
[1][2] on our user and dev lists to address this issue. Some ideas on why
activity has been down that are discussed in the thread are lack of
documentation on using and contributing to VCL, lack of vision on where VCL is
headed, and lack of exposure to new people. I encourage the board and ASF
members to review this thread. Any comments or suggestions sent to any of our
lists is extremely welcome.
## PMC changes:
- Currently 7 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Aaron Coburn on Tue Jun 19 2012
## Committer base changes:
- Currently 8 committers.
- No new committers added in the last 3 months
- Last committer addition was Young Hyun Oh at Sun Dec 08 2013
## Releases:
- Last release was 2.4.2 on Thu Apr 16 2015
- We are hopeful to get VCL 2.5 out in the next several weeks.
## Mailing list activity:
Our user list traffic is down. This was noted in our last report [3] and the
trend hasn't changed yet. We hope to improve things through the ideas expressed
in [1][2].
- dev@vcl.apache.org:
- 134 subscribers (up 1 in the last 3 months):
- 71 emails sent to list (54 in previous quarter)
- user@vcl.apache.org:
- 174 subscribers (up 6 in the last 3 months):
- 18 emails sent to list (9 in previous quarter)
## JIRA activity:
- 17 JIRA tickets created in the last 3 months
- 13 JIRA tickets closed/resolved in the last 3 months
[1] http://vcl.markmail.org/thread/yaqxxfxf7drh4yj5
[2] http://vcl.markmail.org/thread/h33ag3bmrhgkezge
[3] https://cwiki.apache.org/confluence/display/VCL/2015-12-16+Apache+VCL+Board+Report
-----------------------------------------
Attachment BL: Report from the Apache Web Services Project [Sagara Gunathunga]
-----------------------------------------
Attachment BM: Report from the Apache Whimsy Project [Ross Gardler]
1) GitHub experiment has now fully started - bi-directional synchronization
between an ASF hosted and a GitHub hosted repository is now working,
thanks to the work of Daniel Gruno. This provides the potential for a
tangible question as to how to evaluate the ongoing GitHub experiment:
if/when the Infrastructure team decides to recommend that allowing other
projects to make use of this set up, the experiment was a success. Should
the infrastructure team decide to recommend that this set-up is no longer
supported, the experiment is a failure.
2) Manual intervention by the infrastructure team has still proven to be
required to add new committers to the repository. Each month we seem
to get a little closer to making this unnecessary. There are hopeful
signs that next month we will have reached this target.
3) Whimsy has moved over to a new Ubuntu 14.04 VM, complete with automatic
deployment and status monitoring. The fact that the status monitoring is
pushing too much information to the mailing list is a known problem, and
needs resolution. Much of the work of the past month has been focused on
'puppetizing' the remaining tools.
4) A lot of time and effort has gone into improving the documentation of how
to get either individual tools or even the entire whimsy site up and running
on a developers machine.
5) Additional work was done to address stability issues in the board agenda
tool. This is ongoing.
6) The Whimsy roster tool can now be used by PMC chairs to update PMC
membership and committer lists for their projects. And by committers to
update their Spam Assassin score. While the latter may seem odd, it was a
direct result of an infrastructure contractor unilaterally reassigning an
INFRA JIRA to Whimsy without consultation. See associated discussion item.
7) The Whimsy PMC gets periodic requests from the incubator team that
curiously seem to die down quickly. :-(
Other:
Last PMC and committer addition: 14 December 2015
No releases made (code is using a continuous deployment model)
[report prepared by Sam Ruby]
-----------------------------------------
Attachment BN: Report from the Apache Wicket Project [Martijn Dashorst]
Report from the Apache Wicket project [Martijn Dashorst]
Apache Wicket is an open source Java component oriented web application
framework.
## Noteworthy items:
- Currently 30/29 Committers/PMC members.
- Last committer/PMC addition was François Meillet on Mon Jun 29 2015
- There are no issues requiring board attention at this time
- Mailinglist traffic is up over the previous quarter
- Martijn Dashorst was interviewed by InfoQ about the Wicket 7.2 release
- A couple CVE's were handled and fixes were released
- Work on Wicket 8 is in progress
## CVE's
CVE-2015-5347 XSS vulnerability was resolved in Wicket 1.5.15, 6.22.0 and
7.2.0.
CVE-2015-7520 XSS vulnerability was resolved in Wicket 1.5.15, 6.22.0 and
7.2.0
## Releases this quarter
We have issued the following releases: 7.2.0, 6.22.0 and 1.5.15.
## State of the project
As server-side web frameworks mature, we don't expect a big uptake in adoption
of Wicket (or any other server-side framework for that matter). The current
base of users for Wicket seem stable, if slightly declining.
The PMC has been able to mitigate attrition by adding new members to the
project and will continue to do so whenever new potentials arrive. We keep on
the lookout for new candidates.
Apart from bringing in new fresh development resources, the biggest difficulty
currently is to properly weigh new functionality provided by new community
members with the original vision of the project and keeping it maintainable
with a small crew.
Development for Wicket 8 is slow, albeit ongoing.
-----------------------------------------
Attachment BO: Report from the Apache Wink Project [Luciano Resende]
Dear Board,
Please find below the board report for Apache Wink project.
Apache Wink is a project that enables development and consumption of
REST style web services. The core server runtime is based on the
JAX-RS (JSR 311) standard. The project also introduces a client
runtime which can leverage certain components of the server-side
runtime. Apache Wink delivers component technology that can be easily
integrated into a variety of environments.
There are no issues that require Board attention at the moment.
Community:
The Wink project has a mature project with small community which is
currently not very active. Although I believe Wink is a mature project
with active users, the overall PMC has been alive but not active, and
on the last time I ask, they were starting to contemplate a move
to attic. Although they have expressed that willingness, nothing have
been done on that direction and the community seems to still be taking
care of the current code, as we just receive a security patch on the past
couple weeks. Maybe I could try a new release (1.4.1) with the recent
security fix to see if we would generate any community traction.
Last svn activity shows a security fix provided by a user the past week
(03/2016)
Releases:
* Last release was Apache Wink 1.4.0 which was released on September 15, 2013
Committers or PMC changes:
* Voted Gerhard Petracek was added as a Wink committer in August 2013.
Trademark/Branding:
* No known issues.
Legal Issues:
* None
-----------------------------------------
Attachment BP: Report from the Apache Xerces Project [Michael Glavassevich]
Xerces-J
There has been no development activity on Xerces-J since early
December 2015. We still need volunteers to help push out a new
release.
Mailing list traffic has been very low; only 8 posts on the j-dev
and j-users lists since the beginning of December 2015. It appears
the community has shifted over time to using stackoverflow.com for
asking questions related to Xerces instead of using the Apache
mailing lists.
No new releases this quarter. The latest release is
Xerces-J 2.11.0 (November 30th, 2010).
Xerces-C
Xerces-C 3.1.3 was released on February 17th to address a security
vulnerability. It also contains other fixes that were made last
year.
Mailing list traffic has been low; roughly 70+ posts on the c-dev
and c-users lists since the beginning of December 2015.
The latest release is Xerces-C 3.1.3 (February 17th, 2016).
Xerces-P
Nothing in particular to report. There was no development activity
over the reporting period.
XML Commons
No activity over the reporting period.
Committer / PMC Changes
The most recent committers were added in February 2015 (Xerces-C)
and May 2009 (Xerces-J).
No new PMC members in the last four months. The last two additions
to the PMC were in May 2010.
Three committers committed changes to SVN in the last quarter.
Apache Project Branding Requirements
The project logo still needs a "TM" to be added to it.
-----------------------------------------
Attachment BQ: Report from the Apache Yetus Project [Sean Busbey]
Apache Yetus provides libraries and tools that enable contribution and release
processes for software projects.
ISSUES FOR THE BOARD'S ATTENTION
None at this time.
RELEASES
Version 0.1.0 was released on December 13th 2015.
Version 0.2.0 was released on March 7th 2016.
ACTIVITY
Kengo Seki was added to the PMC on February 28th 2016.
No new committers in the last three months.
Last new committer was Kengo Seki on December 01, 2015.
The community has just finished laying some process groundwork to make
on-boarding new release managers easier. This culminated in our second release.
This release should be sufficiently stable for us to concentrate more on
evangelism beyond the handful of projects that brought the current contributors
to Yetus in the first place.
Our Allen Wittenauer has talks on Yetus scheduled for ApacheCon Core as well as
ApacheCon BigData. We believe this will be the largest audience the project has
been presented to.
Mailing list traffic remains low, but responsive.
STATS
- Currently 7 PMC members
- Currently 7 committers
- dev list has 31 subscribers (up 6 in the last 3 months)
- 106 JIRA tickets created in the last 3 months
- 81 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment BR: Report from the Apache Zest Project [Niclas Hedhman]
Description
Apache Zest is a community based effort exploring Composite Oriented
Programming for domain-centric application development.
Activity
The activity in the last quarter was relatively slow. The work on 3.0 came to
a halt at Christmas, mainly due to primary developers got caught up in $dayjob
issues/tasks. But community is still active and discussion are ongoing of next
steps, and we are optimistic of the future.
Issues
There are no issues that requires the Board's attention.
Health report:
As mentioned in previous report, attracting new blood will remain the major
concern of the PMC. Zest got a talk accepted at ApacheCon NA, and will try to
engage more people at the event.
PMC changes:
- Currently 11 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Kent Sølvsten on Tue Sep 22 2015
Committer base changes:
- Currently 17 committers.
- No new committers added in the last 3 months
- Last committer addition was Kent Sølvsten at Sun Jun 14 2015
Releases:
- Last release was JAVA-2.1 on Fri Jul 31 2015
Mailing list activity:
users@ list are effectively not utilized, as basically the entire user base is
on the dev@ list and most are PMC members as well.
- users@zest.apache.org:
- 18 subscribers (up 0 in the last 3 months):
- 1 emails sent to list (1 in previous quarter)
- dev@zest.apache.org:
- 29 subscribers (up 2 in the last 3 months):
- 139 emails sent to list (134 in previous quarter)
JIRA activity:
New tickets created are around the ver 3.0 effort, and closed tickets are
resolution of breaking builds.
- 9 JIRA tickets created in the last 3 months
- 2 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment BS: Report from the Apache ZooKeeper Project [Michi Mutsuzaki]
## Description:
- A distributed computing platform.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
- The PMC has appointed Flavio Junqueira (fpj) as new PMC chair. The votes
can be found here: https://s.apache.org/36nv
- Released 3.4.8, which contains a fix for the deadlocking issue that was
introduced in 3.4.7 (ZOOKEEPER-2347).
- Now we are focusing on releasing 3.5.2-alpha.
- Started a discussion around how to manage pull requests from github.
Currently we do not accept github pull requests.
## Health report:
- Both dev@ and user@ mailing lists have been active:
- dev@zookeeper.apache.org:
- 487 subscribers (up 18 in the last 3 months):
- 1462 emails sent to list (1167 in previous quarter)
- user@zookeeper.apache.org:
- 1142 subscribers (up 27 in the last 3 months):
- 346 emails sent to list (297 in previous quarter)
## PMC changes:
- Currently 10 PMC members.
- Raul Gutierrez Segales was added to the PMC on Tue Feb 02 2016
## Committer base changes:
- Currently 19 committers.
- No new committers added in the last 3 months
- Last committer addition was Chris Nauroth at Wed Sep 09 2015
## JIRA activity:
- 44 JIRA tickets created in the last 3 months
- 38 JIRA tickets closed/resolved in the last 3 months
------------------------------------------------------
End of minutes for the March 16, 2016 board meeting.
Index