Index
Links: 2018 - All years
- Original The Apache Software Foundation
Board of Directors Meeting Minutes
January 17, 2018
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/3dxd
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:40
Jim Jagielski
Chris Mattmann - Joined at 10:40
Brett Porter
Phil Steitz
Mark Thomas
Directors Absent:
none
Executive Officers Present:
Ross Gardler
Kevin A. McGrail
Sam Ruby
Craig L Russell
Executive Officers Absent:
Ulrich Stärk
Guests:
Bruce Snyder
Daniel Gruno
Danny Angus
Greg Stein
Peter Kovacs
Pierre Smits
Sally Khudairi - left at 11:05; rejoined at 11:55
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 December 20, 2017
See: board_minutes_2017_12_20.txt
Approved by General Consent.
4. Executive Officer Reports
A. Chairman [Phil]
At last month's meeting, we continued discussion of the 5-year plan.
This has frankly been difficult for us to complete. Bertrand
suggested that we might do better to focus first on the high-level
vision and objectives before debating specific decision points.
Bertrand drafted a vision statement that we were able to agree on and
which I hope will be formally approved at today's meeting. I proposed
the following objectives for the 5-year plan. We have not reached
consensus yet on these, so they should be viewed as draft at this
point:
1. Ensure that the services that the ASF offers to project communities
are clearly defined and can be reliably delivered in a manner that
meets their expectations.
2 Improve our success for identifying, attracting, welcoming and
developing “like-minded communities” that will be successful at the
ASF.
3. Effectively scale our operations and governance processes in such a
way that the ASF continues to be a light-process, light-governance,
largely decentralized organization whose central operations serve
projects in a manner consistent with the way PMCs are expected to
serve their communities
4. Ensure the financial soundness of the ASF over the term of the plan
and establish the foundation for long-term stability
We need to start planning the 2019 budget soon, so my hope is that we
can complete the 5-year plan, including the financial projections, by
next month's meeting.
The quality of the project reports this month was overall very good.
Many thanks to the PMC chairs and PMC members who contributed. There
were quite a few very good reports this month. I will call out two as
as exemplary: CarbonData and Fineract. In each case, challenges as
well as progress are called out and a complete picture of the state of
the project is presented.
One thing that we often mention is that just presenting mailing list
stats is not necessary and should be omitted unless they add something
to the report. This month's Hbase report provides an example of using
ML stats to support the ideas in a report.
Several projects discussed their challenges with imbalance between
contributors and committers - i.e., large numbers of PRs and not
enough committers to keep up with them. In each case, the feedback
from the board was to try to find ways to get contributors on a faster
path to committership.
In some cases, commenters asked for a more complete picture of project
activity and community health. PMCs were reminded that project reports
are public and are the public record of the state of the project, so
its best to include more than just the basic facts about releases,
committer / PMC changes, etc.
As part of review of projects, we often look at project mailing lists.
This month, some comments were made about topics from dev or private
lists that would have been good to include in reports. For example,
one project dealt with a LGPL dependency issue. Including a summary of
the issue and how it was dealt with in the report would have been
good.
One comment asked that a PMC be careful with how its private repo is
used. Like private mailing lists, private repos should be used only
for things that really have to be private.
Finally, we had to repeat the reminder that reports should always
include the dates of the last committer addition, the last PMC member
addition and the last release.
Thanks again to all PMC chairs for taking the time to develop reports
this month and to my fellow board members for doing such a complete
and thoughtful review of the reports submitted.
B. President [Sam]
Items requiring board attention:
* Budget (can be deferred to discussion items)
* Three minor questions in Fundraising Report
* First has been discussed on board@
* I recommend the second be delegated to Legal Affairs
* Third is not ready for this month
### Executive Assistant
Despite the best efforts of myself, Ross and members of the board, the
ASF has come to the conclusion that it no longer has a need for an
Executive Assistant. This position has now been eliminated, and
Melissa has been laid off.
I've enjoyed working with Melissa, and will enthusiastically give her
a reference. If anybody knows of a good match for her ample talents,
I encourage them to act quickly!
I have no immediate plans to replace Melissa as VP, TAC. This will be
revisited once we have a large scale conference again.
### Finances and Budget
I agree with the Treasurer's report that income is exceeding targets
and expenses are under control, with the possibility that this year we
will show a modest surplus. The only caution is that $171K of this is
due to income that was not received last year, attributed at the time
to timing issues. If that is removed, we will see a deficit; but even
so a much smaller one than budgeted.
The impact of the laying off of the EA will be a modest increase in
expenses in January (to be reported in the February meeting), a modest
decrease in expenses for FY18, and a significant reduction ($100K,
which not only covers salary, but benefits, employer taxes, PEO
management overhead, etc.) in General & Administrative expenses in
subsequent years.
I encourage the board to complete their efforts on the 5 year plan by
the February meeting as that input is needed in the preparation of the
FY2019 budget. Delaying the FY2019 budget past the beginning of the
fiscal year will inevitably result in Tom and I having a shadow budget
that is unapproved by the board. Let's not do that.
My observation remains that both Brand Management and Fundraising
activities are beyond what can reasonably be expected to be sustained
by volunteers; with Brand Management being the more urgent of the two.
Ross has additional input on this matter.
Additionally, please see Attachments 1 through 7.
C. Treasurer [Ulrich]
Virtual Report:
Here is a summary of the Foundation’s performance for the first Eight
months of FY18.
Cash on Dec 31st, 2017 was $1,663K, which is up $31K from last month’s
ending balance (Nov 17) of $1,632K. The Dec 2017 cash balance is up
$65.1K from the Dec 2016 month end balance of $1,597.9K. The Dec 2017
ending cash balance of $1,663K represents a cash reserve of 14.7
months based on the FY18 conservative Cash forecast average monthly
spending of $112.8K/month. The ASF reserve continues to be very
healthy for an organization of ASF's size, with a conservative FY18
YE estimate of 13.5 months of Operating cash reserve.
Regarding the YTD Cash P&L, we continue to have a very strong and
favorable showing against our FY18 budget at this of point of the FY,
however as I will continue to mention, because we are on a cash basis,
the timing of Sponsor payments received and Payables released plays a
big part in how well we perform financially month to month and year
over year. This month we were over the FY 18 budget for Revenue
(Payments were received this month from Facebook Platinum Sponsor,
Aetna Silver Sponsor and STS Web Hosting Bronze Sponsor) and the
Foundation was under the FY18 budget in Expenses. As I have mentioned
in previous months we want to continue to focus on our new sponsors
but we also cannot take away any focus from our existing sponsors as
that was how the FY18 budget was constructed. The Fundraising team
continues to do an excellent job in both areas, servicing both new and
existing Sponsors. With total actual Revenue, as of Dec 31st, 2017,
of $977.1K, we are 79.7% of the way to our Total Revenue budget of
$1,226.5K for FY18, while only 67% of the way through FY18. Regarding
Sponsor revenue, we have received in the first eight months of FY18,
$899.6K, which has us 82.9% of the way to our budgeted Sponsor revenue
goal of $1,084K for FY18. This is fantastic, only 67% of the way
through the current Fiscal Year. As for the remaining revenue
categories, we have received $77.5K against a total budget of $139K or
55.8% of our FY budget eight months into the FY.
YTD expenses, through Dec 31st, 2017 are under budget by $79.7K. Most
depts. are either under budget or at budget, (Infra, due to being
right on budget for Dec 2017 remains YTD where it was at the end of
Nov 2017). We will continue to monitor the actual vs budget as we move
through the remaining four months of FY18. As we finish up Jan 2018, I
will be in contact with the dept. heads, to better forecast the final
quarter of FY18.
Regarding Net Income (NI), YTD for FY18 the ASF finished with a
positive $147.8K NI vs a budgeted negative <$263.9K> NI or $411.7K
ahead of the FY 18 Budget for Net Income eight months into the FY.
With the current conservative forecasted revenue, and expenses for the
remainder of FY 18, we are now estimating, at the Fiscal year end, a
positive $12.8K NI vs a budgeted NI loss of -$167.8K or about a
$180.6K better NI than the FY18 budget. This is attributable to a
combination of additional revenue and lower than budgeted expenses for
FY18 ($139.7K more in revenue and $40.9K in lower expenses based on
our conservative forecast). I would also like to point out that YTD
18 NI vs YTD 17 NI we are $372.8K ahead in Revenue while Expenses were
only $40.1K ahead year over year, for a $332.7K increase in NI year
over year ($147.8K positive NI in FY18 vs <-$184.9K> NI in FY 17).
Again, I want to congratulate the entire Foundation on these very
positive Operating results now that we are eight months through FY 18,
as it truly takes a team effort to achieve these types of results.
Now that we see what can be achieved by our efforts, we do need to
continue to keep these efforts up as we move through the remainder of
FY 18, and continue to give Fundraising all the support we can, while
keeping an eye on our expenses at the same time. We should also
recognize that the Foundation as compared to not only its FY18 budget
but also to FY 17 actuals, is in "a very good place" and we should all
be very proud of that fact.
The Cash Basis Audit continues to move along.
Board Summary Financials
Current Balances:
Citizens Money Market 1,496,525.97
Citizens Checking 152,548.57
Paypal - ASF 14,010.77
Total Checking/Savings 1,663,085.31
Dec-17 Budget Variance
Income Summary:
Inkind Revenue 0.00 0.00 0.00
Public Donations 4,562.55 5,670.32 -1,107.77
Sponsorship Program 135,000.00 20,000.00 115,000.00
Programs Income 0.00 0.00 0.00
Other Income 2,293.03 0.00 2,293.03
Interest Income 1,038.31 292.92 745.39
Total Income 142,893.89 25,963.24 116,930.65
Expense Summary:
In Kind Expense 0.00 0.00 0.00
Infrastructure 66,197.97 66,196.42 1.55
Sponsorship Program 2,000.00 2,000.00 0.00
Programs Expense 0.00 0.00 0.00
Publicity 6,954.83 17,000.00 -10,045.17
Brand Management 4,403.14 7,416.67 -3,013.53
Conferences 0.00 0.00 0.00
Travel Assistance Committee 0.00 0.00 0.00
Tax and Audit 0.00 0.00 0.00
Treasury Services 3,350.00 3,500.00 -150.00
General & Administrative 8,630.01 14,052.73 -5,422.72
Total Expense 91,535.95 110,165.82 -18,629.87
Net Income 51,357.94 -84,202.58 135,560.52
YTD 2018 Budget Variance
Income Summary:
Inkind Revenue 0.00 0.00 0.00
Public Donations 44,921.84 23,403.77 21,518.07
Sponsorship Program 899,612.08 591,250.00 308,362.08
Programs Income 15,100.00 28,025.00 -12,925.00
Other Income 11,850.45 0.00 11,850.45
Interest Income 5,660.01 2,343.36 3,316.65
Total Income 977,144.38 645,022.13 332,122.25
Expense Summary:
In Kind Expense 0.00 0.00 0.00
Infrastructure 557,034.91 549,928.14 7,106.77
Sponsorship Program 16,831.96 23,250.00 -6,418.04
Programs Expense 0.00 0.00 0.00
Publicity 100,037.56 127,000.00 -26,962.44
Brand Management 44,161.02 59,333.36 -15,172.34
Conferences 5,200.15 8,418.00 -3,217.85
Travel Assistance Committee 2,191.81 22,500.00 -20,308.19
Tax and Audit 2,162.00 6,000.00 -3,838.00
Treasury Services 26,550.00 27,450.00 -900.00
General & Administrative 75,148.08 85,090.67 -9,942.59
Total Expense 829,317.49 908,970.17 -79,652.68
Net Income 147,826.89 -263,948.04 411,774.93
Asst Treasurer Report:
- Things are running very smoothly.
- Canceled CSC renewal - $441 just for registered agent, canceled -
Requested refund and we MIGHT get $155 returned for the annual
report filing.
- Hired incorp for $104 annually for registered agent fee. Virtual is
filing annual report at no extra charge. Will file the first,
correct Annual report in about a decade soon (as of 1/12)
Question: Where to store the invoice/contract information for incorp,
our new registered agent?
- PackT royalties will not be sent to the ASF directly. I will have
to give them a personal bank account as the contract is “personal
not business” and has my name on it. Even though it’s royalties
donated by Doug Cutting to the ASF. I haven’t decided if I like
giving them my personal account as a passthrough.
- Network for Good database is updated and they sent a replacement
check which was confirmed cashed.
- A Donation Minimum will be implemented soon with Hopsie. Likely in
the ~$5 range as fees otherwise make it pointless and we get $1
donations and $0.01 donations.
- Any comments or questions to add and answer on the D&O Governance
FAQ?
https://docs.goog le.com/document/d/1k1rjAe8w38pi25Qaksoeu5m45EVnGBXvuK2jqiJo43k/edit#
Previously Reported Items Still Tracking w/Nothing to Report
- Have not tested transferwise.com, pending a contractor’s help
testing.
- Contribution Language for Car Donations - No update. Not a high
priority.
- Documenting payment privacy changes - No update but pinged so we can
consider moving to Google instead of Dropbox since G Suite is
donated.
- CDARS - Paperwork is done and this should be implemented soon.
- Will to get contracts for Virtual, Hopsie & HALO confirmed and in
ASF SVN or drive. Working to make sure as much as possible is
documented.
- Quickbooks Backups - Need to ping Virtual and check on progress for
this.
D. Secretary [Craig]
Work continues on the new whimsy application for inviting contributors
to file an ICLA. For a demo please visit
whimsy.apache.org/project/icla
In December 170 ICLAs, four CCLAs, and three grants were received and
filed.
E. Executive Vice President [Ross]
Infrastructure
==============
Everything progressing well. Upgrades to both Jira and Jenkins being
highlights. Good progress on GitBox tooling to perform "mass
migration" of projects from git-wip over to gitbox, with the goal of
deprecating the Foundation's operation and management of git
repositories.
Marketing and Publicity
=======================
A milestone was reaching - we raised more than $20K and communicated
with 363 individual donors via Hopsie since launching on 28 March
2017. While this number is small when compared to our overall
fundraising activities it is notable that we have been exploring ways
to empower individual donors for many years. This progress is very
encouraging.
At the request of the Presidents office, Halo have worked with VP
Trademarks to draw up a proposal to provide support for our trademarks
activities. This is designed to address the growing workload on our
volunteers. I would note that this proposal is about ensuring prompt
and appropriate attention to trademark issues where the foundation
deems them important. It is independent of any discussion about where
Trademark management should sit in the org structure.
In order to set context I will remind the board of why investing in
supporting our volunteers is important in this area, firstly I'll
quote Phil's proposal [1]:
1. The ASF should provide support for some PMCs to register their
trademarks.
2. The ASF should provide support for some PMCs to help ensure that
their brands are used appropriately.
Assuming that we have consensus on these two statements I'll go on to
explain my own justification for providing support to our volunteers
(shared and refined with others including VP Trademarks, VP Marketing
and President):
* Open source used to be mostly about sharing expertise around
internally used software
* Over time open source has increasingly become a part of products
for sale
* Open source brands have therefore become valuable as a result,
e.g. Apache is about quality and independence, Kubernetes is about
infrastructure standardization
* As direct revenue is increasingly generated from software built on
OSS, so has marketing pressure to use OSS brands to attract sales
* The rise of “consortium led” OSS means that trademark use for this
purpose is often seen as acceptable
* Consequently the ASF is seeing increasing pressure to allow use of
its marks in ways that would undermine our meritocratic model of
independent governance
* Therefore, the ASF needs to step up it’s protection of our marks
so that we maintain independence within our communities
It is my hope that the board will consider Halo's proposal and work
through the Presidents office as we seek to build a model that is both
cost efficient and gentle on our volunteer efforts.
Conferences
===========
Continued investigations with respect to co-location of an event with
Berlin Buzzwords.
TAC
===
No events planned at present.
[1] https://lists.apache.org/thread.html/aa6f29608a6ee1a61490fa54568edf7d7db09097d059850c4c1307d4@%3Cboard.apache.org%3E
F. Vice Chairman [Jim]
Nothing to report.
Executive officer reports approved as submitted by General Consent.
5. Additional Officer Reports
A. VP of W3C Relations [Andy Seaborne / Jim]
See Attachment 8
B. Apache Legal Affairs Committee [Chris Mattmann]
See Attachment 9
C. Apache Security Team Project [Mark J. Cox / Brett]
See Attachment 10
Additional officer reports approved as submitted by General Consent.
6. Committee Reports
Summary of Reports
The following reports required further discussion:
# ActiveMQ [mt]
# AsterixDB [mt]
# Axis [jj]
# Geronimo [bp]
# MINA [rb]
# OpenOffice [bd]
A. Apache Accumulo Project [Michael Wall / Shane]
See Attachment A
B. Apache ActiveMQ Project [Bruce Snyder / Chris]
See Attachment B
@Mark: pursue feedback from board meetings
C. Apache Airavata Project [Suresh Marru / Rich]
See Attachment C
D. Apache Apex Project [Thomas Weise / Ted]
See Attachment D
E. Apache Archiva Project [Olivier Lamy / Mark]
See Attachment E
F. Apache Aries Project [Jeremy Hughes / Bertrand]
See Attachment F
G. Apache Arrow Project [Jacques Nadeau / Phil]
See Attachment G
H. Apache AsterixDB Project [Till Westmann / Phil]
See Attachment H
@Mark: follow up board feedback
I. Apache Attic Project [Jan Iversen / Bertrand]
See Attachment I
J. Apache Avro Project [Ryan Blue / Mark]
See Attachment J
K. Apache Axis Project [Robert Lazarski / Jim]
See Attachment K
L. Apache Calcite Project [Michael Mior / Brett]
See Attachment L
M. Apache CarbonData Project [Liang Chen / Shane]
See Attachment M
N. Apache Celix Project [Pepijn Noltes / Ted]
See Attachment N
O. Apache Chukwa Project [Eric Yang / Rich]
See Attachment O
P. Apache Crunch Project [Josh Wills / Chris]
See Attachment P
Q. Apache CXF Project [Daniel Kulp / Rich]
See Attachment Q
R. Apache DB Project [Bryan Pendleton / Jim]
See Attachment R
S. Apache Directory Project [Stefan Seelmann / Bertrand]
See Attachment S
T. Apache Fineract Project [Myrle Krantz / Mark]
See Attachment T
U. Apache Fluo Project [Keith Turner / Chris]
See Attachment U
V. Apache Geronimo Project [Alan Cabrera / Brett]
See Attachment V
@Brett: follow up on possible chair change
W. Apache Guacamole Project [Mike Jumper / Shane]
See Attachment W
X. Apache Hadoop Project [Christopher Douglas / Ted]
See Attachment X
Y. Apache HBase Project [Misty Stanley-Jones / Phil]
See Attachment Y
Z. Apache Helix Project [Kishore G / Ted]
See Attachment Z
AA. Apache Impala Project [Jim Apple / Shane]
See Attachment AA
AB. Apache Incubator Project [John D. Ament / Mark]
See Attachment AB
AC. Apache Isis Project [Kevin Meyer / Brett]
See Attachment AC
AD. Apache James Project [Eric Charles / Rich]
No report was submitted.
AE. Apache jclouds Project [Andrea Turli / Chris]
See Attachment AE
AF. Apache Jena Project [Andy Seaborne / Phil]
See Attachment AF
AG. Apache JMeter Project [Bruno Demion / Jim]
See Attachment AG
AH. Apache Johnzon Project [Hendrik Saly / Bertrand]
See Attachment AH
AI. Apache JSPWiki Project [Juan Pablo Santos Rodríguez / Brett]
See Attachment AI
AJ. Apache Juneau Project [James Bognar / Bertrand]
See Attachment AJ
AK. Apache Kibble Project [Rich Bowen]
See Attachment AK
AL. Apache Kudu Project [Todd Lipcon / Ted]
See Attachment AL
AM. Apache Labs Project [Danny Angus / Shane]
See Attachment AM
AN. Apache Lucene.Net Project [Prescott Nasser / Mark]
See Attachment AN
AO. Apache Lucy Project [Peter Karman / Jim]
See Attachment AO
AP. Apache MADlib Project [Aaron Feng / Phil]
See Attachment AP
AQ. Apache Mahout Project [Andrew Palumbo / Chris]
See Attachment AQ
AR. Apache Maven Project [Robert Scholte / Rich]
See Attachment AR
AS. Apache Mesos Project [Benjamin Hindman / Bertrand]
No report was submitted.
@Bertrand: pursue a report for Mesos
AT. Apache Metron Project [Casey Stella / Shane]
See Attachment AT
AU. Apache MINA Project [Jeff Maury / Phil]
See Attachment AU
AV. Apache Mnemonic Project [Gang Wang / Mark]
See Attachment AV
AW. Apache MyFaces Project [Mike Kienenberger / Ted]
See Attachment AW
AX. Apache NiFi Project [Joe Witt / Jim]
See Attachment AX
AY. Apache Nutch Project [Sebastian Nagel / Rich]
See Attachment AY
AZ. Apache ODE Project [Sathwik / Brett]
See Attachment AZ
BA. Apache Olingo Project [Christian Amend / Chris]
See Attachment BA
BB. Apache Oltu Project [Antonio Sanso / Jim]
No report was submitted.
BC. Apache OpenJPA Project [Mark Struberg / Brett]
See Attachment BC
BD. Apache OpenMeetings Project [Maxim Solodovnik / Bertrand]
See Attachment BD
BE. Apache OpenOffice Project [Peter Kovacs / Shane]
See Attachment BE
BF. Apache ORC Project [Owen O'Malley / Phil]
See Attachment BF
BG. Apache Parquet Project [Julien Le Dem / Mark]
See Attachment BG
BH. Apache PDFBox Project [Andreas Lehmkühler / Chris]
See Attachment BH
BI. Apache PredictionIO Project [Donald Szeto / Rich]
See Attachment BI
BJ. Apache Ranger Project [Selvamohan Neethiraj / Ted]
See Attachment BJ
BK. Apache Samza Project [Yi Pan / Mark]
See Attachment BK
BL. Apache Sqoop Project [Jarek Jarcec Cecho / Rich]
See Attachment BL
BM. Apache Steve Project [Daniel Gruno / Chris]
See Attachment BM
BN. Apache Streams Project [Steve Blackmon / Bertrand]
See Attachment BN
BO. Apache Struts Project [René Gielen / Phil]
See Attachment BO
BP. Apache Tapestry Project [Thiago Henrique De Paula Figueiredo / Brett]
See Attachment BP
BQ. Apache Tcl Project [Massimo Manghi / Shane]
See Attachment BQ
BR. Apache Tez Project [Siddharth Seth / Ted]
See Attachment BR
BS. Apache Thrift Project [Jake Farrell / Jim]
See Attachment BS
BT. Apache Tika Project [David Meikle / Phil]
See Attachment BT
BU. Apache TinkerPop Project [Stephen Mallette / Mark]
See Attachment BU
BV. Apache Tomcat Project [Mladen Turk / Chris]
See Attachment BV
BW. Apache TomEE Project [David Blevins / Jim]
See Attachment BW
BX. Apache Traffic Server Project [Bryan Call / Rich]
See Attachment BX
BY. Apache Trafodion Project [Pierre Smits / Brett]
See Attachment BY
BZ. Apache VXQuery Project [Till Westmann / Ted]
See Attachment BZ
CA. Apache Web Services Project [Daniel Kulp / Bertrand]
See Attachment CA
CB. Apache Zeppelin Project [Lee Moon Soo / Shane]
See Attachment CB
Committee reports approved as submitted by General Consent.
7. Special Orders
A. Change the Apache Flume Project Chair
WHEREAS, the Board of Directors heretofore appointed Hari Shreedharan
(hshreedharan) to the office of Vice President, Apache Flume, and
WHEREAS, the Board of Directors is in receipt of the resignation of
Hari Shreedharan from the office of Vice President, Apache Flume, and
WHEREAS, the Project Management Committee of the Apache Flume project
has chosen by vote to recommend Mike Percy (mpercy) as the successor
to the post;
NOW, THEREFORE, BE IT RESOLVED, that Hari Shreedharan is relieved and
discharged from the duties and responsibilities of the office of Vice
President, Apache Flume, and
BE IT FURTHER RESOLVED, that Mike Percy be and hereby is appointed to
the office of Vice President, Apache Flume, 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 Flume Project Chair, was
approved by Unanimous Vote of the directors present.
B. Change the Apache Avro Project Chair
WHEREAS, the Board of Directors heretofore appointed Ryan Blue
(blue) to the office of Vice President, Apache Avro, and
WHEREAS, the Board of Directors is in receipt of the resignation
of Ryan Blue from the office of Vice President, Apache Avro,
and
WHEREAS, the Project Management Committee of the Apache Avro
project has chosen by vote to recommend Thiruvalluvan M. G.
(thiru) as the successor to the post;
NOW, THEREFORE, BE IT RESOLVED, that Ryan Blue is relieved and
discharged from the duties and responsibilities of the office
of Vice President, Apache Avro, and
BE IT FURTHER RESOLVED, that Thiruvalluvan M. G. be and hereby
is appointed to the office of Vice President, Apache Foo, 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 Avro Project Chair, was
approved by Unanimous Vote of the directors present.
8. Discussion Items
1. The Board's 2018 vision statement
The following vision statement is proposed for approval by the
Board, to be published on our Foundation blog and used as a basis
for our 5-year plan:
Our mission is to support communities that create and distribute
Open Source software at no charge under the Apache License, per our
Bylaws. To this end we provide (virtual) space and resources,
including mentoring, for project communities to flourish, produce
and release software under our legal umbrella.
We are strongly committed to our projects' independence from any
external influences, be they corporate, organizational or otherwise.
This allows us to provide a neutral space for our communities.
As a Foundation we intentionally do not define a technical strategy;
that is determined by our projects. The Foundation's goals center on
communities, as opposed to technologies.
The Foundation is managed and directed by its Members, who are
individual volunteers. Companies or organizations cannot be members
of the Foundation, nor take a role in the governance of our
projects.
We help our communities understand and practice the Apache Way, a
collection of practices for collaboration and project sustainability
that we document and clarify on an ongoing basis.
We expect our community members to act as individuals. Their rights
and responsibilities are based solely on their merit, defined by
what they individually do in project communities, not on any
external affiliation, title, or degree they may have, nor on their
contributions to external projects or other organizations.
We provide very reliable and highly automated core infrastructure
services to our projects. We allow projects to use external non-core
services based on their specific needs, allowing our own services to
remain simple and focused. For durability, all our critical data and
services are managed or mirrored on systems that we fully control.
Our marketing and outreach is focused on activities that directly
support our mission, educate the public about Apache projects and
the Apache Way, and help attract the types of communities for which
our Foundation is a good home.
Our fundraising-related activities help find and retain the sponsors
and donations on which our operations depend. We seek donations from
corporations and individuals who support our mission.
We provide legal and brand management services to our projects based
on demonstrated needs, and define branding policies and best
practices to help our projects benefit from the strong Apache brand
in an appropriate way.
We welcome new projects via our Incubator, where experienced mentors
help them learn to operate as Apache communities and projects.
Incubation is where communities are defined, so we put a strong
emphasis on guidance during the incubation phase to promote
self-governance and preserve our core values as the Foundation
grows.
The board adopts this mission statement as proposed by general
consent.
@Sally: review the mission statement for publication
2. Budget
With the lay-off of the EA, the bottoms up five year projections now
show a modest positive balance. This likely is understated for the
following reasons:
1. Even conservative projections show us doing better than projected
for FY18. While much of that was due to FY17 timing issues, it still
represents an increased amount in the bank.
2. The model the projections use is a linear change (mostly growth)
in expenses and revenue by category. While there may be some
offsetting expenses we will need to incur without an EA, this amount
is unlikely to equate to the amount projected.
The budget worksheet has been updated to reflect the above.
3. Call-in number changes
The dial in number for future meetings may change. Do we still need
a toll-free US number?
@Sam: pursue an alternative board conference call strategy
9. Review Outstanding Action Items
* Ted: Discuss state of development with PMC; encourage on-list development
[ Tajo 2017-06-21 ]
Status:
* Ted: pursue a report for Community Development; look at previous examples of
[ Community Development 2017-08-16 ]
Status:
* Mark: follow up re: handling security issues
[ Cordova 2017-12-20 ]
Status: In progress.
* Mark: follow up on the comments re: Cloudera support
[ Eagle 2017-12-20 ]
Status: Complete. Clarified as meaning "support for Cloudera's CDH
product".
* Mark: follow up on CVE actions
[ Flex 2017-12-20 ]
Status: Complete: Missed step in handling process completed.
* Mark: pursue a report for Helix
[ Helix 2017-12-20 ]
Status: Complete: Report provided for Jan meeting
* Mark: pursue a report for Labs; what are long term prospects?
[ Labs 2017-12-20 ]
Status: Complete: Report provided for Jan meeting
* Phil: pursue a more substantial report for next month
[ Lucene.Net 2017-12-20 ]
Status: Complete. Report was filed for Jan meeting.
* Rich: follow up on previous board comments regarding PMC and committers
[ UIMA 2017-12-20 ]
Status:
10. Unfinished Business
11. New Business
12. Announcements
13. Adjournment
Adjourned at 12:08 p.m. (Pacific)
============
ATTACHMENTS:
============
-----------------------------------------
Attachment 1: Report from the Executive Assistant [Melissa Warnkin]
-----------------------------------------
Attachment 2: Report from the VP of Brand Management [Shane Curcuru]
* ISSUES FOR THE BOARD (continuing issue)
The number of PMC and external requests coming in continues to exceed the
available volunteer expertise and time by a significant amount.
The current path is unsustainable, and is a disservice to the ASF, all of our
projects, and the many well-behaved outside parties wishing to use Apache
trademarks in their own work.
* OPERATIONS
The number of new requests from PMCs and external parties continues to far
outstrip the available volunteer time and expertise, resulting in a growing
backlog of questions to address. As an example, since the past board meeting
there have been:
- 3 emails to vp-brand@ with actionable information
- 2 invoices
- 2 informational emails to tm-registrations@ (reports of registration actions
that we've requested)
- 3 queries from counsel on tm-registrations@ requiring a response
- 58 total emails to trademarks@:
- 7 new queries/threads from PMCs, Members, or committers
- 4 new queries/threads from outside parties
- traffic on 3 threads dealing with policy questions
- Overall, at least 15 outstanding queries, mostly from outside parties,
awaiting a final answer to their questions about Apache trademark use
Mark Thomas assisted in spotting and correcting a bug in one of our mailing
list configurations.
I co-presented "Trademarks In Open Source" at the PLI: Open Source Software
2017 - From Compliance to Cooperation law continuing education conference.
Website Analytics shows the expected end-of-year dip in overall traffic and
mostly the same kinds of trends as past months.
* REGISTRATIONS & CONTRACTS
To better document the entire registration process, including showing how much
management and coordination is done for each mark applied for, I wrote up the
9 step lifecycle for that process (one out of 24 different processes managed
in brand).
No new registration news otherwise this month.
-----------------------------------------
Attachment 3: Report from the VP of Fundraising [Kevin A. McGrail]
Board Discussion Item #1: Can the board please discuss / vote adding the
phrase “at no charge” to our mission?
Board Discussion Item #2: Thoughts on licensing ASF commercially if people so
desire? Daniel Shahaf pointed out https://sqlite.org/copyright.html. If
people will pay for it and we give them nothing extra, any concerns?
Board Discussion Item #3: Resolution to establish VP, Sponsor Relations is on
a back burner due to the holidays and other priorities. Expect to raise it
again soon, certainly before the end of the FY.
ASF eligibility for Benevity renewed for a year.
We closed out 2017 with $21,743.24 raised through 259 payments processed via
Hopsie. Fundraising committee meetings with Virtual continue and are
productive. Will move to monthly now that Sponsor Audit is complete and
things are more routine.
KAM will attend FOSDEM on behalf of the ASF. Will notify sponsors and
potential sponsors.
KAM planning to attend Buzzwords and FOSS backstage as well.
Completed the pitch deck update that was in progress.
No update about the Fundraising / MiniApacheCon Idea at GMU. College re-opens
on the 16th of January and hope to have more movement after that.
Sent a Happy New Year's note out to Sponsors.
Had a multi-day outage on Hopsie caused by an IP block. Looking at changing
how we proxy Hopsie as the fraud block ended up blocking our proxy.
New sponsors continue to be added and thanks version 2.0 with targeted
sponsors continues to be moved towards launch. A few more logos to add.
Cloudera, Hortonworks also renewed. IBM is currently invoiced for 1 year and
working on the future years. Working with Indeed as a platinum and cloudsoft
renewing. Oath also still moving along and Bookmakers now a 3-year bronze
sponsor
Reiterating from Virtual report: “Regarding Sponsor revenue, we have received
in the first eight months of FY18, $899.6K, which has us 82.9% of the way to
our budgeted Sponsor revenue goal of $1,084K for FY18.”
No update on the Sponsor thank you / fundraising event
-----------------------------------------
Attachment 4: Report from the VP of Marketing and Publicity [Sally Khudairi]
I. Budget: we are reviewing our expenses anticipated through the end
of the fiscal year. Thus far, our operations remain on budget and on
schedule, with no outstanding vendor payments due.
II. Cross-committee Liaison: work with ASF Fundraising continues.
Since formally returning to work with ASF Fundraising in March 2017,
Sally Khudairi was able to successfully secure more than $600K in
Sponsorship renewals. We raised more than $20K and communicated with
363 individual donors via Hopsie since launching on 28 March 2017. ASF
Platinum and Gold Sponsor promotions have begun and will debut early
2018; four ASF Sponsors have participated in new media opportunities
relating to Apache project and community initiatives. The “Success at
Apache” program closed out its inaugural year with the publication of
is 12th post, "Success at Apache: What a Long Strange (and Great) Trip
It's Been" https://s.apache.org/gVuN . We have also published Apache
in 2017 - By The Digits https://s.apache.org/h8do ; most of the data
points were made possible by Snoot.
III. Press Releases: the following formal announcements were issued
via the newswire service, ASF Foundation Blog, and announce@apache.org
during this timeframe:
- 10 January 2018 - The Apache Software Foundation Announces Apache®
Trafodion™ as a Top-Level Project
- 14 December 2017 - The Apache Software Foundation Announces
Apache® Hadoop® v3.0.0 General Availability
- 13 December 2017 - The Apache Software Foundation Announces
Apache® Mnemonic™ as a Top-Level Project
IV. Informal Announcements: 9 items were published on the ASF
"Foundation" Blog. We are preparing new ASF Sponsor promotions, which
include "Success at Apache" and Sponsor Case Studies. 4 Apache News
Round-ups were issued, with a total of 181 weekly summaries published
to date. We tweeted 21 items, and have 45.4K followers on Twitter. We
posted 10 items on LinkedIn, which garnered more than 109.2K organic
impressions in total.
V. Future Announcements: one announcement is in development. Projects
planning to graduate from the Apache Incubator as well as PMCs wishing
to announce major project milestones and "Did You Know?" success
stories are requested to contact Sally at <press@apache.org> with at
least 2-weeks' notice for proper planning and execution.
VI. Media Relations: we responded to 9 media queries. The ASF received
2,038 press clips vs. last month's clip count of 2,119. Media coverage
of Apache projects yielded 3,214 press hits vs. last month's 5,039.
VII. Analyst Relations: we received one analyst query pertaining to
build automation tools. Apache was mentioned in 10 reports by Gartner,
4 reports by Forrester, 11 reports by 451 Research, and 7 reports by
IDC.
VIII. Graphics: no projects are currently in production. We are
consolidating our inventory of signage and promotional items to be
distributed at events.
IX. Events liaison: Sally has been working with Sharan Foga on the
ASF’s ComDev presence at various events over the course of the fiscal
year, and has established criteria for which events the Foundation
would be having an official presence in future. In addition, we have
completed the ASF’s submission for the Open Expo Madrid eBook.
X. Newswire accounts: we have 11 pre-paid press releases remaining
with NASDAQ GlobeNewswire through 2018.
# # #
-----------------------------------------
Attachment 5: Report from the VP of Infrastructure [David Nalley]
General
=======
Infrastructure continues to operate normally, with no issues to raise
to the President or the Board.
Short Term Priorities
=====================
* Move more content onto infra.a.o
* Move our DNS hidden master off of minotaur.a.o, as part of our
long-term program to deprecate minotaur.
* Prepare for moving to Atlassian's "Stride" chat system, as HipChat
is being deprecated. Initial testing has already begun, but we do
not (yet) have a hard date on when they will cut us over.
Long Range Priorities
=====================
* Continue deprecating old hardware and operating systems, moving onto
VMs and machines at third-party hosting services
General Activity
================
Jira underwent a major upgrade on January 14. We are now on the
almost-latest version of Jira (they released a new version last week).
This allows for some better integrations with our LDAP system and
other Atlassian software that we run.
We have continued to make improvements to the GitBox system, including
a more responsive list of respositories. We've been working on tooling
to perform "mass migration" of projects from git-wip over to gitbox,
with the goal of deprecating the Foundation's operation and management
of git repositories. We will retain a mirror/archive of projects'
repositories on GitHub (to meet Legal Affairs' requirements), but
these are much simpler to manage, being readonly and low traffic.
Our work on simplifying the LDAP system has progressed nicely. There
are some remaining items related to older operating systems, and some
external partners that we will be wrapping up. This has reduced the
number of LDAP-related incidents that we used to see, interfering with
operations of our infrastructure.
The holiday season also gave us a great opportunity to upgrade Jenkins
to its next LTS release, and to make numerous improvements to its
speed and reliability. As Apache Maven has reported, we've worked with
them to improve job management and web site generation.
Uptime Statistics
=================
We continue to maintain a high state of uptime, meeting our goals.
-----------------------------------------
Attachment 6: Report from the VP of Conferences [Rich Bowen]
We are still pursuing a small, collocated event alongside Berlin Buzzwords.
Sharan has taken the lead for this event. We are also still looking for venues
in North America for fall of 2018 for a full ApacheCon event.
-----------------------------------------
Attachment 7: Report from the Apache Travel Assistance Committee [Melissa Warnkin]
-----------------------------------------
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 monthly was pretty quiet, as expected since it included the Winter
holidays for many.
Discussion surrounding ECCNs for Cassandra and Kafka was initiated in
LEGAL-358 [1]. Apparently the page for a.o/licenses/exports/ did not include
entries for those projects. So far the Apache Cassandra PMC has responded with
the required updates to the page but we are still waiting for the Apache Kafka
PMC to reply. David Nalley suggested we may want to revisit our policies for
recording ECCNs. Legal advises the Board that the relevant committee
(Security? Infra?) may want to consider this.
A question regarding commercial use and attribution of ASF software was raised
and replied to by members of the Legal committee and list.
Two active threads regarding the proper location of attributions and notices
(LICENSE or NOTICE files) continues on the legal-discuss list. No definitive
conclusions have been arrived at, but the discussions have proven quite
valuable to those participating.
[1] https://issues.apache.org/jira/browse/LEGAL-358
-----------------------------------------
Attachment 10: Report from the Apache Security Team Project [Mark J. Cox]
At the end of 2017 we switched to using a shared gmail account for
handling security@apache mail with use of labels to track issues.
This has already started to have a positive effect stopping the
handlers duplicating effort and allowing us to better track issues
that still need actions.
The metrics I usually include in the board report are a by-product of
a monthly walkthrough of the mailbox to spot any missed issues. The
new handling system does not require this monthly walkthrough and so
there are no stats this month. However we're working on scripts to
reinstate this, as well as provide more useful stats for board
oversight.
One of these reports we can now automatically create is an aging
report showing the number of outstanding security issues per project
and how long they have been open:
* As of 2008-01-01 there were 185 open security issues across
61 projects with median age 134 days
This metric is created automatically and each of the issues has not
been checked for accuracy. We're working our way through these in the
coming weeks to determine the state and then our future board reports
can highlight projects where we have concerns (i.e. with large numbers
of open issues or generally unresponsive).
-----------------------------------------
Attachment A: Report from the Apache Accumulo Project [Michael Wall]
## Description:
- The Apache Accumulo sorted, distributed key/value store is a robust,
scalable, high performance data storage system that features cell-based
access control and customizable server-side processing. It is based on
Google's BigTable design and is built on top of Apache Hadoop, Zookeeper,
and Thrift.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- There were no new releases during the current reporting period.
- There were 4 new contributors added since the last report.
- The 4th annual Accumulo Summit was held just after the last report was
submitted. The PMC has approved the use of the Apache Accumulo trademark.
Slides from the talks can be viewed on the summit website. [1]
- Apache Accumulo now has a hands-on tour that introduces users to key
Accumulo concepts by completing a series of programming exercises. [2]
- Work to support Apache Accumulo in Docker has begun. It is based on the
unreleased 2.0 line, so you will have to build your your image. [3]
- Community is discussing a 1.9 release instead of going from 1.8 to 2.0.
The release of Hadoop 3.0 and how Accumulo will support it started the
discussion.
## Health report:
- The project remains healthy. Activity levels on mailing lists, git and
JIRA remain constant.
## PMC changes:
- Currently 30 PMC members.
- No new committers added in the last 3 months
- Last committer addition was Ivan Bella at Wed Jul 12 2017
## Committer base changes:
- Currently 30 committers.
- No new committers added in the last 3 months
- Last committer addition was Ivan Bella at Wed Jul 12 2017
## Releases:
- Last release was 1.7.3 on Sat Mar 25 2017
## Mailing list activity:
- Nothing significant in the figures
## JIRA activity:
- 60 JIRA tickets created in the last 3 months
- 61 JIRA tickets closed/resolved in the last 3 months
[1]: http://accumulosummit.com/program/schedule/
[2]: http://accumulo.apache.org/blog/2017/12/12/take-the-accumulo-tour.html
[3]: https://github.com/apache/accumulo-docker
-----------------------------------------
Attachment B: Report from the Apache ActiveMQ Project [Bruce Snyder]
Description
Apache ActiveMQ is a popular and powerful open source message-oriented
middleware. Apache ActiveMQ is fast, supports many cross language clients and
protocols, comes with easy to use enterprise integration patterns and many
advanced features while fully supporting JMS 2.0, AMQP 1.0, MQTT, Stomp and
REST.
Activity
ActiveMQ
* Some folks are collaborating on the redesign/refactor of the ActiveMQ
project website to give it a makeover and to better identify where activity
is taking place
* A vote was held to make the Apollo project read-only and indicate on both
the ActiveMQ website and in the Apollo readme that the project is no longer
under active development
ActiveMQ Artemis
* An Artemis Roadmap wiki page was created to identify the outstanding issues
that must be addressed by Artemis in order to achieve some level of feature
parity with ActiveMQ 5.x. The overall objective for working toward feature
parity between ActiveMQ 5.x and Artemis is for Artemis to eventually become
ActiveMQ 6.x.
* The web console for Artemis has had good adoption with contributors beyond
that of the originals contributing
* Clebert Suconic hosted a video call to walk through the Aretmis code base
with some folks
Releases
* ActiveMQ 5.15.2 was released on Fri Oct 20 2017
* ActiveMQ Artemis 2.4.0 was released on Tue Nov 7 2017
Committer Changes
* Michael André Pearce at Fri Sep 29 2017
-----------------------------------------
Attachment C: Report from the Apache Airavata Project [Suresh Marru]
## Description:
- Apache Airavata is a distributed system software framework to manage simple
to composite applications with complex execution and workflow patterns on
diverse computational resources
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- The community is active without any major concerns.
## Health report:
- The community is reasonably active. We are trying to make some
architectural changes which we hope to stir increased developer (and user)
engagement.
## PMC changes:
- Currently 23 PMC members.
- Marcus Christie was added to the PMC on Thu Nov 16 2017
## Committer base changes:
- Currently 33 committers.
- No new committers added in the last 3 months
- Last committer addition was Ajinkya Dhamnaskar at Tue Apr 11 2017
## Releases:
- Last release was 0.16 on Mon Jul 25 2016 We have been excessively relying
on ansible scripts for the user community to clone the master repo and
build and use airavata. This is a concern we will address to make periodic
snapshots and release actively. We will address the release issue (or lack
of) before next board report.
## JIRA activity:
- 84 JIRA tickets created in the last 3 months
- 14 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment D: Report from the Apache Apex Project [Thomas Weise]
## Description:
Apache Apex is a distributed, large-scale, high-throughput, low-latency, fault
tolerant, unified stream and batch processing platform.
## Issues:
There are currently no issues that require the Board's attention.
## Status/Activity:
In November the community released version 3.8.0 of Apex Malhar (the library).
New features included support for Apache Kudu (read and write), connector for
Apache Flume, multi-table output operator for Apache HBase, enhanced example
applications, and more.
For Apex Malhar a new major release line 4.x was started, allowing for
backward incompatible changes (including removal of deprecated code and
overdue cleanup like moving all code under org.apache.apex packages).
Also at the end of 2017, the first book about the project, “Learning Apache
Apex” was published. It was written by project committers.
Activity in the project had declined since June of last year and in the last
few months the project had only very few contributions from a handful of
contributors.
## Community:
- Currently 16 PMC members.
- Last PMC addition was Tushar Gosavi on 2017-10-13
- Currently 41 committers.
- Last committer addition was Ananth Gundabattula on 2017-11-03
- Contributors: 78 all time, 41 in last 12 months (+0, -9 since last report)
## Releases:
Following are the most recent releases:
- Core 3.6.0 released 2017-05-04
- Malhar 3.8.0 released 2017-11-12
-----------------------------------------
Attachment E: Report from the Apache Archiva Project [Olivier Lamy]
## Description:
Apache Archiva software is an extensible repository management tool that
helps taking care of your own personal or enterprise-wide build artifact
repository.
## Issues:
there are no issues requiring board attention at this time
## Activity:
We have finished refactoring moving from Jackrabbit to Oak.
And now discussing even more changes to make Archiva a more generic platform.
## Health report:
We have enough PMC to cut release.
## PMC changes:
- Currently 9 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Martin Stockhammer on Mon Apr 10 2017
## Committer base changes:
- Currently 21 committers.
- No new committers added in the last 3 months
- Last committer addition was Martin Stockhammer at Thu Sep 22 2016
## Releases:
- Last release was 2.2.3 on Tue May 16 2017
## Mailing list activity:
- users@archiva.apache.org:
- 230 subscribers (up 0 in the last 3 months):
- 5 emails sent to list (8 in previous quarter)
- dev@archiva.apache.org:
- 107 subscribers (up 0 in the last 3 months):
- 9 emails sent to list (31 in previous quarter)
- issues@archiva.apache.org:
- 33 subscribers (down -1 in the last 3 months):
- 55 emails sent to list (32 in previous quarter)
- notifications@archiva.apache.org:
- 15 subscribers (up 0 in the last 3 months):
- 33 emails sent to list (69 in previous quarter)
## JIRA activity:
- 8 JIRA tickets created in the last 3 months
- 5 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment F: Report from the Apache Aries Project [Jeremy Hughes]
# January 2018 Board report
- Apache Aries delivers a set of pluggable Java components enabling an
enterprise OSGi application programming model.
## Issues:
- None to report this quarter.
## Activity:
- As a community we made 10 releases this quarter.
- After some discussion, the tx-control module is being moved into
gitbox.apache.org.
## Health report:
- the net number of JIRA tickets has crept up slightly this month, but
generally under control.
## PMC changes:
- Currently 38 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Dominik Przybysz on Tue May 30 2017
## Committer base changes:
- Currently 55 committers.
- No new committers added in the last 3 months
- Last committer addition was Tom De Wolf at Wed May 03 2017
## Releases:
- Aries Blueprint Core (blueprint-core) 1.8.3 on 2017-10-19
- Aries SPI Fly (spi-fly) 1.0.10 on 2017-11-28
- Aries JMX Core (jmx-core) 1.1.8 on 2018-01-09
- Aries JMX Core via Whiteboards (jmx-core-whiteboard) 1.1.6 on 2018-01-09
- Aries JMX Blueprint API (jmx-blueprint-api) 1.2.0 on 2018-01-09
- Aries JMX Blueprint Core (jmx-blueprint-core) 1.2.0 on 2018-01-09
- Aries Whiteboard support for JMX DynamicMBean services (jmx-whiteboard)
1.2.0 on 2018-01-09
## JIRA activity:
- 20 JIRA tickets created in the last 3 months
- 7 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment G: Report from the Apache Arrow Project [Jacques Nadeau]
## Description:
Apache Arrow is a cross-language development platform for in-memory data. It
specifies a standardized language-independent columnar memory format for flat
and hierarchical data, organized for efficient analytic operations on modern
hardware. It also provides computational libraries and zero-copy streaming
messaging and interprocess communication. Languages currently supported include
C, C++, Java, JavaScript, Python, and Ruby.
## Issues:
There are no issues requiring board attention at this time
## Activity:
- Steady development activity from previous quarter and continued growth in
contributor base
- Added 5 new committers
- First JavaScript-only release (0.2.0) made on December 1
## Health report:
Project is very healthy with a growing developer and user community.
## PMC changes:
- Currently 20 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Kouhei Sutou on Fri Sep 15 2017
## Committer base changes:
- Currently 28 committers.
- New commmitters:
- Phillip Cloud was added as a committer on Tue Oct 03 2017
- Bryan Cutler was added as a committer on Wed Oct 04 2017
- Li Jin was added as a committer on Fri Oct 06 2017
- Paul Taylor was added as a committer on Fri Oct 06 2017
- Siddharth Teotia was added as a committer on Wed Oct 04 2017
## Releases:
- 0.8.0 was released on Sat Dec 16 2017
- JS-0.2.0 was released on Fri Dec 01 2017
## JIRA activity:
- 323 JIRA tickets created in the last 3 months
- 300 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment H: Report from the Apache AsterixDB Project [Till Westmann]
Description:
Apache AsterixDB is a scalable big data management system (BDMS) that provides
storage, management, and query capabilities for large collections of
semi-structured data.
Activity:
- Development and discussions are active, the community is healthy and
engaged.
- The 4th non-incubating release is out.
- Received a significant contribution of a new web console for AsterixDB.
Issues:
- There are no issues that require the board's attention at this time.
PMC/Committership changes:
- The last committer added was Dmitry Lychagin on 2017-06-22.
- The last PMC member added was Michael Blow on 2016-03-28.
Releases:
- Apache AsterixDB 0.9.3 was released on 2018-01-15
- Apache Hyracks 0.3.3 was released on 2018-01-15
-----------------------------------------
Attachment I: Report from the Apache Attic Project [Jan Iversen]
## Description:
The Attic is where projects slumber when their communities fade away. Wink moved to the Attic in the last quarter.
## Issues:
No issues
## Activity:
None
## PMC changes:
- Currently 21 PMC members.
- Jan Iversen was added to the PMC on Wed Mar 15 2017
## Committer base changes:
- Currently 25 committers.
- No new committers added in the last 3 months
- Last committer addition was Jan Iversen at Thu Mar 16 2017
## Releases:
- No release can be made in attic
-----------------------------------------
Attachment J: Report from the Apache Avro Project [Ryan Blue]
## Description:
- Avro is a cross-language data serialization system.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- Thiruvalluvan M. G. is replacing Ryan Blue as project chair.
- 1.8.2 released 13 May 2017.
## Health report:
- No significant changes from the last report.
## PMC changes:
- Currently 18 PMC members.
- No new PMC members added in the last 3 months.
- Last PMC addition was Suraj Acharya on Wed Apr 12 2017
## Committer base changes:
- Currently 25 committers.
- New commmitters:
- Nándor Kollár was added as a committer on Sat Nov 04 2017
## Releases:
- Last release was 1.8.2 on 13 May 2017
## Mailing list activity:
- dev@avro.apache.org:
- 296 subscribers (down -7 in the last 3 months):
- 394 emails sent to list (591 in previous quarter)
- user@avro.apache.org:
- 655 subscribers (down -15 in the last 3 months):
- 53 emails sent to list (44 in previous quarter)
## JIRA activity:
- 33 JIRA tickets created in the last 3 months
- 17 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment K: Report from the Apache Axis Project [Robert Lazarski]
# Apache Axis2 Board Report, January 2018
## Description
The Apache Axis project is responsible for the creation and maintenance of
software related to the Axis Web Services frameworks and subsidiary
components (both Java and C).
## Issues
There are no issues requiring board attention at this time.
## Activity
- Axis2 1.7.7 (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 continue to receive patches from various new users/contributors.
## PMC/Committer changes:
- Currently 63 PMC/Committers members.
- No new committers were added in the last 30 days. Last committer was added in
December 2017.
## Releases:
- Axis 2/Java 1.7.7 was released on November 22, 2017.
- Axis 2/C 1.6 was released in April 2009.
## JIRA Activity
- 3 JIRA tickets created in the last month.
- 18 JIRA tickets closed/resolved in the last month.
-----------------------------------------
Attachment L: Report from the Apache Calcite Project [Michael Mior]
## Description:
Apache Calcite is a highly customizable framework for parsing and planning
queries on data in a wide variety of formats. It allows database-like access,
and in particular a SQL interface and advanced query optimization, for data
not residing in a traditional database.
Avatica is a sub-project within Calcite, and provides a framework for building
local and remote JDBC and ODBC database drivers. Avatica has an independent
release schedule, and since April 2017, it has its own independent repository.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
Development and mailing list activity is steady for both Calcite and its
Avatica sub-project.
Calcite 1.15.0, was released in December with 50 issues are fixed by 22
contributors. Some features of note are a "server" module with DDL support;
dynamic parameters in the LIMIT and OFFSET and clauses; refactoring the JDBC
adapter to make it easier to plug in a new SQL dialect; and a data profiling
algorithm, that efficiently analyzes large data sets with many columns,
estimating the number of distinct values in columns and groups of columns.
Our community continued growing this quarter, as two new committers
(Christian Beikov and Vova Vysotskyi) were added to the project.
Finally, members of the Calcite PMC along with external collaborators
submitted a paper to the industrial track of SIGMOD 2018.
## Health report:
Activity levels on mailing lists, git and JIRA are normal for both Calcite and
Avatica.
## PMC changes:
- Currently 16 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Michael Mior on Mon Apr 03 2017
## Committer base changes:
- Currently 28 committers.
- New commmitters:
- Christian Beikov was added as a committer on Thu Oct 12 2017
- Vova Vysotskyi was added as a committer on Thu Dec 21 2017
## Releases:
- 1.14.0 was released on Sun Oct 01 2017
- 1.15.0 was released on Sun Dec 10 2017
- Avatica 1.10.0 was released on Tue May 30 2017
## JIRA activity:
- 121 JIRA tickets created in the last 3 months
- 89 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment M: Report from the Apache CarbonData Project [Liang Chen]
## Description:
- The Apache CarbonData is an indexed columnar store file format for fast
analytics on Big Data platforms (including Apache Hadoop, Apache Spark,
among others) to help speed up queries an order of magnitude faster over
petabytes of data, with the aim of using a unified file format to satisfy
all kinds of data analysis cases.
## Board comment in the last month report:
- rb: I'm fascinated by the statement that you helped 5 companies deploy
CarbonData. Was this via the mailing lists, or was this more direct
involvement?
- Reply: All these discussions and help actions only be supported via
mailing list
## Issues:
- There are no new issues requiring board attention at this time.
## Activity:
- Community is pretty active, contributors who are from 20+ different
organizations , and now the number of contributors is more than 100+, we are
receiving around 100-200 pull requests per month.
- A new release 1.3.0 is preparing rc1, plan to finish this release in
January.
- In 1.3.0, there are many good features(supports spark 2.2.x integration,
streaming ingestion, partition optimization, pre-aggregation etc.),
especially "pre-agg feature" can improve performance 10+ times for some
"group by scenarios".
- We organized 1 time meetup in the past 3 months(19th Nov), the meetup focus
on helping users to use CarbonData(How to use index feature, dictionary
feature, update and delete feature, etc.)
- Liang attended Chinese yearly open source conference in Nov, shared
CarbonData story in Apache.
## Health Report:
- The project is healthy, community keep active in all the various
categories(dev mailing list, JIRAs, and pull requests).
- We added 2 new PMC and 1 committer in Jan,2018, because all of them did very
good contributions in 1.3.0 version.
## Releases:
- Apache CarbonData 1.1.1 released on 2017-07-10
- Apache CarbonData 1.2.0 released on 2017-09-28
## PMC changes:
- Kumar Vishal was added to the PMC on Tue Jan 09 2018
- David Cai was added to the PMC on Tue Jan 09 2018
- Currently 11 PMC members
## Committer base changes:
Currently 16 committers, 1 new committers added in the past quarter:
- Kunal Kapoor was added as a committer on Sat Jan 06 2018
- Currently 16 committers
## Mailing list activity:
- Mailing list activity stays at a high level
- dev@carbondata.apache.org:
- 170 subscribers (up 4 in the last 3 months):
- 264 emails sent to list (244 in previous quarter)
## JIRA activity:
- 459 JIRA tickets created in the last 3 months
- 320 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment N: Report from the Apache Celix Project [Pepijn Noltes]
## Description:
- Dynamic service framework for C and C++.
## Issues:
- It has been a while since the last Celix release. Primarily this was
because we wanted the PubSub implementation as part of the release and
there where still some issues in the PubSub implementation. These
issues should now be solved, so we should be able to create a release
in the coming weeks.
## Activity:
- Some fixes where done for the PubSub implementation, this was
holding the back the next release.
- The specified config attributes (config.properties) for Celix
containers are now also added in the generated main file. This is a
step in decoupling Celix containers from specific work dir
dependencies.
- Support for adding additional services to a running dependency
manager component is added.
## Health report:
- The current activity is a bit on the normal considering the size of
the community.
## PMC changes:
- Currently 7 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Alexander Broekhuis on Wed Jul 16 2014
## Committer base changes:
- Currently 10 committers.
- No new committers added in the last 3 months
- Last committer addition was Roy Lenferink at Thu Feb 09 2017
## Releases:
- Last release was 2.0.0 on Wed Oct 26 2016
## Mailing list activity:
- dev@celix.apache.org:
- 59 subscribers (down -2 in the last 3 months):
- 22 emails sent to list (9 in previous quarter)
## JIRA activity:
- 7 JIRA tickets created in the last 3 months
- 10 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment O: Report from the Apache Chukwa Project [Eric Yang]
## Description:
- Chukwa is an open source data collection system for monitoring
large distributed systems.
## Issues:
- there are no issues requiring board attention at this time.
## Activity:
- Minor security bug fixes contributed by community.
## Health report:
- Chukwa project has little development happening at this time. There is
planned work for more development after Hadoop 3 release to include docker
services. This will require new work to monitor Docker services running in
Hadoop.
## PMC changes:
- Currently 12 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Alan Cabrera on Tue Oct 15 2013
## Committer base changes:
- Currently 16 committers.
- No new committers added in the last 3 months
- Last committer addition was Sreepathi Prasanna at Mon Mar 16 2015
## Releases:
- Last release was 0.8.0 on Fri Jul 15 2016
## Mailing list activity:
- dev@chukwa.apache.org:
- 88 subscribers (down -1 in the last 3 months):
- 3 emails sent to list (10 in previous quarter)
- user@chukwa.apache.org:
- 156 subscribers (up 0 in the last 3 months):
- 0 emails sent to list (0 in previous quarter)
## JIRA activity:
- 0 JIRA tickets created in the last 3 months
- 1 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment P: 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:
- The big push this quarter was to upgrade the Hive dependencies
for Crunch in order to add a new HCatalog module for reading and
writing data to the Hive metastore. This was one of the major
upgrades to the project that we wanted to get done before the 1.0
release, and we're working on getting the HBase version upgrades
and fixes into the mainline of the codebase now.
## Health report:
- Acting on the feedback we received after our last report, the PMC
recently voted to add the primary developer of the Hive/HCatalog
functionality as a new committer on the project, and are reaching
out to him now to kick off the process with the ASF. We're optimistic
about adding another new committer for the HBase work in the next
quarter.
## 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:
- 4 JIRA tickets created in the last 3 months
- 5 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment Q: Report from the Apache CXF Project [Daniel Kulp]
## Description: Apache CXF is an open source services framework. CXF helps you
build and develop services using frontend programming APIs, like JAX-WS and
JAX-RS. These services can speak a variety of protocols such as SOAP,
XML/HTTP, RESTful HTTP, or CORBA and work over a variety of transports such as
HTTP, JMS or JBI.
There are also two sub-projects that leverage CXF:
Fediz - Fediz helps you to secure your web applications via the standard
WS-Federation Passive Requestor Profile.
DOSGi - is the reference implementation of the Distribution Provider component
of the OSGi Remote Services Specification
## Issues: There are no issues requiring board attention at this time
## Activity: Activity this quarter centered around a few efforts:
There were three primary development activities this quarter:
1) Patch releases - primarily to fix bugs found in 3.2.0 we tried to get
the first patch release out so folks don't need to depend on a .0 release.
These patches also fixed a now public CVE (CVE-2017-12624)
2) Fediz - Fediz was updated to use the latest CXF releases as well as
to fix a now public CVE (CVE-2017-12631)
3) New "microprofile" REST client - a discussion was started to
implement the MicroProfile type save rest client specification
(https://github.com/eclipse/microprofile-rest-client)
within CXF. A new module was created for it and a lot of
work has started toward achieving that goal.
## PMC changes:
- Currently 25 PMC members.
- Dennis Kieselhorst was added to the PMC on Thu Nov 02 2017
## Committer base changes:
- Currently 43 committers.
- New commmitters:
- Alexey Markevich was added as a committer on Fri Dec 29 2017
- Adrian Gonzalez was added as a committer on Tue Oct 31 2017
- John D. Ament was added as a committer on Tue Oct 24 2017
## Releases:
- 3.1.14 was released on Sun Nov 05 2017
- 3.2.1 was released on Sun Nov 05 2017
- Apache CXF 3.0.16 was released on Mon Nov 27 2017
- Apache CXF Fediz 1.3.3 was released on Tue Nov 28 2017
- Apache CXF Fediz 1.4.3 was released on Tue Nov 28 2017
-----------------------------------------
Attachment R: Report from the Apache DB Project [Bryan Pendleton]
Report from the Apache DB Project [Bryan Pendleton]
## Description:
The Apache DB TLP consists of the following subprojects:
o Derby : a relational database implemented entirely in Java.
o JDO : focused on building the API and the TCK for compatibility
testing of Java Data Object implementations providing data
persistence.
o Torque : an object-relational mapper for Java.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
Derby 10.14.1.0 was released on Oct 13, 2017.
During the fall, an audit revealed that some paperwork was missing from an
old Derby security vulnerability (CVE-2010-2232) in the MITRE CVE database.
The missing paperwork has now been supplied and the database is accurate.
Following a successful vote, the Derby community has decided to sunset
Java 8. Derby 10.14 was the last release to support Java 8; the community
is actively working on an upcoming release which will require Java 9.
## Health report:
In general, the software in the DB project is mature and reliable,
and isn't undergoing much change. Activity continues to be low, but
stable. Periodic releases occur, primarily containing bug fixes,
and are successfully voted on.
## PMC changes:
- Currently 43 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Matthew Adams on Sun Jan 19 2014
## Committer base changes:
- Currently 44 committers.
- No new committers added in the last 3 months
- Last committer addition was Brett Bergquist at Tue Aug 30 2016
## Releases:
- Derby 10.14.1.0 was released on Oct 13, 2017.
-----------------------------------------
Attachment S: Report from the Apache Directory Project [Stefan Seelmann]
## Description:
The Apache Directory TLP consists of the following sub-projects:
- ApacheDS: An extensible and embeddable directory server entirely
written in Java, which has been certified LDAPv3
compatible by the Open Group. Besides LDAP it supports
Kerberos 5 and the Change Password Protocol.
- LDAP API: An ongoing effort to provide an enhanced LDAP API, as a
replacement for JNDI and the existing LDAP API (jLdap
and Mozilla LDAP API). This is a "schema aware" API
with some convenient ways to access all types of LDAP
servers.
- Studio: A complete directory tooling platform intended to be
used with any LDAP server however it is particularly
designed for use with ApacheDS. It is an Eclipse RCP
application, composed of several Eclipse (OSGi) plugins.
- Fortress: A standards-based access management system that provides
role-based access control, delegated administration and
password policy services with an LDAP backend.
- Kerby: An implementation of Kerberos v5 protocol and contains
various tools to access and manage kerberos principals
and keytabs. It provides a rich, intuitive and
interoperable implementation, library, KDC and various
facilities that integrates PKI, OTP and token (OAuth2)
as desired in modern environments such as cloud, Hadoop
and mobile.
- Mavibot: An embeddable key-value database library with MVCC
(Multi Version Concurrency Control) support.
## Issues:
- there are no issues requiring board attention at this time"
## Activity:
General:
- Finished migration for most projects from SVN to Git/GitBox
- Ongoing search to strengthen the committer pool and the PMC
Per sub-project:
- ApacheDS: low activity
- LDAP API: low activity
- Studio: low activity
- Fortress: low activity
- Kerby: good activity: Relase of version 1.1.0. Started integration
on new "Hadoop Authentication Service" (DIRKRB-671).
- Mavibot: good activity
## Health report:
Overall develomment activity (commits, development related mails,
resolved issues, releases) was lower than last quarter.
The PMC feels the project is still healthy.
## PMC changes:
- Currently 18 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Chris Pike on Wed Nov 23 2016
## Committer base changes:
- Currently 57 committers.
- No new committers added in the last 3 months
- Last committer addition was Wei Zhou at Fri Sep 29 2017
## Releases:
- Apache Kerby 1.1.0 was released on Mon Nov 27 2017
## Mailing list activity:
- Same activiy level then previous quarter
## JIRA activity:
- 43 JIRA tickets created in the last 3 months
- 41 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment T: Report from the Apache Fineract Project [Myrle Krantz]
## Description
Apache Fineract (\’fīn-,ә-,rakt\) is an open source system for core banking as
a platform. Fineract provides a reliable, robust, and affordable solution for
entrepreneurs, financial institutions, and service providers to offer
financial services to the world’s 2 billion underbanked and unbanked.
## Issues
## Activity
We've added committers.
We've voted on and accepted Fineract CN (formerly mifos i/o) and imported the
code into gitbox repositories. We've made progress in deciding how to do
issue tracking, and release management on this code.
We announced the SQL-injection security vulnerability (CVE-2017-5663) which
was fixed in Apache Fineract 1.0.0.
The Mifos Initiative has involved us in Google Code In so we've had the
pleasure of making the acquaintance of many young, up-and-coming programmers
who are introducing themselves on our list. To date we've interacted with 245
students who are all working on a wide range of coding and non-coding
projects.
The Apache Fineract 1.1.0 release is soon to be ready for a vote. The
community has been doing extensive QA cycles. It will include a number of the
GSOC projects including the data import tool enhancements, two-factor
authentication, notifications framework, static analysis and more.
A vote to accept in a code donation from the Mifos Initiative of the Fineract
CN Mobile app developed by Apache Fineract 2017 GSOC intern, Rajan Maurya is
underway and should be complete before the January 17 board meeting.
Google Summer of Code 2018 applications are open now for mentoring
organizations. The Mifos Initiative plans to apply to mentor projects on both
Mifos X and Apache Fineract 1.0/CN which would be in addition to any
participation under Apache Software Foundation as an umbrella organization.
## Health report
We've made progress on our unmerged pull requests. Documenting the process
for merging and closing pull requests in the Fineract confluence seems to have
helped. At the time of our last board report, the oldest open pull request
was from March 2016. Currently, we've reduced the number of open pull requests
from 47 to 16. Unfortunately many had to be closed without merging. Those
that remain are still quite old.
We also were able to resolve several outstanding issues with respect to
committers for whom ICLAs or Apache ids were missing, so that there are no
longer any voted in committers who are not on the roster. Several of the
committers listed below in "committer base changes" were voted in and
announced significantly earlier.
## PMC changes
- Currently 13 PMC members.
- Avik Ganguly was added to the PMC on Sat Oct 14 2017
## Committer base changes
- Currently 22 committers.
- New commmitters:
- Avik Ganguly was added as a committer on Tue Oct 03 2017
- Awasum Yannick was added as a committer on Mon Nov 20 2017
- Ayuk Etta was added as a committer on Wed Nov 15 2017
- Mexina Daniel was added as a committer on Wed Nov 15 2017
- Nayan Ambali was added as a committer on Fri Nov 17 2017
- Nikhil Pawar was added as a committer on Wed Oct 04 2017
- Thynn Win was added as a committer on Tue Dec 12 2017
- Zayyad A. Said was added as a committer on Fri Nov 17 2017
## Releases
- Released version 1.0.0
https://dist.apache.org/repos/dist/release/fineract/1.0.0/ on June 1, 2017.
## Mailing list activity:
- Subscriber counts to dev and user have been slightly but steadily
increasing. The number of new subscribers who introduce themselves has seen
a significant uptick, but is mostly Google Code In students. Not all of
them will remain with the project.
- Email counts are not completely comparable with previous quarters because in
mid-September we rearranged what e-mails are sent to which lists. Those
changes may have also driven changes in subscriber count to the issues and
commits mailing lists. Hopefully, those changes will also make our dev list
more attractive for newcomers. This was also mentioned in our previous
report
- dev@fineract.apache.org:
- 199 subscribers (up 39 in the last 3 months):
- 659 emails sent to list (712 in previous quarter)
- issues@fineract.apache.org:
- 12 subscribers (up 0 in the last 3 months):
- 241 emails sent to list (204 in previous quarter)
- user@fineract.apache.org:
- 160 subscribers (up 17 in the last 3 months):
- 143 emails sent to list (106 in previous quarter)
## JIRA activity:
- Jira activity has been up slightly.
- 55 JIRA tickets created in the last 3 months
- 28 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment U: Report from the Apache Fluo Project [Keith Turner]
## Description:
- Apache Fluo is a distributed processing system built on Apache Accumulo.
Fluo users can easily setup workflows that execute cross node transactions
when data changes. These workflows enable users to continuously join new
data into large existing data sets with low latency while avoiding
reprocessing all data.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- Testing and fixing issues found in preparation for next release.
- Updated install docs to include new fluo-yarn and docker projects
- Rewrote asynchronous commit code to use new Java 8 Completable Futures
- Made many internal Caches with hard coded sizes configurable
- Improved Fluo scanner API
- Improved automatic formatting of Fluo code
- Code cleanup fixed all compiler warnings
- Added read locks to Fluo transactions
- Fluo talk was given at the Accumulo Summit
## Health report:
- Created 57 pull request and closed 59 [10/12/17,1/9/18]
- Created 32 issues and closed closed 29 [10/12/17,1/9/18]
- 60 commits from 4 committers and 8 contributors [10/12/17,1/9/18]
- 6 new contributors
## PMC changes:
- Currently 8 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Billie Rinaldi on Tue Jul 18 2017
## Committer base changes:
- Currently 9 committers.
- Kenneth Mcfarland was added as a committer on Thu Dec 07 2017
- Invited another committer at beginning of Dec but have not heard back.
## Releases:
- fluo-parent-3 was released on Sun Nov 26 2017
-----------------------------------------
Attachment V: Report from the Apache Geronimo Project [Alan Cabrera]
Apache Geronimo project is slowly moving from a full EE server activity to a
JavaEE/EE4J/Microprofile umbrella project and hosts EE utilities as well as
specification API and implementations.
## Issues:
- there are no issues requiring board attention at this time
- we need to put our spec releases in the dist area - habit was to not do it
somehow
## Activity:
- Website got some enhancement to show that the server is no more maintained
and will get live very soon - need some infra fixes we are on.
- Microprofile subprojects get natural activity due to the updates in the
related specifications. To cite two examples: Config and Safeguards are
very active at the moment.
- A security issues came and was handled - a bit slowly - with the server
retirement.
## Health report:
- The development activity is mainly due to the microprofile activity and
some updates of the JavaEE 8 API jars for Meecrowave/CXF release(s).
## PMC changes:
- Currently 43 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was John D. Ament on Thu Aug 24 2017
## Committer base changes:
- Currently 73 committers.
- No new committers added in the last 3 months
- Last committer addition was Jean-Louis Monteiro at Fri Jul 14 2017
## Releases:
- Last release was geronimo-jaxrs_2.1_spec on Dec 19 2017
## Mailing list activity:
- The dev activity is mainly due to the microprofile activity.
- dev@geronimo.apache.org:
- 335 subscribers (down -5 in the last 3 months):
- 88 emails sent to list (247 in previous quarter)
- geronimo-tck@geronimo.apache.org:
- 43 subscribers (up 0 in the last 3 months)
- scm@geronimo.apache.org:
- 95 subscribers (down -1 in the last 3 months):
- 47 emails sent to list (122 in previous quarter)
- tck-commits@geronimo.apache.org:
- 6 subscribers (up 0 in the last 3 months)
- user@geronimo.apache.org:
- 437 subscribers (down -7 in the last 3 months):
- 4 emails sent to list (3 in previous quarter)
## JIRA activity:
- 8 JIRA tickets created in the last 3 months
- 4 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment W: Report from the Apache Guacamole Project [Mike Jumper]
## Description:
- Apache Guacamole is a clientless remote desktop gateway which supports
standard protocols like VNC, RDP, and SSH. We call it "clientless" because
no plugins or client software are required. Once Guacamole is installed on
a server, all you need to access your desktops is a web browser.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- All tasks for 0.9.14 have been completed, and the first RC for 0.9.14 is
imminent.
- New website page documenting vulnerabilities fixed and the release in which
the vulnerabilities were fixed.
- Public announcement of CVE-2017-3158.
## Health report:
- The project is operating in a healthy manner. Development and community
involvement continue to be active.
## PMC changes:
- Currently 9 PMC members.
- Carl Harris was added to the PMC on Sun Nov 19 2017
## Committer base changes:
- Currently 10 committers.
- Carl Harris was added as a committer on Thu Nov 16 2017
## Releases:
- Last release was 0.9.13-incubating on Sat Jul 29 2017
## Mailing list activity:
- Mailing list activity on both the dev@ and user@ continues to be strong.
- The community continues to be mainly active on the user@ list.
- dev@guacamole.apache.org:
- 69 subscribers (up 0 in the last 3 months):
- 546 emails sent to list (422 in previous quarter)
- user@guacamole.apache.org:
- 282 subscribers (up 1 in the last 3 months):
- 637 emails sent to list (582 in previous quarter)
## JIRA activity:
- 71 JIRA tickets created in the last 3 months
- 59 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment X: Report from the Apache Hadoop Project [Christopher Douglas]
Apache Hadoop is a set of related tools and frameworks for creating and
managing distributed applications running on clusters of commodity computers.
Hadoop 3.0.0 is GA. This not only unlocks new features and development, it also
puts the project on stable footing to continue a steady cadence with less
backporting. We're not there yet, as we currently have four active release
branches to support existing users, but it is a significant milestone.
Several feature branches have merged, or are preparing to merge, for a 3.1.0
release in February.
RELEASES
3.0.0-beta1 was released 2017-10-02
2.8.2 was released 2017-10-23
2.9.0 was released 2017-11-16
2.8.3 was released 2017-12-12
3.0.0 was released 2017-12-12
2.7.5 was released 2017-12-13
COMMUNITY
(+ PMC Brahma Reddy Battula 2017-12-14)
(+ PMC Konstantinos Karanasos 2017-11-26)
(+ committer Billie Rinaldi 2017-10-26)
(+ committer Miklos Szegedi 2017-12-27)
(+ committer Sammi Chen 2017-10-15)
(+ committer Virajith Jalaparti 2017-12-29)
(+ committer Inigo Goiri 2017-10-19)
auth: 176 committers (including branch) and 91 PMC members
-----------------------------------------
Attachment Y: Report from the Apache HBase Project [Misty Stanley-Jones]
HBase is a distributed column-oriented database built on top of Hadoop Common
and Hadoop HDFS.
hbase-thirdparty is a set of internal artifacts used by the project to
mitigate the impact of our dependency choices on the wider ecosystem.
ISSUES FOR THE BOARD’S ATTENTION
None at this time.
RELEASES
HBase had three releases during this reporting period, including one alpha
release working toward 2.0.0.
- HBase 1.1.13 was released on Sun Dec 10 2017. This was the final release in
the 1.1 branch. Thanks to Nick Dimiduk for managing releases on this branch
for us.
- HBase 1.4.0 was released on Sun Dec 17 2017. This is the first release of
our new 1.4 code line, the latest in the 1.x series of minor releases. HBase
1.4.0 incorporates 660 bug fixes and improvements and several new features.
See the 1.4.0 release announcement in the archives of our dev list for more
details. We expect to make releases from this line on roughly a monthly
cadence.
- HBase 2.0.0-alpha-4 was released on Mon Nov 06 2017.
In addition, hbase-thirdparty had one release.
- hbase-thrirdparty-2.0.0 was released on Mon Dec 25 2017
ACTIVITY
Development toward a HBase 2.0.0 release is going well, with the fourth alpha
released in November and the first beta around the corner. A release candidate
went up for vote for that beta, but the vote did not pass due to stability
concerns, and we are continuing work to stabilize before the first beta.
Thanks to Michael Stack for driving the 2.0.0 effort. Work toward the Beta has
continued to engage lots of discussions on the dev@ mailing list and to
increase interest in the project overall.
Work on the HBase 1.4.x line is going well, and the HBase 1.1.x line is now at
an end.
The HBase project has added five new committers during this reporting period,
with a total of 71 committers.
- Lars Francke was added as a committer on October 16.
- Rahul Gidwani and Jan Hentschel were added as committers on October 25.
- Zheng Hu was added as a committer on October 21.
- Yi Liang was added as a committer on December 20.
Thanks to PMC members, committers, and active community members for a
successful 2017 for the HBase project!
STATS
The dev@ mailing list saw a slight decrease in membership, but a marked
increase in activity. This was due to several substantial discussions about
project health, work on the upcoming 2.0.0 Beta, and discussion of new
features and design changes.
The user@ mailing list saw a slight decrease in membership and a small
decrease in the number of discussions. This is probably due to holidays.
The builds@ mailing list saw a decrease in traffic, due to significant work on
stabilizing build and test infrastructure over the past quarter.
71 committers 38 PMC members 755 JIRA tickets created 730 JIRA tickets
closed/resolved
-----------------------------------------
Attachment Z: Report from the Apache Helix Project [Kishore G]
## Description:
A cluster management framework for partitioned and replicated distributed
resources
## Issues:
- NO
## Activity:
- 10 pull requests merged in last 3 months.
- 26 commits in last 3 months.
## Health report:
- Helix 0.6.9 was released in Oct. 13. 2017.
- New major release 0.8 is in preparation, currently working on renewing all
documents. The release is expected to be out in Feb 2018.
- There is regular level of activities on commits, pull requests and
releases.
- The dev@ list traffic is healthy, user@ list traffic is decreasing.
- Many of current committers are not quite active in terms of daily
developments and discussions, need to look for potential new committers
from the community.
## PMC changes:
- Currently 18 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Junkai Xue on Mon Jul 03 2017
## Committer base changes:
- Currently 18 committers.
- No new committers added in the last 3 months
- Last committer addition was Junkai Xue at Mon Apr 03 2017
## Releases:
- 0.6.9 was released on Sat Oct 14 2017
## Mailing list activity:
- dev@helix.apache.org:
- 68 subscribers (up 2 in the last 3 months):
- 101 emails sent to list (84 in previous quarter)
- user@helix.apache.org:
- 98 subscribers (down -1 in the last 3 months):
- 21 emails sent to list (3 in previous quarter)
## JIRA activity:
- 1 JIRA tickets created in the last 3 months
- 1 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AA: Report from the Apache Impala Project [Jim Apple]
## Description:
Impala is a high-performance distributed SQL engine.
## Issues:
There are no special issues the board should be aware of.
## Activity:
Notable efforts in December include work on decimal and floating point
correctness, test and build infrastructure refactoring, the addition of more
debugging and profiling information (and the removal of some less helpful
information), perfomance improvements for computing table statistics, support
for processors with AVX-512, a variety of fixes to runtime filters, and
kerberos handling improvements.
## Health report:
The project is healthy. December was a slower month than November, likely due
to two US holidays at the end of the month. There were 60 commits, 112 dev@
emails, 45 user@ emails, 66 tickets resolved, and 94 tickets opened.
## PMC and committer changes:
Greg Rahn was added as a committer on December 12. The most recent new PMC
member was added on 2017-09-27.
## Releases:
The release process for 2.11 is underway:
https://s.apache.org/impala-2.11-vote-results
-----------------------------------------
Attachment AB: Report from the Apache Incubator Project [John D. Ament]
Incubator PMC report for January 2018
The Apache Incubator is the entry path into the ASF for projects and codebases
wishing to become part of the Foundation's efforts.
There are currently 53 podlings in the inubator. We added two new podlings in
December, and executed four podling releases. Two new PMC members joined, in
support of mentoring podlings.
* Community
New IPMC members:
- Stefan Bodewig
- Carl Johan Erik Edstrom
People who left the IPMC:
* New Podlings
- PLC4X
- SkyWalking
* Podlings that failed to report, expected next month
- Airflow - Report received, but not signed off.
- Livy - Low on list activity.
- Milagro - Low on list activity.
- Myriad - Low on list activity.
- Spot - Low on list activity.
- Wave - Retirement vote under way.
* Graduations
The board has motions for the following:
- None
* Releases
The following releases entered distribution during the month of December:
- 2017-12-03 Apache MXNet 1.0.0
- 2017-12-13 Apache BatchEE 0.5
- 2017-12-14 Apache Edgent 1.2.0
- 2017-12-17 Apache Pulsar 1.21.0
----------------------------------------------------------------------
Table of Contents
Amaterasu
Annotator
BatchEE
Crail
DataFu
FreeMarker
Gobblin
Gossip
HAWQ
HTrace
MXNet
NetBeans
ODF Toolkit
PageSpeed
PLC4X
Pony Mail
Rya
SDAP
SensSoft
ServiceComb
SkyWalking
Traffic Control
Weex
----------------------------------------------------------------------
--------------------
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?
* A planning meeting for the next version was held online and most tasks
have been assigned to contributors
* Tow new contributors have started setting up their dev environment and are
getting support from the community
How has the project developed since the last report?
* YARN support is almost completed and a PR is planned to be issued within
the next couple of weeks
* The Amaterasu cli tools for version 0.2.0-incubating is awaiting YARN
support to be completed for integration
* the above tasks are the last two outstanding issues before releasing
version 0.2.0 and the community is getting ready for its first release in
the incubator
Date of last release:
N/A
When were the last committers or PMC members elected?
N/A
How would you assess the podling's maturity?
[ ] Initial setup
[X] Working towards first release
[ ] Community building
[ ] Nearing graduation
[ ] Other:
Signed-off-by:
[X](amaterasu) Jean-Baptiste Onofré
Comments:
[X](amaterasu) Olivier Lamy
Comments:
[X](amaterasu) Davor Bonaci
Comments: visible progress in the last month
IPMC/Shepherd notes:
--------------------
Annotator
Annotator provides annotation enabling code for browsers, servers, and humans.
Annotator has been incubating since 2016-08-30.
Three most important issues to address in the move towards graduation:
1. figuring out how to get our newest committer setup with all the things 2.
determining how to publish to NPM during development and after releases 3.
engaging with other "promised" initial committers who have been AWOL
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?
None.
How has the community developed since the last report?
There is growing interest in our JavaScript libraries being available via
[[http://npmjs.com/|NPM]] and we're sorting through how best to manage that
among the committers. We are also working on ''finally'' getting our newest
committer (who was +1'd back in late October) setup with an ASF account,
GitHub permissions, etc.
How has the project developed since the last report?
We have a basis API roughed in and the key dependency code will be added to
our repository once we have our NPM situation sorted.
How would you assess the podling's maturity? Please feel free to add your own
commentary.
[ ] Initial setup
[X] Working towards first release
[X] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
XXXX-XX-XX
When were the last committers or PPMC members elected?
We elected a new committer on 2017-10-30, but have yet to sort out how to get
him properly added to the project.
Signed-off-by:
[ ](annotator) Nick Kew
Comments:
[ ](annotator) Brian McCallister
Comments:
[ ](annotator) Daniel Gruno
Comments:
[X](annotator) Jim Jagielski
Comments:
IPMC/Shepherd notes:
--------------------
BatchEE
BatchEE projects aims to provide a JBatch implementation (aka JSR352) and a
set of useful extensions for this specification.
BatchEE has been incubating since 2013-10-03.
Three most important issues to address in the move towards graduation:
None
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?
Community is stable. We still get feedback and have active people around.
How has the project developed since the last report?
We got some bugfixes.
How would you assess the podling's maturity? Please feel free to add your own
commentary.
[ ] Initial setup
[ ] Working towards first release
[ ] Community building
[X] Nearing graduation
[ ] Other:
Date of last release:
2017-12-01 batchee-0.5-incubating
When were the last committers or PPMC members elected?
2015-12-01 Reinhard Sandtner
Signed-off-by:
[ ](batchee) Jean-Baptiste Onofré
Comments:
[ ](batchee) Olivier Lamy
Comments:
[X](batchee) Mark Struberg
Comments:
--------------------
Crail
Crail is a storage platform for sharing performance critical data in
distributed data processing jobs at very high speed.
Crail has been incubating since 2017-11-01.
Three most important issues to address in the move towards graduation:
1. 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?
* Got contacted by a few individuals and companies trying Crail for their
internal use. Not much more activities since last month, presumably due to
holidays.
How has the project developed since the last report?
* Working on project website
* Working on Crail code renaming for code landing at Apache
* Incubator status page updates
* Apache ICLA signed by almost all contributors (7 of 9)
* Submitted abstract on Crail project for 2018 DataWorks Summit in Berlin
How would you assess the podling's maturity?
[X] Initial setup
[ ] Working towards first release
[ ] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release: N/A
When were the last committers or PPMC members elected? 2017-11-01 (entering
incubation)
Signed-off-by:
[x](crail) Julian Hyde
Comments: It took a while to get ICLAs signed and
accounts created (thanks Luciano for your help) but the project is getting
through the red tape and real work is starting to surface on the dev list
and in JIRA.
[x](crail) Luciano Resende
Comments:
[ ](crail) Raphael Bircher
Comments:
IPMC/Shepherd notes:
--------------------
DataFu
DataFu provides a collection of Hadoop MapReduce jobs and functions in higher
level languages based on it to perform data analysis. It provides functions
for common statistics tasks (e.g. quantiles, sampling), PageRank, stream
sessionization, and set and bag operations. DataFu also provides Hadoop jobs
for incremental data processing in MapReduce.
DataFu has been incubating since 2014-01-05.
Three most important issues to address in the move towards graduation:
1. Address IPMC feedback raised during graduation discussion 2. Positive
IPMC recommendation vote for graduation 3. Continue releases
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?
None
How has the community developed since the last report?
One new contributor (Yuval Allweil)
How has the project developed since the last report?
Upgraded Guava and Gradle versions. Addressed many website issues raised in
graduation discussion. Whimsy report now mostly green. Rat task
automatically run as part of build. New UDFs for diffing tuples and
computing hashes.
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-03-10
When were the last committers or PPMC members elected?
July 2016 (Eyal Allweil)
Signed-off-by:
[ ](datafu) Ashutosh Chauhan
Comments:
[X](datafu) Roman Shaposhnik
Comments: In my view the podling is ready to
graduate at this point.
[ ](datafu) Ted Dunning
Comments:
IPMC/Shepherd notes:
--------------------
FreeMarker
FreeMarker is a template engine, i.e. a generic tool to generate text output
based on templates. FreeMarker is implemented in Java as a class library for
programmers.
FreeMarker has been incubating since 2015-07-01.
Three most important issues to address in the move towards graduation:
We have a large user base but a rather small group of committers. This was
actually expected, given the maturity (and topic) of the project. While the
FreeMarker 3 branch, which was started 11 month ago, will be much more
appealing for contributors, development and growth due to that will
certainly take a long time. In other respects the project is mature and
ready for graduation.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?
We are eager to graduate but we're afraid that the number of active
contributors will prevent that in the foreseeable future. But remaining in
the incubator for several years is a growing problem as well, so at this
point we will attempt graduation.
How has the community developed since the last report?
We have two new PPMC members, Jacques Le Roux and Woonsan Ko.
How has the project developed since the last report?
There was further discussion about graduation, and we will very soon have a
graduation vote on the podling list. We have done some preparations, like we
have switched from freemarker.org to freemarker.apache.org as our official
domain, created the DOAP file, adjusted home page content to align better
with the recommendations.
We have also made a new release (2.3.27-incubating).
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-11-03
When were the last committers or PPMC members elected?
2017-11-13 Jacques Le Roux (PPMC) 2017-11-09 Woonsan Ko (PPMC)
Signed-off-by:
[X](freemarker) Jacopo Cappellato
Comments:
[ ](freemarker) Jean-Frederic Clere
Comments:
[X](freemarker) David E. Jones
Comments:
[X](freemarker) Ralph Goers
Comments:
[X](freemarker) Sergio Fernández
Comments: I feel that the podling is ready
for graduation.
IPMC/Shepherd notes:
--------------------
Gobblin
Gobblin is a distributed data integration framework that simplifies common
aspects of big data integration such as data ingestion, replication,
organization and lifecycle management for both streaming and batch data
ecosystems.
Gobblin has been incubating since 2017-02-23.
Three most important issues to address in the move towards graduation:
1. Make frequent releases
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?
None
How has the community developed since the last report?
* Gobblin has seen an exciting growth on the community front. It has grown
into a diverse self-sustained community, where non-committer members are
often seen helping out each other on mailing lists and Gitter IRC (on most
days more than the committers). Many contributors have also stepped up and
contributed with important features and taken up ownership of critical
components.
* 70% of commits have been from non-committer contributors.
* Email stats since last report: user@gobblin.incubator.apache.org : 92
dev@gobblin.incubator.apache.org : 671
* Heavy activity on Gitter IRC channel (while the community uses Gitter IRC,
it also does self policing and consciously moves any discussion-thread
beyond casual chatter to the mailing lists)
* There have been 148 Commits since last report: git log --format='%ci' | grep
-cE '(2017-0(9))|(2017-1(0|1|2)|(2018-0(1)))'
* 103 ie. 70% of those commits were by non-committers: git log --format='%ae
%ci' | grep -E '(2017-0(9))|(2017-1(0|1|2)|(2018-0(1)))' | cut -d ' ' -f 1 |
sort | uniq -c | sort -n
* Recurring video conference based meetup has been happening every month with
healthy attendance.
* Gobblin was presented and well received in various conferences eg. Strata
etc.
* More companies have adopted Gobblin, and different members of PPMC have
received positive feedback and interest.
How has the project developed since the last report?
* Several new powerful features have been added to Gobblin that have enhanced
Gobblin to be more valuable in Stream processing as it is in batch data
world.
* Gobblin interestingly has started to evolve into an ecosystem rather than a
singular platform with addition of major sub-systems such as
Gobblin-as-a-Service (PaaS for Gobblin as well as non-Gobblin systems),
Global Throttling (can be used with any distributed system) and existing
Gobblin metrics.
* Documentation and stability has improved across the board.
* Release v0.12.0 is being voted on right now.
* The Apache way has become the normal way of doing things.
How would you assess the podling's maturity?
Gobblin has made good progress on the Community front and overall as a
project. However, before calling it nearing graduation, we will like to make
atleast couple of releases.
[ ] Initial setup
[X] Working towards first release
[X] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
v0.12.0 is being voted on right now.
When were the last committers or PPMC members elected?
Joel Baranick in December, 2017.
(We have a few more strong contributors that we are looking to vote in soon)
Signed-off-by:
[ ](gobblin) Jean-Baptiste Onofré
Comments:
[X](gobblin) Olivier Lamy
Comments:
[X](gobblin) Jim Jagielski
Comments:
--------------------
Gossip
Gossip is an implementation of the Gossip Protocol.
Gossip has been incubating since 2016-04-28.
Three most important issues to address in the move towards graduation:
1. Continue making releases 2. Grow community by getting more active
committers
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 a few code additions that are in the review process
How has the project developed since the last report?
Activity has slowed since the last report.
How would you assess the podling's maturity?
We need more active committers to become more mature. Please feel free to add
your own commentary.
The GSOC period had several spurts of activity. We need to begin creating more
tickets that new committers can get involved in and find more people to do
diligent code reviews.
[ ] Initial setup
[ ] Working towards first release
[X] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
2017-03-01
When were the last committers or PPMC members elected?
Feb 2017
Signed-off-by:
[X](gossip) P. Taylor Goetz
Comments: Activity is indeed slow. I'll work
with the community to brainstorm ways to increase interest.
[X](gossip) Josh Elser
Comments: Activity has definitely tapered off over
the last quarter. Not sure if a short-term lull or a sign that all activity
will fall off soon.
[ ](gossip) Drew Farris
Comments:
--------------------
HAWQ
HAWQ is an advanced enterprise SQL on Hadoop analytic engine built around a
robust and high-performance massively-parallel processing (MPP) SQL framework
evolved from Pivotal Greenplum Database.
HAWQ has been incubating since 2015-09-04.
Three most important issues to address in the move towards graduation:
1. Continue to improve the project's release cadence. To this end we plan on
expanding automation services to support increased developer participation.
(HAWQ-127) 2. Licenses: Check Apache HAWQ mandatory libraries to match LC20,
LC30 license criteria. (HAWQ-1512)
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?
Nothing urgent at this time.
How has the community developed since the last report?
1. Conference Talks (2):
* The nature of cloud database. The 7th Data Technology Carnival (Speaker:
Lei Chang, Nov 17, 2017)
* New Data Warehouse: Apache HAWQ. 2017 Global Internet Technology Conference
(Speaker: Lei Chang, Nov 24, 2017)
2. Active contributions from approximately 20 different community contributors
since the last report.
3. Three committer candidates passed the voting process:
1) Amy BAI 2) ChunLing WANG 3) Hongxu MA
How has the project developed since the last report?
1. The scope of 2.3 release is finalized, and is under development
1) New Feature: HAWQ Ranger supports RPS HA. (Done) 2) New Feature: HAWQ
Ranger supports Kerberos authentication. (Done) 3) New Feature: HAWQ Core
supports plugable external storage framework. (Almost Done HAWQ-786) 4) New
Feature: HAWQ Core supports HDFS TDE (Transparent Data Encryption) through
libHdfs3. (Done, HAWQ-1193) 5) Licenses: Fix PXF license files located in
PXF jar files. (Done HAWQ-1496) 6) Licenses: Check Apache HAWQ mandatory
libraries to match LC20, LC30 license criteria. (Not started HAWQ-1512) 7)
Build: Release build project (On going HAWQ-127) 8) Bug fixes. (On going)
Project page link:
https://cwiki.apache.org/confluence/display/HAWQ/Apache+HAWQ+2.3.0.0-incubating+Release
2. The community discussed the future of PXF with the addition of the
pluggable storage feature: Pluggable storage formats and files systems vs. PXF
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-12, Apache HAWQ 2.2.0.0
When were the last committers or PPMC members elected?
1) Amy BAI: Nov 1, 2017 2) ChunLing WANG: Nov 1, 2017 3) Hongxu MA: Nov 4,
2017
Signed-off-by:
[X](hawq) Alan Gates
Comments:
[ ](hawq) Konstantin Boudnik
Comments:
[ ](hawq) Justin Erenkrantz
Comments:
[ ](hawq) Thejas Nair
Comments:
[X](hawq) Roman Shaposhnik
Comments:
--------------------
HTrace
HTrace is a tracing framework intended for use with distributed systems
written in java.
HTrace has been incubating since 2014-11-11.
Three most important issues to address in the move towards graduation:
1. Continue to grow the Apache HTrace community 2. Further engagement with
projects integrating Apache HTrace 3. Continue to develop and release stable
Apache HTrace incubating artifacts
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?
Several months of stagnation have raised repeated conversations about retiring
HTrace. If nothing materializes before the end of Q1 2018 HTrace will be
retired.
How has the community developed since the last report?
Mailing lists continue quiet (bar the above noted conversations).
How has the project developed since the last report?
No development.
How would you assess the podling's maturity? Please feel free to add your own
commentary.
[X] Initial setup
[X] Working towards first release
[x] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
2016-09-15
When were the last committers or PPMC members elected?
2016-10-03
Signed-off-by:
[ ](htrace) Jake Farrell
Comments:
[ ](htrace) Todd Lipcon
Comments:
[x](htrace) Lewis John Mcgibbney
Comments: HTrace is very quiet. There is
opportunity to continue work is we engage with projects already using
HTrace. If that does not happen, we should retire the podling.
[ ](htrace) Andrew Purtell
Comments:
[x](htrace) Billie Rinaldi
Comments:
[X](htrace) Michael Stack
Comments:
--------------------
MXNet
Apache MXNet is an open-source, scalable, distributed and high-performance
deep learning framework that allows you to define, train, and deploy deep
neural networks on a wide array of devices, from cloud infrastructure to
mobile devices. It is highly scalable, allowing for fast model training, and
supports a flexible programming model and multiple languages. Apache MXNet
allows you to mix symbolic and imperative programming flavors to maximize both
efficiency and productivity. Apache MXNet is built on a dynamic dependency
scheduler that automatically parallelizes both symbolic and imperative
operations on the fly. A graph optimization layer on top of that makes
symbolic execution fast and memory efficient. The Apache MXNet library is
portable and lightweight, and it scales to multiple GPUs and multiple
machines.
Apache MXNet has been incubating since 2017-01-23.
Three most important issues to address in the move towards graduation:
1. Establish a predictable release process consistent with Apache Way --
ONGOING. 2. Grow the community -- ONGOING. 3. Bring website up to Apache
standard -- ONGOING 4. Identify remaining ICLAs or SGAs that need signing --
ONGOING
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?
Request the Incubator PMC to add more mentors to the project, preferably
mentors employed with Open Source companies like Hortonworks that have prior
experience in handling multiple open source projects that were part of an
ecosystem.
How has the community developed since the last report?
a) Various Slack channels, dev@ mailing lists, and user discussion forums
(http://discuss.mxnet.io) are being used actively. The contributors have been
working on having all discussions on the public dev@ mailing list as much as
possible. If some discussions happen in private, they are eventually brought
out on dev@ with all perspectives well-represented. This is an ongoing
improvement process where the discussion will be put on the public dev@
mailing list so that the Apache MXNet community gets a fair chance in
influencing the final outcome/decision of the discussion.
b) O’Reilly published a series of blogs about MXNet, including ones with deep
matrix factorization using Apache MXNet:
https://www.oreilly.com/ideas/sentiment-analysis-with-apache-mxnet
https://www.oreilly.com/ideas/deep-matrix-factorization-using-apache-mxnet
https://www.oreilly.com/ideas/apache-mxnet-in-the-wolfram-language
c) A blog post published on 25-Oct about MXNet – an open source binary neural
network implementation based on MXNet:
https://aws.amazon.com/blogs/ai/research-spotlig ht-bmxnet-an-open-source-binary-neural-network-implementation-based-on-mxnet/
d) A blog post published on 01-Nov about the availability of Nvidia Volta GPU
support and Sparse Tensor support:
https://aws.amazon.com/blogs/ai/a pache-mxnet-release-adds-support-for-new-nvidia-volta-gpus-and-sparse-tensor/
e) A new blog post published on 08-Nov showing MXNet 0.12 extends Gluon
Functionality:
https://aws.amazon.com/blogs/ai/apache-mxn et-version-0-12-extends-gluon-functionality-to-support-cutting-edge-research/
f) A blog post published on 08-Nov introducing Model Server for MXNet:
https://aws.amazon.com/blogs/ai/introducing-model-server-for-apache-mxnet/
g) A blog post published on 7-Nov demonstrating performance and scalability
of MXNet:
h ttps://techburst.io/mxnet-the-real-world-deep-learning-framework-2690e56ef81f
h) Members of the community have conducted open meetups to share information
on Apache MXNet: https://www.meetup.com/Apache-MXNet-learning-group/
i) Talks on Apache MXNet have been held in various universities and
conferences across the world including US, China, etc.:
https://www.youtube.com/watch?v=me1qOzSg8MU
https://www.youtube.com/watch?v=9IrvDHRQaaA
https://www.youtube.com/watch?v=4PbSZRYXa3o
https://www.youtube.com/watch?v=RRy-3VXA0nw
j) MXNet 1.0 was released on 04-Dec, 2017 with extensive support and help
from various community members and timely guidance from the Apache MXNet
Mentors.
How has the project developed since the last report?
a. The community released MXNet 1.0 that is production ready, simplifies deep
learning experience, and significantly improves performance with cutting-edge
features described here:
https://blogs.apache.org/mxnet/entry/milestone-v1-0-release-for
b. Documentation- Architecture guides, How To’s, Tutorials, and APIs continue
to be improved.
c. Support for Perl language bindings - contributed by Sergey Kolychev.
d. More advanced features (e.g. sparse tensor, advanced indexing, gradient
compression) and bug-fixes requested by the user community continue to be
added.
e. Community took complete end-to-end ownership of the continuous integration
process in order to enable reliable testing on a wide set of back ends (IoT
devices to GPU clusters).
How would you assess the podling's maturity?
Podling is still being established in Apache and no efforts being made in
increasing community - hence maturity == Low.
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-12-04
When were the last committers or PPMC members elected?
Sergey Kolychev was elected as a committer and PPMC member in October 2017 for
contributing the Perl language bindings. There is a plan to convert more
contributors into committers in early 2018.
Signed-off-by:
[X](mxnet) Sebastian Schelter
Comments:
[X](mxnet) Suneel Marthi
Comments: 1. All design decisions and project
roadmap seem to be done internally at team huddles and rarely the community
is ever involved in making any decisions. 2. There is no effort being made
to discuss roadmap or project issues on public mail lists. 3. All roadmap
planning seems to happen internally. 4. No effort is being made to build a
diverse community around the project. 5. Most committers (all of whom are
employed by a single vendor) appear to be resistant in moving to using
apache tools such as JIRA or adopting the Apache Way of growing diverse
community.
[X](mxnet) Henri Yandell
Comments:
[X](mxnet) Markus Weimer
Comments:
--------------------
NetBeans
NetBeans is a development environment, tooling platform and application
framework.
NetBeans has been incubating since 2016-10-01.
Three most important issues to address in the move towards graduation:
1. Donating remaining NetBeans code from Oracle to Apache. 2. Moving
netbeans.org to Apache. 3. Voting in new committers.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?
None.
How has the community developed since the last report?
- Voting process for new committers has been documented for the first time,
with mentors:
https://cwiki.apache.org/confluence/display/NETBEANS/Becoming+a+committer
- The start has been made in voting on new committers, though because the
process wasn't clear, we stopped and put together the document above
before continuing.
- All NetBeans.org mailing lists have been contacted and everyone has been
encouraged to move to Apache NetBeans mailing lists.
- NetBeans.org mailing lists scheduled to be deleted (they're backed up on
MarkMail) in the first week of 2018.
- A new Apache NetBeans announce mailing list has been created for those who
want high level occasional announcements only, not day to day NetBeans
e-mails.
- GitHub commits and notifications are now sent to new dedicated mailing
lists to reduce the noise in the Apache NetBeans dev mailing list.
- Standard footers have been added to mails with info about how to
unsubscribe and where to get all the mailing list info
(https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists).
- Currently over 550 on Apache NetBeans users mailing list and over 350 on
Apache NetBeans dev mailing lists
- Continual activity on mailing lists, new pull requests coming in and being
integrated, i.e., continually active community.
- Status report done live with several Apache NetBeans community members,
plus one Apache NetBeans mentor, at Devoxx Belgium December 2017:
https://www.youtube.com/watch?v=EkfX-W0tgNo
How has the project developed since the last report?
- Audit of 2nd code donation from Oracle is complete and is being processed
for donation, see end of this page:
https://cwiki.apache.org/confluence/display/NETBEANS/Apache+Transition
- Alpha of Apache NetBeans (incubating) has been released:
http s://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+9.0+Alpha
- Beta of Apache NetBeans (incubating) is nearing completion and ready for
vote threads:
htt ps://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+9.0+Beta
- A special aspect of Apache NetBeans (incubating) 9.0 Beta is the ability
for the user to need to specify whether they want to use the GPL-ed
nb-javac (which is an Apache requirement, i.e., the user needs to take the
onus of using binaries that are not compliant with Apache licensing
requirements) or javac directly from JDK 9 (which thus complies with
Apache licenses, though has less solid integration with NetBeans):
https: //cwiki.apache.org/confluence/display/NETBEANS/Java+Editor+Using+JDK+javac
- see also https://issues.apache.org/jira/browse/LEGAL-279
- Plan was to work on Beta release during last week of the year, but holiday
season got in the way.
- Repo created for cleaning up netbeans.org website, with content and
instructions included:
https://github.com/apache/incubator-netbeans-website-cleanup
- New Apache NetBeans wiki-export tool has been added to
apache-netbeans-incubator-tools:
https://github.com/apache/incubator-netbeans-tools
How would you assess the podling's maturity? Please feel free to add your own
commentary.
[X] Initial setup
[X] Working towards first release
[X] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
2017-11-29 Apache NetBeans (incubating) 9.0 Alpha [RC2]
When were the last committers or PPMC members elected?
Process for becoming a committer has been documented
(https://cwiki.apache.org/confluence/display/NETBEANS/Becoming+a+committer)
and can now be followed.
Signed-off-by:
[X](netbeans) Ate Douma
Comments:
[X](netbeans) Bertrand Delacretaz
Comments: +1 to Mark's comments
[ ](netbeans) Daniel Gruno
Comments:
[X](netbeans) Mark Struberg
Comments: The understanding of ASF 'mechanics'
grows steadily. Think they are on a good way!
--------------------
ODF Toolkit
Java modules that allow programmatic creation, scanning and manipulation of
OpenDocument Format (ISO/IEC 26300 == ODF) documents
ODF Toolkit has been incubating since 2011-08-01.
Three most important issues to address in the move towards graduation:
1. Fulfil the 1.0 version - (collaboration scheduled for end of March) 2.
Attract more developers 3. Have frequent releases
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?
None.
How has the community developed since the last report? No community
enhancements. Ongoing SVN to GIT transition, with read-only repository.
How has the project developed since the last report? Ongoing SVN to GIT
transition to improve visibility on GitHub and archive better mergeability for
feature branches. Svante Schubert continued sponsorship by German government's
prototypefund.org developing a new collaboration feature for the ODF Toolkit
till end of March.
Date of last release:
2017-04-10
When were the last committers or PMC members elected?
2017-08-02
Signed-off-by:
[ ](odftoolkit) Nick Burch
Comments:
[ ](odftoolkit) Yegor Kozlov
Comments:
[x](odftoolkit) Tom Barber
Comments:
--------------------
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?
- Continued healthy activity has shown on the x-pagespeed-discuss groups and
github issue system.
- There have been limited contributions to pagespeed repositories from outside
of the current committer group.
How has the project developed since the last report?
- There have been bug fixes and feature progress
- Transfers of the pagespeed repositories to the ASF have been initiated
- RAT has been successfully run and an in-detail review of project
dependencies is in progress. So far no blockers or critical issues have been
identified.
How would you assess the podling's maturity? Please feel free to add your own
commentary.
[X] Initial setup
[X] Working towards first release
[X] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release: N/A
When were the last committers or PPMC members elected? 2017-09-30 (entering
incubation)
Signed-off-by:
[x](pagespeed) Jukka Zitting
Comments:
[x](pagespeed) Leif Hedstrom
Comments:
[X](pagespeed) Nick Kew
Comments:
[x](pagespeed) Phil Sorber
Comments:
--------------------
PLC4X
PLC4X is a set of libraries for communicating with industrial programmable
logic controllers (PLCs) using a variety of protocols but with a shared API.
PLC4X has been incubating since 2017-12-18.
Most important issues to address while moving towards graduation:
* Building the community: The PPMC and committer group has a large
percentage of codecentric employees, we have been recruiting people from
other companies, but will have to continue these efforts for
establishing a healthy Apache community.
* Onboarding of new committers: With PLC4X several people on the team are
not very familiar with the Apache Way. We have started and will continue
our efforts on this onboarding.
* Podling name search: We have invested a lot of time on the name search
prior to starting to work on the project, but we still need the official
OK that we’re allowed to keep the Name of Apache PLC4X.
* Make our first release
Any Issues the Incubator PMC or ASF Board might wish/need to be aware of:
* In order to get access to some of the specifications the ASF will
eventually have to become Members of some external foundations: OPC,
EtherCat, Modbus … these memberships usually have a free level, that
allows us to use the specifications but doesn’t result in any regular
costs. We will have to discuss these details with the ASF and the other
foundations.
* One of the external foundations (Profinet) doesn’t have a free
membership. In general, the CEO of the European branch of the Profinet
Foundation has signaled that it should be possible for the ASF to become
a member and have an outside company pay the membership fees, but we
have to discuss the details (With them as well as the ASF).
How has the community developed since the last report?
* We have been accepted into the Apache Incubator just a week before
Christmas, we are still in the process of setting up
* Prior to joining the Apache Incubator however, we have managed to
recruit people from other Apache projects and are working on getting
other people familiar with the protocols and the industry involved.
After the Christmas break we are planning on contacting a big group of
people that have claimed to be wanting to be involved (A list of about
20 Companies, but we can’t tell how many will be using and how many
would also be willing to contribute)
* We have started the onboarding of new committers and will be continuing
to do this (extended emails with a lot of explanations on why we are
doing things the way we are)
* Project has bootstrapped quickly and we have mailing lists, website,
JIRA etc. all set up and running.
* Testing coverage has been improved over the initial code base
How has the project developed since the last report?
* There was no last report.
How does the podling rate their own maturity?
* We have a mix of new participants and experienced Apache people
involved.
* So far, the new participants have shown great willingness and success in
adopting the Apache Way.
* However, we still need to continue:
* the on-boarding
* increasing the diversity of the team
* Also, will we need to decide and establish all the processes involved in
releasing software at Apache
Date of last release:
N/A
When were the last committers or PPMC members elected?
N/A
Signed-off-by:
[X](plc4x) Greg Trasuk
Comments:
[X](plc4x) Justin Mclean
Comments:
[x](plc4x) Luciano Resende
Comments:
[X](plc4x) Stefan Bodewig
Comments:
--------------------
Pony Mail
Pony Mail is a mail-archiving, archive viewing, and interaction service, that
can be integrated with many email platforms.
Pony Mail has been incubating since 2016-05-27.
Three most important issues to address in the move towards graduation:
1. Grow the community 2. Get the 0.10 release out 3. Address issues
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?
There's been a bit of a lull as of late in the project. I'm hopeful that it
will pick up some speed soon.
How has the community developed since the last report?
No noticeable change since last report.
How has the project developed since the last report?
N/A. Working on it!
How would you assess the podling's maturity? Please feel free to add your own
commentary.
[x] Initial setup
[x] Working towards first release
[ ] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
XXXX-XX-XX
When were the last committers or PPMC members elected?
Signed-off-by:
[ ](ponymail) Andrew Bayer
Comments:
[X](ponymail) John D. Ament
Comments: Would be good to get this podling
moving. Needs more committers to be truly viable.
--------------------
Rya
Rya (pronounced "ree-uh" /rēə/) is a cloud-based RDF triple store that
supports SPARQL queries. Rya is a scalable RDF data management system built on
top of Accumulo. Rya uses novel storage methods, indexing schemes, and query
processing techniques that scale to billions of triples across multiple nodes.
Rya provides fast and easy access to the data through SPARQL, a conventional
query mechanism for RDF data.
Rya has been incubating since 2015-09-18.
Three most important issues to address in the move towards graduation: 1. Have
more releases as part of the Apache Foundation 2. Increase diversity of
contributors.
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?
* Working on the next release
* Starting discussions about graduation
How has the project developed since the last report?
* Implemented a cache for Fluo query metadata
* Added a Twill App for running the periodic service
* Fixed several bugs
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-10-10
When were the last committers or PPMC members elected?
* PPMC member Caleb Meier elected on Jan 3rd, 2017
Signed-off-by:
[x](rya) Josh Elser
Comments: Have been pushing community towards
graduation. IMO, they are ready.
[ ](rya) Edward J. Yoon
Comments:
[ ](rya) Venkatesh Seetharam
Comments:
[ ](rya) Billie Rinaldi
Comments:
--------------------
SDAP
SDAP is an integrated data analytic center for Big Science problems.
SDAP has been incubating since 2017-10-22.
Three most important issues to address in the move towards graduation:
1. Grow community 2. Make formal SDAP (Incubating) releases 3. Evangelize
SDAP as an integrated data analytic center for Big Science problems
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?
Over the Christmas holidays not work has been done. SDAP is however being
presented at the ESIP Winter 2018 meeting taking place in Bethesda, Maryland,
U.S.A. this is a community building opportunity.
How has the project developed since the last report?
All infrastructure and codebase(s) have successfully been transitioned over to
the ASF. We are still working on branding, trademarks and source code
compliance.
How would you assess the podling's maturity? Please feel free to add your own
commentary.
[X] Initial setup
[X] Working towards first release
[X] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
XXXX-XX-XX
When were the last committers or PPMC members elected?
No new committers or PPMC have been added other than the original SDAP
committers.
Signed-off-by:
[ ](sdap) Jörn Rottmann
Comments:
[ ](sdap) Raphael Bircher
Comments:
[ ](sdap) Suneel Marthi
Comments:
[X](sdap) Lewis John McGibbney
Comments: SDAP is doing pretty well.
Branding, trademarks and source code compliance are the primary issues
right now. Once these are addressed SDAP can focus on the first Incubating
release.
--------------------
SensSoft
SensSoft is a software tool usability testing platform
SensSoft has been incubating since 2016-07-13.
Three most important issues to address in the move towards graduation:
1. Moving towards the first Incubating release of the source code and other
release artifacts to NPM/Bower, etc. 2. Grow the Apache SensSoft
(Incubating) community. 3. Complete the issues highlighted at the SensSoft
Roadmap https://cwiki.apache.org/confluence/display/SENSSOFT/Roadmap
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?
No
How has the community developed since the last report?
The community continues development via the scrum method. We are aiming for
the generation of the first release candidate for UserALE.js. No new
community members have come onboard with development swamping the mailing
lists. SensSoft is currently being worked into a NASA ACCESS proposal which
we hope will further community use and development.
How has the project developed since the last report?
The project is making sustainable progress. Project members are driving
towards generation of a release candidate for UserALE.js 0.1.0.
How would you assess the podling's maturity? Please feel free to add your own
commentary.
[X] Initial setup
[X] Working towards first release
[X] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
XXXX-XX-XX
When were the last committers or PPMC members elected?
Arthi Vezhavendan was added to PPMC and Committer base on 2017-01-24
Signed-off-by:
[ ](senssoft) Paul Ramirez
Comments:
[X](senssoft) Lewis John McGibbney
Comments:
[ ](senssoft) Chris Mattmann
Comments:
--------------------
ServiceComb
ServiceComb is a microservice framework that provides a set of tools and
components to make development and deployment of cloud applications easier.
ServiceComb has been incubating since 2017-11-22.
Three most important issues to address in the move towards graduation:
1. Finish apache 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?
N/A
How has the project developed since the last report?
This is the first report.
* Apache ICLA signed by all contributors from Huawei.
* Corporate Contributor License Agreement signed by Huawei.
* Software Grant Agreement signed by Huawei.
* Infrastructure setup
* ServiceComb codes are transferred Apache.
How would you assess the podling's maturity? Please feel free to add your own
commentary.
[X] Initial setup
[ ] Working towards first release
[ ] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
N/A
When were the last committers or PPMC members elected?
2017-11-22 (entering incubation)
Signed-off-by:
[X](servicecomb) Roman Shaposhnik
Comments:
[X](servicecomb) Jean-Baptiste Onofre
Comments:
[X](servicecomb) Timothy Chen
Comments:
--------------------
SkyWalking
Skywalking is an APM (application performance monitor), especially for
microservice, Cloud Native and container-based architecture systems. Also
known as a distributed tracing system. It provides an automatic way to
instrument applications: no need to change any of the source code of the
target application; and an collector with an very high efficiency streaming
module.
SkyWalking has been incubating since 2017-12-08.
Three most important issues to address in the move towards graduation:
1. Upload website 2. IP clearance. 3. First ASF release.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of? None. Some branding issues around publicity of incubation were raised and
have been corrected.
How has the community developed since the last report? 1. First Incubator
report. 2. Git repositories and mailing lists in place. 3. Website ready and
in transition to ASF infra. 4. Apache ICLA signed by all contributors from
Huawei.
How has the project developed since the last report? Still in initial setup
stage.
How would you assess the podling's maturity? Please feel free to add your own
commentary.
[x] Initial setup
[ ] Working towards first release
[ ] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release: n/a
When were the last committers or PPMC members elected? 2017-12-09 Sheng Wu
(PMC) 2017-12-09 DongXue Si (committer) 2017-12-09 Hongtao Gao (committer)
2017-12-09 Kai Wang (committer) 2017-12-09 Shinn Zhang (committer) 2017-12-09
Yang Bai (committer) 2017-12-09 Yongsheng Peng (committer) 2017-12-09 Sheng
Wang (committer) 2017-12-09 Yuntao Li (committer) 2017-12-09 Zhang Kewei
(committer)
Signed-off-by:
[X](skywalking) Luke Han
Comments:
[X](skywalking) Willem Ning Jiang
Comments:
[x](skywalking) Mick Semb Wever
Comments:
--------------------
Traffic Control
Traffic Control is a set of components that can be used to build, monitor,
configure, and provision a large scale content delivery network (CDN).
Traffic Control has been incubating since 2016-07-12.
Three most important issues to address in the move towards graduation:
1. Enhance automation to make it easier to build, install, and configure each
component. 2. Improve documentation to ease ramp-up time for new community
members and make it easier for existing community members to find what they
are looking for. 3. Complete at least two releases without license issues.
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 (October 2017)?
We held a fall summit in October in Atlanta. This summit was attended by over
20 participants from 5 different companies. The discussions were great and we
made sure to take any discussion that could potentially affect the community
to the mailing lists.
We cleaned up our mentors a bit by removing a few mentors who have asked to be
removed and/or have not contributed at all.
We have seen a few new users join our community, and our community has done a
good job of helping the new users get Traffic Control up and running.
The community has been working hard to get a new release out, which will be
Traffic Control 2.1.
How has the project developed since the last report?
Since the last report (October 2017), we have
* Merged 218 Pull Requests with 392 commits from 34 contributors
* Opened 135 Github issues
* Closed 70 Github issues
* 233 emails sent by 36 people on the dev@ list
* 25 emails sent by 12 people on the users@ list
How would you assess the podling's maturity? Please feel free to add your own
commentary.
We have started discussions about graduation and we all agree that we should
try to focus on graduating in 2018. As we see it, the biggest hurdles we
still face are: 1) Getting releases through the incubator without licensing
issues - we would like to be able to get at least two releases through without
licensing issues. 2) Removing dependencies with incompatible licenses;
specifically JSON.org and jdnssec
(https://github.com/dblacka/jdnssec-tools/blob/master/licenses/java-dnssec-tools-LICENSE.txt)
- our plan is to have these two mitigated by the end of Q1 2018.
[ ] Initial setup
[ ] Working towards first release (wip)
[] Community building (wip)
[x ] Nearing graduation
[ ] Other:
Date of last release:
Traffic Control 2.0 was released on July 7th, 2017.
Traffic Control 2.1 has passed the PPMC vote and was submitted to IPMC on
January 2nd.
When were the last committers or PPMC members elected?
In October, Traffic Control added 1 new committer: Nir Sopher.
Signed-off-by:
[x](trafficcontrol) Phil Sorber
Comments:
[](trafficcontrol) Eric Covener
Comments:
[x](trafficcontrol) Leif Hedstrom
Comments:
--------------------
Weex
Weex is a framework for building Mobile cross-platform high performance UI.
Weex has been incubating since 2016-11-30.
Three most important issues to address in the move towards graduation:
1. Develop more non-Chinese contributors and committers, to bring diversity
to the community. 2. Replace Facebook's Yoga(Category X) dependency and
release more while in Incubator. 3. Improve the developer's activity in
mailing list, more "bad ideas".
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?
The community is still learning the Apache Way, we are making progress and
need more guidance from Mentors. An additional active Mentor would be good.
How has the community developed since the last report?
• We voted one new committer: wentao shi
• We have encouraged people to discuss more in the JIRA and dev mailing list.
There is an obvious growth. 186(110 new issues since the last report) issues
have been reported on JIRA, and 93(56 since the last report) of them are
resolved or closed. And for dev@ mailing list, more discussions were made
in the past quarter. Some of the discussions are about important decisions
such as Community building roadmaps, whether to use Github issues, how to
develop plugins conveniently, how to replace Facebook/Yoga, whether to
create a project channel, etc. More and more non-alibaba and non-Chinese
guys were participating in the discussions.
• More non-alibaba developers are using Weex and reporting issues, including
developers from Tencent, Geekbang, SNDA, etc.
• Our Github repo has growth in contributors (135), forks (974), watchers
(377) and stars (7108)
• WebSite Trends Month Active, PV(440482), UV(68347), IP(59082), New Unique
Visitor(36063) , Session(114824)
How has the project developed since the last report?
• We have seperated the code for ducumentation & website from main repo to
weex-incubator-site, which will be easier to contribute.
• 9 authors have pushed 36 commits to master and 36 commits to all branches.
The community are intentionally making the committing work more slow and
deliberate.
• Replacing Facebook's Yoga is nearly done.
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-06-08
When were the last committers or PPMC members elected?
wentao shi, 19 Oct 2017
Signed-off-by:
[X](weex) Luke Han
Comments:
[ ](weex) Willem Jiang
Comments:
[ ](weex) Stephan Ewen
Comments:
[ ](weex) Raphael Bircher
Comments:
-----------------------------------------
Attachment AC: Report from the Apache Isis Project [Kevin Meyer]
## Description:
Apache Isis is a framework for rapidly developing domain-driven applications
in Java.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
We have made 1 release this quarter [1].
We believe that 1.16.0 will be the last release against version 1 of the
framework. With version 2 of the framework we plan to implement several major
changes (such as support for Java 8, compatibility with JEE 7, use of
DataNucleus 5.1 and removing deprecated functionality). Together these break
the existing API and hence warrant the increase in major version (we follow
semantic versioning).
## Health report:
The project is healthy with PMC members participating in votes and both
project members and users exchanging questions and answers on the mailing
lists.
## PMC changes:
- Currently 13 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Andi Huber on Mon Oct 09 2017
## Committer base changes:
- Currently 13 committers.
- No new committers added in the last 3 months
- Last committer addition was Andi Huber at Mon Oct 02 2017
## Releases:
- 1.16.0 was released on Mon 08 Jan 2018
## Mailing list activity:
There is nothing significant in the mailing list activity.
## JIRA activity:
- 67 JIRA tickets created in the last 3 months
- 74 JIRA tickets closed/resolved in the last 3 months
## References
[1] http://isis.apache.org/release-notes/release-notes.html#_release-notes_1.16.0
-----------------------------------------
Attachment AD: Report from the Apache James Project [Eric Charles]
-----------------------------------------
Attachment AE: Report from the Apache jclouds Project [Andrea Turli]
== Description ==
A cloud agnostic library that enables developers to access a
variety of cloud providers using one API.
== Project Status ==
We have finally been able to work on adding support for OpenStack Keystone v3,
a long-standing issue that prevents us from supporting modern OpenStack
versions. We are actively testing and expect to be able to cut a new release
in the short term, which will be a significant step as this is one of the
features most eagerly awaited by the community.
Separately, the Azure ARM provider has reached a sufficient level of
completeness and stability for promotion out of the "labs" in the next
release. We have seen continuous contributions to this provider as well as
help in testing, and are happy to see that it is one of the providers getting
more attention recently.
The OpenStack Neutron API has also proven to be very stable, and we intend to
work on promoting it out of "labs" too.
Progress continues on expanding the BlobStore portable interface which now
includes storage tiers.
== Community ==
We have started to use the #jclouds slack channel and are promoting it on the
mailing list and website as an alternative to IRC. Several contributors have
already joined the channel, which has lead to productive chats about
implementation details, source code internals, etc. It seems that Slack is
more user-friendly than IRC, and it is easier to engage users there, so we
will continue to promote and use this channel.
One user has Aliyun OSS support in a private branch and we have asked them to
share this code for possible mainline inclusion.
The project continues to receive contributions in the form of code and issues
from new developers, indicating that development is healthy and that users are
feeding back their problems and feature suggestions.
There are currently 12 PMC members and 24 committers.
Last committer: 2017-02-17 (Svetoslav Neykov)
Last PMC member: 2016-10-21 (Andrea Turli)
== Community Objectives ==
- Release jclouds 2.1.0 soon, as it contains long-awaited features, especially
around the OpenStack and Azure ARM providers
- Continue to monitor our community for potential new committers and PMC
members
== Releases ==
The last jclouds release, 2.0.3, took place on 2017-11-30.
-----------------------------------------
Attachment AF: Report from the Apache Jena Project [Andy Seaborne]
## Description:
Jena is a framework for developing Semantic Web and Linked Data applications
in Java. It provides implementation of W3C standards for RDF and SPARQL.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
There have been two releases this quarter.
## Response to previous board comment:
> Comments:
> mt: It has been a while since a new committer or PMC member was
> added. Is the PMC tracking any prospects?
mt, thank you for the question.
Yes, it has been about 18 months since the last PMC member was voted in and
about 15 months since the last committer was added.
The PMC is active and gets 3 or more binding votes on the hoped-for quarterly
releases. Occasionally, people outside the PMC give feedback on the release
artifacts.
No one on the PMC is employed to work on Jena; some do put in a few
work-hours. Much of the Jena codebase is stable and "maintenance".
There are also some active contributors outside the PMC/committer base. These
people tend to focus on a specific area of the codebase and they may provide a
short burst of interaction to see through their own contribution.
We are discussing how to help sustain this engagement and translate it into
some project level interactions. We have some people on the radar and we are
discussing how to get them involved outside of their specific contribution.
## Health report:
Project activity has been significantly higher than the long-term average
because of the two releases have been done this quarter. The major new feature
in 3.5.0 needed settling into the release process. However, there was also a
bug in an unrelated area which new users could easily walk into, so the
project made another release earlier than the usual 3-4 month cycle. In
addition, there has been ongoing development including contributions from
outside the committers.
## PMC changes:
- Currently 12 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Adam Soroka on Mon Jun 06 2016
## Committer base changes:
- Currently 15 committers.
- No new committers added in the last 3 months
- Last committer addition was Lorenz Buehmann at Fri Oct 28 2016
## Releases:
- Jena 3.5.0 was released on Mon Oct 30 2017
- Jena 3.6.0 was released on Sun Dec 17 2017
## Mailing list activity:
Two releases in one quarter significantly increased the dev@ mailing list
activity.
The 3.5.0 release included new database subsystem which generated quite a lot
of user@ discussion, including long threads on benchmarking of all storage
options.
- users@jena.apache.org:
- 625 subscribers (up 8 in the last 3 months):
- 952 emails sent to list (378 in previous quarter)
- dev@jena.apache.org:
- 151 subscribers (up 1 in the last 3 months):
- 1444 emails sent to list (443 in previous quarter)
## JIRA activity:
- 62 JIRA tickets created in the last 3 months
- 60 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AG: Report from the Apache JMeter Project [Bruno Demion]
## Description:
Pure Java application for load and functional testing.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
- The project prepares the next release: 4.0
## Health report:
- The project has a good activity during last quarter with a high number of
fixes/enhancements and external patches/ PRs.
## PMC changes:
- Currently 8 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Antonio Gomes Rodrigues on Sat Jan 28 2017
## Committer base changes:
- Currently 14 committers.
- No new committers added in the last 3 months
- Last committer addition was Maxime Chassagneux at Wed Feb 15 2017
## Releases:
- Last release was 3.3 final on Thu Sep 21 2017
## Mailing list activity:
- dev@jmeter.apache.org:
- 171 subscribers (up 4 in the last 3 months):
- 947 emails sent to list (640 in previous quarter)
- issues@jmeter.apache.org:
- 47 subscribers (down -1 in the last 3 months):
- 711 emails sent to list (552 in previous quarter)
- user@jmeter.apache.org:
- 872 subscribers (down -1 in the last 3 months):
- 248 emails sent to list (216 in previous quarter)
## Bugzilla Statistics:
- 156 Bugzilla tickets created in the last 3 months
- 124 Bugzilla tickets resolved in the last 3 months
## Social networks Statistics:
- Twitter: @ApacheJMeter has 3264 followers (3205 in previous quarter)
- GitHub.com/apache/jmeter has 1503 stars and 678 forks (1308 stars and 614
forks in previous quarter)
-----------------------------------------
Attachment AH: Report from the Apache Johnzon Project [Hendrik Saly]
## Description:
Apache Johnzon is an implementation of JSR-353 (JSON-P 1.0),
JSR-374 (JSON-P 1.1) and JSR-367 (JSON-B 1.0) and a set of useful extension
for this specification like JAX-RS providers and websocket (JSR-356)
integration.
## Issues:
There are no issues requiring board attention at this time
## Status:
We recently finished and released the implementation of JSR-374 and JSR-367.
Current focus is now to optimize the performance and stabilize the new
features.
## Releases:
- 1.1.5 was released on Mon Nov 13 2017
## Committers and PMC membership:
The last committer we signed up was James W. Carman on July 03, 2017. The
last PMC member was Reinhard Sandtner, added to the PMC on August 30, 2016.
## Project activity:
Since the last report there was low to mid activity.
We had 15 new Jira tickets and closed 10 tickets. On the mailinglist there a
no unanswered questions left. On the dev list we have 32 (+0) subscribers
currently and 10 msg sent per week. Since last report we saw mailing list
activity from a few new people.
-----------------------------------------
Attachment AI: Report from the Apache JSPWiki Project [Juan Pablo Santos Rodríguez]
## Description:
- A feature-rich and extensible WikiWiki engine built around the standard
Java EE components (Java, servlets, JSP).
## Issues:
- there are no issues requiring board attention at this time.
## Activity:
- Compared to last report, there has been an up-tick this quarter, where
activity has been focused on these areas:
* Initial support for Markdown: there is a new custom parser + renderer for
Markdown, although not complete yet (see
https://jspwiki-wiki.apache.org/Wiki.jsp?page=Markdown%20Support for
details)
* Fixed a bug regarding the renderer cache (JSPWIKI-1064)
* Tests were migrated from JUnit 3 to JUnit 4
* Generation of a test-jar, with several utilities to ease testing of
JSPWiki custom components.
- No questions unanswered on MLs, with at least 3 people from PMC showing up
there.
## Health report:
- Last report highlighted some ideas to increase contributions:
* move to Github as primary repo: done; we're also encouraging the use of
jspwiki as a topic on GitHub to increase contributions' visibility.
* adopting something similar to a release train: we should release 2.10.3
next February.
* lower committership barrier by granting commits rights to a) any ASF
committer. b) any other people who simply asks for it. Other than
discussing the idea, we haven't done anything, as nobody new has showed
up yet..
## 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:
- 83 subscribers (down -2 in the last 3 months):
- 40 emails sent to list (39 in previous quarter)
- user@jspwiki.apache.org:
- 176 subscribers (down -2 in the last 3 months):
- 52 emails sent to list (10 in previous quarter)
## JIRA activity:
- 1 JIRA tickets created in the last 3 months
- 3 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AJ: 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:
- Release v7.0.1 was created on Dec 24, 2017
- Release v7.1.0 is in plan to be released in the next couple of weeks.
## Health report:
- Project is still relatively new but generating fresh interest.
## PMC changes:
- Currently 9 PMC members.
- No new PMC members added in the last 3 months
## Committer base changes:
- Currently 9 committers.
- No new changes to the committer base since last report.
## Releases:
- 7.0.0 was released on Oct 20 2017
- 7.0.1 was released on Dec 24 2017
## Mailing list activity:
- dev@juneau.apache.org:
- 24 subscribers (up 1 in the last 3 months):
- 201 emails sent to list (213 in previous quarter)
## JIRA activity:
- 11 JIRA tickets created in the last 3 months
- 7 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AK: 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 past month has been quiet, between various holidays, vacations,
and illnesses. I'm sure we'll spring back into life in the coming
weeks.
We continue to hear from various ASF projects that want to participate
in the data/metric gathering part of the project.
## Health report:
The project has sufficient (3+ PMC members) oversight.
We remain healthy as a project, although a significant number of our
members have been not so healthy in the past weeks.
## PMC changes:
- Currently 12 PMC members.
- We voted Rafael Weingärtner in to our PMC on December 6th, 2017
## Committer base changes:
- Currently 11 committers.
- No new committers since graduation (October, 2017)
## Releases:
- No releases yet. We tentatively plan to have our first release within
the next six months.
## Mailing list and bug tracker activity:
Activity was down over the past month, but we expect a resurgance in
the coming weeks, particularly once FOSDEM is over.
-----------------------------------------
Attachment AL: Report from the Apache Kudu Project [Todd Lipcon]
## Description:
Apache Kudu is a distributed columnar storage engine built for the Apache
Hadoop ecosystem.
## Issues:
No issues requiring the board's attention at this time.
## Activity:
Since the last report, we've made one minor release (1.6.0).
The 1.6.0 release focused on bug fixes, stability, and performance. Notably,
Kudu can now gracefully handle failures of local disk drives without crashing
the process.
Work over the holiday period has been a bit slower, but we continue
to make progress around similar goals of stability and easier operations
for our next release.
In response to our last report, the board offered this feedback:
rb: Some projects find that separating committer and PMC gives you
the opportunity to be more generous with commit rights without
necessarily adding everyone to the PMC. It would be a shame to
have those 6 new contributors go away feeling unwelcomed.
We discussed this briefly on the private list and the consensus seemed to be
that we haven't felt any hesitation to add committers due to the combined
PMC/committer list. In this period we added three new PMC/committers so we
don't feel like splitting the list is necessary at this point.
## Health report:
- Subscriptions to the user mailing list are up slightly over last quarter.
In the previous quarter we noted that mailing list traffic was significantly
down, but in this quarter it has doubled back to previous levels.
It appears that the quiet couple of months was not indicative of any
trend.
- Website traffic is slightly up (unique users up 4.4%, sessions up 8.6%).
This is within our normal quarterly fluctuation.
- Development activity as measured by code reviews and JIRA traffic is down
a bit from the previous quarter, probably due to the holiday season.
- This quarter (Oct-Dec), we committed code authored by 17 distinct
contributors, of whom 3 were new to the project. We added three new
committers and PMC members.
- Collaboration continues with the Apache Impala project around our shared
RPC library code. This has been beneficial to both projects.
## PMC/Committer changes:
- Currently 19 PMC members and committers (all committers are PMC)
- Last committer/PMC additions:
-- Andrew Wong was added as a committer and PMC on Mon Oct 30 2017
-- Grant Henke was added as a committer and PMC on Fri Oct 27 2017
-- Hao Hao was added as a committer and PMC on Wed Dec 13 2017
## Releases:
- Apache Kudu 1.6.0 was released on December 6th, 2017.
-----------------------------------------
Attachment AM: Report from the Apache Labs Project [Danny Angus]
## Description
Apache Labs exists to incubate small and emerging projects from ASF
committers.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
- Another quiet period for Labs.
## Health report:
- As previously reported we have demonstrated that it is possible to generate
expressions of interest from within the committer community, but that has not
translated into positive momentum.
- Looking across the picture it is clear that, to make the service fit for
purpose we would need to adopt a git hub style of provision, and marry that up
to the benefits of ASF community membership (particularly legal), this may be
possible using the ASF->github integration, but I am reluctant to forge ahead
with this without a clear test case or better still a candidate project.
- Assuming a candidate project can be found and that the ASF->github bridge
does indeed provide us with a working option there remain two further
important hurdles, and these are more abstract.
1) The first, and most challenging of these is releases. There is a need for
a labs experiment to make releases, there is an understanding that a release
from a lab experiment would be different than a production ready piece of
infrastructure software, but when this was last discussed releases made
without proper oversight from the PMC were considered an unacceptable risk,
and proper oversight means independent corroboration of the code, which goes
against part of the lab philosophy, which is that we want to allow
already trusted people to get creative here, and not have to find another
place to kick start their one-person project. I think this might be capable of
being resolved by judicious use of branding, and a careful rephrasing of the
labs mission, but would require a board resolution to enact as "no releases"
is enshrined in the resolution that created the labs.
2) The second one is easier to achieve, we need to establish an archiving
process that allows completed and closed experiments to remain read-only in
perpetuity, which is more in keeping with the R&D spirit of labs experiments.
- Although there is a chance that this may be a solution without a problem I
personally believe that labs has the potential to play a major role in our
innovation mission, distinct from and complimentary to the incubator, and I
intend to follow up on these points in 2018.
## PMC changes:
- Currently 11 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Jan Iversen on Tue Feb 04 2014
## Committer base changes:
- Currently 31 committers.
- No new committers added in the last 3 months
- Last committer addition was Jan Iversen at Thu Feb 27 2014
## Releases:
- According to our charter, Labs makes no releases
## Mailing list activity:
- labs@labs.apache.org:
- 209 subscribers (up 0 in the last 3 months):
- 3 emails sent to list (9 in previous quarter)
## JIRA activity:
- 1 JIRA tickets created in the last 3 months
- 0 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AN: Report from the Apache Lucene.Net Project [Prescott Nasser]
Apache Lucene.Net is a port of the Lucene search engine library, written in C#
and targeted at .NET runtime users.
== Summary ==
While we are *very* slowly working towards a 4.8 release, we are
really starting to stumble. Several of the PMC and committers are still
around and semi-response to the mailing lists, but their other commitments
leave little time to help get 4.8.0 over the line to a full release. We've
started a thread to try and learn from the mailing list members what the
barriers to contribute are.
The mailing lists still see's a modest amount of traffic, questions and
answers, but it's primarily support for packages out there and less about the
work we need to do to get over the line.
Additionally, we are looking to rotate VP's of the project, but as of yet
haven't had any takers. My own obligations have unfortunately left me with
little time to actively be involved. A few of the PMC members are still around
to run the test suite and vote, and I believe we have the 3 votes required to
pass releases, but we are limping.
== Releases ==
* Last Release 3.0.3 - Oct 2012 Working toward 4.8.0
==Board Questions==
"Missing Reports" (I'm not sure anyone explicitly asked this). As mentioned
above, my time has been extremely limited, and we are looking to rotate our
VP, but as of yet have had no takers. Stefan Bodewig suggests we might need
to look towards the attic - which I believe would be unfortunate, but may be
the reality.
== Statistics ==
* Last PMC Member Added, Paul Irwin, October 2013
* Last committer added Sept 2016, Shad Storhaug
We've adjusted our package structure with version 4.8 Beta, to be more modular
and we probably need to find a new way to report these metrics. For the older
packages:
* Lucene.Net 3.0.3: 880,370 (up from 357,422)
* Lucene.Net.Contrib 3.0.3: 202,988 (up from 95,087)
* Lucene.Net Contrib Spatial: 17,182 (up from 10,574)
* Lucene.Net Contrib Spatial.NTS: 2,690 (up from 1,999)
Package Downloads (Beta 1-5) Version
Lucene.Net 18171 4.8.0-beta00005
Lucene.Net.Analysis.Kuromoji 50 4.8.0-beta00005
Lucene.Net.Analysis.Phonetic 80 4.8.0-beta00005
Lucene.Net.Analysis.SmartCn 52 4.8.0-beta00005
Lucene.Net.Analysis.Stempel 232 4.8.0-beta00005
Lucene.Net.Benchmark 52 4.8.0-beta00005
Lucene.Net.Classification 337 4.8.0-beta00005
Lucene.Net.Codecs 318 4.8.0-beta00005
Lucene.Net.Expressions 234 4.8.0-beta00005
Lucene.Net.Facet 793 4.8.0-beta00005
Lucene.Net.Grouping 892 4.8.0-beta00005
Lucene.Net.Highlighter 1117 4.8.0-beta00005
Lucene.Net.ICU 246 4.8.0-beta00005
Lucene.Net.Join 819 4.8.0-beta00005
Lucene.Net.Memory 1507 4.8.0-beta00005
Lucene.Net.Misc 878 4.8.0-beta00005
Lucene.Net.Queries 15920 4.8.0-beta00005
Lucene.Net.QueryParser 17078 4.8.0-beta00005
Lucene.Net.Replicator 49 4.8.0-beta00005
Lucene.Net.Sandbox 15321 4.8.0-beta00005
Lucene.Net.Spatial 361 4.8.0-beta00005
Lucene.Net.Suggest 487 4.8.0-beta00005
-----------------------------------------
Attachment AO: Report from the Apache Lucy Project [Peter Karman]
[REPORT] Lucy - January 2018
## Description:
The Apache Lucy search engine library provides full-text search for
dynamic programming languages. The Apache Clownfish "symbiotic" object
system pairs with "host" programming language environments and facilitates
the development of high performance language extensions.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
- There was one Apache Clownfish maintenance release this quarter.
- There were a few threads on the users@ list this quarter.
## Health report:
- One maintenance release indicates we have active committers and enough PMC
voters to create a release.
- This report was approved by at least 3 PMC members on the lucy-private list.
## PMC changes:
- Currently 12 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Timothy Wilkens on Sun Sep 14 2014
## Committer base changes:
- Currently 14 committers.
- No new committers added in the last 3 months
- Last committer addition was Tim Wilkens at Fri Sep 26 2014
## Releases:
- clownfish-0.6.2 was released on Tue Nov 14 2017
## Mailing list activity:
- dev@lucy.apache.org:
- 59 subscribers (down -1 in the last 3 months):
- 18 emails sent to list (0 in previous quarter)
- issues@lucy.apache.org:
- 21 subscribers (up 0 in the last 3 months):
- 6 emails sent to list (0 in previous quarter)
- user@lucy.apache.org:
- 87 subscribers (down -2 in the last 3 months):
- 15 emails sent to list (7 in previous quarter)
## JIRA activity:
- 2 JIRA tickets created in the last 3 months
- 2 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AP: Report from the Apache MADlib Project [Aaron Feng]
[REPORT] MADlib - January 2018
## Description:
- Apache MADlib is a scalable, Big Data, SQL-driven machine learning framework
for Data Scientists.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- MADlib 1.13 was released on 2017-December-22, and this is the second release
as an Apache TLP project.
- There is a MADlib community call on the topic of the 1.13 release scheduled
for 2018-January-17.
- As a final (we think) post-graduation task, we cleaned up
dist/incubator/madlib
- Community is working on 1.14 JIRAs is currently.
## Health report:
The community is relatively small but very engaged with robust mailing list
traffic, interest in doing frequent releases and new functionality being
developed by contributors. The number of developers actively contributing to
the code/documentation has increased to around 9 per month, up from 6 at the
time of the last report. We will constantly be on a lookout for new community
members to be invited either as committers or PMC.
## PMC changes:
- No changes in PMC, currently 13 PMC members.
## Committer base changes:
- Currently 13 committers.
- No new committers added in the last 3 months
- Last committer addition was Nandish Jayaram on 2016-09-08
## Releases:
- Next release: v1.14.0 planned for Feb 2018
- v1.13.0 released on 2017-12-22
- v1.12.0 released on 2017-08-29
- v1.11.0-incubating released on 2017-05-17
## Mailing list activity:
Mailing activity has remained relatively stable with 148 posts to dev@ and 7
posts to user@ during the month of December.
## JIRA Statistics:
- 10 JIRA tickets created in the last month
- 13 JIRA tickets resolved in the last month
-----------------------------------------
Attachment AQ: Report from the Apache Mahout Project [Andrew Palumbo]
Apache Mahout Board Report, Jan 2018
Apache Mahout is an environment for quickly creating scalable performant
machine learning applications.
## Issues:
- None
## Activity:
- 0.13.1 release in the works, though a code freeze has been temporarily
lifted. 0.13.1 is a multi-artifact release extending 0.13.0 to all
combinations of Spark from 1.6 - 2.x and 2.10, scala 2.11
- Continuing work on building out an algorithm library and continued native
optimizations.
- A More modern website has been designed and deployed
- David Miller, Creator of Start Bootstrap has agreed to do the site redesign
pro-bono.
Work is ongoing to fix minor errors on the new website; broken Links, etc. A
new logo is being considered.
## Health report:
- The health of the project is good with a devoted team of committers.
## PMC changes:
- Currently 14 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Trevor Grant on Sat Feb 04 2017
- PMC member Benson Margulies has changed his status to PMC Emeritus
## Committer base changes:
- Currently 28 committers.
- New commmitters:
- Holden Karau was added as a committer on Wed Jul 12 2017
- Dustin VanStee was added as a committer on Tue Jun 20 2017
## Releases:
- Last release was 0.13.0 on Mon Apr 17 2017
## Mailing list activity:
- dev@mahout.apache.org:
- 912 subscribers (down -6 in the last 3 months):
- 53 emails sent to list (110 in previous quarter)
- issues@mahout.apache.org:
- 15 subscribers (down -1 in the last 3 months):
- 132 emails sent to list (111 in previous quarter)
- user@mahout.apache.org:
- 1761 subscribers (down -14 in the last 3 months):
- 19 emails sent to list (43 in previous quarter)
Again we are seeing a dip in user@mahout.apache.org emails and
dev@mahout.apache.org. We will also continue to monitor these.
-----------------------------------------
Attachment AR: Report from the Apache Maven Project [Robert Scholte]
Maven Board Report - January 2018
---------------------------
Apache Maven is a widely-used project build tool, targeting mainly Java
development. Apache Maven promotes the use of dependencies via a
standardized coordinate system, binary plugins, and a standard build
lifecycle.
## Issues
<<There are no issues requiring board attention at this time.>>
## Activity
We've started moving more repositories to Git to improve cooperation on
code. Until now, we used GitWIP, but this time we use GitBox: we
were quite impressed by the self-service tooling and GitHub integration
quality. This will surely improve a lot cooperation with developers
community: we want to move all our projects to GitBox.
Before moving all our (sub)project to GITBox we had to find a solution to
keep control over the CI server jobs: Maven plugins should be tested with
different OSes, JDKs and Maven versions. Up until now this was achieved
by having all plugins in a subversion folder and testing all plugins
at once in one global "Maven plugins" Jenkins Job building. With Git
splitting the source code to about 40 independent source repositories,
this would mean maintaining 40 Jenkins jobs. Same happens for about 20
shared components. Maintaining single jobs for every 40 plugin and 20
shared component is not an option, both from development and
infrastructure perspectives: this would add too much jobs overhead.
With the initiative of Stephen Connolly and support by the ASF Infra team,
we were able to introduce a new ASF-dedicated Jenkins plugin that provide
TLP-jobs integrated with ASF GitPubSub to reduce load on Jenkins server.
We also wrote a shared Jenkinsfile library to ease maintenance of standard
pipeline for Maven TLP builds.
This cleared the path to migrate all our projects: we now have only one
Maven-GitBox job that manages efficiently the builds for every project
having its code on GitBox. We also have another Maven-GitWIP job doing the
same for code on GitWIP: we expect to migrate from GitWIP to GitBox to
benefit from extended high quality GitHub integration during the next
months.
There are several little bugs here and there that we're currently fixing
to have a perfect experience, but this type of setup may be reused in
the future for other ASF projects: we'll need to see how to efficiently
help other projects that may be interested. Having this unusual long
technical explanation on current board report is a first step to sharing.
We're also currently working with Infra on an extension on this
GitBox+Jenkins setup to build and deploy Maven site from a GitHub editing
workflow: this may be of interest also for other projects. We'll
probably do an Apache blog post once it is ready.
## Health Report
We're struggling with active committers. Knowing that Maven is still the
defacto standard buildtool and is used by about 2/3 of the Java
projects/developers it is hard to take all responsibilities by keeping up
with the open issues and to work on the ideas we have for the next major
versions of Maven.
BOFs at conferences have been good places to make developers aware of
the situation. Some are offering their help at that time, but this rarely
leads to participation in the end.
We hope the work on Git migration with great GitHub integration will ease
participation in the future: we've already seen some little improvement.
## PMC changes:
- Currently 25 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Guillaume Boué on Mon Aug 07 2017
## Committer base changes:
- Currently 57 committers.
- No new committers added in the last 3 months
- Last committer addition was Guillaume Boué at Thu Jul 07 2016
## Mailing list activity:
- users@maven.apache.org:
- 1651 subscribers (down -8 in the last 3 months):
- 228 emails sent to list (267 in previous quarter)
- dev@maven.apache.org:
- 605 subscribers (down -4 in the last 3 months):
- 783 emails sent to list (761 in previous quarter)
- announce@maven.apache.org:
- 672 subscribers (up 0 in the last 3 months):
- 11 emails sent to list (16 in previous quarter)
- issues@maven.apache.org:
- 227 subscribers (down -4 in the last 3 months):
- 2059 emails sent to list (1788 in previous quarter)
## JIRA activity:
- 249 JIRA tickets created in the last 3 months
- 159 JIRA tickets closed/resolved in the last 3 months
## Releases:
### Core
- Maven 3.5.2 was released on Tue Oct 24 2017
### Plugins
- Maven JDeprScan Plugin 3.0.0-alpha-1 was released on Wed Nov 15 2017
- Maven Javadoc Plugin 3.0.0 was released on Wed Dec 06 2017
- Maven PDF Plugin 1.4 was released on Thu Dec 28 2017
- Maven Site Plugin 3.7 was released on Sun Dec 31 2017
### Other
- Maven Reporting Executor 1.4 was released on Mon Oct 16 2017
- Maven Indexer 6.0.0 was released on Fri Dec 01 2017
- Maven Doxia 1.8 was released on Thu Dec 21 2017
- Maven Doxia Sitetools 1.8 was released on Thu Dec 28 2017
- Maven Fluido Skin 1.7 was released on Fri Jan 05 2018
-----------------------------------------
Attachment AS: Report from the Apache Mesos Project [Benjamin Hindman]
-----------------------------------------
Attachment AT: Report from the Apache Metron Project [Casey Stella]
## Description:
Metron integrates a variety of open source big data technologies in order to
offer a centralized tool for security monitoring and analysis. Metron
provides capabilities for log aggregation, full packet capture indexing,
storage, advanced behavioral analytics and data enrichment, while applying the
most current threat-intelligence information to security telemetry within a
single platform.
## Issues:
There are no issues requiring board attention at this time
## Activity:
- We added 3 PMC members and 2 committers
## Health report:
Project activity is broadly the same as in prior months. The new release has
been received positively.
## PMC changes:
- Currently 27 PMC members.
- New PMC members:
- Justin Leet was added to the PMC on Sun Dec 03 2017
- Michael Miklavcic was added to the PMC on Thu Nov 30 2017
- Otto Fowler was added to the PMC on Thu Nov 30 2017
## Committer base changes:
- Currently 37 committers.
- New commmitters:
- Anand Subramanian was added as a committer on Mon Dec 25 2017
- Raghu Mitra was added as a committer on Wed Oct 25 2017
## Releases:
- Last release was 0.4.1 on Thu Sep 14 2017
## JIRA activity:
- 150 JIRA tickets created in the last 3 months
- 125 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AU: Report from the Apache MINA Project [Jeff Maury]
## Description:
Apache MINA is a network application framework which helps users
develop high performance and high scalability network applications
easily.
## Issues:
MINA 2.0.17 was not released due to lack of time from the release manager.
## Activity:
Main is SSHD although discussion happened on core
## Health report:
Users have shown interest for the next release of MINA
## PMC changes:
- Currently 12 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Lyor Goldstein on Mon Feb 13 2017
## Committer base changes:
- Currently 26 committers.
- No new committers added in the last 3 months
- Last committer addition was Lyor Goldstein at Thu Apr 30 2015
## Releases:
- Last release was SSHD-1.6.0 on Wed Jul 05 2017
## Mailing list activity:
- users@mina.apache.org:
- 500 subscribers (down -7 in the last 3 months):
- 11 emails sent to list (13 in previous quarter)
- dev@mina.apache.org:
- 347 subscribers (down -7 in the last 3 months):
- 422 emails sent to list (375 in previous quarter)
- ftpserver-users@mina.apache.org:
- 133 subscribers (up 1 in the last 3 months):
- 3 emails sent to list (0 in previous quarter)
## JIRA activity:
- 18 JIRA tickets created in the last 3 months
- 26 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AV: Report from the Apache Mnemonic Project [Gang Wang]
Description:
Apache Mnemonic is an open-source Java library for durable object-oriented
programming on hybrid storage-class memory(e.g. NVM) space. it comes up
with durable object model (DOM) and durable computing model(DCM) and
takes full advantages of storage-class memory to simplify the code
complexity, avoid SerDe/(Un)Marshal, mitigate caching for constructing
next generation computing platform. Mnemonic makes the storing and
transmitting of massive linked objects graphs simpler and more efficient.
The performance tuning could also be mostly converged to a single point
of tuning place if based on Mnemonic to process and analyze
linked objects. The programmer are able to focus on durable object
oriented business logics instead of worrying about how to normalize/join,
serDe(un)marshal, cache and storing their linked business objects
with arbitrary complexity.
Issues:
There are no board-level issues at the moment.
Activity:
This is a vacation month so our community has no much activities durable
this month, basically, we have start to document tutorials, this task is
created by one of our contributor, and another one is to start making
Mnemonic supporting JDK9, the JDK9 changes something that our project
relies on, we have to migrate to JDK9 as well as be compatible with older
versions of JDK e.g. JDK8,JDK7. Lastly we have upvoted a new committer.
Health Report:
Basically unchanged since the last report. Users are generally quiet
in public and no new users are appearing, but development continues.
PMC Changes:
- Currently 11 PMC members.
- No new PMC members added in the last 1 months.
Committer Base Changes:
- Currently 12 committers.
- A new committer has elected and accepted to our committer base on Jan.08
Releases:
- Last release was v0.10.0 on Mon Nov. 2017
- Still active development on next major version (0.11.0)
JIRA Activity:
- 15 JIRA tickets created since the last report
- Also 3 JIRA tickets closed/resolved this period
Sincerely,
Gang(Gary) Wang on behalf of the Apache Mnemonic PMC
-----------------------------------------
Attachment AW: Report from the Apache MyFaces Project [Mike Kienenberger]
## Description:
The Apache MyFaces project is an umbrella project of the Apache Software
Foundation for projects relating to the JavaServer Faces
(JSF) technology.
## Issues:
- There are no issues requiring board attention at this time.
## Activity and health:
- Apache Myfaces Core is healthy, and the community is working on the new JSF
2.3 specification features.
UI-Component Sets:
- Apache Tobago is healthy and active.
- Apache Trinidad is in maintenance mode. Last developer commit was Sept
2017.
- Myfaces Tomahawk is in maintenance mode. Last developer commit was May 2016.
Last commit on behalf of a contributor was May 2016.
Add-ons and Extensions:
- Apache MyFaces Portlet Bridge is in maintenance mode. Last developer commit
was Jan 2014. Last commit on behalf of a contributor was May 2015.
- Apache MyFaces CODI is in maintenance mode. CODI was replaced by Apache
DeltaSpike so new development happens there. Last commit March 2014.
- Apache MyFaces Orchestra is in maintenance mode. New projects use CDI and
DeltaSpike instead. Last commit on behalf of a contributor was August 2016.
- Apache MyFaces ExtVal is in maintenance mode. Last commit June 2014.
- Apache MyFaces Commons is in maintenance mode. Last commit August 2012.
- Apache MyFaces Ext-Scripting is in maintenance mode. Last commit Sept 2017.
- Apache MyFaces Test is in maintenance mode (Used by Myfaces Core). Last
commit May 2017.
## Community changes:
- Currently 78 committers and 43 PMC members.
- Last committer addition was Eduardo Breijo at Thu Jun 29 2017
- Last PMC additions was Dennis Kieselhorst on Sun Feb 05 2017
## Releases:
- tobago-4.0.0 was released on Wed Dec 06 2017
## JIRA activity:
- 51 JIRA tickets created in the last 3 months
- 98 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AX: Report from the Apache NiFi Project [Joe Witt]
## Description:
- Apache NiFi is an easy to use, powerful, and reliable system to process and
distribute data.
- Apache NiFi MiNiFi is an edge data collection agent built to seamlessly
integrate with and leverage the command and control of NiFi. There are both
Java and C++ implementations.
- Apache NiFi Registry is a centralized registry for key configuration items
including flow versions, assets, and extensions for Apache NiFi and Apache
MiNiFi.
- Apache NiFi Nar Maven Plugin is a release artifact used for supporting the
NiFi classloader isolation model.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- Conducted several releases including Apache NiFi Registry, Apache NiFi
MiNiFi CPP and Apache NiFi MiNiFi Java. The Apache NiFi Registry release is
a very important step forward for the community as it provides a powerful
software development lifecycle mechanism for Apache NiFi users and answers
a long standing request and often discussed capability.
- Apache NiFi 1.5.0 Release Candidate under vote at the time of this board
report writing.
- Voted a significant number of new committers and PMC members and are
extremely fortunate to see strong committer pipeline continue through newer
contributors with significant contributions.
- The PMC has identified and worked with Trademarks/Legal at Apache for a
couple of potential trademark or licensing abuse issues. Consensus was
that neither issue rises to the level of requiring any specific official
response though in one case we intend to provide a courtesy notification to
a commercial entity that is heavily leverage Apache NiFi source code
without any attribution. It is more of a poor form issue than a real
problem. Thanks to several highly experienced Apache Members who helped
discuss the threads in detail.
## Health report:
- Health of the community remains strong. Mailing list and JIRA activity is
consistent. ASF Hipchat is serving as an on-ramp for new users to our
mailing list and JIRA systems. We continue to see new users and
contributors.
- The PMC continues to demonstrate ability to detect and handle potential
trademark issues though it needs to focus better on staying tight and
prompt on security matters all the way through resolution.
- As we called out in our previous report we anticipated significant
recognition of earned meritocracy within the committer and PMC ranks. That
held true and the pipeline remains encouraging.
## PMC changes:
- Currently 26 PMC members.
- New PMC members:
- Marc Parisi was added to the PMC on Wed Dec 13 2017
- Jeff Storck was added to the PMC on Mon Dec 04 2017
- Scott Aslan was added to the PMC on Fri Dec 01 2017
- Michael W Moser was added to the PMC on Sun Nov 19 2017
- Last PMC member added Wed Dec 13 2017.
## Committer base changes:
- Currently 38 committers.
- New commmitters:
- Kevin Doran was added as a committer on Wed Jan 03 2018
- Andrew Ian Christianson was added as a committer on Mon Nov 13 2017
- Mike Hogue was added as a committer on Thu Nov 09 2017
- Peter Wicks was added as a committer on Thu Nov 09 2017
- Last committer added Wed Jan 03 2018.
## Releases:
- Apache NiFi Registry 0.1.0 was released Jan 1 2018.
- Apache NiFi MiNiFi Java 0.3.0 was released Dec 22 2017.
- Apache NiFi MiNiFi CPP 0.3.0 was released Nov 30 2017.
## Mailing list activity:
- Activity on the mailing lists remains high with a mixture of new users,
contributors, and deeper more experienced users and contributors sparking
discussion and questions and filing bugs or new features.
- users@nifi.apache.org:
- 581 subscribers (up 25 in the last 3 months):
- 783 emails sent to list (721 in previous quarter)
- dev@nifi.apache.org:
- 388 subscribers (up 5 in the last 3 months):
- 679 emails sent to list (590 in previous quarter)
- issues@nifi.apache.org:
- 46 subscribers (up 0 in the last 3 months):
- 6950 emails sent to list (5388 in previous quarter)
## JIRA activity:
- 356 JIRA tickets created in the last 3 months
- 276 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AY: Report from the Apache Nutch Project [Sebastian Nagel]
Apache Nutch is a highly extensible and scalable open source web crawler
software project. Stemming from Apache Lucene®, the project has diversified
and now comprises two codebases, based respectively on Apache Hadoop® data
structures and Apache Gora for leveraging NoSQL databases.
ISSUES
There are no issues requiring board attention at this time.
RELEASES
Nutch 1.14 was released on Dec 22 2017.
The last release on the 2.x branch (2.3.1) dates to Jan 20 2016.
CURRENT ACTIVITY
We released Nutch 1.14 in December with 37 issues fixed and 41 new features
and improvements, contributions made by 20 developers.
We see an increased activity on Jira and github with contributions from new
developers kept on radar for committership.
We plan to release 2.4 during the next weeks.
We hope to participate again in GSoC and continue with the project
"Graph Generator Tool for Nutch" which was started last year during GSoC 2017
by Omkar Reddy and made huge progress upgrading the Hadoop API but did not
address the graph generation as described.
JIRA ACTIVITY
- 54 JIRA tickets created in the last 3 months
- 64 JIRA tickets closed/resolved in the last 3 months
COMMUNITY
No new committers and PMC members in the last 3 months, last PMC addition was
Ralf Kotowski on Wed Jun 14 2017.
The traffic on the user mailing list is at a steady level:
- dev@nutch.apache.org:
- 530 subscribers (down -10 in the last 3 months)
- 877 emails sent in the past 3 months (484 in the previous quarter)
(mostly machine-generated emails from Jira, Jenkins, Wiki)
- user@nutch.apache.org:
- 1060 subscribers (down -8 in the last 3 months)
- 166 emails sent in the past 3 months (212 in the previous quarter)
-----------------------------------------
Attachment AZ: Report from the Apache ODE Project [Sathwik]
## Description:
Apache ODE is a WS-BPEL implementation that supports web services
orchestration using flexible process definitions.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
We have completed the upgrades of various libraries. Major work completed as
follows,
* Java 8 compatible.
* JPA 2 with OpenJPA-2.4.2
* JPA 2.1 with Hibernate-4.3.11
* TOMEE 7.0.4
* Axis2 1.7.6
We are heading towards 1.3.8 release. Testing is underway. Hoping to make
the release in this quarter. Work is underway on moving some of these
upgrades on to the trunk.
Nothing concrete has come out yet on future of ODE. Some developers have
shown interest to contribute.
[http://markmail.org/message/5zkz7vt33urldv7e]
## Health report:
- ODE is very mature and stable, however the interest in BPEL has decreased
significantly. Thus ODE's development is currently pretty much in
maintenance mode.
## PMC changes:
- Currently 15 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Rafal Rusin on Wed Oct 01 2014
## Committer base changes:
- Currently 26 committers.
- No new changes to the committer base since last report.
- Last committer was Sathwik on Dec 23 2012.
## Releases:
- Last release was 1.3.7 on Fri Jul 07 2017
## Mailing list activity:
dev@ode.apache.org:
- 151 subscribers (up 2 in the last 3 months):
- 86 emails sent to list (77 in previous quarter)
user@ode.apache.org:
- 215 subscribers (down -2 in the last 3 months):
- 22 emails sent to list (48 in previous quarter)
## JIRA activity:
- 3 JIRA tickets created in the last 3 months
- 0 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment BA: Report from the Apache Olingo Project [Christian Amend]
## Description:
Apache Olingo is a Java and JavaScript library that implements the Open Data
Protocol (OData). Apache Olingo serves client and server aspects of OData. It
currently supports OData 2.0 and OData 4.0. The latter is the OASIS version of
the protocol: OASIS Open Data Protocol (OData) TC.
## Olingo Status
Olingo has no issues that would require board attention. We released a patch
for the V2 code line in December to fix small bugs but had no major new
features. The V4 code line is still seeing new features but the main new
features should come when the OData 4.01 specification is released. The
specification is in a public review since June 2017 at Oasis.
We still see good discussions on the user mailing lists and new JIRA issues
contain patches on a more consistent basis which shows that the community is
still working with Olingo.
## PMC changes:
- Currently 13 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Ramesh Reddy on Thu Oct 08 2015
## Committer base changes:
- Currently 25 committers.
- No new committers added in the last 3 months
- Last committer addition was Archana Rai at Fri May 26 2017
## Releases:
- Last release was V2 2.0.9 on Wed Dez 06 2017
## Mailing list activity:
- dev@olingo.apache.org:
- 86 subscribers (up 2 in the last 3 months):
- 158 emails sent to list (248 in previous quarter)
- user@olingo.apache.org:
- 190 subscribers (up 4 in the last 3 months):
- 28 emails sent to list (32 in previous quarter)
## JIRA activity:
- 32 JIRA tickets created in the last 3 months
- 15 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment BB: Report from the Apache Oltu Project [Antonio Sanso]
-----------------------------------------
Attachment BC: 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:
Still low activity. Maintenance is going on at a low level.
## Health report:
Still have to ship OpenJPA-3.0.0. Currently we lack people
who push this forward.
## PMC changes:
- Currently 16 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Jody Grassel on Tue Aug 15 2017
## Committer base changes:
- Currently 33 committers.
- No new committers added in the last 3 months
- Last committer addition was Will Dazey at Thu Aug 17 2017
## Releases:
- Last release was 2.4.2 on Tue Jan 03 2017
## Mailing list activity:
- users@openjpa.apache.org:
- 235 subscribers (down -5 in the last 3 months):
- 11 emails sent to list (35 in previous quarter)
- dev@openjpa.apache.org:
- 137 subscribers (up 0 in the last 3 months):
- 37 emails sent to list (101 in previous quarter)
## JIRA activity:
- 7 JIRA tickets created in the last 3 months
- 1 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment BD: Report from the Apache OpenMeetings Project [Maxim Solodovnik]
## Description:
- Openmeetings provides video conferencing, instant messaging,
white board, collaborative document editing and other groupware
tools using API functions of the Red5 Streaming Server for
Remoting and Streaming.
## Issues:
- there are no issues requiring board attention at this time
## Activity:
- We are working on 4.0.2 release which will address
issues and add improvements. Planning
another round of major changes.
## Health report:
- Improvements are actively being discussed on
user@ list. No new commiters/PMC members hopefully there
will be active users so we can add new members
## PMC changes:
- Currently 25 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Hemant Sabat on Sat Aug 05 2017
## Committer base changes:
- Currently 27 committers.
- No new committers added in the last 3 months
- Last committer addition was Hemant Sabat at Sat Aug 05 2017
## Releases:
- 4.0.0 was released on Fri Nov 03 2017
- 4.0.1 was released on Fri Dec 08 2017
## Mailing list activity:
- Mailing list activity is increased due to major changes in latest
4.0.x releases.
- dev@openmeetings.apache.org:
- 141 subscribers (down -3 in the last 3 months):
- 305 emails sent to list (194 in previous quarter)
- user@openmeetings.apache.org:
- 349 subscribers (up 3 in the last 3 months):
- 937 emails sent to list (785 in previous quarter)
- user-espanol@openmeetings.apache.org:
- 66 subscribers (up 1 in the last 3 months):
- 20 emails sent to list (17 in previous quarter)
- user-russian@openmeetings.apache.org:
- 40 subscribers (up 0 in the last 3 months):
- 177 emails sent to list (93 in previous quarter)
## JIRA activity:
- 95 JIRA tickets created in the last 3 months
- 96 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment BE: Report from the Apache OpenOffice Project [Peter Kovacs]
## DESCRIPTION
Apache OpenOffice is an open-source office-document productivity suite. There
are six productivity applications based around the OpenDocument Format (ODF)
that are Writer, Calc, Impress, Draw, Math, Base. With limited support for
other file formats, OpenOffice ships for Windows, macOS, Linux 64-bit, Linux
32-bit and in 41 languages.
## STATUS
The activity within the project continues to grow. With the latest releases
more traffic came into different mailing lists. The release frequency is
rising. Overall showing a slow recovery of the project in different areas.
Limitations of capacity of development is an ongoing concern.
## ISSUES FOR BOARD AWARENESS
There are no current topics to be concerned with.
## ISSUES
No topics
## RELEASES
The current release is Apache OpenOffice 4.1.5. It is necessary due to
regression issues that were reported recently and need to be fixed since
occurring in 4.1.4. Release Management prefered an own release for 2 reasons:
1) The new release team has build some routine with bugfix releases, which can
be seen in the shorter release cycles in the last releases. 2) The next Major
release is our next big thing. A lot of efforts has to be invested in this
release before a final release is ready. The wait time for users has been
considered as to long to wait.
The desicion to go for another bugfix release was a good one in retrospect.
The team has managed to release the regression fixes within the same quarter.
This is the first time OpenOffice has released 2 updates close together.
The next major release will be 4.2.0 with a target to publish in 2018. In
opposite to the 4.1.x releases it will include new features and bigger
enhancements but of course also bugfixes.
## Complete Release History
2017-12-30 4.1.5
2017-10-19 4.1.4
2016-10-12 4.1.3 (with integrated patch1)
2016-08-30 4.1.2-patch1 (additional binaries)
2016-08-02 4.1.2-patch1 (sourcecode only)
2015-10-28 4.1.2
2014-08-21 4.1.1
2014-04-29 4.1.0
2013-10-01 4.0.1
2013-07-23 4.0.0
2013-01-30 3.4.1 refresh (8 more languages)
2012-08-23 3.4.1 incubating
2012-05-08 3.4.0 incubating
## PMC
There are 28 PMC members as of 2018-Jan-09. The recognition and invitation of
new PMC members remains on a stable level.
Last PMC member addition was on 2017-Dec-20 Keith N. McKenna (knmc) Last PMC
member withdrawal was on 2017-Feb-04 Dennis E. Hamilton (orcmid)
## Committers
There are 140 committers as of 2018-Jan-09. The recognition and invitation of
new committers is also on a stable level.
Last committer addition was on 2017-Dec-18 Guenter Feierabend (guenterf) Last
committer withdrawal was on 2017-Feb-04 Dennis E. Hamilton (orcmid)
## ACTIVITY
## Organization
The project has changed its chair as Marcus Lange had the role for over 1 year
and it was agreed to change it every 12 month. Therefore we had a vote with 2
candidates. Peter Kovacs (petko) has won the election and is now the new chair
since 2017-Dec-20.
## Development and Release Engineering
Currently the project is busy with the next major 4.2.0 release. Dev builds
are already built on routine bases.Testing on a low level is ongoing, more
detailed testing will be the next topic. Upgrades to the build system is
ongoing.
Current activities focus on the reactivation of the localization team.
Documentation, process and tools are undergoing a complete review. The current
activity focus on:
+ importing the latest work by translators into the OpenOffice code.
+ updating Pootle strings to match trunk (the first Pootle update in years).
+ give translators the possibility to test their translations with dedicated
builds.
+ add new languages to the next major release if translators manage to
complete their work in time.
Further activities are:
+ first view tests are run on the dev builds.
+ upgrading the building environment.
The arrival of new developers is very low. But the current committers are
willing to help where possible. Improving the mentoring of newcomers and
expanding the capacity to address major issues is a key factor for the next
time. Some issues and easy tasks are selected to act as training for the new
developers.
## Downloads
As of 2018-Jan-07 we have more than 235,000,000 downloads and it is at a
consistent rate with ~91,000 downloads in average per day. Windows is the most
famous platform. Then macOS and Linux are following.
Downloads regarding the country over the last 3 months are spread like the
following
(source:
https://sourceforge.net/p rojects/openofficeorg.mirror/files/stats/map?dates=2017-10-08+to+2018-01-07):
13.7 % Germany
12.7 % United States
12.0 % France
7.9 % Italy
5.6 % Russia
5.4 % Poland
4.6 % Spain
3.8 % United Kingdom
3.1 % Japan
2.1 % Ukraine
2.0 % Canada
27.1 % All other countries
## Websites
Updates are done and the websites are up-to-date so far, at least for the
initial entrance portal, download webpage and some others.
## Activity of mailing lists
The following table shows the list activity (monthly average):
(source:
https://mail-archives.apache.org/mod_mbox/openoffice-<mailing-list-name>/)
2012 2013 2014 2015 2016 2017 Q1-2018
dev@ 1266 1124 552 340 323 253 6
users@ 235 198 328 219 208 154 1
l10n@ 211 225 119 34 18 19 1
qa@ 150 127 71 16 16 2 0
marketing@ 63 87 18 3 4 2 0
api@ 30 35 20 15 1 0 0
doc@ 7 41 25 12 13 1 0
recruitment@ - - - - 3 11 0 (start in Sep 2016)
users-de@ 38 167 147 94 89 55 1
dev-de@ 0 0 42 6 13 17 0
utenti-it@ 29 40 30 37 27 8 1
progetto-it@ 12 17 8 2 1 1 0
general-es@ 34 24 9 4 4 7 0
users-fr@ 1 4 6 0 1 1 0
general-ja@ 3 2 0 0 0 0 0
geral-ptbr@ 21 5 1 0 0 0 0
## Fairs and events
Apache OpenOffice is represented on a few fairs and events which is managed
regularly by a small and fine team. This will continue in 2018.
## BRANDING
In average there is nearly 1 request per month for use of the marks - but it's
decreasing in the last months. The same for reports about suspected trademark
misuse (or confusion about selling of Apache OpenOffice binaries, e.g., on
eBay).
-----------------------------------------
Attachment BF: Report from the Apache ORC Project [Owen O'Malley]
## Description:
- A high-performance columnar file format for Hadoop workloads.
## Issues:
- There are no issues requiring the board's attention.
## Activity:
- We made bug fix releases for both the 1.3 and 1.4 branches.
- The C++ writer can write the original (Hive 0.11) version and
will be extended to write the current version.
- Apache Hive has moved up to the ORC 1.4.1 release.
- Apache Arrow has started adding support for ORC.
- Apache Flink is working on a patch to add ORC support.
- We are working on getting column encryption implemented.
- We've started release discussions for ORC 1.5.
## Health report:
- We have several active contributors that we are encouraging and
tracking to committership.
## PMC changes:
- Currently 9 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Eugene Koifman on Tue Sep 05 2017
## Committer base changes:
- Currently 36 committers.
- No new committers added in the last 3 months
- Last committer addition was Deepak Majeti at Tue May 09 2017
## Releases:
- Last releases were ORC-1.4.1 and ORC-1.3.4 on Sun Oct 15 2017
## Mailing list activity:
- The email traffic is down a bit this quarter, but I expect it to
pick back up again this quarter as we move forward on ORC 1.5.
- dev@orc.apache.org:
- 50 subscribers (up 1 in the last 3 months):
- 250 emails sent to list (327 in previous quarter)
- issues@orc.apache.org:
- 20 subscribers (up 0 in the last 3 months):
- 265 emails sent to list (417 in previous quarter)
- user@orc.apache.org:
- 56 subscribers (up 3 in the last 3 months):
- 14 emails sent to list (18 in previous quarter)
## JIRA activity:
- 34 JIRA tickets created in the last 3 months
- 31 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment BG: Report from the Apache Parquet Project [Julien Le Dem]
## Description:
Parquet is a standard and interoperable columnar file format
for efficient analytics. Parquet has 3 sub-projects:
- parquet-format: format reference doc along with thrift based metadata
definition (used by both sub-projects bellow)
- parquet-mr: java apis and implementation of the format along with
integrations to various projects (thrift, pig, protobuf, avro, ...)
- parquet-cpp: C++ apis and implementation of the format along with Python
bindings and arrow integration.
## Issues:
No issue at this time
## Activity:
Current activity around:
Deprecating int96 timestamp
Preparing for a release
Supporting dot net integration
Min max stats improvement
Page indexing new features
Bloom filters support
## Health report:
The discussion volume on the mailing lists is stable.
Tickets get created and closed at a reasonable pace
## PMC changes:
- Currently 23 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Uwe Korn on Sun Mar 26 2017
## Committer base changes:
- Currently 28 committers.
- New commmitters:
- Lars Volker was added as a committer on Mon Oct 16 2017
- Zoltan Ivanfi was added as a committer on Fri Oct 27 2017
## Releases:
- CPP-1.3.1 was released on Fri Oct 27 2017
- Format 2.4.0 was released on Sat Oct 21 2017
## Mailing list activity:
- dev@parquet.apache.org:
- 200 subscribers (up 12 in the last 3 months):
- 633 emails sent to list (432 in previous quarter)
## JIRA activity:
- 54 JIRA tickets created in the last 3 months
- 41 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment BH: Report from the Apache PDFBox Project [Andreas Lehmkühler]
## Description:
- the Apache PDFBox library is an open source Java tool for working with PDF
documents.
## Issues:
- there are no issue requiring board attention at this time.
## Activity:
- the integration of the JBig2 ImageIO plugin is complete
- we are planning to release the first Apache based version of the JBig2
ImageIO plugin this month
- we are working on fixing bugs in 2.0.x
- we have resolve quite a number of 2.0.x releated tickets so that most
likely the next bugfix version 2.0.9 will be released this month as well
## Board feedback (comment from the last october board meeting)
mt: Reading the "2.0.7 release" thread on private@ it appears that the
project is dependent on a single committer for at least a sub-set of
regression tests. Could you explain this in more detail please. If there are
tests the community depends on, I'd expect to see those tests in an ASF
repository where any committer can run them.
These tests are not classic regression tests but tests on a large amount (>
500000) of files. The results are compared to the results of a previous
version and then committers investigate files with some extreme negative
differences or with new exceptions. The same is done (on an even larger scale)
for Tika, see [1] and [2]. The Tika tests need 4TB, and the files can't be
hosted on a public ASF repo or released under the Apache License because the
files largely derive from Common Crawl or the internet generally, and
copyright/licensing would pose a problem. There is a special vm to host the
described test and it is possible to grant access to all interested
Tika/PDFBox committers. Tilman already got his access bits in december, so
that at least one other committer is able to run those tests if needed. Maybe
others will follow.
[1]
http://events.lin uxfoundation.org/sites/events/files/slides/ApacheConMiami2017_tallison_v2.pdf
[2]
http://o penpreservation.org/blog/2016/10/04/apache-tikas-regression-corpus-tika-1302/
## Health report:
- there is a steady stream of contributions, bug reports and questions on the
mailing lists
## PMC changes:
- Currently 21 PMC members.
- New PMC members:
- Joerg O. Henne was added to the PMC on Mon Oct 09 2017
- Sebastian Holder was added to the PMC on Wed Oct 11 2017
- Carolin Köhler was added to the PMC on Wed Oct 11 2017
- Matthäus Mayer was added to the PMC on Mon Oct 16 2017
## Committer base changes:
- Currently 21 committers.
- Joerg O. Henne was added as a committer on Mon Oct 09 2017
- Sebastian Holder was added as a committer on Wed Oct 11 2017
- Carolin Köhler was added as a committer on Wed Oct 11 2017
- Matthäus Mayer was added as a committer on Mon Oct 16 2017
## Releases:
- 2.0.8 was released on Thu Nov 02 2017
## JIRA activity:
- 101 JIRA tickets created in the last 3 months
- 75 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment BI: 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:
- Infrastructure has unincubated--all Git repos now have incubator-prefix
removed.
- Started a discussion for 2018 goals.
## 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.
- Next release planned for the end of January 2018.
## JIRA activity:
- 11 JIRA tickets created in the last 3 months
- 0 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment BJ: 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/fix security related issues and working to
integrate with latest hadoop releases.
- Jira: +120(added) -110(resolved) over last 3 months
- Git (Source): 126 (branch:master,ranger-0.7) commits over last 3 months
## Health report:
- Working on few (non CVE) security issues raised by security@apache - will
be released in upcoming releases
- Finalizing the next release details within community
## PMC changes:
- Currently 18 PMC members.
- Abhay Kulkarni was added to the PMC on Fri Dec 15 2017
## Committer base changes:
- Currently 26 committers.
- Zsombor Gegesy was added as a committer on Sat Dec 09 2017
## Releases:
- Last release was Apache Ranger 0.7.1 on Tue Jun 06 2017
## Mailing list activity:
- dev@ranger.apache.org:
- 101 subscribers (up 2 in the last 3 months):
- 1353 emails sent to list (1561 in previous quarter)
- user@ranger.apache.org:
- 169 subscribers (up 8 in the last 3 months):
- 68 emails sent to list (63 in previous quarter)
## JIRA activity:
- 120 JIRA tickets created in the last 3 months
- 110 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment BK: Report from the Apache Samza Project [Yi Pan]
## Description:
- Apache Samza is a distributed stream processing engine that are highly
configurable to process events from various data sources, including
real-time messaging system (e.g. Kafka) and distributed file systems (e.g.
HDFS).
## Issues:
There were comments from board members requesting answers from PMC in the last
report. I have answered in an email earlier. Just to include the answers again
since it seems to be asked multiple times:
Board questions: jj: I am assuming the LinkedIn meet up occurred?
rb: I'm very concerned that Mark has asked a question two quarters in a row
and still received no response. It's not even so much that the question
itself is urgent, but that you don't appear to be reading board feedback to
your reports.
ps: The 9/12 meetup at LinkedIn was announced on the dev list on 8/24 and
9/12. It appears to have been open to all interested parties. Attendance
does appear to have required an NDA signed by attendees. It looks more like
info share than anything actually project dev related. Here is the link from
the mail to the dev list:
https://www.meetup.com/Stream-Processing-Meetup-LinkedIn/events/242656767/?_cookie-check=UErnFE0-NfeCLKWx
My previous answers to the above questions:
A. Yes, LinkedIn meetup was hold on 9/12
B. Yes we do read board's feedbacks and I have already responded with answers
to Marks question in July:
https://mail-search.apache.org/pmc/private-arch/samza-private/201707.mbox/%3CCAFvExu15wywrCpfcxEjUduC2nJs9UgFKCVyti5sFLQ7wi2moog@mail.gmail.com%3E
C. To restate what I have answered in my response to Board's feedback in July,
the meetup was announced via Meetup website, advertised via LinkedIn, tweet,
and Samza dev list. We share the usage information, discuss the features
needed and pain points user has encountered. Once a while, we also share our
development roadmap on big features coming in Samza. Those are all dev
related. Testimony in the exact link listed in the response, you can find the
following description in Redfin's presentation: "Samza is being used at
Redfin, and suggest some features that we'd like to see in Samza". And here is
another meetup where we talk about the roadmap of Samza development:
https://www.meetup.com/Stream-Processing-Meetup-LinkedIn/events/234454163/.
And new features like async API in Samza in yet another meetup:
https://www.meetup.com/Stream-Processing-Meetup-LinkedIn/events/237171557/,
and high-level API in Samza:
https://www.meetup.com/Stream-Processing-Meetup-LinkedIn/events/238303422/.
Hope that I have answered all your questions.
## Activity:
- We have another Stream Processing meetup in Dec 2017:
https://www.meetup.com/Stream-Processing-Meetup-LinkedIn/events/244889719/
- Samza talk in BigDataSpain'17: Nov 2017 - Unified Stream Processing at
Scale with Apache Samza
## Health report:
- Project is in healthy status with a lot of development activities in
continuation (e.g. SamzaSQL, table API, Samza-on-Azure, Kinesis consumer)
- Promotion of new PMC member in progress
## PMC changes:
- Currently 13 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Jagadish Venkatraman on Thu Sep 14 2017
## Committer base changes:
- Currently 18 committers.
- No new committers added in the last 3 months
- Last committer addition was Boris Shkolnik at Mon Oct 02 2017
## Releases:
- 0.14.0 was released on Thu Jan 04 2018
## Mailing list activity:
- dev@samza.apache.org:
- 293 subscribers (up 0 in the last 3 months):
- 263 emails sent to list (288 in previous quarter)
## JIRA activity:
- 102 JIRA tickets created in the last 3 months
- 78 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment BL: Report from the Apache Sqoop Project [Jarek Jarcec Cecho]
## Description:
Apache Sqoop is a tool designed for efficiently transferring bulk data between
Apache Hadoop and structured datastores such as relational databases. It can
be used to import data from external structured datastores into Hadoop
Distributed File System or related systems like Hive and HBase. Conversely,
Sqoop can be used to extract data from Hadoop and export it to external
structured datastores such as relational databases and enterprise data
warehouses.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
Development activity continues mainly on the trunk branch.
## Health report:
The community is healthy; we see new contributors showing up and contributing
to the project.
## PMC changes:
- Currently 16 PMC members.
- We’ve added new PMC member (Abraham Fine) in November 2016
## Committer base changes:
- Currently 31 committers.
- Vasas Szabolcs was added as a committer on Tue Nov 14 2017
## Releases:
- 1.99.7 was released on Sun Aug 07 2016
- We’re working towards 1.4.7 release
## JIRA activity:
- 30 JIRA tickets created in the last 3 months
- 19 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment BM: Report from the Apache Steve Project [Daniel Gruno]
## Description:
Apache STeVe is Apache's Python based voting system that the Foundation
uses to handle things like voting in our new Board of Directors.
## Activity:
No activity of note this period. Activity is expected to pick up in the
coming months as the annual members meeting is anticipated, but prior
to and following the meeting. Some off-list interests in the project
(namely hacking a bit on it) have been received - we'll see if this
results in actual participation or not :)
## Community health:
Community remains the same as last period, no changes. We conducted a
poll on the PMC last period and concluded there was sufficient
oversight on the project. That remains true.
## Releases:
No official releases have been made yet. We will likely be reviewing
this after the annual meeting and decide on whether to craft a release
or not. Having a release might help add users/developers and grow the
community.
## PMC changes:
- Currently 5 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Rich Bowen on Mon Apr 20 2015
## Committer base changes:
- Currently 9 committers.
- No new committers added in the last 3 months
- Last committer addition was Pierre Smits at Tue Dec 15 2015
-----------------------------------------
Attachment BN: Report from the Apache Streams Project [Steve Blackmon]
## Description:
- Apache Streams unifies a diverse world of digital profiles and online
activities into common formats and vocabularies, and makes these datasets
accessible across a variety of databases, devices, and platforms for
streaming, browsing, search, sharing, and analytics use-cases.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- We have completed all known PMC setup, infra, code, and website refactoring
work due to graduation.
- We now have streams.apache.org on CI/CD with no manual steps for the first
time ever.
- We have completed our first TLP release, Apache Streams 0.5.1.
- Apache Streams 0.5.1 adds code for interfacing with Twitter’s new account
activity and enterprise search APIs, and removes our dependency on the
external twitter4j project (which had a category X json.org dependency)
- Apache Kibble expressed interested in integrating Streams to collect social
media profiles and activity - a perfect use case and opportunity to grow the
community.
- Several new faces submitted and reviewed pull requests this quarter.
## Health report:
Streams graduated to TLP on July 19 2017. Activity and email traffic has been
light, but new features and platform improvements are happening at a steady
pace.
## PMC changes:
- None. There are currently 8 PMC members.
## Committer base changes:
- None. There are currently 8 committers.
## Releases:
- Apache Streams 0.5.1 was released on January 09, 2018
- We now have four experienced release managers on the PMC
## Mailing list activity:
21 Emails sent during these 92 days, up 0 (0%) compared to previous 92 days. 6
topics started during these 92 days, down 3 (-33%) compared to previous 92
days. 6 Participants during these 92 days, down 5 (-45%) compared to previous
92 days. Streams > Board Report - January 2018 > PonyMail.png
https://s.apache.org/GTrn
## JIRA Statistics:
36 new, 28 resolved Streams > Board Report - January 2018 > Jira.png
https://s.apache.org/plwc
## Website Traffic (3 month)
1141 sessions, up 20.11% compared to previous 3 months. 1014 users, up 17.77%
compared to previous 3 months. Streams > Board Report - January 2018 > Streams
Web Site Data January 2018.pdf https://s.apache.org/D0pl
## Upcoming Project Initiatives:
- Add official support for Schema.org and Activity Streams 2.0 data types.
- Consolidate streams-examples into primary streams repository, simplifying
deployment and release process.
- Drop remaining maven dependencies on java SDKs for accessing third-party
APIs in favor of HTTP/REST interfaces powered by Apache Juneau Remoteable
Annotations.
- More tweets and blog posts of zeppelin notebooks demonstrating data
pipelines and analyses based on Apache Streams.
- More official examples in source tree demonstrating integration of Apache
Streams with complementary technologies.
- Improve the interfaces by which components are created, configured,
activated, and executed via SDK and CLI.
- Official Binaries and Containers that can be integrated with Apache Kibble.
- Reduce disparities between normalized activities and objects of like type
collected from various data sources.
- Reduce disparities between the configuration objects that initialize similar
providers from various data sources.
-----------------------------------------
Attachment BO: Report from the Apache Struts Project [René Gielen]
The Apache Struts MVC framework is a solution stack for creating elegant and
modern action-based Java web applications. It favors convention over
configuration, is extensible using a plugin architecture, and ships with
plugins to support technologies such as REST, AJAX and JSON.
The Struts team made two GA releases in the last quarter.
* Struts 2.5.14 - full GA release including bug fixes and feature enhancements
(2017-11-23)
* Struts 2.5.14.1 - security fix release (2017-11-30) [1][2]
In the last quarter the team was able to focus more on improvements and bug
fixes after having to mainly deal with security issues and communications in
the previous reporting period. We also noticed increased community
contributions, which we regard as a good sign.
We had to deal with a few security reports and resulting issues, that we were
able to cope with in a timely manner. The issues were mostly related to 3rd
party libraries used by the Struts framework.
The team chose to move our repositories to GitBox [3] and seems to be very
happy with this decision, as it helps to streamline our development efforts.
In the last quarter Yasser Zamani (yasserzamani) was added as a new committer
(2017-11-14). Stefaan Dutry (sdutry) accepted our invitation to join the
Struts PMC (2017-11-06).
We have no issues that require board assistance at this time.
[1] http://struts.apache.org/docs/s2-054.html
[2] http://struts.apache.org/docs/s2-055.html
[3] https://gitbox.apache.org/setup/
[4] http://struts.apache.org/docs/s2-049.html
-----------------------------------------
Attachment BP: Report from the Apache Tapestry Project [Thiago Henrique De Paula Figueiredo]
## Description:
- Apache Tapestry is a Java component-based web framework that features high
productivity, great code reuse, robust deployment, and terrific performance.
## Activity:
- It was a pretty slow quarter in terms of activity. Mailing list had an
increase in volume.
## PMC changes:
- Currently 11 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Bob Harner on Thu Apr 06 2017
## Committer base changes:
- Currently 26 committers.
- No new committers added in the last 3 months
- Last committer addition was Dmitry Gusev at Fri May 26 2017
- No new committers to be invited in sight.
## Releases:
- Last release was 5.4.3 on Sun Apr 23 2017
## JIRA activity:
- 6 JIRA tickets created in the last 3 months
- 7 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment BQ: Report from the Apache Tcl Project [Massimo Manghi]
## Description:
- Apache Tcl is home to the Tcl-Apache integration efforts.
The purpose of our project is to combine the power of the
Apache web server with the capabilities of the mature,
robust and flexible Tcl scripting language. Currently
only the Apache Rivet project is actively maintained
## Issues:
- no issues worth reporting to the board
## Activity:
- One more 2.3 artifact was released last November. A revision
of the manual for the soon to be released 3.0 is nearly completed
and we think a rivet 3.0.0 artifact will be proposed for release
very soon
## Health report:
- The project is healthy from the point of view of its internal life
but still its activity is relatively low, even though rivet 3.0
is a major rewriting of mod_rivet with a new design and support also
for Apache on Windows
## PMC changes:
- Currently 10 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Brice Hamon De Crevecoer on Tue Nov 25 2014
## Committer base changes:
- Currently 15 committers.
- No new committers added in the last 3 months
- Last committer addition was Brice B. Hamon at Tue Nov 25 2014
## Releases:
- rivet-2.3.5 was released on Sat Nov 11 2017
## Bugzilla Statistics:
- 1 Bugzilla tickets created in the last 3 months
- 0 Bugzilla tickets resolved in the last 3 months
-----------------------------------------
Attachment BR: Report from the Apache Tez Project [Siddharth Seth]
## Description:
Apache Tez is an effort to develop a generic application framework which
can be used to process arbitrarily complex directed-acyclic graphs (DAGs) of
data-processing tasks and also a re-usable set of data-processing primitives
which can be used by other projects.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
Trademark registration for TEZ was issued by the USPTO.
There was limited feature development, and some bug fixes which went in.
A 0.9.1 release has been in progress for some time.
## Health report:
Development activity continues to be slow, with features and bug fixes
going in as and when requried by projects which use Apache Tez.
## PMC changes:
- Currently 33 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Sreenath Somarajapuram on Tue May 03 2016
## Committer base changes:
- Currently 38 committers.
- No new committers added in the last 3 months
- Last committer addition was Kuhu Shukla at Wed May 10 2017
## Releases:
- No releases in the last 3 months.
## JIRA activity:
- 30 JIRA tickets created in the last 3 months
- 23 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment BS: Report from the Apache Thrift Project [Jake Farrell]
Apache Thrift is a framework for providing cross-platform RPC and serialization.
Project Status
---------
The Apache Thrift community is happy to announce the availability of our
0.11.0 release which includes a number of stability and performance
enhancements to our client libraries. We have plans to follow up our 0.11.0
release with a 0.11.1 point release which will address a potential security
vulnerability and following that start progress towards updating our build
system from Autotools to CMake.
Community
---
Latest Additions:
* PMC addition: James King, 11.2.2017
* Committer addition: James King, 10.18.2016
Issue backlog status since last report:
* Created: 96
* Resolved: 77
Mailing list activity since last report:
* @dev 2098 messages
* @user 67 messages
Releases
---
Last release: 0.11.0, Release Date: 12.6.2017
-----------------------------------------
Attachment BT: Report from the Apache Tika Project [David Meikle]
## Description:
Apache Tika is a dynamic toolkit for content detection, analysis, and
extraction. It allows a user to understand, and leverage information from, a
growing a list over 1200 different file types including most of the major
types in existence (MS Office, Adobe, Text, Images, Video, Code, and science
data) as recognised by IANA and other standards bodies.
## Issues:
- There are no issues that require the board's attention at this time.
## Board Questions:
- mt: Why was the "2.0.6 release" thread on private@ ? It looks as if it
could/should have been on dev@
- It started off on dev@ but it looks like Tim was trying to ask can it be
pushed ahead of ApacheCon and 'moved' it on private@
- We will avoid this in the future.
- bd: Note that the names of people who haven been invited to join the PMC
but haven't replied yet shouldn't be included in reports, in case they
decline.
- Apologies, will note this for the future.
## Activity:
- Apache Tika 1.17 was released in December with key updates including:
- Automatic image captioning
- Phonetic run handling in Excel and Word
- Many bug fixes and improvements
- We've now changed our repository with master now focusing on the 2.x series
- Discussion has now started on some of the key changes previously discussed
in the Tika 2.0 roadmap[1]
- Sergey Beryozkin's TikaIO Apache Beam component has now stabalised and will
be available in Beam 2.3.0
## PMC changes:
- Currently 29 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Madhav Sharan on Thu Aug 31 2017
## Committer base changes:
- Currently 30 committers.
- No new committers added in the last 3 months
- Last committer addition was Madhav Sharan at Thu Aug 31 2017
## Releases:
- 1.17 was released on Wed Dec 13 2017
## Mailing list activity:
- dev@tika.apache.org:
- 196 subscribers (down -4 in the last 3 months):
- 582 emails sent to list (592 in previous quarter)
- user@tika.apache.org:
- 349 subscribers (down -3 in the last 3 months):
- 76 emails sent to list (35 in previous quarter)
## JIRA activity:
- 71 JIRA tickets created in the last 3 months
- 39 JIRA tickets closed/resolved in the last 3 months
[1] https://wiki.apache.org/tika/Tika2_0RoadMap
-----------------------------------------
Attachment BU: Report from the Apache TinkerPop Project [Stephen Mallette]
## Description:
Apache TinkerPop is a graph computing framework for both graph databases
(OLTP) and graph analytic systems (OLAP).
## Activity:
TinkerPop released versions 3.2.7 and 3.3.1 in this last reporting cycle.
Both were basically maintenance releases as a whole, but both included the
first official convenience releases of Gremlin.Net for the .NET community
(prior versions were just release candidates). Development has started on
the next releases in 3.2.8 and 3.3.2. These releases will again focus on
bug fixes, but may include initial support for gremlin-javascript which
will allow the Javascript community to have more native support for
TinkerPop in their language.
In the wider TinkerPop community, Amazon announced their new TinkerPop
enabled graph database called Neptune[1]. In a separate announcement, we
have also learned that Microsoft's Azure Cosmos DB is now ready for general
availability[2]. Finally, it was learned that the Bitsy[3] graph database
and the Pixy[4] graph pattern matching and logic programming language have
both been upgraded to support the latest version of TinkerPop 3.x (these
pieces of software were originally developed on TinkerPop 2.x years ago,
which is not compatible at all with 3.x so it was nice to see them available
to users again).
TinkerPop has a new committer with the addition of Kelvin Lawrence.
## Issues:
There are no issues requiring board attention at this time.
## Releases:
- 3.2.7 (December 17, 2017)
- 3.3.1 (December 17, 2017)
## PMC/Committer:
- Last PMC addition was Robert Dale - April 2017
- Last committer addition was Kelvin Lawrence - December 2017
## Links
[1] https://aws.amazon.com/neptune/
[2] https://s.apache.org/yTRH
[3] https://github.com/lambdazen/bitsy
[4] https://github.com/lambdazen/pixy
-----------------------------------------
Attachment BV: Report from the Apache Tomcat Project [Mladen Turk]
## Description:
- A Java Servlet, JavaServer Pages, Java WebSocket and Java
Unified Expression language specifications implementation.
## Issues:
- There are no issues requiring board attention at this time
## Activity:
- Continued healthy activity across multiple components and
responsiveness on both dev and user lists.
- The Tomcat event in London went very well and funds were
set aside for future similar events. The event logs were made
available on the http://tomcat.apache.org/presentations.html
page on the website.
- Similar to the TomcatCon one day event in London, another
community conference event is pencilled in for Spring,
probably in Frankfurt.
- Tomcat 9 milestone cycle ended following the release of the
new Servlet 4.0 specification, and a beta release cycle has
started.
- The community is exploring switching from svn to git. We have
identified a number of questions / issues and are working through
those on the dev@ list prior to the actual migration.
- The community is starting to look at building out some ALv2
licensed training material which could then be used in some
future events.
## PMC changes:
- Currently 26 PMC members.
## Committer base changes:
- Currently 44 committers.
## Releases:
- Apache Tomcat 7.0.82 was released on Oct 3 2017
- Apache Tomcat 8.0.47 was released on Oct 3 2017
- Apache Tomcat 8.0.48 was released on Dec 12 2017
- Apache Tomcat 8.5.21 was released on Sep 19 2017
- Apache Tomcat 8.5.23 was released on Oct 3 2017
- Apache Tomcat 8.5.24 was released on Dec 1 2017
- Apache Tomcat 9.0.0.M27 was released on Sep 19 2017
- Apache Tomcat 9.0.1 Beta was released on Oct 3 2017
- Apache Tomcat 9.0.2 Beta was released on Dec 1 2017
## Trademark:
- No new trademark issues in the last 3 months
and there are currently no outstanding trademark issues that the
Apache Tomcat PMC is working on.
- Detailed history is available at:
https://svn.apache.org/repos/private/pmc/tomcat/trademark-status.txt
## Security:
- Detailed status:
http://tomcat.apache.org/security.html
- Important: Security Constraint Bypass CVE-2017-7675
Versions Affected:
Apache Tomcat 9.0.0.M1 to 9.0.0
Apache Tomcat 8.5.0 to 8.5.22
Apache Tomcat 8.0.0.RC1 to 8.0.46
Apache Tomcat 7.0.0 to 7.0.81
When running with HTTP PUTs enabled (e.g. via setting the readonly
initialisation parameter of the Default servlet to false) it was
possible to upload a JSP file to the server via a specially crafted
request. This JSP could then be requested and any code it contained
would be executed by the server.
-----------------------------------------
Attachment BW: Report from the Apache TomEE Project [David Blevins]
## Description:
Apache TomEE delivers enterprise application containers and services
based on, but not limited to the Enterprise JavaBeans Specification
and Java Enterprise Edition Specifications.
## Activity:
Last Board Report was on Dec 20th, 2017 and due to holidays there is
not much activity to report, hence this report is brief. A reminder
to the Board, the project is taking focused efforts to increase
activity and enable potential committers. In the few days of the new
year we are seeing familiar faces who are not yet committers return
with a few PRs. In the last week the PMC has started discussion on a
potential committer. Both of which are good signs of a gradual
incline in activity.
TomEE 7 remains the most active branch with fixes periodically going
to TomEE 1.7.x.
## PMC changes:
- Currently 12 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Andy Gumbrecht on Tue Aug 11 2015
## Committer base changes:
- Currently 30 committers.
- 2 new committers added in the last 3 months
- Svetlin Zarev on Tue Oct 24 2017
- Jonathan S Fisher on Wed Nov 1 2017
-----------------------------------------
Attachment BX: Report from the Apache Traffic Server Project [Bryan Call]
## Description:
Apache Traffic Server is a HTTP and HTTP/2 proxy server and cache. What makes
ATS unique across the landscape of HTTP proxy caches is a focus on
extensibility (plugins), HTTP and HTTP/2 protocol conformity, and performance.
ATS is driving some of the largest CDNs in the world, delivering a significant
portion of all Internet traffic.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- We had a successful ATS Fall Summit, on 10/24 and 10/25, at Yahoo in
Sunnyvale. Over 70 people attended and we had guest speakers from Netflix
and Intel.
- We are planning to have our second ATS Reliability Summit in Cork Ireland
and are seeing a lot of interest for people attending in the ATS Community.
## Health report:
- We were working on releasing ATS 7.1.2 and it was delayed over the holidays.
The release is running in production for at least two large companies and
the vote passed on 1/10/18.
## PMC changes:
- Currently 41 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Gancho Tenev on Sun Jun 04 2017
## Committer base changes:
- Currently 53 committers.
- No new committers added in the last 3 months
- Last committer addition was Chenwei Song at Fri Jun 30 2017
## Releases:
- 7.1.2 was released on Wed Jan 10 2018
## Mailing list activity:
- The user mailing activity increased by 62% while the developer mailing
activity has been flat.
- users@trafficserver.apache.org:
- 498 subscribers (up 0 in the last 3 months):
- 227 emails sent to list (140 in previous quarter)
- dev@trafficserver.apache.org:
- 329 subscribers (down -2 in the last 3 months):
- 106 emails sent to list (106 in previous quarter)
- announce@trafficserver.apache.org:
- 16 subscribers (up 0 in the last 3 months):
- 0 emails sent to list (3 in previous quarter)
- issues@trafficserver.apache.org:
- 33 subscribers (up 0 in the last 3 months):
- 274 emails sent to list (246 in previous quarter)
- summits@trafficserver.apache.org:
- 15 subscribers (up 0 in the last 3 months)
## GitHub Issue activity:
- 63 issues created in the last 3 months
- 61 issues closed in the last 3 months
## Commit activity:
- 80,448 lines of code changed (down -60%)
- 501 commits (up 14%)
- 17 committer email addresses (up 0%)
- 54 author email addresses (up 17%)
-----------------------------------------
Attachment BY: Report from the Apache Trafodion Project [Pierre Smits]
## Description:
- Apache Trafodion extends the Apache Hadoop ecosystem to guarantee
transactional integrity and operational workloads for new kinds of Big Data
applications.
## Issues:
- there are no issues requiring board attention at this time
## Activity:
- During the last month the project worked to address graduation issues both
existing prior to the vote in the board meeting of Dec 2017 and created
after the establishment of the podling as a top-level project
- Working towards getting the establishment as a top-level project announced
in various ways (in collaboration with SK/press at apache.o)
- Our latest/last report submitted as being a podling (dec reporting round)
describes our activities:
-- New mentor added: Jacques Le Roux
-- Slowly attracting more adopters and subscribers.
-- Twitter: 228 followers, 73 tweets, 66 likes
## Health report:
- Given the details under the activity section, the PMC regards the project
as healthy.
- In the reporting month we expect to send out the graduation announcement,
and work towards making our next release available.
- Current report contains a mix of details from the last three months while
incubating, and some minor elements captured after being established as a
top-level project by the board, such as tickets and emails sent (or new
subscribers to project’s mailing lists) created after Dec 21st, 2017.
## PMC changes:
- Currently 11 PMC members.
- No new PMC members added in the last 3 months
- All elected PPMC Members (which came forward during graduation phase)
transitioned to PMC Members
## Committer base changes:
- Currently 18 committers.
- No changes (the PMC was established in the last 3 months)
- All elected podling committers transitions to committers of the established
project.
## Releases:
- during the last quarter we made no new release available to the public. Our
last release is from 2017-05-01, happened while being incubating
- We are working towards our next release, 2.2. Contributor Ming Liu is the
Release Manager.
This was already brought forward in the last quarter while incubating, but
did not gather - at the time - enough binding votes in general at
incubator.a.o.
## Mailing list activity:
- dev@trafodion.apache.org:
- 109 subscribers (up 14 in the last 3 months):
- 468 emails sent to list (299 in previous quarter)
- codereview@trafodion.apache.org:
- 27 subscribers (up 0 in the last 3 months):
- 463 emails sent to list (469 in previous quarter)
- issues@trafodion.apache.org:
- 40 subscribers (up 0 in the last 3 months):
- 771 emails sent to list (596 in previous quarter)
- user@trafodion.apache.org:
- 110 subscribers (up 8 in the last 3 months):
- 48 emails sent to list (37 in previous quarter)
- private@trafodion.apache.org
- 21 subscribers
- currently no automated insights provided by ComDev-reporter services.
Will be taken up with the project.
## JIRA activity:
- 118 JIRA tickets created in the last 3 months
- 82 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment BZ: Report from the Apache VXQuery Project [Till Westmann]
Description:
Apache VXQuery implements a parallel XML Query processor.
Activity:
- A paper on the JSONiq extension for XQuery implemented in VXQuery
"A Parallel and Scalable Processor for JSON Data" was accepted for
publication in EDBT 2018.
- Very low activity otherwise.
- Still no new release.
Issues:
- There are no issues that require the board's attention at this time.
PMC/Committership changes:
- Currently 12 committers and 7 PMC members in the project.
- Last PMC addition was Steven Jacobs at Jul 18, 2014.
- Last committer additions were Riyafa Abdul Hameed and Christina Pavlopoulou
on Aug 22, 2016.
Releases:
- Last release was 0.6 on May 26 2016
-----------------------------------------
Attachment CA: Report from the Apache Web Services Project [Daniel Kulp]
Apache Web Services is a collection of shared technologies related to
SOAP/XML based Web Services that can be shared by different implementations.
Spring-WS, Axis2, CXF, and others use parts of the technology created within
Apache Web Services.
Community:
WebServices is a mature project based on standards that are also quite
mature. As such, there is not a significant amount of activity required.
However, user questions are being answered promptly, bugs are being fixed,
and there are at least 3 independent PMC members around making sure
the project can continue to produce releases as needed. Since
SOAP/XML based Web Services is no longer considered state of the art,
we don’t expect a major uptick in new development efforts, new
committers, etc...
With the holidays, not much has happened at all since we filed the special
report for the Decemeber board meeting. There have been a few commits
to wss4j as we prepare a new patch release there and some cleanup
commits in Axiom, but not much else.
Last committer addition: Sun Sep 14 2014 (Alessio Soldano)
Last PMC addition: Tue May 17 2016 (Alessio Soldano)
Releases this period:
WSS4J - implementation of WS-Security and related technologies
* 2.1.11 - Sept, 2017
* 2.2.0 - Sept, 2017
Last releases for other technologies:
* Axiom 1.2.20 : Oct 2016 (StAX-based, XML Infoset compliant object model)
* Woden 1.0M10 : Sept 2015 (WSDL 2.0 implementation)
* Neethi 3.1.0 - May 2017 (WS-Policy framework)
* XmlSchema 2.2.2 - May, 2017 (XML Schema framework)
-----------------------------------------
Attachment CB: Report from the Apache Zeppelin Project [Lee Moon Soo]
## Description:
- Apache Zeppelin is a collaborative data analytics and visualization tool
for general-purpose data processing systems.
## Issues:
- No issues
## Activity:
- Community is planning on 0.8.0 release
## Health report:
- Steady increment of number of code contributors. +12 since last report, 246
total
## PMC changes:
- Currently 10 PMC members.
- Last PMC addition was Ahyoung Ryu on Thu Jun 29 2017
- A new PMC invitation in progress
## Committer base changes:
- Currently 17 committers.
- Last committer addition was Park Hoon at Jun 22 2017
- A new committer invitation in progress
## Releases:
- 0.7.3 was released on Wed Sep 20 2017
- 0.7.2 was released on Mon Jun 12 2017
- 0.7.1 was released on Fri Mar 31 2017
- 0.7.0 was released on Sun Feb 05 2017
- 0.6.2 was released on Fri Oct 14 2016
- 0.6.1 was released on Aug 15 2016
- 0.6.0 was released on Jul 02 2016
- 0.5.6-incubating was released on Jan 22 2016
- 0.5.5-incubating was released on Nov 18 2015
- 0.5.0-incubating was released on Jul 23 2015
## Mailing list activity:
- users@zeppelin.apache.org:
- 716 subscribers (down -3 in the last 3 months):
- 292 emails sent to list (347 in previous quarter)
- dev@zeppelin.apache.org:
- 330 subscribers (down -2 in the last 3 months):
- 1221 emails sent to list (1703 in previous quarter)
## JIRA activity:
- 146 JIRA tickets created in the last 3 months
- 71 JIRA tickets closed/resolved in the last 3 months
------------------------------------------------------
End of minutes for the January 17, 2018 board meeting.
Index