Index
Links: 2014 - All years
- Original The Apache Software Foundation
Board of Directors Meeting Minutes
May 21, 2014
1. Call to order
The meeting was scheduled for 10:30am Pacific and began at 10:33
when a sufficient attendance to constitute a quorum was
recognized by the chairman.
Other Time Zones: http://timeanddate.com/s/2p7f
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:
Shane Curcuru
Doug Cutting
Bertrand Delacretaz
Roy T. Fielding
Jim Jagielski
Brett Porter
Sam Ruby
Greg Stein
Directors Absent:
Chris Mattmann
Executive Officers Present:
Ross Gardler
Rich Bowen
Craig L Russell
Executive Officers Absent:
none
Guests:
Jake Farrell
Marvin Humphrey
Sean Kelly
Henri Yandell joined at 10:52
Daniel Shahaf
David Nalley
Tom Pappas (Virtual, Inc.)
Daniel Gruno
Andrea Pescetti
Upayavira
Andy Seaborne
Noah Slater
Daniel Kulp
3. Minutes from previous meetings
Published minutes can be found at:
http://www.apache.org/foundation/board/calendar.html
A. The meeting of April 16, 2014
See: board_minutes_2014_04_16.txt
Approved by General Consent.
4. Executive Officer Reports
A. Chairman [Brett]
While some discussion about directed sponsorship and expanding project
resources continued this month, the recent focus has been on immediate
needs and the budget, as covered in the President's report.
We have also been busy with preparations for the Annual Members
Meeting, which will be held next week. We have a very healthy number
of nominations for both new Members, and for the Board of Directors.
This being the last meeting of the current board, I'd like to thank
you all for your time, effort, and service to the Foundation, and for
the privilege of being able to serve you as Chairman. It has been an
honour!
B. President [Ross]
It's a big report this month, so here's a bullet summary of the
key items (not exhaustive, see below for completeness):
- Proposed interim 3-month budget (Special Order G) which shows
a surplus. Full year budget (available in SVN) shows a deficit.
- Working with VP Fundraising to address the budget deficit moving
forwards
- Infrastructure requires immediate action (and budget) to minimize
the likelihood of further outages (included in budget)
- VP Marketing working with CloudStack PMC to develop a long-term
outreach strategy that can be used by all TLPs
- Working with VP Marketing and VP Fundraising to develop better
materials on "what we do"
And here's the details...
Budget
------
The most important item this month is the approval of a 2014/15
budget. I am, however, requesting that the board approve a
3-month interim budget (May - July) rather than a full 12 month
budget. There are a number of reasons for this:
1) proximity to the election of the next board
2) significant exceptional infrastructure costs
3) a need to examine directed funding and additional marketing
activities
Given point 2) and the uncertainty of point 3) I think it is
prudent for the current board, which is meeting this month for the
last time, to only pass an interim budget. Please see Special Order
G. This interim budget shows a surplus based on a majority of sponsors
being due for renewal in this period, but the FY budget shows a
significant deficit.
I've worked with all officers to create an appropriate budget and
believe both the three month interim and proposed 12 month budget
reflect a balance between immediate needs and prudent budget controls.
Deficit
-------
It should be noted that the proposed FY budget shows a significant
deficit. This is well within the foundations cash reserves and provides
an immediate cash injection to address some of the issues reported by
VP Infrastructure (see Attachment 5). We have also seen a significant
increase in administration costs relating to the scaling of the
foundation. These include an increase in the treasury budget
(appointment of Virtual) and our Administration budget (as approved
in Jan 2014).
In order to address this deficit myself, VP Infrastructure and VP
Fundraising have been discussing options. One such option (in kind
donations of equipment for infrastructure) is outlined in VP
Fundraising's report (Attachment 3). Another option that has been
discussed previously is targeted donations (although these would
not address immediate and pressing infrastructure needs). Beyond
discussion we are actively working to ensure that there is an
increased visibility into where sponsorship money goes and what our
projects produce as a result of the foundations existence. This will
enable us to build a strong outreach for existing sponsors as well as
providing valuable materials when seeking new sponsors.
Infrastructure
--------------
Our new VP Infrastructure has had a difficult month. There are
extensive details in the Infrastructure report (Attachment 5). I will
observe that it seems we have been running our infrastructure on much
too tight a budget. This has resulted in a number of outages. I fully
support the proposed remedial action which includes a) replacement
of existing hardware b) appropriate maintenance and monitoring and c)
increased automation and related skills development. I urge both the
current and future board to support the significant budget increase
requested by VP Infrastructure.
Targeted donations
------------------
In recent months there have been many discussions about targeted
donations for project specific infrastructure requirements and project
marketing efforts. It seems that project specific infrastructure is
likely to be on hold until current remediation activities are
complete. With respect to project specific marketing VP Marketing has
been working with, and continues to work with, the CloudStack PMC with
a view to developing a long-term outreach strategy that can be used by
all TLPs in choosing a tactical plan that best suits their specific
marketing/visibility needs. It is expected that this strategy will
highlight any necessity for project specific marketing funds and I
propose to revisit this topic once the strategy is delivered.
Foundation Marketing
--------------------
The community have also discussed the need for ASF wide marketing
activities. This has been further discussed between VP Marketing,
VP Fundraising and myself. It is my belief that the initial focus needs
to be on a) providing valuable information to our existing sponsors
about what we do, how we operate and spend their money and b)
enabling our PMCs to drive appropriate marketing campaigns. Whilst there
is value in marketing the ASF itself I feel that a focus on ensuring
that we support our projects first is the appropriate action. Once
infrastructure is stable and provides the services our existing projects
require, PMCs are equipped to develop and recognize marketing potential
within our existing structure and fundraising is firing on all cylinders
such that we are not showing a budget deficit then I would like to
revisit this topic, but for now my personal focus remains on
infrastructure, PMC marketing capabilities and fundraising.
EA
--
This month has been a relatively quiet month for our EA in the absence
of a conference to organize. Melissa has used this time to further improve
the fundraising processes and to follow up with a number of sponsors
due for renewal (supported by VP Marketing).
Brand Management
----------------
Brand Management has been a "normal" month. Again our VP is indicating
that a number of routine questions are incoming and that these can
be addressed with clearer documentation and policy. I have encouraged
the VP to work with our EA to take some of this load.
TAC
---
TAC provides a useful summary of their work for ACNA and some increased
effort to raise awareness of the TAC process. This awareness raising is
a useful part of the discussion around marketing the ASF and making
sponsors aware of the value they bring to the foundation.
With respect to budget TAC had requested an increase to allow them to
cover two smaller events in addition to the two ApacheCon events. However,
I declined to include the budget for the smaller events, just as I
declined to include my own Event-in-a-Box proposal to ComDev. My intention
is to secure at least one additional sponsor highlighting these items as
additions that their sponsorship will help fund (not necessarily as
directed sponsorship, although that is a possibility as we progress with
discussions around that topic).
And Finally...
--------------
Finally, I would like to thank the outgoing board for their service
to the foundation. I'm sure many will be back again next month, and
even those who don't have a seat are likely to still be watching over
the shoulders of those who do.
Thank you for last year, lets look forward to many more.
Additionally, please see Attachments 1 through 6.
C. Treasurer [Chris]
The big news is that we have officially signed and executed an
agreement with Virtual, Inc. to provide end-to-end financial
management for the ASF, as a contractor approved by the Board
assisting the Treasurer. Virtual will have a representative Guest
on the board call, Tom Pappas, who will attend and observe the
Treasurer report and the initial portion of the meeting before the
committee reports. The Treasurer and Assistant Treasurer are working
with Virtual to make sure there is a smooth on boarding and that
Virtual is provided with access to all material needed, and that
we carefully consider and document their suggestions. At this point
in time due to schedule flexibility and a general East coast favorable
calling time, calls with Virtual and Apache are being attended by
Sam Ruby, Assistant Treasurer, and Sam is taking point on managing
the connection with Virtual, in coordination with Chris. Jim is
meeting with the CPA to discuss the audit now that Virtual is on
board and the Treasurer's Office expects that Jim can report out
on any progress there during the board call and also via audit@apache.org.
The Treasurer's Office is correcting an error made in the original
1099 filed for our EA Melissa. The Treasurer expects to have that
form in the mail NLT Thursday May 22, 2014. Apologies to the EA for
the delay.
Questions about our accounting mechanism were posed by VP Infrastructure
and answered promptly by the Treasurer's Office.
The HALO contract renewal is coming up and VP Press and Marketing
has reached out to the President and Treasurer's Office to proceed
on this. Treasurer's Office has requested an invoice from VP Press
and Marketing so it can go into our Bills/received folder for
approval by the President and/or EVP.
Income and Expenses
Current Balances:
Wells Fargo Business Checking: 1,184,386.24
Wells Fargo Savings: 287,934.59
PayPal: 13,793.75
Amazon: 11,488.70
------------------------------ ---------
Total $ 1,486,114.58
Income Summary:
Amazon 1,284.33
Fundraising 140,000.00
Lockbox 434.62
PayPal 1,479.33
---------------------------- ----------
Total $ 143,198.28
Expense Summary:
Category Amount
---------------------------- ----------
EA 5,539.20
Sysadmin 31,800.00
misc expense 455.87
ASF credit card - Sam Ruby 41.90
ASF credit card - Jim Jagielski 4,559.82
Press 4,545.45
FOSDEM 2013 204.49
Network Services - Traci.net 518.00
---------------------------- ----------
Total $ 47,664.73
We will be transitioning our banking services from Wells Fargo
to Citizens Bank. We expect the transition to take place over
the next few weeks. There is a safety deposit box that Roy
will clear out shortly.
D. Secretary [Craig]
Secretary is running well and the volume of documents has picked up.
In April, 77 iclas, two cclas, and two grants were received and filed.
E. Executive Vice President [Rich]
Planning for ApacheCon Europe is moving along, with several keynotes
selected and 25 papers in the CFP system. The CFP ends in a little
more than a month, so the time to start pushing hard to get papers
in is upon us and we should start seeing a lot more planning
activity in the next few weeks.
F. Vice Chairman [Greg]
Nothing significant to report at this time.
Executive officer reports approved as submitted by General Consent.
5. Additional Officer Reports
A. VP of W3C Relations [Andy Seaborne / Shane]
See Attachment 7
B. Apache Legal Affairs Committee [Jim Jagielski]
See Attachment 8
C. Apache Security Team Project [Mark Cox / Roy]
See Attachment 9
Additional officer reports approved as submitted by General Consent.
6. Committee Reports
A. Apache Abdera Project [Ant Elder / Chris]
No report was submitted.
AI Brett: pursue a report for Abdera
B. Apache Allura Project [Dave Brondsema / Brett]
See Attachment B
C. Apache Ambari Project [Yusaku Sako / Greg]
See Attachment C
D. Apache Ant Project [Conor MacNeill / Sam]
See Attachment D
E. Apache Attic Project [Gianugo Rabellino / Jim]
See Attachment E
F. Apache Avro Project [Scott Carey / Bertrand]
See Attachment F
G. Apache Buildr Project [Alex Boisvert / Doug]
No report was submitted.
AI Doug: pursue a report for Buildr
H. Apache Cassandra Project [Jonathan Ellis / Shane]
See Attachment H
I. Apache Clerezza Project [Hasan Hasan / Doug]
See Attachment I
J. Apache Click Project [Malcolm Edgar / Roy]
No report was submitted.
K. Apache Cocoon Project [Thorsten Scherler / Greg]
See Attachment K
L. Apache Community Development Project [Luciano Resende / Bertrand]
See Attachment L
M. Apache Continuum Project [Brent Atkinson / Brett]
See Attachment M
N. Apache CouchDB Project [Jan Lehnardt / Sam]
See Attachment N
O. Apache Creadur Project [Robert Burrell Donkin / Chris]
No report was submitted.
AI Brett: pursue a report for Creadur
P. Apache DeltaSpike Project [Mark Struberg / Jim]
See Attachment P
Q. Apache DirectMemory Project [Raffaele P. Guidi / Doug]
See Attachment Q
R. Apache Directory Project [Pierre-Arnaud Marcelot / Shane]
See Attachment R
S. Apache Empire-db Project [Francis De Brabandere / Brett]
See Attachment S
T. Apache Etch Project [Martin Veith / Chris]
See Attachment T
U. Apache Flume Project [Arvind Prabhakar / Roy]
See Attachment U
V. Apache Forrest Project [David Crossley / Sam]
See Attachment V
W. Apache Giraph Project [Avery Ching / Jim]
See Attachment W
X. Apache Gora Project [Lewis John McGibbney / Bertrand]
See Attachment X
Y. Apache Hama Project [ChiaHung Lin / Greg]
See Attachment Y
Z. Apache HTTP Server Project [Eric Covener / Shane]
See Attachment Z
AA. Apache HttpComponents Project [Asankha Perera / Greg]
See Attachment AA
AB. Apache Incubator Project [Roman Shaposhnik / Roy]
See Attachment AB
AI Bertrand: Look at the DeviceMap project health
AC. Apache jUDDI Project [Kurt Stam / Brett]
See Attachment AC
AD. Apache Kafka Project [Jun Rao / Chris]
See Attachment AD
AE. Apache Knox Project [Kevin Minder / Bertrand]
See Attachment AE
AF. Apache Lenya Project [Richard Frovarp / Sam]
See Attachment AF
AG. Apache Libcloud Project [Tomaz Muraus / Doug]
See Attachment AG
AH. Apache Logging Project [Christian Grobmeier / Jim]
See Attachment AH
AI. Apache ManifoldCF Project [Karl Wright / Doug]
See Attachment AI
AJ. Apache Marmotta Project [Jakob Frank / Brett]
See Attachment AJ
AK. Apache Mesos Project [Benjamin Hindman / Shane]
See Attachment AK
AL. Apache Olingo Project [Stephan Klevenz / Chris]
See Attachment AL
AM. Apache Oltu Project [Antonio Sanso / Bertrand]
See Attachment AM
AN. Apache Oozie Project [Mohammad Islam / Jim]
See Attachment AN
AO. Apache Open Climate Workbench Project [Michael James Joyce / Roy]
See Attachment AO
AP. Apache Perl Project [Philippe M. Chiasson / Greg]
No report was submitted.
AQ. Apache POI Project [Yegor Kozlov / Sam]
See Attachment AQ
AR. Apache Qpid Project [Gordon Sim / Doug]
See Attachment AR
AS. Apache River Project [Greg Trasuk / Shane]
See Attachment AS
AI Shane: Get them connected with comdev to recruit new blood
AT. Apache Roller Project [Dave Johnson / Greg]
See Attachment AT
AU. Apache Santuario Project [Colm O hEigeartaigh / Jim]
See Attachment AU
AV. Apache SIS Project [Adam Estrada / Bertrand]
See Attachment AV
AW. Apache Spark Project [Matei Zaharia / Sam]
See Attachment AW
AX. Apache Subversion Project [Greg Stein]
See Attachment AX
AY. Apache Syncope Project [Francesco Chicchiricco / Brett]
See Attachment AY
AZ. Apache Tajo Project [Hyunsik Choi / Chris]
See Attachment AZ
BA. Apache TomEE Project [David Blevins / Roy]
See Attachment BA
BB. Apache Turbine Project [Thomas Vandahl / Chris]
See Attachment BB
BC. Apache Tuscany Project [Jean-Sebastien Delfino / Brett]
See Attachment BC
BD. Apache Velocity Project [Nathan Bubna / Bertrand]
See Attachment BD
BE. Apache Xalan Project [Steven J. Hathaway / Greg]
See Attachment BE
BF. Apache Xerces Project [Michael Glavassevich / Jim]
See Attachment BF
BG. Apache XML Graphics Project [Chris Bowditch / Doug]
See Attachment BG
Committee reports approved as submitted by General Consent.
7. Special Orders
A. Change the Apache Cordova Project Chair
WHEREAS, the Board of Directors heretofore appointed Brian LeRoux to
the office of Vice President, Apache Cordova, and
WHEREAS, the Board of Directors is in receipt of the resignation of
Brian LeRoux from the office of Vice President, Apache Cordova, and
WHEREAS, the Project Management Committee of the Apache Cordova project
has chosen by vote to recommend Shazron Abdullah as the successor to
the post;
NOW, THEREFORE, BE IT RESOLVED, that Brian LeRoux is relieved and
discharged from the duties and responsibilities of the office of Vice
President, Apache Cordova, and
BE IT FURTHER RESOLVED, that Shazron Abdullah be and hereby is
appointed to the office of Vice President, Apache Cordova, 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 Cordova Project Chair, was
approved by Unanimous Vote of the directors present.
B. Establish the Apache Stratos 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 providing an implementation of a
Platform-as-a-Service Framework.
NOW, THEREFORE, BE IT RESOLVED, that a Project Management
Committee (PMC), to be known as the "Apache Stratos Project",
be and hereby is established pursuant to Bylaws of the
Foundation; and be it further
RESOLVED, that the Apache Stratos Project be and hereby is
responsible for the creation and maintenance of software
related to providing an implementation of a Platform-as-a-Service
Framework; and be it further
RESOLVED, that the office of "Vice President, Stratos" 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 Stratos Project, and to have primary responsibility
for management of the projects within the scope of
responsibility of the Apache Stratos 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 Stratos Project:
Ant Elder (antelder@apache.org)
Paul Fremantle (pzf@apache.org)
Jonathan Marsh (jonathanmarsh@apache.org)
Afkham Azeez (azeez@apache.org)
Peter Linnell (plinnell@apache.org)
Lakmal Warusawithana (lakmal@apache.org)
Damitha Kumarage (damitha@apache.org)
Samisa Abeysinghe (samisa@apache.org)
Nirmal Fernando (nirmal070125@apache.org)
Sajith Kariyawasam (sajith@apache.org)
Lahiru Sandaruwan (lahirus@apache.org)
Isuru Haththotuwa (isuruh@apache.org)
Madhura Mendis (madhura@apache.org)
Mariangela Hills (mariangela@apache.org)
Suresh Marru (smarru@apache.org)
Chip Childers (chipchilders@apache.org)
Joe Brockmeier (jzb@apache.org)
Noah Slater (nslater@apache.org)
Nandana Mihindukulasooriya (nandana@apache.org)
Isuru Perera (isuru@apache.org)
Reka Thirunavakurussu (reka@apache.org)
Deepal Jayasinghe (deepal@apache.org)
Debo Dutta (ddutta@apache.org)
Udara Liyanage (udara@apache.org)
Manula Chathurika Thantriwatte (manula@apache.org)
Imesh Gunaratne (imesh@apache.org)
Pradeep Fernando (pradeepfn@apache.org)
Chris Snow (chsnow@apache.org)
Melan Nimesh (melan@apache.org)
Jason Daly (jasondalycan@apache.org)
Chanaka Jayasena (chanaka@apache.org)
Jeffrey Nguyen (jeffrngu@apache.org)
Anh Tu Nguyen (tuna@apache.org)
NOW, THEREFORE, BE IT FURTHER RESOLVED, that Lakmal
Warusawithana be appointed to the office of Vice President,
Stratos, 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 Stratos 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 Stratos Project; and be it further
RESOLVED, that the Apache Stratos Project be and hereby
is tasked with the migration and rationalization of the Apache
Incubator Stratos podling; and be it further
RESOLVED, that all responsibilities pertaining to the Apache
Incubator Stratos podling encumbered upon the Apache Incubator
Project are hereafter discharged.
Special Order 7B, Establish the Apache Stratos Project, was
approved by Unanimous Vote of the directors present.
C. Change the Apache DeltaSpike Project Chair
WHEREAS, the Board of Directors heretofore appointed Mark Struberg
to the office of Vice President, Apache DeltaSpike, and
WHEREAS, the Board of Directors is in receipt of the
resignation of Mark Struberg from the office of Vice
President, Apache DeltaSpike, and
WHEREAS, the Project Management Committee of the Apache DeltaSpike
project has chosen by vote to recommend Gerhard Petracek
as the successor to the post;
NOW, THEREFORE, BE IT RESOLVED, that Mark Struberg is
relieved and discharged from the duties and responsibilities of
the office of Vice President, Apache DeltaSpike, and
BE IT FURTHER RESOLVED, that Gerhard Petracek be and hereby is
appointed to the office of Vice President, Apache DeltaSpike, 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 DeltaSpike Project Chair,
was approved by Unanimous Vote of the directors present.
D. Establish the Apache Phoenix 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 a SQL database for NoSQL data stores
such as Apache HBase.
NOW, THEREFORE, BE IT RESOLVED, that a Project Management
Committee (PMC), to be known as the "Apache Phoenix Project",
be and hereby is established pursuant to Bylaws of the
Foundation; and be it further
RESOLVED, that the Apache Phoenix Project be and hereby is
responsible for the creation and maintenance of software
related to a SQL database for NoSQL data stores such as Apache
HBase; and be it further
RESOLVED, that the office of "Vice President, Apache Phoenix" 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 Phoenix Project, and to have primary responsibility
for management of the projects within the scope of
responsibility of the Apache Phoenix 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 Phoenix Project:
* Andrew Purtell <apurtell@apache.org>
* Anoop Sam John <anoopsamjohn@apache.org>
* Devaraj Das <ddas@apache.org>
* Eli Levine <elilevine@apache.org>
* Enis Soztutar <enis@apache.org>
* Gabriel Reid <greid@apache.org>
* James R. Taylor <jamestaylor@apache.org>
* Jeffrey Zhong <jeffreyz@apache.org>
* Jesse Yates <jyates@apache.org>
* Lars Hofhansl <larsh@apache.org>
* Maryann Xue <maryannxue@apache.org>
* Michael Stack <stack@apache.org>
* Mujtaba Chohan <mujtaba@apache.org>
* Nick Dimiduk <ndimiduk@apache.org>
* Ramkrishna Vasudevan <ramkrishna@apache.org>
* Simon Toens <stoens@apache.org>
* Steven Noels <stevenn@apache.org>
NOW, THEREFORE, BE IT FURTHER RESOLVED, that James R. Taylor
be appointed to the office of Vice President, Apache Phoenix, 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 Phoenix 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 Phoenix Project; and be it further
RESOLVED, that the Apache Phoenix Project be and hereby
is tasked with the migration and rationalization of the Apache
Incubator Phoenix podling; and be it further
RESOLVED, that all responsibilities pertaining to the Apache
Incubator Phoenix podling encumbered upon the Apache Incubator
Project are hereafter discharged.
Special Order 7D, Establish the Apache Phoenix Project, was
approved by Unanimous Vote of the directors present.
E. Change the Apache Attic Project Chair
WHEREAS, the Board of Directors heretofore appointed Gianugo Rabellino
to the office of Vice President, Apache Attic, and
WHEREAS, the Board of Directors is in receipt of the resignation of
Gianugo Rabellino from the office of Vice President, Apache Attic, and
WHEREAS, the Project Management Committee of the Apache Attic project
has chosen by vote to recommend Henri Yandell as the successor to
the post;
NOW, THEREFORE, BE IT RESOLVED, that Gianugo Rabellino is relieved and
discharged from the duties and responsibilities of the office of Vice
President, Apache Attic, and
BE IT FURTHER RESOLVED, that Henri Yandell be and hereby is
appointed to the office of Vice President, Apache Attic, 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 Attic Project Chair, was
approved by Unanimous Vote of the directors present.
F. Terminate the Apache Click Project
WHEREAS, the Board of Directors deems it no longer in the best
interest of the Foundation to continue the Apache Click project due to
inactivity
NOW, THEREFORE, BE IT RESOLVED, that the Apache Click project is
hereby terminated; and be it further
RESOLVED, that the Attic PMC be and hereby is tasked with oversight
over the software currently maintained by the Apache Click Project;
and be it further
RESOLVED, that the office of "Vice President, Apache Click" is hereby
terminated; and be it further
RESOLVED, that the Apache Click PMC is hereby terminated.
Special Order 7F, Terminate the Apache Click Project, was
approved by Unanimous Vote of the directors present.
G. Approve the Interim 3 Month ASF Budget
Call for Board approval of proposed 2014 Interim 3 month budget for
the ASF.
The three month interim budget is summarised below:
Income Expenditure Balance
Bank Charges and Interest $900 $950 $(50)
Public Donations $9,400 $25 $9,375
Sponsorship Program $590,000 $3,700 $586,300
Programs $25,400 $6,000 $19,400
Administration $- $23,823 $(23,823)
Infrastructure $- $241,804 $(241,804)
Publicity $- $54,000 $(54,000)
Conferences (President) $- $- $-
Travel Assistance Committee $- $- $-
Legal $- $1,100 $(1,100)
Brand Management $- $16,000 $(16,000)
Board $- $1,100 $(1,100)
Treasury Services $- $20,550 $(20,550)
Licenses/Insurance $- $1,750 $(1,750)
Shipping $- $200 $(200)
====================================================================
Total $625,700 $371,002 $254,698
====================================================================
Discussion:
Publicity looks like it's enough for the entire year. Right. It's an up front
payment of a retainer plus a monthly fee.
Trademarks shows registering all podlings before graduation. The line item
should be for registering "key podlings".
Special Order 7G, Approve the Interim 3 Month ASF Budget, was
approved by Unanimous Vote of the directors present.
8. Discussion Items
9. Review Outstanding Action Items
* Roy: Update the guidance for releases to forbid shipping binary
dependencies within a source package unless their source is also
included (see board_minutes_2012_04_18.txt) and communicate to
committers.
Status: not done
* Chris: follow up on bringing on new committers and PMC members to DB
Status: Done (duplicate of Empire-db?). See below.
* Brett: follow up with Click regarding the Attic or rebooting
Status: resolution in agenda
* Brett: Remind PMCs to check their committee records
Status:
* Greg: ask about "pending discussion by the PMC" by JMeter
Status: not started
* Chris: follow up with Empire-db about steps to bringing on new blood
Status: Done. Email sent to dev list and CC to board@.
* Sam: Discuss with ComDev the vouching process. If ComDev decides to
vouch for other organizations, the decision should be made
public. This might raise questions from others about how to
qualify for vouching and the ComDev PMC should be prepared to
discuss criteria that they use.
Status: I'm satisfied with this response: http://s.apache.org/qOl
* Shane: ask Curator if there a plan to attract new committers/PMC members?
Status:
* Doug: discuss bringing in new PMC members with OFBiz
Status:
* Jim: discuss service hosting issue (licensing, trademark, etc.) with
SpamAssassin PMC.
Status: Not yet complete.
* Ross: what can be done to improve the Attic situation?
Status:
* Doug: suggest naming a new chair for Avro
Status:
* Jim: follow up Cordova with issues regarding committers, PMC
membership, and users mailing lists
Status: On-going... others are also helping.
* Sam: ask CXF to file JIRA for Jenkins issues
Status: Done. http://s.apache.org/g7k
* Shane: to pursue a report for Directory
Status: report is present
* Jim: follow up regarding lack of new PMC members in MyFaces
Status: Will resend and re-enage w/ PMC.
* Chris: follow up Onami regarding engaging the community and looking for
potential PMC members
Status: Done. Email sent to dev list and CC to board@.
* Shane: follow up Open Climate Workbench regarding expanding the user
community
Status:
10. Unfinished Business
11. New Business
New contract for auditing services looks like it will come in around
$13,000. The budget estimate was $10,000. When the contract comes in
it will be distributed for review and approval.
12. Announcements
Roy has decided not to accept the nomination for a board position
this year. Special thanks for his service over the years.
13. Adjournment
Adjourned at 11:39 a.m. (Pacific)
============
ATTACHMENTS:
============
-----------------------------------------
Attachment 1: Report from the Executive Assistant [Melissa Warnkin]
Daily monitoring of all email activity (ea@, fundraising@, trademarks@,
treasurer@, comdev@, and board@) and following-up with appropriate personnel
ApacheCon - TAC:
• Received final hotel bill from The Westin; submitted in svn, Gav approved,
awaiting payment from Chris
Fundraising:
• Created new task sheet in the Sponsorship spreadsheet to streamline the
process of renewals and follow-ups
• Received acknowledgements from Yahoo! and Pivotal on invoices submitted;
completed vendor form for Pivotal’s AP System; issued revised invoice to FB
to include their PO#
• Sam and Chris will work with Wells Fargo to add me to the account for “read
access” so that I can monitor the incoming payments and follow-up on the
past-due renewals more efficiently and effectively.
OSCON:
• Submitted application for a non-profit pavilion booth; application has been
approved; process has begun to complete the exhibitor application and
contract
• In discussions with Sally re giveaways
MISC:
• Created and shared an Infra Vacation calendar that I will be maintaining
• Participated in a ConCall with Sam and Virtual, Inc. for introductory
purposes pertaining to Sponsorship issues
• Sorted out the 1099 error with Chris; Chris to send an amended 1099
-----------------------------------------
Attachment 2: Report from the VP of Brand Management [Shane Curcuru]
The volume and variety of questions and issues on trademarks@ continues
to be heavy, and in particular continues to show that more education
and clearer policy documentation is needed, both for our project
communities as well as a more clearly presented and easily approachable
set of policy documentation for users and potential corporate sponsors
or donors as well.
Telecon with the Apache CouchDB project to discuss branding issues and
enforcement ideas; the project has some great energy with new code
merges and will be working on an improved and better articulated brand
for CouchDB overall.
Budget request submitted to president@. Note that while our actual
spending is still well below budget for last year, this is partly due
to delays in billing and processing time from counsel, so I expect to
get a number of bills soon.
Registrations
Responded to a number of questions to APACHE registration issues in
various jurisdictions.
Preparing registrations for SERVICEMIX and ACTIVEMQ at project request.
Working with counsel on securing a coexistence agreement and/or
opposition to a third party registration of an Apache product name.
-----------------------------------------
Attachment 3: Report from the VP of Fundraising [Upayavira]
Melissa continues to hold the task of managing renewals, either
contacting sponsors directly, or asking myself or Sally for assistance
where necessary.
Given expected increase in financial demands from Infrastructure,
fundraising effort is expected, in a manner that the ASF has not,
certainly in the last few years, attempted.
-----------------------------------------
Attachment 4: Report from the VP of Marketing and Publicity [Sally Khudairi]
I. Budget: we remain on schedule and under budget. All vendor payments have
been processed on time with ongoing thanks to the Treasurer and Operations
teams. The contract with HALO Worldwide has been renewed for FY 2014-2015 with
a remuneration increase due to expanded scale (not scope) of work.
II. Fundraising/Branding/Marketing liaison: Sally Khudairi met with both VP
Fundraising Upayavira and VP Brand Management Shane Curcuru to review current
issues and address future goals. Sally is continuing Sponsor renewal and
general outreach with Platinum-level Sponsors. She has also agreed to observe
and assist with project-specific marketing/promotional support with Apache
CloudStack, and will be developing a long-term outreach strategy that can be
used by all TLPs in choosing a tactical plan that best suits their specific
marketing/visibility needs.
III. Press Releases: the following formal announcement was issued via the
newswire service, ASF Foundation Blog, and announce@apache.org:
- 17 April 2014 --The Apache Software Foundation Announces 100 Million
Downloads of Apache™ OpenOffice™
IV. Informal Announcements: 9 items were tweeted on @TheASF, and 2 on
@ApacheCon post-event. The ApacheCon producers uploaded an unprecedented 166
presentations (a record, both quantity and timeframe) on "TheApacheFoundation"
account on YouTube, which also includes presentations from the CloudStack
Collaboration Conference.
V. Future Announcements: we are preparing two project-related announcements
and one TAC statement to be issued by the end of the month, if not sooner.
PMCs wishing to announce major project news, as well as podlings ready to
graduate from the Incubator, 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: we responded to 22 media requests, and worked with a
small handful of reporters on the ASF's role in the Open Source ecosystem. We
experienced a sharp increase in immediate requests for comment regarding the
Heartbleed security bug. We were also alerted to many instances of
misattribution to the ASF's involvement in the vulnerability, and sent
correction notices to editors/publishers. Sally also issued a cease/retract
request to the president and legal counsel UK-arm of a VoIP service provider
that had alerted its consumers of the "Apache Heartbleed Flaw". The ASF
received 1,200 press clips over this time period, vs. last month's clip count
of 2,259.
VII. Analyst Relations: we responded to 4 analyst queries, and have been
discussing a possible Apache-themed speaker/community event in the UK with
RedMonk. Apache was mentioned in 3 reports by Gartner, 2 reports by Forrester,
8 write-ups by GigaOM, 5 reports by Yankee Group, 4 reports by IDC, and 4
write-ups by 451 Research. In addition, Jonathan Ellis will be featured in an
upcoming issue of Hadoop Magazine dedicated to Apache Cassandra.
VIII. ApacheCon liaison: hats off to the Linux Foundation Events team and
Melissa Warnkin for their efficiency, professionalism, and follow-through in
advance of, during, and post-event.
IX. (Non-ASF) Industry Events and Outreach liaison: Sally is coordinating with
Melissa on the ASF booth at OSCON's Non-profit Pavilion. As Sally will be
unable to attend OSCON this year, Shane will be participating at the Expo in
her stead. Upayavira will also be attending OSCON to conduct Sponsor outreach
and provide booth coverage.
X. Newswire accounts: we have 16 pre-paid press releases with NASDAQ
GlobeNewswire through the end of the calendar year, and continue to receive
gratis news release distribution by Pressat (UK) with no pre-established
termination timeframe.
-----------------------------------------
Attachment 5: Report from the VP of Infrastructure [David Nalley]
New Karma:
==========
Andrew Bayer (abayer) was granted jenkins admin karma.
Finances:
==========
Infra spent or authorized to spend almost $3300 thus far in the new fiscal
year; all related to replacement hardware or service for hardware.
Operations Action Items:
========================
None
Short Term Priorities:
======================
* OSU Hardware failures We have a number of hosts that have degraded or dead
hardware in our Oregon colo. This is mixture of machines that are in and out
of warranty and involves machines that host both core services and less
important machines. Status is being tracked at:
https://pad.apache.org/p/osustatus
* Outage recovery Coming out of our outages we have substantial number of
remediation items. In some cases the service has been restored but is not back
to pre-outage levels of operation.
* Builds.a.o Stabilization of Jenkins is a primary concern. Much work has
happened from volunteers and contractors alike (see comments below in general
activity as to improvement.) We are still suffering from service failures
every couple of days at this point.
Long Range Priorities:
======================
* Monitoring Our monitoring still lacks the level of insight to provide
operationally significant information. Work continues on this front. Our new
monitoring system (Circonus) should come online in the next few weeks; but
much remains to be instrumented for it to be truly useful.
* Automation Slow progress continues on rolling out configuration management
in efforts to make our infrastructure better documented and more easily
reconstructed.
* Technical Debt Work is ongoing to prioritize services infrastructure
provides and to set expectations and service levels around the services.
* Resiliency I wish that I could say that much work has occurred here; but
most of the month has been focused on outage recovery. The beginnings of that
work has taken place in working to restore a stable platform.
(see the note around hardware at OSU)
General Activity:
=================
Infrastructure suffered three major outages in this reporting period. The
first involved the Buildbot host and a disk failure. CMS and Buildbot project
build were down for several days while the machine was rebuilt. The second
outage was the blogs.a.o service. You can see the details and remediation
steps that are being taken here: https://s.apache.org/blogspostmortem The
third was a 4 day outage of our mail services. You can see the results of the
post-mortem here: http://s.apache.org/mailoutagepostmortem As of this writing
there is still a significant backlog of email being processed. At current
rate, we expect the backlog to be cleared by May 16th.
The Buildbot host aegis lost a disk also and the machine was rebuilt over a
few days, changing from Ubuntu to FreeBSD 10. The CMS and project builds were
down whilst this happened. At the same time the Buildbot Master version was
upgraded to the latest release which caused some tweaks to the code and
project config files.
Infra has noted an increased level of concern regarding the CI Systems and in
particular the Jenkins side of builds. Some projects are concerned about the
level of support that Infra gives these systems. A combination of factors over
the last months has seen a decline in support - other higher priority services
taking up time, a decline in volunteer time, an increase in projects using the
systems and in parallel an increase in build complexity, all making for a
decline in available resources due to slave increases not happening in a
scaled manor to match. All this is being resolved as we speak and improvements
are being made; and there are many plans for the short/medium and long
term. The work done already is showing progress. In example on 2 May the
average load time for builds.a.o was 72.69 seconds and the average number of
builds in the queue was 65. On 13 May the average load time is down to 1.86
seconds and the average number of jobs in the queue is less than 4. Much work
remains to be done. For data see: http://people.apache.org/~hboutemy/builds/
Plans to address existing issues:
==================================
As has been noted infra ran into a number of problems bringing a number of
key services back into use. There are a number of planned steps that are
either remedial or work around building a more robust foundation. All of
these tie back into the long term priorities you see above.
Below are things I have requested one or more contractors:
* SLAs - We're dividing up services into various criteria. Failures happen,
but our level and rapidity of response as well as the degree to which we
engineer for failure must be measured against how critical the service
is. The current plan is to submit the finished work to the President for
review and discussion with an audience he deems appropriate.
* Prioritization of hardware replacement - New hardware doesn't guarantee
against an outage. However, continuing to test the mean time between
failure for underlying hardware tends to increase risk on average. Along
with this prioritization; I've asked that each of the services being
replaced be done by a person who isn't the 'primary' for that service.
That list is not yet complete, but is being worked on.
* Documentation - Currently the quality varies from service to service.
Some of our documentation is clearly out of date, some is decent. My
experience is that most documentation suffers from bitrot in any
organization. However; I've requested multiple folks to bring our docs
for various services up to a usable state. I've also requested for
folks other than those who produced or will be producing the documentation
to review the documentation and use it to ensure it is accurate and adequate.
* Backups - In general, our backups, where they've been happening, have been
sufficient. We've already had work around documenting restoration from backup
get committed to our docs in SVN. Additionally short term tasks have been
handed out about establishing, verifying, or restoring backups as well as
checking that against the services and documentation. There's also tasks in
place to work on speeding up our restore timelines.
* Automation - We possess a lot of operational automation (scripts and other
tools that allow us to create or subscribe to lists, create users, etc.) We
have bits and pieces of infrastructure automation - but it's not widespread.
In the three outages we've experienced catastrophic failure of the hardware
resulting in the need to rebuild the service from scratch. Virtually all of
the moving pieces involved manual processes from OS installation to service
configuration. That dramatically increased our time to recovery; as well as
being prone to user error. To that end; I've requested the following:
- Consolidate the number of platforms we support for core services. We
currently have Solaris, Ubuntu, two major versions of FreeBSD. I've
asked for a single version of Ubuntu and a single version of FreeBSD
to be adopted across all of our non-build and non-PMC infrastructure.
- Deploy an automated OS installation tool - During the mail outage we
had to get smarthands in the datacenter to burn a OS install DVD and
deploy a fresh operating system twice. This meant that a ten minute
task turned into more than hour in each case. I've set the criteria
that we be able to deploy our installs over the network and control
booting and other functions via an out-of-band management tool such
as IPMI. We must also be able to host our own package repositories.
- Configurations management - We currently have puppet deployed but it
isn't widely used within our infrastructure. Puppet permits you to
declare state in it's domain specific language that controls how a
machine is configured; what software is installed as well as collect
data on the machine itself. Puppet also enforces state; and this
enforcement is, quite frankly, better than documentation. Even if a
machine is completely destroyed, by having done the work in puppet we,
know the exact state of the machine and can deploy that exact
configuration back to a new machine in a matter of moments. To that end
I have planned the following items:
- Training - Most of the infra contractors have not used puppet in
anger. Beginning in the next few weeks; they'll make use of some
gratis online training from Puppetlabs with plans for attending
a hands-on class within 6 weeks. (budget-willing)
- Mandatory use for new services. I've asked that all new work and
services being stood up must be done using puppet.
- Service restoration. For core services that have failed recently.
we've either updated documentation or have tasks to do so. I've
requested tasks for translating that into puppet manifests to
dramatically reduce our mean time to recovery. For services that
will move to new hardware; if that involves the recreation of the
service I've asked that be done via config management as well.
- Base OS deployment. The base OS deployment at the ASF is very
well documented. In the case of FreeBSD it's ~26 individual
manual steps that must be executed every time. In conjunction
with work on an automated OS install; I've asked that all of the
base OS deployment and configuration be automated via puppet.
- Monitoring - put simply, our monitoring does not currently provide enough
insight. In example, we did not know about the failing hardware underlying
our mail service. According to our monitoring, things were fine. This isn't
to say that knowing about it would have prevented the outage, but I would
at least like the advantage of timely knowing about it. As mentioned
elsewhere; when smarthands were working on our equipment they noted
that many of our servers were complaining about hardware problems.
Monitoring is largely grunt work; knowing what to monitor for each service
is something that the contractors can rattle off. Actually setting up
monitoring is a large time sink. We currently have a volunteer doing a good
chunk of work; and my plan is to temporarily (3-6 month timeframe)
supplement that with an outside contractor who is already familiar with
our monitoring system and puppet.
None of the above prevents failure. It might give us an edge in detecting that
a failure is about to occur, or permit us to drastically reduce our time to
recovery; but it does not actually keep bad things from happening. The longer
term piece of this puzzle is to begin engineering our most important services
to be more redundant or more fault tolerant. Most of our services are not
setup this way. Our first target is going to be the mail service; we are doing
this for two reasons. First our experience with the mail backlog and the hoops
we had to clear to empty that backlog suggest that we aren't very far from the
limits of our current architecture. Second, as you've seen in the past few
weeks, a mail outage is absolutely crippling for the Foundation.
That said, please understand, that the problems we have, are not going to be
solved in the short term. By the end of the quarter I hope to be able to
report that we have a good start on these initiatives, but this is a long term
effort. Unless luck intervenes it's almost inevitable that we'll suffer
another outage this year. Hopefully we'll be in a better place to respond to
those outages as we go forward.
-----------------------------------------
Attachment 6: Report from the Apache Travel Assistance Committee [Gavin McDonald]
The Travel Assistance Committee (TAC) exists to help those that would like to
attend ApacheCon and/or other ASF Sponsored events, but are unable to do so
for financial reasons.
Overall Activity since last report
----------------------------------
Now that the data has been collated and analyzed we have the following stats.
* TAC funded 15 successful applicants at ApacheCon NA 2014 in Denver.
* COMMENTARY ON FINANCIALS & STATS ACCOUNTING/REPORTING
* Beginning in 2013, TAC has started asking for post-conference feedback from
successful applicants in an attempt to improve TAC's role in events such as
ApacheCon. To date 12 TAC'ers responded with raw feedback. This now resides
within the private TAC repos and is open for discussion on travel-assistance@
list.
* This year TAC is also pursuing the initiative to further promote TAC
activities through applicants blogging... to date we have received one blog
entry.
* TAC are working with press@ in preparation for a press release for ApacheCon
EU.
* In preparation for ApacheCon EU 2014 TAC are working more closely with the
Linux Foundation to ensure that the opening call for TAC funding is widely
disseminated.
How has the community developed since the last report?
------------------------------------------------------
No new members have joined TAC since last reporting. There are 12 Subscribers
to the TAC mailing list. ( No change on last month)
(These 12 are pretty much the same 12 for the last 2 years.)
TAC are looking for new members to help! Ideally another 2 or 3 ASF Members.
Budget:
-------
To supply 2 ApacheCons and up to 2 smaller events we request the same budget
as last year - $50,000
Future Events:
--------------
ApacheCon EU is the next event TAC are supporting. Discussions are under way
on list. Any member that wants to help out are welcome, see the resources
section for details.
ApacheCon NA 2013:
Now that the data has been collated and analyzed we have the following stats.
* TAC funded 15 successful applicants at ApacheCon NA 2014 in Denver.
* Budget Actuals for ACNA 2013:
- Hotel cost us $13,145,60 ==~ 7,804.79 GBP
- Flights cost us GBP 11,305.48
- Subsistence Money for 9 people, USD 100 each GBP 557.93
- Welcome Meal for all TAC recipients, USD 653 GBP 405.35
- Batteries for audio recorders, USD 14.52 GBP 8.75
- - Total Cost of ACNA for TAC = GBP 20081.30 == USD$ 33,825.68
* Beginning in 2013, TAC has started asking for post-conference feedback from
successful applicants in an attempt to improve TAC's role in events such as
ApacheCon. To date 12 TAC'ers responded with raw feedback. This now resides
within the private TAC repos and is open for discussion on travel-assistance@
list.
* This year TAC is also pursuing the initiative to further promote TAC
activities through applicants blogging... to date we have received one blog
entry.
* TAC are working with press@ in preparation for a press release for ApacheCon
EU.
* In preparation for ApacheCon EU 2014 TAC are working more closely with the
Linux Foundation to ensure that the opening call for TAC funding is widely
disseminated.
Resources :-
www: https://cwiki.apache.org/confluence/display/TAC/ ::
https://apache.org/travel
-----------------------------------------
Attachment 7: Report from the VP of W3C Relations [Andy Seaborne]
Nothing to report this month.
-----------------------------------------
Attachment 8: Report from the Apache Legal Affairs Committee [Jim Jagielski]
Nothing of note to report this month. Work on TCK clarification and
iCLA "compatibility" with "public domain" software and the US government
are ongoing.
-----------------------------------------
Attachment 9: Report from the Apache Security Team Project [Mark Cox]
There continues to be a steady stream of reports of various kinds
arriving at security@ in April. These continue to be dealt with by
the security team.
April 2014
1 Support question
2 Phishing/spam/proxy/attacks point to site "powered by Apache"
2 Security vulnerability question, but not a vulnerability report
9 Vulnerability reports to security@apache.org
3 [website] (3 closed, invalid)
1 [axis]
1 [maven] (closed, invalid)
1 [httpd]
1 [solr]
1 [poi]
1 [struts]
9 Vulnerability reports to projects own security lists
6 [struts] (1 closed, not issue)
1 [cloudstack]
1 [hadoop] (closed, invalid)
1 [tomcat]
-----------------------------------------
Attachment A: Report from the Apache Abdera Project [Ant Elder]
-----------------------------------------
Attachment B: Report from the Apache Allura Project [Dave Brondsema]
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.
Project Status
--------------
Allura graduated to a TLP in March. Development continues at a moderate pace.
Community
---------
* A test area was set up at forge-allura.a.o for Apache Labs
* We had a discussion about a logo, with several proposals
* Chris Tsai has offered to contribute end-user docs
* PMC diversification has increased due to changes in employment
* No new committers or PMC members since TLP formation (Apr 2014)
Community Objectives
--------------------
We would like to find and encourage new contributors to Allura. We also want to
explore if other Apache projects would be interested in using Allura.
We need to move our tickets from SourceForge to the Allura self-hosted site.
Releases
--------
Last release was Feb 2014.
-----------------------------------------
Attachment C: Report from the Apache Ambari Project [Yusaku Sako]
Apache Ambari simplifies provisioning, managing, and monitoring of Apache
Hadoop clusters.
Since the last report in Feb 2014, Ambari released 1.5.1, 1.5.0, and 1.4.4
which collectively included resolution of 1,239 JIRAs.
1.6.0 release is scheduled later this month.
There has been increased interest from the community surrounding Ambari's
pluggability of stacks (i.e., various Hadoop distributions) and
services. A Hackathon was held to deep dive on this topic on May 1.
Mailing Lists:
* user@ambari.apache.org: 212 subscribers (+11 since last report)
* dev@ambari.apache.org: 127 subscribers (+1 since last report)
Releases:
* 2014-04-23 1.5.1
* 2014-04-08 1.5.0
* 2014-02-20 1.4.4
Committers:
* 2014-04-21 Added Erin Boyd
* 2013-12-23 Added Jeff Sposetti
PMC:
* 2013-11-20 Added 37 initial PMC members upon establishing TLP
Community Events:
* 2014-05-01 Ambari-BigTop Hackathon
Issues:
* There are no board-level issues at this time.
-----------------------------------------
Attachment D: Report from the Apache Ant Project [Conor MacNeill]
Apache Ant is a Java based build tool along with associated tools. It
consists of 4 main projects:
- Ant core and libraries (Antlibs)
- Ivy - Ant based dependency manager
- IvyDE - Eclipse plugin to integrate Ivy into Eclipse
- EasyAnt - Ant and Ivy toolbox to support build processes
o Release Status
Core
---------
Ant 1.9.4 was released on May 5, 2014
AntUnit Antlib 1.3 was released on May 14, 2014
Ivy
-------
Ivy 2.3.0 was released on January 21, 2013
Ivy-DE 2.2.0 was released on November 22, 2013
The Ivy 2.4.0-RC1 release candidate was published on March 23, 2014
EasyAnt
-------------
The current release is still from the Incubator
0.9-Incubating.
o Migration to Git
The project recently voted to move the bulk of codebases from Subversion to
Git.
The project websites and sandbox will remain in Subversion. Some work will
need to be done to adapt build processes to the change.
o Committers and PMC
No changes since last report
o Community
No issues.
-----------------------------------------
Attachment E: Report from the Apache Attic Project [Gianugo Rabellino]
There has been an increase in activity at the Attic with WS-MUSE being
retired, and ESME, XMLBeans and stdcxx all being partially moved to the
Attic. Retiring the XML project has been identified as still having items
to complete.
The process of moving projects to the Attic has been simplified by
splitting into two stages - retiring the project publicly, and freeing up
infrastructure resources. My hope is that this will decouple the essential
parts of moving to the Attic from the clean up.
In moving XMLBeans to the Attic, we've noticed that one commit has
occurred after the board removed the PMC in July. This commit does not
appear to be of concern[1] and SVN has now been made read only for XMLBeans.
The project has put a resolution in front of the board to change the chair.
[1] http://svn.apache.org/viewvc?view=revision&revision=1572882
-----------------------------------------
Attachment F: Report from the Apache Avro Project [Scott Carey]
Apache Avro is a cross-language data serialization system.
== Issues ==
There are no issues that require the board's attention at this time.
== Community ==
Committer activity has slowed a bit in the last quarter. User
questions and bug reports have not flagged, and I expect committer
activity to speed up again soon.
In Q1, 80 Jira issues were files and 33 resolved.
Mailing list activity is steady, with a few hundred messages total per month.
Two new committers were added this quarter: Christophe Taton and Rob Turner.
No new PMC members have been added since 9/2012.
== Releases ==
Avro 1.7.6 was released January 22, 2014.
-----------------------------------------
Attachment G: Report from the Apache Buildr Project [Alex Boisvert]
-----------------------------------------
Attachment H: Report from the Apache Cassandra Project [Jonathan Ellis]
Cassandra is a distributed database providing massive scalability,
high performance, and high availability.
Releases:
1.2.15 02 Feb 2014
2.0.5 06 Feb 2014
2.1 beta1 19 Feb 2014
2.0.6 09 Mar 2014
1.2.16 30 Mar 2014
2.0.7 17 Apr 2014
2.1 beta2 04 May 2014
Development:
2.1 is feature complete with optimized repair [1] and off-heap
memtables [2] joining user-defined types [3] and collection indexing
[4]. Counters have been rewritten [5], and compaction has been tuned
to be page-cache-aware [6]. We expect the first release candidate
this month.
Community:
Tyler Hobbs was added as committer on 27 Feb 2014.
The last PMC addition was Jake Luciani in August 2013.
[1] https://issues.apache.org/jira/browse/CASSANDRA-5351
[2] https://issues.apache.org/jira/browse/CASSANDRA-6694
[3] https://issues.apache.org/jira/browse/CASSANDRA-5590
[4] https://issues.apache.org/jira/browse/CASSANDRA-4511
[5] https://issues.apache.org/jira/browse/CASSANDRA-6504
[6] http://www.datastax.com/dev/blog/compaction-improvements-in-cassandra-21
-----------------------------------------
Attachment I: Report from the Apache Clerezza Project [Hasan Hasan]
DESCRIPTION
Apache Clerezza is an OSGi-based modular application and a set of components
(bundles) for building RESTFul Semantic Web applications and services.
ISSUES FOR THE BOARD
There are no issues requiring board attention at this time.
RELEASE
Latest release (partial-release-20130710) was created on 10.07.2013
Releases as karaf features are planned and being worked on.
ACTIVITY
Various improvements and bug fixes in source codes including:
- Triple Collection Provider:
- Exposing QueryableTcProvider as an additional service besides
(Weighted)TcProvider
- Upgraded jena dependencies:
jena-core 2.11.0 --> 2.11.1
jena-arq 2.11.0 --> 2.11.1
jena-iri 1.0.0 --> 1.0.1
jena-tdb 1.0.0 --> 1.0.1
- Migration to git:
- Adjusted SCM section in parent/pom.xml to reflect the switch from svn
to git
- Adjusted README.txt to no longer mention incubator
- Performance improvement a.o. by enabling garbage collector to gain
memories back from unreferenced BNodes
- Usability improvement (GUI for managing graphs)
- Stability improvement (no longer depending on bundle startup order)
- Improvement in the support for Virtuoso Storage Provider:
- Various bug fixes, improved performance and added a packed launcher
(while bundle lists in provisioning are still to come).
COMMUNITY
Latest change was addition of a new committer and PMC member on 16.08.2013
INFRASTRUCTURE
- Website update
- Published DOAP file
-----------------------------------------
Attachment J: Report from the Apache Click Project [Malcolm Edgar]
-----------------------------------------
Attachment K: Report from the Apache Cocoon Project [Thorsten Scherler]
Apache Cocoon 3 is a major rewrite of Cocoon 2.2. Like Cocoon 2 it is based
around the concept of pipelines and sitemaps and it is very similar to Cocoon
2.2 in many respects but is slimmed down and designed to be easily used with
Java code (= no frameworks required!). On top of this, Cocoon 3 has the goal
of becoming the best available platform for RESTful webservices and web
applications.
Issues needing board attention:
None.
Changes in the PMC membership:
None.
Last modified: 2012/10/21 (change of PMC chair)
Community
Traffic on users and devs list had been busier then the last quarter. Some
users asked about different issues in the different versions of cocoon.
Various devs attended the questions and provided solutions.
We had problems with a jira spammer "ROY Assink" which open/comment/... on
issues with spam messages, different PMC member removed the comment and
reverted the doing.
Releases
2.1 has been released on 2013/03/20.
Development
None
Security issues reported:
None.
Progress of the project:
We need to release a new version of cocoon 3 and cocoon 2.2 but still no
committer has stepped up yet to do so.
-----------------------------------------
Attachment L: Report from the Apache Community Development Project [Luciano Resende]
The Community Development PMC is responsible for helping people become
involved with Apache projects.
Project Status
--------------
We have submitted via the ASF President, a budget that includes GSoC income
and expenses as well as money related to helping with small events (Event in a
Box).
Other then that, there are no issues requiring board attention at this time.
PMC changes
-----------
A new PMC member is being discussed/voted, but the latest official addition
has been Suresh Marru on 2013-04-26.
Google Summer of Code
---------------------
It’s GSoC time again, we have been accepted as a Mentoring Organization
and were given 42 slots for this year program.
Ulrich Stark has volunteered as GSoC Admin and has been doing an excellent
work handling all the Organization registration and mentoring registration
and validation with the respective PMCs and working trough the students
proposals and rankings.
Related to GSoC, the Stratosphere project which just joined Apache
and had also been accepted as a mentor organization for this year GSoC
will be receiving the GSoC mentor stipends and travel costs for their
attendance at the mentor summit via the ASF organization.
Also, there has been some discussions related to vouching for other open
source organizations that are new to GSoC, and currently the consensus with
the Community Development PMC seems to be not to vouch for external
organizations.
ComDev & Events
---------------
The ComDev PMC is now a "home" for some of the ConCom responsibilities. In the
last few months, Rich Bowen has been leading the organization of ApacheCon
Denver and based on all the reports I read from different members, this was a
very successful conference, with 43% more registrants compared to ApacheCon
2013. We are now working on the ApacheCon Europe which is going to happen in
Budapest in November 17 to 21.
Others
---------------
There have been some Apache PMCs that have brought to the attention of the
Community Development PMC that Google has changed the rules for Google Code,
which is where Apache Extra is hosted, and there is going to be issues related
to new downloads. We have had some discussions around the topic and we are
going to evaluate the possibility of finding a new home for Apache Extras.
-----------------------------------------
Attachment M: Report from the Apache Continuum Project [Brent Atkinson]
Apache Continuum is an enterprise-ready continuous integration server with
features such as automated builds, release management, role-based security,
and integration with popular build tools and source control management
systems.
Volume on the mailing lists and in the issue tracker was higher than the last
few periods, but still low as expected.
The last release was Continuum 1.4.1, on January 7, 2013. A release including
an important fix for the previously reported remote execution vulnerabilities
is still pending.
There have been no new committers since last cycle. The last committer was
added December 8, 2010 and the last PMC member was added on September 2, 2012.
-----------------------------------------
Attachment N: Report from the Apache CouchDB Project [Jan Lehnardt]
Description
Apache CouchDB is a database that uses JSON for documents, JavaScript
for MapReduce queries, and regular HTTP for an API.
Releases
1.5.1 (2014-04-08)
http://www.apache.org/dist/couchdb/notes/1.5.1/apache-couchdb-1.5.1.html
Recent Activity
• Started with weekly news with great success. Also available
at https://blogs.apache.org/couchdb/
• The community is in the process of creating a CoC and bylaws
• Ongoing work on the release 1.6.0. Actually voting on Apache
CouchDB 1.6.0-rc.4
• Working on the BigCouch merge from Cloudant
• Good progress in reviewing the rcouch merge
• Community work on migrating content to the new wiki started
• Translation work going well
Community
Including the following additions, CouchDB has 35 committers and 12 PMC members.
New committers:
Robert Kowalski (2014-03-28)
New PMC members:
Joan Touzet (2014-04-10)
Mailing list stats:
announce
175 subscribers (+24)
1 message since February (1)
user
1386 subscribers (-19)
750 messages since February (-336)
erlang
167 subscribers (+13)
1 messages since February (-13)
dev
599 subscribers (-3)
2630 messages since February (+1306)
commits
104 subscribers (0)
2655 messages since February (-80)
marketing
31 subscribers
312 messages since February
l10n
36 subscribers (+5)
16 messages since May (-191)
replication
54 subscribers (+7)
53 messages since February (+28)
Issues
None.
-----------------------------------------
Attachment O: Report from the Apache Creadur Project [Robert Burrell Donkin]
-----------------------------------------
Attachment P: Report from the Apache DeltaSpike Project [Mark Struberg]
Apache DeltaSpike is a portable JSR-299 CDI
(Contexts and Dependency Injection for Java) Extension library
which contains lots of useful tools and helpers
which are missing in the CDI core spec.
DeltaSpike is not a CDI-container itself, but a portable
Extension library which can run on all CDI-containers!
DeltaSpike is tested and runs on many Java EE Servers
like Apache TomEE, Red Hat JBoss Application Server,
JBoss Wildfly, Oracle WebLogic, Oracle Glassfish, IBM WebSphere, and also
on simple Servlet containers like Apache Tomcat or Jetty in combination
with either JBoss Weld or Apache OpenWebBeans.
Project Status:
Bugfixing goes on in the current code base.
Community is stable and active.
Releases:
last release:
deltaspike-0.6 on 2014-03-20
deltaspike-0.7 on 2014-05-03
We still hope to ship 1.0 pretty soon.
Community:
Mailing list activity remained high
Last Committer:
Rafael Benevides got voted as committer and form got submitted on 2014-05-06.
He is still not listed as committer though. Will need to check with infra.
Gerhard Petracek got voted in as new DeltaSpike PMC Chair taking over from
Mark Struberg
Issues:
There are no issues requiring board attention at this time.
-----------------------------------------
Attachment Q: Report from the Apache DirectMemory Project [Raffaele P. Guidi]
Apache DirectMemory is an off-heap cache implementation for the JVM
* General Information
Development and mailing lists traffic are mostly quiet, an attempt is being
made to revive the integration with JCS thread
* Issues
No known issues at the time
* Committers or PMC members change
Last added PMC PMC member was Noctarius (Cristoph Engelbert) on 2013-09-25
* Releases
Release 0.2 has seen the light on 2013-09-17
-----------------------------------------
Attachment R: Report from the Apache Directory Project [Pierre-Arnaud Marcelot]
The Apache Directory Project provides directory solutions entirely written
in Java. These include a directory server, which has been certified as
LDAPv3 compliant by the Open Group (ApacheDS), Eclipse-based directory tools
(Apache Directory Studio) and a client API that can be used to communicate
with any directory server (Apache LDAP API).
-- Community --
* No new committers(last addition: January 2014)
* No new PMC members (last addition: October 2008)
* Mailing lists information:
* users@directory: 279 subscribers (278 in january)
* api@directory: 65 subscribers (62 in january)
* dev@directory: 178 subscribers (173 in january)
-- Current activity --
* Apache Directory LDAP API:
* Two releases during this quarter.
* Good activity
* Refactoring of extended operations system and implementation of the
WhoAmI extended operation.
* Additions of more controls (Server Side Sorting, DirSync).
* Apache Mavibot:
* One release during this quarter.
* Good activity
* Improved performances.
* Partial support of transactions coming soon.
* Apache Escimo:
* Low activity
* No releases yet.
* ApacheDS:
* One release during this quarter.
* Good activity.
* Major fixes around Kerberos & minor bug fixes.
* Apache Directory Studio:
* No releases during this quarter.
* Bug fixes.
* Preparation for a release scheduled next quarter
-- Releases --
* Two releases for Apache Directory LDAP API:
* Apache Directory LDAP API 1.0.0-M21 (March 13th 2014)
* Apache Directory LDAP API 1.0.0-M22 (April 22th 2014)
* One release for Apache Mavibot:
* Apache Mavibot 1.0.0-M4 (March 13th 2014)
* No releases for Apache Escimo.
* One releases for ApacheDS:
* ApacheDS 1.0.0-M16 (March 13th 2014)
* No releases for Apache Directory Studio.
-----------------------------------------
Attachment S: Report from the Apache Empire-db Project [Francis De Brabandere]
Apache Empire-db is a relational database abstraction layer that allows
developers to take a more SQL-centric approach in application development
than traditional ORM frameworks. Its focus is to allow highly efficient
database operations in combination with a maximum of compile-time-safety
and DBMS independence.
Progress of the project
During the last three months there have been no noteworthy changes to the
project.
The project team is answering user questions and provides small
improvements which are collected for an upcoming release.
Changes in committers or PMC members
There have been no changes in committers or PMC members during the last
months.
Issues
There are no issues that require the board's attention at this time.
Releases
NONE
-----------------------------------------
Attachment T: 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.3.0 was released on September 26, 2013.
* Release 1.4.0 is currently on the way.
ACTIVITY
* We have had some new users on the lists but activity on the mailing list
is still rather low.
* We got some more patches for the cpp-binding from external contributors which
have been merged.
COMMITTERS OR PMC MEMBERS CHANGE
* No changes regarding PMC or committers composition since graduation
in January 2013.
* Our committer and user base is still quite small. We were able to get
exactly three PMC votes for the last release.
-----------------------------------------
Attachment U: Report from the Apache Flume Project [Arvind Prabhakar]
DESCRIPTION
Apache Flume is a distributed, reliable, and available system for
efficiently collecting, aggregating, and moving large amounts of log
data to scalable data storage systems such as Apache Hadoop's HDFS.
RELEASES
* The last release of Flume was version 1.4.0, released on July
2, 2013.
* Work is currently underway for the next release of Flume, version 1.5.0.
CURRENT ACTIVITY
* Development activity continues with steady stream of issues being
logged and resolved.
* A total of 67 issues have been filed, and 43 issues have been
resolved between the period starting February 7, 2014 and May 3,
2014.
* Approximately 790 messages were exchanged on the dev list in the
past three months, while a total of 266 were exchanged on the user
list in this period.
COMMUNITY
* Wolfgang Hoschek and Roshan Naik were added as committers to the
project on September 24, 2013.
* No new additions were made to the PMC on the project since it
graduated from Incubator.
* PMC member affiliations have changed. The current affiliations are:
- Apple: 1
- Cloudera: 9
- CyberAgent: 1
- Maas Global Solutions: 1
- Magnify Consulting: 1
- Motorola: 1
- ScalingData: 1
- Vanderbilt University: 1
- Other: 4
* Currently there are:
- Total of 230 subscribers to the developer list
- Total of 552 subscribers to the user list
- Total of 24 committers
- Total of 20 PMC members
ISSUES
* There are no issues requiring board attention at this time.
-----------------------------------------
Attachment V: Report from the Apache Forrest Project [David Crossley]
Apache Forrest mission is software for generation of aggregated multi-channel
documentation maintaining a separation of content and presentation.
Issues needing board attention:
None.
Changes in the PMC membership:
None.
Last modified: 2013-04-08
Most recent addition: 2009-06-09
New committers:
None.
Most recent addition: 2009-06-09
General status:
The most recent release is 0.9 on 2011-02-07.
No activity on the user mail list.
The only activity on the dev mail list was one PMC member attending to an
alert from our zone server.
On the private list there was some discussion among four PMC members, so we
do know that people are still present.
Security issues reported:
None.
Progress of the project:
None.
-----------------------------------------
Attachment W: Report from the Apache Giraph Project [Avery Ching]
Giraph is a Bulk Synchronous Parallel framework for writing programs
that analyze large graphs on a Hadoop cluster. Giraph is similar to
Google's Pregel system.
Project releases
1.1.0 - We have delayed this release until Roman finds some time to work on it.
Overall project activity since the last report
Project activity has remained steady. Not much else to report here.
When were the last committers or PMC members elected?
We as happy to report that we added a PMC member (Maja Kabiljo - 4/22/2014) and a
new committer (Pavan Kumar 4/22/2014) since the last report.
New community development
We recently held a Graph and Iterative Analytics meetup at Facebook in
May. It was a well attended event with lots of interest in Giraph.
Mailing list members
user@ 379 -> 418
dev@ 231 -> 242
-----------------------------------------
Attachment X: Report from the Apache Gora Project [Lewis John McGibbney]
The Apache Gora open source framework provides an in-memory data model and
persistence for big data. Gora supports persisting to column stores, key
value stores, document stores and RDBMSs, and analyzing the data with
extensive Apache Hadoop MapReduce support.
Project Releases
The last release of Gora (0.4) was on 24th April, 2014.
This is a major release for the project with many improvements.
Overall Project Activity since last report
Project activity on the run up to the 0.4 release was excellent.
We've received a number of contributions from
non-pmc/committers which is really positive.
One such individual is now part of our PMC.
The Gora PMC recently VOTE'd to move to Git
as primary SCM. Kudos to Jake Farrell and Infra
for ridiculously quick turnaround on migration.
When were the last committers or PMC members elected?
Alparslan Avci (alparslanavci) was elected as PMC member and committer
on 2014-04-04 (yyyy-mm-dd).
How has the community developed since the last report?
Gora has featured in Black Duck Software's Open Source
Delivers blog with a guest post. Gora also featured in
the London HBase Users Group Meetup on 05/19/2014 mmddyyy.
A number of members were very engaged in both the 0.4
development drive and release review process. We continue
to go from strength to strength.
Mailing list members are as follows
user@: from 57 --> 62
dev@: from 64 --> 74
commits@ from 26 --> 26
Changes to PMC & Committers
Alparslan Avci joined as PMC member and committer
on 2014-04-04 (yyy-mm-dd). Alparslan was one of a number of
community members who advanced the 0.4 release.
PMC and Committer diversity
We currently have committers from a wide variety of Apache projects
including, Nutch, Tika, OODT, Camel, Solr, Accumulo, Whirr, Hadoop,
Any23 & HBase (this is not an exhaustive list).
-----------------------------------------
Attachment Y: Report from the Apache Hama Project [ChiaHung Lin]
Apache Hama is a BSP (Bulk Synchronous Parallel) computing framework
on top of HDFS (Hadoop Distributed File System) for massive scientific
computations such as matrix, graph and network algorithms.
Project Status
--------------
Currently a new refactoring is underway which would address the
shortage of current framework such as fault tolerance computation.
Community
---------
The last PMC addition: Aug 4, 2013
The last committer addition: Sep 9, 2013
Community Objectives
--------------------
Before moving to 1.x, fault tolerance would be the main objective goal
at which the entire community aims.
Releases
--------
The last release of Hama (0.6.4) was on 5th March 2014.
-----------------------------------------
Attachment Z: Report from the Apache HTTP Server Project [Eric Covener]
Project Description
===================
The Apache HTTP Server Project is an effort to develop and maintain an
open-source HTTP server for modern operating systems.
Issues for the Board
====================
There are no outstanding issues that require the board's attention.
Releases
========
We've had one maintenance release of each in-service stream
sinc the last reporting period:
* 2.4.9 : Tagged on March 13, 2014.
* 2.2.27 : Released March 26, 2014
Bug reports
===========
241 bugs had activity, 85 new, 56 resolved
Community
=====================
No committer or PMC roster changes this reporting period.
* Date of last new committer : February 2014 (Yann Ylavic)
* Date of last new PMC member: July 2013 (Ben Reser)
Overall development activity is steady, but slow, with the focus on
the maintenance of 2.4.x which is making its way into various
httpd distributions.
-----------------------------------------
Attachment AA: Report from the Apache HttpComponents Project [Asankha Perera]
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.
Releases
HttpCore 4.3.2 GA was released on the 17th of February 2014
HttpAsyncClient 4.0.1 GA was released on the 24th of February 2014
HttpClient 4.3.3 GA was released on the 27th of February 2014
HttpClient for Android 4.3.3 was released on 20th of March 2014
HttpClient for Android is a port of Apache HttpClient, which can be deployed
on Google Android in parallel to the outdated version shipped with the
platform while remaining partially API compatible with Apache HttpClient 4.3.
Community
The community remains small but active, but has good user interaction on the
mailing lists
-----------------------------------------
Attachment AB: Report from the Apache Incubator Project [Roman Shaposhnik]
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 currently 34 podlings under incubation.
* Community
New IPMC members:
Ashutosh Chauhan
People who left the IPMC:
(None)
* New Podlings
Brooklyn
Slider
* Releases
The following releases were made since the last Incubator report:
phoenix-3.0.0-incubating
phoenix-4.0.0-incubating
tez-0.4.0-incubating
apache-vxquery-0.3-incubating
twill-0.2.0-incubating
hdt-0.0.1.incubating
metamodel-4.1.0-incubating
It took 2-13 days for the third IPMC vote to arrive.
Release VOTE start Third IMPC +1 Days
---------------------------------------------------------------------
phoenix-3.0.0-incubating April 01 April 03 3
phoenix-4.0.0-incubating April 01 April 03 3
tez-0.4.0-incubating April 01 April 04 4
hdt-0.0.1.incubating April 18 May 01 13
apache-vxquery-0.3-incubating April 15 April 17 3
twill-0.2.0-incubating April 03 April 07 4
metamodel-4.1.0-incubating May 03 May 04 2
* IP Clearance
Adobe donated BlazeDS to Apache Flex. BlazeDS was promised by Adobe prior
to entering the Incubator, but the donation was not cleared by Adobe until
after graduation.
In a separate proceeding, Adobe also donated selected popular articles
from the Adobe Developer Connection, plus the FlexPMD project, a version
of FDB that supports ActionScript Workers, the Tour de Flex app, the
Squiggly spell-checker library, the MXMLC specification, a prototype of a
code coverage tool and the Mobile Trader demo app.
Both donations contained extraneous files which were detected on review by
IPMC member and Flex PMC member Justin Mclean. Alex Harui, who was
managing the donation, promised to remove the files before import.
* Miscellaneous
ODF Toolkit has adopted the Alternate Release Voting Process.
DeviceMap has failed to report for two months now.
NPanday shows signs of concern. It consistently misses reporting
deadlines and even when reports arrive they don't seem to be signed
off by a mentor. On top of that, the development activity seems to
be quite low. IPMC will have to figure out what to do about it.
-------------------- Summary of podling reports --------------------
* Still getting started at the Incubator
Slider
Stratosphere
* Not yet ready to graduate
No release:
(None)
Community growth:
BatchEE
Blur
Droids
Celix
Sirona
Tez
* Ready to graduate
The Board has motions for the following:
Phoenix
Stratos
* Did not report, expected next month
DeviceMap
NPanday
----------------------------------------------------------------------
Table of Contents
BatchEE
Blur
Celix
DeviceMap
Droids
Hadoop Development Tools
NPanday
Ripple
Sirona
Stratosphere
Tez
Twill
Phoenix
----------------------------------------------------------------------
--------------------
BatchEE
BatchEE projects aims to provide a JBatch implementation (JSR-352) and a
set of useful extensions for this specification.
BatchEE entered the incubator on 2013-10-03.
Three most important issues to address in the move towards graduation:
1. Get more contributors/committers
2. Get more adoption
3. Get more activity on the list maybe
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
No
How has the community developed since the last report?
We have 3 active committers.
We also started to get some external contributors even if it is still a
bit shy.
How has the project developed since the last report?
Project seems to start to be stable and some nice feature enhancements
have been done. People are starting to use BatchEE in production.
Date of last release:
We shipped our first release (0.1-incubating) on 2014-04-06
When were the last committers or PMC members elected?
No new committers yet, but one contributor is on our radar.
Signed-off-by:
[ ](batchee) Jean-Baptiste Onofré
[ ](batchee) Olivier Lamy
[X](batchee) Mark Struberg
--------------------
Blur
Blur is a search platform capable of searching massive amounts of data
in a cloud computing environment.
Blur has been incubating since 2012-07-24.
Three most important issues to address in the move towards graduation:
1. It is unclear if we can get the Trademark assign document provided by
trademarks@ signed by Near Infinity. The company no longer exists.
2. Another Release
3. Community Growth
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
Other than the issue with the Trademark assignment listed above, no.
How has the community developed since the last report?
Can not get mail stats due to Apache Mail outage.
How has the project developed since the last report?
Apache Blur has become more stable over the past few months and we are in
position to release a stable version.
Date of last release:
2013-10-09 (However we are currently in the voting process now for a release.)
When were the last committers or PMC members elected?
2013-08-30
Signed-off-by:
[ ](blur) Doug Cutting
[X](blur) Patrick Hunt
[ ](blur) Tim Williams
--------------------
Celix
Celix is an OSGi like implementation in C with a distinct focus on
interoperability between Java and C.
Celix has been incubating since 2010-11-02.
Three most important issues to address in the move towards graduation:
1. We believe Celix is ready for graduation, the only thing left is making
sure all project metadata and (administrative) tasks are up to date.
2. Nothing
3. Nothing
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?
Since the last report Celix has gained two committers (Bjorn & Erik),
making the Celix community more diverse. Also a 1.0.0 release has been
released. Combined we believe that Celix is ready for graduation. One
downside is that in the last month activity on Celix mailinglist has been
slow, but we expect some increase in activity when we start graduation.
How has the project developed since the last report?
Two donations were mades and added to Celix. A shared memory
implementation for remote services and the an implementation of the event
admin specification. The event admin implementation was done in a GSoC
project. And a 1.0.0 release, focussing on stability, has been made.
Date of last release:
2014-02-24
2012-12-16
When were the last committers or PMC members elected?
2014-03-04 Erik Jansman elected as committer.
2014-01-08 Bjoern Petri elected as committer.
2013-01-07 Roman Shaposhnik joins as a mentor.
2012-03-20 Pepijn elected as committer.
Signed-off-by:
[x](celix) Marcel Offermans
[ ](celix) Karl Pauls
[x](celix) Roman Shaposhnik
Shepherd/Mentor notes:
Project looks pretty normal; report in readied, traffic on the mailing
list is ok. I don't see any particular cause for concern. Celix might need
to update the project site to reflect recent additions of the committers.
--------------------
Droids
Droids aims to be an intelligent standalone robot framework that allows to
create and extend existing droids (robots).
Droids has been incubating since 2008-10-09.
Three most important issues to address in the move towards graduation:
1. Activity
2. Name Search
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
None. The goal is to complete the name search this quarter.
How has the community developed since the last report?
No change. Name search is one big outstanding piece to complete, and it is
rather intimidating. It is hoped that one of the more experienced
individuals will have time to complete it this quarter. That should help
with participation once the final name is known.
How has the project developed since the last report?
No change.
Date of last release:
2012-10-15
When were the last committers or PMC members elected?
2012-05-07
Signed-off-by:
[x](droids) Thorsten Scherler
[X](droids) Richard Frovarp
--------------------
Hadoop Development Tools
Eclipse based tools for developing applications on the Hadoop platform
Hadoop Development Tools has been incubating since 2012-11-09.
Three most important issues to address in the move towards graduation:
1. We have to define and implement an effective approach to manage the
"client connections" to multiple clusters.
2. Migrate the existing functionality from master to make next releases.
3. Build Community
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
- None
How has the community developed since the last report?
- 36 mail exchanges have happened over the dev list.
How has the project developed since the last report?
- License issues[https://issues.apache.org/jira/browse/HDT-42] were
resolved, which enabled us for a new RC.
- Site has been modified to Markdown but we are awaiting CMS integration
https://issues.apache.org/jira/browse/INFRA-7677
- Released 0.0.1. incubating
Date of last release:
- May'2014
When were the last committers or PMC members elected?
- November 2013
Signed-off-by:
[X](hadoopdevelopmenttools) Suresh Marru
[ ](hadoopdevelopmenttools) Chris Mattmann
[x](hadoopdevelopmenttools) Roman Shaposhnik
Shepherd/Mentor notes:
HDT is off to a slow start, it appears partially due to some licensing
issues. Now that they have their first release out, I hope that they can
continue to create more iterative releases and provide a great tool.
--------------------
Ripple
At the moment the project is discussing its future. So far
almost no community could be grown and it is being discussed
if the project should become a sub-project of Apache Cordova.
The pros of this solution would be:
- Cordova is a consumer of Ripple
- Cordova is an active project and has a functional PMC
One con of this solution is that Cordova cannot guarantee
the success of the project. Also, the current Ripple code base
cannot be released, as there are some things to sort out (from
legal perspective, like the images cannot be redistributed).
Both communities have discussed this option and also the option
to move to GitHub. So far no agreement could be reached.
(Christian Grobmeier)
Signed-off-by:
[ ](ripple) Jukka Zitting
[X](ripple) Christian Grobmeier
[ ](ripple) Andrew Savory
--------------------
Sirona
Monitoring Solution.
Sirona has been incubating since 2013-10-15.
Three most important issues to address in the move towards graduation:
1. Get more committers
2. Get more activity
3. -
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
No
How has the community developed since the last report?
We got some great feedbacks from some other monitoring solution leaders.
How has the project developed since the last report?
We started to work on new advanced features like path tracking.
We reworked completely the javaagent to support Java 8 and be more
optimized.
Date of last release:
2013-12-16
When were the last committers or PMC members elected?
When the project was created.
Signed-off-by:
[ ](sirona) Olivier Lamy
[ ](sirona) Henri Gomez
[ ](sirona) Jean-Baptiste Onofre
[ ](sirona) Tammo van Lessen
[ ](sirona) Mark Struberg
--------------------
Slider
Slider is a collection of tools and technologies to package, deploy, and
manage long running applications on Apache Hadoop YARN clusters.
Slider has been incubating since 2014-04-29.
Three most important issues to address in the move towards graduation:
0. Podling name check
1. LICENSE and NOTICE review
2. Make releases
3. Add committers
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?
none
How has the project developed since the last report?
* Accounts, mailing lists, JIRA, subversion repository, and website
created.
* Initial code contribution completed.
* Name research has begun at PODLINGNAMESEARCH-47.
Date of last release:
none
When were the last committers or PMC members elected?
none
Signed-off-by:
[ ](slider) Vinod Kumar Vavilapalli
[ ](slider) Jean-Baptiste Onofré
[X](slider) Mahadev Konar
[X](slider) Arun Murthy
[X](slider) Devaraj Das
--------------------
Stratosphere
Stratosphere is an open source system for expressive, declarative, fast, and
efficient data analysis. Stratosphere combines the scalability and programming
flexibility of distributed MapReduce-like platforms with the efficiency, out-
of-core execution, and query optimization capabilities found in parallel
databases.
Stratosphere has been incubating since 2014-04-14.
Three most important issues to address in the move towards graduation:
1. Find a new project name
2. Release
3. Build an ASF community
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
None.
How has the community developed since the last report?
This is the first report. We got 2 Google Summer of Code students
and one new external contributor opened a pull request.
How has the project developed since the last report?
This is the first report. We are stabilizing the code base
for a new major release (0.5).
We are currently setting up the initial infrastructure at
the ASF incubator.
Date of last release:
2014-01-13 (no incubator release yet)
When were the last committers or PMC members elected?
Only initial committers.
Signed-off-by:
[ ](stratosphere) Sean Owen
[x](stratosphere) Ted Dunning
[ ](stratosphere) Owen O'Malley
[ ](stratosphere) Henry Saputra
[ ](stratosphere) Ashutosh Chauhan
[X](stratosphere) Alan Gates
Shepherd/Mentor notes:
Dev. list look pretty good, traffic is high and mentors participation is
certainly there.
--------------------
Tez
Tez is an effort to develop a generic application framework which can be used
to process arbitrarily complex data-processing tasks and also a re-usable set
of data-processing primitives which can be used by other projects.
Tez has been incubating since 2013-02-24.
Three most important issues to address in the move towards graduation:
1. Growing the community.
2.
3.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
None at this time.
How has the community developed since the last report?
No new PPMC members or committers added since the last report. We have
started getting steady contributions from some contributors and hope to
graduate them to committers within the coming months. There were around
10 non-committers that contributed to the past 2 releases of Tez.
How has the project developed since the last report?
Since the first week of February, 2014 (last report), we have had around
300+ jiras filed and 215+ jiras resolved. 2 releases were done in the past
3 months. 0.3.0-incubating was released in February and 0.4.0-incubating in
April.
Date of last release:
2014-04-05
When were the last committers or PMC members elected?
At project incubation. No new PPMC members or committers added since the
last report.
Signed-off-by:
[ ](tez) Alan Gates
[X](tez) Arun Murthy
[ ](tez) Chris Douglas
[ ](tez) Chris Mattmann
[x](tez) Jakob Homan
[ ](tez) Owen O'Malley
--------------------
Twill
Twill is an abstraction over Apache Hadoop YARN that reduces the complexity
of developing distributed applications, allowing developers to focus more on
their business logic
Twill has been incubating since 2013-11-14.
Three most important issues to address in the move towards graduation:
1. More committers from different organizations.
2. Regular Releases.
3. Increase adoption.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
None at this time.
How has the community developed since the last report?
Subscribers to the dev list up from 31 in January to 44 in May.
Three new contributors since last report.
How has the project developed since the last report?
40 new JIRA issues filed since last report (2014-02-01)
23 JIRA issues resolved since last report (2014-02-01)
Version 0.1.0-incubating released 2014-02-06
Version 0.2.0-incubating released 2014-04-22
Date of last release:
2014-04-22: 0.2.0-incubating
What are the plans for the next period?
Establish a cadence of monthly releases
Engage more members of the community to contribute actively
Improve documentation and website
When were the last committers or PMC members elected?
No new committers since incubation.
Signed-off-by:
[ ](twill) Arun C Murthy
[X](twill) Tom White
[X](twill) Patrick Hunt
[ ](twill) Andrei Savu
Shepherd/Mentor notes:
Justin Mclean (jmclean):
Dev list and JIRA active, mentors helping out, project has made
releases, no obvious issues for the project towards graduation that I
can see.
--------------------
Phoenix
Phoenix is an open source SQL query engine for accessing NoSQL data
stores such as Apache HBase. It is accessed as a JDBC driver and
enables querying and managing HBase tables using SQL.
Phoenix has been incubating since 12/11/2013.
Three most important issues to address in the move towards graduation:
1) Continue to make our users successful and prove the value of
Phoenix+HBase over other alternatives.
2) Continue to attract new users, contributors, and committers to the
project.
3) Become the defacto standard for accessing data stored in NoSQL stores.
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?
Both dev and user traffic is strong on the mailing list (780 and 187 mail
messages respectively). Work is underway by an engineer from Huawei to
add a new secondary indexing strategy called local indexing to Phoenix.
James Taylor gave a talk on Apache Phoenix at ApacheCon. Eli Levine and
James Taylor gave a talk on Phoenix at HBaseCon. James will also give a
talk at Hadoop Summit. Good discussions took place at the HBase
Hackathon on how to commonize the type system between Phoenix, HBase,
Hive, Impala, and Kite, as well as on how Continuity's transaction support
(soon to be open sourced) may be plugged into Phoenix. An interesting
discussion is underway on how Phoenix can be leveraged to get SQL
support for the Apache Accumulo project.
How has the project developed since the last report?
* Second release has been completed on 4/3/2014
* Third release has been completed on 4/4/2014
* Gabriel Reid was elected as a committer on 4/8/2014
* Graduation resolution passed on incubator general list on 5/4/2014.
Date of last release:
April 4, 2014
When were the last committers or PMC members elected?
Gabriel Reid was elected as a committer on 4/8/2014
Signed-off-by:
[X](phoenix) Michael Stack
[ ](phoenix) Steven Noels
-----------------------------------------
Attachment AC: Report from the Apache jUDDI Project [Kurt Stam]
jUDDI (pronounced "Judy") is an open source Java implementation of the
Universal Description, Discovery, and Integration (UDDI v3) specification for
(Web) Services. The jUDDI project includes Scout. Scout is an implementation
of the JSR 93 - Java API for XML Registries 1.0 (JAXR).
jUDDI
- Very low traffic on the mailing lists this quarter.
- There are now two cloud instances: one for users to test, the other is
meant to be a public UDDI registry, both running in the OpenShift cloud.
- Website is transitioned to SVNPubSub: http://juddi.apache.org/
Scout
- No release this period, not really any development took place.
- Very low volume of JAXR related questions on the mailing list.
Last PMC addition and new committer April 3, 2013 (Alex O'Ree)
Last Release jUDDI-3.2.0, Feb 5, 2014
There are no issues that require the boards attention at this time.
-----------------------------------------
Attachment AD: Report from the Apache Kafka Project [Jun Rao]
Apache Kafka is a distributed pub/sub system for efficiently collecting and
delivering a large number of messages to both offline and online systems.
Development
===========
We released Kafka 0.8.1 and 0.8.1.1, which include a few improved admin tools
and new features like log compaction. We are currently stablizing the new
producer, which provides better performance and a cleaner api. We are
finalizing the api and the design for the new consumer.
Community
===========
Lots of activities in the mailing list. kafka-user has 480, 450, 388 emails in
Feb, Mar and Apr, respectively (slightly less than 538 in Jan). kafka-dev has
1120, 1047, 1272 emails in Feb, Mar and Apr (slightly less than 540 in Jan).
There were three Kafka related talks in ApacheCon 2014. We last elected two
committers in Oct. 2013.
Releases
===========
0.8.1 was released on Mar 21, 2014 and 0.8.1.1 was released on Apr 29, 2014.
Infra
===========
The recent Apache mail server issue impacted many projects. I am sure there
will be some post-mortem on how to prevent this in the future. Could the
post-mortem results be shared with all PMCs?
-----------------------------------------
Attachment AE: Report from the Apache Knox Project [Kevin Minder]
# Description
The Knox Gateway is a REST API gateway for securing the Hadoop REST APIs.
# Issues
* None that require the board's attention at this time
# Status
* Completed cleanup of a number of the tasks required of graduated project.
* First release as a TLP Apache Knox 0.4.0 was complete.
# Releases
* 0.3.0: 2013-10-13 (Incubating)
* 0.4.0: 2014-04-21
# Development Activity
* Community is discussing new features following the 0.4.0 release
* Jira: 357 total, +15 -43 (last 30 days)
* Git (Source): 12 commits over last 30 days
* SVN (Site & Docs): 33 commits over last 30 days
# Community Activity
## Membership Changes
* None since graduation.
* Have not yet made adjustments to membership due to graduation
## Mailing List Activity
* user@knox: 1 messages over last 30 days
* dev@knox: 267 messages over last 30 days
-----------------------------------------
Attachment AF: Report from the Apache Lenya Project [Richard Frovarp]
The Apache Lenya CMS is a Cocoon based XML/XHTML content management
system.
Issues:
No board level issues at this time.
Development:
No new releases this quarter.
Last release: 2.0.4 on 2011-03-14
Community:
Last change to community was PMC addition in October 2011.
Activity:
After the special March report was submitted, additional PMC
members came forward indicating their participation in the project.
At this time, there is enough interest in the project to not
move it to the Attic.
-----------------------------------------
Attachment AG: Report from the Apache Libcloud Project [Tomaz Muraus]
Libcloud is a Python library that abstracts away the differences among
multiple cloud provider APIs.
Issues
There are no issues that require the board's attention at this time.
Releases
- Libcloud 0.14.1 has been released on February 8th, 2014
Community
- No new committers or PMC members have joined the team.
- We have applied for GSoC 2014 and we have received 1 slot. Student Rahul
Ranjan will work on Libcloud CLI project.
-----------------------------------------
Attachment AH: Report from the Apache Logging Project [Christian Grobmeier]
The Apache Logging Services Project creates and maintains open-
source software related to the logging of application behavior.
Currently there are no issues, which require the board’s attention.
- Community
Log4j 2 remains a very active project. The overall
community is healthy and friendly. We expect to add a new committer soon.
Log4cxx is still active at the Incubator.
A new Chainsaw release is currently blocked by this Infra-Ticket
(open since Oct 2011):
* https://issues.apache.org/jira/browse/INFRA-3991
The Logging project reconsiders the Chair role on a yearly
basis. The Community decided to stick with its current Chair.
In general, all subprojects are healthy.
- Project Branding Requirements
All components meet the branding requirements, except Chainsaw.
We will fix the branding with the next release.
- Last three community changes
* Matt Sicker joined as a Committer on Mar 01 2014.
* Nick Williams joined the PMC on Feb 19 2014.
* Remko Popma joined the PMC on Sep 28 2013.
- Releases
* Log4j 2.0 RC1 (Feb 17, 2014)
* Log4j Extras 1.2.17 (Oct 20, 2013)
* Log4j 2.0-beta9 (Sep 21, 2013)
- Subproject summaries
Log4j 2: Very active. A new RC is discussed.
Log4j 1: Almost no activity. A CVE was opened but hasn't been fixed yet.
Log4net: Less active, but healthy and maintained.
Log4cxx: Very active in the Incubator.
Log4php: Less activity.
Chainsaw: The ticket INFRA-3991 is blocking a new release:
https://issues.apache.org/jira/browse/INFRA-3991
-----------------------------------------
Attachment AI: Report from the Apache ManifoldCF Project [Karl Wright]
Project description
==============
ManifoldCF is an effort to provide an open source framework for connecting
source content repositories like Microsoft Sharepoint and EMC Documentum, to
target repositories or indexes, such as Apache Solr, OpenSearchServer or
ElasticSearch. ManifoldCF also defines a security model for target
repositories that permits them to enforce source-repository security policies.
Releases
========
ManifoldCF graduated from the Apache Incubator on May 16, 2012. Since then,
there have been seven major releases, including a 1.6 release on April 30,
2014.
Committers and PMC membership
=============================
The last committer and PMC member we signed up was Graeme Seaton (graemes), on
March 2, 2014. Other contributors have been approached, but have also
declined to accept consideration for possible committership. The most recent
of these encounters took place in September, 2013.
Mailing list activity
=====================
Mailing list has been active, with a wide range of topics. Most of our
connectors now have significant use cases and constituencies, and the
connector family continues to grow. Dev list comments for this period
centered around voting for the major 1.5 release, people looking for
integration advice, etc.
Committer and external contributions have been significant this cycle. I am
unaware of any mailing-list question that has gone unanswered.
Outstanding issues
==================
None known.
Branding
========
We have reviewed the site branding guidelines and believe we are now compliant
with these, with the possible exception of (TM) signs in logos from other
Apache products that don't have any such marks. Hopefully we will be able to
correct this issue
soon.
-----------------------------------------
Attachment AJ: Report from the Apache Marmotta Project [Jakob Frank]
Apache Marmotta, an Open Platform for Linked Data.
Apache Marmotta was founded in December 2012 and has graduated from
the Incubator in November 2013.
In April 2014, Apache Marmotta v3.2.0 was released. The next
maintenance release (v3.1.1) is expected in the upcoming weeks.
Traffic on the lists is stable. We have been approached by
"OverLOD Surfer", a research project, to discuss synergies, common
goals and ways to collaborate.
For the 2014 GSoC Program, Marmotta received 3 project proposals of
which one was finally accepted:
Qihong Lin: "Implementation of the LDP service for Apache Marmotta
based on SPARQL 1.1",
http://s.apache.org/rE
inspired by MARMOTTA-444
Of the other two, one was withdrawn by the student, the second was
not evaluated because only two mentors signed up from the Marmotta
community.
Subscribers to the projects mailing list:
dev@marmotta.a.o: 70 subscribers (+10 since last report, 2014-02)
users@marmotta.a.o: 76 subscribers (+10 since last report, 2014-02)
Releases
2014-04-09 (3.2.0)
2014-01-21 (3.0.1)
Committers & PMC
Peter Ansell (committer&PMC, 2013-06-24)
Raffaele Palmieri (committer&PMC, 2013-05-21)
Issues for the Board
There are no Board-level issues at this time.
-----------------------------------------
Attachment AK: Report from the Apache Mesos Project [Benjamin Hindman]
Apache Mesos is a cluster manager that provides resource sharing and
isolation across cluster applications.
## General ##
The state of the project seems healthy, another two releases have been
made since the last board report and continued increase in
contributors and committers.
## Releases ##
* Apache Mesos 0.17.0 (2014-01-23)
* Apache Mesos 0.18.0 (2014-04-01)
## Community ##
* Added 2 new committer and PMC members:
Ian Downes (idownes) on 2014-03-20
Till Toenshoff (tillt) on 2014-05-08
* 300/165 created/resolved JIRA issues in last 90 days.
* 103/46 created/resolved JIRA issues in last 30 days.
* 144 messages to user@mesos.apache.org (February - April), with
4,940 messages to dev@mesos.apache.org (a lot of which is from
Review Board and JIRA).
* There were two talks on Mesos at ApacheCon which we generally felt
was a big success.
* Twitter hosted an Aurora/Mesos Frameworks meetup as well as a
mini-conference where some members from the community talked about
Mesos (Tom Petr from Hubspot and Christina Delimitrou from
Stanford).
* We're working with the Linux Foundation to have a MesosCon during
LinuxCon in Chicago. Our CFP has completed and we'll be reviewing
the submissions ASAP and constructing the agenda.
## Issues ##
There are no issues requiring board attention at this time.
-----------------------------------------
Attachment AL: Report from the Apache Olingo Project [Stephan Klevenz]
* Briefly describe what your primary software product actually does.
Apache Olingo are libraries that implements the Open Data Protocol (OData).
Apache Olingo serves client and server aspects of OData protocol.
* When did the project last make any releases?
The latest release is version 1.2.0 and was built on 2014-03-24.
* Describe the overall activity in the project over the past quarter.
Olingo community is working on support for OASIS OData 4.0 standard and is
doing the maintenance for OData 2.0 which is already released. The project has
a healthy community and is getting more stakeholders. A new users mailing list
was created. Mailing list and Jira do show constant traffic.
* When were the last committers or PMC members elected?
The PMC is still initial after graduation in April 2014.
* PMC and committer diversity
PMC and committers build together an international team sponsored by various
companies (Microsoft, SAP, Tirasa).
-----------------------------------------
Attachment AM: Report from the Apache Oltu Project [Antonio Sanso]
DESCRIPTION
Oltu is a project to develop a Java library which provides an API
specification for, and an unconditionally compliant implementation of the
OAuth v2.0 specifications.
OAuth is a mechanism that allows users to authenticate and authorise access
by another party to resources they control while avoiding the need to share
their username and password credentials.
MILESTONES
Apache Oltu 1.0 was released on March 3rd.
CURRENT ACTIVITY
The core part of the project related to 'The OAuth 2.0 Authorization
Framework' (RFC 6749) is pretty stable due the fact RFC 6749 is now a
standard.
A stable version 1.0 was released on March 3rd. The current focus is on
extending the coverage for the IETF JOSE specifications e.g. JWS, JWE (that
are strictly correlated to OAuth 2).
Users activity is growing slowly but steadily (the user@ mailing list has got
new messages from new users)
COMMUNITY
PMC composition has not changed since graduation
We have voted one new committer since graduation
ISSUES
There are no issues requiring board attention at this time.
-----------------------------------------
Attachment AN: Report from the Apache Oozie Project [Mohammad Islam]
Apache Oozie is a system for managing and scheduling
workflows that run different types of Hadoop jobs
(such as MapReduce, Pig, Hive and Sqoop) as well as
system specific jobs (such as Java programs and shell scripts).
RELEASES
* Last release was Apache Oozie version 4.0.1, released on March/31/2014
* Next Apache Oozie version is WIP
CURRENT ACTIVITY
* Development activity continues as can be seen from the
following JIRA report: http://s.apache.org/k86 (since
last report, Feb 2014)
COMMUNITY
* PMC composition has not changed since last report.
* Committers composition has changed since last report. PMC added 1 new
committer.
* Currently there are:
- Total of 368 (+38) subscribers to the user list
- Total of 123 (+8) subscribers to the developer list
- Total of 15 committers (+1)
- Total of 12 PMC members
ISSUES
* There are no issues requiring board attention at this time.
-----------------------------------------
Attachment AO: Report from the Apache Open Climate Workbench Project [Michael James Joyce]
Apache Open Climate Workbench is a tool for scalable comparison of remote
sensing observations to climate model outputs.
Project Activity:
OCW development has seen a big increase since the last board meeting.
The mailing lists have been very active with development chatter.
User activity on the lists is still fairly minimal. Encouraging users to be
more active on the lists would be great for the project overall.
Issues for the Board:
None
When was the last release:
2013-10-11
When was the last committer or PMC member elected:
2013-06-21
-----------------------------------------
Attachment AP: Report from the Apache Perl Project [Philippe M. Chiasson]
-----------------------------------------
Attachment AQ: Report from the Apache POI Project [Yegor Kozlov]
Apache POI is a Java library for reading and writing Microsoft Office file
formats.
Releases
--------
There have been no releases in the last quarter.
The last release is 3.10-FINAL released on 8th February 2014
Community
---------
No new committers/PMC members added in the last quarter.
Last committer and PMC was added in December, 2013 (kiwiwings)
Project Status
---------
Apache POI continues to be an active project, both in terms of
community and development. Traffic on the mailing lists has been
steady in the last 3 months.
Most patches are applied without much delay.
General Comments
----------------
There are no issues that require Board attention.
-----------------------------------------
Attachment AR: Report from the Apache Qpid Project [Gordon Sim]
Apache Qpid™ is a project focused on creating software based on the
Advanced Message Queuing Protocol (AMQP), currently providing a
protocol engine library, message brokers written in C++ and Java, and
client libraries for C++, Java (including JMS), .Net, Python, Perl and
Ruby.
AMQP 1.0 became an ISO standard on the 1st May, 2014:
https://www.oasis-open.org/news/pr/iso-and-iec-approve-oasis-amqp-advanced-message-queuing-protocol.
* Releases:
Qpid 0.26 was released on the 19th Feb 2014[1].
Qpid Dispatch Router 0.2 was released on 14th April 2014.
Qpid Proton 0.7 was released on 29th April, 2014.
[1] The first release candidate for Qpid 0.28 was made available for testing
on the 25th April. A second release candidate is expected shortly.
* Community:
The main developer and user lists continue to be active. JIRAs are
being raised and addressed.
No new committers were added since last report (February 2014). The
last committer added was Pavel Moravec on 30th Aug, 2013.
Fraser Adams joined the PMC on 6th March, 2014.
* Issues:
There are no items requiring board attention at this time.
-----------------------------------------
Attachment AS: Report from the Apache River Project [Greg Trasuk]
Apache River is a Java-based Service Oriented Architecture, implementing the
Jini Specification and Jini Technology Starter Kit originally donated by Sun
Microsystems.
ISSUES FOR THE BOARD
There are no board-level issues at this time
RELEASES
Apache River 2.2.2 was released on November 18, 2013
Apache River 2.2.1 was released on May 2, 2013.
COMMUNITY
No new committers have been added since Nov of 2011.
There has been some discussion of the project’s health on the dev@ and users@
mailing lists, which has led to an effort to update the project’s build
architecture, in hopes of removing at least one barrier to participation. The
PMC is curious if there are any Apache resources to aid in community building.
Greg Trasuk has requested that the community nominate a new PMC Chair.
Discussions on a replacement Chair are under way. The board should expect a
resolution to change the Chair at the next board meeting.
ACTIVITY
Mailing lists and development have been reasonably active in the past few
months. 4 messages on users@ from Mar-Apr, and over 150 messages on dev@.
Six issues have been reported on Jira and four of those have been resolved.
-----------------------------------------
Attachment AT: Report from the Apache Roller Project [Dave Johnson]
Apache Roller is a full-featured, Java-based blog server that works
well on Tomcat and MySQL, and is known to run on other Java servers
and relational databases. The ASF blog site at blogs.apache.org runs on
Roller 5.0.2, Tomcat and MySQL.
Issues
No board issues at this time.
Releases
The latest release of Apache Roller is v5.0.2, which was released
on October 30, 2013, a security vulnerability and bug fix release.
Community
The Roller community continues to be rather quiet with low traffic that
mostly concerns bug fixes, code improvements and user support issues.
The last new PMC member and committer who joined is Glenn Mazza in
Nov 2012.
This quarter, like most recent quarters, there has been a slow but steady
stream of bug fixes, re-factorings and improvements to the Roller code
base, documentation and the wiki.
-----------------------------------------
Attachment AU: Report from the Apache Santuario Project [Colm O hEigeartaigh]
The Apache Santuario project is aimed at providing implementation of
security standards for XML.
There was one new release in the last quarter. A new major version (2.0.0) of
the Apache XML Security for Java project was released, after many months of
development work.
Nothing else to report, project activity remains quiet.
Last committer addition: Marc Giger, July 2012.
Last PMC addition: Marc Giger, April 2013.
-----------------------------------------
Attachment AV: Report from the Apache SIS Project [Adam Estrada]
Apache Spatial Information System (SIS)
Apache SIS is a spatial framework that enables better representation of
coordinates for searching, data clustering, archiving, or any other
relevant spatial needs.
Development:
A new Java Specification Request for Unit of Measurement has been
approved [1], on which we plan to participate. Unit of measurements are
part of Coordinate System Axis definitions, and thus needed at the core
of SIS.
A JDK 8 branch has been created for exploring new functionalities and
for Google Summer of Code JavaFX development. The releases however still
target JDK 6.
Community:
Roshan Elvitigala's proposal was accepted by Google Summer of Code 2014 [2]
Began discussions to add Martin as the SIS Chair/VP
Branding:
No new activity
Issues:
None
Releases:
Apache SIS 0.4 [3]
Press:
Martin participated in the OGC meeting in Arlington, Virginia [4][5]
Martin presented at ApacheCon North America [6]
[1] https://jcp.org/en/jsr/detail?id=363
[2] http://s.apache.org/Isq
[3] http://s.apache.org/oke
[4] http://s.apache.org/HOi
[5] http://s.apache.org/PY6
[6] http://events.linuxfoundation.org/sites/events/files/slides/2014-04.pdf
-----------------------------------------
Attachment AW: Report from the Apache Spark Project [Matei Zaharia]
Apache Spark is a fast and general engine for large-scale data processing. It
offers high-level APIs in Java, Scala and Python as well as a rich set of
libraries including stream processing, machine learning, and graph analytics.
Project status:
The project is closing out the work for its 1.0.0 release, which will be a
major milestone introducing both new functionality and API compatibility
guarantees across the 1.X series. We’ve had one release candidate posted and
are working on the next after a period of heavy QA. The project continues to
see fast community growth — over 100 people submitted patches for 1.0.
Some of the major features in 1.0 include:
- A new Spark SQL component for accessing structured data within Spark
programs
- Java 8 lambda syntax support to make Spark programming in Java easier
- Sparse data support, model evaluation, matrix algorithms and decision trees
in MLlib
- Long-lived monitoring dashboard
- Common job submission script for all cluster managers
- Revamped docs including new detailed docs for all the ML algorithms
- Full integration with Hadoop YARN security model
- API stability across the entire 1.X line
Releases:
Our last few releases were:
Apr 9, 2014: Spark 0.9.1
Feb 2, 2014: Spark 0.9.0-incubating
Dec 19, 2013: Spark 0.8.1-incubating
Sept 25, 2013: Spark 0.8.0-incubating
Committers and PMC:
We just opened votes for two new committers and PMC members on May 12th.
The last committers and (podling) PMC members were added on Dec 22, 2013
-----------------------------------------
Attachment AX: Report from the Apache Subversion Project [Greg Stein]
* Overview
No board-level issues at this time, since our report in February.
* Community
No changes in committers or PMC makeup. Our last committer was added
in July 2013. Our last PMC addition was March 2012.
The Subversion Live conferences hosted by WANdisco were held in
early May. An elego-hosted hackathon will be held in Berlin in
June, and a hackathon hosted by WANdisco is being assembled for
August. Historically, these have been well-attended and well-
regarded by the Subversion committers.
* Releases
In February, the community began preparing an alpha release of
1.9.0. That alpha had several problems and was pulled. 1.9.0-alpha2
was eventually released on April 14, 2014. Discussions are being
held regarding finalizing "trunk", branching, and beginning the
release process. Much of the discussion will occur at the above-
mentioned hackathon in June with summaries posted to the list for
non-attendees to participate (as is typical with Subversion
hackathons and the face-to-face discussions).
Since our report in February, Apache Subversion 1.8.9 was released
on May 14, and 1.7.17 was released on May 19.
-----------------------------------------
Attachment AY: Report from the Apache Syncope Project [Francesco Chicchiricco]
Apache Syncope is an Open Source system for managing digital identities
in enterprise environments, implemented in JEE technology.
Status
There are no outstanding issues requiring board attention.
Community
In the last quarter the traffic on user@ and dev@ ML was rather low - while
private@ was instead higher than usual, due to new committer / PMC member
votes and security flaw handling.
We have successfully handled our first security flaw (CVE-2014-0111) and
added a security page to the project's website.
Last committer addition (Andrea Patricelli) is dated March 2014
Last addition to PMC (Guido Wimmel) is dated April 2014.
Releases since last report
* 1.1.6 (Feb 22nd, 2014)
* 1.1.7 (Apr 11th, 2014)
* 1.0.9 (Apr 11th, 2014)
-----------------------------------------
Attachment AZ: Report from the Apache Tajo Project [Hyunsik Choi]
Apache Tajo is a robust big data relational and distributed data warehouse
system for Apache Hadoop. Tajo is designed for low-latency and scalable ad-hoc
queries, online aggregation, and ETL (extract-transform-load process) on
large-data sets stored on HDFS (Hadoop Distributed File System) and other data
sources. By supporting SQL standards and leveraging advanced database
techniques, Tajo allows direct control of distributed execution and data
flow across a variety of query evaluation strategies and optimization
opportunities.
Status
===============
There are no outstanding issues requiring board attention.
Community
===============
Keuntae Park, one of the PMC members, presented the real usecases of Apache
Tajo in ApacheConf North America 2014. Also, Hyunsik Choi, PMC chair, was
invited to Hadoop Summit North America 2014 and Big Data Camp 2014 LA.
These presentations will be on the early and mid of June respectively.
Mailng list:
* dev@tajo.apache.org: 85 subscribers (first report)
* user@tajo.apache.org: 25 subscribers (first report)
Releases
===============
We released 0.8.0 in May 1, 2014. 0.8.0 is the second major release
including lots of improvements, bugfix, and new features.
The last committers or PMC members elected
===========================================
Last new committer: Min Zhou <mzhou@apache.org> on 2014/04/01.
-----------------------------------------
Attachment BA: Report from the Apache TomEE Project [David Blevins]
Apache TomEE delivers enterprise application containers and services based on,
but not limited to the Enterprise JavaBeans Specification and Java Enterprise
Edition Specifications.
Significant work was done by the project around formalizing desired policy and
documentation for security vulnerabilities. To date all of these have been in
sibling projects and not in TomEE or OpenEJB specifically. Regardless users
have come to expect TomEE have the same responsiveness, specifically for
Tomcat vulnerabilities. This work was done actually a month or so before the
Heartbleed incident fortunately enough and the project was able to turn that
around very quickly after it was released by Tomcat. This quarter saw two
security vulnerability releases, TomEE 1.6.0.1 and 1.6.0.2, each about a month
apart. Note frequent releases have been a concern in several prior board
reports. It's very good to see a marked improvement in this area.
Primary focus on trunk has revolved around supporting Java 8, which has
required patches and releases to a handful projects. Trunk will be released
as TomEE 1.7.0, hopefully within a month. After this release the community
plans to change trunk to TomEE 2.0 and begin work towards Java EE 7 (with or
with out a TCK -- hopefully with).
Community activity has increased since last quarter. Patches have been
committed from around six new faces hailing from various parts of the world.
Most having seen some presentation or been a user for a while and encouraged
by seeing others make the jump and start committing. I'll note once again, my
personal observations are individual committers tend to come in at least
groups of two. Seeing others ask the basic questions on how to contribute
often has a way of emboldening others to do the same -- when they do as well,
it tends to snowball. Good to see the right "ingredients" in play for some
community growth.
Conversation about growing the PMC and legal oversight was pushed to the dev
list again. Good opportunity to teach how Apache works as a legal entity for
the new people getting involved and clarify for existing committers. I'd
expect to see some additions there.
Last release was 1.6.0.2 on 2014-05-12. Last committer was added November
2013. Last PMC addition was 2010-08-26.
-----------------------------------------
Attachment BB: Report from the Apache Turbine Project [Thomas Vandahl]
Apache Turbine is a servlet based framework that allows experienced Java
developers to quickly build web applications. Turbine allows you to
personalize the web sites and to use user logins to restrict access to parts
of your application. Turbine is a matured and well established framework that
is used as the base of many other projects.
Status
The Turbine project has again seen low levels of activity in the last quarter.
The Turbine project has no board-level issues at this time.
Project Branding Board Report Checklist
The last issue left is
- TODO: Logos and Graphics : include TM
Community changes
No new committers were voted in since the last board report. The last change
to the committer base was the addition of Georg Kallidis (2012/09/19). No new
PMC members were voted in since the last board report. The last change to the
PMC was the addition of Georg Kallidis (2013/09/30).
Turbine core project
The Turbine project moved its distribution method to svnpubsub. The
distribution directories have been cleaned up on this occasion. The last
released component was the parent POM (2013/09/25).
Fulcrum component project
The first version of the Fulcrum JSON component has been completed
- Fulcrum json 1.0.0 has been released (2014/04/07)
-----------------------------------------
Attachment BC: Report from the Apache Tuscany Project [Jean-Sebastien Delfino]
Apache Tuscany is an SOA framework based on OASIS OpenCSA and SCA.
ISSUES
- There are no issues that require the board's attention.
RELEASES
- Last release was Tuscany SCA 2.0.1, 10/3/2013.
COMMUNITY ACTIVITY
- Last committer addition was Sebastian Millies, 12/4/2012.
- Mailing list traffic hasn't changed much in the past few months, and
continues to be on the lower side, with a few questions on the user
mailing list and a few JIRAs on the dev list.
BRANDING
- We still need to update logos with ™ and review the project DOAP file.
-----------------------------------------
Attachment BD: Report from the Apache Velocity Project [Nathan Bubna]
Apache Velocity is a java template engine and related projects.
RELEASES
* Last release was master POM, May 2012
* Last noteworthy release was Engine in 2010
CURRENT ACTIVITY
* There were two commits this quarter (a bugfix and a doc fix).
COMMUNITY
* Last committer added April 28, 2013
* Activity is inconsistent on the user list but steady on Stack Overflow.
-----------------------------------------
Attachment BE: Report from the Apache Xalan Project [Steven J. Hathaway]
The Xalan project consists of libraries and programs in C/C++ and Java
languages to transform XML documents using XSLT stylesheets into HTML,
text, and other XML document types.
COMMUNITY
----------
New committer profile:
Samuel De Medeiros Queiros is approved by the PMC as a new committer
and a candidate for PMC membership. We are finishing the work of
getting him an official account. Samuel has completed two sessions
of Google Summer of Code: 2012(Xalan-C) 2013(Xalan-Java).
Mail list activity:
The development mail list has seen over 100 messages in the last
three months, preparing for the new Xalan-Java release.
SECURITY
--------
The security patch for Xalan-Java is committed to the trunk.
A new release is approved. We are finishing the publishing
details.
RELEASES
--------
Xalan Java: Previous Release 2.7.1 (2007-11-27)
Version 2.7.2 Package Release (2014-04-23)
Version 2.7.2 Website Updated (2014-05-16)
This includes the security patch.
Xalan C/C++: Current Release 1.11 (2012-10-29)
Quality assurance builds and documentation are being
prepared for a new release.
BOARD ISSUES
------------
Resolved issues from last report:
Committment activity for a new release is resolved.
We are preparing artifacts for official product release.
We have accepted a valued contributor as a new committer
and PMC member.
-----------------------------------------
Attachment BF: Report from the Apache Xerces Project [Michael Glavassevich]
Xerces-J
Four minor bug fixes were made to the XML Schema 1.1 implementation
for JIRA issues that were reported by users.
There were a few students who expressed an interest in working on
Xerces-J for GSoC though none were matched with a mentor this year.
Mailing list traffic has been low; roughly 55 posts on the j-dev
and j-users lists since the beginning of March 2014.
No new releases this quarter. The latest release is
Xerces-J 2.11.0 (November 30th, 2010).
Xerces-C
One minor bug was fixed, a few ones were opened but immediately
resolved as non-bugs.
Mailing list traffic has been almost non-existent; roughly 6 posts
on the c-dev and c-users lists since the beginning of March 2014.
No news about when the 3.2 version will be packaged. The latest
release is Xerces-C 3.1.1 (April 27th, 2010).
Xerces-P
Nothing in particular to report. There was no development activity
over the reporting period.
XML Commons
Nothing in particular to report. There was no development or
mailing list activity over the reporting period.
Committer / PMC Changes
No new committers in the last quarter. The most recent committers
were elected in July 2008 (Xerces-C) and May 2009 (Xerces-J).
No new PMC members in the last quarter. The last two additions to
the PMC were in May 2010.
Apache Project Branding Requirements
There's still some work left to do on the TLP website, including
adding "TM" to the project logo.
-----------------------------------------
Attachment BG: Report from the Apache XML Graphics Project [Chris Bowditch]
The Apache XML Graphics Project is responsible for software intended for
the creation & maintenance of the conversion of XML formats to graphical
output & related software components.
Issues for the Board
====================
No issues at present.
Community
=========
Last new committer: Simon Steiner on 11/04/14
Last new PMC member: Luis Bernardo on 04/03/13
XML GRAPHICS COMMONS
====================
23 separate commits to SVN, of which 22 were related to updating the check
style policy to be inline with the FOP project and only 1 commit was a bug
fix.
There were no releases this quarter.
The latest release is 1.5 (20 October 2012)
FOP
===
199 e-mails on fop-user mailing list this quarter; plenty of questions
asked by users and answered by committers. Some new bugs logged and several
patches have been submitted and processed. 31 separate commits in total to
SVN. A vote to merge the finished whitespace management extension into
trunk passed in the last few days. A branch of code that re-worked the way
fonts work in the FOP and Batik integration layer has also been merged into
trunk.
There were no releases this quarter
The latest release is 1.1 (20 October 2012)
BATIK
=====
Mailing list activity remains light; 24 e-mails to the user list this
quarter. A few bugs have been reported in JIRA. There were 5 commits made
by PMC members during this quarter; 3 of which were community supplied
patches being processed.
There were no releases this quarter.
The latest version is 1.7 (6 January 2008)
------------------------------------------------------
End of minutes for the May 21, 2014 board meeting.
Index