Index
Links: 2017 - All years
- Original The Apache Software Foundation
Board of Directors Meeting Minutes
February 27, 2017
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/35r6
The meeting was held via teleconference, hosted by Doug Cutting
and Cloudera.
IRC #asfboard on irc.freenode.net was used for backup purposes.
2. Roll Call
Directors Present:
Rich Bowen
Shane Curcuru
Bertrand Delacretaz
Isabel Drost-Fromm
Marvin Humphrey
Jim Jagielski
Brett Porter
Mark Thomas
Directors Absent:
Chris Mattmann
Executive Officers Present:
Ross Gardler
Kevin A. McGrail - joined at 10:42
Sam Ruby
Craig L Russell
Executive Officers Absent:
Ulrich Stärk
Guests:
Daniel Gruno
David Nalley
Greg Stein
Hadrian Zbarcea - left at 11:42
Sally Khudairi
Sharan Foga
Tom Pappas
Will Stevens
3. Minutes from previous meetings
Published minutes can be found at:
http://www.apache.org/foundation/board/calendar.html
A. The meeting of December 21, 2016
See: board_minutes_2016_12_21.txt
Approved by General Consent.
B. The meeting of January 18, 2017
See: board_minutes_2017_01_18.txt
Approved by General Consent.
4. Executive Officer Reports
A. Chairman [Brett]
Thanks for everyone's patience due to my low availability over the
last 3 weeks. I'm catching up.
While there have been a number of directors traveling, the focus of
the board list was on a fairly short burst of activity around the
budget and fundraising, as noted in the President's report and
discussion items. We have some work to do to bring this together in
the next month.
Following the last meeting, I sought to clarify the understanding of
board voting in the case of abstentions, given the current wording of
the bylaws. It has been the consistent understanding of the board that
abstentions are not considered "present" at the meeting and do not
contribute to the majority requirement.
I'd like to thank the directors that started capturing some central
pointers to ASF policy.
I propose that we hold the Annual Members Meeting on March 28-30,
2017, however welcome input from any directors or officers -
particularly President, Secretary, Treasurer and vote monitors - as to
whether later dates in April would be more suitable. I will start
preparations immediately this week.
B. President [Sam]
Overall
=======
My current priorities: budget, fundraising, EA/TAC, then Brand
Management. Input from the board on budget will likely affect my
priorities going forward.
Budget
======
A draft FY22 budget has been posted as a discussion item. It contains
the approved FY17 budget, and three projections for FY22.
Feel free to challenge assumptions, pick from the available options, or
even come up with an entirely new target. If the board can provide
quick feedback on these numbers, we may have time for a total of three
iterations; otherwise the next numbers the board will see posted is a
FY18 budget for approval.
I encourage the board to come up with targets for a balanced FY22
budget. Clearly the intervening years won't be balanced, but with both
a target and enough time, we can define a path to get there with
minimum disruption.
The biggest single lever under the board's control that would affect
multiple expense categories is to find a way to significantly limit the
rate of growth of the foundation; more specifically to throttle the
arrival rate of accepted podlings by the incubator.
On the expense side, I'm most concerned about infrastructure as this
one item is simultaneously (1) the largest expense, (2) the least
discretionary, and (3) the item with the most inertia in that it will
take the most time to make a change without substantial disruption.
For this reason, I request that the board make a priority of setting a
FY22 target for this item. Once this target is set, I will ask David
and Greg to prioritize building a plan to get us there. This plan may
include a temporary increase followed by a drop off - which would be OK
as we have the funds.
On the income side, I don't see any magic bullets that we can rely on
to provide us with significant year over year compound growth UNLESS we
manage to identify something of significantly more direct value to our
sponsors than what we have offered to date. A part of this may be a
willingness on our side to be more accommodating when a sponsor makes
requests (e.g., for a Privacy Shield amendment) that would make selling
the sponsorship easier by those within the potential sponsor.
Fundraising
===========
Input has been provided into the budget process, and work is being done
to identify the list of sponsors that we need to follow up on in order
to meet our FY17 targets.
EA/TAC
======
EA has resumed work on TAC preparations for Miami. Nick Burch has been
most helpful.
Brand Management
================
Brand Management is continuing to work with the Podlings and PMCs that
are willing to work within the constraints of the published ASF
Trademark Policy, and per my direction is deferring activity related to
the remainder of the projects.
Less than a day after I thought I had closure from the board on whether
or not the published Trademark Policy was a policy or set of best
practices, multiple board members indicated that this Policy needed to
be ratified and/or given a stamp of approval from the board. So, for
now, I've moved on. I've not added any discussion items or resolutions
related to this matter to this month's agenda. While I will continue
to ask for actionable feedback to be sent to trademarks@, I am no
longer optimistic.
So, to be clear, we currently have a policy that applies to most. At
this time, all it takes for a PMC or PPMC to be excluded is to simply
state that this policy doesn't apply to them. That will mean that PMCs
are free to continue to come up with their own criteria and apply it
unfairly to one third party but not another. Or for one PMC to apply a
different policy than other PMC does, perhaps even to the same third
party.
Additionally, please see Attachments 1 through 7.
@Brett: pursue resolution of Brand Management Policy issue
C. Treasurer [Ulrich]
Virtual Update:
Cash at January 31st 2017 was $1,505.2K, which is down $92.8K from
last month's ending balance (Dec 2016) of $1,598K, due to monthly AP
and lower than expected sponsorship pmts received for Jan 2017. The
January 2017 cash balance is down $53.2K from the January 2016 month
end balance of $1,558.3K. The January 2017 ending cash of $1,505.2K
represents a cash reserve of 14.8 months based on the FY17 Cash
forecast average monthly spending of $101.9/month. The "Estimated"
yearend cash reserve for the ASF, based on the Cash Forecast tab is
16.1 months and the reserve continues to be very healthy for an
organization of ASF's size.
Regarding the Cash P&L, the Foundation's total revenue YTD through
January 2017 was $571.2K and is behind the "UPDATED" budget by $81.3K.
VP of Fundraising is working on the $433K that remains in the
forecast, for the rest of FY17, to make it to the updated budget
number. Currently we have $375K in open AR, which is $58K short to
the updated budget, remaining revenue in the forecast to make it to
the FY 17 Budget. However there are some sponsors who have not been
billed yet as their renewal is not up until April. Sponsorship
payments were received from the following Sponsor in January 2017:
WANdisco for $20K.
In January expenses were over budget by $1.7K This was driven by over
spending in Infra ( $16K due to overspending in Staffing, Hardware,
and particularly the timing of the Carbonite payment of $10K vs a Bud
of $6K for a 2 yr service agreement). Programs was under by $10K
which helped to offset this. Publicity was over budget in Dec by $4K
due to an additional Meltwater invoice paid in Jan. Brand and G& A
were under budget as was Fundraising, with Treasury being right on
budget for the month. With regard to YTD, Infra was over bud by $15K
( $5K in staffing, $5K in Service contracts, due to timing of
carbonite and Travel is also over by $5K). Prog is under by $10K as
is Publicity by $8.5K which may be timing of spending. Tac &
Conference is under by $5.7K. Brand and Treasury are right on budget
with G&A slightly under budget by $.8K. This leaves us YTD $10K under
budget in expenses.
With regard to Net Income, for Jan 2017 we were under by $45K, due to
$43K under in Revenue and $2K over in expenses. From a YTD
perspective we are $81K under in revenue and $10K under in Expenses so
net we are under budget, for Net income by $72K, YTD.
We have a first draft of the FY 16 990 that is out for review with the
Treasurer and we anticipate it being signed and submitted to the IRS
before the final due date of 3.15.17.
Income and Expenses for January 2017:
Current Balances:
Citizens Checking 192,880.07
Citizens Money Market 1,205,478.65
Paypal - ASF 106,806.98
Total Checking/Savings 1,505,165.70
January 2017 Budget Variance
Income Summary:
Inkind Revenue 0.00 0.00 0.00
Public Donations 3,739.58 0.00 3,739.58
Sponsorship Program 20,000.00 68,167.00 -48,167.00
Programs Income 0.00 0.00 0.00
Other Income 0.00 0.00 0.00
Interest Income 511.70 0.00 511.70
Total Income 24,251.28 68,167.00 -43,915.72
Expense Summary:
In Kind Expense 0.00 0.00 0.00
Infrastructure 83,432.51 66,913.00 16,519.51
Sponsorship Program 1,000.00 1,750.00 -750.00
Programs Expense 0.00 10,000.00 -10,000.00
Publicity 15,372.71 11,507.54 3,865.17
Brand Management 6,137.39 7,877.00 -1,739.61
Conferences 0.00 0.00 0.00
Travel Assistance Committee 0.00 0.00 0.00
Tax and Audit 0.00 0.00 0.00
Treasury Services 3,100.00 3,100.00 0.00
General & Administrative 7,945.19 14,142.00 -6,196.81
Total Expense 116,987.80 115,289.54 1,698.26
Net Income -92,736.52 -47,122.54 -45,613.98
YTD YTD Budget Variance
Income Summary:
Inkind Revenue 0.00 0.00 0.00
Public Donations 22,892.29 13,873.67 9,018.62
Sponsorship Program 515,795.00 607,129.00 -91,334.00
Programs Income 27,200.00 27,200.00 0.00
Other Income 825.00 825.00
Interest Income 4,537.14 3,515.00 1,022.14
Total Income 571,249.43 652,542.67 -81,293.24
Expense Summary:
In Kind Expense 0.00 0.00 0.00
Infrastructure 529,473.27 513,861.00 15,612.27
Sponsorship Program 1,000.00 1,750.00 -750.00
Programs Expense 0.00 10,000.00 -10,000.00
Publicity 106,054.02 114,498.10 -8,444.08
Brand Management 58,781.07 58,791.00 -9.93
Conferences 4,822.32 5,409.00 -586.68
Travel Assistance Committee 28,734.51 33,864.00 -5,129.49
Tax and Audit 6,000.00 6,000.00 0.00
Treasury Services 27,900.00 27,900.00 0.00
General & Administrative 86,074.93 86,838.00 -763.07
Total Expense 848,840.12 858,911.10 -10,070.98
Net Income -277,590.69 -206,368.43 -71,222.26
(Continued) Asst Treasurer [KAM]
* Produced draft FY18 budget and FY22 budget at
https://s.apache.org/PdM3
NOTE that I added extra for Bill.com, Expensify or Dropbox.
* I am talking to Bill.com about a discounted account for ASF. It is
pending a manager as of 2/11.
* Treasurer / Individual Giving Contribution Work (Hadrian, Sally & KAM)
* Work on Hopsie Continues - https://s.apache.org/hErs
Please request access.
* Working to confirm our charity status with PayPal. Paperwork
sent Jan 11. Pinged Feb 4 for status.
* Amazon Smiles / Amazon Seller Central changed from psteitz@
to contributions@a.o
* I’ll be working on
https://www.apache.org/foundation/contributing.html to make
sure it’s complete and implement Hopsie soon.
* Question: Does anyone know where proceeds from the donation
of old cars go?
* Next month I plan to work a lot more on Hopsie and cleaning
up the individual contribution items.
* As I get control of various accounts, encrypted passwords are
stored at
https://svn.apache.org/repos/private/financials/Accounts in
case I am hit by a bus. Getting these documented and
appropriately encrypted and appropriately shared is a goal.
* Re: PayPal. I recently learned that PayPal is NOT FDIC Insured
https://www.paypal.com/us/webapps/mpp/ua/useragreement-full - Any
PayPal balance you hold represents an unsecured claim against PayPal
and is not insured by the Federal Deposit Insurance Corporation
(FDIC).
As such, I Requested Transfer of $106900 to another appropriate ASF
FDIC insured account. Virtual created a Money Market Account at
Citizens for this on Monday the 6th of February.
I’ve also added a task to move all funds out of paypal monthly into
an appropriate ASF FDIC-backed account
* Please note my continued thanks to Virtual. It is a joy to work with
them.
* Request board discussion and consensus re: Bitcoins as there is a
risk to association funds. Specifically, here is my recommended plan:
- use Bitstamp to convert existing current bitcoins to cash. There
is a risk I could mess this up and lose our bitcoins. I am not an
expert in cryptocurrency and the technology is far from user
friendly.
- Stop accepting what are effectively investment vehicles as
donations and switch to Coinbase so we aren’t receiving effectively
“investments” but rather cash via bitcoins. This will reduce risk
of loss of money from Bitcoins, simply accounting (because Bitcoins
simply aren’t tracked right now) and simplify donations.
Kevin asked that the board authorize him to convert current
Bitcoin assets to cash and immediately convert future Bitcoin
contributions to cash going forward.
The board agrees.
D. Secretary [Craig]
Secretary continues to run smoothly. In January, 81 iclas, four cclas,
and two grants were received and filed.
E. Executive Vice President [Ross]
Infrastructure
==========
Infra team have had to rescind an offer to maintain a VM, CPU and
storage for a private copy of Maven Central as a precaution. Storage
growth rate indicates that the offer is not sustainable. Maven PMC
have been encouraged to seek specific budget support from the Board
for their needs.
The team are conducting an experiment with a small ($525) unbudgeted
expense on unlimited online coursework for three months. If successful
the next budget will include staff training as a budget item.
There is an effort to accelerate the decommissioning of ASF-owned
hardware and the adoption of the Gitbox service
(Git as a canonical ASF code repository, http://gitbox.apache.org).
Some progress on a new web area for the Directors to create an
authoritative set of pages for Board-approved policies and commentary.
Conferences
==========
232 sessions submitted for ApacheCon Miami, with 193 for Apache: Big
Data. Selection process is now underway.
Marketing and Publicity
==================
A recent focus on the ASF LinkedIn page results in expanded reach for
our news announcements,
Exploring plans for professional editing of ApacheCon recordings as
volunteer efforts, though very much appreciated, are not producing
timely results due to the volume of recordings available.
F. Vice Chairman [Chris]
Nothing to report.
Executive officer reports approved as submitted by General Consent.
5. Additional Officer Reports
A. VP of W3C Relations [Andy Seaborne / Bertrand]
See Attachment 8
B. Apache Legal Affairs Committee [Jim Jagielski]
See Attachment 9
C. Apache Security Team Project [Mark J. Cox / Shane]
See Attachment 10
Additional officer reports approved as submitted by General Consent.
6. Committee Reports
Summary of Reports
The following reports required further discussion:
# BookKeeper [mt]
# Buildr [idf]
# Cassandra [bp]
# Eagle [mt]
# Geronimo [bp]
# Giraph [bp]
# Hama [bp]
# Incubator [bp]
# Oltu [bp]
# Spark [mt]
# Xerces [bp]
A. Apache Abdera Project [Ant Elder / Brett]
No report was submitted.
B. Apache ActiveMQ Project [Bruce Snyder / Jim]
See Attachment B
C. Apache Ambari Project [Yusaku Sako / Marvin]
See Attachment C
D. Apache Ant Project [Jan Matèrne / Chris]
See Attachment D
E. Apache Archiva Project [Olivier Lamy / Mark]
See Attachment E
F. Apache Beam Project [Davor Bonaci / Isabel]
See Attachment F
G. Apache BookKeeper Project [Sijie Guo / Rich]
See Attachment G
@Rich: bring comments regarding transparency to PMC and ask
them to resubmit report next month
H. Apache Brooklyn Project [Richard Downer / Rich]
See Attachment H
I. Apache Buildr Project [Antoine Toulme / Jim]
See Attachment I
@Jim: follow up with PMC to ensure that there are three active
PMC members to provide oversight
J. Apache Cassandra Project [Nate McCall / Shane]
See Attachment J
@Shane: please explain the comment regarding external org
K. Apache Clerezza Project [Hasan Hasan / Marvin]
See Attachment K
L. Apache Cocoon Project [Thorsten Scherler / Chris]
See Attachment L
M. Apache Community Development Project [Ulrich Stärk / Brett]
See Attachment M
N. Apache CouchDB Project [Jan Lehnardt / Bertrand]
See Attachment N
O. Apache Creadur Project [Brian E Fox / Isabel]
See Attachment O
P. Apache CXF Project [Daniel Kulp / Mark]
See Attachment P
Q. Apache DeltaSpike Project [Thomas Andraschko / Shane]
See Attachment Q
R. Apache Drill Project [Parth Chandra / Bertrand]
See Attachment R
S. Apache Eagle Project [Edward Zhang / Chris]
See Attachment S
@Chris follow up on reported meeting between external parties
not brought back to the public lists
T. Apache Empire-db Project [Rainer Döbele / Brett]
See Attachment T
U. Apache Flume Project [Hari Shreedharan / Jim]
See Attachment U
V. Apache Forrest Project [David Crossley / Rich]
See Attachment V
W. Apache Geode Project [Mark Bretl / Marvin]
See Attachment W
X. Apache Geronimo Project [Alan Cabrera / Isabel]
No report was submitted.
Y. Apache Giraph Project [Avery Ching / Mark]
No report was submitted.
@Mark: pursue a report for Giraph
Z. Apache Gora Project [Lewis John McGibbney / Shane]
See Attachment Z
AA. Apache Groovy Project [Guillaume Laforge / Isabel]
See Attachment AA
AB. Apache Hama Project [Edward J. Yoon / Bertrand]
No report was submitted.
@Bertrand: pursue a report for Hama
AC. Apache HTTP Server Project [Eric Covener / Rich]
See Attachment AC
AD. Apache HttpComponents Project [Asankha Perera / Marvin]
See Attachment AD
AE. Apache Ignite Project [Denis Magda / Chris]
See Attachment AE
AF. Apache Incubator Project [Ted Dunning / Brett]
See Attachment AF
AG. Apache jUDDI Project [Alex O'Ree / Jim]
See Attachment AG
AH. Apache Kafka Project [Jun Rao / Mark]
See Attachment AH
AI. Apache Knox Project [Larry McCay / Shane]
See Attachment AI
AJ. Apache Kylin Project [Luke Han / Brett]
See Attachment AJ
AK. Apache Lens Project [Amareshwari Sriramadasu / Mark]
See Attachment AK
AL. Apache Libcloud Project [Tomaž Muraus / Bertrand]
See Attachment AL
AM. Apache Logging Services Project [Ralph Goers / Isabel]
See Attachment AM
AN. Apache ManifoldCF Project [Karl Wright / Chris]
See Attachment AN
AO. Apache Marmotta Project [Jakob Frank / Rich]
See Attachment AO
AP. Apache Mesos Project [Benjamin Hindman / Jim]
See Attachment AP
AQ. Apache MetaModel Project [Kasper Sørensen / Marvin]
See Attachment AQ
AR. Apache Oltu Project [Antonio Sanso / Bertrand]
See Attachment AR
AS. Apache Oozie Project [Robert Kanter / Isabel]
See Attachment AS
AT. Apache Open Climate Workbench Project [Michael James Joyce / Jim]
See Attachment AT
AU. Apache Perl Project [Philippe M. Chiasson / Mark]
No report was submitted.
AV. Apache Phoenix Project [James R. Taylor / Marvin]
See Attachment AV
AW. Apache POI Project [Dominik Stadler / Brett]
See Attachment AW
AX. Apache Qpid Project [Robbie Gemmell / Chris]
See Attachment AX
AY. Apache Ranger Project [Selvamohan Neethiraj / Shane]
See Attachment AY
AZ. Apache REEF Project [Byung-Gon Chun / Rich]
See Attachment AZ
BA. Apache River Project [Patricia Shanahan / Mark]
See Attachment BA
BB. Apache Roller Project [Dave Johnson / Rich]
See Attachment BB
BC. Apache Santuario Project [Colm O hEigeartaigh / Chris]
See Attachment BC
BD. Apache Serf Project [Bert Huijben / Brett]
See Attachment BD
BE. Apache SIS Project [Martin Desruisseaux / Jim]
See Attachment BE
BF. Apache Spark Project [Matei Zaharia / Isabel]
See Attachment BF
@Shane: follow up on brand action item
BG. Apache Sqoop Project [Jarek Jarcec Cecho / Marvin]
See Attachment BG
BH. Apache Subversion Project [Evgeny Kotkov / Bertrand]
See Attachment BH
BI. Apache Syncope Project [Francesco Chicchiriccò / Shane]
See Attachment BI
BJ. Apache Turbine Project [Thomas Vandahl / Chris]
See Attachment BJ
BK. Apache Usergrid Project [Todd Nine / Marvin]
See Attachment BK
BL. Apache Velocity Project [Nathan Bubna / Isabel]
See Attachment BL
BM. Apache Whimsy Project [Sam Ruby / Jim]
See Attachment BM
BN. Apache Xalan Project [Steven J. Hathaway / Mark]
See Attachment BN
BO. Apache Xerces Project [Michael Glavassevich / Bertrand]
No report was submitted.
BP. Apache XML Graphics Project [Glenn Adams / Shane]
See Attachment BP
Committee reports approved as submitted by General Consent.
7. Special Orders
A. Change the Apache Cocoon Project Chair
WHEREAS, the Board of Directors heretofore appointed Thorsten
Scherler (thorsten) to the office of Vice President, Apache Cocoon,
and
WHEREAS, the Board of Directors is in receipt of the resignation
of Thorsten Scherler from the office of Vice President, Apache
Cocoon, and
WHEREAS, the Project Management Committee of the Apache Cocoon
project has chosen by vote to recommend Cédric Damioli (cdamioli)
as the successor to the post;
NOW, THEREFORE, BE IT RESOLVED, that Thorsten Scherler is
relieved and discharged from the duties and responsibilities of
the office of Vice President, Apache Cocoon, and
BE IT FURTHER RESOLVED, that Cédric Damioli be and hereby is
appointed to the office of Vice President, Apache Cocoon, 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 Cocoon Project Chair, was
approved by Unanimous Vote of the directors present.
B. Change the Apache JMeter Project Chair
WHEREAS, the Board of Directors heretofore appointed Sebastian
Bazley (sebb) to the office of Vice President, Apache JMeter, and
WHEREAS, the Board of Directors is in receipt of the resignation
of Sebastian Bazley from the office of Vice President, Apache JMeter,
and
WHEREAS, the Project Management Committee of the Apache JMeter
project has chosen by consensus to recommend Milamber (milamber) as
the successor to the post;
NOW, THEREFORE, BE IT RESOLVED, that Sebastian Bazley is relieved and
discharged from the duties and responsibilities of the office
of Vice President, Apache JMeter, and
BE IT FURTHER RESOLVED, that Milamber be and hereby is
appointed to the office of Vice President, Apache JMeter, 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 7B, Change the Apache JMeter Project Chair, was
approved by Unanimous Vote of the directors present.
C. Terminate the Apache Abdera Project
WHEREAS, the Board of Directors deems it no longer in the best
interest of the Foundation to continue the Apache Abdera project
due to inactivity;
NOW, THEREFORE, BE IT RESOLVED, that the Apache Abdera project is
hereby terminated; and be it further
RESOLVED, that the Attic PMC be and hereby is tasked with oversight
over the software developed by the Apache Abdera Project; and be it
further
RESOLVED, that the office of "Vice President, Apache Abdera" is
hereby terminated; and be it further
RESOLVED, that the Apache Abdera PMC is hereby terminated.
Special Order 7C, Terminate the Apache Abdera Project, was
approved by Unanimous Vote of the directors present.
D. Change the Apache Bigtop Project Chair
WHEREAS, the Board of Directors heretofore appointed Olaf Flebbe
(oflebbe) to the office of Vice President, Apache Bigtop, and
WHEREAS, the Board of Directors is in receipt of the resignation of
Olaf Flebbe from the office of Vice President, Apache Bigtop, and
WHEREAS, the Project Management Committee of the Apache Bigtop project
has chosen by consensus to recommend Evans Ye (evansye) as the
successor to the post;
NOW, THEREFORE, BE IT RESOLVED, that Olaf Flebbe is relieved and
discharged from the duties and responsibilities of the office of Vice
President, Apache Bigtop, and
BE IT FURTHER RESOLVED, that Evans Ye be and hereby is appointed to
the office of Vice President, Apache Bigtop, 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 7D, Change the Apache Bigtop Project Chair, was
approved by Unanimous Vote of the directors present.
E. Change the Apache Vice President of Legal Affairs
WHEREAS, the Board of Directors heretofore appointed Jim Jagielski to
the office of Vice President, Legal Affairs, and
WHEREAS, the Board of Directors is in receipt of the resignation of
Jim Jagielski from the office of Vice President, Legal Affairs, and
WHEREAS, Jim Jagielski has recommended Marvin Humphrey as the
successor to the post;
NOW, THEREFORE, BE IT RESOLVED, that Jim Jagielski is relieved and
discharged from the duties and responsibilities of the office of Vice
President, Legal Affairs, and
BE IT FURTHER RESOLVED, that Marvin Humphrey be and hereby is
appointed to the office of Vice President, Legal Affairs, 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 Vice President of Legal
Affairs, was approved by Unanimous Vote of the directors
present.
F. Change the Apache CloudStack Project Chair
WHEREAS, the Board of Directors heretofore appointed Will Stevens
(swill) to the office of Vice President, Apache CloudStack, and
WHEREAS, the Board of Directors is in receipt of the resignation
of Will Stevens from the office of Vice President, Apache CloudStack,
and
WHEREAS, the Project Management Committee of the Apache CloudStack
project has chosen by vote to recommend Wido den Hollander (widodh)
as the successor to the post;
NOW, THEREFORE, BE IT RESOLVED, that Will Stevens is relieved and
discharged from the duties and responsibilities of the office
of Vice President, Apache CloudStack, and
BE IT FURTHER RESOLVED, that Wido den Hollander be and hereby is
appointed to the office of Vice President, Apache CloudStack, to
serve in accordance with and subject to the direction of the
Board of Directors and the Bylaws of the Foundation until
death, resignation, retirement, removal or disqualification, or
until a successor is appointed.
Special Order 7F, Change the Apache CloudStack Project Chair,
was approved by Unanimous Vote of the directors present.
8. Discussion Items
A. FY22 Budget
The following inputs have been collected as input to the board.
See the President's report for context and associated request.
FY17 Min FY22 FY22 Max FY22
Income
Total Public Donations 89 90 110 135
Total Sponsorship 968 900 1,000 1,100
Total Programs 28 28 28 28
Interest Income 4 4 4 4
----- ----- ----- -----
Total Income 1,089 1,022 1,142 1,267
Expense
Infrastructure 723 868 868 868
Program Expenses 27 27 27 27
Publicity 141 273 352 540
Brand Management 84 92 141 218
Conferences 12 12 12 12
Travel Assistance 62 0 79 150
Treasury 48 49 51 61
Fundraising 8 18 23 23
General & Administrative 114 50 139 300
----- ----- ----- -----
Total Expense 1,219 1,390 1,693 2,199
Net -130 -369 -552 -933
Cash 1,656 290 -259 -1,403
Notes:
1) Units are thousands of US dollars
2) Cash projections are based on linear change in budgets for FY18-FY21
Discussion:
First, a clarification that the first column is the approved budget for FY17
and the next three columns are possible fy22 budgets:
Second column is minimal FY22 budget
Third column is “nominal”, linearly projecting the FY17 budget to FY22
Fourth column is if we expand the services in many areas
Jim: looks like brand management and publicity are the most malleable parts
Sam: there are several areas that could be changed
Jim: we should try to see what a reasonable budget should be and then see
if we can adapt sponsorship to match our needs; thinking we could really
get more sponsorship
Sam: but e.g. should we even have a TAC?
Marvin: Those areas (TAC etc) are investments that we believe are wise,
but which we might choose not to make in slim times
Ross: some of the expanded publicity could lead to more sponsorship
Marvin: going for minimal budget also implies shutting down incubator
Jim: we should go for the middle column and see if we can figure out how
to get there
Shane: we should set a target about halfway between the minimal and
expanded budget
Bertrand: could we consider a really minimal “survival” budget?
Jim: that was supposed to be the minimum column
Sam: survival is a bit less than the first column; would prefer not to
pursue survival budget
Brett: it’s worthwhile to try to be ambitious about the budget; at least
meet the nominal budget
Sam: recommend a f2f meeting in March to resolve direction on fundraising;
maybe in Washington or Boston; with a follow-on meeting in Miami
Sam: sounds like we have consensus to try to strive for the nominal budget
and see if we can achieve income to meet it
9. Review Outstanding Action Items
* Mark: pursue a report for Abdera; determine if the Attic is next
[ Abdera 2016-11-16 ]
Status: Complete: Confirmed that the attic is nextr
* Bertrand: Work with PMC to get a more complete report
[ Felix 2016-12-21 ]
Status:
* Jim: Mentor comments are extremely important; please try to include them.
[ Incubator 2016-12-21 ]
Status: Ongoing
* Jim: Many projects have been incubating for years. Please address this.
[ Incubator 2016-12-21 ]
Status: Ongoing
* Isabel: Work with PMC to see if they plan to change their remit
[ Labs 2016-12-21 ]
Status:
* Mark: help Abdera transition to the Attic
[ Abdera 2017-01-18 ]
Status: Comlete: Resolution submitted for consideration at Feb 2017
board meeting.
* Bruce: resubmit the report for February
[ ActiveMQ 2017-01-18 ]
Status:
* Shane: "encourage" the PMC to be responsive to security issues
[ Apex 2017-01-18 ]
Status: PMC is discussing on private@ and creating their own
security@. If Security Team does not see action, can reopen,
otherwise this is complete.
* Brett: pursue a report for Archiva
[ Archiva 2017-01-18 ]
Status: Present
* Alan: will report next month
[ Geronimo 2017-01-18 ]
Status:
* Jim: consolidate and take board's concerns to IPMC.
[ Incubator 2017-01-18 ]
Status: Ongoing
* Jim: pursue a report for Mesos
[ Mesos 2017-01-18 ]
Status: Report rec'd
* Mark: pursue a report for Sqoop
[ Sqoop 2017-01-18 ]
Status: Complete: Report provided for Feb 2017 meeting
* Marvin: try to get a better report that reflects activity
[ Tajo 2017-01-18 ]
Status:
10. Unfinished Business
11. New Business
12. Announcements
13. Adjournment
Adjourned at 11:46 a.m. (Pacific)
============
ATTACHMENTS:
============
-----------------------------------------
Attachment 1: Report from the Executive Assistant [Melissa Warnkin]
Monitoring of all email and following up with appropriate personnel when
needed
Gearing up for ACNA’17. Will be working with Sharan Foga on swag and booth
logistics, etc.
Handled/processed CSC invoice for payment for renewal of Corporate
registration
-----------------------------------------
Attachment 2: Report from the VP of Brand Management [Shane Curcuru]
* ISSUES FOR THE BOARD
As noted in last month's report, we await ratification by the board as to the
status of brand policy and unresolved questions thereon (issue continued from
last month). As directed by the President, I am prioritizing available
efforts on projects and podlings that are clearly and actively accepting of
the relationship with brand policy.
* OPERATIONS
Slightly slower month than usual on crises and questions, which let us spend
some time focusing on adding to the documentation.
Two draft proposals are awaiting more feedback:
- Services naming policy: https://www.apache.org/foundation/marks/services
- Merchandise use policy:
https://www.apache.org/foundation/marks/merchandise (public)
https://svn.apache.org/repos/private/committers/brand/merchandise.txt
(committer-only additional permissions)
A proposal to encourage (rather than prohibit) "Apache" in third party event
branding has been brought up. As with the draft proposals above,
disappointingly little (none, so far on events) feedback has appeared.
Similarly, a call to members@ soliciting questions about Apache brands met
with resounding silence.
Met with trademark counsel to improve operations around registration
processing and timelines and to bring new counsel on our account up to speed
on our objectives.
* REGISTRATIONS & CONTRACTS
Several project registration requests have gotten change suggestions from
counsel to better provide the best chance at registration without conflicts or
office actions. I don't know yet if this is a trend at the USPTO or just a
factor of some specific project names that are more common words being
popular.
New applications for COUCHDB, MESOS, and BIGTOP have been submitted.
We responded to an overly-broad potential conflict on our TEZ application made
by an overzealous examiner.
-----------------------------------------
Attachment 3: Report from the VP of Fundraising [Hadrian Zbarcea]
Fundraising activities continue normally.
Hadrian and Lynsey got into a good working pattern. We have weekly status
meetings to follow up on outstanding tasks. One of the main focuses is getting
in touch with sponsors to ensure that we meet the targets.
Last month we got a request from one European sponsor to sign a statement that
we comply with European data privacy laws. The request implied that continued
sponsorship is contingent on the ASF signing said document. There was a thread
on fundraising@ to that effect, I had a phone conversation with one of our
lawyers where we agreed that it is ok for us to sign. VP Legal stated that
he's against us signing so I did not. I asked the sponsor for clarifications
regarding the relevace of that document for us but didn't get a reply yet.
This cycle we experienced intense debates about the future of fundraising.
There were a number of opinions, nothing conclusive yet but the convesation
continues.
One task in progress was updating the ASF profile on guidestar [1]. Guidestar
has a ranking algorithm and after my updates it went to 'bronze', then
'silver'. One goal we have is to bump it up to 'gold' before the end of April
(fiscal year). Lynsey engaged the guidestar staff and is trying to organize a
meeting to see how we could better use guidestar to reach out to potential
sponsors.
[1] https://www.guidestar.org/profile/47-0825376
-----------------------------------------
Attachment 4: Report from the VP of Marketing and Publicity [Sally Khudairi]
I. Budget: Sally Khudairi is reviewing final quarter vendor
requirements in preparation for FY2018. No vendor payments are due at
this time. As requested by ASF President Sam Ruby, she also created a
projected budget for FY2022.
II. Cross-committee Liaison: Sally continues work with Fundraising,
Brand Management, Apache Incubator, Events/ApacheCon, and now ComDev.
She has published 1) the third "Success at Apache" post
https://s.apache.org/23CB ; 2) new positioning for ApacheCon
https://s.apache.org/F7Hy ; and 3) The ASF asks: Have you met Apache
Ignite? https://s.apache.org/Slah , among our usual activities. In
addition, she has begun publishing news on the ASF’s LinkedIn page
https://www.linkedin.com/company/the-apache-software-foundation and is
beginning to compile the ASF Q3 Operations Summary. The Apache
Incubator’s call for a new logo http://s.apache.org/rFii continues,
with more than 3 dozen submissions received thus far. The Incubator
has also added a “Press Releases for new TLPs” section under their
Graduation guidelines at
http://incubator.apache.org/guides/graduation.html per Sally’s
request.
III. Press Releases: the following formal announcements were issued
via the newswire service, ASF Foundation Blog, and announce@apache.org
during this timeframe:
- 8 February 2017 -- The Apache Software Foundation Announces Apache®
Ranger™ as a Top-Level Project
- 11 January 2017 --The Apache Software Foundation Announces Apache®
Zest™ Renamed to Apache Polygene
IV. Informal Announcements: 8 items were published on the ASF
"Foundation" Blog. 4 Apache News Round-ups were issued, with a total
of 134 weekly summaries published to date. 53 items were Tweeted on
@TheASF, which has now grown to more than 40,000 followers. Rich
Bowen’s team of ComDev volunteers continue uploading audio recordings
from ApacheCon Europe onto Feathercast. Sally is exploring options for
future professional editing services, as it is now three months since
the event and the job is still not finished. No new videos have been
added to the ASF YouTube channel. Sally continues to tweet for the
Apache Incubator account, and has posted 10 items on LinkedIn, our
newest outreach channel.
V. Future Announcements: one announcement is in development. Projects
planning to graduate from the Apache Incubator as well as PMCs wishing
to announce major project milestones and "Did You Know?" success
stories are requested to contact Sally at <press@apache.org> with at
least 2-weeks' notice for proper planning and execution.
VI. Media Relations: we responded to 2 media queries. The ASF received
1,214 press clips vs. last month's clip count of 973. Media coverage
of Apache projects yielded 3,949 press hits vs. last month's 1,014.
ApacheCon received 18 press hits.
VII. Analyst Relations: we received 1 analyst query during this
timeframe. Apache was mentioned in 24 reports by Gartner, 5 reports by
Forrester, 8 reports by 451 Research, and 5 reports by IDC.
VIII. Graphics: we’ve been working on the ASF Identity Style Guide
(graphics/visual/branding) with Fran Lukesh, one of the designers who
created the new ASF logo. Sally has also been working with several ASF
Sponsors and corporates involved with various Apache projects on
various assets, including “Powered By” logos. The ASF Infrastructure
team, specifically Daniel Takamori and Chris Thistlethwaite, have been
helping with migrating the apache.org favicons to the new feather
graphics.
IX. ApacheCon liaison: Sally published new positioning for ApacheCon
and is exploring possible underwriters for a future event outside of
North America. She is also working alongside Rich Bowen and the Linux
Foundation on marketing the upcoming ApacheCon in Miami.
X. (Non-ASF) Industry Events and Outreach liaison: Sally worked with
Sharan Foga and Daniel Gruno on the ASF’s presence at FOSDEM 2017. The
promotional products that were arranged by Daniel were a tremendous
success: according to Daniel the event had ~6,000 attendees --we could
have easily given away 4-5x the amount of items offered. The Apache
projects banner (similar to the listings at https://s.apache.org/Ccml
) was very helpful with generating conversations. Sharan had also
conducted several “from the conference floor” interviews that have
been posted to https://feathercast.apache.org/ . Huge thanks to
everyone for their help in staffing the booth during the event. In
addition to FOSDEM, Sally secured a community partnership exchange
with the IoTFuse annual conference.
XI. Newswire accounts: we have 23 pre-paid press releases remaining
with NASDAQ GlobeNewswire through December 2017.
# # #
-----------------------------------------
Attachment 5: Report from the VP of Infrastructure [David Nalley]
Recent Issues
=============
Nothing is needed from the President, or the Board. These are reported
as an FYI only.
We have seen issues regarding SHA-1 vulnerabilities, supporting the
Apache Maven project, and changes in our build systems. Details are
provided below, in the "General Activity" section.
Finances
========
We spent $525 to purchase several months of online training. This is
an unbudgeted amount, but we believe its unlimited coursework for the
entire team, for three months, was worth the experiment. At the end of
the period, we will evaluate whether an extension is warranted. Costs
for ongoing staff education will be included into our next budget
request.
Short Term Priorities
=====================
- Decomission ASF-owned hardware at an accelerated rate, in favor of
cloud-provided servers
- Continue ramping up the Gitbox service
- Balance our datacenter usage for cost efficiency
- Gitbox/Jira integration
Long Range Priorities
=====================
- As reported before: continued migrations of our legacy servers and
services into new puppet-based services that we can efficiently
deploy to cost-effective cloud providers.
- Automation to reduce the incremental cost of regular Infra tasks
- Migration from Puppet V3 to $nextgen system for providing services
General Activity
================
We set up a new web area for the Directors to create an authoritative
set of pages for Board-approved policies and commentary. Some initial
work by Directors has populated some data/pages, but the site design
and content is still in its infancy. The plumbing appears to work, so
we're "done" and will follow with continued support.
There has been a lot of Internet discussion about Google and CWI
finding and publishing a SHA-1 collision, and their statement that it
is now possible to construct additional collisions. They will be
releasing further data in a few months.
From our initial analysis, this issue only affects our Subversion
services as a limited denial of service, instituted by an Apache
committer (NOT by a third-party attacker). The Apache Subversion
community has been discussing and analyzing the issue, including the
extent of the problem and appropriate mitigations. We have already
deployed a script developed by their community, to prevent a committer
(or a compromised account) from pushing either collision documents
into our repository.
We have confirmed that our website certificates DO NOT use the SHA-1
algorithm. This has been in place for quite a while.
This past month, we discovered that we cannot support the growth of
Apache Maven's private copy of the Maven Central repository. We
previously offered the PMC a VM to keep a copy (should M.C go dark,
we'd retain all necessary data for the ecosystem), along with CPU to
perform analysis against that copy, but looking at the storage growth
rate, we determined that this offering was not sustainable within the
current Infrastructure budget. We notified the Apache Maven PMC that
we needed to retract the offering, and for them to seek specific
budget support from the Board for their needs.
Over the past year, the Infrastructure Team has moved to a policy of
"Ubuntu Only" for our machines, to lower our costs. In the past, we
had a lot of time to support multiple operating systems, services, and
customized software deployments. With the rapid growth of the ASF, and
the resulting demand for Infra support, we have pulled back on the
edge cases to focus more strongly on ROI of our staff's work
effort. That has resulted in the Ubuntu policy, which then resulted in
the decommissioning of Solaris, Mac OS, and FreeBSD build slaves in
our buildbot service. Needless to say, that has raised concern within
several probjects who relied on the availability of those platforms.
We have made it clear that the Infra Team will integrate third-party
custom build slaves into our system, so that projects can use those
slaves for their non-Ubuntu builds.
Uptime Statistics
=================
Overall uptime reached 'three nines' with 99.9% uptime. The 'worst
offenders' this period were writeable git repositories (due to a TLS
bug) and Jenkins, though none of the critical or core services went
below 99%.
For more information, please see http://status.apache.org/sla/
Community Growth
================
This period, we've had one new contributor to our puppet repository,
Jitendra Pandey, as well as contributions from 9 people who contribute
on a regular basis. on the JIRA side of things, we had 29 new people
interacting with infra via JIRA, making it 29 new users, 93 regulars
(people that have contributed before and do so often), as well as 5
'returnees' (people that have been absent for >2 years but are now
contributing/reporting again).
On a 3 month view, we've now had code contributions from 22 people, of
which 13 were regular contributors and 9 were new. 94 people have worked
on or reported a JIRA ticket for the first time, while the other 187 who
worked on or reported issues had doen so before.
GitHub as Master ("Gitbox")
===========================
Our Git services are planned to land on gitbox.a.o, so we generally
refer to this as "gitbox". In the past month, we start moving the
OpenWhisk podling over to the gitbox service. That has been a very
slow move, so Tika and Nutch have recently been added to gitbox. It is
too soon to remark on problems and SLA for these communities using
GitHub as their master/primary focal point of development. These
communities have enough activity to help us surface and pinpoint
problems. We've made several improvements based on feedback, and still
need to implement some Jira integrations.
We will likely add more projects before the next Board meeting, and
will report on such additions.
Cost-per-Project Reduction
==========================
An important, needed clarification arose this past month, regarding
the definition of this effort. Reducing the cost-per-project is about
managing the marginal/incremental cost each time a project is
introduced to the ASF infrastructure. This effort is not about the
*overall* Infrastructure bottom line (eg. staffing, training, travel
costs) as those costs have *very* tenuous connections to the
incremental cost of a new project.
There is certainly a mild connection to hardware/hosting costs, as we
offer VM services to projects. Those VMs create a very real cost to
the ASF, and we are in-process on a way to track and allocate those costs.
The more direct costs appear to be related to the work that
Infrastructure performs when a podling is accepted, and when a podling
graduates. These events create a lot of work around managing mailing
lists, repositories, Jira, wikis, etc. This is the incremental costs
that we hope to reduce, through automation, once we are done with the
higher-priority work of VM migrations.
-----------------------------------------
Attachment 6: Report from the VP of Conferences [Rich Bowen]
The Call for Papers for ApacheCon Miami closed on February 11th, and
we are now in the process of selecting the schedule.
We have been working on splitting the CFP into topics and tracks, for
easier consideration by our content committee. The distribution of the
ApacheCon CFP was as follows:
* Standard Content (Key signing, BarCamp, State of the Feather, Apache Way, Lightning Talks) 5 sessions
* Apache IoT - 26 sessions, plus 7 OpenWhisk sessions
* TomcatCon - 20 sessions
* Flex Summit - 1 session (They're actually handling their call for content separately, so this isn't cause for concern)
* CloudStack - 43 sessions
* Cassandra - 6 sessions
* Community - 15 sessions (Plus Apache Way goes here, too)
* Containers - 10 sessions
* Incubator - 5 sessions
* Solr/Lucene - 4 sessions
* HTTP Servers - 9 sessions
* Big Data - 25 sessions (Looks like most of these are filed in the wrong CFP, while just a handful were submitted both places)
* Other/Uncategorized - 56 sessions (This is the part that's going to be the hardest work)
Total: 232 sessions
The Apache: Big Data CFP attracted 193 submissions.
The schedule should be announced on March 9th.
The event has been restructured, as we have been talking about doing
for years, into a convention of mini-conferences. This year, we will
be holding the following events, each of which has its own web
presence and marketing:
Apache: Big Data
Apache: IoT (Internet of Things)
CloudStack Collaboration Conference
FlexJS Summit
TomcatCon
Apache Traffic Server and Traffic Control Summit (Monday)
BarCampApache (Monday)
All other topics and projects will be run under the general heading
of ApacheCon, so that smaller projects are still represented.
Admission to any of these events (with the exception of the Traffic
Server event) also grants you access to all of the others.
Further details about this event layout have been elaborated in a
blog post at
https://blogs.apache.org/conferences/entry/final-notice-cfp-for-apachecon
It is hoped that this approach will be much easier to sell tickets
(because the event is about something definable) and acquire
sponsorship (for the same reason).
It is also hoped that other project communities will be watching,
and see the benefits of being part of a larger gathering, and bring
us their conferences next year.
We continue to investigate the possibility of doing an ApacheCon in
Europe later in 2017, but have no concrete plans as yet.
-----------------------------------------
Attachment 7: Report from the Apache Travel Assistance Committee [Melissa Warnkin]
Applications opened on January 25th. To date, we have six applications and two pending submission. These numbers are just shy of the ACEU ’16 numbers for this time. Keep in mind that we had a total of 27 applications at the closing for ACEU ’16. Most applications come in at the last minute.
TAC open emails were sent to committers@, members@, dev@, announce@, discuss@apachecon, and to pmcs@.
Apps close on March 8th
Judges call planned for March 10-12th
Budget approval by March 13th
Sent email to past TACers (ACEU 15, ACNA 16, and ACEU 16) to help spread the word (in their words as a TAC recipient) to their community to encourage participation.
Everything is on track as of this date.
-----------------------------------------
Attachment 8: Report from the VP of W3C Relations [Andy Seaborne]
EME (Encrypted Media Extensions) has been a controversial area in W3C. It
provides a standard browser interface to DRM. The Advisory Committee
review late 2016 has 69 responses with 23 objections, and 46 in favour
of advancing the work to recommendation status.
The main concern is for protection of security and privacy researchers.
A proposal from the Electronic Freedom Foundation was a "covenant" which
required signatories to waive rights of US DMCA for circumvention of DRM
by anyone.
W3C have failed to find a compromise and have undertaken to publish
(March 2nd) guidelines to protect security and privacy researchers.
Initially this is voluntary with a further possibility of being a
requirement for joining future Working Groups.
----
Stian Soiland-Reyes has joined the WebID Community Group, Schema
Architypes Community Group, Schema.org Community Group and Permanent
Identifier Community Group.
His previous membership of these groups was through the the University
of Manchester, but the University is withdrawing from W3C membership.
-----------------------------------------
Attachment 9: Report from the Apache Legal Affairs Committee [Jim Jagielski]
Some discussions regarding whether or not a project can depend on a
codebase with a non-OSI/FSF approved license currently not in the Cat-A
classification. My opinion is that we want our software to be used and
consumed with as little fuss and muss as possible, and a dependency on a
non-OSI approved license is a detriment to that philosophy. Also, it
implies that the ASF is in the business of determining what is, and is
not, OSD compliant. My point in that regard is that that is NOT the ASF's
job; it is clearly one of the key functions of OSI, and always has been.
This is somewhat of a "hard-line" approach, and the board should be
aware of this.
It appears that this is not a popular point-of-view and that others
disagree. I cannot in good conscious agree with a decision and
an action in which we, basically, become authorities on what does
and what does not comply with the OSD. As such, I tender my resignation
and ask the board to assign a replacement at this meeting.
-----------------------------------------
Attachment 10: Report from the Apache Security Team Project [Mark J. Cox]
Stats for January 2016:
10 CVEs issued to projects (some may not be public yet).
e-mails to security@
8 Phishing/spam/proxy/attacks point to site "powered by Apache" or
Confused user due to "Apache" mentioned in OSS licenses
2 Support question
10 Direct Vulnerability report to security@apache.org
3 [httpd] (1 rejected)
2 [ambari]
1 [archiva]
1 [activemq]
1 [cordova]
1 [axis] (rejected)
1 [lucene]
4 Vulnerabilities reported to projects
2 [struts] (1 rejected)
1 [httpd] (already fixed)
1 [couchdb]
-----------------------------------------
Attachment A: Report from the Apache Abdera Project [Ant Elder]
-----------------------------------------
Attachment B: Report from the Apache ActiveMQ Project [Bruce Snyder]
## Description:
Apache ActiveMQ is a popular and powerful open source message-oriented
middleware. Apache ActiveMQ is fast, supports many cross language clients and
protocols, comes with easy to use enterprise integration patterns and many
advanced features while fully supporting JMS 2.0, AMQP 1.0, MQTT, Stomp and
REST.
## Activity:
ActiveMQ
* Continued hardening of AMQP protocol support
** Fixes to some memory leaks and deadlocks added
** Latest release now supports Jetty releases in the 9.3.x family.
* ActiveMQ Artemis
** Apache Artemis 1.5.0 released with follow up of 1.5.1 maintenance release.
** Highlights:
*** Outgoing AMQP connections supported
*** The ability to broker to detect network failures was added
*** CDI Integration was added
*** Apache Artemis 2.0.0 is planned which includes major overhaul of the
Artemis addressing model
*** New model has been proposed and implemented, highlights
include:
**** Better support for address naming across protocols added
**** Ability to define prefixes for specifying pub/sub and point to
point messaging requirements added
**** Consolidation of JMS and other protocol management/configuration
* Both projects are now base-lined on Java 8
* Begin blogging about the ActiveMQ project on https://blogs.apache.org/
## PMC changes:
- Currently 24 PMC members.
- Clebert Suconic was added to the PMC on Thu Oct 27 2016
## Committer base changes:
- Currently 58 committers.
- Christian Schneider was added as a committer on Wed Jan 04 2017
## Releases:
- 5.13.5 was released on Mon Dec 19 2016
- 5.14.2 was released on Wed Dec 07 2016
- 5.14.3 was released on Wed Dec 21 2016
- ActiveMQ Artemis 1.5.0 was released on Mon Nov 07 2016
- ActiveMQ Artemis 1.5.1 was released on Thu Dec 08 2016
-----------------------------------------
Attachment C: Report from the Apache Ambari Project [Yusaku Sako]
## Description:
- Apache Ambari simplifies provisioning, managing, and monitoring of Apache
Hadoop clusters.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- Shortly after the last board report in Nov 2016, the Apache Ambari
community has released 2.4.2 to stabilize the 2.4 line.
The community has also been focusing on preparing for the upcoming 2.5.0
release. So far, more than 1000 fixes have gone into the 2.5 branch from
more than 95 contributors. Aravindan Vijayan has volunteered to be the
release manager for 2.5.0 and he is driving to make the release in the
coming weeks. The project continues to attract new developers and
engage existing ones. The number of committers has been growing
steadily; we now have 80 committers at the time of writing.
## PMC changes:
- Currently 43 PMC members.
- Richard Zang was added to the PMC on Wed Nov 16 2016
## Committer base changes:
- Currently 80 committers.
- New commmitters:
- Buzhor Denys was added as a committer on Fri Dec 30 2016
- Miklos Gergely was added as a committer on Wed Nov 16 2016
- Renjith Kamath was added as a committer on Fri Nov 11 2016
## Releases:
- 2.4.2 was released on Tue Nov 22 2016
## Mailing list activity:
- dev@ambari.apache.org:
- 271 subscribers (up 10 in the last 3 months):
- 108 emails sent to list (101 in previous quarter)
- issues@ambari.apache.org:
- 38 subscribers (up 1 in the last 3 months):
- 10324 emails sent to list (7645 in previous quarter)
- reviews@ambari.apache.org:
- 43 subscribers (up 3 in the last 3 months):
- 3790 emails sent to list (2645 in previous quarter)
- user@ambari.apache.org:
- 466 subscribers (up 9 in the last 3 months):
- 127 emails sent to list (96 in previous quarter)
-----------------------------------------
Attachment D: Report from the Apache Ant Project [Jan Matèrne]
## Description:
Apache Ant is a Java based build tool along with associated tools. It
consists of 3 main projects:
- Ant - core and libraries (AntLibs)
- Ivy - Ant based dependency manager
- IvyDE - Eclipse plugin to integrate Ivy into Eclipse
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
For "project cleanup" we finalized the process of retiring a subproject or
reactivating it [1]. Basically we just place a marker file in the correlating
git repositories, make specific resources read-only and add the name to an
archive-list [2].
With that we voted to archive EasyAnt and all its subcomponents [3]. Archiving
EasyAnt is done. We also voted to archive IvyDE. During that vote few users
came and brought new energy into that project. So we decided to keep it alive
[4].
With Stefan Bodewig as release manager we released two versions of Ant: 1.9.8
and 1.10.0. The 1.10-branch is current development with Java8 as requirement
while 1.9.x is a backport to Java5 - if possible.
Due two important bugfixes the next two releases 1.9.9 and 1.10.1 are in the
pipeline. At time of this writing (2017.02.02) Stefan wants to start to cut
new release candidates.
Update 2017.02.09: Both versions were released on 2017.02.06.
There was a security vulnerability report, passed to us via the Security Team.
Because key of that vulnerability is write access to the buildfile, the Ant
PMC doesn't accept this report as vulnerability, as you could do whatever you
want anyway (<delete>, <ftp>) - access rights by the running user provided.
[1] http://ant.apache.org/processes.html
[2] http://ant.apache.org/archive.html
[3] http://mail-archives.apache.org/mod_mbox/ant-dev/201612.mbox/ajax/%3C000301d25510%2433d37720%249b7a6560%24%40de%3E
[4] http://mail-archives.apache.org/mod_mbox/ant-dev/201612.mbox/ajax/%3C000a01d25511%24f4177a30%24dc466e90%24%40de%3E
## Health report:
Narrowing down the number of subprojects had a positive effect.
## PMC changes:
- Currently 21 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Jean-Louis Boudart on Thu Dec 12 2013
## Committer base changes:
- Currently 29 committers.
- No new committers added in the last 3 months
- Last committer addition was Stephen Haberman at Tue Oct 13 2015
## Releases:
- Ant 1.10.0 was released on Sat Dec 31 2016
- Ant 1.9.8 was released on Sat Dec 31 2016
-----------------------------------------
Attachment E: Report from the Apache Archiva Project [Olivier Lamy]
## Description:
Apache Archiva software is an extensible repository management tool that
helps taking care of your own personal or enterprise-wide build artifact
repository.
## Issues:
There are no issues requiring board attention at this time
## Activity:
Low. We worked on security reports. And some refactoring to get rid of old
jpox library replaced by Apache OpenJpa
## Health report:
3+ people have indicated presence, so has sufficient oversight.
A new committer has been added.
## PMC changes:
- Currently 8 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Jean-Baptiste Onofre on Fri Jul 11 2014
## Committer base changes:
- Currently 21 committers.
- No new committers added in the last 3 months
- Last committer addition was Martin Stockhammer at Thu Sep 22 2016
## Releases:
- Last release was 2.2.1 on Mon May 30 2016
## Mailing list activity:
- users@archiva.apache.org:
- 232 subscribers (up 0 in the last 3 months):
- 7 emails sent to list (26 in previous quarter)
- dev@archiva.apache.org:
- 107 subscribers (down -2 in the last 3 months):
- 15 emails sent to list (94 in previous quarter)
- issues@archiva.apache.org:
- 35 subscribers (up 0 in the last 3 months):
- 4 emails sent to list (79 in previous quarter)
- notifications@archiva.apache.org:
- 14 subscribers (up 0 in the last 3 months):
- 2 emails sent to list (58 in previous quarter)
## JIRA activity:
- 4 JIRA tickets created in the last 3 months
- 0 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment F: Report from the Apache Beam Project [Davor Bonaci]
## Description:
Apache Beam is a unified programming model for both batch and streaming data
processing, enabling efficient execution across diverse distributed execution
engines and providing extensibility points for connecting to different
technologies and user communities.
## Issues:
There are no issues that require the Board's attention at this time.
## Activity:
Apache Beam was established as a top-level project at December’s Board
meeting. This is the second in the series of three consecutive monthly reports
for new projects.
Since last month's report, we have:
- published the second post-graduation release, version 0.5.0,
- added 3 new committers from two different organizations,
- promoted the Python SDK to the master branch with support for two runners.
Over the last month, Apache Beam graduation has been covered in more than a
dozen technical publications and received endorsements from multiple
organizations.
Beam continues to interconnect additional execution engines and data
storage/messaging systems. Since the last report, IO connectors for
Elasticsearch and MQ Telemetry Transport have been released, and additional
connectors for Redis, Apache Cassandra, Apache DistributedLog, Apache Parquet,
RabbitMQ, and Advanced Message Queuing Protocol (AMQP) are in progress.
Going forward, the main focus continues to be on the community growth. On the
technical side, the next major milestone is the availability of the first
stable release, which will include backward-compatibility guarantees.
## Health report:
The community continues to grow steadily, as follows:
- The number of contributors continues to increase.
- Releases continue at a regular pace of 1-1.5 months per release.
- Mailing list activity continues to increase significantly.
## PMC changes:
Currently 14 PMC members. No new PMC members have been added since graduation
two months ago.
## Committer base changes:
Currently 20 committers. Three new committers have been added in the last
month:
- Ahmet Altay was added as a committer on Tue Jan 31 2017.
- Pei He was added as a committer on Tue Jan 31 2017.
- Stas Levin was added as a committer on Tue Jan 31 2017.
## Releases:
In the two months following graduation, Apache Beam has published two
releases:
- 0.4.0 was released on Sun Jan 01 2017.
- 0.5.0 was released on Mon Feb 06 2017.
## Mailing list activity:
Mailing list activity continues to increase across all metrics.
- dev@beam.apache.org
- 332 subscribers (up 56 in the last 3 months)
- 1032 emails sent to list (762 in previous quarter)
- user@beam.apache.org
- 276 subscribers (up 50 in the last 3 months)
- 301 emails sent to list (203 in previous quarter)
## JIRA activity:
- 481 JIRA tickets created in the last 3 months
- 322 JIRA tickets closed/resolved in the last 3 months
## Appendix:
More details about graduation media coverage are available in the “media
recap” blog post:
https://beam.apache.org/blog/2017/02/01/graduation-media-recap.html
-----------------------------------------
Attachment G: Report from the Apache BookKeeper Project [Sijie Guo]
BookKeeper is a distributed, reliable, and high performance
logging service. It has been used as a fundamental service to build
high available and replicated services in companies like Twitter,
Yahoo and Salesforce. It is also the log segment store for Apache
DistributedLog (incubating).
## Issues:
There are no issues requiring board attention at this time
## Activity:
We have a bookkeeper meetup organized by Yahoo on November, 2016.
The community continued with bi-weekly calls for review BPs (bookkeeper
proposals) and discussing issues. The progress is going very well. We have
accepted and reviewed several important BPs, like security, weigh-based
data placement policy, lifecycle management and such.
## Health report:
The community is making good progress on release 4.5.0 . We have been
having discussions around issues and features and there are a few contributors
on track to become.
## PMC changes:
- Currently 8 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Matteo Merli on Wed May 25 2016
## Committer base changes:
- Currently 12 committers.
- No new committers added in the last 3 months
- Last committer addition was Siddharth Boobna at Fri Nov 11 2016
## Releases: - Last release was 4.4.0 on Sun May 15 2016
## Mailing list activity:
The number of subscribers has been going up slightly.
- dev@bookkeeper.apache.org:
- 80 subscribers (up 2 in the last 3 months):
- 618 emails sent to list (322 in previous quarter)
- issues@bookkeeper.apache.org:
- 6 subscribers (up 0 in the last 3 months)
- user@bookkeeper.apache.org:
- 99 subscribers (up 2 in the last 3 months):
- 35 emails sent to list (10 in previous quarter)
## JIRA activity:
- 34 JIRA tickets created in the last 3 months
- 26 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment H: Report from the Apache Brooklyn Project [Richard Downer]
## Description:
- Apache Brooklyn Project is a software framework for modeling, monitoring and
managing cloud applications through autonomic blueprints.
## Issues:
- There are no issues requiring board attention at this time
## Activity:
- Development continues with a regular turnover of pull requests submitted and
merged.
- We have made a release, version 0.10.0
- Two community members were invited to become committers and accepted. Later
they were invited to join the PMC, and also accepted.
## Health report:
- The project continues with a similar level of activity that we have seen
recently. There is a regular turnover of pull requests and commits, and JIRA
tickets, showing that development is at a healthy pace and that users are
feeding back their problems and feature suggestions.
- We continue to monitor our community for potential new committers and PMC
members. Two such individuals joined the PMC since our last report, and I
hope to continue regularly adding individuals.
## PMC changes:
- Currently 13 PMC members.
- Since our last report, Duncan Godwin and Geoff Macartney have joined the
PMC.
## Committer base changes:
- Currently 13 committers.
- Since our last report, Duncan Godwin and Geoff Macartney became committers.
## Releases:
- 0.10.0 was released on Mon Dec 26 2016
## JIRA activity:
- 52 JIRA tickets created in the last 3 months
- 38 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment I: Report from the Apache Buildr Project [Antoine Toulme]
## Description:
Apache Buildr is a build system for Java-based applications, including
support for Scala, Groovy and a growing number of JVM languages and
tools. We wanted something that’s simple and intuitive to use, so
we only need to tell it what to do, and it takes care of the rest.
But also something we can easily extend for those one-off tasks, with
a language that’s a joy to use. And of course, we wanted it to be
fast, reliable and have outstanding dependency management.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
Our activity has slowed down. We have one interesting discussion
slowly going to fix the biggest flaw of Buildr by providing
dependency resolution.
## Health report:
The activity is slow, with 2 active committers.
Very little activity on the user or dev list.
We do see that the project is used at large. For example, the latest
version has been downloaded over 57000 times since last September.
Last time I reported we have started discussing on the dev list
how to improve participation, and have detailed several items
for the next release to engage better our users.
This effort is still ongoing.
## PMC changes:
- Currently 7 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Peter Donald on Tue Oct 15 2013
## Committer base changes:
- Currently 9 committers.
- No new committers added in the last 3 months
- Last committer addition was Tammo van Lessen at Fri Aug 08 2014
## Releases:
- Last release was 1.5 on Fri Sep 23 2016
## JIRA activity:
- 2 JIRA tickets created in the last 3 months
- 6 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment J: Report from the Apache Cassandra Project [Nate McCall]
## Description:
Since the last report, things have stabilized a bit in the community and we
are getting down to business.
After several long conversations on the dev list, we have agreed on the best
way forward of streamlining our release process. Specifically, we have moved
away from the TicTock scheme used throughout the 3.x releases. Though it had
the benefit of creating a better culture of testing, this process proved to be
both incredibly confusing for users as to the current stable version and
overly difficult to maintain for developers for the number of active branches
required.
Our development velocity is lower than I would like. We are still recovering
from the pull out of a large commercial vendor in the space, but independent
activity is increasing and we are steadily adding committers.
It took five voting rounds to release 3.10, but that is more a function of our
agreement to insist on a green test board and being more stringent on blocking
for known issues. I see this particularly as a positive sign of higher
community involvement in the development process as three of the vote vetoes
were a result of end-user discovered issues.
## Issues:
There are no new issues requiring board attention at this time.
## Release Activity:
Apache Cassandra has had the following releases:
- 3.0.10 was released on Wed Nov 16 2016
- 3.10 was released on Fri Feb 03 2017
We are currently working towards an alpha of 4.0 that is a cleanup and
refactoring of some major components.
## PMC changes:
Currently 21 PMC members. No new PMC members added in the last 3 months.
## Committer base changes:
Three new committers have been added in the past quarter:
- Branimir Lambov was added as a committer on Tue Nov 08 2016
- Paulo Motta was added as a committer on Wed Dec 07 2016
- Stefan Powkowinski was voted in, but is pending an ICLA review by his
employer
## Mailing list activity:
Subscriber increases on both mailing lists are marginal, but they are
increases. Activity on the user mailing list is down, but we see that as a
function of not having any new releases before and during the holiday period.
dev@cassandra.apache.org:
- 1613 subscribers (up 28 in the last 3 months):
- 573 emails sent to list (611 in previous quarter)
user@cassandra.apache.org:
- 3135 subscribers (up 30 in the last 3 months):
- 1142 emails sent to list (1548 in previous quarter)
## JIRA activity:
The ratio of closed to created tickets is high, reflective of previous
comments regarding velocity.
- 302 JIRA tickets created in the last 3 months
- 190 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment K: Report from the Apache Clerezza Project [Hasan Hasan]
DESCRIPTION
Apache Clerezza models the RDF abstract syntax in Java and provides
supports for serializing, parsing, and managing triple collections,
as well as a tool to generate the source code of a Java class with
constants for an ontology described in RDF.
Apache Clerezza components are OSGi-based and have the purpose to
ease building of Semantic Web applications and services.
ISSUES FOR THE BOARD
There are no issues requiring board attention at this time.
RELEASE
Latest release was partial-release-201604 created on May 13, 2016.
ACTIVITY
A new unit test class is added to the clerezza-rdf-core.
COMMUNITY
Latest change was addition of a new committer and PMC member on 16.08.2013.
There was a response to the email sent to the dev list requesting
participations as new committers.
INFRASTRUCTURE
There are some suggestions to improve Clerezza Website, in particular
to reflect the current focus of Apache Clerezza.
-----------------------------------------
Attachment L: Report from the Apache Cocoon Project [Thorsten Scherler]
## Description:
Web development framework: separation of concerns, component-based.
## Issues:
Following the step down of Thorsten, the PMC voted for nominating
Cédric Damioli as PMC chair.
## Activity:
The most recent release is 2.1.12 on 2013-03-14
No JIRA issues opened nor resolved since last report
No commits since last report
There's only a little activity on both users and dev mailing-lists.
There have been some quite interesting changes since last release, at
least for 2.1 branch, which would deserve a release.
## PMC changes:
None.
Most recent addition: 2012-07-06
## Committer base changes:
None.
Most recent addition: 2012-07-06
-----------------------------------------
Attachment M: Report from the Apache Community Development Project [Ulrich Stärk]
## Description:
The Community Development PMC is responsible for helping people become
involved with Apache projects
## Issues:
No issues require board attention at the moment.
## Activity:
Community Development Strategy
A key discussion topic this quarter was looking at the refining or re-defining
the goal of Community Development. The project was established with a very
flexible description of 'helping people become involved with Apache projects'
and the discussions highlighted that this was no longer enough and that more
detailed goals, strategies or plans are needed to focus efforts on various
areas. No one has a clear picture of what community development activities are
planned, in progress or completed, or how they fit in any other greater
initiative. By having at least an outline this would allow Community
Development to co-ordinate activities and give potential contributors clear
guidance on what tasks need to be done.
An outline, based on the mailing list discussion, has been created in the
documentation, and we will work towards fleshing that out over the coming
weeks. This is (temporarily) at http://community.staging.apache.org/about/
One comment on the strategy thread highlighted that Community Development as a
mailing list was not very well known (so this links in with some of the
proposed strategy ideas to improve the awareness with the ASF communities
about the role of ComDev and what it does).
Committers Diversity Survey
The Committer Diversity Survey was run in November / December. In total we
received 765 responses (out of a 5861 committer base at the time the survey
was run) which was approx 13% response rate. The survey also got 111 feedback
comments some of which did not give their permission to share or from quote
their comments. A key condition for respondents providing the data was that
The data collected will be used to generate consolidated and aggregated
statistics for the Apache Community Development team and the Apache Software
Foundation. These details may be published as part of Apache presentations and
reports, and made publicly available.
The data from individual responses will not be released.
The survey also got 111 feedback comments some of which can be quoted from.
Those that cannot be quoted will be raised as a general discussion theme.
Next steps will be:
Continue to analyse the information and identify any potential Community
Development related actions Start discussion threads on the various themes and
topics raised to see if they will result in additional actions Discuss
feedback and diversity ideas and if necessary, integrate into diversity
strategy
FOSDEM
A lot of activity this quarter was focussed on preparing for FOSDEM 2017 in
Brussels. The ASF was allocated a booth for the second consecutive year with
the main focus of building awareness of Apache and its projects to the FOSDEM
attendees. An email message was sent out to all ASF projects dev mailing lists
asking if projects wanted to use the opportunity to promote their projects.
Four projects signed up to be present at the booth (Mesos, OpenOffice,
Zeppellin and Lucene/Solr) and 20 presentations at FOSDEM were from ASF
community members.
Daniel worked together with Sally to get some new banners were produced
including one with all the current logos for all ASF projects. This was very
useful for raising ASF brand awareness as many attendees knew many project
names but had not associated them with Apache.This means that there is more
work to be done in reinforcing the ASF brand externally.
Daniel Gruno and Sharan Foga were present at FOSDEM thoughout the weekend at
the ASF booth and received support from other ASF community members.
Relaunch of ComDev Blog
The Community Development Blog was relaunched in November and currently has 2
monthly updates published. A third will be published in February. The aim is
to continue to provide simple regular updates to keep people informed about
key things that have happened or are planned in Community Development.
Google Summer of Code
Another big discussion topic discussed this quarter month was around ASF
involvement in Google Summer of Code (GSoC) and how we might be able to gather
data and statistics that show more clearly how GSoC benefits our projects and
communities.
Apache Community Development's main goal is about developing Apache
communities so it would be good to have actual data about the GSoC program
within the ASF and how it supports us in achieving this.
Addition of Statistics on Projects Directory
A new "Projects Statistics" page has been added to Projects Directory:
https://projects.apache.org/statistics.html
Global ASF statistics on code and discussions evolution are published using
Snoot.io service data.
## PMC changes:
The PMC currently features 22 members. The last addition has been Sharan Foga
on 2016-11-15
Currently 22 PMC members.
Sharan Foga was added to the PMC on Tue Nov 15 2016
## Committer base changes:
Currently 23 committers. Sharan Foga was added as a committer on Tue Nov 15
2016
## Releases:
None.
## Mailing list activity:
Mailing list activity has been high despite a slight drop off over the holiday
period. Many interesting topics have been raised that have resulted in
significant discussions and it is a good sign that mailing list traffic is
increasing because people want to join discussions.
dev@community.apache.org:
728 subscribers (up 9 in the last 3 months): 557 emails sent to list (321 in
previous quarter)
-----------------------------------------
Attachment N: Report from the Apache CouchDB Project [Jan Lehnardt]
## Description:
- CouchDB is a database with seamless multi-master sync that scales from Big
Data to Mobile, with an intuitive HTTP/JSON API, and designed for reliability.
## Issues:
- There are no issues requiring board attention at this time
## Activity:
- Post 2.0 release activities including helping users with new onboarding
and migration of existing apps (it is straightforward), Sorting out all
the small things that people find after a major release.
- Continue to prepare a 2.1.0 release.
- More in-depth discussion about project direction for 3.0 and beyond.
- The 2017 CouchDB Dev Summit just concluded, results publication is
forthcoming.
- The Dev Summit is a small group face-to-face meeting (last held in 2012)
that produces recommendations for the developer mailing list.
## Health report:
- Nothing outstanding to report, the project is humming along nicely.
Nevertheless, we are working on measures to increase contribution yet
again.
## PMC changes:
- Currently 14 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Garren Smith on Mon Oct 19 2015
## Committer base changes:
- Currently 56 committers.
- Michael Hall was added as a committer on Sat Dec 31 2016
## Releases:
- 2.0.0 was released on Tue Sep 20 2016
## JIRA activity:
- 63 JIRA tickets created in the last 3 months
- 35 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment O: Report from the Apache Creadur Project [Brian E Fox]
Apache Creadur creates and maintains a suite of open source software related
to the auditing and comprehension of software distributions. Any language and
build system are welcomed.
Status
------
Same as the last report, email and commit activity continues to move along
slowly. There has been not much other activity.
Creadur is primarily used by other Apache projects to help check for
conformity to ASF standards. This is why the project team is primarily
comprised of members and committers from other ASF projects. The risk of the
project foundering is therefore very low despite the ongoing lack of progress.
If someone has an itch to scratch, it will no doubt get fixed.
Community
---------
In September 2016 Karl Heinz Marbaise was elected to join the PMC / Commit.
Releases
--------
Apache Rat 0.12 was released in June, 2016
Apache Rat 0.11 was released in August, 2014
Apache Rat 0.10 was released in September, 2013.
Community Objectives
--------------------
Find more committers
-----------------------------------------
Attachment P: Report from the Apache CXF Project [Daniel Kulp]
## Description:
Apache CXF is an open source services framework. CXF helps you
build and develop services using frontend programming APIs, like JAX-WS and
JAX-RS. These services can speak a variety of protocols such as SOAP,
XML/HTTP, RESTful HTTP, or CORBA and work over a variety of transports such as
HTTP, JMS or JBI.
There are also two sub-projects that leverage CXF:
Fediz - Fediz helps you to secure your web applications via the standard
WS-Federation Passive Requestor Profile.
DOSGi - is the reference implementation of the Distribution Provider
component of the OSGi Remote Services Specification
## Issues:
There are no issues requiring board attention at this time
## Activity:
There was quite a lot of activity on both the CXF main codebase and the Fediz
subproject. 3 separate security advisories were made public, 2 in CXF and 1
in Fediz. Those were a main driver for releases late in 2016. We’ve also
released 3.1.10 with hopes of being able to concentrate on 3.2.0 and get that
out this quarter. In addition, almost 100 JIRA’s have been resolved this
period as we try and wrap up some of the new ideas and stabilize things for
3.2.0.
## PMC changes:
- Currently 24 PMC members.
- No new PMC members in the last 3 months.
- Last PMC addition: Sun Sep 18 2016 (Francesco Chicchiriccò)
## Committer base changes:
- Currently 38 committers.
- Last committer addition: Sat Nov 19 2016 (Neal Hu)
- There were also discussions on 3 other potential new committers. Hoping to
see a little more contributions from each.
## Releases:
- 3.0.12 was released on Sun Dec 11 2016
- 3.1.9 was released on Sun Dec 11 2016
- 3.1.10 was released on Mon Jan 30 2017
-----------------------------------------
Attachment Q: Report from the Apache DeltaSpike Project [Thomas Andraschko]
## Description:
Apache DeltaSpike is a suite of portable CDI (Contexts & Dependency
Injection) extensions intended to make application development easier when
working with CDI and Java EE. Some of its key features include:
- A core runtime that supports component configuration, type safe messaging
and internationalization, and exception handling.
- A suite of utilities to make programmatic bean lookup easier.
- A plugin for Java SE to bootstrap both JBoss Weld and Apache OpenWebBeans
outside of a container.
- JSF integration, including backporting of JSF 2.2 features for Java EE 6.
- JPA integration and transaction support.
- A Data module, to create an easy to use repository pattern on top of JPA.
- Quartz integration
Testing support is also provided, to allow you to do low level unit testing
of your CDI enabled projects.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
Currently we preparing the upcoming release 1.8, which mainly consists of a
reworked configuration API and bugfixes.
## Health report:
The community and developers activity was less than average in the last
quarter. This just means that DeltaSpike is quite stable and already
covers many real-life usecases. The activity will likely be higher again
if we preparing our code-base this year for Java 8 / Java EE8.
## PMC changes:
- Currently 19 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Harald Wellmann on Thu May 19 2016
## Committer base changes:
- Currently 33 committers.
- No new committers added in the last 3 months
- Last committer addition was Matej Novotny at Fri Jun 03 2016
## Releases:
- 1.7.2 was released on Sun Nov 06 2016
## Mailing list activity:
- users@deltaspike.apache.org:
- 180 subscribers (up 1 in the last 3 months):
- 22 emails sent to list (71 in previous quarter)
- dev@deltaspike.apache.org:
- 104 subscribers (down -1 in the last 3 months):
- 208 emails sent to list (233 in previous quarter)
## JIRA activity:
- 22 JIRA tickets created in the last 3 months
- 19 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment R: Report from the Apache Drill Project [Parth Chandra]
## Description:
- Drill is a Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage
## Issues:
- There are no issues requiring board attention at this time
## Activity:
- Since the last board report, Drill has released version 1.9
- Drill has added many new features since the last report. More Parquet
reader performance improvements, temp tables support, an improved work
assignment algorithm, and an httpd format plugin.
- Work continues on improved use of statistics, and security enhancements
(including support for Kerberos) and a sort with managed memory usage.
## Health report:
- The project is healthy. Development activity is high and is reflected in an
increase in the number of mails to the mailing list, many new pull requests
and increased activity in JIRA. Two new committers were added in the last
period.
## PMC changes:
- Currently 18 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Sudheesh Katkam on Wed Oct 05 2016
## Committer base changes:
- Currently 30 committers.
- New commmitters:
- Chris Westin was added as a committer on Wed Nov 30 2016
- Neeraja Rentachintala was added as a committer on Wed Nov 16 2016
## Releases:
- 1.9.0 was released on Mon Nov 28 2016
## Mailing list activity:
- Mailing list activity is healthy.
- dev@drill.apache.org:
- 436 subscribers (up 2 in the last 3 months):
- 1919 emails sent to list (1599 in previous quarter)
- issues@drill.apache.org:
- 20 subscribers (up 0 in the last 3 months):
- 2618 emails sent to list (2003 in previous quarter)
- user@drill.apache.org:
- 577 subscribers (up 12 in the last 3 months):
- 372 emails sent to list (430 in previous quarter)
## JIRA activity:
- 236 JIRA tickets created in the last 3 months
- 85 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment S: Report from the Apache Eagle Project [Edward Zhang]
## Description
Apache Eagle is an open source analytics solution for identifying security and
performance issues instantly on big data platforms.
## Issues
There are no issues requiring board attention at this time
## Activity
1. In Jan, one meet-up in Shanghai between eBay and China Telecom Shanghai R&D
2. In Jan, Eagle was presented in Bangalore by Senthil, Kumar
## Health report
The community is still active especially after graduation, and going to invite
Jayesh Senjaliya who is active in community to be committer.
## PMC changes
Currently 15 PMC members. No new PMC members have been added in last 3 months.
## Committer base changes
Ji Jun Tang was added as a committer on Mon Jan 23 2017
## Releases
No release
## Mailing list activity
- dev@eagle.apache.org:
- 72 subscribers (up 4in the last 3 months):
- 836 emails sent to list (3384 in previous quarter)
- issues@eagle.apache.org:
- 16 subscribers (down -2 in the last 3 months):
- 1172 emails sent to list (1 in previous quarter)
- user@eagle.apache.org:
- 47 subscribers (up 4 in the last 3 months):
- 12 emails sent to list (4 in previous quarter)
## JIRA activity
- 127 JIRA tickets created in the last 3 months
- 133 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment T: Report from the Apache Empire-db Project [Rainer Döbele]
## Description:
- Apache Empire-db is a relational database access engine that takes an
SQL-centric approach in comparison to traditional OR-Mappers
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- Since the last board report we have approved and released version 2.4.6
- We have also updated and documented the release procedure
## PMC changes:
- Currently 10 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Jan Glaubitz on Sun Jul 10 2016
## Committer base changes:
- Currently 9 committers.
- No new committers added in the last 3 months
- Last committer addition was Jan Glaubitz at Mon Oct 05 2015
## Releases:
- 2.4.6 was released on Tue Jan 17 2017
## Mailing list activity:
- dev@empire-db.apache.org:
- 37 subscribers (up 0 in the last 3 months):
- 48 emails sent to list (30 in previous quarter)
- user@empire-db.apache.org:
- 54 subscribers (up 0 in the last 3 months):
- 5 emails sent to list (10 in previous quarter)
## JIRA activity:
- 5 JIRA tickets created in the last 3 months
- 4 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment U: Report from the Apache Flume Project [Hari Shreedharan]
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.7.0, released on October 16, 2016.
* No other releases are planned at this time.
CURRENT ACTIVITY
* Project activity has picked up over the past few months, and a number of new
contributors are active contributing code, reviews and responding to user
and developer queries on mailing lists.
* A total of 31 issues have been filed, and 15 issues have been resolved in
the last three months.
* Approximately 352 messages were exchanged on the dev list in the past three
months, while a total of 58 were exchanged on the user list in this period.
COMMUNITY
* The last time a committer was added to the project was on September 21,
2016.
* Currently there are:
- Total of 295 subscribers to the developer list
- Total of 694 subscribers to the user list
- Total of 28 committers
- Total of 21 PMC members
* The last time a new PMC member was elected for the project was on November
4, 2014.
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
None on the horizon.
General status:
The most recent release is 0.9 on 2011-02-07.
Since then there have been some changes, but it will need someone to
initiate the release process.
No activity on the user mail list. However it never gets used much anyway.
There was a little activity on the dev mail list via the issue tracker. One
PMC member encountered and commented on an old issue. No further comments.
The same PMC member made a few enhancements to the new "fleece" skin.
Two PMC members were present during the quarter.
At this report, two other PMC members responded to my draft report.
This confirms that there are sufficient people hanging around for us to
potentially be able to make a decision or encourage new contributors.
At the last quarter's report, there were some board comments:
It was discovered that "svn" commit messages were not shown on the
lists.a.o service. I followed up that. Many thanks to Seb for the excellent
investigation. It revealed that the problem was much wider than Forrest.
Initial configuration and loading of the lists.a.o archive was lacking.
Now fixed.
The other matter is that we should be making a release. Yes, i have noted
this in each of our board reports. The procedure is documented, but it
requires someone to commence it. The board prompt did not encourage any
discussion by the project.
Project status:
Activity: Low
3+ people have indicated presence, so has sufficient oversight.
Security issues published:
None.
Progress of the project:
Some enhancements to the new "fleece" bootstrap-based skin.
-----------------------------------------
Attachment W: Report from the Apache Geode Project [Mark Bretl]
## Description:
- Apache Geode provides a database-like consistency model, reliable
transaction processing and a shared-nothing architecture to maintain very
low latency performance with high concurrency processing.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- Geode was promoted to TLP status in the November 2016 board meeting. Since
that time:
- A new TLP repo was created and populated
- Work on the first TLP-level release has been underway.
- Released version 1.1.0. The release addresses 252 JIRA tickets. For a
complete list, please see the Geode Release Notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318420&version=12338352
- A new code contribution is in progress for C++ and C# native clients and
their accompanying documentation. After a lively discussion on the dev list,
it was decided to create a separate Git repo to house this code.
## Health report:
- Mailing lists remain active and productive.
- JIRA tickets show that issues continue to be identified and resolved.
- We’re continuing to work on attracting new contributors and making it easier
to participate in the community.
## PMC changes:
- Jared Stewart was added to the PMC on Sun Feb 12 2017
- Kevin Duling was added to the PMC on Wed Jan 18 2017
- Ken Howe was added to the PMC on Wed Jan 18 2017
- Last PMC addition: Sun Feb 12 2017 (Jared Stewart)
- Currently 33 PMC members.
## Committer base changes:
- Jared Stewart was added as a committer on Thu Feb 09 2017
- Kevin Duling was added as a committer on Sat Jan 14 2017
- Last committer addition: Thu Feb 09 2017 (Jared Stewart)
- Currently 78 committers.
## Releases:
- 1.1.0 was released on Wed Feb 15 2017
- 1.0.0-incubating issued on October 25, 2016
## Mailing list activity:
Following an initial ramp-up in subscriber ship corresponding to TLP
acceptance, mailing lists have remained active and have maintained consistent
usage levels.
- dev@geode.apache.org:
- 155 subscribers (down -4 in the last 3 months):
- 4562 emails sent to list (1761 in previous quarter)
- issues@geode.apache.org:
- 56 subscribers (up 1 in the last 3 months):
- 1042 emails sent to list (3050 in previous quarter)
- user@geode.apache.org:
- 206 subscribers (up 12 in the last 3 months):
- 306 emails sent to list (149 in previous quarter)
## JIRA activity:
- 344 JIRA tickets created in the last 3 months
- 278 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment X: Report from the Apache Geronimo Project [Alan Cabrera]
-----------------------------------------
Attachment Y: Report from the Apache Giraph Project [Avery Ching]
-----------------------------------------
Attachment Z: Report from the Apache Gora Project [Lewis John McGibbney]
## Description:
- Apache Gora provides an in-memory data model and persistence for big data.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- Gora has recently seen some encouraging activity for new community members
in the form of bug fixes. We have one blocking issue prior to our 0.7 release.
This has been pending for quite some time.
## Health report:
- Gora would benefit from the 0.7 release as we have a numbef of new datastores
which, if released, could help the community spirit. We are still working on
the 0.7 blocker, however once done we can VOTE.
## PMC changes:
- Currently 23 PMC members.
- Kevin Ratnasekera was added to the PMC on Thu Jan 12 2017
## Committer base changes:
- Currently 23 committers.
- Kevin Ratnasekera was added as a committer on Wed Dec 07 2016
## Releases:
- Last release was 0.6.1 on Sun Sep 13 2015
## Mailing list activity:
- 2016Q4 - 2017Q1 was a reasonably quiet period. We seen encouraging
figures for our user@ list.
- dev@gora.apache.org:
- 74 subscribers (down -1 in the last 3 months):
- 92 emails sent to list (492 in previous quarter)
- user@gora.apache.org:
- 77 subscribers (up 2 in the last 3 months):
- 22 emails sent to list (2 in previous quarter)
## JIRA activity:
- 7 JIRA tickets created in the last 3 months
- 1 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AA: Report from the Apache Groovy Project [Guillaume Laforge]
## Description:
Apache Groovy is a multi-faceted programming language for the Java platform.
Groovy is a powerful, optionally typed and dynamic language, with static-
typing and static compilation capabilities, aimed at multiplying developers’
productivity thanks to a concise, familiar and easy to learn syntax. It
integrates smoothly with any Java program, and immediately delivers to your
application powerful features, including scripting capabilities, Domain-
Specific Language authoring, first class functional programming support and
runtime and compile-time meta-programming.
## Issues:
The area we still haven’t managed to find time to tackle is with regards to
our website hosting. The community facing and developer facing aspects
are still merged into one single website, which is still hosted on the
groovy-lang.org domain, which although belonging to the Apache Software
Foundation is not under the *.apache.org namespace. As agreed previously, we
intend on keeping the community facing side under the familiar
groovy-lang.org website, while separating the developer oriented part
under the groovy.apache.org website. But the focus on the release process
was higher on our priority list and we haven’t had time to dig deeper in
this area unfortunately. It’s next on our priority list.
## Activity:
We made a lot of progress with our release process automation, and the 2.4.8
release was made thanks to the new process. So the community is very happy
to see us moving forward with newer releases, with a clearer vision of the
roadmap of upcoming versions, as well as with the upcoming new features.
In addition to the treatment of the vulnerability issue that got solved and
released in 2.4.8, and the usual bug fixing to continue to stability the
platform, the big key area of work has been with the new Antlr v4 parser, in
the “parrot” branch, which brings Java 8 syntax elements, some new
Operators, as well as some missing elements from previous versions of Java.
Groovy has historically been adopted by Java developers for its
familiarity in terms of syntax with Java, so these new developments continue
along that theme.
## Health report:
We closed the year 2016 with our record number of downloads, across Maven
Central and JFrog Bintray, with 23 million downloads, up from 12.7 millions
the previous year. The last four months of the year, the monthly downloads
exceeded 2.2 millions every month.
The @ApacheGroovy Twitter account gained more followers, totalling 2266
followers, compared to last report’s sub 2k. On the TIOBE programming index
the project left the top 20 after several months in -- fluctuations in
search rankings are pretty high. The LinkedIn Groovy group moved from 4717
members to 4755. And the community-driven Slack channel went from 400 to
535 members.
## PMC changes:
- Currently 9 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Andrew Bayer on Wed Nov 18 2015
## Committer base changes:
- Currently 18 committers.
- New commmitters:
- Sergei Egorov was added as a committer on Thu Dec 08 2016
- Daniel Sun was added as a committer on Thu Nov 03 2016
We’re very happy to have added those two new committers who are contributing
two key new aspects to Apache Groovy: the new language parser that adds Java 8
syntax constructs (among other things), and a macro system to help make
AST code transformation even more easier to implement.
This quarter, 79 commits were contributed from 12 contributors including 7
non-committer contributors (5 new).
## Releases:
- 2.4.8 was released on Sat Jan 14 2017
## Mailing list activity:
- users@groovy.apache.org:
- 393 subscribers (up 15 in the last 3 months):
- 286 emails sent to list (132 in previous quarter)
- dev@groovy.apache.org:
- 223 subscribers (up 7 in the last 3 months):
- 627 emails sent to list (306 in previous quarter)
- issues@groovy.apache.org:
- 9 subscribers (up 0 in the last 3 months)
- notifications@groovy.apache.org:
- 31 subscribers (up 1 in the last 3 months):
- 721 emails sent to list (1215 in previous quarter)
## JIRA activity:
- 81 JIRA tickets created in the last 3 months
- 75 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AB: Report from the Apache Hama Project [Edward J. Yoon]
-----------------------------------------
Attachment AC: Report from the Apache HTTP Server Project [Eric Covener]
## Description:
The Apache HTTP Server Project develops and maintains an
open-source HTTP server for modern operating systems.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
* Development pace is slow with a few notable exceptions
(HTTP/2, security investigations)
## Health report:
* Overall things are healthy. Routine tickets/emails
are being addressed in a timely manner.
* The backlog of aged security issues has been mostly cleared out with last
reporting periods releases.
## PMC changes:
* Daniel Ruggeri was added to the PMC on Wed Dec 28 2016
* Jacob Champion was added to the PMC on Wed Dec 28 2016
* Lucien Gentis was added to the PMC on Fri Jan 06 2017
* Luca Toscano was added to the PMC on Sat Jan 07 2017
* Currently 48 PMC members.
## Committer base changes:
* No new committers this period
* * Last new committer: Evgeny Kotkov was added on Tue Sep 20 2016
* Currently 116 committers.
## Releases:
* Stable release: 2.4.25 on December 21, 2016
* Legacy release: 2.2.32 on January 13, 2017
-----------------------------------------
Attachment AD: Report from the Apache HttpComponents Project [Asankha Perera]
## Description:
- The Apache HttpComponents project is responsible for creating and
maintaining a toolset of low-level Java components focused on HTTP and
associated protocols
## Issues:
- There are no issues requiring board attention at this time
## Activity:
- We are currently working on adding support for HTTP/2 protocol to HttpCore
and HttpClient.
- We understand that our web site could be improved to migrate away from
XML/APT and Maven generation to something like Markdown and jekyll. This
would be something we plan to look into in the months ahead.
- Our builds now appear on Travis CI.
- The team also plans to migrate away from svn into git sometime after a
few more releases related to HTTP/2.
## Health report:
- Overall the project remains active. Although established in late 2007
the project remains stable and active as seen by JIRA and Emails.
- The number of emails could be seen as low, but it is stable like the state
of the project, and we still have interested people joining into the
dev list hoping to contribute, and saying so on the list.
## PMC changes:
- Currently 9 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Michael Osipov on Mon Aug 24 2015
## Committer base changes:
- Currently 18 committers.
- No new committers added in the last 3 months
- Last committer addition was Julian Sedding at Fri Sep 30 2016
## Releases:
- HttpAsyncClient 4.1.3 GA was released on Fri Feb 10 2017
- HttpClient 4.5.3 GA was released on Thu Jan 26 2017
- HttpComponents project POM (a.k.a. parent POM) was released on Thu Dec 01
2016
- HttpCore 4.4.6 GA was released on Thu Jan 12 2017
- HttpCore 5.0-alpha2 was released on Tue Dec 27 2016
## JIRA activity:
- 37 JIRA tickets created in the last 3 months
- 38 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AE: Report from the Apache Ignite Project [Denis Magda]
## Description:
The Apache Ignite (TM) In-Memory Data Fabric is a high-performance, integrated
and distributed in-memory platform for computing and transacting on
large-scale data sets in real-time, orders of magnitude faster than possible
with traditional disk-based or flash technologies.
Apache Ignite (TM) provides many in-memory components to improve performance
and scalability of user applications, including in-memory data grid, in-memory
sql grid, in-memory compute grid, in-memory streaming, and more.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
- The community worked hard and managed to release Apache Ignite 1.8 on Dec 8,
2016. The release encompasses a brand new In-Memory SQL Grid component that
allows to work with an Ignite cluster as with an in-memory database fully
relaying on SQL syntax. In addition, the release introduces support of
Redis compliant client, improvements in Ignite.NET and deadlock detection
mechanism. More details:
https://blogs.apache.org/foundation/entry/the-asf-asks-have-you
- Presently the community is approaching the next major release - Apache
Ignite 2.0. The new version will be based on new memory architecture that
will keep down an impact of Java Garbage Collectors. Also there will be many
core and SQL related performance.
- The community refined the technical documentation making it clearer and
actively maintains the blogging list - https://ignite.apache.org/blogs.html
- Apache Ignite enrolled in Google Summer of Code 2017 program
(https://goo.gl/4SpTzK) and submitted a bunch of talks to upcoming ApacheCon
conference.
## Health report:
The mailing statistics, project evolvement, releases delivery and overall
community engagement shows that the state of the project in a good shape.
However, the community has not promoted contributors to committers and
committers to PMC members for a long time. PMC members are willing to motivate
and support the most active contributors and committers during the next
quarter so that they can get to the next level.
## PMC changes:
- Currently 24 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Denis Magda on Sun Sep 27 2015
## Committer base changes:
- Currently 32 committers.
- Igor Rudyak was added as a committer on Mon Nov 14 2016
## Releases:
- 1.8.0 was released on Thu Dec 08 2016
## Mailing list activity:
The number of subscribers grows steadily across the dev and user lists. The
of discussion on the dev list increased while slightly went down on the user
list.
- dev@ignite.apache.org:
- 245 subscribers (up 34 in the last 3 months):
- 2213 emails sent to list (1867 in previous quarter)
- issues@ignite.apache.org:
- 24 subscribers (down -1 in the last 3 months):
- 4955 emails sent to list (5042 in previous quarter)
- services@ignite.apache.org:
- 6 subscribers (up 0 in the last 3 months)
- user@ignite.apache.org:
- 399 subscribers (up 46 in the last 3 months):
- 1655 emails sent to list (1954 in previous quarter)
## JIRA activity:
- 469 JIRA tickets created in the last 3 months
- 406 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AF: Report from the Apache Incubator Project [Ted Dunning]
Incubator PMC report for February 2017
The Apache Incubator is the entry path into the ASF for projects and
codebases wishing to become part of the Foundation's efforts.
There are presently 63 podlings incubating. We had one new PMC member and had one podling retire. There were seven podling releases in the month of January.
* Community
New IPMC members:
- Markus Weimer
People who left the IPMC:
- N/A
* New Podlings
- MXNet
- Ratis
* Graduations
The board has motions for the following:
- None
* Retiring Podlings
- Climate Model Data Analyzer
* Releases
The following releases entered distribution during the month of
January:
- 2017-01-03 Apache Juneau 6.0.1
- 2017-01-17 Apache Fineract 0.6.0
- 2017-01-20 Apahce Impala 2.8.0
- 2017-01-24 Apache Gossip 0.1.1
- 2017-01-24 Apache Mnemonic 0.4.0
- 2017-01-28 Apache Atlas 0.7.1
- 2017-01-28 Apache Carbondata 1.0.0
* IP Clearance
- Henri Yandell has stepped up to help revise the IP Clearance page,
improve wording to not sound so closely tied to corporate donations.
* Miscellaneous
- An updated format of the Incubator report will be rolling out in the
March report. A preview based on the February template can be found at
https://wiki.apache.org/incubator/testpage
- We have begun pushing a hard review of both active podlings and mentors
associated. A number of mentors have stepped down from their roles, and
a few podlings have been contacted to begin thinking about retirement.
- Report formatting continues to be an issue until a fix is applied to
whimsy.
- Report contents are much more robust this month, likely due to increased
requests for input in podling reports.
* Credits
- Report Manager: John D. Ament
-------------------- Summary of podling reports --------------------
* Still getting started at the Incubator
- MXNet
- OpenWhisk
- Ratis
- RocketMQ
* Not yet ready to graduate
No release:
- DistributedLog
- iota
- Joshua
- SensSoft
- Toree
Community growth:
- CarbonData
- Edgent
- Fineract
- Guacamole
- Impala
- PredictionIO
- S2Graph
- SystemML
- Tamaya
- Unomi
* In Danger
- Blur
- Sirona
- Milagro
- Toree
* Podlings that only received a single mentor sign off:
- Blur
- DataFu
- Fineract
- iota
- Milagro
- OpenWhisk
- RocketMQ
- Senssoft
- Slider
- Spot
- Tamaya
- Toree
- Unomi
This represents ~50% of all podlings.
* Ready to graduate
The Board has motions for the following:
- None
* Did not report, expected next month
- ODF Toolkit (2 months in a row)
- Sirona
- Weex
----------------------------------------------------------------------
Table of Contents
Blur
CarbonData
DataFu
DistributedLog
Edgent
Fineract
Fluo
Guacamole
Impala
iota
Joshua
Milagro
MXNet
OpenWhisk
PredictionIO
Ratis
RocketMQ
S2Graph
SensSoft
Slider
Spot
SystemML
Tamaya
Toree
Unomi
----------------------------------------------------------------------
--------------------
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. Greater community involvement.
2. Produce releases.
3.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?
Lack of community involvement has brought the topic of retirement to the
blur-dev list.
http://mail-archives.apache.org/mod_mbox/incubator-blur-dev/201702.mbox/%3Cpony-4f6911432c0e56d59d8abe5b65087e9956a6af1e-bfe4bfa9a663176fde9c80c2d11c9dc3c6e81311%40blur-dev.incubator.apache.org%3E
We feel that the board should be aware of a potential retirement to the
project.
How has the community developed since the last report?
Subscriptions: user@ - 61[-1]; dev@ - 77[-1]
The community involvement has not really changed over the past few
months.
How has the project developed since the last report?
- Nothing has changed since the last report.
Date of last release:
2014-07-29
When were the last committers or PMC members elected?
2014-07-28
Signed-off-by:
[ ](blur) Doug Cutting
[X](blur) Patrick Hunt
[ ](blur) Tim Williams
Shepherd/Mentor notes:
John D. Ament:
Sent a note to the podling RE lack of change in status. Asked to
contemplate retirement.
--------------------
Apache CarbonData is an indexed columnar data format for fast analytics on
big data platform, e.g.Apache Hadoop, Apache Spark, etc.
CarbonData has been incubating since 2016-06-02.
Three most important issues to address in the move towards graduation:
1. Already finished 4 apache releases and all driven by different release
managers.
2. The community is growing well:
a. There are more than 60+ contributors from different organizations,
increasing the diversity.
b. Increased mailing list activity, the solutions be discussed by
mailing list and users can get efficient helps to quickly solve
their issues by mailing list
3. Finish all INFRA built: github, CI, website, Cwiki and so on.
We think we are very close to the graduation and we are focused on the
last steps for the graduation.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
None
How has the community developed since the last report?
- Increased mailing list activity: solutions be discussed and decided in
mailing list.
- More than 20+ new contributors from different organizations since
November.
- Organized two meetup, the attendees was more than 100+.
- There are more than 10+ organizations decided to use Apache CarbonData
and 6 of them already formally deployed in business system.
How has the project developed since the last report?
- Since November 1,306 issues+ have been reported on JIRA site and 294
have been resolved or closed. Since November 1,282+ pull requests have
been created and 268+ pull requests have been closed.
- Finished a new release 1.0.0, which improved the ecosystem integration
with Apache Hadoop,Apache Spark,Apache Flink.
- Created Jenkins CI and Travis CI.
- Created the website: http://carbondata.incubator.apache.org.
- Finished podling suitable names search, and the name of "Apache
CarbonData" got approved.
https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-117
Date of last release:
2017-01-29
When were the last committers or PMC members elected?
We elected Kumar Vishal as new committer on 2016-10-15.
We are voting a new Committer(He xiaoqiao) on the private mailing list.
Signed-off-by:
[X] (carbondata) Henry Saputra
[X] (carbondata) Jean-Baptiste Onofre
[X] (carbondata) Uma Maheswara Rao G
Shepherd/Mentor notes:
Drew Farris (shepherd):
Two mentors active on the mailing lists. Healthy community activity and
progress over the last month.
--------------------
DataFu
DataFu provides a collection of Hadoop MapReduce jobs and functions in higher
level languages based on it to perform data analysis. It provides functions
for common statistics tasks (e.g. quantiles, sampling), PageRank, stream
sessionization, and set and bag operations. DataFu also provides Hadoop jobs
for incremental data processing in MapReduce.
DataFu has been incubating since 2014-01-05.
Three most important issues to address in the move towards graduation:
1. Resolve NOTICE and LICENSE issues for binary distributions
2. Continued releases
3. Increased committer activity
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
None
How has the community developed since the last report?
Received a patch from a new contributor.
How has the project developed since the last report?
No updates
Date of last release:
2016-08-10
When were the last committers or PPMC members elected?
July 2016 (Eyal Allweil)
Signed-off-by:
[ ](datafu) Ashutosh Chauhan
[X](datafu) Roman Shaposhnik
[ ](datafu) Ted Dunning
Shepherd/Mentor notes:
Roman Shaposhnik:
I really think we need to do one final push and either graduate or retire.
--------------------
DistributedLog
DistributedLog is a high-performance replicated log service. It offers
durability, replication and strong consistency, which provides a fundamental
building block for building reliable distributed systems.
DistributedLog has been incubating since 2016-06-24.
Three most important issues to address in the move towards graduation:
1. Continue to grow the community, and increase diversity of community.
2. Improve documentation, including documentation of project and processes.
3. Successful releases.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
None
How has the community developed since the last report?
1. Increase in contributions from community.
- 127 created and 103 resolved issues in community JIRA between Nov
2016 and Feb 2017.
2. Lots of engagements on feature proposals - 7 improvement proposals.
3. Increased traffic on the mailing list, in particular, due to committers
engaging more actively with contributors.
- we have 43 people subscribed mail list.
How has the project developed since the last report?
The community is voting for release 0.4.0-incubating.
Date of last release:
None
When were the last committers or PPMC members elected?
N/A
Signed-off-by:
[X](distributedlog) Flavio Junqueira
[X](distributedlog) Chris Nauroth
[X](distributedlog) Henry Saputra
Shepherd/Mentor notes:
Flavio Junqueira:
The project has been progressing well despite the absence of a release.
The community has put a release candidate together, but unfortunately we
didn't that it was missing a few important additions and changes (e.g.,
DISCLAIMER and license header). I'm happy with the community development.
There is interest and new contributors are continuously joining.
--------------------
Edgent
Edgent is a stream processing programming model and lightweight runtime to
execute analytics at devices on the edge or at the gateway.
Edgent has been incubating since 2016-02-29.
Three most important issues to address in the move towards graduation:
1. Create and expand a diverse community of contributors and committers
around the Edgent project
2. Checking of all items in the project's Maturity Model
https://cwiki.apache.org/confluence/display/EDGENT/Apache+Maturity+Model+For+Edgent
3. Create a second release of Apache Edgent with additional features and
fixes.
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?
* A well attended meetup in San Francisco, CA about Apache Edgent was held
on January 18th. It covered introductory concepts of datastreaming, the
positioning of Edgent in the datastreaming universe, and examples and
use cases of Edgent. The meetup was attended by roughly 40 developers.
"Apache Edgent: Datastreaming and Analytics for IoT Devices "
https://www.meetup.com/SF-Data-Science/events/236682354/
* There has been at least one question both asked and answered on
Stackoverflow by a non-committer non-PPMC member of the community.
http://stackoverflow.com/questions/41280097/joining-streams-of-different-types-in-apache-edgent
* Since the last report, at least 5 individuals have subscribed to the
Apache Edgent dev mailing list.
How has the project developed since the last report?
* The first release of Edgent as part of the Apache incubator was created
on 2016-12-15. This represents a large amount of work, including
numerous improvements to connectors, the console, and a complete
overhaul of the build system to use Gradle.
* According to JIRA, the project has added the following:
* November 2016: 6 new issues; 18 issues resolved.
* December: 18 new issues; 29 issues resolved.
* January: 15 new issues; 12 issues resolved
Date of last release:
* The most recent release of Apache Edgent was 2016-12-15.
When were the last committers or PMC members elected?
* In May 2016, we added two new committers and PPMC members, Kathy
Saunders and Queenie Ma.
Signed-off-by:
[ ](edgent) Daniel Debrunner
[ ](edgent) Luciano Resende
[X](edgent) Katherine Marsden
[X](edgent) Justin Mclean
Shepherd/Mentor notes:
Katherine Marsden:
Checking of the Maturity model is not yet complete and is just being
used as an aid to help assess our progress. Hopefully now that we have
a release and with the meetup we will have more people get interested
and involved. The active development community, while still small seems
to be communicating well on the list and it was great to see the
release.
Justin Mclean:
Great work on the release, project progressing along well.
--------------------
Fineract
Fineract is an open source system for core banking as a platform.
Fineract has been incubating since 2015-12-15.
Three most important issues to address in the move towards graduation:
1. Addressing areas of concern raised by community based on our Maturity
Evaluation including:
* Full documentation of our release management process
* Implementation of Findbugs to show commitment to quality of code
* Preparation of our community to respond any security threats or
vulnerabilities that are reported.
* Improvement of backwards compatibility of APIs and communication of
breaking changes with each release.
* Updating Apache Fineract webpage with latest releases.
2. Adding new committers and contributors to the project.
3. Continuing to move over additional documentation and providing full
clarity to our community on how and where to report issues via the
issue tracker.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
How has the community developed since the last report?
* Community continues to stay strongly engaged on the mailing lists with
active reporting of issues via the mailing list and issue tracker.
How has the project developed since the last report?
* The community has made 2 additional releases since the last report.
* Our second release was made on December 21, 2016 with three binding
votes from the community.
* Our third release was made on January 17, 2017 with three binding
votes from the community.
Date of last release:
2017-01-17
When were the last committers or PPMC members elected?
2016-05-16
Signed-off-by:
[ ](fineract) Ross Gardler
[ ](fineract) Greg Stein
[X](fineract) Roman Shaposhnik
--------------------
Fluo
Fluo is a distributed system for incrementally processing large data sets
stored in Accumulo.
Fluo has been incubating since 2016-05-17.
Three most important issues to address in the move towards graduation:
1. Attract new contributors and users
2. Additional releases
3.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
None
How has the community developed since the last report?
* Its been quiet.
How has the project developed since the last report?
* Wrote two blog post to help raise awareness of Fluo.
- http://fluo.apache.org/blog/2016/12/22/spark-load/
- http://fluo.apache.org/blog/2016/11/10/immutable-bytes/
* Made many improvements and bug fixes. Need to start planning for next
release.
* Experimented with setting Apache Logo as twitter header. Shared this
with members list and a few other Apache projects did something similar.
https://twitter.com/apachefluo
Date of last release:
2016-10-28
When were the last committers or PPMC members elected?
Never
Signed-off-by:
[x](fluo) Billie Rinaldi
[x](fluo) Drew Farris
[x](fluo) Josh Elser
Shepherd/Mentor notes:
Josh Elser:
The current podling members are all rather experienced in running
(other) TLPs and this has been obvious in their actions as a podling.
They are doing a very good job, but the group still struggles with
attracting new committers to the project. They are making efforts here,
but not seeing any result from those actions yet. This is the biggest
barrier to graduation, IMO.
--------------------
Guacamole
Guacamole is an enterprise-grade, protocol-agnostic, remote desktop gateway.
Combined with cloud hosting, Guacamole provides an excellent alternative to
traditional desktops. Guacamole aims to make cloud-hosted desktop access
preferable to traditional, local access.
Guacamole has been incubating since 2016-02-10.
Three most important issues to address in the move towards graduation:
1. Identifying contributors with merit warranting committership
2. Engaging mentors to assess podling status and provide guidance
3. Ensuring mentors are subscribed to the lists and are generally aware of
podling status/activities
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
Not at present.
How has the community developed since the last report?
Frequency and complexity of contributions seem to be increasing. Community
presence and activity on the mailing lists has also increased due to the
use of Nabble to provide a forum-like interface.
How has the project developed since the last report?
The project has succeeded in producing its first release under the
Incubator, 0.9.10-incubating, and the process is already underway for
producing the next, with the IPMC vote for release having been started on
2017-01-26.
With the first release out of the way, development is finally moving
smoothly again. We have adopted a branching workflow which allows
development to continue unhindered, with only the release scope being
frozen.
Date of last release:
2016-12-29 (0.9.10-incubating)
When were the last committers or PMC members elected?
The most recent committer, Frode Langelo, was accepted into the
project by VOTE on 2016-04-03, with the required ICLA received on
2016-04-05.
As of the VOTE on 2016-12-09, all committers are implicitly members of the
PPMC.
Signed-off-by:
[X](guacamole) Jean-Baptiste Onofre
[ ](guacamole) Daniel Gruno
[ ](guacamole) Olivier Lamy
[X](guacamole) Jim Jagielski
[X](guacamole) Greg Trasuk
Shepherd/Mentor notes:
Greg Trasuk:
Watching the dev list, I've seen good discussions of features and
engagement of users and potential developers. Community seems to be
operating well and making decisions on-list.
--------------------
Impala
Impala is a high-performance C++ and Java SQL query engine for data stored in
Apache Hadoop-based clusters.
Impala has been incubating since 2015-12-03.
Three most important issues to address in the move towards graduation:
1. Community growth
2. Transition of bug tracker to issues.apache.org
3. Evolution of documentation to describe specifically Apache Impala
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
No
How have the community and project developed since the last report?
Our last report was in November. Since then, there have been 148
commits. 49 commits were authored by non-committers, of which 4 new
commits come from 3 new contributors. dev@ received 496 emails and
user@ received 53. 443 new issues have been filed. There has been one
release (our second Apache release) and we have added one new PPMC
member. Our infrastructure has been transitioning: we moved our
pre-commit testing out of our old, pre-Apache hosting and we have been
actively working with Gavin McDonald on migrating our JIRA hosting.
Date of last release:
2017-01-22
When were the last committers or PPMC members elected?
2017-01-12
Signed-off-by:
[x](impala) Tom White
[x](impala) Todd Lipcon
[ ](impala) Carl Steinbach
[ ](impala) Brock Noland
--------------------
iota
Open source system that enables the orchestration of IoT devices.
iota has been incubating since 2016-01-20.
Three most important issues to address in the move towards graduation:
1. Getting a release out based on the current code base - will will commit
to do that this quarter
2. Using the mailing list to discuss current and future development and
needs - we commit more regular dialogue on the mailing list
3. Growing the community - we have been slow to get off the ground and
need to put more effort in here - we will commit to do more outreach to
grow the community
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
We realize we have been a little slow is getting off the ground as an
Apache Project. I have spoken to Hadrian Zbarcea and explained to him why
this has been the case. We are really committed to iota as a technology
and commit to put more effort into making this a successful project.
How has the community developed since the last report?
No - we need to spend time on this and we will do so.
How has the project developed since the last report?
We have added global performers
Date of last release:
XXXX-XX-XX
When were the last committers or PPMC members elected?
Yes - Barbara Gomes was added as a committer on 12/02/2016
Signed-off-by:
[ ](iota) Daniel Gruno
[ ](iota) Sterling Hughes
[X](iota) Justin Mclean
[ ](iota) Hadrian Zbarcea
Shepherd/Mentor notes:
Justin Mclean:
Project is still having issues with doing development in an open way
after a year of incubation. They now realise this is an issue will
hopefully correct. If not I question if Apache is right place for this
project.
--------------------
Joshua
Joshua is a statistical machine translation toolkit
Joshua has been incubating since 2016-02-13.
Three most important issues to address in the move towards graduation:
1. Putting together a formal release.
2. Identifying specific use cases that we might excel at.
3. Attracting active developers and users.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
None that come to mind.
How has the community developed since the last report?
We have added some new members. The Joshua PPMC has also
been VOTE'ing actively and have received (and are acting upon)
feedback from the IPMC on our mlst recent release candidate.
How has the project developed since the last report?
Things have stalled a bit over the winter holidays, but we have recently
started to pick things up again. As always, a release is imminent.
Date of last release:
N/A.
When were the last committers or PPMC members elected?
Per http://incubator.apache.org/projects/joshua.html:
- 2016-11-16 Michael A. Hedderich (mhedderich) joins the Joshua PPMC +
Committership.
- 2016-11-16 Tobias Domhan (tdomhan) joins the Joshua PPMC + Committership.
- 2016-11-02 Max Thomas (mthomas) joins the Joshua PPMC + Committership.
Signed-off-by:
[ ](joshua) Paul Ramirez
[X](joshua) Lewis John McGibbney
[ ](joshua) Chris Mattmann
[X](joshua) Tom Barber
[ ](joshua) Henri Yandell
--------------------
Milagro
Distributed Cryptography; M-Pin protocol for Identity and Trust
Milagro has been incubating since 2015-12-21.
Three most important issues to address in the move towards graduation:
1. Develop MILAGRO toolbox
2. Creating full working MILAGRO ecosystem, based on MILAGRO crypto
library – further research and development (IoT, blockchain, fractions
etc.)
3. Building the MILAGRO community – engaging developers and
cryptographers, raising awareness and helping to secure future of
internet.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
No.
How has the community developed since the last report?
After ApacheCon in Spain – MILAGRO was in the scope of interest, and we
can see the increasing community interest in MILAGRO ecosystem. In
December 2016 MILAGRO ecosystem draft was published on MILAGRO mailing
list and now we are looking to begin development of new structure.
How has the project developed since the last report?
In last few months the MILAGRO ecosystem proposal was developed and
published in order to organize, and prioritize the MILAGRO workflow. In
order to develop new structure, we are discussing new architecture of
MILAGRO repositories.
Date of last release:
n/a
When were the last committers or PPMC members elected?
n/a
Signed-off-by:
[ ](milagro) Sterling Hughes
[ ](milagro) Jan Willem Janssen
[*](milagro) Nick Kew
Shepherd/Mentor notes:
Nick Kew:
I find it frustrating that after a year in incubation, dev activity and
decisions still appear to be happening away from the dev list.
Consequently there is little community activity beyond sporadic
questions and answers which, while good, could equally be served by
github alone. I have discussed this with some of the team and
understand there are good intentions for a push, and intend to post a
critique of this report to try and 'nudge' the project.
--------------------
MXNet
MXNet is an open-source deep learning framework that allows you to define,
train, and deploy deep neural networks on a wide array of devices, from
cloud infrastructure to mobile devices. It is highly scalable, allowing
for fast model training, and supports a flexible programming model and
multiple languages.
MXNet has been incubating since 2017-01-23.
Three most important issues to address in the move towards graduation:
1. Getting ICLAs signed/private@ populated.
2. Sharing documentation/mentor thoughts on being an Apache committer.
3. Migrating the code/issues over to Apache.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
None
How has the community developed since the last report?
1. This is our first report.
2. The mailing lists are created; with the dev@ list being well populated.
3. ICLAs are being signed.
How has the project developed since the last report?
1. Trademark review seems complete.
2. A vendor, AWS, worked with Sally on a blog posting[1].
Date of last release:
No Apache release yet; still being setup.
When were the last committers or PPMC members elected?
At Proposal time. We have a few folk who asked to join the incubation
proposal after the vote started and will be discussed once private@
is populated.
[1] - https://aws.amazon.com/blogs/aws/excited-about-mxnet-joining-apache/
Signed-off-by:
[X](mxnet) Henri Yandell
[X](mxnet) Markus Weimer
[X](mxnet) Sebastian Schelter
[X](mxnet) Suneel Marthi
Shepherd/Mentor notes:
John D. Ament:
I find it a bit odd that the linked article uses "MXNet" repeatedly but
only refers to it as "Apache MXNet" once near the end of the page.
--------------------
OpenWhisk
OpenWhisk is an open source, distributed Serverless computing platform able
to execute application logic (Actions) in response to events (Triggers) from
external sources (Feeds) or HTTP requests governed by conditional logic
(Rules). It provides a programming environment supported by a REST API-based
Command Line Interface (CLI) along with tooling to support packaging and
catalog services.
OpenWhisk has been incubating since 2016-11-23.
Three most important issues to address in the move towards graduation:
1. Moving github repos under the Apache Github Org (organization move,
repository renames)
2. Working to redirect openwhisk.incubator.apache.org to openwhisk.org,
update openwhisk.org to be Apache compliant
3. Review and update project checklist
http://incubator.apache.org/projects/openwhisk.html
Some items should be mark done (around infra), CLA's have been confirmed
for all Committers. URL/links need to be updated.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
- No issues so far
How has the community developed since the last report?
- All Initial Committers now have ICLA’s and have access to private email
list
- Nearly all pre-Incubator active contributors have signed ICLAs, a few
new contributor ICLAs have been received
- Project GitHub (all repos.) now govern access via 3 “Teams” Committer
(write), Contributor-CLA (read), Contributor (read/default)
- “dev", “private” email list traffic continues to be healthy; positive
discussion of a few new code feature/change topics
- GitHub project “Stars” = 1024 (a nice binary number), up a couple dozen
from last month
How has the project developed since the last report?
- Updated CONTRIBUTING.md to ref. Apache processes, Added CREDITS.txt to
all repos., in process of changing all code headers to use Apache
approved text. Need to update Travis CI checks to look for new header
(per repo. basis)
- Confluence WIKI established:
https://cwiki.apache.org/confluence/display/OPENWHISK/OpenWhisk+Project+Wiki
- added project overview and contributor/committer role/process
descriptions
- website updates continue, now include “Incubator” disclaimer, working
issues opened by community to list “supporters” and provide a form to
submit to request to be added.
- deprecated “whisk” object for Nodejs6 runtime (javascript)
actions/functions in favor of single dictionary and use of Nodejs
built-in “promises”
- Size limits discussed and being updated for per-request/response for
actions (and sequences) to preserve performance/reliability
- Discussing proposals for the proper use and optimization of KV stores
for configurations information (along with Ansible for deployments)
- API gateway moved to support LUA as plug-in model, added OAuth support.
Client ID/secret validation, Dynamic upstream routing using Redis
- An OpenWhisk plug-in contribution was accepted for the serverless.com
framework
https://serverless.com/blog/openwhisk-integration-with-serverless/
Date of last release:
- No release yet
When were the last committers or PPMC members elected?
- No activity
Signed-off-by:
[ ](openwhisk) Felix Meschberger
[ ](openwhisk) Isabel Drost-Fromm
[X](openwhisk) Sergio Fernández
Shepherd/Mentor notes:
John D. Ament:
OpenWhisk is our GitHub as master guinea pig. However, they still don't
have source code in our organization. Not sure what we can do to help, or
why that isn't listed as a problem or issue.
--------------------
PredictionIO
PredictionIO is an open source Machine Learning Server built on top of
a state-of-the-art open source stack, that enables developers to manage and
deploy production-ready predictive services for various kinds of machine
learning tasks.
PredictionIO has been incubating since 2016-05-26. The initial code for
PredictionIO was granted on 2016-06-16. The second grant of PredictionIO
templates and SDKs was granted on 2016-09-20.
Three most important issues to address in the move towards graduation:
1. Establish a formal release schedule and process, allowing for
dependable release cycles in a manner consistent with the Apache way.
2. Grow the community to establish diversity of background.
3. Transition remaining former PredictionIO users from google-groups to
ASF mailing lists.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?
None
How has the community developed since the last report?
1. Both user and development mailing lists are more active than the last
report.
2. There are major feature contributions from both new committers and the
community.
3. The ecosystem around engine templates is gaining traction. There are
several new templates added to the engine template gallery.
4. Local user groups are budding, e.g. Japan PredictionIO User Group.
How has the project developed since the last report?
1. Several major feature contributions are under review.
2. The second release is on track for early February release.
3. There have been active discussions which have driven a solid roadmap
for future releases, especially centering around microservice
architecture, stateless builds, and running from anywhere with a
centralized metadata registry.
Date of the last release:
Apache PredictionIO 0.10.0-incubating on 2016-10-17
When were the last committers or PMC members elected?
Chan Lee was elected as committer and PMC member on Nov 14, 2016.
Marcin Ziemiński was elected as committer and PMC member on Nov 14, 2016.
Signed-off-by:
[X](predictionio) Andrew Purtell
[ ](predictionio) James Taylor
[ ](predictionio) Lars Hofhansl
[x](predictionio) Luciano Resende
[ ](predictionio) Xiangrui Meng
[X](predictionio) Suneel Marthi
Shepherd/Mentor notes:
--------------------
Ratis
Ratis is a java implementation for RAFT consensus protocol. Ratis aims to
make raft available as a java library that can be used by any system that
needs to use a replicated log.
Ratis has been incubating since 2017-01-03.
Three most important issues to address in the move towards graduation:
1. Setup wiki, jenkins
2. Start active development in Apache.
3. Make the first release.
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 are still bootstrapping. The mailing lists
became available very recently.
How has the project developed since the last report?
- This is the first report, we are still bootstrapping. We are working
with INFRA to get committer access.
Date of last release:
None
When were the last committers or PPMC members elected?
Only initial set of committers. This is the first report.
Signed-off-by:
[X](ratis) Chris Nauroth
[x](ratis) Devaraj Das
[ ](ratis) Jakob Homan
[X](ratis) Uma Maheswara Rao G
--------------------
RocketMQ
RocketMQ is a fast, low latency, reliable, scalable, distributed, easy to use
message-oriented middleware, especially for processing large amounts of
streaming data.
RocketMQ has been incubating since 2016-11-21.
Three most important issues to address in the move towards graduation:
1. Grow the community
2. Make our first Apache release
3. Vote in our first committer / PMC members
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
None
How has the community developed since the last report?
* Several people have contributed a number of accepted PRs to the code
base
* Discussions are taking place on the dev@ mailing and traffic has
increased
* Development occurring at https://github.com/rocketmq is going to be
brought back into the project
* Increase in JIRA activity and 80% of raised issues resolved
* Small lull in activity due to Chinese New Year
How has the project developed since the last report?
* Project been successfully moved to Apache infrastructure
* Moved towards creating first Apache release
Date of last release:
No releases yet but first release currently being discussed and will be
voted on soon.
When were the last committers or PPMC members elected?
No elections have taken place yet but discussions are taking place.
Signed-off-by:
[ ](rocketmq) Bruce Snyder
[ ](rocketmq) Brian McCallister
[ ](rocketmq) Willem Ning Jiang
[ ](rocketmq) Luke Han
[X](rocketmq) Justin McLean
Shepherd/Mentor notes:
Justin Mclean:
Project is off to a fast start and will have a release out and is likely
to have committers voted in before next report. There's been IMO a few
teething issues re development outside the project and PRs being closed
with explanation but on-list discussions have resolved these issues
amicably.
--------------------
S2Graph
S2Graph is a distributed and scalable OLTP graph database built on Apache
HBase to support fast traversal of extremely large graphs.
S2Graph has been incubating since 2015-11-29.
Three most important issues to address in the move towards graduation:
1. Make a second release.
2. Attract more users and contributors.
3. Build the developer community in both size and diversity.
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?
* Participated in Apache Big Data and ApacheCon Europe, Sevilla, Spain.
- Core: https://apachebigdataeu2016.sched.com/event/8U0O/graph-processing-with-apache-tinkerpop-on-apache-s2graph-doyung-yoon-kakao-corp
- Use case: https://apachebigdataeu2016.sched.com/event/8U0P/apache-s2graph-incubating-as-a-user-event-hub-hyunsung-jo-daewon-jeong-hwansung-yu-kakao-corp
* Discussion regarding adding new committers is in progress.
How has the project developed since the last report?
* Integration with Apache TinkerPop3 has begun.
* Discussion regarding second release is in progress.
* Issues created - resolved: 25 - 19
Date of last release:
Apache S2Graph 0.1.0-incubating on 2016-11-01.
When were the last committers or PMC members elected?
None
Signed-off-by:
[X](s2graph) Andrew Purtell
[ ](s2graph) Seetharam Venkatesh
[X](s2graph) Sergio Fernández
--------------------
SensSoft
SensSoft is a software tool usability testing platform
SensSoft has been incubating since 2016-07-13.
Three most important issues to address in the move towards graduation:
1. Moving towards the first Incubating release of the source code and other
release artifacts.
2. Grow the Apache SensSoft (Incubating) community.
3. Complete the issues highlighted at the SensSoft Roadmap
https://cwiki.apache.org/confluence/display/SENSSOFT/Roadmap
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
No
How has the community developed since the last report?
SensSoft has seen increased uptake in ongoing DARPA projects meaning that
there is increased opportunity for adoption as the Podling matures and
aims for the first incubating release.
How has the project developed since the last report?
The PPMC have developed a stunning/killer Website which embeds a demo:
http://senssoft.incubator.apache.org
The codebase has seen a bunch of commits and we are ready to move towards
the first incubating release.
Date of last release:
N/A
When were the last committers or PPMC members elected?
Arthi Vezhavendan was added to PPMC and Committer base on 2017-01-24
Signed-off-by:
[ ](senssoft) Paul Ramirez
[X](senssoft) Lewis John McGibbney
[ ](senssoft) Chris Mattmann
--------------------
Sirona
Monitoring Solution.
Sirona has been incubating since 2013-10-15.
Shepherd/Mentor notes:
Justin Mclean:
No report and very little activity on list, last releases in late 2015.
Probably time to ask if there 3 active PMC members and think of ways to
attract committers.
John D. Ament:
Emailed podling, retirement is likely.
--------------------
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:
1. Apache Slider community/PPMC has voted to move portions of Slider into
Apache Hadoop YARN as modules. It is possible that the remaining pieces
will be moved at a later point in time or become obsolete or evolve to
work closely with YARN. Slider PPMC will decide what makes the most
sense as we progress through this exciting time.
2. Getting more external users
3. Growth of a diverse set of developers/committers/PMC members is also
crucial towards the final state of Slider
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?
There has been one new contributor since the last report. Mailing list
activity has been lower due to the bulk of the development moving to an
Apache Hadoop branch, but the lists are still active.
How has the project developed since the last report?
Work continues in parallel on the Apache Hadoop yarn-native-services
branch and on the Slider podling. The bulk of the work has been in
yarn-native-services, while a few Slider patches (related to critical
issues or agent-only issues) have been committed as well.
Date of last release:
2016-06-28 slider-0.91.0-incubating
When were the last committers or PMC members elected?
2015-07-07: Yu (Thomas) Liu
Signed-off-by:
[ ](slider) Arun C Murthy
[x](slider) Devaraj Das
[ ](slider) Jean-Baptiste Onofré
[ ](slider) Mahadev Konar
--------------------
Spot
Apache Spot is a solution stack that provides the capability to ingest IT
related telemetry (network flows, domain name service information and proxy
server logs) and provide unsupervised machine learning capabilities to
identify suspicious activity. The information is organized and presented
using operational analytics so that a security analyst can investigate the
most suspicious connections. Apache Spot is built on an open data model
using Apache Spark and Apache Hadoop.
Spot has been incubating since 2016-09-23.
Three most important issues to address in the move towards graduation:
1. Move infrastructure and development to ASF (code, issues, mailing
list, ...)
2. Build diverse community
3. Demonstrate ability to create releases
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
IPMC this point has been posted on the last two report, we have not
received any feedback in terms of how it goes, please comment.
Please elaborate on the process for code scanning and IP reviews. On the
last report this was brought to attention but no communication was
received.
How has the community developed since the last report?
Community is pushing more aggressively on project interaction which is
good, by opening issues on ASF JIRA, some of them have been closed with
their respective PR for bug fixing. Also developers in Brazil are
proposing a new UI schema by their own, which once is voted will
incorporate as contribution/new functionality towards our first Apache
release.
Adoption rate and popularity of the project has been recognized by
Industry receiving an award from Infoworld as Technology of the year and
also finalist on Edison Awards.
How has the project developed since the last report?
The Spot team launched a new project webpage version which incorporate
the long term vision and objectives of Apache Spot, and also includes a
new documentation package which is similar in structure to other ASF
projects.
Two new processes were published to explain on commits and how to open
issues, providing a structured frame that Community in general can follow
up in order to facilitate follow-up in combination of technology tools,
that can facilitate the life cycle continuity.
During this period 14 pull request were merged over different pipeline
components , as committers work also on the new design for data storage
through non-relational database technologies.
Also facilitating a quick demo of the project, we have updated our
container demo, and added automation in order to reflect those changes as
commits to UI are pulled to ASF Git repository.
Date of last release:
N/A
When were the last committers or PMC members elected?
Last committer was elected on 1/24
Signed-off-by:
[ ](spot) Jarek Jarcec Cecho
[ ](spot) Brock Noland
[ ](spot) Andrei Savu
[X](spot) Uma Maheswara Rao G
--------------------
SystemML
SystemML provides declarative large-scale machine learning (ML) that aims at
flexible specification of ML algorithms and automatic generation of hybrid
runtime plans ranging from single node, in-memory computations, to distributed
computations running on Apache Hadoop MapReduce and Apache Spark.
SystemML has been incubating since 2015-11-02.
Three most important issues to address in the move towards graduation:
1. Grow SystemML community: increase mailing list activity, increase
adoption of SystemML for scalable machine learning, encourage data
scientists to adopt DML and PyDML algorithm scripts, respond to user
feedback to ensure SystemML meets the requirements of real-world
situations, write papers, and present talks about SystemML.
2. Continue to produce releases.
3. Increase the diversity of our project's contributors and 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?
Our mailing list from November through January had 249 messages on a
variety of topics. We gained 2 new contributors to the project since
November 1. On GitHub, the project has been starred 451 times and forked
168 times. Elgamal et al wrote the paper "SPOOF: Sum-Product Optimization
and Operator Fusion for Large-Scale Machine Learning," which was presented
at CIDR'17 in January.
How has the project developed since the last report?
The main project has had 114 commits since November 1. 90 pull requests
have been created since November 1, and 79 pull requests have been closed.
Since November 1, 143 issues have been reported on our JIRA site and 64 of
these have been resolved or closed.
Date of last release:
2016-11-13 (version 0.11.0-incubating)
When were the last committers or PPMC members elected?
2017-01-19 Nakul Jindal (Committer and PPMC)
Signed-off-by:
[x](systemml) Henry Saputra
[x](systemml) Luciano Resende
[ ](systemml) Patrick Wendell
[ ](systemml) Reynold Xin
[ ](systemml) Rich Bowen
--------------------
Tamaya
Tamaya is a highly flexible configuration solution based on an modular,
extensible and injectable key/value based design, which should provide a
minimal but extendible modern and functional API leveraging SE, ME and EE
environments.
Tamaya has been incubating since 2014-11-14.
Three most important issues to address in the move towards graduation:
1. Extend Community
2. Improve Documentation / finish new homepage
3. Start graduation after 0.3 is out
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
We are thinking about graduating after the next release since our new
homepage contains information about many new features and we do have a new
module structure.
How has the community developed since the last report?
On conferences and after Oracle dropped the configuration JSR many
conversations started about Configuration in the Java world. Apart from
bugfixes the main new features is basic OSGi support (currently still in
development in sandbox module).
Weekly hangouts (monday 8pm Berlin time) take place to have shorter
feedback cycles, minutes are communicated via mail.
How has the project developed since the last report?
The infrastructure runs much more smoothly with the new module structure:
core, extensions, sandbox and a separate project for the homepage based on
jBake.
OSGi support is a big thing since different OSGi containers have their
problems. Good contact to Apache Karaf developers.
New homepage with new structure and more information available as
prototype via: https://tamaya.apache.org/jbake/ Homepage is connected to
its repository via gitpubsub.
Date of last release:
2016-04-06
When were the last committers or PPMC members elected?
P. Ottlinger at 2016-04-24.
Signed-off-by:
[X](tamaya) John D. Ament
[ ](tamaya) David Blevins
Shepherd/Mentor notes:
John D. Ament:
Podling is having some initial conversations around graduation.
--------------------
Toree
Toree provides applications with a mechanism to interactively and remotely
access Apache Spark. It enables interactive workloads between applications
and a Spark cluster. As a Jupyter Notebook extension, it provides the user
with a preconfigured environment for interacting with Spark using Scala,
Python, R or SQL.
Toree has been incubating since 2015-12-02.
Three most important issues to address in the move towards graduation:
1. Make a release: The community is working on RC from 0.1.x branch.
Master has moved to start support for Spark 2.0. Currently working on
RC5.
2. Grow a diverse community: We should put some emphasis on growing the
community and making it diverse (the rule is at least three independent
contributors) In progress.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?
NONE
How has the community developed since the last report?
1. Active communication in mailing list and gitter with early adopters
2. Migrated gitter to away from ibm-et/spark-kernel to apache/toree
3. More external contributions being made. Mainly focused on master to
stabilize Spark 2.0 support
How has the project developed since the last report?
1. Still working on 1st release. Removed several legacy binaries from
release builds that were not in compliance with Apache release
processes. Will be starting the vote for RC5 shortly
2. Addressing issues opened by community
Date of last release:
None since incubation.
When were the last committers or PMC members elected?
No new additions since incubation
Signed-off-by:
[X](toree) Luciano Resende
[ ](toree) Reynold Xin
[ ](toree) Hitesh Shah
[ ](toree) Julien Le Dem
Shepherd/Mentor notes:
Drew Farris (shepherd):
Two mentors active on the mailing lists. Evident progress toward 0.1.0
release observed on mailing lists.
--------------------
Unomi
Unomi is a reference implementation of the OASIS Context Server
specification currently being worked on by the OASIS Context Server
Technical Committee. It provides a high-performance user profile and event
tracking server.
Unomi has been incubating since 2015-10-05.
Three most important issues to address in the move towards graduation:
1. Stable release with extended tests
2. Promote the project and grow up the community
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
None
How has the community developed since the last report?
The PPMC voted two new committers on the project: Damien Gaillard and
Abdelkader Midani.
We expect traction around the coming release and new updated on the
website (factual use cases).
How has the project developed since the last report?
After the 1.1.0-incubating release, we are now preparing 1.2.0-incubating
release.
We improved the tests coverage, including performance benchmark (tests
have been performed with 5M of profiles, and 35M events for instance).
Date of last release:
2016-10-03
When were the last committers or PMC members elected?
2017-01-23
Signed-off-by:
[X](unomi) Jean-Baptiste Onofré
[ ](unomi) Bertrand Delacretaz
-----------------------------------------
Attachment AG: Report from the Apache jUDDI Project [Alex O'Ree]
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
- All mailing lists have had very Low traffic this quarter.
- 3.3.3 Released Sept 12, 2016, maintenance and bug fixes.
Scout
- No release this period, no development took place.
- No JAXR related questions on the mailing list.
Last PMC addition and new committer April 3, 2013 (Alex O'Ree)
Last Release jUDDI-3.3.3, Sept 12, 2016
Next Release jUDDI-3.3.4, Planned for Feb 2016
There are no issues that require the boards attention at this time.
Low development activity is a factor for low mailing list volume, but in all
likelihood, it's from a general lack of interest in the protocol.
There are enough active PMC members to approve releases and respond to potential
security issues. There was a bug was report 2 Feb 2017 and a fix is already in
the works. A release is planned shortly.
-----------------------------------------
Attachment AH: Report from the Apache Kafka Project [Jun Rao]
Apache Kafka is a distributed streaming platform for efficiently storing and
processing a large number of records in real time.
Development
===========
We released 0.10.1.1, which fixes 30 critical issues. We are in the process of
releasing 0.10.2.0, which includes new features such as session window and
global table in streams, client compatibilty, multiple listeners in the same
security protocol and SASL/SCRAM. This is our second time-based release and
we expect it to be released on time as well.
We are actively working on new features such as exactly-once semantic, admin
apis, and better JBOD support.
Community
===========
Lots of activities in the mailing list. We have 2324 subscribers in the user
mailing list, up 79 in the last 3 months. We have 1954 emails in the user
mailing list in the last 3 months, up from 1630 in the previous cycle. We have
912 subscribers in the dev mailing list, up 44 in the last 3 months. We have
6537 emails in the dev mailing list in the last 3 months, up from 5156 in the
previous cycle.
We elected one new committer, Grant Henke on Jan. 10, 2017. We last elected a
new PMC member Gwen Shapira on Aug. 17, 2016.
We had several Kafka meetups in various cities in this quarter.
One feedback from the community is that it's a bit hard to find an answer by
searching the Apache mailing list. We are wondering if Apache has considered
some sort of integration with things like Stack Overflow that does a better
job at Q/A.
Releases
===========
0.10.1.1 was released on Dec. 19, 2016.
-----------------------------------------
Attachment AI: Report from the Apache Knox Project [Larry McCay]
# Description
The Apache Knox Gateway is a REST API Gateway for interacting with Apache
Hadoop clusters. The Knox Gateway provides a single access point for all
REST/HTTP interactions with Apache Hadoop clusters.
# Issues
None
# Status
The Apache Knox team released 0.11.0 was release on Dec 28th with some great
enhancements and new features, some of the highlights are:
- Metrics collection capabilities for the gateway server
- Basic administrator UI
- New REST API support for Druid, SOLR, Avatica
- Hadoop group mapping support.
We have continued to use the KIP-# pages to drive the primary focus of each
release and feel it is working well. The 0.12.0 release is primarily focused
on the client library and programming model for consuming REST APIs through
Knox. There has been an increasing uptake of this library and it has become
clear that it needed to mature. We are discussing what really needs to land
in 0.12.0 as the number JIRAs has pushed the date out beyond our target and we
want to be able to maintain our release cadence but not at the expense of
addressing our goals. The current level of collaboration is healthy and
encouraging within the community on both mailing lists and JIRAs.
# Releases
* 0.11.0: 2016-12-28 Added Metric collection, Basic admin UI, new API support,
hadoop group lookup and fixed a number of bugs - through ~35 commits.
# Development Activity
* Community is discussing the 0.11.0 release scoping and what to move out to
0.13.0 which will continue to use the KIPs to drive the release themes
* Jira: 873 total, +29 -24 (last 30 days)
* Git (Source): 26 commits over last 30 days
* SVN (Site & Docs): 3 commits over last 30 days
# Community Activity
## Membership Changes
* Sandeep More was added as a committer and PMC member on 1/20/2017 [1].
* We continue to see a growth in contributions from the community and remain
on the lookout for new committer candidates to emerge.
## Mailing List Activity
* user@knox: ~17 messages over last 30 days
* dev@knox: ~400 messages over last 30 days (inflated due to jenkins emails)
1. http://mail-archives.apache.org/mod_mbox/knox-user/201701.mbox/%3CCACRbFyiELBS%2B9OPi4OHzqJ%3DapR%2BU9JHTj6CEFudfZexGP4xxig%40mail.gmail.com%3E
-----------------------------------------
Attachment AJ: Report from the Apache Kylin Project [Luke Han]
## Description:
===============
Apache Kylin is an open source Distributed Analytics Engine designed
to provide SQL interface and multi-dimensional analysis (OLAP) on
Hadoop supporting extremely large datasets.
## Issues:
==========
- there are no issues requiring board attention at this time
## Activity:
- Apache Kylin & Alluxio Meetup hosted on 2016-11-21 in Shanghai, China
engaged more than 200 participants, with 3 sessions from Bin Fan(Alluxio),
Mars Xie (VIP.com) and Yang Li (Kylin PMC),
- Mars Xie presented Apache Kylin Use Case in VIP.com at this meetup
- Luke Han presented Apache Kylin project at Wuzhen Summit on 2016-11-18 in
Wuzhen, Zhejiang
- Jia Lu presented Apache Kylin Use Case in Guomei Online at World Of Tech on
2016-11-25 in Beijing
- Yi Lv presented Apache Kylin Use Case at Lianjia at SDCC 2016 on 2016-11-18
in Beijing
- Luke Han presented Kylin and Azure/HDInsight topic at Microsoft Ignite China
2016 on 2016-12-02 in Beijing
- Luke Han presented Apache Kylin TLP topic at OSC Annual Event on 2016-12-04
in Beijing
- Yang Li presented Kylin Streaming topic at BDTC on 2016-12-10 in Beijing
- Yang Li presented Apache Kylin Use Cases at Top100 Summit on 2016-12-10 in
Beijing
- Luke Han presented Kylin Streaming topic at ECUG Con on 2017-01-14 in
Shenzhen
## PMC changes:
- Currently 18 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Dong Li on Tue Apr 12 2016
## Committer base changes:
- Currently 25 committers.
- New commmitters:
- Billy Liu was added as a committer on Thu Dec 01 2016
- Kaisen Kang was added as a committer on Sat Jan 07 2017
## Releases:
- 1.6.0 was released on Sat Nov 26 2016
## Mailing list activity:
- dev@kylin.apache.org:
- 310 subscribers (up 37 in the last 3 months):
- 953 emails sent to list (643 in previous quarter)
- issues@kylin.apache.org:
- 53 subscribers (up 12 in the last 3 months):
- 1581 emails sent to list (1295 in previous quarter)
- user@kylin.apache.org:
- 216 subscribers (up 41 in the last 3 months):
- 333 emails sent to list (385 in previous quarter)
## JIRA activity:
- 270 JIRA tickets created in the last 3 months
- 217 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AK: Report from the Apache Lens Project [Amareshwari Sriramadasu]
## Description:
Lens provides an Unified Analytics interface. Lens aims to cut the Data
Analytics silos by providing a single view of data across multiple tiered
data stores and optimal execution environment for the analytical query. It
seamlessly integrates Hadoop with traditional data warehouses to appear
like one.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
Community has done the following improvements in the project:
- Druid SQL rewriter has been stabilised
- Work on Fact to Fact union is happening in a feature branch
- Ability to do data completeness checks during query time has been added
- Issues wrt session expiration are fixed
- Few OLAP cube rewrite bugs have been fixed.
## Health report:
This quarter had the least engagement in jira activity and mailing list,
mostly due to temporary unavailability of many developers. And majority
of the developers are working on a feature branch.
## PMC changes:
- Currently 18 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Puneet Gupta on Tue Sep 20 2016
## Committer base changes:
- Currently 22 committers.
- No new committers added in the last 3 months
- Last committer addition was Archana H at Sat May 21 2016
## Releases:
- Last release was 2.6 on Tue Oct 25 2016
-----------------------------------------
Attachment AL: Report from the Apache Libcloud Project [Tomaž Muraus]
## Description:
Libcloud is a Python library that abstracts away the differences among
multiple cloud provider APIs.
## Issues:
There are no issues which require board attention at this time.
## Activity:
We have continued to receive a good amount of various contributions
on Jira and our Github repository.
## PMC changes:
- Currently 13 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Jeff Dunham on Sat May 21 2016
## Committer base changes:
There is an open voting thread for a new committer and a PMC member.
- Currently 19 committers.
- No new committers added in the last 3 months
- Last committer addition was Jeff Dunham at Sat May 21 2016
## Releases:
In addition to the releases mentioned below, we have a big new
release which rewrites the underlying HTTP layer (it replaces custom
built code from many years ago with popular requests Python library
which reduces some of the complexity and amount of code we need to
maintain) coming in the near future.
- 1.4.0 was released on Sun Nov 27 2016
- 1.5.0 was released on Thu Dec 29 2016
## JIRA activity:
- 22 JIRA tickets created in the last 3 months
- 9 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AM: Report from the Apache Logging Services Project [Ralph Goers]
The Apache Logging Services Project creates and maintains open-
source software related to application logging.
Currently there are no issues which require the board's attention.
- Community
Log4j 2 remains an active project. The overall community is healthy
and friendly.
Log4cxx is still active in the Incubator. They have been sporadic
discussions regarding performing a release but little real progress
has been made.
In general, all subprojects are still healthy although none has grown
since the last report.
- Project Branding Requirements
All components except Chainsaw meet the branding requirements.
We will fix the Chainsaw branding with the next release.
- Last three community changes
* Jonathon Davies has accepted an invite to be a committer on Jan 8, 2017
* Mikael Ståldal joined as a PMC Member on June 20 2016
* Ralph Goers was voted to be the next Chair on Nov 01 2015
- Releases
* Log4j 2.8 (Jan 24, 2017)
* Logging Parent 1.0 (Jan 25, 2017)
* Log4net 2.0.7 (Jan 4, 2017)
* Log4net 2.0.6 (Dec 24, 2016)
- Subproject summaries
Log4j 2: Active. Several new git repos have been created for additional
components related to Log4j.
The number of emails on the developer mailing list has increased by about
30% in the last 3 months although the number of subscribers has decreased
slightly. The increase may be due to github now sending emails to the dev
list.
Log4net: Active with 2 releases within the last quarter and a significant
uptick in activity on the dev and user lists.
Log4cxx: Prgoress seems to have stalled in the incubator. They have made
no progress towards a release. Only minor mailing list activity.
Log4php: No activity this quarter.
Chainsaw: No activity this quarter.
-----------------------------------------
Attachment AN: 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 numerous major releases, including a 2.6 release on
December 30, 2016. The next major release is scheduled for April 30, 2017.
Committers and PMC membership
=============================
The last committer we signed up was Markus Schuch on December 2, 2016.
The last PMC member was Rafa Haro, voted in on August 31, 2015.
Mailing list activity
=====================
Mailing list activity has been moderate this quarter. Issues reported have been
mainly garden-variety bugs. We've had several feature requests but few
contributions. Dev list comments for this period have also been light, with
occasional user questions. I am unaware of any mailing list question that
has gone unanswered.
Outstanding issues
==================
No outstanding infrastructure issues are known at this time.
Branding
========
We continue to believe we are now compliant with Apache branding guidelines,
with the possible exception of (TM) signs in logos from other Apache products
that don't have any such marks. We received word that the ManifoldCF
trademark application (US TM App No. 86583085 for "MANIFOLDCF" in Cl. 9 | DLA
Ref: 393457-900118) has been accepted.
-----------------------------------------
Attachment AO: 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.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
A very quiet quarter in the project, both in terms of development and mailing
lists activity.
The project struggles to find new challenges and people to activelly work on
the project. This issue has been discussed several times, still looking for a
sustainable solution.
A release is long overdue (now more than two years since the last!). After the
last report in November there was some small and short-lived development
activity to resolve the remaining issues, but without much progress.
## Health report:
The project was considered feature-complete in 3.3.0. The current release
cicle (3.4.0) focused on refining and fixing bug, plus incorporation some
non-core new features. The development (issues, commits, emails) has
significantly come down in the last year.
## PMC changes:
- Currently 11 PMC members.
- Mark A. Matienzo was added as a PMC member on Wed Aug 03 2016.
## Committer base changes:
- Currently 13 committers.
- Mark A. Matienzo was added as a committer on Wed Aug 03 2016.
## Releases:
- Last release was 3.3.0 on Fri Dec 05 2014
## Mailing list activity:
- users@marmotta.apache.org:
- 115 subscribers (up 1 in the last 3 months)
- 5 emails sent to list (44 in previous quarter)
- dev@marmotta.apache.org:
- 95 subscribers (up 0 in the last 3 months)
- 19 emails sent to list (64 in previous quarter)
## JIRA activity:
- 1 JIRA tickets created in the last 3 months
- 1 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AP: Report from the Apache Mesos Project [Benjamin Hindman]
Description:
Apache Mesos abstracts CPU, memory, storage, and other compute resources away
from machines (physical or virtual), enabling fault-tolerant and elastic
distributed systems to easily be built and run effectively.
Issues:
There are no Board-level issues at this time.
Activity:
The project continues to see new bug reports, bug fixes, features, reviews
and releases. The mailing lists, slack and IRC channels are also very much
active with healthy discussions.
Current plans:
Mesos 1.3 is being released this month.
New committers:
Haosdent Huang and Neil Conway were voted in as committers and PMCs.
Another contributor is close to becoming a committer and we are actively
working to nominate them.
Committer diversity:
We are excited about our newest committer Haosdent because he adds diversity
in terms of organization (independent) and geography (China).
We need to identify more diverse potential committers from our contributor
pool.
Releases: (since last board report)
1.1.0 Nov 10th
1.0.2 Nov 15th
1.2.0 In progress
1.0.3 In progress
JIRA Activity:
523 - Issues created
279 - Issues resolved
-----------------------------------------
Attachment AQ: Report from the Apache MetaModel Project [Kasper Sørensen]
## Description:
Providing a common interface for discovery, exploration of metadata and
querying of different types of data sources.
## Issues:
- There are no issues requiring board attention at this time
## Activity:
- Apache MetaModel 4.6.0 released.
- Activity on the main @dev mailing list is down from 148 emails sent to just 78.
- A new @users mailing list has emerged, but not with a lot of activity in it.
## Health report:
- The slowdown in activity is a bit worrying. It would seem that we are not
attracting a lot of new community members and/or not doing a great job of
promoting Apache MetaModel.
## PMC changes:
- Currently 11 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Dennis Du Krøger on Mon Sep 05 2016
## Committer base changes:
- Currently 11 committers.
- No new committers added in the last 3 months
- Last committer addition was Dennis Du Krøger at Thu Oct 15 2015
## Releases:
- 4.5.5 was released on Wed Nov 16 2016
- 4.6.0 was released on Fri Feb 03 2017
## JIRA activity:
- 8 JIRA tickets created in the last 3 months
- 6 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AR: Report from the Apache Oltu Project [Antonio Sanso]
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 2014.
Apache Oltu Oauth2 module version 1.0.2 was released June 20th 2016.
Apache Oltu Parent v4 was released June 20th 2016.
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 2014 and some minor
releases are going out regularly for bug fixing. Updated modules contained bug
fixing were released June 20th 2016 . Vote for releasing JWT 1.0.3 is in
progress.
At the moment we are working on JSON Web Encryption support ( OLTU-80 -
Implement JWE support for JWT IN PROGRESS ).
In a recent mail thread in private@ some important things have been pointed
out:
The last few months it has been awfully quiet (this might also be due the fact
the OAuth spec is stable). But not only, since we have some patches laying
around for a while
The release has not been finished. It seems some of the artifacts are not
synched correctly in https://www.apache.org/dist/oltu
The builds keep failing
One of the outcome was that embracing the Apache way of having new blood from
time to time we are going to rotate the VP for the project. Hence I proposed
to step down from my role of chair. Unluckily at the moment nobody seems to be
keen to take this responsibility. For this reason I will keep my role of
chair for now.
COMMUNITY
We have voted two new PMC members: Stein Welberg and Jasha Joachimsthal in
June 2016 (13/06/2016)
ISSUES
There are no issues requiring board attention at this time.
-----------------------------------------
Attachment AS: Report from the Apache Oozie Project [Robert Kanter]
## Description:
- Oozie is a workflow scheduler system to manage Apache Hadoop jobs.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- Oozie 4.3.0 was released!
- The OOZIE-1770 Oozie on Yarn project continues to make good progress in a
feature branch. We're currently reviewing the bulk of the work for
merging back to trunk given the current state of development and the
release of 4.3.0.
## PMC changes:
- Currently 16 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Ryota Egashira on Mon Aug 10 2015
## Committer base changes:
- Currently 23 committers.
- New commmitters:
- Abhishek Bafna was added as a committer on Wed Dec 21 2016
- Satish Saley was added as a committer on Mon Jan 02 2017
## Releases:
- 4.3.0 was released on Thu Dec 01 2016
## Mailing list activity:
- dev@oozie.apache.org:
- 152 subscribers (up 1 in the last 3 months):
- 2024 emails sent to list (2468 in previous quarter)
- user@oozie.apache.org:
- 505 subscribers (up 1 in the last 3 months):
- 77 emails sent to list (71 in previous quarter)
## JIRA activity:
- 64 JIRA tickets created in the last 3 months
- 53 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AT: Report from the Apache Open Climate Workbench Project [Michael James Joyce]
Apache Open Climate Workbench is a tool for scalable comparisons of remote
sensing observations to climate model outputs.
Activities on the task have slowed down in December and January due to the
holidays and a large number of science conferences that many of the project's
committers attend. This is expected and we look forward to an uptick soon.
The project released v 1.1.0 late in July which provides a number of key
features required of the tool in addition to many quality-of-life
improvements. The team is working towards 1.2 and a number of new features.
Issues for the Board:
None
When was the last committer or PMC member elected:
- Omkar Reddy - 20 January 2016
- Ibrahim Jarif - 26 April 2016
When was the last release:
- 1.0.0 - 22 September 2015
- 1.1.0 - 27 July 2016
-----------------------------------------
Attachment AU: Report from the Apache Perl Project [Philippe M. Chiasson]
--- mod_perl --
No new mod_perl 2.x releases since 2016-10.
-- Activity --
mod_perl continues to be a healthy development community, though
as a mature and stable product development moves at a naturally
slower pace than in years past. Bugs are found and discussed and
fixes are applied with due consideration for our production userbase.
The genral activity is low, but the recent release of mod_perl 2.0.10 has
caused some renewed movement on the development side, even if somwaht minor.
-- Users --
The mod_perl users list is seeing little activity, with a bump in activity
following the 2.0.10 RCs and the final release.
Patches and bug reports are few, but keep on coming.
-- Commiters --
Currently 22 committers.
No new changes to the committer base since last report.
-- PMC --
Currently 11 PMC members.
No new PMC members added in the last 3 months
Last PMC addition was Steve Hay on Wed Feb 29 2012
-----------------------------------------
Attachment AV: Report from the Apache Phoenix Project [James R. Taylor]
## Description:
- Apache Phoenix enables SQL-based OLTP and operational analytics
for Apache Hadoop using Apache HBase as its backing store.
## Issues:
- There are no issues requiring board attention at this time
## Activity:
- Plan to release 4.10.0 in Feb with some substantial performance
improvements.
- Work progressing on a 5.0 release leveraging Apache Calcite.
## Health report:
- The project is healthy and continues to grow as users look for easy
ways to gain insight over and manage their ever-increasing Hadoop
data through standard SQL and JDBC APIs.
## PMC changes:
- Currently 24 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Josh Elser on Tue Aug 09 2016
## Committer base changes:
- Currently 29 committers.
- Kevin Liew was added as a committer on Thu Nov 10 2016
## Releases:
- 4.9.0 was released on Tue Nov 22 2016
## Mailing list activity:
- Both dev and user lists continue to gain subscribers
- dev@phoenix.apache.org:
- 223 subscribers (up 4 in the last 3 months):
- 2328 emails sent to list (3652 in previous quarter)
- user@phoenix.apache.org:
- 550 subscribers (up 29 in the last 3 months):
- 270 emails sent to list (622 in previous quarter)
## JIRA activity:
- 215 JIRA tickets created in the last 3 months
- 121 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AW: Report from the Apache POI Project [Dominik Stadler]
## Description:
- Apache POI is a Java library for reading and writing Microsoft Office file
formats
## Issues:
- there are no issues requiring board attention at this time
## Activity:
- There was work in some areas, notably parsing/reading of WMF/EMF files which
can be used for pictures in Office documents. Also initial support for
extracting text from embedded files was added and some improvements to
handling of Unicode characters have landed. Additionally a number of
Findbugs/SonarQube reports were fixed.
On the build-automation-side the Gradle build was enhanced some more and the
Jenkins builds are now fully version-controlled as part of the core source via
the Jenkins DSL plugin.
We release 3.16-beta1 in November and just released 3.16-beta2.
Additionally a number of users posted questions on the user-list which were
discussed.
## Health report:
- the last few months we saw a bit less bugfix-activity, the number of open
bug-reports is unfortunately increasing. However this is partly due to the
nature of Apache POI and the inherent complexity of the Office formats, which
means there is a constant influx of bug-reports, some with fairly high
complexity and needed amount of work to resolve.
On new committers/PMC: there are currently only a few users active enough to
discuss committership to bring on new talent.
## PMC changes:
- Currently 28 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Greg Woolsey on Wed Oct 05 2016
## Committer base changes:
- Currently 35 committers.
- No new committers added in the last 3 months
- Last committer addition was Greg Woolsey at Tue Oct 04 2016
## Releases:
- 3.16-beta1 was released on Sun Nov 20 2016
- 3.16-beta2 was released on Thu Feb 02 2017
## Mailing list activity:
- Mainly constant membership numbers. POI is a mature project with a stable
user/developer-base.
- dev@poi.apache.org:
- 238 subscribers (down -4 in the last 3 months):
- 773 emails sent to list (1018 in previous quarter)
- general@poi.apache.org:
- 131 subscribers (up 1 in the last 3 months):
- 3 emails sent to list (4 in previous quarter)
- user@poi.apache.org:
- 636 subscribers (down -20 in the last 3 months):
- 206 emails sent to list (150 in previous quarter)
## Bugzilla Statistics:
- 76 Bugzilla tickets created in the last 3 months
- 52 Bugzilla tickets resolved in the last 3 months
- 458 bugs are open overall (plus 26)
- Having 111 enhancements, thus having 347 actual bugs (plus 8 and 18)
- 101 of these are waiting for feedback (plus/minus 0)
- thus having 246 actual workable bugs (plus 16)
- 4 of the workable bugs have patches available (minus 1)
- Distribution of workable bugs across components: HSSF=76, XSSF=70, HWPF=36,
SS Common=17, XWPF=14, XSLF=10, SXSSF=6, HPSF=4, POI Overall=4, POIFS=4,
HSLF=3, HSMF=1, OPC=1
-----------------------------------------
Attachment AX: Report from the Apache Qpid Project [Robbie Gemmell]
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, a
message router, and client libraries for C++, Java / JMS, .Net,
Python, Perl and Ruby.
# Releases:
- Qpid for Java 6.1.0 was released on 15th Nov 2016.
- Qpid Dispatch 0.7.0 was released on 18th Nov 2016.
- Qpid Proton 0.16.0 was released on 12th Dec 2016.
- Qpid CPP 1.36.0 was released on 13th Dec 2016.
- Qpid for Java 6.0.6 was released on 23rd Dec 2016.
- Qpid for Java 6.1.1 was released on 23rd Dec 2016.
- Qpid JMS 0.20.0 was released on 19th Jan 2017.
- Qpid Proton 0.17.0 was released on 7th Feb 2017.
- Qpid Proton-J 0.17.0 was released on 7th Feb 2017.
# Community:
- The main user and developer mailing lists continue to be active and JIRAs
are being raised and addressed, in line with prior activity levels.
- Ganesh Murthy was voted in for the PMC, added on 30th Jan 2017.
- There were no new committer additions in this quarter.
The most recent new committer is Ganesh Murthy, added on 29th Feb 2016.
# Development:
- The AMQP 1.0 JMS client had its 0.20.0 release adding support for JMS 2.0,
and moving to requiring Java 8. Various bug fixes and improvements have
been made since, and a followup release is planned in the coming weeks.
- Following previous discussion around future direction for Proton, its
C (+language binding) and Java components have been made independently
releasable, and each has since undergone a new 0.17.0 release. Work now
continues toward their respective 0.18.0 releases.
- Development on the Java broker and AMQP 0-x JMS client continues, with
discussions undertaken around moving the broker to require Java 8 and
separating the AMQP 0-x JMS client out as an independently releasable
component going forward as more emphasis is placed on AMQP 1.0 support,
with work on these changes now under way.
- Work is ongoing towards a 0.8.0 release of the Qpid Dispatch router
incorporating numerous improvements and bug fixes.
# Issues:
There are no Board-level issues at this time.
-----------------------------------------
Attachment AY: Report from the Apache Ranger Project [Selvamohan Neethiraj]
# Description
The Ranger project is a framework to enable, monitor and manage comprehensive
data security across the Hadoop platform.
# Issues
* Running into some JIRA permission issues for the past few days. Working
with INFRA team (INFRA-13423)
# Status
* Graduation approved by board on Jan 18, 2017
* Working through tasks required of graduating projects
* Release Plan for Ranger 0.7.0 will be started soon.
# Releases
* ranger-0.6.3 released on 2017-01-30 (Fixed some of the key security issues)
# Development Activity
* Community is discussing the scope of next release
* Jira: 55(added), 66(resolved) (in the last 31 days)
* Git(Source): 75 commits over last 31 days
* SVN(Site & Docs): 5 commits over last 31 days
# Community Activity
## Membership Changes
* Added all committers to PMC list as part of the graduation (01-18-2017);
Added (Alok Lal, Colm O hEigeartaigh, Gautam Borad)
* Gautam Borad was added as a committer on 06-29-2015
## Mailing List Activity
* user@ranger: 48 messages over last 31 days
* dev@ranger: 587 messages over last 31 days
* commits@ranger: 96 messages over last 31 days
-----------------------------------------
Attachment AZ: Report from the Apache REEF Project [Byung-Gon Chun]
## Description:
Apache REEF (Retainable Evaluator Execution Framework) is a library for
developing portable applications for cluster resource managers such as
Apache Hadoop YARN or Apache Mesos.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
- Lots of work towards making REEF components start from another
Java or C# application in the same VM
- Continuous enhancements to the Iterative Map Reduce layer
- Preparation for REEF 0.16.0 release
## Health report:
Overall, the community is healthy: there is a constant flow of bug reports,
fixes and discussions.
## PMC changes:
- Currently 21 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Andrew Chung on Wed Nov 18 2015
## Committer base changes:
- Currently 33 committers.
- No new committers added in the last 3 months
- Last committer addition was Carlo Curino at Wed Jun 08 2016
## Releases:
- Last release was 0.15 on Mon May 23 2016
## Mailing list activity:
Mailing list and JIRA activities are down partly due to vacation season.
There is also active discussion on Github PRs.
- dev@reef.apache.org:
- 75 subscribers (up 7 in the last 3 months):
- 411 emails sent to list (919 in previous quarter)
- user@reef.apache.org:
- 9 subscribers (up 2 in the last 3 months)
## JIRA activity:
- 73 JIRA tickets created in the last 3 months
- 88 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment BA: Report from the Apache River Project [Patricia Shanahan]
## Description:
- Apache River software provides a standards-compliant JINI service.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- Continued discussion of River's future direction, this quarter mainly on
OSGi and serialization.
- Zsolt Kúti reworked the River web site.
## Health report:
- The future directions discussion continues.
- Attracting new developers will remain difficult until the future direction
is firmed up and made visible. We did add one committer this quarter.
## PMC changes:
- Currently 11 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Bryan Thompson on Sun Aug 30 2015
## Committer base changes:
- Currently 14 committers.
- Zsolt Kúti was added as a committer on Wed Dec 07 2016
## Releases:
- River-3.0.0 was released on Wed Oct 05 2016
## Mailing list activity:
- There has been a recent increase in dev@ activity due to a lively technical
discussion of OSGi and serialization in the context of River. That
discussion is on-going.
- dev@river.apache.org:
- 95 subscribers (up 0 in the last 3 months):
- 201 emails sent to list (114 in previous quarter)
- user@river.apache.org:
- 96 subscribers (up 0 in the last 3 months):
- 2 emails sent to list (3 in previous quarter)
## JIRA activity:
- 2 JIRA tickets created in the last 3 months
- 1 JIRA tickets closed/resolved in the last 3 months
=======================================
The above report received +1 votes from PMC members Peter Firmstone, Patricia
Shanahan, and Bryan Thompson.
-----------------------------------------
Attachment BB: Report from the Apache Roller Project [Dave Johnson]
## Description:
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.3 Tomcat and MySQL.
## Issues:
- There are no issues requiring board attention at this time
## Activity:
- The core Roller community is small and with low activity levels.
- Roller website was switched over from Apache CMS to Git PubSub with JBake
- There is ongoing work to create a modernized UI using Bootstrap with Struts,
but it has slowed a bit since our last report.
## Health report:
- Community is made-up of part-time volunteers with limited time to devote to Roller.
## PMC changes:
- Currently 5 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Kohei Nozaki on Sun Dec 06 2015
## Committer base changes:
- Currently 10 committers.
- No new committers added in the last 3 months
- Last committer addition was Kohei Nozaki at Mon Mar 09 2015
## Releases:
- Last release was 5.1.2 on Tue Mar 24 2015
## Mailing list activity:
Subscriber counts could be taken to mean there is still some interest in
Apache Roller. The low email counts reflec the low level of development
and user-support activity.
- dev@roller.apache.org:
- 157 subscribers (down -1 in the last 3 months):
- 5 emails sent to list (5 in previous quarter)
- user@roller.apache.org:
- 287 subscribers (up 0 in the last 3 months):
- 3 emails sent to list (5 in previous quarter)
## JIRA activity:
- 2 JIRA tickets created in the last 3 months
- 1 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment BC: Report from the Apache Santuario Project [Colm O hEigeartaigh]
## Description:
- Library implementing XML Digital Signature Specification & XML Encryption
Specification
## Issues:
- There are no issues requiring board attention at this time
## Activity:
- There was one release over the last quarter - Apache Santuario XML Security
for Java 2.0.8. This was a minor bug fix release. We have only had one
issue fixed since the last release, so at this point we don't anticipate
another release in the next quarter.
An image was added to the Santuario web page pointing to the Apache
"current event" to help promote ApacheCon.
## Health report:
- Apache Santuario is a mature and stable project that has reached a point
where not too many fixes are required, as it is a set of implementations
of some specifications that are quite old now. It is actively managed by
the PMC. Right now there are no obvious potential new committers for the
project.
## PMC changes:
- Currently 6 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Marc Giger on Wed Apr 03 2013
## Committer base changes:
- Currently 16 committers.
- No new changes to the committer base since last report.
- Last committer addition was Marc Giger in July 2012
## Releases:
- Apache Santuario XML Security for Java 2.0.8 was released on Mon Dec 05
2016
-----------------------------------------
Attachment BD: Report from the Apache Serf Project [Bert Huijben]
## Description:
The serf library is a high performance C-based HTTP client library
built upon the Apache Portable Runtime (APR) library. Serf is the
default client library of Apache Subversion, Apache OpenOffice and
mod_pagespeed.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
Some feature development happened over the last quarter, and there
was some work going on around improving support for the different
SSL libraries forked from OpenSSL that differ in how they announce
new features.
## Health report:
Activity is at a normal, fairly quiet level.
The serf project's activity is quite related to that of Subversion
and with that projects recent affairs we slowed more than expected.
## PMC & Committer changes:
Currently 11 PMC members and 12 committers. Our last new committer was
added on Wed Sep 02 2015.
## Releases:
Apache Serf 1.3.9 was released on Thu Sep 01 2016
## Mailing list and Jira activity:
Normal slow activity.
-----------------------------------------
Attachment BE: Report from the Apache SIS Project [Martin Desruisseaux]
## Description:
Apache Spatial Information System (SIS) is a Java library for developing
geospatial applications. SIS enables better representation of spatial
objects for searching, archiving, or other relevant spatial needs. The
SIS metadata module forms the base of the library and enables the
creation of metadata objects which comply with the model of
international standards. The SIS referencing module enable the
construction of geodetic data structures for geospatial referencing such
as axis, projection and coordinate reference system definitions, along
with the associated operations which enable the mathematical conversion
of coordinates between different systems of reference.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
### On items cited in previous SIS report:
The previous report (November 2016) listed Google Summer of Code (GSoC)
work that we were integrating into trunk. Since that report, integration
has been completed for the metadata part of LANDSAT and GeoTIFF formats.
Work has not yet started for integration of MODIS and Catalog Web
Services (WCS) parts. In relation with this work, the board provided the
following feedback:
rb: "Remi Marechal is continuing Hao's work on GeoTIFF" ... does
that mean that Hao went away at the end of the GSoC effort? (I'm
curious about the long-term benefits of GSoC in growing communities.)
Hao went back to the university after GSoC and did not have much time
for SIS anymore. She is still in touch with the Vietnamese Space Agency
(VNSC) which provided GSoC data, and contacted us in October about the
HDF format. We presume that her contribution will depend on Apache SIS
relevance for VSNC, but do not know if they are still using it.
The previous report cited the recent JSR-363 final approval and its
implementation in Apache SIS. We need the Open Geospatial Consortium
(OGC) to release GeoAPI 3.0.1 before we can release Apache SIS 0.8
(unless we rollback our JSR-363 support). This release has been approved
in OGC meeting in Taiwan in December and is now in the hands of OGC staff.
### Integration of new work:
A work has been submitted for the GPS Exchange (GPX) format. This
integration has been completed, but raise questions about its API that
have been submitted on the mailing list [1].
Recently, a new possible contributor upgraded the XML metadata file
format supported by Apache SIS to the latest revision of the
international standard [2]. His company seems willing to share their
work, but we are still checking if they agree to sign ICLA.
### Meetings
Presented Apache SIS to some Hitachi and AIST peoples in Tokyo. The
presentation was similar to the "Apache SIS for Earth Observation" talk
done at ApacheCon in Seville [3]. We discussed about conceptual issues
encounter while implementing the Moving Feature standard in Apache SIS
(some authors of that standard were in the room), and the next steps for
collaboration.
## Health report
Commits continue at the usual pace, but are still mostly from the same
committer. Project is reported as healthy by the Apache Committe Report
Helper. Issues requiring a decision that could have a wide impact are
posted on the mailing list [1], but trig few discussion at this time. I
would like to post an email about the above-cited issue with the "Moving
Features" implementation, but I'm not sure what would be the most
appropriate list (dev@sis...? geospatial@...?, OGC mailing list?) since
the issue is quite abstract and require familiarity with some ISO standards.
## PMC changes:
* Currently 19 PMC members.
* No new PMC members added in the last 3 months.
* Last PMC addition was Marc Le Bihan on Wed Dec 10 2014.
## Committer base changes:
* Currently 21 committers.
* No new committers added in the last 3 months.
* Last committer addition was Johann Sorel at Thu Mar 31 2016.
## Releases:
* Last release was 0.7 on Fri May 27 2016
## JIRA activity:
* 13 JIRA tickets created in the last 3 months
* 2 JIRA tickets closed/resolved in the last 3 month
[1] https://lists.apache.org/thread.html/5e052209b5d2023a4e05b5f08dc9b755501c6798ba7b4de38a82614b@%3Cdev.sis.apache.org%3E
[2] https://lists.apache.org/thread.html/f669f4996d11b4019cdf9321a8c5bcf8a95e94d135e87b68a4a3e050@%3Cdev.sis.apache.org%3E
[3] http://events.linuxfoundation.org/sites/events/files/slides/SIS%20for%20earth%20observation.pdf
-----------------------------------------
Attachment BF: 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, Python and R as well as a rich set of
libraries including stream processing, machine learning, and graph analytics.
Project status:
- The community released Apache Spark 2.1.0 on Dec 28 with a variety of
new features for the 2.x branch, most notably improvements to streaming
(http://spark.apache.org/releases/spark-release-2-1-0.html). We also
released Spark 2.0.2 on Nov 14 with bug fixes for the 2.0.x branch.
- The Spark Summit East conference is running Feb 7th to 9th in Boston.
- We've continued discussions on a "Spark Improvement Proposal" format
for documenting large proposed additions over the dev list and are
converging towards a final version that we want to post on our website.
Trademarks:
- We are continuing engagement with various organizations.
Latest releases:
- Dec 28, 2016: Spark 2.1.0
- Nov 14, 2016: Spark 2.0.2
- Nov 07, 2016: Spark 1.6.3
- Oct 03, 2016: Spark 2.0.1
- July 26, 2016: Spark 2.0.0
Committers and PMC:
- The last committers were added on Jan 24th, 2017
(Holden Karau and Burak Yavuz).
- The last PMC members were added on Feb 15th, 2016
(Joseph Bradley, Sean Owen and Yin Huai).
-----------------------------------------
Attachment BG: Report from the Apache Sqoop Project [Jarek Jarcec Cecho]
## Description:
Apache Sqoop is a tool designed for efficiently transferring bulk data
between Apache Hadoop and structured datastores such as relational
databases. It can be used to import data from external structured
datastores into Hadoop Distributed File System or related systems like
Hive and HBase. Conversely, Sqoop can be used to extract data from
Hadoop and export it to external structured datastores such as relational
databases and enterprise data warehouses.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
Development activity continues to be primarily on sqoop2 branch, but there are
still bugfixes on trunk branch as well.
## Health report:
Community is healthy, we see a new contributors showing up and contributing to
the project.
## PMC changes:
- Currently 16 PMC members.
- We’ve added new PMC member (Abraham Fine) in November 2016
## Committer base changes:
- Currently 28 committers.
- Attila Szabo was added as a committer on Sun Aug 14 2016
## Releases:
- 1.99.7 was released on Sun Aug 07 2016
## JIRA activity:
- 88 JIRA tickets created in the last 3 months
- 32 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment BH: Report from the Apache Subversion Project [Evgeny Kotkov]
Apache Subversion exists to be universally recognized and adopted as
an open-source, centralized version control system characterized by
its reliability as a safe haven for valuable data; the simplicity of
its model and usage; and its ability to support the needs of a wide
variety of users and projects, from individuals to large-scale
enterprise operations.
* Board Issues
There are no Board-level issues of concern.
* Community
During this quarter, the community has finished the work on two
bugfix/security releases addressing the CVE-2016-8734 vulnerability.
Apart from this, we have been working on changes planned for Subversion
1.10.x. Overall, these changes include different minor improvements,
and two new features: the interactive tree conflict resolver, and
the reimplemented authorization mechanism with a support for wildcard
rules. There are plans to release an alpha version with these features
in the nearby time.
Our dev@ and users@ mailing lists are active and have received 292 and
336 messages during the past three months. (This is roughly the same
amount as in the previous quarter.) The commit rate remains on the same
level as well.
Stefan Hett was added to the Subversion PMC in February 2017.
Last committer addition was November 2015 (James McCoy).
* SHA1 Collisions and Subversion
With the recent publication of the first known SHA1 collision by Google
and CWI, we have identified a couple of related issues.
While Subversion is designed to not rely on SHA1 for content indexing, we
found a few bugs in the implementations of particular features. The most
severe issue is caused by an oversight in the data deduplication feature.
It can result in inability to access files with colliding SHA1 values or
result in data loss for such files.
We are now working on resolving these issues. It is likely that we
will need to prepare new 1.8.x and 1.9.x patch releases, and schedule
additional changes for Subversion 1.10.x.
* Releases
Since the last report, Subversion 1.8.17 and 1.9.5 were released on
November 29th.
The work toward Subversion 1.10.x continues, and we hope to prepare a
1.10.0-alpha1 release soon.
-----------------------------------------
Attachment BI: Report from the Apache Syncope Project [Francesco Chicchiriccò]
## Description:
Apache Syncope is an Open Source system for managing digital identities in
enterprise environments.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
Overall, the period was busy with bugfixing and enhancements to the stable
(2.0) and old stable (1.2) series. New users are approaching via IRC and the
user mailing list.
About the Syncope PoC with Infra, we have started some
activity on the provided VM and got some initial support from Infra.
## Health report:
Discussions about new features and improvements arose in the dev mailing list
and still progressing.
At the moment we have not yet identified any potential
new committer, though some contribution via GitHub PR is in progress.
## PMC changes:
- Currently 11 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Andrea Patricelli on Thu Oct 13 2016
## Committer base changes:
- Currently 20 committers.
- No new committers added in the last 3 months
- Last committer addition was Matteo Di Carlo at Sat Jul 09 2016
## Releases:
- 1.2.10 was released on Tue Jan 24 2017
- 2.0.2 was released on Fri Jan 27 2017
-----------------------------------------
Attachment BJ: Report from the Apache Turbine Project [Thomas Vandahl]
Apache Turbine Project Board Report, February 2017
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 had a busy quarter by our measures.
The Turbine project has no board-level issues at this time.
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 Maven Archetype for a Hello-World-application has been released. The
following components have been released this quarter
- Turbine Parent POM, Version 4 (2016/12/18)
- Turbine Parent Assembly, Version 1.0.0 (2016/12/12)
- Turbine4 Webapp Archetype, version 1.0.1 (2017/01/25)
Fulcrum component project
The following components have been released this quarter
- Fulcrum Factory, Version 1.1.0 (2016/12/12)
- Fulcrum Intake, Version 1.2.2 (2016/12/18)
-----------------------------------------
Attachment BK: Report from the Apache Usergrid Project [Todd Nine]
## Description:
- Usergrid is Backend-as-a-Service (BaaS) composed of an integrated
database (Cassandra), a query engine (Elastic Search), and
application layer and client tier with SDKs for developers.
## Issues:
- There are no issues requiring board attention at this time
## Activity:
- Unique value implementation has been moved to Akka. This has increased
data stability significantly for unique name values.
- Multi-region queueing via Akka (Qakka) is available in master for beta use.
(Thanks Dave for this).
## Health report:
- Usergrid is healthy and the community is growing at a moderate pace.
## PMC changes:
- Currently 25 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Mike Dunker on Mon Jan 18 2016
## Committer base changes:
- Currently 14 committers.
- No new committers added in the last 3 months
- Last committer addition was George Reyes at Tue Sep 29 2015
## Releases:
- Last release was 2.1.0 on Wed Feb 17 2016.
Available via website https://usergrid.apache.org/releases/
## Mailing list activity:
- dev@usergrid.apache.org:
- 105 subscribers (up 6 in the last 3 months):
- 83 emails sent to list (98 in previous quarter)
- user@usergrid.apache.org:
- 135 subscribers (up 7 in the last 3 months):
- 12 emails sent to list (25 in previous quarter)
## JIRA activity:
- 14 JIRA tickets created in the last 3 months
- 2 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment BL: Report from the Apache Velocity Project [Nathan Bubna]
## Description:
- Java-based template engine
## Issues:
- No issues requiring board attention at this time.
## Activity:
- Very busy, mostly one developer, with others testing and discussing changes.
Still aiming at Engine 2.0 release soon; there have been many release
candidates already.
## Health report:
- Engine 2.0 release candidates are coming steadily, release should be soon.
- A Tools 3.0 release is still planned, but Engine 2.0 has priority currently.
## PMC changes:
- Currently 9 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Sergiu Dumitriu on Wed Jun 10 2015
## Committer base changes:
- Currently 14 committers.
- Michael Osipov was added as a committer on Mon Jan 30 2017
## Releases:
- none in this quarter
## JIRA activity:
- 1 JIRA tickets created in the last 3 months
- 1 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment BM: Report from the Apache Whimsy Project [Sam Ruby]
## Description:
Tools that help automate various administrative tasks or information lookup
activities
## Issues:
There are no issues requiring board attention at this time
## GitHub experiment:
- No issues to report. The Whimsy project continues to operate with GitHub
defacto acting as master.
## Health report:
- While there remains sufficient oversight, there has been no progress this
quarter in growing a development community.
## Development:
- Function was added to the roster tool to enable members of a podling to
maintain their own roster. Future plans include extending this to all
PMCs. Code was also added to extract this data for use by the phone book
and other applications.
- Improved checks were made to prevent reserved ids from being requested
by the account request tool.
## PMC and committer base:
- Currently 9 committers, all on the PMC.
- Last addition was Craig L Russell in December of 2015.
-----------------------------------------
Attachment BN: Report from the Apache Xalan Project [Steven J. Hathaway]
The Apache Xalan Project develops and maintains libraries and programs
that transform XML documents using XSLT standard stylesheets. Our subprojects
use the Java and C++ programing languages to implement the XSLT libraries.
Xalan is a mature project, but we are hoping to acquire more committers
who can help with integration builds for a new release that integrates
Xerces-C.
ISSUES FOR THE BOARD
None.
CURRENT ACTIVITY
Oregon State University Capstone students are now working hard on the
Xalan source code and Apache web server integration to prototype
a high-performance XML transformation service. Student activity is
being tracked on GitHub as part of their classwork.
Most activity has been through JIRA issue tracking. The email lists
have seen little activity.
There has been sparce build activity toward patch releases.
MEMBERSHIP
Changes in the PMC membership:
None.
Last new committer:
May 2014
PROJECT RELEASES
Xalan Java 2.7.2 April 15, 2014
Xalan C/C++ 1.11 October 31, 2012
Publishing of project releases was refreshed Oct 30, 2014.
OTHER ISSUES
We would still appreciate more active persons to build Xalan-C tests.
We continue to get requests for Xalan to support XSLT version 2. The
Xalan libraries currently support XSLT version 1. Feature ugrades and
migration will require more than a few committers.
BRANDING ISSUES
None.
-----------------------------------------
Attachment BO: Report from the Apache Xerces Project [Michael Glavassevich]
-----------------------------------------
Attachment BP: Report from the Apache XML Graphics Project [Glenn Adams]
## Description:
- 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:
- There are no issues requiring board attention at this time.
## Activity:
- During this reporting period, activity on the three sub-projects
has remained low, with 48 issues resolved or closed during this
reporting period.
## Health:
- The level of community and developer activity remains at a
low level for a relatively mature product, albeit one
with a fair number of outstanding unresolved issues.
## PMC:
- Currently 11 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Simon Steiner on Tue Jan 19 2016
## Committers:
- Currently 21 committers.
- No new committers added in the last 3 months
- Last committer addition was Matthias Reischenbacher at Wed May 13
2015
## Releases:
- No releases during thiis period.
- XMLGraphics Commons 2.1 was released on Wed Jan 13 2016
- XMLGraphics FOP 2.1 was released on Wed Jan 13 2016
## Mailing Lists:
- Slight decrease in number of subscribers. Mail lists show a 30%
rise in message traffic from the previous period, up from 349 to
454.
------------------------------------------------------
End of minutes for the February 27, 2017 board meeting.
Index