Index
Links: 2017 - All years
- Original The Apache Software Foundation
Board of Directors Meeting Minutes
November 15, 2017
1. Call to order
The meeting was scheduled for 10:30am Pacific and began at 10:31
when a sufficient attendance to constitute a quorum was
recognized by the chairman.
Other Time Zones: https://timeanddate.com/s/3d52
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 - left at 11:35
Jim Jagielski
Chris Mattmann
Brett Porter
Phil Steitz
Mark Thomas
Directors Absent:
none
Executive Officers Present:
Ross Gardler
Sam Ruby
Craig L Russell - left at 11:30
Executive Officers Absent:
Kevin A. McGrail
Ulrich Stärk
Guests:
Daniel Gruno
Greg Stein
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 October 18, 2017
See: board_minutes_2017_10_18.txt
Approved by General Consent.
4. Executive Officer Reports
A. Chairman [Phil]
I had calls with Sam and Greg this past month, discussing a range of
topics relating to the two things that I am working on at the
foundation level now: 1) the 5-year strategic plan and 2) ASF document
retention and access policy. I received some great feedback on the
members list on the strategic plan components and I have started work
on a plan draft, which I will make available in the ASF GoogleDocs
space. I would like to reserve time at next month’s board meeting to
discuss the plan.
There has been some discussion recently on how to streamline
communications between the Board and PMCs, or more specifically how to
make the PMC Chair’s job more manageable by reducing the number of
email messages that Chairs need to read. One item that was suggested
for suppression is Board comments on project reports. Thinking about
that, and discussing with Sam, I have decided to start including a
summary of recent Board feedback in this report. Feedback on my
feedback summary is of course welcome. If this turns out to be
effective, I will propose that we suppress copying board@apache.org on
report comments.
There were quite a few positive comments over the last month thanking
PMCs for producing informative and thoughtful reports. In general,
the positive comments were in response to reports that gave a clear
picture of the state of a project, interpreting data rather than just
presenting it. An excellent example is this month’s HTTP Server
report. Critical comments centered on a few recurring themes:
1. Reminders to always include the dates when the last committer and
PMC member were added to the project.
2. Reminders that mailing list and / or JIRA statistics presented by
themselves (i.e. not in support of a statement related to project
health or issues faced by the project) can be omitted.
3. Requests to affirm that there is sufficient PMC oversight for the
project.
4. Reminders that no response has been received to a comment that
requires a response (comments that require response are flagged in
Whimsy. I am happy to personally respond to questions regarding
whether or not a specific comment requires a response of if a proposed
response is adequate).
Constructive feedback also followed some common themes:
1. Projects considering formal criteria for committership are
encouraged to be careful setting the bar too high or making the
criteria too complex.
2. Projects organizing meetings, meet-ups or other in-person events
need to make sure that either the events do not have any specific
bearing on the project or a) they are open to all interested parties
and b) discussions and any proposed decisions are brought back to the
project dev list.
3. Private mailing lists should be used sparingly, only for issues
that can’t be discussed on the public dev list.
4. Votes for PMC Chair rotations and / or committer / PMC nominations
should always be closed and actioned.
B. President [Sam]
Items requiring board attention:
* Fundraising VP resolution. I believe that the bylaws question has
been resolved. I believe that need for a VP title has been
established. I see that there has been some calls for additional
process; I don't see the need for such, but if the board chooses
to table this resolution again, I ask that clear guidance be
provided.
* Conferences discussion item. I suggest that this not merely be
discussed as if it were a one time expense, but as input to
the five year plan.
* In order to reach they goal of having a top-down five year plan by
year end, there really should have been some draft numbers produced
by now. Certainly no later than by the end of this month so that they
can be approved in the next board meeting.
Overall, expenses remain under control. Working with Virtual,
it was determined that Infrastructure incorrectly forecasted FY18
costs. This should be covered this year, but may result in the
need to revise upwards future budgets.
Income appears to be on track, with the normal comment about sponsor
timing considerations make this difficult to be sure.
Ross and I talked about what can be done to ensure that the EA is
fully utilized, and we are exploring a number of options.
Brand Management continues to work to produce a proposal for board
consideration. Ideally, this would also be included in the five
year plan discussion.
Additionally, please see Attachments 1 through 7.
C. Treasurer [Ulrich]
Virtual Report:
Here is a summary of the Foundation’s performance for the first Six
months of FY18.
Cash on Oct 31st, 2017 was $1,710K, which is down $24.3K from last
month’s ending balance (Sept 17) of $1,734.3K, due to the timing of
some Sponsor payments and Payables released. The Oct 2017 cash
balance is down $86.8K from the Oct 2016 month end balance of
$1,796.8K. The Oct 2017 ending cash balance of $1,710K represents a
cash reserve of 14.9 months based on the FY18 Cash forecast average
monthly spending of $114.6K/month. The ASF reserve continues to be
very healthy for an organization of ASF’s size, with an FY18 YE
estimate of 12.4 month’s cash reserve.
Regarding the YTD Cash P&L, we continue to have a very strong showing
against our FY18budget at the halfway point of the year, however as I
noted last month the timing of Sponsor payments and Payables releases
plays a big part in how well we perform financially each month. This
month while we are under the FY 18 plan for Revenue, we are also under
plan for Expenses, by more, and that gets us to a better actual Net
Income as compared to our FY18 Budget. Therefore, we need to
continue to focus on our new sponsors but we also cannot afford to
take any focus away from our existing sponsors as that was how the
FY18 budget was constructed. The Fundraising team continues to do an
excellent job in both areas, servicing both new and existing Sponsors.
With total actual Revenue, as of Oct 31st, 2017, of $826.1K, we are
67.4% of the way to our total Revenue budget for FY18 of $1,226.5K.
Regarding Sponsor revenue, specifically, we have received so far in
the first six months of FY18, $744.6K, which has us 68.7% to our
budgeted Sponsor revenue goal of $1,084K for FY18, which is fantastic,
at the halfway point of the current Fiscal Year. We remain
conservative in our forecasting, showing modest annual increases in
annual Sponsorship and Donations, due to actual collected amounts such
as those coming from Hopsie (which was not budgeted for FY 18).
YTD expenses, through Oct 31st, 2017 are under budget by $68.4K. All
depts. are either under budget or at budget, (Infra, YTD, is slightly
over budget by $0.2K or flat to FY18 budget YTD which is another $10K
improvement vs Budget, from last month). I also completed a review of
the Forecast for expenses, in Oct and have either spoken to or had
email correspondence with the Dept. heads after last month’s close and
have incorporated those discussions in the current forecast for the
last six months of FY18. We will continue to monitor the actual vs
budget as we move through the remaining six months of FY18 and we will
stay in contact with the dept. heads as we close each month going
forward so that we have a clearer picture for the remainder of the
Fiscal year.
Regarding Net Income (NI), YTD for FY18 the ASF finished with a
positive $194.7K NI vs a budgeted negative <$156.3K> NI or $351K ahead
of FY 18 Budget at the half year for Net Income. With the current
conservative forecasted revenue, and expenses for the remainder of FY
18, we are estimating a $-97K negative NI for FY18 vs a budgeted NI
loss of -$167.8K or about $70.8K better NI than the FY18 budget. I
would also like to point out that YTD 18 vs YTD 17 we are $336.4K
ahead in Revenue while Expenses were only $140.8K ahead year over
year, for a $195.6K increase in Net Income year over year ($194.7K
positive NI in FY18 vs <-$.84K> NI in FY 17.) Again, I want to
congratulate the entire Organization on these very positive numbers as
we have arrived at the halfway point of FY 18, though we do need to
continue to keep these efforts up as we move through the back half of
FY 18 and continue to give Fundraising all the support we can as we
move forward, while keeping an eye on our expenses at the same time.
We have been in contact with the CPA and we will be getting the Cash
Basis Audit underway shortly, and we will keep everyone updated as to
its progress once it starts.
Board Summary Financials:
Current Balances:
Citizens Money Market 1,495,276.23
Citizens Checking 214,684.63
Paypal - ASF 0.00
Total Checking/Savings 1,709,960.86
Oct-17 Budget Variance
Income Summary:
Inkind Revenue 0.00 0.00 0.00
Public Donations 12,707.53 3,415.15 9,292.38
Sponsorship Program 70,000.00 105,000.00 -35,000.00
Programs Income 0.00 0.00 0.00
Other Income 3,137.43 0.00 3,137.43
Interest Income 629.92 292.92 337.00
Total Income 86,474.88 108,708.07 -22,233.19
Expense Summary:
In Kind Expense 0.00 0.00 0.00
Infrastructure 62,255.13 72,187.44 -9,932.31
Sponsorship Program 2,000.00 5,000.00 -3,000.00
Programs Expense 0.00 0.00 0.00
Publicity 13,628.17 25,375.00 -11,746.83
Brand Management 22,156.06 7,416.67 14,739.39
Conferences 0.00 4,418.00 -4,418.00
Travel Assistance Committee 0.00 17,500.00 -17,500.00
Tax and Audit 2,150.00 6,000.00 -3,850.00
Treasury Services 3,350.00 3,500.00 -150.00
General & Administrative 8,281.57 12,637.21 -4,355.64
Total Expense 113,820.93 154,034.32 -40,213.39
Net Income -27,346.05 -45,326.25 17,980.20
YTD 2018 Budget Variance
Income Summary:
Inkind Revenue 0.00 0.00 0.00
Public Donations 54,264.79 15,409.61 38,855.18
Sponsorship Program 744,612.08 526,250.00 218,362.08
Programs Income 15,100.00 0.00 15,100.00
Other Income 8,402.54 0.00 8,402.54
Interest Income 3,709.76 1,757.52 1,952.24
Total Income 826,089.17 543,417.13 282,672.04
Expense Summary:
In Kind Expense 0.00 0.00 0.00
Infrastructure 416,488.29 416,250.56 237.73
Sponsorship Program 12,788.66 19,250.00 -6,461.34
Programs Expense 0.00 0.00 0.00
Publicity 78,466.36 100,000.00 -21,533.64
Brand Management 36,187.57 44,500.02 -8,312.45
Conferences 4,987.62 8,418.00 -3,430.38
Travel Assistance Committee 2,191.81 22,500.00 -20,308.19
Tax and Audit 2,150.00 6,000.00 -3,850.00
Treasury Services 19,850.00 20,450.00 -600.00
General & Administrative 58,275.41 62,373.07 -4,097.66
Total Expense 631,385.72 699,741.65 -68,355.93
Net Income 194,703.45 -156,324.52 351,027.97
Assistant Treasurer Report:
* Transferwise.com account setup for the ASF. Thanks to all directors
for their info.
* We are now storing some ASF data for Treasurer and Fundraising such
as these reports up on the G Suite instance. Custom URLs are now setup thanks to
Infra’s help with DNS. drive.gsuite.cloud.apache.org, for example.
* Working with Infra and President to greenlight G Suite for the
foundation. Expect to move dropbox services to G Suite in the near future and hand off
administration to Infra currently just pending multi factor auth setup for Greg.
Soon, it will be considered just another system under operations control and Superadmin
(like root/wheel) will be controlled by existing policies in place now for infra.
* Met with Boston Private Bank and Virtual with Uli about CDARS and
designed a multi-tiered approach for different sums on different schedules since vetted
by Treasurer with Virtual and the Bank, Boston Private. See
https://docs.google.com/document/d/1JAYMfSuXf5aK6dUJUR39omwT62uuiqYKINUNZG8sH1I/edit#
CDARS paperwork is with Uli for review/signature.
* D&O Policy was issued. Added to svn:
https://svn.apache.org/repos/private/foundation/legal/2017%20Directors%20and%20Officers%20Policy.pdf
* Working on getting backups of the ASF Quickbooks file at Virtual
submitted periodically to SVN for an extra backup. Have reviewed Virtual’s internal
backup regimen and it is excellent.
* Certificate of Residence for the ASF pending IRS.
* I validated a volunteer hour request by Microsoft
* Previously Reported Items Still Tracking w/Nothing to Report
- Contribution Language for Car Donations - No update
- Payment Privacy changes to move away from Dropbox, etc. Virtual will
be documenting what they do now which is working - No update since last meeting.
- Network for Good - Missing a $125 check - Will ask for a reissue. No
Update
D. Secretary [Craig]
Work is continuing on a streamlined approach to inviting new
contributors, committers, and project management committee members to
submit ICLAs. For a demo, please visit whimsy.apache.org/project/icla
The day-to-day workload on secretary remains well within bounds.
In October, 86 iclas, three cclas, and one grant were received and
filed.
E. Executive Vice President [Ross]
Infrastructure
==============
The team have investigated an oddity in our staffing expenditures as
identified last month. It seems that Infra incorrectly foretasted FY18
costs from the FY17 actuals. This means there is no budget for the
open headcount. However, other areas of the infra budget are in a good
state and with ongoing and predicted savings in other areas it is
expected that the team will come within its total budget.
In other news there was an outage on mail-archives.a.o that took a
while to correct. It highlighted our ongoing issues with services on
old hardware, old operating systems, and non-puppetized services. This
has been mitigated and work to improve aging services continues,
Marketing and Publicity
=======================
Sponsor Ambassador program work continues, along with general
awareness raising around what the foundation does (e.g. published
"Success at Apache: Scratch Your Own Itch" https://s.apache.org/7Amk ,
which was also published as a cover feature in JAX Magazine's special
issue on Open Source).
The recent turmoil around high profile security breaches has died down
and PR and Marketing activity is mostly back to normal.
Conferences
===========
VP Conferences continues to explore options for ApacheCon events after
having confirmed with the broader community that such a thing is still
needed. Input welcome on planners@apachecon.com mailing list, which is
open to members.
TAC
===
Nothing to report (no events planned)
F. Vice Chairman [Jim]
I am working on a short video introduction for COSCon 2017. Other than that, nothing to report.
Executive officer reports approved as submitted by General Consent.
5. Additional Officer Reports
A. VP of W3C Relations [Andy Seaborne / Brett]
See Attachment 8
B. Apache Legal Affairs Committee [Chris Mattmann]
See Attachment 9
C. Apache Security Team Project [Mark J. Cox / Phil]
See Attachment 10
Additional officer reports approved as submitted by General Consent.
6. Committee Reports
Summary of Reports
The following reports required further discussion:
# ACE [rb]
# Axis [cm]
# Giraph [mt]
# Hama [rb]
# Libcloud [bd]
# POI [bd]
A. Apache ACE Project [Marcel Offermans / Shane]
No report was submitted.
@Phil: draft Attic resolution for ACE
B. Apache Ambari Project [Yusaku Sako / Jim]
See Attachment B
C. Apache Ant Project [Jan Materne / Chris]
See Attachment C
D. Apache Axis Project [Deepal Jayasinghe / Mark]
See Attachment D
@Mark: follow up with PMC; ask them to report for the next two
months
E. Apache BookKeeper Project [Sijie Guo / Rich]
No report was submitted.
F. Apache Brooklyn Project [Richard Downer / Ted]
See Attachment F
G. Apache Buildr Project [Antoine Toulme / Bertrand]
No report was submitted.
H. Apache Cassandra Project [Nate McCall / Ted]
See Attachment H
I. Apache Celix Project [Alexander Broekhuis / Jim]
No report was submitted.
J. Apache Clerezza Project [Hasan Hasan / Phil]
See Attachment J
K. Apache Cocoon Project [Cédric Damioli / Shane]
See Attachment K
L. Apache Community Development Project [Sharan Foga / Brett]
See Attachment L
M. Apache CouchDB Project [Jan Lehnardt / Bertrand]
See Attachment M
N. Apache Creadur Project [Brian E Fox / Mark]
See Attachment N
O. Apache Crunch Project [Josh Wills / Chris]
See Attachment O
P. Apache DeltaSpike Project [Mark Struberg / Rich]
See Attachment P
Q. Apache DRAT Project [Chris Mattmann]
See Attachment Q
R. Apache Drill Project [Aman Sinha / Brett]
See Attachment R
S. Apache Empire-db Project [Rainer Döbele / Phil]
See Attachment S
T. Apache Flume Project [Hari Shreedharan / Bertrand]
See Attachment T
U. Apache Forrest Project [David Crossley / Shane]
See Attachment U
V. Apache Geode Project [Mark Bretl / Jim]
See Attachment V
W. Apache Giraph Project [Avery Ching / Ted]
See Attachment W
@Mark: follow up with PMC to ensure three active PMC members
X. Apache Gora Project [Lewis John McGibbney / Chris]
See Attachment X
Y. Apache Groovy Project [Guillaume Laforge / Rich]
See Attachment Y
Z. Apache Hama Project [Edward J. Yoon / Mark]
No report was submitted.
@Rich: follow up with PMC
AA. Apache HTTP Server Project [Daniel Gruno / Phil]
See Attachment AA
AB. Apache HttpComponents Project [Asankha Chamath Perera / Jim]
See Attachment AB
AC. Apache Ignite Project [Denis A. Magda / Bertrand]
See Attachment AC
AD. Apache Incubator Project [John D. Ament / Chris]
See Attachment AD
AE. Apache JSPWiki Project [Juan Pablo Santos Rodríguez / Shane]
See Attachment AE
AF. Apache jUDDI Project [Alex O'Ree / Ted]
See Attachment AF
AG. Apache Juneau Project [James Bognar / Brett]
See Attachment AG
AH. Apache Kafka Project [Jun Rao / Mark]
See Attachment AH
AI. Apache Kibble Project [Rich Bowen]
See Attachment AI
AJ. Apache Knox Project [Larry McCay / Rich]
See Attachment AJ
AK. Apache Kylin Project [Luke Han / Mark]
See Attachment AK
AL. Apache Lens Project [Amareshwari Sriramadasu / Brett]
See Attachment AL
AM. Apache Libcloud Project [Tomaž Muraus / Jim]
See Attachment AM
AN. Apache Logging Services Project [Matt Sicker / Ted]
See Attachment AN
AO. Apache Lucene.Net Project [Prescott Nasser / Shane]
No report was submitted.
AP. Apache ManifoldCF Project [Karl Wright / Chris]
See Attachment AP
AQ. Apache Marmotta Project [Jakob Frank / Rich]
See Attachment AQ
AR. Apache Mesos Project [Benjamin Hindman / Bertrand]
See Attachment AR
AS. Apache MetaModel Project [Kasper Sørensen / Phil]
See Attachment AS
AT. Apache Oltu Project [Antonio Sanso / Bertrand]
No report was submitted.
AU. Apache Oozie Project [Robert Kanter / Chris]
See Attachment AU
AV. Apache Open Climate Workbench Project [Michael James Joyce / Rich]
See Attachment AV
AW. Apache OpenJPA Project [Mark Struberg / Shane]
See Attachment AW
AX. Apache Perl Project [Philippe Chiasson / Mark]
No report was submitted.
AY. Apache Phoenix Project [James R. Taylor / Ted]
See Attachment AY
AZ. Apache POI Project [Dominik Stadler / Phil]
See Attachment AZ
BA. Apache PredictionIO Project [Donald Szeto / Brett]
See Attachment BA
BB. Apache Qpid Project [Robert Gemmell / Jim]
See Attachment BB
BC. Apache Ranger Project [Selvamohan Neethiraj / Brett]
See Attachment BC
BD. Apache REEF Project [Byung-Gon Chun / Rich]
See Attachment BD
BE. Apache River Project [Peter Firmstone / Phil]
No report was submitted.
BF. Apache RocketMQ Project [Xiaorui Wang / Chris]
See Attachment BF
BG. Apache Roller Project [David M. Johnson / Mark]
See Attachment BG
BH. Apache Royale Project [Harbs / Jim]
See Attachment BH
BI. Apache Santuario Project [Colm O hEigeartaigh / Bertrand]
See Attachment BI
BJ. Apache Serf Project [Bert Huijben / Ted]
See Attachment BJ
BK. Apache SIS Project [Martin Desruisseaux / Shane]
See Attachment BK
BL. Apache Spark Project [Matei Alexandru Zaharia / Chris]
See Attachment BL
BM. Apache Stanbol Project [Fabian Christ / Jim]
No report was submitted.
BN. Apache Subversion Project [Stefan Sperling / Rich]
See Attachment BN
BO. Apache Syncope Project [Francesco Chicchiriccò / Shane]
See Attachment BO
BP. Apache SystemML Project [Jon Deron Eriksson / Mark]
See Attachment BP
BQ. Apache TomEE Project [David Blevins / Bertrand]
No report was submitted.
BR. Apache Turbine Project [Georg Kallidis / Phil]
See Attachment BR
BS. Apache Usergrid Project [Todd Nine / Ted]
See Attachment BS
BT. Apache Velocity Project [Nathan Bubna / Brett]
See Attachment BT
BU. Apache Web Services Project [Sagara Gunathunga / Shane]
No report was submitted.
BV. Apache Whimsy Project [Sam Ruby / Brett]
See Attachment BV
BW. Apache Xalan Project [Steven J. Hathaway / Bertrand]
No report was submitted.
BX. Apache Xerces Project [Michael Glavassevich / Ted]
See Attachment BX
BY. Apache XML Graphics Project [Glenn Adams / Mark]
See Attachment BY
Committee reports approved as submitted by General Consent.
7. Special Orders
A. Change the Apache Felix Project Chair
WHEREAS, the Board of Directors heretofore appointed Carsten Ziegeler
(cziegeler) to the office of Vice President, Apache Felix, and
WHEREAS, the Board of Directors is in receipt of the resignation
of Carsten Ziegeler from the office of Vice President, Apache
Felix and
WHEREAS, the Project Management Committee of the Apache Felix
project has chosen by vote to recommend Karl Pauls (pauls)
as the successor to the post;
NOW, THEREFORE, BE IT RESOLVED, that Carsten Ziegeler is
relieved and discharged from the duties and responsibilities of
the office of Vice President, Apache Felix, and
BE IT FURTHER RESOLVED, that Karl Pauls be and hereby is appointed
to the office of Vice President, Apache Felix, to serve in
accordance with and subject to the direction of the Board of
Directors and the Bylaws of the Foundation until death, resignation,
retirement, removal or disqualification, or until a successor is
appointed.
Special Order 7A, Change the Apache Felix Project Chair, was
approved by Unanimous Vote of the directors present.
B. Change the Apache Sling Project Chair
WHEREAS, the Board of Directors heretofore appointed Carsten Ziegeler
(cziegeler) to the office of Vice President, Apache Sling, and
WHEREAS, the Board of Directors is in receipt of the resignation
of Carsten Ziegeler from the office of Vice President, Apache
Sling and
WHEREAS, the Project Management Committee of the Apache Sling
project has chosen by vote to recommend Robert Munteanu (rombert)
as the successor to the post;
NOW, THEREFORE, BE IT RESOLVED, that Carsten Ziegeler is
relieved and discharged from the duties and responsibilities of
the office of Vice President, Apache Sling, and
BE IT FURTHER RESOLVED, that Robert Munteanu be and hereby is appointed
to the office of Vice President, Apache Sling, 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 Sling Project Chair, was
approved by Unanimous Vote of the directors present.
C. Establish the Apache Mnemonic 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 transparent nonvolatile hybrid memory
oriented library for Big data, High-performance computing, and
Analytics.
NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
(PMC), to be known as the "Apache Mnemonic Project", be and hereby is
established pursuant to Bylaws of the Foundation, and be it further
RESOLVED, that the Apache Mnemonic Project be and hereby is
responsible for the creation and maintenance of software related to a
transparent nonvolatile hybrid memory oriented library for Big data,
High-performance computing and Analytics; and be it further
RESOLVED, that the office of "Vice President, Apache Mnemonic" 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
Mnemonic Project, and to have primary responsibility for management of
the projects within the scope of responsibility of the Apache Mnemonic
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 Mnemonic
Project:
* Andrew Kyle Purtell <apurtell@apache.org>
* Debojyoti Dutta <ddutta@apache.org>
* Gang Wang <garyw@apache.org>
* Hao Cheng <chhao01@apache.org>
* James R. Taylor <jamestaylor@apache.org>
* Johnu George <johnu@apache.org>
* Kai Zheng <drankye@apache.org>
* Patrick D. Hunt <phunt@apache.org>
* Rakesh Radhakrishnan <rakeshr@apache.org>
* Uma Maheswara Rao G <umamahesh@apache.org>
* Yanping Wang <yanpingw@apache.org>
NOW, THEREFORE, BE IT FURTHER RESOLVED, that Gang Wang be appointed to
the office of Vice President, Apache Mnemonic, to serve in accordance
with and subject to the direction of the Board of Directors and the
Bylaws of the Foundation until death, resignation, retirement, removal
or disqualification, or until a successor is appointed, and be it
further
RESOLVED, that the initial Apache Mnemonic PMC be and hereby is tasked
with the creation of a set of bylaws intended to encourage open
development and increased participation in the Apache Mnemonic
Project; and be it further
RESOLVED, that the Apache Mnemonic Project be and hereby is tasked
with the migration and rationalization of the Apache Incubator
Mnemonic podling; and be it further
RESOLVED, that all responsibilities pertaining to the Apache Incubator
Mnemonic podling encumbered upon the Apache Incubator PMC are
hereafter discharged.
Special Order 7C, Establish the Apache Mnemonic Project, was
approved by Unanimous Vote of the directors present.
D. Establish the Apache Impala 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 high-performance distributed SQL engine.
NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
(PMC), to be known as the "Apache Impala Project", be and hereby is
established pursuant to Bylaws of the Foundation; and be it further
RESOLVED, that the Apache Impala Project be and hereby is responsible
for the creation and maintenance of software related to a
high-performance distributed SQL engine; and be it further
RESOLVED, that the office of "Vice President, Apache Impala" 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 Impala
Project, and to have primary responsibility for management of the
projects within the scope of responsibility of the Apache Impala
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 Impala
Project:
* Alex Behm <abehm@apache.org>
* Bharath Vissapragada <bharathv@apache.org>
* Brock Noland <brock@apache.org>
* Carl Steinbach <cws@apache.org>
* Casey Ching <casey@apache.org>
* Daniel Hecht <dhecht@apache.org>
* Dimitris Tsirogiannis <dtsirogiannis@apache.org>
* Henry Robinson <henry@apache.org>
* Ishaan Joshi <ishaan@apache.org>
* Jim Apple <jbapple@apache.org>
* John Russell <jrussell@apache.org>
* Juan Yu <jyu@apache.org>
* Lars Volker <lv@apache.org>
* Lenni Kuff <lskuff@apache.org>
* Marcel Kornacker <marcel@apache.org>
* Martin Grund <mgrund@apache.org>
* Matthew Jacobs <mjacobs@apache.org>
* Michael Brown <mikeb@apache.org>
* Michael Ho <kwho@apache.org>
* Sailesh Mukil <sailesh@apache.org>
* Skye Wanderman-Milne <skye@apache.org>
* Taras Bobrovytsky <tarasbob@apache.org>
* Tim Armstrong <tarmstrong@apache.org>
* Todd Lipcon <todd@apache.org>
NOW, THEREFORE, BE IT FURTHER RESOLVED, that Jim Apple be appointed to
the office of Vice President, Apache Impala, to serve in accordance
with and subject to the direction of the Board of Directors and the
Bylaws of the Foundation until death, resignation, retirement, removal
or disqualification, or until a successor is appointed; and be it
further
RESOLVED, that the initial Apache Impala PMC be and hereby is tasked
with the creation of a set of bylaws intended to encourage open
development and increased participation in the Apache Impala Project;
and be it further
RESOLVED, that the Apache Impala Project be and hereby is tasked with
the migration and rationalization of the Apache Incubator Impala
podling; and be it further
RESOLVED, that all responsibilities pertaining to the Apache Incubator
Impala podling encumbered upon the Apache Incubator PMC are hereafter
discharged.
Special Order 7D, Establish the Apache Impala Project, was
approved by Unanimous Vote of the directors present.
E. Change the Apache Axis Project Chair
WHEREAS, the Board of Directors heretofore appointed Deepal Jayasinghe
Smith (djayasinghe) to the office of Vice President, Apache Axis, and
WHEREAS, the Board of Directors is in receipt of the resignation of
Deepal Jayasinghe from the office of Vice President, Apache Axis, and
WHEREAS, the Project Management Committee of the Apache Axis project
has chosen by vote to recommend Robert Lazarski (rlazarski) as the
successor to the post;
NOW, THEREFORE, BE IT RESOLVED, that Deepal Jayasinghe is relieved and
discharged from the duties and responsibilities of the office of Vice
President, Apache Axis, and
BE IT FURTHER RESOLVED, that Robert Lazarski be and hereby is
appointed to the office of Vice President, Apache Axis, 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 Axis Project Chair, was
approved by Unanimous Vote of the directors present.
F. Establish Position of VP, Sponsor Relations
WHEREAS, the Board of Directors hereby creates the position of Vice
President, Sponsor Relations to assist the Vice President,
Fundraising, in maintaining good relations with the sponsors of the
foundation; and
NOW, THEREFORE, BE IT RESOLVED, that the number of Vice President,
Sponsor Relations and their responsibilities shall be initially
defined and subsequently amended at the direction of the Vice
President, Fundraising; and
BE IT FURTHER RESOLVED, that appointments to the office of Vice
President, Sponsor Relations, shall be at the discretion of the Vice
President of Fundraising, to serve in accordance with and subject to
the direction of the Vice President of Fundraising, the ASF President,
and the ASF 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, Establish Position of VP, Sponsor Relations,
was tabled.
G. Establish the Apache Guacamole Project
WHEREAS, the Board of Directors deems it to be in the best interests
of the Foundation and consistent with the Foundation's purpose to
establish a Project Management Committee charged with the creation and
maintenance of open-source software, for distribution at no charge to
the public, related to providing performant, browser-based remote
access.
NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
(PMC), to be known as the "Apache Guacamole Project", be and hereby is
established pursuant to Bylaws of the Foundation; and be it further
RESOLVED, that the Apache Guacamole Project be and hereby is
responsible for the creation and maintenance of software related to
providing performant, browser-based remote access; and be it further
RESOLVED, that the office of "Vice President, Apache Guacamole" 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
Guacamole Project, and to have primary responsibility for management
of the projects within the scope of responsibility of the Apache
Guacamole 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 Guacamole
Project:
* Daniel Gruno <humbedooh@apache.org>
* Frode Langelo <frode@apache.org>
* Greg Trasuk <gtrasuk@apache.org>
* James Muehlner <jmuehlner@apache.org>
* Jean-Baptiste Onofré <jbonofre@apache.org>
* Jim Jagielski <jim@apache.org>
* Mike Jumper <mjumper@apache.org>
* Nick Couchman <vnick@apache.org>
NOW, THEREFORE, BE IT FURTHER RESOLVED, that Mike Jumper be appointed
to the office of Vice President, Apache Guacamole, to serve in
accordance with and subject to the direction of the Board of Directors
and the Bylaws of the Foundation until death, resignation, retirement,
removal or disqualification, or until a successor is appointed; and be
it further
RESOLVED, that the initial Apache Guacamole PMC be and hereby is
tasked with the creation of a set of bylaws intended to encourage open
development and increased participation in the Apache Guacamole
Project; and be it further
RESOLVED, that the Apache Guacamole Project be and hereby is tasked
with the migration and rationalization of the Apache Incubator
Guacamole podling; and be it further
RESOLVED, that all responsibilities pertaining to the Apache Incubator
Guacamole podling encumbered upon the Apache Incubator PMC are
hereafter discharged.
Special Order 7G, Establish the Apache Guacamole Project, was
approved by Unanimous Vote of the directors present.
H. Change the Apache Calcite Project Chair
WHEREAS, the Board of Directors heretofore appointed Jesús Camacho Rodríguez
(jcamacho) to the office of Vice President, Apache Calcite, and
WHEREAS, the Board of Directors is in receipt of the resignation
of Jesús Camacho Rodríguez from the office of Vice President, Apache
Calcite and
WHEREAS, the Project Management Committee of the Apache Calcite
project has chosen by vote to recommend Michael Mior (mmior)
as the successor to the post;
NOW, THEREFORE, BE IT RESOLVED, that Jesús Camacho Rodríguez is
relieved and discharged from the duties and responsibilities of
the office of Vice President, Apache Calcite, and
BE IT FURTHER RESOLVED, that Michael Mior be and hereby is appointed
to the office of Vice President, Apache Calcite, 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 7H, Change the Apache Calcite Project Chair, was
approved by Unanimous Vote of the directors present.
8. Discussion Items
* Sponsor communications
* ApacheCon North America: Discuss willingness to front $100k seed
money to produce an event. Discuss what we might be willing to
invest ("lose") each year in the interest of outreach and
promotion.
* Five Year budget projections
* Sponsor communications
Postponed until next month
* ApacheCon North America: Discuss willingness to front $100k seed
money to produce an event. Discuss what we might be willing to
invest ("lose") each year in the interest of outreach and promotion.
Tentative plans to co-locate ApacheCon EU 2018 with Buzzwords
Berlin.
Board approves a one time $100K budget increase for conferences,
additional years will be considered in the five year budget plan.
* Five Year budget projections
Phil and Sam to produce a draft in the upcoming weeks.
9. Review Outstanding Action Items
* Ted: Discuss state of development with PMC; encourage on-list development
[ Tajo 2017-06-21 ]
Status:
* Chris: pursue a report for Hama; is a new chair needed?
[ Hama 2017-07-19 ]
Status: discussed this at the last call. A new chair IS needed in my
mind and ideally the project needs to retire. Rich has the
ball now on this.
* Ted: pursue a report for Community Development; look at previous examples of
[ Community Development 2017-08-16 ]
Status:
* Rich: follow up to see if the project is still viable
[ Hama 2017-08-16 ]
Status:
* Jim: follow up to document the resolution of ignite.run issue next board
[ Ignite 2017-08-16 ]
Status: Done.
* Jim: follow up with the PMC to get a public statement out
[ Discussion Items 2017-08-16 ]
Status: almost complete
* Phil: engage with PMC to see what is going on
[ Tajo 2017-09-20 ]
Status: Ted sent a mail to the dev list last month and got no
response. I just mailed the private list asking if the project
is still alive or should be considered for the Attic.
* Phil: get an answer to who can attend the meetups
[ Samza 2017-10-18 ]
Status: Done. Confirmed meetings are open to all. Moreover, decisions
are not made at these meetings - more info/share meetup
meetings.
* Mark: ensure that there are 3 active PMC members
[ Stanbol 2017-10-18 ]
Status: Ping message sent. PMC members given 7 days to identify
themselves as active.
* Bertrand: pursue a report for Web Services
[ Web Services 2017-10-18 ]
Status: No reply to my Oct.19 email, pinged the PMC again on Nov.13
10. Unfinished Business
11. New Business
12. Announcements
13. Adjournment
Adjourned at 12:06 p.m. (Pacific)
============
ATTACHMENTS:
============
-----------------------------------------
Attachment 1: Report from the Executive Assistant [Melissa Warnkin]
* Coordinated with SES (ATO’s exhibition service) re all logistics for the
show, including negotiating a deep discount to compensate for our box of
swag they misplaced (it was leftover inventory).
* Special thanks to Sam, Sam’s wife, and everyone who helped setup/breakdown and staff
the booth!
-----------------------------------------
Attachment 2: Report from the VP of Brand Management [Shane Curcuru]
* ISSUES FOR THE BOARD (continuing issue)
The core issue is that we are greatly under-serving our projects in terms of
brand services. The lack of questions vs. number of popular projects we host
shows many PMCs aren't properly policing their marks.
Brand strategy - at a very high level, there are two long-term blockers with
providing brand services to our projects currently:
- Lack of reliable volunteers. We have only two volunteers in recent years
who have shown a sustained interest and knowledge of our policies. Thus,
nearly all the work is done by a single person.
- Specialized knowledge. Being able to *accurately* answer most trademarks@
questions doesn't require law experience, but it does require both a
thorough reading our our existing policies, as well as a keen attention to
detail and consistent way of looking at each situation for the visible
facts. This requires a notable amount of time to correctly answer questions
for anyone who might volunteer.
(To be continued next month, reviewing skills/work needed)
* OPERATIONS
A normal month, with more questions about use of Apache brands on merchandise.
We are getting (a very small) amount of royalties on licensing Apache marks to
Litographs, which is heartening to see. It's likely there are other vendors
interested in similar arrangements.
A large thread discussed appropriate boundaries for use of commercially
licensed software in building and displaying the website for a newly created
TLP. The specific questions were handled with Legal, but the larger question
of prominent use of commercial software displayed on Apache project websites
bears watching.
Website Analytics shows a steady decline in overall hits - not sure what
that's from, although since we don't have any campaign for awareness, it's
hard to tell. Assistance planning outreach would be useful. The majority of
hits are still direct to the primary policy page.
* REGISTRATIONS & CONTRACTS
HAWQ has finished transferring ownership to the ASF. The US registration of
PREDICTIONIO has transferred, however a number of international applications
are outstanding and will be evaluated for cost effectiveness.
Our BROOKLYN registration in the EU was finally issued.
Counsel continues to craft a contentious consent contract.
-----------------------------------------
Attachment 3: Report from the VP of Fundraising [Kevin A. McGrail]
* Resolution to establish VP, Sponsor Relations
* We continue to discuss new sponsorships and renewing existing. Nothing
unusual to report but multi-year commits are helping both with less stressful
large sponsors relations and putting Infra concerns to rest. The no-follow
policy also appears to be getting rid of the SEO-focused tiny sponsors.
* Raising Hopsie minimum donation to $10 due to high overhead with Stripe is
pending Sally’s input.
* Meetings semi-monthly with Virtual continue between KAM and Lynsey. Sally
will also be joining them as well.
* Directed sponsorship process continues to go well. Met with Infra and started
the audit of all inkind sponsors and their levels.
* Started creating the new Directed Sponsor levels at
http://www.staging.apache.org/foundation/thanks2.html
* Sponsor Agreement is now written and was Used to sign Union Investment as a
Silver Sponsor!
https://docs.google.com/document/d/1Pdksp-XuI1nbZfjW4n218WUJCe3Zpd8Ele4m1euXcok/edit
* I am using this agreement with all new sponsors as they onboard. Should we
send a copy to existing sponsors with no requirement to sign but so they know
the details. And then require signing on renewal?
* Future or Items with no Progress to Report: Attending FOSDEM on ASF Behalf
Likely to attend Berlin Buzzwords & FOSS Backstage on ASF Behalf Sponsor thank
you / fundraising event
-----------------------------------------
Attachment 4: Report from the VP of Marketing and Publicity [Sally Khudairi]
I. Budget: we are on budget and on schedule. One new vendor payment
request has been submitted for processing.
II. Cross-committee Liaison: work on the Sponsor Ambassador program is
ongoing with ASF Fundraising. Sally Khudairi has secured a handful of
Sponsor commitments for renewals for the upcoming year, and is
planning a new individual giving campaign for the holidays. We
published "Success at Apache: Scratch Your Own Itch"
https://s.apache.org/7Amk , which was also published as a cover
feature in JAX Magazine's special issue on Open Source.
III. Press Releases: the following formal announcements were issued
via the newswire service, ASF Foundation Blog, and announce@apache.org
during this timeframe:
- 1 November 2017 - The Apache Software Foundation Announces Apache® Kafka®
v1.0.0
- 31 October 2017 - The Apache Software Foundation Announces Apache® Juneau™
as a Top-Level Project
- 24 October 2017 - The Apache Software Foundation Announces Apache®
PredictionIO™ as a Top-Level Project
- 19 October 2-17 - The Apache Software Foundation Announces Five
Years of Apache® OpenOffice™ as a Top-Level Project
IV. Informal Announcements: 10 items were published on the ASF
"Foundation" Blog. 1 "Success at Apache" blog post was published, as
mentioned above. 4 Apache News Round-ups were issued, with a total of
173 weekly summaries published to date. We tweeted 25 items, and have
44.3K followers on Twitter. We posted 9 items on LinkedIn, which
garnered more than 226.8K 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 8 media queries, and are working
on 2 long-lead media opportunities. The ASF received 2,090 press clips
vs. last month's clip count of 4,639. Media coverage of Apache
projects yielded 5,579 press hits vs. last month's 14,364.
VII. Analyst Relations: we received two analyst queries during this
timeframe, including a preview of a Cloud influencer report. Apache
was mentioned in 10 reports by Gartner, 7 reports by Forrester, 4
reports by 451 Research, and 7 reports by IDC.
VIII. Graphics: we completed graphics production for several
promotional items to be used at various conferences. Sharan Foga and
Melissa Warnkin have been very helpful in shepherding these projects.
IX. Events liaison: in addition to liaising with ComDev with external
community-focused opportunities, we are supporting the ASF’s presence
at China Open Source Conference COSCon '17 in Shanghai.
X. Newswire accounts: we have 1 pre-paid press release remaining with
NASDAQ GlobeNewswire through December 2017, and will be applying our
2018-2019 contract early to accommodate any announcements issued
before the end of 2017.
# # #
-----------------------------------------
Attachment 5: Report from the VP of Infrastructure [David Nalley]
General
=======
Infra continues to operate as expected, and there are no issues for
the President or the Board at this time.
Much work has been done around finances this past month, but we remain
on track to meet our overall budget.
Finances
========
With the help of Tom from Virtual, we investigated an oddity in our
staffing expenditures. Given that we currently have an open headcount,
our year-to-date costs should be low, but they were running at our
budget levels instead. The answer is that Infra incorrectly forecasted
FY18 costs from the FY17 actuals. We left the headcount open for a
while, and along with savings in other cost centers, when we fill the
headcount for the remainder of FY18, the total Infra costs should fall
within its total budget.
One of our secondary (large) budget items has been variable, due to
currency fluctations. The structure of the payments and related
sponsorship is due to change soon, and should create a more stable
cash flow. The Treasurer and Fundraising teams are working on this.
Short Term Priorities
=====================
- Working out plans to move some services into Azure, under their
programs to assist F/OSS organizations.
- Digging into our VM usage across our various datacenters to find the
top-line costs, for future tradeoffs and cost-savings.
Long Range Priorities
=====================
- Continue VM migration and puppetization. Our major concerns here
revolve around mail handling.
General Activity
================
We have consolidated our domain management under Namecheap to reduce
expenses, make use of their API, and get better support. We plan to
expand/shift our DNS management to Namecheap as well, away from our
custom solutions.
Uptime Statistics
=================
We had an outage on mail-archives.a.o that took us a while to correct.
It hightlighted our ongoing issues with services on old hardware, old
operating systems, and non-puppetized services. We corrected the
issue, but have started on additional disaster-relief measures. Given
the age of these services, monitoring is difficult.
-----------------------------------------
Attachment 6: Report from the VP of Conferences [Rich Bowen]
Since our last report, I've been considering options for a way forward
with ApacheCon, in the hopes that we can still do a North America
event in Spring 2018, and a Europe event in the latter half of the
year.
In the time since ApacheCon Miami, I have received numerous queries
about when we'll be holding the next event, and lamentations that we
didn't have an EU event this year. It is clear that our community
wants this event.
To this end, we'll be working towards that goal, and discussion will
begin immediately on the planners@apachecon.com mailing list, wihch is
open to members.
-----------------------------------------
Attachment 7: Report from the Apache Travel Assistance Committee [Melissa Warnkin]
No issues to report
-----------------------------------------
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]
The month began with discussion surrounding fair use of files used
in our projects, e.g., open image files, or scans of text from the
web. Though no broad policy updates emerged, the parties in discussion
received the feedback needed from the Legal committee to move on
with their efforts as described in LEGAL-331 [1] and LEGAL-332 [2].
A new top level project (TLP) wanted Legal's opinion in the
construction of its new website as to whether or not design files
licensed commercially (and not under the ALv2) would affect their
use on the website. Legal provided guidance that this was acceptable
in this specific case, but further requests similar to this would
need to be evaluated on their own merits. More information on the
discussion can be found in [3] and in LEGAL-341 [4].
An ASF and Legal Committee member raised discussion surrounding
replacing our CLA with DCO+ALv2 as described in [5]. Several other
members chimed in and the overall consensus was that our ICLAs are
working out just fine since they are a direct pre-requisite to
having ASF accounts and thus there is a community benefit of having
an ICLA on file should contributors be invited as committers or PMC
members to ASF projects.
The question of what metrics can be recorded in ASF projects w.r.t.
downloads and user information related to them incepted a spirited
discussion. Pointers were made to infra policy and infra members
including the Infra Admin provided guidance in the thread.
[1] https://issues.apache.org/jira/browse/LEGAL-331
[2] https://issues.apache.org/jira/browse/LEGAL-332
[3] https://s.apache.org/YwMN
[4] https://issues.apache.org/jira/browse/LEGAL-341
[5] https://s.apache.org/0NzX
-----------------------------------------
Attachment 10: Report from the Apache Security Team Project [Mark J. Cox]
This month we had a researcher incorrectly report an issue in
Solr/lucene by sending it not just to security@apache.org but also to
public mailing lists. CVE-2017-12629. This information included an
exploit and spread rapidly. Updates from the project to mitigate this
were produced rapidly and we worked with Press to ensure we had a
media response.
Stats for October 2017:
11 CVEs issued to projects (some may not be public yet).
e-mails to security@
7 Phishing/spam/proxy/attacks point to site "powered by Apache" or
Confused user due to "Apache" mentioned in OSS licenses
5 Support Questions
13 Direct Vulnerability report to security@apache.org
5 [ignite]
1 [jmeter/activemq]
1 [james]
2 [solr]
1 [httpd]
2 [site] 1 rejected
1 [commons]
10 Vulnerabilities reported to projects
1 [hive]
1 [nifi]
2 [couchdb]
3 [geode]
1 [cloudstack]
1 [aurora]
1 [tomcat]
-----------------------------------------
Attachment A: Report from the Apache ACE Project [Marcel Offermans]
-----------------------------------------
Attachment B: Report from the Apache Ambari Project [Yusaku Sako]
## Description:
- Apache Ambari simplifies provisioning, managing, and monitoring of Apache
Hadoop clusters.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- Since the last report, the community managed to release Ambari 2.6.0 with
350 JIRAs resolved by 47 contributors.
In addition to 2.6.0, the community has been steadily working on 3.0.0 for
new feature / re-architecture / scalability work.
Development cadence and activity remains high.
7 committers have been added since the last report, raising the total
number of committers to 97.
## PMC changes:
- Currently 44 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Aravindan Vijayan on Sun Jun 04 2017
## Committer base changes:
- Currently 97 committers.
- New commmitters:
- Amruta R Borkar was added as a committer on Wed Oct 18 2017
- Anita Jebaraj was added as a committer on Wed Sep 20 2017
- Daniel Gergely was added as a committer on Wed Sep 20 2017
- Ishan Bhatt was added as a committer on Wed Oct 25 2017
- Nishant Bangarwa was added as a committer on Mon Sep 18 2017
- Qin Liu was added as a committer on Wed Oct 04 2017
- Vishal Suvagia was added as a committer on Wed Sep 20 2017
## Releases:
- 2.5.2 was released on Mon Aug 28 2017
- 2.6.0 was released on Wed Oct 25 2017
## Mailing list activity:
- dev@ambari.apache.org:
- 285 subscribers (up 6 in the last 3 months):
- 62 emails sent to list (39 in previous quarter)
- issues@ambari.apache.org:
- 41 subscribers (up 0 in the last 3 months):
- 6347 emails sent to list (5866 in previous quarter)
- reviews@ambari.apache.org:
- 47 subscribers (up 2 in the last 3 months):
- 1717 emails sent to list (2184 in previous quarter)
- user@ambari.apache.org:
- 489 subscribers (up 18 in the last 3 months):
- 101 emails sent to list (40 in previous quarter)
## JIRA activity:
- 711 JIRA tickets created in the last 3 months
- 646 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment C: Report from the Apache Ant Project [Jan Materne]
## Description:
Apache Ant is a Java based build tool along with associated tools.
It consists of 3 main projects:
- Ant - core and libraries (AntLibs)
- Ivy - Ant based dependency manager
- IvyDE - Eclipse plugin to integrate Ivy into Eclipse
Additionally Ant provides several extensions to Ant (antlibs).
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
Apache Ant is an old - and maybe wise - project. So the grandfather gives a look back
on to its life so other younger projects could benefit from this. Stefan Bodewig
will be giving such a talk on FOSS Backstage Micro Summit on 20th November in Berlin
(https://berlinbuzzwords.de/17/news/foss-backstage-micro-summit-program-online-now).
Fixed some Ivy issues.
Updated Ivy+IvyDE codebase to newer Java version.
## Health report:
For Ant we feel healthy enough to apply patches, and get a release done.
But basically we are in "maintenance mode". There isn't much development.
With the two new committers Ivy + IvyDE revived and activity is (relativly) high.
## PMC changes:
- Currently 21 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Jean-Louis Boudart on Thu Dec 12 2013
## Committer base changes:
- Currently 30 committers.
- No new committers added in the last 3 months
- Last committer addition was Gintas Grigelionis at Sat Aug 05 2017
## Releases:
- Last release was Compress Antlib 1.5 on Tue Jun 13 2017
-----------------------------------------
Attachment D: Report from the Apache Axis Project [Deepal Jayasinghe]
## 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 1.7.6 (stable)
- Maintenance only.
- Axis2 1.8 (development)
## Health report: We have enough PMC to cut releases. Axis2 is a mature
project, but still actively maintained. We expect to have a new PMC chair
accepted by the board this month (Robert Lazarski). Most of the emails on
the Axis2 user mailing list, and Jira issues created in the last 3 months,
have received timely responses. We continue to receive patches from various
new users/contributors.
## PMC/Committer changes:
- Currently 62 PMC/Commiters members.
- No new committers were added in last three months (last addition was in
June 2016).
## Releases:
- Axis 2/Java 1.7.6 was released on July 30, 2017.
## JIRA Activity
- 33 JIRA tickets created in the last 3 months.
- 24 JIRA tickets closed/resolved in the last 3 months.
-----------------------------------------
Attachment E: Report from the Apache BookKeeper Project [Sijie Guo]
-----------------------------------------
Attachment F: Report from the Apache Brooklyn Project [Richard Downer]
## Description:
- Apache Brooklyn Project is a software framework for modeling, monitoring and
managing cloud applications through autonomic blueprints.
## Issues:
- There are no issues requiring board attention at this time
## Activity:
- Development continues with a regular turnover of pull requests submitted and
merged.
- We made a new release (0.12.0) which made Apache Karaf the underlying
framework for the project
- A community member was invited to become a committer and accepted. Later
they were invited to join the PMC, and also accepted.
## Health report:
- The project continues with a similar level of activity that we have seen
recently. There is a regular turnover of pull requests and commits, and JIRA
tickets, showing that development is at a healthy pace and that users are
feeding back their problems and feature suggestions.
- We continue to monitor our community for potential new committers and PMC
members with the aim of regularly adding individuals.
## PMC changes:
- Currently 15 PMC members.
- Thomas Bouron was added to the PMC on Tue Oct 31 2017
## Committer base changes:
- Currently 15 committers.
- Thomas Bouron was added as a committer on Wed Oct 04 2017
## Releases:
- 0.12.0 was released on Wed Sep 27 2017
## JIRA activity:
- 21 JIRA tickets created in the last 3 months
- 9 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment G: Report from the Apache Buildr Project [Antoine Toulme]
-----------------------------------------
Attachment H: Report from the Apache Cassandra Project [Nate McCall]
## Description:
The Apache Cassandra database is the right choice when you need scalability
and high availability without compromising performance. Linear scalability and
proven fault-tolerance on commodity hardware or cloud infrastructure make it
the perfect platform for mission-critical data.Cassandra's support for
replicating across multiple datacenters is best-in-class, providing lower
latency for your users and the peace of mind of knowing that you can survive
regional outages.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
The Next Generation Cassandra Conference
(https://www.eventbrite.com/e/next-generation-cassandra-conference-ngcc-ticket
s-36160855091#) was recently held in San Antonio, TX. This conference was
planned and run solely by the community coordinated on the private,
development and user mail lists (as appropriate) with no vendor influence.
Talks were selected directly by the PMC. A summary of the event posted to the
dev list can be found here:
https://lists.apache.org/thread.html/5ab801e508a792d81defe092a77c59df862ce36b1
4c1a41445367190@%3Cdev.cassandra.apache.org%3E
Great care was taken to summarize any major discussions back to their
respective JIRA tickets as well as summarize and continue conversations on the
development mailing list after the event to facilitate larger community
participation.
A huge thanks to long-time PMC members Gary Dusbabek and Eric Evans for doing
all the leg work in putting this event on.
## Health report:
Overall the project is healthy. We continue to leverage the lack of any vendor
influence by focusing the current work on stability and testing.
## PMC changes:
There were three new PMC members added this quarter:
- Josh McKenzie was added to the PMC on Fri Aug 18 2017
- Marcus Eriksson was added to the PMC on Fri Aug 18 2017
- Jon Haddad was added to the PMC on Sun Aug 20 2017
## Committer base changes:
There was one committer added this quarter:
- Jon Haddad was added as a committer on Sat Aug 19 2017
## Releases:
- 2.1.19 was released on Thu Oct 05 2017
- 2.2.11 was released on Thu Oct 05 2017
- 3.0.15 was released on Tue Oct 10 2017
- 3.11.1 was released on Tue Oct 10 2017
## Mailing list activity:
Development list activity saw a substantial uptick as the result of
continuation of discussion from topics presented at the NGCC. User list
activity remained stable.
dev@cassandra.apache.org:
- 1626 subscribers (up 5 in the last 3 months):
- 349 emails sent to list (316 in previous quarter)
user@cassandra.apache.org:
- 3102 subscribers (down -6 in the last 3 months):
- 1150 emails sent to list (1133 in previous quarter)
## JIRA activity:
- 249 JIRA tickets created in the last 3 months
- 211 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment I: Report from the Apache Celix Project [Alexander Broekhuis]
-----------------------------------------
Attachment J: Report from the Apache Clerezza Project [Hasan Hasan]
DESCRIPTION
Apache Clerezza models the RDF abstract syntax in Java and provides supports
for serializing, parsing, and managing triple collections, as well as a tool
to generate the source code of a Java class with constants for an ontology
described in RDF. Apache Clerezza components are OSGi-based and have the
purpose to ease building of Semantic Web applications and services.
ISSUES FOR THE BOARD
There are no issues requiring board attention at this time.
RELEASE
Latest release was partial-release-201604 created on May 13, 2016.
ACTIVITY
- No code development during the last three months.
- A tutorial about Apache Clerezza Parser was added to the website.
COMMUNITY
Latest change was addition of a new committer and PMC member on 16.08.2013.
We haven't got new committers. I will send another email to the dev list
and in particular to also gather dev opinions regarding further development
of Apache Clerezza and potential improvements of existing codes.
INFRASTRUCTURE
Latest update of the Apache Clerezza Website was in November 2017.
-----------------------------------------
Attachment K: Report from the Apache Cocoon Project [Cédric Damioli]
## Description:
Web development framework: separation of concerns, component-based.
## Issues:
there are no issues requiring board attention at this time
## Activity:
The most recent release is 2.1.12 on 2013-03-14
2 JIRA issues opened and resolved since last report.
There's only a little activity on both users and dev mailing-lists (a dozen messages during the period).
The project is mainly in maintenance mode.
There have been some quite interesting changes since last release, at least for
2.1 branch, which would deserve a release. We issued the same statement
last quarter but noone launched the process yet.
## PMC changes:
None.
Most recent addition: 2012-07-06
## Committer base changes:
None.
Most recent addition: 2012-07-06
-----------------------------------------
Attachment L: Report from the Apache Community Development Project [Sharan Foga]
## Description:
The Community Development PMC is responsible for helping people become
involved with Apache projects
## Issues:
No issues require board attention at the moment.
## Activity:
Our last board report for August was missing so those items are included as
part of this report.
During the last two quarters our main focus was to promote an Apache presence
at existing conferences with a booth or presentation content.
OpenExpo
We participated for the first time at the OpenExpo Madrid event in June. We
received an invitation to the event because of a contact made at FOSDEM. We
recruited two Spanish speaking booth volunteers (Ignasi Barrera and Jan
Iversen). Ignasi created a small ASF brochure that has been approved by Sally.
The conference attracted over 3000 visitors and approx around 10% stopped to
talk to us at the Apache booth. We found that many people didn't really know
that there was a Foundation behind Apache projects so being there helped fill
this knowledge. As a follow up Ignasi was invited for an interview at a local
Spanish radio station to talk about the ASF.
Following on from this, the organisers are planning the 2018 conference and
would like more English content so have asked the ASF to become more involved
and to organise a track around on open source governance, trends and best
practices.
Solutions Hamburg
In early September we participated in a 3 day Apache track at Solutions
Hamburg. Nine ASF speakers participated include a keynote from Greg Stein.
Attendance was mixed and the talks about microservices were the most attended.
This was the first time at this event and need to review how we could improve
our participation. Thanks to the speakers and especially to Myrle Krantz and
Chris Dutz for their work in organising, facilitating and generally liaising
with the organisers.
Open Source Summit Prague
Although we did not have a booth at this event, there were several Apache
related presentations including a Keynote from Neha Narkhede about Apache
Kafka, Rich Bowen talked about Mentoring,Piergiorgio Lucidi talked about the
incubation process for Apache ManifoldCF and Sharan Foga spoke about the
Committer Diversity Survey at the Diversity Empowerment Summit.
MesosCon Prague
The Apache Mesos community were happy to have an Apache presence with a booth
and also a Keynote from Rich Bowen. Feedback on the keynote was very positive
and we received several enquiries about future ApacheCons.
ComDev Jira
We have started using the ComDEV Jira again to help track tasks. Some cleanup
of old / existing tasks are in progress. Notifications have been moved to the
dev list to allow better communication and this has been successful as seen by
the ASF Brochure translations.
Open Source Summit Paris We have been given a booth and also a half day track
at OSS Paris. The track has been filled with presentation from several
projects. We have also been given a keynote slot which will be presented by
Bertrand Delacretaz.
FOSDEM
A request for an Apache booth has been made and decisions will be announced in
late November. Based on community feedback, we also put together a proposal
for an Apache Community Collaboration devroom but this was unsuccessful.
Another Community devroom was accepted and we are encouraging people to make
submissions to this.
Rotation of PMC Chair
In September we rotated the PMC Chair from Uli Stark to Sharan Foga. Many
thanks to Uli for all his hard work and effort as VP ComDev over the last few
years.
FOSS Backstage
The schedule for FOSS Backstage Micro Summit has been announced and focusses
on community, governance and the legal aspects around open source. Several
speakers from Apache have been selected to present.
GSoC Update
Uli is keeping track and following up on GSoC progress for the various
projects involved.
Marketing
With the help of various volunteers, the ASF Brochure has been translated into
several languages. This will be available for people to use at events.
Discussions around the introduction of Apache Community business cards has
been very positive so we will be looking at promoting it to committers and
projects.
ComDev Mission
A discussion is currently in progress about the mission of Comdev to adjust
the description, scope and focus of activities.
## PMC changes:
- Currently 22 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Sharan Foga on Tue Nov 15 2016
## Committer base changes:
- Currently 22 committers.
- No new committers added in the last 3 months
- Last committer addition was Sharan Foga at Tue Nov 15 2016
## Releases:
- No release data could be found
## Mailing list activity:
- Mailing list activity has increased partly due to re-direction of Jira
notifications to dev list and also because several interesting discussion
proposals have been raised. Increased Jira activity for the clean up of old /
existing tickets and also creation of new tickets to manage the work on ASF
Brochure translations.
- dev@community.apache.org:
- 793 subscribers (up 7 in the last 3 months):
- 530 emails sent to list (362 in previous quarter)
## JIRA activity:
- 18 JIRA tickets created in the last 3 months
- 21 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment M: Report from the Apache CouchDB Project [Jan Lehnardt]
## Description:
- Seamless multi-master sync, that scales from Big Data to Mobile,
with an Intuitive HTTP/JSON API and designed for Reliability.
## Issues:
- there are no issues requiring board attention at this time
## Activity:
- Released versions 2.1.1 and 1.7.0 in response to a critical
security vulnerability being reported. Details are embargoed
for a few more days at the time of writing of this report.
CVE’s have been filed and should be out by the time of the
board meeting.
- Released version 1.7.1 because 1.7.0 included an unintentional
API break.
- Barring any other major security issues, this will have been
the last release in the 1.x.x line.
- 2.1.1 included a flurry of other improvements and performance
advancements an follows relatively shortly after 2.1.0 (August),
showcasing the advance in CI reliability and breadth allowing
for faster and more confident releases (just wish we had that
in place for 1.x.x so we could have avoided 1.7.1, alas).
- Late response to a March Board Report question by `mt`
(again, all formal apologies for the delay). In January 2017,
CouchDB was in the news about data leaks and ransom scenarios,
citing CouchDB’s “open by default” setup. In short CouchDB 1.x
has followed an open-by-default strategy to make it easy for
new users to get started. The main mitigating factor only
binding to 127.0.0.1, and requiring an explicit admin step
to bind to a public IP. 10 years in the strategy worked, but
it is also time to shed that legacy. CouchDB 2.x default
setup requires an admin password to be set, even on 127.0.0.1.
This is a big improvement, but leaves a few more ways until
we get to a closed-by-default sitaution. We’re expecting a
full transition to be done by CouchDB 3.0.
## Health report:
- CouchDB is doing fine. Unprecedented activity in Q3 of work
that ended up in a release already. We aim to keep up a
quarterly release cadence.
## PMC changes:
- Currently 15 PMC members.
- Nick Vatamaniuc was added to the PMC on Tue Nov 07 2017
## Committer base changes:
- Currently 60 committers.
- New commmitters:
- Mayya Sharipova was added as a committer on Thu Aug 31 2017
- Will Holley was added as a committer on Thu Aug 31 2017
## Releases:
- 1.7.0 was released on Mon Nov 06 2017
- 1.7.1 was released on Sat Nov 11 2017
- 2.1.1 was released on Mon Nov 06 2017
-----------------------------------------
Attachment N: Report from the Apache Creadur Project [Brian E Fox]
Apache Creadur creates and maintains a suite of open source software related
to the auditing and comprehension of software distributions. Any language and
build system are welcomed.
Status
------
Since the last report, a new TLP for DRAT was proposed, which raised
some questions about how it relates to Creadur / RAT. There were no specific
concerns raised within the Creadur PMC. An offer was extended to the Creadur
PMC members to join the DRAT PMC, and Brian Fox accepted and is now also part
of DRAT. Otherwise, no changes to the code.
Since this is a low activity project, a vote was called on the content of this
report as a test of our ability to self-govern. As of the time of posting, we
achieved 4 +1s in less than 24 hours.
Creadur is primarily used by other Apache projects to help check for
conformity to ASF standards. This is why the project team is primarily
comprised of members and committers from other ASF projects. The risk of the
project foundering is therefore very low despite the ongoing lack of progress.
If someone has an itch to scratch, it will no doubt get fixed.
Community
---------
In September 2016 Karl Heinz Marbaise was elected to join the PMC /
Commit.
Releases
--------
Apache Rat 0.12 was released in June, 2016 Apache Rat 0.11 was
released in August, 2014 Apache Rat 0.10 was released in September, 2013.
-----------------------------------------
Attachment O: Report from the Apache Crunch Project [Josh Wills]
## Description:
Apache Crunch is a Java library for writing, testing, and running MapReduce
and Apache Spark pipelines on Apache Hadoop.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
Aside from a few small bug fixes, the main focus of development/discussion
in the last quarter was how to execute the series of upgrades on our
dependencies (mainly Apache Hadoop, HBase, and Hive) that we need to complete
the 1.0 release. We need to do some heavy lifting and compatibility-breaking
changes to the HBase module in order to make the move to HBase 2.x, which
is necessary to make the move to Hive 2.x. The JIRA issue here tracks this:
https://issues.apache.org/jira/browse/CRUNCH-659
## Health report:
The fact that we're no longer really working on new features or functionality
in favor of bug fixes and version upgrades is the most significant issue with
the health of the project. The good news is that a number of new contributors
have been driving the version upgrade effort, and several of them clearly
have the potential to become committers and PMC members once this work is
done. The biggest need (and where I have fallen short as PMC chair) is
providing them with guidance, feedback, and support for their efforts so
that they can complete this work and earn their committerships.
## PMC changes:
- Currently 12 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Micah Whitacre on Wed Apr 02 2014
## Committer base changes:
- Currently 14 committers.
- No new committers added in the last 3 months
- Last committer addition was David Whiting at Mon Nov 30 2015
## Releases:
- Last release was 0.15.0 on Sat Feb 25 2017
## JIRA activity:
- 8 JIRA tickets created in the last 3 months
- 2 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment P: Report from the Apache DeltaSpike Project [Mark Struberg]
## Description:
Apache DeltaSpike is a suite of portable CDI (Contexts & Dependency
Injection) extensions intended to make application development easier when
working with CDI and Java EE. Some of its key features include:
- A core runtime that supports component configuration, type safe messaging
and internationalization, and exception handling.
- A suite of utilities to make programmatic bean lookup easier.
- A plugin for Java SE to bootstrap both JBoss Weld and Apache OpenWebBeans
outside of a container.
- JSF integration, including backporting of JSF 2.2 features for Java EE 6.
- JPA integration and transaction support.
- A Data module, to create an easy to use repository pattern on top of JPA.
- Quartz integration
Testing support is also provided, to allow you to do low level unit testing of
your CDI enabled projects.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
Activity was a bit down in the last quarter.
We get user questions on the lists and continue to maintain
and evolve the project.
## Health report:
Community involvement is ok but could be a tad higher.
## PMC changes:
- Currently 19 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Harald Wellmann on Thu May 19 2016
## Committer base changes:
- Currently 33 committers.
- No new committers added in the last 3 months
- Last committer addition was Matej Novotny at Fri Jun 03 2016
## Releases:
- Last release was 1.8.0 on Thu Jun 01 2017
## Mailing list activity:
- users@deltaspike.apache.org:
- 188 subscribers (up 7 in the last 3 months):
- 26 emails sent to list (46 in previous quarter)
- dev@deltaspike.apache.org:
- 104 subscribers (down -1 in the last 3 months):
- 91 emails sent to list (219 in previous quarter)
## JIRA activity:
- 16 JIRA tickets created in the last 3 months
- 6 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment Q: 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:
1. Working on design of DRAT website, can be seen here in drat #98 [1]
2. Stood up DRAT VM (see INFRA-15304 [2]) and demo service of DRAT proteus,
here: https://drat.apache.org/demo/ (evaluate one repo at a time), and
here: https://drat.apache.org/asfgit/ (generated weekly, full DRAT runs
and statistics for ALL of the ASF git repositories. Thanks to Chris
Lambertus and infra for helping us get going there.
3. In standing up DRAT on Ubuntu, we ran into some Apache OODT bugs in the
recent 1.2 release, and are working with Apache OODT to roll a 1.2.1 that
fixes these bugs. In addition we were able to harden DRAT a bit more as
described in DRAT #100 [3] and #101 [4].
## Health report:
- We've had some engagement from Wayne Burke who started a thread to figure
out whether or not we wanted to create a #drat channel in ASF slack.
Mattmann went ahead and created it after the thread on dev@drat.
- Shivika Thapar and Nipurn Doshi are working on the website design as
described in DRAT #98 [1].
- Thejan Wijesinghe from Apache Tika's GSOC 2017 project has began testing
DRAT and is filing tickets (e.g., DRAT #104 [5].
- Phil Ottlinger of the Creadur community is checking out DRAT and wants to
help with the website.
- The project's activity is ramping up, but still remains a small set of
folks working on it.
## PMC changes:
- Currently 10 PMC members.
- No new PMC members added in the last 3 months
## Committer base changes:
- Currently 10 committers.
- No changes (the PMC was established in the last 3 months)
## Releases:
- None yet
## Mailing list activity:
- More emails being sent to the dev list, including commits, and issue
activity from Github. A thread was started to discuss website development
that linked to several Github issues. Now that we have our Proteus demo
up at https://drat.apache.org/demo/, we expect more folks to check out
and try DRAT. We also will begin shortly publishing weekly runs of Apache
DRAT against all ASF Git repos at https://drat.apache.org/asfgit/. Both of
these will likely generate more mailing list activity.
- dev@drat.apache.org:
- 14 subscribers (up 14 in the last 3 months):
- 29 emails sent to list (0 in previous quarter)
- issues@drat.apache.org:
- 10 subscribers (up 10 in the last 3 months)
[1] https://s.apache.org/EUKE
[2] https://issues.apache.org/jira/browse/INFRA-15304
[3] https://s.apache.org/Bbiw
[4] https://s.apache.org/sr0N
[5] https://s.apache.org/Xkc8
-----------------------------------------
Attachment R: Report from the Apache Drill Project [Aman Sinha]
## Description:
- Drill is a Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage.
## Issues:
- There are no issues requiring board attention at this time
## Activity:
- An all-day Drill 2.0 Hackathon was organized on Sept 18th in San Jose at a
participating company's headquarters. 27 developers registered and
participated in the hackathon. It was a productive day of technical design
discussions on topics related to a major 2.0 release next year.
- The community is actively working towards an upcoming 1.12 release sometime
in late November.
- There is a noticeable uptick in contributions of storage/format plugins for
Drill; PCAP, OpenTSDB, Kafka plugins are either committed or nearing
completion.
## Health report:
- The project is healthy. Development activity based on the pull requests and
JIRAs is quite good and growing, as evidenced by 63 more JIRA tickets resolved
in this reporting period compared to the prior one. Activity on the dev list
showed a 48% jump compared to the previous quarter and activity on the user
list showed a moderate increase. Two new committers were added in the last
period.
## PMC changes:
- Currently 18 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Arina Ielchiieva on Tue Aug 01 2017
## Committer base changes:
- Currently 38 committers.
- New commmitters:
- AnilKumar B was added as a committer on Wed Oct 25 2017
- Kamesh Bhallamudi was added as a committer on Wed Oct 25 2017
## Releases:
- Last release was 1.11.0 on Thu Jul 27 2017
## Mailing list activity:
- dev@drill.apache.org:
- 450 subscribers (up 2 in the last 3 months):
- 2683 emails sent to list (1810 in previous quarter)
- issues@drill.apache.org:
- 19 subscribers (up 1 in the last 3 months):
- 3453 emails sent to list (2582 in previous quarter)
- user@drill.apache.org:
- 615 subscribers (up 6 in the last 3 months):
- 454 emails sent to list (432 in previous quarter)
## JIRA activity:
- 228 JIRA tickets created in the last 3 months
- 164 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment S: Report from the Apache Empire-db Project [Rainer Döbele]
## Description:
- Apache Empire-db is a relational database access engine that takes an
SQL-centric approach in contrast to object-relational-mapping like with JPA
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- There has been activity in providing bugfixes, feature improvements
and answering user questions.
- The project is mature and there seems to be currently little demand by the
committers or users to undertake major changes. The chair intends new to ask
committers about where the project should be heading. Unfortunately the
chair has been too busy recently to already have started such a discussion.
## Answers to comments made by Board members to our last report
Mark Thomas: "It has been a while since the last committer was added. Are
there any prospects on the horizon?"
- Whenever we are notified of suggestions for improvement other than simple
bugfixes we guide people to a possible solution and encourage them to
provide us with their code that solves their problem and make a
contribution. However there has not been enough feedback recently that made
us believe that there is a willingness by someone to engage in the project
and really bring the project forward. This may also be due to the fact that
rdbms and sql have been around for so long, that there is little change on
the rdbms side and hence there is little demand for big changes or
improvements in our code base. So to be frank, at the moment there are no
good prospects for new comitters.
## Health report:
- The project remains healthy although activity has been low this quarter.
## PMC changes:
- Currently 10 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Jan Glaubitz on Sun Jul 10 2016
## Committer base changes:
- Currently 9 committers.
- No new committers added in the last 3 months
- Last committer addition was Jan Glaubitz at Mon Oct 05 2015
## Releases:
- Last release was 2.4.6 on Tue Jan 17 2017
## Mailing list activity:
- dev@empire-db.apache.org:
- 38 subscribers (up 1 in the last 3 months):
- 2 emails sent to list (7 in previous quarter)
- user@empire-db.apache.org:
- 56 subscribers (up 1 in the last 3 months):
- 0 emails sent to list (9 in previous quarter)
## JIRA activity:
- 3 JIRA tickets created in the last 3 months
- 3 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment T: Report from the Apache Flume Project [Hari Shreedharan]
DESCRIPTION
Apache Flume is a distributed, reliable, and available system for
efficiently collecting, aggregating, and moving large amounts of log
data to scalable data storage systems such as Apache Hadoop's HDFS.
RELEASES
* The last release of Flume was version 1.8.0, released on October
4, 2017.
* No other releases are planned at this time.
CURRENT ACTIVITY:
* A total of 51 issues have been filed, and 31 issues have been
resolved in the last three months.
* Approximately 500 messages were exchanged on the dev list in the
past three months, while a total of 36 were exchanged on the user
list in this period.
COMMUNITY
* The last time a committer was added to the project
was on Nov 4, 2017. Attila Simon and Ferenc Szabo were added as committers.
* Currently there are:
- Total of 291 subscribers to the developer list
- Total of 691 subscribers to the user list
- Total of 31 committers
- Total of 23 PMC members
PMC CHANGES
* The last time a new PMC member was elected for the project was
on Nov 5, 2017. Denes Arvay was added to the PMC.
ISSUES
* There are no issues requiring board attention at this time.
-----------------------------------------
Attachment U: Report from the Apache Forrest Project [David Crossley]
Apache Forrest mission is software for generation of aggregated multi-channel
documentation maintaining a separation of content and presentation.
Issues needing board attention:
None.
Changes in the PMC membership:
None.
Last modified: 2017-10-09
Most recent addition: 2009-06-09
New committers:
None.
Most recent addition: 2009-06-09
None on the horizon.
General status:
The most recent release is 0.9 on 2011-02-07.
No activity on the user mail list. However it never gets used much anyway.
No activity on the dev mail list.
Four PMC members were present during the quarter. One PMC member decided to
become emeritus.
At this report, two other PMC members responded to my draft report.
This confirms that there are sufficient people hanging around for us to
potentially be able to make a decision or encourage new contributors.
Project status:
Activity: Idle
3+ people have indicated presence, so has sufficient oversight.
Last quarter there was Board feedback asking if it is time to move to the
Attic. There has been some initial discussion. I will report further at the
next quarter.
Security issues published:
None.
Progress of the project:
None.
-----------------------------------------
Attachment V: Report from the Apache Geode Project [Mark Bretl]
## Description:
- Apache Geode provides a database-like consistency model, reliable
transaction processing and a shared-nothing architecture to maintain
low-latency performance with high-concurrency processing.
## Issues:
- There are no issues requiring board attention.
## Activity:
- Release Geode 1.2.1 containing a small number of improvements, bug and
security fixes
- Released Geode 1.3.0 with 371 resolved tickets, including the following
improvements:
- Finer-grained security
- The ability to snapshot multiple regions simultaneously
- New Geode examples:
- Putting multiple values at once
- Demonstrating Lucene indexing and searching
## Health report:
- We’re continuing to work on attracting new contributors and making it easier
to participate in the community.
- Mailing list activity is healthy.
- Work has started toward the next Geode 1.4.0 release, with a plan to include
the new client/server protocol.
## PMC changes:
- Currently 41 members
- New PMC members:
- David Kimura was added to the PMC on Sun Sep 10 2017.
- Galen O'Sullivan was added to the PMC on Mon Sep 25 2017.
- Mike Stolz was added to the PMC on Sun Oct 29 2017.
- Nick Reich was added to the PMC on Thu Oct 19 2017.
- Patrick Rhomberg was added to the PMC on Tue Oct 31 2017.
## Committer base changes:
- Currently 86 committers.
- New committers:
- David Kimura was added as a committer on Mon Sep 11 2017.
- Galen O'Sullivan was added as a committer on Tue Sep 05 2017.
- Mike Stolz was added as a committer on Sat Oct 21 2017.
- Nick Reich was added as a committer on Sat Oct 14 2017.
- Patrick Rhomberg was added as a committer on Wed Nov 01 2017.
## Releases:
- 1.2.1 was released in September and contained a small number of
improvements, bug and security fixes.
- Most recent release was 1.3.0 on Tue Oct 31 2017. Geode 1.3.0 contains a
number of bug fixes and improvements, including finer-grained security and the
ability to snapshot multiple regions simultaneously.
-- Release notes:
https://cwiki.apache.org/confluence/display/GEODE/Release+Notes#ReleaseNotes-1
.3.0
-- Release artifacts: http://geode.apache.org/releases/
-- Release documentation:
http://geode.apache.org/docs/guide/13/about_geode.html
## Mailing list activity:
- dev@geode.apache.org:
- 175 subscribers (up 1 in the last 3 months):
- 2030 emails sent to list (4170 in previous quarter)
- issues@geode.apache.org:
- 55 subscribers (down 1 in the last 3 months):
- 4883 emails sent to list (3066 in previous quarter)
- user@geode.apache.org:
- 234 subscribers (up 2 in the last 3 months):
- 236 emails sent to list (277 in previous quarter)
## JIRA activity:
- 547 JIRA tickets created in the last 3 months
- 422 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment W: Report from the Apache Giraph Project [Avery Ching]
## Description:
- Giraph is a Bulk Synchronous Parallel framework for writing programs
that analyze large graphs on a Hadoop cluster. Giraph is similar to
Google's Pregel system.
## Issues:
- The VP hasn't been reliably submitting board reports.
+ Two reports in the last 12 months. Both reports were pretty minimal.
+ After reminder last month, no one stepped up to submit a report.
- The project is very inactive.
+ The only non-jira message to dev@giraph was from a board member.
+ There were 15 jiras created, but none committed.
+ Last release 10/21/2016.
## Activity:
- None.
## Health report:
- Very quiet
## PMC changes:
- Currently 12 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Sergey Edunov on Wed Aug 24 2016
## Committer base changes:
- Currently 19 committers.
- No new committers added in the last 3 months
- Last committer addition was Hassan Eslami at Fri Jul 15 2016
## Releases:
- Last release was 1.2.0 on Thu Oct 20 2016
## Mailing list activity:
- As stated above, only 1 non-jira message was sent to dev by a board
member. The 2 messages to user were about Gora's release and
Gora-Giraph.
- dev@giraph.apache.org:
- 278 subscribers (down -1 in the last 3 months):
- 67 emails sent to list (32 in previous quarter)
- user@giraph.apache.org:
- 455 subscribers (down -5 in the last 3 months):
- 2 emails sent to list (2 in previous quarter)
## JIRA activity:
- 15 JIRA tickets created in the last 3 months
- 0 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment X: Report from the Apache Gora Project [Lewis John McGibbney]
## Description:
The Apache Gora open source framework provides an in-memory data model
and persistence for big data. Gora supports persisting to
* column stores,
* key value stores,
* document stores,
* distributed in-memory key/value stores,
* in-memory data grids,
* in-memory caches,
* distributed multi-model stores, and
* hybrid in-memory architectures
Gora also enables analysis of data with extensive Apache Hadoop MapReduce
and Apache Spark support. Gora uses the Apache Software License v2.0.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
Project activity has been low. Nothing worrying as we shipped 0.8
not too long ago and have received no big fixes in that period. The
PMC discussed evolving the project description. The new descripion
can be seen above, this reflects several years of GSoC contributions
and a wide variety of community input over the years.
## Health report:
Post GSoC and 0.8 release, things have quietened somewhat. The
mailing lists however are still active and queries are answered
in a timely manner.
## PMC changes:
- Currently 25 PMC members.
- New PMC members:
- Madhawa Kasun Gunasekara was added to the PMC on Fri Sep 22 2017
- Nishadi Kirielle was added to the PMC on Sun Sep 10 2017
## Committer base changes:
- Currently 25 committers.
- New commmitters:
- Madhawa Kasun Gunasekara was added as a committer on Thu Sep 21 2017
- Nishadi Kirielle was added as a committer on Mon Sep 11 2017
## Releases:
- 0.8 was released on Mon Sep 18 2017
## Mailing list activity:
We recently received a mailing list request for Google BigTable
integration so it is encouraging that people are using Gora
for new things.
- dev@gora.apache.org:
- 73 subscribers (down -1 in the last 3 months):
- 229 emails sent to list (559 in previous quarter)
- user@gora.apache.org:
- 78 subscribers (down -3 in the last 3 months):
- 48 emails sent to list (9 in previous quarter)
-----------------------------------------
Attachment Y: Report from the Apache Groovy Project [Guillaume Laforge]
## Description:
Apache Groovy is a multi-faceted programming language for the Java platform.
Groovy is a powerful, optionally typed and dynamic language, with static-
typing and static compilation capabilities, aimed at multiplying developers’
productivity thanks to a concise, familiar and easy to learn syntax. It
integrates smoothly with any Java program, and immediately delivers to your
application powerful features, including scripting capabilities, Domain-
Specific Language authoring, first class functional programming support
and runtime and compile-time meta-programming.
## Issues:
There are no new issues arising requiring board attention at this time.
Update on a previous issue (website update) is still being tracked by
these 3 tickets:
- GROOVY-8181: Website move - step 1:
create new repositories for user and dev sites
- GROOVY-8182: Website move - step 2:
populate user and dev sites splitting current content
- GROOVY-8183: Website move - step 3:
generate user and dev sites from repo content
Of these, step 1 and step 2 (previously reported) are complete.
Some work has begun on step 3. We are still exploring how to adapt our
current site generation scripts to work with existing Apache tools in this
area (e.g. Buildbot). As well as automating some manual steps taken to
complete step 2, part of step 3 completes the move of the website fully
onto Apache infrastructure. Due to time constraints completion of this
step has been slower than we would like but progress is being made.
## Activity:
This quarter, 279 commits were contributed from 24 contributors
including 19 non-committer contributors (12 new).
## Health report:
With the progress on the build and release aspects of the project,
our release train has increased velocity, and the community seems
happy to see us being back on track with regular releases.
## PMC changes:
- Currently 10 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was John Wagenleitner on Sun Apr 02 2017
## Committer base changes:
- Currently 18 committers.
- No new committers added in the last 3 months
- Last committer addition was Sergei Egorov at Thu Dec 08 2016
## Releases:
- 2.5.0-beta-2 was released on Mon Oct 02 2017
- 2.6.0-alpha-1 was released on Wed Sep 06 2017
## Mailing list activity:
- users@groovy.apache.org:
- 419 subscribers (up 5 in the last 3 months):
- 123 emails sent to list (157 in previous quarter)
- dev@groovy.apache.org:
- 243 subscribers (up 8 in the last 3 months):
- 201 emails sent to list (134 in previous quarter)
## JIRA activity:
- 90 JIRA tickets created in the last 3 months
- 58 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment Z: Report from the Apache Hama Project [Edward J. Yoon]
-----------------------------------------
Attachment AA: Report from the Apache HTTP Server Project [Daniel Gruno]
## Description:
- The Apache HTTP Server is an open-source HTTP server for modern operating
systems including UNIX, Microsoft Windows, Mac OS/X and Netware.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
Two releases, 2.4.28 and 2.4.29, were cut for the 2.4 branch.
Discussion is underway for a possible 2.5.0 alpha release. It was decided to
do some pruning of our (visible) branches in svn, to make it less muddy when
browsing our source code.
## Health report:
The project remains in good health. What follows is a slightly more
technical/academic analysis than usual.
Code-wise, activity has been pretty much the same as in the past quarter with
roughly the same number of committers and commits. Diversity-wise, httpd
remains at a Pony Factor[1] of 5-6, which is a solid diversity score for a
project of httpd's age.
Email-wise, the PF score is currently 5 for dev@ and 46 for the users@ list,
arguably because a handful of people are responsible for the bulk of helping
users with issues.
Retention-wise, the community has managed to retain a steady amount of people
over the past 6 years, "idling" at around 35 people actively working on code,
700ish people active on the mailing list, and some 250 working on bugzilla
issues. The bulk of people working on code has a five year or longer
experience with httpd. We can interpret this as two distinct causes: 1) We are
excellent at retaining people we take under our wings as committers, but also
2) We need to put more effort into getting new committers (the average httpd
coder has spent nearly 8 years working on httpd).
While I'm sure the PMC will discuss ways to engage with newcomers and make
working on the httpd project more accessible and appealing to more people, I
wish to also point out that we have maintained this status for more than six
years. So...we excel at retaining, but we could also do with some fresh blood
in the ranks.
Using Apache Kibble, I have also personally been able to assess more social
aspects of the community, and I am pleased to note that the overall mood of
our mailing lists are above average for the ASF. The take-away here being
that we for the most part adhere well to the ASF code of conduct. See
mailing list section below for more information.
[1] https://ke4qqq.wordpress.com/2015/02/08/pony-factor-math/
## PMC changes:
- Currently 49 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Steffen Land on Mon Feb 27 2017
## Committer base changes:
- Currently 119 committers.
- No new committers added in the last 3 months
- Last committer addition was Daniel Ferradal at Wed Apr 26 2017
## Releases:
- 2.4.28 was released on Thu Oct 05 2017
- 2.4.29 was released on Mon Oct 23 2017
## Mailing list activity:
Mailing list activity remains steady. August was slower than the other months,
likely due to summer vacations ending there. 812 emails were sent to our user
and dev lists by 143 people, spread over 242 topics.
We have had to re-iterate to people that the ASF has a code of conduct that
should be followed. As a result, a member of the mailing list was removed for
continuously failing to follow these guidelines.
## Bugzilla Statistics:
BugZilla stats are pretty much identical to past quarter:
- 71 Bugzilla tickets created in the last 3 months by 61 people
- 51 Bugzilla tickets resolved in the last 3 months by 12 people
-----------------------------------------
Attachment AB: Report from the Apache HttpComponents Project [Asankha Chamath Perera]
## Description:
- The Apache HttpComponents project is responsible for creating and
maintaining a toolset of low-level Java components focused on HTTP and
associated protocols
## Issues:
- There are no issues requiring board attention at this time.
- The board has asked about prospective PMCs or committers, but
we do not have any at this moment.
## Activity:
- The HttpCore 5.0 beta 1 has been released with HTTP/2 support
## Health report:
- Overall the project remains active. Although established in late 2007
the project remains stable and active as seen by JIRA and Emails.
- The number of emails could be seen as low, but it is stable like the state
of the project, and we still have interested people contributing.
## PMC changes:
- Currently 9 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Michael Osipov on Mon Aug 24 2015
## Committer base changes:
- Currently 18 committers.
- No new committers added in the last 3 months
- Last committer addition was Julian Sedding at Fri Sep 30 2016
## Releases:
- HttpCore 4.4.7 GA was released on Thu Sep 14 2017
- HttpCore 4.4.8 was released on Sat Oct 07 2017
- HttpCore 5.0-alpha4 was released on Mon Sep 04 2017
- HttpCore 5.0-beta1 was released on Mon Nov 06 2017
-----------------------------------------
Attachment AC: Report from the Apache Ignite Project [Denis A. Magda]
## Description:
- Apache Ignite is an in-memory computing platform that is strongly consistent
and highly available with powerful SQL, key-value, and processing APIs.
## Comments
The section includes commentaries on questions raised by board members during
at the previous board meeting.
Q1: it would be good to include a note about the ignite.run data collection
issue and it's resolution in the official board report.
The issue was solved. The ignite.run domain was transferred to ASF and shut
down. All the statistics collected before was purged. Presently, an Ignite
node process connects to this page [1] deployed on ASF to find out the latest
Ignite version and notify a user about its availability. No user data is
collected at all.
Q2: Ignite has historically been very tightly aligned with a single vendor.
How are efforts going forward to add more diversity?
The community is becoming more and more diversified. Specifically, we see many
contributors coming from the financial sector (banks, etc.) who widely use
Ignite in production and want to take part in its development. Next, the
community is about to accept a big contribution by NetMillennium, Inc [2].
Finally, Ignite members take part in a myriad of events (meetups, conferences,
webinars) to expand awareness of the project and get more contributors. At
all, I wouldn’t say that presently the project is somehow tightly aligned with
a single vendor.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- Apache Ignite 2.2 and 2.3 were released since the time of the previous
report.
- Filed a trademark request for Apache Ignite. The request has been awaiting
the examination.
- More than 30 talks were conducted by community members and Ignite users at
various meetups, conferences, and webinars.
## Health report:
- The popularity of Ignite continues to grow. We see it in an increased number
of users, contributors, discussions, releases.
## PMC changes:
- Currently 24 PMC members.
- Pavel Tupitsyn was added to the PMC on Mon Aug 28 2017
## Committer base changes:
- Currently 33 committers.
- No new committers added in the last 3 months
- Last committer addition was Igor Sapego at Thu Mar 02 2017
## Releases:
- 2.2.0 was released on Mon Sep 18 2017
- 2.3.0 was released on Tue Oct 31 2017
[1] https://ignite.apache.org/latest
[2]
http://apache-ignite-developers.2346864.n4.nabble.com/GA-Grid-Request-to-contr
ibute-GA-library-to-Apache-Ignite-td23920.html
-----------------------------------------
Attachment AD: Report from the Apache Incubator Project [John D. Ament]
Incubator PMC report for November 2017
The Apache Incubator is the entry path into the ASF for projects and
codebases wishing to become part of the Foundation's efforts.
October was a quieter month in the incubator. We executed 4 podling releases, had
no changes in staff. One new podling joined, and are having graduation discussions
for two podlings. We expect Mnemonic to fully graduate this month.
* Community
New IPMC members:
- None
People who left the IPMC:
- None
* New Podlings
- SDAP
* Podlings that failed to report, expected next month
- iota (discussing retirement)
- Milagro
- Myriad
* Graduations
The board has motions for the following:
- Guacamole
- Impala
- Mnemonic
* Releases
The following releases entered distribution during the month of
October:
- 2017-10-04 Apache Juneau 6.4.0
- 2017-10-11 Apache Rya 3.2.11
- 2017-10-13 Apache Pulsar 1.20.0
- 2017-10-30 Apache MXNet 0.12.0
----------------------------------------------------------------------
Table of Contents
Amaterasu
Daffodil
Edgent
Guacamole
Heron
Impala
Joshua
Milagro
PageSpeed
Ratis
S2Graph
Slider
Tamaya
Toree
Unomi
----------------------------------------------------------------------
--------------------
Amaterasu
Apache Amaterasu is a framework providing continuous deployment for Big
Data Pipelines.
It provides the following capabilities:
Continuous integration tools to package pipelines and run tests.
A repository to store those packaged applications: the applications
repository.
A repository to store the pipelines, and engine configuration (for
instance, the location of the Spark master, etc.): per environment - the
configuration repository.
A dashboard to monitor the pipelines.
A DSL and integration hooks allowing third parties to easily integrate.
Amaterasu has been incubating since 2017-09.
Three most important issues to address in the move towards graduation:
1. Prepare the first release
2. Grow up user and contributor communities
3. Prepare documentation
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?
* Talks have been given in different events to promote and give
visibility to Amaterasu
How has the project developed since the last report?
* Code based was moved to the ASFs git box
* One new pull request was issued
Date of last release:
N/A
When were the last committers or PMC members elected?
N/A
[X] Initial setup
[ ] Working towards first release
[ ] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
N/A
Signed-off-by:
[X](amaterasu) Jean-Baptiste Onofré
Comments:
[X](amaterasu) Olivier Lamy
Comments:
[X](amaterasu) Davor Bonaci
Comments: Initial setup continues: codebase has moved to the ASF repository.
--------------------
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. Obtaining SGAs
2. Establishing new apache-centric infrastructure
3. Broadening base of contributors
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
- Only that chasing the SGAs down is going to take some time, though
this may be typical.
How has the community developed since the last report?
- Users: No change.
- Developers/Contributors: No change.
How has the project developed since the last report?
- Completed setup of the git repo.
- Started process of transfer of existing JIRA
tickets to Apache.
- Established our contributor/branch workflow and
published to wiki.
- Submitted Tresys SGA.
- Progress is being made on obtaining organizational
SGAs from NCSA and IBM.
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:
XXXX-XX-XX
When were the last committers or PPMC members elected?
- No changes yet - same as at our project incubator
inception
Signed-off-by:
[X](daffodil) John D. Ament
Comments:
[X](daffodil) David Fisher
Comments:
--------------------
Edgent
Apache Edgent is a programming SDK and micro-kernel style runtime
that can be embedded in gateways and small footprint edge devices enabling
local, real-time, analytics on the continuous streams of data coming
from equipment, vehicles, systems, appliances, devices and sensors of
all kinds (for example, Raspberry Pis or smart phones). Working in
conjunction with centralized analytic systems, Apache Edgent provides
efficient and timely analytics across the whole IoT ecosystem: from the
center to the edge.
Edgent has been incubating since 2016-02-29.
Three most important issues to address in the move towards graduation:
1. Create and expand a diverse community of contributors and committers
around the Edgent project.
2. Attracting at least another independent committer/ppmc member.
3. Finding further real world users of Edgent
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
While two contributors are still quite active working on
the conversion to maven and towards getting out the next release,
there has been very little other community or dev list activity.
How has the community developed since the last report?
* Will Marshall had a meetup in San Francisco on the 20th of September
to demonstrate an Edgent video analytics application which was
initially presented at ApacheCon 2017 (Video Analytics at the Edge:
Fun with Apache Edgent, OpenCV and a Raspberry Pi).
* Christofer Dutz gave a presentation at Solutions Hamburg that
included Apache Edgent.
* There was one new non-committer enhancement/PR merged.
* There was one JIRA from a new individual: asked & answered.
* Total, we have 73 subscribers to our mailing list, an improvement
of 3 since the last report.
How has the project developed since the last report?
* Two contributors/committers have been very active overhauling the
Edgent build system to Maven from Gradle on the features/maven
branch. We are very close to merging and working on a release.
Maven provides benefits over Gradle, including a more rigid build
structure, the Maven package system, and ASF release process integration.
The work includes a variety of other cleanup / usability items,
such as how we distribute Edgent samples and how users build them.
* According to JIRA, 6 new issues were added to the project and
2 issues have been resolved or closed between August 2017 and October 2017.
11 issues are in progress as part of PR-309 (the maven work).
How would you assess the podling's maturity?
Edgent is making slow but consistent progress towards graduation. While we
don't yet meet the diversity requirements, we put emphasis on community
growth through outreach which will ultimately pave the way for additional
committers and contributors.
Additionally, before we graduate it is important that we find users
outside of IBM. As most Edgent committers are employed by IBM, external
stakeholders help ensure long term contribution to the project.
[ ] Initial setup
[ ] Working towards first release
[X] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
2017-05-17
When were the last committers or PPMC members elected?
In August 2017, we added Christofer Dutz as a new committer
and PPMC member.
Signed-off-by:
[ ](edgent) Daniel Debrunner
Comments:
[ ](edgent) Luciano Resende
Comments:
[ ](edgent) Justin Mclean
Comments:
[X](edgent) John D. Ament
Comments: The podling is still growing. I don't believe things have changed
since I joined as mentor a few months ago. To be able to graduate, they need
to have a truly viable community with actual features coming in.
IPMC/Shepherd notes:
Development and the number of developers working on the project have fallen off. Dave Fisher.
--------------------
Guacamole
Guacamole is an enterprise-grade, protocol-agnostic, remote desktop gateway.
Combined with cloud hosting, Guacamole provides an excellent alternative to
traditional desktops. Guacamole aims to make cloud-hosted desktop access
preferable to traditional, local access.
Guacamole has been incubating since 2016-02-10.
Three most important issues to address in the move towards graduation:
1. Reach consensus on graduation resolution DISCUSS thread (general@)
2. Call IPMC graduation vote
3.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
None.
How has the community developed since the last report?
The community has discussed, voted upon, and approved a resolution to
graduate to TLP. This resolution is now being discussed on the general@
list, prior to calling the IPMC graduation vote.
Community activity on the mailing lists continues to be productive and
increasing, with the user@ list now receiving an average of 201 posts per
month.
Overall:
Report | Period | Avg. posts (per month)
--------------+--------------------+------------------------
May 2016 (1) | (START) .. 2016-04 | 0 (Not yet migrated)
Aug 2016 (2) | 2016-05 .. 2016-07 | 90
Nov 2016 (3) | 2016-08 .. 2016-10 | 108
Feb 2017 (4) | 2016-11 .. 2017-01 | 129
May 2017 (5) | 2017-02 .. 2017-04 | 164
Aug 2017 (6) | 2017-05 .. 2017-07 | 171
Nov 2017 (7) | 2017-08 .. 2017-10 | 201
How has the project developed since the last report?
A new release is underway, a new committer (Carl Harris) has been accepted,
and things are moving forward with respect to graduation.
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-07-30 (0.9.13-incubating)
When were the last committers or PPMC members elected?
The following committers have been elected since Guacamole began incubation:
* Carl Harris - 2017-10-19
* Nick Couchman - 2017-02-09
* Frode Langelo - 2016-04-03
As of the VOTE on 2016-12-09, all committers are implicitly members of the
PPMC.
Signed-off-by:
[ ](guacamole) Jean-Baptiste Onofre
Comments:
[x](guacamole) Daniel Gruno
Comments:
[ ](guacamole) Jim Jagielski
Comments:
[X](guacamole) Greg Trasuk
Comments:
--------------------
Heron
A real-time, distributed, fault-tolerant stream processing engine.
Heron has been incubating since 2017-06-23.
Three most important issues to address in the move towards graduation:
1. Finish bootstrapping project, IP clearance, initial website
2. Expanding the community and adding new committers
3. 1st ASF release
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
In LEGAL-339[1] clarification was provided that the project could move into Apache
git without having an SGA in place. The Heron team has developed a migration plan[2]
forward into Apache which is currently being discussed.
1 - https://issues.apache.org/jira/browse/LEGAL-339
2 - https://lists.apache.org/thread.html/a83095cd44e09fa179c4b5034e04acdb055a671406f1501a796700e0@%3Cdev.heron.apache.org%3E
How has the community developed since the last report?
* One new developer has approached the dev list to volunteer to drive the Heron/Scala implementation.
How has the project developed since the last report?
* Development has been active, despite limited progress migrating to Apache infra.
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:
XXXX-XX-XX
When were the last committers or PPMC members elected?
Signed-off-by:
[X](heron) Jake Farrell
Comments:
[ ](heron) Jacques Nadeau
Comments:
[ ](heron) Julien Le Dem
Comments:
[X](heron) P. Taylor Goetz
Comments:
IPMC/Shepherd notes:
Drew Farris (shepherd): Three mentors active on the mailing list. Aside from the
issues around the SGA, it appears the project is still in process of adopting
Apache infrastructure for project communication.
--------------------
Impala
Impala is a high-performance C++ and Java SQL query engine for data stored in
Apache Hadoop-based clusters.
Impala has been incubating since 2015-12-03.
Three most important issues to address in the move towards graduation:
Our graduation proposal is in the works.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
No
How has the community developed since the last report?
There have been 279 Commits:
git log --format='%ci' | grep -cE '2017-(08|09|10)'
62 of those commits were by non-committers:
git log --format='%an %ci' | grep -E '2017-(08|09|10)' | tr -d '0-9\-' | cut -d ' ' -f -2 | sort | uniq -c | sort -n
Of the 37 patch authors, 16 were not committers at the beginning of this reporting period.
There are three new committers members and one new PPMC member:
https://lists.apache.org/list.html?dev@impala.apache.org:dfr=2017-8-1|dto=2017-10-31:%22has%20invited%22
Impala has done a fourth release with a third release manager.
Impala has begun graduation procedures: we have held a community discussion and a
community vote on graduation, both unanimous. We have established our intended PMC.
Next, we will draft our charter and hold a discussion on general@incubator.
How has the project developed since the last report?
Impala has removed the old unpartitioned hash and aggregation nodes, relics from
years ago that were kept around for backwards compatibility: the new buffer management
makes these obsolete. Code generation for decimal and timestamp types has been added
to the text scanner, increasing the performance of some queries by up to 19%. More
robust query plans in case of data skew have made some aggregations eight times as fast.
A number of large changes are in-flight, including changes to equivalence class computation
in the planner, more decimal semantics adjustments, min-max filters for Kudu, and
multi-threaded metadata loading that increases the performance of some metadata operations by 8x.
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-09-14
When were the last committers or PPMC members elected?
2017-09-29
Signed-off-by:
[ ](impala) Tom White
Comments:
[X](impala) Todd Lipcon
Comments:
[ ](impala) Carl Steinbach
Comments:
[X](impala) Brock Noland
Comments:
IPMC/Shepherd notes:
Drew Farris (shepherd): Three mentors active on the mailing lists, healthy project, excellent progress towards graduation.
--------------------
Joshua
Joshua is a statistical machine translation toolkit
Joshua has been incubating since 2016-02-13.
Three most important issues to address in the move towards graduation:
1. Make another Apache Joshua incubating release (7.0.0).
2. Identifying specific use cases that Joshua might excel at.
3. Attracting active developers and users.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
None
How has the community developed since the last report?
The community mailing lists continue to see a few new users
requiring assistance with using the project.
Questions have been answered in reasonable time. Community
building continues to be the biggest challenge for Joshua right
now.
How has the project developed since the last report?
The PPMC is actively working towards a 7.0.0 release
candidate which will essentially be a re-modularization of
the Joshua source code for distribution and hopefully
improved consumption as a dependency within other projects.
We have seen a few pull requests logged specifically addressing
source code formatting, this is a positive.
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
[X] Nearing graduation
[ ] Other:
Date of last release:
2017-06-22
When were the last committers or PPMC members elected?
- 2016-11-16 Michael A. Hedderich (mhedderich) joins the Joshua PPMC +
Committership.
- 2016-11-16 Tobias Domhan (tdomhan) joins the Joshua PPMC + Committership.
- 2016-11-02 Max Thomas (mthomas) joins the Joshua PPMC + Committership.
Signed-off-by:
[ ](joshua) Paul Ramirez
Comments:
[X](joshua) Lewis John McGibbney
Comments: I suspect that the Joshua PPMC will move towards proposing the
project graduates post 7.0.0 release. I am working with Tommaso to progress
the 7.X branch merge into mainstream development.
[ ](joshua) Chris Mattmann
Comments:
[ ](joshua) Tom Barber
Comments:
IPMC/Shepherd notes:
johndament: The project seems OK. Not a lot of on list chatter, outside of JIRA. May be
ready, may warrant some additional time growing. Will leave it to mentors to decide.
--------------------
Milagro
Distributed Cryptography; M-Pin protocol for Identity and Trust
Milagro has been incubating since 2015-12-21.
Three most important issues to address in the move towards graduation:
1. Improve project communication
2. Discuss a possible project roadmap
3. Building the community
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?
No new committers were added since the last report.
How has the project developed since the last report?
After some expressed concerns, it was decided that the crypto code will be moved back to the Apache repository.
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup
[x] 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:
[ ](milagro) Sterling Hughes
Comments:
[ ](milagro) Jan Willem Janssen
Comments:
[X](milagro) Nick Kew
Comments:
Comments sent to project list. Project activity needs to be visible @apache!
IPMC/Shepherd notes:
johndament: The podling is not in good shape. We need to follow up to understand current
state. May request an additional report next month to clarify.
--------------------
PageSpeed
PageSpeed represents a series of open source technologies to help make the web
faster by rewriting web pages to reduce latency and bandwidth.
PageSpeed has been incubating since 2017-09-30.
Three most important issues to address in the move towards graduation:
1. Finish project setup
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 initial committers have submitted ICLAs (when needed), and accounts
have been setup. Mailing list were created.
- We have seen activity from two unaffiliated developers. One is contributing
to solving a complex issue and another is helping out with FreeBSD platform
support.
How has the project developed since the last report?
- We are working on the transfer of IP from Google to the ASF.
- Someone worked on FreeBSD compatibility and added a port based on the
latest stable mod_pagespeed release:
https://svnweb.freebsd.org/changeset/ports/452011
- Progress was made on Alpine support.
- Progress was made on Content-Security-Policy support.
- A couple of bugs have been solved.
- The Google hosted pagespeed-dev@ mailing list was been notified of the newly
created dev@ list.
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[X] Initial setup
[ ] 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-09-30
Signed-off-by:
[X](pagespeed) Jukka Zitting
Comments:
[X](pagespeed) Leif Hedstrom
Comments:
[X](pagespeed) Nick Kew
Comments:
[ ](pagespeed) Phil Sorber
Comments:
--------------------
Ratis
Ratis is a java implementation for RAFT consensus protocol
Ratis has been incubating since 2017-01-03.
Three most important issues to address in the move towards graduation:
1. Setup Jenkins (In Progress)
2. Add new committers
3. Work towards a beta 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?
7 new contributors have been added. Total 36 contributors currently.
How has the project developed since the last report?
Ratis delivered its first release, alpha release 0.1.0-alpha has been made available.
39 new commits to the project.
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup - Jenkins setup is in progress
[ ] Working towards first release - First release 0.1.0-alpha is available. Discussion about 0.2-alpha has started.
[ ] Community building - Many new contributors. Need to get new committers
[ ] Nearing graduation
[ ] Other:
Date of last release:
2017-05-17
When were the last committers or PPMC members elected?
- Initial set of committers/PPMC.
Signed-off-by:
[ ](ratis) Chris Nauroth
Comments:
[x](ratis) Jakob Homan
Comments:
[X](ratis) Uma Maheswara Rao G
Comments:
[ ](ratis) Devaraj Das
Comments:
IPMC/Shepherd notes:
Dave Fisher:
I am concerned that this podling has 36 contributors but has never added committers/PPMC members.
PPMC and Mentors should handle this regularly. I've sent a note to private. Let's see when it is moderated.
--------------------
S2Graph
S2Graph is a distributed and scalable OLTP graph database built on Apache
HBase to support fast traversal of extremely large graphs.
S2Graph has been incubating since 2015-11-29.
Three most important issues to address in the move towards graduation:
1. Make a third release.
2. Attract more users and contributors.
3. Build the developer community in both size and diversity.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
None
How has the community developed since the last report?
* We had our second official release 0.2.0 on Aug 26th 2017.
* There have been 2 PR from a new contributor
How has the project developed since the last report?
* Discuss the scope of next release.
- New Feature: Provide java client. (on going S2GRAPH-80)
- New Feature: Support more storage backend implementation. (ongoing S2GRAPH-169, S2GRAPH-166)
- New Feature: Support more Index Provider implementation. (not started)
- New Feature: Implement TinkerPop`s Graph Compute for OLAP support (not started)
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-08-26
When were the last committers or PPMC members elected?
None
Signed-off-by:
[ ](s2graph) Andrew Purtell
Comments:
[ ](s2graph) Seetharam Venkatesh
Comments:
[X](s2graph) Sergio Fernández
Comments: Community building it's the major cornerstone towards graduation.
--------------------
Slider
Slider is a collection of tools and technologies to package, deploy, and
manage long running applications on Apache Hadoop YARN clusters.
Slider has been incubating since 2014-04-29.
Three most important issues to address in the move towards graduation:
1. Apache Slider community/PPMC has voted to move portions of Slider into
Apache Hadoop YARN as modules. It is possible that the remaining pieces
will be moved at a later point in time or become obsolete or evolve to
work closely with YARN. A vote was initiated in the Apache Hadoop
community to merge all Slider specific changes (now referred to as YARN
Services) from a branch to trunk. Expectation is to make YARN Services
an integral part of Apache Hadoop 3.x release. Few issues were raised
on the changes in the branch, but all have been addressed and a new
vote was initiated on Oct 30, 2017.
2. Getting more external users
3. Growth of a diverse set of developers/committers/PMC members
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?
No.
How has the community developed since the last report?
Mailing list activity has been lower due to the bulk of the development
moving to an Apache Hadoop branch. Questions on usage and issues
encountered by end users keep coming at regular intervals, keeping the DL
somewhat active.
How has the project developed since the last report?
Work continues in parallel on the Apache Hadoop yarn-native-services
branch and on the Slider podling. The bulk of the work has been in
yarn-native-services. However, quite a few Fortify identified issues,
a new feature for Percentage based Health Monitor support (SLIDER-1246) and
a few Slider patches (related to critical issues or agent-only issues) have
been committed to the Slider podling, since the last report.
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-03-23 slider-0.92.0-incubating
When were the last committers or PPMC members elected?
2015-07-07: Yu (Thomas) Liu
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: Work happening in Apache Hadoop YARN project has reached a critical milestone -
the Apache Hadoop community has voted and Slider functionality is now merged into Apache
Hadoop trunk. It is potentially going to be part of the Apache Hadoop 3.1 release. Slider
community to summarize this on dev-list and figure out the mechanics of working with
Incubator to retire the Slider project and draw plans for hosting old releases, supporting
and migrating existing applications etc.
--------------------
Tamaya
Tamaya is a highly flexible configuration solution based on an modular,
extensible and injectable key/value based design, which should provide a
minimal but extendible modern and functional API leveraging SE, ME and EE
environments.
Tamaya has been incubating since 2014-11-14.
Three most important issues to address in the move towards graduation:
1. Announce release 0.3 properly
2. Prepare release 0.4 (end of November)
3. Grow community and get more active developers as a TLP
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
We'd like to graduate after 0.4 is out, maybe Q1-2018.
How has the community developed since the last report?
A lot of discussion/bugreport/fixing concerning the upcoming OSGi features on the mailing list.
Unfortunately not yet any new committers.
Members of the project have joined the official Configuration JSR (Anatole/John)
How has the project developed since the last report?
We've introduced new features such as OSGi support and full Java8 compatibility
while raising test and mutation test coverage.
Apart from that the upcoming 0.4-SNAPSHOT has Microprofile API support.
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
[X] Nearing graduation
[ ] Other:
Date of last release:
2017-08-01
When were the last committers or PPMC members elected?
P. Ottlinger at 2016-04-24.
Signed-off-by:
[X](tamaya) John D. Ament
Comments: Its clear to me that the podling has a rough understanding of Apache Way.
However, I think they need the marketing side to pick up to draw some interest.
[ ](tamaya) David Blevins
Comments:
--------------------
Toree
Toree provides applications with a mechanism to interactively and remotely
access Apache Spark.
Toree has been incubating since 2015-12-02.
Three most important issues to address in the move towards graduation:
1. More discussion and engagement on the mailing list as opposed to "gitter"
2. Community growth
3. Continue to make releases
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
* No issues require attention at this time.
How has the community developed since the last report?
* We are waiting for an IPMC vote on the 0.2.0 release.
How has the project developed since the last report?
* Cleaning up existing PRs and voting the 0.2.0 release in the PPMC
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-02-21
When were the last committers or PPMC members elected?
* Ryan Blue was added to the PMC on 2017-04-03
Signed-off-by:
[x](toree) Luciano Resende
Comments:
[ ](toree) Reynold Xin
Comments:
[x](toree) Hitesh Shah
Comments:
[ ](toree) Julien Le Dem
Comments:
[ ](toree) Ryan Blue
Comments:
IPMC/Shepherd notes:
Podling is in good shape. Dave Fisher
--------------------
Unomi
Unomi is a reference implementation of the OASIS Context Server specification
currently being worked on by the OASIS Context Server Technical Committee. It
provides a high-performance user profile and event tracking server.
Unomi has been incubating since 2015-10-05.
Three most important issues to address in the move towards graduation:
1. Keep a good pace in releases
2. Still increase the communities (both dev and user)
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 user community grew up (according messages and feedback we go). We started
to review the maturity matrix in preparation for a graduation proposal.
How has the project developed since the last report?
1.2.0-incubating has been released including a bunch of bug fixes and improvements.
Now that 1.2.0-incubating has been released, we are heading to 2.0.0-incubating on the dedicated branch.
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-09-20
When were the last committers or PPMC members elected?
2017-01-23
Signed-off-by:
[ ](unomi) Bertrand Delacretaz
Comments:
[X](unomi) Jean-Baptiste Onofre
Comments:
-----------------------------------------
Attachment AE: Report from the Apache JSPWiki Project [Juan Pablo Santos Rodríguez]
## Description:
- A feature-rich and extensible WikiWiki engine built around the standard
JEE components (Java, servlets, JSP).
## Issues:
- there are no issues requiring board attention at this time.
## Activity:
- It's been another quiet quarter, with only a couple of commits needed to
complete markup's parsing and rendering decoupling, so that other
alternatives to JSPWiki markup parser / renderer can be used.
- As something stripped from @dayjob, Markdown support will hopefully
arrive next weeks (see "Markdown support" thread at dev@jspwiki.a.o for
details [1]), at least for discussion and study. Scope and things
remaining to be done still ongoing at dev@jspwiki.a.o
## Health report:
- Another quiet quarter, but enough people from PMC show up to provide
oversight.
- Several ideas being discussed at user@jspwiki.a.o to increase
contributions [2], namely:
* move to Github as primary repo
* lower committership barrier by granting commits rights to
a) any ASF committer
b) any other people who simply asks for it
* adopting something similar to a release train, and release
master every four months or so
## PMC changes:
- Currently 11 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Dave Koelmeyer on Wed Apr 06 2016
## Committer base changes:
- Currently 16 committers.
- No new committers added in the last 3 months
- Last committer addition was Dave Koelmeyer at Wed Apr 06 2016
## Releases:
- Last release was 2.10.2 on Sat Feb 20 2016
## Mailing list activity:
- dev@jspwiki.apache.org:
- 85 subscribers (up 0 in the last 3 months):
- 31 emails sent to list (39 in previous quarter)
- user@jspwiki.apache.org:
- 178 subscribers (down -1 in the last 3 months):
- 23 emails sent to list (13 in previous quarter)
## JIRA activity:
- 1 JIRA tickets created in the last 3 months
- 0 JIRA tickets closed/resolved in the last 3 months
[1]: https://s.apache.org/KXQO
[2]: https://s.apache.org/prGg
-----------------------------------------
Attachment AF: Report from the Apache jUDDI Project [Alex O'Ree]
## Description:
jUDDI (pronounced "Judy") is an open source Java implementation of the
Universal Description, Discovery, and Integration (UDDI v3)
specification for (Web) Services. The jUDDI project includes Scout.
Scout is an implementation of the JSR 93 - Java API for XML Registries
1.0 (JAXR).
## Issues:
There are no issues that require the boards attention at this time.
## Activity:
jUDDI
- Aside from JIRA, Buildbot and commit emails, all mailing lists have had
low traffic this quarter with some additional out of band email traffic
from one user.
- There were a number of new issues created and fixed, primarily bug fixes
and stability improvements discovered from findbugs.
Scout
- No release this period, no development took place.
- No JAXR related questions on the mailing list.
## PMC changes:
- Currently 7 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Alex O'Ree on Sun Mar 17 2013
## Committer base changes:
- Currently 7 committers.
- No new changes to the committer base since last report.
## Releases:
- Last release was 3.3.4 on Fri Feb 10 2017
- Next Release jUDDI-3.3.5, Planned for Dec 2017
## Mailing list activity:
- dev@juddi.apache.org:
- 74 subscribers (up 0 in the last 3 months):
- 186 emails sent to list (2 in previous quarter)
- user@juddi.apache.org:
- 119 subscribers (up 0 in the last 3 months):
- 5 emails sent to list (6 in previous quarter)
## JIRA activity:
- 16 JIRA tickets created in the last 3 months
- 22 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AG: Report from the Apache Juneau Project [James Bognar]
## Description:
- Juneau is a Java library used for constructing REST microservices using
marshalled POJOs.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- Juneau graduated from incubation on Oct 19, 2017.
- We quickly migrated our project off the incubator infrastructure and
released 7.0.0 as our first release as a top-level project on Oct 25, 2017.
- Press releases were made on Oct 31, 2017.
## PMC changes:
- Currently 9 PMC members.
- No new PMC members added in the last 3 months
## Committer base changes:
- Currently 9 committers.
- No changes (the PMC was established in the last 3 months)
## Releases:
- 7.0.0 was released on Oct 25 2017.
## Mailing list activity:
- dev@juneau.apache.org:
- 23 subscribers (up 2 in the last 3 months):
- 196 emails sent to list (326 in previous quarter)
-----------------------------------------
Attachment AH: Report from the Apache Kafka Project [Jun Rao]
Apache Kafka is a distributed streaming platform for efficiently storing and
processing a large number of records in real time.
Development
===========
We released 1.0.0! This is a big milestone of Apache Kafka after
7+ years of active development, which has accumulated key features such as
intra cluster replication,
compacted topics, security, connect, kstream, exactly-once semantics, among
others. 108 people contributed to the 1.0.0 release. More than 340 people have
contributed to Apache Kafka over time.
We are actively working on new features such as JBOD, delegation tokens,
additional
improvements of the controller, various improvements in kstream and connect,
etc.
Community
===========
Lots of activities in the mailing list. We have 2551 subscribers
in the user mailing list, up 78 in the last 3 months. We have 1268 emails in
the user mailing list in the last 3 months, a bit less than the 1631 in the
previous cycle. We have 1059 subscribers in the dev mailing list, up 55 in the
last 3 months. We have 4409 emails in the dev mailing list in the last 3
months, a bit less from the 6349 in the previous cycle.
We elected one new committer, Onur Karaman on Oct. 31, 2017. We elected one
new PMC member, Becket Qin on Aug. 23, 2017.
The next Kafka Summit in London in Apr. 2018 is now open for submission.
Releases
===========
0.11.0.1 was released on Sep. 13, 2017.
1.0.0 was released on Nov. 1, 2017.
-----------------------------------------
Attachment AI: Report from the Apache Kibble Project [Rich Bowen]
## Description:
Apache Kibble is a suite of tools for collecting, aggregating and
visualizing activity in software projects.
## Issues:
There are no issues requiring board attention at this time
## Activity:
The project is starting up as a TLP within the Apache family. October
was a month which saw many community members doing a ton of travel,
which hampered the project somewhat. Nonetheless, the project has
managed to set up its initial web site, code repositories, and a demo
instance of the Kibble software suite. The community will be working
towards defining goals and contacting interested parties (such as
other PMCs at Apache interested in taking part in our community
analyses). One of the many benefits of being part of the Apache family
is ready access to a lot of interesting projects from both a technical
and - equally important - community aspect, and we'll be working with
the ASF projects to determine what projects would like to see emerge
from Kibble in terms of trends, breakdowns, aggregations etc that can
help shed some light on how projects and their communities are doing.
There has also been discussion of what metrics are useful, or at
least potentially useful, and how we might engage with projects to
get their input on what metrics they consider important measures of
project health, as this will vary from one project to another, and
may be very different for projects outside of the ASF.
## Health report:
The project has sufficient (3+ PMC members) oversight.
It is too early to contemplate progression of community health,
but we will of course keep the board apprised of any changes.
## PMC changes:
- Currently 11 PMC members.
- All PMC members added in the last 3 months
## Committer base changes:
- Currently 11 committers.
- No changes (the PMC was established in the last 3 months)
## Releases:
- No releases yet. We tentatively plan to have our first release within
the next six months.
## Mailing list and bug tracker activity:
As we have just started, it makes little sense to discuss these stats yet.
-----------------------------------------
Attachment AJ: Report from the Apache Knox Project [Larry McCay]
## Description:
The Apache Knox Gateway is a REST API Gateway for interacting with Apache
Hadoop clusters. The Knox Gateway provides a single access point for all
REST/HTTP interactions with Apache Hadoop clusters.
## Issues:
There are no issues that requiring board attention at this time
## Activity:
The Apache Knox team is in the process of an active VOTE for our 0.14.0 release.
We will be immediately following up with our 1.0.0 release which will include
a repackaging of all of our class package names to remove "hadoop" from the name.
This will allow downstream consumers to take on new features in 0.14.0 without
moving to new package names in case of incompatibilities.
## Health report:
We have continued to use the KIP-# pages to drive the primary focus of each
release and feel it is working well. The 0.14.0 release was primarily
focused on the addition of the service discovery and simplified descriptors
(KIP-8) to improve and simplify management of topologies. It also includes
many improvements and bug fixes.
The current level of collaboration is healthy and encouraging within the
community on both mailing lists and JIRAs.
## PMC changes:
- Currently 15 PMC members.
- Jeffrey Rodriguez was added to the PMC on Thu Aug 24 2017
## Committer base changes:
- Currently 19 committers.
- New commmitters:
- Colm O hEigeartaigh was added as a committer on Sat Aug 19 2017
- Jeff Rodriguez was added as a committer on Fri Aug 25 2017
## Releases:
- Last release was 0.13.0: 2017-08-19 Added Topology Port Mapping,
support for new APIs and UIs, many improvements on
existing features, and fixes of a number of bugs - through
~71 commits.
- 0.14.0: Currently pending VOTE of the first RC
## Mailing list activity:
- The mailing list activity seems to continued growth in community activity.
- dev@knox.apache.org:
- 84 subscribers (up 4 in the last 3 months):
- 1526 emails sent to list (818 in previous quarter)
- user@knox.apache.org:
- 108 subscribers (up 6 in the last 3 months):
- 127 emails sent to list (42 in previous quarter)
## JIRA activity:
- 118 JIRA tickets created in the last 3 months
- 115 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AK: Report from the Apache Kylin Project [Luke Han]
## Description:
Apache Kylin is an open source Distributed Analytics Engine designed
to provide SQL interface and multi-dimensional analysis (OLAP) on
Hadoop supporting extremely large datasets.
## Issues:
- there are no issues requiring board attention at this time
## Activity:
- Dong Li presented Apache Kylin 2.x
at OSC on 2017-11-10 in Xian
- Dong Li presented Apache Kylin 2.x
at OSC on 2017-10-21 in Shenyang
- Yang Li presented Apache Kylin Open Source
at The Computing Conference on 2017-10-21 in Hangzhou
- Luke Han presented Apache Kylin & Use cases
at Strata NY on 2017-09-21 in New York
- Luke Han presented Kylin on Cloud
at MS Tech Summit NY on 2017-11-02 in Beijing
## PMC changes:
- Currently 18 PMC members.
- Last PMC addition was Billy Liu on Tue Oct 16 2017
## Committer base changes:
- Currently 30 committers.
- New commmitters:
- Guosheng Lu was added as a committer on Wed Oct 11 2017
- Wang Cheng was added as a committer on Thu Oct 12 2017
## Releases:
- 2.2.0 was released on Fri Nov 03 2017
- 2.1.0 was released on Fri Aut 17 2017
## Mailing list activity:
- dev@kylin.apache.org:
- 820 emails sent to list (745 in previous quarter)
- issues@kylin.apache.org:
- 2239 emails sent to list (1205 in previous quarter)
- user@kylin.apache.org:
- 351 emails sent to list (321 in previous quarter)
## JIRA activity:
- 243 JIRA tickets created in the last 3 months
- 192 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AL: Report from the Apache Lens Project [Amareshwari Sriramadasu]
## Description:
Lens provides an Unified Analytics interface. Lens aims to cut the Data
Analytics silos by providing a single view of data across multiple tiered
data stores and optimal execution environment for the analytical query. It
seamlessly integrates Hadoop with traditional data warehouses to appear like
one.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
- Stabilizing Cube segmentation and Virtual fact features.
- Bug fixes for drop partitions with update period, server's session state
persistence errors and sync queries in jdbc driver
- Release 2.7 is stabilized and is ready for vote
## PMC changes:
- Currently 18 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Puneet Gupta on Tue Sep 20 2016
## Committer base changes:
- Currently 22 committers.
- No new committers added in the last 3 months
- Last committer addition was Archana H at Sat May 21 2016
## Releases:
- Last release was 2.6 on Tue Oct 25 2016
-----------------------------------------
Attachment AM: Report from the Apache Libcloud Project [Tomaž Muraus]
## Description:
Libcloud is a Python library that abstracts away the differences among
multiple cloud provider APIs.
## Issues:
There are no issues which require board attention at this time.
## Activity:
We had two releases this quarter (one major one - 2.2.0) and overall we
received a good amount of activity and contributions from the team
members and external contributors.
We also added one new committer - Quentin Pradet.
## PMC changes:
- Currently 13 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Jeff Dunham on Sat May 21 2016
## Committer base changes:
- Currently 20 committers.
- Quentin Pradet was added as a committer on Thu Sep 21 2017
## Releases:
- 2.2.1 was released on September 21, 2017
- 2.2.0 was released on September 04, 2017
## Response to the board feedback from previous reports:
cm: Plans to take those new contributors in Oct and to turn them
into PMC or committers?
Yes, we invited Quentin Pradet to join us as a committer and they
accepted. We are also looking for potential other candidates for
committer / PMC members.
-----------------------------------------
Attachment AN: Report from the Apache Logging Services Project [Matt Sicker]
## Description:
Apache Logging Services creates and maintains open source software
related to application logging.
## Issues:
- There are no issues requiring board attention at this time
## Activity:
- Log4j: during this quarter, some of our main work has revolved
around Java 9 support, improved support for generating and parsing
safer formats such as JSON in order to discourage native Java
serialization and the vulnerabilities associated with that, removal
of default configurations that would use the old Java serialization
layout, better defaults for XML parsing to avoid potential security
issues with configuration files, a new HTTP appender, and automatic
JMS reconnection support for JMS clients that don't support that
natively.
- Log4net: no new releases this quarter, but the Jenkins pipeline
builds have been stabilized. Some bug fixes and enhancements to
the AdoNetAppender.
- Log4j Scala: no new releases this quarter. Some talk about testing
for Scala 2.13 beta releases. The website was partially integrated
back into the Log4j site.
- Log4cxx: no new releases this quarter. Some bugfixes committed.
- Log4php: no new releases this quarter. No new commits.
- Chainsaw: no new releases this quarter. Discussion has started
regarding revitalizing the project for a 3.0 version with the
general idea being to migrate to JavaFX for its GUI instead of
Swing, and to write it in either Scala 2.12 or Java 8. Work was
done to prepare the project for a release, and discussion is taking
place to start a release candidate process for it. Talk about how
to package appropriate binaries for various operating systems was
also considered. There is general interest in overhauling the
project after a new release of the existing 2.x codebase.
- Log4j Audit: some initial work has been done towards creating
an audit logging framework and catalog.
## Health report:
Logging Services remains an active project. The overall community
is healthy and friendly. We recently voted to rotate the PMC Chair
to Matt Sicker which was approved by the Board on 18 October 2017.
## PMC changes:
- Currently 13 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Mikael Ståldal on Mon Jun 20 2016
- Ralph Goers resigned from PMC Chair on Oct 18 2017
- Matt Sicker was added as PMC Chair on Oct 18 2017
## Committer base changes:
- Currently 32 committers.
- No new committers added in the last 3 months
- Last committer addition was Thorsten Schöning at Mon Mar 06 2017
## Releases:
- LOG4J-2.9.0 was released on Sat Aug 26 2017
- LOG4J-2.9.1 was released on Wed Sep 20 2017
## Mailing list activity:
We recently added a notifications@ mailing list to redirect a lot
of duplicate messages that are generated by tools such as GitHub,
JIRA, and other integrations. This will decrease the absolute traffic
numbers in the dev@ list and has already had an effect by decreasing
the traffic to dev@ by almost 300 emails.
The dev@ mailing list had less traffic than last quarter. The
log4j-user@ list had more activity than last quarter. The other
user lists had about the same amount of traffic as last quarter.
-----------------------------------------
Attachment AO: Report from the Apache Lucene.Net Project [Prescott Nasser]
-----------------------------------------
Attachment AP: Report from the Apache ManifoldCF Project [Karl Wright]
Project description
==============
ManifoldCF is an effort to provide an open source framework for connecting
source content repositories like Microsoft Sharepoint and EMC Documentum, to
target repositories or indexes, such as Apache Solr, OpenSearchServer or
ElasticSearch. ManifoldCF also defines a security model for target
repositories that permits them to enforce source repository security policies.
Releases
========
ManifoldCF graduated from the Apache Incubator on May 16, 2012. Since then,
there have been numerous major releases, including a 2.8.1 release on
September 7, 2017. The next major release is scheduled for December 31, 2017.
Committers and PMC membership
=============================
We signed up three committers in this period; the most recent one was Julien
Massiera on September 30, 2017. We have not made much progress, however, on
signing up new PMC members; the last PMC member remains Rafa Haro, voted in on
August 31, 2015. In response to the Board's inquiry in February, we've been
looking for PMC members and there have been some discussions, but so far we do
not see PMC-level committment for any of our current committers. Generally we
like to see long-term interest in the project before we offer PMC memberships.
There have also been discussions around planning for transfer of the PMC Chair
position to another person in some reasonable timeframe. We've discussed
responsibilities and requirements for the PMC Chair position and looked for a
volunteer. Currently we've had no takers, so Karl Wright will continue to be
the Chair for the foreseeable future.
Mailing list activity
=====================
Mailing list activity has been fairly high this quarter. Development has been
taking place due to many downstream critical release updates. Issues reported
have been largely about refinements to some of our connectors that have less
robust user communities and constituencies. I am unaware of any mailing list
question that has gone unanswered.
Outstanding issues
==================
No outstanding infrastructure issues are known at this time.
Branding
========
We continue to believe we are now compliant with Apache branding guidelines,
with the possible exception of (TM) signs in logos from other Apache products
that don't have any such marks. We received word that the ManifoldCF
trademark application (US TM App No. 86583085 for "MANIFOLDCF" in Cl. 9 | DLA
Ref: 393457-900118) has been accepted.
-----------------------------------------
Attachment AQ: Report from the Apache Marmotta Project [Jakob Frank]
# Marmotta Board Report for November, 2017;
## Description: Apache Marmotta, an Open Platform for Linked Data. Apache
Marmotta was founded in December 2012, and has graduated from the Incubator in November 2013.
## Issues: There are no major issues requiring board attention at this time.
## Activity: Two very quiet months since the last report.
After GSoC finished, the mailing-lists went silent. A single bugfix was
committed, but no other acitvities happened. We're still struggling to ensure
the midterm viability of the project.
## Health report: The project was considered feature-complete in 3.3.0. The
current release cycle (3.4.0) focuses on refining and fixing bug, plus incorporation
some non-core new features. The development activities
(issues, commits, emails) have significantly come down in the last year.
## PMC changes:
- Currently 11 PMC members.
- Last PMC addition was Mark A. Matienzo on Thu Aug 18 2016
## Committer base changes:
- Currently 13 committers.
- Xavier Sumba was added as a committer on Mon Mar 27 2017
## Releases:
- Last release was 3.3.0 on Fri Dec 05 2014
## Mailing list activity:
- users@marmotta.apache.org:
- 115 subscribers (down 1 since last report):
- 0 emails sent to list (4 in previous report)
- dev@marmotta.apache.org:
- 102 subscribers (up 1 since last report):
- 15 emails sent to list (183 in previous report)
## JIRA activity:
- 1 JIRA tickets created in the last 3 months
- 0 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AR: Report from the Apache Mesos Project [Benjamin Hindman]
Description:
Apache Mesos abstracts CPU, memory, storage, and other compute
resources away from machines (physical or virtual), enabling
fault-tolerant and elastic distributed systems to easily be built and
run effectively.
Issues:
There are no Board-level issues at this time.
Activity:
* The community completed two successful events since our last board
report, MesosCon North America in Los Angeles and MesosCon Europe in
Prague. Both conferences were co-located with Linux Foundation's
Open Source Summit. We added two new parts to the conference that
were a huge hit, town where community members got together to talk
about various projects in the Mesos ecosystem (including Mesos) and
MesosCon University where we ran longer, tutorial/workshop based
presentations.
* The community held a "docathon" in September that brought in
numerous community members and really helped improve the
documentation.
* The community started a performance working group where numerous
community members and organizations are joining to improve the
performance in Mesos.
* Members of the community are driving a new container storage
standard called Container Storage Interface (CSI) and are working
with other open source communities such as Cloud Foundry, Docker,
and Kubernetes.
* The project continues to see new bug reports, bug fixes, features,
reviews and releases. The mailing lists, slack and IRC channels are
also very much active with healthy discussions.
New committers:
Alexander Rojas was voted in as a committer and PMC member on 2017-07-02.
James Peach was voted in as a committer and PMC member on 2017-07-15.
Benjamin Bannier was voted in as a committer and PMC member on 2017-09-12.
Releases (since last board report):
1.4.0 Sep 17 2017
1.1.3 Aug 30th 2017
1.3.1 Aug 14th 2017
1.2.2 Aug 10th 2017
1.4.1 (In progress)
1.3.2 (In progress)
1.2.3 (In progress)
JIRA Activity (last 3 months):
336 Issues - Created
244 Issues - Resolved
-----------------------------------------
Attachment AS: Report from the Apache MetaModel Project [Kasper Sørensen]
Report from the Apache MetaModel project [Kasper Sørensen]
## Description:
Providing a common interface for discovery, exploration of metadata and
querying of different types of data sources.
## Issues:
- there are no issues requiring board attention at this time
## Activity:
- We've just released MetaModel 5.0.0 which has been brewing for a long time.
Whether the release is a big a success is too early to say anything about,
but it's good to finally have it out!
- The new "Membrane" subproject will get it's initial release soon too. We
hope that this subproject will act as a showcase for what MetaModel's
capabilities can be used to archieve. Membrane will be distributed as a
Docker image too, making it very easy to install and try out.
- An initial check was made to see how MetaModel works on JDK 9. Due to
limitations in some of the supported datastores (old version of
ElasticSearch, Neo4j) we still cannot do the complete build on JDK 9.
This is something I think we'll have to address soon.
## Health report:
- We're not seeing explosive growth or anything like that, but it seems to be
a good time with decent amounts of activity from both recurring and new
contributors.
- Good signals in terms of new contributions coming organically and less
company-sponsored.
## PMC changes:
- Currently 11 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Dennis Du Krøger on Mon Sep 05 2016
## Committer base changes:
- Currently 11 committers.
- No new committers added in the last 3 months
- Last committer addition was Dennis Du Krøger at Thu Oct 15 2015
## Releases:
- 5.0-RC4 was released on Fri Aug 18 2017
- 5.0.0 was released on Wed Nov 8 2017
## JIRA activity:
- 17 JIRA tickets created in the last 3 months
- 12 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AT: Report from the Apache Oltu Project [Antonio Sanso]
-----------------------------------------
Attachment AU: Report from the Apache Oozie Project [Robert Kanter]
## Description:
- Oozie is a workflow scheduler system to manage Apache Hadoop jobs.
## Issues:
- There are no issues requiring board attention at this time.
- The board had asked about our Committer vs PMC gap in
the previous report. Some of the Committers are no longer
active. Otherwise, we generally wait about 1 year after
Committership to promote to PMC. A couple Committers
are reaching that point in the next month or so, and a few
more will be there early next year.
## Activity:
- We're now planning a 5.0.0 beta release sometime before
the end of the year, with Oozie on Yarn as the flagship feature.
- Someone was asking about us giving them the "Oozie"
twitter handle. We've decided to keep it to protect the brand.
We'll look into actively using it again.
- Other misc bug/usability fixes and improvements are still
ongoing.
## PMC changes:
- Currently 16 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Ryota Egashira on Mon Aug 10 2015
## Committer base changes:
- Currently 24 committers.
- Andras Piros was added as a committer on Mon Oct 16 2017
## Releases:
- Last release was 4.3.0 on Thu Dec 01 2016
## JIRA activity:
- 81 JIRA tickets created in the last 3 months
- 65 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AV: Report from the Apache Open Climate Workbench Project [Michael James Joyce]
## Description:
Apache Open Climate Workbench is an effort to develop software that performs
climate model evaluation using model outputs from a variety of different
sources the Earth System Grid Federation, the Coordinated Regional Climate
Downscaling Experiment, the U.S. National Climate Assessment and the North
American Regional Climate Change Assessment Program and temporal/spatial
scales with remote sensing data from NASA, NOAA and other agencies. The toolkit
includes capabilities for rebinning, metrics computation and visualization.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
Activity has been pretty quiet but stable indicating the the community
is still alive and kicking. We are working towards our 1.2.0 release.
Scientists and Researchers from NASA JPL are working to publish an
academic paper on updates in OCW.
## Health report:
OCW has not attracted many new community members however a handful
of existing community members are ensuring that the project is moving
forward.
## PMC changes:
- Currently 30 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Ibrahim Jarif on Mon Apr 25 2016
## Committer base changes:
- Currently 30 committers.
- No new committers added in the last 3 months
- Last committer addition was Christopher Douglas at Tue Apr 26 2016
## Releases:
- Last release was climate-1.1.0 on Wed Jul 27 2016
## Mailing list activity:
Mailing list subscribers are up which is excellent. JIRA
tickets are being opened and addressed which is also positive
for the project.
- dev@climate.apache.org:
- 59 subscribers (up 5 in the last 3 months):
- 88 emails sent to list (70 in previous quarter)
## JIRA activity:
- 11 JIRA tickets created in the last 3 months
- 9 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AW: Report from the Apache OpenJPA Project [Mark Struberg]
## Description:
Apache OpenJPA is a persistent object management kernel for databases,
relational as well as non-relational. For relational databases, OpenJPA is
compliant to the Java Persistence Architecture (JPA) version 2.0.
OpenJPA runs in stand-alone Java SE as well as containers e.g Java EE,
Tomcat, Spring or OSGi.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
Low activity. Maintenance is going on steadily but at a low level.
## Health report:
We should finally ship OpenJPA-3.0.0. Currently we lack on people
who push this forward. Or rather those people are busy with other stuff.
## PMC changes:
- Currently 16 PMC members.
- Jody Grassel was added to the PMC on Tue Aug 15 2017
## Committer base changes:
- Currently 33 committers.
- Will Dazey was added as a committer on Thu Aug 17 2017
## Releases:
- Last release was 2.4.2 on Tue Jan 03 2017
## Mailing list activity:
- users@openjpa.apache.org:
- 239 subscribers (down -3 in the last 3 months):
- 28 emails sent to list (17 in previous quarter)
- dev@openjpa.apache.org:
- 137 subscribers (up 0 in the last 3 months):
- 58 emails sent to list (100 in previous quarter)
## JIRA activity:
- 8 JIRA tickets created in the last 3 months
- 1 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AX: Report from the Apache Perl Project [Philippe Chiasson]
-----------------------------------------
Attachment AY: Report from the Apache Phoenix Project [James R. Taylor]
## Description:
- Apache Phoenix enables SQL-based OLTP and operational analytics
for Apache Hadoop
## Issues:
- There are no issues requiring board attention at this time
## Activity:
- Released 4.12.0 and 4.13.0 in the last three months
- Ongoing work to support HBase 2.0 with good collaboration between
HBase and Phoenix communities
- Dropping support for HBase 1.1 and HBase 1.2 after discussion due
to lack of interest/need (no one volunteered to be RM).
- Continuing HBase 0.98 support for another couple releases, but
moving toward maintenance-only mode.
## Health report:
- The project is healthy and continues to grow as users look for easy
ways to gain insight over and manage their ever-increasing Hadoop
data through standard SQL and JDBC APIs.
## PMC changes:
- Currently 25 PMC members.
- Sergey Soldatov was added to the PMC on Mon Oct 02 2017
## Committer base changes:
- Currently 33 committers.
- New commmitters:
- Ethan Wang was added as a committer on Tue Oct 10 2017
- Vincent Poon was added as a committer on Thu Oct 12 2017
## Releases:
- 4.12.0 was released on Tue Oct 10 2017
- 4.13.0 was released on Thu Nov 09 2017
## Mailing list activity:
- Mailing list subscriptions remain relatively constant
- dev@phoenix.apache.org:
- 223 subscribers (down -3 in the last 3 months):
- 3350 emails sent to list (2950 in previous quarter)
- user@phoenix.apache.org:
- 553 subscribers (up 7 in the last 3 months):
- 245 emails sent to list (271 in previous quarter)
## JIRA activity:
- More JIRAs filed than closed due mostly to lack of grooming
of backlog.
- 281 JIRA tickets created in the last 3 months
- 185 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AZ: Report from the Apache POI Project [Dominik Stadler]
Report from the Apache POI committee [Dominik Stadler]
## Description:
- Apache POI is a Java library for reading and writing Microsoft Office file
formats
## Issues:
- There are no issues requiring board attention at this time
## Activity:
- There is constant activity in commits, bugfixes, feature-work and also
user questions.
We release 3.17 and started work on a major release 4.0 in order to perform
some larger work on the codebase. Among those is to desupport Java 6 and 7
as well as removal of some deprecated API parts.
Work happened to cleanup the code-base after the switch to 4.0, a number of
bugfixes and some function enhancements/additions.
We started discussion about a non-maintainer-update of XMLBeans (which is in
the Attic) to fix some bugs that affect Apache POI users.
## Health report:
- We again saw a constant stream of new bug reports/feature
requests which indicates that the popularity of Apache POI is still very
good. Questions via email or on Stackoverflow usually get answers quickly,
regularly even from people not actively involved in Apache POI development.
We just started the process of adding a new Committer and PMC
member.
## PMC changes:
- Currently 29 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was PJ Fanning on Fri Jun 23 2017
## Committer base changes:
- Currently 36 committers.
- No new committers added in the last 3 months
- Last committer addition was PJ Fanning at Fri Jun 23 2017
## Releases:
- 3.17 was released on Wed Sep 13 2017
## Mailing list activity:
- Mostly constant membership numbers, a few un-subscribers for this
period, not apparent reason for that. POI is a mature project with
a stable user/developer-base.
- dev@poi.apache.org:
- 239 subscribers (down -2 in the last 3 months):
- 810 emails sent to list (834 in previous quarter)
- general@poi.apache.org:
- 134 subscribers (up 3 in the last 3 months):
- 0 emails sent to list (6 in previous quarter)
- user@poi.apache.org:
- 615 subscribers (down -7 in the last 3 months):
- 89 emails sent to list (108 in previous quarter)
## Bugzilla Statistics:
- 61 Bugzilla tickets created in the last 3 months
- 71 Bugzilla tickets resolved in the last 3 months
- 492 bugs are open overall (-3)
- Having 134 enhancements, thus having 358 actual bugs (+-0)
- 98 of these are waiting for feedback (-3)
- Thus having 260 actual workable bugs (+1)
- 5 of the workable bugs have patches available (-1)
- Distribution of workable bugs across components: {HSSF=72, XSSF=64, HWPF=36,
SS Common=30, XWPF=18, XSLF=9, SXSSF=8, POI Overall=7, HPSF=4, HSLF=3,
POIFS=3, OPC=2, HMEF=1, HPBF=1, HSMF=1, SL Common=1}
-----------------------------------------
Attachment BA: 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:
- PredictionIO graduated from the Apache Incubator on 10/18/2017.
- Press release were made on 10/24/2017.
- Planning a patch release as the first release since graduating to TLP.
## Health report:
- Project is in good health. Regular user and dev mailing list traffic.
- We are planning a video call for a major rearchitecting effort.
## PMC changes:
- Currently 28 PMC members.
- No new PMC members added in the last 3 months
## Committer base changes:
- Currently 29 committers.
- No changes (the PMC was established in the last 3 months)
## Releases:
- Current release is 0.12.0-incubating, which was released on 9/26/2017.
- No new release since graduation.
## JIRA activity:
- 25 JIRA tickets created in the last 3 months
- 25 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment BB: Report from the Apache Qpid Project [Robert Gemmell]
Apache Qpid is a project focused on creating software based on the
Advanced Message Queuing Protocol (AMQP), currently providing a
protocol engine library, message brokers written in C++ and Java, a
message router, and client libraries for C++, Java / JMS, .Net,
Python, Perl and Ruby.
# Releases:
- Qpid Proton-J 0.21.0 was released on 4th September 2017.
- Qpid Proton-J 0.22.0 was released on 15th September 2017.
- Qpid JMS 0.25.0 was released on 21st September 2017.
- Qpid JMS 0.26.0 was released on 6th October 2017.
- Qpid Proton-J 0.23.0 was released on 15th October 2017.
- Qpid Proton 0.18.0 was released on 22nd October 2017.
- Qpid Proton 0.18.1 was released on 3rd November 2017.
- Qpid JMS 0.27.0 was released on 5th November 2017.
# Community:
- The main user and developer mailing lists continue to be active and JIRAs
are being raised and addressed, in line with prior activity levels.
- Adel Boutros was added as a committer on 9th August 2017.
- There were no new PMC additions in this quarter.
The most recent new PMC member is Ganesh Murthy, added on 30th Jan 2017.
# Development:
- Work progresses towards a 1.0.0 release of Dispatch router, with various
new features and an overhaul of its IO handling based on new functionality
from Proton-C in 0.18.0. A 1.0.x branch has been created and a couple of
testing candidates created, with progress being made on resolving some
final issues ahead of calling a 1.0.0 release vote.
- A 7.0.0 Qpid Broker-J release is imminent, with voting open on a second
candidate for release. The AMQP 0-x JMS client will soon proceed to a
6.3.0 release vote to complete making it independent going forward. Some
broker fixes are going to be backported to the existing 6.x line for a
further bug fix release.
- Proton-C and its language bindings had their 0.18.0 release, incorporating
some extensive work on new IO handling, as well as a 0.18.1 bug fix to
clear up some niggles. Work on 0.19.0 is under way, aiming to build on
some of this work and making improvements to the Ruby binding. Work
continues on Proton-J to incorporate fixes and changes needed to enable
bug fix and feature additions in dependent client/broker/other components.
- The AMQP 1.0 JMS client had its 0.25.0-0.27.0 releases, incorporating
various bug fixes and improvements, and facilitating building and using
on JDK9. Work on additional fixes and improvements continues.
# Issues:
There are no Board-level issues at this time.
-----------------------------------------
Attachment BC: Report from the Apache Ranger Project [Selvamohan Neethiraj]
# Description:
The Ranger project is a framework to enable, monitor and manage comprehensive
data security across the Hadoop platform.
# Issues:
* There are no issues requiring board attention at this time.
# Activity:
* Community is working to improve security features of hive/hdfs/usersync
modules and adding more integration with Apache Atlas
* Jira: +192(added) -133(resolved) over last 3 months
* Git (Source): 148 commits over last 3 months
# Health report:
* Fixed few CVE issues - raised by community and user groups
* Actively working to add more functionalities to Apache Ranger
* Still working on next release with more integration with Apache Atlas
## PMC changes:
- Currently 17 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Alok Lal on Tue Jan 17 2017
## Committer base changes:
- Currently 25 committers.
- New commmitters:
- Deepak Sharma was added as a committer on Wed Sep 20 2017
- Jianhua Peng was added as a committer on Tue Sep 26 2017
## Releases:
- Last release was Apache Ranger 0.7.1 on Tue Jun 06 2017
## Mailing list activity:
- dev@ranger.apache.org:
- 97 subscribers (up 1 in the last 3 months):
- 1740 emails sent to list (1554 in previous quarter)
- user@ranger.apache.org:
- 164 subscribers (up 9 in the last 3 months):
- 66 emails sent to list (72 in previous quarter)
-----------------------------------------
Attachment BD: Report from the Apache REEF Project [Byung-Gon Chun]
## Description:
- Apache REEF (Retainable Evaluator Execution Framework) is a library for
developing portable applications for cluster resource managers such as
Apache Hadoop YARN or Apache Mesos.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- Continued great progress towards running REEF.Net on CoreCLR/Linux.
- Progress towards building new elastic group communication in .NET.
- Improving REEF testing.
## Health report:
Overall, the community is healthy: the community has been achieving
important milestones and there is a constant flow of bug reports, fixes,
and discussions.
## PMC changes:
- Currently 22 PMC members.
- Doug Service was added to the PMC on Fri Sep 29 2017
## Committer base changes:
- Currently 34 committers.
- No new committers added in the last 3 months
- Last committer addition was Doug Service at Tue Apr 11 2017
## Releases:
- 0.16 was released on Thu Aug 10 2017
## Mailing list activity:
- dev@reef.apache.org:
- 83 subscribers (up 0 in the last 3 months):
- 636 emails sent to list (675 in previous quarter)
- user@reef.apache.org:
- 15 subscribers (up 1 in the last 3 months):
- 0 emails sent to list (2 in previous quarter)
## JIRA activity:
- 94 JIRA tickets created in the last 3 months
- 72 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment BE: Report from the Apache River Project [Peter Firmstone]
-----------------------------------------
Attachment BF: Report from the Apache RocketMQ Project [Xiaorui Wang]
## Description:
- Apache RocketMQ is a distributed messaging and streaming platform with low latency,
high performance and reliability, trillion-level capacity and flexible scalability.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- All the graduation common tasks have been finished.
- aqlu contributed a spring boot starter for RocketMQ, the related pull request is still in work.
- Clear up and schedule version 4.2.0 related JIRA issues for a TLP release, these are mostly done.
## Health report:
Within the past three months:
- 43 JIRA issues were opened, 18 closed and 7 in progress
- 57 GitHub pull requests were opened and 32 were closed
- 35 commits were made by 5 authors, 3 authors were not committers
## PMC changes:
- Currently 10 PMC members.
- The last time a new PMC member was elected for the project was on July 13, 2017. dongeforever was added a PMC member.
## Committer base changes:
- Currently 15 committers.
- The last time a committer was added to the project was on July 19, 2017. linjunjie was added a committer.
## Releases:
- The last release of RocketMQ was version 4.1.0-incubating, released on June
8, 2017.
- The first TLP release Apache RocketMQ 4.2.0 is postponed until November 2017.
## Mailing list activity:
- users@rocketmq.apache.org:
- 91 subscribers (up 9 in the last 3 months):
- 34 emails sent to list (49 in previous quarter)
- dev@rocketmq.apache.org:
- 83 subscribers (up 7 in the last 3 months):
- 612 emails sent to list (818 in previous quarter)
- issues@rocketmq.apache.org:
- 39 subscribers (up 3 in the last 3 months):
- 535 emails sent to list (939 in previous quarter)
## JIRA activity:
- 50 JIRA tickets created in the last 3 months
- 25 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment BG: Report from the Apache Roller Project [David M. Johnson]
## Description:
Apache Roller is a full-featured, Java-based blog server that works well on
Tomcat and MySQL, and is known to run on other Java servers and relational
databases. The ASF blog site at blogs.apache.org runs on Roller 5.1.2 Tomcat
and MySQL.
## Issues:
- There are no issues requiring board attention at this time
## Activity:
- A new Roller 5.2.0 release was made on Sunday Nov 5, 2017, which
included small improvements, bug fixes and dependency upgrades.
- The core Roller community is small and with low activity levels.
- There is ongoing work to create a modernized UI using Bootstrap with Struts.
## Health report:
- Community is made-up of part-time volunteers with very limited time to
devote to Roller.
## PMC changes:
- Currently 5 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Kohei Nozaki on Sun Dec 06 2015
## Committer base changes:
- Currently 8 committers.
- No new committers added in the last 3 months
- Last committer addition was Kohei Nozaki at Mon Mar 09 2015
## Releases:
- 5.2.0 was released on Sun Nov 05 2017
## Mailing list activity:
Subscriber counts could be taken to mean there is still some interest in
Apache Roller. The low email counts reflec the low level of development
and user-support activity.
- dev@roller.apache.org:
- 158 subscribers (up 0 in the last 3 months):
- 31 emails sent to list (4 in previous quarter)
- user@roller.apache.org:
- 281 subscribers (up 0 in the last 3 months):
- 5 emails sent to list (1 in previous quarter)
## JIRA activity:
- 2 JIRA tickets created in the last 3 months
- 1 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment BH: 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.
Apache Royale was approved as a new TLP in the September meeting. Royale took
over responsibility for the code related to what was known as Apache FlexJS
from the Apache Flex community. This is our second report.
## ISSUES
There are no issues requiring board attention at this time.
## RELEASES
- Apache FlexJS 0.8.0 was released on 6/25/17.
## ACTIVITY
- The effort to set up new builds and rename code assets from FlexJS to Royale
was/is significant and that effort is still in progress, but nearing
completion.
- Some new names have appeared on the mailing lists investigating whether
Royale is a suitable solution for migrating existing Flex applications off of
Flash.
- One PMC member has proposed an initial web site for Royale. There were some
logistical issues in being allowed to use it as he created it on WordPress
with a commercial theme. Those issues are mostly resolved at this time.
- Some work is being done on a new default look-and-feel for Royale.
- There has been some progress and discussion on improving the testing
architecture to make it easier to improve the automated test coverage.
## COMMUNITY
The community is still working through the transition from Apache Flex to
Apache Royale. There is much documentation remaining to be transitioned from
the Apache Flex wiki to some place in Apache Royale.
Currently, users@royale has 38 subscribers (up from 29) and dev@royale has 47
(up from 42) subscribers. We are not sure why more folks from the Flex
mailing lists haven't subscribed to Royale, but it's likely that once we get
our website and documentation moved over we will ask again on the Flex lists
to see if folks want to come over.
We have not added any new committers or PMC members yet.
## TRADEMARKS
Several PMC members wanted to allow another PMC member to use royalesdk.io
and/or royalesdk.org to externally host some content to promote Apache Royale.
Trademarks denied use of that domain name. We might revisit the topic if and
when there is a concrete reason to do so.
-----------------------------------------
Attachment BI: Report from the Apache Santuario Project [Colm O hEigeartaigh]
## Description:
- Library implementing XML Digital Signature Specification & XML Encryption
Specification
## Issues:
- There are no issues requiring board attention at this time
## Activity:
- There were two new releases over the last quarter of the Apache Santuario
XML Security for Java project. 2.0.9 was a minor bug fix release, albeit
with an important bug fix when deploying the library in the Google App
Engine. 2.1.0 was a new major release with support for JDK 9.
A new release of the C++ library is expected in the next quarter.
## Health report:
- Apache Santuario is a mature and stable project that has reached a point
where not too many fixes are required, as it is a set of implementations
of some specifications that are quite old now. It is actively managed by
the PMC. Right now there are no obvious potential new committers for the
project.
## PMC changes:
- Currently 6 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Marc Giger on Wed Apr 03 2013
## Committer base changes:
- Currently 16 committers.
- No new changes to the committer base since last report.
- Last committer addition was Marc Giger in July 2012
## Releases:
- Apache Santuario XML Security for Java 2.0.9 was released on Mon Aug 28
2017
- Apache Santuario XML Security for Java 2.1.0 was released on Mon Aug 28
2017
## JIRA activity:
- 14 JIRA tickets created in the last 3 months
- 18 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment BJ: Report from the Apache Serf Project [Bert Huijben]
## Description:
The serf library is a high performance C-based HTTP client library
built upon the Apache Portable Runtime (APR) library. Serf is the
default client library of Apache Subversion, Apache OpenOffice and
mod_pagespeed.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
There hasn't been much activity over the last few months, but minor
tweaks are applied quite often to keep up to date with changes in
other relevant projects such as OpenSSL. I expect that we will
release a new 1.3 release soon.
## Health report:
Activity is at a normal, fairly quiet level.
The serf project's activity is quite related to that of Subversion
and with that projects recent affairs we slowed more than expected.
## PMC & Committer changes:
Currently 12 PMC members and 13 committers. We added Evgeny Kotkov
as Committer and PMC member this April.
## Releases:
Apache Serf 1.3.9 was released on Thu Sep 01 2016
## Mailing list and Jira activity:
Normal slow activity.
-----------------------------------------
Attachment BK: Report from the Apache SIS Project [Martin Desruisseaux]
## Description:
Apache Spatial Information System (SIS) is a Java library for developing
geospatial applications. SIS enables better representation of spatial objects
for searching, archiving, or other relevant spatial needs. The base of the SIS
library is modelled according international standards published jointly by the
Open Geospatial Consortium (OGC) and the International Organization for
Standardization (ISO).
## Issues:
There are no issues requiring board attention at this time.
## Activity:
The two Google Summer of Code (GSoC) projects have been completed, but their
integration into SIS will require a significant amount of work. For example
the Android port had a rewrite of some classes for using the Google SQLite API
instead than JDBC. The amount of code changes will make difficult to merge
future work from SIS trunk to Android branch. A more convenient approach would
have been to create JDBC wrapper for SQLite (only for the parts that we use).
The student was aware of this issue, but didn’t had time to change his
approach before the end of the project. A cause of this issue may have been
the mentor (myself) not putting enough insistence for a change.
Following the Apache SIS presentations in two Free and Open Source Software
for Geospatial (FOSS4G) conferences, we wrote two blogs comparing Apache SIS
and Proj.4 (the dominant open source map projections library) [1] [2]. Our
main conclusion is that Proj.4 supports more map projections and is generally
faster (because of faster trigonometric functions in C/C++ compared to Java
8), but Apache SIS provides better compliance with international standards
together with more information (accuracy, domain of validity) for evaluating
coordinate operations reliability.
Related to above paragraph, we proposed to the Open Geospatial Consortium
(OGC) a process for evaluating the reliability of geospatial referencing
softwares [3]. If this process is accepted and if OGC find sponsors for it,
Apache SIS would be in good position for participating and I think it would
perform well.
OGC has deployed GeoAPI 3.0.1 on Maven Central, which allow us to release
Apache SIS 0.8. A release candidate is being prepared and will be submitted to
vote this week. Status of work submitted by external contributors:
* Update of netCDF discovery metadata [4] has been integrated in SIS.
* Update of XML metadata: we delayed their integration to after SIS 0.8
release in order to avoid the risk of major changes to close to a release.
## Health report:
The project is reported mostly okay according the Apache Committee Report
Helper. However mailing list activity went down to the usual level when there
is no GSoC projects.
## PMC changes:
* Currently 20 PMC members.
* Johann Sorel was added to the PMC on Thu Sep 07 2017
## Committer base changes:
* Currently 21 committers.
* No new committers added in the last 3 months.
* Last committer addition was Johann Sorel at Thu Mar 31 2016.
## Releases:
* Last release was 0.7 on May 27 2016.
* 0.8 release candidate is in preparation.
## Mailing list activity:
* dev@sis.apache.org:
- 66 subscribers (up 1 in the last 3 months):
- 36 emails sent to list (142 in previous quarter)
## JIRA activity:
* 7 JIRA tickets created in the last 3 months.
* 9 JIRA tickets closed/resolved in the last 3 months.
[1] https://www.geomatys.com/wordpress/index.php/2017/08/28/english-proj-4-versus-apache-sis-a-performance-comparison/?lang=en
[2] https://www.geomatys.com/wordpress/index.php/2017/09/20/proj-4-versus-apache-sis-an-accuracy-comparison/?lang=en
[3] https://github.com/opengeospatial/testbed14-ideas/issues/37
[4] https://issues.apache.org/jira/browse/SIS-171
-----------------------------------------
Attachment BL: Report from the Apache Spark Project [Matei Alexandru Zaharia]
Apache Spark is a fast and general engine for large-scale data processing. It
offers high-level APIs in Java, Scala, Python and R as well as a rich set of
libraries including stream processing, machine learning, and graph analytics.
Project status:
- We released Spark 2.1.2 on October 9th, with maintenance fixes for the
2.1 branch. This release was also managed by a new committer, which
helped expose issues in the release process documentation that we've
fixed. We are encouraging more new committers to be RMs for upcoming
releases like 2.2.1.
- The Spark Summit Europe conference ran in Dublin, Ireland in October
with 1200 attendees.
- Work is under way to merge Kubernetes support for Spark 2.3.0, with
the first major pull requisition having undergone a bunch of review
and getting close to merging. We need one more pull request beyond
this for basic support.
SPIPs:
We wanted to give an update on Spark Project Improvement Proposals
(SPIPs), the process we started to formally propose large changes
before having an implementation. Since we started the process, there
have been seven SPIPs proposed on the mailing list with the first in
June 2017, which are all listed in JIRA at https://s.apache.org/aMHI.
So far all the voted-on SPIPs have been accepted and it seems that
the discussions, both on our dev list and in JIRA, have been useful,
resulting in design changes, better understanding of each idea, and
feedback from a wide range of Spark users. Some of the major SPIPs
discussed and accepted include Kubernetes support, images as a
first-class data type in MLlib, updates to the data source API, and low
latency continuous processing. We will continue to encourage people to
write large proposals as SPIPs to generate this type of discussion.
Trademarks:
- No large issues to report in the past 3 months.
Latest releases:
- October 9, 2017: Spark 2.1.2
- July 11, 2017: Spark 2.2.0
- May 02, 2017: Spark 2.1.1
- Dec 28, 2016: Spark 2.1.0
Committers and PMC:
- The latest committer was added on September 22nd, 2017
(Tejas Patil).
- The latest PMC members were added on June 16th, 2017
(six new PMC members from the existing committers).
-----------------------------------------
Attachment BM: Report from the Apache Stanbol Project [Fabian Christ]
-----------------------------------------
Attachment BN: Report from the Apache Subversion Project [Stefan Sperling]
Apache Subversion exists to be universally recognized and adopted as
an open-source, centralized version control system characterized by
its reliability as a safe haven for valuable data; the simplicity of
its model and usage; and its ability to support the needs of a wide
variety of users and projects, from individuals to large-scale
enterprise operations.
* Board Issues
There are no Board-level issues of concern.
* Community
The community is healthy and active. New features are being designed
and developed, and bug reports are being handled. Our user support
forums (Email and IRC) receive questions and answers regularly.
The project is holding a hackathon in Aachen, Germany, for a duration
of 5 days in November (21st - 26th). At least 5 developers will be
attending this event. The community has reached out to the general
public with an invitation to a "meet and greet" event which will
occur on the 23rd of November. Funding for this hackathon was first
sought from the Foundation, but ended up being covered by the company
Assembla.
Two committer additions happened in October 2017:
Pavel Lyalyakin who has been contributing to the project's website.
Troy Curtis Jr who has been contributing to SVN's Python 3 bindings.
In October, the PMC chair hat was passed from Evgeny Kotkov to
Stefan Sperling. There was no pressing need for this switch.
The switch was discussed beforehand and agreed upon by the entire PMC.
Our main motivation was our belief that occasionally passing such
responsibilities around benefits our community in the long term.
Evgeny Kotkov served as PMC chair for one year, and we expect our
new chair to serve for at least the same amount of time.
* Releases
There were no new releases published since August 10 2017.
The current supported releases are still 1.9.7 and 1.8.19.
Several bug fixes for our stable release series have since been proposed,
implying that new stable releases can be expected in the near future.
None of the proposed bug fixes have security implications.
We continue moving towards the first GA release of Subversion 1.10.
-----------------------------------------
Attachment BO: Report from the Apache Syncope Project [Francesco Chicchiriccò]
## Description: Apache Syncope is an Open Source system for managing digital
identities in enterprise environments.
## Issues: There are no issues requiring board attention at this time.
## Activity: The last months were again busy with fixes, new features and
enhancements for the stable branch, which led to the release of 2.0.5 and
2.0.6. The work on the master branch (for next stable 2.1.0) has started.
## Health report: Discussions about new features and improvements keep
appearing and being followed up in dev@.
Newcomers approach user@ and are getting supported by various members of the
community.
## PMC changes:
- Currently 11 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition: Thu Oct 13 2016 (Andrea Patricelli)
## Committer base changes:
- Currently 21 committers.
- Matteo Alessandroni was added as a committer on Fri Jul 28 2017
- Last committer addition: Fri Jul 28 2017 (Matteo Alessandroni)
## Releases:
- 2.0.5 was released on Wed Sep 06 2017
- 2.0.6 was released on Mon Oct 09 2017
-----------------------------------------
Attachment BP: Report from the Apache SystemML Project [Jon Deron Eriksson]
[REPORT] Apache SystemML - November 2017
## Description:
SystemML provides declarative large-scale machine learning (ML) that aims at
flexible specification of ML algorithms and automatic generation of hybrid
runtime plans ranging from single node, in-memory computations, to distributed
computations such as Apache Hadoop MapReduce and Apache Spark.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- We graduated as an Apache top-level project on May 18, 2017.
- Our first top-level project release (0.15.0) was approved on September,
13, 2017.
- We added our first new committer since becoming a top-level project on
October 25, 2017.
- We are planning our 1.0.0 release.
## Health report:
- Code activity is healthy with 270 commits in the last 3 months.
- Community growth is healthy with 1 new contributor and 1 new committer in
the last 3 months.
- Communication is healthy on mailing list, JIRAs, and pull requests.
## PMC changes:
- Currently 23 PMC members.
- Felix Schüler was elected as PMC member on April 19, 2017.
## Committer base changes:
- Currently 24 committers.
- Krishna Kalyan was added as a committer on October 25, 2017.
## Releases:
- Version 0.15.0 was released on September 13, 2017.
-----------------------------------------
Attachment BQ: Report from the Apache TomEE Project [David Blevins]
-----------------------------------------
Attachment BR: Report from the Apache Turbine Project [Georg Kallidis]
# Description:
Apache Turbine is a servlet based framework that allows experienced Java
developers to quickly build web applications. Turbine allows you to
personalize the web sites and to use user logins to restrict access to parts
of your application.
Turbine is a matured and well established framework that is used as the base
of many other projects.
## PMC changes:
- Currently 8 PMC members.
- No new PMC members added in the last 3 months
- Jeffrey Painter has been elected as new PMC member. PMC member annoucement
in progress.
## Committer base changes:
- Currently 11 committers.
- No new changes to the committer base since last report.
- The last change to the committer base was the addition of Georg Kallidis
(2012/09/19).
## Releases:
Fulcrum component project:
- The latest released component was Fulcrum JSON 1.1.1 (August 15 2017)
Turbine core project:
- Release of the Turbine Core component 4.0 (November 8 2017).
- Turbine 4.0 Webapp Archetype in preparation.
## Issues:
- Unresolved issue INFRA-15106 with GitHub mirroring Turbine core trunk.
Either resolution may be accepted, that is following the proposed suggestion
in the last comments - or not.
## Health report:
- The Turbine project has had low levels of activity this quarter.
- Code activity was mainly in Turbine4 Core.
-----------------------------------------
Attachment BS: Report from the Apache Usergrid Project [Todd Nine]
## Description:
- Usergrid is Backend-as-a-Service (BaaS) composed of an integrated
database (Cassandra), a query engine (Elastic Search), and
application layer and client tier with SDKs for developers.
## Issues:
- There are no issues requiring board attention at this time
## Activity:
- Implementation of several indexing configuration options to allow user customization
- Bug fixes and administrative tooling improvements
## Health report:
- Usergrid is healthy and the community is stable. Growth has been slow.
## PMC changes:
- Currently 25 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Mike Dunker on Mon Jan 18 2016
## Committer base changes:
- Currently 15 committers.
- No new committers added in the last 3 months
- Last committer addition was Robert Walsh at Sun Feb 26 2017
## Releases:
- Last release was 2.1.0 on Wed Feb 17 2016
## Mailing list activity:
- dev@usergrid.apache.org:
- 108 subscribers (up 0 in the last 3 months):
- 54 emails sent to list (48 in previous quarter)
- user@usergrid.apache.org:
- 145 subscribers (up 3 in the last 3 months):
- 2 emails sent to list (3 in previous quarter)
## JIRA activity:
- 2 JIRA tickets created in the last 3 months
- 0 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment BT: Report from the Apache Velocity Project [Nathan Bubna]
## Description:
- Java-based template engine
## Issues:
- No issues requiring board attention at this time.
## Activity:
- Light activity, mostly centered around changes to the Velocity Tools project
## Health report:
- Project is fine. Light work on Tools project. Pretty quiet since the release
of Engine 2.
## PMC changes:
- Currently 9 PMC members.
- Michael Osipov was added to the PMC on Thu Jul 27 2017
## Committer base changes:
- Currently 14 committers.
- No new committers added in the last 3 months
- Last committer addition was Michael Osipov at Mon Jan 30 2017
## Releases:
- None this period.
## Mailing list activity:
- Very light traffic, mostly about bugs in Tools.
- dev@velocity.apache.org:
- 125 subscribers (up 0 in the last 3 months):
- 17 emails sent to list (71 in previous quarter)
- general@velocity.apache.org:
- 80 subscribers (down -3 in the last 3 months):
- 1 emails sent to list (3 in previous quarter)
- user@velocity.apache.org:
- 299 subscribers (down -8 in the last 3 months):
- 16 emails sent to list (2 in previous quarter)
## JIRA activity:
- 3 JIRA tickets created in the last 3 months
- 1 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment BU: Report from the Apache Web Services Project [Sagara Gunathunga]
-----------------------------------------
Attachment BV: Report from the Apache Whimsy Project [Sam Ruby]
## Description:
Tools that help automate various administrative tasks or information lookup
activities
## Issues:
None
## Health report:
We continue to have more than adequate oversight, with two to three active
committers, and two to four occasional committers.
## Development:
- All tools which previously used React.js were converted to use Vue.js just
in time for Facebook to re-license React.js. At the moment, we are
continuing with Vue.js, but this could change.
- Development has resumed on a tool to assist PMCs with inviting new
committers. Once deployed, this tool will reduce errors and reduce the
workload on the Secretary. Craig is leading up the coding of this effort.
- Whimsy-vm3 has been retired. There are no current plans to create a
whimsy-vm5 until the infrastructure team is ready to support Ubuntu 18.04
(due to be released in April).
## PMC and committer base:
- Currently 10 committers, all on the PMC.
- Last addition: Thu Jun 2017 (John D. Ament)
-----------------------------------------
Attachment BW: Report from the Apache Xalan Project [Steven J. Hathaway]
-----------------------------------------
Attachment BX: Report from the Apache Xerces Project [Michael Glavassevich]
Xerces-J
In the month since the previous report there's been no development activity,
though there was some discussion about getting help for reviewing a patch for
XInclude 1.1.
Mailing list traffic has been low; roughly 10+ posts on the j-dev and j-users
lists since the beginning of October 2017.
No new releases since the previous report. The latest release is Xerces-J
2.11.0 (November 30th, 2010).
Xerces-C
Aside from the handful of mailing list posts there's no activity to report for
the last month.
Mailing list traffic has been low; roughly 10+ posts on the c-dev and c-users
lists since the beginning of October 2017.
No new releases since the previous report. The latest release is Xerces-C
3.2.0 (August 28th, 2017).
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.
No committers have committed changes to SVN since October.
Apache Project Branding Requirements
The project logo still needs a "TM" to be added to it.
-----------------------------------------
Attachment BY: Report from the Apache XML Graphics Project [Glenn Adams]
## Description:
- The Apache XML Graphics Project is responsible for software
intended for the creation & maintenance of the conversion of XML
formats to graphical output & related software components.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- During this reporting period, activity on the three sub-projects
has remained low, with 56 issues resolved or closed during this
reporting period.
## Health:
- The level of community and developer activity remains at a
low level for a relatively mature product, albeit one
with a fair number of outstanding unresolved issues.
## PMC:
- No new PMC members added in the last 3 months
- Last PMC addition was Simon Steiner on Tue Jan 19 2016
- Currently 11 PMC members.
## Committers:
- No new committers added in the last 3 months
- Last committer added was Matthias Reischenbacher at Wed May 13 2015
- Currently 21 committers.
## Releases:
- XMLGraphics Batik 1.9.1 was released on Tue Aug 01 2017
## Mailing Lists:
- Slight increase in subscribers of 1%, up from 1083 to 1093.
- Mail lists show an increase in traffic of 32%, up from 367 to 484.
------------------------------------------------------
End of minutes for the November 15, 2017 board meeting.
Index