Index
Links: 2018 - All years
- Original The Apache Software Foundation
Board of Directors Meeting Minutes
March 21, 2018
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: https://timeanddate.com/s/3fey
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
Ted Dunning
Jim Jagielski
Chris Mattmann
Brett Porter
Phil Steitz
Mark Thomas
Directors Absent:
none
Executive Officers Present:
Ross Gardler
Kevin A. McGrail
Sam Ruby
Craig L Russell
Executive Officers Absent:
Ulrich Stärk
Guests:
Daniel Gruno
Gavin McDonald
Greg Stein
Jake Farrell
Matt Sicker
Pierre Smits
Sally Khudairi
Tom Pappas
3. Minutes from previous meetings
Published minutes can be found at:
http://www.apache.org/foundation/board/calendar.html
A. The meeting of February 21, 2018
See: board_minutes_2018_02_21.txt
Approved by General Consent.
4. Executive Officer Reports
A. Chairman [Phil]
This month, we prepared and are in process of running the Annual
Mambers Meeting. We are also preparing the 2019 budget. The timing
of the decisions that we have to make, coincident with the election of
a new board and new members has created some stress among the
officers, directors and membership. That stress manifested in
behaviours on members@ and board@ that were not what we expect of
ourselves. I expect that we will do better moving forward.
The usual themes were repeated in some of the report comments this
month - remember to always include dates of most recent commmitter /
PMC additions and releases, keep discussions that can be on the public
dev list public, focus on helping new contributors earn merit so that
they can be voted in as committers and committers to PMC members. This
month, several projects were commmended and / or advised on handling
of security issues. A great resource for this is
https://www.apache.org/security/committers.html.
The Storm project submitted a very good report this month. In the
Activity and Health sections, there is good discussion of community
health, practical problems that the community is dealing with, and
actions taken. The Axis report was also very good this month, showing
continued progress restoring that community to a healthy and active
state.
B. President [Sam]
Issues for the board:
None this month. Next month there will be a FY19 budget to be
approved, and I will highlight the need to come to a decision on
how to proceed with Fundraising.
Overall
Yet another month where income exceeds targets, and expenses are
under budget. And that is not including the Pineapple BTC donation.
No major issues to report across operations. Sally and Mark are
actively working on issues related to companies not working with
our trademark policy. I'm confident that they both have matters
under control and/or will ask for help if/when they need to do so.
Fundraising
The key line in the fundraising report is: "the ability for me to
volunteer as VP Fundraising comes to an end". Next month, I intend
to recommend that the board fund this position for up to two years.
I encourage any returning or new directors who may be inclined to
reach a different conclusion to reach out directly to Tom, Sally,
and Kevin for their perspective; either 1-on-1 or collectively as
each of you see best.
Sponsorship thanks page now includes targeted sponsors:
https://www.apache.org/foundation/thanks.html
Kevin attended events at GMU NSF / Smartcities, OSLS & Google UC
Berkeley Tech Talk, and ISSA-NoVA. Expenses and results are detailed
in the Fundraising report.
Brand Management
The transition from Shane to Mark has gone smoothly, as expected.
Mark has established a new issue tracking process and reviewed
emails dating back to June 2017. Currently there are 25 issues,
and all are awaiting action from (P)PMC, external parties etc. to
progress them.
Mark is requesting input on the content and level of detail provided
in his report. I'm very happy with the report.
Additionally, please see Attachments 1 through 6.
C. Treasurer [Ulrich]
Virtual Report:
Here is a summary of the Foundation’s performance for the first Ten
months of FY18.
Operating Cash as of Feb 28th, 2018 was $1,804.6K, which is up $11.2K
from last month’s ending balance (Jan 18) of $1,793.4K. As a
majority of the Pineapple Donation was collected in Feb 18 ($695.6K)
this has been segregated as non-operating funds at this point until
the Board makes decision as to how to permanently record it. Total
Cash as of Feb 28th, 2018 is $2,500.2K. The Feb 2018 Operating cash
balance is up $382.2K from the Feb 17 month end balance of $1,476.4K
(and $1,023.8K in total cash compared to Feb 17, due to the $695.6K
Pineapple Donation amount collected). The Feb 2018 ending Operating
cash balance of $1,804.6K represents an Operating cash reserve of 16
months based on the FY18 conservative Cash forecast average monthly
spending of $112.6K/month. The ASF reserve continues to be very
healthy for an organization of ASF’ s size, with a conservative FY18
YE estimate of 15.9 months of Operating cash reserve.
Regarding the YTD Cash P&L, we continue to have a very strong and
favorable showing as compared to our FY18 budget through ten months
of FY18, however as I will continue to mention, because we are on a
cash basis, the timing of Sponsor payments received (including
multi-year sponsors) and Payables released plays a big part in how
well we perform financially month to month and year over year. This
month we were over the FY 18 budget for Revenue (Timing of estimated
sponsor payments were under but offset by a large annual donation
that was budgeted to be received in Mar 2018 offset the sponsorship
timing issue). The Foundation was also under the FY18 budget in
Expenses as well for February. As I have mentioned in previous
months we want to continue to focus on our new Sponsors, but we also
cannot take away any focus from our existing sponsors as that was how
the FY18 budget was constructed. If anything, the Fundraising effort
will become one of the most critical functions within the Foundation
especially with the upward trend in expenses noted in the 5-year plan
as the Foundation continues to grow each year. Any significant
disruption in the momentum that the Fundraising efforts have gained
in the last year, puts achieving the results noted in the 5-year plan
(that was voted in last month) in serious jeopardy, which will result
in the Foundation not continuing to grow as planned. The Fundraising
team continues to do an excellent job in both areas, servicing both
new and existing Sponsors. With total actual Revenue, as of Feb
28th, 2018, of $1,308.6K (up $97K from Jan 18 and up $615.9K from Feb
2017), we are 106.7% of the way to our Total Revenue budget of
$1,226.5K for FY18, with two months of FY18 remaining. Regarding
Sponsor revenue, we have received in the first ten months of FY18,
$1,143.6K, (up $18K from Jan 18 and up $579.1K from Feb 17) which has
us at 105.5% for YTD, exceeding the budgeted Sponsor revenue goal of
$1,084K for FY18. This is a great accomplishment as we still have 2
months left of FY 18 and we have exceeded our Sponsorship goal by
$59.6K (and we are estimating another $310K+ to come in between Mar
and Apr 18). As for the remaining revenue categories, we have
received $164.9K against a total budget of $142.5K or 1.16% of our FY
budget with 2 months left of FY18 (due to the timing of a large,
annual, one-time donation, which was budgeted to be received in Mar
18).
YTD expenses, through Feb 28th, 2018 are under budget by $110.6K.
All depts., for the first time in FY18, are under budget. We will
continue to monitor the actual vs budget as we move through the
remaining 2 months of FY18. As we finish up Mar 2018, I will be in
contact with the dept. heads, to make sure, as we are on a cash
basis, that any FY18 expenses are accounted for in FY18 and do not
carry over to FY19.
Regarding Net Income (NI), YTD for FY18 the ASF finished with a
positive $286.9K NI vs a budgeted negative <$394.2K> NI or $681.1K
ahead of the FY 18 Budget for Net Income ten months into the FY.
With the current conservative forecasted revenue, and expenses for
the remainder of FY 18, we are now estimating, at the Fiscal year
end, a positive $276.6K NI vs a budgeted NI loss of -$167.8K or about
a $444.4K better NI than the FY18 budget. This is attributable to a
combination of additional revenue and lower than budgeted expenses
for FY18 ($400.8K more in revenue and $43.6K in lower expenses based
on our conservative forecast). I would also like to point out that
YTD 18 NI vs YTD 17 NI we are $615.9K ahead in Revenue while Expenses
were $35.9K higher year over year, for a $580K increase in NI year
over year ($281.3K positive NI in FY18 vs <-$298.7K> NI in FY 17).
Again, I want to congratulate the entire Foundation on these very
positive Operating results now that we are ten months into FY 18 and
coming down the home stretch for the remainder of FY18. It does
truly take a team effort to achieve these types of results. Now that
we see what can be achieved by all our efforts, we do need to
continue to keep these efforts up as we move through the remainder of
FY 18, and into FY19. We need to continue to provide Fundraising all
the support and resources we can, to continue with the traction that
has been created with in the last year, while keeping an eye on our
expenses at the same time. We should also recognize that the
Foundation as compared to not only its FY18 budget but also to FY 17
actuals, is in “an extremely good place” by all measures and we
should all be very proud of that fact, as we finish out FY 18 and
enter FY19.
The Cash Basis Audit has been completed, and the ASF came through it
with flying colors, as we knew it would, receiving the highest rating
possible, that being an Unqualified opinion from the Auditors.
Everyone should be very proud of this result for the Foundation’s
first ever Independent Audit. Also, the 990 for FY17 was signed by
the Treasurer, submitted and accepted by the IRS well in advance of
the 3.15.18 due date. So, the Foundation is not only on very solid
financial footing but has been audited, for the first time, and has
filed all of its required compliance returns, both State and Federal
for FY17. One last item is the transfer of $1,500K of the
Foundations funds has been successfully transferred to CDARS, as the
assistant Treasurer had noted during the last Board meeting. This is
a CD “laddering” option that is administered by banks accredited by
the Treasury and is now fully insured by the FDIC which was not the
case when the deposits were in Citizens as the FDIC only insures up
to $205K per tax id number. Moving the Pineapple donation into the
CDAR system will begin in the next month or so.
Current Balances:
Boston Private Checking Account 1,500,000.00
Citizens Money Market 111,471.96
Citizens Checking 886,948.67
Paypal - ASF 1,813.47
Total Checking/Savings 2,500,234.10
Feb-18 Budget Variance
Income Summary:
Inkind Revenue 0.00 0.00 0.00
Public Donations 77,110.94 2,141.85 74,969.09
Sponsorship Program 18,000.00 61,000.00 -43,000.00
Programs Income 0.00 0.00 0.00
Other Income 1,434.16 0.00 1,434.16
Interest Income 436.45 292.92 143.53
Total Income 96,981.55 63,434.77 33,546.78
Expense Summary:
In Kind Expense 0.00 0.00 0.00
Infrastructure 59,389.40 62,956.17 -3,566.77
Sponsorship Program 3,944.35 2,000.00 1,944.35
Programs Expense 0.00 0.00 0.00
Publicity 7,799.29 10,000.00 -2,200.71
Brand Management 10,618.72 7,416.67 3,202.05
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,350.00 3,500.00 -150.00
General & Administrative 646.29 8,628.62 -7,982.33
Total Expense 85,748.05 94,501.46 -8,753.41
Net Income 11,233.50 -31,066.69 42,300.19
YTD 2018 Budget Variance
Income Summary:
Inkind Revenue 0.00 0.00 0.00
Public Donations 126,679.18 29,836.62 96,842.56
Sponsorship Program 1,143,612.08 677,250.00 466,362.08
Programs Income 15,100.00 28,025.00 -12,925.00
Other Income 15,980.48 0.00 15,980.48
Interest Income 7,210.87 2,929.20 4,281.67
Total Income 1,308,582.61 738,040.82 570,541.79
Expense Summary:
In Kind Expense 0.00 0.00 0.00
Infrastructure 681,342.78 684,556.70 -3,213.92
Sponsorship Program 23,442.76 30,250.00 -6,807.24
Programs Expense 0.00 0.00 0.00
Publicity 114,941.61 161,375.00 -46,433.39
Brand Management 54,779.74 74,166.70 -19,386.96
Conferences 5,200.59 8,418.00 -3,217.41
Travel Assistance Committee 2,191.81 22,500.00 -20,308.19
Tax and Audit 4,687.00 10,200.00 -5,513.00
Treasury Services 33,250.00 34,450.00 -1,200.00
General & Administrative 101,881.47 106,384.16 -4,502.69
Total Expense 1,021,717.76 1,132,300.56 -110,582.80
Net Income 286,864.85 -394,259.74 681,124.59
Asst Treasurer's Report:
- [IMPORTANT] Identified an operational concern caused by unclear
budgets for items crossing over fiscal years coupled with a lack
of signatory limits that presents a risk for the foundation. To
be clear, the issue at hand is that the status quo allows officers
to sign contracts in excess of their budgets because of a
precedent to use estimated net amounts for budget authority.
The solution I recommend is that the board is three fold:
1) be more specific on budget limits that look at the maximum,
worst-case scenario risk not the net. As a specific example, this
means that the VP of Conferences has a spending budget of 100K Net
with a Maximum Risk Authority of 250K covering the events in CALENDAR
year 2018 (not Fiscal Year).
2) expressly discuss during budget discussions that some expenditures
will be across FY and that VP is authorized to act in this manner.
Specific Example, we are looking to execute agreements for ApacheCon
2019.
3) require the treasurer’s agreement before committing the foundation
for any amounts over $5,000 (or that person’s credit card authority
whichever is greater). This adds a similar oversight to what exists
right now when sending actual money but applies to contracts,
purchase orders, etc..
Additionally, more clarity is needed for future years especially for
roles involving large sums of money and future events which is
primarily going to be our Events.
See this email for my initial report on the matter:
https://lists.apache.org/thread.html/af95e4303d2b7801a1d2da3f4841133b33b4583b8494da98859cac1b@%3Cboard.apache.org%3E
- Proposed Budget for Treasurer FY19
NOTE: Spreadsheet version available at:
https://docs.google.com/spreadsheets/d/1WdNOj0qvtCJEFtuxh7owrYR3488OOEC3gl1M9GQ3gEA/edit#gid=0
TREASURER FY19 Rationale Income Interest Income $14,400 CDARS &
Money Market - Interest income has been estimated conservatively.
This is an estimate based on market conditions that we cannot
influence. See below for the exact method used for the estimation.
Total Income $14,400 USD
Expenses Finance, Accounting and HQ services $40,200 The ASF is using
Virtual for our services at a cost of $3350/mth. Paid Expense
Solution $1,500 The ASF is using some paid solutions to streamline
processes and protect data confidentiality. This includes services
such as bill.com, dropbox (currently in use), Expensify, etc. CPA
Financial review / Audit $0 The Audit Is anticipated to be done every
3 years. Last done for FY17. Skipping FY18 and FY19 for an audit in
FY20. CPA 990 Preparation $4,500 The ASF files a United States IRS
tax return for non-profits called a 990. This is the anticipated
budget to prepare and file this form. We will work to reduce this to
$2500 with another vendor. Total Expense $46,200 USD
Total (Expenses - Income) $31,800 USD
- I've converted the BTC to $892,881.67 USD after bank fees and value
loss due to the volatility of the BTC. As of today, March 17,BTC
is at 8271. Upon donation, it was ~11,300.
- Filed 3rd quarter report for Treasurer and working on the annual
members meeting report
- 990 filing for the FY ending Apr 2017 is completed and e-filed.
- First audit completed with unqualified status for records through
FY ending Apr 2017 (that’s good). Next audit scheduled for FY2020.
- I have handled the PackT royalties and expect it to be annoying
ongoing. They now have my personal account having refused to send
the money any longer to a “business account”.
- Previously Reported Items Still Tracking w/Nothing to Report
Have not tested transferwise.com, pending a contractor’s help
testing.
Contribution Language for Car Donations - No update. Not a high
priority.
Need still to get contracts for Virtual, Hopsie & HALO confirmed and
in ASF SVN or drive.
Quickbooks Backups - Need to ping Virtual and check on progress for
this.
Documenting payment privacy changes is still in KAM’s court.
There is consensus that the budget should include both the
expected expense as well as offsetting expected revenue. This
will be reflected in the budget that will be discussed next
month.
D. Secretary [Craig]
Matt Sicker has volunteered to help secretary, and has already been
responsible for filing two dozen incoming documents. Please see
Discussion item 8B to discuss appointing Matt to Assistant Secretary.
In February 73 ICLAS, three CCLAs, and two grants were received and
filed.
E. Executive Vice President [Ross]
Infrastructure
==============
No issues to report. For the most part it's business as usually, two
items of particular interest are:
Progress being made on a self service infrastructure (Apache
Infrastructure Management, AIM). This will free infra team members to
focus on non-standard requests and issues.
Some analysis of our usage of Travis is providing valuable data to
help with capacity planning in the future.
Marketing and Publicity
=======================
VP M&P is actively engaging with a company engaged with one of our
high profile projects that is having some difficulties working within
our trademark policy. The main focus of her work is to educate the
company on what is and is not acceptable use of our marks.
Otherwise business as usual.
Conferences
===========
Apache EU Roadshow program is published -
https://apachecon.com/euroadshow18/
Apache North America CFP is open and going well. Two keynotes have
been announced. Details at http://apachecon.com/acna18/
TAC
===
Applications for ApacheCon NA applications are open (closing May 1st).
Judges have started reviewing. It's great to see TAC being on track
again. Well done team.
F. Vice Chairman [Jim]
Nothing to report. Thanks for all the fish.
Executive officer reports approved as submitted by General Consent.
5. Additional Officer Reports
A. VP of W3C Relations [Andy Seaborne / Jim]
See Attachment 8
B. Apache Legal Affairs Committee [Chris Mattmann]
See Attachment 9
C. Apache Security Team Project [Mark J. Cox / Ted]
See Attachment 10
Additional officer reports approved as submitted by General Consent.
6. Committee Reports
Summary of Reports
The following reports required further discussion:
# Sentry [mt]
# Tomcat [rb]
# UIMA [rb]
# Xerces [jj]
A. Apache Allura Project [David Philip Brondsema / Chris]
See Attachment A
B. Apache Any23 Project [Lewis John McGibbney / Phil]
See Attachment B
C. Apache Archiva Project [Olivier Lamy / Shane]
No report was submitted.
@Shane: pursue a report for Archiva
D. Apache Atlas Project [Madhan Neethiraj / Bertrand]
See Attachment D
E. Apache Aurora Project [Jake Farrell / Rich]
See Attachment E
F. Apache Axis Project [Robert Lazarski / Brett]
See Attachment F
G. Apache Bahir Project [Luciano Resende / Mark]
No report was submitted.
@Mark: pursue a report for Bahir
H. Apache Beam Project [Davor Bonaci / Chris]
See Attachment H
I. Apache Bigtop Project [Evans Ye / Phil]
See Attachment I
J. Apache Bloodhound Project [Gary Martin / Rich]
See Attachment J
K. Apache BVal Project [Matthew Jason Benson / Ted]
See Attachment K
L. Apache Camel Project [Christian Mueller / Brett]
No report was submitted.
@Brett: pursue a report for Camel
M. Apache Cayenne Project [Michael Ray Gentry / Shane]
See Attachment M
N. Apache Chemistry Project [Florian Müller / Mark]
See Attachment N
O. Apache CloudStack Project [Wido den Hollander / Bertrand]
See Attachment O
P. Apache Commons Project [Gary D. Gregory / Jim]
See Attachment P
Q. Apache Cordova Project [Shazron Abdullah / Chris]
See Attachment Q
R. Apache cTAKES Project [Pei Chen / Jim]
See Attachment R
S. Apache Curator Project [Jordan Zimmerman / Mark]
See Attachment S
T. Apache DataFu Project [Matthew Hayes / Bertrand]
See Attachment T
U. Apache DRAT Project [Chris Mattmann]
See Attachment U
V. Apache Eagle Project [Edward Zhang / Rich]
See Attachment V
W. Apache Falcon Project [Pallavi Rao / Shane]
See Attachment W
X. Apache Felix Project [Karl Pauls / Brett]
See Attachment X
Y. Apache Flex Project [Tom Chiverton / Ted]
See Attachment Y
Z. Apache Flink Project [Stephan Ewen / Phil]
See Attachment Z
AA. Apache Giraph Project [Avery Ching / Brett]
No report was submitted.
@Brett: pursue a report for Giraph
AB. Apache Guacamole Project [Mike Jumper / Shane]
See Attachment AB
AC. Apache Gump Project [Stefan Bodewig / Rich]
See Attachment AC
AD. Apache Hama Project [Chia-Hung Lin / Phil]
No report was submitted.
@Phil: pursue a report for Hama
AE. Apache Helix Project [Kishore G / Mark]
See Attachment AE
AF. Apache Hive Project [Ashutosh Chauhan / Jim]
See Attachment AF
AG. Apache Incubator Project [John D. Ament / Ted]
See Attachment AG
AH. Apache Jackrabbit Project [Michael Dürig / Bertrand]
See Attachment AH
AI. Apache James Project [Eric Charles / Chris]
See Attachment AI
AJ. Apache Karaf Project [Jean-Baptiste Onofré / Bertrand]
See Attachment AJ
AK. Apache Labs Project [Danny Angus / Mark]
See Attachment AK
AL. Apache Lucene Project [Adrien Grand / Rich]
See Attachment AL
AM. Apache Lucene.Net Project [Prescott Nasser / Shane]
No report was submitted.
@Shane: pursue a report for Lucene.Net
AN. Apache Mnemonic Project [Gang Wang / Brett]
See Attachment AN
AO. Apache Mynewt Project [Justin Mclean / Ted]
No report was submitted.
@Ted: pursue a report for Mynewt
AP. Apache OFBiz Project [Jacopo Cappellato / Phil]
See Attachment AP
AQ. Apache Olingo Project [Christian Amend / Chris]
See Attachment AQ
AR. Apache Oltu Project [Antonio Sanso / Jim]
No report was submitted.
AS. Apache OODT Project [Tom Barber / Rich]
See Attachment AS
AT. Apache OpenNLP Project [Jörn Kottmann / Chris]
See Attachment AT
AU. Apache OpenWebBeans Project [Mark Struberg / Brett]
See Attachment AU
AV. Apache Perl Project [Philippe Chiasson / Bertrand]
No report was submitted.
AW. Apache Pig Project [Koji Noguchi / Phil]
See Attachment AW
AX. Apache Pivot Project [Roger Lee Whitcomb / Ted]
See Attachment AX
AY. Apache Polygene Project [Paul Merlin / Shane]
See Attachment AY
AZ. Apache Portable Runtime (APR) Project [Nick Kew / Jim]
See Attachment AZ
BA. Apache Portals Project [David Sean Taylor / Mark]
See Attachment BA
BB. Apache PredictionIO Project [Donald Szeto / Shane]
See Attachment BB
BC. Apache Royale Project [Harbs / Rich]
See Attachment BC
BD. Apache Sentry Project [Alex Kolbasov / Phil]
See Attachment BD
@Mark: get an answer to question on previous report:
"..automatic generation of license information..."
BE. Apache ServiceMix Project [Krzysztof Sobkowiak / Ted]
See Attachment BE
BF. Apache Shiro Project [Les Hazlewood / Jim]
See Attachment BF
BG. Apache Sling Project [Robert Munteanu / Chris]
See Attachment BG
BH. Apache SpamAssassin Project [Sidney Markowitz / Mark]
See Attachment BH
BI. Apache Stanbol Project [Fabian Christ / Brett]
No report was submitted.
@Brett: pursue a report for Stanbol
BJ. Apache Storm Project [P. Taylor Goetz / Bertrand]
See Attachment BJ
BK. Apache Synapse Project [Isuru Udana / Jim]
See Attachment BK
BL. Apache Tajo Project [Hyunsik Choi / Mark]
See Attachment BL
BM. Apache Tiles Project [Michael Semb Wever / Bertrand]
See Attachment BM
BN. Apache Tomcat Project [Mladen Turk / Rich]
See Attachment BN
BO. Apache Trafodion Project [Pierre Smits / Brett]
See Attachment BO
BP. Apache Twill Project [Terence Yim / Ted]
See Attachment BP
BQ. Apache UIMA Project [Marshall Schor / Phil]
See Attachment BQ
BR. Apache VCL Project [Josh Thompson / Shane]
See Attachment BR
BS. Apache Wicket Project [Martijn Dashorst / Chris]
No report was submitted.
BT. Apache Xalan Project [Steven J. Hathaway / Phil]
See Attachment BT
BU. Apache Xerces Project [Michael Glavassevich / Jim]
See Attachment BU
@Jim: when will the TM be added to the logo?
BV. Apache Yetus Project [Allen Wittenauer / Shane]
See Attachment BV
BW. Apache ZooKeeper Project [Flavio Paiva Junqueira / Ted]
See Attachment BW
Committee reports approved as submitted by General Consent.
7. Special Orders
A. Establish the Apache FreeMarker Project
WHEREAS, the Board of Directors deems it to be in the best interests
of the Foundation and consistent with the Foundation's purpose to
establish a Project Management Committee charged with the creation and
maintenance of open-source software, for distribution at no charge to
the public, related to a template engine.
NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
(PMC), to be known as the "Apache FreeMarker Project", be and hereby
is established pursuant to Bylaws of the Foundation; and be it further
RESOLVED, that the Apache FreeMarker Project be and hereby is
responsible for the creation and maintenance of software related to a
template engine, and be it further
RESOLVED, that the office of "Vice President, Apache FreeMarker" be
and hereby is created, the person holding such office to serve at the
direction of the Board of Directors as the chair of the Apache
FreeMarker Project, and to have primary responsibility for management
of the projects within the scope of responsibility of the Apache
FreeMarker Project; and be it further
RESOLVED, that the persons listed immediately below be and hereby are
appointed to serve as the initial members of the Apache FreeMarker
Project:
* Dániel Dékány <ddekany@apache.org>
* David E. Jones <jonesde@apache.org>
* Jacopo Cappellato <jacopoc@apache.org>
* Jacques Le Roux <jleroux@apache.org>
* Nan Lei <nanlei@apache.org>
* Sergio Fernández <wikier@apache.org>
* Woonsan Ko <woonsan@apache.org>
NOW, THEREFORE, BE IT FURTHER RESOLVED, that Dániel Dékány be
appointed to the office of Vice President, Apache FreeMarker, to serve
in accordance with and subject to the direction of the Board of
Directors and the Bylaws of the Foundation until death, resignation,
retirement, removal or disqualification, or until a successor is
appointed; and be it further
RESOLVED, that the Apache FreeMarker Project be and hereby is tasked
with the migration and rationalization of the Apache Incubator
FreeMarker podling; and be it further
RESOLVED, that all responsibilities pertaining to the Apache Incubator
FreeMarker podling encumbered upon the Apache Incubator Project are
hereafter discharged.
Special Order 7A, Establish the Apache FreeMarker Project, was
approved by Unanimous Vote of the directors present.
B. Change the Apache XML Graphics Project Chair
WHEREAS, the Board of Directors heretofore appointed Glenn Adams
(gadams) to the office of Vice President, Apache XML Graphics, and
WHEREAS, the Board of Directors is in receipt of the resignation of
Glenn Adams from the office of Vice President, Apache XML Graphics, and
WHEREAS, the Project Management Committee of the Apache XML Graphics
project has chosen by vote to recommend Clay Leeds (clay) as
the successor to the post;
NOW, THEREFORE, BE IT RESOLVED, that Glenn Adams is relieved and
discharged from the duties and responsibilities of the office of Vice
President, Apache XML Graphics, and
BE IT FURTHER RESOLVED, that Clay Leeds be and hereby is
appointed to the office of Vice President, Apache XML Graphics, 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 XML Graphics Project
Chair, was approved by Unanimous Vote of the directors
present.
C. Change the Apache Tcl Project Chair
WHEREAS, the Board of Directors heretofore appointed Massimo Manghi
(mxmanghi) to the office of Vice President, Apache Tcl, and
WHEREAS, the Board of Directors is in receipt of the resignation of
Massimo Manghi from the office of Vice President, Apache Tcl, and
WHEREAS, the Project Management Committee of the Apache Tcl project
has chosen by vote to recommend Georgios Petasis (petasis) as the
successor to the post;
NOW, THEREFORE, BE IT RESOLVED, that Massimo Manghi is relieved and
discharged from the duties and responsibilities of the office of
Vice President, Apache Tcl, and
BE IT FURTHER RESOLVED, that Georgios Petasis be and hereby is
appointed to the office of Vice President, Apache Tcl, to serve in
accordance with and subject to the direction of the Board of
Directors and the Bylaws of the Foundation until death,
resignation, retirement, removal or disqualification, or until a
successor is appointed.
Special Order 7C, Change the Apache Tcl Project Chair, was
approved by Unanimous Vote of the directors present.
D. Change the Apache Phoenix Project Chair
WHEREAS, the Board of Directors heretofore appointed James R. Taylor
(jamestaylor) to the office of Vice President, Apache Phoenix, and
WHEREAS, the Board of Directors is in receipt of the resignation of
James R. Taylor from the office of Vice President, Apache Phoenix, and
WHEREAS, the Project Management Committee of the Apache Phoenix project
has chosen by vote to recommend Josh Elser (elserj) as the
successor to the post;
NOW, THEREFORE, BE IT RESOLVED, that James R. Taylor is relieved and
discharged from the duties and responsibilities of the office of
Vice President, Apache Phoenix, and
BE IT FURTHER RESOLVED, that Josh Elser be and hereby is
appointed to the office of Vice President, Apache Phoenix, to serve in
accordance with and subject to the direction of the Board of
Directors and the Bylaws of the Foundation until death,
resignation, retirement, removal or disqualification, or until a
successor is appointed.
Special Order 7D, Change the Apache Phoenix Project Chair, was
approved by Unanimous Vote of the directors present.
E. Change the Apache CloudStack Project Chair
WHEREAS, the Board of Directors heretofore appointed Wido den
Hollander (widodh) to the office of Vice President, Apache CloudStack,
and
WHEREAS, the Board of Directors is in receipt of the resignation of
Wido den Hollander 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 Mike Tutkowski (mtutkowski) as
the successor to the post;
NOW, THEREFORE, BE IT RESOLVED, that Wido den Hollander is relieved
and discharged from the duties and responsibilities of the office of
Vice President, Apache CloudStack, and
BE IT FURTHER RESOLVED, that Mike Tutkowski 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 7E, Change the Apache CloudStack Project Chair,
was approved by Unanimous Vote of the directors present.
F. Change the Apache Tez Project Chair
WHEREAS, the Board of Directors heretofore appointed Siddharth
Seth (sseth) to the office of Vice President, Apache Tez, and
WHEREAS, the Board of Directors is in receipt of the resignation
of Siddharth Seth from the office of Vice President, Apache Tez,
and
WHEREAS, the Project Management Committee of the Apache Tez
project has chosen by vote to recommend Jonathan Eagles (jeagles) as
the successor to the post;
NOW, THEREFORE, BE IT RESOLVED, that Siddharth Seth is relieved and
discharged from the duties and responsibilities of the office
of Vice President, Apache Tez, and
BE IT FURTHER RESOLVED, that Jonathan Eagles be and hereby is
appointed to the office of Vice President, Apache Tez, 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 Tez Project Chair, was
approved by Unanimous Vote of the directors present.
G. Terminate the Apache Oltu Project
WHEREAS, the Board of Directors deems it no longer in the best
interest of the Foundation to continue the Apache Oltu project
due to inactivity;
NOW, THEREFORE, BE IT RESOLVED, that the Apache Oltu
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 Oltu
Project; and be it further
RESOLVED, that the office of "Vice President, Apache Oltu" is
hereby terminated; and be it further
RESOLVED, that the Apache Oltu PMC is hereby terminated.
Special Order 7G, Terminate the Apache Oltu Project, was
approved by Unanimous Vote of the directors present.
8. Discussion Items
A. Review /board/policies page for use
We have a simple yet comprehensive single page list of all services
available to PMCs, and policies required of PMCs by the board. The
board should agree to remove the DRAFT markers and use this page to
help improve board<->PMC shared expectations.
https://www.apache.org/board/policies
@Shane: discuss this proposal on board@ for the next board to take up.
B. Appoint Matt Sicker to the position of Assistant Secretary
Matt has volunteered to help Secretary, and since early March, has been
filing incoming documents. Craig would like the board to formally
recognize his contributions by appointing him Assistant Secretary,
replacing Sam Ruby. Thanks to Sam for his dedicated service in this role.
The board appoints Matt Sicker to Assistant Secretary, relieving Sam
Ruby.
9. Review Outstanding Action Items
* Ted: Discuss state of development with PMC; encourage on-list development
[ Tajo 2017-06-21 ]
Status: I have had off-list discussions with Hunsik. There is a
considerable amount of chaebol politics that has inhibited a
number of committers from contributing back. He is working to
smooth that out. I have high uncertainty about whether he can
do that.
* Ted: pursue a report for Community Development; look at previous examples of
[ Community Development 2017-08-16 ]
Status:
* Rich: follow up on previous board comments regarding PMC and committers
[ UIMA 2017-12-20 ]
Status: UIMA have responded to our concerns and have will report
PMC/Commiter names/dates in future reports.
* Mark: pursue feedback from board meetings
[ ActiveMQ 2018-01-17 ]
Status: Complete: Bruce replied on private@ and I copied that reply to
board@
* Mark: follow up board feedback
[ AsterixDB 2018-01-17 ]
Status: Complete: Till replied on private@ and I copied that reply to
board@
* Jim: work with Greg on resourcing infra resources for OpenOffice
[ Executive Vice President 2018-02-21 ]
Status: Action started
* Mark: is this project still viable?
[ Clerezza 2018-02-21 ]
Status: Ongoing: PMC is conducting a roll-call
* Jim: pursue a report for Giraph
[ Giraph 2018-02-21 ]
Status: PMC pinged. No report
* Chris: pursue a report for Hama
[ Hama 2018-02-21 ]
Status: didn't get a chance to finish this, so please reassign to one
of the new directors.
* Danny: pursue a report for James
[ James 2018-02-21 ]
Status: present
* Brett: discuss with PMC content of the report
[ Mnemonic 2018-02-21 ]
Status: got a response on list
* Jim: draft a resolution for the Attic for Oltu
[ Oltu 2018-02-21 ]
Status: Complete
* Jim: follow up with PMC on activity
[ Open Climate Workbench 2018-02-21 ]
Status: Will need someone else to take this on
* Chris: pursue a report for Perl
[ Perl 2018-02-21 ]
Status: didn't get to finish this, so time for a new Director to step
in here.
* Brett: pursue a report or Attic proposal for Xalan
[ Xalan 2018-02-21 ]
Status: report received, will follow up the previous comment
10. Unfinished Business
11. New Business
12. Announcements
Thanks to the outgoing board, especially to the members who will not
be returning: Jim Jagielski and Chris Mattmann.
13. Adjournment
Adjourned at 11:46 a.m. (Pacific)
============
ATTACHMENTS:
============
-----------------------------------------
Attachment 1: Report from the VP of Brand Management [Mark Thomas]
* ISSUES FOR THE BOARD
None.
* OPERATIONS
The transition of the role of VP Brand from Shane Curcuru to Mark Thomas
is complete.
The new GSuite based issue tracking process (modelled after the process
used by the Security Team) is up and running and working well so far.
All mail to trademarks@ dating back to 1 June 2017 has been loaded into
GSuite and has been reviewed for outstanding issues. Out of ~270 threads
since then there are ~25 current issues. All of these are up to date and
are waiting on action from (P)PMC, external parties etc. to progress them.
An overdue invoice (we had no record of the original) was identified and
paid. Contact details were clarified and subsequent invoices have been
received correctly.
David Fisher (wave) has joined the Brand Management committee.
Jukka Zitting (jukka) and Upayavira (upayavira) resigned from the Brand
Management committee.
I've noticed a more than expected level of off-list communication from
both inside and outside the foundation. Nearly all of it belongs on list
and I am re-directing it to the relevant list as it arrives.
As this is my first report as VP Brand, I'd welcome feedback on the
content and level of detail provided.
* REGISTRATIONS
A letter of understanding has been signed with the Eclipse Foundation
allowing Eclipse to use the name Jakarta EE as the new name for Java EE.
The OpenOffice PMC have reviewed their existing trademark registrations
and proposed a plan for future registrations and renewals. This is a
very welcome action and the plan is now under discussion.
-----------------------------------------
Attachment 2: Report from the VP of Fundraising [Kevin A. McGrail]
- Overall fundraising continues well with sponsorship exceeding targets for
the entire year without considering the additional $892K from Pineapple.
- The Sponsor Thanks Page with targeted sponsors is now launched
https://www.apache.org/foundation/thanks.html
- Switched the BTC Donation wallet to a Coinbase wallet on apache.org. No
longer using the old wallet.
- As the ability for me to volunteer as VP Fundraising comes to an end, I
have submitted a proposal to the board to continue in a paid role while at
the same time working to make sure the G Suite team drive is highly
organized and things are well documented. Additionally, moderation for the
fundraising & fundraising-private are now moderated by a group (thanks to
Mark Thomas).
- Apache Roadshow DC is shaping up nicely:
https://docs.google.com/spr eadsheets/d/1tzHt55CUEMs-r-PDdCEk0-N7mqyTe9Ty5W2jy_YnLfs/edit#gid=979328350
Fundraising for our events is off to a nice start with an event contract
created based on our sponsorship agreement and 4 sponsors with contracts in
their inbox representing $52K if inked with many many more in the pipeline.
- targeted sponsorship for one sponsor is now $5k annual renewable + $60 per year for 3
years, renewable after 24 months.
- On behalf of ASF, I attended a GMU NSF / Smartcities event to identify
potential sponsors and review the space for the DC Rodshow. Total costs: 55.97.
- Also attended OSLS & Google UC Berkeley Tech Talk to talk with the Linux
Foundation, identify potential sponsors, and talk to current sponsors.
Costs $2,343.73
The next event was a Tech Talk at Google. Overall a good event. I spoke to
quite a number of people about sponsoring the AC
At Berkeley and OSLS, was able to support the International Women's Day. No more
bracelets left and I think they were a big hit.
- I am now out of all of the red do IT like a girl bracelets with the last 50
shipped to support the United Women in Cyber which I will attend on the
29th as well on behalf of the ASF
- Attended ISSA-NoVA Monthly meeting to ask them to advertise our events,
identify possible sponsors and discuss the CFP. Will be pitching two
recruiters to sponsor and ISSA-NOVA will share our event with their
members. Costs: 49.13.
- Filed 3rd quarter report for Fundraising and working on the annual members
meeting report
- Minimum donation implemented (I think it’s $5 or $10) with Hopsie to slow
down the abuse and small charges with exorbitant fees.
-----------------------------------------
Attachment 3: Report from the VP of Marketing and Publicity [Sally Khudairi]
[REPORT] ASF Marketing & Publicity - March 2018
I. Budget: we have submitted our budget for the upcoming the fiscal year.
Standing, and/or mult-year contracts with press release distribution, media
clipping, and projects analytics services have been renewed to avoid
interruption in service, and will be invoiced in FY2019. We are projected to
remain on budget and on schedule through the remainder of the fiscal year. The
quarterly report for Q3 FY2018 is underway and will be published shortly.
II. Cross-committee Liaison: work with ASF Fundraising continues. We published
"Success at Apache" twice to accommodate a lag in production at the beginning
of the year; they are: "A Newbie's Narrative" https://s.apache.org/A72H and
"Contributing to Open Source even with a high-pressure job"
https://s.apache.org/lM9O. Sally Khudairi has been helping ApacheCon on
promoting the event. She is also once again counseling a specific vendor
involved with a highly-visible Apache project in the Big Data space regarding
their repeat offenses regarding established ASF publicity, outreach, and
branding guidelines. Sally initially brought the issue to the project's PMC
and worked with the vendor's marketing and PR teams with specific instruction
in May 2016.
III. Press Releases: the following formal announcements were issued via the
newswire service, ASF Foundation Blog, and announce@apache.org during this
timeframe:
- 12 February 2018 - The Apache Software Foundation Announces Apache®
CloudStack® v4.11
IV. Informal Announcements: 7 items were published on the ASF "Foundation"
Blog. 4 Apache News Round-ups were issued, with a total of 191 weekly
summaries published to date. We tweeted 28 items, and have 46.7K followers on
Twitter. We posted 7 items on LinkedIn, which garnered more than 40.4K organic
impressions in total.
V. Future Announcements: three announcements are 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 5 media queries. The ASF 3,200 received
press clips vs. last month's clip count of 1,682. Media coverage of Apache
projects yielded 7,185 press hits vs. last month's 3,846. ApacheCon received
23 press hits.
VII. Analyst Relations: we received three analyst queries. Apache was
mentioned in 27 reports by Gartner (including 6 Magic Quadrant reports:
Identity Governance and Administration {Apache Syncope}, Data Management
Solutions for Analytics {Apache HBase, Impala, and Kudu}, Data Science and
Machine-Learning Platforms {Apache Spark}, Managed Security Services,
Worldwide, Analytics and Business Intelligence Platforms, and Data and
Analytics Service Providers, Worldwide, ): no reports by Forrester, 11 reports
by 451 Research, and 5 reports by IDC.
VIII. Graphics: no projects are in production.
IX. Events liaison: Sally continues work with ASF Conferences and ComDev
regarding upcoming Apache Community events and ApacheCon.
X. Newswire accounts: we have 7 pre-paid press releases remaining with NASDAQ
GlobeNewswire through 2018.
# # #
-----------------------------------------
Attachment 4: Report from the VP of Infrastructure [David Nalley]
General
=======
Infrastructure is operating as expected, and has no current issues to
bring to the attention of the President or the Board.
Finances
========
We have entered "budget season". Infrastructure has submitted its
first draft to the President for inclusion into a draft budget. That
draft will be presented to Members during our Annual Members Meeting
(starting March 20th), and later to the Board that will be elected
during that Meeting.
For Fiscal Year 18 (May 2017 to April 2018), the Infrastructure team
has managed its outlays and should end the year on-budget. We've
adjusted our FY19 request based on past-year actuals, and expected
growth in outlays corresponding to the Foundation's growth.
Short Term Priorities
=====================
* We have picked up some responsibilities for running Apache STeVe as
the voter tool, used by the Foundation, for its Annual Meeting
* The feature for "searching of private ASF archives" is being
removed, in favor of a longer-term solution focused around
lists.apache.org. However, mail-search.apache.org still resides on
old hardware and needs to be migrated before our expected timeframe
for validating "full production" of lists.a.o. The browsing of
private archives is in-process, and should be deployed shortly to
mail-private.apache.org.
General Activity
================
* As part of our migration plan, mail-archives.apache.org has been
moved to a brand new VM (rather than ASF-owned metal). The site has
been reviewed, verified, and switched over to the new VM. This is
just one part of our overall migration process, and upgrading the
many systems involved in our mail handling, but a very necessary
part that is now behind us.
* We have been continuing work on ASF users being able to "self serve"
their needs. Over the past month, we've improved the ability for
Incubator Members be able to request new respositories, mailing
lists, and other resource for their podlings. Another facility was
added to assist with recovering from problems in website updates.
* Using some of the Travis CI APIs, and working with their support
team, we have been able to analyze our usage of running builds,
their concurrency, and queueing of builds. This will help us to
review our capacity planning, and determine growth needs around our
projects' use of Travis.
-----------------------------------------
Attachment 5: Report from the VP of Conferences [Rich Bowen]
Over the last month, much progress has been made on all currently-active
events. That is, ApacheCon North America 2018, the Apache EU Roadshow, and the
proposed DC Roadshow.
The schedule for the EU Roadshow has been published, and this event is paid
for and ready to go. Sharan has handled everything about that event. I (Rich)
anticipate that I will be on-site for that event, but I am still sorting out
details. Details of this event are at https://apachecon.com/euroadshow18/
The CFP for the North America event is going well. Sponsorship and other
planning items are progressing smoothly. Two keynotes have been announced, and
two others are in discussion. Details of this event are at
http://apachecon.com/acna18/
Please join the planners@apachecon.com mailing list if you wish to help,
volunteer, or be better informed. Archives of that list are, of course,
available on lists.apache.org
-----------------------------------------
Attachment 6: Report from the Apache Travel Assistance Committee [Gavin McDonald]
After the initial ramp up and getting applications open, we are now in a quiet
period. Applications are coming in steadily and at least two judges are
starting to score them as they come in. In a week or so we'll send out another
reminder to committers and PMCs.
Applications close on May 1st - at which time the judges will get together and
compare scores etc.
-----------------------------------------
Attachment 8: Report from the VP of W3C Relations [Andy Seaborne]
Nothing to report this month.
-----------------------------------------
Attachment 9: Report from the Apache Legal Affairs Committee [Chris Mattmann]
Despite my original intention to step down, I had a change of heart
and desire to continue as VP, Legal for the near future. I will be
looking over the next 6-12 months for an appropriate candidate if
one emerges to train in the role so there is a smooth transition
when the time is right. Thanks to those who sent words of encouragement
to continue on.
Not a busy month but there were a handful of issues to report on.
In LEGAL-363 [1] we are disussing the use of CC-BY-4.0 HTML and CSS
in Example code. Discussions are ongoing, but based on precedent
this will likely be disallowed.
A question surrounding ASF, copyleft and container images, includes
ongoing discussion about the ability for projects to publish
"official" Apache container releases. Guidance from Legal at this
point is that the ASF only releases source code, and our policy
officially covers that. However, the ASF does allow for binary or
"convenience" artifacts, as unofficial artifacts released by the
PMC. It would seem that Docker containers fall into this area, and
so Legal is unlikely to provide any specific approvals, etc., and
we do not see this as outside of the existing approach to dealing
with binary / convenience artifacts. Guidance was provided to check
with infra regarding the ability to publish to DockerHub.
The committee answered a question regarding an external project
already licensed under the ALv2 and whether it made sense to a)
fork the project; and b) if so, bring the project into the ASF via
the Incubator. Legal committee recommended that the upstream project
determine the situation surrounding the copyright for the existing
code first before continuing the discussion surrounding Apache
incubation. The resolution was provided in LEGAL-367 [2].
Discussion is ongoing in reference to the inclusion of documentation
produced by the Open Grid Forum (OGF) within an Apache project. The
documentation is licensed using the OGF license. The discussion in
LEGAL-369 [3] led to the creation of LEGAL-372 [4] in which their
is a request to categorize the OGF license. That classification is
critical to determine how to proceed in LEGAL-369.
One of our podlings requested a definitive ruling regarding the
necssity of including a list of 3rd party dependencies accompanying
software grants from upstream IP holders. Legal does not believe
these are required, though in the recent past, a company did provide
such a list along with a grant, and Legal saw no problem with its
inclusion. However, the ASF secretary and the podling mentors for
the project in question do not believe that the list is a requirement
- and Legal agrees. The discussion is close to resolution in LEGAL-374
[5].
Finally, a question was quickly answered regarding the use of Jetty
in Apache projects in LEGAL-375 [6].
[1] https://issues.apache.org/jira/browse/LEGAL-363
[2] https://issues.apache.org/jira/browse/LEGAL-367
[3] https://issues.apache.org/jira/browse/LEGAL-369
[4] https://issues.apache.org/jira/browse/LEGAL-372
[5] https://issues.apache.org/jira/browse/LEGAL-374
[6] https://issues.apache.org/jira/browse/LEGAL-375
-----------------------------------------
Attachment 10: Report from the Apache Security Team Project [Mark J. Cox]
Continued work on incoming security issues and helping projects clean
up the backlog of old issues and outstanding CVE names. Meanwhile we
continue being responsive to new security@ emails, with all issues
recently handled by next working day (and most within hours).
* 2018-03-01 there were 117 open issues across 58 projects with median
ages 84 days (2018-02-01 there were 142 open issues across 59
projects with median age 89 days). (Around a dozen are github
dependancies that mostly will have no security consequence)
* 2018-03-01 there are only 3 CVE not yet in Mitre CVE database from
before Apache became a CNA in 2017. This is down from 133 when we
started the cleanup on 2017-05-09.
Stats for February 2018.
10 [license confusion]
9 [support request/question not security notification]
Security reports: 40
3 [hadoop]
3 [openoffice]
2 [hive]
2 [lucene]
2 [ofbiz]
2 [spamassassin]
2 [tomcat]
2 [struts]
1 each [allura],[ambari],[beam],[brooklyn],[camel],[derby]
[geode],[guacamole],[incubator/hawq],[incubator/superset]
[infrastructure],[juddi],[kafka],[knox],[nifi],[portals]
[ranger],[spark],[synapse],[thrift],[xerces],[zeppelin]
-----------------------------------------
Attachment A: Report from the Apache Allura Project [David Philip Brondsema]
## Description:
Apache Allura is an open source implementation of a software forge, a web site
that manages source code repositories, bug reports, discussions, wiki pages,
blogs, and more for any number of individual projects.
## Issues:
- No issues needing board attention.
## Activity:
- Handled with our first CVE security issue
- Some Google Summer of Code interest
- Various improvements and fixes continue
## Health report:
Development is slow but steady. A new release manager is handling our current
release.
## PMC changes:
- No changes.
- Currently 14 PMC members.
- Kenton Taylor was added to the PMC on Sun Jan 22 2017
## Committer base changes:
- No changes.
- Currently 14 committers.
- Kenton Taylor was added as a committer on Thu Jan 19 2017
## Releases:
- 1.8.0 was released on Sun Feb 04 2018
- 1.8.1 in progress currently
-----------------------------------------
Attachment B: Report from the Apache Any23 Project [Lewis John McGibbney]
## Description:
Anything To Triples (Any23) is a library, a web service and a command line
tool that extracts structured data in RDF format from a variety of Web
documents.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
Activity has really picked up this last quarter. The Any23 community is
currently (2018-03/05) VOTE'ing on a 2.2 RC#2 which includes a large number
of improvements, bug fixes and features. There was an issue with the 2.2 RC#2
which is being addressed at https://issues.apache.org/jira/browse/INFRA-16130,
essentially the Any23 service artifacts are rather large, this will have an
inevitable impact on Mirror(s) and the network so INFRA is kindly suggested that
we try to work things through a CDN. We will pursue this offer with the aim of
distributing the service artifacts in future releases.
## Health report:
Any23 is looking in good shape. Enjoying a peak in community activity and source
code contributions. Life is good!
## PMC changes:
- Currently 15 PMC members.
- Hans Brende was added to the PMC on Sun Feb 25 2018
## Committer base changes:
- Currently 15 committers.
- Hans Brende was added as a committer on Wed Feb 21 2018
## Releases:
- 2.1 was released on Tue Oct 31 2017
## Mailing list activity:
Stats on user@ and dev@ are up which is great. Hopefully
our 2.2 release will increase these further over the next
quarter.
- dev@any23.apache.org:
- 38 subscribers (up 3 in the last 3 months):
- 442 emails sent to list (52 in previous quarter)
- user@any23.apache.org:
- 49 subscribers (up 1 in the last 3 months):
- 16 emails sent to list (4 in previous quarter)
## JIRA activity:
- 19 JIRA tickets created in the last 3 months
- 45 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment C: Report from the Apache Archiva Project [Olivier Lamy]
-----------------------------------------
Attachment D: Report from the Apache Atlas Project [Madhan Neethiraj]
## Description:
Apache Atlas is a scalable and extensible set of core foundational governance
services that enables enterprises to effectively and efficiently meet their
compliance requirements within Hadoop and allows integration with the
complete enterprise data ecosystem
## Issues:
There are no issues requiring board attention at this time.
## Activity:
- replaced Scala based DSL with ANTLR based implementation
- added support for propagation of classifications via relationships
- enhanced classifications with ability to specify validity periods
- added Open Connector Framework (OCF)
- added Open Metadata Repository Services (OMRS) API, and IGC connector skeleton
- enhanced notifications to support V2 style data structures
- enhanced authorization model to support fine-grained authorization
- updated UI to render entity relationships
- working on migration of data in Atlas 0.8.x (Titan graph DB) to Atlas 1.0 (JanusGraph)
- released 0.8.2 and 1.0.0-alpha versions
- planning to release 1.0.0 by end of April 2018
## Health report:
- 5 new contributors added in last 3 months: Bosco Durai, Mark Ottesen, Pierre Padovani, Shrinivas Kane, Vishal Suvagia
## PMC changes:
- Currently 33 PMC members
- No new PMC members added in last 3 months
- Last PMC member addition was on 6/21/2017
## Committer base changes:
- Currently 37 committers
- 1 new committer in last 3 months, Graham Wallis added on 1/9/2018
- Last addition to committer role was on 1/9/2018
## Releases:
1.0.0 plan to release by 04/30/2018
0.8.2 was released on 02/05/2018
1.0.0-alpha was released on 01/25/2018
0.8.1 was released on 08/29/2017
0.8-incubating was released on 03/16/2017
0.7.1-incubating was released on 01/26/2017
0.7-incubating was released on 07/09/2016
0.6-incubating was released on 12/31/2015
0.5-incubating was released on 07/11/2015
-----------------------------------------
Attachment E: Report from the Apache Aurora Project [Jake Farrell]
Apache Aurora is a stateless and fault tolerant service scheduler used to
schedule jobs onto Apache Mesos such as long-running services, cron jobs,
and one off tasks.
Project Status
---------
The Apache Aurora community has welcomed a new committer, Jordan Ly, and a new
PMC member, Renan DelValle, to the project since our last report. We have released
Apache Aurora 0.19.1 and have started progress on our next 0.20.0 release candidate
to resolve conflicts in our slow query log threshold, update dependencies to
latest versions, and address a number of bugs.
Community
---
Latest Additions:
* Committer addition: Jordan Ly, 1.22.2018
* PMC addition: Renan DelValle, 1.28.2018
Issue backlog status since last report:
* Created: 18
* Resolved: 10
Mailing list activity since last report:
* @dev 158 messages
* @user 64 messages
* @reviews 395 messages
Releases
---
Last release:
* Apache Aurora 0.19.1 released 2.10.2018
-----------------------------------------
Attachment F: Report from the Apache Axis Project [Robert Lazarski]
# Apache Axis2 Board Report, March 2018
## Description
The Apache Axis project is responsible for the creation and maintenance of
software related to the Axis Web Services frameworks and subsidiary
components (both Java and C).
## Issues
There are no issues requiring board attention at this time.
## Activity
- Axis2 Java 1.7.7 (stable)
- Maintenance only.
- Axis2 Java 1.8 (development)
- Axis2 C 1.7 (development)
## Health report:
We have enough PMC to cut releases. Axis2 is a mature project, but still actively maintained. We continue to receive patches from various new users/contributors.
Axis2 Java put out several releases in 2017. Lately the focus has been responding to mailing list questions and Jira issues concerning end users automated
penetration testing by various 3rd party tools.
Several email threads occurred with security@apache.org this past 30 days concerning Axis2 Java and also Axis Java 1.x (last release was 2006). Jira issues have been created (AXIS2-5910 , AXIS2-5911) , emails have been sent to the original sender, and internal discussions are in progress.
Axis 1.x is likely to have a new release after all. RHEL 6 and 7 distribute it so its widely a problem at our day jobs. There are numerous security issues - several already fixed by community submitted patches and in SVN. An additional challenge for a release will be the migration off of the unsupported httpclient 3.x libs, to httpclient4.
Axis2 C added a new committer this past December 2017, and so far that is helping the project pick up speed. Possibly the Java team that knows C (myself for example) , could help get a release in motion. The Java team needs to get past the security issues first, then revisit how we can help the C team.
## PMC/Committer changes:
- Currently 63 PMC/Commiters members.
- No new committers were added in the last 30 days, last committer added was Bill Blough on December 7th 2017.
## Releases:
- Axis 2/Java 1.7.7 was released on November 22, 2017.
- Axis 2/C 1.6 was released on April 20, 2009.
- Axis 1.4 was last released in 2006.
## JIRA Activity
- 4 JIRA tickets created in the last month.
- 0 JIRA tickets closed/resolved in the last month.
-----------------------------------------
Attachment G: Report from the Apache Bahir Project [Luciano Resende]
-----------------------------------------
Attachment H: 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 is now in its second year as a top-level project, and the
community continues to grow modestly.
In this quarter, the main technical focus continues to be on the portability
framework, and its adoption across all components of the project, which would,
among other benefits, extend the Python and Go SDKs to all Beam runners. A
sizeable portion of the community is working on this effort.
As usual, the project kept interconnecting additional execution engines and
data storage/messaging systems, and serves as a glue in the ecosystem. On the
execution side, runners for JStorm, Apache Hadoop MapReduce, Apache Samza and
Apache Tez are being prototyped in feature branches, but without too much
recent activity. On the IO connector side, the healthy growth continues, with
new connectors being contributed or improved month-over-month.
Seznam.cz decided to donate the Euphoria API to Apache Beam. Also, an SGA for
Google’s previous donation of the Go SDK is still pending. Both IP clearances
should complete by the next report.
Recent major community decisions include:
- Dropping Java 7 support, and requiring users to upgrade to Java 8.
- Dropping Apache Spark 1.6 support, and requiring users to upgrade to a Spark
2.x cluster.
- Completely switching the build system to Gradle.
In this quarter, the community published two blog posts, one as a look-back at
2017 and one about the most recent release. Beam was featured at Strata Data
Conference San Jose 2017. Additionally, Google hosted a day-long Beam Summit
with solid participation.
Going forward, the main focus should be on the community growth, particularly
on the user side using non-proprietary engines. On the technical side, the
next major milestone is the completion of the portability framework across all
components of the project.
## Health report:
The community continues to grow steadily, as follows:
- Lifetime unique contributors grew to 245, with 30 new first-time
contributors.
- Increased mailing list subscriber/activity.
- Increased JIRA activity.
- Contribution of new components into the project by external entities.
- Continued release cadence.
The overall health is solid, improving from a recent low, and is benefited by
addition of new community members with foundation membership and/or experience
in other projects.
## PMC changes:
Currently 18 PMC members. No new members have been added since the last
report. Last PMC addition was on Wed Nov 08 2017. We are watching several
potential candidates.
## Committer base changes:
Currently 31 committers. No new members have been added since the last report.
Last committer addition was on Wed Nov 08 2017.
There are clear candidates, probably five or so. I’m confident the PMC will
address this very quickly.
## Releases:
Since the last report, Apache Beam has published one release:
- 2.3.0 was released on Thu Feb 15 2018.
Version 2.0.0 was the first release that comes with API stability guarantees.
Going forward, we expect to publish a release every 2 months.
## Mailing list activity:
Mailing list subscriptions and activity continues to increase modestly. It is
worth noting that we saw an increase in frequency and depth of mailing list
discussions, as well as better participation and diversity of opinion compared
to last year.
- dev@beam.apache.org
- 501 subscribers (up 28 in the last 3 months).
- 1595 emails sent to list (1452 in previous quarter).
- user@beam.apache.org
- 530 subscribers (up 36 in the last 3 months).
- 503 emails sent to list (456 in previous quarter).
## JIRA activity:
Whereas JIRA activity was going down for a few quarters, it is great to report
that we’ve turned the trend back upwards.
- 507 JIRA tickets created in the last 3 months (449 in the previous quarter).
- 324 JIRA tickets closed/resolved in the last 3 months (171 in the previous
quarter).
-----------------------------------------
Attachment I: Report from the Apache Bigtop Project [Evans Ye]
## Description:
Apache Bigtop is a software related to a system for integration, packaging,
deployment and validation of a big data management software distribution based
on Apache Hadoop.
## Issues:
In reply to Board's comment on last report: We had to remove Kafka artifacts
because they violate ASF's policy to ban Facebook BSD+Patents license. The
PMC had a discussion in [1]. There's also a Legal Jira[2] linked with it.
## Activity:
* The BoF at FOSDOM 2018 hosted by Olaf brought back a discussion to the
community that Bigtop dev is slowing down. The community is reaching
out to ODPi[3] for comments.
* The community is mainly fixing issues after bumping up versions of supported
Linux distros [4].
## PMC changes:
Last PMC addition was Kevin Monroe on Mon Nov 27 2017 Currently 26
PMC members.
## Committer base changes:
Last committer addition was Jun He on Fri Feb 23 2018 Currently 37
committers.
## Releases:
Last release was 1.2.1 on Sun Nov 12 2017
## Links
[1] https://s.apache.org/BEg1
[2] https://issues.apache.org/jira/browse/LEGAL-322
[3] https://www.odpi.org
[4] https://ci.bigtop.apache.org/view/Packages/job/Bigtop-trunk-packages
-----------------------------------------
Attachment J: Report from the Apache Bloodhound Project [Gary Martin]
Project Description
===================
Apache Bloodhound is a software development collaboration tool, including
issue tracking, wiki and repository browsing
Issues
======
The project remains in a low activity mode although there have been
continuing discussions. Good progress has been made on infrastructure
related issues. There have also been recent discussions on a new core
component as a means to migrate away from using Trac as a backend.
See further information below.
Releases
========
There have been no releases over the last three months. The last release
was towards the end of 2014:
* apache-bloodhound-0.8 (11th December 2014)
PMC/Committer Changes
=====================
There are currently 14 PMC members on the project. The last changes were
in April 2017.
The last new committers were added in May 2014.
The last addition to the PMC was in January 2017 (dammina)
Ryan Ollos resigned from the PMC in April 2017.
Community & Development
=======================
The main progress since the last report has been an effort by John
Chambers to restore issue tracking to the project. Now this work has been
completed to a reasonable point. The linking to source control for repo
browsing has been changed to use the git repo instead of the main
subversion repository. This has the benefit that we do not need to rely
on continuing maintenance of some kind of local mirroring of an svn repo
which did not prove to be a robust solution before. One downside is that
old links to patchsets via their revision number are not expected to
work and we do not envisage using up any effort to fix this automatically.
There is a continuing need to raise activity in other areas. Discussions
up to the previous report gave some confidence that there was a community
with an interest in moving the project on and that they were willing to
consider the migration away from Trac to be viable. Since then, a further
proposal has been made to create a core project based on Django to
experiment with the basic data model for issue tracking. This resulted in
a moderate response but this has been seen by the project chair as excuse
enough to go ahead with the experiment.
Along the lines of suggestions in the last report, we will take the
opportunity to look into the use of git for source control. The ability of
our issue tracker to browse to such a git repo with relative ease makes
splitting new work out to a new repository straight forward. Opinions of
the community are currently being sought on this matter. This choice does
not block progress.
As expressed in the previous month, with some progress still in evidence
the PMC wish to repeat deferral of the proposal to move Apache Bloodhound
to the Attic for another three months. The PMC is aware that it will need
to continue to engage with the community for determining direction and
attempting to recognise contributors as potential PMC members at the
earliest opportunity.
-----------------------------------------
Attachment K: Report from the Apache BVal Project [Matthew Jason Benson]
## Apache BVal Report March 2018 ##
- The Apache BVal project implements the Java EE Bean Validation
specification(s) and related extensions, and became a top-level project of
the foundation on February 15, 2012.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- The Apache BVal project has taken the task of implementing Java Bean
Validation 2.0 as an opportunity for a major overhaul of the underlying
structure of the codebase. This is more or less complete and the team is
currently focused on meeting the requirements of the technology
compatibility kit (TCK) for certification as a compliant implementation
of the latest specification.
## Health report:
- We retain a small core (or corps, even) of developers with the desire to
keep this project afloat.
## PMC changes:
- Currently 13 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Romain Manni-Bucau on Mon Nov 18 2013
## Committer base changes:
- Currently 14 committers.
- No new changes to the committer base since last report.
## Releases:
- Last release was 1.1.2 on Wed Nov 02 2016
## Mailing list activity:
- dev@bval.apache.org:
- 46 subscribers (up 0 in the last 3 months):
- 11 emails sent to list (19 in previous quarter)
- user@bval.apache.org:
- 54 subscribers (up 0 in the last 3 months):
- 2 emails sent to list (4 in previous quarter)
-----------------------------------------
Attachment L: Report from the Apache Camel Project [Christian Mueller]
-----------------------------------------
Attachment M: Report from the Apache Cayenne Project [Michael Ray Gentry]
# Apache Cayenne Board Report, March 2018
## Description
Apache Cayenne is a Java database persistence framework. It takes a
distinct approach to object persistence and provides an ORM runtime,
remote persistence services, and a cross-platform GUI mapping/modeling
tool.
## Issues
There are no issues requiring board attention at this time.
## Activity
An overhauled website and core development on our future releases
marked the main activity this quarter.
- Cayenne 3.1.2 (stable)
- Maintenance only. Cayenne 3.1.2 is the current stable product
line.
- Cayenne 4.0 (development)
- The API is frozen, barring any major issues, and development
efforts are only for bug fixes and documentation leading up to
the final release of Cayenne 4.0.
- Cayenne 4.1 (development)
- Work continues on Cayenne 4.1 even as 4.0 is being finalized.
- Website
- An updated website that is cleaner, more modern, and
mobile-friendly was launched this quarter.
## Health Report
Cayenne is healthy. Development activity is stable and the website
was overhauled. We have a stable user and developer community.
## PMC Changes
- Currently 9 PMC members.
- No new PMC members added in the last 3 months.
- Last PMC addition was Nikita Timofeev on Sun Jun 25 2017.
## Committer Base Changes
- Currently 22 committers.
- No new committers added in the last 3 months.
- Last committer addition was Hugi Thordarson at Mon Jun 19 2017.
## Releases
- Cayenne 3.1.2 on Wed Nov 22 2017.
- Cayenne 4.0.B2 on Sat Oct 7 2017.
- Cayenne 4.1.M1 on Sat Oct 14 2017.
## Mailing List Activity
- dev@cayenne.apache.org:
- 131 subscribers (up 0 in the last 3 months).
- 37 emails sent to list (96 in previous quarter).
- user@cayenne.apache.org:
- 248 subscribers (down -2 in the last 3 months).
- 89 emails sent to list (122 in previous quarter).
## JIRA Activity
- 25 JIRA tickets created in the last 3 months.
- 27 JIRA tickets closed/resolved in the last 3 months.
-----------------------------------------
Attachment N: Report from the Apache Chemistry Project [Florian Müller]
## Description:
Apache Chemistry is an effort to provide an implementation of the CMIS
(Content Management Interoperability Services) specification in Java,
Python, PHP, .NET, Objective-C, and JavaScript (and possibly other
languages).
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- There was basically no activity in the last three months.
## Health report:
- We have a mature code base. No major development is expected.
## PMC changes:
- Currently 36 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Laurent Mignon on Sat Sep 23 2017
## Committer base changes:
- Currently 38 committers.
- No new committers added in the last 3 months
- Last committer addition was Laurent Mignon at Wed Sep 20 2017
## Releases:
- Last release was cmislib 0.6.0 on Thu Aug 31 2017
## Mailing list activity:
- dev@chemistry.apache.org:
- 172 subscribers (down -2 in the last 3 months):
- 60 emails sent to list (138 in previous quarter)
## JIRA activity:
- 5 JIRA tickets created in the last 3 months
- 5 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment O: Report from the Apache CloudStack Project [Wido den Hollander]
## Description:
Apache CloudStack (ACS) is an IaaS (Infrastructure as a Service) cloud
orchestration platform. ACS manages many types of hypervisors, storage
and networking devices.
## Issues:
there are no issues requiring board attention at this time
## Activity:
- Mike Tutkowski (mtutkowski) was elected as the new VP of the CloudStack project
The resolution has been filed at the board
## Health report:
- Version 4.11 was released recently and the project is now working towards
the 4.12 release. All seems healthy
## PMC changes:
- Currently 47 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Syed Ahmed on Mon Oct 09 2017
## Committer base changes:
- Currently 116 committers.
- No new committers added in the last 3 months
## Releases:
- Release 4.11.0 on Mon Feb 12 2018
- Release 4.10.0 on Fri Sep 1 2017
- Release 4.9.3.0 on Tue Sep 12 2017
## Mailing list activity:
- users@cloudstack.apache.org:
- 1110 subscribers (up 8 in the last 3 months):
- 700 emails sent to list (630 in previous quarter)
- dev@cloudstack.apache.org:
- 722 subscribers (down -1 in the last 3 months):
- 728 emails sent to list (483 in previous quarter)
- announce@cloudstack.apache.org:
- 524 subscribers (up 9 in the last 3 months):
- 0 emails sent to list (0 in previous quarter)
- issues@cloudstack.apache.org:
- 236 subscribers (up 1 in the last 3 months):
- 5349 emails sent to list (2034 in previous quarter)
- marketing@cloudstack.apache.org:
- 238 subscribers (up 3 in the last 3 months):
- 9 emails sent to list (11 in previous quarter)
- press@cloudstack.apache.org:
- 13 subscribers (up 0 in the last 3 months)
## JIRA activity:
- 133 JIRA tickets created in the last 3 months
- 168 JIRA tickets closed/resolved in the last 3 months
## Social Media
At 12th March 2018:
- The CloudStack Twitter (@cloudstack) account has 34,800 followers (+"00 since last report)
- The Github mirror of CloudStack repository has 548 stars (+37) and 608 forks (+2)
-----------------------------------------
Attachment P: Report from the Apache Commons Project [Gary D. Gregory]
## Description:
- The Apache Commons project focuses on all aspects of reusable Java components.
- The Apache Commons components are widely used in many projects, both within
Apache and without. Any ASF committer can commit to Apache Commons.
- The last report was for the meeting of December 20, 2017.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- The project is active with nine (9) releases this reporting period.
## Health report:
- Most components in Commons are mature, but are still actively maintained
(9 releases). The dev list is active. JIRA is active. Speed of responses
to users is reasonable in most cases. We have no new PMC members, no new
committers, and Commons is still open to any Apache Committer.
- We have been addressing a backlog of messages from security@a.o.
- Previous growing pains toward Commons Math 4 might see resolution with a
plan toward splitting off Commons Math into new components like Commons Numbers.
## PMC changes:
- Currently 38 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Rob Tompkins on Fri Jun 30 2017
## Committer base changes:
- Currently 146 committers.
- No new committers added in the last 3 months
- Last committer addition was Sergio Fernández at Sat Nov 04 2017
## Releases:
- COMPRESS-1.16 was released on Sun Feb 04 2018
- COMPRESS-1.16.1 was released on Fri Feb 09 2018
- DBCP-2.2.0 was released on Sun Dec 24 2017
- PARENT-43 was released on Fri Jan 05 2018
- PARENT-44 was released on Sat Mar 10 2018
- PARENT-45 was released on Wed Mar 14 2018
- RDF-0.5.0 was released on Fri Dec 22 2017
- RELEASEPLUGIN-1.1 was released on Sun Mar 04 2018
- release-plugin-1.0 was released on Tue Jan 16 2018
## JIRA activity:
- 216 JIRA tickets created in the last 3 months
- 165 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment Q: Report from the Apache Cordova Project [Shazron Abdullah]
## Description:
A platform for building native mobile applications using HTML, CSS and
JavaScript.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
We had four platform releases - two patch release for Browser (5.0.2, 5.0.3),
one minor release for Android (7.1.0) and one major release for Windows
(6.0.0) The Android and Browser releases were just small bug fixes. The
Windows release now suppoorts the latest version of visual studio and does
Windows 10 builds by default.
We had many plugins gets released. Many of the releases needed second releases
due to issues with installing from npm due to us forgetting to update some
fields.
Cordova-cli@8.0.0 was also released. This was accompanied by releases in other
tools that the CLI is composed of. We took the release of this major version
to drop deprecated code.
## Health report:
Our status dashboard at http://status.cordova.io is mostly all green.
We still have a huge backlog of GitHub Pull Request activity, again, same as
last quarter. Will keep chipping away.
## PMC changes:
- Currently 89 PMC members.
- Chris Brody was added to the PMC on Tue Feb 13 2018
## Committer base changes:
- Currently 92 committers.
- Chris Brody was added as a committer on Mon Feb 12 2018
## Releases:
- cordova-android@7.1.0 was released on Fri Feb 23 2018
- cordova-browser@5.0.2 was released on Tue Dec 19 2017
- cordova-browser@5.0.3 was released on Wed Dec 27 2017
- cordova-cli@8.0.0 was released on Mon Dec 18 2017
- cordova-common@2.2.1 was released on Mon Dec 18 2017
- cordova-create@1.1.2 was released on Mon Dec 18 2017
- cordova-fetch@1.3.0 was released on Mon Dec 18 2017
- cordova-lib@8.0.0 was released on Mon Dec 18 2017
- cordova-plugin-battery-status@2.0.0 was released on Tue Dec 19 2017
- cordova-plugin-camera@4.0.0 was released on Tue Dec 19 2017
- cordova-plugin-camera@4.0.2 was released on Sun Jan 28 2018
- cordova-plugin-contacts@3.0.1 was released on Tue Dec 19 2017
- cordova-plugin-device@2.0.0 was released on Tue Dec 19 2017
- cordova-plugin-dialogs@2.0.0 was released on Tue Dec 19 2017
- cordova-plugin-file-transfer@1.7.1 was released on Sun Jan 28 2018
- cordova-plugin-inappbrowser@2.0.2 was released on Sun Jan 28 2018
- cordova-plugin-media@5.0.2 was released on Sun Jan 28 2018
- cordova-plugin-splashscreen@5.0.2 was released on Sun Jan 28 2018
- cordova-plugin-file@6.0.0 was released on Tue Dec 19 2017
- cordova-plugin-geolocation@4.0.0 was released on Tue Dec 19 2017
- cordova-plugin-globalization@1.0.9 was released on Tue Dec 19 2017
- cordova-plugin-inappbrowser@2.0.0 was released on Tue Dec 19 2017
- cordova-plugin-media-capture@3.0.0 was released on Tue Dec 19 2017
- cordova-plugin-media@5.0.0 was released on Tue Dec 19 2017
- cordova-plugin-network-information@2.0.0 was released on Tue Dec 19 2017
- cordova-plugin-screen-orientation@3.0.0 was released on Tue Dec 19 2017
- cordova-plugin-splashscreen@5.0.0 was released on Tue Dec 19 2017
- cordova-plugin-statusbar@2.4.0 was released on Tue Dec 19 2017
- cordova-plugin-vibration@3.0.0 was released on Tue Dec 19 2017
- cordova-plugman@2.0.0 was released on Mon Dec 18 2017
- cordova-windows@6.0.0 was released on Thu Feb 22 2018
- cordova-plugin-vibration: 3.0.1 was released on Sat Dec 30 2017
- cordova-plugin-screen-orientation: 3.0.1 was released on Sat Dec 30 2017
- cordova-plugin-splashscreen: 5.0.1 was released on Sat Dec 30 2017
- cordova-plugin-media: 5.0.1 was released on Sat Dec 30 2017
- cordova-plugin-media-capture: 3.0.1 was released on Sat Dec 30 2017
- cordova-plugin-network-information: 2.0.1 was released on Sat Dec 30 2017
- cordova-plugin-file: 6.0.1 was released on Sat Dec 30 2017
- cordova-plugin-geolocation: 4.0.1 was released on Sat Dec 30 2017
- cordova-plugin-device: 2.0.1 was released on Sat Dec 30 2017
- cordova-plugin-dialogs: 2.0.1 was released on Sat Dec 30 2017
- cordova-plugin-battery-status: 2.0.1 was released on Sat Dec 30 2017
- cordova-plugin-camera: 4.0.1 was released on Sat Dec 30 2017
- cordova-plugin-inappbrowser: 2.0.1 was released on Sat Dec 30 2017
- cordova-plugin-statusbar: 2.4.1
## JIRA activity:
- 303 JIRA tickets created in the last 3 months
- 246 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment R: Report from the Apache cTAKES Project [Pei Chen]
## Description:
Apache clinical Text Analysis and Knowledge Extraction System (cTAKES) is
an open-source natural language processing system for information extraction
from electronic medical record clinical free-text.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
- Committee continues to work on the future release (4.0.1)
- Committee continues to improve unit and regression tests.
- Committee continues to work on bug fixes and improvements documented in Jira
- Committee is actively working on updating the cTAKES Confluence
website for improved documentation
## Health report:
- The community continues to be moderately active.
- There are patches from various new users/contributors
recently. Three new committers were added within the last quarter.
## PMC changes:
- Currently 30 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Michelle Chen on Mon Feb 02 2015
## Committer base changes:
- Currently 38 committers.
- New commmitters:
- Alex Zbarcea was added as a committer on Fri Oct 20 2017
- Gandhi Rajan was added as a committer on Tue Nov 14 2017
- Matthew Vita was added as a committer on Mon Nov 13 2017
## Releases:
- Last release was 4.0.0 on Apr 27 2017
- 3.2.2 was released on May 30 2015
- 3.2.1 was released on Dec 10 2014
## Mailing list activity:
There was an increase in number of subscribers to the dev and user @
mailing lists.
- dev@ctakes.apache.org:
- 242 subscribers (up 8 in the last 3 months):
- 190 emails sent to list (441 in previous quarter)
- user@ctakes.apache.org:
- 241 subscribers (up 5 in the last 3 months):
- 124 emails sent to list (34 in previous quarter)
-----------------------------------------
Attachment S: Report from the Apache Curator Project [Jordan Zimmerman]
## Description:
- Apache Curator is a Java/JVM client library for Apache ZooKeeper, a
distributed coordination service. It includes a highlevel API framework and
utilities to make using Apache ZooKeeper much easier and more reliable. It
also includes recipes for common use cases and extensions such as service
discovery and a Java 8 asynchronous DSL.
## Issues:
- there are no issues requiring board attention at this time
## Activity:
- No important activity to report. We are responding to bug reports,
questions as normal and we have fairly regular releases.
## Health report:
- As we continue to mention, the project appears to be slowing down just as
ZooKeeper seems to be slowing down. This is probably healthy for a project
of Curator's age.
- Apache Curator would benefit from one or more additional active committers
but it's difficult to find these people.
## PMC changes:
- Currently 12 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Fangmin Lv on Mon Mar 27 2017
## Committer base changes:
- Currently 12 committers.
- No new committers added in the last 3 months
- Last committer addition was Fangmin Lv at Tue Mar 28 2017
## Releases:
- Apache Curator 4.0.1 was released on Sat Feb 10 2018
## Mailing list activity:
- dev@curator.apache.org:
- 51 subscribers (up 0 in the last 3 months):
- 258 emails sent to list (144 in previous quarter)
- user@curator.apache.org:
- 160 subscribers (up 1 in the last 3 months):
- 18 emails sent to list (10 in previous quarter)
## JIRA activity:
- 13 JIRA tickets created in the last 3 months
- 6 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment T: Report from the Apache DataFu Project [Matthew Hayes]
## Description:
- DataFu provides a collection of Hadoop MapReduce jobs and Pig UDFs 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.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- Much of the recent activity has focused on tasks related to incubator
graduation.
- A Download page (http://datafu.apache.org/docs/download.html) was added
with clearer instructions for getting the most recent source release and
validating it.
- Infra set up the new domain for Apache DataFu: http://datafu.apache.org/
- There is some upcoming work on other post-graduation items, such as
updating the website to reflect being a TLP now, building artifacts without
"incubating" in the name, etc.
## Health report:
- A JIRA was filed from a new user. It was found to not be an issue.
- The last release was in January 2018 while still in incubation. Planning
to do a new release soon now that the project has graduated to TLP.
## PMC changes:
- Currently 11 PMC members.
- No new PMC members added in the last 3 months
## Committer base changes:
- Currently 18 committers.
- No changes (the PMC was established in the last 3 months)
## Releases:
- No releases so far since graduating to TLP.
- Last release during incubation was 1.3.3 on January 26th, 2018.
## JIRA activity:
- 10 JIRA tickets created in the last 3 months
- 11 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment U: Report from the Apache DRAT Project [Chris Mattmann]
## Description:
- Apache DRAT is a distributed, parallelized (Map Reduce) wrapper around
Apache RAT™ and other code auditing tools to allow it to complete on large
code repositories of multiple file types.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- Philipp Ottlinger was elected to the DRAT PMC and as a committer
- The new DRAT website is up and going! http://drat.apache.org thanks to
Nipurn, Shivika, Wayne, and Philipp for all the hard work
- there is increasing activity surrounding people trying to use DRAT with a
lot of comments and potential bugs and issues to fix in various
environments.
- Chris Mattmann registered for GSoC 2018 as a mentor and posted several
issues in the DRAT Github and tagged them with gsoc and gsoc2018 labels
- one of the issues https://github.com/apache/drat/issues/113 already has
interest
## Health report:
- Still want to turn our attention to getting a full ASF scan of DRAT over the
Github/Gitbox repositories for ASF projects as a start.
- GSOC 2018 will help with attracting more contributors (already doing so in
#113)
## PMC changes:
- Currently 11 PMC members.
- Philipp Ottlinger was added to the DRAT PMC and as a committer on
2018-02-27
## Committer base changes:
- Currently 11 committers.
- Philipp Ottlinger was added to the DRAT PMC and as a committer on
2018-02-27
## Releases:
- Working towards a 1.0 release still. Hopefully in the next quarter.
## Mailing list activity:
- Mailing list subscriptions remain stable. There hasn't been as much mail
sent (about half as much). I think folks just were focused on getting the
website going, and I think the next step of running DRAT over all the ASF
repos weekly will generate a lot of traffic. Also I think making a first
release will also do that. Finally GSOC 2018 will likely generate more
mailing list traffic as well.
- dev@drat.apache.org:
- 14 subscribers (up 0 in the last 3 months):
- 45 emails sent to list (82 in previous quarter)
- issues@drat.apache.org:
- 10 subscribers (up 0 in the last 3 months)
-----------------------------------------
Attachment V: 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:
- In recent months, seems more users started to try Apache Eagle 0.5.0
release version. And users also reported some issues with starting Eagle
with command line and other usability issues. Community has solved those
issues.
## Health report:
- We see some new users trying out Eagle and some of users can submit PR for
some fix, but seems we still need volunteers to do some small fixes quickly
to help community.
## PMC changes:
- Currently 16 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Deng Lingang on Mon May 08 2017
## Committer base changes:
- Currently 18 committers.
- No new committers added in the last 3 months
- Last committer addition was Jay Sen at Thu Mar 16 2017
## Releases:
- Last release was 0.5.0 on Sat Sep 09 2017
## Mailing list activity:
- dev@eagle.apache.org:
- 78 subscribers (up 2 in the last 3 months):
- 71 emails sent to list (36 in previous quarter)
- issues@eagle.apache.org:
- 19 subscribers (up 0 in the last 3 months):
- 204 emails sent to list (26 in previous quarter)
- user@eagle.apache.org:
- 56 subscribers (up 1 in the last 3 months):
- 22 emails sent to list (4 in previous quarter)
## JIRA activity:
- 16 JIRA tickets created in the last 3 months
- 17 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment W: Report from the Apache Falcon Project [Pallavi Rao]
ABOUT
Falcon is a data processing and management solution for Hadoop designed
for data motion, coordination of data pipelines, lifecycle management, and
data discovery. Falcon enables end consumers to quickly onboard their data and
its associated processing and management tasks on Hadoop clusters.
ISSUES
There are no issues that require board's attention at this time.
STATUS
Falcon 0.11 was released on 13th March 2018. The new release comes with
following new features:
1. User Extensions
2. Backlog metrics for Processes.
3. Spring shell for Falcon Client (alpha) The release also includes many
improvements and bug fixes. See release notes for details.
PMC CHANGES
- Currently 17 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Sowmya Ramesh on Mon Jun 06 2016
COMMITTER CHANGES
- Currently 25 committers.
- No new committers added in the last 3 months
- Last committer addition was Sandeep Samudrala at Thu Mar 09 2017
RELEASES
- Last release was 0.11 on Tue Mar 13 2018
MAILING LIST ACTIVITY
- dev@falcon.apache.org:
- 113 subscribers (up 0 in the last 3 months):
- 158 emails sent in the past 3 months (104 in the previous cycle)
JIRA ACTIVITY
- 17 JIRA tickets created in the last 3 months
- 13 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment X: Report from the Apache Felix Project [Karl Pauls]
## Description:
Apache Felix is a project aimed at implementing specifications from
the OSGi Alliance as well as implementing other supporting tools and
technologies aligned with OSGi technology.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- Existing implementations have been improved/enhanced based on
community feedback.
- Finished IP clearance of the BAR file installer contribution from
Intel and added code to svn (release pending).
- Efforts to implement the upcoming OSGi R7 specifications still
on-going (mostly focusing on the framework atm).
- Released 5 components (mostly bug fixes and minor improvments).
## Health report:
- Overall the project is in good health (but not growing atm).
- Questions on the user list are answered, development concerns are
either discussed on the mailing list or directly in the JIRA issues.
- The project as well as the OSGi community in general is still in the
process of adapting to JPMS and its long term impact.
- We need to focus on adding a new pmc member and attracting new
committers (we started a discussion on private@ to see if we have
any current candidates). However, we had no issues voting on
releases and JIRA issues are generally addressed promptly.
## PMC changes:
- Currently 24 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Jean-Baptiste Onofré on Fri Jul 15 2016
## Committer base changes:
- Currently 61 committers.
- No new committers added in the last 3 months
- Last committer addition was Neil Bartlett at Thu Feb 09 2017
## Releases:
- maven-bundle-plugin-3.4.0 was released on Mon Dec 18 2017
- maven-bundle-plugin-3.5.0 was released on Tue Jan 09 2018
- org.apache.felix.resolver-1.16.0 was released on Tue Mar 13
2018
- org.apache.felix.scr-2.0.14 was released on Mon Dec 18 2017
- org.apache.felix.webconsole.plugins.memoryusage-1.0.8 was
released on Wed Feb 28 2018
## Mailing list activity:
- users@felix.apache.org:
- 567 subscribers (down -4 in the last 3 months):
- 62 emails sent to list (67 in previous quarter)
- dev@felix.apache.org:
- 328 subscribers (up 2 in the last 3 months):
- 354 emails sent to list (600 in previous quarter)
## JIRA activity:
- 41 JIRA tickets created in the last 3 months
- 31 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment Y: Report from the Apache Flex Project [Tom Chiverton]
Apache Flex is an application framework for easily building Flash-based
applications for mobile devices, the browser and desktop.
RELEASES
No new releases in the last quarter.
Older Releases:
-Apache Flex SDK Installer 3.3 was released on 2017-11-16
-Apache Flex SDK 4.16.1 was released on 2017-11-22
-Apache Flex BlazeDS 4.7.3 was released on 3/31/17.
-Apache Flex Tour De Flex Component Explorer 1.2 was released on 11/28/14.
-Apache Flex Tool API 1.0.0 was released on 11/20/14
-Apache Flex Squiggly 1.1 was released on 10/26/14
ACTIVITY
There are still questions being asked on users@ and bugs being filed in JIRA.
Activity on dev@ continues at it's reduced level since the Royal
(https://royale.apache.org/) project split at the end of 2017.
There are issues downloading a dependency from SourceForge. It is an MPL
binary from Adobe.
A migration to SHA1 checksums (per the updated Apache policy) is being
discussed.
COMMUNITY
Flex is using the Wiki to draft Board reports successfully.
TRADEMARKS
Nothing noted.
SECURITY
Nothing to report.
-----------------------------------------
Attachment Z: Report from the Apache Flink Project [Stephan Ewen]
DESCRIPTION
Apache Flink is a distributed data streaming system for batch and streaming
data analysis on top of a streaming dataflow engine. Flink's stack contains
functional batch and streaming analysis APIs in Java and Scala and libraries
for various use cases.
Flink interacts and integrates with several Apache projects in the broader
ecosystem of data storage and computing, such as Apache Beam,
Hadoop, Mesos, Kafka, HBase, Cassandra, and various others.
ISSUES
- There are no issues that require board attention.
STATUS AND ACTIVITY
- The Flink community is in the final phase of the 1.5 release, with the
release branch being forked and final tests and bug fixes happening.
- The 1.5 release marks a major rework of Flink, to make its design more
natural for idiomatic use with containers (specifically Kubernetes) and more
dynamic resource environments, but at the same time retain the current
integration with Yarn, Mesos, and standalone setups.
Aside from that, the release improves latency, checkpoints, recovery time,
and extends streaming SQL and the DataStream API, among other things.
- The Flink Forward San Francisco conference will happen in three weeks.
Flink committers were offered a free pass.
The program can be found under https://sf-2018.flink-forward.org/conference/
- Concerning the note in the previous board report, the Huawei
CloudStream website now uses Apache Flink, rather than only
Flink (accessed March 15th)
https://www.huaweicloud.com/en-us/product/cs.html
COMMUNITY
No new PMC members were added since the last report.
The newest PMC member is Chesnay Schepler, joined on July 26th, 2017
Committers added since the last board report:
- Eron Wright was added as a committer on January 17th, 2018
Flink currently has 35 committers and 19 PMC members.
RELEASES
The following releases were made since the last board report:
- 1.4.1 was released on February 15th, 2018
- 1.4.2 was released on March 8th, 2018
- 1.3.3 was released on March 15th, 2018
- shaded-3.0 was released on February 28th, 2018
ACTIVITY ON JIRA / MAILING LISTS
The Flink community was very proud to be in the top 10 active mailing lists in Apache :-)
user@f.a.o (1817 mails/quarter) and dev@f.a.o (1154 mails/quarter)
As the community pushes towards the 1.5 release, JIRA continues
to be very active, with 688 JIRA tickets created and 672 JIRA tickets
resolved over last 3 months.
-----------------------------------------
Attachment AA: Report from the Apache Giraph Project [Avery Ching]
-----------------------------------------
Attachment AB: Report from the Apache Guacamole Project [Mike Jumper]
## Description:
- Apache Guacamole is a clientless remote desktop gateway which supports
standard protocols like VNC, RDP, and SSH. We call it "clientless" because
no plugins or client software are required. Once Guacamole is installed on
a server, all you need to access your desktops is a web browser.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- Several edge-case fixes related to keyboard behavior on specific platforms.
- Recent attention and development on allowing redirected device names to be
configurable.
- Contributions of enhancements to guacenc's featureset from the community
look promising.
## Health report:
- The project is still operating in a healthy manner. No significant changes
in the last month. Development and community involvement continue to be
active.
## PMC changes:
- Currently 9 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Carl Harris on Sun Nov 19 2017
## Committer base changes:
- Currently 10 committers.
- No new committers added in the last 3 months
- Last committer addition was Carl Harris at Thu Nov 16 2017
## Releases:
- 0.9.14 was released on Wed Jan 17 2018
## Mailing list activity:
- dev@guacamole.apache.org:
- 71 subscribers (up 4 in the last 3 months):
- 660 emails sent to list (570 in previous quarter)
- user@guacamole.apache.org:
- 281 subscribers (up 2 in the last 3 months):
- 655 emails sent to list (696 in previous quarter)
## JIRA activity:
- 62 JIRA tickets created in the last 3 months
- 86 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AC: Report from the Apache Gump Project [Stefan Bodewig]
Apache Gump is a cross-project continuous integration server. Gump's
intention isn't so much to be a CI server but rather a vehicle that
makes people look beyond their project's boundaries and helps the
projects to collaborate.
Gump is written in Python and supports several build tools and version
control systems. The Apache installation of Gump builds ASF as well
as non-ASF projects and their dependencies. It started in the Java
part of the foundation but also builds projects like APR, HTTPd and
XMLUnit.NET.
== Summary ==
Two of the projects who still get notified by Gump build failures
indicated they still get useful results out of Gump, two others
indicated they no longer want to receive notifications.
No other changes compared to the last quarter.
== Releases ==
Gump has never done any releases. One reason for this is that the ASF
installations of Gump work on the latest code base almost all of the
time following its "integrate everything continuously" philosophy.
== Activity ==
The Apache POI project opted out of Gump.
We asked the five remaining projects who still would receive
notifications of build failures whether Gump was still useful for
them. The Apache Tomcat and Apache Forrest projects indicated they
really take value from it, while the XML Graphics Commons project told
us they'd no longer need Gump (and we've disabled notifications for
them).
== Changes to the Roster ==
All ASF committers have write access to the metadata that configure
the ASF installations.
The last changes to the PMC have seen Konstantin Kolinko and Mark
Thomas join in November 2014.
-----------------------------------------
Attachment AD: Report from the Apache Hama Project [Chia-Hung Lin]
-----------------------------------------
Attachment AE: Report from the Apache Helix Project [Kishore G]
## Description:
- A cluster management framework for partitioned and replicated distributed
resources
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- New major release 0.8.0 is out.
- 29 pull requests merged in last 3 months.
## Health report:
- New major release 0.8 is officially out in Feb 2018.
- There is a regular level of activities on commits, pull requests and
releases.
- The dev@ and user@ list traffic is increasing after new release out.
- Many of current committers are not quite active in terms of daily
developments and pull request review, need to look for potential new
committers from the community.
## PMC changes:
- Currently 18 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Junkai Xue on Mon Jul 03 2017
## Committer base changes:
- Currently 18 committers.
- No new committers added in the last 3 months
- Last committer addition was Junkai Xue at Mon Apr 03 2017
## Releases:
- Last release was 0.6.9 on Sat Oct 14 2017
## Mailing list activity:
- dev@helix.apache.org:
- 70 subscribers (up 3 in the last 3 months):
- 249 emails sent to list (108 in previous quarter)
- user@helix.apache.org:
- 97 subscribers (up 0 in the last 3 months):
- 68 emails sent to list (11 in previous quarter)
## JIRA activity:
- 10 JIRA tickets created in the last 3 months
- 7 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AF: Report from the Apache Hive Project [Ashutosh Chauhan]
## Description:
- The Apache Hive (TM) data warehouse software facilitates querying and
managing large datasets residing in distributed storage.
## Issues:
- There are no issues requiring board attention at this time
## Activity:
- PMC received many security reports this quarter which are actively being
worked on.
- Multiple proposals to extend metastore functionality. Active dev activity
in standalone-metastore branch
- Sustained discussions and efforts to improve tests and test infra of
project.
- Master branch continues to receive continuous stream of bug fixes and new
features.
## PMC changes:
- Currently 42 PMC members.
- Naveen Gangam was added to the PMC on Thu Feb 22 2018
## Committer base changes:
- Currently 75 committers.
- New commmitters:
- Chris Drome was added as a committer on Mon Dec 18 2017
- Deepak Jaiswal was added as a committer on Thu Jan 04 2018
## Releases:
- Last release was 2.3.2 on Sun Nov 12 2017
## Health report:
- dev@ 883 subscribers (down -7 in the last 3 months)
- user@ 2263 subscribers (up 7 in the last 3 months):
- 685 JIRA tickets created in the last 3 months
- 483 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AG: Report from the Apache Incubator Project [John D. Ament]
Incubator PMC report for March 2018
The Apache Incubator is the entry path into the ASF for projects and
codebases wishing to become part of the Foundation's efforts.
There are currently 54 podlings under incubation. We added 1 new IPMC member, 3 new podlings and executed on 4 releases. The HTrace report indicates retirement in flight.
* Community
New IPMC members:
- Timothy Chen
People who left the IPMC:
* New Podlings
- Druid
- Dubbo
- Nemo
* Podlings that failed to report, expected next month
- Gearpump
- Hivemall
- Milagro
- Pony Mail
- Quickstep
- SINGA
* Graduations
The board has motions for the following:
- Freemarker
* Releases
The following releases entered distribution during the month of
February:
- 2018-02-05 Apache Livy 0.5.0
- 2018-02-15 Apache Netbeans 9.0 beta
- 2018-02-19 Apache PonyMail 0.10.0
- 2018-02-19 Apache MXNet 1.1.0
* IP Clearance
* Legal / Trademarks
- See Daffodil's report related to open legal questions.
- See SkyWalking's report for open questions around optional modules under discussion on legal lists.
* Infrastructure
* Miscellaneous
* Credits
----------------------------------------------------------------------
Table of Contents
AriaTosca
Crail
Druid
Dubbo
ECharts
Griffin
HTrace
Myriad
Nemo
Omid
OpenWhisk
PLC4X
Pulsar
Quickstep
SAMOA
ServiceComb
SkyWalking
Slider
Spot
Superset
Taverna
Tephra
----------------------------------------------------------------------
--------------------
AriaTosca
ARIA TOSCA project offers an easily consumable Software Development Kit(SDK)
and a Command Line Interface(CLI) to implement TOSCA(Topology and
Orchestration Specification of Cloud Applications) based solutions.
AriaTosca has been incubating since 2016-08-27.
Three most important issues to address in the move towards graduation:
1. Grow the community and enroll new committers.
2. Have (more) frequent Release cycles to be compliant with the Apache Way.
3. Grow the project’s contributions from existing community of contributors
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?
1. The project issued its third release (0.2.0) as far as the code is
concerned. Some considerable functionality has been added since the last
release in addition to a growth in diversity of contributions.
How has the community developed since the last report?
* All project communication now takes place on either the mailing list or
ASF's Slack, and is open for everybody. We have worked hard to make this
the normal operating mode of the community. There have been some hiccups,
but in general the majority of discourse has taken place on the list.
* Increased chatter on the mailing list including new subscribers who ask
questions, make suggestions and are likely to become contributors
themselves in the near future.
* Weekly grooming meetings are now attended by the majority of the community.
This is not only a forum to review the weekly work items list, but also as a
place for open discussion about issues, questions as well as for the
community to get to better know each other.
How has the community developed since the last report?
Over the last 3 months we have seen a significant increase in contributions as
well as a few new contributors, particularly from the Ericsson contingent.
How has the project developed since the last report?
ARIA now has two new patches considerably extend the parser's
plugin/extensions
Website and documentation improvements for usability and to enhance new user
Usability in terms of “getting started” instructions
9 JIRA issues have been resolved since the last report. Note that the
repository was locked for several weeks during this period due to release
process issues and learning curve.
We will be doing another release during this quarter.
The community has begun to undertake updating AriaTosca to support the Tosca
1.1 Simple YAML profile.
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup
[ ] Working towards first release
[X] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
The 0.2.0 release was issued on January 16, 2018. The .3 release is planned
for this quarter.
When were the last committers or PPMC members elected?
Tom Nadeau was added to the PMC/committers on 11/28/2017
Signed-off-by:
[X](ariatosca) Suneel Marthi
Comments: Podling needs to focus on growing the community and a more frequent release cadence.
[X](ariatosca) John D. Ament
Comments: It's a small group. On list communication is still a struggle.
[X](ariatosca) Jakob Homan
Comments: Small but growing slowly and heading in the right direction.
--------------------
Crail
Crail is a storage platform for sharing performance critical
data in distributed data processing jobs at very high speed.
Crail has been incubating since 2017-11-01.
Three most important issues to address in the move towards graduation:
1 Community building
2. Improve project visibility
3. Create a 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?
* We got one new active committer.
After moving the code base under apache/incubator-crail,
we are re-gaining frequency on downloads and followers
* To advertise the project, we are preparing for the
SF Spark Summit presentation on Crail.
We got a presentation on Crail's non-volatile data
management accepted at OpenFabrics workshop in April.
How has the project developed since the last report?
* Podling name search done and approved by Legal.
* Applied fixes resolving two major bugs within Crail code.
* New project front end website.
How would you assess the podling's maturity?
[X] Initial setup
[X] Working towards first release
[X] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
N/A
When were the last committers or PPMC members elected?
2017-11-01 (entering incubation)
Signed-off-by:
[x] (crail) Julian Hyde
Comments: Good progress on the "admin" aspects of incubation,
and dev list is showing good activity.
[ ] (crail) Luciano Resende
Comments:
[ ] (crail) Raphael Bircher
Comments:
--------------------
Daffodil
Apache Daffodil is an implementation of the Data Format Description Language
(DFDL) used to convert between fixed format data and XML/JSON.
Daffodil has been incubating since 2017-08-27.
Three most important issues to address in the move towards graduation:
1. Complete first Apache release as an Incubator
2. Broaden base of contributors and build the community (e.g. work with
other Apache projects where Daffodil could provide extra functionality)
3. Improve documentation on setting up a development environment to ease the
addition of new developers
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?
- Outstanding legal issue regarding Open Grid Forum document inclusion in
Daffodil (LEGAL-369)
How has the community developed since the last report?
- No new committers. However, we have had activity from a couple outside users
on the mailing lists asking about Daffodil capabilities/usage
How has the project developed since the last report?
- All SGA/CLAs have been submitted (from Tresys, IBM, and NCSA), all code
relicensed to ASF, and package namespace switched to org.apache.daffodil
- Development pace has continued without any notable issues
- The first release candidate was created in February 2018. However, bugs were
found that required an rc2 release. Those issues were resolved, but issues
related to the LICENSE and NOTICE files were raised in the rc2 release vote.
This is expected to require an rc3 release, planned to start voting in early
March.
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup
[X] Working towards first release
[X] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
2017-09-06 - 2.0.0 (pre-Apache release)
When were the last committers or PPMC members elected?
- None, same as project incubation
Signed-off-by:
[X](daffodil) John D. Ament
Comments: Project is moving in the right direction, and aiming for their first ASF release.
[X](daffodil) David Fisher
Comments:
--------------------
Druid
Druid is a high-performance, column-oriented, distributed data store.
Druid has been incubating since 2018-02-28.
Three most important issues to address in the move towards graduation:
1. Migrate existing contributors and users to apache mailing lists.
2. Move the source code and website to apache infrastructure.
3. Plan and execute our first Apache release.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?
* The team is working on the items on the Incubation Checklist.
* We’re working on moving the existing mailing lists, source code, github
issues and website to Apache Infrastructure.
* In order to keep the project momentum up until the migration is complete we
are continuing the development on existing druid repository.
* We are considering doing the 0.12.0 release before migrating source code to
apache, since the IPMC has already voted for it and migrating infra to
apache might take a while, and we don't want to block 0.12.0 on this
migration.
How has the community developed since the last report?
* This is our first board report.
* Current Status of our Github contributors (212), forks (1,516), watchers
(524) and stars (6,157)
How has the project developed since the last report?
* Creation of Domain name for Druid - DONE
* Creation of Mailing lists - DONE.
* A healthy, constant flow of bug fixes, quality improvements and new
Features are still ongoing on https://github.com/druid-io/druid.
How would you assess the podling's maturity?
@Mentors Please feel free to add your own commentary.
[X] Initial setup
[ ] Working towards first release
[ ] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
* No official release yet since being voted into Apache Incubation.
(Planning for the first Apache release in Q2, 2018)
When were the last committers or PPMC members elected?
* Project is still functioning with the initial set of committers.
Signed-off-by:
[x] (druid) Julian Hyde
Comments:
Druid has only been in the incubator for a week, but
the PPMC have already checked off quite a few of the
initial tasks. This momentum is encouraging.
[X] (druid) P. Taylor Goetz
Comments: Druid is off to a good start. They were not
required to report this soon, but voluntarily did so.
[X] (druid) Jun Rao
Comments:
Good start for Druid.
--------------------
Dubbo
Dubbo is a high-performance, lightweight, java based RPC framework.
Dubbo has been incubating since 2018-02-16.
Three most important issues to address in the move towards graduation:
1. Get ICLA signed (currently got 7 out of 9 initial committers)
2. Get community to sign up and move discussion to dev@
3. Move codebase 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?
N/A(This is the first report)
How has the project developed since the last report?
N/A(This is the first report)
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[X] Initial setup
[ ] Working towards first release
[ ] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
2018-01-25 (before joining Apache Incubator)
When were the last committers or PPMC members elected?
N/A, right now all the PPMC members come from initial committers.
Signed-off-by:
[X](dubbo) Justin Mclean
Comments:
[X](dubbo) John D. Ament
Comments: Keep up the focus on the transition work.
[ ](dubbo) Jean-Frederic Clere
Comments:
[X](dubbo) Mark Thomas
Comments: Transition is still underway. Good to see discussion with (prospective)
mentors that was happening off-list has moved on-list.
--------------------
ECharts
ECharts is a charting and data visualization library written in JavaScript.
ECharts has been incubating since 2018-01-18.
Three most important issues to address in the move towards graduation:
1. Move GitHub repository to apache/incubator-echarts.
2. Working towards first ASF release.
3. Build the community and attract more 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?
1. Got all ICLA signed of initial committers.
2. Updated the license to apache v2
How has the project developed since the last report?
None
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[x] Initial setup
[ ] Working towards first release
[ ] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
N/A
When were the last committers or PPMC members elected?
N/A
Signed-off-by:
[X](echarts) John D. Ament
Comments: No on list discussion of report. Some more user based discussions happening, no development activities.
[ ](echarts) Daniel Gruno
Comments:
[ ](echarts) Kevin A. McGrail
Comments:
[X](echarts) Dave Fisher
Comments: Slow startup.
--------------------
Griffin
Griffin is a open source Data Quality solution for distributed data systems at any scale in both streaming or batch data context.
Griffin has been incubating since 2016-12-05.
Three most important issues to address in the move towards graduation:
1. Grow/Marketing the community since we will release milestone version soon.
2. Onboard use cases, we need to contact with our customers weekly for feedback.
3. Make profiling and accuracy matured based on feedback.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
- None
How has the community developed since the last report?
- A new committer has been elected.
- More users had contacted us for use cases.
How has the project developed since the last report?
- Active development is moving on well, 38 commits in last three months.
- Measure module performance enhancement in streaming mode.
- Timeliness and uniqueness measure for batch and streaming mode has been developed.
- Publish measure management has been developed.
- Metrics management supported in service module.
- UI module for job schedule process has been developed.
- Work toward for next version release.
How would you assess the podling's maturity?
[] Initial setup
[] Working towards first release
[] Community building - One new contributor
[X] Nearing graduation
[] Other:
Date of last release:
- Nov 23rd, 2017
When were the last committers or PPMC members elected?
- A new committer was elected at Dec 21st, 2017
Signed-off-by:
[X](griffin) Henry Saputra
Comments:
[ ](griffin) Kasper Sørensen
Comments:
[X](griffin) Uma Maheswara Rao Gangumalla
Comments:
[ ](griffin) Luciano Resende
Comments:
--------------------
HTrace
HTrace is a tracing framework intended for use with distributed systems
written in java.
HTrace has been incubating since 2014-11-11.
Three most important issues to address in the move towards graduation:
1. -
2. -
3. -
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
The HTrace podling has seen no code activity in months. Discussion of
sending it to the Attic have been circulating for some time as well.
After literally no activity again over the last few months, it looks like
it is time to progress with sending HTrace to the Attic.
How has the community developed since the last report?
It has not.
How has the project developed since the last report?
It has not.
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[X] Initial setup
[X] Working towards first release
[X] Community building
[ ] Nearing graduation
[X] Other: No actiity.
Date of last release:
2016-03-04
When were the last committers or PPMC members elected?
2016-10-03
Signed-off-by:
[ ](htrace) Jake Farrell
Comments:
[ ](htrace) Todd Lipcon
Comments:
[X](htrace) Lewis John Mcgibbney
Comments: In our January 2018 report we mentioned that
"HTrace is very quiet. There is opportunity to continue
work if we engage with projects already using HTrace. If that does not
happen, we should retire the podling." We should therefore retire the podling.
[ ](htrace) Andrew Purtell
Comments:
[ ](htrace) Billie Rinaldi
Comments:
[ ](htrace) Michael Stack
--------------------
Myriad
Myriad enables co-existence of Apache Hadoop YARN and Apache Mesos together on
the same cluster and allows dynamic resource allocations across both Hadoop
and other applications running on the same physical data center
infrastructure.
Myriad has been incubating since 2015-03-01.
Three most important issues to address in the move towards graduation:
In this project state the most important action to move towards
graduation is to create traction on the project again. So from my
point of view the list of actions is the following:
[X] Promote the project in social networks, blog entries and so forth
for getting interest again.
[X] Get a few active new users.
[X] Refresh the state of unattended issues reported for interested
users in the pass.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
Only to be informed about new users are willing to boosting up the
project again.
How has the community developed since the last report
The most relevant thing is the activation of mailing list again and a
few new users willing to participate.
How has the project developed since the last report.
The project has not evolved since the last report.
How does the podling rate their own maturity.
[ ] Initial setup
[ ] Working towards first release
[X] Community building
[ ] Nearing graduation
Date of last release:
2016-05-29
When were the last committers or PPMC members elected?
Signed-off-by:
[ ](myriad) Benjamin Hindman
Comments:
[ ](myriad) Danese Cooper
Comments:
[X](myriad) Ted Dunning
Comments:
[ ](myriad) Luciano Resende
Comments:
--------------------
Nemo
Nemo is a data processing system to flexibly control the runtime behaviors
of a job to adapt to varying deployment characteristics.
Nemo has been incubating since 2018-02-04.
Three most important issues to address in the move towards graduation:
1. Grow the community
2. Create a first Apache release
3. Donate code to ASF
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?
* Committers filed ICLAs.
* Committers enrolled in mailing lists
* Committers enrolled in the slack channel
* Committers used mailing lists to discuss initial setups
* Committers started to send PRs to the apache infra
How has the project developed since the last report?
* gitbox/github set up and code transferred from snuspl/nemo to apache/incubator-nemo
* JIRA created and issues transferred from github to JIRA
* web site set up
* mailing lists set up
* The name ‘Apache Nemo’ approved (PODLINGNAMESEARCH-139)
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[x] Initial setup
[ ] Working towards first release
[ ] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
None yet.
When were the last committers or PPMC members elected?
None yet.
Signed-off-by:
[X](nemo) Davor Bonaci
Comments: The podling is moving very quickly.
[ ](nemo) Hyunsik Choi
Comments:
[X](nemo) Byung-Gon Chun
Comments:
[X](nemo) Jean-Baptiste Onofre
Comments:
[ ](nemo) Markus Weimer
Comments:
[ ](nemo) Reynold Xin
IPMC/Shepherd notes:
johndament: Seeing good progress with on list communication.
--------------------
Omid
Omid is a flexible, reliable, high performant and scalable ACID transactional
framework that allows client applications to execute transactions on top of
MVCC key/value-based NoSQL datastores (currently Apache HBase) providing
Snapshot Isolation guarantees on the accessed data.
Omid has been incubating since 2016-03-28.
Three most important issues to address in the move towards graduation:
1. Boost project dissemination in the Apache community.
2. Collaborate/integrate Omid with other Apache projects.
3. Get positive feedback from other projects currently in Apache.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
N/A
How has the community developed since the last report?
Apache Phoenix
How has the project developed since the last report?
HBase 0.x version being tested in prod environment at Yahoo.
Preparing 0.9.0 version.
Quarter Stats (from: 2017-12-01 to: 2018-02-28):
+---------------------------------------------+
| Metric | counts |
+---------------------------------------------+
| # of msgs in dev list | 108 |
| Active Contributors (incl mentors)| 8 |
| Jira New Issues | 2 |
| Resolved Issues | 8 |
| Pull Requests merged | 9 |
| Pull Requests proposed | 3 |
+---------------------------------------------+
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup
[ ] Working towards first release
[X] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
2016-06-24
When were the last committers or PPMC members elected?
Signed-off-by:
[ ](omid) Alan Gates
Comments:
[ ](omid) Lars Hofhansl
Comments:
[ ](omid) Flavio P. Junqueira
Comments:
[ ](omid) Thejas Nair
Comments:
[x](omid) James Taylor
Comments:
--------------------
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. Additionally, it now provides options to host the platform
components as Docker containers on various Container Frameworks such as Mesos,
Kubernetes, and Compose.
OpenWhisk has been incubating since 2016-11-23.
Three most important issues to address in the move towards graduation:
Establish process for source release (automation work ongoing here
https://github.com/apache/incubator-openwhisk-release) Increase contributions
to maintain all project repos. Kubernetes and Mesos deployments work and
integrations need improvement; comm, aware of lots of work being done in
(private and public) forks.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?
- Issue backlog building on incubator-openwhisk has grown significantly;
need to prioritize and work to reduce while advancing
performance/security/deployment issues.
- Trying to add more active Committers to augment those who have
dropped off in their activity. A consistent hosted, staging
environment would help repro. issues, as well as stage PRs to test
fixes. It had been our intent to have Apache host our staging (and
move it out of disparate private builds within various companies).
However, INFRA indicates they only typically allocate 1 VM per
project for use with demos and minor things. They indicate that
perhaps a corporate donation is in order (ala. Spark).
- Goal: standup testing resources at Apache and utilize for public CI
and performance testing of OpenWhisk on Kubernetes
- See discussion here: OpenWhisk / Kubernetes proposed epics/action
items/questions
- No change in status since last quarterly report
- Formal hand-off of OpenWhisk trademark/logo from IBM needs to be
executed; need to identify process for this.
- Discussion started w/ Apache legal via "legal-discuss" mailing list
with subject "Trademark handoff for "OpenWhisk" name and logo".
- No change in status since last quarterly report
How has the community developed since the last report?
Mentor changes:
- Felix Meschberger and Sergio Fernández have stepped down from being
mentors with regrets.
- Bertrand Delacretaz volunteered to become mentor to fill Felix' spot.
- Jim Jagielski volunteered to become mentor to fill Sergio's spot.
- dev mailing list usage has been relatively active
- incubator-openwhisk Github stars: 2877 (+696 since last report)
- incubator-openwhisk GitHub forks: 544 (+75 since last report)
The bi-weekly Zoom "Technical Interchange" continues to be well received
and attended. Complete videos posted to OW YouTube channel and detailed
notes to our CWIKI. YouTube Channel:
https://www.youtube.com/channel/UCbzgShnQk8F43NKsvEYA1SA CWiki Meeting
Notes: OpenWhisk Technical Interchange Meeting
Notes:https://cwiki.apache.org /confluence/display/OPENWHISK/OpenWhisk+Technical+Interchange+Meeting+Notes
New Contributors
- Michele Sciabarra: developing a GoLang runtime w/ perf. tests
- Seonghyun Oh: working on a Bash runtime for functions
- Nhat Nguyen: NodeJS interest
- Sang Heon Lee: working on CouchDB implementation for ArtifactStore (WIP)
- Allen Servedio: identified a bug in wskdeploy, extended code to allow
support for GitHub private repos.
- Vipul Kashyap: RedHat, no commits yet
- Lorna Mitchell: IBM, data service integrations (e.g., CouchDB), NodeJS,
PHP runtimes
- Neeraj Mangal: discussing namespace enhancements
- Jason Peterson: IBM, maintaining packages Alarms, Push Notifications,
Cloudant and Deploy
- Sudipta Biswas: support S390X deployment (i.e., power architectures)
- Kiseok Jang: Java (JVM) enhancement interest, no commits yet
- Junyoung Sung: interest in support Bash actions (runtime), no commits yet
How has the project developed since the last report?
Emphasis on 3 areas have been featured since last report:
- Release process
- See incubator-openwhisk-release (code, tools, documentation), see
demo (as of 2/28): YouTube
- Lots of discussion and work on developing both a manual and
automated (source code) release process for 12 openwhisk project
repos. that constitute the project's platform and related tooling
(i.e., version tied).
- All steps in release process are described in repo's markdown
that the comm. is working to complete
- Checklists/Runbooks created for release managers to follow
- Automation tested with signing/hashing as per Apache requirements
- still working on assuring all Apache license/legal/notice/change
files are present (perhaps automated as well) issues with RAT and
TENTACLES tools documented, working to document our exception
lists and policies and alternative tools to verify licenses when
not supported by RAT
- Security enhancements
- Now encrypting "data-in-motion" by enabling SSL between Controllers,
Kafka and Invokers.
- Scalability / Performance
- Controller now uses fully scalable impl. instead of active with "hot
standby"; lots of testing/changes to validate as optional before
moving to promote as default on dev. list.
- Introduced new LoadBalancer plug-in that uses Horizontal sharding;
evaluating making it the default as perf. tests indicate notable
improvement in controller-invoker throughput under load.
- Improved handling of Artifact Attachments as a separate artifact (for
storage/update/deletion) and provide alternative implementations
(other than CouchDB), primarily Object Storage services as targets.
- Made ActivationId implementation leaner by adopting UUID (single
string) versus an object that wraps a UUID.
- Other Notable discussions/changes/issues/features:
- Added support of Time-series DBs using Kamon Tag (e.g., OpenTSDB,
Datadog)
- Discussions on large (size) argument support in runtimes/impacts on
performance/configurability.
- Updated all tools/ubuntu-setup to support xenial and later Ubuntu
releases.
- Implementation of runtime for Go (GoLang) actions. New contributor
authored new Invoker runtime and tested with 3 possible impls. for
performance before submitting for review.
- Action Compositions now supported in Controller and demonstrated on
Interchange call; more changes may be coming for Controller to enable
parallel processing.
- Added A Pull Request (PR) template (checklist) for all code
submissions (incubator-openwhisk) to assure they are ready for review
and get assigned correctly.
- https://github.com/apache/incubator-openwhisk/pull/3386
- Action time limits are now configurable.
How would you assess the podling's maturity? Please feel free to add your
own commentary.
[ ] Initial setup
[X] Working towards first release
[X] Community building
[ ] Nearing graduation
[ ] Other:
Comments:
Need greater variety of contributors and contributing companies
Date of last release:
N/A
When were the last committers or PPMC members elected?
New Committers+PPMC: Dave Grove (2018-02-08), James Thomas (2018-02-08)
Mark Deuser (2018-02-22) New Committers: Priti Desai (2018-02-19)
Signed-off-by:
[X](openwhisk) Bertrand Delacretaz
Comments:
[ ] (openwhisk) Jim Jagielski
Comments:
[ ](openwhisk) Isabel Drost-Fromm
Comments:
--------------------
PLC4X
PLC4X is a set of libraries for communicating with industrial programmable
logic controllers (PLCs) using a variety of protocols but with a shared API.
PLC4X has been incubating since 2017-12-18.
Three most important issues to address in the move towards graduation:
1. Building the community: The PPMC and committer group has a large
percentage of codecentric employees, we have been recruiting people
from other companies, but will have to continue these efforts for
establishing a healthy Apache community.
2. Onboarding of new committers: With PLC4X several people on the team
are not very familiar with the Apache Way. We have started and will
continue our efforts on this onboarding.
3. Make our first release
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
In order to get access to some of the specifications the ASF will eventually
have to become Members of some external foundations: OPC, EtherCat, Modbus …
these memberships usually have a free level, that allows us to use the
specifications but doesn’t result in any regular costs. We will have to discuss
these details with the ASF and the other foundations.
One of the external foundations (Profinet) doesn’t have a free membership. In
general, the CEO of the European branch of the Profinet Foundation has signaled
that it should be possible for the ASF to become a member and have an outside
company pay the membership fees, but we have to discuss the details (With them
as well as the ASF).
How has the community developed since the last report?
Christofer has invested most of his time in February spreading the word about
PLC4X.
A first POC has been created for the company “Kampf Schneid- und Wickeltechnik
GmbH & Co. KG”
Two articles for IoT Special editions of German tech magazines have been
submitted. The “JavaSPEKTURM – IoT Sonderheft” is scheduled for sale end or
March, the “iX – IoT Sonderheft” is scheduled later.
The university of Stuttgart has shown great interest in joining our effort, as
they had just started a project with a similar goal. Chris will continue
on-boarding efforts in March.
At this year’s AALE Conference in Cologne, Chris has talked to a lot of people
from different German universities. We’re hoping to get at least a hand full of
them on board too.
We have continuing our onboarding of new Apache committers (extended emails
with a lot of explanations on why we are doing things the way we are)
In the next few months we are expecting to spread the word and hopefully grow
the community due to the tech magazine articles as well as several talks on
different conferences.
How has the project developed since the last report?
The work on the RawSocket Netty transport which is a requirement to implement
protocols that are IP based, but are not TCP or UDP has continued and we are
currently waiting for infra to setup a dedicated Jenkins VM for our project so
we can enable the RawSocket releated tests.
We have finished a first version of the Beckhoff ADS driver, and are looking
forward to first tests with this.
The functionality of the S7 driver has improved due to experience collected
with the Kampf POC.
Next we are aiming to implement Modbus and OPC-UA protocols.
How would you assess the podling's maturity?
Please feel free to add your own commentary.
We have a mix of new participants and experienced Apache people involved.
So far, the new participants have shown great willingness and success in
adopting the Apache Way.
However, we still need to continue:
the on-boarding
increasing the diversity of the team
Also, will we need to decide and establish all the processes involved in
releasing software at Apache
[X] Initial setup
[X] Working towards first release
[ ] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
XXXX-XX-XX
When were the last committers or PPMC members elected?
Signed-off-by:
[ ](plc4x) Greg Trasuk
Comments:
[X](plc4x) Justin Mclean
Comments:
[ ](plc4x) Luciano Resende
Comments:
[X](plc4x) Stefan Bodewig
--------------------
Pulsar
Pulsar is a highly scalable, low latency messaging platform running on
commodity hardware. It provides simple pub-sub semantics over topics,
guaranteed at-least-once delivery of messages, automatic cursor management for
subscribers, and cross-datacenter replication.
Pulsar has been incubating since 2017-06-01.
Two most important issues to address in the move towards graduation:
1. Grow the community with new Committers/PPMC members.
2. Complete the Podling name search tasks
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 community added 6 new contributors that submitted pull-requests which
were merged into master.
There has been a sharp increase in users approaching the team on the Slack
channel with many questions on getting started, clarifications,
troubleshooting. While developers use Slack for informal chatting, the
predominant usage of Slack has be users support. We have created a tool to
create daily email digests of the conversation and post it on dev@ and user@
lists, to comply with ASF policy of. We are also extracting the most
recurrent questions/answer from Slack and plan to add an FAQ section on the
website, together with improving documentation in the areas that seemed more
difficult to users.
Project members from several companies have organized or participated in
several meetups, presenting Pulsar's introductions, deep-dives and hands-on
tutorial, including recorded podcasts. We have several scheduled talks on
Pulsar at various conferences (such as Strata San Jose on March 8th).
How has the project developed since the last report?
22 authors have pushed 536 commits to master in the last 3 months.
The project has made the its third and fourth releases since joining the
Apache Incubator (1.21.0-incubating on Dec 17th and 1.22.0-incubating on Mar
6th). Project members are actively working on next milestone, 2.0 release
that will include several new features including:
* Topic compaction
* Redesigned type-safe API with schema support
* Lightweight compute support
Overall, since December, 7 new PIPs (Pulsar Improvement Proposals) for major
feature/changes, have been submitted to the wiki and discussed in the
mailing list.
Since the last report the number of weekly-active-users on the Slack channel
has increased from 27 to 53.
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup
[ ] Working towards first release
[ ] Community building
[X] Nearing graduation
[ ] Other:
Date of last release:
2017-12-13, 1.21.0-incubating
2018-03-06, 1.22.0-incubating
When were the last committers or PPMC members elected?
2018-01-19 - Sijie Guo
Signed-off-by:
[X](pulsar) Dave Fisher
Comments: They have the release cycle down pretty well. Building community.
[X](pulsar) Jim Jagielski
Comments: I would say that the project is still building community and doing so extremely well.
[X](pulsar) P. Taylor Goetz
Comments: I would have checked the "Community Building" box, but the podling is doing very well.
[ ](pulsar) Francis Liu
Comments:
--------------------
SAMOA
SAMOA provides a collection of distributed streaming algorithms for the most
common data mining and machine learning tasks such as classification,
clustering, and regression, as well as programming abstractions to develop new
algorithms that run on top of distributed stream processing engines (DSPEs).
It features a pluggable architecture that allows it to run on several DSPEs
such as Apache Storm, Apache Flink, and Apache Samza.
SAMOA has been incubating since 2014-12-15.
Three most important issues to address in the move towards graduation:
1. Enlarge the contributing community
2. Have new companies and organizations using the Apache Samoa technology
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
None
How has the community developed since the last report?
Mailing list activity (December 2017 - February 2018):
* @dev: 23 messages
Jira issues backlog (December 2017 - February 2018):
* Created: 2
* Resolved: 1
How has the project developed since the last report?
* Just elected two new members to the Apache Samoa PPMC
* Planning a new release in the next month
* Worked on consolidating input and output API, to work better with multiple types of data
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup
[ ] Working towards first release
[X] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
2016-09-30
When were the last committers or PPMC members elected?
January 2018
Signed-off-by:
[ ](samoa) Alan Gates
Comments:
[ ](samoa) Ashutosh Chauhan
Comments:
[ ](samoa) Enis Soztutar
Comments:
[X](samoa) Ted Dunning
Comments: Is this community really generating enough momentum to graduate?
--------------------
ServiceComb
ServiceComb is a microservice framework that provides a set of tools and
components to make development and deployment of cloud applications easier.
ServiceComb has been incubating since 2017-11-22.
Three most important issues to address in the move towards graduation:
1. IP clearance and License clean up
2. Community building
3. Create a 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?
* The community has been working hard to get the first release out, which will be service-center 1.0.0-m1, java-chassis 1.0.0-m1 and saga 0.1.0
* service-center had three internal release votes, java-chassis and saga release is one the way.
How has the project developed since the last report(Feb 2018)?
Due to Chinese new year, lots of committer take the holiday
* Java Chassis merged with 10 PRs by 5 contributors.
* Service Center merged with 24 PRs by 4 contributors .
* Saga resolved merged with 6 PRs by 3 contributors.
* 48 mails sent by 14 people on the dev@ list
Please feel free to add your own commentary.
[ ] Initial setup
[*] Working towards first release
[*] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
XXXX-XX-XX
When were the last committers or PPMC members elected?
NONE
Signed-off-by:
[X](servicecomb) Roman Shaposhnik
Comments:
[ ](servicecomb) Jean-Baptiste Onofre
Comments:
[X](servicecomb) Timothy Chen
Comments:
--------------------
SkyWalking
Skywalking is an APM (application performance monitor), especially for
microservice, Cloud Native and container-based architecture systems. Also
known as a distributed tracing system. It provides an automatic way to
instrument applications: no need to change any of the source code of the
target application; and an collector with an very high efficiency streaming
module.
SkyWalking has been incubating since 2017-12-08.
Three most important issues to address in the move towards graduation:
1. IP clearance.
3. First ASF release. (SkyWalking 5.0)
3. Further ASF culture and processes.
4. 5.x releases are stable for product, and have an open end user case, at least.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
Looking for input on how to develop/release our plugins that rely on GPL libraries,
is making those plugins optional good enough?
How has the community developed since the last report?
Improved understanding of the release process way of the Apache. And
prepare for the first release.
A C# agent proposed by .NET community has started.
After it release, will make SkyWalking can support multi languages.
Some discussions about golang and Nodejs server are on going.
How has the project developed since the last report?
Code wise the project has good momentum.
There has been ~44 pull requests opened and accepted, and 103 commits,
by 7 contributors in the last month.
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[X] Initial setup
[X] Working towards first release
[ ] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
5.0.0-alpha is currently in progress. One attempt was made and put into the staging repository,
only a minor issue blocked the test build announcement email going out.
When were the last committers or PPMC members elected?
Hongtao Gao (PPMC)
Sheng Wu (PPMC)
Shinn Zhang (PPMC)
Yongsheng Peng (PPMC)
Signed-off-by:
[x](skywalking) Luke Han
Comments:
[X](skywalking) Willem Ning Jiang
Comments:
[x](skywalking) Mick Semb Wever
Comments:
--------------------
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.
Most important issues to address in the move towards graduation:
Since new development on one of Slider's primary maven modules has
moved to the hadoop-yarn-services-core module in Apache Hadoop,
development of other Slider modules has also tailed off. The Slider
community needs to decide whether we should retire the remaining
Slider code or propose graduation.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
No additional issues.
How has the community developed since the last report?
Mailing list and commit activity have continued at a low rate. We invited
a new committer / PPMC member, Kyungwan Nam.
How has the project developed since the last report?
An improvement to allow Slider to work in multi-homed environments is
in progress and we have fixed a couple of bugs related to certificate
management and functional test failures when running on newer versions
of Hadoop.
How would you assess the podling's maturity?
The podling is relatively mature, but activity is low.
[ ] Initial setup
[ ] Working towards first release
[ ] Community building
[ ] Nearing graduation
[x] Other: Discussing direction
Date of last release:
2017-03-23 slider-0.92.0-incubating
When were the last committers or PPMC members elected?
2018-02-21 New committer and PPMC member Kyungwan Nam
Signed-off-by:
[ ](slider) Arun C Murthy
Comments:
[ ](slider) Devaraj Das
Comments:
[ ](slider) Jean-Baptiste Onofré
Comments:
[ ](slider) Mahadev Konar
Comments:
[X](slider) Vinod Kumar Vavilapalli
Comments: Given the progress of development in hadoop-yarn-services, I think this community should start the retirement proceedings. The things to figure out when the retirement happens is the website redirect, past releases' bits and any outstanding apps that are not yet migrated.
--------------------
Spot
Apache Spot is a platform for network telemetry built on an open data model
and Apache Hadoop.
Spot has been incubating since 2016-09-23.
Three most important issues to address in the move towards graduation:
1. More activity in the User and Dev mail lists
2. Integrate Open Data Model on top of Spot modules
3. Develop a better release process
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?
A. more interaction from partners
B. Seeing more interest and usage of Spot leading to more contributions in on the way
How has the project developed since the last report?
A. More development around Open Data Model
B. New data sources being integrated with ODM is maturing the structure
C. Adding Kerberos support to the project
D. Ingest Redesign
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup
[ ] Working towards first release
[X] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
2017-09-08
When were the last committers or PPMC members elected?
2018-01-18
Signed-off-by:
[ ](spot) Jarek Jarcec Cecho
Comments:
[ ](spot) Brock Noland
Comments:
[ ](spot) Andrei Savu
Comments:
[X](spot) Uma Maheswara Rao G
Comments: Dev list discussions are low and community should give more attention to this point.
--------------------
Superset
Superset is an enterprise-ready web application for data exploration, data
visualization and dashboarding.
Superset has been incubating since 2017-05-21.
Three most important issues to address in the move towards graduation:
1. Plan and execute our first Apache release
2. Align on a long-term product roadmap with the broader Apache Superset community
3. Grow the community and enroll new committers
Any issues that the Incubator PMC or ASF Board might wish/need to be aware of?
* None
How has the community developed since the last report?
* Organic growth of our Github contributors (211), forks (2,981), watchers
(975) and stars (18,249)
* Group of active committers meeting bi-weekly from Airbnb, Lyft and Twitter
* Slack channel for Apache Superset at https://apache-superset.slack.com/ has active growth and activity
How has the project developed since the last report?
* A redesign of the Dashboarding view is now midway through completion
* A redesign of the Explore view has just started
* Deck.gl (https://uber.github.io/deck.gl/#/) has been integrated as a visualization type
* A healthy, constant flow of bug fixes, quality improvements and new
features, take a look at the project’s Pulse on Github for more details
How does the podling rate their own maturity.
[ ] Initial setup
[X] Working towards first release
[ ] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release: No official release yet since being voted into Apache
Incubation. (Planning for the first Apache release in Q2, 2018)
When were the last committers or PPMC members elected?
* Grace Guo - PPMC & Committer (2017-10-29)
* Chris Williams - PPMC & Committer (2017-10-20)
* John Bodley - PPMC & Committer (2017-10-20)
Signed-off-by:
[X](superset) Ashutosh Chauhan
Comments:
[x](superset) Luke Han
Comments:
[X](superset) Jim Jagielski
Comments: Looking forward to seeing how the project handles the release process
--------------------
Taverna
Taverna is a domain-independent suite of tools used to design and execute
data-driven workflows.
Taverna has been incubating since 2014-10-20.
Three most important issues to address in the move towards graduation:
1. Re-engage PPMC towards community building
2. Release or Retire legacy git repositories
3. Graduate!
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?
Large interest from Google Summer of Code students.
Multiple pull requests, many already merged.
Elected new PPMC member Sagar.
Email stats dev@taverna:
2017-12: 18
2018-01: 120
2018-02: 156
How has the project developed since the last report?
Taverna Server release, addressed many IP/license issues.
Active development, but focused mainly on the Android app.
Some challenges with maintaining legacy git repositories as
they require different skills.
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup
[ ] Working towards first release
[x] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
2018-01-18
When were the last committers or PPMC members elected?
2018-02-26 (PPMC)
Signed-off-by:
[ ](taverna) Andy Seaborne
Comments:
While there has been an uptick in development activity recently, and the
contributor is a new PPMC member, the podling PPMC as a group is not moving
towards graduation.
Reiterating my comments from December: I am worried that pushing through
graduation will only result in the same situation as a TLP.
[ ](taverna) Daniel J Debrunner
Comments:
[ ](taverna) Marlon Pierce
Comments:
[x](taverna) Stian Soiland-Reyes
Comments:
I have been quite impressed by the uptick since New Year, which shows how just
a bit of PMC engagement can give lots of follow-on activitity. I would hope
Taverna can continue this move out of the "risk of retire" zone, but that
requires more PMC members to chip in now and then.
[ ](taverna) Suresh Marru
Comments:
[ ](taverna) Suresh Srinivas
Comments:
IPMC/Shepherd notes:
johndament: the discrepancies between the mentors seems to be a concern. In general it seems like good communication flow.
--------------------
Tephra
Tephra is a system for providing globally consistent transactions on top of
Apache HBase and other storage engines.
Tephra has been incubating since 2016-03-07.
Two most important issues to address in the move towards graduation:
1. Improve community engagement
2. Increase adoption
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
- None at this time.
How has the community developed since the last report?
- 15 new JIRAs filed since the last report
- 1 external contributors submitted patches since the last report
- 1 external contributor created tickets in JIRA since the last report
How has the project developed since the last report?
- Working on 0.14.0-incubating release
- Adding support for HBase 2.0 (new major version of HBase)
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup
[ ] Working towards first release
[x] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
2017-09-21
When were the last committers or PPMC members elected?
- None since coming to incubation
Signed-off-by:
[ ](tephra) Alan Gates
Comments:
[ ](tephra) Andrew Purtell
Comments:
[x](tephra) James Taylor
Comments:
[ ](tephra) Lars Hofhansl
Comments:
-----------------------------------------
Attachment AH: Report from the Apache Jackrabbit Project [Michael Dürig]
Report from the Apache Jackrabbit committee [Michael Dürig]
## Description:
The Apache Jackrabbit™ content repository is a fully conforming
implementation of the Content Repository for Java™ Technology API
(JCR, specified in JSR 170 and 283). The Jackrabbit content
repository is stable, largely feature complete and actively being
maintained.
Jackrabbit Oak is an effort to implement a scalable and performant
hierarchical content repository as a modern successor to the Apache
Jackrabbit content repository. It is targeted for use as the
foundation of modern world-class web sites and other demanding
content applications. In contrast to its predecessor, Oak does not
implement all optional features from the JSR specifications and it
is not a reference implementation.
## Issues:
There are no issues requiring board attention at this time
## Activity:
Apache Jackrabbit Oak receives most attention nowadays. All
maintenance branches and the unstable development branch are
continuously seeing moderate to high activity.
Apache Jackrabbit itself is mostly in maintenance mode with most of
the work going into bug fixing and tooling. New features are mainly
driven by dependencies from Oak.
This quarter saw the 5th major release of Jackrabbit Oak (1.8). With
Oak 1.8 out the team is currently discussing future topics including
supporting other persistence back ends, adapting to upcoming Java
versions and how to support older Java versions while maintaining
backward compatibility without losing the ability to invent.
A potential security vulnerability was reported to us by the Apache
Security Team on Dec. 25th. See https://s.apache.org/7l6s. After careful
evaluation and consideration with the reporter no exploitable issue was
identified. See https://s.apache.org/R3Ke. Nevertheless the affected code
was improved to avoid a potential future vulnerability through reuse of
that code in another context. See OAK-7119.
## Health report:
The project is healthy with a continuous stream of traffic on all
mailing lists reflecting the activity of the respective component.
There is a wide range of topics being discussed on the dev and user
lists as well as on the various Jira issues.
Turn around on Jira issues is on the lower end this quarter. It is
expected to rise again once feature work on the next release picks up.
## PMC changes:
- Currently 50 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Robert Munteanu on Mon May 22 2017
- Roy T. Fielding resigned and was removed from the PMC on March 6th.
See https://s.apache.org/l8Kj
## Committer base changes:
- Currently 50 committers.
- No new committers added in the last 3 months
- Last committer addition was Robert Munteanu on Mon May 22 2017
- Roy T. Fielding resigned and was removed from committers on March 6th.
https://s.apache.org/l8Kj
- Removed orphaned account "alexparvulescu" from committers. This account
belonged to Alex Parvulescu who went through a name change to Alex Deparvu and
whos new account is "stillalex".
## Releases:
- jackrabbit-2.16.1 was released on Tue Feb 06 2018
- jackrabbit-2.17.0 was released on Mon Dec 18 2017
- jackrabbit-2.17.1 was released on Tue Jan 30 2018
- jackrabbit-2.6.10 was released on Mon Mar 05 2018
- jackrabbit-2.8.7 was released on Fri Dec 29 2017
- oak-1.0.40 was released on Fri Jan 05 2018
- oak-1.0.41 was released on Mon Mar 05 2018
- oak-1.2.28 was released on Tue Jan 16 2018
- oak-1.2.29 was released on Mon Mar 12 2018
- oak-1.4.19 was released on Thu Jan 04 2018
- oak-1.4.20 was released on Mon Feb 12 2018
- oak-1.6.10 was released on Mon Mar 05 2018
- oak-1.6.8 was released on Tue Jan 09 2018
- oak-1.6.9 was released on Wed Feb 07 2018
- oak-1.7.14 was released on Wed Dec 20 2017
- oak-1.8.0 was released on Tue Jan 09 2018
- oak-1.8.1 was released on Mon Jan 22 2018
- oak-1.8.2 was released on Tue Feb 06 2018
## JIRA activity:
- 349 JIRA tickets created in the last 3 months
- 337 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AI: Report from the Apache James Project [Eric Charles]
## Description:
- The Apache James Project delivers a rich set of open source modules and
libraries, written in Java, related to Internet mail which build into an
advanced enterprise mail server.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- The project joins Google Summer Of Code 2018
- The newbie label has been added to some issues in order to encourage
contributions
- The team has planned to replace the actual mail queue for a scalable
implementation
- We have migrated the james-hupa sub-project from svn to git
- We are working on:
* better support of spam handling
* sending Message Disposition Notification on the JMAP protocol
* handling quotas per user / per domain
- CVE-2012-3536 for Hupa fix has been published on the web site (mitre
updated).
- Release of james-skin 1.10.
## Health report:
- Ongoing bug fixes and user support on mailing list.
- Eric (James Chair) has not been able to submit the reports those last
months. We will report next month (April) to get back to normal schedule.
## PMC changes:
- Currently 16 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Antoine Duprat on Fri Mar 11 2016
## Committer base changes:
- Currently 37 committers.
- No new committers added in the last 3 months
- Last committer addition was Raphael Ouazana at Thu Jul 07 2016
## Releases:
- 3.0.0 was released on Tue Jul 25 2017
## Mailing list activity:
- Subscribers and email activity stable.
## JIRA activity:
- 91 JIRA tickets created in the last 3 months
- 105 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AJ: Report from the Apache Karaf Project [Jean-Baptiste Onofré]
## Description:
- Apache Karaf provides a very modern and polymorphic container,
multi-purpose (microservices, OSGi, etc) powered by OSGi.
## Issues:
- There are no issues requiring board attention at this time
## Activity:
- We continue the preparation of the 4.2.0 GA.
- We are preparing new subproject releases.
- A couple of new features are coming like the docker feature (it has been
discussed on the mailing list) in the container.
## Health report:
- We continue interactions with other community and are committed to help
users.
- We also "monitoring" new potential new committers.
## PMC changes:
- Currently 15 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Christian Schneider on Mon Aug 22 2016
## Committer base changes:
- Currently 30 committers.
- No new committers added in the last 3 months
- Last committer addition was Stephen Kitt at Tue Jul 04 2017
## Releases:
- 3.0.9 was released on Fri Mar 02 2018
- 4.1.4 was released on Tue Dec 19 2017
- 4.1.5 was released on Thu Feb 15 2018
- 4.2.0.M2 was released on Tue Jan 02 2018
- Cave 4.1.0 was released on Tue Jan 02 2018
- Decanter 2.0.0 was released on Tue Feb 06 2018
## Mailing list activity:
- We can note a constant activity on the user mailing list activity. It's
really important for us as the user community is key for the project.
- dev@karaf.apache.org:
- 189 subscribers (up 6 in the last 3 months):
- 224 emails sent to list (321 in previous quarter)
- issues@karaf.apache.org:
- 42 subscribers (up 0 in the last 3 months):
- 1358 emails sent to list (1635 in previous quarter)
- user@karaf.apache.org:
- 375 subscribers (up 7 in the last 3 months):
- 432 emails sent to list (355 in previous quarter)
## JIRA activity:
- 137 JIRA tickets created in the last 3 months
- 189 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AK: Report from the Apache Labs Project [Danny Angus]
## Description
Apache Labs exists to incubate small and emerging projects from ASF
committers.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
- Labs has had a quiet period. Largely because PMC Chair has had a new job to
settle into and the ASF Members meeting is coming up.
- We still haven't managed to get any volunteers to spin up a lab, but I have
had some ideas for other ways in which labs could be of use and I will
develop those in the next period.
## Health report:
- Labs is quiet, but while there are still avenues to explore for how it might
benefit the community and generate some interaction I will persist in
following them up
## PMC changes:
- Currently 11 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Jan Iversen on Tue Feb 04 2014
- Jan Iversen resigned from the PMC on 15 Feb 2017
## Committer base changes:
- Currently 31 committers.
- No new committers added in the last 3 months
- Last committer addition was Jan Iversen at Thu Feb 27 2014
## Releases:
- According to our charter, Labs makes no releases
## Mailing list activity:
- labs@labs.apache.org:
- 209 subscribers (up 0 in the last 3 months):
- 3 emails sent to list (9 in previous quarter)
## JIRA activity:
- 1 JIRA tickets created in the last 3 months
- 0 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AL: Report from the Apache Lucene Project [Adrien Grand]
## Description:
- Lucene Core is a search-engine toolkit
- Solr is a search server built on top of Lucene Core
## Issues:
- There are no new issues requiring board attention at this time.
## Activity:
- The 7.x branch is very active and receives many bug fixes and incremental
improvements like soft deletes (Lucene), more stream evaluators and
improvements to the existing learning-to-rank support (Solr) or OpenNLP
integration (both).
- The master branch (future 8.0) mostly diverges from 7.x by improvements to
scoring and to the execution of top-k queries sorted by score.
- Both user and dev mailing-lists are very active.
- Discussions are generally flowing in a good shape.
- We produced 3 releases since the last report.
- We had a discussion around test failures which were getting ignored[1],
which resulted in a deeper analysis of test failures in order to try to
finally fix those failures[2].
- We receive vulnerability reports on a regular basis, but for one of them
we requested a CVE more than 1 year ago and haven't been able to fix it
yet[3][4]. We made it a priority and will try to more quickly act on
vulnerability reports in the future.
- We agreed to ask for reviews more systematically in order to improve code
quality[5], but without requiring reviews for code to be committed, trusting
everybody's judgment to figure out when a change absolutely requires review.
- In order to keep Java 8 as a minimum version requirement while taking
advantage of Java 9's new APIs like Arrays.mismatch, we now package a
multi-release JAR.[6]
[1] https://lists.apache.org/thread.html/b783a9d7c22f518b07355e8e4f2c6f56020a7c32f36a58a86d51a3b7@%3Cdev.lucene.apache.org%3E
[2] https://issues.apache.org/jira/browse/SOLR-12028
[3] https://lists.apache.org/thread.html/aaea8fb9cf1730a9a601d668e70b3dc9716ef9eb16e1a56cc86998a0@%3Cprivate.lucene.apache.org%3E
[4] https://issues.apache.org/jira/browse/SOLR-9755
[4] https://lists.apache.org/thread.html/04b0b550cec79508cc80914a56676105355f58d7d676db1359336284@%3Cdev.lucene.apache.org%3E
[5] https://issues.apache.org/jira/browse/LUCENE-7966
## PMC changes:
- Jim Ferenczi was added to the PMC on December 20th.
- Dennis Gove was added to the PMC on December 23th.
- Karl Wright was added to the PMC on December 28th.
- Currently 48 PMC members.
## Committer base changes:
- Ahmet Arslan was made a committer on December 17th.
- Ignacio Vera was made a committer on January 11th.
- Jason Gerlowski was made a committer on February 8th.
- Currently 72 committers.
## Releases:
- Lucene/Solr 6.6.3 was released on March 7th.
- Lucene/Solr 7.2.0 was released on December 21st.
- Lucene/Solr 7.2.1 was released on January 15th.
- There is an ongoing discussion to release 7.3.0.
-----------------------------------------
Attachment AM: Report from the Apache Lucene.Net Project [Prescott Nasser]
-----------------------------------------
Attachment AN: Report from the Apache Mnemonic Project [Gang Wang]
Description:
Apache Mnemonic is an open-source Java library for durable object-oriented
programming on hybrid storage-class memory(e.g. NVM) space. it comes up
with durable object model (DOM) and durable computing model(DCM) and
takes full advantages of storage-class memory to simplify the code
complexity, avoid SerDe/(Un)Marshal, mitigate caching for constructing
next generation computing platform. Mnemonic makes the storing and
transmitting of massive linked objects graphs simpler and more efficient.
The performance tuning could also be mostly converged to a single point
of tuning place if based on Mnemonic to process and analyze
linked objects. The programmer is able to focus on durable object
oriented business logic instead of worrying about how to normalize/join,
serDe(un)marshal, cache and storing their linked business objects
with arbitrary complexity.
Issues:
There are no board-level issues at the moment.
Activity:
In this period of reporting, A new major improvement has been added to
Mnemonic codebase that helps the developer to remove the boilerplates
that are required to use durable classes with generic types.
Usually a custom factory proxy must be defined for each of durable
type if that is a generic type, right now, just need to instantiate a
helper class with 1 line code instead of 27 lines code;
this improvement makes code less error-prone and more concise.
With the support of some members of PMC, we may have a chance to run
Mnemonic on cutting edge server platform equipping with very large
volumn of non-volatile memory device. I think this may help us to
study the system and identify the gaps for durable models if any.
We also have fixed a major bug that may impact the user experience
on Fedora 27.
With the support of our community contributors, there are 2 conference
that has accepted our Mnemonic related topics, one is NVMW2018 as poster
and another is OSTS as presentation.
The Mnemonic code has become stable again and is ready for next release,
so the v0.11 might be released before next report.
Health Report:
Basically unchanged since the last report. Users are generally quiet
in public and no new users are appearing, but development continues.
PMC Changes:
- Currently 11 PMC members.
- No new PMC members added in the last 1 months.
Committer Base Changes:
- Currently 13 committers.
- No new committer added since the last committer on Jan. 8, 2018.
Releases:
- Last release was v0.10.0 on Mon Nov. 2017
- Still active development on next major version (0.11.0)
JIRA Activity:
- 13 JIRA tickets created since the last report (Feb. 2018)
- Also 13 JIRA tickets closed/resolved this period
Sincerely,
Gang(Gary) Wang on behalf of the Apache Mnemonic PMC
-----------------------------------------
Attachment AO: Report from the Apache Mynewt Project [Justin Mclean]
-----------------------------------------
Attachment AP: Report from the Apache OFBiz Project [Jacopo Cappellato]
## Description:
Apache OFBiz is an open source enterprise automation software project
## Issues:
there are no issues requiring board attention at this time
## Activity:
- the new release branch, named 17.12, was created in December 2017: once
stabilized by back-porting bug fixes it will be the basis of the new
releases
- vulnerability reports: a new report was received on 27/02/2018 but it was
based on the output of a static code analysis tool and we suspect it may
contain only false positives; we replied to the reporter to ask for
additional details but so far we haven't received any response; apparently
several other projects received similar reports from the same author and
they have been advised by the Security Team to discard them; we will do the
same if we do not get any further information from the reporter; apart from
this, there are no other open tickets concerning security vulnerability
reports
- the community started a documentation initiative; the goal is to move
technical and user documentation into the repository where it will be
maintained along with the codebase; after several discussions an initial
proof of concept was done; it is based on the Asciidoctor Gradle plugin and
generates PDF and html output formats; in parallel we asked for volunteers
from the community [5] to become part of an OFBiz documentation team that
would help review existing documentation and create content for the new
documentation framework; the 20 people currently in the documentation team
are made up of a mix of experienced and new contributors; a Skype call was
organised to kickstart the effort and notes from the call were posted to the
mailing list [6]
- we continue to monitor for any brand or trademark violations
- various bug fixes and enhancements have been contributed and committed to
the trunk
- as usual, more details about the community activities are published in the
official blog [1], on Twitter [2] and other social media [3]; our public
HipChat room [4] has seen low activity
## Health report:
while the committer and PMC base didn't change in the last quarter, the PMC is
in the process of inviting a new PMC member that will be announced in the next
report; as usual, the PMC is monitoring and discussing new candidates for the
PMC and the committers' groups; the community is active: a new release has
been published and the stabilization of the new release branch is in progress;
the documentation effort has generated a lot of activity and also helped
identify and engage new contributors.
## PMC changes:
- Currently 19 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Deepak Dixit on Fri Feb 24 2017
## Committer base changes:
- Currently 43 committers.
- No new committers added in the last 3 months
- Last committer addition was Akash Jain at Wed Aug 09 2017
## Releases:
- 16.11.04 was released on Tue Jan 02 2018
## Mailing list activity:
there is nothing special to report on the mailing list traffic of the last
quarter: the number of subscriptions to the user list slightly decreased but
the number of emails exchanged is steady in all lists
(slightly increased since the last quarter).
- user@ofbiz.apache.org:
- 936 subscribers (down -14 in the last 3 months)
- 544 emails sent to list (490 in previous quarter)
- dev@ofbiz.apache.org:
- 577 subscribers (up 2 in the last 3 months):
- 674 emails sent to list (687 in previous quarter)
- notifications@ofbiz.apache.org:
- 78 subscribers (down -1 in the last 3 months):
- 2385 emails sent to list (2396 in previous quarter)
## JIRA activity:
- 223 JIRA tickets created in the last 3 months
- 275 JIRA tickets closed/resolved in the last 3 months
## References
[1] https://blogs.apache.org/ofbiz/
[2] https://twitter.com/ApacheOfbiz
[3] https://www.facebook.com/Apache-OFBiz-1478219232210477/
[4] https://apache.hipchat.com/chat/room/2814115
[5] https://s.apache.org/edM8
[6] https://s.apache.org/QV3m
-----------------------------------------
Attachment AQ: Report from the Apache Olingo Project [Christian Amend]
## Description:
Apache Olingo is a Java and JavaScript library that implements the Open
Data Protocol (OData). Apache Olingo serves client and server aspects of
OData. It currently supports OData 2.0 and OData 4.0. The latter is
the OASIS version of the protocol: OASIS Open Data Protocol (OData) TC.
## Olingo Status
Olingo has no issues that would require board attention.
There has not been much activity since the January board report.
The Oasis specification is still not released and there have been no
requests for a new release in the old code lines. So no releases have been
built within the last 3 months.
Mails on the dev or user mailing list focus mostly on usage questions.
## PMC changes:
- Currently 13 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Ramesh Reddy on Thu Oct 08 2015
## Committer base changes:
- Currently 25 committers.
- No new committers added in the last 3 months
- Last committer addition was Archana Rai at Fri May 26 2017
## Releases:
- Last release was 4.4.0 on Fri Sep 01 2017
## Mailing list activity:
- dev@olingo.apache.org:
- 86 subscribers (down -1 in the last 3 months):
- 168 emails sent to list (174 in previous quarter)
- user@olingo.apache.org:
- 192 subscribers (up 1 in the last 3 months):
- 39 emails sent to list (28 in previous quarter)
## JIRA activity:
- 32 JIRA tickets created in the last 3 months
- 17 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AR: Report from the Apache Oltu Project [Antonio Sanso]
-----------------------------------------
Attachment AS: Report from the Apache OODT Project [Tom Barber]
DESCRIPTION
Apache OODT is a software framework as well as an architectural style for
the rapid construction of scientific data systems. It provides components for
data capture, curation, metadata extraction, workflow management, resource
management, and data processing.
RELEASES/DEVELOPMENT
- Last release was 1.2.2 on March 5th 2018
We resolved 1 issues for this release.
Decent activity for this period in terms of new features and commits.
Regular releases have aided activity and generated interest.
COMMUNITY
Latest committers and PMC members
Imesha Sudasingha(imesha) on 28th Aug 2017 as committer and PMC member
ISSUES
There are no issues requiring board attention at this time.
HEALTH REPORT
The project commit activity is pretty quiet, but activity continues and regular
releases contribute to a functioning and useful project.
-----------------------------------------
Attachment AT: Report from the Apache OpenNLP Project [Jörn Kottmann]
## Description:
- Apache OpenNLP library is a machine learning based toolkit for the
processing of natural language text.
## Issues:
- There are no issues requiring board attention at this time
## Activity:
- Peter Thygesen and Jörn Kottmann presented ‘Deriving Actionable Insights
from High Volume Media Streams’ at Big Data Tech Warsaw, Warsaw, Poland on
Feb 22, 2018.
- Apache OpenNLP 1.8.4 was released on Dec 24, 2017 with Jeff Zemerick as the
Release Manager.
- Jeff Zemerick published a 2017 OpenNLP retrospective here -
https://blogs.apache.org/opennlp/entry/apache-opennlp-2017-year-in
- The project has sustained activity levels and a strong user community.
- Work in progress on Deep Learning OpenNLP leveraging TensorFlow.
## Health report:
- The project has sustained activity levels and a strong user community.
## PMC changes:
- Currently 15 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Koji Sekiguchi on Mon Oct 09 2017
## Committer base changes:
- Currently 21 committers.
- No new committers added in the last 3 months
- Last committer addition was Jeff Zemerick at Wed Apr 26 2017
## Releases:
- 1.8.4 was released on Sun Dec 24 2017
## JIRA activity:
- 23 JIRA tickets created in the last 3 months
- 21 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AU: Report from the Apache OpenWebBeans Project [Mark Struberg]
## Description:
Apache OpenWebBeans is an ALv2-licensed implementations of the
"Contexts and Dependency Injection for the Java EE platform"
specifications which are defined as JSR-299 (CDI-1.0), JSR-346
(CDI-1.1 and CDI-1.2 MR) and JSR-365 (CDI-2.0).
The OWB community also maintains a small server as
Apache Meecrowave subproject. Meecrowave consists of the ASF
projects Tocmat9 + OpenWebBeans + CXF + Johnzon + log4j2.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
Activity is fine. OWB core gets a few maintenance improvements.
We also probably gonna ship another CDI-1.2 (OWB-1.7.x) maintenance release.
Meecrowave is also doing fine. Got a lot of attraction lately.
Mark Struberg presented Meecrowave and TomEE at the JavaLand Conference.
We are currently evaluating the use of the OWASP maven plugin to check
for CVE vulnerabilities. If it works out then the next step would be
to check whether this could be provided via the apache-parent pom
for other projects as well.
## Health report:
All fine. No fights, no burnout.
## PMC changes:
- Currently 13 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Reinhard Sandtner on Mon Oct 09 2017
## Committer base changes:
- Currently 20 committers.
- No new committers added in the last 3 months
- Last committer addition was John D. Ament at Mon Oct 09 2017
## Releases:
- OWB-2.0.3 was released on Sun Dec 24 2017
- Meecrowave-1.2.0 was released on Sun Dec 24 2017
- OWB-2.0.4 was released on Sat Feb 24 2018
- Meecrowave-1.2.1 was released on Thu Mar 01 2018
## Mailing list activity:
- dev@openwebbeans.apache.org:
- 69 subscribers (up 0 in the last 3 months):
- 193 emails sent to list (126 in previous quarter)
- user@openwebbeans.apache.org:
- 97 subscribers (down -2 in the last 3 months):
- 49 emails sent to list (28 in previous quarter)
## JIRA activity:
- 33 JIRA tickets created in the last 3 months
- 28 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AV: Report from the Apache Perl Project [Philippe 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.
-- Users --
The mod_perl users list is seeing little activity, as usual.
Patches and bug reports are few, but keep on coming.
-- Commiters --
Currently 22 committers.
No new changes to the committer base since last report.
Last Commiter addition was Jan Kaluza in April 2013
-- 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 AW: Report from the Apache Pig Project [Koji Noguchi]
## Description:
Apache Pig is a platform for analyzing large data sets on Hadoop. It
provides a high-level language for expressing data analysis programs,
coupled with infrastructure for evaluating these programs.
## Issues:
- There are no issues requiring board attention at this time
## Activity:
- Mostly bug fixes and enhancements being worked on. Feature work will resume
next quarter.
## Health report:
- Project activity in the community - mails, commits, jiras, etc is lower
than average for two quarters in a row. This is mostly due to continued
parental leaves, vacations and focus on other Apache projects by the
committers. Should be back to normal next quarter.
## PMC changes:
- Currently 17 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Koji Noguchi on Fri Aug 05 2016
## Committer base changes:
- Currently 30 committers.
- No new committers added in the last 3 months
- Last committer addition was Ádám Szita at Sat May 20 2017
## Releases:
- Last release was 0.17.0 on Fri Jun 16 2017
## Mailing list activity:
- dev@pig.apache.org:
- 395 subscribers (down -4 in the last 3 months):
- 351 emails sent to list (384 in previous quarter)
- user@pig.apache.org:
- 1115 subscribers (down -3 in the last 3 months):
- 2 emails sent to list (1 in previous quarter)
## JIRA activity:
- 11 JIRA tickets created in the last 3 months
- 10 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AX: Report from the Apache Pivot Project [Roger Lee Whitcomb]
Description:
Apache Pivot is an open-source platform for building installable Internet
applications (IIAs). It combines the enhanced productivity and usability
features of a modern user interface toolkit with the robustness of the
Java platform.
Issues:
There are no board-level issues at the moment.
Activity:
The long-awaited 2.1 release is closer than ever -- at least two big
refactoring projects for this release are done, and a host of other,
smaller changes have been made. Expectations are now that we will be
able to release this next quarter. A new user has recently gotten
Pivot to work with NetReXX, which is a very interesting development.
The project builds and runs with JDK 9, although no "modularization"
has taken place yet. There has been a lot of "commit" traffic from
the new development, and a larger number both of new JIRA tickets,
but also JIRA tickets fixed this quarter.
Health Report:
Basically unchanged since the last report. Users are generally quiet
and a new user appeared. Development on the next version is very
active.
PMC Changes:
- Currently 4 PMC members.
- No new PMC members added in the last 3 months.
- Last PMC re-addition was Niclas Hedhman on Wed Jan 13 2016.
Committer Base Changes:
- Currently 9 committers.
- No new changes to the committer base since last report.
- No new committers added in the last 3 months
- Last committer addition was more than 2 years ago
Releases:
- Last release was 2.0.5 on Mon Jul 3 2017
- Still active development on next major version (2.1)
Mailing List Activity:
- All mailing list activity (except private@) is up this quarter, although
subscribers are down a bit. Note: these stats for last quarter are the
same as the previous report, but differ from the "reporter" app --
probably because of timing differences for the "quarter".
- dev@pivot.apache.org
- 61 subscribers (unchanged from last report)
- 270 emails sent to list (143 in previous quarter)
- user@pivot.apache.org
- 170 subscribers (down two from last report)
- 15 emails sent to list (1 in previous quarter)
- commits@pivot.apache.org
- 19 subscribers (down -1 from last time)
- 151 emails this quarter (vs. 91 in last quarter)
- private@pivot.apache.org
- 12 subscribers (unchanged from last quarter)
- Just a few emails this quarter also
JIRA Activity:
- 16 JIRA tickets created this quarter
- Also 15 JIRA tickets closed/resolved this period
-----------------------------------------
Attachment AY: Report from the Apache Polygene Project [Paul Merlin]
Description:
Apache Polygene is a community based effort exploring Composite
Oriented Programming for domain centric application development.
Issues:
There are no issues requiring board attention at the moment.
Activity:
Activity is slow. A lot is due to individual contributors busy with
their own businesses. We have a remarkable high degree of entrepreneurs in our
mix, and we seem to be busy putting Polygene 3.0 to work. The planned 3.1
release has been postponed and probably not coming in the next quarter either,
for above mentioned reasons. In January we made one Polygene presentation at
Alibaba in Hangzhou.
Health report:
Community health continues to struggle, but as long as there is
interest and enough active PMC members, we will continue.
PMC changes:
- Currently 12 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Stanislav Muhametsin on Mon Jun 12 2017
Committer base changes:
- Currently 18 committers.
- No new changes to the committer base since last report.
- No new committers added in the last 3 months
- Last committer addition was more than 2 years ago
Releases:
- Last release was 3.0.0 on Wed Jul 26 2017
Mailing list activity:
Mailing list activity is a little bit down, but that is
expected from the lesser dev activity in general.
- dev@polygene.apache.org:
- 38 subscribers (up 1 in the last 3 months):
- 58 emails sent to list (104 in previous quarter)
JIRA activity:
- 7 JIRA tickets created in the last 3 months
- 0 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AZ: Report from the Apache Portable Runtime (APR) Project [Nick Kew]
## Description:
- The Apache Portable Runtime (APR) project creates and maintains
software libraries that provide a predictable and consistent interface
to underlying platform-specific implementations. There are three
sub-projects: APR, APR-UTIL and APR-ICONV, of which the first two
are the main focus of developer interest.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
- This has been a quiet period in a stable project with a slow but
comfortable life cycle. Activity has been low.
## Health report:
- Following a new release and a followup release for errata in 2017,
it is to be expected that activity should fall back. The underlying
condition of the project remains quiet but healthy.
## PMC changes:
- Currently 41 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Evgeny Kotkov on Tue Sep 12 2017
## Committer base changes:
- Currently 67 committers.
- No new committers added in the last 3 months
- Last committer addition was Evgeny Kotkov at Wed Sep 13 2017
## Releases:
- None in the period. Last release was a joint release of
APR-1.6.3, APR-UTIL-1.6.1 and APR-ICONV-1.2.2 in October 2017.
## Mailing list activity:
- The subscriber base remains stable. Activity is sharply down
as described above.
- dev@apr.apache.org:
- 335 subscribers (down -1 in the last 3 months):
- 59 emails sent to list (164 in previous quarter)
- bugs@apr.apache.org:
- 20 subscribers (up 0 in the last 3 months):
- 44 emails sent to list (45 in previous quarter)
## Bugzilla Statistics:
- 8 Bugzilla tickets created in the last 3 months
- 3 Bugzilla tickets resolved in the last 3 months
-----------------------------------------
Attachment BA: Report from the Apache Portals Project [David Sean Taylor]
## Description:
Apache Portals exists to promote the use of open source portal technology. We
intend to build freely available and interoperable portal software in order to
promote the use of this technology. With the Pluto project, we provide a
reference implementation for the Java portlet standard. The Jetspeed project is
a full feature enterprise open source portal. The Portals Applications project
is dedicated to providing robust, full-featured, commercial-quality, and freely
available portlet applications.
## Activity:
Apache Portals released 0 releases since the last report.
Pluto: Continued development and refinement and testing with the Portlet 3.0 TCK as we implement Portlet 3.0 support for our portal products. Expecting a 3.0.1 version will be released with next report.
Pluto: JIRA issues were closed and bugs fixed.
No additional members since last report, although we have had 3 CLAs sent in, who I believe want to become Apache committers:
Dante Wang, Vernon Singleton, Leon Chi
12 Feb 2017 - Two new PMC members added
27 April 2017 - Apache Portals Pluto team released Pluto Maven Archetypes 3.0 to support to developing new portlets to the new 3.0 spec
## Mailing list activity:
Not much activity. Some discussions around TCK implementation on the Pluto list.
Low volume activity on the Jetspeed lists.
## Issues:
We have no board-level issues at this time.
## PMC/Committership changes:
Last Added PMC Members:
12 Feb 2017 - Scott Martin Nicklaus
12 Feb 2017 - Neil Griffin
Last Added Committers:
05 August 2016 Mohd Ahmed Kahn
11 Dec 2014 Martin Scott Nicklous
11 Dec 2014 Neil Griffin
## Releases:
Pluto Maven Archetype 3.0.0 - 27 April 2017
Pluto 3.0.0 - 18 January 2017
Jetspeed 2.3.1- 09 May 2016
-----------------------------------------
Attachment BB: Report from the Apache PredictionIO Project [Donald Szeto]
## Description:
- PredictionIO is an open source Machine Learning Server built on top of
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.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- Continued community support and driving for contributions.
- Starting work on previously discussed 2018 goals.
- Google Summer of Code 2018.
## PMC changes:
- Currently 28 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Andrew Kyle Purtell on Tue Oct 17 2017
## Committer base changes:
- Currently 29 committers.
- No new changes to the committer base since last report.
## Releases:
- 0.12.1 was released on Sat Mar 10 2018
## JIRA activity:
- 13 JIRA tickets created in the last 3 months
- 14 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment BC: Report from the Apache Royale Project [Harbs]
## DESCRIPTION
Apache Royale is a new implementation of the principles of Apache Flex but
designed for JavaScript runtimes instead of Adobe Flash/AIR runtimes. Apache
Royale is designed to improve developer productivity in creating applications
for wherever Javascript runs, including browsers as well as Apache Cordova
applications, Node, etc.
## ISSUES
There are no issues requiring board attention at this time.
## RELEASES
- Apache Royale 0.9.0 was released on Jan. 28 2018.
- Apache Royale 0.9.1 was released on Feb. 13 2018.
- Apache Royale 0.9.2 in progress.
## ACTIVITY
- We have finished our first release and we're working on releasing often.
- We published convenience binaries to npm.
- Our website in now live with content.
- We have a couple of members who are active promoting Royale using social
media.
- A new contributor helped to really move the user documentation forward.
- Our ASDoc (ActionScript Doc just like JavaDoc) also went live. It is a
(almost) production Royale app.
- The ASDoc is indexed by Google, something that Flex apps had a hard time
doing, so another reason for Flex users to migrate to Royale.
- One PMC member is working hard on the default look-and-feel for Royale apps.
- The compiler was extended to be able to report on API usage in order to
understand what Flex dependencies Flex apps might have when migrating.
- Several people are investigating Royale as a way to break their Flex app's
dependencies on Flash. One user claims to be about 4 bugs short of
finishing his migration.
## COMMUNITY
- Andrew Wetmore as added as a committer on Jan. 22 2018.
- No new PMC members yet.
- There are some new names on the user and dev lists. Some of these might have
the potential of becoming actively involved.
## Mailing list activity:
Both user and dev lists have seen healthy growth:
- users@royale.apache.org:
- 47 subscribers (up 7 in the last 3 months):
- 527 emails sent to list (219 in previous quarter)
- dev@royale.apache.org:
- 68 subscribers (up 14 in the last 3 months):
- 2100 emails sent to list (1339 in previous quarter)
-----------------------------------------
Attachment BD: Report from the Apache Sentry Project [Alex Kolbasov]
## Description:
Apache Sentry is a highly modular system for providing fine grained role
based authorization to both data and metadata stored on an Apache Hadoop
Cluster.
## Issues:
There are no issues requiring board attention at this time
## Activity:
- Planning work for 2.1 release
## Health report:
- Development activity seems pretty consistent;
- New developers starting contributng to the project;
## PMC changes:
- Currently 37 PMC members.
- Kalyan Kalvagadda was added to the PMC on Sun Feb 04 2018
## Committer base changes:
- Currently 39 committers.
- Na Li was added as a committer on Mon Feb 05 2018
## Releases:
- 1.7.1 was released on Sat Dec 23 2017
- 2.0.0 was released on Dec 7 2017
## Mailing list activity:
Most of the activity is around 2.1 release planning.
- dev@sentry.apache.org:
- 94 subscribers (up 0 in the last 3 months):
- 574 emails sent to list (804 in previous quarter)
- issues@sentry.apache.org:
- 22 subscribers (down -1 in the last 3 months):
- 912 emails sent to list (1924 in previous quarter)
## JIRA activity:
- 61 JIRA tickets created in the last 3 months
- 37 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment BE: Report from the Apache ServiceMix Project [Krzysztof Sobkowiak]
### Description
Apache ServiceMix is a flexible, open-source integration container that
unifies the features and functionality of Apache ActiveMQ, Camel, CXF and
Karaf to provide a complete, enterprise-ready ESB powered by OSGi.
### Issues
There are no outstanding issues requiring board attention.
### Activity
The project focus of Apache ServiceMix is the assembly of the integration
container, the actual functionality is being maintained in related projects
like Apache Karaf, Apache CXF, Apache Camel and Apache ActiveMQ.
- We have released 3 sets of OSGi bundles
- We have refactored the Specs repository to ba able to release each spec
separately
- In the next period we are going to focus on documentation and examples
improvement as it's still outstanding theme. We are also going to focus
on releasing of e new ServiceMix version based on the newest releases of
Apache Karaf and Apache Camel. We should also focus on preparing ServiceMix
for Java 9.
### Health report
Due to winter vacation and over the year change the activity of the community
(mailing lists, JIRA, releases) has been a bit slower than during the last
period.
### PMC changes
- Currently 23 PMC members.
- Andrea Cosentino was added to the PMC on Wed Mar 15 2017
### Committer base changes
- Currently 50 committers.
- No new committers added in the last 3 months
- Last committer addition was Andrea Cosentino at Sun Mar 13 2016
### Releases
- Apache ServiceMix Bundles 2017.12 on January 01 2018
- Apache ServiceMix Bundles 2018.01 on February 08 2018
- Apache ServiceMix Bundles 2018.02 on March 07 2018
### JIRA activity
- 75 JIRA tickets created in the last 3 months
- 73 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment BF: Report from the Apache Shiro Project [Les Hazlewood]
2018 March - Board report for Apache Shiro
Apache Shiro is a powerful and flexible open-source application security
framework that cleanly handles authentication, authorization, enterprise
session management and cryptography.
We have no issues that require Board assistance at this time.
Releases:
- Last release was 1.4.0 on 05-May-2017
Community & Project:
- Mailing list traffic has returned to normal (after a lull around the
holidays last quarter). StackOverflow remains a popular alternative
for the user list.
- Feature development is planned to continue against master.
- OSGI support is a popular feature, we get an occasional one-liner
patch. However, we do NOT have a committer with sufficient experience,
which makes supporting it difficult.
- The 1.4.0 Release has been a step toward modernizing Shiro as well
as retain backwards compatibility
Last committer voted in: Andreas Kohn on 15 Jul 2016
Last PMC Member voted in: Andreas Kohn on 26 Jul 2016
-----------------------------------------
Attachment BG: Report from the Apache Sling Project [Robert Munteanu]
## Description:
Apache Sling™ is a framework for RESTful web-applications based on an
extensible content tree.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
Since the last board report we released Sling 10, Sling IDE Tooling for
Eclipse 1.2.0 and also released many other Sling modules.
## Health report:
Good activity level overall, contributions from different people continue.
## PMC changes:
- Currently 21 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Konrad Windszus on Sat Oct 01 2016
## Committer base changes:
- Currently 43 committers.
- New commmitters:
- Andreas Schaefer was added as a committer on Fri Jan 19 2018
- Chris Millar was added as a committer on Wed Jan 24 2018
- A. J. David Bosschaert was added as a committer on Fri Mar 09 2018
- Jason Bailey was added as a committer on Mon Jan 22 2018
## Releases:
- Apache Sling Commons Java Compiler 2.3.6 was released on Fri Jan 19 2018
- Apache Sling Context-Aware Configuration Impl 1.4.10 was released on Fri
Jan 19 2018
- Apache Sling File System Resource Provider 2.1.10 was released on Tue Jan
16 2018
- Apache Sling File System Resource Provider 2.1.12 was released on Wed Feb
07 2018
- Apache Sling HTL Maven Plugin 1.1.4-1.3.1 was released on Thu Feb 01 2018
- Apache Sling I18N Support 2.5.12 was released on Mon Jan 29 2018
- Apache Sling IDE Tooling for Eclipse 1.2.0 was released on Sun Jan 21 2018
- Apache Sling Installer Core 3.8.12 was released on Mon Feb 19 2018
- Apache Sling Log Tracer 1.0.6 was released on Thu Jan 11 2018
- Apache Sling Models Impl 1.4.8 was released on Mon Mar 05 2018
- Apache Sling Repoinit JCR 1.1.8 was released on Mon Feb 12 2018
- Apache Sling Repoinit Parser 1.2.2 was released on Mon Feb 12 2018
- Apache Sling Resource Resolver 1.5.36 was released on Tue Feb 20 2018
- Apache Sling Scripting Core 2.0.54 was released on Tue Dec 19 2017
- Apache Sling Scripting HTL Compiler 1.0.16 was released on Tue Dec 19 2017
- Apache Sling Scripting HTL Compiler 1.0.20-1.3.1 was released on Thu Feb 01
2018
- Apache Sling Scripting HTL Engine 1.0.46 was released on Tue Dec 19 2017
- Apache Sling Scripting HTL Engine 1.0.48-1.3.1 was released on Thu Feb 01
2018
- Apache Sling Scripting HTL JS Use Provider 1.0.26 was released on Tue Dec
19 2017
- Apache Sling Scripting HTL Java Compiler 1.0.22-1.3.1 was released on Thu
Feb 01 2018
- Apache Sling Scripting HTL Testing 1.0.6-1.3.1 was released on Thu Feb 01
2018
- Apache Sling Scripting HTL Testing Content 1.0.8-1.3.1 was released on Thu
Feb 01 2018
- Apache Sling Scripting JavaScript 3.0.4 was released on Tue Dec 19 2017
- Apache Sling ServiceUser WebConsole 1.0.0 was released on Thu Jan 18 2018
- Apache Sling Slingstart Archetype 1.0.4 was released on Wed Feb 07 2018
- Apache Sling Starter 10 was released on Sat Feb 03 2018
- Apache Sling Testing Sling Mock 1.9.12, Sling Mock 2.2.16 was released on
Mon Jan 29 2018
- Apache Sling Testing Sling Mock 2.2.18, Servlet Helpers 1.1.4 was released
on Thu Mar 01 2018
- Apache Sling Thread Support 3.2.16 was released on Wed Jan 31 2018
- Apache Sling XSS Protection API 2.0.4 was released on Mon Jan 08 2018
- JCR Oak Server 1.2.0 was released on Wed Mar 07 2018
- Pipes 2.0.2 was released on Wed Feb 07 2018
- Sling Parent 33 was released on Sat Jan 20 2018
- Testing PaxExam 1.0.0 was released on Fri Feb 02 2018
- Testing PaxExam 2.0.0 was released on Wed Mar 07 2018
- org.apache.sling.serviceusermapper-1.4.0 was released on Fri Jan 19 2018
## JIRA activity:
- 234 JIRA tickets created in the last 3 months
- 226 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment BH: Report from the Apache SpamAssassin Project [Sidney Markowitz]
Apache SpamAssassin report to Board for March 2018
SpamAssassin is a mail filter to identify spam. The project provides a
framework/engine and regular rule updates that reflect the changing nature of
spam email seen in the wild. Updated rules are generated through a combination
of hand crafted contributions and automated processing of spam and anonymized
processed non-spam that are contributed by volunteers.
Health report:
This has been another good quarter for the project.
We added one new committer and had one committer join the PMC.
Our mass-check system is running smoothly.
The users, dev, and sysadmins mailing lists have been active and healthy.
We had one member of the PMC volunteer to be a mentor and have a project
proposal for GSoC 2018. We have posted a call for applicants.
Releases:
The last release was Apache SpamAssassin version 3.4.1 on 30 April 2015.
Note that we maintain online rule updates that are continuously updated
through a combination of developer contributions and automated processing via
our mass-check facility.
In last quarterly report we said that we were resuming work on a version 3.4.2
after having put it aside to complete an update of the mass-check system
infrastructure. Our expectation that we would complete the release in January
proved to be overly optimistic. We have been making steady progress on closing
the issues that are targeted for 3.4.2, with some increase in participation by
committers. Our current hope is to have a release by mid-June.
We have previously said that this should be the last release of the 3.4 branch
before moving on with work towards 4.0, but a future 3.4.3 release is now
looking more likely in the balance of priorities to get 3.4.2 released.
Committer/PMC changes:
One new committer this quarter:
Giovanni Bechis (gbechis) 15 February 2018
One new PMC member this quarter:
Bill Cole (billcole) 5 March 2018
-----------------------------------------
Attachment BI: Report from the Apache Stanbol Project [Fabian Christ]
-----------------------------------------
Attachment BJ: Report from the Apache Storm Project [P. Taylor Goetz]
## Description:
- Apache Storm is a distributed real-time computation system.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- The Storm PMC has an ongoing discussion and effort to expand and diversify
the PMC and committership. There are currently 4 candidates under
consideration and/or vote.
- The community has decided to reduce the number of active/supported version
lines to 3 (currently 1.2.x, 1.1.x, and 1.0.x) and has updated the downoad
page and cleaned up dist.a.o accordingly.
- The community hopes to release a beta version 2.0 soon now that the 1.2.x
release line has been introduced.
- For our 1.2.0 release, an LGPL binary dependency was inadvertently
included. The issue was quickly noticed and fixed (by making the dependency
optional), and 1.2.1 was released shortly thereafter. The 1.2.0 artifacts
have been removed from distribution. I have reminded PMC members (including
myself, as the source of the mistake ;) ) the importance dependency/license
checking during release votes.
## Health report:
- Project activity continues to be fairly consistent, with periodic lulls and
bursts in activity.
- New contributors continue to engage and that engagement tends to keep up
activity levels, even as some contributors move on.
## PMC changes:
- Currently 35 PMC members.
- Erik Weathers was added to the PMC on Wed Feb 21 2018
## Committer base changes:
- Currently 36 committers.
- Erik Weathers was added as a committer on Wed Feb 21 2018
## Releases:
- 1.0.6 was released on Thu Feb 15 2018
- 1.1.2 was released on Thu Feb 15 2018
- 1.2.0 was released on Thu Feb 15 2018
- 1.2.1 was released on Sun Feb 18 2018
## JIRA activity:
- 143 JIRA tickets created in the last 3 months
- 122 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment BK: Report from the Apache Synapse Project [Isuru Udana]
## Description:
Apache Synapse is a high performance, flexible, lightweight Enterprise Service
Bus (ESB) and a mediation framework.
## Issues:
None identified.
## Activity:
After the Synapse 3.0.1 release, activity on the project has gone down in last
quarter. That is mainly because of all the active committers got busy on their
regular day to day work at the start of the year. Community is actively
responding to the security issues reported by the external people. But other
than that there wasn't much activity. We expect to get more contribution from
the community in Q2 as several people have expressed their interest in
contributing to the project. Plan is to get the next release done in Q2.
## PMC changes:
- Currently 27 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Prabath Ariyarathna on Thu May 04 2017
## Committer base changes:
- Currently 34 committers.
- No new committers added in the last 3 months
- Last committer addition was Prabath Ariyarathna at Fri Feb 10 2017
## Releases:
- Last release was 3.0.1 on Sat Dec 09 2017
-----------------------------------------
Attachment BL: Report from the Apache Tajo Project [Hyunsik Choi]
## Description:
- Tajo is an open source big data warehouse system in Hadoop for processing
web-scale data sets.
## Issues:
- there are no issues requiring board attention at this time
## Activity:
- We migrated our git repository to GitBox.
- The signatures of releases had been invalid because the PGP key used
for release was expired. We signed the release artifacts with the new PGP
key and deployed them through a PMC vote.
## Health report:
- The activity of this project has been low since 2016. However,
PMC members have been immediately reacted important issues in the community.
## PMC changes:
- Currently 13 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Hyoung Jun Kim on Sun Dec 07 2014
## Committer base changes:
- Currently 18 committers.
- No new committers added in the last 3 months
- Last committer addition was Jong-young Park at Sun May 29 2016
## Releases:
- Last release was 0.11.3 on Wed May 18 2016
## Mailing list activity:
- dev@tajo.apache.org:
- 101 subscribers (down -1 in the last 3 months):
- 25 emails sent to list (8 in previous quarter)
- issues@tajo.apache.org:
- 27 subscribers (up 0 in the last 3 months):
- 9 emails sent to list (83 in previous quarter)
- user@tajo.apache.org:
- 49 subscribers (up 0 in the last 3 months):
- 2 emails sent to list (0 in previous quarter)
## JIRA activity:
- 1 JIRA tickets created in the last 3 months
- 0 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment BM: Report from the Apache Tiles Project [Michael Semb Wever]
## Description:
Apache Tiles is a free open-sourced templating framework for Java
applications. Based upon the Composite pattern it is built to simplify
the development of user interfaces.
## Activity:
Mailing list traffic was lower this quarter. And responsive rate was
not great. Activity generally has noticably been on summer holidays
this quarter. This will be addressed and discussed in the dev ML.
The last release was Tiles-3.0.8, on November 18th 2017.
On the table are four more releases following this, in
an effort to upgrade the project to Java9.
## Health report:
There are currently two responsive PMC, other PMC help out with votes
when needed. In total there are 8 PMC members, and 10 committers.
The last PMC/committer was added on Mon Apr 23 2012,
being Nicolas LE BAS.
## Issues:
There are no issues requiring board attention at this time.
-----------------------------------------
Attachment BN: Report from the Apache Tomcat Project [Mladen Turk]
## Description:
- A Java Servlet, JavaServer Pages, Java WebSocket and Java
Unified Expression language specifications implementation.
## Issues:
- There are no issues requiring board attention at this time
## Activity:
- Continued healthy activity across multiple components and
responsiveness on both dev and user lists.
- Given the timing of the EU roadshow, we decided not to run a Tomcat
specific event in Frankfurt this Spring. Instead, we are running a
training course in Manchester UK. The event is currently predicted to
make a small (<$100) loss but there are still two weeks to go and one
more ticket sale will mean the event generates a surplus. In any
event, the current losses are more than offset by the surplus
generated from the previous event.
- In support of the training course we have started to produce ALv2
licensed training material. The long term aim is to create a large
number of modules that may then be combined into courses as required.
- We have put together a day long Tomcat track for the ApacheCon EU
Roadshow. We anticipate at least as much content, if not more, for
ApacheCon NA.
- Tomcat 9.0.4, the first stable release of the 9.0.x branch
implementing Servlet 4.0 was released this period.
- We continue to explore migrating from svn to git. The open issue /
question list is reducing as we explore each issue and reach
consensus on the way forward. Discussions continue on dev@.
## PMC changes:
- Currently 26 PMC members.
- The last addition was Huxing Zhang on 2017-05-18.
## Committer base changes:
- Currently 44 committers.
- The last addition was Michael Osipov on 2017-05-08.
- We voted to add a new committer this period but after the offer was
extended, the contributor went silent.
## Releases:
- We continue on our roughly monthly release cadence for 9.0.x and
8.5.x with the older versions releases once every 1-2 months.
- Apache Tomcat 7.0.84 was released on 2018-01-24
- Apache Tomcat 7.0.85 was released on 2018-02-13
- Apache Tomcat 8.0.49 was released on 2018-01-24
- Apache Tomcat 8.0.50 was released on 2018-02-13
- Apache Tomcat 8.5.27 was released on 2018-01-22
- Apache Tomcat 8.5.28 was released on 2018-02-11
- Apache Tomcat 8.5.29 was released on 2018-03-08
- Apache Tomcat 9.0.4 was released on 2018-01-22
- Apache Tomcat 9.0.5 was released on 2018-02-11
- Apache Tomcat 9.0.6 was released on 2018-03-08
## Trademark:
- No new trademark issues in the last 3 months
and there are currently no outstanding trademark issues that the
Apache Tomcat PMC is working on.
- Detailed history is available at:
https://svn.apache.org/repos/private/pmc/tomcat/trademark-status.txt
## Security:
- Detailed status:
http://tomcat.apache.org/security.html
- CVE-2017-12615 Remote Code Execution via JSP Upload
- CVE-2017-12616 Information Disclosure
- CVE-2017-12617 Remote Code Execution via JSP Upload
- CVE-2017-15698 Native Connector - OCSP check omitted
- CVE-2017-15706 Incorrectly documented CGI search algorithm
- CVE-2018-1304 Security constraints mapped to context root are ignored
- CVE-2018-1305 Security constraint annotations applied too late
- CVE-2018-1323 JK ISAPI Connector path traversal
-----------------------------------------
Attachment BO: Report from the Apache Trafodion Project [Pierre Smits]
## Description:
- Apache Trafodion extends the Apache Hadoop ecosystem to guarantee
transactional integrity and operational workloads for new kinds of Big
Data
applications.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- During the first week of February the official registration of new
committers Liu Yu and Sean Broeder came through.
- The community continued working on tickets and participated on the
Project's mailing list in line with previous months.
- Work continues on getting a new release out.
- Focus of the PMC remains on growing the community.
## Health report:
- During this 3rd month of our post graduation reporting cycle the
community of the project performed similarly as in the previous
2 months.
- Subscriptions to the (public) mailing lists remained on par with
previous 2 months.
- Compared to previous 3 months, the community involvement shows a 50%
growth in number of emails submitted across all mailing lists,
and an increase of 60% of JIRA tickets filed.
- The PMC regards the project as healthy.
## PMC changes:
- Currently 11 PMC members.
- No new PMC members added in the last 3 months
## Committer base changes:
- Currently 20 committers.
- New commmitters:
- Liu Yu was added as a committer on Mon Feb 05 2018
- Sean Broeder was added as a committer on Mon Feb 05 2018
## Releases:
- Last release was 2.1.0 on Mon May 01 2017
## Mailing list activity:
- dev@trafodion.apache.org:
- 105 subscribers (down -2 in the last 3 months):
- 410 emails sent to list (375 in previous quarter)
- codereview@trafodion.apache.org:
- 27 subscribers (up 0 in the last 3 months):
- 659 emails sent to list (473 in previous quarter)
- issues@trafodion.apache.org:
- 37 subscribers (down -3 in the last 3 months):
- 1114 emails sent to list (594 in previous quarter)
- user@trafodion.apache.org:
- 110 subscribers (up 0 in the last 3 months):
- 56 emails sent to list (19 in previous quarter)
- security@trafodion.apache.org:
- 6 subscribers (up 6 in the last 3 months):
- 56 emails sent to list (19 in previous quarter)
- private@trafodion.apache.org:
- 18 subscribers ( up 0 in the last 3 months)
- Currently no automated insights in number of ml postings
provided by ComDev-reporter services.
## JIRA activity:
- 154 JIRA tickets created in the last 3 months
- 93 JIRA tickets closed/resolved in the last 3 months
## Social media activity
- Followers: 250 (+4)
- Tweets: 82 (+0)
- Likes: 66 (+0)
-----------------------------------------
Attachment BP: Report from the Apache Twill Project [Terence Yim]
Apache Twill is an abstraction over Apache Hadoop YARN to reduce the
complexity of developing distributed applications.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
- Added new committer and contributor
- A new release is in voting process
## Health report:
- Project is healthy and is seeing more engagements from the community through
contributors and new committer.
## PMC changes:
- Currently 6 PMC members
- Last PMC addition was Henry Saputra on August 4, 2015
## Committer base changes:
- Currently 9 committers and 24 contributors
- One new committer added in the last 3 months
- One new contributor added in the last 3 months
- Last committer addition was Yuliya Feldman on Mar 6, 2018
- Last contributor addition was Clay B on Feb 3, 2018
## Releases:
- Last release was release 0.12.0 on August 24, 2017
## Mailing list activity:
- dev@twill.apache.org:
- 68 subscribers
- 123 emails sent to the list in past three months (43 in last report)
- commits@twill.apache.org:
- 16 subscribers
- 22 emails sent to the list in past three months (5 in last report)
## JIRA activity:
- 3 new JIRA tickets created in the last month
- 1 JIRA tickets resolved in the last month
-----------------------------------------
Attachment BQ: Report from the Apache UIMA Project [Marshall Schor]
Board report for Apache UIMA, for March 2018.
Apache UIMA's mission: the creation and maintenance of open-source
software related to the analysis of unstructured data, guided by the
UIMA Oasis Standard.
Dates:
05 Mar 2018 (new) last release - UIMA Java SDK 3.0.0
03 May 2016 (no change) last PMC addition
18 Apr 2017 (no change) last Committer addition
Releases:
05 Mar 2018 Apache UIMA Java SDK 3.0.0
07 Feb 2018 Apache UIMA Asynchronous Scaleout (UIMA-AS) 2.10.2
Activity:
Java SDK, UIMA-AS, DUCC, RUTA are
actively being worked on.
The Java SDK version 3.0.0 was finally released after
an extensive ramp up involving 2 alpha releases and
one beta release.
Our last committer addition was William Colen, who is contributing
to the C++ implementation of the UIMA framework.
Mailing list activity remains moderate.
Community:
The community continues to be moderately active.
There has been a bit of discussion around moving more to GIT;
some are in favor; others feel it would be a significant
workload increase for which they don't have time.
Issues:
No Board level issues at this time.
-----------------------------------------
Attachment BR: Report from the Apache VCL Project [Josh Thompson]
## Description:
- VCL is a modular cloud computing platform which dynamically provisions and
brokers remote access to compute resources including virtual machines,
bare-metal computers, and resources in other cloud platforms. A self-service
web portal is used to request resources and for administration. VCL became a
TLP on June 20, 2012.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- A community member has started working on some new authentication code.
Hopefully, this can lead to a new committer.
## Health report:
- Project health is being monitored. Project is largely in a steady state
though there is a slight uptick in community participation.
## PMC changes:
- Currently 7 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Aaron Coburn on Tue Jun 19 2012
## Committer base changes:
- Currently 8 committers.
- No new committers added in the last 3 months
- Last committer addition was Young Hyun Oh at Sun Dec 08 2013
## Releases:
- Last release was 2.5 on Thu Aug 17 2017
## Mailing list activity:
- Development efforts have not started back up after our last release. So,
there has been little dev list traffic. User list traffic is about the same
as last quarter from people upgrading to the latest release.
- dev@vcl.apache.org:
- 125 subscribers (up 1 in the last 3 months):
- 16 emails sent to list (16 in previous quarter)
- user@vcl.apache.org:
- 166 subscribers (up 0 in the last 3 months):
- 36 emails sent to list (39 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 BS: Report from the Apache Wicket Project [Martijn Dashorst]
-----------------------------------------
Attachment BT: 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 of the Xalan C/C++
library.
The libraries need little work to make sure the code base is operational
in the newer software development studios and platforms.
ISSUES FOR THE BOARD
None.
CURRENT ACTIVITY
Most activity has been through JIRA issue tracking. The email lists
have seen little activity.
There has been some work to put patches into JIRA but we still need to get
the patches integrated into the XALAN-C for an update release. The contributors
are active with other source projects and currently have little time to
devote on the Xalan C/C++ library. There still is some activity devoted
to the Xalan Java library.
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.
The libraries need little work to make sure the code base is operational
in the newer software development studios and platforms.
BRANDING ISSUES
None.
-----------------------------------------
Attachment BU: Report from the Apache Xerces Project [Michael Glavassevich]
Xerces-J
Since November, there were some minor improvements made for XML Schema 1.1 and
the documentation for that feature.
There was one individual who expressed an interest in helping with the
Xerces-J 2.12.0 release. It seemed like they were going to work with their
employer to get a CLA on file, but we have not heard back from them yet.
Mailing list traffic has been moderate; roughly 100+ posts on the j-dev and
j-users lists since the beginning of November 2017.
No new releases since the previous report. The latest release is Xerces-J
2.11.0 (November 30th, 2010).
Xerces-C
Xerces-C 3.2.1 was released at the end of February which addresses a security
issue (CVE-2017-12627) and fixes some other bugs.
Mailing list traffic has been high; roughly 360+ posts on the c-dev and
c-users lists since the beginning of November 2017.
The latest release is Xerces-C 3.2.1 (February 28th, 2018).
Xerces-P
Nothing in particular to report. There was no development activity over the
reporting period.
XML Commons
No activity over the reporting period.
Committer / PMC Changes
The most recent committers were added in April 2017 (Xerces-C) and May 2017
(Xerces-J).
No new PMC members since the last report. The most recent addition to the PMC
was in June 2016.
Three committers have committed changes to SVN since November 2017.
Apache Project Branding Requirements
The project logo still needs a "TM" to be added to it.
-----------------------------------------
Attachment BV: Report from the Apache Yetus Project [Allen Wittenauer]
## Description:
Apache Yetus provides libraries and tools that enable contribution and release
processes for software projects.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
No new PMC members added in the last three months; our Last PMC addition was
Ajay Yadav on Thu Dec 01 2016. There are currently 8 PMC members.
Akira Ajisaka was added as a committer on Tue Feb 06 2018. There are
currently 12 committers.
Since the last report, version 0.7.0 was released with the resource related
changes. This release, however, was problematic in a few ways. The ASF JIRA
upgrade broke patch precommit testing for a large number of projects. After
getting changes in place, this required the project to "rush" a release to get
these other projects back to functional. Unfortunately, this revealed that
the PMC's ability to get the necessary votes for a release promptly doesn't
appear to be realistic. There has been some discussion in the past quarter to
rethink how we do releases to make this possible.
## Health report:
Activity is significantly down, despite reliance on the project being up. The
software itself is relatively stable, so that may be the reason why.
## Releases:
- 0.7.0 was released on Fri Jan 26 2018
## Mailing list activity:
- dev@yetus.apache.org:
- 44 subscribers (down -1 in the last 3 months):
- 23 emails sent to list (67 in previous quarter)
- notifications@yetus.apache.org:
- 16 subscribers (up 0 in the last 3 months):
- 87 emails sent to list (445 in previous quarter)
## JIRA activity:
- 25 JIRA tickets created in the last 3 months
- 13 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment BW: Report from the Apache ZooKeeper Project [Flavio Paiva Junqueira]
## Description:
Apache ZooKeeper is a system for distributed coordination. It enables
the implementation of a variety of primitives and mechanisms that are
critical for safety and liveness in distributed settings, e.g.,
distributed locks, master election, group membership, and configuration.
## Issues:
No issue requiring board attention
## Activity:
- Community is working towards releasing 3.5.4. There are currently 10
listed blocker issues.
- Release 3.4.11 had a regression and 3.4.12 is on the way, we are ready
to cut a release candidate.
- There has been questions and work in the security list around
vulnerabilities, but there has been no disclosure in this period.
## Health report:
The project activity is currently at a low. It has been fairly stable
during the past year, but we are still suffering from the
fact that a good chunk of the project committers are busy with other
activities. Our goal has been to work with contributors to offer them
committership to guarantee that we have a continuous flow of
contributions being merged.
## PMC changes:
- Currently 13 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Michael Han on Wed Jun 21 2017
## Committer base changes:
- Currently 22 committers.
- Abraham Fine was added as a committer on Tue Jan 30 2018
## Releases:
- Last release was 3.4.11 on Wed Nov 08 2017
## Mailing list activity:
There has been a 15% and 35% drop in the dev and user lists,
respectively. This is significant and we attribute it to the
fact that we haven’t had enough committer activity in the
project during this period.
- dev@zookeeper.apache.org:
- 512 subscribers (down -9 in the last 3 months):
- 2052 emails sent to list (2426 in previous quarter)
- user@zookeeper.apache.org:
- 1236 subscribers (up 8 in the last 3 months):
- 77 emails sent to list (118 in previous quarter)
## JIRA activity:
- 46 JIRA tickets created in the last 3 months
- 25 JIRA tickets closed/resolved in the last 3 months
------------------------------------------------------
End of minutes for the March 21, 2018 board meeting.
Index