Index
Links: 2018 - All years
- Original The Apache Software Foundation
Board of Directors Meeting Minutes
June 20, 2018
1. Call to order
The meeting was scheduled for 10:30am Pacific and began at 10:31
when a sufficient attendance to constitute a quorum was
recognized by the chairman.
Other Time Zones: https://timeanddate.com/s/3hnf
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
Ted Dunning
Brett Porter
Roman Shaposhnik
Phil Steitz
Mark Thomas
Directors Absent:
Bertrand Delacretaz
Isabel Drost-Fromm
Executive Officers Present:
Ross Gardler
Sam Ruby - joined at 11:10
Craig L Russell
Matt Sicker
Ulrich Stärk - joined at 11:10
Executive Officers Absent:
none
Guests:
Daniel Gruno
Daniel Ruggeri
Danny Angus
Gavin McDonald
Kevin A. McGrail
Sharan Foga
Tom Pappas
3. Minutes from previous meetings
Published minutes can be found at:
http://www.apache.org/foundation/board/calendar.html
A. The meeting of May 16, 2018
See: board_minutes_2018_05_16.txt
Approved by General Consent.
4. Executive Officer Reports
A. Chairman [Phil]
This month, I worked on educating myself on non-profit finance and
worked with Sam and others on the idea for a VP, Finance to establish
a financial analysis and planning function at the ASF. This is
necessary now that we are considering long-term finance strategies
such as an endowment. I expect to spend a significant amount of time
over the next several months helping develop and support the finance
function at the ASF. I will also continue to work on educating myself
and helping interested members come up to speed and participate in
financial analysis and planning.
I did not make the progress that I hoped to make last month on
progressing the policy roadmap. I hope to get back to this in the
current month.
This month’s reports included some very good ones: Bean, Bloodhound,
DeltaSpike and Felix were all complimented for their comprehension and
thoughtfulness. In addition to the usual comments about long lapses
since new committer / PMC member additions and reminder that jira /
commit / mail volume stats are not useful unless supporting a specific
point, there were a few less common comments this month:
* Reminder to copy trademarks@ when dealing with potential
infringement issues
* Reminder that individuals contribute to ASF projects, not companies
* Observation that some important discussions on dev or private lists
were missing from project reports.
B. President [Sam]
Issues for the Board
====================
See VP, Finance resolution.
Overall
=======
Income running under plan. Expenses running slightly under plan.
Neither are a concern. Expenses are easier to plan for and we
consistently under-run the plan. Income is notoriously difficult to
determine when individual donations will be received, so it will
require a quarter or two before we can determine any real trends.
Brand Management
================
There are currently 36 tasks being tracked/monitored by the brand
management team.
Mostly "business as usual".
Most notable: Registrations have been submitted in the US for APACHE.
Fundraising
===========
Significant cycles spent on endowment. Details in the report. Quick
overall summary: based on a suggestion from Phil, this will be split
out into a separate role and generalized to overall financial
planning. Tom has been nominated to lead this, with work to be done
or brought back to a new finance@ mailing list. Everyone that has
contributed to the endowment discussion is welcome to participate.
No increase of expenditures to Virtual are being asked for at this
time. Some of the expenses budgeted for Bronze Sponsor relations that
have not yet been started may be redirected to expenses related to the
development of an endowment proposal (e.g., third party review of
proposals).
Informal target for bringing a completed proposal for ratification by
the board is the September board meeting. No funds will be solicited
until we have a board approved plan. Meanwhile, I plan to operate
under the assumption that I (The President) can approve or delegate
the approval of reasonable expenditures and discussions with third
parties (specifically items like a review of proposal seeking input,
and specifically EXCLUDING actual solicitation).
Additionally, please see Attachments 1 through 6.
C. Treasurer [Ulrich]
Virtual Report:
Here is a summary of the Foundation’s Financial performance for the
first month of FY19;
Operating Cash on May 31st, 2018 was $1,999K, which is down $73K from
last month’s ending balance (Apr 18) of $2,072K. Total Cash as of
May 31st, 2018 is $3,392K ( includes the Pineapple and restricted
Donation). The May 2018 ending Operating cash balance of $1,999K
represents an Operating cash reserve of 12.6 months based on the FY19
conservative Cash forecast average monthly spending of $158.1K/month(
which is roughly $55K/month higher than the FY18 avg monthly expense
amount). The ASF reserve continues to be very healthy for an
organization of the ASF’s size.
Regarding the YTD Cash P&L, the ASF, with regard to Income, was down
both vs budget and vs FY18. With regard to the Income vs Budget we
were off $94K due mostly to timing of sponsor payments. This is the
same issue when compared to FY18 where a couple of Platinum sponsor
payments arrived in May vs April. YTD expenses, through May 31st,
2018 are under budget by $40.4K, with all but Fundraising being under
budget ( this is timing related as both the May and Jun Sponsorship
paid service, were made in May and Infra is under due to timing of
Lease web and staffing expenses as is Publicity due to timing of some
vendor invoices ). Expenses, as compared to May 2017 were $38.2K
higher due to increases in Fundraising and the timing of some
Publicity vendor payments, that were offset by lower Infra costs due
to the timing of the Travis CL and Lease web payments.
Regarding Net Income (NI), for May 2018 the ASF finished with a -
$72.5K NI vs a budgeted negative <$18.6K> NI or $53.9K behind the
May 2018 budget for Net Income. This was mostly attributable to
timing of Sponsor payments though there were some vendor invoice
timing issues as well so we will monitor this going forward, however
as this is the first month of the Fiscal year, this type of result is
not A-typical.
Financials:
Current Balances:
Boston Private Checking Account 2,250,000.00
Citizens Money Aprket 965,948.70
Citizens Checking 173,934.78
Paypal - ASF 2,037.84
Total Checking/Savings 3,391,921.32
May-18 Budget Variance
Income Summary:
Inkind Revenue 0.00 0.00 0.00
Public Donations 2,970.30 8,212.23 -5,241.93
Sponsorship Program 70,000.00 165,000.00 -95,000.00
Programs Income 0.00 0.00 0.00
Other Income 9,710.12 2,881.17 6,828.95
Interest Income 293.63 1,160.65 -867.02
Total Income 82,974.05 177,254.05 -94,280.00
Expense SumApry:
In Kind Expense 0.00 0.00 0.00
Infrastructure 59,757.16 90,128.32 -30,371.16
Sponsorship Program 20,836.39 17,333.34 3,503.05
Programs Expense 0.00 0.00 0.00
Publicity 62,389.47 72,858.34 -10,468.87
Brand Management 5,129.39 8,166.67 -3,037.28
Conferences 500.00 0.00 500.00
Travel Assistance Committee 0.00 0.00 0.00
Tax and Audit 2,500.00 2,150.00 350.00
Treasury Services 3,350.00 3,350.00 0.00
General & Administrative 1,015.08 1,841.28 -826.20
Total Expense 155,477.49 195,827.95 -40,350.46
Net Income -72,503.44 -18,573.90 -53,929.54
YTD 2018 Budget Variance
Income Summary:
Inkind Revenue 0.00 0.00 0.00
Public Donations 2,970.30 8,212.23 -5,241.93
Sponsorship Program 70,000.00 165,000.00 -95,000.00
Programs Income 0.00 0.00 0.00
Other Income 9,710.12 2,881.17 6,828.95
Interest Income 293.63 1,160.65 -867.02
Total Income 82,974.05 177,254.05 -94,280.00
Expense SumApry:
In Kind Expense 0.00 0.00 0.00
Infrastructure 59,757.16 90,128.32 -30,371.16
Sponsorship Program 20,836.39 17,333.34 3,503.05
Programs Expense 0.00 0.00 0.00
Publicity 62,389.47 72,858.34 -10,468.87
Brand Management 5,129.39 8,166.67 -3,037.28
Conferences 500.00 0.00 500.00
Travel Assistance Committee 0.00 0.00 0.00
Tax and Audit 2,500.00 2,150.00 350.00
Treasury Services 3,350.00 3,350.00 0.00
General & Administrative 1,015.08 1,841.28 -826.20
Total Expense 155,477.49 195,827.95 -40,350.46
Net Income -72,503.44 -18,573.90 -53,929.54
D. Secretary [Craig]
In May, 54 ICLAs, four CCLAs, and two grants were received and filed.
E. Executive Vice President [Ross]
Infrastructure
==============
The earliest cloud service credits donations are coming up for
renewal. No concerns about lack of renewal at this time.
Thanks to the long running work to Puppetize workloads Infra is now
able to move services to take advantage of cost structures (e.g. low
bandwidth charges in EU)
Marketing and Publicity
=======================
Annual Report is being prepared.
Sponsor engagement / support continues to reap benefits.
Mostly "business as usual".
Conferences
===========
Apache EU Roadshow was a success. There are ongoing conversations
about further collaborations with NewThinking producers.
ACNA18 now becomes the focus with respect to promotional work. Please
help amplify. There is a call for volunteers open for help with items
not covered by paid staff.
On going discussions relating to Chicago and DC Roadshow proposals and
early stage conversations about potential for ApacheCon in Seoul in
2019.
TAC
===
Of the 28 that applied, 13 were accepted for ACNA.
F. Vice Chairman [Shane]
Met with a potential Sponsor at Apache EU Roadshow - which was also an
amazing event!
ASFP wiki and issues space are still quiet; still working on suggested
guidelines for use. Often the speed of large-subscription mailing
lists is so fast to require a conscious decision to keep topics
focused.
Executive officer reports approved as submitted by General Consent.
5. Additional Officer Reports
A. VP of W3C Relations [Andy Seaborne / Brett]
No report was submitted.
B. Apache Legal Affairs Committee [Chris Mattmann / Rich]
See Attachment 8
C. Apache Security Team Project [Mark J. Cox / Bertrand]
See Attachment 9
Additional officer reports approved as submitted by General Consent.
6. Committee Reports
Summary of Reports
The following reports required further discussion:
# Attic [rb]
# BVal [rb]
# Olingo [rs]
# Pig [idf]
# UIMA [ps]
A. Apache Allura Project [David Philip Brondsema / Mark]
See Attachment A
B. Apache Any23 Project [Lewis John McGibbney / Phil]
No report was submitted.
@Phil: pursue a report for Any23
C. Apache Archiva Project [Olivier Lamy / Ted]
No report was submitted.
D. Apache Atlas Project [Madhan Neethiraj / Isabel]
See Attachment D
E. Apache Aurora Project [Jake Farrell / Shane]
See Attachment E
F. Apache Axis Project [Robert Lazarski / Roman]
See Attachment F
G. Apache Bahir Project [Luciano Resende / Ted]
See Attachment G
H. Apache Beam Project [Davor Bonaci / Phil]
See Attachment H
I. Apache Bigtop Project [Peter Linnell / Brett]
No report was submitted.
@Phil: pursue a report for Bigtop
J. Apache Bloodhound Project [Gary Martin / Mark]
See Attachment J
K. Apache BVal Project [Matthew Jason Benson / Roman]
See Attachment K
L. Apache Camel Project [Andrea Cosentino / Isabel]
See Attachment L
M. Apache Cayenne Project [Michael Ray Gentry / Shane]
See Attachment M
N. Apache Chemistry Project [Florian Müller / Bertrand]
See Attachment N
O. Apache CloudStack Project [Mike Tutkowski / Rich]
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 / Isabel]
See Attachment R
S. Apache Curator Project [Jordan Zimmerman / Mark]
See Attachment S
T. Apache DeltaSpike Project [Mark Struberg / Bertrand]
See Attachment T
U. Apache Eagle Project [Edward Zhang / Brett]
See Attachment U
V. Apache Falcon Project [Pallavi Rao / Rich]
See Attachment V
W. Apache Felix Project [Karl Pauls / Roman]
See Attachment W
X. Apache Flex Project [Tom Chiverton / Phil]
See Attachment X
Y. Apache Flink Project [Stephan Ewen / Isabel]
See Attachment Y
Z. Apache Forrest Project [David Crossley / Brett]
See Attachment Z
AA. Apache FreeMarker Project [Dániel Dékány / Ted]
See Attachment AA
AB. Apache Guacamole Project [Mike Jumper / Bertrand]
See Attachment AB
AC. Apache Gump Project [Stefan Bodewig / Mark]
See Attachment AC
AD. Apache Hama Project [Chia-Hung Lin / Shane]
See Attachment AD
AE. Apache Helix Project [Kishore G / Phil]
No report was submitted.
@Phil: pursue a report for Helix
AF. Apache Hive Project [Ashutosh Chauhan / Roman]
No report was submitted.
@Roman: pursue a report for Hive
AG. Apache Incubator Project [Justin Mclean / Rich]
See Attachment AG
AH. Apache Jackrabbit Project [Michael Dürig / Rich]
See Attachment AH
AI. Apache Karaf Project [Jean-Baptiste Onofré / Roman]
See Attachment AI
AJ. Apache Labs Project [Danny Angus / Shane]
See Attachment AJ
AK. Apache Libcloud Project [Tomaž Muraus / Ted]
See Attachment AK
AL. Apache Lucene Project [Adrien Grand / Bertrand]
See Attachment AL
AM. Apache Lucene.Net Project [Prescott Nasser / Phil]
See Attachment AM
AN. Apache Marmotta Project [Jakob Frank / Mark]
See Attachment AN
AO. Apache Mnemonic Project [Gang Wang / Brett]
See Attachment AO
AP. Apache Mynewt Project [Justin Mclean / Isabel]
No report was submitted.
@Isabel: pursue a report for Mynewt
AQ. Apache OFBiz Project [Jacopo Cappellato / Shane]
See Attachment AQ
AR. Apache Olingo Project [Christian Amend / Roman]
See Attachment AR
AS. Apache OODT Project [Imesha Sudasingha / Ted]
See Attachment AS
AT. Apache OpenNLP Project [Jörn Kottmann / Brett]
See Attachment AT
AU. Apache OpenWebBeans Project [Mark Struberg / Isabel]
See Attachment AU
AV. Apache Perl Project [Philippe Chiasson / Phil]
No report was submitted.
@Rich: pursue a report for Perl and possibly change the chair
or "escalate" to dev@
AW. Apache Pig Project [Koji Noguchi / Rich]
See Attachment AW
AX. Apache Pivot Project [Roger Lee Whitcomb / Mark]
See Attachment AX
AY. Apache Polygene Project [Paul Merlin / Bertrand]
No report was submitted.
AZ. Apache Portable Runtime (APR) Project [Nick Kew / Ted]
See Attachment AZ
BA. Apache Portals Project [David Sean Taylor / Bertrand]
See Attachment BA
BB. Apache PredictionIO Project [Donald Szeto / Rich]
See Attachment BB
BC. Apache Royale Project [Harbs / Brett]
See Attachment BC
BD. Apache Sentry Project [Alex Kolbasov / Phil]
See Attachment BD
BE. Apache Serf Project [Bert Huijben / Roman]
See Attachment BE
BF. Apache ServiceMix Project [Krzysztof Sobkowiak / Isabel]
See Attachment BF
BG. Apache Shiro Project [Les Hazlewood / Mark]
See Attachment BG
BH. Apache Sling Project [Robert Munteanu / Shane]
See Attachment BH
BI. Apache SpamAssassin Project [Sidney Markowitz / Rich]
See Attachment BI
BJ. Apache Stanbol Project [Fabian Christ / Brett]
No report was submitted.
@Brett: pursue a report for Stanbol
BK. Apache Storm Project [P. Taylor Goetz / Isabel]
See Attachment BK
BL. Apache Synapse Project [Isuru Udana / Phil]
See Attachment BL
BM. Apache Tajo Project [Hyunsik Choi / Roman]
See Attachment BM
BN. Apache Tapestry Project [Thiago Henrique De Paula Figueiredo / Bertrand]
See Attachment BN
BO. Apache Tiles Project [Michael Semb Wever / Shane]
See Attachment BO
BP. Apache Tomcat Project [Mladen Turk / Ted]
See Attachment BP
BQ. Apache Traffic Control Project [David Neuman / Mark]
See Attachment BQ
BR. Apache Trafodion Project [Pierre Smits / Roman]
See Attachment BR
BS. Apache Twill Project [Terence Yim / Mark]
No report was submitted.
@Mark: pursue a report for Twill
BT. Apache UIMA Project [Marshall Schor / Rich]
See Attachment BT
BU. Apache VCL Project [Josh Thompson / Phil]
See Attachment BU
BV. Apache Wicket Project [Martijn Dashorst / Ted]
See Attachment BV
BW. Apache Xalan Project [Steven J. Hathaway / Isabel]
See Attachment BW
BX. Apache Yetus Project [Allen Wittenauer / Bertrand]
See Attachment BX
BY. Apache ZooKeeper Project [Flavio Paiva Junqueira / Brett]
See Attachment BY
BZ. Apache Attic Project [Jan Iversen / Brett]
See Attachment BZ
Committee reports approved as submitted by General Consent.
7. Special Orders
A. Terminate the Apache Lucy Project
WHEREAS, the Project Management Committee of the Apache Lucy
project has chosen by vote to recommend moving the project to the
Attic; and
WHEREAS, the Board of Directors deems it no longer in the best
interest of the Foundation to continue the Apache Lucy project
due to inactivity;
NOW, THEREFORE, BE IT RESOLVED, that the Apache Lucy
project is hereby terminated; and be it further
RESOLVED, that the Attic PMC be and hereby is tasked with
oversight over the software developed by the Apache Lucy
Project; and be it further
RESOLVED, that the office of "Vice President, Apache Lucy" is
hereby terminated; and be it further
RESOLVED, that the Apache Lucy PMC is hereby terminated.
Special Order 7A, Terminate the Apache Lucy Project, was
approved by Unanimous Vote of the directors present.
B. Change the Apache Attic Project Chair
WHEREAS, the Board of Directors heretofore appointed Jan Iversen
(jani) to the office of Vice President, Apache Attic, and
WHEREAS, the Board of Directors is in receipt of the resignation of
Jan Iversen from the office of Vice President, Apache Attic, and
WHEREAS, the Project Management Committee of the Apache Attic project
has chosen by vote to recommend Henk P. Penning (henkp) as the
successor to the post;
NOW, THEREFORE, BE IT RESOLVED, that Jan Iversen is relieved and
discharged from the duties and responsibilities of the office of Vice
President, Apache Attic, and
BE IT FURTHER RESOLVED, that Henk P. Penning be and hereby is appointed
to the office of Vice President, Apache Attic, 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 Attic Project Chair, was
approved by Unanimous Vote of the directors present.
C. Change the Apache Oozie Project Chair
WHEREAS, the Board of Directors heretofore appointed Robert Kanter
(rkanter) to the office of Vice President, Apache Oozie, and
WHEREAS, the Board of Directors is in receipt of the resignation of
Robert Kanter from the office of Vice President, Apache Oozie, and
WHEREAS, the Project Management Committee of the Apache Oozie project
has chosen by vote to recommend Gézapeti (gezapeti) as the successor to
the post;
NOW, THEREFORE, BE IT RESOLVED, that Robert Kanter is relieved and
discharged from the duties and responsibilities of the office of Vice
President, Apache Oozie, and
BE IT FURTHER RESOLVED, that Gézapeti be and hereby is appointed to the
office of Vice President, Apache Oozie, to serve in accordance with and
subject to the direction of the Board of Directors and the Bylaws of
the Foundation until death, resignation, retirement, removal or
disqualification, or until a successor is appointed.
Special Order 7C, Change the Apache Oozie Project Chair, was
approved by Unanimous Vote of the directors present.
D. Change the Apache Lucene.Net Project Chair
WHEREAS, the Board of Directors heretofore appointed Prescott Nasser
(pnasser) to the office of Vice President, Apache Lucene.Net, and
WHEREAS, the Board of Directors is in receipt of the resignation of
Prescott Nasser from the office of Vice President, Apache Lucene.Net,
and
WHEREAS, the Project Management Committee of the Apache Lucene.Net
project has chosen by vote to recommend Shad Storhaug (nightowl888) as
the successor to the post;
NOW, THEREFORE, BE IT RESOLVED, that Prescott Nasser is relieved and
discharged from the duties and responsibilities of the office of Vice
President, Apache Lucene.Net, and
BE IT FURTHER RESOLVED, that Shad Storhaug be and hereby is appointed
to the office of Vice President, Apache Lucene.Net, 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 Lucene.Net Project Chair,
was approved by Unanimous Vote of the directors present.
E. Establish Position of VP, Finance
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 officer responsible for financial matters, including but
not limited to financial planning and management of financial risks.
NOW, THEREFORE, BE IT RESOLVED that the office of "Vice President,
Finance" be and hereby is created, the person holding such office to
serve at the direction of the President, and to have primary
responsibility of managing the ASF's financial strategy; and be it
further
RESOLVED, that Tom Pappas be and hereby is appointed to the office of
Vice President, Finance, to serve in accordance with and subject to
the direction of the President until death, resignation, retirement,
removal or disqualification, or until a successor is appointed.
Special Order 7E, Establish Position of VP, Finance, was
approved by Unanimous Vote of the directors present.
F. Change the Apache Tika Project Chair
WHEREAS, the Board of Directors heretofore appointed David Meikle
(dmeikle) to the office of Vice President, Apache Tika, and
WHEREAS, the Board of Directors is in receipt of the resignation of
David Meikle from the office of Vice President, Apache Tika, and
WHEREAS, the Project Management Committee of the Apache Tika project
has chosen by vote to recommend Tim Allison (tallison) as the successor
to the post;
NOW, THEREFORE, BE IT RESOLVED, that David Meikle is relieved and
discharged from the duties and responsibilities of the office of Vice
President, Apache Tika, and
BE IT FURTHER RESOLVED, that Tim Allison be and hereby is appointed to
the office of Vice President, Apache Tika, to serve in accordance with
and subject to the direction of the Board of Directors and the Bylaws
of the Foundation until death, resignation, retirement, removal or
disqualification, or until a successor is appointed.
Special Order 7F, Change the Apache Tika Project Chair, was
approved by Unanimous Vote of the directors present.
8. Discussion Items
A. Appoint Phil Steitz to the position of Assistant Treasurer
Phil has volunteered to serve as Assistant Treasurer, filling the role
vacated at the end of April by Kevin McGrail.
The board appoints Phil Steitz to the position of Assistant Secretary
by general consent.
9. Review Outstanding Action Items
* Brett: pursue a report or Attic proposal for Xalan
[ Xalan 2018-02-21 ]
Status: message sent to PMC - they are looking to add committers
* Mark: get an answer to question on previous report: "..automatic generation
[ Sentry 2018-03-21 ]
Status: The June report answers this question in some detail. Action
closed.
* Mark: when will the TM be added to the logo?
[ Xerces 2018-03-21 ]
Status: Ongoing. Date requested from PMC no later than next report
(August)
* Rich: follow up re: responses to board comments
[ MyFaces 2018-04-18 ]
Status: Closed: Discussion on the list acknowledged that the concern
was being taken seriously, but it doesn't appear that anyone
is working on it yet. I believe that this action item is
complete, in that they are aware and plan to do something
about it. (This was in regard to the "maintenance only" status
of some of the sub projects, which is not called out clearly
on the websites.)
* Mark: pursue a report for Tapestry
[ Tapestry 2018-04-18 ]
Status: Closed: 2018-06-18 Followed the standard reminder from BD with
a slightly stronger message. Report has been provided.
* Shane: send note publicizing the list of services to the PMCs; precise url
[ Publicize board-sanctioned list of services available to projects 2018-04-18 ]
Status: Ongoing.
* Shane: continue to discuss establishing a COI policy on board@
[ Adopting a well-known COI policy 2018-04-18 ]
Status: DEFER (i.e. no longer an action item): this is a longer
discussion as part of any policy work the board will adopt.
* Daniel: flesh out what sponsor plus means
[ Fundraising 2018-05-16 ]
Status: Completed and shared w/ board:
https://lists.apache.org/thread.html/31fe15de55fb43aba3b8e626deaa4158b90b9b4a03ac9139644b13a9@%3Cboard.apache.org%3E
* Roman: start discussion with members on how to deal with unaddressed
security
[ Security Team 2018-05-16 ]
Status: Complete.
* Brett: pursue a report for DeltaSpike
[ DeltaSpike 2018-05-16 ]
Status: reminder sent
* Phil: pursue a report for Hama
[ Hama 2018-05-16 ]
Status: Complete: Report has been submitted.
* Isabel: follow up to get a better report next month
[ Libcloud 2018-05-16 ]
Status: Complete.
* Ted: remind them to please be sure to report next month
[ Lucene.Net 2018-05-16 ]
Status: Reminder sent
* Rich: ask for a new chair, due to chronic missed or late reports
[ Perl 2018-05-16 ]
Status: Closed: Philippe Chiasson responded swiftly with a promise to
pay more attention in the future. I'll call this closed, but
something we need to continue to watch going forward.
* Mark: pursue a report (again) for Tapestry
[ Tapestry 2018-05-16 ]
Status: Closed. Same action still open from April meeting so track
there.
* Brett: pursue a report for Xalan
[ Xalan 2018-05-16 ]
Status: duplicate action
* Phil: work with infrastructure (Greg) on plans for projects with
extraordinary requirements
[ Action Items 2018-05-16 ]
Status: Ongoing.
10. Unfinished Business
11. New Business
12. Announcements
13. Adjournment
Adjourned at 12:00 p.m. (Pacific)
============
ATTACHMENTS:
============
-----------------------------------------
Attachment 1: Report from the VP of Brand Management [Mark Thomas]
* ISSUES FOR THE BOARD
None.
* OPERATIONS
Approved one event for GEODE. Answered external questions regarding how
to refer to Apache marks in one textbook, in one software product, in
one presentation and on one website. Provided copy for the ASF Annual
Report. Approved one Podling Name Search and provided feedback on
another. Provided advice to ServiceComb regarding trademark transfer and
graduation.
There are currently 36 tasks being tracked/monitored by the brand
management team.
* REGISTRATIONS
Registrations have been submitted in the US for APACHE, OPENOFFICE and
APACHE IGNITE.
Worked with the Beam PMC to provide direction to our lawyers regarding
an office action associated with our application for BEAM.
* INFRINGEMENTS
Provided advice to the Hive PMC regarding a potential infringement.
Outstanding issues being progressed by the Impala PMC have been
satisfactorily resolved.
-----------------------------------------
Attachment 2: Report from the VP of Fundraising [Daniel Ruggeri]
Daniel Ruggeri:
A successful month in terms of day-to-day fundraising
activities as well as thoughtful conversations around expanding fundraising
and solidifying our future.
Endowment Conversations
* We have broached the topic of "Should we pursue an endowment?" with the
membership at large. Lots of feedback and conversation ensued resulting in
the gathering of data into a starting point document.
* Several folks have engaged to lend their expertise and help shape the
potential plan on the fundraising@ list.
* A proposal has been drafted to re-purpose a portion of the fundraising
budget to focus specifically on examining the idea of and potential planning
for establishing an endowment.
* Conversations are beginning on what this might mean to our outreach (Sponsor
Relations) activities
Other day to day:
* Confusion around "Sponsor+" and "Platinum+" terminology was held resulting
in a finalized name of "Sponsor + Events". Key takeaway: This is not a new
level of sponsorship or new fundraising program - just a way to bundle and
recognize sponsors for the expanded support.
* "Sponsor + Events" conversations with VP Marketing & Publicity as well as VP
Conferences have been held to ensure alignment.
* Ideas of running a yearly, more visible campaign (colloquially referred to
as "Super Thermometer Campaign") as well as using a formal IT system for
sponsor tracking and handling were initially discussed, but tabled due to
the endowment conversations.
* Strong fundraising work this month. We have some excitement due to new,
returning and renewing sponsors.
KAM:
Overall, fundraising continues to go well. Some small points: Work for
additional bronze ambassador support from Tom is delayed pending both a
contract vehicle from Virtual as well as discussions around a pivot to use
the budget for a VP, Finance role. Committee meetings continue to occur
monthly. Continue improving our fundraising procedures and working on our
playbook website. Daniel Ruggeri now has access to my private notes and task
tracking system. The ASF Sponsor Benefits is now cleaned up and consistent
with the slide deck.
And now bigger points:
- Sponsor.apache.org is now fixed. Thanks Infra!
- The minimum for Hopsie donations is now working at $5. Otherwise, donating a
dollar nets us a few cents.
- Submitted annual report for Fundraising to SK:
2018 FUNDRAISING REPORT by Kevin A. McGrail aka KAM
As always, we would like to start our fundraising report by thanking our
sponsors for their continued support. As a 501(c)(3) charity, our sponsors
are our sole source of funding. We could not do it without them!
For fiscal year 2018, thanks to our generous sponsors, we finished with a
positive net income and raised 150% of our goals. We also benefited from an
additional large donation that netted just under $900K from the Pineapple
Fund which opened up the ability to explore endowments for the long-term
viability of the Apache Software Foundation.
In fact, this year has been all about bringing new ideas to the sponsorship
program.
In the first quarter, the ASF Fundraising team welcomed Kevin A. McGrail to
the role of VP Fundraising after he worked to launch our individual sponsor
program with Hopsie in his role as Assistant Treasurer. After brainstorming
ideas at two face to face meetings, we identified a lot of points where we
could improve things and set ambitious goals for the year.
In the second quarter, we worked to refine our Targeted Sponsorship program
that recognizes sponsors who support us in ways beyond normal sponsorship.
Donated software, credits for cloud servers, graphical work, travel
assistance, legal support and more!
We also looked at creating a closely related company to help the Apache
Software Foundation do things outside of our 501(c)(3) and support the
foundation. We decided against doing so but it was a valuable exercise.
In the third quarter, we launched our new thanks page including Targeted
Sponsorship. We also began heavily working on three Apache events for 2018:
ApacheCon 2018 North America in Montreal in September, the Apache 2018 EU
Roadshow in Berlin in June and the Apache 2018 US Roadshow in Washington, DC
in October.
The DC Roadshow is one of the first, if not the first event that we are
looking to provide a career fair at the same time as we have a day long track
on open source!
Visit https://apachecon.com for more information. We hope to see you at one
if not all of the events.
Finally, we increased our sponsorship rates for the first time in our 18 year
history.
In the fourth quarter, we began working on the concept of an endowment in
earnest which continues with lots of debate. Looking back over the whole
year, we had a lot of small but important news: We added routine committee
meetings.
We were chosen by Amazon for early access to Alexa Donations with Amazon Pay
("Make a donation to the Apache Software Foundation").
We began asking for multi-year commitments to bring more stability to
operations.
We grew the ambassador program to make sure our sponsors each have a contact
to improve two-way communications.
We expanded our work with Virtual to continue improving our operations,
fundraising & accounting. This has been a wonderful partnership that we are
working to expand again further.
We completed our first ever audit with an unqualified status and brought our
Guidestar profile up to Gold status.
And finally, to recognize our “Apache Family”, we want to recognize the
support of the following sponsors:
8 Platinum Sponsors: Cloudera, Comcast, Facebook, Google, LeaseWeb,
Microsoft, Oath & the Pineapple Fund.
9 Gold Sponsors: Anonymous (we know who you are!), ARM, Bloomberg,
Hortonworks, Huawei, IBM, Indeed, ODPI & Pivotal.
8 Silver Sponsors: Aetna, Budget Direct, Capital One, Cerner, Inspur, Private
Internet Access, Red Hat, Target & Union Investment.
14 Bronze Sponsors: Airport Rentals, The Blog Starter, Casino Bonus,
Bookmakers, Casino2k, Emerio, HostChecka.com, HostingAdvice.com, HostPapa Web
Hosting, The Linux Foundation, Mobile Slots, SCAMS.info, Site Builder Report,
Twitter & Web Hosting Secret Revealed
&
4 Platinum Targeted Sponsors: Microsoft, Oath, OSU Open Source Labs &
Sonatype.
5 Gold Targeted Sponsors: Atlassian, The CrytpoFund, Datadog, PhoenixNAP &
Quenda.
3 Silver Targeted Sponsors: Amazon Web Services, Hotwax Systems & Rackspace.
11 Bronze Targeted Sponsors: Assembla, Bintray, Education Networks of
America, Google, Hopsie, No-IP, PagerDuty, Peregrine Computer Consultants
Corporation, Sonic.net, SURFnet & Virtru.
And last but not least, our 2018 event sponsors: Amazon, CloudOps, Comcast,
GridGain, IBM, Linode, Red Hat, ShapeBlue & Talener. Thank you!
As we head towards our 20th anniversary, we welcome Daniel Ruggeri as a co-VP
of Fundraising. Together we want to express our thanks to our very generous
Sponsors who are crucial to the Apache Software Foundation’s success! Thank
you, thank you, thank you.
Events:
Attended BBW & FOSS Backstage for ASF to speak on How to be an Effective
Board Member: https://foss-backstage.de/session/how-be-effective-board-member
The show was a great success in my opinion. NewThinking is a wonderful
organization and the venue was great. Also had a number of meetings and will
have an after report done in the next few days.
After report at https://lists.apache.org/thread.html/9f6114a064e0250e7910b80c9af3f3a9b96d51495a2cf3be0c53ad98@%3Cfundraising.apache.org%3E
- Work continues on our remaining two 2018 Apache events including sponsor
agreements and pitches. NOTE: We are almost sold out for the sponsorship
for ApacheCon.
- Attended breakfast for GMU Cyber. Key benefit was support for JP who is our
sponsor for the DC Roadshow. A meeting is being coordinated to plan the
roadshow further now that the Berlin show is out of the way.
- (Repeat from last report): Planning to attend AC2018 to speak on Inclusion,
Meritocracy and the Apache Way
- Framework for Sponsor + Events (previously Sponsor+) updated and approved
by Rich. See
https://docs.google.com/document/d/1O4kz-OZY8UTXwtorctWwFe0OCZ2ChJ8vPVYva4-qoDc/edit#heading=h.sktiqud2p4nr
- Coordination for Huawei annual conference: From Chris Xie: “Huawei Connect
2018 conference has allocated one exhibition booth (about 6 square meters) to
showcase Apache Software Foundation during the conference. This is just to
give you a heads-up notice so that you can think about how you would like to
utilize this booth for ASF. Zhanghaitao(Hector) in the cc list is helping
organize this event. If you have further questions, please feel free to let
him know.”
- The endowment project is effectively on hold for anyone outside the
foundation. Additional Key points:
Copied Sam & Roman’s notes into the overview doc. Spoke to Myrle’s mother
about the endowment. She has recommended we talk to John H. Taylor
Consulting. Sam’s goal is to create a new role, VP Finance with a goal of
having an endowment ready for a board consideration in the Fall. Roman
obtained a proposal from the Jewish Community Foundation that he’s having
vetted to share further.
- Discussions with Dito continue about bringing GAM
https://github.com/jay0lee/GAM under the ASF Umbrella
- Two Recommendations for the Board from our events discussion:
#1 - For next year, the budget should include the max risk exposure assuming
worst case scenarios: There is a concern that events are beyond the level of
risk exposure that the budget was intended to allow for due to unclear
processes at the ASF for signatory privileges:
https://lists.apache.org/thread.html/af9 5e4303d2b7801a1d2da3f4841133b33b4583b8494da98859cac1b@%3Cboard.apache.org%3E
Clarify if budgets are based on the Net or Gross and if Net, then also
include a maximum risk exposure. Real World Recommendation: The ASF CY 2019
Event Budget should be revised for a Net Loss of 100K with a max signature
authority of 250K.
#2 - We need to spend money from sponsors.
https://lists.apache.org/thread.html/66b 77312d1281c5a68867dd3c8b87c91a4bc51bd18137dac56fe7829@%3Cboard.apache.org%3E
We cannot simply grow a hoard of cash. Losing money on events around the
world with a variety of roadshows and apachecon is a good implementation of
our mission for OSS by educating people.
Based on past performance, ApacheCon is not a money maker and should not be
considered to be one. However, it is an amazing event that should be
considered a success based on attendance not profit.
As such, we recommend the board align the CY 2019 budget for a $100K loss on
conferences as an excellent and appropriate use of our sponsor funds. We do
not need to break even on our events as we raise funds elsewhere.
The Sponsor + Events and Fundraising improvements allow Conferences to have
financial freedom to run worthwhile events with less concern about the
financial impact and lower cost of entry for attendees.
NOTE: Only subsidize, do not give away free attendance.
https://en.wikipedia.org/wiki/Giffen_good
- We continue working to get targeted sponsors for Infra and Legal
-----------------------------------------
Attachment 3: Report from the VP of Marketing and Publicity [Sally Khudairi]
[REPORT] ASF Marketing & Publicity - June 2018
I. Budget: we are on budget and on schedule. All vendor payment requests have
been submitted for processing.
II. Cross-committee Liaison: Sally Khudairi is preparing the ASF Annual
Report. She continues day-to-day Sponsor ambassadorial outreach with
Fundraising under her new role of VP Sponsor Relations, and has issued our
first joint press release announcing the new Targeted Sponsor program
https://s.apache.org/eTNY . Sally is also working on closing a new
Platinum-level Sponsor. She has been working with ASF Conferences and
Community Development on promoting ApacheCon and the Apache Roadshow events,
as well as the ASF's participation in community events such as Open Expo
Europe and OSCON. She is counseling a a podling in the Apache Incubator to
correct their promotional practices to align with established ASF publicity,
outreach, and branding guidelines. We published the latest "Success at Apache"
post: "The Chance to Influence the World" https://s.apache.org/MfuS .
III. Press Releases: the following formal announcements were issued via the
newswire service, ASF Foundation Blog, and announce@apache.org during this
timeframe:
- 4 June 2018 - The Apache Software Foundation Announces Apache® Traffic
Control™ as a Top-Level Project
- 31 May 2018 - The Apache® Software Foundation Announces Added Support by
Oath to Help Apache Infrastructure
- 23 May 2018 - The Apache Software Foundation Announces Apache® Wicket™
v8.0.0
- 17 May 2018 - The Apache® Software Foundation Announces Agenda, Keynotes,
and Sponsors for ApacheCon™ North America 2018
IV. Informal Announcements: 9 items were published on the ASF "Foundation"
Blog. 5 Apache News Round-ups were issued, with a total of 205 weekly
summaries published to date. We tweeted 27 items, and have 48.4K followers on
Twitter. We posted 10 items on LinkedIn, which garnered more than 33.2K
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 5 media queries. The ASF received 1,241
press clips vs. last month's clip count of 1,999. Media coverage of Apache
projects yielded 4,174 press hits vs. last month's 4,690. ApacheCon received
108 press hits.
VII. Analyst Relations: we received one analyst query. Apache was mentioned in
23 reports by Gartner; 1 reports by Forrester; 8 reports by 451 Research; and
8 reports by IDC.
VIII. Graphics: aside from production for graphics for the Annual Report, no
projects are currently underway.
IX. Events liaison: Sally continues work with ASF Conferences and ComDev
regarding upcoming Apache Community events that include ApacheCon and both
Apache Roadshows. In addition, she is assisting with securing media and
community partners for ApacheCon, as outreach has yet to be initiated by the
production team.
X. Newswire accounts: with the above 4 press releases, we have depleted our
pre-paid press release package with NASDAQ GlobeNewswire, and have now
initiated a new pre-paid contract through 2019.
# # #
-----------------------------------------
Attachment 4: Report from the VP of Infrastructure [David Nalley]
Finances
========
* One of our sponsors has provided cloud service credits for Infra to
use for running our services. These credits are running out at the
end of September, but we have received assurances they will be
continued. The Infra team has been working with Fundraising to
secure the continued credits, hopefully with an increase and with
public recognition under the "Targeted Sponsorship" program.
* Another sponsor has been providing cloud service credits, and Infra
has been working with Fundraising to streamline, simplify, and
recognize their donation.
* Taking advantage of our puppetized services, the team has been able
to easily shift services around to reduce our overall costs. In
particular, Europe has very low bandwidth charges, so we have moved
heavy users (rsync, archive, TLP) to European data centers.
Short Term Priorities
=====================
- The Apache Subversion server that we run has been having some
difficulties related to backups. The server runs in the United
States, and backs up to Europe. We plan to move this server to
Europe, which will have second order effects on costs, some
downstream services, and reliability.
- Our Jenkins build environment is due for an upgrade to the next LTS
release, as does Jira. We will be upgrading both of these systems
over the next month.
- In order to drop our open issue count, the Infra team is planning a
bug bash to occur on Monday, June 18th (two days before the Board
meeting).
Long Range Priorities
=====================
- Moving our email instructure from old FreeBSD-based systems into
newer, puppetized services has been an ongoing, difficult, and
long-term goal. Some good progress has been made on this front over
the past month, but we have lots of investigation, building, and
testing before enabling the new setup of this critical service.
General Activity
================
- Confluence was upgraded to 6.9.0
- Continued work on our new status and monitoring changes
- We had some failing disks on our mailing system, which took several
days to sort through. Additional disks were ordered, and we have two
hot spares installed now. This should hold us until our long-term
work enables our migration.
- We've had a project, Fineract, request a project VM with a resource
allocation an order of magnitude higher than what we typically
provide. We've told them that this request exceeds our ability to
provide the service, and redirected them to the Board to seek
funding for such a service.
-----------------------------------------
Attachment 5: Report from the VP of Conferences [Rich Bowen]
Conferences Board Report, June 2018
* EU Roadshow
The Apache EU Roadshow was last week in Berlin, in conjunction with
Berlin Buzzwords and FOSS Backstage.
Apache had a lounge, upstairs, with icecream and stickers. We had many
great conversations with many participants.
In addition to the Roadshow-specific content, it's also worth noting
that roughly half of the content for Berlin Buzzwords was related to
Apache projects. Overall, we had a great showing here.
We had a very productive conversation with the NewThinking producers,
and we are considering cooperating with them for future events. The fit
was perfect, and the event was brilliantly executed.
* ACNA18
With the EU Roadshow complete, we're starting to focus more on ApacheCon
Montreal. This includes:
- Increased traffic on Twitter, Facebook, and Google+ groups.
- Publishing videos and podcasts from the EU Roadshow, with the additional
message encouraging people to come to Montreal. This will hopefully also
give us the opportunity to promote some of these on higher-visibility
sites.
- Calls for volunteers (http://apachecon.com/acna18/volunteer.html) to
cover things that are not being handled by paid staff.
- Periodic reminders to dev and user lists of the event.
- Encouraging speakers to do their own event promotion.
Members are encouraged to amplify all of these efforts in their own
spheres of influence.
* DC Roadshow
While in Berlin, Kevin started working on the DC Roadshow website and
CFP. We should have something to announce there soon.
* Chicago Roadshow
Discussions are ongoing about doing a "Roadshow" type event in Chicago
in 2019.
* Seoul 2019
A discussion about doing an ApacheCon in Seoul in Spring 2019 is in very
preliminary stages.
-----------------------------------------
Attachment 6: Report from the Apache Travel Assistance Committee [Gavin McDonald]
Of the 28 that applied, 13 were accepted for ACNA this time around. We had a
high standard of applicants but in the end, these 13 stood out from the rest
as a group. The TAC team continue to get applicants ready for ACNA Rooms ,
flights and Visa letters are in progress but not yet complete. Not much else
happening at this time other than wait for the processes to complete. As last
year we will be using one Travel Agent for all flights. Treasurer is aware and
prepped to go for payments.
Apologies for the tardy commit of this report.
-----------------------------------------
Attachment 7: Report from the VP of W3C Relations [Andy Seaborne]
-----------------------------------------
Attachment 8: Report from the Apache Legal Affairs Committee [Chris Mattmann]
VP, Infra has provided a draft policy for GDPR that we are currently
reviewing. Progress has been slow but I expect in the next month or two to get
something finalized and posted regarding it. Most of the policy shifts the
operational day to day to infra, and appoints VP, Legal as a Data Privacy
officer for strategic review.
Given this, and also our DMCA policy which is extremely similar, I approached
the Board privately about considering the appointment of a VP, Data Privacy,
initially staffed by VP, Legal (me), but after six months, staffed by a new
volunteer, providing an opportunity for growth. It makes sense during this
time and I am willing to commit to doing so, but after six months I won't be
able to fulfill both positions and during that time, considering the wealth of
people chiming in w.r.t things like GDPR and other issues, I think finding
such a volunteer would not prove difficult. So, I specifically request that
the Board consider this officer appointment publicly in next month's meeting -
based on private positive feedback so far.
Discussions on the legal-discuss list are consistently answered in a timely
fashion, mostly by other contributors to the committee and the list.
-----------------------------------------
Attachment 9: Report from the Apache Security Team Project [Mark J. Cox]
Continued work on incoming security issues and helping projects clean
up the backlog of old issues and outstanding CVE names. Signifcant
co-ordination work happened in April and May based on the "Zip Slip"
flaws reported by Snyk that were reported in more than a dozen ASF
projects. In most cases these were not found to be security
vulnerabilities, and the affected code was fixed or removed.
Stats for May 2018:
6 [license confusion]
21 [support request/question not security notification]
Security reports: 55 (last months: 54, 47, 40)
5 [tomcat]
4 [hadoop]
3 [httpd]
3 [nifi]
2 [hbase], [ignite], [mesos], [spark], [tika]
1 [activemq], [apex], [beam], [bigtop], [cassandra],
[gobblin], [guacamole], [hive], [incubator/heron],
[incubator/superset], [incubator/systemml], [infrastructure],
[jackrabbit], [jmeter], [kafka], [lucene], [metron],
[openoffice], [orc], [qpid], [reef], [sentry], [spamassassin],
[storm], [struts], [tapestry], [trafficserver], [xerces],
[xmlgraphics], [yetus]
-----------------------------------------
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:
- One Google Summer of Code student is working with Allura this summer
- Various improvements and fixes continue
- A few new external users/devs have been active on our list & tickets.
## Health report:
A new release manager handled our last release, and some new users are good
to see. Otherwise still relatively quiet but steady.
The GSOC student may be someone we can add to the PMC, but otherwise no new
committer candidates on the horizon.
## PMC changes:
- No changes.
- Currently 14 PMC members.
- Kenton Taylor was added to the PMC on Sun Jan 22 2017
## Committer base changes:
- No changes.
- Currently 14 committers.
- Kenton Taylor was added as a committer on Thu Jan 19 2017
## Releases:
- 1.8.1 was released on Tue Mar 13 2018
-----------------------------------------
Attachment B: Report from the Apache Any23 Project [Lewis John McGibbney]
-----------------------------------------
Attachment C: Report from the Apache Archiva Project [Olivier Lamy]
-----------------------------------------
Attachment D: Report from the Apache Atlas Project [Madhan Neethiraj]
## Description:
Apache Atlas is a scalable and extensible set of core foundational
governance services that enables enterprises to effectively and efficiently
meet their compliance requirements within Hadoop and allows integration with
the complete enterprise data ecosystem
## Issues:
There are no issues requiring board attention at this time.
## Activity:
- released 1.0.0 version on 06/02/2018. This is a major release, result of
more than a year of contributions from Apache Atlas community. Here are
few of the features and enhancements in this release:
- introduction of relationships as a first-class type
- support for propagation of classifications along entity relationships –
like lineage
- fine-grained metadata security
- introduction of Glossary feature
- enhancements in notifications module to support V2 style data structures
- introduction of Atlas hook for HBase
- introduction of Atlas bridge for Kafka
- support for Cassandra and Elasticsearch (tech-preview)
- updates to use JanusGraph as the graph store, which replaces use of
Titan in earlier releases
- significant updates in Atlas Web UI
- release 0.8.3 is likely to be around end of July-2018
- will start work on supporting Hadoop 3, HBase 2, Solr 7
## Health report:
- 7 new contributors added in last 3 months: Abhishek Kadam, Barbara Eckman,
Bogdan Sava, Constantin Nastase, Jing Zhou, Nagaraj Janardhana, Vineeth
Seth
## 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 on 07/31/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 growth from new contributors and user
activity over the last quarter. We have successfully released our latest version
of Apache Aurora during this time: a regular planned release of Apache Aurora
0.20.0. The community has also started discussions on moving our source
repository over to leveraging the Apache Infrastructure Gitbox setup to enable
an easier development lifecycle and to help with automated and faster feedback
for patch contributions.
Community
---
Latest Additions:
* Jordan Ly was added to the PMC on Wed May 02 2018
* Santhosh Kumar Shanmugham was added to the PMC on Wed May 02 2018
Issue backlog status since last report:
* Created: 10 in the last 3 months
* Resolved: 8 in the last 3 months
Mailing list activity since last report:
* @dev 108 messages
* @user 20 messages
* @reviews 397 messages
Releases
---
Last release:
* Apache Aurora 0.20.0 released 4.2.2018
-----------------------------------------
Attachment F: Report from the Apache Axis Project [Robert Lazarski]
# Apache Axis2 Board Report, June 2018
## Description
The Apache Axis project is responsible for the creation and maintenance of
software related to the Axis Web Services frameworks and subsidiary components
(both Java and C).
## Issues
There are no issues requiring board attention at this time.
## Activity
- Axis2 Java 1.7.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 various new
users/contributors.
As the IT industry moves in droves from SOAP to JSON, Axis2 Java and my day
job are no exception and while Axis2 has an excellent REST / GSON module its
lacking docs and examples so its not used much. This next quarter the Axis2
teams expects to discuss bugfixes, docs and future direction to this module.
Another trend is Spring Boot and some projects like Log4j2 I notice has
starter kits. This next quarter we will be looking at what a starter kit for
our project would look like.
Axis 1.x has not been released since 2006 however one committer, Andreas
Veithen, has been very active in that repo for several years. No decision has
been made on a release schedule however several open threads are currently in
progress concerning what a release may look like at this point.
Axis2 C added a new committer this past December 2017, and so far that is
helping the project pick up speed. Indications are that a 1.7 release could
happen by the end of the year.
## 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 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
- 11 JIRA tickets created in the last 90 days.
- 6 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, while it is working
to catch up on Spark releases, few members are also working on porting the
data source implementations to the new data source API that was released with
Spark 2.3.
There is also a conversation on new extensions being donated to the project,
but that has a dependency on Spark 2.3.
Activities around Flink extensions at the moment are very low.
Issues:
* No known issues
Releases:
06/04/2018 - Bahir for Spark 2.1.2
08/22/2017 - Bahir for Spark2.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 9 PMC / 37 committers)
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:
There are no issues that require the Board's attention at this time.
## Activity:
Apache Beam is now in its second year as a top-level project, and just
celebrated one-year anniversary of its first stable release.
Major technical efforts going on include:
- Building a portable Flink runner, which adds support for Python and Go
SDKs.
- Beam SQL.
- Infrastructure and automation.
Beam desires to serve as a glue in the ecosystem, interconnecting SDKs,
engines and storage/messaging systems. On the execution side, Apache Samza
runner has seen increased activity, while other prototype runners are mostly
dormant on feature branches. On the IO connector side, the healthy growth
continues, with new connectors being contributed or improved month-over-month.
IP clearances have been completed for:
- Euphoria API.
- Go SDK.
Recent community decisions include:
- Publishing guidelines for becoming (and behaving as) a Beam committer.
- Releasing Go SDK.
- Automation of stale pull requests.
No blog posts have been published this quarter. Beam was featured at several
conferences, including Flink Forward San Francisco, and DataWorks Summit
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 community continues to grow steadily, as follows:
- Lifetime unique contributors grew to 269, with 24 new first-time
contributors.
- Increased subscriptions and activity on the mailing list and in JIRA.
- Contribution of new components into the project by external entities.
The amount of open discussion and design on the mailing list is at a new high,
benefited by arrival of new contributors and increased openness by existing
contributors.
## PMC changes:
Currently 19 PMC members. One PMC member has been added since the last report:
- Thomas Weise was added to the PMC on Fri Jun 08 2018.
## Committer base changes:
Currently 37 committers. Six new committers have been added since the last
report. New committers:
- Jason Kuster was added as a committer on Fri Apr 27 2018.
- Pablo Estrada was added as a committer on Fri Apr 27 2018.
- Gris Cuevas was added as a committer on Thu May 03 2018.
- Charles Chen was added as a committer on Fri Jun 08 2018.
- Henning Rohde was added as a committer on Fri Jun 08 2018.
- Alexey Romanenko was added as a committer on Tue Jun 12 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 general plan is to invite quite a
few new committers over the next period of time, but not too quickly to
jeopardize the community, or negatively affect where the project business is
handled.
Other recent actions include:
- Revision of new contributor materials to be more welcoming.
- Publishing the (subjective) guidelines for becoming a committer.
- Adding an explicit "Community" section to the web site, highlighting
ongoing projects to join.
PMC member Kenneth Knowles deserves (a rare) mention by name for proactively
reaching out to a large number of contributors, offering encouragement and
individual coaching to those interested. This effort meaningfully moved the
needle forward.
## Releases:
Since the last report, Apache Beam has published one release, with one more
currently in progress:
- 2.4.0 was released on Mon Mar 19 2018.
- 2.5.0 is currently under preparation and voting.
Version 2.0.0 was the first release that comes with API stability guarantees.
Going forward, we expect to publish a release every 6 weeks. We have been
short of our declared goal recently; however, the community is tackling this
issue.
## Mailing list activity:
Mailing list subscriptions and activity continues to increase modestly. The
number of emails on the development mailing list is up ~47%, and the number of
threads is up ~45%. We continue to see an increase in frequency and depth of
mailing list discussions, as well as better participation and diversity of
opinion compared to last year.
- dev@beam.apache.org
- 519 subscribers (up 15 in the last 3 months).
- 2127 emails sent to list (1393 in previous quarter).
- user@beam.apache.org
- 548 subscribers (up 15 in the last 3 months).
- 389 emails sent to list (456 in previous quarter).
## JIRA activity:
For the second quarter in a row, the JIRA activity is increasing, turning over
the earlier trend.
- 705 JIRA tickets created in the last 3 months (507 in the previous quarter).
- 368 JIRA tickets closed/resolved in the last 3 months (324 in the previous
quarter).
-----------------------------------------
Attachment I: Report from the Apache Bigtop Project [Peter Linnell]
-----------------------------------------
Attachment J: Report from the Apache Bloodhound Project [Gary Martin]
Project Description
===================
Apache Bloodhound is a software development collaboration tool, including
issue tracking, wiki and repository browsing
Issues
======
As for previous reports, activity remains on the low side. Some progress
has been achieved with experimentation with a new core model.
See further information below.
Releases
========
There have been no releases over the last three months. The last release
was towards the end of 2014:
* apache-bloodhound-0.8 (11th December 2014)
PMC/Committer Changes
=====================
There are currently 14 PMC members on the project. The last changes were
in April 2017.
The last new committers were added in May 2014.
The last addition to the PMC was in January 2017 (dammina)
Ryan Ollos resigned from the PMC in April 2017.
Community & Development
=======================
With the previous report mainly able to focus on infrastructure issues,
such as restoration of issue tracking for the project through migration
of the main Apache Bloodhound instance to new hardware, this quarter
we have considered moving the development of new sub projects in git
instead of Apache Subversion and experimenting with Django as a means
to replace Trac as the base for the project.
The idea of moving to git appeared to have backing from the community.
While the community generally avoided spelling out their reasons for
wanting to move, it may be that the move will benefit the project from
more people being used to using git than Subversion. Progress to make
this decision final has not yet been sought but discussion of this may
be expected in the next report. Certainly the PMC is not treating this
as something to rush as it does not actively block progress.
The new bloodhound core experiment has begun with a new branch of the
subversion repository dedicated to looking at making the core database
model with Django tooling. The current state of this is still fairly
basic but flexible. With decisions to be made about the direction to
take from this point, opinions have been sought by the chair to attempt
to encourage more engagement from those that have expressed interest
in the project.
Despite perhaps a disappointing amount of progress, the project Chair
suggests on behalf of the PMC that there is a continued wish to defer
the proposal to move Apache Bloodhound to the Attic for another three
months.
-----------------------------------------
Attachment K: Report from the Apache BVal Project [Matthew Jason Benson]
## Apache BVal Report June 2018 ##
- The Apache BVal project implements the Java EE Bean Validation
specification(s) and related extensions, and became a top-level project of
the foundation on February 15, 2012.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- The (new) Apache BVal 2.0 codebase now passes the Java Bean Validation 2.0
TCK.
- Apache BVal 2.0 has a dependency on the Apache Commons Weaver component and
is awaiting a release compatible with Java 8.
- In the past week we have received a report of a security issue which a member
of the community has begun to triage.
## 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:
- 2 JIRA tickets created in the last 3 months
- 2 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 release Apache Camel 2.22.0 expected for
the end of June: we are working on the last touches to be prepared for
release.
- 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.
## Health report:
- The project is super healthy, active and stays at a high level
## PMC changes:
- Currently 31 PMC members.
- Onder Sezgin is the last new PMC Member added since the last report
- Last PMC was added on Sun Apr 29 2018
## Committer base changes:
- Currently 63 committers.
- 1 additions since the last report
- Dmitry Volodin was added as a committer on Sat May 19 2018
## Releases:
- 2.20.3 was released on Fri Mar 30 2018
- 2.21.0 was released on Thu Mar 15 2018
- 2.21.1 was released on Fri May 04 2018
## Mailing list activity:
- users@camel.apache.org:
- 995 subscribers (up 12 in the last 3 months)
- 290 emails sent to list (403 in previous quarter)
- dev@camel.apache.org:
- 357 subscribers (down -1 in the last 3 months)
- 508 emails sent to list (388 in previous quarter)
- issues@camel.apache.org:
- 86 subscribers (up 1 in the last 3 months):
- 2226 emails sent to list (2172 in previous quarter)
- notifications@camel.apache.org:
- 8 subscribers (up 0 in the last 3 months)
## JIRA activity:
- 248 JIRA tickets created in the last 3 months
- 237 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment M: Report from the Apache Cayenne Project [Michael Ray Gentry]
# Apache Cayenne Board Report, June 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 first Release Candidate of Cayenne 4.0 occurred this quarter moving
us closer to the final "GA" release.
- Cayenne 3.1.2 (stable)
- Maintenance only. Cayenne 3.1.2 is the current stable product
line.
- Cayenne 4.0 (development)
- The API is frozen, barring any major issues, and development
efforts are only for bug fixes and documentation leading up to
the final release of Cayenne 4.0.
- Cayenne 4.1 (development)
- Work continues on Cayenne 4.1 even as 4.0 is being finalized.
## Health Report
Cayenne is healthy. Development activity is stable and and we have a
stable user and developer community.
## PMC Changes
- Currently 9 PMC members.
- No new PMC members added in the last 3 months.
- Last PMC addition was Nikita Timofeev on Sun Jun 25 2017.
## Committer Base Changes
- Currently 22 committers.
- No new committers added in the last 3 months.
- Last committer addition was Hugi Thordarson at Mon Jun 19 2017.
## Releases
- Cayenne 3.1.2 on Wed Nov 22 2017.
- Cayenne 4.0.RC1 on Sat Apr 26 2018.
- Cayenne 4.1.M1 on Sat Oct 14 2017.
## JIRA Activity
- 27 JIRA tickets created in the last 3 months.
- 32 JIRA tickets closed/resolved in the last 3 months.
-----------------------------------------
Attachment N: Report from the Apache Chemistry Project [Florian Müller]
## Description:
Apache Chemistry is an effort to provide an implementation of the
CMIS
(Content Management Interoperability Services) specification in
Java,
Python, PHP, .NET, Objective-C, and JavaScript (and possibly other
languages).
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- There was basically no activity in the last three months.
## Health report:
- We have a mature code base. No major development is expected.
## PMC changes:
- Currently 36 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Laurent Mignon on Sat Sep 23 2017
## Committer base changes:
- Currently 38 committers.
- No new committers added in the last 3 months
- Last committer addition was Laurent Mignon at Wed Sep 20 2017
## Releases:
- Last release was cmislib 0.6.0 on Thu Aug 31 2017
this
section.
- dev@chemistry.apache.org:
- 168 subscribers (down -3 in the last 3 months):
- 39 emails sent to list (57 in previous quarter)
## JIRA activity:
- 5 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.
## Activity:
- One new release (4.9.3.1) since the previous report.
## Health report:
- Version 4.12.0 is in development.
- Version 4.11.1 is in the RC process.
- 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 (up by one since the last report)
- Most recently added committer was Dag Sonstebo on Mon Mar 19 2018
## Releases:
- Release 4.11.0 on Mon Feb 12 2018
- Release 4.10.0 on Fri Sep 1 2017
- Release 4.9.3.1 on Fri Mar 29 2018
- Release 4.9.3.0 on Tue Sep 12 2017 member added. I think I was getting
conflicting information from different sources.
-----------------------------------------
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 medium with the release of 4 components and 4 internal
components.
## Health report:
- The project is moderately healthy but suffers from a lack of committer and
PMC growth.
- Releases for existing components are in the planning stage for Collections,
Lang, IO, Pool, DBCP, RNG, Numbers, and Weaver (for Apache BVal 2.0.)
- 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:
- BUILDPLUGIN-1.8 was released on Wed Apr 04 2018
- COMPRESS-1.17 was released on Sat Jun 02 2018
- DBCP-2.3.0 was released on Fri May 11 2018
- PARENT-45 was released on Wed Mar 14 2018
- PARENT-46 was released on Sun Apr 15 2018
- RELEASEPLUGIN-1.2 was released on Wed Apr 04 2018
- TEXT-1.3 was released on Tue Mar 20 2018
- TEXT-1.4 was released on Mon Jun 11 2018
## JIRA activity:
- 170 JIRA tickets created in the last 3 months
- 133 JIRA tickets closed/resolved in the last 3 months
## Odds and ends:
- Incomplete stats from https://demo.kibble.apache.org:
- 1,570 Commits this period
- 72 Authors this period
- 204,475 Lines changed this period
- 40 Committers this 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 no platform releases this quarter. Regarding tools releases - we had
one for cordova-common and cordova-serve, mainly to fix small bugs and update
dependencies. We had also one plugins release, where we released new versions
for 10 plugins - which contained bug fixes.
With the deprecation of Node.js 4 support by the Node Foundation (see our
[blog
post](https://cordova.apache.org/news/2016/10/01/0.x-4.x-deprecation-timeline.html))
we are proceeding with removing Node 4 support in all our tools and
platforms, which will bump up all versions by a major version. This will
bring ES6 and ES7 support into Cordova.
## Health report:
Our status dashboard at http://status.cordova.io is mostly all green.
We still have a backlog of GitHub Pull Request activity, again, same as last
quarter. We have started migrating from JIRA to Github Issues (starting with
cordova-docs) to perhaps take advantage of some automation available through
Github apps.
## PMC changes:
- Currently 91 PMC members.
- New PMC members:
- Gandhi Rajan was added to the PMC on Sat Apr 28 2018
- Raphael von der Grün was added to the PMC on Tue May 29 2018
## Committer base changes:
- Currently 94 committers.
- New commmitters:
- Gandhi Rajan was added as a committer on Thu Apr 26 2018
- Raphael von der Grün was added as a committer on Tue May 29 2018
## Releases:
- cordova-common@2.2.3 was released on Mon Jun 04 2018
- cordova-plugin-battery-status@2.0.2 was released on Tue Apr 17 2018
- cordova-plugin-camera@4.0.3 was released on Tue Apr 17 2018
- cordova-plugin-device-motion@2.0.1 was released on Tue Apr 17 2018
- cordova-plugin-device-orientation@2.0.1 was released on Tue Apr 17 2018
- cordova-plugin-device@2.0.2 was released on Tue Apr 17 2018
- cordova-plugin-globalization@1.11.0 was released on Tue Apr 17 2018
- cordova-plugin-statusbar@2.4.2 was released on Tue Apr 17 2018
- cordova-plugin-vibration@3.1.0 was released on Tue Apr 17 2018
- cordova-plugin-inappbrowser@3.0.0 was released on Tue Apr 17 2018
- cordova-plugin-media-capture@3.0.2 was released on Tue Apr 17 2018
- cordova-serve@2.0.1 was released on Fri Jun 08 2018
## JIRA activity:
- 156 JIRA tickets created in the last 3 months
- 188 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment R: Report from the Apache cTAKES Project [Pei Chen]
## Description:
Apache clinical Text Analysis and Knowledge Extraction System (cTAKES) is
an open-source natural language processing system for information extraction
from electronic medical record clinical free-text.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
- Committee continues to work on the future release (4.0.1)
- Committee continues to 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 30 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Michelle Chen on Mon Feb 02 2015
## Committer base changes:
- Currently 38 committers.
- New commmitters:
- Alex Zbarcea was added as a committer on Fri Oct 20 2017
- Gandhi Rajan was added as a committer on Tue Nov 14 2017
- Matthew Vita was added as a committer on Mon Nov 13 2017
## Releases:
- Last release was 4.0.0 on Apr 27 2017
- 3.2.2 was released on May 30 2015
- 3.2.1 was released on Dec 10 2014
## Mailing list activity:
There was an increase in number of subscribers to the dev and user @
mailing lists.
- dev@ctakes.apache.org:
- 251 subscribers (up 8 in the last 3 months)
- 148 emails sent in the past 3 months (183 in the previous quarter)
- user@ctakes.apache.org:
- 253 subscribers (up 12 in the last 3 months)
- 82 emails sent in the past 3 months (111 in the 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:
- Both Curator and ZooKeeper (Curator is a ZooKeeper client) are slowing into
a mature maintenance mode. Given this, Curator is healthy.
## 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:
- 51 subscribers (up 0 in the last 3 months):
- 204 emails sent to list (245 in previous quarter)
- user@curator.apache.org:
- 158 subscribers (down -1 in the last 3 months):
- 23 emails sent to list (13 in previous quarter)
## JIRA activity:
- 9 JIRA tickets created in the last 3 months
- 4 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment T: Report from the Apache DeltaSpike Project [Mark Struberg]
## Description:
Apache DeltaSpike is a suite of portable CDI (Contexts & Dependency
Injection) extensions intended to make application development easier when
working with CDI and Java EE. Some of its key features include:
- A core runtime that supports component configuration, type safe messaging
and internationalization, and exception handling.
- A suite of utilities to make programmatic bean lookup easier.
- A plugin for Java SE to bootstrap both JBoss Weld and Apache OpenWebBeans
outside of a container.
- JSF integration, including backporting of JSF 2.2 features for Java EE 6.
- JPA integration and transaction support.
- A Data module, to create an easy to use repository pattern on top of JPA.
- Quartz integration
Testing support is also provided, to allow you to do low level unit testing of
your CDI enabled projects.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
Activity is fine. We had quite some discussions in the Config
area. They derived from discussions at the ConfigJSR (JSR-382)
which took over the core design of DeltaSpike. We had 1 person
taking part in the discussion over there whereas in DeltaSpike
I really got a hand full of people giving feedback. So we ended
up implementing the feature in DeltaSpike first and then porting
it back to ConfigJSR (as it's also ALv2). This will be in the
upcoming 1.9.0 release.
## Health report:
Health is ok. The project is already very stable and probably
had it's peak. A BUNCH of features we have in DeltaSpike since
almost forever have now been directly made part of the respective
JSRs. E.g. CDI.current(), JSF CDI support etc.
We still add a lot of additional value and we allow to make the same
code run on JavaEE6 to EE8++! This is something big companies love.
## PMC changes:
- Currently 19 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Harald Wellmann on Thu May 19 2016
## Committer base changes:
- Currently 33 committers.
- No new committers added in the last 3 months
- Last committer addition was Matej Novotny at Fri Jun 03 2016
## Releases:
- 1.8.2 was released on Tue May 22 2018
## Mailing list activity:
- users@deltaspike.apache.org:
- 176 subscribers (down -8 in the last 3 months):
- 122 emails sent to list (84 in previous quarter)
- dev@deltaspike.apache.org:
- 99 subscribers (down -2 in the last 3 months):
- 251 emails sent to list (202 in previous quarter)
## JIRA activity:
- 19 JIRA tickets created in the last 3 months
- 19 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment U: Report from the Apache Eagle Project [Edward Zhang]
## Description:
- Apache Eagle is an open source analytics solution for identifying security
and performance issues instantly on big data platforms.
## Issues:
- There are no issues requiring board attention at this time
## Activity:
- In last quarter, community merged some pending PRs and now it is
0.5.1-SNAPSHOT. Community also asked release of 0.5.1 which mostly contains
bug fixes but no significant features, will plan to release it in this
quarter. Also some bugs were reported from community.
## Health report:
- Project health is ok, community continued to use Eagle and reported
bugs/issues. Bug fix and question answer is voluntary, so the speed of
solving issues needs to be improved.
## 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:
- 79 subscribers (up 1 in the last 3 months):
- 12 emails sent to list (70 in previous quarter)
- issues@eagle.apache.org:
- 20 subscribers (up 1 in the last 3 months):
- 31 emails sent to list (203 in previous quarter)
- user@eagle.apache.org:
- 58 subscribers (up 2 in the last 3 months):
- 3 emails sent to list (22 in previous quarter)
## JIRA activity:
- 4 JIRA tickets created in the last 3 months
- 1 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment V: Report from the Apache Falcon Project [Pallavi Rao]
## Description:
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 the 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.
Roadmap for the next release is yet to be charted out.
## 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 (down -3 in the last 3 months):
- 75 emails sent to list (154 in previous quarter)
- user@falcon.apache.org:
- 30 subscribers (down -1 in the last 3 months):
- 3 emails sent to list (2 in previous quarter)
## JIRA activity:
- 8 JIRA tickets created in the last 3 months
- 4 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment W: Report from the Apache 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.
- Accepted and finished IP clearance of two contributions namely, a "System
readiness framework" by Andrei Dulvac and Christian Schneider and a
"Logback integration with OSGi Log 1.4" by Raymond Augé.
- Released most of the OSGi R7 specification related components.
- Framework is now OSGi R7 compliant (release pending)
- Released 15 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.
- We managed to attract some new committers and added some new PMC members.
Regardless, attracting new committers needs to still be a focus.
- We had no issues voting on releases and JIRA issues are generally addressed
promptly.
## PMC changes:
- Currently 26 PMC members.
- New PMC members:
- Raymond Augé was added to the PMC on Thu May 03 2018
- Tom Watson was added to the PMC on Thu May 03 2018
## Committer base changes:
- Currently 63 committers.
- New commmitters:
- Christian Schneider was added as a committer on Thu May 03 2018
- Andrei Dulvac was added as a committer on Thu May 03 2018
## Releases:
- Apache Felix Gogo Runtime / JLine 1.0.12 was released on Thu Apr 12 2018
- org.apache.felix.configadmin-1.9.2 was released on Mon Apr 30 2018
- org.apache.felix.configurator-1.0.0 was released on Mon Apr 30 2018
- org.apache.felix.connect-0.2.0 was released on Mon May 28 2018
- org.apache.felix.converter-1.0.2 was released on Thu Apr 26 2018
- org.apache.felix.eventadmin-1.5.0 was released on Mon May 07 2018
- org.apache.felix.http.base-4.0.0 was released on Mon Apr 30 2018
- org.apache.felix.http.bridge-4.0.0 was released on Mon Apr 30 2018
- org.apache.felix.http.jetty-4.0.0 was released on Mon Apr 30 2018
- org.apache.felix.http.whiteboard-4.0.0 was released on Mon Apr 30 2018
- org.apache.felix.metatype-1.2.0 was released on Mon May 07 2018
- org.apache.felix.resolver-1.16.0 was released on Tue Mar 13 2018
- org.apache.felix.scr-2.1.0 was released on Mon Apr 30 2018
- org.apache.felix.utils-1.11.0 was released on Sat May 05 2018
## Mailing list activity:
- users@felix.apache.org:
- 566 subscribers (down -1 in the last 3 months):
- 68 emails sent to list (50 in previous quarter)
- dev@felix.apache.org:
- 327 subscribers (down -2 in the last 3 months):
- 626 emails sent to list (319 in previous quarter)
## JIRA activity:
- 60 JIRA tickets created in the last 3 months
- 60 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment X: 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.1 was released on 2018-04-18 - this was an
update to match the latest Flash Player SDK.
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
Dev@ has seen a recent uptick in emails, and user@ has also seen a sharp
increase in posts. These seem to be driven largely by installer-related
issues.
Last PMC addition: Mon Aug 28 2017 (Olaf Krüger)
Last committer addition: Wed Sep 07 2016 (Greg Dove)
COMMUNITY
The Apache Flex community feels like a calmer and more stable place, with
conversations driven directly by features or bug reports rather than
discussions over process. This suggests we're doing the right thing compared
to a year ago.
TRADEMARKS
Nothing noted.
SECURITY
Nothing to report.
-----------------------------------------
Attachment Y: 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.5 release, with major changes to the
deployment model, network stack, recovery, and more.
- Community has invested a lot of time into automating release testing, to
be able to switch to a more strict time-based release model.
- Work towards the next version (1.6) has started, a discussion about parts of
the feature set is still ongoing on the mailing lists.
- The Flink Forward San Francisco conference took place in April,
with a mix of committers, contributors, users, and explorers.
The call for presentations for the next Flink Forward conference
in Berlin (September 3rd-5th) is open.
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:
- Nico Kruber was added as a committer on May 10th, 2018
- Xingcan Cui was added as a committer on May 10th, 2018
- Shuyi Chen was added as a committer on June 5th, 2018
Flink currently has 38 committers and 19 PMC members.
RELEASES
The following releases were made since the last board report:
- 1.5.0 was released on May 25th, 2018
- shaded-4.0 (auxiliary project) was released on June 6th, 2018
ACTIVITY ON JIRA / MAILING LISTS
The Flink community is proud to continues to be in the top 10
active mailing lists in Apache:
- user@f.a.o (1847 mails/quarter)
- dev@f.a.o (1285 mails/quarter)
JIRA continues to be active as well, 653 JIRA tickets created, 589 JIRA
tickets resolved in the last 3 months .
-----------------------------------------
Attachment Z: Report from the Apache Forrest Project [David Crossley]
Apache Forrest mission is software for generation of aggregated multi-channel
documentation maintaining a separation of content and presentation.
Issues needing board attention:
None.
Changes in the PMC membership:
None.
Last modified: 2013-04-08
Most recent addition: 2009-06-09
New committers:
None.
Most recent addition: 2009-06-09
None on the horizon.
General status:
The most recent release is 0.9 on 2011-02-07.
I needed to miss the normal May reporting period. So this report covers the
previous four months.
No activity on the user mail list. However it never gets used much anyway.
Some minor activity on the dev list, early in the quarter.
For the last month, Gump has been trying to be helpful by telling about
a problem with one of our various Gump runs. No one has found the time to
do extended investigation.
Four PMC members were present during the quarter. This was mainly initial
discussion of a draft new logo, that was proposed to the private list.
People were involved and encouraging. However there was no follow-up.
For this last month there was no presence indicated by any PMC member.
At this report, three other PMC members responded to my draft report.
This confirms that there are sufficient people hanging around for us to
potentially be able to make a decision or encourage new contributors.
Project status:
Activity: Idle
3+ people have indicated presence, so has the potential for sufficient
oversight.
There was no discussion following board feedback at the previous report,
which again wondered why no recent release, and how does the community
benefit from any development of the past seven years.
It does take effort to release Forrest. It is well-documented, and there
have been past suggestions for making it a bit easier. As stated before,
i hope to assist, but am not in a position to initiate or drive it.
The project has been in a treading-water state for a long time, as notified
in previous reports.
My impression is that it is a dedicated group, that does not (in general)
actively use or develop the project, but are still attached. However these
days no-one has the energy to further the project.
The project should probably again consider moving to the Attic, given the
lack of attention to Gump and the state of no discussion about the board
feedback.
The abovementioned, was the state of things. Then in response to this
draft report a non-PMC member said that they are intending to address
the release and Gump.
So it seems that we should continue to tread water for a while longer.
Security issues published:
None.
Progress of the project:
Apache Gump asked various projects if they were still interested. One of
our committers replied that we are. Gump is still useful for us. Thanks.
-----------------------------------------
Attachment AA: Report from the Apache FreeMarker Project [Dániel Dékány]
## Description:
Apache FreeMarker is a template engine, i.e. a generic tool to generate text
output based on templates. Apache FreeMarker is implemented in Java as a class
library for programmers.
FreeMarker 2 (the current stable line) produces releases since 2002. The
FreeMarker project has joined the ASF in 2015, and graduated from the
Incubator in early 2018.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
Activity was low this month. There was some site updates regarding EU
regulations, and transition from http://try.freemarker.org to
https://try.freemarker.apache.org is almost done.
## Health report:
Activity is relatively low but steady, as it's usual for this project. User
question (mostly on StackOverflow) and new Jira issues are being answered
promptly.
The long term goal is continuing the ongoing development on the 3.0 branch, so
that the project can innovate and the code base can become much cleaner (and
more attractive for new committers), instead of being blocked by 15 years of
historical baggage. (Meanwhile, the backward compatible 2.x branch must be
maintained, and produce releases.)
## PMC changes:
- Currently 7 PMC members.
- No changes since the graduation on 2018-03-21
## Committer base changes:
- Currently 7 committers.
- No changes since the graduation on 2018-03-21
## Releases:
- 2.3.28 was released on Wed Apr 04 2018
## Mailing list activity:
- dev@freemarker.apache.org:
- 63 subscribers (up 2 in the last 3 months):
- 190 emails sent to list (152 in previous quarter)
- notifications@freemarker.apache.org:
- 16 subscribers (up 1 in the last 3 months):
- 605 emails sent to list (235 in previous quarter)
## JIRA activity:
- 6 JIRA tickets created in the last 3 months
- 5 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AB: Report from the Apache Guacamole Project [Mike Jumper]
## Description:
- Apache Guacamole is a clientless remote desktop gateway which supports
standard protocols like VNC, RDP, and SSH. We call it "clientless" because
no plugins or client software are required. Once Guacamole is installed on
a server, all you need to access your desktops is a web browser.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- Several recent contributions related to improving the functionality of
Guacamole's terminal emulator.
- A contributor has accepted an invitation for committership. We are
currently awaiting their CLA.
- The scope of the 1.0.0 release has been finalized, and the release process
has begun.
## Health report:
- The project is still operating in a healthy manner. No significant changes
in the last quarter. Development and community involvement continue to be
active.
## PMC changes:
- Currently 9 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Carl Harris on Sun Nov 19 2017
## Committer base changes:
- Currently 10 committers.
- No new committers added in the last 3 months
- Last committer addition was Carl Harris at Thu Nov 16 2017
## Releases:
- Last release was 0.9.14 on Wed Jan 17 2018
## Mailing list activity:
- dev@guacamole.apache.org:
- 77 subscribers (up 7 in the last 3 months):
- 647 emails sent to list (650 in previous quarter)
- user@guacamole.apache.org:
- 299 subscribers (up 15 in the last 3 months):
- 543 emails sent to list (613 in previous quarter)
## JIRA activity:
- 45 JIRA tickets created in the last 3 months
- 39 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AC: Report from the Apache Gump Project [Stefan Bodewig]
Apache Gump is a cross-project continuous integration server. Gump's
intention isn't so much to be a CI server but rather a vehicle that
makes people look beyond their project's boundaries and helps the
projects to collaborate.
Gump is written in Python and supports several build tools and version
control systems. The Apache installation of Gump builds ASF as well
as non-ASF projects and their dependencies. It started in the Java
part of the foundation but also builds projects like APR, HTTPd and
XMLUnit.NET.
== Summary ==
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 AD: Report from the Apache Hama Project [Chia-Hung Lin]
## Description:
- Apache Hama is a framework for Big Data analytics based on the Bulk
Synchronous Parallel paradigm
## Issues:
- There are no issues requiring board attention at this time
## Activity:
- A branching for further componentization core module is underway, preparing
for 0.8.0 release.
## Health report:
- One new committer joined the community.
## PMC changes:
- Currently 10 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Behroz Sikander on Mon Feb 01 2016
## Committer base changes:
- Currently 18 committers.
- New committer:
- YoungWoo Kim was added as a committer on Sun May 20 2018
## Releases:
- Last release was hama-0.7.1 on Sun Mar 13 2016
-----------------------------------------
Attachment AE: Report from the Apache Helix Project [Kishore G]
-----------------------------------------
Attachment AF: Report from the Apache Hive Project [Ashutosh Chauhan]
-----------------------------------------
Attachment AG: Report from the Apache Incubator Project [Justin Mclean]
= Incubator PMC report for June 2018 =
=== Timeline ===
||Wed June 06 ||Podling reports due by end of day ||
||Sun June 10 ||Shepherd reviews due by end of day ||
||Sun June 10 ||Summary due by end of day ||
||Tue June 12 ||Mentor signoff due by end of day ||
||Wed June 13 ||Report submitted to Board ||
||Wed June 20 ||Board meeting ||
=== Shepherd Assignments ===
||Dave Fisher ||Myriad ||
||Dave Fisher ||Nemo ||
||Drew Farris ||Druid ||
||Drew Farris ||Superset ||
||John Ament ||S2Graph ||
||John Ament ||SINGA ||
||Justin Mclean ||Gearpump ||
||P. Taylor Goetz ||Dubbo ||
||P. Taylor Goetz ||Quickstep ||
||P. Taylor Goetz ||Tephra ||
||Timothy Chen ||AriaTosca ||
||Timothy Chen ||Daffodil ||
||Timothy Chen ||Taverna ||
||[none] ||Crail ||
||[none] ||Gossip ||
||[none] ||Griffin ||
||[none] ||Hivemall ||
||[none] ||Omid ||
||[none] ||OpenWhisk ||
||[none] ||Pony Mail ||
||[none] ||Pulsar ||
||[none] ||SAMOA ||
||[none] ||SkyWalking ||
||[none] ||Spot ||
=== Report content ===
{{{
Incubator PMC report for June 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 May,
podlings executed 7 distinct releases and there are several ongoing votes
and releases for June. We added one new IPMC member. No podlings are
graduating this month, but many are heading towards graduation. We had one
project, Apache Slider, require to the attic. There were 5 IP clearances.
* Community
New IPMC members:
- Sharan Foga
People who left the IPMC:
- None
* New Podlings
- None, but there are several threads on possible new podlings.
* Podlings that failed to report, expected next month. All three project
have failed to report before.
- Druid - Activity on list and reminders sent but no report. May need
more active mentors. Will also follow up on non ASF releases.
- Pony Mail - No report and almost no activity on list. Will check if
there's still active mentors.
- Spot - No report and almost no activity on list. Communication may be
happening elsewhere.
* Graduations
The board has motions for the following:
- None
* Releases
The following releases entered distribution during the month of March:
- 2018-05-15 Apache Daffodil 2.1.0
- 2018-05-16 Apache Griffin 0.2.0
- 2018-05-22 Apache MXNet 1.2.0
- 2018-05-23 Apache Skywalking 5.0.0 beta
- 2018-05-27 Apache Pulsar 2.0.0
- 2018-05-29 Apache Netbeans 9.0
- 2018-05-31 Apache Crail 1.0
Vote passed but missing from release area:
- 2018-05-29 Apache Omid 0.9.0
- 2018-05-26 Apache Tephra 0.14.0
* IP Clearance
- Apache Beam Go SDK
- Dubbox documentation
- Arrow Ruby Library
- System Readiness Check Framework
- Logback integration with OSGi Log 1.4
* Legal / Trademarks
- None
* Infrastructure
- None
* Miscellaneous
- None
----------------------------------------------------------------------
Table of Contents
AriaTosca
Crail
Daffodil
Dubbo
Gearpump
Gossip
Griffin
Hivemall
Myriad
Nemo
Omid
OpenWhisk
Pulsar
Quickstep
S2Graph
SAMOA
SINGA
SkyWalking
Superset
Taverna
Tephra
----------------------------------------------------------------------
--------------------
AriaTosca
ARIA TOSCA project offers an easily consumable Software Development Kit(SDK)
and a Command Line Interface(CLI) to implement TOSCA(Topology and
Orchestration Specification of Cloud Applications) based solutions.
AriaTosca has been incubating since 2016-08-27.
Three most important issues to address in the move towards graduation:
1. All development activity has ceased.
2. Discussions underway to decide on the future course of the podling.
3.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
How has the community developed since the last report?
Discussions in progress about the future course of the project.
How has the project developed since the last report?
All development activity on the project has ceased, all present
committers have moved on to pursue other interests.
How would you assess the podling's maturity?
Community Building
Please feel free to add your own commentary.
[ ] Initial setup
[ ] Working towards first release
[X] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
2018-01-16
When were the last committers or PPMC members elected?
Thomas Nadeau added in Feb 2018
Signed-off-by:
[X](ariatosca) Suneel Marthi
Comments:
[ ](ariatosca) John D. Ament
Comments:
[ ](ariatosca) Jakob Homan
Comments:
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: Additional contributors from different
companies/affiliations
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?
* To advertise the project, we present(ed) the Crail project at:
* OpenFabrics 2018 Workshop
(Crail non-volatile memory integration, presented in April)
* Spark and AI 2018 Summit
(Serverless computing with Crail, presented June 5)
* DataWorks 2018 Summit in June (Crail, to be presented June 21)
How has the project developed since the last report?
* First source code release (Apache-Crail 1.0-incubating) done
(+4, -0 binding votes) and available
* Designed/implemented new generic NVMeF storage tier which makes
code base independent of SPDK/DPDK environment
* 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:
Having made the (always difficult) first release, the project
is in good shape. They are starting to generate some publicity
by speaking at conferences. I am encouraging them to create a
twitter account (so that they can interact with the wider
community more frequently) and to start thinking of a second
release (to ensure that the release process is reproducible).
[x] (crail) Luciano Resende
Comments:
[] (crail) Raphael Bircher
Comments:
IPMC/Shepherd notes:
lresende: I removed the check from 'working towards first release' as the
first release was just completed
--------------------
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, previous legal issues regarding Open Grid Forum license were
clarified (LEGAL-369)
How has the community developed since the last report?
- Starting community building, including conversations on the user@ and
dev@ lists from a handful of outside users requesting some support and
information on Daffodil for DFDL schema creation.
- Mike Beckerle was accepted for a talk on Daffodil at ApacheCon
- Received two bug fix contributions from an outside user, who was able
to spin up and make contributions quickly
How has the project developed since the last report?
- Created our first release as an Apache incubator
- All website and wiki documentation is up to date
- Had 14 commits from 5 different developers over the past three months
- Still under active development, though upcoming features are large
and take time to implement
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-05-14
When were the last committers or PPMC members elected?
- None, same as project incubation
Signed-off-by:
[ ](daffodil) John D. Ament
Comments:
[X](daffodil) David Fisher
Comments: Project is making progress. Another Mentor would be helpful.
IPMC/Shepherd notes:
--------------------
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. First release
2. Community building
3. Change group id to org.apache
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
None.
How has the community developed since the last report?
* Complete All ICLA collection for all the contributors which are
necessary to have
* The first Apache release 2.6.2 has passed the incubator community vote
* zonghaishang(yiji) has been voted as new committer
* Ian Luo/Jun Liu's talk about
"Introducing Apache Dubbo(Incubating): What is Dubbo and How it Works"
has been accepted by ApacheCon NA.
* The first Dubbo meetup has been held in Beijing, with over 400+
people attended
* 10 new companies reported their using of Dubbo since last report
How has the project developed since the last report?
* 2.6.2 is ready to release
* The community has decided to a new major version 2.7.x to
incorporate incompatible changes.
* 57 Active Pull Requests, 49 pull request merged, with 21
contributors involved
* 180 Active Issues, 127 issues closed
* Github star 19286, fork 13491
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. (2.6.2 has passed incubator community release vote and is
expected to be released within several days)
When were the last committers or PPMC members elected?
2018-06-01
Signed-off-by:
[X](dubbo) Justin Mclean
Comments:
[ ](dubbo) Jean-Frederic Clere
Comments:
[X](dubbo) Mark Thomas
Comments: Good work on the first release.
dev@ list traffic is a lot easier to follow
now notifications have moved to a separate
list
I'm still struggling with the volume of
notifications. It is getting easier as I
become more familiar with the project but I do
worry that newcomers to the project will find
it difficult to follow.
IPMC/Shepherd notes:
--------------------
Gearpump
Gearpump is a reactive real-time streaming engine based on the
micro-service Actor model.
Gearpump has been incubating since 2016-03-08.
Most important issues to address in the move towards graduation:
1. Have frequent release cycles.
2. Continue to evolve community interest and support.
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 contributor added Apache Kudu integration to Gearpump.
How has the project developed since the last report?
- 13 issues created and 17 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:
2017-07-17
When were the last committers or PMC members elected?
No new committers or PMC members elected yet.
Signed-off-by:
[X](gearpump) Jean-Baptiste Onofré
Comments: low but "stable" activity, we definitely should try to speed
up the release cycle
[ ](gearpump) Andrew Purtell
Comments:
[ ](gearpump) Jarek Jarcec Cecho
Comments:
[ ](gearpump) Reynold Xin
Comments:
[ ](gearpump) Todd Lipcon
Comments:
[ ](gearpump) Xuefu Zhang
Comments:
IPMC/Shepherd notes:
--------------------
Gossip
Gossip is an implementation of the Gossip Protocol.
Gossip has been incubating since 2016-04-28.
Three most important issues to address in the move towards graduation:
1. Locating willing committers to handle code reviews
2. Achieving out third release
3. Integration into some downstream tools.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
How has the community developed since the last report?
Discussed status/availability with some of the initial committers. There
was some general interest, but no strong commitments to providing time for
reviews.
How has the project developed since the last report?
We took some time and reviewed community committed PRs. Those will be
merged over the next 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:
2017-03-02
When were the last committers or PPMC members elected?
Chandresh Pancholi added as a committer in February 2017
Signed-off-by:
[X](gossip) P. Taylor Goetz
Comments: Activity is very low. Retirement is likely on the horizon.
[ ](gossip) Josh Elser
Comments:
[ ](gossip) Drew Farris
Comments:
IPMC/Shepherd notes:
--------------------
Griffin
Griffin is an 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. Improve user guide documents.
2. Preparation for graduation.
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?
- 3 new committers have been elected.
- 14 new contributors contributed to our community.
- More users have contacted us for use cases.
How has the project developed since the last report?
- Active development is moving on well, 53 commits in last three months.
- Released new version 0.2.0-incubating.
- Support measure job scheduler for batch mode.
- Use PostgreSQL instead of MySQL by default.
- Upgrade default spark version from 1.6.x to 2.2.1 in measure module.
- Upgrade default hive version from 1.2.1 to 2.2.0 in measure module.
- Refactor measure module for clearer structure.
- Work toward for next version release.
How would you assess the podling's maturity?
[] Initial setup
[] Working towards first release
[] Community building - One new contributor
[X] Nearing graduation
[] Other:
Date of last release:
- May 16th, 2018
When were the last committers or PPMC members elected?
- 3 new committers were elected at Mar 30th, 2018
Signed-off-by:
[X](griffin) Henry Saputra
Comments:
[ ](griffin) Kasper Sørensen
Comments:
[ ](griffin) Uma Maheswara Rao Gangumalla
Comments:
[x](griffin) Luciano Resende
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 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:
145 stars as of June 5 (was 131 on April 3)
* Twitter account @ApacheHivemall followers are gradually increasing:
145 followers as of June 5 (was 123 on April 3)
How has the project developed since the last report?
* Preparing the second Apache release, v0.5.2. It will be release in
July, 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 2 months, we opened 21 JIRA issues and closed 10 JIRA
issues as seen in https://goo.gl/QFQEF5 (as of June 5)
Created Resolved
April 2018 17 10
May 2018 4 0
* Created 11 Pull Requests and merged 11 Pull Requests between Apr 01
and May 31.
https://github.com/apache/incubator-hivemall/pulls?q=is%3Apr%20created%3A201
8-04-01..2018-05-31
https://github.com/apache/incubator-hivemall/pulls?q=is%3Apr%20closed%3A2018
-04-01..2018-05-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:
[ ](hivemall) Xiangrui Meng
Comments:
[ ](hivemall) Daniel Dai
Comments:
IPMC/Shepherd notes:
--------------------
Myriad
Myriad enables co-existence of Apache Hadoop YARN and Apache Mesos together
on the same cluster and allows dynamic resource allocations across both Hadoop
and other applications running on the same physical data center
infrastructure.
Myriad has been incubating since 2015-03-01.
Three most important issues to address in the move towards graduation:
1. Grow the community and enroll new committers.
2. Have (more) frequent Release cycles to be compliant with the Apache
Way.Creating roadmaps for releases with goals (new features).
3. Social media presence (new blog entries, conference talks).
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
There are no new issues requiring board attention at this time.
How has the community developed since the last report?
1. Two new committers/PMC members from the last report (total 8
committers).
2. Increase activity in the dev mailing list.
3. Twitter account with 1018 followers and daily basis activity.
4. Community chat channel with 7 registered user (low activity).
How has the project developed since the last report?
1. Project rebooting roadmap on going with success: https://goo.gl/2gdcrP
2. Resolved JIRA Issues: 11
3. Pull Requests merged: 8
4. Strong local development environment for Apache Mesos and Mesosphere
DC/OS.
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: Project rebooting in progress, retirement risk not present
right now.
Date of last release:
The 0.2.0 release was issued on Jun 29, 2016. The .3 release is
planned for this quarter.
When were the last committers or PPMC members elected?
1. 2018-05-22 New committer/PMC member Juan P. Gilaberte.
2. 2018-03-28 New committer/PMC member Javi Roman.
Signed-off-by:
[ ](myriad) Benjamin Hindman
Comments:
[ ](myriad) Danese Cooper
Comments:
[X](myriad) Ted Dunning
Comments:
IPMC/Shepherd notes:
--------------------
Nemo
Nemo is a data processing system to flexibly control the runtime behaviors
of a job to adapt to varying deployment characteristics.
Nemo has been incubating since 2018-02-04.
Three most important issues to address in the move towards graduation:
1. Grow the community
2. Create a first Apache release
3. Donate code to ASF
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
None.
How has the community developed since the last report?
* Committers actively involved in mailing lists
* Committers actively started to send PRs and do code reviews
How has the project developed since the last report?
* Progress towards supporting Spark DSL programs
* Refactoring the Nemo runtime
* Finishing up a paper that describes the design and
implementation of Nemo
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[X] Initial setup
[X] Working towards first release
[ ] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
None yet.
When were the last committers or PPMC members elected?
None yet.
Signed-off-by:
[X](nemo) Davor Bonaci
Comments: Progress is probably a bit slower than before, but still
very high. Podling is doing great.
[ ](nemo) Hyunsik Choi
Comments:
[X](nemo) Byung-Gon Chun
Comments:
[ ](nemo) Jean-Baptiste Onofre
Comments:
[ ](nemo) Markus Weimer
Comments:
[ ](nemo) Reynold Xin
Comments:
IPMC/Shepherd notes:
Dave Fisher: AFAICT the SGA has not been provided and a mentor has
advised that this can wait until graduation.
I don't think that is correct and it is not the same as the guidance
given to other podlings like Heron.
See
https://lists.apache.org/thread.html/df7040d27bc8c01ec1601476b1e465226d4b1ea
99d0e5991b977fd1c@%3Cprivate.nemo.apache.org%3E
--------------------
Omid
Omid is a flexible, reliable, high performant and scalable ACID
transactional
framework that allows client applications to execute transactions on top of
MVCC key/value-based NoSQL datastores (currently Apache HBase) providing
Snapshot Isolation guarantees on the accessed data.
Omid has been incubating since 2016-03-28.
Three most important issues to address in the move towards graduation:
1. Boost project dissemination in the Apache community.
2. Collaborate/integrate Omid with other Apache projects.
3. Get positive feedback from other projects currently in Apache.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
N/A
How has the community developed since the last report?
Omid 0.9.0 released.
Continue integration with Apache Phoenix.
Pinterest exploring to use Omid in production.
How has the project developed since the last report?
Preparing 0.9.0 version. Solved issues related to legal stuff.
Quarter Stats (from: 2017-03-01 to: 2018-05-31):
+---------------------------------------------+
| Metric | counts |
+---------------------------------------------+
| # of msgs in dev list | 192 |
| Active Contributors (incl mentors)| 8 |
| Jira New Issues | 10 |
| Resolved Issues | 10 |
| Pull Requests merged | 12 |
| Pull Requests proposed | 14 |
+---------------------------------------------+
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-05-29
When were the last committers or PPMC members elected?
Signed-off-by:
[X](omid) Alan Gates
Comments:
[ ](omid) Lars Hofhansl
Comments:
[ ](omid) Flavio P. Junqueira
Comments:
[ ](omid) Thejas Nair
Comments:
[X](omid) James Taylor
Comments:
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:
* Produce our first source code release under Incubator (automation work
is now complete here https://github.com/apache/incubator-openwhisk-release).
We believe that the process to release will be initiated in the next 2
weeks.
* Increase contributions to ensure all project repos are maintained. and
address Issue / PR backlog.
* 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 #3 above). As of this report, the "open" issue backlog is
365 and open PR is 55. Need to prioritize and work to reduce while
advancing performance/security/deployment issues.
* Trying to add more active Committers to augment those who have dropped
off in their activity; 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.
* Formal hand-off of OpenWhisk trademark/logo from IBM needs to be
executed; need to identify process for this.
Discussion started w/ Apache legal via "legal-discuss" mailing list with
subject "Trademark handoff for "OpenWhisk" name and logo".
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 has been down with the exception of work
around the new Go language runtime (mostly April). It appears that 2Q
conferences may be partly to blame with corporate Committers being
preoccupied.
* incubator-openwhisk Github stars: 3218 (+341 since last report)
* incubator-openwhisk GitHub forks: 616 (+72 since last report)
* Slack community We're ~800 members and it is really active, from both
end users or the project and contributors
* 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
(https://www.youtube.com/channel/UCbzgShnQk8F43NKsvEYA1SA)
* CWiki Meeting Notes: OpenWhisk Technical Interchange Meeting Notes
* 2018-05-23 OW Tech Interchange - Meeting Notes
* 2018-05-09 OW Tech Interchange - Meeting Notes
* 2018-04-25 OW Tech Interchange - Meeting Notes
* 2018-04-11 OW Tech Interchange - Meeting Notes
* 2018-03-28 OW Tech Interchange - Meeting Notes
* 2018-03-14 OW Tech Interchange - Meeting Notes
New Contributors
* Moritz Raho: (Adobe) intern, focus on user/dev experience
* Nareej: (Adobe) started using OpenWhisk for internal notifications,
looking to become a contrib.
* Andy Steed (Adobe): starting to work on OW project, getting on-boarded
* Dan Klco, comes from Apache Sling looking at OW and Java tooling…
* Eric in RTP (IBM) plans to help with runtime work; newer to open source
openwhisk
* Justin Halsall (IBM) dev. looking at creating a Ruby runtime
* Dominic Kim: (Naver) working for Naver in Korea on their platform using
OW, interested in improving scheduling algorithms.
* Sam Baxter - no intentions described yet
* Tzu Chiao - no intentions described yet
How has the project developed since the last report?
Emphasis on these areas have been featured since last report:
* Release process, See incubator-openwhisk-release (code, tools,
documentation), see demo (as of 2/28) on YouTube
* Automated and Manual release process complete and documented:
* Instructions for Release Managers.
* 100% of release candidate source code has Apache 2 license headers or
a documented exception as allowed by ASF policy (e.g., simple data or
config files):
* See
https://github.com/apache/incubator-openwhisk-release/blob/master/docs/licen
se_compliance.md
* Currently, working to assure JDK is configurable for builds.
* See PR: Update the document regarding Open JDK and Oracle JDK
* Codecov added: codecov coverage badge displayed
* Security enhancements
* Limit cipher suites used for controller https
* Assure nginx verifies upstream ssl certs
* Add option to encrypt redis password
* CLI "Go client": Changing default namespace from guest to _
* Docker runtime/SDK: add openssh client for dockerskeleton
* Scalability / Performance
* Make REST communication with action containers more robust - Lowered
the time between retries from 100 ms to 10 ms because this shorter time
should be sufficient to have routing available / the target socket
listening.
* Add build matrix to execute performance tests
* Add gatling as performance test suite
* Add gatling-throughput test for cold invocations - added a
"ColdBlockingInvokeSimulation"
* Split test jobs in Travis - improve Travis build performance
(parallelize tests)
* Make limit overcommit relative to the actual cluster size
* Augment RuntimeManifest with stem cell configuration per kind
* Other Notable discussions/changes/issues/features:
* MemoryArtifactStore for unit testing and ArtifactStore SPI Validation
* bump reference for NodeJS images, updating NodeJS6 & NodeJS8
* Bump nginx version to latest and disable server-side information
* Emit activation metadata to Kafka
* Update akka to 2.5.12 and akka-http to 10.1.1
* Various Vagrant (user, ez-up) fixes, including: increase vagrant
disksize using plugin vagrant-disksize,
* Fix vagrant not use runc
* Document updates:
* Remove Consul from "The Internal flow of processing" section
diagram in about.md
* Create troubleshooting guide for dependency download failures
* Fix outdated docs in about.md and actions.md
* Runtime updates
* NodeJS: update nodejs6 -> 6.14.2, nodejs8 -> 8.11.2
* Java: Make AdoptOpenJDK Eclipse OpenJ9 the Java runtime for Java
actions
* Swift: Update swift41 to 03-26a - update swift41 snapshot build to
`2018-03-26-a`
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:
Comments:
* Need greater variety of contributors and contributing companies
Date of last release:
* N/A
When were the last committers or PPMC members elected?
* New Committers+PPMC: None
* New Committers: Vadim Raskin (2018-04-20), Jason Peterson (2018-04-18)
Signed-off-by:
[ ](openwhisk) Isabel Drost-Fromm
Comments:
[X](openwhisk) Bertrand Delacretaz
Comments:
[X](openwhisk) Jim Jagielski
Comments:
IPMC/Shepherd notes:
--------------------
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:
1. Complete the Podling name search tasks. The task is in progress right
now.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?
None
How has the community developed since the last report?
The community added 7 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.
Project members from several companies have organized or participated in
several meetups, presenting Pulsar's introductions, deep-dives and hands-on
tutorial, including recorded podcasts. We have several scheduled talks on
Pulsar at various conferences, 2 at ApacheCon in September, one at OSCon
in July and 2 others at Strata New York in September. A Pulsar dedicated
meetup is being organized for next July.
Since the last report the number of weekly-active-users on the Slack
channel has increased from 53 to 88.
We have reached the 1 year mark since Pulsar entering the Apache
Incubator.
Here is a summary of the community developments over the past year:
1. Pulsar community has done 5 Apache releases since entering
incubator. The release process is well documented and we have
had 4 different release managers from 3 different companies.
2. We have added 3 committers and PPMC members since incubation and
there are also other candidates who have already made significant
contributions to the project.
3. Community of users and people interested in Pulsar has expanded
considerably. Thanks to the months long work in improving ease of
use, documentation and blogs, many people became aware of Pulsar
and started playing with it, then evaluating it and finally
putting it in production for critical use cases.
4. We have tried to help users getting started through any
communication channel. Even though we keep trying to encourage
people to use the mailing list, most of the first interactions
have been happening through the Slack channel. We also did make
sure that:
a) No decisions are taken in Slack channel
b) Developers technical discussion happen mostly in Github
issue/Pull-Request or in developers mailing list
c) Conversations in Slack are sent to dev/user mailing list in a
daily digest form for archival and to be searchable
In any case Slack has been working fairly well in engaging with
users, by providing a tool to have very quick informal
question/answer interactions that were very appreciated by users.
5. Overall, there were a lot of healthy discussions, with feedback
and collaborations from people from different companies and
different perspectives that resulted in much stronger design
decisions and ultimately a better system.
6. We have taken several steps to increase awareness, like blog
posts, meetups (both dedicated to Pulsar or dedicated to similar
topics) and presentations to conferences, like Strata or
ApacheCon (where we have 2 talks scheduled for next September).
How has the project developed since the last report?
23 authors have pushed 469 commits to master in the last 3 months.
The project has made the its fifth release since joining the
Apache Incubator (2.0.0-rc1-incubating on May 29th). This was a
major release that culminated several months of works and lays the
foundation for the next stage in Pulsar development. New major
features include:
* Pulsar Functions (Lightweight compute framework)
* Schema registry
* Topic compaction
Community is actively working on next milestone, 2.1 release that
will include several new features including:
* Pulsar IO connector framework
* Tiered storage
* Go client library
Since March, 3 new PIPs (Pulsar Improvement Proposals) for major
feature/changes, have been submitted to the wiki and discussed in the
mailing list.
To recap the project developments since entering Apache Incubator:
1. Moved to Apache BookKeeper 4.7. Before Pulsar 2.0, we were using
a fork of BookKeeper from Yahoo, based on 4.3.1 with 245
additional commits. Thanks to a a big effort in the BookKeeper
community (which has a large overlap with Pulsar community), all
these changed were merged back into mainstream BookKeeper branch
and released in BookKeeper 4.7.0, making possible for Pulsar to
switch over from the Yahoo fork.
2. We have received a lot of feedback from people approaching Pulsar
and learned a lot on how to simplify tools, documentation and
concepts to make it easier for people to get started.
3. Based on the same feedback and inputs, we have been adding new
features or extended existing features to match a new variety of
use case, some of them outside the scope the initial Pulsar
codebase from Yahoo.
To summarize the "major" features added in the last year:
- Pulsar stateless proxy
- Non-persistent topics
- End-to-End message encryption
- Effectively-once semantics
- Type-safe APIs
- Schema Registry
- Pulsar Functions
- Topic compaction
- Python client library
With more scheduled for next upcoming release 2.1:
- Pulsar IO connector framework
- Tiered storage
- Go client library
4. In addition to features, we have been trying to smooth the
deployment of a production ready Pulsar cluster, by improving the
documentation and providing templates for more common environments,
such as Kubernetes, DCOS or just plain VMs with Ansible.
5. Having exposure to many users testing and using the sytem outside
the original Yahoo use cases has proven very effecting in helping
identifying and resolving corner cases that were not being
stressed before. This resulted in a much resilient system that
can adapt better to a large array of different requirements and
environments.
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-29, 2.0.0-rc1-incubating
When were the last committers or PPMC members elected?
2018-05-28 - Jerry Peng
2018-05-28 - Sanjeev Kulkarni
Signed-off-by:
[X](pulsar) Dave Fisher
Comments: PPMC needs to work on brand management issues. Mentors are
engaging the PPMC in the issue.
[X](pulsar) Jim Jagielski
Comments: Also community and corporate interaction issues are being worked.
[X](pulsar) P. Taylor Goetz
Comments:
[ ](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?
We have added a new member as a committer.
How has the project developed since the last report?
We are working on improving the code base. Routine bug
fixes aside, there are ongoing efforts for three main development directions
(respective JIRA issues have been opened):
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:
The project seems to have slowed somewhat. Development activity
is about the same, but there has not been a release for over a
year, and I do not sense any real efforts at community building
outside of the core group. I will be concerned if things don't
change soon.
[ ](quickstep) Roman Shaposhnik
Comments:
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?
* Contributions on few components from community
- bulk loader (S2GRAPH-178, S2GRAPH-184)
- rest api(S2GRAPH-186)
- logger(S2GRAPH-188)
* Submit a talk to ApacheCon NA 2018
-
https://apachecon.dukecon.org/acna/2018/#/scheduledEvent/835a6adcab1ce83a0
* Two initial committer become active, which make 3 active committers.
How has the project developed since the last report?
* 42 issues are created and 36 of them are resolved.
* Works more on GraphQL integration.
* Start to work on supporting OLAP.
* Add simple example using movielens dataset.
* Generalize read/write interface more to integrate more storage backend
easily.
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. Revitalise 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 (March 2018 - May 2018):
* @dev: 25 messages
How has the project developed since the last report?
* Work on the project has slowed down, no new development since the last
report
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup
[ ] Working towards first release
[X] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
2016-09-30
When were the last committers or PPMC members elected?
January 2018
Signed-off-by:
[X](samoa) Alan Gates
Comments: I am glad to see the project is aware it needs to increase
the pace of development. Hopefully this will lead to more contributions
from the core team.
[ ](samoa) Ashutosh Chauhan
Comments:
[ ](samoa) Enis Soztutar
Comments:
[ ](samoa) Ted Dunning
Comments:
IPMC/Shepherd notes:
--------------------
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. Finish the tickets for supporting Keras (SINGA-340), ONNX (SINGA-333),
etc in the next release.
2.
3.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
No
How has the community developed since the last report?
The community becomes stable with 34 contributors in total.
How has the project developed since the last report?
A new version has been released, i.e. V1.2.
The major changes include the autograd feature and improvements to the
tensor class.
The last report is April.
There are 47, 140 and 7 emails from the dev@ list for April, May and June
respectively.
There are 98 commits since the last report.
How would you assess the podling's maturity?
We have one more release (i.e. V2.0) to do before graduation.
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: I agree that this community has started growing in a healthy
way and should be thinking about the path to graduation.
[ ](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 an open end user case,
at least.
5. Support multiple languages agents/SDKs
6. Integration with other pupolar OSS systems.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
Have two Apache releases already. 5.0.0-alpha, 5.0.0-beta
How has the community developed since the last report?
1. .NetCore agent has three releases based on SkyWalking's network
protocol and data format.
2. Node.js server side agent has three releases based on SkyWalking's
network protocol and data format.
3. 5.0.0-alpha/beta has been used in product env as their primary APM
system, by more than 5 companies.
4. Proposal, voted and passed Haoyang Liu, the lead of the .NetCore agent
project, as the new Committer.
5. There are 38 people to contribute codes to our main repo. 10 more than
last report.
6. Work with the Zipkin tracing system group, try to accept Zipkin data
by SkyWalking collector.
How has the project developed since the last report?
Code wise the project has good momentum.
There has been ~200 pull requests opened and accepted, and 214 commits,
by 21 contributors in the last month.
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[X] Initial setup
[X] Working towards first release
[X] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
2018-05-23
When were the last committers or PPMC members elected?
May. 2018
Signed-off-by:
[ ](skywalking) Luke Han
Comments:
[ ](skywalking) Willem Ning Jiang
Comments:
[X](skywalking) Mick Semb Wever
Comments: optional, but you might write up the feedback you got from
the IMPC on your last release, and how it's been addressed and what you
learnt.
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?
* None
How has the community developed since the last report?
* Organic growth of our Github contributors (211->246), forks
(2,981->3318), watchers
(975->1020) and stars (18,249->19,399)
* Group of active committers meeting bi-weekly from Airbnb, Lyft and
Twitter. New committers include Vyl Chiang, Hugh Miles, Fabian Menges
and Sylvia Tomiyama.
* Slack channel for Apache Superset at https://apache-superset.slack.com/
has active growth and activity
How has the project developed since the last report?
* A redesign of the Dashboarding view is rolling out week of 6/11/2018
* The new metrics definition flow is rolling out on [DATE TBD]
* A redesign of the Explore view has just started
* Rich geospatial visualizations utilizing deck.gl including interactive
time slider/player
* Improved SQL Lab to Visualization flow including a redesign of the
table config editor will be rolling out in July 2018
* Improved time selector in Explore view
* 1 new feature, 1 improvement and 2 bugs fixes from Twitter
* 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 Q3, 2018)
When were the last committers or PPMC members elected?
* Vyl Chiang - Committer (2018-05-01)
* Sylvia Tomiyama - Committer (2018-05-01)
* Hugh Miles - Committer (2018-03-24)
* Fabian Menges - Committer (2018-03-21)
Signed-off-by:
[ ](superset) Ashutosh Chauhan
Comments:
[ ](superset) Luke Han
Comments:
[X](superset) Jim Jagielski
Comments: Still somewhat concerned about the reliance on the bi-weeklies...
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
2. Release or Retire legacy git repositories
3. Graduate!
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
How has the community developed since the last report?
Uptake in activity with GSOC students, already multiple merged pull
requests.
Little engagement from the wider PMC.
Email stats dev@taverna:
2018-05: 62
2018-04: 41
2018-03: 102
How has the project developed since the last report?
Moved to Java 9 (just in time for Java 10?).
PPMC voted on Taverna Language release, but it failed IPMC vote
due to CC-BY licensed schema files. Will refactor.
Some confusion as this seemed allowed by
http://www.apache.org/legal/resolved.html#category-b
See https://s.apache.org/lang-0.16.0-RC1-vote
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup
[ ] Working towards first release
[x] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
2018-01-18
When were the last committers or PPMC members elected?
2018-02-26 (PPMC)
Signed-off-by:
[x](taverna) Andy Seaborne
Comments:
There has been an encouraging pickup in development going on but the
PPMC remains quite quiet in terms of project graduation.
Mentor engagement, including mime, is low.
[ ](taverna) Daniel J Debrunner
Comments:
[ ](taverna) Marlon Pierce
Comments:
[x](taverna) Stian Soiland-Reyes
Comments:
If Taverna is to proceed to Graduation instead of Retirement from the
incubator, it needs to keep more of the PMC members engaged and
motivated.
[ ](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?
- 7 new JIRAs filed since the last report
How has the project developed since the last report?
- Completed the 0.14.0-incubating release
- Working on 0.15.0-incubating release
- Added support for HBase 2.0 (new major version of HBase)
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup
[ ] Working towards first release
[x] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
2018-05-30
When were the last committers or PPMC members elected?
- None since coming to incubation
Signed-off-by:
[X](tephra) Alan Gates
Comments: Sent following email to dev list after reading this report:
It seems development on Tephra has slowed quite a bit lately, with only 7
JIRAs filed during the last 3 months. I know Tephra is used in other
projects, like Apache Phoenix. Is this slowdown temporary? Is development
slowing because Tephra is mature and only maintenance is now required? Is
it continuing to be picked up by new projects or only used in 1 or 2
places? I ask because it feels like it is near time for Tephra to graduate
(it's been incubating for over 2 years now) and what needs to be done to
graduate is somewhat determined by the answers to these questions.
[ ](tephra) Andrew Purtell
Comments:
[x](tephra) James Taylor
Comments:
[ ](tephra) Lars Hofhansl
Comments:
IPMC/Shepherd notes:
}}}
----------------------------------------------------------------------
Table of Contents
AriaTosca
Crail
Daffodil
Dubbo
Gearpump
Gossip
Griffin
Hivemall
Myriad
Nemo
Omid
OpenWhisk
Pulsar
Quickstep
S2Graph
SAMOA
SINGA
SkyWalking
Superset
Taverna
Tephra
----------------------------------------------------------------------
--------------------
AriaTosca
ARIA TOSCA project offers an easily consumable Software Development Kit(SDK)
and a Command Line Interface(CLI) to implement TOSCA(Topology and
Orchestration Specification of Cloud Applications) based solutions.
AriaTosca has been incubating since 2016-08-27.
Three most important issues to address in the move towards graduation:
1. All development activity has ceased.
2. Discussions underway to decide on the future course of the podling.
3.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
How has the community developed since the last report?
Discussions in progress about the future course of the project.
How has the project developed since the last report?
All development activity on the project has ceased, all present
committers have moved on to pursue other interests.
How would you assess the podling's maturity?
Community Building
Please feel free to add your own commentary.
[ ] Initial setup
[ ] Working towards first release
[X] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
2018-01-16
When were the last committers or PPMC members elected?
Thomas Nadeau added in Feb 2018
Signed-off-by:
[X](ariatosca) Suneel Marthi
Comments:
[ ](ariatosca) John D. Ament
Comments:
[ ](ariatosca) Jakob Homan
Comments:
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: Additional contributors from different
companies/affiliations
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?
* To advertise the project, we present(ed) the Crail project at:
* OpenFabrics 2018 Workshop
(Crail non-volatile memory integration, presented in April)
* Spark and AI 2018 Summit
(Serverless computing with Crail, presented June 5)
* DataWorks 2018 Summit in June (Crail, to be presented June 21)
How has the project developed since the last report?
* First source code release (Apache-Crail 1.0-incubating) done
(+4, -0 binding votes) and available
* Designed/implemented new generic NVMeF storage tier which makes
code base independent of SPDK/DPDK environment
* 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:
Having made the (always difficult) first release, the project
is in good shape. They are starting to generate some publicity
by speaking at conferences. I am encouraging them to create a
twitter account (so that they can interact with the wider
community more frequently) and to start thinking of a second
release (to ensure that the release process is reproducible).
[x] (crail) Luciano Resende
Comments:
[] (crail) Raphael Bircher
Comments:
IPMC/Shepherd notes:
lresende: I removed the check from 'working towards first release' as the
first release was just completed
--------------------
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, previous legal issues regarding Open Grid Forum license were
clarified (LEGAL-369)
How has the community developed since the last report?
- Starting community building, including conversations on the user@ and
dev@ lists from a handful of outside users requesting some support and
information on Daffodil for DFDL schema creation.
- Mike Beckerle was accepted for a talk on Daffodil at ApacheCon
- Received two bug fix contributions from an outside user, who was able
to spin up and make contributions quickly
How has the project developed since the last report?
- Created our first release as an Apache incubator
- All website and wiki documentation is up to date
- Had 14 commits from 5 different developers over the past three months
- Still under active development, though upcoming features are large
and take time to implement
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-05-14
When were the last committers or PPMC members elected?
- None, same as project incubation
Signed-off-by:
[ ](daffodil) John D. Ament
Comments:
[X](daffodil) David Fisher
Comments: Project is making progress. Another Mentor would be helpful.
IPMC/Shepherd notes:
--------------------
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. First release
2. Community building
3. Change group id to org.apache
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
None.
How has the community developed since the last report?
* Complete All ICLA collection for all the contributors which are
necessary to have
* The first Apache release 2.6.2 has passed the incubator community vote
* zonghaishang(yiji) has been voted as new committer
* Ian Luo/Jun Liu's talk about
"Introducing Apache Dubbo(Incubating): What is Dubbo and How it Works"
has been accepted by ApacheCon NA.
* The first Dubbo meetup has been held in Beijing, with over 400+
people attended
* 10 new companies reported their using of Dubbo since last report
How has the project developed since the last report?
* 2.6.2 is ready to release
* The community has decided to a new major version 2.7.x to
incorporate incompatible changes.
* 57 Active Pull Requests, 49 pull request merged, with 21
contributors involved
* 180 Active Issues, 127 issues closed
* Github star 19286, fork 13491
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. (2.6.2 has passed incubator community release vote and is
expected to be released within several days)
When were the last committers or PPMC members elected?
2018-06-01
Signed-off-by:
[X](dubbo) Justin Mclean
Comments:
[ ](dubbo) Jean-Frederic Clere
Comments:
[X](dubbo) Mark Thomas
Comments: Good work on the first release.
dev@ list traffic is a lot easier to follow
now notifications have moved to a separate
list
I'm still struggling with the volume of
notifications. It is getting easier as I
become more familiar with the project but I do
worry that newcomers to the project will find
it difficult to follow.
IPMC/Shepherd notes:
--------------------
Gearpump
Gearpump is a reactive real-time streaming engine based on the
micro-service Actor model.
Gearpump has been incubating since 2016-03-08.
Most important issues to address in the move towards graduation:
1. Have frequent release cycles.
2. Continue to evolve community interest and support.
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 contributor added Apache Kudu integration to Gearpump.
How has the project developed since the last report?
- 13 issues created and 17 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:
2017-07-17
When were the last committers or PMC members elected?
No new committers or PMC members elected yet.
Signed-off-by:
[X](gearpump) Jean-Baptiste Onofré
Comments: low but "stable" activity, we definitely should try to speed
up the release cycle
[ ](gearpump) Andrew Purtell
Comments:
[ ](gearpump) Jarek Jarcec Cecho
Comments:
[ ](gearpump) Reynold Xin
Comments:
[ ](gearpump) Todd Lipcon
Comments:
[ ](gearpump) Xuefu Zhang
Comments:
IPMC/Shepherd notes:
--------------------
Gossip
Gossip is an implementation of the Gossip Protocol.
Gossip has been incubating since 2016-04-28.
Three most important issues to address in the move towards graduation:
1. Locating willing committers to handle code reviews
2. Achieving out third release
3. Integration into some downstream tools.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
How has the community developed since the last report?
Discussed status/availability with some of the initial committers. There
was some general interest, but no strong commitments to providing time for
reviews.
How has the project developed since the last report?
We took some time and reviewed community committed PRs. Those will be
merged over the next 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:
2017-03-02
When were the last committers or PPMC members elected?
Chandresh Pancholi added as a committer in February 2017
Signed-off-by:
[X](gossip) P. Taylor Goetz
Comments: Activity is very low. Retirement is likely on the horizon.
[ ](gossip) Josh Elser
Comments:
[ ](gossip) Drew Farris
Comments:
IPMC/Shepherd notes:
--------------------
Griffin
Griffin is an 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. Improve user guide documents.
2. Preparation for graduation.
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?
- 3 new committers have been elected.
- 14 new contributors contributed to our community.
- More users have contacted us for use cases.
How has the project developed since the last report?
- Active development is moving on well, 53 commits in last three months.
- Released new version 0.2.0-incubating.
- Support measure job scheduler for batch mode.
- Use PostgreSQL instead of MySQL by default.
- Upgrade default spark version from 1.6.x to 2.2.1 in measure module.
- Upgrade default hive version from 1.2.1 to 2.2.0 in measure module.
- Refactor measure module for clearer structure.
- Work toward for next version release.
How would you assess the podling's maturity?
[] Initial setup
[] Working towards first release
[] Community building - One new contributor
[X] Nearing graduation
[] Other:
Date of last release:
- May 16th, 2018
When were the last committers or PPMC members elected?
- 3 new committers were elected at Mar 30th, 2018
Signed-off-by:
[X](griffin) Henry Saputra
Comments:
[ ](griffin) Kasper Sørensen
Comments:
[ ](griffin) Uma Maheswara Rao Gangumalla
Comments:
[x](griffin) Luciano Resende
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 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:
145 stars as of June 5 (was 131 on April 3)
* Twitter account @ApacheHivemall followers are gradually increasing:
145 followers as of June 5 (was 123 on April 3)
How has the project developed since the last report?
* Preparing the second Apache release, v0.5.2. It will be release in
July, 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 2 months, we opened 21 JIRA issues and closed 10 JIRA
issues as seen in https://goo.gl/QFQEF5 (as of June 5)
Created Resolved
April 2018 17 10
May 2018 4 0
* Created 11 Pull Requests and merged 11 Pull Requests between Apr 01
and May 31.
https://github.com/apache/incubator-hivemall/pulls?q=is%3Apr%20created%3A201
8-04-01..2018-05-31
https://github.com/apache/incubator-hivemall/pulls?q=is%3Apr%20closed%3A2018
-04-01..2018-05-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:
[ ](hivemall) Xiangrui Meng
Comments:
[ ](hivemall) Daniel Dai
Comments:
IPMC/Shepherd notes:
--------------------
Myriad
Myriad enables co-existence of Apache Hadoop YARN and Apache Mesos together
on the same cluster and allows dynamic resource allocations across both Hadoop
and other applications running on the same physical data center
infrastructure.
Myriad has been incubating since 2015-03-01.
Three most important issues to address in the move towards graduation:
1. Grow the community and enroll new committers.
2. Have (more) frequent Release cycles to be compliant with the Apache
Way.Creating roadmaps for releases with goals (new features).
3. Social media presence (new blog entries, conference talks).
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
There are no new issues requiring board attention at this time.
How has the community developed since the last report?
1. Two new committers/PMC members from the last report (total 8
committers).
2. Increase activity in the dev mailing list.
3. Twitter account with 1018 followers and daily basis activity.
4. Community chat channel with 7 registered user (low activity).
How has the project developed since the last report?
1. Project rebooting roadmap on going with success: https://goo.gl/2gdcrP
2. Resolved JIRA Issues: 11
3. Pull Requests merged: 8
4. Strong local development environment for Apache Mesos and Mesosphere
DC/OS.
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: Project rebooting in progress, retirement risk not present
right now.
Date of last release:
The 0.2.0 release was issued on Jun 29, 2016. The .3 release is
planned for this quarter.
When were the last committers or PPMC members elected?
1. 2018-05-22 New committer/PMC member Juan P. Gilaberte.
2. 2018-03-28 New committer/PMC member Javi Roman.
Signed-off-by:
[ ](myriad) Benjamin Hindman
Comments:
[ ](myriad) Danese Cooper
Comments:
[X](myriad) Ted Dunning
Comments:
IPMC/Shepherd notes:
--------------------
Nemo
Nemo is a data processing system to flexibly control the runtime behaviors
of a job to adapt to varying deployment characteristics.
Nemo has been incubating since 2018-02-04.
Three most important issues to address in the move towards graduation:
1. Grow the community
2. Create a first Apache release
3. Donate code to ASF
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
None.
How has the community developed since the last report?
* Committers actively involved in mailing lists
* Committers actively started to send PRs and do code reviews
How has the project developed since the last report?
* Progress towards supporting Spark DSL programs
* Refactoring the Nemo runtime
* Finishing up a paper that describes the design and
implementation of Nemo
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[X] Initial setup
[X] Working towards first release
[ ] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
None yet.
When were the last committers or PPMC members elected?
None yet.
Signed-off-by:
[X](nemo) Davor Bonaci
Comments: Progress is probably a bit slower than before, but still
very high. Podling is doing great.
[ ](nemo) Hyunsik Choi
Comments:
[X](nemo) Byung-Gon Chun
Comments:
[ ](nemo) Jean-Baptiste Onofre
Comments:
[ ](nemo) Markus Weimer
Comments:
[ ](nemo) Reynold Xin
Comments:
IPMC/Shepherd notes:
Dave Fisher: AFAICT the SGA has not been provided and a mentor has
advised that this can wait until graduation.
I don't think that is correct and it is not the same as the guidance
given to other podlings like Heron.
See
https://lists.apache.org/thread.html/df7040d27bc8c01ec1601476b1e465226d4b1ea
99d0e5991b977fd1c@%3Cprivate.nemo.apache.org%3E
--------------------
Omid
Omid is a flexible, reliable, high performant and scalable ACID
transactional
framework that allows client applications to execute transactions on top of
MVCC key/value-based NoSQL datastores (currently Apache HBase) providing
Snapshot Isolation guarantees on the accessed data.
Omid has been incubating since 2016-03-28.
Three most important issues to address in the move towards graduation:
1. Boost project dissemination in the Apache community.
2. Collaborate/integrate Omid with other Apache projects.
3. Get positive feedback from other projects currently in Apache.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
N/A
How has the community developed since the last report?
Omid 0.9.0 released.
Continue integration with Apache Phoenix.
Pinterest exploring to use Omid in production.
How has the project developed since the last report?
Preparing 0.9.0 version. Solved issues related to legal stuff.
Quarter Stats (from: 2017-03-01 to: 2018-05-31):
+---------------------------------------------+
| Metric | counts |
+---------------------------------------------+
| # of msgs in dev list | 192 |
| Active Contributors (incl mentors)| 8 |
| Jira New Issues | 10 |
| Resolved Issues | 10 |
| Pull Requests merged | 12 |
| Pull Requests proposed | 14 |
+---------------------------------------------+
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-05-29
When were the last committers or PPMC members elected?
Signed-off-by:
[X](omid) Alan Gates
Comments:
[ ](omid) Lars Hofhansl
Comments:
[ ](omid) Flavio P. Junqueira
Comments:
[ ](omid) Thejas Nair
Comments:
[X](omid) James Taylor
Comments:
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:
* Produce our first source code release under Incubator (automation work
is now complete here https://github.com/apache/incubator-openwhisk-release).
We believe that the process to release will be initiated in the next 2
weeks.
* Increase contributions to ensure all project repos are maintained. and
address Issue / PR backlog.
* 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 #3 above). As of this report, the "open" issue backlog is
365 and open PR is 55. Need to prioritize and work to reduce while
advancing performance/security/deployment issues.
* Trying to add more active Committers to augment those who have dropped
off in their activity; 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.
* Formal hand-off of OpenWhisk trademark/logo from IBM needs to be
executed; need to identify process for this.
Discussion started w/ Apache legal via "legal-discuss" mailing list with
subject "Trademark handoff for "OpenWhisk" name and logo".
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 has been down with the exception of work
around the new Go language runtime (mostly April). It appears that 2Q
conferences may be partly to blame with corporate Committers being
preoccupied.
* incubator-openwhisk Github stars: 3218 (+341 since last report)
* incubator-openwhisk GitHub forks: 616 (+72 since last report)
* Slack community We're ~800 members and it is really active, from both
end users or the project and contributors
* 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
(https://www.youtube.com/channel/UCbzgShnQk8F43NKsvEYA1SA)
* CWiki Meeting Notes: OpenWhisk Technical Interchange Meeting Notes
* 2018-05-23 OW Tech Interchange - Meeting Notes
* 2018-05-09 OW Tech Interchange - Meeting Notes
* 2018-04-25 OW Tech Interchange - Meeting Notes
* 2018-04-11 OW Tech Interchange - Meeting Notes
* 2018-03-28 OW Tech Interchange - Meeting Notes
* 2018-03-14 OW Tech Interchange - Meeting Notes
New Contributors
* Moritz Raho: (Adobe) intern, focus on user/dev experience
* Nareej: (Adobe) started using OpenWhisk for internal notifications,
looking to become a contrib.
* Andy Steed (Adobe): starting to work on OW project, getting on-boarded
* Dan Klco, comes from Apache Sling looking at OW and Java tooling…
* Eric in RTP (IBM) plans to help with runtime work; newer to open source
openwhisk
* Justin Halsall (IBM) dev. looking at creating a Ruby runtime
* Dominic Kim: (Naver) working for Naver in Korea on their platform using
OW, interested in improving scheduling algorithms.
* Sam Baxter - no intentions described yet
* Tzu Chiao - no intentions described yet
How has the project developed since the last report?
Emphasis on these areas have been featured since last report:
* Release process, See incubator-openwhisk-release (code, tools,
documentation), see demo (as of 2/28) on YouTube
* Automated and Manual release process complete and documented:
* Instructions for Release Managers.
* 100% of release candidate source code has Apache 2 license headers or
a documented exception as allowed by ASF policy (e.g., simple data or
config files):
* See
https://github.com/apache/incubator-openwhisk-release/blob/master/docs/licen
se_compliance.md
* Currently, working to assure JDK is configurable for builds.
* See PR: Update the document regarding Open JDK and Oracle JDK
* Codecov added: codecov coverage badge displayed
* Security enhancements
* Limit cipher suites used for controller https
* Assure nginx verifies upstream ssl certs
* Add option to encrypt redis password
* CLI "Go client": Changing default namespace from guest to _
* Docker runtime/SDK: add openssh client for dockerskeleton
* Scalability / Performance
* Make REST communication with action containers more robust - Lowered
the time between retries from 100 ms to 10 ms because this shorter time
should be sufficient to have routing available / the target socket
listening.
* Add build matrix to execute performance tests
* Add gatling as performance test suite
* Add gatling-throughput test for cold invocations - added a
"ColdBlockingInvokeSimulation"
* Split test jobs in Travis - improve Travis build performance
(parallelize tests)
* Make limit overcommit relative to the actual cluster size
* Augment RuntimeManifest with stem cell configuration per kind
* Other Notable discussions/changes/issues/features:
* MemoryArtifactStore for unit testing and ArtifactStore SPI Validation
* bump reference for NodeJS images, updating NodeJS6 & NodeJS8
* Bump nginx version to latest and disable server-side information
* Emit activation metadata to Kafka
* Update akka to 2.5.12 and akka-http to 10.1.1
* Various Vagrant (user, ez-up) fixes, including: increase vagrant
disksize using plugin vagrant-disksize,
* Fix vagrant not use runc
* Document updates:
* Remove Consul from "The Internal flow of processing" section
diagram in about.md
* Create troubleshooting guide for dependency download failures
* Fix outdated docs in about.md and actions.md
* Runtime updates
* NodeJS: update nodejs6 -> 6.14.2, nodejs8 -> 8.11.2
* Java: Make AdoptOpenJDK Eclipse OpenJ9 the Java runtime for Java
actions
* Swift: Update swift41 to 03-26a - update swift41 snapshot build to
`2018-03-26-a`
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:
Comments:
* Need greater variety of contributors and contributing companies
Date of last release:
* N/A
When were the last committers or PPMC members elected?
* New Committers+PPMC: None
* New Committers: Vadim Raskin (2018-04-20), Jason Peterson (2018-04-18)
Signed-off-by:
[ ](openwhisk) Isabel Drost-Fromm
Comments:
[X](openwhisk) Bertrand Delacretaz
Comments:
[X](openwhisk) Jim Jagielski
Comments:
IPMC/Shepherd notes:
--------------------
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:
1. Complete the Podling name search tasks. The task is in progress right
now.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?
None
How has the community developed since the last report?
The community added 7 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.
Project members from several companies have organized or participated in
several meetups, presenting Pulsar's introductions, deep-dives and hands-on
tutorial, including recorded podcasts. We have several scheduled talks on
Pulsar at various conferences, 2 at ApacheCon in September, one at OSCon
in July and 2 others at Strata New York in September. A Pulsar dedicated
meetup is being organized for next July.
Since the last report the number of weekly-active-users on the Slack
channel has increased from 53 to 88.
We have reached the 1 year mark since Pulsar entering the Apache
Incubator.
Here is a summary of the community developments over the past year:
1. Pulsar community has done 5 Apache releases since entering
incubator. The release process is well documented and we have
had 4 different release managers from 3 different companies.
2. We have added 3 committers and PPMC members since incubation and
there are also other candidates who have already made significant
contributions to the project.
3. Community of users and people interested in Pulsar has expanded
considerably. Thanks to the months long work in improving ease of
use, documentation and blogs, many people became aware of Pulsar
and started playing with it, then evaluating it and finally
putting it in production for critical use cases.
4. We have tried to help users getting started through any
communication channel. Even though we keep trying to encourage
people to use the mailing list, most of the first interactions
have been happening through the Slack channel. We also did make
sure that:
a) No decisions are taken in Slack channel
b) Developers technical discussion happen mostly in Github
issue/Pull-Request or in developers mailing list
c) Conversations in Slack are sent to dev/user mailing list in a
daily digest form for archival and to be searchable
In any case Slack has been working fairly well in engaging with
users, by providing a tool to have very quick informal
question/answer interactions that were very appreciated by users.
5. Overall, there were a lot of healthy discussions, with feedback
and collaborations from people from different companies and
different perspectives that resulted in much stronger design
decisions and ultimately a better system.
6. We have taken several steps to increase awareness, like blog
posts, meetups (both dedicated to Pulsar or dedicated to similar
topics) and presentations to conferences, like Strata or
ApacheCon (where we have 2 talks scheduled for next September).
How has the project developed since the last report?
23 authors have pushed 469 commits to master in the last 3 months.
The project has made the its fifth release since joining the
Apache Incubator (2.0.0-rc1-incubating on May 29th). This was a
major release that culminated several months of works and lays the
foundation for the next stage in Pulsar development. New major
features include:
* Pulsar Functions (Lightweight compute framework)
* Schema registry
* Topic compaction
Community is actively working on next milestone, 2.1 release that
will include several new features including:
* Pulsar IO connector framework
* Tiered storage
* Go client library
Since March, 3 new PIPs (Pulsar Improvement Proposals) for major
feature/changes, have been submitted to the wiki and discussed in the
mailing list.
To recap the project developments since entering Apache Incubator:
1. Moved to Apache BookKeeper 4.7. Before Pulsar 2.0, we were using
a fork of BookKeeper from Yahoo, based on 4.3.1 with 245
additional commits. Thanks to a a big effort in the BookKeeper
community (which has a large overlap with Pulsar community), all
these changed were merged back into mainstream BookKeeper branch
and released in BookKeeper 4.7.0, making possible for Pulsar to
switch over from the Yahoo fork.
2. We have received a lot of feedback from people approaching Pulsar
and learned a lot on how to simplify tools, documentation and
concepts to make it easier for people to get started.
3. Based on the same feedback and inputs, we have been adding new
features or extended existing features to match a new variety of
use case, some of them outside the scope the initial Pulsar
codebase from Yahoo.
To summarize the "major" features added in the last year:
- Pulsar stateless proxy
- Non-persistent topics
- End-to-End message encryption
- Effectively-once semantics
- Type-safe APIs
- Schema Registry
- Pulsar Functions
- Topic compaction
- Python client library
With more scheduled for next upcoming release 2.1:
- Pulsar IO connector framework
- Tiered storage
- Go client library
4. In addition to features, we have been trying to smooth the
deployment of a production ready Pulsar cluster, by improving the
documentation and providing templates for more common environments,
such as Kubernetes, DCOS or just plain VMs with Ansible.
5. Having exposure to many users testing and using the sytem outside
the original Yahoo use cases has proven very effecting in helping
identifying and resolving corner cases that were not being
stressed before. This resulted in a much resilient system that
can adapt better to a large array of different requirements and
environments.
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-29, 2.0.0-rc1-incubating
When were the last committers or PPMC members elected?
2018-05-28 - Jerry Peng
2018-05-28 - Sanjeev Kulkarni
Signed-off-by:
[X](pulsar) Dave Fisher
Comments: PPMC needs to work on brand management issues. Mentors are
engaging the PPMC in the issue.
[X](pulsar) Jim Jagielski
Comments: Also community and corporate interaction issues are being worked.
[X](pulsar) P. Taylor Goetz
Comments:
[ ](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?
We have added a new member as a committer.
How has the project developed since the last report?
We are working on improving the code base. Routine bug
fixes aside, there are ongoing efforts for three main development directions
(respective JIRA issues have been opened):
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:
The project seems to have slowed somewhat. Development activity
is about the same, but there has not been a release for over a
year, and I do not sense any real efforts at community building
outside of the core group. I will be concerned if things don't
change soon.
[ ](quickstep) Roman Shaposhnik
Comments:
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?
* Contributions on few components from community
- bulk loader (S2GRAPH-178, S2GRAPH-184)
- rest api(S2GRAPH-186)
- logger(S2GRAPH-188)
* Submit a talk to ApacheCon NA 2018
-
https://apachecon.dukecon.org/acna/2018/#/scheduledEvent/835a6adcab1ce83a0
* Two initial committer become active, which make 3 active committers.
How has the project developed since the last report?
* 42 issues are created and 36 of them are resolved.
* Works more on GraphQL integration.
* Start to work on supporting OLAP.
* Add simple example using movielens dataset.
* Generalize read/write interface more to integrate more storage backend
easily.
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. Revitalise 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 (March 2018 - May 2018):
* @dev: 25 messages
How has the project developed since the last report?
* Work on the project has slowed down, no new development since the last
report
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup
[ ] Working towards first release
[X] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
2016-09-30
When were the last committers or PPMC members elected?
January 2018
Signed-off-by:
[X](samoa) Alan Gates
Comments: I am glad to see the project is aware it needs to increase
the pace of development. Hopefully this will lead to more contributions
from the core team.
[ ](samoa) Ashutosh Chauhan
Comments:
[ ](samoa) Enis Soztutar
Comments:
[ ](samoa) Ted Dunning
Comments:
IPMC/Shepherd notes:
--------------------
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. Finish the tickets for supporting Keras (SINGA-340), ONNX (SINGA-333),
etc in the next release.
2.
3.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
No
How has the community developed since the last report?
The community becomes stable with 34 contributors in total.
How has the project developed since the last report?
A new version has been released, i.e. V1.2.
The major changes include the autograd feature and improvements to the
tensor class.
The last report is April.
There are 47, 140 and 7 emails from the dev@ list for April, May and June
respectively.
There are 98 commits since the last report.
How would you assess the podling's maturity?
We have one more release (i.e. V2.0) to do before graduation.
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: I agree that this community has started growing in a healthy
way and should be thinking about the path to graduation.
[ ](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 an open end user case,
at least.
5. Support multiple languages agents/SDKs
6. Integration with other pupolar OSS systems.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
Have two Apache releases already. 5.0.0-alpha, 5.0.0-beta
How has the community developed since the last report?
1. .NetCore agent has three releases based on SkyWalking's network
protocol and data format.
2. Node.js server side agent has three releases based on SkyWalking's
network protocol and data format.
3. 5.0.0-alpha/beta has been used in product env as their primary APM
system, by more than 5 companies.
4. Proposal, voted and passed Haoyang Liu, the lead of the .NetCore agent
project, as the new Committer.
5. There are 38 people to contribute codes to our main repo. 10 more than
last report.
6. Work with the Zipkin tracing system group, try to accept Zipkin data
by SkyWalking collector.
How has the project developed since the last report?
Code wise the project has good momentum.
There has been ~200 pull requests opened and accepted, and 214 commits,
by 21 contributors in the last month.
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[X] Initial setup
[X] Working towards first release
[X] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
2018-05-23
When were the last committers or PPMC members elected?
May. 2018
Signed-off-by:
[ ](skywalking) Luke Han
Comments:
[ ](skywalking) Willem Ning Jiang
Comments:
[X](skywalking) Mick Semb Wever
Comments: optional, but you might write up the feedback you got from
the IMPC on your last release, and how it's been addressed and what you
learnt.
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?
* None
How has the community developed since the last report?
* Organic growth of our Github contributors (211->246), forks
(2,981->3318), watchers
(975->1020) and stars (18,249->19,399)
* Group of active committers meeting bi-weekly from Airbnb, Lyft and
Twitter. New committers include Vyl Chiang, Hugh Miles, Fabian Menges
and Sylvia Tomiyama.
* Slack channel for Apache Superset at https://apache-superset.slack.com/
has active growth and activity
How has the project developed since the last report?
* A redesign of the Dashboarding view is rolling out week of 6/11/2018
* The new metrics definition flow is rolling out on [DATE TBD]
* A redesign of the Explore view has just started
* Rich geospatial visualizations utilizing deck.gl including interactive
time slider/player
* Improved SQL Lab to Visualization flow including a redesign of the
table config editor will be rolling out in July 2018
* Improved time selector in Explore view
* 1 new feature, 1 improvement and 2 bugs fixes from Twitter
* 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 Q3, 2018)
When were the last committers or PPMC members elected?
* Vyl Chiang - Committer (2018-05-01)
* Sylvia Tomiyama - Committer (2018-05-01)
* Hugh Miles - Committer (2018-03-24)
* Fabian Menges - Committer (2018-03-21)
Signed-off-by:
[ ](superset) Ashutosh Chauhan
Comments:
[ ](superset) Luke Han
Comments:
[X](superset) Jim Jagielski
Comments: Still somewhat concerned about the reliance on the bi-weeklies...
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
2. Release or Retire legacy git repositories
3. Graduate!
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
How has the community developed since the last report?
Uptake in activity with GSOC students, already multiple merged pull
requests.
Little engagement from the wider PMC.
Email stats dev@taverna:
2018-05: 62
2018-04: 41
2018-03: 102
How has the project developed since the last report?
Moved to Java 9 (just in time for Java 10?).
PPMC voted on Taverna Language release, but it failed IPMC vote
due to CC-BY licensed schema files. Will refactor.
Some confusion as this seemed allowed by
http://www.apache.org/legal/resolved.html#category-b
See https://s.apache.org/lang-0.16.0-RC1-vote
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup
[ ] Working towards first release
[x] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
2018-01-18
When were the last committers or PPMC members elected?
2018-02-26 (PPMC)
Signed-off-by:
[x](taverna) Andy Seaborne
Comments:
There has been an encouraging pickup in development going on but the
PPMC remains quite quiet in terms of project graduation.
Mentor engagement, including mime, is low.
[ ](taverna) Daniel J Debrunner
Comments:
[ ](taverna) Marlon Pierce
Comments:
[x](taverna) Stian Soiland-Reyes
Comments:
If Taverna is to proceed to Graduation instead of Retirement from the
incubator, it needs to keep more of the PMC members engaged and
motivated.
[ ](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?
- 7 new JIRAs filed since the last report
How has the project developed since the last report?
- Completed the 0.14.0-incubating release
- Working on 0.15.0-incubating release
- Added support for HBase 2.0 (new major version of HBase)
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup
[ ] Working towards first release
[x] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
2018-05-30
When were the last committers or PPMC members elected?
- None since coming to incubation
Signed-off-by:
[X](tephra) Alan Gates
Comments: Sent following email to dev list after reading this report:
It seems development on Tephra has slowed quite a bit lately, with only 7
JIRAs filed during the last 3 months. I know Tephra is used in other
projects, like Apache Phoenix. Is this slowdown temporary? Is development
slowing because Tephra is mature and only maintenance is now required? Is
it continuing to be picked up by new projects or only used in 1 or 2
places? I ask because it feels like it is near time for Tephra to graduate
(it's been incubating for over 2 years now) and what needs to be done to
graduate is somewhat determined by the answers to these questions.
[ ](tephra) Andrew Purtell
Comments:
[x](tephra) James Taylor
Comments:
[ ](tephra) Lars Hofhansl
Comments:
IPMC/Shepherd notes:
}}}
-----------------------------------------
Attachment AH: Report from the Apache Jackrabbit Project [Michael Dürig]
Report from the Apache Jackrabbit committee [Michael Dürig]
## Description:
The Apache Jackrabbit™ content repository is a fully conforming
implementation of the Content Repository for Java™ Technology API
(JCR, specified in JSR 170 and 283). The Jackrabbit content
repository is stable, largely feature complete and actively being
maintained.
Jackrabbit Oak is an effort to implement a scalable and performant
hierarchical content repository as a modern successor to the Apache
Jackrabbit content repository. It is targeted for use as the
foundation of modern world-class web sites and other demanding
content applications. In contrast to its predecessor, Oak does not
implement all optional features from the JSR specifications and it
is not a reference implementation.
## Issues:
There are no issues requiring board attention at this time
## Activity:
Apache Jackrabbit Oak receives most attention nowadays. All
maintenance branches and the unstable development branch are
continuously seeing moderate to high activity.
Apache Jackrabbit itself is mostly in maintenance mode with most of
the work going into bug fixing and tooling. New features are mainly
driven by dependencies from Oak.
This quarter saw the first few unstable releases from the 1.9 branch,
which will eventually be leading to the next major release.
There is currently an effort under way so simplify Oak deployments
by supporting a broader range of Guava versions, which Oak depends on.
Also modularisation is being further improved by refactoring and
decoupling individual components.
On the other end of the spectrum there is ideas, prototyping and
evaluations being done regarding cloud friendly persistence back-ends.
## 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 50 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Robert Munteanu on Mon May 22 2017
## Committer base changes:
- Currently 50 committers.
- No new committers added in the last 3 months
- Last committer addition was Alex Deparvu at Fri Jun 09 2017
## Releases:
- oak-1.2.29 was released on Mon Mar 12 2018
- oak-1.0.42 was released on Wed Mar 21 2018
- oak-1.4.21 was released on Wed Apr 04 2018
- oak-1.6.11 was released on Wed Apr 04 2018
- oak-1.6.12 was released on Mon May 28 2018
- oak-1.8.3 was released on Fri May 11 2018
- oak-1.8.4 was released on Thu Jun 07 2018
- oak-1.9.0 was released on Mon Apr 23 2018
- oak-1.9.1 was released on Thu May 10 2018
- oak-1.9.2 was released on Mon May 21 2018
- oak-1.9.3 was released on Mon Jun 04 2018
- jackrabbit-2.10.8 was released on Mon Jun 04 2018
- jackrabbit-2.12.9 was released on Mon May 07 2018
- jackrabbit-2.14.5 was released on Mon Apr 16 2018
- jackrabbit-2.17.2 was released on Wed Apr 04 2018
- jackrabbit-2.17.3 was released on Fri May 11 2018
## JIRA activity:
- 265 JIRA tickets created in the last 3 months
- 225 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AI: 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 issue requiring board attention at this time
## Activity:
- We released new major milestone: 4.2.0, it's an very important step forward in our release cycle.
- We revamped the website and created a #karaf room on The ASF Slack
- We are preparing new Cave and Decanter releases, including new features requested by users
- We still have lot of interactions with other communities from Apache (from Apache, like jclouds, sling), and others (OpenHAB, OpenDaylight, ...)
## Health report:
- We can note increased messages and feedback from users.
## 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.
- Francois Papon was added as a committer on Sat May 19 2018
## Releases:
- 4.2.0 was released on Mon Apr 09 2018
## Mailing list activity:
We can note a constant activity.
- dev@karaf.apache.org:
- 185 subscribers (down -4 in the last 3 months):
- 148 emails sent to list (223 in previous quarter)
- issues@karaf.apache.org:
- 43 subscribers (up 1 in the last 3 months):
- 909 emails sent to list (1219 in previous quarter)
- user@karaf.apache.org:
- 363 subscribers (down -10 in the last 3 months):
- 481 emails sent to list (434 in previous quarter)
## JIRA activity:
- 117 JIRA tickets created in the last 3 months
- 91 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AJ: Report from the Apache Labs Project [Danny Angus]
## Description
Apache Labs exists to incubate small and emerging projects from ASF
committers.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
Labs has at last become host to a new lab! "Turbulence" from
maintainer jpgilaberte.
Turbulence is Chaos Engineering engine for testing
distributed environments based on Apache Mesos.
- Test high availability cases (HA).
- Test fault tolerance cases (FT).
- Error prediction cases in the underlying technologies.
- HA benchmarks, FT capabilities regarding different
distributed architectures.
- Productive environment sizing.
- Environment behaviour understanding.
This is the trigger for PMC to start some modernisation activity. I
Have reached out to users@infra.a.o for advice on github integration,
I intend to engage with the board vis a vis options to overcome
the "no release" strictures, and I intend to revisit the permalink
issue, I don't think that requires board attention.
I have also created a mailinglist "tech@labs.a.o" to attempt to do some
outreach into the commiters and members. It was sparked by a thread on
members@ round the AGM where a recent member bemoaned the lack of a
place where in depth discussions of tech without specific project goals
was on topic.
I have yet to launch it, need to figure out how to publicise it and
get it to critical mass. Sally suggested inviting people to do
"fast feather" posts that could spawn threads, and I thought maybe
hosting AMAs with people might be interesting.
## Health report:
- Labs is quiet, still, but moving along a positive vector.
## 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.
- Juan P. Gilaberte was added as a committer on Wed May 30 2018
## Releases:
- In accordance with our charter, Labs makes no releases
-----------------------------------------
Attachment AK: Report from the Apache Libcloud Project [Tomaž Muraus]
## Description:
Libcloud is a Python library that abstracts away the differences among
multiple cloud provider APIs.
## Issues:
There are no issues which require board attention at this time.
## Activity:
Project continues to receive a good amount of activity and contributions.
In May 2018, Quentin Pradet has joined us as a PMC member. Recently, Quentin
started a voting thread for a new committer so we also expect new committer
to join our project in the near future.
## PMC changes:
- Currently 14 PMC members.
- Quentin Pradet was added to the PMC on Mon May 14 2018
## Committer base changes:
- Currently 20 committers.
- No new committers added in the last 3 months
- Last committer addition was Quentin Pradet at Thu Sep 21 2017
## Releases:
- 2.3.0 was released on March 03, 2018
- 2.2.1 was released on September 21, 2017
- 2.2.0 was released on September 04, 2017
-----------------------------------------
Attachment AL: Report from the Apache Lucene Project [Adrien Grand]
## Description:
- Lucene Core is a search-engine toolkit
- Solr is a search server built on top of Lucene Core
## Issues:
- There are no new issues requiring board attention at this time.
## Activity:
The upcoming Lucene 7.4 will include:
- support for soft deletes[1], which allows to keep deleted documents around
for an arbitrarily long time.
- a new FeatureField[2] which makes it easy and efficient to incorporate
static relevance signals into the score (think pagerank for instance).
There are ongoing discussions to support dynamic signals[3] as well such as
recency or geo distance.
- a new ConditionalTokenFilter[4] which allows to put conditions in analysis
chains.
- a Korean analyzer[5] which performs much better than other alternatives
that we are aware of.
The upcoming Solr 7.4 will include:
- more stream evaluators, in particular one for Fourier transform[6] and
another one to compute geo distances.
- support for child roll-ups[8].
- an upgrade to log4j 2[9], log4j 1 being end-of-life.
- We implemented a new process to bad-apple tests that fail too regularly in
order to get builds back to green so that the volume of failures is easier
to process by humans. At the same time, we added reporting of disabled
tests to make sure they do not get forgotten.
- Both user and dev mailing-lists are very active.
- Discussions are generally flowing in a good shape.
- We produced 3 releases since the last report.
[1] https://issues.apache.org/jira/browse/LUCENE-8200
[2] https://issues.apache.org/jira/browse/LUCENE-8197
[3] https://issues.apache.org/jira/browse/LUCENE-8340
[4] https://issues.apache.org/jira/browse/LUCENE-8273
[5] https://issues.apache.org/jira/browse/LUCENE-8231
[6] https://issues.apache.org/jira/browse/SOLR-12266
[7] https://issues.apache.org/jira/browse/SOLR-12273
[8] https://issues.apache.org/jira/browse/SOLR-8998
[9] https://issues.apache.org/jira/browse/SOLR-7887
## PMC changes:
- Cao Mạnh Đạt was added to the PMC on April 2nd.
- Currently 49 PMC members.
## Committer base changes:
- No new committers.
- Last committer we added was Jason Gerlowski on February 8th 2018.
- We had one failed vote, and there is one ongoing vote.
- Currently 72 committers.
## Releases:
- Lucene/Solr 6.6.4 was released on May 18th.
- Lucene/Solr 7.3.0 was released on April 4th.
- Lucene/Solr 7.3.1 was released on May 15th.
- There is an ongoing discussion to release 7.4.0.
-----------------------------------------
Attachment AM: Report from the Apache Lucene.Net Project [Prescott Nasser]
We've engaged the Lucene.Net community of the dev and user mailing lists in
discussions about the future of the project and people are showing interest in
helping out.
With this board meeting we are asking the board to make Shad the new chairman
of the Lucene.Net PMC and want to thank Prescott for his duty.
-----------------------------------------
Attachment AN: 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:
Close to the previous report, the final issues for Marmotta 3.4.0 have been
resolved and finally 3.4.0 has been released.
## Health report:
The project was considered feature-complete in 3.3.0. The current release
cycle (3.4.0) focuses on refining and fixing bug, plus incorporation some new
non-core features. Besides the work done towards 3.4.0 and the release itself,
no significant development activities have taken place. The VOTE for 3.4.0 had
good resonance, in total 9 votes were cast (7 binding)
## 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:
- 115 subscribers (down 1 since last report):
- 15 emails sent to list (10 in previous report)
- dev@marmotta.apache.org:
- 100 subscribers (down 2 since last report):
- 27 emails sent to list (15 in previous report)
## JIRA activity:
- 1 JIRA tickets created in the last 3 months
- 1 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AO: 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, A new major feature has been added to
Mnemonic codebase that this new feature fill in the missing building
block of handling large amount linked objects that can not be fully
loaded to system memory or the memory footprint may cause system
performance downgrading. our solution offers Mnemonic users a way
to offload part of cool linked objects from heap in durable object level
without destroying them from durable memory space. this approach allows
user to keep the reference to this durable object while free up the
memory resources that occupied by its object graphs referred by the
durable object.
With the support of our community contributors, the Apache Mnemonic has
been presented in OSTS2018 and posted in AIDev conference
The Mnemonic code has become stable again and is ready for next release,
so the v0.12 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.
- 1 new PMC member added in the last 1 months.
Committer Base Changes:
- Currently 13 committers.
- No new committer added since the last reporting.
Releases:
- Last release was v0.11.0 on Apr.02 2018
- Still active development on next major version (0.12.0)
JIRA Activity:
- 17 JIRA tickets created since the last report (Mar. 2018)
- Also 15 JIRA tickets closed/resolved this period
Sincerely,
Gang(Gary) Wang on behalf of the Apache Mnemonic PMC
-----------------------------------------
Attachment AP: Report from the Apache Mynewt Project [Justin Mclean]
-----------------------------------------
Attachment AQ: Report from the Apache OFBiz Project [Jacopo Cappellato]
## Description:
Apache OFBiz is an open source enterprise automation software project
## Issues:
There are no issues requiring board attention at this time
## Activity:
- The stabilization of the new release branch, 17.12, is proceeding well but
we still don't have scheduled a date for the releases
- Vulnerability reports: a new report was received on the 1st of June 2018; at
the moment the security team is working on it; the other vulnerability
report that the team was reviewing at the time of our previous report to the
ASF Board has been discarded as invalid and no further action will be taken
for it
- The documentation initiative: documentation discussions have been moved to
the dev mailing list and an umbrella JiRA task has been created to help
consolidate and track all documentation related work; a documentation style
guide has been created based on asciidoc best practices; over the last month
work has slowed a little and we plan to focus on reviving community
involvement
- We continue to monitor for any brand or trademark violations: we do not have
anything new on this
- Various bug fixes and enhancements have been contributed and committed to
the trunk
- As usual, more details about the community activities are published in the
official blog [1], on Twitter [2] and other social media [3]; our public
HipChat room [4] has seen low activity as in the previous quarter
## Health report:
As anticipated in our previous report to the ASF Board, we have invited a new
PMC member; as usual, the PMC is monitoring and discussing new candidates for
the PMC and the committers' groups; the community is actively involved in
various discussions and support requests, posted mostly in the mailing list
and in Jira.
## PMC changes:
- Currently 20 PMC members.
- Paul Foxworthy was added to the PMC on Mon Mar 19 2018
## Committer base changes:
- Currently 43 committers.
- No new committers added in the last 3 months
- Last committer addition was Akash Jain at Wed Aug 09 2017
## Releases:
- Last release was 16.11.04 on Tue Jan 02 2018
## Mailing list activity:
The number of subscriptions to the user and dev list is slightly decreasing
but the number of emails exchanged is rather high in all lists.
- dev@ofbiz.apache.org:
- 574 subscribers (down -6 in the last 3 months):
- 565 emails sent to list (663 in previous quarter)
- notifications@ofbiz.apache.org:
- 78 subscribers (up 0 in the last 3 months):
- 1582 emails sent to list (2333 in previous quarter)
- user@ofbiz.apache.org:
- 926 subscribers (down -10 in the last 3 months):
- 572 emails sent to list (508 in previous quarter)
## JIRA activity:
- 154 JIRA tickets created in the last 3 months
- 99 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
-----------------------------------------
Attachment AR: Report from the Apache Olingo Project [Christian Amend]
## Description:
Apache Olingo is a Java and JavaScript library that implements the Open Data
Protocol (OData). Apache Olingo serves client and server aspects of OData. It
currently supports OData 2.0 and OData 4.0. The latter is the OASIS version of
the protocol: OASIS Open Data Protocol (OData) TC.
## Olingo Status
Olingo has no issues that would require board attention.
There are no new releases as the OData V4.01 specification is still not final.
As we saw no community requests for patch releases we did not create any.
The discussions and questions on the users list are declining and revolve
mostly about small issues with the library or questions about entirely new
extensions like a JPA extension for the V4 library. JIRA issues are still
created on a low basis and contain mostly bug reports.
## PMC changes:
- Currently 13 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Ramesh Reddy on Thu Oct 08 2015
## Committer base changes:
- Currently 25 committers.
- No new committers added in the last 3 months
- Last committer addition was Archana Rai at Fri May 26 2017
## Releases:
- Last release was 4.4.0 on Fri Sep 01 2017
## Mailing list activity:
- dev@olingo.apache.org:
- 86 subscribers (up 0 in the last 3 months):
- 139 emails sent to list (154 in previous quarter)
- user@olingo.apache.org:
- 194 subscribers (up 2 in the last 3 months):
- 16 emails sent to list (37 in previous quarter)
## JIRA activity:
- 23 JIRA tickets created in the last 3 months
- 19 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AS: 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.2 on March 5th 2018
- A new PMC chair (Imesha Sudasingha) was elected in April, 2018. (Previous
chair - Tom Barber)
Improved activity compared to last reporting periods with improvements being
made on stabilizing Avro RPC implementations of OODT components and improving
logging support for OODT. Furthermore, Apache DRAT GSoC student is making
improvements to OODT APIs in order to use OODT functionalities though REST
APIs.
All these new additions will affect towards OODT being an easy to use platform
for scientific data systems in near future.
## Health report:
We are currently working on 1.9 release which will be the last in line before
completely removing XML RPC code from the project. As per now, once the above
mentioned logging improvements are done and workflow manager and resource
manager are stabilized, we are ready to release 1.9. Hopefully within the next
reporting period.
So, project activity is below average with few contributors making constant
contributions throughout the period.
## 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:
- Last release was 1.2.2 on Mon Mar 05 2018
## Mailing list activity:
Most of the mailing list activities are related to improvements that being
done for 1.9 release.
- dev@oodt.apache.org:
- 91 subscribers (down -1 in the last 3 months):
- 156 emails sent to list (74 in previous quarter)
## JIRA activity:
- 11 JIRA tickets created in the last 3 months
- 3 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AT: 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:
- Team working towards next 1.8.5 release and OpenNLP 2.0
- Work on a proof-of-concept Deep Learning NER component started and is
currently being evaluated
- Suneel Marthi presented at Dataworks Summit, Berlin on April 19 2018 about
Streaming pipelines for Neural Machine Translation leveraging Apache
OpenNLP for SLangiuentence Detection, Tokenization, Language Detection from
an Apache Flink streaming pipelines.
## 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:
- Last release was 1.8.4 on Mon Dec 25 2017
## JIRA activity:
- 14 JIRA tickets created in the last 3 months
- 19 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AU: Report from the Apache OpenWebBeans Project [Mark Struberg]
## Description:
Apache OpenWebBeans is an ALv2-licensed implementations of the
"Contexts and Dependency Injection for the Java EE platform"
specifications which are defined as JSR-299 (CDI-1.0), JSR-346
(CDI-1.1 and CDI-1.2 MR) and JSR-365 (CDI-2.0).
The OWB community also maintains a small server as
Apache Meecrowave subproject. Meecrowave 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 have been busy doing gradual updates and also did a released
for EE7 for inclusion in the upcoming Apache TomEE-7.0.5 release.
So we actually do a lot of work for the TomEE community as well.
Via the Meecrowave users we also got a few bug reports for CXF
which we forwarded resp shipped patches for.
We now wait for this release to ship the next MW release.
## Health report:
Health is ok for such an 'old' project. Otoh we are now almost
10 years old and still have a lot of drive and there is no
end in sight.
## 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:
- 1.7.5 was released on Wed May 02 2018
- 2.0.5 was released on Wed May 02 2018
## Mailing list activity:
- dev@openwebbeans.apache.org:
- 69 subscribers (up 0 in the last 3 months):
- 193 emails sent to list (202 in previous quarter)
- user@openwebbeans.apache.org:
- 97 subscribers (up 0 in the last 3 months):
- 7 emails sent to list (49 in previous quarter)
## JIRA activity:
- 21 JIRA tickets created in the last 3 months
- 28 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AV: Report from the Apache Perl Project [Philippe Chiasson]
-----------------------------------------
Attachment AW: Report from the Apache Pig Project [Koji Noguchi]
## Description:
Apache Pig is a platform for analyzing large data sets on Hadoop. It
provides a high-level language for expressing data analysis programs,
coupled with infrastructure for evaluating these programs.
## Issues:
- There are no issues requiring board attention at this time
## Activity:
- Activity continues to be low and no new release for almost an year.
Planning to address that with a major release 0.18 with support for
bytecode optimization, more scalable bloom join, Hadoop 3 support etc next
quarter some of which have been worked on in the past year.
- SIGMOD 2018 software systems award has been granted to Hive and Pig
database systems
(https://sigmod2018.org/sigmod_awards.shtml at the bottom) The awardees are
the initial authors of the original paper before it was contributed to
Apache.
## 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 30 committers.
- No new committers added in the last 3 months
- Last committer addition was Ádám Szita at Sat May 20 2017
## Releases:
- Last release was 0.17.0 on Thu Jun 15 2017
## Mailing list activity:
- dev@pig.apache.org:
- 385 subscribers (down -10 in the last 3 months):
- 200 emails sent to list (345 in previous quarter)
- user@pig.apache.org:
- 1093 subscribers (down -19 in the last 3 months):
- 20 emails sent to list (2 in previous quarter)
## JIRA activity:
- 10 JIRA tickets created in the last 3 months
- 8 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AX: Report from the Apache Pivot Project [Roger Lee Whitcomb]
Description:
Apache Pivot is an open-source platform for building installable Internet
applications (IIAs). It combines the enhanced productivity and usability
features of a modern user interface toolkit with the robustness of the
Java platform.
Issues:
There are no board-level issues at the moment.
Activity:
One new potential developer showed up this quarter, so mailing lists
are up by one. Development of the next version (2.1) is still ongoing,
although slower than last quarter. I anticipate an attempt to release
in a few weeks time.
Health Report:
Basically unchanged since the last report. Users are still generally
quiet. Development on the next version is still ongoing.
PMC Changes:
- Currently 4 PMC members.
- No new PMC members added in the last 3 months.
- Last PMC re-addition was Niclas Hedhman on Wed Jan 13 2016.
Committer Base Changes:
- Currently 9 committers.
- No new changes to the committer base since last report.
- No new committers added in the last 3 months
- Last committer addition was more than 2 years ago
Releases:
- Last release was 2.0.5 on Mon Jul 3 2017
- Still active development on next major version (2.1)
Mailing List Activity:
- All mailing list activity (except private@) is down this quarter,
even though we gained a subscriber. Note: these numbers are from
the reporter app.
- dev@pivot.apache.org
- 62 subscribers (up +1 from last report)
- 48 emails sent to list (270 in previous quarter)
- user@pivot.apache.org
- 171 subscribers (up +1 from last report)
- 4 emails sent to list (15 in previous quarter)
- commits@pivot.apache.org
- 19 subscribers (unchanged from last time)
- 56 emails this quarter (vs. 151 in last quarter)
-----------------------------------------
Attachment AY: Report from the Apache Polygene Project [Paul Merlin]
-----------------------------------------
Attachment AZ: Report from the Apache Portable Runtime (APR) Project [Nick Kew]
## Description:
- The Apache Portable Runtime (APR) project creates and maintains
software libraries that provide a predictable and consistent interface
to underlying platform-specific implementations. There are three
sub-projects: APR, APR-UTIL and APR-ICONV, of which the first two
are the main focus of developer interest.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
- This has been a quiet period in a stable project with a slow but
comfortable life cycle. Activity has been low.
## Health report:
- Following a new release and a followup release for errata in 2017,
activity has fallen back to a now-customary low level. The
underlying condition of the project remains quiet but healthy.
## PMC changes:
- Currently 41 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Evgeny Kotkov on Tue Sep 12 2017
## Committer base changes:
- Currently 67 committers.
- No new committers added in the last 3 months
- Last committer addition was Evgeny Kotkov at Wed Sep 13 2017
## Releases:
- None in the period. Last release was a joint release of
APR-1.6.3, APR-UTIL-1.6.1 and APR-ICONV-1.2.2 in October 2017.
## Mailing list activity:
- The subscriber base remains stable. Activity is sharply down
as described above.
- dev@apr.apache.org:
- 334 subscribers (down -2 in the last 3 months):
- 82 emails sent to list (60 in previous quarter)
- bugs@apr.apache.org:
- 20 subscribers (up 0 in the last 3 months):
- 52 emails sent to list (42 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
- 5 Bugzilla tickets resolved in the last 3 months
-----------------------------------------
Attachment BA: Report from the Apache Portals Project [David Sean Taylor]
## Description:
Apache Portals exists to promote the use of open source portal technology.
We
intend to build freely available and interoperable portal software in order
to
promote the use of this technology. With the Pluto project, we provide a
reference implementation for the Java portlet standard. The Jetspeed
project is
a full feature enterprise open source portal. The Portals Applications
project
is dedicated to providing robust, full-featured, commercial-quality, and
freely
available portlet applications.
## Activity:
Apache Portals released 0 releases since the last report.
Pluto: A Security Vulnerability Report was logged against Pluto 3.0.0 by
the Apache Security Team (Mark J. Cox) titled “Unauthenticated Remote Code
Execution". This issue has been fixed and is scheduled to be released again
(after a failed attempt in May) this weekend (June 16-17, 2018) in a Pluto
version 3.0.1 release. Development and refinement and testing with the
Portlet 3.0 TCK is finalizing. Expecting a 3.0.1 version will be released
with next report.
Pluto: JIRA issues were closed and bugs fixed.
No additional members since last report
12 Feb 2017 - Two new PMC members added
27 April 2017 - Apache Portals Pluto team released Pluto Maven Archetypes
3.0 to support to developing new portlets to the new 3.0 spec
## Mailing list activity:
Not much activity. Some discussions around TCK implementation on the Pluto
list.
Low volume activity on the Jetspeed lists.
## Issues:
We have no board-level issues at this time.
## PMC/Committership changes:
Last Added PMC Members:
12 Feb 2017 - Scott Martin Nicklaus
12 Feb 2017 - Neil Griffin
Last Added Committers:
05 August 2016 Mohd Ahmed Kahn
11 Dec 2014 Martin Scott Nicklous
11 Dec 2014 Neil Griffin
## Releases:
Pluto 3.0.1 - in progress
Pluto Maven Archetype 3.0.0 - 27 April 2017
Pluto 3.0.0 - 18 January 2017
Jetspeed 2.3.1- 09 May 2016
-----------------------------------------
Attachment BB: Report from the Apache PredictionIO Project [Donald Szeto]
## Description:
- PredictionIO is an open source Machine Learning Server built on top of
state-of-the-art open source stack, that enables developers to manage and
deploy production-ready predictive services for various kinds of machine
learning tasks.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- Continued community support and driving for contributions.
- 2018 roadmap posted to dev ML.
- Most automatic tests ported from Travis to ASF Jenkins.
## 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.
- Latest committer addition was Mars Hall on Wed Jul 12 2017
## Releases:
- Last release was 0.12.1 on Sat Mar 10 2018
## JIRA activity:
- 4 JIRA tickets created in the last 3 months
- 3 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment BC: Report from the Apache Royale Project [Harbs]
## DESCRIPTION
Apache Royale is a new implementation of the principles of Apache Flex but
designed for JavaScript runtimes instead of Adobe Flash/AIR runtimes. Apache
Royale is designed to improve developer productivity in creating applications
for wherever Javascript runs, including browsers as well as Apache Cordova
applications, Node, etc.
## ISSUES
There are no issues requiring board attention at this time.
## RELEASES
- Apache Royale 0.9.2 was released on March 16 2018.
- Apache Royale 0.9.3 in progress.
## ACTIVITY
- No releases this quarter although 0.9.2 was released between the report and
the board meeting. 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 reslove 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.
## 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:
Both user and dev lists have seen healthy growth:
- users@royale.apache.org:
- 58 subscribers (up 11 in the last 3 months):
- 657 emails sent to list (475 in previous quarter)
- dev@royale.apache.org:
- 75 subscribers (up 7 in the last 3 months):
- 1768 emails sent to list (1952 in previous quarter)
-----------------------------------------
Attachment BD: Report from the Apache Sentry Project [Alex Kolbasov]
## Description:
Apache Sentry is a highly modular system for providing fine grained role based
authorization to both data and metadata stored on an Apache Hadoop Cluster.
## Issues:
There was a question asked by ASF board earlier about handling of licenses.
Here is a clarification of the issue.
Apache Sentry now uses an automated license generation process in place which
creates a license file adding pointers to the dependency's license within the
distribution. When sentry is build, license-maven-plugin which kicks in
package stage of mvn and gathers the license information of all the jars that
re ditributed. Here is the license information that Apache Sentry currently
uses/ License file is generated in sentry-dist which will have the license
information from top level LICENSE.txt and license details of all the third
party jars distributed and the path to their license files. Currently sentry
is distributing jars with licenses listed below
1. BSD License
2. 2-Clause BSD License
3. 3-Clause BSD License
4. CDDL 1.0
5. CDDL 1.1
6. Eclipse Public License
7. MIT License
8. Mozilla Public License
license-maven-plugin that is used does not provide all the information that
isneeded as the license information for a bunch of dependencies was not found.
Apache Sentry team have gone through an exercise of finding the license
information for such dependencies manually and used them as an overrides.
These steps has to be done before ever new release to make sure that license
information for the dependencies that changes are updated properly.
There are no other issues requiring board attention at this time
## Activity:
- Development work for 2.1 release mostly around adding support for
fine-grained privileges in Hive
- Discussions about implementing tag-based column masking
## 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 39 committers.
- No new committers added in the last 3 months
- Last committer addition was Na Li at Mon Feb 05 2018
## Releases:
- 2.0.0 was released on Dec 7 2017
- 1.7.1 on Sat Dec 23 2017
## Mailing list activity:
Most of the activity is around 2.1 release features.
- dev@sentry.apache.org:
- 90 subscribers (down -4 in the last 3 months):
- 539 emails sent to list (530 in previous quarter)
- issues@sentry.apache.org:
- 22 subscribers (up 0 in the last 3 months):
- 1025 emails sent to list (856 in previous quarter)
## JIRA activity:
- 109 JIRA tickets created in the last 3 months
- 59 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment BE: 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 finally released, now that
Subversion's release is done. I expect this new release to be available
before the next report.
## Health report:
Activity is at a normal, fairly quiet level.
## PMC & Committer changes:
Currently 12 PMC members and 13 committers. We added Evgeny Kotkov
as Committer and PMC member last April.
## Releases:
Apache Serf 1.3.9 was released on Thu Sep 01 2016
## Mailing list and Jira activity:
Normal slow activity.
-----------------------------------------
Attachment BF: 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 and 1 set of Specs.
- We focus currently on ServiceMix 7 and upgrading preparing the new release
containing the newest versions of Apache Karaf and Apache Camel.
- Our goal for the next months is also to improve the documentation and examples,
which is our still outstanding theme.
## Health report
- Activity on the mailing lists and in JIRA is on the same level like in the last
period. We had some contributions.
## PMC changes
- Currently 23 PMC members.
- Andrea Cosentino was added to the PMC on Wed Mar 15 2017
## Committer base changes
- Currently 50 committers.
- No new committers added in the last 3 months
- Last committer addition was Andrea Cosentino at Sun Mar 13 2016
## Releases
- Apache ServiceMix Specs 2017.12 on April 03 2018
- Apache ServiceMix Bundles 2018.03 on April 03 2018
- Apache ServiceMix Bundles 2018.04 on May 09 2018
- Apache ServiceMix Bundles 2018.05 on June 07 2018
## JIRA activity
- 85 JIRA tickets created in the last 3 months
- 85 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment BG: 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
- There is more interesting in translating shiro.apache.org to
Chinese, but nothing concrete yet.
- 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 BH: 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 also released
Sling IDE Tooling for Eclipse 1.2.2 with bugfixes.
The "Apache Sling and friends" conference - adaptTo - will take place this
year in Potsdam, Germany on 10-12 september. We view this event as an
opportunity to gather more community around Sling ( also Jackrabbit and Felix
).
Sling is participating in the GSOC, more details in SLING-2759 .
## Health report:
Good activity level overall, contributions from different people continue.
## PMC changes:
- Currently 21 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Konrad Windszus on Sat Oct 01 2016
## Committer base changes:
- Currently 43 committers.
- A. J. David Bosschaert was added as a committer on Fri Mar 09 2018
## Releases:
- Apache Sling Commons Log 5.1.4 was released on Mon Mar 26 2018
- Apache Sling Commons Log 5.1.6 was released on Fri Apr 27 2018
- Apache Sling Context-Aware Configuration Impl 1.4.12, Maven Sling Plugin
2.3.6 was released on Mon May 07 2018
- Apache Sling Feature 0.1.0 was released on Wed May 09 2018
- Apache Sling Feature-Analyser 0.1.0 was released on Wed May 09 2018
- Apache Sling Feature-IO 0.1.0 was released on Wed May 09 2018
- Apache Sling Feature-ModelConverter 0.1.0 was released on Wed May 09 2018
- Apache Sling File System Resource Provider version 2.1.14 was released on
Tue Apr 24 2018
- Apache Sling Form Based Authentication 1.0.10 was released on Tue May 22
2018
- Apache Sling IDE Tooling for Eclipse 1.2.2 was released on Wed May 09 2018
- Apache Sling JCR Content Parser 1.2.6, Sling Query 4.0.2 was released on
Sun May 06 2018
- Apache Sling JSP Taglib 2.3.0 was released on Tue May 22 2018
- Apache Sling Scripting HTL Engine 1.0.52-1.3.1 was released on Fri Mar 16
2018
- Apache Sling Scripting HTL Testing 1.0.8-1.3.1 was released on Fri Mar 16
2018
- Apache Sling Servlet Helpers 1.1.6 was released on Sat May 12 2018
- Apache Sling Servlets Get 2.1.32 was released on Wed May 23 2018
- Apache Sling Servlets Post 2.3.26 was released on Tue May 22 2018
- Apache Sling Starter Content 1.0.0 was released on Tue May 22 2018
- Apache Sling Starter Startup 1.0.6 was released on Tue May 22 2018
- Apache Sling Testing Clients 1.2.0 was released on Wed Apr 11 2018
- Apache Sling Testing OSGi Mock 2.3.8 was released on Fri Mar 23 2018
- Apache Sling Testing Rules 1.0.8 was released on Wed Apr 11 2018
- Apache Sling XSS Protection API 2.0.6 was released on Fri Mar 16 2018
- Commons HTML 1.0.2 was released on Sat May 12 2018
## JIRA activity:
- 182 JIRA tickets created in the last 3 months
- 137 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment BI: Report from the Apache SpamAssassin Project [Sidney Markowitz]
Apache SpamAssassin report to Board for June 2018
SpamAssassin is a mail filter to identify spam. The project provides a
framework/engine and regular rule updates that reflect the changing nature of
spam email seen in the wild. Updated rules are generated through a combination
of hand crafted contributions and automated processing of spam and anonymized
processed non-spam that are contributed by volunteers.
Health report:
The project activities are continuing smoothly with nothing that is both new
and notable to report.
We had one project proposal for GSoc 2018 accepted and started, but it failed
when no code was submitted to a repository in time for a hard deadline imposed
by the GSoc rules. The mentor and student intend to continue work on the
project outside of GSoc 2018.
Releases:
The last release was Apache SpamAssassin version 3.4.1 on 30 April 2015.
Note that we maintain online rule updates that are continuously updated
through a combination of developer contributions and automated processing via
our mass-check facility.
A release candidate for version 3.4.2 is imminent. At the time of writing of
this report, the rc is scheduled for release before the meeting of the Board.
We have previously said that this should be the last release of the 3.4 branch
before moving on with work towards 4.0, but a future 3.4.3 release is now
looking more likely in the balance of priorities to get 3.4.2 released.
Committer/PMC changes (none this quarter):
Most recent new committer:
Giovanni Bechis (gbechis) 15 February 2018
Most recent new PMC member:
Bill Cole (billcole) 5 March 2018
-----------------------------------------
Attachment BJ: Report from the Apache Stanbol Project [Fabian Christ]
-----------------------------------------
Attachment BK: Report from the Apache Storm Project [P. Taylor Goetz]
## Description:
- Apache Storm is a distributed real-time computation system.
## Issues:
## Activity:
- The community released versions 1.2.2 and 1.1.3 this month.
- The 1.2.2 and 1.1.3 releases addressed the folowing CVEs:
* CVE-2018-8008: Apache Storm arbitrary file write vulnerability
* CVE-2018-1332: Apache Storm user impersonation vulnerability
- The community has discussed and plans to move forward with
releasing some components (e.g. Apache Kafka integration, etc.)
separately to speed up the release cycle and encourage more
contributors to get involved in the release process.
- The community continues to make progress toward a 2.0 release.
## Health report:
- Project activity continues to be fairly consistent, with periodic lulls and
bursts in activity.
- New contributors continue to engage and that engagement tends to keep up
activity levels, even as some contributors move on. We continue to expand
the PMC by regularly inviting new members.
## PMC changes:
- Currently 37 PMC members.
- New PMC members:
- Ethan Li was added to the PMC on Tue Apr 10 2018
- Roshan Naik was added to the PMC on Mon Apr 02 2018
## Committer base changes:
- Currently 38 committers.
- New commmitters:
- Ethan Li was added as a committer on Wed Apr 11 2018
- Roshan Naik was added as a committer on Tue Apr 03 2018
## Releases:
- 1.2.2 was released on Mon Jun 04 2018
- 1.1.3 was released on Mon Jun 04 2018
## JIRA activity:
- 109 JIRA tickets created in the last 3 months
- 100 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment BL: Report from the Apache Synapse Project [Isuru Udana]
## Description:
Apache Synapse is a high performance, flexible, lightweight Enterprise Service
Bus (ESB) and a mediation framework.
## Issues:
None identified.
## Activity:
We couldn’t get the release work going as expected in this quarter due to lack
of activity/cycles of the contributors.
However we expect to boost the activity of the project as WSO2 (the major
consumer of Apache Synapse) is willing to contribute again by providing bug
fixes and features they have done for their forked repository of Apache
Synapse. To encourage and make things much easier for the external
contributors, we are discussing to move our source repository to github.
## PMC changes:
- Currently 27 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Prabath Ariyarathna on Thu May 04 2017
## Committer base changes:
- Currently 34 committers.
- No new committers added in the last 3 months
- Last committer addition was Prabath Ariyarathna at Fri Feb 10 2017
## Releases:
- Last release was 3.0.1 on Sat Dec 09 2017
-----------------------------------------
Attachment BM: Report from the Apache Tajo Project [Hyunsik Choi]
## Description:
- Tajo is an open source big data warehouse system in Hadoop for processing
web-scale data sets.
## Issues:
- there are no issues requiring board attention at this time
## Activity:
- We are migrating the svn repository for tajo-site to git.
## 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:
- 101 subscribers (up 0 in the last 3 months):
- 10 emails sent to list (19 in previous quarter)
- issues@tajo.apache.org:
- 26 subscribers (up 0 in the last 3 months):
- 10 emails sent to list (2 in previous quarter)
- user@tajo.apache.org:
- 48 subscribers (down -1 in the last 3 months):
- 3 emails sent to list (2 in previous quarter)
-----------------------------------------
Attachment BN: Report from the Apache Tapestry Project [Thiago Henrique De Paula Figueiredo]
## Description:
- Apache Tapestry is a Java component-based web framework that features high
productivity, great code reuse, robust deployment, and terrific performance.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- It was another pretty slow quarter in terms of activity.
## PMC changes:
- Currently 11 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Bob Harner on Thu Apr 06 2017
## Committer base changes:
- Currently 26 committers.
- No new committers added in the last 3 months
- Last committer addition was Dmitry Gusev at Fri May 26 2017
## Releases:
- Last release was 5.4.3 on Sun Apr 23 2017
## Mailing list activity:
- users@tapestry.apache.org:
- 744 subscribers (down -5 in the last 3 months):
- 133 emails sent to list (75 in previous quarter)
- dev@tapestry.apache.org:
- 243 subscribers (down -1 in the last 3 months):
- 7 emails sent to list (21 in previous quarter)
## JIRA activity:
- 2 JIRA tickets created in the last 3 months
- 0 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment BO: 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:
Mailing list traffic was lower this quarter. And responsive rate was
not great.
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.
Currently there's an initial agreement from the two responsive PMC to
move the project to the Attic. 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 BP: 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.
- We have put together a day long Tomcat track at the ApacheCon EU
Roadshow.
## PMC changes:
- Currently 27 PMC members.
- Emmanuel Bourg was added to the PMC on Tue May 08 2018
## Committer base changes:
- Currently 45 committers.
- Igal Sapir was added as a committer on Sat May 19 2018
## Releases:
- Apache Tomcat 7.0.86 was released on Fri Apr 13 2018
- Apache Tomcat 7.0.88 was released on Fri May 11 2018
- Apache Tomcat 8.0.51 was released on Fri Apr 13 2018
- Apache Tomcat 8.0.52 was released on Tue May 08 2018
- Apache Tomcat 8.5.30 was released on Sat Apr 07 2018
- Apache Tomcat 8.5.31 was released on Thu May 03 2018
- Apache Tomcat 9.0.7 was released on Sat Apr 07 2018
- Apache Tomcat 9.0.8 was released on Thu May 03 2018
- Apache Tomcat Native 1.2.17 was released on Wed Jul 13 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
-----------------------------------------
Attachment BQ: Report from the Apache Traffic Control Project [David Neuman]
## Description:
- Apache Traffic Control can be used to build, monitor, configure, and
provision a large-scale content delivery network (CDN).
## Issues:
- Waiting on Infra to complete Graduation ticket:
https://issues.apache.org/jira/browse/INFRA-16631
- We have a release ready to be announced but PMC members can't upload
binaries to dist.apache.org until the infra ticket is complete and we get
the proper permissions.
## Activity:
- Worked on a press release announcing our graduation.
- Worked on figuring out what the next steps are for becoming a TLP
- Opened INFRA ticket to take care of incubator -> TLP migration
- Called the vote on the Traffic Control 2.2 release (waiting for Infra
ticket before announcing - see issues above)
- Agreed on versioning for next release, currently working on naming a
release manager and defining scope.
## Health report:
- Just became a TLP
- The entire community is very excited to graduate from the Incubator and
become a TLP
- The project is healthy.
## PMC changes:
- Currently 13 PMC members.
- No new PMC members added in the last 3 months
## Committer base changes:
- Currently 18 committers.
- No changes (the PMC was established in the last 3 months)
## Releases:
- Traffic Control 2.1 was released on 1/22/2018
- The vote for Traffic Control 2.2 was called as passed on 6/7/2018
- Traffic Control 3.0 is currently being defined.
-----------------------------------------
Attachment BR: 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 lists in line with previous quarter.
- Work continues on getting a new release out.
- Focus of the PMC remains on growing the community.
- A meet up was held in the Peoples Republic of China (in Shanghai), hosted by
DBAPlus: contributor (and PMC Member) Ming Liu gave a presentation to
introduce Apache Trafodion.
- On The Roaring Elephant podcast contributor Rohit Jain was interviewed
regarding the project and our product.
- Rotation of the role of release manager continues; the community thanks Ming
Liu for the activities on release 2.2.0. Contributor Sean Broeder has
volunteered to be the release manager for release 2.3.0.
## Health report:
- During last quarter across the board the number of postings to mailing lists
was slightly lower.
- Subscriptions to the (public) mailing lists showed a slight decline compared
to previous quarter.
- Social Media interest has slightly increased.
- The PMC regards the project as healthy.
## PMC changes:
- Currently 11 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Amanda K Moran on Wed Dec 20 2017
## 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:
- 2.2.0 was released on Sat Mar 10 2018
## Mailing list activity:
- dev@trafodion.apache.org:
- 103 subscribers (down -2 in the last 3 months):
- 231 emails sent to list (387 in previous quarter)
- codereview@trafodion.apache.org:
- 26 subscribers (down -1 in the last 3 months):
- 534 emails sent to list (609 in previous quarter)
- issues@trafodion.apache.org:
- 36 subscribers (down -1 in the last 3 months):
- 1154 emails sent to list (1040 in previous quarter)
- user@trafodion.apache.org:
- 107 subscribers (down -2 in the last 3 months):
- 19 emails sent to list (38 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 17 subscribers (down —1 in the last 3 months):
- Currently no automated insights in number of ml postings provided by
ComDev-reporter services.
## JIRA activity:
- 120 JIRA tickets created in the last 3 months
- 100 JIRA tickets closed/resolved in the last 3 months
## Social media activity
- Followers: 265 (+10)
- Tweets: 92 (+10)
- Likes: 73 (+7)
-----------------------------------------
Attachment BS: Report from the Apache Twill Project [Terence Yim]
-----------------------------------------
Attachment BT: Report from the Apache UIMA Project [Marshall Schor]
Board report for Apache UIMA, for June 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:
- Currently 24 committers.
- No new committers added in the last 3 months
- Last committer addition was William Colen at Wed Apr 19 2017
## Releases:
- UIMA Asynchronous Scaleout (UIMA-AS) 2.10.3 was released on Mon Apr 16 2018
- UIMA-DUCC 2.2.2 was released on Sun Mar 18 2018
- UIMA ConceptMapper addon 2.10.2 was released 27 April 2018
Activity: Java SDK, UIMA-FIT, UIMA-AS, DUCC, RUTA are actively being worked
on.
uimaFIT moved to GIT from SVN, the first project within UIMA to do so.
Mailing list activity remains moderate.
Community: The community continues to be moderately active.
Issues: No Board level issues at this time.
-----------------------------------------
Attachment BU: 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:
- Code contributed by a community member referenced in our previous board
report as well as code from another new community member has been committed
to the project. Both contributors will likely be pursued as committers if
they continue to show interest in VCL.
## Health report:
- Project health is largely in a steady state, though we continue to have a
small uptick in community participation.
## PMC changes:
- Currently 7 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Aaron Coburn on Tue Jun 19 2012
## Committer base changes:
- Currently 8 committers.
- No new committers added in the last 3 months
- Last committer addition was Young Hyun Oh at Sun Dec 08 2013
## Releases:
- Last release was 2.5 on Thu Aug 17 2017
- We are trying to finish up a few tasks to hopefully get a new release out
soon
## Mailing list activity:
- Contributions for community members and development efforts toward a new
release have contributed to an increase in dev list traffic.
- dev@vcl.apache.org:
- 124 subscribers (down -1 in the last 3 months):
- 122 emails sent to list (7 in previous quarter)
- user@vcl.apache.org:
- 164 subscribers (down -2 in the last 3 months):
- 3 emails sent to list (57 in previous quarter)
## JIRA activity:
- 14 JIRA tickets created in the last 3 months
- 17 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment BV: 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:
- Worked with Sally to issue a press release for Wicket 8 which was done
really quick and satisfactory (Thanks SK!)
- Wicket 8 was released
- A couple of tech interviews were done regarding the Wicket 8 release [1][2]
## Issues:
- No issues require board attention.
## Activity:
- Initial work on wicket 9 has started
- First issues for Wicket 8 have been fixed
## 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:
- Last release was 8.0.0 on May 16 2018
[1] https://www.infoworld.com/article/3
276606/java/apache-wicket-java-8-upgrade-only-partially-supports-lambdas.html
[2] https://thenewstack
.io/wicket-8-whats-new-and-whats-next-for-the-server-side-java-web-framework/
-----------------------------------------
Attachment BW: 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.
ISSUES FOR THE BOARD
None.
CURRENT ACTIVITY
Most activity has been through JIRA issue tracking. The email lists
have seen little activity.
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.
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
We continue to get requests for Xalan to support XSLT version 2. The
Xalan libraries currently support XSLT version 1. Feature ugrades and
migration will require more than a few committers.
The libraries need 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.
BRANDING ISSUES
None.
-----------------------------------------
Attachment BX: Report from the Apache Yetus Project [Allen Wittenauer]
## Description:
Apache Yetus provides libraries and tools that enable contribution and release
processes for software projects.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
No new PMC members added in the last three months; our Last PMC addition was
Ajay Yadav on Thu Dec 01 2016. There are currently 8 PMC members.
Akira Ajisaka was added as a committer on Tue Feb 06 2018. There are
currently 12 committers.
Since the last report, a few patches have been committed and some interest in
generating an 0.8.0 release.
## Health report:
Activity continues to be steadily trending down.
## Releases:
- 0.7.0 was released on Fri Jan 26 2018
## Mailing list activity:
- dev@yetus.apache.org:
- 44 subscribers (up 0 in the last 3 months):
- 30 emails sent to list (48 in previous quarter)
- notifications@yetus.apache.org:
- 16 subscribers (up 0 in the last 3 months):
- 142 emails sent to list (184 in previous quarter)
## JIRA activity:
- 25 JIRA tickets created in the last 3 months
- 13 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment BY: 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 versions 3.4.12 and 3.5.4 during the
reporting period:
- Release 3.4.12: This release fixes 22 issues, including issues that
affect incorrect handling of the dataDir and the dataLogDir as reported
in the previous version of the 3.4 branch.
- Release 3.5.4: 3.5.4-beta is the second beta in the planned 3.5 release
line leading up to a stable 3.5 release. It comprises 113 bug fixes and
improvements. The previous release of branch 3.5, release 3.5.3, added
a new feature ZOOKEEPER-2169 “Enable creation of nodes with TTLs”. There
was a major oversight when TTL nodes were implemented, and ZOOKEEPER-2901
fixes the issue.
## Health report:
- The community has released two new versions of Apache ZooKeeper, and has
Successfully worked towards those releases.
- The PMC has invited one new committer.
- Apache ZooKeeper meetup in the Bay Area hosted by Cloudera:
https://www.meetup.com/Bay-Area-Cloudera-User-Group/events/250182745/
- Mailing list is mostly stable, except for a spike on dev due to the
Coordination around the releases.
## 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.
- Andor Molnar was added as a committer on Fri Jun 01 2018
## Releases:
- 3.4.12 was released on Wed Apr 25 2018
- 3.5.4 was released on Wed May 16 2018
## Mailing list activity:
We had more activity on the dev list due to the two releases we
Have cut in the reporting period.
- dev@zookeeper.apache.org:
- 510 subscribers (down -2 in the last 3 months):
- 2454 emails sent to list (1847 in previous quarter)
- user@zookeeper.apache.org:
- 1230 subscribers (down -10 in the last 3 months):
- 194 emails sent to list (120 in previous quarter)
## JIRA activity:
- 63 JIRA tickets created in the last 3 months
- 51 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment BZ: Report from the Apache Attic Project [Jan Iversen]
## Description:
The Attic is where projects slumber when their communities fade away.
## Issues:
No public issues
## Activity:
Prolonged discussions on 2 (of 3) suggestions on how to make the technical
most elegant maintenance solution. Remark the original objective was to make
maintenance simpler and easy to do without the need for special tools.
## PMC changes:
- Currently 21 PMC members.
- Jan Iversen was added to the PMC on Wed Mar 15 2017
- Jan Iversen left the PMC on Wed May 19 2018
## Committer base changes:
- Currently 25 committers.
- No new committers added in the last 3 months
- Last committer addition was Jan Iversen at Thu Mar 16 2017
- Jan Iversen left the project on Wed May 19 2018
## Releases:
- No release can be made in attic
------------------------------------------------------
End of minutes for the June 20, 2018 board meeting.
Index