Index
Links: 2018 - All years
- Original The Apache Software Foundation
Board of Directors Meeting Minutes
September 19, 2018
1. Call to order
The meeting was scheduled for 10:30am Pacific and began at 10:33
when a sufficient attendance to constitute a quorum was
recognized by the chairman.
Other Time Zones: https://timeanddate.com/s/3kp9
The meeting was held via teleconference, hosted by Doug Cutting
and Cloudera.
IRC #asfboard on irc.freenode.net was used for backup purposes.
2. Roll Call
Directors Present:
Rich Bowen
Shane Curcuru
Bertrand Delacretaz
Isabel Drost-Fromm
Ted Dunning - left at 11:52
Roman Shaposhnik
Phil Steitz
Mark Thomas
Directors Absent:
Brett Porter
Executive Officers Present:
Ross Gardler
Tom Pappas
Sam Ruby
Daniel Ruggeri
Craig L Russell
Matt Sicker
Executive Officers Absent:
Ulrich Stärk
Guests:
Andrew Musselman
Daniel Gruno
Greg Stein
Jim Jagielski
Kevin A. McGrail
Pierre Smits
Sally Khudairi
3. Minutes from previous meetings
Published minutes can be found at:
http://www.apache.org/foundation/board/calendar.html
A. The meeting of August 15, 2018
See: board_minutes_2018_08_15.txt
Approved by General Consent.
4. Executive Officer Reports
A. Chairman [Phil]
This month's reports show a huge amount of activity, some of the usual
challenges and some solid progress addressing community challenges.
The following reports were acknowledged to include good examples /
strategies that other communities could learn from: Beam, Mynewt,
Incubator and Storm. Constructive feedback included the following
items:
* Reminder to always use links to lists.apache.org for mail archive
references
* Reminder to enclose sensitive items in <private> markers (since
board reports become public when minutes are published)
* Reminder to always include the date of the last release and last
committer and PMC additions
My personal focus last month was on getting started on the 5-year plan
refresh and continuing research into nonprofit finance best practices.
Watch members@ for updates.
B. President [Sam]
Additionally, please see Attachments 1 through 7.
C. Treasurer [Ulrich]
Virtual Report:
Here is a summary of the Foundation’s Financial performance for the
first four months of FY19;
Operating Cash on Aug 31st, 2018 was $2,055.3K, which is up $12.8K
from last month’s ending balance (Jul 18) of $2,042.5K. Total Cash
as of Aug 31st, 2018 is $3,448.1K ( includes the Pineapple and
restricted Donation). The Aug 2018 ending Operating cash balance of
$2,055.3K represents an Operating cash reserve of 13 months based on
the FY19 conservative Cash forecast average monthly spending of
$158K/month. The ASF actual reserve of 13 months at the end of Aug
2018 is ahead of the budgeted 10.2 month reserve for YTD through Aug
2018. The ASF Operating reserve continues to be very healthy for an
organization of the ASF’ s size and Operating activity.
Reviewing the YTD Cash P&L, the ASF, with regard to Income, was
ahead vs the FY19 budget but behind where we were at this time in
FY18. With regard to the Income vs Budget, YTD, we are up $157.6K
in total. Compared to FY18 the variance continues to be the timing of
when Platinum Sponsor payments arrived in FY18 vs FY19. We are
however now ahead in donation income, due to the Handshake
contribution, which has offset the timing variance of some
sponsorship payments, as compared to the FY19 budget YTD.
YTD expenses, through Aug 31st, 2018 are under budget by $295.6K,
with all depts being under budget. Infra as noted in the Board
summary is $87K under budget due to Timing of hiring of staff and
timing of Lease web invoices. The other major timing issue is
Conferences is under by $118.8K, which as we draw near the ACNA 2018
it will resolve itself . We have moved most of the dept
underspending forward in the Cash forecast and will be reviewing the
underspending with the departments as we move forward in FY19 Q2.
Regarding Net Income (NI), YTD FY 19 the ASF finished with a -
<$.783> NI (or Breakeven YTD FY19) vs a budgeted negative <$453.9K>
NI or $453.1K ahead of Budget, NI, for FY19 at this point in the
Fiscal year. This was attributable to timing of Sponsor payments
offset by more Donations than were budgeted as well as underspending
in all depts YTD, vs the FY19 Budget. At this point in the FY we are
doing well, ahead in Revenue and well under budget in Expenses. We
will continue to monitor this as we move further into FY19.
Current Balances:
Boston Private CDARS Account 2,250,000.00
Citizens Money Market 967,166.57
Citizens Checking 227,279.59
Paypal - ASF 3,695.77
Total Checking/Savings 3,448,141.93
Aug-18 Budget Variance
Income Summary:
Inkind Revenue 0.00 0.00 0.00
Public Donations 121,408.32 2,979.02 118,429.30
Sponsorship Program 25,000.00 0.00 25,000.00
Event Revenue 11,250.00 0.00 11,250.00
Programs Income 0.00 0.00 0.00
Conference Income 0.00 0.00 0.00
Other Income 0.00 505.94 -505.94
Interest Income 526.98 1,162.09 -635.11
Total Income 158,185.30 4,647.05 153,538.25
Expense Summary:
In Kind Expense 0.00 0.00 0.00
Infrastructure 70,083.83 82,128.32 -12,044.49
Programs Expense 0.00 0.00 0.00
Publicity 8,548.52 18,646.22 -10,097.70
Brand Management 2,392.55 8,166.67 -5,774.12
Conferences 49,785.62 90,000.00 -40,214.38
Travel Assistance Committee 0.00 10,000.00 -10,000.00
Fundraising 11,214.40 17,333.34 -6,118.94
Treasury Services 3,350.00 3,475.00 -125.00
General & Administrative 543.52 3,540.03 -2,996.51
Total Expense 145,918.44 233,289.58 -87,371.14
Net Income 12,266.86 -228,642.53 240,909.39
YTD FY19 Budget Variance
Income Summary:
Inkind Revenue 0.00 0.00 0.00
Public Donations 109,761.13 16,651.79 93,109.34
Sponsorship Program 280,371.47 310,000.00 -29,628.53
Event Revenue 81,800.00 0.00 81,800.00
Programs Income 0.00 0.00 0.00
Conference Income 0.00 0.00 0.00
Other Income 20,748.57 5,803.32 14,945.25
Interest Income 1,947.95 4,626.02 -2,678.07
Total Income 494,629.12 337,081.13 157,547.99
Expense Summpry:
In Kind Expense 0.00 0.00 0.00
Infrastructure 246,372.30 333,513.28 -87,140.98
Programs Expense 0.00 0.00 0.00
Publicity 108,586.20 120,213.67 -11,627.47
Brand Management 16,718.97 32,666.68 -15,947.71
Conferences 51,214.83 170,000.00 -118,785.17
Travel Assistance Committee 0.00 40,000.00 -40,000.00
Fundraising 54,201.15 69,333.36 -15,132.21
Treasury Services 16,035.00 16,050.00 -15.00
General & Administrative 2,283.50 9,206.50 -6,923.00
Total Expense 495,411.95 790,983.49 -295,571.54
Net Income -782.83 -453,902.36 453,119.53
D. Secretary [Craig]
The office of Secretary is running smoothly.
In August, 73 ICLAs, five CCLAs, and one grant were received and
filed.
E. Executive Vice President [Ross]
Infrastructure
=============
Infrastructure team have posted their open position, please help
amplify: https://s.apache.org/hiring2018
There was an extended downtown of around 60 hours due to a hardware
failure in our Jenkins master.
Marketing and Publicity
=======================
A number of F2F sponsor meetings at ApacheCon are being coordinated by
Sally, along with the on-boarding of two new Sponsor Ambassadors
(Craig Russell and Ted Liu).
Media and Analyst training will be available, for the 12th consecutive
year, at ApacheCon. All are encouraged to participate in this
excellent course.
Otherwise, business as usual.
Conferences
===========
The 20th anniversary edition of ApacheCon is almost upon us. This is a
"small one" by design (to keep the cadence going, and fill the gap
between two producers). Current registrations stand at 300 and
finances are healthy.
Special thanks to:
* Rich Bowen for coordinating
* Ruth Suehle, for "everything" (Ruth is bridging the gap between
producers)
* Kevin McGrail, for fundraising
* Sally Khudairi, for marketing assistance
* Sharan Foga, for organizing the ASF booth presence
* Trevor Grant, for being our on-site person for the booth
* Daniel Gruno, for printing, design, and other logistics
* Daniel Ruggeri, for booth assistance and other planning help
* Chris Dutz, who is hosting and maintaining our event schedule
system
DC Road Show, 2018 is confirmed for Dec 4, 2018. See
http://www.apachecon.com/usroadshow18/ CFP is open.
Proposed events (status in full report):
* JBCNConf, Barcelona, Spain
* ApacheCOn EU, 2019, Berlin, Germany
* Apache Roadshow Chicago, 2019
* ApacheCon North America 2019
Travel Assistance Committee
===========================
We have 10 (ten) TAC folks coming to ApacheCon - we ended up with 3
Visa rejections and so had to cancel 3 flights. Coordination with
planners around supporting roles for these people is underway.
F. Vice Chairman [Shane]
A common issue with communication comes up when contributors escalate
concerns or issues across communities or mailing lists; all too often
we spend additional volunteer cycles on tangents or how things are
written, instead of focusing on the root issue and what works best for
the ASF and our projects.
I've drafted "How To Escalate Issues At The ASF" under
board/escalation for discussion, as a specific guide for helping our
communities better discuss hard issues across different groups at the
ASF. Feedback welcome before wider publication & linking.
Executive officer reports approved as submitted by General Consent.
5. Additional Officer Reports
A. VP of W3C Relations [Andy Seaborne / Ted]
See Attachment 8
B. Apache Legal Affairs Committee [Chris Mattmann / Phil]
See Attachment 9
C. Apache Security Team Project [Mark J. Cox / Roman]
See Attachment 10
D. VP of Data Privacy [Chris Mattmann / Isabel]
See Attachment 11
Additional officer reports approved as submitted by General Consent.
6. Committee Reports
Summary of Reports
The following reports required further discussion:
# Lucene [ps]
# Security Team [rs]
# ServiceMix [rb]
# SpamAssassin [rb]
# Stanbol [rs]
# Xalan [rs]
A. Apache Allura Project [David Philip Brondsema / Mark]
See Attachment A
B. Apache Any23 Project [Lewis John McGibbney / Rich]
See Attachment B
C. Apache Archiva Project [Olivier Lamy / Brett]
See Attachment C
D. Apache Atlas Project [Madhan Neethiraj / Bertrand]
See Attachment D
E. Apache Aurora Project [Jake Farrell / Shane]
See Attachment E
F. Apache Axis Project [Robert Lazarski / Isabel]
See Attachment F
G. Apache Bahir Project [Luciano Resende / Rich]
See Attachment G
H. Apache Beam Project [Davor Bonaci / Roman]
See Attachment H
I. Apache Bigtop Project [Peter Linnell / Brett]
See Attachment I
J. Apache Bloodhound Project [Gary Martin / Ted]
No report was submitted.
@Ted: pursue a report for Bloodhound
K. Apache BVal Project [Matthew Jason Benson / Mark]
See Attachment K
L. Apache Camel Project [Andrea Cosentino / Phil]
See Attachment L
M. Apache Cayenne Project [Michael Ray Gentry / Bertrand]
See Attachment M
N. Apache Chemistry Project [Florian Müller / Shane]
See Attachment N
O. Apache CloudStack Project [Mike Tutkowski / Brett]
See Attachment O
P. Apache Commons Project [Gary D. Gregory / Shane]
See Attachment P
Q. Apache Cordova Project [Shazron Abdullah / Ted]
See Attachment Q
R. Apache cTAKES Project [Pei Chen / Mark]
See Attachment R
S. Apache Curator Project [Jordan Zimmerman / Roman]
See Attachment S
T. Apache Eagle Project [Edward Zhang / Isabel]
See Attachment T
U. Apache Falcon Project [Pallavi Rao / Bertrand]
See Attachment U
V. Apache Felix Project [Karl Pauls / Rich]
See Attachment V
W. Apache Flex Project [Tom Chiverton / Phil]
See Attachment W
X. Apache Flink Project [Stephan Ewen / Brett]
See Attachment X
Y. Apache Guacamole Project [Mike Jumper / Bertrand]
See Attachment Y
Z. Apache Gump Project [Stefan Bodewig / Rich]
See Attachment Z
AA. Apache HAWQ Project [Lei Chang / Roman]
See Attachment AA
AB. Apache Helix Project [Kishore G / Ted]
No report was submitted.
@Ted: pursue a report for Helix
AC. Apache Hive Project [Ashutosh Chauhan / Phil]
See Attachment AC
AD. Apache Incubator Project [Justin Mclean / Shane]
See Attachment AD
AE. Apache Jackrabbit Project [Michael Dürig / Mark]
See Attachment AE
AF. Apache Karaf Project [Jean-Baptiste Onofré / Isabel]
See Attachment AF
AG. Apache Labs Project [Danny Angus / Brett]
See Attachment AG
AH. Apache Lucene Project [Adrien Grand / Bertrand]
See Attachment AH
AI. Apache Lucene.Net Project [Shad Storhaug / Rich]
No report was submitted.
@Rich: pursue a report for Lucene.Net
AJ. Apache Marmotta Project [Jakob Frank / Phil]
See Attachment AJ
AK. Apache Mnemonic Project [Gang Wang / Roman]
See Attachment AK
AL. Apache Mynewt Project [Justin Mclean / Ted]
See Attachment AL
AM. Apache OFBiz Project [Jacopo Cappellato / Shane]
See Attachment AM
AN. Apache Olingo Project [Christian Amend / Mark]
No report was submitted.
AO. Apache OODT Project [Imesha Sudasingha / Isabel]
See Attachment AO
AP. Apache Open Climate Workbench Project [Michael James Joyce / Bertrand]
See Attachment AP
AQ. Apache OpenNLP Project [Jörn Kottmann / Shane]
See Attachment AQ
AR. Apache OpenWebBeans Project [Mark Struberg / Phil]
See Attachment AR
AS. Apache Pig Project [Koji Noguchi / Roman]
See Attachment AS
AT. Apache Pivot Project [Roger Lee Whitcomb / Mark]
See Attachment AT
AU. Apache Polygene Project [Jiri Jetmar / Rich]
No report was submitted.
AV. Apache Portable Runtime (APR) Project [Nick Kew / Isabel]
See Attachment AV
AW. Apache Portals Project [David Sean Taylor / Ted]
See Attachment AW
AX. Apache PredictionIO Project [Donald Szeto / Brett]
See Attachment AX
AY. Apache Royale Project [Harbs / Bertrand]
See Attachment AY
AZ. Apache Sentry Project [Alex Kolbasov / Brett]
See Attachment AZ
BA. Apache Serf Project [Bert Huijben / Shane]
See Attachment BA
BB. Apache ServiceMix Project [Krzysztof Sobkowiak / Ted]
See Attachment BB
BC. Apache Shiro Project [Les Hazlewood / Isabel]
See Attachment BC
BD. Apache Sling Project [Robert Munteanu / Mark]
See Attachment BD
BE. Apache SpamAssassin Project [Sidney Markowitz / Rich]
See Attachment BE
BF. Apache Stanbol Project [Fabian Christ / Roman]
No report was submitted.
@Roman: is this project still viable?
BG. Apache Storm Project [P. Taylor Goetz / Phil]
See Attachment BG
BH. Apache Synapse Project [Isuru Udana / Shane]
No report was submitted.
BI. Apache Tajo Project [Hyunsik Choi / Rich]
See Attachment BI
BJ. Apache Tiles Project [Michael Semb Wever / Brett]
See Attachment BJ
BK. Apache Tomcat Project [Mladen Turk / Roman]
See Attachment BK
BL. Apache Trafodion Project [Pierre Smits / Ted]
See Attachment BL
BM. Apache Twill Project [Terence Yim / Phil]
See Attachment BM
BN. Apache UIMA Project [Marshall Schor / Isabel]
See Attachment BN
BO. Apache Usergrid Project [Todd Nine / Bertrand]
No report was submitted.
BP. Apache VCL Project [Josh Thompson / Mark]
See Attachment BP
BQ. Apache Whimsy Project [Sam Ruby / Rich]
No report was submitted.
BR. Apache Wicket Project [Martijn Dashorst / Ted]
See Attachment BR
BS. Apache Xalan Project [Steven J. Hathaway / Roman]
See Attachment BS
@Roman: help the project with their request to add new
pmc/committers
BT. Apache Xerces Project [Michael Glavassevich / Mark]
See Attachment BT
BU. Apache Yetus Project [Allen Wittenauer / Bertrand]
See Attachment BU
BV. Apache ZooKeeper Project [Flavio Paiva Junqueira / Shane]
See Attachment BV
BW. Apache TinkerPop Project [Stephen Mallette / Isabel]
See Attachment BW
Committee reports approved as submitted by General Consent.
7. Special Orders
A. Change the Apache Serf Project Chair
WHEREAS, the Board of Directors heretofore appointed Bert
Huijben (rhuijben) to the office of Vice President, Apache
Serf, and
WHEREAS, the Board of Directors is in receipt of the
resignation of Bert Huijben from the office of Vice President,
Apache Serf, and
WHEREAS, the Project Management Committee of the Apache Serf
project has chosen by vote to recommend Branko Čibej (brane) as
the successor to the post;
NOW, THEREFORE, BE IT RESOLVED, that Bert Huijben is relieved
and discharged from the duties and responsibilities of the
office of Vice President, Apache Serf, and
BE IT FURTHER RESOLVED, that Branko Čibej be and hereby is
appointed to the office of Vice President, Apache Serf, 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 Serf Project Chair, was
approved by Unanimous Vote of the directors present.
B. Change the Apache Beam Project Chair
WHEREAS, the Board of Directors heretofore appointed Davor Bonaci
(davor) to the office of Vice President, Apache Beam, and
WHEREAS, the Board of Directors is in receipt of the resignation of
Davor Bonaci from the office of Vice President, Apache Beam, and
WHEREAS, the Project Management Committee of the Apache Beam project
has chosen by vote to recommend Kenneth Knowles (kenn) as the successor
to the post;
NOW, THEREFORE, BE IT RESOLVED, that Davor Bonaci is relieved and
discharged from the duties and responsibilities of the office of Vice
President, Apache Beam, and
BE IT FURTHER RESOLVED, that Kenneth Knowles be and hereby is appointed
to the office of Vice President, Apache Beam, 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 Beam Project Chair, was
approved by Unanimous Vote of the directors present.
C. Establish the Apache Pulsar Project
WHEREAS, the Board of Directors deems it to be in the best interests of
the Foundation and consistent with the Foundation's purpose to establish
a Project Management Committee charged with the creation and maintenance
of open-source software, for distribution at no charge to the public,
related to a highly scalable, low latency messaging platform running on
commodity hardware.
NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
(PMC), to be known as the "Apache Pulsar Project", be and hereby is
established pursuant to Bylaws of the Foundation; and be it further
RESOLVED, that the Apache Pulsar Project be and hereby is responsible
for the creation and maintenance of software related to a highly
scalable, low latency messaging platform running on commodity hardware;
and be it further
RESOLVED, that the office of "Vice President, Apache Pulsar" be and
hereby is created, the person holding such office to serve at the
direction of the Board of Directors as the chair of the Apache Pulsar
Project, and to have primary responsibility for management of the
projects within the scope of responsibility of the Apache Pulsar
Project; and be it further
RESOLVED, that the persons listed immediately below be and hereby are
appointed to serve as the initial members of the Apache Pulsar Project:
* Boyang Jerry Peng <jerrypeng@apache.org>
* Brad McMillen <bradtm@apache.org>
* David Fisher <wave@apache.org>
* Francis Christopher Liu <toffer@apache.org>
* Hiroyuki Sakai <hrsakai@apache.org>
* Ivan Brendan Kelly <ivank@apache.org>
* Jai Asher <jai1@apache.org>
* Jia Zhai <zhaijia@apache.org>
* Jim Jagielski <jim@apache.org>
* Joe Francis <joef@apache.org>
* Ludwig Pummer <ludwigp@apache.org>
* Masahiro Sakamoto <massakam@apache.org>
* Masakazu Kitajo <maskit@apache.org>
* Matteo Merli <mmerli@apache.org>
* Nozomi Kurihara <nkurihar@apache.org>
* P. Taylor Goetz <ptgoetz@apache.org>
* Rajan Dhabalia <rdhabalia@apache.org>
* Sahaya Andrews <andrews@apache.org>
* Sanjeev Kulkarni <sanjeevrk@apache.org>
* Sebastián Schepens <sschepens@apache.org>
* Siddharth Boobna <sboobna@apache.org>
* Sijie Guo <sijie@apache.org>
* Yuki Shiga <yushiga@apache.org>
NOW, THEREFORE, BE IT FURTHER RESOLVED, that Matteo Merli be appointed
to the office of Vice President, Apache Pulsar, to serve in accordance
with and subject to the direction of the Board of Directors and the
Bylaws of the Foundation until death, resignation, retirement, removal
or disqualification, or until a successor is appointed; and be it
further
RESOLVED, that the Apache Pulsar Project be and hereby is tasked with
the migration and rationalization of the Apache Incubator Pulsar
podling; and be it further
RESOLVED, that all responsibilities pertaining to the Apache Incubator
Pulsar podling encumbered upon the Apache Incubator PMC are hereafter
discharged.
Special Order 7C, Establish the Apache Pulsar Project, was
approved by Unanimous Vote of the directors present.
D. Change the Apache MyFaces Project Chair
WHEREAS, the Board of Directors heretofore appointed Mike Kienenberger
(mkienenb) to the office of Vice President, Apache MyFaces, and
WHEREAS, the Board of Directors is in receipt of the resignation of
Mike Kienenberger from the office of Vice President, Apache MyFaces,
and
WHEREAS, the Project Management Committee of the Apache MyFaces project
has chosen by vote to recommend Bernd Bohmann (bommel) as the successor
to the post;
NOW, THEREFORE, BE IT RESOLVED, that Mike Kienenberger is relieved and
discharged from the duties and responsibilities of the office of Vice
President, Apache MyFaces, and
BE IT FURTHER RESOLVED, that Bernd Bohmann be and hereby is appointed
to the office of Vice President, Apache MyFaces, to serve in accordance
with and subject to the direction of the Board of Directors and the
Bylaws of the Foundation until death, resignation, retirement, removal
or disqualification, or until a successor is appointed.
Special Order 7D, Change the Apache MyFaces Project Chair, was
approved by Unanimous Vote of the directors present.
E. Appoint Vice President, Legal Affairs
WHEREAS, the Board of Directors heretofore appointed Chris Mattmann
(mattmann) to the office of Vice President, Legal Affairs; and
WHEREAS, the Board of Directors is in receipt of the resignation of
Chris Mattmann from the office of Vice President, Legal Affairs; and
WHEREAS, Roman Shaposhnik has been nominated as a successor to the
post;
NOW, THEREFORE, BE IT RESOLVED, that Chris Mattman is relieved and
discharged from the duties and responsibilities of the office of Vice
President, Legal Affairs, and
BE IT FURTHER RESOLVED, that Roman Shaposhnik (rvs) be and hereby is
appointed to the office of Vice President, Legal Affairs, to serve in
accordance with and subject to the direction of the Board of Directors
and the Bylaws of the Foundation until death, resignation, retirement,
removal or disqualification, or until a successor is appointed.
Special Order 7E, Appoint Vice President, Legal Affairs, was
approved by Unanimous Vote of the directors present.
F. Establish Position of Assistant VP, Legal Affairs
WHEREAS, the Board of Directors deems it to be in the best interests
of the Foundation and consistent with the Foundation's purpose to
appoint an Assistant Vice President, Legal Affairs;
NOW, THEREFORE, BE IT RESOLVED that the office of "Assistant Vice
President, Legal Affairs" be and hereby is created, the person holding
such office to serve at the direction of the Board, and to share
responsibilities with and support the Vice President, Legal Affairs;
and be it further
RESOLVED, that Henri Yandell (bayard) be and hereby is appointed to
the office of Assistant Vice President, Legal Affairs, to serve in
accordance with and subject to the direction of the Board until
death, resignation, retirement, removal or disqualification, or
until a successor is appointed.
Special Order 7F, Establish Position of Assistant VP, Legal
Affairs, was approved by Unanimous Vote of the directors
present.
8. Discussion Items
A. Bylaws 4.5: Reinstatement of Membership of Emeritus Members
A suggestion has been made [1] to consider modifying Section 4.5 of the ASF
bylaws to make it easier to re-instate emeritus members.
[1]
https://lists.apache.org/thread.html/6c80a8fcc13ea99baf1b32afcc052bd815d57defe65cf36f1464855c@%3Cboard.apache.org%3E
@Phil: document process of reinstatement of emeritus members
9. Review Outstanding Action Items
* Brett: pursue a report or Attic proposal for Xalan
[ Xalan 2018-02-21 ]
Status: Complete: report was submitted
* Phil: work with infrastructure (Greg) on plans for projects with
extraordinary requirements
[ Action Items 2018-05-16 ]
Status: Discussion is ongoing.
* Brett: pursue a report for Stanbol
[ Stanbol 2018-06-20 ]
Status: not done
* Mark: Follow up with project as to current status
[ Creadur 2018-08-15 ]
Status: In progress
* Phil: follow up with IPMC on missing podling reports
[ Incubator 2018-08-15 ]
Status: Complete. September report shows strong progress.
* Ted: pursue a report for Marmotta
[ Marmotta 2018-08-15 ]
Status: Done: report was submitted this month.
* Brett: pursue a report for Open Climate Workbench
[ Open Climate Workbench 2018-08-15 ]
Status: present
* Jim: perhaps the httpd project would be willing to adopt mod_perl as a
[ Perl 2018-08-15 ]
Status: httpd would be willing to take over some bits of the project,
but not the whole kit and kaboodle
* Mark: pursue a report for Serf
[ Serf 2018-08-15 ]
Status: Complete. PMC reported in September.
* Isabel: is Usergrid ready for the attic?
[ Usergrid 2018-08-15 ]
Status:
* Phil: pursue a report for Xerces
[ Xerces 2018-08-15 ]
Status: Complete: report has been submitted.
* Phil: organize the agenda and synchronous meeting time
[ Synchronous meeting to kick off 5-year plan refresh 2018-08-15 ]
Status: Draft agenda was posted and a Doodle poll was set up to select
times. Have narrowed it down to 3 times in the first two weeks
of October.
10. Unfinished Business
11. New Business
12. Announcements
13. Adjournment
Adjourned at 12:14 p.m. (Pacific)
============
ATTACHMENTS:
============
-----------------------------------------
Attachment 1: Report from the VP of Brand Management [Mark Thomas]
* ISSUES FOR THE BOARD
None.
* OPERATIONS
Provided advice to SPARK regarding the naming the extensions listed on
their web site.
Responded to 6 requests (5 logos, 1 name) related to nominative use of
our marks.
Provided advice to MAHOUT regarding a naming potential conflict.
Approval was granted for the BEAM summit.
There are currently 26 tasks being tracked/monitored by the brand
management team.
* REGISTRATIONS
The agreement to transfer the NETBEANS marks has been signed and is now
with Oracle's counsel to progress the transfer.
The draft agreement for the transfer of the SERVICECOMB registrations is
being reviewed.
The work to transfer the BROOKLYN marks to the ASF appears to have
fallen though the cracks. It is being restarted.
* INFRINGEMENTS
Work continues to address a number of potential infringements.
-----------------------------------------
Attachment 2: Report from the VP of Fundraising [Daniel Ruggeri]
Fundraising is going well and our monthly committee meetings continue.
Event sponsorship for 2018 has topped $192K and ApacheCon and the DC Roadshow
are both expected to be in the black.
As of this month’s financials, we are within $1K of being break even and
$453K ahead of budget.
As promised, the Targeted Sponsorship Policy is completed
https://docs.google.com/document/d/1JhZEcty2fSx7ZxiBs41j3qOUrqsA7TvKmQ13ZZ61lJY/edit
We have a Sponsor Lunch planned during ApacheCon in Montreal
Daniel Ruggeri is working with Infra to automate access to G Suite.
Minor note: Open Graph Protocol has been implemented for ApacheCon.com. You
can see this if you post something on LinkedIn mentioning apachecon.com vs
apachecon.com/usroadshow18 vs http://apachecon.com/acna18/. Potentially
useful to look at the meta tags for this for other needs in the future.
-----------------------------------------
Attachment 3: Report from the VP of Marketing and Publicity [Sally Khudairi]
I. Budget: we are on budget and on schedule, with all vendor payments
up-to-date. We have had considerably more expenses than usual to accommodate
our participation in multiple events.
II. Cross-committee Liaison: Sally Khudairi continues Sponsor outreach
activities with Fundraising. She is coordinating several face-to-face meetings
with ASF sponsors at ApacheCon, and will be onboarding new Sponsor
Ambassadors Craig Russell and Ted Liu during ApacheCon as well. Her work with
ASF Conferences and Community Development includes promoting ApacheCon and
supporting the ASF’s participation in numerous community events. The latest
"Success at Apache" post: "赢在 Apache: If it helps others, all the better." is
now live https://s.apache.org/Et2y .
III. Press Releases: the following formal announcement was issued via the
newswire service, ASF Foundation Blog, or announce@apache.org during this
timeframe:
- 22 August: The Apache Software Foundation Announces Apache® HAWQ® as a
Top-Level Project
IV. Informal Announcements: 5 items were published on the ASF "Foundation"
Blog. 5 Apache News Round-ups were issued, with a total of 217 weekly
summaries published to date. We tweeted 32 items, and have 49.6K followers on
Twitter. We posted 10 items on LinkedIn, which garnered more than 39.9K
organic impressions.
V. Future Announcements: two announcements are in development. Projects
planning to graduate from the Apache Incubator as well as PMCs wishing to
announce major project milestones and "Did You Know?" success stories are
requested to contact Sally at <press@apache.org> with at least 2-weeks' notice
for proper planning and execution.
VI. Media Relations: we responded to 3 media queries. The ASF received 2,285
press clips vs. last month's clip count of 3,654. Media coverage of Apache
projects yielded 3,891 press hits vs. last month's 5,226. ApacheCon received
10 press hits.
VII. Analyst Relations: we received 2 analyst queries. Apache was mentioned in
7 reports by Gartner; 4 reports by Forrester; 4 reports by 451 Research; and 8
reports by IDC.
VIII. Graphics: Sally completed graphics production for ApacheCon and is
beginning a series of promotional assets for 2019 anniversaries.
IX. Events liaison: Sally augmented the digital ad campaigns for ApacheCon to
reflect the CFP for the Apache Roadshow DC. She is coordinating the ASF’s
presence at Huawei Connect and COSCon in China, which will be overseen by
several members of the Apache community, including Craig Russell, Justin
Mclean, and others. Sally will also be holding Media & Analyst Training at
ApacheCon for the 12th consecutive year. Two reporters will be attending
ApacheCon to participate in the training.
X. Newswire accounts: we have 9 pre-paid press releases remaining in our
contract with GlobeNewswire, which will auto-renew through December 2019.
# # #
-----------------------------------------
Attachment 4: Report from the VP of Infrastructure [David Nalley]
General
=======
Infrastructure is operating as expected, and has no current issues to
bring to the attention of the President or the Board.
Our job opening is now posted at https://s.apache.org/hiring2018
Short Term Priorities
=====================
- Establish a new DNS hidden master, deprecating that function from
our old minotaur.a.o server. This will also puppetize and trim the
domains that our instructure supports. The bulk of our owned domains
are handled by our domain provider.
Long Range Priorities
=====================
- Moving to Puppet 5, and to Ubuntu 18.04
General Activity
================
- Restored dSNMP monitoring, after our prior provider ended the
service. The tool is a F/OSS script pulled from GitHub.
- Rebuilt our logging storage/query service on new machines more
finely-tuned to the ElasticSearch installation. This expanded our
storage capacity from a single month to over a half-dozen.
- Various Jenkins node work (Windows, disk space, etc)
- Streamline git integration/config with ASF mailing lists, jira
Uptime Statistics
=================
We had an extended downtime (about 60 hours) after the backplane for
our Jenkins Master machine blew up. We were able to bring up a new
machine, get the build data moved over, and turned the service back
on. We picked up more storage space on the master, in the process.
-----------------------------------------
Attachment 5: Report from the VP of Conferences [Rich Bowen]
## ApacheCon North America 2018, Montreal
Date: September 24-27, 2018
Location: Montreal, Canada
URL: https://apachecon.com/acna18
We are, at meeting time, five days away from ApacheCon North
America 2018, the 20th anniversay edition of ApacheCon. This is
going to be a small one, so it is well to remember that this was
by design, not by accident. We intended to do a small event to
keep the cadence going, and fill the gap between two producers.
Ruth Suehle has stepped up and helped us bridge that divide, and
we expect an great, if small, event.
As of now (when I'm writing the report) we have just crossed the
300 mark in registrations. The hotel is *completely* full. We
are still substantially in the black, even with some unexpected
last minute costs. Many thanks to everyone involved, especially:
* Ruth Suehle, for everything
* Kevin McGrail, for fundraising
* Sally Khudairi, for marketing assistance
* Sharan Foga, for organizing the ASF booth presence
* Trevor Grant, for being our on-site person for the booth
* Daniel Gruno, for printing, design, and other logistics
* Daniel Ruggeri, for booth assistance and other planning help
* Chris Dutz, who is hosting and maintaining our event schedule
system
* All of our sponsors and speakers
Yes, I'm certain I'm forgetting lots of people.
Details about the event are at https://apachecon.com/acna18
## DC Road Show, 2018
Date: December 4, 2018
Location: Washington, DC, USA
URL: http://www.apachecon.com/usroadshow18/
Event lead: Kevin McGrail
The CFP for the DC Road has been opened, and notifications have been
sent out to our user and developer communities. Since it's a small
event, we anticipate a lot more submissions than spaces for that
content.
Planning discussions are ongoing, on the planners@apachecon.com
mailing list.
We are looking for speakers, and for a content committee. Please
subscribe to planners@apachecon.com if you are interested in
participate in the planning of this event.
## JBCNConf, 2019
Date: TBD
Location: Barcelona, Spain
URL: https://www.jbcnconf.com/
Event lead: Ignasi Barrera
JBCNConf is a Java event that is always heavy on Apache content. They
have proposed that we, the ASF, manage the content for a track or two,
and produce a co-branded event. Details are still sparse, but they're
looking at budget considerations and trying to find a date and venue.
This conversation will be brought back to the planners list soon,
since there are broader considerations that various people - notably
Sally and Kevin - have expressed concerns about.
## ApacheCon EU, 2019
Date: TBD
Location: Berlin, Germany
URL: https://apachecon.com/
Event lead: Rich/TBD
We have tentatively agreed to have NewThinking produce ApacheCon EU
2019 in Berlin. There are, however, no details yet. (NT are the folks
that produced the Berlin roadshow this year, in conjunction with
FOSSBackstage.)
If there's someone who lives in Berlin (or, at least, in Germany) who
wishes to step up to be event lead, I will gladly delegate this event.
Failing that, I (Rich) will be the event leadon this.
I hope that meetings with NT begin soon, but I have been completely
focused on ACNA18, and haven't really given it much thought yet.
## Apache Roadshow Chicago, 2019
Date: TBD
Location: Chicago, USA
URL: https://apachecon.com
Event lead: Trevor Grant
Trevor has sent a proposal for a roadshow in Chicago in 2019. He's
received a little pushback because what is proposed was a multi-track,
3 day event that looks much more like ApacheCon, and we are very
reluctant to have an event that directly competes with ApacheCon,
particularly in our 20th anniversary year. Details are still being
discussed, but it's very much taking a backseat to other more urgent
events.
## ApacheCon North America 2019
Date: TBD (September 2019?)
Location: TBD
URL: https://apachecon.com
Event lead: Rich Bowen
We are still looking for a venue for ACNA19, having determined that
the proposed venues were too small. We hope that our 20th anniversary
event is something that we can promote all year long and get a larger
than usual attendance turnout. Thus, we are looking at several cities
that are *not* in California.
We hope to announce ACNA19 at ACNA18, and are actively working towards
that goal, but it's looking iffy.
## Other Events
We still have silence regarding a Seoul event, but we haven't
attempted to rekindle that conversation since last month's meeting. If
there's someone interested in stepping up to drive this, please
contact Rich, or the planners list.
-----------------------------------------
Attachment 6: Report from the Apache Travel Assistance Committee [Gavin McDonald]
This report comes the week leading up to ApacheCon NA Montréal. Needless to
say, it is getting busy behind the scenes. All flight tickets are confirmed,
Hotel rooms sorted, Conference passes done.
We have 10 (ten) TAC folks coming - we ended up with 3 Visa rejections and so
had to cancel 3 flights (some sort or refund may be due in a few weeks.)
Note that confirmed flight reservation numbers are required as part of Visa
applications. We do not usually get this many Visa rejections, the norm is
either 0 or maybe 1. A routine inquiry with the travel agent proves once again
that is it still not worth us getting cancellation insurance for each ticket
as that far outweighs any loss incurred.
We are in communication with the planners folks to liaise what roles during
the week that TAC folks can assist with.
We look forward to another successful event!
-----------------------------------------
Attachment 7: Report from the VP of Finance [Tom Pappas]
Aug 2018 Report for VP Finance. As was the case in July there was not
much activity, though the Document from the AAFCPA's Wealth Management
firm arrived and I will be sharing it with the Board on the Board list
before the Board meeting.
-----------------------------------------
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]
We're moving ahead with the plan proposed last month:
1. Create an Assistant VP, Legal position and nominate Henri
Yandell
to this position.
2. Appoint Roman Shaposhnik to a position of Vice President, Legal
Affairs
Both resolutions have been submitted as separate items for the board
consideration. Huge kudos go to Chris for ensuring smooth transition
and making himself available until the end of 2018.
We see usual amount (roughly a couple per week) of Q&A happening
on the legal mailing list and LEGAL jira. All of these are being
handled with great support from Hen Yandell and others on the Legal
discuss list.
Chris is still working with VP, Infra and the office of Data Privacy
to draft a data privacy plan and set of updates to the ASF mailing
list archival removal policy owned by the infra team.
The only big in-bound item requiring us to formulate an externally
visible response this month is a request from a European Commission
in a Case M.8994 "MICROSOFT / GITHUB" This is being handled in a
timely manner but may require involvement of our legal counsel.
-----------------------------------------
Attachment 10: Report from the Apache Security Team Project [Mark J. Cox]
Continued work on incoming security issues, keeping projects reminded
of outstanding issues, and general oversight and advice.
Current clean-up focus is on issues that are more than 90 days old
where no CVE name is yet assigned (therefore still in "investigation"
state). There are currently 10 of these across 8 projects.
Stats for August 2018:
13 [license confusion]
24 [support request/question not security notification]
Security reports: 37 (last months: 32, 39, 55)
3 [couchdb], [httpd], [spamassassin]
2 [commons], [nifi], [struts], [tomcat], [trafficserver]
1 [accumulo], [activemq], [allura], [fineract], [hive],
[karaf], [netbeans], [ofbiz], [openoffice], [qpid],
[ranger], [shiro], [spark], [storm], [subversion],
[thrift], [zookeeper], [site]
In total, as of 1st September, we're tracking 89 (last month: 95)
open issues across 42 projects, median age 113 (last month: 112)
days. 56 of those issues have CVE names assigned.
8 (last month: 9) of these issues, across 7 projects, are older
than 365 days. We continue to work with these projects to get
these closed out.
-----------------------------------------
Attachment 11: Report from the VP of Data Privacy [Chris Mattmann]
Nothing much to report this month other than still working on the Privacy
Draft. For those interested, contact myself or VP, Infra to see a draft.
-----------------------------------------
Attachment A: Report from the Apache Allura Project [David Philip Brondsema]
## Description:
Apache Allura is an open source implementation of a software forge, a web site
that manages source code repositories, bug reports, discussions, wiki pages,
blogs, and more for any number of individual projects.
## Issues:
- No issues needing board attention.
## Activity:
- Google Summer of Code student Deshani worked on a personal dashboard this
summer
- Various improvements and fixes continue
- A few new users/devs have been active on our list & tickets.
## Health report:
- GSoC student Deshani was added to committers & PMC. And continues to make
contributions after GSoC
- A different new contributor has been getting involved quite recently too.
## PMC changes:
→ Deshani Geethika was added to the PMC on Sun Jul 22 2018
→ Last PMC addition: Sun Jul 22 2018 (Deshani Geethika)
→ Currently 15 PMC members.
## Committer base changes:
→ Deshani Geethika was added as a committer on Mon Jul 23 2018
→ Last committer addition: Mon Jul 23 2018 (Deshani Geethika)
→ Currently 15 committers.
## Releases:
- 1.8.1 was released on Tue Mar 13 2018
-----------------------------------------
Attachment B: Report from the Apache Any23 Project [Lewis John McGibbney]
## Description:
Anything To Triples (Any23) is a library, a web service and a command line
tool that extracts structured data in RDF format from a variety of Web
documents.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
We continue to see positive project activity with active development and
mailing lists. Our GSoC project finished very well and we intend to merge in
the contribution after the pending Any23 2.3 release. We may release 2.4
shortly after that... who knows.
## Health report:
Any23 is looking in fair shape. We are enjoying the project getting better as
time goes on.
## PMC changes:
- Currently 15 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Hans Brende on Sun Feb 25 2018
## Committer base changes:
- Currently 15 committers.
- No new committers added in the last 3 months
- Last committer addition was Hans Brende at Wed Feb 21 2018
## Releases:
- Last release was 2.2 on Mon Mar 26 2018
## Mailing list activity:
Unfortunately we lost one person from user@, however once we make our next
release, hopefully we will add to users. dev@ is where it is all happening.
- dev@any23.apache.org:
- 39 subscribers (up 0 in the last 3 months):
- 534 emails sent to list (334 in previous quarter)
- user@any23.apache.org:
- 50 subscribers (down -1 in the last 3 months):
- 4 emails sent to list (13 in previous quarter)
## JIRA activity:
- 44 JIRA tickets created in the last 3 months
- 39 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment C: 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:
Some refactoring are happening now to make Archiva more generic and support
more repository types.
## 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:
- 226 subscribers (down -2 in the last 3 months):
- 2 emails sent to list (9 in previous quarter)
- dev@archiva.apache.org:
- 106 subscribers (up 0 in the last 3 months):
- 5 emails sent to list (35 in previous quarter)
- issues@archiva.apache.org:
- 34 subscribers (up 1 in the last 3 months):
- 14 emails sent to list (26 in previous quarter)
- notifications@archiva.apache.org:
- 16 subscribers (up 0 in the last 3 months):
- 37 emails sent to list (72 in previous quarter)
## JIRA activity:
- 4 JIRA tickets created in the last 3 months
- 0 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment D: Report from the Apache Atlas Project [Madhan Neethiraj]
## Description:
Apache Atlas is a scalable and extensible set of core foundational
governance services that enables enterprises to effectively and efficiently
meet their compliance requirements within Hadoop and allows integration with
the complete enterprise data ecosystem
## Issues:
There are no issues requiring board attention at this time.
## Activity:
- team has been busy working on maint releases 1.1.0 and 0.8.3
- vote to release 1.1.0 concluded on 9/12/2018. Release announcement will go
out in next few days
- release 0.8.3 is likely to be around mid October-2018
- updated authorization model to support access control on relationship
operations
- added support for AWS S3 datatypes, in Atlas server and Hive hook
- updated JanusGraph version from 0.2.0 to 0.3.0
- hooks updated to send Kafka notifications asynchronously
- enhanced classification-propagation with options to handle entity-deletes
- notification module updated to send notification after successful commit
- enhanced export/import to support replication across Atlas instances
- will start work on supporting Hadoop 3, HBase 2, Solr 7 in master branch
## Health report:
- 1 new contributor added in last 3 months: Kapildeo Nayak
## PMC changes:
- Currently 33 PMC members
- No new PMC members added in last 3 months
- Last PMC member addition was on 6/21/2017
## Committer base changes:
- Currently 37 committers
- No new committers added in last 3 months
- Last addition to committer role was on 1/9/2018
## Releases:
0.8.3 plan to release by 10/15/2018
1.1.0 plan to release by 09/15/2018
1.0.0 was released on 06/02/2018
0.8.2 was released on 02/05/2018
1.0.0-alpha was released on 01/25/2018
0.8.1 was released on 08/29/2017
0.8-incubating was released on 03/16/2017
0.7.1-incubating was released on 01/26/2017
0.7-incubating was released on 07/09/2016
0.6-incubating was released on 12/31/2015
0.5-incubating was released on 07/11/2015
-----------------------------------------
Attachment E: Report from the Apache Aurora Project [Jake Farrell]
Apache Aurora is a stateless and fault tolerant service scheduler used to
schedule jobs onto Apache Mesos such as long-running services, cron jobs,
and one off tasks.
Project Status
---------
The Apache Aurora community has seen consistent involvement from
contributors and consistent user activity over the last quarter. We have
successfully released one new versions of Apache Aurora during this time:
a regular planned release of 0.21.0.
Community
---
Latest Additions:
* No new PMC members added in the last 3 months
Issue backlog status since last report:
* Created: 5 in the last 3 months
* Resolved: 3 in the last 3 months
* Issues created on GitHub: 4 in the last 3 months
* Issues resolved on GitHub: 1 in the last 3 months
Mailing list activity since last report:
* @dev 97 messages
* @user 12 messages
* @reviews 179 messages
Releases
---
Last release:
* 0.21.0 was released on Sun Sep 09 2018
-----------------------------------------
Attachment F: Report from the Apache Axis Project [Robert Lazarski]
# Apache Axis2 Board Report
## Description
The Apache Axis project is responsible for the creation and maintenance of
software related to the Axis Web Services frameworks and subsidiary components
(both Java and C).
## Issues
There are no issues requiring board attention at this time.
## Activity
- Axis2 Java 1.7.8 (stable)
- Maintenance only.
- Axis2 Java 1.8 (development)
- Axis2 C 1.7 (development)
## Health report:
We have enough PMC to cut releases. Axis2 is a mature project, but still
actively maintained. We continue to receive patches from new users.
The vast majority of recent mailing list traffic comes in two forms: security
issues found by researchers and users static analysis tools such as Veracode,
and migration issues from old releases that are long unsupported.
Going forward the web service trends in the industry are REST, JSON and
annotation driven development via JSR 181 POJO Web Services - all things Axis2
has excellent support for however the docs are lacking to tie it all together.
Our day jobs have already moved in this direction, and recently we have seen
users figuring out that since they are already using Axis2 for SOAP they can
also use it for REST and JSON. We see an opportunity to grow our community via
better docs in this area. A Spring Boot starter kit is planned for the next
quarter, the idea being one maven dep instead of literally 25 separate Jars
and also code based auto configuration of the most common use cases.
Axis2 C added a new committer this past December 2017, and so far that is
helping the project pick up speed. There was more progress via commits and
Jira issues this past quarter. Indications are that an Axis 2 C 1.7 release
could happen by the end of the year.
There are indications via various user list threads and Jira issues that an
Axis2 Java 1.7.9 release is likely to happen this upcoming quarter.
## PMC/Committer changes:
- Currently 63 PMC/Commiters members.
- No new committers were added in the last 90 days, last committer added was
Bill Blough on December 7th 2017 who also was added to the PMC on May 9th
2018.
## Releases:
- Axis 2/Java 1.7.8 was released on May 19, 2018.
- Axis 2/C 1.6 was released on April 20, 2009.
- Axis 1.4 was last released in 2006.
## JIRA Activity
- 10 JIRA tickets created in the last 90 days.
- 11 JIRA tickets closed/resolved in the last 90 days.
-----------------------------------------
Attachment G: Report from the Apache Bahir Project [Luciano Resende]
Apache Bahir provides extensions to distributed analytic platforms such as
Apache Spark and Apache Flink. Currently, Bahir provides extensions to
multiple distributed analytic platforms, extending their reach with a
diversity of streaming connectors and SQL data sources.
Community Activity:
Apache Bahir community activity has been resuming slowly, and not much has
changed from last report where the community continue working to catch up on
Spark releases and we have recently released Bahir for Spark 2.2.1.
Activities around Flink extensions are growing back to normal levels. A new
connector for Apache Kudu as added and few other updates to support latest
Apache Flink release was also provided to the project.
Issues:
* No known issues
Releases:
06/27/2018 - Bahir for Spark 2.2.1
06/04/2018 - Bahir for Spark 2.1.2
08/22/2017 - Bahir for Spark 2.2.0
07/11/2017 - Bahir for Spark 2.1.1
05/24/2017 - Bahir for Flink 1.0
03/05/2017 - Bahir for Spark 2.1.0
01/28/2017- Bahir for Spark 2.0.2
10/28/2016 - Bahir for Spark 2.0.1
Committers or PMC changes:
(Currently 10 PMC / 38 committers)
06/25/2018 - Zhihong Yu (Ted Yu) becomes Apache Bahir PMC
09/14/2017 - Esteban Laver becomes Apache Bahir committer
04/05/2017 - Robert Metzger becomes Apache Bahir PMC
03/13/2017 - Christian Kadner becomes Apache Bahir PMC
11/30/2016 - Christian Kadner voted as Apache Bahir committer
10/18/2016 - Robert Metzger voted as Apache Bahir committer
Trademark/Branding:
* No known issues.
Legal Issues:
* None
-----------------------------------------
Attachment H: Report from the Apache Beam Project [Davor Bonaci]
## Description:
Apache Beam is a unified programming model for both batch and streaming data
processing, enabling efficient execution across diverse distributed execution
engines and providing extensibility points for connecting to different
technologies and user communities.
## Issues:
The Board is presented with a Special Order 7B to appoint Kenneth Knowles
(kenn) to the office of Vice President, Apache Beam. Kenneth has served on the
PMC since its inception, and is very active and effective in growing the
community. His exemplary posts have been cited in other projects.
## Activity:
Apache Beam is now approaching its second anniversary as a top-level project.
Major technical efforts going on include:
- Finishing the portable Flink runner, which adds support for Python and Go
SDKs.
- Adding Schema support.
- Beam SQL.
- Infrastructure and automation.
Recent community decisions include:
- Providing designated "Long Term Support" releases.
- Better management of outdated dependencies.
- Using JIRA to track and highlight non-code contributions.
Several blog posts have been published this quarter, primarily promoting the
releases. Google is organizing a Beam Summit in London next month, expecting
modest attendance. Additionally, Beam was featured at several conferences,
including Flink Forward 2018 in Berlin.
Going forward, the main focus should be on the community growth, particularly
on the user side using non-proprietary engines. This goes hand-in hand with
the next major technical milestone of delivering on the portability framework,
making Beam available to Python and Go communities.
## Health report:
The user community grew modestly, as evidenced by the increased mailing list
activity, which is encouraging.
Activity on the development mailing list decreased, but there were quite a few
new contributors joining, improving the diversity. Lifetime unique code
contributors grew to 322, with 53 new first-time contributors.
## PMC changes:
Currently 19 PMC members. No new PMC members have been added since the last
report. The last PMC addition was Thomas Weise on Fri Jun 08 2018.
Frances Perry requested to resign from the PMC, though that resignation has
been put on hold pending discussions around establishing an emeritus policy
instead, taking into account recent Board discussions and recommendations to
other projects.
## Committer base changes:
Currently 42 committers. Five new committers have been added since the last
report. New committers:
- Scott Wegner was added as a committer on Thu Jun 21 2018.
- Łukasz Gajowy was added as a committer on Wed Jun 27 2018.
- Anton Kedin was added as a committer on Wed Aug 01 2018.
- Andrew Pilloud was added as a committer on Wed Aug 01 2018.
- Tim Robertson was added as a committer on Thu Aug 23 2018.
The PMC recognizes two areas for improvement: (1) diversity of affiliations
among active committers, and (2) an imbalance of contributors to active
committers. The main cause of these recent imbalances is turnover over the
last year, perhaps among some others. The plan of inviting quite a few new
committers over a period of time has materialized. We continue to be cautious
not to grow too quickly to jeopardize the community, or negatively affect
where the project business is handled.
## Releases:
Since the last report, Apache Beam has published two releases, with one more
currently in progress:
- 2.5.0 was released on Thu Jun 21 2018.
- 2.6.0 was released on Tue Aug 07 2018.
- 2.7.0 is currently under preparation.
Going forward, we expect to publish a release every 6 weeks, a target that we
have become better at achieving.
## Mailing list activity:
Mailing list subscriptions and activity continues to increase modestly. The
activity on the development mailing list is down compared to the previous
quarter, likely due to seasonal effects of summer vacations. The activity on
the user mailing list has increased to a new high, which is very encouraging.
- dev@beam.apache.org
- 547 subscribers (up 27 in the last 3 months).
- 1757 emails sent to list (2000 in previous quarter).
- user@beam.apache.org
- 574 subscribers (up 25 in the last 3 months).
- 525 emails sent to list (353 in previous quarter).
## JIRA activity:
For the third quarter in a row, the JIRA activity is increasing, turning over
the earlier trend.
- 811 JIRA tickets created in the last 3 months (705 in the previous quarter).
- 501 JIRA tickets closed/resolved in the last 3 months (368 in the previous
quarter).
-----------------------------------------
Attachment I: Report from the Apache Bigtop Project [Peter Linnell]
## Description:
Apache Bigtop is a software related to a system for integration, packaging,
deployment and validation of a big data management software distribution based
on Apache Hadoop.
## Issues:
None
## Activity:
The community is actively working on 1.3.0 release and target to be released
before ApacheCon 2018. Committer Jun He is serving as the RM. Currently we
see a good progress being made.
## PMC changes:
Last PMC addition was Kevin Monroe on Mon Nov 27 2017
Currently 26 PMC members
## Committer base changes:
Last committer addition was Jun He on Fri Feb 23 2018
Currently 37 committers
## Releases:
Last release was 1.2.1 on Sun Nov 12 2017
-----------------------------------------
Attachment J: Report from the Apache Bloodhound Project [Gary Martin]
-----------------------------------------
Attachment K: Report from the Apache BVal Project [Matthew Jason Benson]
## Apache BVal Report September 2018 ##
- The Apache BVal project implements the Java EE Bean Validation
specification(s) and related extensions, and became a top-level project of
the foundation on February 15, 2012.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- Apache BVal community members working in Apache Commons have recently
succeeded in pushing the 2.0 release of the Apache Commons Weaver component
upon which we depend.
- Our immediate plans are to push the release of the Apache licensed bean
validation 2.0 specification artifact through the Apache Geronimo project and
then to release Apache BVal 2.0.
- The security issue mentioned last quarter is incurred at the specification
level and has been deemed low priority by the bean validation community as a
whole, any vulnerability requiring deliberate and naive custom code on the
part of the application developer. The Apache BVal community continue to
ponder what actions we might take to reduce the likelihood of such naive
exposures.
## Health report:
- We retain a small core of developers with the desire to keep this project
afloat.
## PMC changes:
- Currently 13 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Romain Manni-Bucau on Mon Nov 18 2013
## Committer base changes:
- Currently 14 committers.
- No new changes to the committer base since last report.
## Releases:
- Last release was 1.1.2 on Wed Nov 02 2016
## JIRA activity:
- 1 JIRA tickets created in the last 3 months
- 0 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment L: Report from the Apache Camel Project [Andrea Cosentino]
## Description:
- Apache Camel is a powerful open source integration library based on
Enterprise Integration Patterns. Rules for Camel's routing engine can be
defined in either a Java based DSL or XML.
## Issues:
- there are no issues requiring board attention at this time
## Activity:
- We are preparing for the next minor releases Apache Camel 2.22.1 expected
for the beginning of September and 2.21.2.
- We are working on a new website while the documentation has been totally
migrated to Github to be able to control the documentation at code level.
- We are continuing our work towards Apache Camel 3.0.0.
- We announced the following vulnerability with the last releases:
http://camel.apache.org/security-advisorie
s.data/CVE-2018-8027.txt.asc?version=4&modificationDate=1533020841313&api=v2
## Health report:
- The project is super healthy, active and stays at a high level
## PMC changes:
- Currently 32 PMC members.
- Nicola Ferraro is the last new PMC Member added since the last report
- Last PMC was added on Mon Jul 16 2018
## Committer base changes:
- Currently 63 committers.
- No new committers in the last 3 months.
- Dmitry Volodin was added as a committer on Sat May 19 2018
## Releases:
- 2.21.2 was released on Sat Jul 21 2018
- 2.22.0 was released on Tue Jul 03 2018
## Mailing list activity:
- users@camel.apache.org:
- 1009 subscribers (up 14 in the last 3 months)
- 325 emails sent to list (290 in previous quarter)
- dev@camel.apache.org:
- 360 subscribers (up 3 in the last 3 months)
- 540 emails sent to list (501 in previous quarter)
- issues@camel.apache.org:
- 84 subscribers (down -2 in the last 3 months):
- 2555 emails sent to list (2172 in previous quarter)
- notifications@camel.apache.org:
- 8 subscribers (up 0 in the last 3 months)
## JIRA activity:
- 214 JIRA tickets created in the last 3 months
- 234 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment M: Report from the Apache Cayenne Project [Michael Ray Gentry]
# Apache Cayenne Board Report, September 2018
## Description
Apache Cayenne is a Java database persistence framework. It takes a
distinct approach to object persistence and provides an ORM runtime,
remote persistence services, and a cross-platform GUI mapping/modeling
tool.
## Issues
There are no issues requiring board attention at this time.
## Activity
The past quarter saw 3 major releases as 4.0 was finally released,
a new 4.1 milestone released, and a maintenance patch for 3.1.3 was
also released. All of these releases include a fix for CVE-2018-11758
(https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11758).
- Cayenne 3.1.3 (aging)
- Maintenance only.
- Cayenne 4.0 (stable)
- After years of development, the next major version of Cayenne was
finalized and released. This version replaces 3.1.x as the current
stable release -- not that 3.1.x is unstable, but upgrading is
encouraged at this point. Some of the new features can be seen at
https://cayenne.apache.org/2018/08/cayenne-40-final-released/.
- Cayenne 4.1M2 (development/alpha)
- Work continues on Cayenne 4.1 as a new milestone was released which
includes new features and bug fixes.
## Health Report
Cayenne is healthy. Development activity is stable and and we have a
stable user and developer community.
## Board Questions
During the last board meeting it was asked if there were any potential
candidates for committers or the PMC. There are a few possible
committers we are keeping an eye on and will encourage and coach
should they show more interest.
## PMC Changes
- Currently 9 PMC members.
- No new PMC members added in the last 3 months.
- Last PMC addition was Nikita Timofeev on Sun Jun 25 2017.
## Committer Base Changes
- Currently 22 committers.
- No new committers added in the last 3 months.
- Last committer addition was Hugi Thordarson at Mon Jun 19 2017.
## Releases
- Cayenne 3.1.3 on Wed Jul 25 2018.
- Cayenne 4.0 on Mon Aug 20 2018.
- Cayenne 4.1.M1 on Wed Jul 25 2018.
## JIRA Activity
- 34 JIRA tickets created in the last 3 months.
- 31 JIRA tickets closed/resolved in the last 3 months.
-----------------------------------------
Attachment N: Report from the Apache Chemistry Project [Florian Müller]
## Description:
Apache Chemistry is an effort to provide an implementation of the CMIS
(Content Management Interoperability Services) specification in Java,
Python, PHP, .NET, Objective-C, and JavaScript (and possibly other
languages).
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- There has been a major refactoring of the Python CMIS library,
which among other things makes it compatible with Python 2 and Python 3.
We are waiting for community feedback before releasing it.
There has been no activity around the other subprojects in the last
three months.
## Health report:
- We have a mature code base. No major development is expected.
## PMC changes:
- Currently 36 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Laurent Mignon on Sat Sep 23 2017
## Committer base changes:
- Currently 38 committers.
- No new committers added in the last 3 months
- Last committer addition was Laurent Mignon at Wed Sep 20 2017
## Releases:
- Last release was cmislib 0.6.0 on Thu Aug 31 2017
## Mailing list activity:
- dev@chemistry.apache.org:
- 165 subscribers (down -1 in the last 3 months):
- 32 emails sent to list (43 in previous quarter)
## JIRA activity:
- 1 JIRA tickets created in the last 3 months
- 2 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment O: Report from the Apache CloudStack Project [Mike Tutkowski]
## Description:
Apache CloudStack (ACS) is an IaaS (Infrastructure as a Service) cloud
orchestration platform. ACS manages many types of hypervisors, storage and
networking devices.
## Issues:
## Activity:
- One new release (4.11.1.0) since the previous report.
## Health report:
- Version 4.12.0 is in development.
- Version 4.11.2 is in development.
- All seems healthy
## PMC changes:
- Currently 47 PMC members (same as of the last report)
- Most recently added PMC member was Syed Ahmed on Sun Oct 08 2017
## Committer base changes:
- Currently 117 committers (same as of the last report)
- Most recently added committer was Dag Sonstebo on Mon Mar 19 2018
## Releases (one release since the previous report):
- Release 4.11.1.0 on June 21 2018
-----------------------------------------
Attachment P: Report from the Apache Commons Project [Gary D. Gregory]
## Description:
- Apache Commons is an Apache project focused on all aspects of reusable Java
components.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- Activity is high with the release of 10 components and 4 internal
components.
## Health report:
- The project is healthy but suffers from a lack of committer and PMC
growth.
- Releases for existing components are in the planning stage for Pool,
DBCP, IO, and Numbers.
- We are discussing the addition of a new component, mailing activity is good
and JIRAs are addressed in a timely manner.
## PMC changes:
- Currently 38 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Rob Tompkins on Fri Jun 30 2017
## Committer base changes:
- Currently 146 committers.
- No new committers added in the last 3 months
- Last committer addition was Sergio Fernández at Sat Nov 04 2017
## Releases:
- BUILD-PLUGIN-1.9 was released on Tue Jun 19 2018
- COLLECTIONS-4.2 was released on Tue Jul 10 2018
- COMPRESS-1.18 was released on Wed Aug 15 2018
- CONFIGURATION-2.3 was released on Tue Aug 07 2018
- DBCP-2.4.0 was released on Fri Jun 15 2018
- DBCP-2.5.0 was released on Sun Jul 15 2018
- JCS-2.2.1 was released on Thu Sep 06 2018
- LANG-3.8 was released on Sat Aug 18 2018
- PARENT-47 was released on Sun Jul 01 2018
- POOL-2.6.0 was released on Thu Jul 05 2018
- RELEASE-PLUGIN-1.3 was released on Sun Jun 17 2018
- RELEASE-PLUGIN-1.4 was released on Tue Aug 28 2018
- RNG-1.1 was released on Mon Aug 13 2018
- WEAVER-2.0 was released on Thu Sep 06 2018
## JIRA activity:
- 175 JIRA tickets created in the last 3 months
- 117 JIRA tickets closed/resolved in the last 3 months
## Odds and ends:
Incomplete stats from https://demo.kibble.apache.org:
- 977 Authors this period; Down -4% since last period
- 19,242 Commits this period; Down -21% since last period
- 558 Committers this period; Down -3% since last period
- 10,881,243 Lines changed this period; Down -19% since last period
-----------------------------------------
Attachment Q: Report from the Apache Cordova Project [Shazron Abdullah]
## Description:
- A platform for building native mobile applications using HTML, CSS and
JavaScript.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
We had four platform releases this quarter. The releases were mainly bug fixes
and also fixes related to `npm audit` issues. `npm audit` checks the
dependency tree for your code and provides a security vulnerability report.
We had tool releases for cordova-common, cordova-js, and cordova-coho. The
releases relate to bug fixes and fixes related to `npm audit` issues. We also
upgraded support to `node-6` and greater, with our dropping of `node-4`
support.
We had our first committers meeting (over video call) of 2018 with all the new
committers to discuss project direction. Our last meeting face to face was in
Oct 2016 in Redmond, WA.
We shut down creation of new issues in Apache JIRA, and enabled `Github
Issues` in all 71 repositories that we have in Apache's Github org. We decided
not to migrate any existing open issues in JIRA to Github -- we will
investigate and triage those issues in JIRA and migrate issues on a case by
case basis. We established an org-level Github Project Board for us to have a
bird's eye view of all Cordova issues in all our numerous repos, for planning
purposes.
## Health report:
Our status dashboard at http://status.cordova.io is mostly all green -
failures are usually due to external service issues that do device testing.
Our nightly builds have been stable with occasional packaging failures.
We are actively trying to resolve all existing issues in JIRA while also
maintaining all the new issues in Github.
## PMC changes:
- Currently 94 PMC members.
- New PMC members:
- Bryan Ellis was added to the PMC on Wed Jul 25 2018
- Ken (knaito) was added to the PMC on Wed Jul 25 2018
- Gearóid M was added to the PMC on Wed Jul 25 2018
## Committer base changes:
- Currently 97 committers.
- New commmitters:
- Bryan Ellis was added as a committer on Thu Jul 26 2018
- Ken (knaito) was added as a committer on Thu Jul 26 2018
- Gearóid M was added as a committer on Mon Jul 23 2018
## Releases:
- cordova-android@7.1.1 was released on Mon Jul 16 2018
- cordova-browser@5.0.4 was released on Fri Aug 10 2018
- cordova-coho@1.0.1 was released on Wed Jun 20 2018
- cordova-common@2.2.4 was released on Tue Jun 19 2018
- cordova-common@2.2.5 was released on Mon Jul 02 2018
- cordova-ios@4.5.5 was released on Thu Jul 26 2018
- cordova-js@4.2.3 was released on Thu Jun 21 2018
- cordova-js@4.2.4 was released on Tue Jun 26 2018
- cordova-osx@4.0.2 was released on Tue Aug 14 2018
## JIRA activity:
- 140 JIRA tickets created in the last 3 months
- 288 JIRA tickets closed/resolved in the last 3 months
## Github activity:
- 165 Github Issues created in the last 3 months
- 62 Github Issues closed in the last 3 months
- 308 Github Pull Requests created in the last 3 months
- 257 Github Pull Requests closed/merged in the last 3 months
-----------------------------------------
Attachment R: Report from the Apache cTAKES Project [Pei Chen]
## Description:
Apache clinical Text Analysis and Knowledge Extraction System (cTAKES) is
an open-source natural language processing system for information extraction
from electronic medical record clinical free-text.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
- Committee continues to work on the future release (4.0.1)
- Committee continues to work on bug fixes and improvements documented in Jira
## Health report:
- The community continues to be moderately active.
- There are new questions/suggestions from new users on the mailing lists
- There is steady increase in interest and growth in the community
based on the activity on the mailing lists
- Potential future new committers/PMC members being discussed on private@
## PMC changes:
- Currently 31 PMC members.
- Gandhi Rajan was added to the PMC on Thu Jul 12 2018
## Committer base changes:
- Currently 38 committers.
- No new committers added in the last 3 months
- Last committer addition was Gandhi Rajan at Tue Nov 14 2017
## Releases:
- Last release was 4.0.0 on Apr 27 2017
- 3.2.2 was released on May 30 2015
- 3.2.1 was released on Dec 10 2014
## Mailing list activity:
There was an increase in number of subscribers to the dev and user @
mailing lists.
- dev@ctakes.apache.org:
- 255 subscribers (up 4 in the last 3 months):
- 63 emails sent to list (148 in previous quarter)
- user@ctakes.apache.org:
- 265 subscribers (up 12 in the last 3 months):
- 46 emails sent to list (71 in previous quarter)
-----------------------------------------
Attachment S: Report from the Apache Curator Project [Jordan Zimmerman]
## Description:
- Apache Curator is a Java/JVM client library for Apache ZooKeeper, a
distributed coordination service. It includes a highlevel API framework and
utilities to make using Apache ZooKeeper much easier and more reliable. It
also includes recipes for common use cases and extensions such as service
discovery and a Java 8 asynchronous DSL.
## Issues:
- there are no issues requiring board attention at this time
## Activity:
- No important activity to report. We are responding to bug reports,
questions as normal and we have fairly regular releases.
## Health report:
- As we continue to mention both Curator and ZooKeeper are slowing into
maintenance mode
- Curator could use another committer. There some who look promising and are
being encouraged to contribute more
## PMC changes:
- Currently 12 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Fangmin Lv on Mon Mar 27 2017
## Committer base changes:
- Currently 12 committers.
- No new committers added in the last 3 months
- Last committer addition was Fangmin Lv at Tue Mar 28 2017
## Releases:
- Last release was Apache Curator 4.0.1 on Sat Feb 10 2018
## Mailing list activity:
- dev@curator.apache.org:
- 52 subscribers (up 1 in the last 3 months):
- 202 emails sent to list (203 in previous quarter)
- user@curator.apache.org:
- 161 subscribers (up 3 in the last 3 months):
- 18 emails sent to list (22 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 T: Report from the Apache Eagle Project [Edward Zhang]
## Description:
- Apache Eagle is an open source analytics solution for identifying security
and performance issues instantly on big data platforms.
## Issues:
- There are no issues requiring board attention at this time
## Activity:
- Clean up of some existing Jira tickets for release 0.5.0 in order for preparing 0.5.1
- User asked for Eagle to read from Kafka using SASL, community needs evaluate
whether this feature should be supported
## Health report:
- Health is ok, but need a few committers to volunteer to help with 0.5.1 which is minor
improvement from 0.5.0.
## PMC changes:
- Currently 16 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Deng Lingang on Mon May 08 2017
## Committer base changes:
- Currently 18 committers.
- No new committers added in the last 3 months
- Last committer addition was Jay Sen at Thu Mar 16 2017
## Releases:
- Last release was 0.5.0 on Sat Sep 09 2017
## Mailing list activity:
- dev@eagle.apache.org:
- 75 subscribers (down -4 in the last 3 months):
- 9 emails sent to list (9 in previous quarter)
- issues@eagle.apache.org:
- 19 subscribers (down -1 in the last 3 months):
- 31 emails sent to list (30 in previous quarter)
- user@eagle.apache.org:
- 56 subscribers (down -2 in the last 3 months):
- 2 emails sent to list (3 in previous quarter)
## JIRA activity:
- 0 JIRA tickets created in the last 3 months
- 16 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment U: Report from the Apache Falcon Project [Pallavi Rao]
ABOUT
Falcon is a data processing and management solution for Hadoop
designed for data motion, coordination of data pipelines,
lifecycle management, and data discovery. Falcon enables end
consumers to quickly onboard their data and its associated
processing and management tasks on Hadoop clusters.
ISSUES
There are no issues that require board's attention at this time.
## Activity:
Currently bug fixes to existing features are making into the code base.
## Health report:
After 0.11 release there have been no new feature asks from the community.
## PMC changes:
- Currently 17 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Sowmya Ramesh on Mon Jun 06 2016
## Committer base changes:
- Currently 25 committers.
- No new committers added in the last 3 months
- Last committer addition was Sandeep Samudrala at Thu Mar 09 2017
## Releases:
- Last release was 0.11 on Tue Mar 13 2018
## Mailing list activity:
- dev@falcon.apache.org:
- 110 subscribers (up 0 in the last 3 months):
- 44 emails sent to list (64 in previous quarter)
- user@falcon.apache.org:
- 30 subscribers (up 0 in the last 3 months):
- 2 emails sent to list (3 in previous quarter)
## JIRA activity:
- 1 JIRA tickets created in the last 3 months
- 7 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment V: Report from the Apache Felix Project [Karl Pauls]
## Description:
Apache Felix is a project aimed at implementing specifications from the OSGi
Alliance as well as implementing other supporting tools and technologies
aligned with OSGi technology.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- Existing implementations have been improved/enhanced based on community
feedback.
- Released "System readiness framework" by Andrei Dulvac and Christian
Schneider and the "Logback integration with OSGi Log 1.4" by Raymond Augé.
- Released most of the OSGi R7 specification related components.
- Released OSGi R7 compliant Framework.
- Released 16 components (mostly bug fixes and OSGi R7 releated).
## Health report:
- Overall the project is in good health (but not growing atm).
- Questions on the user list are answered, development concerns are either
discussed on the mailing list or directly in the JIRA issues.
- The project as well as the OSGi community in general is still in the
process of adapting to JPMS and its long term impact.
- Attracting new committers needs to be a focus - one or two promising
candidates.
- We had no issues voting on releases and JIRA issues are generally addressed
promptly.
## PMC changes:
- Currently 26 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Raymond Augé on Thu May 03 2018
## Committer base changes:
- Currently 63 committers.
- No new committers added in the last 3 months
- Last committer addition was Christian Schneider at Thu May 03 2018
## Releases:
- maven-bundle-plugin-3.5.1 was released on Tue Jun 19 2018
- maven-bundle-plugin-4.0.0 was released on Fri Aug 31 2018
- org.apache.felix.framework-6.0.0 was released on Fri Jul 06 2018
- org.apache.felix.framework-6.0.1 was released on Mon Aug 20 2018
- org.apache.felix.framework.security-2.6.1 was released on Mon Aug 20 2018
- org.apache.felix.gogo.jline-1.1.0 was released on Thu Jun 14 2018
- org.apache.felix.gogo.runtime-1.1.0 was released on Thu Jun 14 2018
- org.apache.felix.gogo.shell-1.1.0 was released on Thu Jun 14 2018
- org.apache.felix.http.jetty-4.0.2 was released on Fri Jul 13 2018
- org.apache.felix.log-1.2.0 was released on Fri Jul 13 2018
- org.apache.felix.log.extension-1.0.0 was released on Fri Jul 13 2018
- org.apache.felix.logback-1.0.0 was released on Mon Jun 25 2018
- org.apache.felix.main-6.0.0 was released on Fri Jul 06 2018
- org.apache.felix.main-6.0.1 was released on Mon Aug 20 2018
- org.apache.felix.main.distribution-6.0.0 was released on Fri Jul 06 2018
- org.apache.felix.main.distribution-6.0.1 was released on Mon Aug 20 2018
- org.apache.felix.main.resolver-2.0.0 was released on Fri Jul 06 2018
- org.apache.felix.systemready-0.2.0 was released on Mon Jul 16 2018
- org.apache.felix.systemready-0.4.0 was released on Sat Aug 18 2018
## Mailing list activity:
- users@felix.apache.org:
- 569 subscribers (up 3 in the last 3 months):
- 117 emails sent to list (66 in previous quarter)
- dev@felix.apache.org:
- 325 subscribers (down -2 in the last 3 months):
- 660 emails sent to list (613 in previous quarter)
## JIRA activity:
- 59 JIRA tickets created in the last 3 months
- 50 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment W: Report from the Apache Flex Project [Tom Chiverton]
Apache Flex is an application framework for easily building Flash-based
applications for mobile devices, the browser and desktop. RELEASES
Apache Flex SDK Installer 3.3.2 - a bug fix release for an issue on Windows
with large downloads. In order to work around this issue, the 32-bit based
installer runs a 64-bit version of the installer now.
Older Releases:
-Apache Flex SDK 4.16.1 was released on 2017-11-22
-Apache Flex BlazeDS 4.7.3 was released on 3/31/17.
-Apache Flex Tour De Flex Component Explorer 1.2 was released on 11/28/14.
-Apache Flex Tool API 1.0.0 was released on 11/20/14
-Apache Flex Squiggly 1.1 was released on 10/26/14
ACTIVITY & COMMUNITY
We are constantly helping users on dev and users list if any requests come
out.
Last PMC addition: Mon Aug 28 2017
Last committer addition: Wed Sep 07 2016
TRADEMARKS
VP-Brand notified the PMC of three potentially infringing trademarks, and has
instructed legal to oppose.
SECURITY
Nothing to report.
-----------------------------------------
Attachment X: Report from the Apache Flink Project [Stephan Ewen]
DESCRIPTION
Apache Flink is a distributed data streaming system for batch and streaming
data analysis on top of a streaming dataflow engine. Flink's stack contains
functional batch and streaming analysis APIs in Java and Scala and libraries
for various use cases.
Flink interacts and integrates with several Apache projects in the broader
ecosystem of data storage and computing, such as Apache Beam,
Hadoop, Mesos, Kafka, HBase, Cassandra, and various others.
ISSUES
- There are no issues that require board attention.
STATUS AND ACTIVITY
- The Flink community has released the 1.6 release, with enhancements
to Streaming SQL, connectors, container-based deployment, and more.
- The investment in more automated release testing seems to pay off. The
community is releasing bugfix releases faster and more frequently.
- The Flink Forward Berlin conference took place earlier in September April
bringing together many community members. Talks were a mix of use cases,
tech deep dive, ecosystem, and (for the first time) stream processing
research topics.
- Two more Flink Forward conferences have been announced: In Beijing on
December 20-21, 2018, and in San Francisco on April 1-2, 2019.
COMMUNITY
No new PMC members were added since the last report.
The newest PMC member is Chesnay Schepler, joined on July 26th, 2017
Committers added since the last board report:
- Sihua Zhou was added as a committer on June 23rd, 2018
- Piotr Nowojski was added as a committer on June 27th, 2018
- Gary Yao was added as a committer on September 9th, 2018
Flink currently has 41 committers and 19 PMC members.
RELEASES
The following releases were made since the last board report:
- 1.5.1 was released on July 12th, 2018
- 1.5.2 was released on July 31st, 2018
- 1.5.3 was released on August 21st, 2018
- 1.6.0 was released on August 9th, 2018
ACTIVITY ON JIRA / MAILING LISTS
Mailing lists continue to be very active and steadily grow in traffic:
- user@f.a.o (2376 mails/quarter)
- dev@f.a.o (1413 mails/quarter)
JIRA continues to be active as well, 740 JIRA tickets created, 565 JIRA
tickets resolved in the last 3 months .
-----------------------------------------
Attachment Y: 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:
- A new committer, Jim Chen, has joined the project.
- Several improvements to Guacamole's terminal emulator and RDP support
support have been merged.
- Support for SSH/SFTP host key checking has been added.
- Regressions discovered in the pending 1.0.0 release are slowing the release
process.
## Health report:
- The project is healthy. Development and community involvement continue to
be active.
## PMC changes:
- Currently 9 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Carl Harris on Sun Nov 19 2017
## Committer base changes:
- Currently 11 committers.
- Jim Chen was added as a committer on Thu Jun 21 2018
## Releases:
- Last release was 0.9.14 on Wed Jan 17 2018
## Mailing list activity:
- dev@guacamole.apache.org:
- 82 subscribers (up 5 in the last 3 months):
- 413 emails sent to list (587 in previous quarter)
- user@guacamole.apache.org:
- 314 subscribers (up 14 in the last 3 months):
- 469 emails sent to list (537 in previous quarter)
## JIRA activity:
- 53 JIRA tickets created in the last 3 months
- 35 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment Z: Report from the Apache Gump Project [Stefan Bodewig]
Apache Gump is a cross-project continuous integration server. Gump's
intention isn't so much to be a CI server but rather a vehicle that
makes people look beyond their project's boundaries and helps the
projects to collaborate.
Gump is written in Python and supports several build tools and version
control systems. The Apache installation of Gump builds ASF as well
as non-ASF projects and their dependencies. It started in the Java
part of the foundation but also builds projects like APR, HTTPd and
XMLUnit.NET.
== Summary ==
No changes compared to the last quarter.
== Releases ==
Gump has never done any releases. One reason for this is that the ASF
installations of Gump work on the latest code base almost all of the
time following its "integrate everything continuously" philosophy.
== Activity ==
The Tomcat and Forrest communities are still using Gump actively.
== Changes to the Roster ==
All ASF committers have write access to the metadata that configure
the ASF installations.
The last changes to the PMC have seen Konstantin Kolinko and Mark
Thomas join in November 2014.
-----------------------------------------
Attachment AA: Report from the Apache HAWQ Project [Lei Chang]
## Description:
HAWQ is an advanced enterprise SQL on Hadoop analytic engine built around a
robust and high-performance massively-parallel processing (MPP) SQL engine
evolved from Greenplum Database.
## Issues:
None
## Activity:
1) The community is actively working on 2.4.0.0 release and target to be
released in Oct. Radar is serving as the RM. Currently we see a good progress
being made. The major features included in this release are:
- New Feature: Pluggable Vectorized Execution Engine on HAWQ.
- New Feature: Support Runtime Filter for HAWQ local hash join.
2) Coming community talks:
- The way to Apache TLP - HAWQ practices, COSCon 2018 (Speaker: Lei Chang)
- Apache HAWQ on Kubernetes: Bring SQL on Hadoop to Cloud, ApacheCon 2018
(Speaker: Ivan Weng, Wen Lin)
## Mailing list & JIRA activity in last three months:
- dev@hawqapache.org: 100 emails sent to list
- JIRA: 15 Issues Opened, 10 issues Closed/Resolved
## PMC changes:
Last PMC addition was Amy Bai Kevin Monroe on April 24, 2018, Currently 36 PMC
members
## Committer base changes:
Last committer addition was Shubham Sharma on April 25, 2018, Currently 45
committers
## Releases: Last release was 2.3.0.0 on Mar 21, 2018
-----------------------------------------
Attachment AB: Report from the Apache Helix Project [Kishore G]
-----------------------------------------
Attachment AC: Report from the Apache Hive Project [Ashutosh Chauhan]
## Description:
- The Apache Hive (TM) data warehouse software facilitates querying and
managing large datasets residing in distributed storage.
## Issues:
- There are no issues requiring board attention at this time
## Activity:
- Project continues to receive new features and bug fixes at steady rate as
evident from jira stats.
- Gunther Hagleitner (PMC member) gave a presentation in Future of Data:
Silicon Valley meetup on Sept 6 on Hive 3 which was well attended.
## PMC changes:
- Currently 46 PMC members.
- Peter Vary was added to the PMC on Tue Jul 24 2018
- Sahil Takiar was added to the PMC on Tue Jul 24 2018
- Vineet Garg was added to the PMC on Sat Jul 28 2018
- Vihang Karajgaonkar was added to the PMC on Tue Jul 24 2018
## Committer changes:
- Currently 79 committers.
- Andrew Sherman was added as a committer on Fri Aug 10 2018
- Slim Bouguerra was added as a committer on Sun Jul 29 2018
## Releases:
- 3.1.0 was released on Mon Jul 30 2018
## Lists ;
- dev@hive.apache.org: - 883 subscribers (up 0 in the last 3 months):
- user@hive.apache.org: - 2244 subscribers (up 2 in the last 3 months):
## JIRA activity:
- 666 JIRA tickets created in the last 3 months
- 552 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AD: Report from the Apache Incubator Project [Justin Mclean]
= Incubator PMC report for September 2018 =
=== Timeline ===
||Wed September 05 ||Podling reports due by end of day ||
||Sun September 09 ||Shepherd reviews due by end of day ||
||Sun September 09 ||Summary due by end of day ||
||Tue September 11 ||Mentor signoff due by end of day ||
||Wed September 12 ||Report submitted to Board ||
||Wed September 19 ||Board meeting ||
=== Shepherd Assignments ===
||Dave Fisher ||Pony Mail ||
||Dave Fisher ||Tephra ||
||Drew Farris ||Omid ||
||Drew Farris ||S2Graph ||
||John Ament ||Doris ||
||John Ament ||SkyWalking ||
||Justin Mclean ||Gearpump ||
||P. Taylor Goetz ||Hivemall ||
||P. Taylor Goetz ||Superset ||
||P. Taylor Goetz ||Toree ||
||Timothy Chen ||Crail ||
||Timothy Chen ||OpenWhisk ||
||Timothy Chen ||Warble ||
||[none] ||Annotator ||
||[none] ||Daffodil ||
||[none] ||Druid ||
||[none] ||Dubbo ||
||[none] ||Griffin ||
||[none] ||Joshua ||
||[none] ||Milagro ||
||[none] ||Myriad ||
||[none] ||Nemo ||
||[none] ||PageSpeed ||
||[none] ||Pulsar ||
||[none] ||Quickstep ||
||[none] ||SAMOA ||
||[none] ||SINGA ||
||[none] ||SensSoft ||
||[none] ||Spot ||
||[none] ||Tamaya ||
||[none] ||Taverna ||
||[none] ||Zipkin ||
=== Report content ===
{{{
Incubator PMC report for September 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 presently 52 podlings incubating. During the month of August,
podlings executed 8 distinct releases and there are several ongoing votes
on releases for September. Some long standing release votes were resolved.
We added three new IPMC members.
Several podlings are heading towards graduation. We had one project,
Gossip, retire to the attic. BatchEE seems stuck in performing the last
graduation steps and needs some nudging over the line.
There were no IP clearances.
A number of podlings (3) that didn't report has decreased and Pony Mail has
finally reported. Senssoft has some issues that stoped it from reporting
but they are currently being addressed. Milagro has missed several reports
in a row and has failed to respond to queries to why this has occurred.
Gearpump have indicated they are discussing retiring.
Discussion continues about with to do about missing mentors and some
actions should be taken in the next month including contacting mentors and
asking if they still want to continue in the role. This may result in a
number of mentors needing to be replaced, and currently it is not known what
mentor capacity the IPMC has. We've had a number of members join the IPMC
to mentor projects this month which is encouraging. Given the low levels of
activity on some projects (as indicated by sign off rates and a sampling
of email list activity) this is a serious issue for the IPMC.
There's also been discussion on some podlings spending too long in
incubation and hopefully that will lead to a few more graduations and
retirements in the near future.
Changes have been suggested to the podling report and incubator proposal
template that should help in small ways with the above situations.
A podling, Superset, has been making releases not in line with the Apache
release policy. I've asked the podling to correct this and it's mentors are
helping out with this and other issues. The podling has been almost 2 years
in incubation and has made a large number of "unofficial" releases (50+).
* Community
New IPMC members:
- Andriy Redko
- Christofer Dutz
- William Colen
People who left the IPMC:
None
* New Podlings
- Zipkin
- DLab
- Marvin-AI
* Podlings that failed to report, (perhaps) expected next month
- Gearpump (discussing retirement)
- Milagro (no response and missing multiple reports in a row)
* Graduations
None this month.
* Releases
The following releases entered distribution during the month of
August:
- ServiceComb Chassis 1.0.0
- ServiceComb Service-Centre 1.0.0
- Pulsar 2.1.0
- Echarts 4.1.0
- Toree 0.2.0
- Openwhisk CLI 0.9.0
- Airflow 1.10.0
- Unomi 1.3.0
* IP Clearance
None
* Legal / Trademarks
No issues or discussions.
* Infrastructure
No issues.
* Miscellaneous
- Gossip podling was retired.
- HAWQ graduated to TLP last month.
- A DRAT prototype can be found here
(http://drat-vm.apache.org:8080/proteus-new/)
* Credits
None
----------------------------------------------------------------------
Table of Contents
Airflow
Annotator
Crail
Daffodil
Doris
Druid
Dubbo
Griffin
Hivemall
Myriad
Nemo
Omid
OpenWhisk
Pony Mail
Pulsar
Quickstep
S2Graph
SAMOA
SensSoft
SINGA
SkyWalking
Spot
Superset
Tamaya
Taverna
Tephra
Warble
----------------------------------------------------------------------
--------------------
Airflow
Airflow is a workflow automation and scheduling system that can be used to
author and manage data pipelines.
Airflow has been incubating since 2016-03-31.
Three most important issues to address in the move towards graduation:
1.Once we make a release with the licensing fix we will move forward
with graduation.
2.
3.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of? None
How has the community developed since the last report?
1. Since our last podling report 1 month ago (i.e. between August 5 &
September 4, inclusive), we grew our contributors from 512 to 548 (36 new
contributors)
2. Since our last podling report 1 month ago (i.e. between August 5 &
September 4, inclusive), we resolved 129 pull requests (currently at 2963
closed PRs)
3. Since being accepted into the incubator, the number of companies
officially
using Apache Airflow has risen from 30 to 193, 10 new from the last
podling report 1 month ago.
How has the project developed since the last report?
See above : 129 PRs resolved, 36 new contributors, & 10 new companies
officially using it. We also released 1.10.0, our 4th Apache Release while
in the incubator as seen on https://pypi.org/project/apache-airflow/ #history
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:
2018-08-27
When were the last committers or PPMC members elected?
Kaxil Naik on May 7 & Tao Feng on Aug 3
Signed-off-by:
[ ](airflow) Chris Nauroth
Comments:
[ ](airflow) Hitesh Shah
Comments:
[x](airflow) Jakob Homan
Comments:
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. Expanding the PMC
2. Establishing a regular release cadence
3. Engaging the broader community
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
The project was mostly idle the second half of the summer, with active
maintainers consumed by travel and other obligations, and missed board
reports.
How has the community developed since the last report?
- The PMC and contributors met face to face at the I Annotate conference in
San Francisco
- The project is seeing more frequent cloning and forking
How has the project developed since the last report?
- The project packaged a pre-release for developer testing
- The website now incorporates a demo thanks to a new contributor
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:
N/A
When were the last committers or PPMC members elected?
2018-06-06: gerben
Signed-off-by:
[X](annotator) Nick Kew
Comments: Report above explains low activity. Mostly seems to be
happening @github.
[ ](annotator) Brian McCallister
Comments:
[X](annotator) Daniel Gruno
Comments: Project seems to be in hiatus. Might be worth discussing
very soon what their options are, or if they are okay with this
activity level.
[X](annotator) Jim Jagielski
Comments: Not sure whether it makes sense for this podling to
continue at this activity level
IPMC/Shepherd notes:
--------------------
Crail
Crail is a storage platform for sharing performance critical
data in distributed data processing jobs at very high speed.
Crail has been incubating since 2017-11-01.
Three most important issues to address in the move towards graduation:
1. Community building: attract additional contributors from different
companies/affiliations + Crail deployments
2. Increase visibility / PR
3. Harden the code and improve stability and usability
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 twitter account "@ApacheCrail" was recently created
How has the project developed since the last report?
* Container support made available
* Improved failure handling (more meaningful error messages)
* Improved documentation
* Working towards second release
* Constant activities on bug fixes, quality improvements and
additional features at https://github.com/apache/incubator-crail
How would you assess the podling's maturity?
[ ] Initial setup
[ ] Working towards first release
[X] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
5/28/2018
When were the last committers or PPMC members elected?
2017-11-01 (entering incubation)
Signed-off-by:
[x](crail) Julian Hyde
Comments: The project is healthy and making good progress. As noted,
community building is the main challenge now. The technology is
in good shape, so I believe people will start adopting.
I am very pleased that they have created a twitter account; it should
allow them to build community daily.
[x](crail) Luciano Resende
Comments:
[ ](crail) Raphael Bircher
Comments:
IPMC/Shepherd notes:
--------------------
Daffodil
Apache Daffodil is an implementation of the Data Format Description Language
(DFDL) used to convert between fixed format data and XML/JSON.
Daffodil has been incubating since 2017-08-27.
Three most important issues to address in the move towards graduation:
1. Increase community growth and participation
2. Establish a frequent release schedule
3. Work with other Apache projects where Daffodil could provided extra
functionality
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
- None, though an extra mentor would be beneficial. We currently only
have 2 mentors.
How has the community developed since the last report?
- Received and merged new features from two new outside users
- Mike Beckerle was accepted for a talk on Daffodil at ApacheCon
- Steve Lawrence was accepted for a talk on Daffodil at a local Meetup
How has the project developed since the last report?
- Second release as an Apache incubator was completed (version 2.2.0)
- 42 commits from 6 different developers, including fairly large
features and refactoring
- 22 issues created, 49 issues resolved
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup
[ ] Working towards first release
[X] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
2018-09-05
When were the last committers or PPMC members elected?
- None, same as project incubation
Signed-off-by:
[X](daffodil) John D. Ament
Comments: Agree with Dave on all points.
[X](daffodil) David Fisher
Comments: Development is going well. Community building will need
some focus. The podling could use an additional Mentor.
IPMC/Shepherd notes:
--------------------
Doris
Doris is a MPP-based interactive SQL data warehousing for reporting and
analysis.
Doris has been incubating since 2018-07-18.
Three most important issues to address in the move towards graduation:
1. Finish the transfer of the repository
2. Prepare and set up the website for project.
3. Set up and start to develop by Apache infrastructure and tools.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
N/A.
How has the community developed since the last report?
The SGA has been received by the Secretary.
All of the initial committers have filled their ICLA and accounts are
created.
How has the project developed since the last report?
N/A.
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[x] Initial setup
[ ] Working towards first release
[ ] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
N/A.
When were the last committers or PPMC members elected?
N/A.
Signed-off-by:
[X](doris) Dave Fisher
Comments: The repository in GitHub is just about ready.
[ ](doris) Luke Han
Comments:
[X](doris) Willem Jiang
Comments:
IPMC/Shepherd notes:
--------------------
Druid
Druid is a high-performance, column-oriented, distributed data store.
Druid has been incubating since 2018-02-28.
Three most important issues to address in the move towards graduation:
1. Plan and execute our first Apache release.
2. Move the website to Apache infrastructure.
3. Expanding the community and adding more committers
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?
- None.
How has the community developed since the last report?
- A healthy, constant flow of bug fixes, quality improvements and new
features are still ongoing at https://github.com/apache/incubator-druid.
How has the project developed since the last report?
- We have renamed our packages from `io.druid.` to `org.apache.druid`, and
we are currently working on updating our NOTICE file.
- We expect to do a code freeze for our first incubating release,
0.13.0-incubating, within the next two weeks.
- Since the last report there have been 61 commits from 16 individuals.
- We have released 0.12.2, a non-incubator bugfix release.
- We are making a 0.12.3 bugfix release to address certain bugs found after
0.12.2 was released.
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup
[X] Working towards first release
[ ] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
- Druid 0.12.2 on 2018-08-09 (non-Apache release)
- No official Apache release yet since beginning Apache Incubation
When were the last committers or PPMC members elected?
- Project is still functioning with the initial set of committers.
Signed-off-by:
[x](druid) Julian Hyde
Comments: The first release will be an important milestone. (During
incubation the project has made non-ASF releases, with permission.)
All other aspects of the project are functioning well; the project
has built a vibrant community and lets the community drive its
decision-making. I think it is not far from graduating.
[x](druid) P. Taylor Goetz
Comments:
[ ](druid) Jun Rao
Comments:
IPMC/Shepherd notes:
Justin Mclean: I not sure that a project could be considered for graduation
without making a first release or adding committers.
--------------------
Dubbo
Dubbo is a high-performance, lightweight, java based RPC framework.
Dubbo has been incubating since 2018-02-16.
Three most important issues to address in the move towards graduation:
1. Community building
2. Ensure more discussion and decision making to be happening on the
mailing list.
3. New PPMC Member
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?
* Meetup
* Shanghai Meetup (2018-06-23): Online registration ~700, on-site
registration: 300+
* Shenzhen Meetup (2018-07-29): Online registration ~2k, on-site
registration: 700+
* Chengdu Meetup (2018-08-26): Online registration ~1000, on-site
registration: 350+
* The community has voted for new logo
* The community has voted for new website
* New committer:
* htynkn has been voted as committer on 2018-07-06
* kimming has been voted as committer on 2018-07-30
* diecui1201 has been voted as committer on 2018-07-30
* carryxyh has been voted as committer on 2018-08-20
* Dubbo has joined CNCF landscape: https://landscape.cncf.io/selected=dubbo
* Dubbo has reached 20k stars and 100 contributors, as of August 29th
* number of stars has grown from ~16000 to 21126 since start incubating.
* contributors has been grown from 75 to 119 since start incubating.
* It also has 14625 forks, which ranks #3 in all Github Java projects.
* 15 new companies reported their using of Dubbo since last report, 104 in
total
* The following projects has been added to external Apache Dubbo
ecosystem(http://github.com/dubbo, non-Apache repositories):
* dubbo-php-frmework
* dubbo-serialiazation-avro
* dubbo-sentinel-support
* Intellij IDEA plugin
* dubbo-rpc-native-thrift
These projects are being watched by Apache Dubbo PPMC and are planning be
moved to Apache once they meet the quality requirement.
How has the project developed since the last report?
* 2.6.2 is released
* 2.6.3 release is under way, RC4 is being voted
* All the package name has been changed to org.apache.dubbo and group
id has been changed to org.apache on 2.7.x branch
* New dubbo website has been published.
* Dubbo-ops has been refactored into a spring-boot project.
* Mailing list stats:
* August: 193 emails, 33 topics, 44, participants
* July: 248 emails, 46 topics, 45 participants
* June: 195 emails, 41 topics, 32 participants
* May: 138 emails, 23 topics, 35 participants (last report 2018-06-05)
Comparing to last report period, the number of mails/topics/participants
are all increased. More people
(including PPMC, committer and users) are getting involved to the mailing
list, and more discussion is happening on the list.
* Gtihub stats:
* August: 114 issues closed, 155 pr closed
* July: 181 issues closed, 56 pr closed
* June: 68 issues closed, 79 pr closed
* May: 106 issues closed, 75 pr closed(last report 2018-06-05)
The stats shows more people are coming to Github, more pull request
are coming, issues are getting solved.
The community is responding quicker to issues and pull request than before.
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:
* 2.6.2 has been released on 2018-6-7.
* 2.6.3 RC5 is under release process.
When were the last committers or PPMC members elected?
Yuhang Xiu(carryxyh) has been voted as committer on 2018-08-20.
Signed-off-by:
[X](dubbo) Justin Mclean
Comments: I agree with Mark that this project can be difficult to
follow.
It would be good to see more discussion on the mailing list.
[ ](dubbo) Jean-Frederic Clere
Comments:
[X](dubbo) Mark Thomas
Comments: Generally, the podling is doing well. The community is still
getting used to using mailing lists but I have no concerns at
at this stage of the podling's development
I do remain concerned at the volume of github notifications
and the difficulty in following them. I plan to chat with the
infrastructure folks at ApacheCon NA to see if there are any
changes that could be made on the infrastructure side to help
in this area.
IPMC/Shepherd notes:
--------------------
Griffin
Griffin is a open source Data Quality solution for distributed data systems
at any scale in both streaming or batch data context
Griffin has been incubating since 2016-12-05.
Three most important issues to address in the move towards graduation:
1. Preparation for graduation.
2. Enhance user guide documents.
3. Grow and marketing the community.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
None
How has the community developed since the last report?
- 1 new PPMC member(Lionel Liu) have been elected.
- 4 new committers(Jason Liao, Jenny Li, Liu Jin, Grant Xuexu) have been
elected.
- 6 new contributors contributed to our community.
- 10+ users have contacted us for use cases.
How has the project developed since the last report?
- Active development is moving on well, 101 commits in last three months.
- Voting for releasing version 0.3.0-incubating.
- Refactor measure module to make its architecture simpler and extensible.
- Refine Griffin DSL to remove complex expression.
- Looking forward to graduation release.
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:
2018-05-16
When were the last committers or PPMC members elected?
- Last committers(Jason Liao) were elected at July 31, 2018
- Last PPMC Member(Lionel Liu) were elected at July 8, 2018
Signed-off-by:
[ ](griffin) Kasper Sørensen
Comments:
[x](griffin) Uma Maheswara Rao Gangumalla
Comments:
[x](griffin) Luciano Resende
Comments:
[x](griffin) Henry Saputra
Comments:
IPMC/Shepherd notes:
--------------------
Hivemall
Hivemall is a library for machine learning implemented as Hive
UDFs/UDAFs/UDTFs.
Hivemall has been incubating since 2016-09-13.
Three most important issues to address in the move towards graduation:
1. Two or more Apache Releases as an Incubator project
2. Community growth (committers and users)
3. Documentation improvements
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?
* Github watchers/stars are gradually increasing:
169 stars as of Sept 3 (was 145 on June 5)
* Twitter account @ApacheHivemall followers are gradually increasing:
154 followers as of Sept 3 (was 145 on June 5)
* PPMC members (Makoto and Takeshi) will give a talk at ApacheCon North
America 2018
* PPMC members (Makoto and Takuya) will give a demo at ACM RecSys'18.
https://recsys.acm.org/recsys18/
How has the project developed since the last report?
* Preparing the second Apache release, v0.5.2. Release voting will start
in Sept, 2018.
https://issues.apache.org/jira/issues/?jql=project+%3D+HIVEMALL+AND+fixVersi
on+%3D+0.5.2
Since the last report, we have
* In the last 3 months, we opened 11 JIRA issues and closed 7 JIRA
issues as seen in https://goo.gl/QFQEF5 (as of Sept 3)
Created Resolved
June 2018 4 3
July 2018 1 1
Aug 2018 6 3
* Created 9 Pull Requests and closed 10 Pull Requests between June 1st
and Aug 31th.
https://github.com/apache/incubator-hivemall/pulls?q=is%3Apr%20created%3A201
8-06-01..2018-08-31
https://github.com/apache/incubator-hivemall/pulls?q=is%3Apr%20closed%3A2018
-06-01..2018-08-31
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:
March 5, 2018.
When were the last committers or PPMC members elected?
- Elected Jerome Banks as a committer on April 2.
Signed-off-by:
[ ](hivemall) Reynold Xin
Comments:
[X](hivemall) Xiangrui Meng
Comments:
[X](hivemall) Daniel Dai
Comments:
--------------------
Myriad
Description:
Myriad enables co-existence of Apache Hadoop YARN and Apache Mesos
together on the same cluster and allows dynamic resource allocations
across both Hadoop and other applications running on the same physical
data center infrastructure.
Myriad has been incubating since 2015-03-01.
Three most important issues to address in the move towards graduation:
* Grow the community and enroll new committers.
* Have (more) frequent Release cycles to be compliant with the Apache Way.
* Creating roadmaps for releases with goals (new features).
* Social media presence (new blog entries, conference talks).
* Unblock the issue [MYRIAD-264] Upgrade Mesos API to 1.5.x
Any issues that the IPMC or ASF Board wish/need to be aware of?:
This Poddlig is one of the listed at IPMC list thread
“Poddlings length of time in the incubator”. This Poddling was stalled
for about two years, however the current new PPMCs have the hope of
increasing the community unlocking the main issue we are facing. We
have had low dev-mailing list activity the pass months, nevertheless
we are working for unlocking our main issue.
How has the community developed since the last report:
General low activity since June.
How has the project developed since the last report:
No visible activity.
How does the podling rate their own maturity:
[ ] Initial setup
[X] Working towards next release
[X] Community building
[ ] Nearing graduation
[x] Other: Working for outcoming our main blocker issue.
Date of last release:
The 0.2.0 release was issued on Jun 29, 2016.
When were the last committers or PPMC members elected?:
2018-05-22 New committer/PMC member Juan P. Gilaberte.
2018-03-28 New committer/PMC member Javi Roman.
Have your mentors been helpful and responsive?:
Yes. In particular Ted Dunning was really helpful for rebooting the
project.
Signed-off-by:
[ ](myriad) Benjamin Hindman
Comments:
[ ](myriad) Danese Cooper
Comments:
[x](myriad) Ted Dunning
Comments:
IPMC/Shepherd notes:
ted: Myriad is in the process of deciding whether to reboot as Apache or
to go independent. This is on the knife edge and I personally don't know
the right answer.
--------------------
Nemo
Nemo is a data processing system to flexibly control the runtime behaviors
of a job to adapt to varying deployment characteristics.
Nemo has been incubating since 2018-02-04.
Three most important issues to address in the move towards graduation:
1. Grow the community
2. Create the first Apache release
3. Donate code to ASF
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
None.
How has the community developed since the last report?
* Committers actively sent PRs and did code reviews
* Committers actively involved in mailing lists
* Getting contributors including a GSoC student
How has the project developed since the last report?
* Made great progress in every aspect of the project
* Working on the first release Almost done with the features to be
included in the first release
* Solidified runtime by refactoring how to handle
tasks, stages, and jobs, and scheduling policies
* Rule-based policy support in the compiler
* Composition of passes
* Added Multiple DAG submission support in a user
program
* Added Beam 2.6, Beam SQL support
* Spark RDD caching support
* Task cloning support
* Intermediate data locality aware scheduling
* Added a WebUI (contributed by a GSoC student),
which we will polish
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:
None yet.
When were the last committers or PPMC members elected?
None yet.
Signed-off-by:
[X](nemo) Davor Bonaci
Comments: All great; active community contributing towards the first
release.
[X](nemo) Hyunsik Choi
Comments:
[X](nemo) Byung-Gon Chun
Comments:
[X](nemo) Jean-Baptiste Onofre
Comments: Focusing on first release would be great, it would be a
great milestone for the podling
[X](nemo) Markus Weimer
Comments: Good progress all around; but it is time for a first release
:)
[ ](nemo) Reynold Xin
Comments:
IPMC/Shepherd notes:
Our mentors mostly have been helpful and responsive.
--------------------
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. Create a first release
2. The project needs more active developers
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
The last report being missed was my bad (oschaaf), I was on vacation
and forgot to ask someone else to do it.
How has the community developed since the last report?
Again, there have been very limited external contributions, two
contributions to the core code-base.
We do see certain users committing to helping out others on the google
group and github, some of them consistently for months now.
In terms of user engagement activity continues to be healthy.
How has the project developed since the last report?
- Problems with Travis timeouts have been mostly fixed
- Flaking dependencies hosted on sourcefourge have been fixed
- Work is still in progress for a particularly nasty bug, which
would be great to have fixed in a first release.
- An external contributor has been maintaining a docker image
for ngx_pagespeed, which should be proposed for inclusion into
the ASF repo soon
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:
N/A
When were the last committers or PPMC members elected?
Feb 2 2018 (Huibao Lin, elected as both committer and PMC member)
Signed-off-by:
[ ](pagespeed) Jukka Zitting
Comments:
[ ](pagespeed) Leif Hedstrom
Comments:
[X](pagespeed) Nick Kew
Comments: A healthy level of activity in github/issues, but the dev
list is looking thin (I don't recollect any of the issues reported
above discussed there), and community development seems slow.
[ ](pagespeed) Phil Sorber
Comments:
--------------------
Omid
Omid is a flexible, reliable, high performant and scalable ACID
transactional framework that allows client applications to execute
transactions on top of MVCC key/value-based NoSQL datastores (currently
Apache HBase) providing Snapshot Isolation guarantees on the accessed data.
Omid has been incubating since 2016-03-28.
Three most important issues to address in the move towards graduation:
1. Get new committers.
2. Finish integration with Apache Phoenix.
3. Get positive feedback from other projects currently in Apache.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
N/A
How has the community developed since the last report?
1. Integration with Apache Phoenix is at its final stage.
2. New active contributor, Yonatan Gottesman.
How has the project developed since the last report?
1. Release 0.9.0 was released on June 10.
2. Omid low latency [OMID-90] committed to a feature branch.
3. Omid and Apache Phoenix integration is at its final stage. The Omid
version for the integration is located at feature branch
phoenix-integration. This feature branch will be the next release candidate
that will start a release process in a few weeks.
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup
[ ] Working towards first release
[X] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
2018-06-10
When were the last committers or PPMC members elected?
Signed-off-by:
[X](omid) Alan Gates
Comments: A criterion for graduation is adding at least one committer
to the project. So I believe "Community building" would be a more
accurate assessment of your podling's maturity.
[ ](omid) Lars Hofhansl
Comments:
[ ](omid) Flavio P. Junqueira
Comments:
[ ](omid) Thejas Nair
Comments:
[x](omid) James Taylor
Comments: I've updated the community assessment to "Community building"
based on Alan's feedback. Once a new committer is added to the project
(which will happen soon), then we can update to "Nearing graduation".
IPMC/Shepherd notes:
--------------------
OpenWhisk
OpenWhisk is an open source, distributed Serverless computing platform able to
execute application logic (Actions) in response to events (Triggers) from
external sources (Feeds) or HTTP requests governed by conditional logic
(Rules). It provides a programming environment supported by a REST API-based
Command Line Interface (CLI) along with tooling to support packaging and
catalog services. Additionally, it now provides options to host the platform
components as Docker containers on various Container Frameworks such as Mesos,
Kubernetes, and Compose.
OpenWhisk has been incubating since 2016-11-23.
Three most important issues to address in the move towards graduation:
1. Finish the remaining component source code release under Incubator
a. Release process/automation/documtantion are here
https://github.com/apache/incubator-openwhisk-release).
2. Increase additional company and individual Contributors to maintain all
project repos. and address Issue / PR backlog.
3. Close legal transferred of Trademark handoff for "OpenWhisk" name and
logo to ASF
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of?
* Issue backlog building on incubator-openwhisk is still a major issue
(partly due to #2 above). As of this report, the "open" issue backlog is 384
(up from 365 as of last report), but open PR is at 35 (down from 55 as of last
report). Please note this is just on the "main" platform repo. and likely is
paralleled in other release component repos.
* Need to prioritize and work to reduce while advancing major proposals
around restructuring around abstractions to accommodate running on Knative
while enhancing support for better logging/scheduling and performance testing
enhancements.
* Trying to add more active Committers to augment those who have
dropped off in their activity; however, we have reached an impasse where
potential new Contributor pull requests are not getting timely reviews/merges
to provide a resume' for adding to the Committer roles.
* It seems that Apache Infra. will not provide us servers to host a staging
environment that would help us perform needed staging testing on Pull Requests.
This means that independent testing needs to be done by members (companies).
We have explored a corporate donation as suggested (ala Spark and SystemML),
but this does not seem possible at this time.
* No change in status since last quarterly report.
* Formal hand-off of OpenWhisk trademark/logo from IBM needs to be
executed; need to identify process for this. See #3 above.
* Discussion started w/ Apache legal via "legal-discuss" mailing list
with subject "Trademark handoff for "OpenWhisk" name and logo".
* IBM intends to hand-off ownership of trademarks at time of graduation.
How has the community developed since the last report?
* dev mailing list activity increased since Q2 driven by release-related
activity and an increase in technical discussion on the mailing list.
* incubator-openwhisk Github stars: 3472 (+254 since last report)
* incubator-openwhisk GitHub forks: 652 (+36 since last report). Note lots
of more competing projects entering the Serverless space.
* Slack community:
* 969 members (+151 from last report). Very active in most channels
from both end users or the project and contributors
* To-date: 112,326 messages sent across all channels
* Analytics: https://openwhisk-team.slack.com/admin/stats
* The bi-weekly Zoom "Technical Interchange" continues to be well received
and attended.
* Complete videos posted to OW YouTube channel and detailed notes to
our CWIKI.
* YouTube Channel: Apache Meetings Playlist
* CWiki Meeting Notes: OpenWhisk Technical Interchange Meeting Notes
* 2018-08-29:
https://cwiki.apache.org/confluence/display/OPENWHISK/2018-08-29+OW+Tech+Interch
ange+-+Meeting+Notes
* 2018-08-15:
https://cwiki.apache.org/confluence/display/OPENWHISK/2018-08-15+OW+Tech+Interch
ange+-+Meeting+Notes
* 2018-08-01:
https://cwiki.apache.org/confluence/display/OPENWHISK/2018-08-01+OW+Tech+Interch
ange+-+Meeting+Notes
* 2018-07-18:
https://cwiki.apache.org/confluence/display/OPENWHISK/2018-07-18+OW+Tech+Interch
ange+-+Meeting+Notes
* 2018-06-20:
https://cwiki.apache.org/confluence/display/OPENWHISK/2018-06-20+OW+Tech+Interch
ange+-+Meeting+Notes
* 2018-06-06:
https://cwiki.apache.org/confluence/display/OPENWHISK/2018-06-06+OW+Tech+Interch
ange+-+Meeting+Notes
* New Contributors
* ICLAs received:
* Qian Gao (gaoqian126@126.com), No intentions submitted (is this
Albert Gau from Cloud Academy?)
* Manoj Mishra (manojmishra404@gmail.com)
(https://github.com/manojkmishra), Looking at integrating the "Karate" test
framework into OpenWhisk working with Rahul.
* Rahul Tripathi (er.rahultr@yahoo.com)
(https://github.com/rahulqelfo), Leading the "Karate" test framework
integration (proposed). See https://github.com/rahulqelfo/ow-karate
* Justin Halsall, IBM Developer Advocate based in NYC, Submitted
the Ruby runtime, helped update/correct website content, added CLI and
wskdeploy to Homebrew to provide convenient installs on Linux, Mac, and
Windows. Seeks to improve end-user experience and documentation.
* Kei Sawada (k@swd.cc)(https://github.com/remore) (@remore), Red
Hat, DevOps consultant, No intentions submitted.
* Joined Community Interchange calls and introduced themselves:
* Mparuthickal (Matthew) - NYC, last 4-5 months been exploring OW,
delivering all data fabric via OW api
* Viay - also trying to inc. OW in our environment, doing PoC using
OW last 2 months
* Sam Baxter - 2nd call, phd student at UMass an IBM intern,
looking at long-running computations using javascript
* Spencer Krum, Similar job as Justin, works at IBM as an advocate;
wishes to become active in community.
How has the project developed since the last report?
Emphasis on these areas have been featured since last report:
* Google Knative announce
* The announcement of Knative has elicited LOTS of discussion on
dev list and during interchange calls, as well as proposals on the Wiki, as to
how OpenWhisk can better align/position itself relative to this Kubernetes
(family) technology. See some of the proposal discussions:
* Knative, Kubernetes, and Apache OpenWhisk
* Prototyping for a future architecture
* Proposal on a future architecture of OpenWhisk
* Kafka and Proposal on a future architecture of OpenWhisk
* Simplifying configuring OpenWhisk Components (#3984)
* Naver has asked to be listed as both a project Supporter and an
acknowledged OpenWhisk provider
* Logo added: http://openwhisk.apache.org/community.html#supporters
* Release process
* Please see incubator-openwhisk-release (code, tools,
documentation), see demo (as of 2/28):
https://www.youtube.com/watch?v=qkqenC5b1kE
* So far we have release the following components
* [RESULT][VOTE]: Release Apache OpenWhisk (Incubating): main
module 0.9.0 [RC2]
* https://lists.apache.org/thread.html/44d91b570ba51e7c88eff59aaca04a83fcad706bdabf4614baadac3f@%3Cdev.openwhisk.apache.org%3E
* [RESULT][VOTE] Release Apache OpenWhisk 0.9.0-incubating rc1:
OpenWhisk catalog and apigateway
* https://lists.apache.org/thread.html/8df308901539b825466505e7e51df32ba511fa2a39de8335a694bd05@%3Cdev.openwhisk.apache.org%3E
* [RESULT][VOTE] Release Apache OpenWhisk (Incubating): Client
Go and CLI 0.9.0 [RC1]
* https://lists.apache.org/thread.html/7985c7ad9528fada0efa4093d67ae47d78ba0dcf2f1f7f5916570f69@%3Cdev.openwhisk.apache.org%3E
* [RESULT][VOTE] Release Apache OpenWhisk 0.9.8-incubating rc1:
OpenWhisk wskdeploy
* https://lists.apache.org/thread.html/caea29e3b3c8ea56f5bb3e40ee4b57153787ef193dc64ff63024230b@%3Cdev.openwhisk.apache.org%3E
* with these components being prepared for the voting process:
* Runtimes (i.e., NodeJS, Python, Java, Go, Ruby, Swift, etc.)
* The comm. is currently discussing how to align versions
(i.e., rebase to same version level) for all runtime components
(e.g., Java, JS, Python, Ruby, etc.) now:
* Re: [DISCUSSION]: Proposing to use 1.12.0 as the version
for all runtimes for the first-time
* https://lists.apache.org/thread.html/7df7764fc6a0f33580ab5666645b61d857c5492ca6e1d2438c2518e8@%3Cdev.openwhisk.apache.org%3E
* Providers (i.e., Alarms, Kafka/MessageHub, Cloudant/Couch)
* The community anticipates producing a combined 1.x release (of
all components at once) in the near future under a single tar.gz.
* Website revamp
* See proposal here (with proof that no information was lost in
transitioning):
* OpenWhisk Website Redesign:
https://cwiki.apache.org/confluence/display/OPENWHISK/OpenWhisk+Website+Redesign
* Apache Compliant: Updated to be fully compliant with Apache
standards: see https://whimsy.apache.org/pods/project/openwhisk
* Canonical starting point for all things Apache OpenWhisk
* Role-based
* The entire website was revamped and streamlined to
include only current info targeted to 2 roles: Developer and Operator
* See Documentation:
http://openwhisk.apache.org/documentation.html
* Indexed all content and added left-side navigation
* Provided initial "getting started" examples for all language
runtimes (using CLI and wskdeploy
* Leveraged github repo content, and created proper linkage to
further resources (no broken links)
* Assured we had no redundant information
* leverage CWiki
* In addition, we cleaned up (and organized) the project
Confluence Wiki: https://cwiki.apache.org/confluence/display/OPENWHISK
* and the Cwiki content now has proper ANCHORS that we
reference from our project website.
* Media Adaptive Content: Verified website worked in all major
browsers and on all device form-factors (mobile, tablet, and desktop)
* Security enhancements
* PureSec contacted PPMC about a runtime security vulnerability,
Rodric Rabbah took the lead in addressing and followed the Apache process (as
the project is mature for an Incubator project and we are aware that
companies have OW in production)
* [CVE] CVE-2018-11756 PHP Runtime for Apache OpenWhisk
* [CVE] CVE-2018-11757 Docker Skeleton Runtime for Apache
OpenWhisk
* Here is the Apache OpenWhisk project blog (Medium) explaining
the vulnerability and how it was closed by the team:
* https://medium.com/openwhisk/security-and-serverless-functions-b97618430db6
* Scalability / Performance / Testing
* Presentation/proposals to integrate the Karate Web Service Test
Framework into OW. Intent is not to overlap or replace exiting Scala
tests but to allow Java developers the ability to submit new test cases
more easily. See
https://github.com/intuit/karate.
* Thread: OpenWhisk Karate Based BDD Functional and Performance
Tests
* BDD Test Cases Contribution to complement existing test cases and
coverage
* Runtime updates:
* New runtime for the Ballerina language: Proposing Ballerina
Runtime for OpenWhisk
* Github repo.:
https://github.com/apache/incubator-openwhisk-runtime-ballerina
* Other Notable discussions/changes/issues/features:
* [Discussion] Use TransactionID as ActivationID
* Re: Proposal: Memory Aware Scheduling
* logging baby step -- worth pursuing?
* Pluggable API Gateways
* Re: AI Actions as a first-class citizen in OpenWhisk
* MiniWhisk: what you think?
* Proposing Lean OpenWhisk
* System overflow based on invoker status
* Add support for microkernels instead of containers
How would you assess the podling's maturity? Please feel free to add your own
commentary.
[ ] Initial setup
[X] Working towards first release (nearly complete, see above)
[X] Community building
[X] Nearing graduation
[ ] Other:
Comments:
* Need greater variety of contributors and contributing companies
Date of last release:
* Various, by component, see above for details
When were the last committers or PPMC members elected?
* New Committers+PPMC:
* Ben Browning, Red Hat
* Brendan McAdams, Red Hat
* Sven Lange-Last, IBM
* Tyson Norris, Adobe, added to PPMC (already a Committer)
* New Committers:
* No new Committers
Signed-off-by:
[x] (openwhisk) Bertrand Delacretaz
Comments:
[X] (openwhisk) Jim Jagielski
Comments:
[ ] (openwhisk) Isabel Drost-Fromm
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. Growing community and interest around the project
2. Step up pace of branch development
3. Fine-tune release process
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
Pony Mail is in a bit of a slumber at the moment, with the principal
people being busy elsewhere. This is not to say that oversight isn't
happening, but that the development pace has slowed significantly.
We hope this picks up in the foreseeable future.
How has the community developed since the last report?
Sharan Foga has joined as a new mentor. We are assessing whether there
is need for more people to help out.
How has the project developed since the last report?
Not much to report here, a few bug fixes and issues filed.
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:
2018-02-19
When were the last committers or PPMC members elected?
Sebastian Bazley was elected committer in Oct, 2016.
Signed-off-by:
[ ](ponymail) Andrew Bayer
Comments:
[X](ponymail) John D. Ament
Comments:
[x](ponymail) Sharan Foga
Comments:Good to see community building being highlighted as something
to work on.
IPMC/Shepherd notes:
wave (Dave Fisher): I would ask what this project that has become core to
ASF infra with lists.apache.org needs to do before graduating?
--------------------
Pulsar
Pulsar is a highly scalable, low latency messaging platform running on
commodity hardware. It provides simple pub-sub semantics over topics,
guaranteed at-least-once delivery of messages, automatic cursor management
for subscribers, and cross-datacenter replication.
Pulsar has been incubating since 2017-06-01.
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?
Earlier in June there have been few discussions on the private list
regarding communications regarding Pulsar that were not coming from
PPMC or that were not respecting the ASF policies. Clarifications
followed between PPMC members, mentors and interested parties to
ensure the mistakes were made in good faith and, in particular, to
make sure everyone was fully has full understanding of ASF
policies. There was no other branding related issue after the first
occurrence.
How has the community developed since the last report?
The community added 8 new contributors that submitted pull-requests
which were merged into master.
The number of users approaching the team on the Slack channel has
kept steadily increasing since the last report. Many users have
actively deployed. Pulsar for evaluation and production use cases.
Different meetups were organized by project members and hosted by
Yahoo in Sunnyvale and Yahoo Japan in Tokyo. We have presented
Pulsar's introductions, updates on the state of the projects,
deep-dives and hands-on tutorial, including recorded podcasts.
One talk on Pulsar was presented at one at OSCon in July and there
are several scheduled talks: 2 at ApacheCon in September, and 2
others at Strata New York in September.
Since the last report the number of weekly-active-users on the Slack
channel has increased from 53 to 88.
How has the project developed since the last report?
28 authors have pushed 494 commits to master in the last 3 months.
The project has made the its seventh release since joining the
Apache Incubator (2.1.0-incubating on Aug 2nd).
This release introduced these new features:
* Pulsar IO: A connector framework for moving data in and out of
Apache Pulsar leveraging Pulsar Functions runtime.
* A number of builtin connectors: (Aerospike, Cassandra, Kafka,
Kinesis, RabbitMQ, Twitter)
* Tiered Storage: An extension in Pulsar segment store to offload
older segments into long term storage (e.g. HDFS, S3). S3 support
is supported in 2.1 release.
* Stateful function: Pulsar Functions is able to use State API for
storing state within Pulsar.
* Pulsar Go Client
* Avro and Protobuf Schema support
Community is actively working on a bug-fix release
(2.1.1-incubating) and on the next milestone, 2.2 release for which
the biggest feature will be support for SQL within Pulsar.
Since June, 5 new PIPs (Pulsar Improvement Proposals) for
major feature/changes, have been submitted to the wiki and
discussed in the mailing list.
PIP 23: Message Tracing By Interceptors
PIP 22: Pulsar Dead Letter Topic
PIP 21: Pulsar Edge Component
PIP 20: Mechanism to revoke TLS authentication
PIP 19: Pulsar SQL
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:
2018-08-02, 2.1.0-incubating
When were the last committers or PPMC members elected?
2018-06-11 - Ivan Kelly
2018-06-11 - Jia Zhai
Signed-off-by:
[X](pulsar) Dave Fisher
Comments: Looking forward to the graduation resolution.
[X](pulsar) Jim Jagielski
Comments:
[X](pulsar) P. Taylor Goetz
Comments: Good report. At the urging of mentors, Pulsar completed a
maturity model evaluation, which I think worked well. They also dealt
with the branding issue fairly well after realizing how important such
issues are to the Foundation.
Currently moving toward graduation, which I support.
[ ](pulsar) Francis Liu
Comments:
IPMC/Shepherd notes:
--------------------
Quickstep
Quickstep is a high-performance database engine.
Quickstep has been incubating since 2016-03-29.
Three most important issues to address in the move towards graduation:
1. Adoption of the Quickstep technology.
2. Grow the Quickstep developer community.
3. Work towards a second 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?
Harshad presented the Quickstep paper at VLDB 2018 conference in Rio De
Janeiro, Brazil.
The presentation was attended by many database researchers and industry
practitioners.
The presentation had explicit calls to collaborate and participate in the
Apache community.
We plan to reach out with those who expressed interest in the project.
How has the project developed since the last report?
The development activity was slow during the summer.
There are ongoing efforts on the following objectives.
1. Enhancing the type system used by Quickstep
2. Supporting concurrent queries in the system
3. Developing a distributed version of Quickstep
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup
[ ] Working towards first release
[x] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
2017-03-25
When were the last committers or PPMC members elected?
Dylan Bacon, June 2 2018 (committer)
Signed-off-by:
[x](quickstep) Julian Hyde
Comments: I am becoming worried about the project. Development
continues at a reasonable pace, and serves the needs of existing
contributors who are producing research papers. The "following
objectives" listed above were not discussed on-list, AFAICT.
However Quickstep is unable to attract outside contributors, nor
apparently achieve adoption by end users.
It is nearly 18 months since the last release. I will encourage
them to make a new release. That will generate some activity, but it
may not be enough.
[x](quickstep) Roman Shaposhnik
Comments: Big +1 to what Julian is saying. Also, see the following
thread on general: https://s.apache.org/Y6tt
IPMC/Shepherd notes:
--------------------
S2Graph
S2Graph is a distributed and scalable OLTP graph database built on Apache
HBase to support fast traversal of extremely large graphs.
S2Graph has been incubating since 2015-11-29.
Three most important issues to address in the move towards graduation:
1. Make a third release.
2. Attract more users and contributors.
3. Build the developer community in both size and diversity.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
None
How has the community developed since the last report?
* not much activities on the mailing list.
* few active committers spend their time working on opened issues.
How has the project developed since the last report?
* mostly still working on opened issues.
- 22 issues are created and 16 of them are resolved since the last
report(June 2018).
- keep working on GraphQL integration/OLAP supports.
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup
[ ] Working towards first release
[X] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
2017-08-26
When were the last committers or PPMC members elected?
None
Signed-off-by:
[ ](s2graph) Andrew Purtell
Comments:
[ ](s2graph) Seetharam Venkatesh
Comments:
[X](s2graph) Sergio Fernández
Comments:
IPMC/Shepherd notes:
--------------------
SAMOA
SAMOA provides a collection of distributed streaming algorithms for the
most common data mining and machine learning tasks such as classification,
clustering, and regression, as well as programming abstractions to develop
new algorithms that run on top of distributed stream processing engines
(DSPEs).
It features a pluggable architecture that allows it to run on several DSPEs
such as Apache Storm, Apache S4, and Apache Samza.
SAMOA has been incubating since 2014-12-15.
Three most important issues to address in the move towards graduation:
1. Revitalize the project by resuming development
2. Enlarge the user base and contributing community
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?
None
How has the community developed since the last report?
* Mailing list activity (June 2018 - August 2018):
* @dev: 19 messages
How has the project developed since the last report?
* 2 new PRs created
* Presentation at KDD 2018 (MUD3 workshop) on urban data mining using
Apache SAMOA
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup
[ ] Working towards first release
[X] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
2016-09-30
When were the last committers or PPMC members elected?
January 2018
Signed-off-by:
[X](samoa) Alan Gates
Comments: I agree with Ted, I remain concerned about the lack of
activity in this podling.
[ ](samoa) Ashutosh Chauhan
Comments:
[ ](samoa) Enis Soztutar
Comments:
[x](samoa) Ted Dunning
Comments:
IPMC/Shepherd notes:
ted: Almost no mailing list activity since April. March looked promising,
but after voting in a new committer, nothing much else happened.
--------------------
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. Extending release process to other parts of the SensSoft software stack.
2. Grow the Apache SensSoft (Incubating) Committer/Community Base.
3. Complete the issues highlighted at the SensSoft Roadmap
https://cwiki.apache.org/confluence/display/SENSSOFT/Roadmaps
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
Yes. In the last Quarter, a number of core Apache SensSoft committers
changed organization. While the Apache SensSoft team will use this as an
opportunity to organically grow the committer/community based, these
departures have caused branding concerns for the organization that
initiated the Apache SensSoft software gift to Apache—The Charles Stark
Draper Laboratory, Inc. (Draper). Specifically, in referencing an
affiliation with the ‘Apache SensSoft’ project at different organizations,
an Apache SensSoft committer received the following request from Draper:
“We flagged your signature for review by Draper legal since SENSOFTtm and
Software as a Sensor (R) are Draper-owned trademarks. As you know, the main
purpose of trademarks is to avoid customer confusion. We believe that the
use of SENSOFT or SOFTWARE AS A SENSOR in [another company’s] employee
signature block may lead to confusion as to the source and owner of the
SENSOFT product. While we appreciate your acknowledgement that Draper owns
SOFTWARE AS A SENSOR and SENSOFT technology, and the good will behind your
intentions to promote technology you worked on while at Draper, in order to
preserve the Draper trademarks we respectfully request that you either:
-Remove any reference of SENSOFT or SOFTWARE AS A SENSOR from your BAE
signature block; OR -Indicate in the signature directly following SENSOFT
the following: “SENSOFTtm and SOFTWARE AS A SENSOR are trademarks owned by
the Charles Stark Draper Laboratory, Inc.” NOTE: SENSOFT refers to
SENSSOFT (SENSOFT is a misspelling) The committer in question has
corresponded Draper and raised the issue that ‘Apache SensSoft’ refers to a
public open source project, where ‘Software as a Sensor’ and ‘SENSSOFT’
refer to Draper proprietary technology, as well as citing the terms of the
Software Gift. Draper is steadfast in asserting rights now that committers
formerly at Draper are now at other employers. While this affects the
Apache SensSoft community’s ability to grow through outreach and publicity,
we do not believe we require Legal assistance from the ASF. Rather, in
discussion with both Draper and Apache SensSoft PPMC/Champions, the path of
least resistance appears to be to change the Apache SensSoft project name.
The PPMC will initiate a vote on @dev for changing the name. If it passes,
a subsequent vote will determine the projects new name. In the meantime,
committers will begin removing references to Software as a Sensor(tm) from
project documentation.
How has the community developed since the last report?
Several community members have started new employment opening opportunities
for community growth in the last quarter. No new community members have
come onboard.
How has the project developed since the last report?
Development continues at a sustainable level. Several major improvements
have been made to make the Apache SensSoft stack deployable at various
levels of scale, including major improvements to documentation and
examples, and testing procedures. Project maturity roadmaps (Wiki) and
version release plans (JIRA) continue to be maintained.
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[X] Initial setup
[X] Working towards first release
[X] Community building
[X] Nearing graduation
[ ] Other:
Date of last release:
2018-03-14
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: There are several issues identified above which, as would be
expected, have somewhat stunted sustained growth. SensSoft is still
however on track to graduation with motivation for graduation still
present. The above report was produced by a PPMC member this time
around, NOT the mentoring team.
[X](senssoft) Chris Mattmann
Comments:
IPMC/Shepherd notes:
Dave Fisher - I've pointed the podling to the suitable name search and
reminded them that they need to look into more than the name
of the project. They need to check their product names like UserAle,
TAP, Distill and Stout.
--------------------
SINGA
SINGA
SINGA is a distributed deep learning platform.
SINGA has been incubating since 2015-03-17.
Three most important issues to address in the move towards graduation:
1. Build and collect the information about the user community
2. Release V2.0
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?
Two new contributors since the last report.
How has the project developed since the last report?
The development was focusing on the autograd feature [SINGA-371, 382-385,
387-389, etc.], which is almost done.
Every layer operation of Singa now supports autograd.
There are 24, 56 and 26 emails in the mailing list for June, July and
August respectively.
There are 80 commits since last report.
How would you assess the podling's maturity?
Singa has a diverse developer community.
We need to collect the user community information and encourage open
discussion on the mailing list.
Please feel free to add your own commentary.
[ ] Initial setup
[ ] Working towards first release
[ ] Community building
[X] Nearing graduation
[ ] Other:
Date of last release:
2018-06-06
When were the last committers or PPMC members elected?
2017-09-01
Signed-off-by:
[ ](singa) Daniel Dai
Comments:
[X](singa) Alan Gates
Comments: Development in this project has picked up, and they have
successfully done releases and added contributors. I agree they are
nearing graduation.
[x](singa) Ted Dunning
Comments:
[ ](singa) Thejas Nair
Comments:
IPMC/Shepherd notes:
--------------------
SkyWalking
Skywalking is an APM (application performance monitor), especially for
microservice, Cloud Native and container-based architecture systems. Also
known as a distributed tracing system. It provides an automatic way to
instrument applications: no need to change any of the source code of the
target application; and an collector with an very high efficiency streaming
module.
SkyWalking has been incubating since 2017-12-08.
Three most important issues to address in the move towards graduation:
1. IP clearance.
3. First ASF release. (SkyWalking 5.0)
3. Further ASF culture and processes.
4. 5.x releases are stable for product, and have 5 open end users, at
least.
5. Support multiple languages agents/SDKs.
6. Integration with other pupolar OSS systems. Zipkin data format
supported.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
Have three Apache releases already. 5.0.0-alpha, 5.0.0-beta, 5.0.0-beta2.
Another release is on going, 5.0.0-RC
How has the community developed since the last report?
1. .NetCore agent goes well, as a community agent implementation, have
received it is being used in product env.
2. Node.js agent supports `egg` framework, releases the new version.
3. More than 35 companies have confirmed they are using SkyWalking
through issue report or our powered-by page.
4. There are 57 people to contribute codes to our main repo. 19 more than
the last report.
How has the project developed since the last report?
The project has a diverse community, many users, contributors are from
different companies.
There has been 100 commits by more than 30 contributors in the three
months.
In beta2 release milestones, there are 160 issues and pull requests
solved.
In RC release milestones, there are 124 issues and pull requests solved.
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:
beta2 12 Jul 2018
RC(voting) 30 Aug 2018
When were the last committers or PPMC members elected?
May. 2018
Signed-off-by:
[X](skywalking) Luke Han
Comments:
[X](skywalking) Willem Ning Jiang
Comments: It's great to see Skywalking has attracted lot of contributor
and user durning the incubation.
[X](skywalking) Mick Semb Wever
Comments:
[X](skywalking) Ignasi Barrera
Comments:
IPMC/Shepherd notes:
--------------------
Spot
Apache Spot is a platform for network telemetry built on an open data model
and Apache Hadoop.
Spot has been incubating since 2016-09-23.
Three most important issues to address in the move towards graduation:
1. Revive community activity (Discussion in mailing lists, increase
frequency of commits).
2. Make it easier for Devs to create plug-ins for ingest of data.
3. Developing a workflow in Spot that allows intuitive analytics without
the need of licensed software.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?
N/A
Have your mentors been helpful and responsive or are things falling through
the cracks?
Due to the community’s irregular activity level over the past months we
have had trouble aligning with our mentors.
The project is in the process of establishing a cadence to our activities
and we welcome help and advice from mentors.
How has the community developed since the last report?
Project wide meetings are continuing every 2 weeks. We are starting to see
more Pull Requests come in. Hoping that the end of summer (end of
vacations) will bring further participation from the community. We are
working on updating the Spot website and confluence pages to reflect
changes in the project.
How has the project developed since the last report?
A roadmap draft has been constructed. Our next focus is creating a new
release. Therefore, work is underway on closing some long running Pull
Requests and important bug fixes.
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup
[ ] Working towards first release
[X] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
2017-09-08
When were the last committers or PPMC members elected?
2018-01-18
Signed-off-by:
[ ](spot) Jarek Jarcec Cecho
Comments:
[ ](spot) Brock Noland
Comments:
[ ](spot) Andrei Savu
Comments:
[X](spot) Uma Maheswara Rao G
Comments:
IPMC/Shepherd notes:
--------------------
Superset
Superset is an enterprise-ready web application for data exploration, data
visualization and dashboarding.
Superset has been incubating since 2017-05-21.
Three most important issues to address in the move towards graduation:
1. Plan and execute our first Apache release
2. Align on a long-term product roadmap with the broader Apache Superset
community
3. Grow the community and enroll new committers
Any issues that the Incubator PMC or ASF Board might wish/need to be aware
of?
* At this point in time, we’re having issues on how to come up with the
LICENSE file needed for our first Apache release given the number of
dependencies we have on the Javascript side. Since we package the JS
bundle along with our Python application, it seems like we'll have to
come up with either a programmatic way to extract the LICENSE info, or ship
the application without the JS deps, and provide instruction has to how to
fetch and build the package deps, which isn't very convenient. We also have
some minor deps on GPL lib, one of which we need to get clarity as to how
to to handle them. It's related to the "chardet" sub dependency of the Pypi
requests library.
Currently, we believe there are 2 approaches to dealing with the LICENSE
and NOTICE files for Superset. Either:
A) Dynamically building these files by querying npm/pypi (the javascript
and python package repositories) for all the metadata and assembling these
files. See the list of JS packages organized by licenses here:
Https://github.com/apache/incubator-superset/pull/5801
B) The other approach is to distributed a stripped down version of Superset
that has a script that fetches external deps and builds it.
The committers are activating around these issues and thinking creatively
about resolving them. A thread on dev@superset.incubator.apache.org was
started and a discussion is taking place.
How has the community developed since the last report?
* Organic growth of our Github contributors (246->274), forks (3318->3627),
watchers
(1020->1077) and stars (19,399->20,519)
* Group of active committers meeting bi-weekly from Airbnb, Lyft and
Twitter. Added Michelle Thomas as a new committer.
How has the project developed since the last report?
* A completely redesigned dashboarding experience launched
* Big Number charts have a new look and visualization
* In the Table Config & SQL Lab -> Explore View, clicking a data source now
opens a modal with table editing for settings, columns, calculated columns,
& metrics
* Addition of integration and functional tests
* A healthy, constant flow of bug fixes, quality improvements and new
features, take a look at the project’s Pulse on Github for more details
How does the podling rate their own maturity.
[ ] Initial setup
[X] Working towards first release
[ ] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
No official release yet since being voted into Apache
Incubation. (Planning for the first Apache release in Q4, 2018)
When were the last committers or PPMC members elected?
* Michelle Thomas - Committer (2018-09-01)
Signed-off-by:
[ ](superset) Ashutosh Chauhan
Comments:
[ ](superset) Luke Han
Comments:
[X](superset) Jim Jagielski
Comments: A number of issues have been brought up to the PPMC
IPMC/Shepherd notes:
--------------------
Tamaya
Tamaya is a highly flexible configuration solution based on an modular,
extensible and injectable key/value based design, which should provide a
minimal but extendible modern and functional API leveraging SE, ME and EE
environments.
Tamaya has been incubating since 2014-11-14.
Three most important issues to address in the move towards graduation:
1.release new versions compliant with configJSR, rework API
2.grow the community, get more active participants
3.graduate as the project is functionally very mature already
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
We'd like to graduate after 0.4 is out.
How has the community developed since the last report?
New external contributors: Aaron Coburn, William Lieurance
How has the project developed since the last report?
* minor bugfixes and small changes (due to summer holidays)
* relatively low traffic on mailing lists
* some interest via mail/contributions from external people/possibly new
contributors
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup
[ ] Working towards first release
[X] Community building
[X] Nearing graduation
[ ] Other:
Date of last release:
2018-05-27 v0.3-incubating
When were the last committers or PPMC members elected?
P. Ottlinger at 2016-04-24.
Signed-off-by:
[ ] David Blevins
Comments:
[X] John D. Ament
Comments: The podling shows a lot of potential, but I'm not sure there's
enough for it to move forward as a TLP.
IPMC/Shepherd notes:
--------------------
Taverna
Taverna is a domain-independent suite of tools used to design and execute
data-driven workflows.
Taverna has been incubating since 2014-10-20.
Three most important issues to address in the move towards graduation:
1. Re-engage PPMC members
2. Graduate?
3.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
INFRA-16698 is pending comments from Daniel Gruno / IPMC on how
to manage incubator repositories on git-wip-us.apache.org that have
been retired (in our case transferred to another GitHub organizations).
The suggestion is to do a "git rm" and leave a README on the head commit
pointing to the new location.
See also
https://lists.apache.org/thread.html/b4672999838a64a1883407f0c827d7d40fdef13
f2424fa5465e944c3@%3Cgeneral.incubator.apache.org%3E
How has the community developed since the last report?
2 Google Summer of Code students have been active over the summer with
strong guidance from mentors and getting pull requests merged.
However the rest of the community has been very quiet and not
commented much on the GSOC progress or pull requests.
How has the project developed since the last report?
Good progress from GSOC students, which code bases are now
due a new release to include their changes.
Two legacy git repositories were retired to not go through
graduation (INFRA-16698).
There is not much outstanding towards graduation, except
re-engaging the PMC members.
We will have to admit we are a slow project, which is
OK (many Apache projects are), yet still there seems
to be some kind of incubator fatigue - for
instance no-one else picked up the job of doing this
report although prompted to do so by a mentor.
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
[x] Other: PPMC dormant?
Date of last release:
2018-01-18
When were the last committers or PPMC members elected?
2018-02-26 (PPMC)
Signed-off-by:
[x](taverna) Andy Seaborne
Comments:
The PPMC needs to work on a graduation plan. Graduation should
not be a major task for Taverna but it does need doing.
[ ](taverna) Daniel J Debrunner
Comments:
[ ](taverna) Marlon Pierce
Comments:
[x](taverna) Stian Soiland-Reyes
Comments:
GSOC activity may have taken focus from work
towards graduation in this period.
[ ](taverna) Suresh Marru
Comments:
[ ](taverna) Suresh Srinivas
Comments:
IPMC/Shepherd notes:
--------------------
Tephra
Tephra is a system for providing globally consistent transactions
on top of Apache HBase and other storage engines.
Tephra has been incubating since 2016-03-07.
Two most important issues to address in the move towards graduation:
1. Improve community engagement
2. Increase adoption
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
- None at this time.
How has the community developed since the last report?
- 5 new JIRAs filed since the last report
- 1 new subscriber in dev mailing list since the last report
How has the project developed since the last report?
- Tephra 0.15.0-incubating released
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup
[ ] Working towards first release
[x] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
2018-09-04
When were the last committers or PPMC members elected?
- None since coming to incubation
Signed-off-by:
[X](tephra) Alan Gates
Comments:
[ ](tephra) Andrew Purtell
Comments:
[x](tephra) James Taylor
Comments:
[ ](tephra) Lars Hofhansl
Comments:
IPMC/Shepherd notes:
Dave Fisher: This podling thinks they are near graduation, but has never
added any new committers/PPMC members. Not so sure. I sent a message to the
podling about this.
Alan Gates: This is my fault. See email thread
https://lists.apache.org/thread.html413e06bde2263f2f56797e871b256ec1584f8c5
41fdc5e96857b13f5@%3Cdev.tephra.apache.org%3E where I started pushing them
towards determining their future direction. I assumed they had added
additional PPMC members without checking. I can take this feedback back to
them and help them work through this.
James Taylor: I've updated the community assessment to "Community building"
based on the above feedback.
--------------------
Warble
Warble has been incubating since 2018-06-11
Warble is a distributed endpoint monitoring solution where the agent is
hosted
on your own hardware.
Three most important issues to address in the move towards graduation.
1. Engage initial committers.
2. Set core design and feature set, avoid creep of new features before
the core is complete.
3. Expand committers and community
Any issues that the Incubator PMC or ASF Board might wish/need to be aware
of:
none
How has the community developed since the last report?
This is the first report since entering the Incubator. Community
involvement has slowly increased.
How has the project developed since the last report?
This is the first report since entering the Incubator. Code has been
donated and work has been done on initial designs and documentation.
How would you assess the podling's maturity?
We're working through initial design as most of the donated code will need
to be re-written/adapted to what we want to do with Warble. Community
input has been good working towards documentation and initial code updates.
[X] Initial setup
[ ] Working towards first release
[X] Community building
[ ] Nearing graduation
[X] Other: Building initial designs and re-writing donated code
Date of last release:
N/A
When were the last committers or PPMC members elected?
N/A
Signed-off-by:
[X](warble) Daniel Takamori
Comments:
IPMC/Shepherd notes:
Justin Mclean: You might go toward solving 1 by adding the initial
committers and mentors to the roster. I also note this is your first
report when in you should of been reporting for every one of the
first three months.
Daniel Gruno: Chris actually did try to report earlier (I have said
reports), but did not find Warble listed in the monthly report document.
Bug in the system?
--------------------
Zipkin
Zipkin has been incubating since 2018-08-30
Zipkin is a distributed tracing system. It helps gather timing data needed
to troubleshoot latency problems in microservice architectures. It manages
both the collection and lookup of this data. Zipkin’s design is based on
the Google Dapper paper.
Three most important issues to address in the move towards graduation.
1. Initial committers ICLAs
2. Migrate GitHub repositories
3. Migrate website
Any issues that the Incubator PMC or ASF Board might wish/need to be aware
of:
none
How has the community developed since the last report?
N/A
How has the project developed since the last report?
N/A
How would you assess the podling's maturity?
Zipkin only entered the Incubator just over a week ago.
The project DNS and mailing lists have been setup.
Currently in progress is git repository migration.
Otherwise the community is still handing in ICLAs and learning up on ASF.
[X] Initial setup
[ ] Working towards first release
[ ] Community building
[ ] Nearing graduation
[ ] Other: Building initial designs and re-writing donated code
Date of last release:
N/A
When were the last committers or PPMC members elected?
N/A
Signed-off-by:
[X](zipkin) Mick Semb Wever
Comments:
[X](zipkin) Andriy Redko
Comments:
[X](zipkin) John D. Ament
Comments:
[ ](zipkin) Willem Ning Jiang
Comments:
IPMC/Shepherd notes:
}}}
-----------------------------------------
Attachment AE: Report from the Apache Jackrabbit Project [Michael Dürig]
Report from the Apache Jackrabbit committee [Michael Dürig]
## Description:
The Apache Jackrabbit™ content repository is a fully conforming
implementation of the Content Repository for Java™ Technology API
(JCR, specified in JSR 170 and 283). The Jackrabbit content repository is
stable, largely feature complete and actively being maintained. Jackrabbit
Oak is an effort to implement a scalable and performant hierarchical content
repository as a modern successor to the Apache Jackrabbit content
repository. It is targeted for use as the foundation of modern world-class
web sites and other demanding content applications. In contrast to its
predecessor, Oak does not implement all optional features from the JSR
specifications and it is not a reference implementation.
## Issues:
There are no issues requiring board attention at this time
## Activity:
Apache Jackrabbit Oak receives most attention nowadays. All maintenance
branches and the unstable development branch are continuously seeing moderate
to high activity.
Apache Jackrabbit itself is mostly in maintenance mode with most of the work
going into bug fixing and tooling. New features are mainly driven by
dependencies from Oak.
The direct binary access feature finally landed in trunk this quarter. This
is a major new feature that required effort and coordination from many
different domain experts in our comitter base.
There is an ongoing effort to understand and be prepared for the impact of
the changes in the release model of Java. This includes evaluating whether we
can support newer Java versions on some of our branches.
We expect to further improve modularisation of our code base to enable
independent releases for non core moduls. Discussions and prototyping is
expected to happen in the next couple of months.
## Health report:
The project is healthy with a continuous stream of traffic on all mailing
lists reflecting the activity of the respective component. There is a wide
range of topics being discussed on the various Jira issues.
## PMC changes:
- Currently 51 PMC members.
- Last PMC addition was Matt Ryan on Mon Sep 10 2018
## Committer base changes:
- Currently 51 committers.
- Matt Ryan was added as a committer on Sun Sep 09 2018
## Releases:
- jackrabbit-2.14.6 was released on Sun Sep 02 2018
- jackrabbit-2.16.2 was released on Tue Jun 12 2018
- jackrabbit-2.16.3 was released on Tue Jul 31 2018
- jackrabbit-2.17.4 was released on Tue Jul 10 2018
- jackrabbit-2.17.5 was released on Wed Jul 25 2018
- jackrabbit-2.8.8 was released on Tue Jul 03 2018
- jackrabbit-2.8.9 was released on Mon Jul 16 2018
- vault-3.2 was released on Thu Aug 09 2018
- vault-package-maven-plugin-1.0.3 was released on Fri Aug 31 2018
- oak-1.4.22 was released on Mon Jun 25 2018
- oak-1.6.13 was released on Wed Jul 25 2018
- oak-1.8.5 was released on Tue Jul 03 2018
- oak-1.8.6 was released on Tue Jul 31 2018
- oak-1.8.7 was released on Tue Aug 28 2018
- oak-1.9.5 was released on Tue Jul 03 2018
- oak-1.9.6 was released on Wed Jul 18 2018
- oak-1.9.7 was released on Tue Aug 14 2018
- oak-1.9.8 was released on Tue Aug 28 2018
## JIRA activity:
- 281 JIRA tickets created in the last 3 months
- 263 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AF: Report from the Apache Karaf Project [Jean-Baptiste Onofré]
## Description:
- Apache Karaf provides a very modern and polymorphic container,
multi-purpose (microservices, OSGi, etc) powered by OSGi.
## Issues:
- There are no issues requiring board attention at this time
## Activity:
- New update/polishing on the website
- New important versions have been released (4.2.1)
- A talk about Karaf will stand at ApacheCon NA
- We are preparing new subprojects releases (Cave, Decanter) and a new
subproject (Vineyard)
## Health report:
- We asked communities to share their experience/usage of Karaf to
populate the Stories pages on our website
- We can see updates from users asking for release so we agreed to have
a periodically release cycle (every two months).
- We note a growing interest for Karaf in the cloud and Karaf with docker.
- We are reviewing a CVE report
## PMC changes:
- Currently 15 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Christian Schneider on Mon Aug 22 2016
## Committer base changes:
- Currently 31 committers.
- No new committers added in the last 3 months
- Last committer addition was Francois Papon at Sat May 19 2018
## Releases:
- 4.1.6 was released on Sun Aug 12 2018
- 4.2.1 was released on Wed Aug 22 2018
## /dist/ errors: 15
- We are updating the signature for the existing releases on dist
(it's "old" releases on maintenance branches)
## Mailing list activity:
- dev@karaf.apache.org:
- 187 subscribers (up 2 in the last 3 months):
- 173 emails sent to list (179 in previous quarter)
- issues@karaf.apache.org:
- 42 subscribers (up 0 in the last 3 months):
- 927 emails sent to list (904 in previous quarter)
- user@karaf.apache.org:
- 365 subscribers (up 1 in the last 3 months):
- 517 emails sent to list (416 in previous quarter)
## JIRA activity:
- 110 JIRA tickets created in the last 3 months
- 119 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AG: 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:
One active lab Turbulence. This has been quiet in the last period.
## Health report:
Labs remains quiet, but not inactive. Time constraints and lack of volunteer
energy have limited our progress.
## PMC changes:
- Currently 10 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Simone Tripodi on Tue Jun 14 2011
## Committer base changes:
- Currently 31 committers.
- No new committers added in the last 3 months
- Last committer addition was Juan P. Gilaberte at Wed May 30 2018
## Releases:
Per our charter Labs does not make releases.
-----------------------------------------
Attachment AH: Report from the Apache Lucene Project [Adrien Grand]
## Description:
- Lucene Core is a search-engine toolkit
- Solr is a search server built on top of Lucene Core
## Activity:
The upcoming Lucene 7.5 will include:
- Support for indexing and searching geo-shapes as 6D points which represent
tessellated triangles rather than terms in an inverted index. We expect
this new approach to perform better. [1]
- Better reclamation of deletes through merges. We previously allowed indices
to contain about 50% deleted documents, and potentially much more on
indices that have been force-merged. Forced merges do not create huge
segments anymore[2] and deletes are now more aggressively reclaimed[3],
allowing up to about 33% deleted documents per index.
The upcoming Solr 7.5 will include:
- Support for co-locating replicas of multiple collections on the same
nodes.[4]
- Inclusion of the new "Nori" korean analyzer in the default distribution.
[5]
- More stream evaluators, in particular around outlier detection. [6]
- There is an ongoing discussion to release Lucene/Solr 8.0 later this year.
[7]
- Both user and dev mailing-lists are very active.
- Discussions are generally flowing in a good shape.
- We produced 2 releases since the last report.
- We are updating our release process to conform with Apache requirements.
[8]
[1] https://issues.apache.org/jira/browse/LUCENE-8396
[2] https://issues.apache.org/jira/browse/LUCENE-7976
[3] https://issues.apache.org/jira/browse/LUCENE-8263
[4] https://issues.apache.org/jira/browse/SOLR-11990
[5] https://issues.apache.org/jira/browse/SOLR-12665
[6] https://issues.apache.org/jira/browse/SOLR-12660
[7]
https://lists.apache.org/thread.html/19fd6e0 7b75fc2f75758c30962d955450c14b5583690c4a8e703d879@%3Cdev.lucene.apache.org%3E
[8] https://issues.apache.org/jira/browse/LUCENE-8493
## PMC changes:
- No new PMC members
- Last addition was Cao Mạnh Đạt on on April 2nd 2018
- Currently 49 PMC members.
## Committer base changes:
- Nhat Nguyen was added as a committer on June 18th 2018
- Currently 73 committers.
## Releases:
- Lucene/Solr 7.4.0 was released on June 27th.
- pylucene 7.4 was released on September 4th.
- There are ongoing discussions to release 7.5.0 and 8.0.0.
-----------------------------------------
Attachment AI: Report from the Apache Lucene.Net Project [Shad Storhaug]
-----------------------------------------
Attachment AJ: Report from the Apache Marmotta Project [Jakob Frank]
## Description:
Apache Marmotta, an Open Platform for Linked Data. Apache Marmotta was founded
in December 2012, and has graduated from the Incubator in November 2013.
## Issues:
There are no major issues requiring board attention at this time.
## Activity:
Quiet summer after finally completing the release of Marmotta 3.4.0. Besides
traffic around the release-process (VOTE and Jira bulk-mail) all public lists
went quiet.
## Health report:
The project was considered feature-complete since 3.3.0. Currently there are
no active development activities. While the project currently is dormant,
PMC-members are responsive on the lists.
## PMC changes:
- Currently 11 PMC members.
- Last PMC addition was Mark A. Matienzo on Thu Aug 18 2016
## Committer base changes:
- Currently 13 committers.
- Xavier Sumba was added as a committer on Mon Mar 27 2017
## Releases:
- Last release was 3.4.0 on Tue Jun 12 2018
## Mailing list activity:
- users@marmotta.apache.org:
- 116 subscribers (up 1 since last report):
- 1 emails sent to list (15 in previous report)
- dev@marmotta.apache.org:
- 97 subscribers (down 3 since last report):
- 98 emails sent to list (27 in previous report)
## JIRA activity:
- 0 JIRA tickets created in the last 3 months
- 1 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AK: Report from the Apache Mnemonic Project [Gang Wang]
Description:
Apache Mnemonic is an open-source Java library for durable object-oriented
programming on hybrid storage-class memory(e.g. NVM) space. it comes up
with durable object model (DOM) and durable computing model(DCM) and
takes full advantages of storage-class memory to simplify the code
complexity, avoid SerDe/(Un)Marshal, mitigate caching for constructing
next generation computing platform. Mnemonic makes the storing and
transmitting of massive linked objects graphs simpler and more efficient.
The performance tuning could also be mostly converged to a single point
of tuning place if based on Mnemonic to process and analyze
linked objects. The programmer is able to focus on the durable object
oriented business logic instead of worrying about how to normalize/join,
serDe(un)marshal, cache and storing their linked business objects
with arbitrary complexity.
Issues:
There are no board-level issues at the moment.
Activity:
In this period of reporting, No much of tickets has been created and
resolved, basically, we add test cases for the feature of reference
breaking and bugfix, also we are trying to upgrade the dependent
artifacts to support latest JDK version. From JDK9, there are many gaps
need to be identified and filled up, we are trying to make all dependent
artifacts to be compatible with JDK9 and then resolving the compatibility
issues for Mnemonic itself.
With the support of our community contributors, we have added new
operators to Chunkbuffer for the convenience of adoption and integration
with other projects.
Recently, a new The Mnemonic version has been released, we are starting
to work on v0.13 that might be released before next report.
Health Report:
Basically unchanged since the last report. Users are generally quiet
in public but development continues.
PMC Changes:
- Currently 12 PMC members.
- no new PMC member added since Jun. 2018.
Committer Base Changes:
- Currently 13 committers.
- No new committer added since Jun. 2018.
Releases:
- Last release was v0.12.0 on Sep. 04 2018
- Still active development on next major version (0.13)
JIRA Activity:
- 3 JIRA tickets created since the last report (Jun. 2018)
- Also 5 JIRA tickets closed/resolved this period
Sincerely,
Gang(Gary) Wang on behalf of the Apache Mnemonic PMC
-----------------------------------------
Attachment AL: Report from the Apache Mynewt Project [Justin Mclean]
## Description:
Mynewt is a real-time operating system for constrained embedded systems like
wearables, lightbulbs, locks and doorbells. It works on a variety of 32-bit
MCUs (microcontrollers), including ARM Cortex-M, RISC-V and MIPS
architectures.
## Issues:
None.
## Activity:
- Release 1.4.1 completed on July 1, 2018 following release 1.4 on June 12,
2018
- Bluetooth component split out into a different repo on a separate release
track. The first NimBLE Bluetooth protocol stack 1.0.0 was released on June
13, 2018.
- Community work in serval areas including logging enhancements, sensor
additions, Bluetooth mesh profiles, Bluetooth SIG certification fixes,
LoRa/LoraWAN testing, support for UCIFI comms, expansion of MCU
architectures supported
- Documentation now has doxygen-based APIs generated for all component code in
the project.
## Health report:
- PMC and committers are active
- Users questions and contributor's pull requests are quickly dealt with
- Four new committers added since last board report in April
- talk and demos of Apache Mynewt BLE and LoRa at Open IoT Summit, Portland,
Feb 2018
- participation in LoRa demo table at Mobile World Congress, Feb 2018
- Mynewt talk at Apache Roadshow in Berlin
- Mynewt demos planned at Runtime booth at Bluetooth World, Sep 2018
## PMC changes:
- Currently 19 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Aditi Hilbert on Wed Jun 21 2017
## Committer base changes:
- Currently 28 committers
- 5 new committer voted on and added since last report Kevin Townsend (July
17) Jerzy Kasenberg (June 21) Stephane D'Alu (April 19) Markus Lampert
(April 19) Matthew Warnes (April 19)
## Releases:
- 1.4.1 was released on July 1, 2018
- 1.4.0 was released on June 12, 2018
- planning on 1.5 release is currently underway
## Mailing list activity:
- Mailing list activity seeing several new users.
- Mailing list exchanges are mostly around BLE, BLE mesh, API enhancements,
sensor support additions, build and usage issues, newt tool and newtmgr
issues
- Mailing list average activity (# of topics, messages, people responding) has
held steady over the past few months.
- Slack activity up significantly and weekly/daily active users up 50% from
last period (currently at 362 active users), new channels added.
## GitHub Issues activity:
- Issue tracking for each repo moved over to corresponding GitHub Issues after
discussion on mailing list
-----------------------------------------
Attachment AM: Report from the Apache OFBiz Project [Jacopo Cappellato]
## Description:
Apache OFBiz is an open source enterprise automation software project
## Issues:
There are no issues requiring board attention at this time
## Activity:
- Vulnerability reports: the security team has received a few reports and it
is communicating with the reporters to confirm and properly address them
- The stabilization of the new release branch, 17.12, is proceeding well but
we still don't have scheduled a date for the first release; we will publish
soon a new bug fix release for the 16.11 branch
- The documentation initiative: We are trying to re-start the documentation
effort and although progress has been slow during the annual holiday period
we hope to see a lot more focus on this in the coming months
- Various bug fixes and enhancements have been contributed and committed to
the trunk: a summary of the main changes is available as usual in the
project's blog [1]
- More details about the community activities are published in the official
blog [1], on Twitter [2] and other social media [3]; our public HipChat room
[4] has seen low activity as in the previous quarter
- Trademarks: there are a few domains in our backlog for which we have to take
some corrective actions [5]; they do not represent very concerning
violations but the PMC needs to take some action soon since they are in the
backlog since a long time; one month ago the Trademark team asked for an
update about one of them and we still have to provide a response; we will
follow up with them as soon as we have an update
- We did some housekeeping (renaming of hash files and removal of deprecated
hashes) in the project's release archive to make it fully compliant with the
latest ASF release policies [6]
## Health report:
We have invited three new committers; as usual the PMC is monitoring and
discussing new candidates for the PMC and the committers' groups; the
community is actively involved in improving the trunk, stabilizing the release
branches and in various discussions and support requests posted mostly in the
mailing list and in Jira.
## PMC changes:
- No new PMC members added in the last 3 months
- Last PMC addition was Paul Foxworthy on Mon Mar 19 2018
- Currently 20 PMC members.
## Committer base changes:
- New committers:
- Aditya Sharma was added as a committer on Tue Jun 26 2018
- Suraj Khurana was added as a committer on Tue Jun 26 2018
- Swapnil Mane was added as a committer on Tue Jun 26 2018
- Currently 46 committers.
## Releases:
- Last release was 16.11.04 on Tue Jan 02 2018
## Mailing list activity:
There is nothing significant to report in the mailing list activity and
statistics.
## JIRA activity:
- 125 JIRA tickets created in the last 3 months
- 115 JIRA tickets closed/resolved in the last 3 months
## References
[1] https://blogs.apache.org/ofbiz/
[2] https://twitter.com/ApacheOfbiz
[3] https://www.facebook.com/Apache-OFBiz-1478219232210477/
[4] https://apache.hipchat.com/chat/room/2814115
[5] https://svn.apache.org/repos/private/pmc/ofbiz/trademarks/trademarks.txt
[6] https://checker.apache.org/projs/ofbiz.html
-----------------------------------------
Attachment AN: Report from the Apache Olingo Project [Christian Amend]
-----------------------------------------
Attachment AO: Report from the Apache OODT Project [Imesha Sudasingha]
## Description:
- Apache OODT is a software framework as well as an architectural style for
the rapid construction of scientific data systems. It provides components
for data capture, curation, metadata extraction, workflow management,
resource management, and data processing.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- Last release was 1.2.5 released on Thu Sep 13 2018
- Couple of issues were fixed and released (3 releases) related to OODT 1.2
within the reporting period including support for JDK 8.
- On the other hand, 1.9 is almost ready to be released after switching to
Avro RPC for communications. This will be released within the coming
month.
- We are also working on supporting OODT to be built under JDK 10.
## Health report:
- Project activity has been quiet except for the 3 1.2.x releases.
- Due to Apache DRAT GSoC project, OODT could identify bottlenecks of using
XML RPC and could expedite the Avro RPC migration. As a result, Avro RPC
support has been made stable along with better logging support.
- Despite the number of mails in the lists are lower compared to the last
term, contributor involvement has increased within the period where more
contributors worked actively within the period.
- OODT 1.9 is ready to be released and will be released in the coming month.
- After 1.9, we will be moving to the 2.0 development cycle which will be a
major step forward.
## PMC changes:
- Currently 45 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Imesha Sudasingha on Mon Aug 28 2017
## Committer base changes:
- Currently 46 committers.
- No new committers added in the last 3 months
- Last committer addition was Imesha Sudasingha at Tue Aug 29 2017
## Releases:
- 1.2.3 was released on Mon Aug 06 2018
- 1.2.4 was released on Sun Aug 19 2018
- 1.2.5 was released on Thu Sep 13 2018
## Mailing list activity:
- Mailing list activity has increased with increased user queries, developer
discussions and releases. The numbers are lower because the auto generated
mails (Jenkins/Jira) have decreased within the period.
- dev@oodt.apache.org:
- 92 subscribers (up 2 in the last 3 months):
- 125 emails sent to list (152 in previous quarter)
## JIRA activity:
- 7 JIRA tickets created in the last 3 months
- 8 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AP: Report from the Apache Open Climate Workbench Project [Michael James Joyce]
Apache Open Climate Workbench is a tool for scalable comparisons of remote
sensing observations to climate model outputs.
We've seen activity pick back up since the unusually slow end to last quarter.
We voted on and released version 1.3.0 which included a number of key fixes,
improvements, and new features for the toolkit and we've continued to work on
improvements, bug fixes, and polishing as we work towards 1.4.0.
We're working with a new contributor to get them involved in GSoC since they
have been working on contributing and expressed interest in having a mentor so
they can expand their understanding of the toolkit. Hopefully schedules will
work out and we'll be on our way to a new committer/PMC member after a
successful GSoC! We're continuing to monitor activity given the occasional
drop that we see and the overall stagnation of PMC/Committer additions.
Issues for the board: None
When was the last committer or PMC member elected:
- Ibrahim Jarif - 26 April 2016
- Omkar Reddy - 20 January 2016
When was the last release:
- 1.3.0 - 23 April 2018
- 1.2.0 - 24 April 2017
-----------------------------------------
Attachment AQ: Report from the Apache OpenNLP Project [Jörn Kottmann]
## Description:
- Apache OpenNLP is a machine learning based toolkit for the
processing of natural language text.
## Issues:
- No issues to report.
## Activity:
- Suneel Marthi and Joey Frazee presented at FlinkForward, Berlin
on 5th September 2018 about "Streaming topic model training and
inference with Apache Flink" leveraging Apache OpenNLP with Apache Flink.
- OpenNLP is used by https://github.com/tteofili/jtm for jira issue tracking
- Various bug fixes and refactorings
- Team’s presently working on the next OpenNLP release
## Health report:
- The project has a very active committer base and there’s healthy
activity on mailing lists.
## PMC changes:
- Currently 15 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Koji Sekiguchi on Tue Oct 10 2017
## Committer base changes:
- Currently 21 committers.
- No new committers added in the last 3 months
- Last committer addition was Jeffrey T. Zemerick at Wed Apr 26 2017
## Releases:
- 1.9.0 was released on Mon Jul 02 2018
## JIRA activity:
- 16 JIRA tickets created in the last 3 months
- 17 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AR: Report from the Apache OpenWebBeans Project [Mark Struberg]
## Description:
Apache OpenWebBeans is an ALv2-licensed implementations of the
"Contexts and Dependency Injection for the Java EE platform"
specifications which are defined as JSR-299 (CDI-1.0), JSR-346
(CDI-1.1 and CDI-1.2 MR) and JSR-365 (CDI-2.0).
The OWB community also maintains a small server as
Apache Meecrowave subproject. Meecrowave bundles latest releases of
the ASF projects Tocmat9 + OpenWebBeans + CXF + Johnzon + log4j2.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
We fixed a lot of tickets we got as feedback from real production.
We also continue pushing performance despite the fact that we are still
a few times faster than other CDI containers.
The new Oracle Java release cadence (half year updates to bytecode)
causes quite some additional work.
## Health report:
Community is doing fine. Small but active.
Meecrowave sees some adoption and TomEE did some releases lately
which both help with the adoption.
## PMC changes:
- Currently 13 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Reinhard Sandtner on Mon Oct 09 2017
## Committer base changes:
- Currently 20 committers.
- No new committers added in the last 3 months
- Last committer addition was John D. Ament at Mon Oct 09 2017
## Releases:
- 2.0.7 was released on Fri Aug 31 2018
- meecrowave-1.2.3 was released on Sun Jul 22 2018
## Mailing list activity:
- dev@openwebbeans.apache.org:
- 68 subscribers (down -1 in the last 3 months):
- 199 emails sent to list (202 in previous quarter)
- user@openwebbeans.apache.org:
- 97 subscribers (up 0 in the last 3 months):
- 5 emails sent to list (9 in previous quarter)
## JIRA activity:
- 36 JIRA tickets created in the last 3 months
- 35 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AS: Report from the Apache Pig Project [Koji Noguchi]
## Description:
- Apache Pig is a platform for analyzing large data sets on Hadoop. It
provides a high-level language for expressing data analysis programs,
coupled with infrastructure for evaluating these programs.
## Issues:
- There are no issues requiring board attention at this time
## Activity:
- Activity is still low but making progress.
- Nándor has been added as a commiter this quarter.
- We're behind on the next major release of 0.18.
## Health report:
- Mostly bug fixes and enhancements being worked on.
## PMC changes:
- Currently 17 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Koji Noguchi on Thu Aug 04 2016
## Committer base changes:
- Currently 31 committers.
- Nándor Kollár was added as a committer on Thu Sep 06 2018
## Releases:
- Last release was 0.17.0 on Thu Jun 15 2017
## Mailing list activity:
- dev@pig.apache.org:
- 377 subscribers (down -8 in the last 3 months):
- 238 emails sent to list (192 in previous quarter)
- user@pig.apache.org:
- 1077 subscribers (down -16 in the last 3 months):
- 15 emails sent to list (20 in previous quarter)
## JIRA activity:
- 15 JIRA tickets created in the last 3 months
- 14 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AT: Report from the Apache Pivot Project [Roger Lee Whitcomb]
Description:
Apache Pivot is an open-source platform for building installable
Internet applications (IIAs). It combines the enhanced productivity and
usability features of a modern user interface toolkit with the robustness of
the Java platform.
Issues:
There are no board-level issues at this time.
Activity:
Development activity continues toward the 2.1.0 release, which still should
be *soon*, although a bit slower due to summer vacations. Builds were done
using Java 10, and numerous issues fixed, so we are well-positioned for
going forward. Community is very silent as usual these last few years.
Health report:
Basically unchanged for several years: development is ongoing, but users
are quiet.
PMC changes:
- Currently 7 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Niclas Hedhman on Wed Jan 13 2016
Committer base changes:
- Currently 9 committers.
- No new changes to the committer base since last report.
- No new committers added in the last 3 months
- Last committer addition was more than 2 years ago
Releases:
- Last release was 2.0.5 on Mon Jul 03 2017
- Still active development on next major version (2.1.0).
Mailing list activity:
- dev@pivot.apache.org:
- 62 subscribers (unchanged in the last 3 months)
- 56 emails sent to list (46 in previous quarter)
- user@pivot.apache.org:
- 171 subscribers (unchanged in the last 3 months)
- 2 emails sent to list (4 in previous quarter)
JIRA activity:
- 7 JIRA tickets created in the last 3 months
- 7 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AU: Report from the Apache Polygene Project [Jiri Jetmar]
-----------------------------------------
Attachment AV: Report from the Apache Portable Runtime (APR) Project [Nick Kew]
## Description:
- The Apache Portable Runtime (APR) project creates and maintains
software libraries that provide a predictable and consistent interface
to underlying platform-specific implementations. There are three
sub-projects: APR, APR-UTIL and APR-ICONV, of which the first two
are the main focus of developer interest.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
- This quarter has seen increased activity in trunk. The big
event is that an APR-JSON module, originally developed by
a third-party, has been adopted by the project (the original
author has moved on and was happy to donate but not to join
the team). Another activity has been crypto updates
reflecting OpenSSL updates and deprecations.
There have been some platform changes, with Windows updates
reserved for future versions, and a bugfix affecting Solaris.
The latter calls for a new bugfix release, which is anticipated
very shortly.
## Health report:
- The project remains basically healthy.
## PMC changes:
- Currently 41 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Evgeny Kotkov on Tue Sep 12 2017
## Committer base changes:
- Currently 67 committers.
- No new committers added in the last 3 months
- Last committer addition was Evgeny Kotkov at Wed Sep 13 2017
## Releases:
- None in the period. Last release was a joint release of
APR-1.6.3, APR-UTIL-1.6.1 and APR-ICONV-1.2.2 in October 2017.
A new bugfix release (of APR only) is anticipated in September.
## Mailing list activity:
- The subscriber base remains stable. Reasons for renewed activity
are described above.
- dev@apr.apache.org:
- 329 subscribers (down -4 in the last 3 months):
- 214 emails sent to list (79 in previous quarter)
- bugs@apr.apache.org:
- 20 subscribers (up 0 in the last 3 months):
- 38 emails sent to list (50 in previous quarter)
COMMENT: these figures are from reporter.apache.org, but are not
consistent, in that the "previous quarter" numbers disagree with
those then reported. The differences are not significant.
## Bugzilla Statistics:
- 4 Bugzilla tickets created in the last 3 months
- 1 Bugzilla tickets resolved in the last 3 months
-----------------------------------------
Attachment AW: Report from the Apache Portals Project [David Sean Taylor]
## Description:
Apache Portals exists to promote the use of open source portal technology. We
intend to build freely available and interoperable portal software in order to
promote the use of this technology. With the Pluto project, we provide a
reference implementation for the Java portlet standard. The Jetspeed project
is a full feature enterprise open source portal. The Portals Applications
project is dedicated to providing robust, full-featured, commercial-quality,
and freely available portlet applications.
## Activity:
Apache Portals released 1 release since the last report.
21 June 2017 - Pluto 3.0.1
http://portals.apache.org/pluto/news.html
<http://portals.apache.org/pluto/news.html>
Pluto: Final Release of Pluto 3.0.1 Fix for Apache Security Team found bug
"Apache Pluto 3.0.0 Unauthenticated Remote Code Execution” included in 3.0.1
release Nearing completion of the Portlet 3.0 TCK as we implement Portlet
3.0.1 support for our portal products.
Pluto: JIRA issues were closed and bugs fixed.
12 Feb 2017 - Two new PMC members added 27 April 2017 - Apache Portals Pluto
team released Pluto Maven Archetypes 3.0 to support to developing new portlets
to the new 3.0 spec
## Mailing list activity:
Not much activity. Some discussions around TCK implementation on the Pluto
list. Low volume activity on the Jetspeed lists.
## Issues:
We have no board-level issues at this time.
## PMC/Committership changes:
Last Added PMC Members:
12 Feb 2017 - Scott Martin Nicklaus 12 Feb 2017 - Neil Griffin
Last Removed PMC Members:
25 Aug 2018 - David Jencks
Last Added Committers:
05 August 2016 Mohd Ahmed Kahn 11 Dec 2014 Martin Scott Nicklous 11 Dec 2014
Neil Griffin
Last Removed Committers:
25 Aug 2018 - David Jencks
## Releases:
Pluto 3.0.1 - 21 June 2018 Pluto Maven Archetype 3.0.0 - 27 April 2017 Pluto
3.0.0 - 18 January 2017 Jetspeed 2.3.1- 09 May 2016
-----------------------------------------
Attachment AX: 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:
- Technology stack updates and pending new release (0.13.0).
- Release management rotation.
- Major revamp to Java SDK.
- Continued community support and driving for contributions.
## PMC changes:
- Currently 28 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Andrew Kyle Purtell on Tue Oct 17 2017
## Committer base changes:
- Currently 29 committers.
- No new changes to the committer base since last report.
## Releases:
- Last release was 0.12.1 on Sat Mar 10 2018
## JIRA activity:
- 6 JIRA tickets created in the last 3 months
- 5 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AY: Report from the Apache Royale Project [Harbs]
## DESCRIPTION
Apache Royale is a new implementation of the principles of Apache Flex but
designed for JavaScript runtimes instead of Adobe Flash/AIR runtimes. Apache
Royale is designed to improve developer productivity in creating applications
for wherever Javascript runs, including browsers as well as Apache Cordova
applications, Node, etc.
## ISSUES
There are no issues requiring board attention at this time.
## RELEASES
- Apache Royale 0.9.2 was released on March 16 2018.
- Apache Royale 0.9.4 in progress.
## ACTIVITY
- No releases this quarter. Releases have been stalled by a combination of
factors. One is that someone volunteered to be the RM and had not released
Royale before and ran into configuration issues. Another is that so many new
files were added that the Maven SCM plugin would not work correctly. Another
is that there is a disagreement about the organization of files in the
release. There has been a lot of work done to resolve this disagreement and
it looks like we are close to resolving it. It looks like the Maven plugin
has been fixed so hopefully we will release soon.
- Lots of progress on a new default look (component set) for Royale apps.
- Lots of progress on migrating a large Flex app to Royale. A new "Flex
Emulation" component set is being worked on to ease migrations.
- New names are showing up on the mailing list asking about Royale.
- The owner of an ActionScript code base that doesn't use Flex is attempting
to use the Royale Compiler to cross compile his code to JavaScript.
- There have been a number of blog posts on using Royale. They seem to be well
received.
- We are using Disqus for blog comments. It seems to help engagement. We were
not able to figure out how to get comments sent to the @dev list.
- We had huge activity on Social Networks, trying to inform about what is
happening in Apache Royale as we progress in the project. We think is
important to do this so people outside the project, not following in a daily
basis could get a notion of how we are doing. The numbers here are the
following:
- Twitter got 375 followers since we open the account, and we are getting
around 30 likes when we post something, and between 10 to 20 retweets,
showing interest in what we're doing.
- Facebook gets 97 likes to the page and we are getting around 10-15
interactions (likes) and some comments, showing interest in Apache
Royale. We took advantage of a promo in Facebook that allowed us to
promote Apache Royale during 1 month (5 Jun - 5 July). We spend 1€ per
day during 30 days, during that time we reached 34.879 People and had
6.943 Interactions.
- Google Plus, we post here as well but seem this social networks gets few
interactions and seems not widely used by our target users.
- We started a LinkedIn Group where 113 people joined in no time since
opened. Groups in LinkedIn used to be watched by many people but remains
silent most of the time, although it seems the way most of LinkedIn
groups work.
## COMMUNITY
- Alina Kazi was added as committer on April 26 2018.
- No new PMC Members yet
- Two new contributors being watched to be committers.
## Mailing list activity:
User lists subscribers continue to grow. Fewer emails to read, but still a
lot of emails.
- users@royale.apache.org:
- 69 subscribers (up 9 in the last 3 months):
- 181 emails sent to list (610 in previous quarter)
- dev@royale.apache.org:
- 76 subscribers (up 1 in the last 3 months):
- 1391 emails sent to list (1614 in previous quarter)
-----------------------------------------
Attachment AZ: Report from the Apache Sentry Project [Alex Kolbasov]
## Description:
Apache Sentry is a highly modular system for providing fine grained role
based authorization to both data and metadata stored on an Apache Hadoop
Cluster.
## Issues:
There are no issues requiring board attention at this time
## Activity:
- Preparation for 2.1 release which will include support for fine-grained
privileges and object ownership
- Discussion going on about implementing attribute-based access control
features
## Health report:
- Development activity seems pretty consistent;
- New developers starting contributng to the project;
## PMC changes:
- Currently 37 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Kalyan Kalvagadda on Sun Feb 04 2018
## Committer base changes:
- Currently 40 committers.
- Arjun Mishra was added as a committer on Fri Jul 06 2018
## Releases:
- 2.0.1 was released on Sun Aug 19 2018
(this is a targeted release to address
https://nvd.nist.gov/vuln/detail/CVE-2018-8028).
## Mailing list activity:
Most of the activity is about preparation for 2.1 release.
- dev@sentry.apache.org:
- 91 subscribers (up 1 in the last 3 months):
- 737 emails sent to list (546 in previous quarter)
- issues@sentry.apache.org:
- 22 subscribers (up 0 in the last 3 months):
- 1247 emails sent to list (993 in previous quarter)
## JIRA activity:
- 131 JIRA tickets created in the last 3 months
- 113 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment BA: Report from the Apache Serf Project [Bert Huijben]
Report from the Apache Serf Project [Bert Huijben]
## Description:
The serf library is a high performance C-based HTTP client library
built upon the Apache Portable Runtime (APR) library. Serf is the
default client library of Apache Subversion, Apache OpenOffice and
mod_pagespeed.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
There is some ongoing work to get Serf 1.4.0 released. In the
previous report we predicted it would be released by now, but
that has not happened yet.
## Health report:
Activity is at a normal, fairly quiet level.
## PMC & Committer changes:
Currently 12 PMC members and 13 committers. We are in the process of
adding Branko Čibej as a PMC member. The vote by the PMC passed and the
board was notified on 3rd September.
Bert Huijben, the current VP Apache Serf, decided to step down on 25th
August. A board resolution has been proposed for this meeting to change
the Apache Serf PMC Chair.
## Releases:
Apache Serf 1.3.9 was released on Thu Sep 01 2016
## Mailing list and Jira activity:
Normal slow activity.
-----------------------------------------
Attachment BB: Report from the Apache ServiceMix Project [Krzysztof Sobkowiak]
Description
===========
Apache ServiceMix is a flexible, open-source integration container that
unifies the features and functionality of Apache ActiveMQ, Camel, CXF and
Karaf to provide a complete, enterprise-ready ESB powered by OSGi.
Issues
======
There are no outstanding issues requiring board attention.
Activity
========
The project focus of Apache ServiceMix is the assembly of the integration
container, the actual functionality is being maintained in related projects
like Apache Karaf, Apache CXF, Apache Camel and Apache ActiveMQ.
- We have released 3 sets of OSGi bundles.
- Our users are asking for the new ServiceMix release, so we should focus on
preparing the new ServiceMix 7 (or maybe 8) based on the newest versions of
Apache Karaf and Apache Camel.
- We are going to focus more on improvement of the documentation and
improvement of the examples to give people easier start into integration
with ServiceMix.
- We should focus during the next periods on cloud and devops themes to make
the ServiceMix distribution more attractive for users.
Health report
=============
- Activity on the mailing lists and in JIRA is on the same level like in the
last period. We had some contributions.
- Our 2 PMC members have stepped down from PMC, because they have been
inactive for a longer time and they didn't expect any further contribution
from their side. We actually don't see any new candidates to be invited to
join the PMC.
PMC changes
===========
- Currently 22 PMC members.
- Andrea Cosentino was added to the PMC on Wed Mar 15 2017
Committer base changes
======================
- Currently 50 committers.
- No new committers added in the last 3 months
- Last committer addition was Andrea Cosentino at Sun Mar 13 2016
Releases
========
- Apache ServiceMix Bundles 2018.06 on July 10 2018
- Apache ServiceMix Bundles 2018.07 on August 12 2018
- Apache ServiceMix Bundles 2018.08 on September 06 2018
JIRA activity
=============
- 51 JIRA tickets created in the last 3 months
- 50 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment BC: Report from the Apache Shiro Project [Les Hazlewood]
Apache Shiro is a powerful and flexible open-source application security
framework that cleanly handles authentication, authorization, enterprise
session management and cryptography.
We have no issues that require Board assistance at this time.
Releases:
- Last release was 1.4.0 on 05-May-2017
Community & Project:
- Mailing list traffic has dipped slightly in the last quarter
- Feature development is planned to continue against master.
- OSGI support is a popular feature, we get an occasional one-liner
patch. However, we do NOT have a committer with sufficient experience,
which makes supporting it difficult.
- The 1.4.0 Release has been a step toward modernizing Shiro as well
as retain backwards compatibility
Last committer voted in: Andreas Kohn on 15 Jul 2016
Last PMC Member voted in: Andreas Kohn on 26 Jul 2016
-----------------------------------------
Attachment BD: Report from the Apache Sling Project [Robert Munteanu]
## Description:
Apache Sling™ is a framework for RESTful web-applications based on an
extensible content tree.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
Business continues as usual with individual module releases. We are
considering releasing Sling 11 in the near future with Java 11 and preliminary
Java 12 support.
The "Apache Sling and friends" conference - adaptTo - is taking place in
Potsdam, Germany on 10-12 september, and we welcome the opportunity of meeting
in person and having a Sling hackathon.
## Health report:
Good activity level overall, contributions from different people continue. We
_think_ we see an increase in casual contributions after the move to Github
but could not quantify this yet due to missing tooling for aggregating stats
across a large number of repositories.
## PMC changes:
- Currently 26 PMC members.
- New PMC members:
- A. J. David Bosschaert was added to the PMC on Thu Jul 05 2018
- Andrei Dulvac was added to the PMC on Mon Jul 30 2018
- Georg Henzler was added to the PMC on Mon Jul 30 2018
- Julian Sedding was added to the PMC on Mon Jul 30 2018
- Nicolas Peltier was added to the PMC on Mon Jul 30 2018
## Committer base changes:
- Currently 43 committers.
- No new committers added in the last 3 months
- Last committer addition was A. J. David Bosschaert at Fri Mar 09 2018
## Releases:
- Apache Sling API 2.18.4 was released on Mon Aug 27 2018
- Apache Sling App CMS 0.9.0 was released on Wed Aug 01 2018
- Apache Sling Commons Threads 3.2.18 was released on Tue Jun 19 2018
- Apache Sling Content Distribution Core version 0.3.0 was released on Mon
Aug 27 2018
- Apache Sling Context-Aware Configuration API 1.1.2, Context-Aware
Configuration SPI 1.3.4, Context-Aware Configuration Impl 1.4.14 was
released on Wed Sep 05 2018
- Apache Sling Discovery Oak 1.2.28 was released on Fri Aug 31 2018
- Apache Sling Dynamic Include 3.1.2 was released on Tue Aug 14 2018
- Apache Sling Engine 2.6.14 was released on Mon Aug 13 2018
- Apache Sling Event Support 4.2.12 was released on Mon Jul 23 2018
- Apache Sling Feature 0.1.2 was released on Thu Jun 21 2018
- Apache Sling Feature-Analyser 0.1.2 was released on Thu Jun 21 2018
- Apache Sling Feature-IO 0.1.2 was released on Thu Jun 21 2018
- Apache Sling Feature-ModelConverter 0.1.2 was released on Thu Jun 21 2018
- Apache Sling File Optimization 0.9.0 was released on Wed Aug 01 2018
- Apache Sling HTL Maven Plugin 1.1.8-1.4.0 was released on Tue Aug 07 2018
- Apache Sling JCR Content Loader 2.2.6 was released on Tue Jul 10 2018
- Apache Sling JCR Repository Registration 1.0.6 was released on Tue Aug 14
2018
- Apache Sling JCR Resource Resolver 3.0.16 was released on Tue Aug 14 2018
- Apache Sling Maven Sling Plugin 2.3.8 was released on Fri Aug 17 2018
- Apache Sling Parent 34 was released on Thu Aug 09 2018
- Apache Sling Resource Builder 1.0.4, Testing JCR Mock 1.3.6,
ResourceResolver Mock 1.1.22, OSGi Mock 2.4.0, Sling Mock 2.3.0, Sling Mock
Oak 2.1.0, Context-Aware Configuration Mock Plugin 1.3.2 was released on
Tue Aug 21 2018
- Apache Sling Scripting HTL Java Compiler 1.0.26-1.4.0 was released on Tue
Aug 07 2018
- Apache Sling Servlet Helpers 1.1.8, Testing JCR Mock 1.3.4, Testing OSGi
Mock 2.3.10, Testing Sling Mock 2.2.20 was released on Mon Aug 06 2018
- Apache Sling Servlets Get 2.1.34 was released on Fri Aug 31 2018
- Apache Sling Slingstart Maven Plugin 1.8.2 was released on Thu Jun 21 2018
- Apache Sling Tenant 1.1.2 was released on Wed Sep 05 2018
- Apache Sling Testing JCR Mock 1.4.0, Sling Mock 2.3.2 was released on Mon
Aug 27 2018
- Apache Sling Testing OSGi Mock 2.4.2, Sling Mock 2.3.4 was released on Mon
Sep 03 2018
- Apache Sling XSS Protection 2.0.10 was released on Thu Jul 12 2018
- Apache Sling XSS Protection API 2.0.12 was released on Tue Aug 07 2018
- Apache Sling XSS Protection API 2.0.8 was released on Tue Jul 03 2018
## JIRA activity:
- 174 JIRA tickets created in the last 3 months
- 169 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment BE: Report from the Apache SpamAssassin Project [Sidney Markowitz]
Apache SpamAssassin report to Board for Sep 2018
SpamAssassin is a mail filter to identify spam. The project provides a
framework/engine and regular rule updates that reflect the changing nature of
spam email seen in the wild. Updated rules are generated through a combination
of hand crafted contributions and automated processing of spam and anonymized
processed non-spam that are contributed by volunteers.
Request to the Board for variance from new release policy:
We are requesting a variance from the Board regarding the new release policy
that disallows new artifacts from using SHA-1.
Apache SpamAssassin publishes rules updates that are cryptographically signed
using GPG, and have SHA-1, SHA-256, and SHA-512 hashes that are intended to
protect against data corruption in transit. The updates we publish can be used
by people who are still running the previous version of SpamAssassin, 3.3.2,
as well as the current version 3.4.1, which only recognize the GPG signature
and SHA-1 hash checksum. The recently released 3.4.2 drops the use of SHA-1
completely. We would like a variance to continue to publish SHA-1 hashes with
the rule updates until some date that we will specify as end of life for
SpamAssassin 3.3.2. We would then stop including SHA-1 hashes with the rule
updates, requiring everyone to upgrade to at least SpamAssassin 3.4.2 or stop
updating their rules. The exact date will depend in part on the response from
the Board regarding this request. Please note that the security of the
downloads come from the use of GPG signatures, not the hashes.
It can be argued that the use of SHA-1 in our rule updates does not fall under
the release policy, as we are not using it as part of the distribution of new
package releases. We do owe it to our users to be reasonable about how we
expect them to transition to the new SpamAssassin version 3.4.2. We would like
confirmation from the Board that we can proceed with the orderly transition to
dropping use of SHA-1 in our rule update system by setting a reasonable end of
life date.
We have a discussion of our request in
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7618
Status and health report:
The project activities, including running of our rule update infrastructure
and our dev and user mailing lists, are continuing smoothly.
Major news is that we have produced our first release in over three years.
We have added a new committer.
Releases:
The last release was Apache SpamAssassin version 3.4.2 on 16 September 2018.
Note that we maintain online rule updates that are continuously updated
through a combination of developer contributions and automated processing via
our mass-check facility.
Version 3.4.2 includes several security fixes, including four for which CVEs
have been issued. We expect to produce a version 3.4.3 in the near future to
address some issues that were deferred, in part so we could quickly release
the security fixes. Our main development branch is for a version 4.0.
Committer/PMC changes:
New committer this quarter:
Paul Stead (pds) 11 September 2018
Most recent new PMC member:
Bill Cole (billcole) 5 March 2018
-----------------------------------------
Attachment BF: Report from the Apache Stanbol Project [Fabian Christ]
-----------------------------------------
Attachment BG: Report from the Apache Storm Project [P. Taylor Goetz]
## Description:
- Apache Storm is a distributed real-time computation system.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- It was pointed out on the board@ list that Storm was one of a number of ASF
projects with bylaws that include a provision for the voluntary and
involuntary designation of inactive PMC members as "emeritus". The PMC
discussed the issue and agreed that such provisions, though never used,
should be removed.
Ultimately, the PMC voted to retire our project-specific bylaws entirely,
in favor of documenting project-specific policies (e.g. commmit policy) in
a "Developer Guidelines" document. Once the patch is approved, the bylaws
document will be removed from the Storm website.
- The developer community is currently in the final discussion phase for the
2.0 release and we expect to release that version this month. We also
expect to make a 1.2.3 maintenance release shortly.
## Health report:
- Project activity is steady, neither increasing nor decreasing.
- New contributors continue to engage and that engagement tends to keep up
activity levels, even as some contributors move on. We continue to expand
the PMC by regularly inviting new members.
## PMC changes:
- Currently 37 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Ethan Li on Tue Apr 10 2018
## Committer base changes:
- Currently 38 committers.
- No new committers added in the last 3 months
- Last committer addition was Ethan Li at Wed Apr 11 2018
## Releases:
- Last release was 1.1.3 on Mon Jun 04 2018
## JIRA activity:
- 119 JIRA tickets created in the last 3 months
- 93 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment BH: Report from the Apache Synapse Project [Isuru Udana]
-----------------------------------------
Attachment BI: Report from the Apache Tajo Project [Hyunsik Choi]
## Description:
- Tajo is an open source big data warehouse system in Hadoop for processing
web-scale data sets.
## Issues:
- The board asked Tajo community to confirm at least active PMC members.
We recalled PMCs through an mailing thread (https://goo.gl/v2kuQw).
6 PMC members responsed to the recall.
## Activity:
- There have been few bug fixes.
## Health report:
- The activity of this project is still low. However, PMC members
have been immediately reacted important issues in the community.
## PMC changes:
- Currently 13 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Hyoung Jun Kim on Sun Dec 07 2014
## Committer base changes:
- Currently 18 committers.
- No new committers added in the last 3 months
- Last committer addition was Jong-young Park at Sun May 29 2016
## Releases:
- Last release was 0.11.3 on Wed May 18 2016
## Mailing list activity:
- dev@tajo.apache.org:
- 96 subscribers (down -5 in the last 3 months):
- 2 emails sent to list (10 in previous quarter)
- issues@tajo.apache.org:
- 23 subscribers (down -3 in the last 3 months):
- 31 emails sent to list (10 in previous quarter)
- user@tajo.apache.org:
- 47 subscribers (down -1 in the last 3 months):
- 2 emails sent to list (3 in previous quarter)
## JIRA activity:
- 2 JIRA tickets created in the last 3 months
- 3 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment BJ: Report from the Apache Tiles Project [Michael Semb Wever]
## Description:
Apache Tiles is a free open-sourced templating framework for Java
applications. Based upon the Composite pattern it is built to simplify
the development of user interfaces.
## Activity & Health report:
User and dev ML traffic was lower this quarter.
Commits and Issues ML traffic show a small increase.
The last release was Tiles-3.0.8, on November 18th 2017.
There are currently two responsive PMC, other PMC help out with votes
when needed. In total there are 8 PMC members, and 10 committers.
The last PMC/committer was added on Mon Apr 23 2012,
being Nicolas LE BAS.
The initial agreement from the two responsive PMC to
move the project to the Attic still stands.
Initiating the process has been on hold as some contributions have
come in, albeit small bugs fixes.
There is low-hanging-fruit tasks of moving the codebase onto JDK11
for any new contributors to get into.
If no new activity eventuates then the process of moving to the Attic,
starting off with an announcement to users ML and then a vote, will
commence in the next quarter.
## Issues:
There are no issues requiring board attention at this time.
-----------------------------------------
Attachment BK: 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.
- Tomcat 8.0.x reached end of life.
- Two days of sessions and a BoF planned for ApacheCon NA.
- Continue to monitor progress of the Jakarta EE projects at
Eclipse on which Tomcat depends. Haven't seen anything to cause
concern. Waiting to see the proposed timeline for the releases
where the specs are updated to include new features.
- The community has been discussing a migration from svn to git.
Most of the issues / concerns have been addressed. The migration
is expected to proceed once final issues have been resolved.
## PMC changes:
- Currently 27 PMC members.
- Last addition May 2018
## Committer base changes:
- Currently 45 committers.
- Last addition May 2018
## Releases:
- Apache Tomcat 7.0.90 was released on Fri Jul 06 2018
- Apache Tomcat 8.0.53 was released on Thu Jul 05 2018
- Apache Tomcat 8.5.32 was released on Mon Jun 25 2018
- Apache Tomcat 8.5.33 was released on Fri Aug 17 2018
- Apache Tomcat 9.0.10 was released on Mon Jun 25 2018
- Apache Tomcat 9.0.11 was released on Fri Aug 17 2018
- Apache Tomcat JK Connector jk-1.2.44 was released on Sat Sep 01 2018
## 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: Information disclosure CVE-2018-1323
Versions Affected:
Apache Tomcat JK Connector jk-1.2.0 to jk-1.2.40
- Important: Information Disclosure in Apache Tomcat's servlet
async processing CVE-2018-8037
Versions Affected:
Apache Tomcat 9.0.0.M9 to 9.0.9
Apache Tomcat 8.5.0 to 8.5.31
Apache Tomcat 8.0.0.RC1 to 8.0.52
- Important: A bug in the UTF-8 decoder can lead to DoS CVE-2018-1336
Versions Affected:
Apache Tomcat 8.5.0 to 8.5.31
Apache Tomcat 8.0.0.RC1 to 8.0.52
Apache Tomcat 7.0.28 to 7.0.88
- Low: Host name verification missing in WebSocket client CVE-2018-8034
Versions Affected:
Apache Tomcat 9.0.0.M1 to 9.0.9
Apache Tomcat 8.5.0 to 8.5.31
Apache Tomcat 8.5.0 to 8.5.31
Apache Tomcat 7.0.25 to 7.0.88
-----------------------------------------
Attachment BL: 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:
- The community continued working on tickets and participated on the
Project's mailing list in line with previous months.
- Work continues on getting a new release out.
- Focus of the PMC remains on growing the community.
## Health report:
- Subscriptions to the (public) mailing lists showed a slight decline
compared to previous quarter.
- Compared to previous quarter, the community involvement showed a
growth in number of emails submitted across all mailing lists,
and a healthy amount of tickets raised/addressed in JIRA.
## PMC changes:
- Currently 13 PMC members.
- New PMC members:
- Sandhya Sundaresan was added to the PMC on Tue Aug 14 2018
- Sean Broeder was added to the PMC on Mon Jun 18 2018
## Committer base changes:
- Currently 20 committers.
- No new committers added in the last 3 months
- Last committer addition was Liu Yu at Mon Feb 05 2018
## Releases:
- Last release was 2.2.0 on Sat Mar 10 2018
## Mailing list activity:
- dev@trafodion.apache.org:
- 98 subscribers (down -5 in the last 3 months):
- 240 emails sent to list (226 in previous quarter)
- codereview@trafodion.apache.org:
- 25 subscribers (down -1 in the last 3 months):
- 511 emails sent to list (509 in previous quarter)
- issues@trafodion.apache.org:
- 34 subscribers (down -2 in the last 3 months):
- 841 emails sent to list (1127 in previous quarter)
- user@trafodion.apache.org:
- 105 subscribers (down -2 in the last 3 months):
- 15 emails sent to list (18 in previous quarter)
- security@trafodion.apache.org:
- 6 subscribers (up 0 in the last 3 months):
- Currently no automated insights in number of ml postings provided by
ComDev-reporter services.
- private@trafodion.apache.org:
- currently 20 subscribers (up 3 in the last 3 months):
- Currently no automated insights in number of ml postings provided by
ComDev-reporter services.
## JIRA activity:
- 95 JIRA tickets created in the last 3 months
- 52 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment BM: Report from the Apache Twill Project [Terence Yim]
Apache Twill is an abstraction over Apache Hadoop YARN to reduce the
complexity of developing distributed applications.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
- Initial exploration work to expand Apache Twill to works with other
scheduler, such as Kubernetes.
## Health report:
- Made one release since July 2018
## PMC changes:
- Currently 6 PMC members
- Last PMC addition was Henry Saputra on August 4, 2015
## Committer base changes:
- Currently 9 committers and 24 contributors
- No new committer added in the last 3 months
- No new contributor added in the last 3 months
- Last committer addition was Yuliya Feldman on Mar 6, 2018
- Last contributor addition was Clay B on Feb 3, 2018
## Releases:
- Last release was release 0.13.0 on July 17, 2018
## Mailing list activity:
- dev@twill.apache.org:
- 68 subscribers
- 19 emails sent to the list in past three months (80 in last report)
- commits@twill.apache.org:
- 17 subscribers
- 9 emails sent to the list in past three months (0 in last report)
## JIRA activity:
- 1 new JIRA tickets created in the last month
- 0 JIRA tickets resolved in the last month
-----------------------------------------
Attachment BN: Report from the Apache UIMA Project [Marshall Schor]
Board report for Apache UIMA, for September 2018.
Apache UIMA's mission: the creation and maintenance of open-source software
related to the analysis of unstructured data, guided by the UIMA Oasis
Standard.
## PMC changes:
- Currently 16 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Lou DeGenaro on Mon May 02 2016
## Committer base changes:
- voting on new committer now.
- Currently 24 committers.
- No new committers added in the last 3 months
- Last committer addition was William Colen at Wed Apr 19 2017
## Releases:
- no new releases this quarter. We almost had one, but it was delayed
so we could work on the new policy around checksums
- last release was UIMA ConceptMapper addon 2.10.2 on 27 April 2018
Activity:
This summer quarter has been a bit quieter than usual.
Java SDK, UIMA-FIT, UIMA-AS, DUCC, RUTA are actively being worked on.
Two new ICLAs and one CCLA received.
Mailing list activity remains moderate.
Community: The community continues to be moderately active.
Issues: No Board level issues at this time.
-----------------------------------------
Attachment BO: Report from the Apache Usergrid Project [Todd Nine]
-----------------------------------------
Attachment BP: Report from the Apache VCL Project [Josh Thompson]
## Description:
- VCL is a modular cloud computing platform which dynamically provisions and
brokers remote access to compute resources including virtual machines,
bare-metal computers, and resources in other cloud platforms. A self-service
web portal is used to request resources and for administration. VCL became a
TLP on June 20, 2012.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- Our previous board report specified there are two people that could be
potential committers. Nothing has been received from them in since the last
board report. We will continue to look for opportunities to engage with them
in an attempt to get them more involved, hopefully leading to becoming
committers. The comments on the last two reports suggested to add people
sooner rather than later. I think this is a great model, but I also think
that needs to be balanced with having a higher commitment to the project
than just contributing something once. Do you have any suggestions on what
would be the minimal someone should do to be considered for a committer?
- As explained in the Health report point below, work has slowed with the
start of university semesters. We are hopeful these two people will have
more opportunity to engage as things pick up toward our next release.
## Health report:
- Committee Health score: -2.65 (Action required!) - The report generator tool
lists VCL as having a low health score. The VCL project has had very slow
progress in the last few months, but that does not mean no progress. Most of
the committers involved in the project work for universities and have had
other responsibilities take priority at the beginning of the fall semester.
Progress toward our next release (which only needs a little more work)
should pick back up again in the next few weeks as start of semester
activities die down.
## PMC changes:
- Currently 7 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Aaron Coburn on Tue Jun 19 2012
## Committer base changes:
- Currently 8 committers.
- No new committers added in the last 3 months
- Last committer addition was Young Hyun Oh at Sun Dec 08 2013
## Releases:
- Last release was 2.5 on Thu Aug 17 2017
## Mailing list activity:
- dev@vcl.apache.org:
- 117 subscribers (down -7 in the last 3 months):
- 17 emails sent to list (122 in previous quarter)
- user@vcl.apache.org:
- 157 subscribers (down -7 in the last 3 months):
- 1 emails sent to list (3 in previous quarter)
## JIRA activity:
- 3 JIRA tickets created in the last 3 months
- 2 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment BQ: Report from the Apache Whimsy Project [Sam Ruby]
-----------------------------------------
Attachment BR: Report from the Apache Wicket Project [Martijn Dashorst]
Report from the Apache Wicket project [Martijn Dashorst]
Apache Wicket is an open source Java component oriented web application
framework.
## Noteworthy items:
- Wicket 8.1 was released
- Wicket 8 was received very well, download statistics for Maven central are
more than doubled in August
## Issues:
- No issues require board attention.
## Activity:
- Work on Wicket 9 continues and is in its early stages
- First update for Wicket 8 was released
## Health report:
- The community is stable as is to be expected from a mature server side Java
web framework. We don't anticipate a sudden large growth or large decline.
- Questions to the user list and dev list are answered, resolved and
discussed.
## PMC changes:
- Currently 30 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Maxim Solodovnik on Thu Apr 13 2017
## Committer base changes:
- Currently 31 committers.
- No new committers added in the last 3 months
- Last committer addition was Maxim Solodovnik at Thu Apr 13 2017
## Releases:
- 8.1.0 was released on Mon Sep 10 2018
-----------------------------------------
Attachment BS: Report from the Apache Xalan Project [Steven J. Hathaway]
The Apache Xalan Project develops and maintains libraries and programs
that transform XML documents using XSLT standard stylesheets. Our subprojects
use the Java and C++ programing languages to implement the XSLT libraries.
Xalan is a mature project.
The libraries need some work to make sure the code base is operational
in the newer software development studios and platforms. The 'C++' project
needs significant work to become C++17 standards compliant. The Java library
has the most activity.
ISSUES FOR THE BOARD
We could use assistance with the details of inviting contributors to the PMC.
CURRENT ACTIVITY
Most activity has been through JIRA issue tracking. The email lists
have seen little activity. There are several contributors we are considering
as members to the PMC.
Contributors have recently increased their activity in both the Xalan-C and
Xalan-J projects.
There are two contributors to Xerces that have expressed an interest in
contributing to the Xalan projects. They have also contributed to the Xalan
JIRA system.
MEMBERSHIP
Changes in the PMC membership:
None.
There are two contributors that we are hoping to become active members of
the Xalan project. They currently support the Xerces project upon which
the Xalan project is based.
Last new committer:
May 2014
PROJECT RELEASES
Xalan Java 2.7.2 April 15, 2014
Xalan C/C++ 1.11 October 31, 2012
Publishing of project releases was refreshed Oct 30, 2014.
OTHER ISSUES
The libraries need some work to make sure the code base is operational
in the newer software development suites. We need to ensure that the
Xalan libraries are compatible with the Xerces projects.
There is also a concern that there is insufficient support to maintain
the Xalan projects.
BRANDING ISSUES
None.
-----------------------------------------
Attachment BT: Report from the Apache Xerces Project [Michael Glavassevich]
Xerces-J
With help from the community Xerces-J 2.12.0 was published to Maven Central in
June. There have been a few minor fixes and improvements made since the last
release. Most of the project activity has been mailing list discussion in the
last quarter.
Mailing list traffic has been moderate; roughly 190+ posts on the j-dev and
j-users lists since the beginning of May 2018.
No new releases since the previous report. The latest release is Xerces-J
2.12.0 (April 30th, 2018).
Xerces-C
A number of fixes and improvements have been made since Xerces-C 3.2.1. The
developers have been working on making a 3.2.2 release and started voting on a
release candidate last week.
Mailing list traffic has been low; roughly 70+ posts on the c-dev and c-users
lists since the beginning of May 2018.
No new releases since the previous report. The latest release is Xerces-C
3.2.1 (February 28th, 2018).
Xerces-P
Nothing in particular to report. There was no development activity over the
reporting period.
XML Commons
No activity over the reporting period.
Committer / PMC Changes
The most recent committers were added in April 2017 (Xerces-C) and May 2017
(Xerces-J).
No new PMC members since the last report. The most recent addition to the PMC
was in June 2016.
Three committers have committed changes to SVN since May 2018.
Apache Project Branding Requirements
The Xerces logo was updated in June to include a "TM" symbol. We have no
further actions for branding and so will be dropping this section from future
reports.
-----------------------------------------
Attachment BU: Report from the Apache Yetus Project [Allen Wittenauer]
## Description:
Apache Yetus provides libraries and tools that enable contribution and
release processes for software projects.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
No new PMC members added in the last three months; our last PMC addition
was Ajay Yadav on Thu Dec 01 2016. There are currently 8 PMC members.
No new committers added in the last three months; our last committer
addition was Akira Ajisaka on Tue Feb 06 2018. There are currently 12
committers.
The project released 0.8.0. This is the first release in a while that was
not centered around some sort of "bad actor" or a change to the ASF
infrastructure. Let's hope this continues!
## Health report:
Our typical pattern appears to continue: activity goes significantly up
due to the work required to get a new release out. Unless a new release
is eminent, next quarter will likely be another quiet one.
## Releases:
- 0.8.0 was released on Fri 30 Aug 2018
## Mailing list activity:
- dev@yetus.apache.org:
- 45 subscribers (up 1 in the last 3 months):
- 62 emails sent to list (28 in previous quarter)
- notifications@yetus.apache.org:
- 16 subscribers (up 0 in the last 3 months):
- 578 emails sent to list (141 in previous quarter)
## JIRA activity:
- 50 JIRA tickets created in the last 3 months
- 45 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment BV: Report from the Apache ZooKeeper Project [Flavio Paiva Junqueira]
## Description:
Apache ZooKeeper is a system for distributed coordination. It enables
the implementation of a variety of primitives and mechanisms that are
critical for safety and liveness in distributed settings, e.g.,
distributed locks, master election, group membership, and configuration.
## Issues:
No issue requiring board attention
## Activity:
- The community has released a bug-fix version of the 3.4 branch.
- The community organised a meetup in Budapest in June:
https://www.meetup.com/Cloudera-Tech-Meetup/events/250837466/
## Health report:
The summer months are typically not that active because of school breaks.
For this past period, the activity has remained roughly constant with some
minor changes. The community continues to work with contributors to offer
committership.
## PMC changes:
- Currently 13 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Michael Han on Wed Jun 21 2017
## Committer base changes:
- Currently 23 committers.
- No new committers added in the last 3 months
- Last committer addition was Andor Molnar at Fri Jun 01 2018
## Releases:
- 3.4.13 was released on Mon Jul 16 2018
## Mailing list activity:
The activity of the dev list has increased by roughly 13%, while the
activity of the user list has dropped by roughly 8%. The user list has
not been very active in the recent past, while the dev list has traditionally
been more active.
- dev@zookeeper.apache.org:
- 510 subscribers (up 2 in the last 3 months):
- 2632 emails sent to list (2320 in previous quarter)
- user@zookeeper.apache.org:
- 1219 subscribers (down -11 in the last 3 months):
- 176 emails sent to list (191 in previous quarter)
## JIRA activity:
- 85 JIRA tickets created in the last 3 months
- 66 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment BW: 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 does not typically report during this period, but given some
discussion on the private mailing list and the board attention that this
discussion has had, the PMC thought it best to submit a summary of the
current situation in this month's report to see what feedback the board may
have at this point. This issue is explained in detail below in the "Issues"
section.
As a side note, TinkerPop has recently added a new committer in Harsh
Thakkar.
## Issues:
For many months, the TinkerPop PMC has been discussing the idea of an
"emeritus system", similar in nature, but not quite the same, to what had
been published in Hadoop (and other TLP) by-laws. The fact that we had been
in discussion on this topic had been reported as private remarks on both the
July 2018[1] and the April 2018[2] reports. The board did provide some
general feedback on the April report[3] in relation to those remarks.
It was somewhat unfortunate that we'd classified this discussion as one
related to "emeritus", which has specific meaning in Apache parlance, as
ultimately the concern was more related to how the TinkerPop website
organized the listing of contributors to the project. Perhaps it took
discussion to get to that point of understanding, but none of this talk has
anything to do with revoking committer rights or removing PMC members.
With that much in mind, a summary of where the discussion has led can be
found here[4]. That post also contains some proposed work items based on
those points. Pending board feedback, there are likely still some open
issues:
1. RELEASE NOTES format changes should be discussed on the dev list for
wider feedback
2. The summary refers to a "bio update email" - the wording of that email
is perhaps a simple one or two sentences, but would require consideration.
## Releases:
- 3.2.9 (May 8, 2018)
- 3.3.3 (May 8, 2018)
## PMC/Committer:
- Last PMC addition was Robert Dale - April 2017
- Last committer addition was Harsh Thakkar - August 2018
## Links
[1] https://s.apache.org/nXG3
[2] https://s.apache.org/dOAN
[3] https://s.apache.org/TGId
[4] https://s.apache.org/TvsR
------------------------------------------------------
End of minutes for the September 19, 2018 board meeting.
Index