Index
Links: 2019 - All years
- Original The Apache Software Foundation
Board of Directors Meeting Minutes
December 18, 2019
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/40sr
The meeting was held via teleconference, hosted by the Secretary
via Zoom.
IRC #asfboard on irc.freenode.net was used for backup purposes.
2. Roll Call
Directors Present:
Rich Bowen
Shane Curcuru
Ted Dunning
Dave Fisher
Myrle Krantz
Daniel Ruggeri
Craig L Russell
Roman Shaposhnik
Directors Absent:
Danny Angus
Executive Officers Present:
Sally Khudairi
David Nalley
Tom Pappas
Sam Ruby
Matt Sicker
Executive Officers Absent:
none
Guests:
Daniel Gruno
Dirk-Willem van Gulik
Gavin McDonald
Greg Stein
Henri Yandell
Jim Jagielski
Paul Angus
Trevor Grant
3. Minutes from previous meetings
Published minutes can be found at:
http://www.apache.org/foundation/board/calendar.html
A. The meeting of November 20, 2019
See: board_minutes_2019_11_20.txt
Approved by General Consent.
4. Executive Officer Reports
A. Chairman [Craig]
Work continues to better understand how Apache can be more welcoming
to underrepresented communities. The 2019 Apache Diversity Survey has
been released. All committers should have received a personal
invitation to take the survey. If you have not done so already, please
help by taking the survey.
This has been a milestone year in many ways. I would like to thank our
sponsors, members, officers, contractors, contributors, and all our
volunteers for making Apache The Best Software Foundation. Raise a
glass for freedom; something they can never take away!
B. President [Sam]
Financially, expenses are more comfortably under-running budget than
they were last month; but income continues to under-run. It looks
like it will work out, but perhaps we should plan differently next
year.
Highlights for areas that I cover (David covers infra and TAC), where
highlights are things that are notably different than last month:
- Central services is working on a new landing page and on a number of
updates to existing pages.
- http://events.apache.org now shows an impressive line up of 2020
events
- Diversity survey launched and has received over 500 results to date
- Our first Outreachy intern has been selected
In the new year, I'll be looking to re-balance work with David. One
thing we have tentative agreement on is his taking the lead on the
FY21 budget. Additionally, I expect that David will take the lead in
the oversight of the Data Privacy role, should that resolution be passed
in its current form.
Additionally, please see Attachments 1 through 8.
@Gavin: document results of fundraising/TAC call
C. Treasurer [Myrle]
Operating Cash on November 30th, 2019 was $1,735K, which is up $34K
from last month’s ending balance (Oct 19) of $1,701K. Total Cash as
of Nov 30th, 2019 is $3,158.9K (includes the Pineapple, Restricted
Donation as well as the Tides Restricted Donations) as compared to
$3,599.9K on October 31st, 2018, (a decrease of $441K year over year).
The November 2019 ending Operating cash balance of $1,735K represents
an Operating cash reserve of 7.5 months based on the FY20 Cash
forecast average monthly spending of $229.8K/month. The ASF actual
Operating reserve of 7.5 months at the end of November 2019 is a bit
behind the budgeted 8 months of reserve for YTD through November 2019.
The estimated YE Operating reserve of 8.2 months is ahead of the
Budgeted YE reserve of 7.6 month. The ASF Operating reserve is above
the ASAE standard average of 6 months of reserve for Non Profits.
Reviewing the YTD Cash P&L, total Income is behind budget at this
point in the Fiscal year by $469.1K, partly due to ACNA19 Registration
income was behind but the budget but was, offset to a degree, by
ANCA 19 Sponsorship exceeding the budget. Public Donations are a bit
behind as is Foundation sponsorship due to some timing of payments (
The open Accounts Receivable is very healthy at $1,123.2K). As
compared to FY19, YTD revenue is behind by $95.9K primarily due to
timing of some Sponsor payments.
YTD expenses through November 30th, 2019 are under budget by $203.3K.
All departments are under budget, except for Conferences. As noted in
last month’s narrative the budgeted loss for ACNA19 was $55K and we
were estimating it to be in the $110K-$120K loss range, once all
expenses are in. As noted in the October Narrative, the estimated
loss for ACEU19 could be 107K Euros, however as ACEU19 took place in
October 2019, the final reconciliation is still being compiled.
Regarding Net Income (NI), YTD FY20 the ASF finished with a negative
<$668K> NI vs a budgeted negative <$402.2K> NI or $265.8K behind
Budgeted NI for FY20 at this point in the Fiscal year. This is
attributable to timing of Conference payments, Timing of TAC, Timing
of the Lease web payment as well as timing of Sponsor payments vs the
FY20 Budget. The cash forecast has been updated, with the information
we have at hand, and at this point more than halfway through the
Fiscal year, we are still on pace to meet our budget. I would urge
all dept heads to review, their depts in the Cash forecast, for the
last 5 months of the Fiscal year, and let us know if there is
anything that they are aware of that could change the estimates for
the remaining five months of FY2020. This effort will make the Cash
forecast a much more accurate management tool for the Foundation
With regard to FY19, we are behind in revenue, by $95.9K as noted
above, but we are also ahead on expenses by $693.7K (due to ACNA19 and
the Lease web payment which should have taken place in FY19, but did
not); thus, year over year NI for FY20 is behind FY19 by $789.6K. It
is estimated that this will even out, to a degree, as the FY20
progresses.
Current Balances:
Boston Private CDARS Account 2,265,241.60
Citizens Money Market 710,182.78
Citizens Checking 183,053.94
Paypal - ASF 414.57
Total Checking/Savings 3,158,892.89
Nov-19 Budget Variance
Income Summary:
Public Donations 14,157.66 6,502.09 7,655.57
Sponsorship Program 134,000.00 105,000.00 29,000.00
Programs Income 0.00 0.00 0.00
Conference/Event Income 3,287.10 180,000.00 -176,712.90
Other Income 0.00 0.00 0.00
Interest Income 481.92 400.00 81.92
Total Income 151,926.68 291,902.09 -139,975.41
Expense Summary
Infrastructure 64,701.09 95,733.08 -31,031.99
Programs Expense 0.00 3,333.33 -3,333.33
Publicity 11,340.31 52,738.34 -41,398.03
Brand Management 1,143.87 8,166.67 -7,022.80
Conferences 7,360.42 27,250.00 -19,889.58
Travel Assistance Committee 0.00 10,000.00 -10,000.00
Fundraising 11,420.01 16,080.00 -4,659.99
Treasury Services 3,350.00 3,350.00 0.00
General & Administrative 1,088.05 1,925.00 -836.95
Diversity and Inclusion 0.00 5,833.33 -5,833.33
Total Expense 100,403.75 224,409.75 -124,006.00
Net Income 51,522.93 67,492.34 -15,969.41
YTD FY20 Budget Variance
Income Summary:
Public Donations 29,502.03 110,581.82 -81,079.79
Sponsorship Program 479,000.00 687,000.00 -208,000.00
Programs Income 14,900.00 14,000.00 900.00
Conference/Event Income 516,012.91 700,000.00 -183,987.09
Other Income 0.00 0.00 0.00
Interest Income 6,132.99 3,050.00 3,082.99
Total Income 1,045,547.93 1,514,631.82 -469,083.89
Expense Summary
Infrastructure 610,705.11 642,131.56 -31,426.45
Programs Expense 1,158.53 23,333.31 -22,174.78
Publicity 243,696.17 288,713.38 -45,017.21
Brand Management 31,591.02 57,166.69 -25,575.67
Conferences 641,029.28 598,750.00 42,279.28
Travel Assistance Committee 43,092.21 105,000.00 -61,907.79
Fundraising 88,911.41 112,560.00 -23,648.59
Treasury Services 23,450.00 23,450.00 0.00
General & Administrative 29,974.10 24,915.00 5,059.10
Diversity and Inclusion 0.00 40,833.31 -40,833.31
Total Expense 1,713,607.83 1,916,853.25 -203,245.42
Net Income -668,059.90 -402,221.43 -265,838.47
D. Secretary [Matt]
In November, the Secretary received 50 ICLAs, two CCLAs, and two
software grants.
E. Executive Vice President [David]
As Sam noted in his report, I've agreed to start FY21 budget planning.
My current plan is to start this just after the new year.
Travel Assistance
=================
Travel Assistance is working on funding committers to attend FOSDEM as
part of their new-for-FY20 line item for committers.
Infrastructure
==============
Infrastructure appears close to filling the open req for a tech
writer/editor.
F. Vice Chairman [Shane]
Nothing of note to report this month.
Executive officer reports approved as submitted by General Consent.
5. Additional Officer Reports
A. VP of W3C Relations [Andy Seaborne / Ted]
See Attachment 9
B. Apache Legal Affairs Committee [Roman Shaposhnik]
See Attachment 10
C. Apache Security Team Project [Mark J. Cox / Rich]
See Attachment 11
D. VP of Data Privacy [John Kinsella / Shane]
See Attachment 12
E. VP of Jakarta EE Relations [Mark Struberg / Myrle]
No report was submitted.
@Roman: reach out to members@ for any interest in volunteering
Additional officer reports approved as submitted by General Consent.
6. Committee Reports
Summary of Reports
The following reports required further discussion:
# Labs [myrle]
# Lucene [df]
# PredictionIO [rb]
# Tajo [df]
# Travel Assistance [myrle]
A. Apache Airflow Project [Bolke de Bruin / Daniel]
See Attachment A
B. Apache Allura Project [David Philip Brondsema / Roman]
See Attachment B
C. Apache Any23 Project [Lewis John McGibbney / Craig]
See Attachment C
D. Apache Archiva Project [Olivier Lamy / Dave]
See Attachment D
E. Apache Atlas Project [Madhan Neethiraj / Danny]
See Attachment E
F. Apache Aurora Project [Renan DelValle / Roman]
See Attachment F
G. Apache Axis Project [Robert Lazarski / Craig]
See Attachment G
H. Apache Bahir Project [Luciano Resende / Daniel]
See Attachment H
I. Apache Beam Project [Kenneth Knowles / Dave]
See Attachment I
J. Apache Bigtop Project [Youngwoo Kim / Ted]
See Attachment J
K. Apache Bloodhound Project [Gary Martin / Danny]
No report was submitted.
@Myrle: pursue Attic resolution for Bloodhound
L. Apache BVal Project [Matthew Jason Benson / Shane]
See Attachment L
M. Apache Camel Project [Andrea Cosentino / Myrle]
See Attachment M
N. Apache Cayenne Project [Michael Ray Gentry / Rich]
See Attachment N
O. Apache Chemistry Project [Florian Müller / Danny]
See Attachment O
P. Apache CloudStack Project [Paul Angus / Myrle]
See Attachment P
Q. Apache Commons Project [Gary D. Gregory / Dave]
See Attachment Q
R. Apache Cordova Project [Jesse MacFadyen / Roman]
See Attachment R
S. Apache cTAKES Project [Pei Chen / Craig]
See Attachment S
T. Apache Curator Project [Jordan Zimmerman / Rich]
See Attachment T
U. Apache Eagle Project [Edward Zhang / Shane]
See Attachment U
V. Apache Felix Project [Karl Pauls / Daniel]
See Attachment V
W. Apache Flex Project [Olaf Krüger / Ted]
See Attachment W
X. Apache Flink Project [Stephan Ewen / Ted]
See Attachment X
Y. Apache Guacamole Project [Mike Jumper / Dave]
See Attachment Y
Z. Apache Gump Project [Stefan Bodewig / Rich]
See Attachment Z
AA. Apache Hama Project [Chia-Hung Lin / Myrle]
No report was submitted.
@Ted: pursue Attic resolution for Hama
AB. Apache Helix Project [Kishore G / Roman]
No report was submitted.
@Roman: pursue a report for Helix
AC. Apache Hive Project [Ashutosh Chauhan / Danny]
See Attachment AC
AD. Apache Incubator Project [Justin Mclean / Shane]
See Attachment AD
AE. Apache Jackrabbit Project [Marcel Reutegger / Daniel]
See Attachment AE
AF. Apache jUDDI Project [Alex O'Ree / Craig]
See Attachment AF
AG. Apache Karaf Project [Jean-Baptiste Onofré / Rich]
See Attachment AG
AH. Apache Labs Project [Danny Angus]
See Attachment AH
@Dave: pursue a roll call for Labs
AI. Apache Libcloud Project [Tomaž Muraus / Roman]
See Attachment AI
AJ. Apache Lucene Project [Cassandra Targett / Daniel]
See Attachment AJ
AK. Apache Lucene.Net Project [Shad Storhaug / Ted]
See Attachment AK
AL. Apache Mnemonic Project [Gang Wang / Myrle]
See Attachment AL
AM. Apache Mynewt Project [Justin Mclean / Dave]
See Attachment AM
AN. Apache NetBeans Project [Geertjan Wielenga / Danny]
See Attachment AN
AO. Apache OFBiz Project [Jacopo Cappellato / Craig]
See Attachment AO
AP. Apache Olingo Project [Michael Bolz / Shane]
See Attachment AP
AQ. Apache OODT Project [Imesha Sudasingha / Shane]
See Attachment AQ
AR. Apache OpenNLP Project [Jörn Kottmann / Daniel]
See Attachment AR
@Daniel: pursue a better report for next month
AS. Apache OpenWebBeans Project [Mark Struberg / Danny]
See Attachment AS
AT. Apache Petri Project [Dave Fisher]
See Attachment AT
AU. Apache Pig Project [Koji Noguchi / Dave]
No report was submitted.
AV. Apache Pivot Project [Roger Lee Whitcomb / Ted]
See Attachment AV
AW. Apache PLC4X Project [Christofer Dutz / Roman]
See Attachment AW
AX. Apache Portable Runtime (APR) Project [Nick Kew / Craig]
See Attachment AX
AY. Apache Portals Project [David Sean Taylor / Myrle]
See Attachment AY
AZ. Apache PredictionIO Project [Donald Szeto / Rich]
See Attachment AZ
@Rich: pursue a roll call for PredictionIO
BA. Apache Pulsar Project [Matteo Merli / Shane]
See Attachment BA
BB. Apache Royale Project [Piotr Zarzycki / Ted]
See Attachment BB
BC. Apache Sentry Project [Kalyan Kalvagadda / Dave]
See Attachment BC
BD. Apache ServiceMix Project [Krzysztof Sobkowiak / Danny]
See Attachment BD
BE. Apache Shiro Project [Les Hazlewood / Myrle]
See Attachment BE
BF. Apache SINGA Project [Wang Wei / Rich]
See Attachment BF
BG. Apache Sling Project [Robert Munteanu / Roman]
See Attachment BG
BH. Apache SpamAssassin Project [Sidney Markowitz / Daniel]
See Attachment BH
BI. Apache Stanbol Project [Rafa Haro / Craig]
No report was submitted.
BJ. Apache Storm Project [P. Taylor Goetz / Roman]
See Attachment BJ
BK. Apache Submarine Project [Wangda Tan / Myrle]
See Attachment BK
BL. Apache Synapse Project [Isuru Udana / Daniel]
See Attachment BL
BM. Apache Tajo Project [Hyunsik Choi / Dave]
See Attachment BM
@Sally: talk to Tajo about Attic
BN. Apache Tomcat Project [Mladen Turk / Danny]
See Attachment BN
BO. Apache Trafodion Project [Pierre Smits / Shane]
See Attachment BO
BP. Apache Twill Project [Terence Yim / Ted]
No report was submitted.
@Ted: pursue a report for Twill
BQ. Apache UIMA Project [Marshall Schor / Rich]
See Attachment BQ
BR. Apache Unomi Project [Serge Huber / Craig]
See Attachment BR
BS. Apache VCL Project [Josh Thompson / Dave]
See Attachment BS
BT. Apache Wicket Project [Andrea Del Bene / Rich]
See Attachment BT
BU. Apache Xerces Project [Michael Glavassevich / Myrle]
See Attachment BU
BV. Apache Yetus Project [Allen Wittenauer / Shane]
No report was submitted.
@Shane: pursue a report for Yetus
BW. Apache ZooKeeper Project [Flavio Paiva Junqueira / Daniel]
See Attachment BW
Committee reports approved as submitted by General Consent.
7. Special Orders
A. Change the Apache Calcite Project Chair
WHEREAS, the Board of Directors heretofore appointed Francis Chuang
(francischuang) to the office of Vice President, Apache Calcite, and
WHEREAS, the Board of Directors is in receipt of the resignation of
Francis Chuang from the office of Vice President, Apache Calcite, and
WHEREAS, the Project Management Committee of the Apache Calcite
project has chosen by vote to recommend Stamatis Zampetakis (zabetak)
as the successor to the post;
NOW, THEREFORE, BE IT RESOLVED, that Francis Chuang is relieved and
discharged from the duties and responsibilities of the office of Vice
President, Apache Calcite, and
BE IT FURTHER RESOLVED, that Stamatis Zampetakis be and hereby is
appointed to the office of Vice President, Apache Calcite, to serve in
accordance with and subject to the direction of the Board of Directors
and the Bylaws of the Foundation until death, resignation, retirement,
removal or disqualification, or until a successor is appointed.
Special Order 7A, Change the Apache Calcite Project Chair, was
approved by Unanimous Vote of the directors present.
B. New VP Data Privacy to serve at the direction of the President
WHEREAS, the Board of Directors deems it to be in the best interests
of the Foundation for the officers responsible for executing the
operations of the Foundation to serve in accordance with and subject
to the direction of the President; and
WHEREAS, the Board of Directors heretofore appointed John Kinsella
(jlk) to the office of "Vice President, Data Privacy", and
WHEREAS, the Board of Directors is in receipt of the resignation of
John Kinsella from the office of Vice President, Data Privacy.
NOW, THEREFORE, BE IT RESOLVED, that John Kinsella is relieved and
discharged from the duties and responsibilities of the office of Vice
President, Data Privacy, and be it further
RESOLVED that the office of "Vice President, Data Privacy" shall serve
at the direction of the President; and be it further
RESOLVED, that Dirk-Willem van Gulik be and hereby is appointed to the
office of "Vice President, Data Privacy", to serve in accordance with
and subject to the direction of the President and the Bylaws of the
Foundation until death, resignation, retirement, removal or
disqualification, or until a successor is appointed
Special Order 7B, New VP Data Privacy to serve at the
direction of the President, was approved by Unanimous Vote of
the directors present.
C. Establish the Apache Druid Project
WHEREAS, the Board of Directors deems it to be in the best interests of
the Foundation and consistent with the Foundation's purpose to
establish a Project Management Committee charged with the creation and
maintenance of open-source software, for distribution at no charge to
the public, related to analytical database software.
NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
(PMC), to be known as the "Apache Druid Project", be and hereby is
established pursuant to Bylaws of the Foundation; and be it further
RESOLVED, that the Apache Druid Project be and hereby is responsible for
the creation and maintenance of software related to analytical database
software; and be it further
RESOLVED, that the office of "Vice President, Apache Druid" be and
hereby is created, the person holding such office to serve at the
direction of the Board of Directors as the chair of the Apache Druid
Project, and to have primary responsibility for management of the
projects within the scope of responsibility of the Apache Druid
Project; and be it further
RESOLVED, that the persons listed immediately below be and hereby are
appointed to serve as the initial members of the Apache Druid Project:
* Charles Allen <crallen@apache.org>
* Nishant Bangarwa <nishant@apache.org>
* Maxime Beauchemin <maximebeauchemin@apache.org>
* Lijin Bin <binlijin@apache.org>
* Slim Bouguerra <bslim@apache.org>
* Fokko Driesprong <fokko@apache.org>
* P. Taylor Goetz <ptgoetz@apache.org>
* Himanshu Gupta <himanshug@apache.org>
* Julian Hyde <jhyde@apache.org>
* Parag Jain <pjain1@apache.org>
* Benedict Jin <asdf2014@apache.org>
* Furkan Kamaci <kamaci@apache.org>
* Xavier Léauté <xvrl@apache.org>
* Roman Leventov <leventov@apache.org>
* David Lim <davidlim@apache.org>
* Gian Merlino <gian@apache.org>
* Vadim Ogievetsky <vogievetsky@apache.org>
* Mingming Qiu <qmm@apache.org>
* Niketh Sabbineni <niketh@apache.org>
* Surekha Saharan <surekha@apache.org>
* Jihoon Son <jihoonson@apache.org>
* Eric Tschetter <cheddar@apache.org>
* Jonathan Wei <jonwei@apache.org>
* Clint Wylie <cwylie@apache.org>
* Dylan Wylie <dylanwylie@apache.org>
* Fangjin Yang <fjy@apache.org>
* Kurt Young <kurt@apache.org>
NOW, THEREFORE, BE IT FURTHER RESOLVED, that Gian Merlino be appointed
to the office of Vice President, Apache Druid, to serve in accordance
with and subject to the direction of the Board of Directors and the
Bylaws of the Foundation until death, resignation, retirement, removal
or disqualification, or until a successor is appointed; and be it
further
RESOLVED, that the initial Apache Druid Project be and hereby
is tasked with the migration and rationalization of the Apache
Incubator Druid podling; and be it further
RESOLVED, that all responsibility pertaining to the Apache
Incubator Druid podling encumbered upon the Apache Incubator
PMC are hereafter discharged.
Special Order 7C, Establish the Apache Druid Project, was
approved by Unanimous Vote of the directors present.
8. Discussion Items
A. Assigning committers@ and www.apache.org to Marketing and Publicity
Our infrastructure team typically requires that there be an owner
(generally a PMC or a committee or officer) for every resource. To date,
commmitters@ and www.apache.org have been exceptions. To address this, the
President proposes that the following takes effect at the start of the 2020
calendar year:
1) Marketing & Publicity gets final approval for all emails sent to
committers@, as well as all emails addressed to all committers whether or not
it uses such a list. An example of this was as the recent email announcing
the Diversity and Inclusion survey. Greg has a todo to come up with a proposal
for guidelines. Marketing & Publicity will ensure that the tools used for any
emails that do not make use of the committers@ list are approved by the VP,
Data Privacy.
2) Marketing & Publicity would be responsible for Ownership and management of
www.apache.org. This would make things clearer for Central Services which
will administer such pages as they would have a single source from which to
get answers.
This should provide clarity over list ownership whenever future
infrastructure tickets are brought up regarding these lists.
Send an email to press@ for inquiries about this list.
B. Loomio Pilot
Daniel Gruno and Sam Ruby have an instance of the Loomio application
up and running on ASF Infrastructure and integrated with Apache OAuth.
As the board is a potential user of this tool, lets take the
opportunity to have a brief overview and answer any questions the
board may have. Results of the discussion will be brought back to the
appropriate mailing list, and discussion can continue there after the
meeting.
The initial focus of this service would be for Foundation topics (and
in particular, on the board mailing list), though the potential for
wider community use may be possible in the future.
9. Review Outstanding Action Items
* Tom: research what other nonprofits do for CoCs for boards
[ Statement of Expectation of Conduct of Board Members 2019-05-15 ]
Status:
* Roman: Update docs around legal FAQ
[ President 2019-09-18 ]
Status:
* David: close the loop with Arrow and other communities with needs for CI
[ Arrow 2019-10-16 ]
Status:
* Craig: pursue report for next month; possible Attic candidate
[ Joshua 2019-10-16 ]
Status:
* Danny: work with Sally on info about the Attic process
[ Tajo 2019-10-16 ]
Status:
* Danny: speak with Mark about how to handle Ambari and Xerces [
Security Team 2019-11-20 ]
Status: Done. Thanks for the update Mark. Don't hesitate to ask for
help with next steps if you could use it. ## _mjc_: these are
mostly case by case. Talked to xerces and have a plan to
update the web page to list 'unfixed' issues, talked to Ambari
and they've agreed to deal with the outstaning issues (and we
have a plan for next steps if they do not).
_mjc_: xerces solution was https://marc.info/?m=157653840106914
* Danny: pursue a change of chair for Data Privacy
[ Data Privacy 2019-11-20 ]
Status: Having been unable to devote enough time to the role John
Kinsella has indicated privately that he wishes to stand down.
Given the need for action to unblock operational risks a
proposal to move the VP role to the President has been added
to the agenda as item 7B. Dirk-Willem van Gulik has agreed to
volunteer.
* Roman: find out about bandwidth
[ Jakarta EE Relations 2019-11-20 ]
Status:
* Rich: pursue a better report
[ jUDDI 2019-11-20 ]
Status: The report is still basically the same report we've been
receiving for 18 months. I'm not sure what guidance to give
the project and welcome the input of other directors as to
whether I'm being too nit-picky.
* Danny: pursue a report for Libcloud
[ Libcloud 2019-11-20 ]
Status: Done (I didn't *actually* do anything but they have reported.)
* Shane: pursue a roll call for Stanbol
[ Stanbol 2019-11-20 ]
Status: In progress; three PMC members replied that perhaps the Attic
is the next step in a future month unless there's additional
energy somewhere.
* Myrle: pursue a roll call for SystemML
[ SystemML 2019-11-20 ]
Status:
* Rich: pursue a report for Xerces
[ Xerces 2019-11-20 ]
Status: Sent reminder on Dec 13
* Myrle: work with Roman to lead discussion on this
[ Convenience Binaries 2019-11-20 ]
Status:
10. Unfinished Business
11. New Business
12. Announcements
13. Adjournment
Adjourned at 12:05 p.m. (Pacific)
============
ATTACHMENTS:
============
-----------------------------------------
Attachment 1: Report from the VP of Brand Management [Mark Thomas]
* ISSUES FOR THE BOARD
None.
* OPERATIONS
Covering the period November 2019
Responded to the following queries, liaising with projects as required:
- Provided advice to FLINK regarding setting up an externally managed packages
registry for the project.
- Provided advice to IBM on acceptable uses of our logos to refer to our
products within IBM products and documentation.
- Approved the first Apache Local Chapter event. Discussions around setting up
a framework for future events continues on ComDev.
- Approved an event for Kafka, liaising with planners@ to adjust the dates to
avoid ApacheCon.
- Approved an event for Pulsar, liaising with planners@ to adjust the dates to
avoid the proposed Roadshow.
- Provided the Q2 report for Press and Marketing
- Approved 1 Podling Name Search (STREAMPIPES)
- Continued to provide advice to DRUID
- Provided advice to WEEX regarding community managed sites using a domain
name that includes our mark
* REGISTRATIONS
Instructed counsel to allow the OPENOFFICE.ORG registration in Norway to
lapse.
The registration of OPENOFFICE.ORG in India has been renewed.
The registration for APACHE IGNITE in the US completed.
The registration for APACHE in the US completed.
* INFRINGEMENTS
We received several reports related to OPENOFFICE.
PMCs continue to work on resolving a range of issues.
-----------------------------------------
Attachment 2: Report from the VP of Fundraising [Daniel Ruggeri]
Our typical Fundraising operations continue as usual. Several renewals have
been processed and several are in flight. We saw a pleasant change in
sponsorship level with one sponsor upgrading from Bronze to Silver. Two bronze
sponsors have rolled off (on has gone out of business and the second is not
renewing). We continue working with a new Silver sponsor, but progress is slow
due to email deliverability challenges
We are excited to have completed onboarding for two new Targeted Sponsorships.
The Apache Cordova project received an anonymous donation and Cloudbees is
providing benefits to ASF Infrastructure https://s.apache.org/buq73
Although we've only just closed all remaining ApacheCon 2019 payments, work
for ApacheCon and the various roadshows in 2020 has begun.
In November we received $8,686 from individual and corporate donors via Hopsie
with THREE QUARTERS ($6,519) being raised during the Individual and Corporate
Giving campaign, which launched on 27 November and will continue to run
through the end of 2019.
-----------------------------------------
Attachment 3: Report from the VP of Marketing and Publicity [Sally Khudairi]
[REPORT] ASF Marketing & Publicity — December 2019
I. Budget: we are on budget as planned. No outstanding payments are due at
this time.
II. Cross-committee Liaison: Sally Khudairi continues to support ASF
Fundraising with ASF Sponsor renewals, onboarding new Targeted Sponsors,
launching the end-of-year Individual and Corporate Giving campaign, and
working with virtual to close out outstanding sponsor payments. Additional
support provided includes publishing the Foundation Statement on the sale of
the .org registry https://s.apache.org/zkthl , helping launch the 2020 ASF
Community Survey for Diversity & Inclusion https://s.apache.org/pzol5 , and
provide strategic and tactical support for ASF Conferences, ComDev, and Brand
Management. We published the Foundation Operations Summary (quarterly report)
for Q1 FY2020 https://s.apache.org/a6s40 , and are preparing the Q2 report for
publishing before the end of the year. We helped develop an FAQ for a new
project. Two Platinum Sponsor case studies/profiles (similar to
https://s.apache.org/jKNc ) are on hold due to Sponsor scheduling. The ASF
documentary, “Trillions and Trillions Served”, is in post-production.
III. Press Releases: the following formal announcement was issued via the
newswire service, ASF Foundation Blog, and announce@apache.org during this
timeframe:
- 4 December 2019: The ApacheⓇ Software Foundation Welcomes CloudBees as its
Newest Targeted Sponsor at the Platinum Level
IV. Informal Announcements: 8 items were published on the ASF "Foundation"
Blog. 4 Apache News Round-ups were issued, with a total of 283 weekly
summaries published to date. We tweeted 33 items to 55.5K followers on
Twitter, and posted 6 items on LinkedIn that garnered more than 101.2K organic
impressions.
V. Future Announcements: 2 announcements are in development. Projects planning
to graduate from the Apache Incubator as well as PMCs wishing to announce
major project milestones, "Did You Know?" success stories, “Have You Met?”
highlights, and “Project Perspectives” profiles 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 two media queries. The ASF received 1,411
press clips vs. last month's clip count of 1,313. Media coverage of Apache
projects yielded 2,322 press hits vs. last month's 2,260. ApacheCon received
126 press hits.
VII. Analyst Relations: we received 2 requests for fact-checking of an
upcoming analyst report, and have also been working on a few insights
projects. Apache was mentioned in 3 reports by Gartner; 4 reports by
Forrester; 3 reports by 451 Research; and 4 reports by IDC.
VIII. Central Services: Kenneth Paskett is working on updates to the ApacheCon
pages, Apache PLC4X theme, ASF Fundraising pages, and Apache project logo
pages (in collaboration with Daniel Gruno). He is also creating a new landing
page for Central Services, which will utilize Jira for project progress. The
volunteers for editorial services have mostly been unavailable over the past 6
weeks, aside from Swapnil Mane, who has continued to publish the majority of
the Weekly News Round-ups. We have also had to adjust our publishing schedule
of our “Success at Apache” series due to the availability of volunteer
contributors.
IX. Events liaison: we are supporting members of the Apache community who are
managing ASF booths by providing with signage, stickers, and swag for upcoming
third party events, including DevNexus, FOSDEM, and Huawei Developer
Conference 2020. We are also assisting ASF Conferences with planning and
advisory assistance for 2020 Roadshows and ApacheCon. We are working with ASF
VP ConCom Sharan Foga on stickers/swag production for community events as well
as various project MeetUps in China.
X. Newswire and press clip accounts: our pre-paid press release package and
clipping service have been set to auto-renew through 2020 to ensure we have
constant access without interruption.
# # #
-----------------------------------------
Attachment 4: Report from the VP of Infrastructure [David Nalley]
General
=======
Infrastructure is operating as expected, and has no current issues
requiring escalation to the President or the Board.
Highlights
==========
- Likely to hire a Technical Writer/Editor this month
Short Term Priorities
=====================
- Complete LDAP configuration changes.
- Solve httpd stability problem.
Long Range Priorities
=====================
- Complete the work on transitioning our email archives, and the email
delivery systems.
General Activity
================
- Testing CloudBees Core for some Jenkins features, notably requested
by the Apache CouchDB community. The system may be useful for other
communities, particularly to fence off their allocated/donated job
nodes to that community.
- Standing up some ARM Jenkins nodes.
- Getting Pootle in line for AOO, along with investigating other
online collaborative translation tools.
- Upgraded Confluence.
- Testing some new GitHub features for our projects' usage: Pages, and
Actions (along with Secrets for the Actions).
- Turned off our SonarQube server, in favor of the donated services
from SonarCloud.
- New OTP command line tool for sudo access.
- Testing automated redirects for mail archives over to lists.a.o
- Some work to ensure svn authz is functioning correctly, and to
simplify ongoing management.
Uptime Statistics
=================
- Our Subversion server has seen errors with "stuck" processes. We
have seen similar behavior on our TLP website servers, and the
Bugzilla server, so it appears to be due to the particular usage and
configuration of httpd. We've spent a good amount of time trying
different approaches of traffic management, configuration,
reporting, and analysis. We are optimistic that it should return to
stability shortly. It appears the root cause was our migration to
the platform in early November.
- Our DNS provider was pointing at our old hidden master. We are
investigating an alternate solution for DNS, to remove this reliance
and problem vector.
-----------------------------------------
Attachment 5: Report from the VP of Conferences [Rich Bowen]
The full schedule of 2020 events is now up at http://events.apache.org
ApacheCon, and two of the Roadshow events (DC and Chicago) have
provided starter web presences for their events, at
http://apachecon.com/
We are working on new event documentation - "playbooks" to ensure that
our events become more consistent from one year to another, and that
lessons learned are passed on to future events. These documents are at
https://svn.apache.org/repos/private/committers/events
ApacheCon North America New Orleans
The venue has been selected and signed. The website has yet to be
updated with this information, but that should be done by the time of
this meeting.
We hope to open the CFP early January.
Brian Proffitt has agreed to handle promotion for the event, and is
also helping with promotion of our other events.
DC Roadshow 2020
Website is launched, ticket sales are open, and the CFP is open
Location is confirmed and listed on the website.
Endnote and Keynote are confirmed. No sponsor sales yet.
Chicago
Chicago Roadshow 2020: Website is soft launched (exists, lots of
placeholders, no link on main page). Determining venue this week
and next. After venue will generate budget (hopefully next week).
China Roadshow
* Date tentatively set on Oct. 24-25, Sat.-Sun., 2020
* City: Tentatively in Beijing, followed by a few meetups across a few cities,
such as Chengdu, Xiamen, Zhengzhou (satellite meetups TBD)
* Expected to have a sizable sponsors, such as Alibaba, Baidu, Didi, Huawei,
JD Cloud, MSFT, OSCAR, Redhat, Synopsys, Tencent, Ubuntu Kylin, WeBank...
* Prospectus is under discussion
* Event website and CfP will be built around April or early May timeframe.
Seattle Roadshow:
* Venue reserved for June 10-12, 2020
* Prospectus drafted
* A few sponsors approached, one committed
* Agenda being drafted
EU Roadshow in DE:
* No final decision if we do it
* Planned für late June or July
* Multiple Sponsors approached, good response from two, none commited yet
* Draft Prospectus exists
Third party events
We have a table/stand at FOSDEM, which is February 1st and 2nd, 2020,
in Brussels, and have a number of people who have volunteered to
represent us there.
-----------------------------------------
Attachment 6: Report from the Apache Travel Assistance Committee [Gavin McDonald]
Events
======
Currently supporting Travel and Accommodation to attend FOSDEM 2020 for ASF
Committers. Applications were open from November 23rd until December 10th. We
did not get very many applications. Of those, 4 have been accepted and they
will be informed over the next few days. With more preparation being possible
next time, and for the next event like Berlin Buzzwords, we anticipate a much
longer opening period for applications, more time for advertising etc.
Miscellany
==========
Still awaiting feedback from the EVP reference questions asked last month. No
changes to current membership.
-----------------------------------------
Attachment 7: Report from the VP of Finance [Tom Pappas]
VP Finance Report Nov 2019
Continued work with Fundraising,
specifically with Lease Web Working with Seattle and DC Roadshows for
operational issues such as insurance, Contracts and Sponsorship's
Continue to work on Foundation General Liability and Travel insurance
options
-----------------------------------------
Attachment 8: Report from the VP of Diversity and Inclusion [Gris Cuevas]
Contributors Gris Cuevas Katia Rojas Georg Link
## Description:
- The Diversity and Inclusion VP works in collaboration with a team who
contributes towards generating a current description of the D&I landscape in
the industry and for the foundation. The team also focuses on developing
resources the projects can leverage to increase diversity and inclusion in
their communities.
## Issues:
The Survey launch plan surfaced the need to work with the V.P. of Data Privacy
Policy to define a scalable long term solution to reach out to people when
applying the ASF community survey.
## Activity:
*** Project: Survey revamp***
The 2020 ASF Community Survey was launched on Dec 05, 2019 according to it's
launch plan [ 1 ]
We have had so far: 423 responses from unique links and 131 from the open
link.
Survey closes on January 4th, 2020.
Please, promote the survey in your project mailing lists using the message
shared by Sally in the pmc@ and ppmc@ lists.
You can find a template to promote the survey with the link to the public
version here [2]
Further reminders to take the survey won't be sent.
*** Project: UX Research on new contributors ***
We will start preparations to recruit people to interview.
We will also take a look at preliminary answers from the survey to draft
interview questions.
We are still on track to kick this off on time per the reviewed scheduled or
finishing the project on May 2020.
*** Project: Internships for underrepresented groups (Outreachy) ***
*** Operations ***
- We selected our first Outreachy intern and she has accepted the internship
[3]. The interns selection was announced on the alums page on Nov. 26, 2019
at 4pm UTC. The project is Migrate Apache Juneau PetStore Sample Application
To Spring Boot Standalone Application [4]
- Internship period is from Dec. 3, 2019, to March 3, 2020.
- The first mentor's review has been submitted to Outreachy and it is
positive. Mentor's feedback about the last two weeks of internship is also
positive.
- In order to address the problem of attracting applicants to the program we
are developing a tooling training manual to help newcomers: Getting started
at Apache [5]
- Friction log: we keep working with the friction log coordinators of the
Survey Design & Contributor Experience Research project. We updated the
first template of friction log with feedback provided in the dev@ mailing
list, thread: First draft of friction log template. See updated draft [6].
We are waiting for the coordinator's feedback before reopening the
discussion on the mailing list.
- We keep working on the migration of previous meeting notes to Confluence to
create a report that includes all action items, to make the process more
transparent.
## Health report:
The dev@ and diversity@ mailing lists continue to be slow, not too much
activity outside the work done for each ongoing project. The discussions have
been focused on topics that pertain to the projects we are running.
## Committee members changes:
None.
## References
[1] https://cwiki.apache.org/confluence/display/EDI/Launch+Plan+-+The+2020+ASF+Community+Survey
[2] https://cwiki.apache.org/confluence/display/EDI/Comms+Copy+-+The+2020+ASF+Community+Survey
[3] https://www.outreachy.org/alums/
[4] https://www.outreachy.org/december-2019-to-march-2020-internship-round/communities/apache/#migrate-apache-juneau-petstore-sample-application-
[5] http://cwiki.apache.org/confluence/display/EDI/Getting+Started+At+Apache
[6] https://docs.google.com/document/d/1Qbhrwfy0jN-Ibq6VV2bJOsDL3H1VAay4PcfNs6CwJdM/edit
-----------------------------------------
Attachment 9: Report from the VP of W3C Relations [Andy Seaborne]
Nothing to report this month.
-----------------------------------------
Attachment 10: Report from the Apache Legal Affairs Committee [Roman Shaposhnik]
For the past months we've had a regular amount of usual requests flowing
through LEGAL JIRA and legal-discuss. Hen and the rest of the volunteers took
a good care of resolving most of these in time. We're up 4 to 24, unresolved
issues this month.
Sadly, there has been no progress with Eclipse foundation mainly because lack
of time on our end with key volunteers (Roman and Mark Struberg) we will try
to do better next month.
I had a call with Qualcomm clarifying some of the ramifications of the patent
clause in the Apache License. Based on the discussion, I'll be proposing
additions to our legal FAQ soon.
-----------------------------------------
Attachment 11: Report from the Apache Security Team Project [Mark J. Cox]
Continued work on incoming security issues, keeping projects reminded
of outstanding issues, and general oversight and advice.
Stats for November 2019:
15 [license confusion]
12 [support request/question not security notification]
Security reports: 31 (last months: 29, 28, 46, 26)
3 [cxf], [lucene], [site]
2 [httpd], [olingo], [struts]
1 [cordova], [directory], [dubbo], [flink], [hive],
[infrastructure], [kudu], [nifi], [shiro], [spamassassin],
[syncope], [tomcat], [trafficcontrol], [ws], [xerces],
[xmlgraphics]
In total, as of 1st December 2019, we're tracking 60 (last month:
74) open issues across 32 projects, median age 119 (last month:
88) days. 36 of those issues have CVE names assigned.
7 (last month: 7) of these issues, across 5 projects, are older
than 365 days.
-----------------------------------------
Attachment 12: Report from the VP of Data Privacy [John Kinsella]
Having been unable to devote enough time to the role John Kinsella has
indicated privately that he wishes to stand down. Given the need for action to
unblock operational risks a proposal to move the VP role to the President has
been added to the agenda as item 7B. Dirk-Willem van Gulik has agreed to
volunteer. (danny@)
-----------------------------------------
Attachment 13: Report from the VP of Jakarta EE Relations [Mark Struberg]
-----------------------------------------
Attachment A: Report from the Apache Airflow Project [Bolke de Bruin]
## Description:
The mission of Apache Airflow is the creation and maintenance of software
related to workflow automation and scheduling that can be used to author and
manage data pipelines
## Issues:
## Membership Data:
Apache Airflow was founded 2018-12-19 (a year ago)
There are currently 29 committers and 21 PMC members in this project.
The Committer-to-PMC ratio is roughly 4:3.
Community changes, past quarter:
- Aizhamal Nurmamat kyzy was added to the PMC on 2019-11-21
- Kevin Yang was added to the PMC on 2019-11-21
- Jarek Potiuk was added to the PMC on 2019-10-18
- Kengo Seki was added to the PMC on 2019-12-01
- Kengo Seki was added as committer on 2019-12-01
## Project Activity:
Recent releases:
1.10.6 was released on 2019-10-28.
1.10.5 was released on 2019-09-04.
1.10.4 was released on 2019-08-06.
## Community Health:
We have quite a few active discussions on Airflow Improvement Proposals (AIP)
which are more and more being picked up by the community to steer large
changes. Mailinglist and PRs remain very active as well. The growth of
committers and PMC members is therefore very welcome.
dev@airflow.apache.org had a 8% decrease in traffic in the past quarter (735
emails compared to 791) users@airflow.apache.org had a 360% increase in
traffic in the past quarter (92 emails compared to 20) 751 issues opened in
JIRA, past quarter (7% increase) 474 issues closed in JIRA, past quarter (no
change) 1117 commits in the past quarter (no change) 176 code contributors in
the past quarter (-12% decrease) 841 PRs opened on GitHub, past quarter (21%
increase) 826 PRs closed on GitHub, past quarter (13% increase)
-----------------------------------------
Attachment B: 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:
- Large merge request from a new contributor is awaiting review
- Movement towards Python 3 hasn't been as fast as we'd want, but still on
the short-term roadmap
## Health report:
- Slower development this quarter, expected to pick back up with final python
3 push soon
- Not much from end-users/deployers this quarter
## PMC changes:
- Last PMC addition: Sun Oct 28 2018 (Shalitha Suranga)
- Currently 15 PMC members.
## Committer base changes:
- Last committer addition: Mon Oct 29 2018 (Shalitha Suranga)
- Currently 15 committers.
## Releases:
- 1.12.0 was released on 2019-10-04
-----------------------------------------
Attachment C: Report from the Apache Any23 Project [Lewis John McGibbney]
## Description:
The mission of Apache Any23 is the creation and maintenance of software related
to automatic crawling, parsing, analyzing, producing, validating and converting
RDF (Resource Description Framework) data
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache Any23 was founded 2012-08-27 (7 years ago)
There are currently 15 committers and 15 PMC members in this project.
The Committer-to-PMC ratio is 1:1.
Community changes, past quarter:
- No new PMC members. Last addition was Hans Brende on 2018-02-25.
- No new committers. Last addition was Hans Brende on 2018-02-21.
## Project Activity:
Although project activity has been low since October, Any23 is very close
to a version 2.4 release. One of the IN PROGRESS tickets relates to fixing
all spotbugs issues so this is taking a while.
Recently a Docker build was developed and committed to the server repository.
## Community Health:
In October, the Any23 community decided to simplify the core repository by
extracting the Any23 plugins and server modules into separated repositories.
This consensus indicated decent community health.
A new use case for Any23 is being realized at NASA JPL relating to
enterprise knowledge graphs so it is envisaged that
more community contributions will ensue from that.
-----------------------------------------
Attachment D: Report from the Apache Archiva Project [Olivier Lamy]
## Description:
The mission of Archiva is the creation and maintenance of software related to
Build Artifact Repository Manager
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache Archiva was founded 2008-03-19 (12 years ago)
There are currently 21 committers and 9 PMC members in this project.
The Committer-to-PMC ratio is 7:3.
Community changes, past quarter:
- No new PMC members. Last addition was Martin Stockhammer on 2017-04-10.
- No new committers. Last addition was Martin Stockhammer on 2016-09-22.
## Project Activity:
Low activity. Mainly java 11 compliance and bug fixes
## Community Health:
We received more pull requests than previously.
4 code contributors in the past quarter (300% increase)
7 PRs opened on GitHub, past quarter (600% increase)
2 PRs closed on GitHub, past quarter (200% increase)
-----------------------------------------
Attachment E: 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:
- enhancements to support user-defined attributes in entity instances
- enhancements to support labels to entity instances
- enhancements in search functionality to find entities with multiple
classifications, by labels
- upgraded JanusGraph version to the most recent release, 0.4.0
- improvements to stats/metrics API and UI to include JVM details
- added an option to authorize notifications using the username in the
message
- added REST APIs to: retrieve entity-header given its unique attributes,
purge deleted entities
- working on a new feature to introduce namespace attributes
- working on search enhancements to support system-attributes
- release 2.1.0 will be around end of January 2020
## Health report:
- 1 new contributor added in last 3 months: leslizhang
## PMC changes:
- Currently 34 PMC members
- Last addition to PMC role was on 5/13/2019
## Committer base changes:
- Currently 38 committers
- No new committers added in last 3 months
- Last addition to committer role was on 10/15/2018
## Releases:
0.8.4 was released on 06/21/2019
1.2.0 was released on 06/12/2019
2.0.0 was released on 05/14/2019
0.8.3 was released on 10/31/2018
1.1.0 was released on 09/17/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 F: Report from the Apache Aurora Project [Renan DelValle]
## Description:
The mission of Aurora is the creation and maintenance of software related to
Mesos framework for long-running services and cron jobs.
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache Aurora was founded 2015-03-17 (5 years ago)
There are currently 23 committers and 22 PMC members in this project.
The Committer-to-PMC ratio is roughly 1:1.
Community changes, past quarter:
- No new PMC members. Last addition was Mauricio Garavaglia on 2019-07-29.
- No new committers. Last addition was Mauricio Garavaglia on 2019-07-25.
## Project Activity:
We're in the middle of releasing a new version of our software. The voting is
currently open for the second RC for version 0.22.0 and only needs one more
vote to meet quorum. Mauricio Garavaglia has proven to be a very valuable and
very active addition to the PMC and has helped the project regain stability
after the departure of many folks including our former chair. With his help,
as the community health statistics show, we've been able to get more work
done, more fixes, and even land some new features into the master branch. We
will be looking to add more committers and possibly PMC members in the very
near future.
## Community Health:
dev@aurora.apache.org had a 50% increase in traffic in the past quarter (24
emails compared to 16) reviews@aurora.apache.org had a 53% increase in traffic
in the past quarter (95 emails compared to 62) 17 commits in the past quarter
(183% increase) 9 PRs closed on GitHub, past quarter (28% increase)
-----------------------------------------
Attachment G: Report from the Apache Axis Project [Robert Lazarski]
# Apache Axis Board Report
## Description
The Apache Axis project is responsible for the creation and maintenance of
software related to the Axis Web Services frameworks and subsidiary components
(both Java and C).
## Issues
There are no issues requiring board attention at this time.
## Membership Data:
Axis was created on 2001-01-19 (18 years ago).
There are currently 63 committers and PMC members in this project, a vote in
2010 made all committers automatically PMC members.
Community changes, past quarter:
## Activity
- Axis2 Java 1.7.9 (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 received and applied several patches this past quarter, see AXIS-2935 and
AXIS2-5969. There was light but consistent traffic of new users this past
quarter on the Axis2 users mailing list.
While best known for SOAP, the future of Axis2 is with JSON and REST - which
it supports well though its not well documated nor does it yet have the modern
auto config features that would make it easier for new users.
Work continues on removing the com.sun classes from the Axis2 client code, so
it can run on JDK 11 which the server code now supports.
The axis 1.4 branch, last released in 2006, has had several security patches
applied however its far from being able to run on JDK 11, which would also be
a compelling reason to upgrade for those users that remain.
Axis2 C PMC member Bill Blough has continued his progress via upgrading the
build system this past quarter. The communication continues to be good.
## PMC/Committer changes:
- Currently 63 PMC/Commiters members.
- No new committers were added in the last 90 days, last committer added was
Bill Blough on December 7th 2017 who also was added to the PMC on May 9th
2018.
## Releases:
- Axis 2/Java 1.7.9 was released on November 16, 2018.
- Axis 2/C 1.6 was released on April 20, 2009.
- Axis 1.4 was last released in 2006.
## JIRA Activity for Axis2 java
- 11 JIRA tickets created in the last 90 days.
- 3 JIRA tickets closed/resolved in the last 90 days.
-----------------------------------------
Attachment H: Report from the Apache Bahir Project [Luciano Resende]
## Description:
The mission of Bahir is the creation and maintenance of software related to
Extensions to distributed analytic platforms such as Apache Spark
## Issues:
There are no issues requiring board attention at this time
## Membership Data:
Apache Bahir was founded 2016-05-17 (4 years ago)
There are currently 40 committers and 11 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:2.
Community changes, past quarter:
- No new PMC members. Last addition was Prashant Sharma on 2018-10-19.
- No new committers. Last addition was Łukasz Antoniak on 2019-01-21.
## Project Activity:
Apache Bahir community continues to see a flow of contributions enhancing
the existing extensions for both Apache Spark and Apache Flink.
A new SQS stream connector is being proposed/reviewed as a new extension
for the Spark platform.
For the Bahir Flink extensions, multiple bugfixes and dependency updates
have been provided and is now available in master. A release of the Flink
extensions are still pending.
## Community Health:
Overall community activity has decreased in the last quarter, with lower
mailing list traffic, hopefully this will pickup again on the next year.
Also, there was a question related to committer:pmc ratio, and tha is a side
effect that we offered committer access to all Apache Spark committers when
the project was created, and a not all of them became very active, and thus
didn't become PMC members.
## Trademark/Branding
* No known issues.
## Legal Issues
* None
-----------------------------------------
Attachment I: Report from the Apache Beam Project [Kenneth Knowles]
## Description:
The mission of Apache Beam is the creation and maintenance of software related
to 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 requiring board attention.
## Membership Data:
Apache Beam was founded 2016-12-20 (3 years ago)
There are currently 63 committers and 21 PMC members in this project.
The Committer-to-PMC ratio is 3:1.
Community changes, past quarter:
- No new PMC members. Last addition was Pablo Estrada on 2019-05-13.
- Alan Myrvold was added as committer on 2019-09-24
- Brian Hulette was added as committer on 2019-11-14
- Daniel Oliveira was added as committer on 2019-11-20
## Project Activity:
We crossed 10,000 pull requests! That is just a cumulative milestone, but this
quarter alone was extremely active. Number of days from PR #1 and PR #1000:
211. Number of days from PR #9000 and PR #10000: 71
Some notable technical developments, focusing mostly on integrations:
- A new experimental Spark runner based on Spark structured streaming
framework is available on master for testing. To fully support the Beam
model, it will require Spark structured streaming to support multiple
aggregations, but it can be tested for batch jobs in the meantime. [1]
- A new Jupyter notebook integration, dubbed "interactive beam", was proposed
and implemented, and remains under heavy development. [2]
- Portability continues to mature, with significant use and development of
Python on Flink, and maturation of multi-language pipelines, in which a
"Beam Python" pipeline can include connectors and SQL from Java. The Go SDK
intends to primarily support this mode, to avoid re-implementing any
connectors, so this will lead to "Go on any data processing engine".
- The beginning of transition from AWS v1 to AWS v2 [3]. Many other
improvements across a many connectors to storage systems.
[1] https://lists.apache.org/thread.html/0135c726ab
f454ea381c1075fe6b588b42b8e6b1e69964e749a0621d%40%3Cdev.beam.apache.org%3E
[2] https://lists.apache.org/thread.html/6ed9a4100
89b86c7c99a0f0ad8e9ce97b6414eb95ffb69f5a52dc0dc%40%3Cdev.beam.apache.org%3E
[3] [https://lists.apache.org/thread.html/130cb60e6b
cdd58c5afdd0c375663eaf05e705aab9ee0196535cd17f%40%3Cdev.beam.apache.org%3E]
Some notable community resolutions and discussions:
- Discussion of Beam Summit 2020 [4]
- The Beam community has decided to adopt a mascot, the Firefly. [5] [6]
Currently being designed by community members.
- We documented Jira priority explanations and release blocking policies [7]
- We joined a pledge on https://python3statement.org/ to discontinue Python 2
support in 2020. [8]
- A renewed discussion and interest is communicating effectively with Beam
users the maturity and stability of different components. [9]
- Another renewed conversation around a more formal "BIP" (Beam Improvement
Proposal) process, to improve clarity of approval and development of bigger
changes. [10]
- Our Outreachy proposals did not receive contributions in the needed
timeframe, despite some initial interest. They may not have been
appropriately scoped for an Outreachy internship. [11]
- LTS (Long Term Support) version has not been very successful, with zero
patch releases, because no one really seemed to want one. We may designate
another one and try harder next time to really finish a patch release and
measure its uptake.
[12]
[4] https://lists.apache.org/thread.html/bd9a1cebbcc
6994b0f9a5f1cdb402a19efe9c5acc54d6aa65bc671a2%40%3Cdev.beam.apache.org%3E][5]
https://lists.apache.org/thread.html/ff60eabbf8
349ba6951633869000356c2c2feb48bbff187cf3c60039%40%3Cdev.beam.apache.org%3E
[6] https://lists.apache.org/thread.html/fd8146e3e7
9fc41e8c760924be3b29b1c5314024336f473f9f0e7723%40%3Cdev.beam.apache.org%3E
[7] https://lists.apache.org/thread.html/05fa80345
f9e9ed5c9233f1dd2aa7ffbf1b5691dfeef5b449f6be338%40%3Cdev.beam.apache.org%3E
[8] https://lists.apache.org/thread.html/634f7346
b607e779622d0437ed0eca783f474dea8976adf41556845b%40%3Cdev.beam.apache.org%[9]
https://lists.apache.org/thread.html/0f76973
6be1cf2fc5227f7a25dd3fdbb9296afe8a071761cb91f588a%40%3Cdev.beam.apache.org%3E
[10] https://lists.apache.org/thread.html/9236522d90
06d6b8747d179bc369f5b082801e31fbecd4bdfce8f3e1%40%3Cdev.beam.apache.org%3E
[11] https://lists.apache.org/thread.html/217daec97f
bcf04c71a93a2d306593f01c18f09aaad7abd69ec33eef%40%3Cdev.beam.apache.org%3E
[12] https://lists.apache.org/thread.html/100e13251b
31ca601ddd53ab7e819de0960e826e96a0aece43045861%40%3Cdev.beam.apache.org%3E
A continuing pain point is our release process being slow and cumbersome. The
2.17.0 release has been underway for over 6 weeks. Such a burden is not
approachable for volunteer contributors.
## Community Health:
The community is vigorous, but the balance of activities is imperfect.
Mailing list stats are worth mentioning because dev@ traffic is getting *very*
large. It does not include Jira/Jenkins/GitHub notifications. Even some steady
contributors have indicated that they cannot really follow the dev@ list.
- dev@beam.apache.org had a 23% increase in traffic in the past quarter (1820
emails compared to 1478)
- user@beam.apache.org had a 32% increase in traffic in the past quarter (446
emails compared to 336)
The open PR count (steady state) has climbed from about 100 to over 150. This
is not due to more PRs being opened. The PR open rate is about the same. The
PR close rate is also about the same. I think this implies we have been
steadily falling behind further and further. Cultivating new
contributors/committers may help, as well as highlighting or trying to
incentivize code review by existing committers and also by non-committers.
-----------------------------------------
Attachment J: Report from the Apache Bigtop Project [Youngwoo Kim]
## Description:
Bigtop is a project for the development of packaging and tests of the Apache
Hadoop ecosystem. The primary goal of Bigtop is to build a community around the
packaging and interoperability testing of Hadoop-related projects. This
includes testing at various levels (packaging, platform, runtime, upgrade,
etc...) developed by a community with a focus on the system as a whole, rather
than individual projects. In short we strive to be for Hadoop what Debian is to
Linux.
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache Bigtop was founded 2012-09-19 (7 years ago)
There are currently 37 committers and 27 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:4.
Community changes, past quarter:
- No new PMC members. Last addition was Jun He on 2018-11-25.
- No new committers. Last addition was Jun He on 2018-02-23.
## Project Activity:
* Bigtop community have discussed and developed next 1.5.0 release.
In upcoming release, we will update the support matrix of Linux distributions
and also bump up up-to-date version of Bigtop components.
* Alongside 1.5 development, Bigtop community discussed about
'Cloud Native Bigtop' as well. The purpose of CNB is building a
big data and analytics distribution for cloud native world.
* What we are trying to achieve via Cloud Native Bigtop are pushing for
replacing traditional packaging and provisioning to new container based tooling
and platforms. Eventually, Bigtop project can help move data
infrastructure to more simple and cloud native platform along with
related projects in ASF.
## Community Health:
* Overall, commits and discussions on the community have increased.
* During the last period, there were discussions and development activities
on upcoming release and new features.
-----------------------------------------
Attachment K: Report from the Apache Bloodhound Project [Gary Martin]
-----------------------------------------
Attachment L: Report from the Apache BVal Project [Matthew Jason Benson]
## Description:
The mission of BVal is the creation and maintenance of software related to
Apache BVal: JSR-303 Bean Validation Implementation and Extensions
## Issues:
No issues requiring board attention at this time.
## Membership Data:
Apache BVal was founded 2012-02-14 (8 years ago)
There are currently 15 committers and 14 PMC members in this project.
The Committer-to-PMC ratio is roughly 8:7.
Community changes, past quarter:
- No new PMC members. Last addition was Thomas Andraschko on 2019-05-15.
- No new committers. Last addition was Thomas Andraschko on 2019-05-16.
## Project Activity:
Apache BVal 2.0.3 was released on 2019-08-19. Last quarter we reported a
planned 1.1.x maintenance release but there has not yet been significant
forward movement on that.
## Community Health:
We have had a very quiet quarter, with a single issue reported and
subsequently closed having verified the issue was not with Apache BVal
itself. Our (low) capacity continues to exceed our (lower) demand.
-----------------------------------------
Attachment M: 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
## Membership Data:
Apache Camel was founded 2008-12-17 (11 years ago) There are currently 69
committers and 35 PMC members in this project. The Committer-to-PMC ratio is
roughly 9:5.
Community changes, past quarter:
- No new PMC members. Last addition was Dmitry Volodin on 2019-05-08.
- Omar Al-Safi was added as committer on 2019-11-07
## Project Activity:
- We finally released Apache Camel 3.0.0 on 24 Nov 2019
- We are working already on the first minor release 3.0.1 and we are focusing
on bug fixes, stabilization and minor improvements.
- We are working already on the 3.1.0 version too.
- During this quarter we released two release candidates for Camel 3.0.0: RC2
on 6 Oct 2019 and RC3 on 25 Oct 2019. We use the feedback from the community
to finalize the GA release.
- We released a new 2.x version, the 2.24.2 on 13 Sept 2019. Also we released
2.23.4 on 22 Sept 2019.
- We are working on a new minor release Apache Camel 2.25.0, we're working on
bug fixes and stabilisation of the codebase.
- We are preparing for the next minor release Apache Camel 2.24.3 expected for
the end of the year: we are working on bug fixes mainly.
- We released Camel-K-Runtime 1.0.4, 1.0.5 and 1.0.7, respectively on 05 Oct
2019, 18 Oct 2019 and 13 Nov 2019
- We released Camel-K 1.0.0-M2, 1.0.0-M3 and 1.0.0-M4, respectively on 08 Oct
2019, 22 Oct 2019 and 18 Nov 2019
- We are continuing our work on Camel-K by improving the support for Camel 3
and we plan to release a GA soon in the beginning of 2020.
- We are continuing to support Camel-Quarkus by releasing multiple
versions in this quarter
- We released the following Camel-Quarkus versions:
- 0.2.0 on 23 Sep 2019
- 0.3.0 on 25 Oct 2019
- 0.3.1 on 30 Oct 2019
- 0.4.0 on 15 Nov 2019
- 1.0.0-M1 on 04 Dec 2019
- We added another project to the Apache Camel ecosystem:
camel-kafka-connector, this project is based on Kafka-connect and it is
leveraging the components that we already have in Camel.
- This is the complete releases list
- 3.0.0 was released on 2019-24-11
- 3.0.0-RC2 released on 2019-06-10
- 3.0.0-RC3 released on 2019-25-10
- 2.24.2 released on 2019-13-09
- 2.23.4 released on 2019-22-09
- Camel-K 0.3.4 was released on Tue Jun 11 2019
- Camel-K 1.0.0-M2 released on 2019-10-08
- Camel-K 1.0.0-M3 released on 2019-10-22
- Camel-K 1.0.0-M4 released on 2019-11-18
- Camel-Quarkus 0.2.0 released on 2019-09-23
- Camel-Quarkus 0.3.0 released on 2019-10-25
- Camel-Quarkus 0.3.1 released on 2019-10-30
- Camel-Quarkus 0.4.0 released on 2019-11-15
- Camel-Quarkus 1.0.0-M1 released on 2019-12-04
## Community Health:
- dev@camel.apache.org had a 35% decrease in traffic in the past quarter (1550
emails compared to 2371) This is for the GA release
- users@camel.apache.org had a 51% increase in traffic in the past quarter
(465 emails compared to 307) This is for the feedback we got
- 307 issues opened in JIRA, past quarter (-6% decrease) This is because we
were focusing on existing issues
- 305 issues closed in JIRA, past quarter (-11% decrease) This is because we
were focusing on existing issues
- 2601 commits in the past quarter (-13% decrease) This is for the GA release,
so more stabilization
- 113 code contributors in the past quarter (14% increase) This is for the new
projects in the ecosystem, we are noticing more contributors
- 602 PRs opened on GitHub, past quarter (19% increase) This is for the new
projects in the ecosystem, we are noticing more contributors
- 598 PRs closed on GitHub, past quarter (21% increase) This is for the new
projects in the ecosystem, we are noticing more contributors
- 261 issues opened on GitHub, past quarter (42% increase) This is for the new
projects in the ecosystem, we are noticing more contributors
- 225 issues closed on GitHub, past quarter (61% increase) This is for the new
projects in the ecosystem, we are noticing more contributors
-----------------------------------------
Attachment N: Report from the Apache Cayenne Project [Michael Ray Gentry]
# Apache Cayenne Board Report, December 2019
## 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.
## Membership Data
Apache Cayenne was founded 2006-12-19 (13 years ago).
There are currently 23 committers and 9 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
Community changes, past quarter:
- No new PMC members. Last addition was Nikita Timofeev on 2017-06-25.
- No new committers. Last addition was Arseni Bulatski on 2018-12-10.
## Project Activity
Development is focused on Cayenne 4.1 and 4.2. Prior versions are
maintenance-only.
- Cayenne 3.1.3 (aging)
- Maintenance only.
- Cayenne 4.0.2 (stable)
- Maintenance only.
- Cayenne 4.1.RC (beta)
- Expecting to release Cayenne 4.1 soon as final bugs are fixed and tested.
- Cayenne 4.2M1 (development)
- Most development work is focused on this version.
### Releases
- Cayenne 3.1.3 on 2018-07-25.
- Cayenne 4.0.2 on 2019-10-14.
- Cayenne 4.1.RC1 on 2019-10-14.
- Cayenne 4.1.RC2 on 2019-10-29.
## Community Health
Cayenne is healthy. Development activity is stable and and we have a
stable user and developer community.
### Mailing List Activity
- dev@cayenne.apache.org had a 226% increase in traffic in the past
quarter (62 emails compared to 19).
- user@cayenne.apache.org had a 29% increase in traffic in the past
quarter (96 emails compared to 74).
Mailing list traffic increased mainly due to 4.1 RC issues being discovered,
fixed, and new RC versions released.
### JIRA Activity
- 23 issues opened in JIRA, past quarter (-32% decrease).
- 14 issues closed in JIRA, past quarter (-61% decrease).
- 156 commits in the past quarter (19% increase).
-----------------------------------------
Attachment O: 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.
## Membership Data:
Apache Chemistry was founded 2011-02-16 (9 years ago)
There are currently 38 committers and 36 PMC members in this project.
The Committer-to-PMC ratio is roughly 1:1.
Community changes, past quarter:
- No new PMC members. Last addition was Laurent Mignon on 2017-09-23.
- No new committers. Last addition was Laurent Mignon on 2017-09-20.
## Project Activity:
There was almost no activity in the last three months.
Last releases were in 2017.
## Community Health:
We have a mature code base. No major development is expected.
-----------------------------------------
Attachment P: Report from the Apache CloudStack Project [Paul Angus]
## Description:
Apache CloudStack (ACS) is an IaaS (Infrastructure as a Service) cloud
orchestration platform. ACS manages many types of hypervisors, storage and
networking devices.
## Issues:
- The security ‘team’ is triaging a number of issues, progress is slow but
steady.
## Activity:
- the community has voted to accept two new sub-projects within CloudStack:
https://github.com/apache/cloudstack-primate (see below)
https://github.com/apache/cloudstack-kubernetes-provider (the CloudStack
provider was removed from Kubernetes core code by the Kubernetes community
as part of a ‘streamlining of the core’ exercise – the provider will now be
maintained separately by the CloudStack community)
- The community has coalesced behind the development of an all-new UI
(Primate). It is hoped that the use of modern tools and a modern interface
will encourage a new wave of users and developers to get involved. The
outgoing UI is somewhat antiquated. A special interest group (SIG) holds
bi-weekly meetings and reports updates on dev@. Certainly, some ‘new faces’
have got involved in the UI’s development already.
- A ‘winter’ LTS release would be expected in early Q1 next year, but no
announcement has been made along those lines yet.
## Health report:
- Apropos of the activity report; the project is considered healthy
## PMC changes:
- Currently 51
- no new PMC members were added since the last report. The following members
were added in the previous quarter: Andrija Panic, Gabriel Beims Bräscher,
Bobby Stoyanov, Nathan Johnson, Sven Vogel
## Committer base changes (2 added since the last report):
- Currently 121 committers
- Most recently added committers: Sven Vogel on March 18th 2019 and Dennis
Konrad on March 21st 2019
## Releases:
- 4.13 was released on 24th September 2019
-----------------------------------------
Attachment Q: Report from the Apache Commons Project [Gary D. Gregory]
## Description:
The mission of Apache Commons is the creation and maintenance of Java focused
reusable libraries and components.
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache Commons was founded 2007-06-19 (12 years ago)
There are currently 148 committers and 38 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:2.
Community changes, past quarter:
- No new PMC members. Last addition was Alex Herbert on 2019-05-09.
- No new committers. Last addition was Alex Herbert on 2019-01-30.
## Project Activity:
The community is active and accepting a majority of its contribution
through GitHub PRs.
Our releases this period were:
PARENT-50 was released on 2019-12-17.
POOL-2.8.0 was released on 2019-12-11.
SKIN-4.2 was released on 2019-11-25.
RNG-1.3 was released on 2019-11-11.
DAEMON-1.2.2 was released on 2019-10-03.
BCEL-6.4.1 was released on 2019-10-02.
BCEL-6.4.0 was released on 2019-09-24.
## Community Health:
Most activity is GitHub PRs.
Mailing list and Jira is active and questions are handled in a timely manner.
Commons allows any ASF committer to commit
(though of course we do expect prior discussion for new committers).
Additions to the PMC will result in additions to the committer group, but
there is no need to do this for other occasional committers.
So the size of the committer LDAP group is not necessarily a reflection of
acive committer numbers.
-----------------------------------------
Attachment R: Report from the Apache Cordova Project [Jesse MacFadyen]
## Status report for the Apache Cordova project - December 2019
## 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:
cordova-eslint is a new repo which consolidates linting standards which will
be applied across all our repos.
The project received a generous anonymous donation, which took us a while to
decide on an acceptable use of the funds. We will be using the donation to
pay to have some documentation, information architecture and technical writing
done to update our documentation and author some getting started guides.
cordova-ios release includes prep work for removing the UIWebView
implementation ( deprecated by Apple ) We will move forward this quarter with
the migration from UIWebView to WKWebView for iOS.
## Health report:
Our status dashboard at http://status.cordova.io is mostly all green -
failures are usually due to external service issues that do device testing.
Our nightly builds remain stable.
We are still working to resolve all existing issues in JIRA while also
maintaining all the new issues and pull requests in Github.
## PMC changes:
- Currently 98 PMC members.
- New PMC members:
- Norman Breau was added to the PMC on 2019-09-29
- Gedas Gardauskas was added to the PMC on 2019-10-18
- Last PMC addition: 2019-10-18 (Gedas Gardauskas)
## Committer base changes:
- Currently 101 committers.
- New commmitters:
- Norman Breau was added as committer on 2019-09-30
- Gedas Gardauskas was added as committer on 2019-10-18
- Last committer addition: 2019-10-18 (Gedas Gardauskas)
## Releases:
### Platforms
- cordova-android@8.1.0 was released on 2019-09-17.
- cordova-ios@5.1.1 was released on 2019-12-02.
- cordova-ios@5.1.0 was released on 2019-11-25.
### Libraries
- cordova-eslint@2.0.0 was released on 2019-11-14.
- cordova-eslint@1.0.0 was released on 2019-11-09.
- cordova-common@3.2.1 was released on 2019-11-05.
## Mailing list activity:
- dev@cordova.apache.org:
- 234 emails sent to list (176 in previous quarter)
- issues@cordova.apache.org:
- 98 emails sent to list (82 in previous quarter)
## JIRA activity:
- 0 JIRA tickets created in the last 3 months (JIRA has been shut down)
- 92 JIRA tickets closed/resolved in the last 3 months
## Github activity:
Issue close rate of 71%:
- 334 Github Issues created in the last 3 months
- 236 Github Issues closed in the last 3 months
PR close rate of 87%:
- 288 Github Pull Requests created in the last 3 months
- 250 Github Pull Requests closed/merged in the last 3 months
-----------------------------------------
Attachment S: 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
## PMC changes:
- Currently 31 PMC members.
- Last PMC addition was Gandhi Rajan on Thu Jul 12 2018
## Committer base changes:
- Currently 38 committers.
- Last committer addition was Gandhi Rajan at Tue Nov 14 2017
## Releases:
- Last release was 4.0.0 on Thu Apr 27 2017
- 3.2.2 was released on May 30 2015
- 3.2.1 was released on Dec 10 2014
## Mailing list activity:
Overall community health is good. Sean Finan spoke at ApacheCon EU 2019.
We are seeing a steady influx of new people asking questions on the mailing
lists- both programming-and documentation-wise.
-----------------------------------------
Attachment T: Report from the Apache Curator Project [Jordan Zimmerman]
## Description:
The mission of Curator is the creation and maintenance of software related to
Java libraries that make using Apache ZooKeeper easier
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache Curator was founded 2013-09-17 (6 years ago)
There are currently 13 committers and 13 PMC members in this project.
The Committer-to-PMC ratio is 1:1.
Community changes, past quarter:
- No new PMC members. Last addition was Shay Shimony on 2019-04-17.
- No new committers. Last addition was Shay Shimony on 2019-04-18.
## Project Activity:
Reasonable activity. Curator is preparing for the next major release of
ZooKeeper and we have decent contributor activity in that regard.
## Community Health:
Community activity is decent. We can always use more committers but the
project is in use and healthy.
-----------------------------------------
Attachment U: Report from the Apache Eagle Project [Edward Zhang]
## Description:
The mission of Apache Eagle is the creation and maintenance of software related
to a distributed monitoring solution for identifying security and performance
issues in real time on big data platforms, including Apache Hadoop and Apache
Spark.
## Issues:
There are no issues requiring board attention
## Membership Data:
Apache Eagle was founded 2016-12-20 (3 years ago)
There are currently 18 committers and 16 PMC members in this project.
The Committer-to-PMC ratio is 9:8.
Community changes, past quarter:
- No new PMC members. Last addition was Deng Lingang on 2017-05-08.
- No new committers. Last addition was Jay Sen on 2017-03-16.
## Project Activity:
Upgraded Siddi dependency to v5.1.4 which is used by Eagle alert engine
and CVE maven plugin was integrated for fixing vulnerabilities in Eagle's
library dependency.
## Community Health:
Grainier Perera from Siddi open source project volunteered to upgrade
Siddhi's version to latest. The increase of activities in emails,
jiras was mostly related to this feature discussion and development.
-----------------------------------------
Attachment V: Report from the Apache Felix Project [Karl Pauls]
## Description:
Apache Felix is a project aimed at implementing specifications from the OSGi
Alliance as well as implementing other supporting tools and technologies
aligned with OSGi technology.
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache Felix was founded 2007-03-28 (13 years ago)
There are currently 67 committers and 27 PMC members in this project.
The Committer-to-PMC ratio is roughly 9:4.
Community changes, past quarter:
- No new PMC members. Last addition was Georg Henzler on 2019-06-10.
- No new committers. Last addition was Bertrand Delacretaz on 2018-12-18.
## Project Activity:
- Existing implementations have been improved/enhanced based on community
feedback.
- We voted to migrate from svn to git(box).
- Released 10 components (mostly bug fixes overall).
## Releases:
- maven-scr-plugin-1.26.2: 2019-12-07
- org.apache.felix.scr.bnd-1.9.6: 2019-12-07
- org.apache.felix.scr.generator-1.18.4: 2019-12-07
- org.apache.felix.configadmin.plugin.interpolation-0.0.4: 2019-11-14
- org.apache.felix.converter-1.0.12: 2019-11-11
- org.apache.felix.http.jetty-4.0.14: 2019-09-15
- org.apache.felix.http.base-4.0.8: 2019-09-07
- org.apache.felix.http.bridge-4.0.10: 2019-09-07
- org.apache.felix.http.jetty-4.0.12: 2019-09-07
## Community Health:
- Overall the project is in ok health.
- Questions on the user list are answered, development concerns are either
discussed on the mailing list or directly in the JIRA issues.
- The project as well as the OSGi community in general is still in the process
of adapting to JPMS and its long term impact.
- We need to be on the lookout for new committers. We hope that moving to
git(box) and with that to github we will make it easier to attract new
people.
- We had no issues voting on releases and JIRA issues are generally addressed.
- dev@felix.apache.org had a 31% increase in traffic in the past quarter (425
emails compared to 323)
- users@felix.apache.org had a 86% decrease in traffic in the past quarter (3
emails compared to 21)
- 26 issues opened in JIRA, past quarter (-29% decrease)
- 16 issues closed in JIRA, past quarter (-44% decrease)
- 30 commits in the past quarter (-70% decrease)
- 7 code contributors in the past quarter (no change)
- 13 PRs opened on GitHub, past quarter (1300% increase)
- 6 PRs closed on GitHub, past quarter (600% increase)
-----------------------------------------
Attachment W: Report from the Apache Flex Project [Olaf Krüger]
## Description:
Apache Flex is an application framework for easily building Flash-based
applications for mobile devices, the browser and desktop. Because the
FlashPlayer reaches its EOL at the end of 2020, we won't be able to
target the browser with Flex after 2020.
## Issues:
There are no issues requiring board attention at this time.
## Membership Data:
Apache Flex was founded 2012-12-19 (7 years ago)
There are currently 69 committers and 45 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:2.
Community changes, past quarter:
- No new PMC members. Last addition was Olaf Krüger on 2017-08-28.
- No new committers. Last addition was Greg Dove on 2016-09-07.
## Project Activity:
The "flex-dk-converter-maven-extension" was released in order to simplify Flex
and Apache Royale builds. With this release current projects using this
extension can simplify the command line instructions by removing "-s
settings-template.xml" and not depending on that xml file anymore. That makes
the build process less verbose and more easy for the users.
## Community Health:
Activity on users list is still decreasing. Activity on dev list is
increasing, mainly because of the latest Maven related activities.
-----------------------------------------
Attachment X: Report from the Apache Flink Project [Stephan Ewen]
## Description:
Apache Flink is a distributed data streaming system for batch and streaming
data analysis on top of a streaming dataflow engine. Flink's stack contains
functional batch and streaming analysis APIs in Java, Scala, Python, 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, Calcite, Hadoop,
Mesos, Kafka, HBase, Cassandra, and various others.
## Issues:
- There are no community issues that require board attention.
## Membership Data:
PMC members added since the last board report:
- Jark Wu joined the PMC on November 8th, 2019
- Becket Qin joined the PMC on October 21st, 2019
Committers added since the last board report:
- Zhu Zhu was added as committer on December 17th, 2019
The newest PMC member is Jark Wu, joined on November 8th, 2019. The newest
committer is Zhu Zhu, joined on December 17th, 2019.
Flink currently has 52 committers and 26 PMC members.
## Releases
The following releases were made since the last board report:
- 1.8.3 was released on December 12th, 2019.
- 1.9.1 was released on October 18th, 2019.
- shaded-9.0 was released on November 23rd, 2019.
## Project Activity:
- The community has frozen the feature set for the 1.10 release and is now
in the testing and validation phase. The release adds various enhancements
to the runtime (easier memory configuration and threading model) and many
enhancements to the "batch on streaming" capabilities of Flink, including
the Table API/SQL and integrations with the SQL/Hive ecosystem.
- There is an ongoing discussion how to better handle the use of the Apache
Flink name in China, where there is a large community. The ASF does not
have the trademark for Flink in China. The suggestion from Apache
trademarks is that the PMC does outreach and education for now, and not
push for a trademark registration process at the moment.
- The PMC voted to start an WeChat account for Flink that is managed by the
PMC. Similar to the @ApacheFlink Twitter account, this channel would be
used for various types of Flink news and to publicize interesting
mentionings of Flink from users and contributors.
- The Flink community voted to accept the "Stateful Functions" project as
contribution. https://statefun.io/ Stateful Functions is a library built
on Apache Flink to support new use cases that are not easily mappable to
the existing APIs, but more of a match distributed actor frameworks. The
library was already open source and Apache 2 licensed.
- The community is exploring to migrate the CI service fully away from
Travis CI. Currently Pull Requests are tested through a separately-paid
Travis subscription to take load off the ASF-paid account/budget, which
is only used to test the master branch.
The goal is to have everything in Azure Pipelines, which offers better
tools as well as the opportunity to hook in external build servers that
Alibaba is offering to sponsor. We hope that this both simplifies Flink's
build setup, as well as reduces feedback times on Pull Requests
significantly.
- The next Flink Forward community conference will be in San Francisco on
March 23rd-25th. There is a public call for presentations:
https://www.flink-forward.org/sf-2020/call-for-presentations Apache
committers can contact the organizers for a free pass.
## Community Health:
After a big increase in activity in the previous quarter, the mailing list
activity seems to be stable now.
- user@f.a.o (1730 mails/quarter)
- user-zh@f.a.o (570 mails/quarter)
- dev@f.a.o (3057 mails/quarter)
JIRA continues to be active as well, 1096 JIRA tickets created, 833 JIRA
tickets resolved in the last 3 months.
-----------------------------------------
Attachment Y: Report from the Apache Guacamole Project [Mike Jumper]
## Description:
The mission of Apache Guacamole is the creation and maintenance of software
related to providing performant, browser-based remote access
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache Guacamole was founded 2017-11-14 (2 years ago)
There are currently 12 committers and 9 PMC members in this project.
The Committer-to-PMC ratio is 4:3.
Community changes, past quarter:
- No new PMC members. Last addition was Carl Harris on 2017-11-19.
- No new committers. Last addition was Joel Best on 2019-01-30.
## Project Activity:
Contributions from the community covering improvements to LDAP integration,
RDP keymap support, and the SSH/telnet terminal emulator have been merged.
Contributions covering REST API documentation and improvements to CAS support
are now under review. Core RDP support finally builds against the 2.0.0
version of the FreeRDP library. Support for non-core RDP channels remains to
be ported to the new library.
## Community Health:
The community is active and healthy, however there has been a decrease in
activity relative to last quarter across most metrics. The reason for the
decrease is unclear.
-----------------------------------------
Attachment Z: Report from the Apache Gump Project [Stefan Bodewig]
Apache Gump is a cross-project continuous integration server. Gump's intention
isn't so much to be a CI server but rather a vehicle that makes people look
beyond their project's boundaries and helps the projects to collaborate.
Gump is written in Python and supports several build tools and version control
systems. The Apache installation of Gump builds ASF as well as non-ASF
projects and their dependencies. It started in the Java part of the foundation
but also builds projects like APR, HTTPd and XMLUnit.NET.
# Summary
Some of the older projects that are no longer depended on by anybody have been
removed. This includes Forrest. The Tomcat community now seems to be the only
one still using Gump actively.
# 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.
# 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.
Brett Porter has left the PMC in December 2019.
-----------------------------------------
Attachment AA: Report from the Apache Hama Project [Chia-Hung Lin]
-----------------------------------------
Attachment AB: Report from the Apache Helix Project [Kishore G]
-----------------------------------------
Attachment AC: Report from the Apache Hive Project [Ashutosh Chauhan]
## Description:
The mission of Hive is the creation and maintenance of software related to Data
warehouse infrastructure using the Apache Hadoop Database
## Issues:
No issues requiring board attention at this time.
## Membership Data:
There are currently 87 committers and 47 PMC members in Hive.
Community changes, past quarter:
- No new PMC members. Last addition was Zoltan Haindrich on 2018-10-29.
- No new committers. Last addition was David Mollitor on 2019-09-11.
## Project Activity:
Project recently did a release hive-storage-2.7.1 2019-11-30.
## Community Health:
Both user and dev activity has increased this quarter. Earlier quarter in the
year had almost a flat curve w.r.t user and dev participation. This quarter we
saw emails on dev@ increase by ~50%, 25% increase in issues reported and 15%
increase in issues resolved. All signs of healthy and growing community.
-----------------------------------------
Attachment AD: Report from the Apache Incubator Project [Justin Mclean]
The Apache Incubator is the entry path into the ASF for projects and
codebases wishing to become part of the Foundation's efforts.
This monthly report is in markdown so that it's easier to read. If you are
not viewing this in that format, it can be seen here:
https://cwiki.apache.org/confluence/display/INCUBATOR/December2019
There are presently 45 podlings incubating. In December, podlings executed
13 distinct releases. We added no new IPMC members and no IPMC members
retired. There were one IP clearances.
We have one new podling this month StreamPipes; other is under discussion
NuttX and two others a possibility. No projects graduated last month. Omin
and Tephra exited the Incubator and became sub-projects of Phoenix. BatchEE
is trying to complete becoming a subproject of Geronimo. At least one
podling is heading towards graduation in the next few months. The Warble
podling did not submit reports and will be asked to report again next month.
TubeMQ has not been bootstrapped yet.
Weex is actively working on its branding issues mentioned last month.
Further work was done on cleaning up the incubator web site, including the
cookbook.
Podlings, have continued to use the new disclaimer policy, and this seems
to be working well. TVM asked the Incubator to review a release candidate
before making a release, and several issues were identified and fixed.
PageSpeed, which joined the Incubator in October 2017, also put its first
release up for a vote. A couple of releases needed IPMC prodding to get
votes, but most were quickly voted on.
Some statistics were generated, showing how many project enter and leave
and how long they stay in incubating to see if any trends were visible.
While the overall trend is up, there has been a decrease in podlings
joining the Incubator in the last couple of years. There may be a number of
reasons for this, including the outside perception of the ASF. It is likely
that the carrying capacity of the Incubator had been exceeded in years
before this. There have been 315 projects helped by the Incubator, and 77%
of them have graduated, most spend 1 1/2 years in incubation. There's been
more than a 1000 mentors.
The Incubator release area was cleaned up and old releases from retired and
graduated projects removed.
A new branding/trademark question was added the podling report and the
podling proposal as a few podling have not realised the importance of this.
A new top level project called Petri, was approved by the board. It's goal
is to help external projects go straight to TLP, not using the Incubating
process.
## Community
### New IPMC members:
- None
### People who left the IPMC:
- None
## New Podlings
- StreamPipes
## Podlings that failed to report, expected next month
- Warble
## Graduations
- None
The board has motions for the following:
- Druid
## Releases
The following releases entered distribution during the month of
November:
- ApiSix 0.9
- Datasketches memory 1.2.0
- Datasketches postgresql 1.3.0
- ECharts 4.5.0
- Heron 0.20.2
- IoTDB 0.9.0
- Pinot 0.2.0
- Pinot 0.2.0
- Ratis Thirdparty 0.3.0
- ShardingSphere 4.0.0
- Superset 0.35.0
- Superset 0.35.1
- Tamaya 0.4-incubating
## IP Clearance
- Weex UI
## Legal / Trademarks
- New podling branding/trademark questions
## Infrastructure
- No issues
## Miscellaneous
|----------------------------------------------------------------------
Table of Contents
[Batchee](#Batchee)
[brpc](#brpc)
[Crail](#Crail)
[Daffodil](#Daffodil)
[DolphinScheduler](#DolphinScheduler)
[Druid](#Druid)
[Hivemall](#Hivemall)
[IoTDB](#IoTDB)
[Marvin-AI](#Marvin-AI)
[MesaTEE](#MesaTEE)
[Nemo](#Nemo)
[SAMOA](#SAMOA)
[APISIX](#APISIX)
[ShardingSphere](#ShardingSphere)
[Spot](#Spot)
[StreamPipes](#StreamPipes)
[Superset](#Superset)
|----------------------------------------------------------------------
## BatchEE
BatchEE projects aims to provide a JBatch implementation (aka JSR352) and a
set of useful extensions for this specification.
BatchEE has been incubating since 2013-10-03.
### Three most important unfinished issues to address before graduating:
1. Project needs to finish its migration to Geronimo and exit incubator.
### Are there any issues that the IPMC or ASF Board need to be aware of?
No
### How has the community developed since the last report?
No change
### How has the project developed since the last report?
Minor dependency upgrades
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [ ] Working towards first release
- [ ] Community building
- [ ] Nearing graduation
- [X] Other: exiting incubation in favor of a Geronimo subproject
### Date of last release:
2017-12-01
### When were the last committers or PPMC members elected?
2019-24-01
### Have your mentors been helpful and responsive?
No answer.
### Is the PPMC managing the podling's brand / trademarks?
No answer.
### Signed-off-by:
- [X] (batchee) Jean-Baptiste Onofré
Comments: BatchEE is discussing move into Geronimo project, and I
think it makes sense.
- [ ] (batchee) Mark Struberg
Comments:
- [ ] (batchee) Olivier Lamy
Comments:
### IPMC/Shepherd notes:
--------------------
## brpc
brpc is an industrial-grade RPC framework for building reliable and high-
performance services.
brpc has been incubating since 2018-11-13.
### Three most important unfinished issues to address before graduating:
1. make more apache release
2. attract more committer
3. clean branding issue
### Are there any issues that the IPMC or ASF Board need to be aware of?
No big issues.
### How has the community developed since the last report?
1. Website for brpc has been setup, https://brpc.apache.org
2. Organized brpc workshop on coscon 2019 Shanghai, more than 30 people
attended
### How has the project developed since the last report?
1. released 0.97 rc1
2. vote for apache release 0.97 rc1 failed ，due to some minor problem
3. working on 0.97rc2 release, will call for vote in one week
### 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:
still on first apache release
### When were the last committers or PPMC members elected?
No new committer, will search for some candidate next.
### Have your mentors been helpful and responsive?
Our mentor Von pointed out some minor problem for 0.97 rc1，
and gave some detail instruction through phone calls.
JB and Kevin helped to sign the pod report。
### Is the PPMC managing the podling's brand / trademarks?
Not ready for the branding issue, will check it next month.
### Signed-off-by:
- [X] (brpc) Kevin A. McGrail
Comments: None
- [X] (brpc) Jean-Baptiste Onofré
Comments:
- [X] (brpc) Von Gosling
Comments: In terms of brand / trademarks, I have read github and
website briefly, haven't found any problem at present.
### 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 unfinished issues to address before graduating:
1. Community building: Increase on number of contributors and users.
2. Establish new use cases in the community
3. Make release cycles more steady
### Are there any issues that the IPMC or ASF Board need to be aware of?
No issues.
### How has the community developed since the last report?
We released a new blog reporting "YCSB Benchmark with Crail
on DRAM, Flash and Optane over RDMA and NVMe-over-Fabrics"
Samsung Research uses the data store for showcasing KV disk
performance.
Stanford University used the data sore within their serverless
'Pocket' project.
### How has the project developed since the last report?
- Significant improvements to TCP/DRAM tier stability
- Added resource elasticity to better fit serverless deployment
model. According to current storage capacity needs, data nodes
can be dynamically added and removed.
- A new release 1.2 with above features is ongoing.
### 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-11-26
### When were the last committers or PPMC members elected?
December 4th, 2018
### Have your mentors been helpful and responsive?
Our mentors are very helpful.
### Is the PPMC managing the podling's brand / trademarks?
Yes, others are using the podling's name correctly
(e.g. Samsung Research, Stanford University)
### Signed-off-by:
- [x] (crail) Julian Hyde
Comments: Crail seems to be slowing down. Only about 5 emails per
month on the dev list, no significant code contributions for six
months, no new committers or PPMC members added for a year. A new
release is welcome, especially if it spurs community activity.
I am worried that Crail will never acquire sufficient momentum to
graduate.
- [x] (crail) Luciano Resende
Comments:
- [x] (crail) Felix Cheung
Comments: I share concerns with Julian
### IPMC/Shepherd notes:
--------------------
## Daffodil
Apache Daffodil is an implementation of the Data Format Description Language
(DFDL) used to convert between fixed format data and XML/JSON.
Daffodil has been incubating since 2017-08-27.
### Three most important unfinished issues to address before graduating:
1. Increase community growth and participation from outside Tresys
(main priority)
2. Work with other Apache projects where Daffodil could provide
extra functionality (Apache PLC4X, NiFI, and Drill are potential
goals)
3. Establish a frequent release schedule
### Are there any issues that the IPMC or ASF Board need to be aware of?
- None
### How has the community developed since the last report?
- Voted to add a new Committer, on boarding now.
- Daffodil talk at ApacheCon NA 2019
- Daffodil attendance at Podling SharkTank at ApacheCon NA 2019
- Daffodil talk at BarCamp at ApacheCon NA 2019
- Attended Hackathon at ApacheCon NA 2019, led to collaboration with
Apache PLC4X/code generation and planned collaboration with Apache
Drill
- Discussions have continue with relative frequency on users@ and dev@
mailing lists, which more new people popping up in discussions
- Planning to submit a talk for the DC Roadshow in March when CFP opens
### How has the project developed since the last report?
- 25 commits merged from 4 different contributors
- 50 issues created, 28 issues resolved--lagging in keeping up with
new bugs, but focus has been on bigger features rather than bug
fixes for this release
- Nearing next release, expected in early December. Major features
include user defined functions, support for BLOBs and files larger
than 2GB, and fixed schema compilation performance regression with
ultimate goal of improving schema compilation speed.
### 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:
2019-07-12
### When were the last committers or PPMC members elected?
- 2019-11-26 - Olabusayo Kilo (Committer)
- 2019-06-20 - Brandon Sloane (PPMC)
### Have your mentors been helpful and responsive?
- Yes
### Is the PPMC managing the podling's brand / trademarks?
- No known cases of a 3rd party incorrectly using the Daffodil
name/brand.
- Podling name search has been completed and approved by Brand
Management Committee:
https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-147
### Signed-off-by:
- [x] (daffodil) Dave Fisher
Comments: Community growth beyond Tresys has been difficult.
- [ ] (daffodil) Christofer Dutz
Comments:
### IPMC/Shepherd notes:
--------------------
## DolphinScheduler
Dolphin Scheduler is a distributed and easy-to-expand visual DAG workflow
scheduling system dedicated to solving the complex dependencies in data
processing, making the scheduling system out of the box for data processing.
Dolphin Scheduler has been incubating since 2019-8-29.
### Three most important unfinished issues to address before graduating:
1. Make first Apache releases. (In voting progress)
2. Appeal more users and contributors.
3. Make more interactive e-mail discussion besides github, wechat
### Are there any issues that the IPMC or ASF Board need to be aware of?
None
### How has the community developed since the last report?
1. Now there are 42 external contributors, keep the same as November.
2. 2 committers were voted to join Dolphin Scheduler committers group
last month, and there is a plan to vote 3-4 more committers next month.
3. 131 users subscribed the mail(from 67 subscribers) of dev and
dev-notification and we got 113 mails formal discussions（from about 60
mails).
4. There is a plan to hold a co-meetup with Sharding Sphere in Dec, 8th
in Beijing.
### How has the project developed since the last report?
1. PPMC is voting for an Apache release 1.2.0 on Nov,27,which includes 9
features and 18 enhancements and bug fix.
2. Build a CI/CD base on Github actions.
3. Default DB is changed from MySQL to PostgreSQL.
4. 241 issues created，237 PRs merged .
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [X] Working towards first release
- [ ] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
No answer.
### When were the last committers or PPMC members elected?
2019-11-11
### Have your mentors been helpful and responsive?
Yes, our mentors help a lot on our first Apache Release, including first
time on CI/CD, license check, Apache checklist, and so on. Wu Sheng gave
us many useful advice.
### Is the PPMC managing the podling's brand / trademarks?
Yes, We keep tracking podling's brand / trademarks.
### Signed-off-by:
- [x] (dolphinscheduler) Sheng Wu
Comments: Need more works on working in Apache way, especially remote
work mode, mail list discussion and decision. Good start for a new
project. Hope they are learning fast.
- [ ] (dolphinscheduler) ShaoFeng Shi
Comments:
- [X] (dolphinscheduler) Liang Chen
Comments:
- [X] (dolphinscheduler) Furkan KAMACI
Comments:
- [X] (dolphinscheduler) Kevin Ratnasekera
Comments:
### IPMC/Shepherd notes:
--------------------
## Druid
Druid is a high-performance, column-oriented, distributed data store.
Druid has been incubating since 2018-02-28.
### Three most important unfinished issues to address before graduating:
1. The project is not aware of any issues blocking graduation. Druid
previously shelved a resolution to graduate due to a potential brand
issue, which the project has since been working on with VP Brand. It is
now no longer a concern so the project is proceeding towards graduation
once again.
### Are there any issues that the IPMC or ASF Board need to be aware of?
None
### How has the community developed since the last report?
- 2 new committers have been added
- A healthy, constant flow of bug fixes, quality improvements and new
features are still ongoing at https://github.com/apache/incubator-druid.
- Several community meetups have been held.
### How has the project developed since the last report?
- Since the last report, we have had a total of 187 commits from 34
contributors.
- We have released 1 version, 0.16.0.
- We currently have a vote open for 0.16.1, second release candidate
### 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:
Druid 0.16.0-incubating was released on Sep 24, 2019
### When were the last committers or PPMC members elected?
The Druid PPMC elected 2 new committers to the project on September 22,
2019.
The previous Sep 2019 report was incorrect here, as the two committers
were not yet officially elected then.
### Have your mentors been helpful and responsive?
As always, Julian has been quite helpful.
### Is the PPMC managing the podling's brand / trademarks?
The PPMC has from time to time reached out to have naming corrected on
third party sites. VP Brand has approved graduating as Apache Druid.
### Signed-off-by:
- [x] (druid) Julian Hyde
Comments: Though not stated in the above report, there will be a
resolution to graduate Druid at this month's board meeting.
The IP issues that caused us to pause last time have been resolved.
This is why the '3 issues to address before graduating' contains
only one issue.
- [ ] (druid) P. Taylor Goetz
Comments:
- [ ] (druid) Jun Rao
Comments:
### IPMC/Shepherd notes:
Dave Fisher - It looks like Druid will move forward with graduation soon!
--------------------
## 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 unfinished issues to address before graduating:
1. Community growth (committers and users)
2. One or more Apache Releases as an Incubator project
### Are there any issues that the IPMC or ASF Board need to be aware of?
None
### How has the community developed since the last report?
- Takuya (PPMC) gave [a talk]
(https://aceu19.apachecon.com/session/apache-hivemall-meets-pyspark-sca
lable-machine-learning-hive-spark-and-python) at ApacheCon, Europe 2019.
- Two external contributors are trying to create patches. Good sign for
community growth. (see [HIVEMALL-280]
(https://issues.apache.org/jira/browse/HIVEMALL-280) and
[HIVEMALL-186](https://issues.apache.org/jira/browse/HIVEMALL-186)
- Github watchers/stars are gradually increasing: 243 stars as of Dec 2
(was 234 on Sept 1)
- Twitter account @ApacheHivemall followers are gradually increasing: 214
followers as of Dec 2 (was 208 on Sept 1)
### How has the project developed since the last report?
- Issued and finished [a vote for v0.6.0-rc1]
(https://lists.apache.org/thread.html/fae10ab709f0e6e61f529d234a7
a8e8f7900eafa5964852e929ce803@%3Cgeneral.incubator.apache.org%3E)
(for Third ASF apache)
- In the last 3 months, we opened [19 JIRA issues and closed 49 JIRA
issues](https://goo.gl/QFQEF5). It was very active toward v0.6.0-rc1.
### 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-12-03
### When were the last committers or PPMC members elected?
Elected Jerome Banks as a committer on April 2, 2018.
### Have your mentors been helpful and responsive?
Koji is active at mentoring.
### Is the PPMC managing the podling's brand / trademarks?
- We initiate an initial podling name search and created a ticket in
[Jira](https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-176)
### Signed-off-by:
- [ ] (hivemall) Xiangrui Meng
Comments:
- [ ] (hivemall) Daniel Dai
Comments:
- [x] (hivemall) Koji Sekiguchi
Comments: Makoto Yui is very active in the community.
### IPMC/Shepherd notes:
--------------------
## IoTDB
IoTDB is a data store for managing large amounts of time series data such as
timestamped data from IoT sensors in industrial applications.
IoTDB has been incubating since 2018-11-18.
### Three most important unfinished issues to address before graduating:
1. Learn to discuss things on the mailing list, rather than just post an
ISSUE created or closed message, or discuss on Github.
2. More committers should know how to release a version. And more PPMC
should join to vote.
3. Write more documentation to help new contributors.
### Are there any issues that the IPMC or ASF Board need to be aware of?
No
### How has the community developed since the last report?
1. New contributors appears, e.g., HT Hou for PR527, liutaohua for PR578,
yx-zhang for PR540, francisdu for ISSUE293, SilverNarcissus for PR327,
nlosilva1 for PR298, Zesong Sun etc..
2. According to github's records, there are 50 contributors now.
3. New committer Jack Tsai.
4. New PPMC: Julian Feinauer
5. Twitter account is created: Apacheiotdb
6. More than 137 mails are recorded on dev@ mailing list
### How has the project developed since the last report?
1. IoTDB released v0.8.1. And vote for 0.9.0 has passed.
2. IoTDB v0.9.0 fixed 16 bugs, introduced 31 new features and 27
improvements. (According to the statistics of 0.9.0's RELEASE_NOTE)
### 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:
1. The community is more diverse than before. As far as the reporter
knows, the contributors come from more than 10 companies/organizers.
2. More users begin to report the bugs, which means that more and more
users are using IoTDB.
3. According to the reporter's view, IoTDB is more stable and has better
performance than before.
### Date of last release:
2019-10-30 (0.8.1)
### When were the last committers or PPMC members elected?
2019-11-05 for new committer and 2019-11-07 for new PPMC
### Have your mentors been helpful and responsive?
1. Few PPMCs have permissions to maintain IoTDB JIRA (e.g., add label,
close issues.). The permission may need to be fixed.
### Is the PPMC managing the podling's brand / trademarks?
Required Name Search is done. A google search didn’t show any major
branding issues that the PPMC needs to deal with.
### Signed-off-by:
- [X] (iotdb) Justin Mclean
Comments: Growing well.
- [ ] (iotdb) Christofer Dutz
Comments:
- [X] (iotdb) Willem Ning Jiang
Comments: I can see IoTDB did lot of works to growing the community,
it's in a right track now.
- [X] (iotdb) Kevin A. McGrail
Comments: Great project and great community. Love to be a witness to
their continued growth.
### IPMC/Shepherd notes:
--------------------
## Marvin-AI
Marvin-AI is an open-source artificial intelligence (AI) platform that helps
data scientists, prototype and productionalize complex solutions with a
scalable, low-latency, language-agnostic, and standardized architecture
while simplifies the process of exploration and modeling.
Marvin-AI has been incubating since 2018-08-21.
### Three most important unfinished issues to address before graduating:
1. Increase activity from current contributors and community.
2. Build compatibility with all the mainstream storages for artifact
persistence.
3. Finish the new version of Toolbox.
### Are there any issues that the IPMC or ASF Board need to be aware of?
* No.
### How has the community developed since the last report?
* We implemented Marvin in a new Fintech company "Ame Digital" in Sao
Paulo - Brazil as their main MLOps tool,
and all their data department are interested in contributing. We are
currently working together to add compatibility
with MS Azure for artifact persistence.
### How has the project developed since the last report?
* New AutoML public engines added.
* Minor bug fixes.
* Compatibility with Google Cloud BigQuery for data import added.
* AutoML module with Spark MLib in construction.
### 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:
2019-07-18
### When were the last committers or PPMC members elected?
* Wei Chen added as new PPMC member (2019-06-07)
### Have your mentors been helpful and responsive?
* Our mentors are sometimes active.
### Is the PPMC managing the podling's brand / trademarks?
Yes.
### Signed-off-by:
- [ ] (marvin-ai) Luciano Resende
Comments:
- [X] (marvin-ai) William Colen
Comments:
### IPMC/Shepherd notes:
--------------------
## MesaTEE
MesaTEE is the next-gen solution to enable general computing service for
security-critical scenarios. It will allow even the most sensitive data to
be securely processed to enable offshore businesses without leakage.
MesaTEE has been incubating since 2019-08-19.
### Three most important unfinished issues to address before graduating:
1. Finish the initial setup for MesaTEE and its sub-repos.
2. Choose a suitable name for MesaTEE and rename the repos.
3. Make the access control mechanism and RPC framework more scalable and
ergonomic.
### Are there any issues that the IPMC or ASF Board need to be aware of?
Regarding to the CI system, we do have some problem with migrating the
webhooks. MesaTEE definitely requires CI runs on customized hardware.
However, the Apache INFRA team is pretty conservative on adopting novel CI
systems which support customized hardware and self-hosted agent, such as
Github Action, Drone etc. We observed that Apache projects depending on CI
running on customized hardware, such as incubator-tvm, experienced
difficulty to migrate its webhooks and was challenged several times on the
reason of using customized hardware in CI. Besides, we observed that
Apache Spark is using Github Action, while we are blocked on it (see
INFRA-19381).
The bootstrapping process seems slow due to the above problem. We have a
temporary workaround to use our Drone CI system. It leverages a sync bot
which automatically sync up incubator-mesatee and a testing fork and
triggers the webook of the testing fork. For management, we force the
developers to put the link of CI status for each PR in their PR message.
It works, but we really desire the integration to new CI and self-hosted
CI agents.
For the renaming, we found a new name "Teaclave" which is not used
anywhere.
### How has the community developed since the last report?
MesaTEE has one more contributor this month, and merged 50+ PRs from 13
contributors.
### How has the project developed since the last report?
We implemented the new access control system in MesaPy, and merged into
MesaTEE. The new access control system is much more powerful and flexible
than traditional user/role/group based access control system, and is
memory-safe and trusted with the help of MesaPy and MesaTEE.
We improved the MesaTEE infrastructure to make it k8s-friendly. We
refactored parts of the MesaTEE system and are doing on others.
We improved the build system. We deprecated the old-fashioned Makefile,
and only kept the cmake system.
We figured out a temporary solution for integrating the Drone CI system
and self-hosted agents by syncing up incubator-mesatee and testing fork,
and triggering tests on the testing fork.
We are improving the built-in RPC framework to use prost to automatically
generate Rust source codes from protobuf's protocol definitions.
We fixed a couple of bugs reported from the open source community.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [x] Initial setup
- [ ] Working towards first release
- [ ] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
N/A
### When were the last committers or PPMC members elected?
N/A
### Have your mentors been helpful and responsive?
We received instructions on the project renaming process from our mentors.
Thanks to every one!
### Is the PPMC managing the podling's brand / trademarks?
Yes. We don't find any 3rd parties incorrectly using the podling's name
and brand for now. Also, PPMC is working on the podling name search.
### Signed-off-by:
- [x] (MesaTEE) Felix Cheung
Comments: sounds like the issue in INFRA-19381 on the way, is that
still blocked or just need more time?
- [X] (MesaTEE) Furkan Kamaci
Comments:
- [ ] (MesaTEE) Jianyong Dai
Comments:
- [X] (MesaTEE) Luciano Resende
Comments:
- [ ] (MesaTEE) Matt Sicker
Comments:
- [ ] (MesaTEE) Zhijie Shen
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 unfinished issues to address before graduating:
1. Grow the community (committers, contributors, users)
2. Create more releases
### Are there any issues that the IPMC or ASF Board need to be aware of?
None.
### How has the community developed since the last report?
- Attracted contributors through the GSoC program and
class offering
### How has the project developed since the last report?
- Preparing for a new release
- Improved code quality by addressing many sonarcloud issues
- Stream processing features implemented but not merged yet
into the master
### 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:
Release 0.1 on Dec. 31, 2018
### When were the last committers or PPMC members elected?
None yet.
We have a couple of candidates we would like to invite.
### Have your mentors been helpful and responsive?
Yes.
### Is the PPMC managing the podling's brand / trademarks?
Yes.
### Signed-off-by:
- [X] (nemo) Hyunsik Choi
Comments:
- [X] (nemo) Byung-Gon Chun
Comments:
- [ ] (nemo) Jean-Baptiste Onofre
Comments:
- [X] (nemo) Markus Weimer
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 unfinished issues to address before graduating:
1. Revitalize the project by resuming development
2. Enlarge the user base and contributing community
### Are there any issues that the IPMC or ASF Board need to be aware of?
Nothing important. It took more than 2 months to create the account
of Corey Sterling, as it seems that some things are still done manually,
and there was a mistake with his email address. Finally, we could solve
it out.
### How has the community developed since the last report?
* Mailing list activity:
* @dev: 33 messages
### How has the project developed since the last report?
* Retirement has been suggested due to its very low activity
* To restart engagement, Corey Sterling has been elected as commiter in
late August. With his help, we prepared a new release of Apache
SAMOA, that is already being discussed and voted (RC).
### 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?
August 2019
### Have your mentors been helpful and responsive?
Yes, the mentors have been helpful and responsive.
### Is the PPMC managing the podling's brand / trademarks?
Yes. There are no 3rd parties incorrectly using the podling‘s name and
brand for now.
### Signed-off-by:
- [X] (samoa) Alan Gates
Comments:
- [ ] (samoa) Ashutosh Chauhan
Comments:
### IPMC/Shepherd notes:
--------------------
## APISIX
APISIX is a cloud-native microservices API gateway, delivering the
ultimate performance, security, open source and scalable platform
for all your APIs and microservices.
APISIX is based on Nginx and etcd. Compared with traditional API gateways,
APISIX has dynamic routing and plug-in hot loading, which is especially
suitable for API management under micro-service system.
### Three most important unfinished issues to address before graduating
1. More Apache Releases and more committers act as release manager to
release a version.
2. More committers and PPMC members.
3. Branding issues in the documentation, code, website, etc.
### Are there any issues that the IPMC or ASF Board need to be aware of?
None
### How has the community developed since the last report?
- We are proud to have launched the first apache release (0.9).
- Learning Apache way and its value behind rules, working in Apache way.
- We have 13 committers and 46 contributors (including 13 committers)
contributing to Apache APISIX.
- PPMC members of Apache APISIX elected a new committer
lilien1010@HelloTalk, who is the first non-initial committer.
### How has the project developed since the last report?
The project has been quite health, with more than 88 pull requests,
83 of them have being merged in November. These pull requests are authored
by a diverse set of contributors. We also suggest and guide users from
QQ group to make issues at Apache APISIX mailing list, which is helpful
for people who have the same issue and tracking bugs. The active and busy
dev subscribe mailing list dev@apisix.apache.org has received more than
120 emails with various subjects, all of which are well repled.
Some highlights of recent developments:
- Launched the first apache release 0.9.
- Added advanced debug mode which is friendly to the developers.
- Added new uri redirect plugin.
- Use an entirely new jsonschema which performance increase by
an order of magnitude.
- Enable HTTP2 support and settings for ssl_protocols.
### 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:
* Mon Nov 25 2019 (0.9)
### When were the last committers or PPMC members elected?
* At Nov 28 2019 PPMC members elected a new commiter @lilien1010
who worked for HelloTalk.
### Have your mentors been helpful and responsive?
Mentors are responsive and helpful. Things tend to be on the right way.
### Is the PPMC managing the podling's brand and trademarks?
At present, there are still some brand and trademarks problems. `APISIX`
was the name of `Apache APISIX` before entering the incubator, so the
search results of `APISIX` currently obtained through the search engine
actually belongs to `Apache APISIX` and are completely controllable.
### Signed-off-by:
- [X] (APISIX) Willem Ning Jiang
Comments: Congratulation to the first release of APISIX, this
podling is in a good track now.
- [X] (APISIX) Justin Mclean
Comments: Off to a very goos start.
- [X] (APISIX) Kevin Ratnasekera
Comments:
- [X] (APISIX) Von Gosling
Comments: Good shape.
### IPMC/Shepherd notes:
--------------------
## ShardingSphere
ShardingSphere is an ecosystem of transparent distributed database
middleware,
focusing on data sharding, distributed transaction and database
orchestration.
ShardingSphere has been incubating since 2018-11-10.
### Three most important unfinished issues to address before graduating:
1. Clear Brand issues with other ecosystem projects.
2. Further ASF culture and processes.
3. Make more apache releases.
### Are there any issues that the IPMC or ASF Board need to be aware of?
No. Right now, the brand issues are under control, so we think board or
IPMC may do not need do any actions for now.
There are still several related project on GitHub org in ShardingSphere
ecosystem, before or during project joined the ASF incubator, such as
extension modules, extension module examples and acceptance test are not
in Apache repo.
We have already moved some extension modules into Apache repo,
and plan to transfer all of them soon.
### How has the community developed since the last report?
1. Ya Li, Zhiyi Yan have been voted and joined as committer.
2. There are 89 people to contribute codes to the main repo, there are 15
new contributors during last report.
We are happy to see the community are growing up.
3. Over 100 companies have confirmed they are using ShardingSphere
through issue report, and show at powered-by page[1].
Individuals from different companies and communities have provided
some patches to feed back ShardingSphere community.
4. Share a topic for Apache way and how to join ShardingSphere community
in Apache meetup at Tsinghua University.
5. Finish Podling Maturity Assessment for ShardingSphere[2].
6. Plan to establish a co-meetup with Apache DolphinScheduler(incubator)
in Beijing at Dec 8th.
[1]https://shardingsphere.apache.org/community/en/poweredby/
[2]https://cwiki.apache.org/confluence/display/SHARDINGSPHERE/Podling
+Maturity+Assessment+for+ShardingSphere
### How has the project developed since the last report?
1. Release 4.0.0-RC3 last month, main features are UI and SQL92 supported.
2. Accept donated sharding-scaling project and will merge to trunk before
next release.
3. Plan to release 4.0.0 stable version soon.
### 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:
2019-11-22
### When were the last committers or PPMC members elected?
2019-11-13
### Have your mentors been helpful and responsive?
Mentors are responsive and helpful. Things tend to be on the right way.
### Is the PPMC managing the podling's brand / trademarks?
Yes. We don't find any 3rd parties incorrectly using the podling‘s name
and brand for now.
### Signed-off-by:
- [x] (shardingsphere) Craig L Russell
Comments:
- [ ] (shardingsphere) Benjamin Hindman
Comments:
- [X] (shardingsphere) Willem Ning Jiang
Comments: Shardingsphere made a very good progress of growing the
community, I think it's time to consider the graduation.
- [X] (shardingsphere) Von Gosling
Comments: developer community is very active in github issues and pr.
IMO, if we could take brand / trademarks well in the next, it would
be nice to call for graduation.
### IPMC/Shepherd notes:
--------------------
## Spot
Apache Spot is a platform for network telemetry built on an open data model
and Apache Hadoop.
Spot has been incubating since 2016-09-23.
### Three most important unfinished issues to address before graduating:
1. Revive community activity (Discussion in mailing lists, increase
frequency of commits)
2. Create a new roadmap and release plan that will improve adoption.
3. Make it easier to contribute to the project (e.g. documentation,
framework).
### Are there any issues that the IPMC or ASF Board need to be aware of?
No
### How has the community developed since the last report?
There are community members that have reached out and are interested in
contributing, but there are only a couple of active committers at this
time. Currently the main hurdle for new contributors is the amount of
effort required today to deploy Spot and build development environments.
### How has the project developed since the last report?
Open PRs with sufficient votes against the master branch and SPOT-181
epic have been merged. There's also been a substantial amount of work
to categorize all of the open JIRAs into a Project board on Github to
help the community more easily triage high priority issues, organize
feature enhancements into future epics, clean-up closed tickets, and
also group issues that require more information from the community
before taking action. Additionally there's been some work to clean-up
the asf-site branch, and minor updates (PRs are being pushed soon).
There's a larger project to re-organize the asf-site to make it easier
for the community to update and add new pages, but that hasn't started
yet.
The project with the most priority going forward is to make Spot easier
to deploy. There's a large learning curve for deploying Spot today, which
makes it difficult for both users and committers to be successful when
standing up Spot, using certain features, testing, and making
contributions back into the project. Using Cloudbreak to stand-up an
environment and deploying Spot as an Ambari package will help lower the
barriers to entry for new and existing users and contributors alike.
We expect during this project that we'll also uncover a number of deployment
issues and incompatibilities along the way and by resolving these will also
help bring confidence to users that this new deployment pattern will be
better tested and reliable.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [x] Initial setup
- [x] Working towards first release
- [x] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
2017-09-08
### When were the last committers or PPMC members elected?
2018-01-18
### Have your mentors been helpful and responsive?
Yes
### Is the PPMC managing the podling's brand / trademarks?
Yes
### Signed-off-by:
- [X] (spot) Uma Maheswara Rao G
Comments: Community is not active in mailing lists. I have not seen
any discussions on release plans etc. I don't see committers/PPMC
responding to queries on dev list. I am concerned on community
building as well. With this pace, I don't think project can apply
for graduation in near future time.
### IPMC/Shepherd notes:
--------------------
## StreamPipes
StreamPipes is a self-service (Industrial) IoT toolbox to enable non-
technical users to connect, analyze and explore (Industrial) IoT data
streams.
StreamPipes has been incubating since 2019-11-11.
### Three most important unfinished issues to address before graduating:
1. Finish the initial setup
2. Make a first Apache release
3. Grow the community
### Are there any issues that the IPMC or ASF Board need to be aware of?
There are no issues right now.
### How has the community developed since the last report?
All initial committers have subscribed to the new mailing list.
We started to spread the project on Twitter and other channels to
reach more potential community members, but currently, the main priority
is to move the project infrastructure to Apache.
There was also one event focused on extending the developer base:
* We gave a talk at a meetup on "Self-Service IoT Data Analytics with
StreamPipes" (~70 participants)
### How has the project developed since the last report?
This is the first report after StreamPipes joined the incubator on
November 11th.
Most work during the last month was focused around setting up StreamPipes
and doing some legal paperwork to transition StreamPipes to Apache:
* Creation of mailing lists
* Setting up the new StreamPipes Jira
* We made a last pre-Apache release and started to refactor our code
(restructuring the code base to reflect the new repository structure)
* The website and documentation is already moved to Apache Git
repositories,
and a draft is online at streampipes.apache.org, however, we need to wait
to "announce" the web page and forward traffic from the existing
domains untilthe Git repos are all transferred
* All initial committers have signed and submitted their ICLAs
* FZI has submitted a CCLA and donated the initial code base to Apache
* Right now, we are waiting to transfer our existing Git repos from the
streampipes organization to the Apache organization on Github
* We are also waiting to get admin access to the StreamPipes instance on
Jira to import existing issues to the new issue tracker
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [x] Initial setup
- [ ] Working towards first release
- [ ] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
XXXX-XX-XX
### When were the last committers or PPMC members elected?
No new committers were elected beyond the initial committers.
We'll focus on attracting new committers once the initial setup is
finished.
### Have your mentors been helpful and responsive?
We would really like to thank our mentors. Chris was very helpful and
responsive in setting up the infrastructure, and all questions we had
on the mailing list were answered immediately by our mentors.
### Is the PPMC managing the podling's brand / trademarks?
* We initiated an initial podling name search and created a ticket to get
the name approved in Jira (November 25th).
* The name "Apache StreamPipes" got approved by VP Brand Management on
December, 12th
### Signed-off-by:
- [X] (streampipes) Christofer Dutz
Comments:
- [ ] (streampipes) Jean-Baptiste Onofré
Comments:
- [ ] (streampipes) Julian Feinauer
Comments:
- [X] (streampipes) Justin Mclean
Comments:
- [ ] (streampipes) Kenneth Knowles
Comments:
### IPMC/Shepherd notes:
--------------------
## Superset
Apache Superset (incubating) is a modern, enterprise-ready business
intelligence web application.
### Graduation Progress
A list of the three most important issues to address in the move towards
graduation.
1. Get the trademark search / name approved; Suitable name search has
been submitted.
### How has the project developed since the last report?
- 2-3 more official ASF releases
- New committer + PMC Daniel Gaspar
- Submitted our [suitable name
search](https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-173)
(waiting for approval)
- Major dev milestones:
-- Enhancing Big Query integration
-- Improving Elastic search and Superset
### 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:
November 26th, 2019 (0.35.1), released by user: dgaspar
[https://www.apache.org/dist/incubator/superset/0.35.1](https://www.apache.o
rg/dist/incubator/superset/0.35.1)
### How has the community developed since the last report?
- Organic growth of our Github Contributors:
-- Stars (25,200 → 27,034)
-- Forks (5076→ 5,400)
-- Watchers (1212 → 1,245)
- Added 295 commits (August, Sept, November to date)
- Grew Superset slack users to (973→ 1,023)
- Set up Meetup Group w/ Bug Bash + Happy Hour with first meetup on 12/2
in partnership with other committers
- Published by Community Members:
[https://engineering.linkedin.com/blog/2019/an-inside-look-at-linkedins-data
-pipeline-monitoring-system-](https://engineering.linkedin.com/blog/2019/an-
inside-look-at-linkedins-data-pipeline-monitoring-system-)
### When were the last committers or PPMC members elected?
- Daniel Gaspar (committer + PPMC) - announced september 27th
### Have your mentors been helpful and responsive?
Yes, Alan Gates validates and votes on releases, and are generally
responsive when we ask for their attention.
### Is the PPMC managing the podling's brand / trademarks?
Yes.
### Signed-off-by:
- [ ] (superset) Ashutosh Chauhan
Comments:
- [ ] (superset) Luke Han
Comments:
- [X] (superset) Alan Gates
Comments: After a slow start the Superset
podling has really picked up momentum. They are consistently making
releases and have been adding new members to the community. It is good
to see.
- [X] (superset) Jakob Homan
Comments:
### IPMC/Shepherd notes:
-----------------------------------------
Attachment AE: Report from the Apache Jackrabbit Project [Marcel Reutegger]
Apache Jackrabbit: Board Report December 2019
=============================================
## 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 main development branch are continuously seeing moderate to
high activity.
We continue making regular feature releases of Jackrabbit Oak. The most recent
release was Jackrabbit Oak 1.20.0 that was made available on November 25th.
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 Jackrabbit Oak.
## Health report:
The project is healthy with a continuous stream of traffic on all mailing
lists reflecting the activity of the respective component.
There is a wide range of topics being discussed on the dev and user lists as
well as on the various JIRA issues.
Commit activity is moderate to high mirroring the activity on the JIRA issues
and the desire of the individual contributors to bring features and
improvements in for the next Jackrabbit Oak release.
## PMC changes:
- Currently 56 PMC members.
- No new PMC members. Last additions were Mohit Kataria and Nitin Gupta on
2019-08-08.
## Committer base changes:
- Currently 56 committers.
- No new committers. Last additions were Mohit Kataria and Nitin Gupta on
2019-08-08.
## Releases:
- jackrabbit-2.14.8 was released on 2019-09-12
- jackrabbit-oak-1.8.17 was released on 2019-09-16
- jackrabbit-filevault-3.4.0 was released on 2019-09-16
- jackrabbit-oak-1.10.5 was released on 2019-09-18
- jackrabbit-oak-1.18.0 was released on 2019-09-30
- jackrabbit-2.19.5 was released on 2019-10-10
- jackrabbit-oak-1.6.18 was released on 2019-10-15
- jackrabbit-2.18.4 was released on 2019-11-08
- jackrabbit-oak-1.10.6 was released on 2019-11-12
- jackrabbit-oak-1.20.0 was released on 2019-11-25
- jackrabbit-oak-1.8.18 was released on 2019-11-29
- jackrabbit-2.19.6 was released on 2019-12-10
## JIRA activity:
- 261 JIRA tickets created in the last 3 months
- 255 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AF: Report from the Apache jUDDI Project [Alex O'Ree]
## Description:
- jUDDI (pronounced "Judy") is an open source Java implementation of the
Universal Description, Discovery, and Integration (UDDI v3) specification
for (Web) Services. The jUDDI project includes Scout. Scout is an
implementation of the JSR 93 - Java API for XML Registries 1.0 (JAXR).
## Issues:
- There are no issues that require the board's attention at this time.
If the board has explicit requirements for future reports, please
make it available. It is not always clear how much level of detail
is required and I generally prefer not to bother the board for trivial
issues or for issues in which no action is needed from the board.
## Activity:
- jUDDI - last release was 04 DEC 2018. Resolved several requisite bugs for
updating SCOUT. A demo site has been stood up on ASF INFRA at
https://demo.juddi.apache.org.
Next release planned before the end of the year.
- SCOUT - last release 10 DEC 2018. Resolved several bugs and dependencies.
## Health report:
- Low development activity is a factor for low mailing list volume, but in all
likelihood, it's from a general lack of interest in the protocol.
- There has been some new feature development recently related to enhanced
security and access control mechanisms.
- There are enough active PMC members to approve releases and respond to
potential security issues. There were no issues raised since the last
report.
## PMC changes:
- Currently 7 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Alex O'Ree on Sun Mar 17 2013
## Committer base changes:
- There are currently 7 committers and 7 PMC members in this project.
- The Committer-to-PMC ratio is 1:1.
- No new changes to the committer base since last report.
## Releases:
- 3.3.6 was released on Tue Dec 04 2018
- SCOUT-1.2.8 was released on Mon Dec 10 2018
## JIRA activity:
- 1 JIRA tickets created in the last 3 months
- 0 JIRA tickets closed/resolved in the last 3 months
## Commit activity:
- 0 commits in the past quarter
- 0 code contributors in the past quarter
-----------------------------------------
Attachment AG: Report from the Apache Karaf Project [Jean-Baptiste Onofré]
## Description:
Apache Karaf provides a modern and polymorphic applications runtime,
multi-purpose (microservices, cloud, IoT, OSGi, etc).
## Issues:
There are no issues requiring board attention at this time
## Membership Data:
Apache Karaf was founded 2010-06-16 (9 years ago)
There are currently 31 committers and 17 PMC members in this project.
The Committer-to-PMC ratio is roughly 8:5.
Community changes, past quarter:
- No new PMC members. Last addition was Francois Papon on 2018-11-29.
- No new committers. Last addition was Francois Papon on 2018-05-19.
## Project Activity:
We did a complete refactoring on Karaf Cave and did two releases:
* Cave 4.2.1 was released on 2019-12-02.
* Cave 4.2.0 was released on 2019-10-31.
We also did a Karaf runtime maintenance release:
* 4.2.7 was released on 2019-09-29.
We also vote the donation of Winegrower as new Apache Karaf subprojec.
A first Winegrower release will happen soon.
## Community Health:
* dev@karaf.apache.org had a 82% increase in traffic in the past quarter
(223 emails compared to 122)
* user@karaf.apache.org had a 35% increase in traffic in the past quarter
(405 emails compared to 298)
* 126 issues opened in JIRA, past quarter (53% increase)
* 98 issues closed in JIRA, past quarter (66% increase)
* 199 commits in the past quarter (61% increase)
* 19 code contributors in the past quarter (72% increase)
* 118 PRs opened on GitHub, past quarter (81% increase)
* 115 PRs closed on GitHub, past quarter (101% increase)
We also started and helped other communities during the past quarter:
* discussion with Apache PLC4X about OSGi/Karaf adoption
* help Apache Unomi to upgrade to the latest Karaf releases branch
-----------------------------------------
Attachment AH: Report from the Apache Labs Project [Danny Angus]
## Description:
The mission of Labs is the creation and maintenance of software related to A
place for innovation where committers of the foundation can experiment with new
ideas.
Per our charter Labs does not make releases.
## Issues:
There are no issues that require board attention.
## Membership Data:
Apache Labs was founded 2006-11-15 (13 years ago)
There are currently 31 committers and 10 PMC members in this project.
The Committer-to-PMC ratio is roughly 8:3.
Community changes, past quarter:
- No new PMC members. Last addition was Simone Tripodi on 2011-06-14.
- No new committers. Last addition was Juan P. Gilaberte on 2018-05-30.
## Project Activity:
Labs has one open experiment, but there has been no activity this past quarter.
## Community Health:
Labs is inactive, but not without oversight.
It may be time to carry out another roll call.
-----------------------------------------
Attachment AI: 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.
## Project Activity
We released 3 new releases since the last report. That includes 2
releases with major new changes and improvements
We are also looking at releasing v3.0.0 early next year which will drop
support for Python 2.7 and Python 3.4. This date coincides with Python
2.7 EOL (January 2020).
This will allow us to simplify the code base and remove a lot of boiler
plate code which is / was needed to support Python 2 and Python 3 through
a single code base.
## Community Health
Community state is similar to the one in the last report.
We have received a good amount of activity on Github (this includes
merging multiple community contributed pull requests).
We also received a good amount of downloads / installations on PyPi (primary
method of installing the library) -
https://pypistats.org/packages/apache-libcloud.
## Membership Data
- Currently 13 PMC members.
- No new PMC members added in the last 3 months
- Currently 22 committers.
- Clemens Wolff was added as committer on 2019-07-15
## Releases
- 2.7.0 was released on December 9, 2019
- 2.6.1 was released on November 18, 2019
- 2 6.0 was released on August 28, 2019
- 2.5.0 was released on May 30, 2019
-----------------------------------------
Attachment AJ: Report from the Apache Lucene Project [Cassandra Targett]
## Description:
- Lucene Core is a search-engine toolkit
- Solr is a search server built on top of Lucene Core
- PyLucene is a Python extension for accessing Lucene
## Issues:
During this quarter, one member of the PMC publicly called out the significant
tech debt Solr specifically is carrying with regard to features collectively
called "SolrCloud" (Solr's distributed mode) as a way of spurring us to action
(https://s.apache.org/66ri1).
The PMC realizes that the state of SolrCloud efficiency, reliability, and code
is something that needs to be improved drastically to better suit the needs of
ever-increasing scale of deployments and workloads that Solr is being used
for. Towards that, we recognize the challenges, and have solutions that we're
aggressively working towards.
The PMC feels we have this situation under control, and now need to follow
through with improvements in this area.
## Membership Data:
Apache Lucene was founded 2005-01-18 (15 years ago)
There are currently 82 committers and 53 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:2.
Community changes, past quarter:
- No new PMC members. Last addition was Kevin Risden on 2019-06-25.
- Atri Sharma was added as committer on 2019-09-18
- Bruno Roustant was added as committer on 2019-11-22
- Houston Putman was added as committer on 2019-11-13
## Project Activity:
We released Lucene and Solr 8.3 and 8.3.1 since the last report.
With 8.3, we expanded our Spanish language support in Lucene, as well as added
new PostingsFormats and several optimizations and enhancements. Solr added
support for two-dimensional collection aliases and improvements to caching and
math streaming expression support.
An 8.3.1 release was made for Solr to provide an emergency fix for a
corruption issue and lock our integration with Velocity from being able to
load external resources except when explicitly allowed by the system
administrator.
We are just beginning the release process for Lucene and Solr 8.4 and hope to
have that completed before the end of 2019.
PyLucene is actively voting on a 8.3.0 release.
We are still working to change our build system from Ant to Gradle. We are
making progress on that front, and hope it will be complete before the next
board update.
We are also working on migrating our project website from being built with the
CMS (via SVN) to being built with Pelican (via Git).
We are making a couple of changes to how we work together:
* We're discussing how to semi-require code reviews by defining project
guidelines. We invite a board member to help/advice how to navigate this
balance.
* We're discussing use of a new "Solr Improvement Process" inspired from those
of other projects, e.g. Kafka Improvement Process (KIP).
* We started a quarterly virtual committer meeting by video conference.
## Community Health:
Due to the changes we made right before the last report to the board to move
Jira and Jenkins notifications to their own lists, activity in our devs@lucene
list declined dramatically (-82%). I think I speak for all of us, however, in
saying that it is much easier to follow conversations now.
The main Lucene user list (java-user@lucene) saw a 50% decline in traffic,
while the main Solr user list (solr-user@lucene) saw a 19% increase. I'm not
sure there is anything to worry about in regard to the Lucene list decline,
but we will continue to monitor it.
Code contributions remain quite strong: we had 1560 commits (-18%) from 86
contributors (+10%_ and a 19% increase (197) in GitHub pull requests compared
to last quarter.
-----------------------------------------
Attachment AK: Report from the Apache Lucene.Net Project [Shad Storhaug]
Apache Lucene.Net is a port of the Lucene search engine library, written in C#
and targeted at .NET runtime users.
== Summary ==
There has been some progress in the last couple of months:
The broken NativeFSLock has been fixed for non-Windows platforms. The
remaining Lucene 4.8.0 modules, Lucene.Net.Analysis.OpenNLP (the Lucene 8.3
replacement for Lucene.Net.Analysis.UIMA) and Lucene.Net.Analysis.Mofologik
and its dependencies have been ported. ICU4N has had some API refactoring to
be more .NET-like and the API documentation comments have been (mostly)
completed. ICU4N has also had 2 releases on NuGet. A new project named J2N was
started to host the JDK-like types that were haphazardly lumped into the
“Support” namespace in both Lucene.NET and ICU4N. Full API documentation and
tests are being added, bugs fixed, as well as optimizations and finished
implementations. J2N has had 2 alpha releases to date. Now that the porting
work is complete, the focus has shifted to improving performance. Some
bottlenecks and potential bottlenecks have been identified, a few of which
have already been addressed. The API doc website (and the automation to
generate it) is continuing to be improved (thanks @Shannon Deminick and @Steve
Temple). It has been determined that NUnit has adequate repeatability for end
users to be able to debug random tests without having to port the
RandomizedTesting runner (which was previously our biggest remaining task).
Additionally, Aaron Powell blogged about Lucene.NET recently
(https://dev.to/dotnet/implementing-search-in-blazor-webassembly-with-lucene-net-4mpi)
and it was re-tweeted by Jon Galloway from Microsoft this week. Thanks Aaron
and Jon!
The mailing lists have been pretty quiet, and no new issues have been opened
recently. However, we are working on getting another beta release out soon.
== Remaining Work on 4.8.0 ==
We updated the itemized list of remaining issues for both Lucene.NET and ICU4N
and have arrived at the following estimates to production release:
Lucene.NET 4.8.0
Hours Completed: ~3850 Hours Remaining: ~600
ICU4N 60.x
Hours Completed: ~500 Hours Remaining: ~300 (assuming we don’t port any more
of it) Hours Remaining: ~750 (ported to feature completion)
Lucene.NET 8.x Upgrade
Hours Completed: 0 Hours Remaining: ~1700
The primary items left to complete for the 4.8.0 release are migrating the
remaining types from Support to J2N (with improved implementations, tests, and
benchmarks), the API docs, and ICU4N.
== Releases ==
* Last Release 3.0.3 - Oct 2012
* Working toward 4.8.0 - Currently beta0006, released 2019-08-13
== People ==
* Last PMC Member added May 2017, Shad Storhaug (nightowl888)
* Last committer added Oct 2019, Shannon Deminick (shazwazza)
* PMC Chair rotated 20 June 2018 to Shad Storhaug (nightowl888)
== Statistics ==
As of 2019.12.13 Metric are as follows (followed by metric from 2019.10.10 for
comparison):
Release 3.0.3
* Lucene.Net 3.0.3: 3,095,953 (up from 2,737,979)
* Lucene.Net.Contrib 3.0.3: 671,201 (up from 601,751)
* Lucene.Net Contrib Spatial: 37,415 (up from 34,273)
* Lucene.Net Contrib Spatial.NTS: 7,177 (up from 6,986)
Beta 4.8.0-beta00005 (Published 10/24/2017)
* Lucene.Net: 206,059 (up from 177,945 )
* Lucene.Net.Analysis.Common: 189,268 (up from 164,168 )
* Lucene.Net.Analysis.Kuromoji: 5,911 (up from 5,070 )
* Lucene.Net.Analysis.Phonetic: 3,104 (up from 2,506)
* Lucene.Net.Analysis.SmartCn: 614 (up from 583)
* Lucene.Net.Analysis.Stempel: 1,221 (up from 1,141)
* Lucene.Net.Benchmark: 530 (up from 523)
* Lucene.Net.Classification: 1,090 (up from 1,065)
* Lucene.Net.Codecs: 3,381 (up from 3,125)
* Lucene.Net.Expressions: 6,441 (up from 6,065)
* Lucene.Net.Facet: 10,065 (up from 8,794)
* Lucene.Net.Grouping: 11,905 (up from 10,059)
* Lucene.Net.Highlighter: 6,012 (up from 5,251)
* Lucene.Net.ICU: 974 (up from 923)
* Lucene.Net.Join: 10,328 (up from 9,055)
* Lucene.Net.Memory: 11,180 (up from 9,171)
* Lucene.Net.Misc: 7,342 (up from 6,507)
* Lucene.Net.Queries: 167,030 (up from 144,937)
* Lucene.Net.QueryParser: 159,701 (up from 138,434)
* Lucene.Net.Replicator: 567 (up from 560)
* Lucene.Net.Sandbox: 165,227 (up from 144,268)
* Lucene.Net.Spatial: 6,363 (up from 5,553)
* Lucene.Net.Suggest: 6,316 (up from 5,604)
Beta 4.8.0-beta00006 (Published 08/13/2019)
* Lucene.Net: 21,486 (up from 4,989)
* Lucene.Net.Analysis.Common: 19,556 (up from 4,351)
* Lucene.Net.Analysis.Kuromoji: 147 (up from 93)
* Lucene.Net.Analysis.Phonetic: 129 (up from 72)
* Lucene.Net.Analysis.SmartCn: 268 (up from 138)
* Lucene.Net.Analysis.Stempel: 128 (up from 62)
* Lucene.Net.Benchmark: 57 (up from 47)
* Lucene.Net.Classification: 157 (up from 91)
* Lucene.Net.Codecs: 145 (up from 93)
* Lucene.Net.Expressions: 121 (up from 65)
* Lucene.Net.Facet: 687 (up from 125)
* Lucene.Net.Grouping: 750 (up from 141)
* Lucene.Net.Highlighter: 812 (up from 240)
* Lucene.Net.ICU: 269 (up from 125)
* Lucene.Net.Join: 732 (up from 140)
* Lucene.Net.Memory: 1,252 (up from 259)
* Lucene.Net.Misc: 585 (up from 139)
* Lucene.Net.Queries: 17,847 (up from 4,024)
* Lucene.Net.QueryParser: 17,674 (up from 3,989)
* Lucene.Net.Replicator: 62 (up from 53)
* Lucene.Net.Sandbox: 17,657 (up from 3,992)
* Lucene.Net.Spatial: 174 (up from 98)
* Lucene.Net.Suggest: 438 (up from 130)
* lucene-cli: 115 (up from 74)
-----------------------------------------
Attachment AL: 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, 1 of tickets has been created and
1 resolved, basically, We added a new feature to support PMDK based
Persistent memory infrastructure and improved the code according to
community contributor's feedback, there are still some bugs at the
service part, those bugs is very difficult to diagnose, we may need
more contributors to invest engineering efforts on that to make memory
service stable and mature to use.
Health Report:
Basically unchanged since the last report. Users are generally quiet
in public but development continues.
PMC Changes:
- Currently 12 PMC members.
- no new PMC member added since Jun. 2018.
Committer Base Changes:
- Currently 13 committers.
- No new committer added since Jun. 2018.
Releases:
- Last release was v0.12.0 on Sep. 04 2018
- Still active development on next major version (0.13)
-----------------------------------------
Attachment AM: Report from the Apache Mynewt Project [Justin Mclean]
## Description:
Mynewt is a real-time operating system for constrained embedded systems like
wearables, lightbulbs, locks and doorbells. It works on a variety of 32-bit
MCUs (microcontrollers), including ARM Cortex-M, RISC-V and MIPS
architectures.
The mission of Apache Mynewt is the creation and maintenance of software
related to an embedded OS optimized for networking and built for remote
management of constrained devices that are incapable of running either Linux or
Android
## Issues:
None.
## Membership Data:
Apache Mynewt was founded 2017-06-21 (2 years ago)
There are currently 33 committers and 19 PMC members in this project.
The Committer-to-PMC ratio is roughly 9:5.
Community changes, past quarter:
- Jerzy Kasenberg was added to the PMC on 2019-10-24
- Hauke Petersen was added as committer on 2019-11-13
- Niklas Casaril was added as committer on 2019-11-12
## Project Activity:
Work on release 1.8.0 in January 2020
- NimBLE 1.3 stack release at same time
- BT 5.1 features are being added to NimBLE stack
- Community work in several areas including:
test facilities, new BLE features, internal code improvements and
refactoring, new core features (eg USB support)
- Continued work on core decoupling - next release will be first to use
apache-mcumgr instead of internal fork
- github PRs are mostly reviewed in timed fashion
## Community Health:
# Mailing list activity:
- Mailing list activity seeing new users and responders to questions asked
(esp. questions from newcomers)
- Mailing list exchanges are mostly around BLE, image management and low level
core details
- Mailing list activity has dropped slightly compared to last quarter
- Some questions on mailing list remained without response
- Slack activity is up and more users have joined
# GitHub Issues activity:
- Issue types seen include change/feature requests, bug reports,
contributions/PR, Q&A
-----------------------------------------
Attachment AN: Report from the Apache NetBeans Project [Geertjan Wielenga]
## Description:
The mission of Apache NetBeans is the creation and maintenance of software
related to development environment, tooling platform, and application framework.
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache NetBeans was founded 2019-04-17 (8 months ago)
There are currently 69 committers and 63 PMC members in this project.
The Committer-to-PMC ratio is roughly 1:1.
Community changes, past quarter:
- No new PMC members. Last addition was Sarvesh Kesharwani on 2019-06-06.
- Gaurav Gupta was added as committer on 2019-11-15
## Project Activity:
- Apache NetBeans 11.2 was released on 2019-10-25, with thanks to Neil C Smith
for managing the process awesomely.
- Apache NetBeans 11.3 to be released in early 2020, with Eric Barboni planned
as release manager.
- Related projects, e.g., HTMLJAVAAPI-1.7, Maven artifacts, and installer
bundles, have also been released in this period.
- 4th donation completed, providing C/C++ and dark look and feel.
- Waiting for next donation of dtrace/dlight, related to C/C++, before
integrating C/C++ features.
- Plugin portal transition continuing, available at new location here, with
thanks to Jiri Kovalsky and Jan Pirek:
http://netbeans-vm.apache.org/pluginportal/
- New NetBeans book to be published soon by Apress, with several Apache
NetBeans community members involved, excellently led by John Kostaras.
- Strong Apache NetBeans presence at GDG Istanbul, enthusiastically led by
Mark Stephens.
## Community Health:
dev@netbeans.apache.org had a 22% increase in traffic in the past quarter
(1523 emails compared to 1246)
469 issues opened in JIRA, past quarter (9% increase)
183 issues closed in JIRA, past quarter (3% increase)
633 commits in the past quarter (69% increase)
46 code contributors in the past quarter (6% increase)
300 PRs opened on GitHub, past quarter (16% increase)
282 PRs closed on GitHub, past quarter (11% increase)
-----------------------------------------
Attachment AO: Report from the Apache OFBiz Project [Jacopo Cappellato]
## Description:
Apache OFBiz is an open source product for the automation of enterprise
processes that includes framework components and business applications for ERP
(Enterprise Resource Planning), CRM (Customer Relationship Management),
E-Business / E-Commerce, SCM (Supply Chain Management), MRP (Manufacturing
Resource Planning), MMS/EAM (Maintenance Management System/Enterprise Asset
Management). Apache OFBiz provides a foundation and starting point for
reliable, secure and scalable enterprise solutions.
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache OFBiz was founded 2006-12-20 (13 years ago)
There are currently 49 committers and 23 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:3.
Community changes, past quarter:
- Mathieu Lirzin was added to the PMC on 2019-11-12
- Gil Portenseigne was added to the PMC on 2019-11-08
- Pranay Pandey was added to the PMC on 2019-09-24
- No new committers. Last addition was Deepak Nigam on 2019-06-12.
## Project Activity:
- The main event in the last quarter has been the migration from svn to Git;
thanks to our committers and to the amazing Infra team the migration was
smooth and it is completed now; we are now reviewing with our community the
best practices for contributions in order to leverage the advantages offered
by the new versioning system
- Various bug fixes and enhancements have been contributed and committed to
the trunk and backported to the various release branches
- Trademarks: we do not have trademark related concerns at the moment and our
backlog of non-compliant parties is mostly empty [1]
- More details about the community activities are published in the official
blog [3], on Twitter [4] and other social media [5].
[1] https://svn.apache.org/repos/private/pmc/ofbiz/trademarks/trademarks.txt
[2] https://svn.apache.org/repos/private/pmc/ofbiz/security/vulnerabilities.txt
[3] https://blogs.apache.org/ofbiz/
[4] https://twitter.com/ApacheOfbiz
[5] https://www.facebook.com/Apache-OFBiz-1478219232210477/
## Community Health:
since our last report we have added three new PMC members; the vote for one of
them started at the time we submitted our previous report while the other two
have been invited after we reviewed our committers group in search for
potential PMC members, as suggested by this Board in response to our last
report; we have other candidates in our watchlist and we will do our best to
grow both groups as soon as we identify good candidates; as usual the
community is actively involved in improving the trunk, fixing vulnerabilities,
stabilizing the release branches and in various discussions and support
requests posted mostly in the mailing list and in our issue tracker.
-----------------------------------------
Attachment AP: Report from the Apache Olingo Project [Michael Bolz]
## Description:
The Apache Olingo Project is responsible for the creation and maintenance of
software related to providing an implementation of the OASIS OData (Open Data
Protocol) specifications, in server and client form; 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.
## Issues:
There are no issues requiring board attention at this time
## Membership Data:
Apache Olingo was founded 2014-03-19 (5 years ago)
There are currently 25 committers and 15 PMC members in this project.
The Committer-to-PMC ratio is 5:3.
Community changes, past quarter:
- No new PMC members. Last addition was Ramya Vasanth on 2019-04-15.
- No new committers. Last addition was Archana Rai on 2017-05-26.
## Project Activity:
Recent releases:
- 4.7.0 was released on 2019-12-04.
- 4.6.0 was released on 2019-05-05.
- V2 2.0.11 was released on 2019-02-16.
People from the community plan did several security contributions in the form
of a code review. As result three CVEs were requested and related JIRA issues
were created and fixed.
## Community Health:
Overall community health is good.
The V4 code line is on steady development also reflected in related
discussions on mailing list and new created JIRA items. Release of V4 version
4.7.0 was done in December this year.
The V2 code line had minor bugfix contributions as well as open and new
created JIRA items.
Over the last months there were fewer new JIRA issues created then in the
past quarter (-27% created).
We closed as many JIRA issues as in the past quarter.
We used GitHub more and get 13 PRs closed which is an increase by 333% to past
quarter.
-----------------------------------------
Attachment AQ: 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
## Membership Data:
Apache OODT was founded 2010-11-17 (9 years ago) There are currently 46
committers and 45 PMC members in this project. The Committer-to-PMC ratio is
roughly 1:1.
Community changes, past quarter:
- No new PMC members. Last addition was Imesha Sudasingha on 2017-08-28.
- No new committers. Last addition was Imesha Sudasingha on 2017-08-29.
## Project Activity:
2 Google Summer of Code projects were completed in this quarter. With them a
new UI was introduced for OODT and main OODT components were dockerized to
support k8s deployment. These features are being further enhanced under 2.x
developments which are yet to be released.
After around one year silence, OODT 1.9 was released in this October which
included the major update of making Avro RPC the default. We are working on a
maintenance release, 1.9.x to address a backward compatibility issue
introduced with 1.9 release due to avro being default over XML RPC.
## Community Health:
Mailing list activity was high due to recent release and completion of GSoC
projects. Jira and PR activity were lower compared to last quarter since GSoC
projects finished at the beginning of this quarter.
We are tracking 2 prospects at the moment. Furthermore, we are planning to
submit projects for 2020 GSoC program.
-----------------------------------------
Attachment AR: Report from the Apache OpenNLP Project [Jörn Kottmann]
## Description:
The mission of OpenNLP is the creation and maintenance of software related to
Machine learning based toolkit for the processing of natural language text.
## Issues:
No issues to report.
## Membership Data:
Apache OpenNLP was founded 2012-02-15 (8 years ago)
There are currently 21 committers and 15 PMC members in this project.
The Committer-to-PMC ratio is 7:5.
Community changes, past quarter:
- No new PMC members. Last addition was Koji Sekiguchi on 2017-10-10.
- No new committers. Last addition was Jeffrey T. Zemerick on 2017-04-26.
## Project Activity:
The project will prepare a release to the end of the year to include
the few Pull Requests we received from our community.
## Community Health:
We see the usual activity on the dev and user list.
-----------------------------------------
Attachment AS: Report from the Apache OpenWebBeans Project [Mark Struberg]
## Description:
Apache OpenWebBeans software is an ALv2-licensed implementation of the JSR-299
"Contexts and Dependency Injection for the Java (TM) EE platform" specification.
We also provide full support for CDI-2.0 JSR-365.
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache OpenWebBeans was founded 2009-12-16 (10 years ago)
There are currently 20 committers and 13 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:4.
Community changes, past quarter:
- No new PMC members. Last addition was Reinhard Sandtner on 2017-10-09.
- No new committers. Last addition was John D. Ament on 2017-10-09.
## Project Activity:
Project activity is fine. We became aware of yet another micro container
framework which uses Apache OpenWebBeans as CDI container core.
We continue with bug fixing and adoption to latest Java versions.
There was also a quite nice interaction with the Apache Aries team
regarding their OWB support for the osgi-cdi spec.
## Community Health:
From time to time new users pop up on our lists but there are no
new committers in sight right now. Otoh our active committer base
is really fine and active.
-----------------------------------------
Attachment AT: Report from the Apache Petri Project [Dave Fisher]
## Description:
The mission of the Apache Petri project is the creation and maintenance of
software related to assessment of, education in, and adoption of the
Foundation's policies and procedures for collaborative development and the
pros and cons of joining the Foundation
## Issues:
No issues for the board at this time.
## Membership Data:
Apache Petri was founded 2019-11-19 (22 days ago)
There are currently 6 committers and 6 PMC members in this project.
The Committer-to-PMC ratio is 1:1.
Community changes, past quarter:
- No new PMC members (project established recently).
- No new committers were added.
## Project Activity:
We are working on the petri website using Pelican.
The FAQ is online.
We are prepared to start discussions about one or two possible projects
on discuss@petri.apache.org
## Community Health:
A slow but steady start.
discuss@petri.apache.org traffic so far (26 emails)
Currently 30 commits to petri-site repository.
-----------------------------------------
Attachment AU: Report from the Apache Pig Project [Koji Noguchi]
-----------------------------------------
Attachment AV: 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:
No board-level issues at this time.
Activity:
A little bit of development work continued toward the 2.1.0 release, and
so there were some dev emails because of that. But no traffic on user mailing
list.
Development continues toward the 2.1.0 release, including testing/changes with
the latest (9,10,11,etc.) Java releases.
Health Report:
Basically unchanged again this quarter, although there was some small amount
of development activity. Users remain quiet.
PMC changes:
- Currently 7 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Niclas Hedhman on Wed Jan 13 2016
Committer base changes:
- Currently 9 committers.
- No new changes to the committer base since last report.
- No new committers added in the last 3 months
- Last committer addition was more than 2 years ago
Releases:
- Last release was 2.0.5 on Mon Jul 03 2017
- Still some development on next major version (2.1.0).
Mailing list activity:
- dev@pivot.apache.org:
- 13 emails sent to list (13 in previous quarter)
- user@pivot.apache.org:
- No emails sent to list (none in previous quarter either)
JIRA activity:
- No JIRA activity in the last quarter.
-----------------------------------------
Attachment AW: Report from the Apache PLC4X Project [Christofer Dutz]
## Description:
The mission of the Apache PLC4X project is creating a set of libraries for
communicating with industrial programmable logic controllers (PLCs) using a
variety of protocols but with a shared API.
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache PLC4X was founded 2019-04-17 (8 months ago) There are currently 9
committers and 9 PMC members in this project. The Committer-to-PMC ratio is
1:1.
Community changes, past quarter:
- No new PMC members. Last addition was Łukasz Dywicki on 2019-07-28.
- No new committers. Last addition was Łukasz Dywicki on 2019-07-28.
However we just invited Lukas Ott to join the project as a comitter and he has
accepted the invitation. We are now waiting for his ICLA to be recorded on file.
## Project Activity:
Releases:
- 0.5.0 was released on 2019-11-25
Community Events:
- 2019-09-09 - 2019-09-12 ApacheCon NA 2019, Las Vegas, US (Multiple talks and
hackathon)
- 2019-09-24 IoT Hessen, Kassel, Germany (From the chip to the cloud with
Apache)
- 2019-10-22 - 2019-10-24 ApacheCon EU 2019, Berlin, Germany (Multiple talks
and hackathon)
- 2019-11-26 ElasticSearch UG Meetup, Frankfurt, Germany (Introduction
Logstash PLC4X Plugin)
- 2019-12-03 Apache IoT @ JUG Saar, Saarbrücken, Germany (From the chip to the
cloud with Apache)
- 2019-12-11 Apache NiFi + Hacking around the IoTree, Frankfurt, Germany
(Apache NiFi PLC4X Integration)
We have been continuing to port existing drivers to the new code-generation
framework. Also have we been implementing new protocols (Mostly based on paid
gigs from the industry). A lot of bug-fixing has been done and we're looking
forward to a big refactoring and brainstorming Hackathon form 2019-12-17 -
2019-12-19 in Weinheim, where we are going to work on a proposal for the
version 1.0.0 API.
## Community Health:
This quarter for most of the time activity on the mailing-list and in the
commits had dropped to worrying levels. This was mainly related to high
workload on the day-jobs of the community members. However in the past 2-3
weeks a lot of new people have joined discussions and submitted PRs and the
existing committer- and PMC activity has picked up again.
- dev@plc4x.apache.org had a 8% decrease in traffic in the past quarter (349
emails compared to 379)
- issues@plc4x.apache.org had a 73% increase in traffic in the past quarter
(132 emails compared to 76)
- 19 issues opened in JIRA, past quarter (46% increase)
- 13 issues closed in JIRA, past quarter (62% increase)
- 309 commits in the past quarter (-20% decrease)
- 23 PRs opened on GitHub, past quarter (91% increase)
- 20 PRs closed on GitHub, past quarter (66% increase)
- 29 contributors which have contributed code to the git repo (up by 3)
- 142 Github Stars (up by 18 since last report) (up by 43)
- 272 @ApachePLC4X Twitter account followers (up by 86)
We are very happy to see more people joining in from companies reporting to
use Apache PLC4X.
-----------------------------------------
Attachment AX: Report from the Apache Portable Runtime (APR) Project [Nick Kew]
## Description:
The mission of the Apache Portable Runtime (APR) project is to create and
maintain software libraries that provide a predictable and consistent interface
to underlying platform-specific implementations. The primary goal is to provide
an API to which software developers may code and be assured of predictable if
not identical behaviour regardless of the platform on which their software is
built, relieving them of the need to code special-case conditions to work
around or take advantage of platform-specific deficiencies or features.
## Issues:
No issues at this time.
## Membership Data:
Apache Portable Runtime (APR) was founded 2000-12-01 (19 years ago)
There are currently 67 committers and 42 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:2.
Community changes, past quarter:
- Ivan Zhakov was added to the PMC on 2019-11-05
- No new committers. Last addition was Evgeny Kotkov on 2017-09-13.
## Project Activity:
Nothing to report in the project. Activity has been subdued,
with a small amount of work focussed on Windows platform issues.
No milestones are in view. This may be seen as a reasonable
baseline state for a project that is stable and mature.
## Community Health:
The community remains quiet but responsive. In the short term, no change,
but perhaps worth noting that we may have improved since a few years ago,
as relatively-recent team members have somewhat rebalanced the project's
platform expertise towards Windows where we have at times been thin.
-----------------------------------------
Attachment AY: 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:
No new releases since April 25 (Pluto 3.1.0)
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:
Low activity. Primary activity on Pluto dev list, discussions around the the
Pluto releases.
## 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.1.0 - 25 April 2019
Pluto 3.0.1 - 21 June 2018
Pluto Maven Portlet Archetype 3.0.1 - 21 June 2018
Pluto Maven Generic Archetype 3.0.1 - 21 June 2018
Pluto Maven Archetype 3.0.0 - 27 April 2017
Pluto 3.0.0 - 18 January 2017
Jetspeed 2.3.1- 09 May 2016
-----------------------------------------
Attachment AZ: Report from the Apache PredictionIO Project [Donald Szeto]
## Description:
The mission of Apache Predictionio is the creation and maintenance of software
related to a 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:
No PMC chair nominee was nominated a week after the PMC chair expressed
intention to resign from the chair on the PMC mailing list.
## Membership Data:
Apache PredictionIO was founded 2017-10-17 (2 years ago)
There are currently 29 committers and 28 PMC members in this project.
The Committer-to-PMC ratio is roughly 8:7.
Community changes, past quarter:
- No new PMC members. Last addition was Andrew Kyle Purtell on 2017-10-17.
- No new committers were added.
## Project Activity:
Mostly in maintenance mode at this point. PMCs and committers fix bugs that
are reported by the community on the mailing list.
Recent releases:
0.14.0 was released on 2019-03-11.
0.13.0 was released on 2018-09-20.
0.12.1 was released on 2018-03-11.
## Community Health:
We are seeking new leadership for the project at the moment to bring it out
of maintenance mode. Moving to the attic would be the last option.
-----------------------------------------
Attachment BA: Report from the Apache Pulsar Project [Matteo Merli]
## Description:
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.
## Issues:
- There are no issues requiring board attention at this time.
## Project Activity:
- The project has released 2.4.2 in December and it is in the process
of releasing the next feature release 2.5.0.
Highlights include:
* [PIP-41] Introduce Protocol Handler API
* [PIP-45] Pluggable metadata interface
* [PIP-44] Separate schema compatibility checker for producer and consumer
* [PIP-43] Producer send messages with different schema
* [PIP-51] Introduce sticky consumer
* [PIP-38] Support batch receive in java client.
* [PIP-52] Add support of dispatch throttling relative to publish-rate
* Upgraded to ZooKeeper 3.5
* Upgraded to BookKeeper 4.10.0
* HDFS offloader for Pulsar tiered storage
- Several talk on Pulsar were presented at conferences and meetups,
in US, Europe
and China, both by Pulsar committer/PMC members as well as other members of
the community. Non-exaustive list:
* Pulsar meetup in Shanghai on Nov. 20th
* Query Pulsar Streams using Apache Flink at Flink Forward Berlin by Sijie Guo
* Apache Pulsar - Flexible Pub-Sub and Compute backed by durable
log storage
at IEEE Big Data - Real-time streaming workshop by Matteo Merli
* Go in Pulsar by Xiaolong Ran at Github meetup
* Stream processing with Apache Pulsar by Bruno Bonnin
* Scalable logs processing with Pulsar at Paris Data Eng by Alexandre Duval and
Quentin Adam
* Apache Pulsar 101: architecture, concepts & benchmark at Devoxx BE by Quentin
Adam and Steven Le Roux
- The first release of Pulsar Manager was released on Nov. 25th
- Work is ongoing for next release (2.6.0) and for to reach the first release
for the native Go client library.
## Community Health:
- There is healthy grow in the community, several users are starting to
become contributors to the project and engaging more and more with
the community.
- Activity on the Slack channel is still high, many first time users come
to ask questions while getting started. There are 160 weekly active users
on the channel, up from 148 in Sep.
## Membership Data:
- Currently 24 PMC members
- No new PMC members added since last report.
- Last PMC member added:
- Penghui Li - Sep 10th
- Currently 30 committers
- 2 committers were added since last report
- Guangning E - Oct 8th
- Liu Yu - Dec 3rd
## Releases:
- 2.4.2 was released on Dec. 4th 2019
## Mailing list activity:
- Activity on the mailing lists remains high with a mixture of new users,
contributors, and deeper more experienced users and contributors sparking
discussion and questions and filing bugs or new features.
- users@pulsar.apache.org:
- 130 subscribers (+9 from Sep 2019) - 205 emails sent to list in
last 3 months
- dev@pulsar.apache.org:
- 153 subscribers (+18 from Sep 2019) - 390 emails sent to list in
last 3 months
## Slack activity:
* 1311 Members (1041 in Sep 2019)
* 160 Active weekly users (148 in Sep 2019)
## GitHub activity:
- 339 PRs from 71 contributors were merged in the last 3 months
- 278 Issues were created and 165 closed in the last 3 months
- 4608 Stars (up from 4130 in Sep 2019)
-----------------------------------------
Attachment BB: Report from the Apache Royale Project [Piotr Zarzycki]
## Description:
Apache Royale is a new implementation of the principles of Apache Flex,
designed for JavaScript instead of Adobe Flash/AIR runtimes. Apache Royale
improves developer productivity in creating applications to run wherever
JavaScript runs, including on browsers as well as in Apache Cordova
applications, Node, etc.
## Issues:
There are no issues requiring board attention at this time.
## RELEASES:
- Apache Royale 0.9.2 was released on March 16 2018.
- Apache Royale 0.9.4 was released on November 14 2018.
- Apache Royale 0.9.6 was released on October 1 2019
## Membership Data:
Apache Royale was founded 2017-09-20 (2 years ago)
There are currently 16 committers and 14 PMC members in this project.
The Committer-to-PMC ratio is 8:7.
Community changes, past quarter:
- Andrew Wetmore was added to the PMC on 2019-09-16
- Greg Dove was added to the PMC on 2019-10-29
- No new committers. Last addition was Greg Dove on 2018-10-28.
## Project Activity:
- We have invested a lot of time in helping users who are trying to port their
application from Flex to Royale. There is also increased activity and
questions from new users about porting Flex applications to Royale.
- The team made good progress in emulation of Flex components and improvements
to MX and Spark Flex component sets.
- We have seen great progress in performance improvements for one of the
modules.
- Important components that the developer community needs, such as ButtonBar
and DataGrid, are under development for the Jewel UI Set.
- Royale members have contributed many improvements in the Compiler.
- We have greatly simplified the release process, and successfully tested the
changes with the 0.9.6 release, but we continue to try to streamline the
process of build and release so we can gain more traction withnew users.
- Royale Docs continues to be improved as the project is developed.
- We had a lot of activity on social networks, sharing what is happening in
Apache Royale as we progress in the project. We think it is important to do
this so people outside the project and not following it on a daily basis can
get a notion of how we are doing. The numbers are:
- Our Twitter account has 610 (590 at the time of the last Board report)
followers.
- Our Facebook page has 144 (previously 130) likes.
- Our LinkedIn Group has 129 (previously 126) people.
- Our StackOVerFlow "apache-royale" tag currently has 43 questions.
- We recently added a Slack channel, "royale", in the-asf.slack.com workspace
as an experiment.
## Community Health:
User-lists continue to grow:
- users@royale.apache.org:
- 78 subscribers (up 5 in the last 3 months)
- 1116 emails sent in the past 3 months (317 in the previous cycle)
- dev@royale.apache.org:
- 79 subscribers (up 5 in the last 3 months)
- 1451 emails sent in the past 3 months (1287 in the previous cycle)
-----------------------------------------
Attachment BC: Report from the Apache Sentry Project [Kalyan Kalvagadda]
## Description:
The mission of Sentry is the creation and maintenance of software related to
Fine grained authorization to data and metadata in Apache Hadoop
## Issues:
There are no issues requiring board attention
## Membership Data:
Apache Sentry was founded 2016-03-15 (4 years ago)
There are currently 40 committers and 38 PMC members in this project.
The Committer-to-PMC ratio is roughly 1:1.
Community changes, past quarter:
- No new PMC members. Last addition was Na Li on 2018-12-10.
- No new committers. Last addition was Arjun Mishra on 2018-07-06.
- We have new contributors to the community.
## Project Activity:
- we made couple of improvements and bug fixes in 2.2 release
- We are preparing to making release candidates for 2.2 this week.
- One of the bug fixed addresses CVE-2018-11777
## Community Health:
There has been some drop in sentry contribution but still healthy.
- 8 issues opened in JIRA, past quarter (no change)
- 1 issue closed in JIRA, past quarter (-66% decrease)
- 5 commits in the past quarter (150% increase)
- 2 code contributors in the past quarter (no change)
- 7 PRs opened on GitHub, past quarter (700% increase)
- 1 PR closed on GitHub, past quarter (100% increase)
-----------------------------------------
Attachment BD: 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.
## Membership Data:
Apache ServiceMix was founded 2007-09-19 (12 years ago)
There are currently 50 committers and 21 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:3.
Community changes, past quarter:
- No new PMC members. Last addition was Andrea Cosentino on 2017-03-15.
- No new committers. Last addition was Andrea Cosentino on 2016-03-13.
## Project Activity:
- During the last period we have released 3 sets of OSGi bundles:
- Apache ServiceMix Bundles 2019.09 on October 03 2019
- Apache ServiceMix Bundles 2019.10 on November 01 2019
- Apache ServiceMix Bundles 2019.11 on November 29 2019
- After the first release of Apache Camel 3.x we would like
to work on a new line of ServiceMix based on the newest version
of Apache Camel and Apache Karaf
## Community Health:
- During the last period the activity of the community (mailing lists, JIRA,
releases) has been slower than during the last period.
- As the most work is done in the dependency projects and the activity
in ServiceMix project is slower, we actually observe no potential
candidates to be invited as committer or PMC member
-----------------------------------------
Attachment BE: Report from the Apache Shiro Project [Les Hazlewood]
## Description:
Apache Shiro is a powerful and flexible open-source application security
framework that cleanly handles authentication, authorization, enterprise
session management and cryptography.
## Issues:
There are no issues requiring board attention at this time
## Membership Data:
Apache Shiro was founded 2010-09-21 (9 years ago)
There are currently 13 committers and 11 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:6.
Community changes, past quarter:
- Colm O hEigeartaigh was added to the PMC on 2019-10-08
- Jean-Baptiste Onofré was added to the PMC on 2019-10-07
- Colm O hEigeartaigh was added as committer on 2019-10-09
- Jean-Baptiste Onofré was added as committer on 2019-10-08
## Project Activity:
We are still working towards the next 1.5.0 release, which has taken a little
longer than expected. Last release was 1.4.1 on 2019-05-01.
## Community Health:
- dev@shiro.apache.org had a 2% increase in traffic in the past quarter
(291 emails compared to 284)
- user@shiro.apache.org had a 35% increase in traffic in the past quarter
(42 emails compared to 31)
- 10 issues opened in JIRA, past quarter (-44% decrease)
- 17 issues closed in JIRA, past quarter (no change)
- 28 commits in the past quarter (-3% decrease)
- 8 code contributors in the past quarter (no change)
- 23 PRs opened on GitHub, past quarter (no change)
- 30 PRs closed on GitHub, past quarter (20% increase)
-----------------------------------------
Attachment BF: Report from the Apache SINGA Project [Wang Wei]
## Description:
- Apache SINGA is a distributed, scalable machine learning library with a
focus on deep learning.
## Issues:
- No issues requires board attention
## Membership Data
- A new PMC member (Sheng Wang) was added on Nov 30, 2019.
- There are invitations under voting for a new PMC member and a
new committer.
- Currently, we have 13 PMC members and 17 committers.
## Last release
- The last release was v2.0.0 on 20 April 2019
## Activity
- 95 emails from dev@singa.apache.org since the last report (Nov 13, 2019)
- 70 commits on Github since the last report (Nov 13, 2019)
- The community is working towards the next release by refactoring some core
components, improving distributed training, building up the model zoo and
updating the website with a new framework.
## Community Health
- The community is growing smoothly with new committers and PMC members
joining.
- The development is active with continuous commits for various features. We
are preparing for the next release, which is scheduled to be in Jan 2020.
-----------------------------------------
Attachment BG: Report from the Apache Sling Project [Robert Munteanu]
## Description:
Apache Sling™ is a framework for RESTful web-applications based on an
extensible content tree.
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache Sling was founded 2009-06-17 (10 years ago)
There are currently 45 committers and 27 PMC members in this project.
The Committer-to-PMC ratio is 5:3.
Community changes, past quarter:
- No new PMC members. Last addition was Timothée Maret on 2019-06-21.
- Angela Schreiber was added as committer on 2019-10-30
## Project Activity:
We continue making individual module releases. There is interest in
making a release for the next version of our Starter module, but we
are not there yet.
## Community Health:
Good activity level overall, contributions from different people
continue.
We seem to talk slightly more (+10% emails on dev@sling) and commit
less ( -34% commits ) but I not would read too much into these stats right now.
-----------------------------------------
Attachment BH: Report from the Apache SpamAssassin Project [Sidney Markowitz]
Apache SpamAssassin report to Board for December 2019
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.
Status and health report:
The project activities, including running of our rule update infrastructure
and our dev and user mailing lists, are continuing smoothly.
SpamAssassin 3.4.3 was released on 11 December, 2019, somewhat over a year
since our previous release. We now intend to return our development focus to
our main branch for 4.0.
We are having disruption to our automated processing due to denial of service
attacks against the SVN resources. Thank you to infra for fighting this
attack.
Releases:
The last release was Apache SpamAssassin version 3.4.3 on 11 December 2019.
It contained two CVE fixes and resolves all known outstanding open security
issues on the project.
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.
Committer/PMC changes:
Most recent new committer:
Paul Stead (pds) 12 September 2018
Most recent new PMC members:
Giovanni Bechis (gbechis) 24 Sep 2018
Henrik Krohns (hege) 25 Sep 2018
-----------------------------------------
Attachment BI: Report from the Apache Stanbol Project [Rafa Haro]
-----------------------------------------
Attachment BJ: Report from the Apache Storm Project [P. Taylor Goetz]
## Description:
The mission of Storm is the creation and maintenance of software related to
Distributed, real-time computation system
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache Storm was founded 2014-09-16 (5 years ago)
There are currently 40 committers and 39 PMC members in this project.
The Committer-to-PMC ratio is roughly 1:1.
Community changes, past quarter:
- No new PMC members. Last addition was Aaron Gresch on 2019-08-08.
- No new committers. Last addition was Aaron Gresch on 2019-08-09.
## Project Activity:
- Version 2.1.0 was released on 2019-10-31. This represents a new release line
making the currently supported release lines 2.1.x, 2.0.x, and 1.2.x. Earlier
releases are considered EOL.
- I have announced my resignation as PMC Chair. We will hold nominations
and an election in the near future and submit a resolution to the board.
- We have begun rotating release managers.
## Community Health:
- This has been a quiet quarter with respect to email and issue activity. This
can be attributed to a quieting down from the previous quarter that included
a flurry of activity related to the lead-up and follow-up of the 2.0 release.
-----------------------------------------
Attachment BK: Report from the Apache Submarine Project [Wangda Tan]
# Apache Submarine - Dec 2019
## Description
The Apache™ Submarine® is a project which allows infra engineer/data scientist
to run machine learning unmodified Tensorflow or PyTorch programs on YARN or
Kubernetes.
## Issues
There are no problematic issues requiring board attention.
## General
### Feature development of Submarine:
The community is busy working on following features.
- Submarine Server and K8s Support.
- Submarine workbench for note book service.
- Submarine workflow for ML applications.
Overall the development from the community is good, we're talking to some
contributors to see if we can get some of them to run the Submarine project
management to help community move ahead.
## Membership Data:
Apache Submarine was founded on 2019-10 There are currently 27 committers and
7 PMC members in this project.
### PMC changes, past quarter:
- No new PMC member since last report.
### Committer base changes, past quarter:
- No new committers since last report.
## Project Activity:
### Releases
- Community is actively working on 0.3.0 release and target to ship by end
Dec, 2019.
## Community Health:
### JIRA Activity
Significantly up compared to last quarter
- 139 JIRA tickets created since the past quarter [ project in ("Apache
Submarine") AND createdDate >= 2019-09-10
]
- 111 JIRA tickets resolved since the past quarter [ project in ("Apache
Submarine") AND resolutiondate >= 2019-09-10
]
- 30 JIRA tickets created since the past month [ project in ("Apache
Submarine") AND createdDate >= 2019-11-10
]
- 31 JIRA tickets resolved since the past month [ project in ("Apache
Submarine") AND resolutiondate >= 2019-11-10
]
### Mailing list, slack channel, activity:
- dev@submarine: 490 emails since Nov 1st.
- slack: submarine-dev: there're 19 users in the channel since creation (Sep
12, 2019)
- Community sync up: Submarine community is very active now, weekly sync up
has 10+ participants in the last several months.
- There are not many activities in users, we expect to see more questions from
users post 0.3.0 release.
-----------------------------------------
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.
## Membership Data:
Apache Synapse was founded 2007-12-19 (12 years ago)
There are currently 34 committers and 26 PMC members in this project.
The Committer-to-PMC ratio is roughly 9:7.
Community changes, past quarter:
- No new PMC members. Last addition was Prabath Ariyarathna on 2017-05-04.
- No new committers. Last addition was Prabath Ariyarathna on 2017-02-10.
## Project Activity:
We were expecting to see an increase in the activity of the project after the
Github move. But it didn't happen to the expected level.
We are having discussions on the PMC list on how we can improve the activity.
One of the major discussion points is that whether we should position Synapse
as an integration framework rather than an ESB. The world has been moved
towards container friendly products, microservices, and cloud-native
technologies. With a little effort, we could make Synapse a container friendly
product that suits any architectural style for doing the integration.
## Community Health:
dev@synapse.apache.org had a 16% increase in traffic in the past quarter (36
emails compared to 31)
Activity in the Jira has also gone down in the last quarter.
-----------------------------------------
Attachment BM: Report from the Apache Tajo Project [Hyunsik Choi]
## Description:
The mission of Tajo is the creation and maintenance of software related to Big
data warehouse system on Apache Hadoop
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache Tajo was founded 2014-03-19 (6 years ago) There are currently 18
committers and 13 PMC members in this project. The Committer-to-PMC ratio is
roughly 9:7.
Community changes, past quarter:
- No new PMC members. Last addition was Hyoung Jun Kim on 2014-12-07.
- No new committers. Last addition was Jong-young Park on 2016-05-29.
## Project Activity:
* Opened a release vote 3 month ago, but canceled due to an artifact issue
* Very low activity
## Community Health:
* Very low activity, and overally no mailing threads, no jira issues in
community
-----------------------------------------
Attachment BN: Report from the Apache Tomcat Project [Mladen Turk]
## Description:
- A Java Servlet, JavaServer Pages, Java WebSocket and Java
Unified Expression language specifications implementation.
## Issues:
There are no issues requiring board attention at this time
## Membership Data:
- Apache Tomcat was founded 2005-05-18 (15 years ago)
- There are currently 46 committers and 28 PMC members in this project.
- The Committer-to-PMC ratio is roughly 3:2.
- Community changes, past quarter:
- No new PMC members. Last addition was Igal Sapir on 2019-03-18.
- No new committers. Last addition was Woonsan Ko on 2018-12-19.
## Project Activity:
- Apache Tomcat 9.0.29 was released on 2019-11-21
- Apache Tomcat 9.0.27 was released on 2019-10-11
- Apache Tomcat 9.0.26 was released on 2019-09-19
- Apache Tomcat 8.5.49 was released on 2019-11-21
- Apache Tomcat 8.5.47 was released on 2019-10-11
- Apache Tomcat 8.5.46 was released on 2019-09-19
## Community Health:
- Continued healthy activity across multiple components and
responsiveness on both dev and user lists.
## 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 BO: Report from the Apache Trafodion Project [Pierre Smits]
## Description:
The mission of Apache Trafodion is the creation and maintenance of software
related to webscale SQL-on-Hadoop solution enabling transactional or
operational workloads.
## Issues:
There are no issues requiring the boards attention at this moment.
## Membership Data:
Apache Trafodion was founded 2017-12-20 (2 years ago)
There are currently 24 committers and 15 PMC members in this project.
The Committer-to-PMC ratio is 8:5.
Community changes, past quarter:
- No new PMC members. Last addition was Anoop Sharma on 2018-12-06.
- No new committers. Last addition was Prashanth Vasudev on 2018-11-13.
## Project Activity:
The latest release of the project was r2.3.0, which was released to the public
on 2019-02-27. The project continues to work on improving the products, and
working towards a new release. In the coming period the PMC will continue to
work on on boarding new committers.
## Community Health:
Activities on the project's main mailing list (dev@) rose back - and
over - to levels before last reporting period. However, activities on
some other mailing lists decreased further.
While the increase on activities is a positive, the decreases on the
other mailing lists and the decreases regarding JIRA, Github Pull-Requests
and commits indicate that the interest in the project is in decline.
The PMC regards the project still as healthy, but will continue to monitor
the situation.
## Project statitics:
Mailing Lists:
- dev@trafodion.apache.org:
- 90 subscribers (Up 3)
- 108 emails sent to list (Up 52%)
- codereview@trafodion.apache.org:
- 18 subscribers (Down 1)
- 86 emails sent to list (Down 18%)
- issues@trafodion.apache.org:
- 28 subscribers (Down 0)
- 99 emails sent to list (Down 29%)
- user@trafodion.apache.org:
- 100 subscribers (Up 1)
- Currently no automated insights in number of ml postings provided by
ComDev-reporter services.
- security@trafodion.apache.org:
- 3 subscribers (down 0)
- Currently no automated insights in number of ml postings provided by
ComDev-reporter services.
- private@trafodion.apache.org:
- 16 subscribers (Down 0)
- Currently no automated insights in number of ml postings provided by
ComDev-reporter services.
JIRA activities:
- 7 tickets created (Down 50%)
- 2 tickets closed (Down 81%)
GitHub Actviities:
- PR opened: 9 (Down 25%)
- PR closed: 10 (Down 16%)
Commit activities:
- commits: 18 (Down 64%)
- active contributors: 3 (Down 40%)
-----------------------------------------
Attachment BP: Report from the Apache Twill Project [Terence Yim]
-----------------------------------------
Attachment BQ: Report from the Apache UIMA Project [Marshall Schor]
## Description:
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. The software provides frameworks, tools and annotators,
facilitating the analysis of unstructured content such as text, audio and
video.
## Membership Data:
Apache UIMA was founded 2010-03-16 (10 years ago)
There are currently 25 committers and 17 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:5.
Community changes, past quarter:
- Viorel Morari was added to the PMC on 2019-11-18
- No new committers. Last addition was Viorel Morari on 2018-09-20.
## Releases:
3 releases in last quarter
uimaj-3.1.1 was released on 2019-11-08.
UIMA Ruta 2.8.0 was released on 2019-11-28.
UIMA Ruta 3.0.0 was released on 2019-12-09.
## Activity:
The uimaj-3.1.1 was the first release of uimaj after
migrating that project from SVN to GIT.
The Ruta 3.0.0 is the first release of Ruta that
depends on the newer release stream of core uima version 3.
The uima-cpp subproject was (after many years of
dormancy) upgraded to current levels of C++ compiler tool
chains and associated dependencies; we hope a release will
be forthcoming after some more testing, soon.
## Community Health: The community continues to be moderately active.
## Issues: No Board level issues at this time.
-----------------------------------------
Attachment BR: Report from the Apache Unomi Project [Serge Huber]
## Description:
The mission of Apache Unomi is the creation and maintenance of software related
to providing a reference implementation of the OASIS Customer Data Platform
specification currently being worked on by the OASIS Context Server Technical
Committee
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache Unomi was founded 2019-02-20 (10 months ago)
There are currently 12 committers and 6 PMC members in this project.
The Committer-to-PMC ratio is 2:1.
Community changes, past quarter:
- No new PMC members. Last addition was David Griffon on 2019-02-20.
- No new committers. Last addition was Taybou on 2019-04-01.
## Project Activity:
The Apache Unomi community is highly focused on working on the next version
(1.5.0) that will include major improvements including:
- Support for ElasticSearch 7.5 (including an automatic migration tool from ES
5.6)
- Support for JDK 11
- Support for Apache Karaf 4.2
Some of these improvements required important changes to the underlying
persistence layer but fortunately migration will remain pretty
straight-forward as the REST API has not been touched at all.
On going efforts on onboarding and documentation are also paying off we are
seeing newcomers the users mailing list.
## Community Health:
The activity in the development mailing list mostly reflects all the current
work being done and mentioned in the activity. On the users mailing list
however we are seeing more newcomers which is great, and hopefully this is a
result of the efforts on the onboarding work being done.
We still want to continue to grow the community and make it easier to get
people to join the community. Also, we are seeing quite a lot of activity on
Slack which is not reflected in the standard Apache metrics. It might be
interesting to setup some kind of Slack digest in the mailing list.
Here are some community metrics:
- dev@unomi.apache.org had a 157% increase in traffic in the past quarter
- users@unomi.apache.org had a 100% increase in traffic in the past quarter
- 11 issues opened in JIRA, past quarter (no change)
- 8 issues closed in JIRA, past quarter (33% increase)
- 134 commits in the past quarter (509% increase)
- 10 code contributors in the past quarter (66% increase)
- 22 PRs opened on GitHub, past quarter (144% increase)
- 22 PRs closed on GitHub, past quarter (175% increase)
-----------------------------------------
Attachment BS: Report from the Apache VCL Project [Josh Thompson]
## Description:
The mission of the Apache VCL project is to create and maintain of software
related to a modular cloud computing platform which dynamically provisions and
brokers remote access to compute resources.
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache VCL was founded 2012-06-19 (7 years ago)
There are currently 10 committers and 7 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:4.
Community changes, past quarter:
- No new PMC members. Last addition was Aaron Coburn on 2012-06-19.
- No new committers. Last addition was Mike Jennings on 2019-01-04.
## Project Activity:
Most of the activity we've had since our 2.5.1 release at the end of July has
been related to supporting people upgrading to that release.
## Community Health:
We typically have a bit of a lull in development after getting a release out
as committers catch up on things they have been putting off while working on
the release. We are seeing that now and expect to see things pick back up a
bit in the next few months.
We have a good candidate in a recently added committer to become a new PMC
member.
-----------------------------------------
Attachment BT: Report from the Apache Wicket Project [Andrea Del Bene]
## Description:
Apache Wicket is an open source Java component oriented web application
framework.
## Issues:
- No issues require board attention.
## Membership Data:
Apache Wicket was founded 2007-06-20 (12 years ago)
There are currently 32 committers and 31 PMC members in this project.
The Committer-to-PMC ratio is roughly 1:1.
Community changes, past quarter:
- No new PMC members. Last addition was Ernesto Reinaldo Barreiro on 2019-08-14.
- No new committers. Last addition was Ernesto Reinaldo Barreiro on 2019-08-13.
## Project Activity:
In this last quarter we have been pretty busy working on a couple of issues:
- WICKET-6703 which was about removing JavaScript window.eval from our Ajax
code in order to comply with CSP standard
- WICKET-6666 which is about rewriting our ModalWindow component. The current
one is pretty old and the code has become messy and difficult to maintain.
So we decided to rewrite this component using modern web standards and
keeping code clean. This feature is not finished yet and will be available
only on the next major release 9.
More generally, in view of the next major release, we worked on some other
tasks aimed to clean our code base.
## Community Health:
The community is stable and healthy. Questions to the user list and dev list
are answered, resolved and discussed. We are seeing an increasing numbers of
contributions on our GitHub mirror with more PRs than the previous quarter.
In the last three months we also seen a positive trend with downloads number
on Apache Maven repository and on December we hit a new record for the last
year (about 360000 downloads).
-----------------------------------------
Attachment BU: Report from the Apache Xerces Project [Michael Glavassevich]
Xerces-J
A vote was just started on a release candidate for Xerces-J 2.12.1. This would
roll up minor bug fixes and enhancements that have been made in the past year.
One of the developers has been cleaning up issues in JIRA and properly tagging
ones that would be resolved by the new release. Most of the activity for the
release preparation has been in recent weeks.
Mailing list traffic has been low; roughly 70+ posts on the j-dev and j-users
lists since the beginning of September 2019.
No new releases since the previous report. The latest release is Xerces-J
2.12.0 (April 30th, 2018).
Xerces-C
One of the developers finally got around to converting the Xerces-C++ SVN
repository to Git after it was understood that this a self-serve process.
A report is currently being drafted to report a vulnerability that is known
but not yet resolved. This was discussed with security@ before heading down
this path. The existence of an issue has been made public on the c-dev mailing
list, but as of today the details have not been disclosed yet.
Most of the project activity in the last four months has been in response to
JIRA issues.
Mailing list traffic has been increasing; roughly 130+ posts on the c-dev and
c-users lists since the beginning of September 2019.
No new releases since the previous report. The latest release is Xerces-C
3.2.2 (September 19th, 2018).
Xerces-P
Nothing in particular to report. There was no development activity over the
reporting period.
XML Commons
No activity over the reporting period.
Committer / PMC Changes
The most recent committers were added in April 2017 (Xerces-C) and May 2017
(Xerces-J).
No new PMC members since the last report. The most recent addition to the PMC
was in June 2016.
Two committers have committed changes to SVN since September 2019.
-----------------------------------------
Attachment BV: Report from the Apache Yetus Project [Allen Wittenauer]
-----------------------------------------
Attachment BW: Report from the Apache ZooKeeper Project [Flavio Paiva Junqueira]
## Description:
Apache ZooKeeper is a system for distributed coordination. It enables
the implementation of a variety of primitives and mechanisms that are
critical for safety and liveness in distributed settings, e.g.,
distributed locks, master election, group membership, and configuration.
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache ZooKeeper was founded 2010-11-17 (9 years ago)
There are currently 27 committers and 14 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:4.
Community changes, past quarter:
- No new PMC members. Last addition was Andor Molnar on 2019-04-08.
- Brian Nixon was added as committer on 2019-09-24
## Project Activity:
* Recent releases:
• 3.5.6 was released on 2019-10-18.
• 3.5.5 was released on 2019-05-20.
• 3.4.14 was released on 2019-04-01.
* No new security vulnerabilities identified during the period
## Community Health:
It has been a slow period with respect to contributions. Overall, contributions
and discussions on the dev list have dropped, but the traffic on the user list
has gone up with various questions ranging from semantics to upgrades.
- dev@zookeeper.apache.org had a 2% decrease in traffic in the past quarter
(1076 emails compared to 1096)
- issues@zookeeper.apache.org had a 29% increase in traffic in the past quarter
(1097 emails compared to 844)
- user@zookeeper.apache.org had a 59% increase in traffic in the past quarter
(279 emails compared to 175)
- 99 issues opened in JIRA, past quarter (-14% decrease) 45 issues closed in
JIRA, past quarter (-49% decrease)
- 70 commits in the past quarter (-36% decrease) 25 code contributors in the
past quarter (-21% decrease)
- 82 PRs opened on GitHub, past quarter (-19% decrease) 74 PRs closed on GitHub,
past quarter (-30% decrease)
------------------------------------------------------
End of minutes for the December 18, 2019 board meeting.
Index