Index
Links: 2019 - All years
- Original The Apache Software Foundation
Board of Directors Meeting Minutes
November 20, 2019
1. Call to order
The meeting was scheduled for 10:30am Pacific and began at 10:30
when a sufficient attendance to constitute a quorum was
recognized by the chairman.
Other Time Zones: https://timeanddate.com/s/3zwe
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:
Danny Angus
Rich Bowen
Shane Curcuru
Ted Dunning
Dave Fisher
Myrle Krantz
Daniel Ruggeri
Craig L Russell
Roman Shaposhnik
Directors Absent:
none
Executive Officers Present:
Tom Pappas
Sam Ruby
Matt Sicker
Executive Officers Absent:
David Nalley
Guests:
Daniel Gruno
Greg Stein
Henri Yandell
Kevin A. McGrail
Sally Khudairi
Sander Striker
Wangda Tan
3. Minutes from previous meetings
Published minutes can be found at:
http://www.apache.org/foundation/board/calendar.html
A. The meeting of October 16, 2019
See: board_minutes_2019_10_16.txt
Approved by General Consent.
4. Executive Officer Reports
A. Chairman [Craig]
Kudos to the conference organizers for another excellent ApacheCon EU
in Berlin.
I had the honor of giving a keynote speech at the first Tencent Tech
Echo (Techo) conference in Beijing. I also gave a presentation at
Tsinghua University to an audience consisting mostly of undergraduate
students. Special thanks to Sally Khudairi for her invaluable help in
preparing these presentations.
While in Beijing, I met with several people about how to make Apache
projects more accessible to Chinese community members, including
users, contributors, and committers. One result of these meetings is
continuation of dialog to implement a bot to facilitate communications
among e.g. mail lists, WeChat groups, Slack, Dingding, and issue
tracking systems like GitHub and JIRA. The group is currently deciding
on next steps.
B. President [Sam]
Regarding finances, "we are on pace to meet our budget". This is a
quite notable change from previous months. Not a cause for concern,
but definitely something to watch.
Highlights from various areas:
* Brand management is essentially treating direct to TLP projects the
same as podlings for the purposes of name searches at this point.
* Fundraising has modified its link policy to include rel="sponsored"
on all links going forward.
* Marketing and Publicity helped drive the Petri faq.
* M&P published the Q1 report for FY2020 https://s.apache.org/a6s40
* ApacheCon NA 2020 is tentatively the last week in September in New
Orleans. Four (and possibly more) roadshows are in various stages
of planning.
* Conferences has also assumed responsibility for small event
planning.
* A new photos.apachecon.com site is live.
* New Expected time for a full report on Equity, Diversity, and
Inclusion analysis is May. Comms plan for D&I committee is on hold
due to bandwidth to work on it and the survey. Focusing on the
survey first.
Additionally, please see Attachments 1 through 8.
C. Treasurer [Myrle]
Operating Cash on October 31st, 2019 was $1,701K, which is down
$659.9K from last month’s ending balance (Sept 19) of $2,360.9K.
Total Cash as of October 31st, 2019 is $3,124.9K (includes the
Pineapple, Restricted Donation as well as the Tides Restricted
Donations) as compared to $3,564.4K on Sept. 30th, 2018, (a decrease
of $439.5K year over year). The October 2019 ending Operating cash
balance of $1,701K represents an Operating cash reserve of 7.3 months
based on the FY20 Cash forecast average monthly spending of
$233.7K/month. The ASF actual Operating reserve of 7.3 months at the
end of October 2019 is bit behind the budgeted 7.7 month’s reserve for
YTD through October 2019. The estimated YE Operating reserve of 8.1
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 $322.2K. ACNA19 Sponsorship exceeded the
budget, however ACNA 19 Registration is below 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
$945K). As compared to FY19, YTD revenue is behind by $107.8K
primarily due to timing of some Sponsor payments.
YTD expenses through October 31st, 2019 are under budget by $79.1K.
Most departments are under budget, however due to the finalization of
the amount owed to Leaseweb Infra is slightly over budget, again a
timing issue as compared to the budget . Conferences expenses at this
point are over budget, as the ANCA19 Hotel bill was paid in October.
As noted in last month’s narrative the budgeted loss for ACNA19 is
$55K and we were estimating it to be in the $110K-$120K loss range.
At this point the Loss for ACNA19 stands at $110.5K. For ACEU19 as
noted in last month’s narrative, estimated loss could be 107K Euros,
however as ACEU19 took place in October 2019, it will be a month or
two before we have a preliminary P&L.
Regarding Net Income (NI), YTD FY20 the ASF finished with a negative
<$712.9K> NI vs a budgeted negative <$469.7K> NI or $243.2K 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 Leaseweb payment as well as timing of Sponsor payments vs the
FY20 Budget. The cash forecast has been updated and at this point
halfway through the Fiscal year, we are on pace to meet our budget. I
would ask that all dept heads review the Cash forecast and let us know
if there is anything that could change in the estimates for the
remaining six months of FY2020. With regard to FY19, we are behind
in revenue, by $107.8K as noted above, but we are also ahead on
expenses by $691.2K (due to ACNA19 and the Leaseweb payment which
should have taken place in FY19, but did not); thus, year over year NI
for FY20 is behind FY19 by $799K. It is estimated that this will even
out as the second six months of FY 20 progresses.
Current Balances:
Boston Private CDARS Account 2,265,241.60
Citizens Money Market 701,618.65
Citizens Checking 156,027.87
Paypal - ASF 2,011.82
Total Checking/Savings 3,124,899.94
Oct-19 Budget Variance
Income Summary:
Public Donations 1,682.91 2,276.96 -594.05
Sponsorship Program 31,000.00 170,000.00 -139,000.00
Programs Income 0.00 0.00 0.00
Conference/Event Income 47,400.95 189,000.00 -141,599.05
Other Income 0.00 0.00 0.00
Interest Income 4,084.23 450.00 3,634.23
Total Income 84,168.09 361,726.96 -277,558.87
Expense Summary
Infrastructure 162,378.47 85,733.08 76,645.39
Programs Expense 1,158.53 3,333.33 -2,174.80
Publicity 64,877.89 44,233.34 20,644.55
Brand Management 3,187.97 8,166.67 -4,978.70
Conferences 457,860.82 48,250.00 409,610.82
Travel Assistance Committee 16,837.65 10,000.00 6,837.65
Fundraising 14,330.37 16,080.00 -1,749.63
Treasury Services 3,350.00 3,350.00 0.00
General & Administrative 13,654.35 1,915.00 11,739.35
Diversity and Inclusion 0.00 5,833.33 -5,833.33
Total Expense 737,636.05 226,894.75 510,741.30
Net Income -653,467.96 134,832.21 -788,300.17
YTD FY20 Budget Variance
Income Summary:
Public Donations 21,895.59 104,079.73 -82,184.14
Sponsorship Program 345,000.00 582,000.00 -237,000.00
Programs Income 14,900.00 14,000.00 900.00
Conference/Event Income 512,725.81 520,000.00 -7,274.19
Other Income 0.00 0.00 0.00
Interest Income 5,988.19 2,650.00 3,338.19
Total Income 900,509.59 1,222,729.73 -322,220.14
Expense Summary
Infrastructure 558,291.02 546,398.48 11,892.54
Programs Expense 1,158.53 19,999.98 -18,841.45
Publicity 232,355.86 235,975.04 -3,619.18
Brand Management 30,447.15 49,000.02 -18,552.87
Conferences 633,668.86 571,500.00 62,168.86
Travel Assistance Committee 30,805.21 95,000.00 -64,194.79
Fundraising 77,491.40 96,480.00 -18,988.60
Treasury Services 20,100.00 20,100.00 0.00
General & Administrative 29,066.57 22,990.00 6,076.57
Diversity and Inclusion 0.00 34,999.98 -34,999.98
Total Expense 1,613,384.60 1,692,443.50 -79,058.90
Net Income -712,875.01 -469,713.77 -243,161.24
D. Secretary [Matt]
In October, we received 64 ICLAs, 5 CCLAs, and 6 software grants.
E. Executive Vice President [David]
I attended ACEU and gave the SoTF.
ACEU was well produced and attended.
Travel Assistance
=================
TAC had a few last minute challenges around payment, but executed
well. Kudos to Christopher Dutz for leading the TAC efforts in Europe.
The TAC folks took advantage of being co-located at ACEU and spent
some time planning for the rest of the Fiscal Year. See the Travel
Assistance report for more details.
Infrastructure
==============
Infrastructure is largely operating normally. Of note, infrastructure
has re-enabled per-project web statistics and is evaluating a new l10n
platform.
F. Vice Chairman [Shane]
Nothing to report this month.
Executive officer reports approved as submitted by General Consent.
5. Additional Officer Reports
A. VP of W3C Relations [Andy Seaborne / Roman]
See Attachment 9
B. Apache Legal Affairs Committee [Roman Shaposhnik]
See Attachment 10
C. Apache Security Team Project [Mark J. Cox / Daniel]
See Attachment 11
@Danny: speak with Mark about how to handle Ambari and Xerces
D. VP of Data Privacy [John Kinsella / Myrle]
No report was submitted.
@Danny: pursue a change of chair for Data Privacy
E. VP of Jakarta EE Relations [Mark Struberg / Danny]
No report was submitted.
@Roman: find out about bandwidth
Additional officer reports approved as submitted by General Consent.
6. Committee Reports
Summary of Reports
The following reports required further discussion:
# Cassandra [myrle]
# Security Team [da]
# SystemML [myrle]
# Tajo [df]
# jUDDI [df]
A. Apache Ambari Project [Jayush Luniya / Dave]
See Attachment A
B. Apache Ant Project [Jan Materne / Shane]
See Attachment B
C. Apache BookKeeper Project [Sijie Guo / Ted]
See Attachment C
D. Apache Brooklyn Project [Geoff Macartney / Rich]
See Attachment D
E. Apache Buildr Project [Antoine Toulme / Craig]
See Attachment E
F. Apache Cassandra Project [Nate McCall / Myrle]
See Attachment F
G. Apache Clerezza Project [Hasan Hasan / Shane]
See Attachment G
H. Apache Cocoon Project [Cédric Damioli / Danny]
See Attachment H
I. Apache Community Development Project [Sharan Foga / Ted]
See Attachment I
J. Apache CouchDB Project [Jan Lehnardt / Roman]
See Attachment J
K. Apache Creadur Project [Brian E Fox / Daniel]
See Attachment K
L. Apache DeltaSpike Project [Mark Struberg / Craig]
See Attachment L
M. Apache DRAT Project [Tom Barber / Dave]
See Attachment M
N. Apache Drill Project [Charles Givre / Rich]
See Attachment N
O. Apache Empire-db Project [Rainer Döbele / Myrle]
See Attachment O
P. Apache Flume Project [Ferenc Szabo / Craig]
See Attachment P
Q. Apache Forrest Project [David Crossley / Roman]
See Attachment Q
R. Apache FreeMarker Project [Dániel Dékány / Dave]
See Attachment R
S. Apache Geode Project [Karen Miller / Daniel]
See Attachment S
T. Apache Giraph Project [Dionysios Logothetis / Danny]
See Attachment T
U. Apache Gora Project [Kevin Ratnasekera / Ted]
See Attachment U
V. Apache Groovy Project [Paul King / Rich]
See Attachment V
W. Apache Hama Project [Chia-Hung Lin / Shane]
No report was submitted.
X. Apache HTTP Server Project [Daniel Gruno / Ted]
See Attachment X
Y. Apache HttpComponents Project [Asankha Chamath Perera / Roman]
See Attachment Y
Z. Apache Ignite Project [Denis A. Magda / Craig]
See Attachment Z
AA. Apache Impala Project [Jim Apple / Shane]
See Attachment AA
AB. Apache Incubator Project [Justin Mclean / Dave]
See Attachment AB
AC. Apache Joshua Project [Tommaso Teofili / Danny]
See Attachment AC
AD. Apache jUDDI Project [Alex O'Ree / Rich]
See Attachment AD
@Rich: pursue a better report
AE. Apache Juneau Project [James Bognar / Myrle]
See Attachment AE
AF. Apache Kafka Project [Jun Rao / Daniel]
See Attachment AF
AG. Apache Kibble Project [Rich Bowen]
See Attachment AG
AH. Apache Knox Project [Larry McCay / Rich]
See Attachment AH
AI. Apache Kylin Project [Shao Feng Shi / Shane]
See Attachment AI
AJ. Apache Lens Project [Amareshwari Sriramadasu / Roman]
See Attachment AJ
AK. Apache Libcloud Project [Tomaž Muraus / Danny]
No report was submitted.
@Danny: pursue a report for Libcloud
AL. Apache Logging Services Project [Matt Sicker / Craig]
See Attachment AL
AM. Apache ManifoldCF Project [Karl Wright / Ted]
See Attachment AM
AN. Apache Marmotta Project [Jakob Frank / Daniel]
See Attachment AN
AO. Apache MetaModel Project [Kasper Sørensen / Myrle]
See Attachment AO
AP. Apache Oozie Project [Gézapeti / Dave]
See Attachment AP
AQ. Apache Open Climate Workbench Project [Huikyo Lee / Dave]
See Attachment AQ
AR. Apache OpenJPA Project [Mark Struberg / Danny]
See Attachment AR
AS. Apache OpenWhisk Project [Dave Grove / Shane]
See Attachment AS
AT. Apache Perl Project [Philippe Chiasson / Rich]
No report was submitted.
AU. Apache Phoenix Project [Josh Elser / Myrle]
See Attachment AU
AV. Apache POI Project [Dominik Stadler / Ted]
See Attachment AV
AW. Apache Qpid Project [Robbie Gemmell / Craig]
See Attachment AW
AX. Apache REEF Project [Sergiy Matusevych / Roman]
See Attachment AX
AY. Apache River Project [Peter Firmstone / Daniel]
See Attachment AY
AZ. Apache RocketMQ Project [Xiaorui Wang / Rich]
See Attachment AZ
BA. Apache Roller Project [David M. Johnson / Ted]
See Attachment BA
BB. Apache Samza Project [Yi Pan / Daniel]
See Attachment BB
BC. Apache Santuario Project [Colm O hEigeartaigh / Craig]
See Attachment BC
BD. Apache Serf Project [Branko Čibej / Roman]
See Attachment BD
BE. Apache ServiceComb Project [Willem Ning Jiang / Dave]
See Attachment BE
BF. Apache SINGA Project [Wang Wei / Danny]
See Attachment BF
BG. Apache SIS Project [Martin Desruisseaux / Myrle]
See Attachment BG
BH. Apache Spark Project [Matei Alexandru Zaharia / Shane]
See Attachment BH
BI. Apache Stanbol Project [Rafa Haro / Shane]
No report was submitted.
@Shane: pursue a roll call for Stanbol
BJ. Apache Submarine Project [Wangda Tan / Roman]
See Attachment BJ
BK. Apache Subversion Project [Stefan Sperling / Rich]
See Attachment BK
BL. Apache Syncope Project [Francesco Chicchiriccò / Daniel]
See Attachment BL
BM. Apache SystemML Project [Jon Deron Eriksson / Myrle]
See Attachment BM
@Myrle: pursue a roll call for SystemML
BN. Apache Tajo Project [Hyunsik Choi / Dave]
No report was submitted.
BO. Apache Tapestry Project [Thiago Henrique De Paula Figueiredo / Craig]
See Attachment BO
BP. Apache Tez Project [Jonathan Turner Eagles / Danny]
See Attachment BP
BQ. Apache TomEE Project [David Blevins / Ted]
See Attachment BQ
BR. Apache Traffic Control Project [David Neuman / Danny]
See Attachment BR
BS. Apache Turbine Project [Georg Kallidis / Daniel]
See Attachment BS
BT. Apache Usergrid Project [Michael Russo / Roman]
See Attachment BT
BU. Apache Velocity Project [Nathan Bubna / Ted]
See Attachment BU
BV. Apache Whimsy Project [Sam Ruby / Myrle]
See Attachment BV
BW. Apache Xalan Project [Gary D. Gregory / Dave]
See Attachment BW
BX. Apache Xerces Project [Michael Glavassevich / Rich]
No report was submitted.
@Rich: pursue a report for Xerces
BY. Apache XML Graphics Project [Clay Leeds / Craig]
See Attachment BY
BZ. Apache Zeppelin Project [Lee Moon Soo / Shane]
See Attachment BZ
Committee reports approved as submitted by General Consent.
7. Special Orders
A. Change the Apache jclouds Project Chair
WHEREAS, the Board of Directors heretofore appointed Andrea Turli
(andreaturli) to the office of Vice President, Apache jclouds, and
WHEREAS, the Board of Directors is in receipt of the resignation of
Andrea Turli from the office of Vice President, Apache jclouds, and
WHEREAS, the Project Management Committee of the Apache jclouds
project has chosen by consensus to recommend Ignasi Barrera (nacx) as
the successor to the post;
NOW, THEREFORE, BE IT RESOLVED, that Andrea Turli is relieved and
discharged from the duties and responsibilities of the office of Vice
President, Apache jclouds, and
BE IT FURTHER RESOLVED, that Ignasi Barrera be and hereby is appointed
to the office of Vice President, Apache jclouds, 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 jclouds Project Chair, was
approved by Unanimous Vote of the directors present.
B. Change the Apache Ignite Project Chair
WHEREAS, the Board of Directors heretofore appointed Denis A. Magda
(dmagda) to the office of Vice President, Apache Ignite, and
WHEREAS, the Board of Directors is in receipt of the resignation of
Denis A. Magda from the office of Vice President, Apache Ignite, and
WHEREAS, the Project Management Committee of the Apache Ignite project
came to a consensus to recommend Dmitry Pavlov (dpavlov) as the
successor to the post;
NOW, THEREFORE, BE IT RESOLVED, that Denis A. Magda is relieved and
discharged from the duties and responsibilities of the office of Vice
President, Apache Ignite, and
BE IT FURTHER RESOLVED, that Dmitry Pavlov be and hereby is appointed
to the office of Vice President, Apache Ignite, to serve in accordance
with and subject to the direction of the Board of Directors and the
Bylaws of the Foundation until death, resignation, retirement, removal
or disqualification, or until a successor is appointed.
Special Order 7B, Change the Apache Ignite Project Chair, was
approved by Unanimous Vote of the directors present.
C. Change the Apache Creadur Project Chair
WHEREAS, the Board of Directors heretofore appointed Brian E Fox
(brianf) to the office of Vice President, Apache Creadur, and
WHEREAS, the Board of Directors is in receipt of the resignation of
Brian E Fox from the office of Vice President, Apache Creadur, and
WHEREAS, the Project Management Committee of the Apache Creadur project
has chosen by vote to recommend Philipp Ottlinger (pottlinger) as the
successor to the post;
NOW, THEREFORE, BE IT RESOLVED, that Brian E Fox is relieved and
discharged from the duties and responsibilities of the office of Vice
President, Apache Creadur, and
BE IT FURTHER RESOLVED, that Philipp Ottlinger be and hereby is
appointed to the office of Vice President, Apache Creadur, to serve in
accordance with and subject to the direction of the Board of Directors
and the Bylaws of the Foundation until death, resignation, retirement,
removal or disqualification, or until a successor is appointed.
Special Order 7C, Change the Apache Creadur Project Chair, was
approved by Unanimous Vote of the directors present.
D. Change the Apache OpenOffice Project Chair
WHEREAS, the Board of Directors heretofore appointed Peter Kovacs
(petko) to the office of Vice President, Apache OpenOffice, and
WHEREAS, the Board of Directors is in receipt of the resignation of
Peter Kovacs from the office of Vice President, Apache OpenOffice, and
WHEREAS, the Project Management Committee of the Apache OpenOffice
project has chosen by vote to recommend Jim Jagielski (jim) as the
successor to the post;
NOW, THEREFORE, BE IT RESOLVED, that Peter Kovacs is relieved and
discharged from the duties and responsibilities of the office of Vice
President, Apache OpenOffice, and
BE IT FURTHER RESOLVED, that Jim Jagielski be and hereby is appointed
to the office of Vice President, Apache OpenOffice, to serve in
accordance with and subject to the direction of the Board of Directors
and the Bylaws of the Foundation until death, resignation, retirement,
removal or disqualification, or until a successor is appointed.
Special Order 7D, Change the Apache OpenOffice Project Chair,
was approved by Unanimous Vote of the directors present.
E. Establish the Apache Petri 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 shepherding
communities, producing open-source software for distribution at no
charge to the public, 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;
NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
(PMC), to be known as the "Apache Petri Project", be and hereby is
established pursuant to Bylaws of the Foundation; and be it further
RESOLVED, that the Apache Petri Project be and hereby is assigned and
charged with the responsibility of creating and maintaining processes
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; and be it further
RESOLVED, that the office of "Vice President, Apache Petri" 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 Petri
Project, and to have primary responsibility for management of the
projects within the scope of responsibility of the Apache Petri
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 Petri Project:
Daniel Gruno <humbedooh@apache.org>
Daniel Shahaf <danielsh@apache.org>
Dave Fisher <wave@apache.org>
David Nalley <ke4qqq@apache.org>
Greg Stein <gstein@apache.org>
Ross Gardler <rgardler@apache.org>
NOW, THEREFORE, BE IT FURTHER RESOLVED, that Dave Fisher be appointed
to the office of Vice President, Apache Petri, to serve in accordance
with and subject to the direction of the Board of Directors and the
Bylaws of the Foundation until death, resignation, retirement, removal
or disqualification, or until a successor is appointed.
Special Order 7E, Establish the Apache Petri Project, was
approved by Unanimous Vote of the directors present.
8. Discussion Items
A. Convenience Binaries
Official Apache releases are source code. But we have allowed
"convenience binaries" to be created and even hosted on Apache
infrastructure. Further, we have allowed projects to vote on, approve,
and publish these artifacts as if they were official releases. And
some of these artifacts are signed by Apache infrastructure tools. And
some of these artifacts contain Category X components.
I'd like to revisit the topic of convenience binaries and establish
some ground rules for PMCs to follow.
@Myrle: work with Roman to lead discussion on this
9. Review Outstanding Action Items
* Rich: open up attic discussions to dev list
[ Forrest 2019-05-15 ]
Status: Vote happening on dev list right now:
https://lists.apache.org/thread.html/c49f6223e82bf32b559dc4bf0a061a75369856e11cf05cf654e51036@%3Cdev.forrest.apache.org%3E
* Rich: find out what the sentence in Issues means
[ Open Climate Workbench 2019-05-15 ]
Status: https://lists.apache.org/thread.html/ec419e4484046d767acc9673d7b2f06f27d0f36a2a6310d7f31ca578@%3Cprivate.climate.apache.org%3E
To summarize, it sounds like some major chunk of code is being
developed inside NASA, and then they're going to come back to
the community with it. While this doesn't sound ideal to me,
it at least explains what the statement in that report meant,
all those months ago.
* Tom: research what other nonprofits do for CoCs for boards
[ Statement of Expectation of Conduct of Board Members 2019-05-15 ]
Status:
* Ted: clarify red tape and release process
[ RocketMQ 2019-08-21 ]
Status:
* Danny: follow up to get a report for the normal reporting cycle
[ Zeppelin 2019-08-21 ]
Status: Done. Email sent offering to help get a report done.
2019-11-14. More informative report submitted for 11/2019
* Roman: Update docs around legal FAQ
[ President 2019-09-18 ]
Status:
* Daniel: get project moved to Attic
[ Falcon 2019-09-18 ]
Status:
* Ted: pursue Atticking
[ Hama 2019-09-18 ]
Status: Only one reply on private@ agreeing with Ted; Attic
announcement needs to move to dev@ to let the community know
the project is being Attic'd.
* Myrle: follow up about build server breach
[ Royale 2019-09-18 ]
Status: sent e-mail
* Ted: pursue a report for Tajo
[ Tajo 2019-09-18 ]
Status:
* Sam: pursue a resolution for signing the agreement
[ Jakarta EE Relations 2019-10-16 ]
Status: I plan to take no further action unless asked again to do so
by the board.
* David: close the loop with Arrow and other communities with needs for CI
[ Arrow 2019-10-16 ]
Status:
* Danny: pursue PMC roll call and potential Attic resolution
[ Chukwa 2019-10-16 ]
Status: In progress. Chukwa PMC have discussed this and are ready to
Vote to move to the attic. more than 3 PMC members indicated
+1 on the discussion thread. I anticipate an attic resolution
in December.
* Ted: discuss commit squashing from outside branches and loss of code
[ DataFu 2019-10-16 ]
Status: The situation was pretty much best-case of the scenarios we
imagined. No issue at all. The squash didn't lose any author
information.
* Ted: follow up on tweet
[ HBase 2019-10-16 ]
Status: The HBase community is handling these issues well. No further
action required.
* Craig: pursue report for next month; possible Attic candidate
[ Joshua 2019-10-16 ]
Status:
* Roman: pursue a report for next month
[ OpenJPA 2019-10-16 ]
Status: Done: report provided.
* Dave: find out more details on Catalina requirements and how we can address
[ OpenOffice 2019-10-16 ]
Status: A past contributor, PMC member, and MacOS builder has returned
to the project! The project is now experimenting with macOS
Notarization and Windows certificate signing.
* Dave: pursue a roll call for Samza
[ Samza 2019-10-16 ]
Status: Roll call completed with 6 affirmative responses and 1
resignation. Expected to report in November
* Danny: pursue a report for Stanbol
[ Stanbol 2019-10-16 ]
Status: Done. Email sent offering to help get a report done.
2019-11-14
* Danny: work with Sally on info about the Attic process
[ Tajo 2019-10-16 ]
Status: Working on a blog post
* Daniel: pursue a report for Tapestry
[ Tapestry 2019-10-16 ]
Status: Done; report submitted.
* Craig: pursue a report for Tez
[ Tez 2019-10-16 ]
Status: Done; report submitted.
* Danny: find out what help the PMC needs to improve reporting
[ Zeppelin 2019-10-16 ]
Status: Done. Email sent offering to help get a report done.
2019-11-14
* Sally: work with @Dave on an FAQ for Petri
[ Establish Petri 2019-10-16 ]
Status:
10. Unfinished Business
11. New Business
12. Announcements
13. Adjournment
Adjourned at 11:55 a.m. (Pacific)
============
ATTACHMENTS:
============
-----------------------------------------
Attachment 1: Report from the VP of Brand Management [Mark Thomas]
* ISSUES FOR THE BOARD
None.
* OPERATIONS
Covering the period October 2019
Responded to the following queries, liaising with projects as required:
- Resolved 3 Podling name searches (PETRI, DORIS, SUBMARINE)
- Redirected an enquiry about an ALv2 licensed font to the font owner
- Request to reference Apache projects in a book
- Use of R, TM and SM with PETRI
- Naming of a training course for KAFKA
- Use of KAFKA logo
- Clarified that we don;t register marks for incubating projects
- Produced the Q1 report for press and marketing
- Declined to sign a license to use material in a book as the rights requested
were either not ours to license or covered by the ALv2
Fixed a handful of syntax bugs on the brand web pages. Thanks to danielsh.
Discussed whether a more formal process for direct to TLP name searches was
required. No change is proposed.
* REGISTRATIONS
Redirected a SUBVERSION related renewal request to the correct trademark
owner.
Reviewed the domain transfer agreement for dubbo.io
* INFRINGEMENTS
-----------------------------------------
Attachment 2: Report from the VP of Fundraising [Daniel Ruggeri]
Fundraising continues operating smoothly. We are in the process of renewing
additional sponsors --3 Platinum, 3 Gold, 1 Silver, and 1 Bronze-level
Sponsors. Payment has been received by 1x Platinum, 1x Gold, and 1x Silver.
We look forward to announcing a new Sponsor at the Silver level after
identifying some issues with email (China firewall?) that caused a few weeks'
delay.
We continue working on two new Targeted Sponsorships: one to benefit the
Apache Cordova project, and the other for ASF Infrastructure. The
Infrastructure-supporting sponsor is being onboarded and is working with ASF
Marketing & Publicity on messaging and related communications.
We are beginning to support sponsorship planning for ASF Conferences in 2020,
including Roadshows in North America and Europe, as well as ApacheCon North
America. We are continuing to help Virtual/Accounting on remaining sponsor
payments for 2019 ApacheCons in North America and Europe
Campaign preparations for Individual Giving season, which includes Corporate
Giving, has begun. These will launch in the next few weeks.
We received about $1,185 from individual donors via Hopsie.
We have modified our link policy for the "thanks page". Going forward, all
new Sponsor links will be added with the rel="sponsored" tag. See
http://www.apache.org/foundation/sponsorship.html#Links. Existing links will
be converted upon renewal or opt-in by the Sponsor. Site, policy, form, and
agreement documentation has been updated.
We were delighted to say hello to and thank several of our sponsors in person
at COSCon in Shanghai Nov 2 and 3. Attending the event from the Fundraising
team was Daniel Ruggeri (VP Fundraising) and Ted Liu (Sponsor Ambassador,
COSCon organizer).
-----------------------------------------
Attachment 3: Report from the VP of Marketing and Publicity [Sally Khudairi]
[REPORT] ASF Marketing & Publicity — November 2019
I. Budget: we are on budget as planned, with no outstanding payments due at
this time.
II. Cross-committee Liaison: Sally Khudairi continues to support ASF
Fundraising by securing 15 sponsorship renewals to date (7 Platinum, 5 Gold, 3
Silver), and is working with Virtual/ASF Accounting on settling a small
handful of overdue sponsor payments. She is working with ASF Sponsor
Ambassadors Bob Paulin and Craig Russell (Bronze sponsors) and Ted Liu
(Chinese sponsors) on renewals as well as new candidate sponsors at the Silver
and Bronze level. In addition, we are onboarding a new Targeted Sponsor. We
are also preparing Individual Giving & Corporate Contribution campaigns that
will be launching in the coming weeks. Additional support continues at the
Foundation/executive-level, along with ASF Conferences, ComDev, Brand
Management, and Diversity & Inclusion as needed. We published the Q1FY2020
Foundation Operations Summary (quarterly report) https://s.apache.org/a6s40 ,
and are working on a Sponsor case study/profile (similar to
https://s.apache.org/jKNc ) with support from Central Services/Editorial.
Principal photography on "Trillions and Trillions Served" (the documentary on
the ASF) resumed during ApacheCon Berlin
https://blogs.apache.org/press/entry/trillions-and-trillions-served-a ; we
have wrapped filming and are now entering 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 November 2019: The Apache Software Foundation Announces Apache® SINGA™ as
a Top-Level Project
IV. Informal Announcements: 6 items were published on the ASF "Foundation"
Blog. 5 Apache News Round-ups were issued, with a total of 279 weekly
summaries published to date. We tweeted 54 items to 55.3K followers on
Twitter, and posted 23 items on LinkedIn that garnered more than 91.1K organic
impressions.
V. Future Announcements: 1 announcement is 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 5 media queries. The ASF received 1,313
press clips vs. last month's clip count of 1,006. Media coverage of Apache
projects yielded 2,260 press hits vs. last month's 2,240. ApacheCon received
15 press hits. We had done an exhaustive amount of work with local press in
support of a Board-level keynote and overall ASF presence at a national
developer conference, but the outcome was highly disconnected for myriad
reasons: we are trying to see how it can be salvaged, if at all. This also
impacted another event in the same country, with the same publisher, but with
different Board members, who canceled their media activities as a result.
VII. Analyst Relations: we received 1 analyst query. Apache was mentioned in 3
reports by Gartner; 4 reports by Forrester; 2 reports by 451 Research; and 7
reports by IDC. We are also working with a global top 5 FinServ on a research
project.
VIII. Central Services: Kenneth Paskett attended ApacheCon Berlin on behalf of
ASF Marketing & Publicity/Central Services and met with the Open Source Design
community to explore ways we can engage on future Apache-related projects. The
timing is favorable, as a small handful of projects are seeking our assistance
with various creative and UX/site-related projects. We are also finalizing the
list of Central Services/Editorial projects through 2019.
IX. Events liaison: we will be supporting the Apache community with signage,
stickers, and swag for the ASF booths at Devnexus and FOSDEM in February 2020.
Per usual, we are standing by to assist ASF Conferences with planning,
advisory, and oversight for 2020 Roadshows and ApacheCon as needed.
X. Newswire accounts: our pre-paid press release package with GlobeNewswire
expires in 2021, but we will likely need to renew before then.
# # #
-----------------------------------------
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
==========
We are engaging a third-party to assist us with translations. This
should provide projects with a translation/crowdsource tool for their
translations. We're currently evaluating, with optimism.
Short Term Priorities
=====================
- Ensure stable backups after several disk failures/swaps.
Long Range Priorities
=====================
- Finalize a service for our projects' translations needs.
- Move qmail off our archaic fbsd servers to a new Ubuntu/Puppet install.
General Activity
================
- Migrated/upgrade our Subversion service to a new server.
- New features in the ".asf.yaml" service; several provided by Bryan
Ellis (an infra volunteer).
- Our translation service/VM has been incredibly difficult to upgrade.
We are testing a new, outsourced service for performing translations.
Apache OpenOffice is the primary user, so we are working with them
on testing and evaluation.
- A couple disks failed on our backup server, but thankfully not at
the same time. Our service provider is *very* fast with disk
replacements (about 15 minutes), but then it took several days each
time to "resilver" the RAID array. We are stable now, and will
monitor the system over the next few weeks. During this process, we
took a few extra steps at our cloud providers to create snapshots
and replications "just in case". We'll unwind those additional
precautions once we see our needed stability in the RAID array.
- Working with a potential service on our CI/CD. A new Jenkins Master
has been stood up, and testing is progressing.
- Working on moving many qmail/ezmlm configuration files into svn for
recovery/audit purposes.
- Nearing turn-down of our local Sonar analysis install, after moving
many projects to the hosted SonarCloud service. Several new projects
have signed up for the service.
- Implemented a new frontend component of our centralized blocking
service (blocky) that explains bans to affected users and guides
them through the unban process, should they request such. We hope
this new process will lessen the communication load when people find
themselves blocked on Apache services.
- Improved the infra-provided website statistics[1] available to all
projects, including adding a human-readable YAML version of the
various sheets of statistics.
[1] https://uls.apache.org/exports/
-----------------------------------------
Attachment 5: Report from the VP of Conferences [Rich Bowen]
VP Conferences took about a month "sabbatical" after ApacheCon North America,
which resulted in rather slower response to issues for that period. He is back
on the job now, and activity on the various event-related mailing lists has
picked back up.
ApacheCon Europe was held in Berlin, in October. While it was smaller than its
cousin in Las Vegas, the event itself was great, with truly amazing keynotes,
and a very engaged group of attendees.
At ApacheCon Europe we announced tentative dates for ApacheCon North America
2020, which will (again, tentatively - nothing is signed yet) be held in New
Orleans in the last week of September.
Due to the closeness of ACNA and ACEU in 2019, we intend to skip ACEU in 2020
in order to get back onto a six-month gap between events. However, it is also
being considered to alternate North America and Europe years, in order to have
a broader range of date options. This has not yet been determined, and there
are strong arguments on both sides.
In addition to ApacheCon, we are building out or 2020 calendar of events, and
they are listed on events.apache.org The list is currently:
* Apache Roadshow Chicago (Proposed) - 2020-05-27 to 2020-05-30
* Apache Roadshow, Seattle - 2020-06-10 to 2020-06-13
* ApacheCon North America, New Orleans - 2020-09-28 to 2020-10-03
* Apache Roadshow China (Proposed) - 2020-10-24 to 2020-10-26
An event has also been proposed in DC in May, but it is unclear at this time
whether this is a Roadshow or something else.
A call for volunteers to manage Small Events was sent to the members list.
Isaac Goldstand has stepped forward to manage that process, but other
volunteers are still welcome to assist in that. We intend for it to be a very
lightweight process. The goal is to encourage small events such as meetups,
focused on Apache technologies. A budget was approved for this for the past
several years, but we have not, to date, spent any of that budget.
A discussion is ongoing on the planners list regarding policy around approving
events that conflict with other Apache official events. This begins with
defining what a conflict is. Member input into that is welcomed on that list
(planners@apachecon.com).
You should expect to see more calls for volunteers around 2020 and 2021 events
in the coming weeks, as we try to be more aggressive about announcing our
event schedule further in advance. This makes sponsor acquisition easier, and
also helps avoid conflicts with other conferences in our ecosystem.
A new photo site has been launched at photos.apachecon.com in order to have
our event photographs all in one place, which we control and back up. This was
largely spurred by the recent changes to the Flickr limits, which resulted in
many of our historic photographs disappearing. If you have photographs from
past events, please contact the planners list for information on how to share
them with the community.
-----------------------------------------
Attachment 6: Report from the Apache Travel Assistance Committee [Gavin McDonald]
Travel Assistance Report (November 2019)
========================================
ApacheCon EU 2019 Berlin
=====================
TAC had 14 people attend Berlin after a couple of late withdrawals and one
visa denial.
We had a TAC 'Lunch' on the Monday comprising the 14 attendees and some
invited long time ASF folks. As usual, this was received very well by the
attendees and they got a lot out of the lunch.
Right after lunch we had a meeting to go through what is expected of the
attendees for the week and went through what sessions they would be hosting.
Having some of this pre-filled before arrival meant that this went pretty
smoothly.
During the week, the attendees all performed their duties well and the
organisers were happy with the level of assistance given.
Post event surveys are yet to be sent out.
Congrats from the entire TAC Committee go to Chris Dutz as Lead TAC organiser
for this event, for a well prepared and well executed Conference from the TAC
side of things. Hard work from the beginning through to the event itself
ensured a smooth process and a successful ACEU from the TAC standpoint.
TAC Meeting
==========
committer supported / small events
-----------------------------------------------
A few members of the TAC Committee had a face to face meeting in Berlin which
lasted just over 2 hours. Present at the meeting were Gavin McDonald, Daniel
Gruno, Chris Dutz and Nick Burch.
A number of items were discussed, raw notes of which were posted to the main
travel-assistance mailing list. Follow up and further discussions of some of
those have continued on list. Some of these are mentioned below.
TAC has approved funding for committers; and funds for smaller/non ApacheCon
events. We are trialing use of the new committer funding by supporting taking
a group of committers to Fosdem 2020 at the beginning of February. Gavin is
Lead for this event. The application process for this and other
smaller/committer events will be revamped and simpler. Note that at the time
of writing, the approval of Stands/Booths has not been released.
There is a list of other suggested non ApacheCon events to support, the next
one after Fosdem is likely to be Berlin Buzzwords.
Projects should note that TAC has funds to support travel/hotel for project
organised meetups/hackathons. An email to all PMCs will start to be sent
quarterly reminding/informing them of this.
Travel Arrangements
----------------------------
A major topic and one that has been under scrutiny quite recently. Making
Travel arrangements for successful applicants is quite a time consuming
process. Liaising with a Travel Agent by email and by phone (and recently even
in person!), getting many quotes to approve, sending them to the applicant for
approval, then back to the TA. Travel Insurance, Visa support letters, Hotel
room booking dates to be timed with flight arrival/departures etc. This was
hard enough for 10 to 20 people. Now, we also have increased budget to have at
least another 20+ people (per event) on top of that, more than doubling the
work effort.
(In a one year period, our budget could allow us to take around 100 people)
Add into the mix recently for ACNA there was a poor experience with a Travel
Agent, often taking days to respond, adds pressure.
Therefore, during our TAC Committee meeting , we agreed to ask about the
possibility of getting paid help in this area, a part time contract possibly,
where that person gathers all the information needed and performs all the
booking tasks, from quote, to visas, support letters, to ticketing and
ensuring payment. Keeping the TAC committee in the loop at each stage, but
taking away all that work that volunteers currently do, allowing them to
concentrate on other important aspects. TAC has asked EVP about this and are
awaiting a reply.
Payment Methods
-------------------------
Another important topic discussed was that of payment methods. Payments to
Travel Agents, Hotels etc.
Payments to Travel Agents involve lump sum amounts sent via international wire
transfer, usually needing a final top up via the TAC credit card. Payments to
Hotels for TAC recipients rooms sometimes also require a wire transfer - as
was the case for Berlin. This was not without its own issues either - the
Hotel received the wire transfer into their account on the Monday afternoon,
our TAC attendees arrived the day before, so payment was asked for by Credit
Card monday morning. Therefore the Hotel actually received 2 x payments. They
have refunded the duplicate amount to the event organisers, who are
calculating what we owe them and refunding the rest back to us. A messy
process that might have been avoided if TAC had something like Transferwise -
international payments made instantly and at mid-market rates and small fixed
fee. This would make things much easier in the future. TAC has asked EVP to
inquire about this and are awaiting a reply.
TAC Credit Card
----------------------
The TAC card, in addition to a relatively small maximum allowed balance, also
has a maximum daily withdrawal limit. Although since having a TAC card, which
has been extremely invaluable, there has been instances on occasion where the
daily limit was exceeded and so had to borrow from another staffer until the
next day when it could be paid back. The maximum limit may also soon become an
issue , with an increased budget, comes increased TAC attendees, comes
increased on site expenditures. TAC Chair has a todo to ask the Treasurer for
an increase in both the daily limit and the overall maximum balance.
Committee Membership
==================
TAC is a working Committee, and likes to align its membership with active
members every couple of years. Inactive members are always welcome to re-join
should they find themselves with time to become active again. Inactive members
were notified on list last month. TAC Chair will make the changes known to the
President in the next few days. There are also some additions to the committee
to announce at the same time.
---
Gav...
-----------------------------------------
Attachment 7: Report from the VP of Finance [Tom Pappas]
* Continued work with Fundraising committee
* Assisted Seattle Roadshow team, with agreement and insurance
* Working on Travel and General Liability insurance for the Foundation
* Verified D&O insurance is current
* Renewed Foundation Registered Agent
-----------------------------------------
Attachment 8: Report from the VP of Diversity and Inclusion [Gris Cuevas]
October 2019 Report
## 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:
Two points that are not really issues, but more resetting expectations:
The feedback and decision making process to launch the survey has pushed the
entire project by 2 months since the holidays get on the way of new
deadlines. New Expected time for a full report on EDI analysis is May.
Comms plan for D&I committee is on hold due to bandwidth to work on it and
the survey. Focusing on the survey first.
## Activity:
*** Project: Survey revamp***
We're in the final review for V1.0 for the survey (see final deck here [1]
There is a vote to finalize best way to send survey [2], current plans are:
1. Use LimeSurvey as the platform for the EDI Survey and share visibly a link
to their data privacy policy.
2. Upload a list of all apache.org email addresses to LimeSurvey and send
direct emails to individuals
3. Use a re-usable token for a universal link that we'll use to promote the
survey in social media
I re-opened the vote and intent to close it on Friday, will assume lazy
consensus.
*** Project: UX Research on new contributors ***
Nothing has happened yet since this part is pending some initial results from
the survey. As soon as we get the survey published, we'll start working on
the questions for the interviews.
*** Project: Internships for underrepresented groups (Outreachy) ***
We are 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.
The contributions period started on Oct. 1t and ended on Nov. 5th. Two
projects out of three got contributions recorded. 5 contributions recorded in
total. [3]
We encounter some problem while attracting applicants to record
contributions. We think that there could be two reasons for this: the skill
level required in the project is too high, the wording of the project is a
bit intimidating due to the technical language or unclear goals and/or high
system requirements. In order to address this issue, we took the following
action:
setup cheat sheet + more guided or explained tasks. Include this sheet in the
project submission to guide applicants in their initial contributions. we've
seen sometimes there is no time to address all queries/questions from
applicants, therefore we could include this sheet to help them guide
themselves. We opened a conversation to create a "Tooling training for ASF
projects" [4].
we need a more easy-to-start development environment. regarding applicants
with less experience. In this case, it is hard to find a solution other than
committing enough mentor time, which is hard to find. We opened a discussion.
The period for the selection of interns start on Nov. 6th and ended on Nov.
14th. After rating contributions, one intern has been selected. [5] Friction
log: we started working with the coordinators of the friction log of the
Survey Design & Contributor Experience Research project. First draft of the
friction log template has been shared on the mailing list dev@ [6].
*** Operations ***
First payment to Bitergia was approved on the 15th. This payment is for
Milestone 1, total amount $30,000 out of the total $75,000 for the project.
*** Community Highlights ***
New contributors have been collaborating in the EDI projects: Laura Zanella
Arianne Navarro
## Health report:
Mailing list continues to be active with regular emails from the working
groups. A few new members have joined and participated. Some people have been
sharing interesting articles and started good discussions.
## Committee members changes:
None
## References
[1] https://docs.google.com/document/d/1tCQvR1NmR8ds8dqECr0Hs6vheKjouDclBjhZQfMoLlQ/edit
[2] https://lists.apache.org/thread.html/250bf12767efb5a6d433834c489677b9bba3ca5e5d69b06596a38836@%3Cdev.diversity.apache.org%3E
[3] https://www.outreachy.org/december-2019-to-march-2020-internship-round/communities/apache/applicants/
[4] 2019-10-31 Outreachy Meeting notes
[5] https://www.outreachy.org/december-2019-to-march-2020-internship-round/communities/apache/applicants/
[6] http://mail-archives.apache.org/mod_mbox/diversity-dev/201911.mbox/%3cCAN_Ypr3cHMcSgd3t1xH3pzMCBof6B9dK0i2WDFtFJ1Q+P1aQdw@mail.gmail.com%3e
-----------------------------------------
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 dow 2 to 20, 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.
Two noteworthy discussions are around LEGAL-488 and LEGAL-489 where we are
trying to figure out how to help NetBeans community in particular (and anyone
in business of build end-to-end end-user facing project at ASF be able to
ship their binaries based on modularization framework available in modern
JREs).
-----------------------------------------
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 October 2019:
3 [license confusion]
14 [support request/question not security notification]
Security reports: 29 (last months: 28, 46, 26, 23)
5 [site]
4 [httpd], [tomcat]
3 [guacamole]
2 [cloudstack], [netbeans]
1 [airflow], [deltaspike], [dubbo], [hadoop], [infrastructure],
[jmeter], [ofbiz], [struts], [xmlgraphics]
In total, as of 31st Oct 2019, we're tracking 74 (last month:
81) open issues across 37 projects, median age 88 (last month:
75) days. 37 of those issues have CVE names assigned.
7 (last month: 8) of these issues, across 5 projects, are older
than 365 days.
-----------------------------------------
Attachment 12: Report from the VP of Data Privacy [John Kinsella]
-----------------------------------------
Attachment 13: Report from the VP of Jakarta EE Relations [Mark Struberg]
-----------------------------------------
Attachment A: Report from the Apache Ambari Project [Jayush Luniya]
## Description:
The mission of Apache Ambari is the creation and maintenance of software
related to Hadoop cluster management
## Issues:
- There are no issues requiring board attention at this time.
## Membership Data:
Apache Ambari was founded 2013-11-19 (6 years ago)
There are currently 106 committers and 48 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 Ishan Bhatt on 2018-10-25.
- Masahiro Tanaka was added as committer on 2019-11-07
## Project Activity:
- 2.7.4 was released on 2019-09-13.
- 2.7.3 was released on 2018-11-17.
- 2.7.1 was released on 2018-08-27.
## Community Health:
- The development community and engagement remains good, however many
committers and PMC members have moved to other projects.
-----------------------------------------
Attachment B: Report from the Apache Ant Project [Jan Materne]
## Description:
The mission of Apache Ant is the creation and maintenance of the Ant build
system and related software components.
It consists of 3 main projects:
- Ant - core and libraries (AntLibs)
- Ivy - Ant based dependency manager
- IvyDE - Eclipse plugin to integrate Ivy into Eclipse
Additionally Ant provides several extensions to Ant (antlibs).
## Issues:
There are no issues requiring board attention at this time.
## Membership Data:
Apache Ant was founded 2002-11-18 (17 years ago)
There are currently 29 committers and 23 PMC members in this project.
The Committer-to-PMC ratio is roughly 4:3.
Community changes, past quarter:
- No new PMC members. Last (re)addition was Magesh Umasankar on 2018-07-06.
- No new committers. Last addition was Jaikiran Pai on 2017-06-14.
## Project Activity:
- Ivy 2.5.0 was released on 2019-10-24 (after a long period of minor activity).
- Ant 1.10.7 was released on 2019-09-05.
- (Ant 1.10.6 was released on 2019-05-08).
## Community Health:
For Ant we feel healthy enough to apply patches, and get a release done. But
basically we are in "maintenance mode". There isn't much development.
For IvyDE we lack the knowledge of building Eclipse plugins on actual Eclipse
versions. We hope to get the build running again so we could update that.
-----------------------------------------
Attachment C: Report from the Apache BookKeeper Project [Sijie Guo]
## Description:
BookKeeper is a scalable, fault-tolerant, and low-latency storage
service optimized for append-only workloads. It has been used as
a fundamental service to build high available and replicated services
in companies like Twitter, Yahoo and Salesforce. It is also the log
segment store for Apache DistributedLog and message store for Apache Pulsar.
Apache DistributedLog is a high-level API and service layer for
Apache BookKeeper, providing easier access to the BookKeeper
primitives. It is a subproject of Apache BookKeeper.
## Issues:
There are no issues requiring board attention at this time.
## Membership Data:
Apache BookKeeper was founded 2014-11-19 (5 years ago)
There are currently 21 committers and 16 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 Charan Reddy G on 2019-07-24.
- No new committers. Last addition was Andrey Yegorov on 2018-02-09.
## Project Activity:
- 4.9.1 was released on April 7 2019
- 4.9.2 was released on May 16 2019
- 4.10.0: was released on November 6 2019
- The growth of Apache Pulsar community also help grow the adoption
of BookKeeper. This helps building the ecosystem around BookKeeper.
- The project is also extending its scope to cover long term distributed
storage and now bundles a new KV distributed database (StreamStorage).
- We released a new Python client for the StreamStorage service.
- We are working on a brand new CLI interface
GitHub issues:
19 issues opened on GitHub, past quarter (35% increase)
35 issues closed on GitHub, past quarter (191% increase)
GitHub PR activity:
37 PRs opened on GitHub, past quarter (2% increase)
26 PRs closed on GitHub, past quarter (-33% decrease)
## Community Health:
- During the last quarter there development slowed down a little and we
missed one scheduled release (we started a Time based release plan this
year).
- During the last months new users and contributors appeared especially from
Apache Pulsar community and from other OSS projects that were born recently
and are based on Apache BookKeeper.
- Mailing list discussions are brisk, in particularly around the active
projects.
-----------------------------------------
Attachment D: Report from the Apache Brooklyn Project [Geoff Macartney]
## Description:
The mission of Apache Brooklyn is the creation and maintenance of software
related to a software framework for modeling, monitoring and managing cloud
applications through autonomic blueprints.
## Issues:
- there are no issues requiring board attention at this time
## Membership Data:
Apache Brooklyn was founded 2015-11-18 (4 years ago)
There are currently 16 committers and 16 PMC members in this project.
The Committer-to-PMC ratio is 1:1.
Community changes, past quarter:
- No new PMC members. Last addition was Duncan Grant on 2018-08-30.
- No new committers. Last addition was Duncan Grant on 2018-06-13.
## Project Activity:
- Brooklyn is quite stable at present, with a low level of development
activity. Discussions and assistance to users continues on the mailing
list.
## Releases:
- Last release was 1.0.0-M1 on Mon Sep 17 2018
## Community Health:
- The project continues with a low turnover of pull requests and commits.
- We continue to monitor our community for potential new committers and PMC
members with the aim of regularly adding individuals.
- We had previously discussed releasing Brooklyn 1.0.0, but have not yet managed
to get this organised.
-----------------------------------------
Attachment E: Report from the Apache Buildr Project [Antoine Toulme]
## Description:
Apache Buildr is a build system for Java-based applications, including
support for Scala, Groovy and a growing number of JVM languages and
tools. We wanted something that’s simple and intuitive to use, so
we only need to tell it what to do, and it takes care of the rest.
But also something we can easily extend for those one-off tasks, with
a language that’s a joy to use. And of course, we wanted it to be
fast, reliable and have outstanding dependency management.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- We have released 1.5.8 in July. We haven't had any activity since.
## Health report:
- We still have a small PMC presence of 3 active members still able
to vote releases.
## PMC changes:
- Currently 7 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Peter Donald on Tue Oct 15 2013
## Committer base changes:
- Currently 10 committers.
- Olle Jonsson was added as a committer on Wed Dec 12 2018
## Releases:
- Last release was 1.5.8 on July 14th 2019
-----------------------------------------
Attachment F: Report from the Apache Cassandra Project [Nate McCall]
## Description:
The Apache Cassandra database is the right choice when you need scalability
and high availability without compromising performance. Linear scalability and
proven fault-tolerance on commodity hardware or cloud infrastructure make it
the perfect platform for mission-critical data. Cassandra's support for
replicating across multiple datacenters is best-in-class, providing lower
latency for your users and the peace of mind of knowing that you can survive
regional outages.
## Issues:
No issues to report at this time.
## Membership Data:
Apache Cassandra was founded 2010-02-17 (10 years ago)
There are currently 54 committers and 33 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:2.
Community changes, past quarter:
- Chris Lohfink was added to the PMC on 2019-10-01
- No new committers this quarter.
## Project Activity:
This quarter has been active. We have had a very successful ApacheCon with 2
well attended tracks over three days. Of the vendors there, five of them had
Cassandra product offerings while two were focused exclusively on Cassandra.
We have already begun talking a similar sized effort for ApacheCon NA 2020.
We have begun migrating our site off of SVN as that has been a barrier to
entry in accepting documentation patches in a timely manner.
We have released two alphas of the upcoming 4.0 and received helpful feedback
and bug reports from the community. All other active versions were released as
well. A list of releases follows:
- 2.2.15 was released on 2019-10-29.
- 3.0.19 was released on 2019-10-29.
- 3.11.5 was released on 2019-10-29.
- 4.0-alpha2 was released on 2019-10-29.
- 2.2.15 was released on 2019-10-29.
## Community Health:
Interesting statistics from community health:
- dev@cassandra.apache.org had a 163% increase in traffic in the past quarter
(329 emails compared to 125)
- 44 PRs opened on GitHub, past quarter (69% increase)
- 20 PRs closed on GitHub, past quarter (53% increase)
- 124 issues opened in JIRA, past quarter (-21% decrease)
- 52 issues closed in JIRA, past quarter (-40% decrease)
We think this reduction of new and closed issues in JIRA in conjunction with
the rate of PRs addressed is indicative of the community efforts focused on
the alpha releases of 4.0. Dev list traffic is up as a result of some good
discussions regarding development processes (soon to be published), releases
and documentation.
-----------------------------------------
Attachment G: Report from the Apache Clerezza Project [Hasan Hasan]
DESCRIPTION
Apache Clerezza models the RDF abstract syntax in Java and provides supports
for serializing, parsing, managing and querying triple collections (graphs).
Apache Clerezza modules aim at supporting the development of Semantic Web
applications and services.
ISSUES FOR THE BOARD
There are no issues requiring board attention at this time.
RELEASE
Latest release of the parent module was created on November 04, 2019.
All other modules will be released within Q4 2019 and Q1 2020.
Since each module has its own release version, only independent modules
can be released together.
ACTIVITY
Parent module's pom.xml has been cleaned up, including update of dependencies
to latest version of various artifacts.
COMMUNITY
Latest change was addition of a new committer and PMC member on 27.12.2018
INFRASTRUCTURE
Latest update of the Apache Clerezza Website was in February 2018.
-----------------------------------------
Attachment H: Report from the Apache Cocoon Project [Cédric Damioli]
## Description:
Web development framework: separation of concerns, component-based.
## Issues:
there are no issues requiring board attention at this time
## Activity:
Still very few activity on the project. Still active PMC members around here.
Question on dev list showed that there is still someone to answer (quickly).
An email to users@infra.a.o about our git mirror remains unanswered.
The most recent release is 2.1.12 on 2013-03-14
A few JIRA issues opened or resolved since last report.
A little activity on both users and dev mailing-lists, even if still at a low level.
The project is mainly in maintenance mode.
## PMC changes:
None.
Most recent addition: 2012-07-06
## Committer base changes:
None.
Most recent addition: 2012-07-06
-----------------------------------------
Attachment I: Report from the Apache Community Development Project [Sharan Foga]
## Description:
The mission of Community Development is to help, support and create resources
for people to become involved with Apache projects
## Issues:
- No issues require board attention at the moment
## Membership Data:
Apache Community Development was founded 2009-11-01 (10 years ago)
There are currently 33 committers and 31 PMC members in this project.
The Committer-to-PMC ratio is roughly 9:8.
Community changes, past quarter:
- No new PMC members. Last addition was Christofer Dutz on 2019-06-21.
- No new committers. Last addition was Christofer Dutz on 2019-06-21.
## Project Activity:
Redbubble
Projects have continued to request setup for the Redbubble store and
we now have nearly 50 different logos available. Some training has been done
so that we have additional administrators to help setup new logos when
requested.
ApacheCon
In preparation for both ApacheCon NA and ApacheCon EU we asked
projects to let us know if they wanted stickers ordered for the event. We
especially let incubating projects know they too could be included. In total
approx 50,000 stickers were ordered and the Apache booth at booth was
completely covered. Feedback from attendees was extremely positive and for
some projects this was the first time that they had their stickers available
New Reporter Tool
One of the tools provided for projects to use, is a reporter
tool for preparing their quarterly reports to the ASF Board. This tool has
been updated and now includes a new interface, additional community statistics
and is integrated into the Board agenda itself.The new version was trialled
and has now been adopted.
Apache Local Community
One of the discussions this quarter was around setting
up local groups of Apache and open source contributors that would be
responsible for organising meetings and events.A new organisational structure
has been proposed and it is still unclear if these will form part the general
ASF initiative around Apache Small events, or if it will be managed as part of
ComDev.Two events (24th August & 28th September) have already been held, both
in Indore, India
Events
Members from the community participated in events such as All Things
Open, where we had a booth and CCOSS 19 in Guadalajara, Mexico. There was an
Apache track with talks ranging from Getting Started to Governance and Open
Source Licences. This was a great opportunity to connect with potential new
contributors to open source. We have applied for a booth at FOSDEM and are
awaiting the result. We are still receiving requests to participate at events
and have recently offered a booth at Devnexus in Atlanta in March 2020.
## Community Health:
Mailing list traffic has decreased significantly this quarter. This could be
as a result of the holiday season and also that both ApacheCon NA and
ApacheCon EU took place this during this period.
dev@community.apache.org had a 46% decrease in traffic in the past quarter
(292 emails compared to 531):
-----------------------------------------
Attachment J: Report from the Apache CouchDB Project [Jan Lehnardt]
## Description:
Apache CouchDB software is a document-oriented database that can be queried and
indexed in a MapReduce fashion using JavaScript. CouchDB also offers
incremental replication with bi-directional conflict detection and resolution.
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache CouchDB was founded 2008-11-19 (11 years ago)
There are currently 64 committers and 15 PMC members in this project.
The Committer-to-PMC ratio is roughly 4:1.
Community changes, past quarter:
- No new PMC members. Last addition was Nick Vatamaniuc on 2017-11-07.
- No new committers. Last addition was Jay Doane on 2019-01-05.
## Project Activity:
- project management tasks and work tickets to close up all remaining tasks
for the 3.0 release are commencing nicely.
- foundational work for 4.0 is going on concurrently.
- a number of our committers are attending the FoundationDB Summit this week,
to meet with the larger FoundationDB community (see previous reports for
a detailed explanation)
## Community Health:
In the past quarter we’ve been in chugging-along mode mostly on all
official channels. The unofficial CouchDB Slack instance is seeing a continuous
uptick in activity, which might explain the decrease in user@ traffic.
A lot of work is happening in PRs as opposed to merges to master at the
moment, which explains the relative shift in numbers there.
dev@couchdb.apache.org had a 2% decrease in traffic in the past
quarter (153 emails compared to 156)
user@couchdb.apache.org had a 75% decrease in traffic in the past
quarter (36 emails compared to 140)
318 commits in the past quarter (-19% decrease)
32 code contributors in the past quarter (28% increase)
147 PRs opened on GitHub, past quarter (59% increase)
135 PRs closed on GitHub, past quarter (62% increase)
113 issues opened on GitHub, past quarter (43% increase)
70 issues closed on GitHub, past quarter (79% increase)
-----------------------------------------
Attachment K: Report from the Apache Creadur Project [Brian E Fox]
Apache Creadur creates and maintains a suite of open source software related
to the auditing and comprehension of software distributions. Any language and
build system are welcomed.
Status
------
Creadur is primarily used by other Apache projects to help check for
conformity to ASF standards. This is why the project team is primarily
comprised of members and committers from other ASF projects. The risk
of the project foundering is therefore very low despite the ongoing
lack of progress.
If someone has an itch to scratch, it will no doubt get fixed.
Community
---------
This month we are proposing to rotate the PMC chair from Brian Fox
to Phil Ottlinger. See associated agenda item.
In July, Sebb stepped down from the PMC In September 2016 Karl Heinz Marbaise
was elected to join the PMC
Releases
--------
Apache Rat 0.13 was released Nov 5th, 2018 Apache Rat 0.12 was released in
June 2016 Apache Rat 0.11 was released in August, 2014 Apache Rat 0.10 was
released in September, 2013
-----------------------------------------
Attachment L: Report from the Apache DeltaSpike Project [Mark Struberg]
## Description:
The mission of DeltaSpike is the creation and maintenance of software related
to Portable CDI extensions that provide useful features for Java application
developers
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache DeltaSpike was founded 2013-04-17 (7 years ago)
There are currently 35 committers and 19 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 Harald Wellmann on 2016-05-19.
- Christian Beikov was added as committer on 2019-10-21
## Project Activity:
We are right now preparing for a 1.9.2 release.
We expect it in the next 2 weeks. There are user requests
coming in and we react in a decent time frame. We also right now
go through old tickets and clean them up.
With the advent of MicroProfile we got a bit competition, but
overall that's healthy and the communities are working well with
each other.
## Community Health:
We have a new committer and are always actively looking out for new
folks which might be a good addition.
-----------------------------------------
Attachment M: Report from the Apache DRAT Project [Tom Barber]
## Description:
- Apache DRAT is a distributed, parallelized (Map Reduce) wrapper around
Apache RAT™ and other code auditing tools to allow it to complete on large
code repositories of multiple file types.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- DRAT is still awaiting a 1.0 release and is still currently blocked by the
latest Apache OODT codebase. Work is still progressing to resolve that.
- A new React based user interface has also been prototyped and plans are
being worked on to integrate that UI into the Apache DRAT codebase.
## Health report:
- Slow pace of development, but functioning PMC and looking to get 1.0
released.
## PMC changes:
- Currently 14 PMC members.
- Ahmed Ifhaam was added to the PMC on Thu Aug 30 2018
## Committer base changes:
- Currently 14 committers.
- Ahmed Ifhaam was added as a committer on Tue Aug 28 2018
## Releases:
- Work is ongoing to ready a 1.0 release
## Mailing list activity:
- Mailing list activity was pretty flat, but expected
- dev@drat.apache.org:
- 16 subscribers (down -1 in the last 3 months):
- 0 emails sent to list (50 in previous quarter)
- issues@drat.apache.org:
- 10 subscribers (up 0 in the last 3 months)
-----------------------------------------
Attachment N: Report from the Apache Drill Project [Charles Givre]
## Description:
The mission of Drill is the creation and maintenance of software related to
Schema-free SQL Query Engine for Apache Hadoop, NoSQL and Cloud Storage
## Issues:
There are no issues requiring board attention at this time.
## Membership Data:
Apache Drill was founded 2014-11-18 (5 years ago)
There are currently 55 committers and 24 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 Sorabh Hamirwasia on 2019-04-04.
- No new committers. Last addition was Anton Gozhiy on 2019-07-22.
## Project Activity:
- Drill 1.16 was released on 2019-05-02.
- Drill 1.17 was delayed until end of November.
### Next Release
The next release of Drill (1.17) resolved many issues and added a lot of new
functionality including:
- Enhanced Drill metastore
- Hive complex types support (arrays, structs, union)
- Canonical Map<K, V> support
- Schema provisioning via table function
- Empty parquet files read / write support
- Run-time row group pruning
- Numerous enhancements and upgrades to Drill with Hive
- Format plugin for Excel Files
- Format plugin for ESRI Shape Files
- Add Variable Argument UDFs
- Add UDF to parse user agent strings
### Future Functionality in Development
There are a number of enhancements for which there are active PRs or discussions
on the various boards.
- Integration between Apache Drill and Apache Daffodil (Incubating)
- Storage plugin for Apache Druid
- Upgrading Drill to use Hadoop v. 3.0
- Format plugin for HDF5
## Community Health:
Drill seems to be recovering from the collapse of Drill's major backer MapR.
### Development Activity
- 96 issues opened in JIRA (1% increase from last quarter)
- 85 issues closed in JIRA (28% increase from last quarter)
- 55 commits in past quarter (14% increase from last quarter)
- 15 contributors from last quarter (25% increase)
- 53 PRs opened on GitHub (no change from last quarter)
- 63 PRs closed on GitHub (no change from last quarter)
### Email Lists
- dev@drill.apache.org
- 46% increase in traffic in past quarter (1574 compared to 1073)
- issues@drill.apache.org
- 47% increase in traffic in past quarter (2027 compared to 1377)
- users@drill.apache.org
- 27% decrease in traffic in past quarter (116 compared to 157)
-----------------------------------------
Attachment O: Report from the Apache Empire-db Project [Rainer Döbele]
## Description:
The mission of Empire-db is the creation and maintenance of software related to
Relational Data Persistence
## Issues:
There are no issues requiring board attention at this time.
## Membership Data:
Apache Empire-db was founded 2012-01-24 (8 years ago)
There are currently 9 committers and 10 PMC members in this project.
The Committer-to-PMC ratio is roughly 9:10.
Community changes, past quarter:
- No new PMC members. Last addition was Jan Glaubitz on 2016-07-10.
- No new committers. Last addition was Jan Glaubitz on 2015-10-05.
## Project Activity:
During the past three months considerable work has been done on the project:
17 issues have been opened in JIRA. 51 commits have been performed by 3
contributors. As soon as the issues have all been resolved and features are
complete a new release will be published.
## Community Health:
Attracting new committers has not been easy and remains difficult. This may be
due to serveral reasons like e.g. relational database access is a rather old
subject that is not the most trendy among young developers. Also there is not
a lot of change in the underlying relational database systems either. However
we acknowledge that especially our website needs more attention and updates.
This will probably be done with or after the upcoming release.
-----------------------------------------
Attachment P: Report from the Apache Flume Project [Ferenc Szabo]
## Description:
The mission of Flume is the creation and maintenance of software related to A
reliable service for efficiently collecting, aggregating, and moving large
amounts of log data
## Issues:
There are no issues requiring board attention at this time.
## Membership Data:
Apache Flume was founded 2012-06-20 (7 years ago)
There are currently 31 committers and 24 PMC members in this project.
The Committer-to-PMC ratio is roughly 4:3.
Community changes, past quarter:
- No new PMC members. Last addition was Ferenc Szabo on 2019-01-28.
- No new committers. Last addition was Attila Simon on 2017-11-04.
## Project Activity:
The project has a slow but steady activity. Some documentation fixes came in
and as a new feature the Kudu sink thanks to the Kudu community.
## Community Health:
The community is still alive. New contributors show up time to time.
Reviewing is a bit slow.
-----------------------------------------
Attachment Q: Report from the Apache Forrest Project [David Crossley]
Apache Forrest mission is software for generation of aggregated multi-channel
documentation maintaining a separation of content and presentation.
Issues needing board attention:
None.
Changes in the PMC membership:
None.
Last modified: 2013-04-08
Most recent addition: 2009-06-09
New committers:
None.
Most recent addition: 2009-06-09
None on the horizon.
General status:
The most recent release is 0.9 on 2011-02-07.
At this report, two other PMC members responded to my draft report.
This confirms that there are sufficient people hanging around for us to
potentially be able to make a decision.
Project status:
Activity: Idle
There is a vote underway on the Forrest developers mailing list to
determine the desire of the project regarding the potential retirement and
move to the Attic. Also notified the users mail list. It is due to be
tallied in early December to allow plenty of time for people to respond.
Security issues published:
None.
Progress of the project:
None.
-----------------------------------------
Attachment R: Report from the Apache FreeMarker Project [Dániel Dékány]
## Description:
Apache FreeMarker is a template engine, i.e. a generic tool to generate text
output based on templates. Apache FreeMarker is implemented in Java as a class
library for programmers.
FreeMarker 2 (the current stable line) produces releases since 2002. The
FreeMarker project has joined the ASF in 2015, and graduated from the
Incubator in early 2018.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
We have released a new version mid August, with some major features.
Development slowly but steadily continues towards the next version, addressing
feature requests from the users.
## Health report:
Activity is low but steady, as it's usual for this project. User questions
(mostly on StackOverflow) and new Jira issues are being answered promptly. The
short term goal is to develop the next micro version (2.3.30). The long term
goal is continuing the ongoing development on the 3.0 branch, so that the
project can innovate and the code base can become much cleaner and more
attractive for new committers.
## PMC changes:
- Currently 7 PMC members.
- No changes since the graduation on 2018-03-21
## Committer base changes:
- Currently 7 committers.
- No changes since the graduation on 2018-03-21
## Releases:
- 2.3.29 was released on 2019-08-17
-----------------------------------------
Attachment S: Report from the Apache Geode Project [Karen Miller]
## Description:
The mission of Apache Geode is the creation and maintenance of software
related to a data management platform that provides real-time, consistent
access to data-intensive applications throughout widely distributed cloud
architectures.
## Issues:
There are no issues requiring board attention at this time.
## Membership Data:
Apache Geode was founded 2016-11-15 (3 years ago) There are currently 104
committers and 52 PMC members in this project. The Committer-to-PMC ratio is
2:1.
Community changes, past quarter:
- Bill Burcham was added to the PMC on 2019-09-08
- Mario Ivanac was added to the PMC on 2019-09-08
- Bill Burcham was added as committer on 2019-09-09
- Mario Ivanac was added as committer on 2019-09-09
## Project Activity:
- Released Apache Geode 1.10.0 on 2019-09-26.
- Released Apache Geode 1.9.1 on 2019-09-06.
- Released Apache Geode 1.9.2 on 2019-10-29.
## Community Health:
The community is actively contributing to the Apache Geode code base. In the
past quarter:
- 61 code contributors
- 347 issues opened in JIRA
- 275 issues closed in JIRA
- 434 PRs opened on GitHub
- 426 PRs closed on GitHub
Enjoyed great attendance at the Apache Geode Summit held October 7, 2019, in
Austin, Texas, with 500 attendees at the 12 sessions.
-----------------------------------------
Attachment T: Report from the Apache Giraph Project [Dionysios Logothetis]
## Description:
The mission of Giraph is the creation and maintenance of software related to
Iterative graph processing system built for high scalability
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache Giraph was founded 2012-05-15 (7 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 Dionysios Logothetis on 2018-04-22.
- No new committers. Last addition was Dionysios Logothetis on 2018-04-23.
## Project Activity:
- Mechanism for maintaining counters depends on the underlying resource
management (e.g. Hadoop, Yarn). Made a change that allows the use of
counters independently from the resource management system.
- Made the thrift client configurable. This ensures users with different
requirements with respect to the thrift services can plug their own client
(e.g. the may require security-related configuration).
- Currently working on upgrading the Netty dependency. This is a core
dependency that hasn't been updated for many years. It requires a lot of
experimentation to ensure there are no regressions. This will be committed
in the next couple of months.
## Community Health:
- Even though it did not come from new contributors, due to the development of
the features mentioned above, there was increased activity this last
quarter.
-----------------------------------------
Attachment U: Report from the Apache Gora Project [Kevin Ratnasekera]
## Description:
- The Apache Gora open source framework provides an in-memory data model and
persistence for big data. Gora supports persisting to column stores, key-value
stores, document stores, distributed in-memory key-value stores, in-memory data
grids, in-memory caches, distributed multi-model stores and hybrid in-memory
architectures. Gora also enables analysis of data with extensive Apache Hadoop
MapReduce, Apache Spark, Apache Flink, and Apache Pig support.
## Issues:
- There are no issues requiring board attention at this time.
## Membership Data:
Apache Gora was founded 2012-01-24 (8 years ago)
There are currently 30 committers and 30 PMC members in this project.
The Committer-to-PMC ratio is 1:1.
Community changes, past quarter:
- Chanaka Balasooriya was added to the PMC on 2019-09-07
- John Mora was added to the PMC on 2019-09-24
- Sheriffo Ceesay was added to the PMC on 2019-10-01
- Chanaka Balasooriya was added as committer on 2019-09-08
- John Mora was added as committer on 2019-09-25
- Sheriffo Ceesay was added as committer on 2019-10-01
## Project Activity:
- Last quarter was mainly about post release work and GSoC mentoring efforts.
Apache Gora 0.9 was released on 2019-08-15.
- Apache Gora community elected new 3 committer / PMC members to the project
based on solid contributions. This includes two of recent GSoC students as well
as one external contributor.
- We also received several other contributions which are at the moment, under
our community review process. Hopefully we will finish these and potentially
evaluate to further extend our committer base.
## Community Health:
There has some decent level of Github and Mailing list activity, even though
it's post release period for us. Current plan is to reignite discussions
around, steps for our next release development drive. Time to time we observe
some external contributors, making effort in joining our community.
- dev@gora.apache.org had a 76% increase in traffic in the past quarter
(586 emails compared to 332)
- 16 issues opened in JIRA, past quarter (60% increase)
- 6 issues closed in JIRA, past quarter (-33% decrease)
- 41 commits in the past quarter (41% increase)
- 9 PRs opened on GitHub, past quarter (-52% decrease)
- 12 PRs closed on GitHub, past quarter (no change)
-----------------------------------------
Attachment V: Report from the Apache Groovy Project [Paul King]
## Description:
Apache Groovy is responsible for the evolution and maintenance of the Groovy
programming language. Groovy is a multi-faceted JVM programming language.
## Issues:
No issues requiring board attention at this time.
## Membership Data:
Apache Groovy was founded 2015-11-18 (4 years ago).
There are currently 18 committers and 10 PMC members in this project.
Community changes, past quarter:
- No new PMC members. Last addition was Daniel Sun on 2019-05-06.
- Eric Milles was added as committer on 2019-08-21
## Project Activity:
Recent releases:
- 3.0.0-rc-1 was released on 2019-10-25.
- 2.5.8 was released on 2019-08-07.
- 3.0.0-beta-3 was released on 2019-08-07.
Downloads for the quarter: over 58 million
## Community Health:
Last quarter stats:
- 88/86 PRs opened/closed on GitHub.
- 88/95 issues opened/closed in JIRA.
Master/all branch commits:
- 237/551 commits were contributed from 12/13 contributors
including 7 non-committer contributors (6 new).
Apache Groovy continues to rank well on the TIOBE index being
11th most popular language for September and October.
-----------------------------------------
Attachment W: Report from the Apache Hama Project [Chia-Hung Lin]
-----------------------------------------
Attachment X: Report from the Apache HTTP Server Project [Daniel Gruno]
## Description:
The Apache HTTP Server Project is an effort to develop and maintain an
open-source HTTP server for modern operating systems including UNIX and
Windows. The goal of this project is to provide a secure, efficient and
extensible server that provides HTTP services in sync with the current HTTP
standards.
The Apache HTTP Server ("httpd") was launched in 1995 and it has been the most
popular web server on the Internet since April 1996. It is celebrating its
25th birthday as a project in February 2020.
## Issues:
There are currently no issues for the board.
## Membership Data:
Apache HTTP Server was founded 1995-02-27 (25 years ago) There are currently
122 committers and 53 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 Stefan Sperling on 2019-01-24.
- No new committers. Last addition was Sebb on 2018-07-14.
## Project Activity:
- There were no new releases since the last report. Last release was 2.4.41 on
2019-08-14.
- Discussions have kicked off about the next httpd (2.6 or 3.0)[1], and while
still not at the end of the discussion (which is of course going to take
time), there is traction towards getting this done, with most of the current
discussions hovering around the more technical aspects of how to create the
split/fork from trunk.
- Another hot topic is integration testing on docker and/or travis[2], with
Luca Toscano and Joe Orton generally being on point for this and handling it
well, with the usual hiccups that happen when you try new approaches. A
proof-of-concept build is already working[0], and I am confident we'll get
this further set up and running smoothly within the month.
- The discussion surrounding migrating from subversion to git seems to have
stalled a bit[3]. That is not in itself a bad thing, rather I see it as
indicative that the inherent benefits are not viewed by the larger populace
of the PMC as a must, but rather something that comes second to the larger
discussion about the next version of httpd. Priorities :)
- A sizeable httpd crowd was present at both ApacheCon North America and
ApacheCon Europe, giving presentations and participating in press events.
- Other topics of heavy interest this quarter were, among others: SSL/TLS
protocol inheritance and defaults[4] (based on users@ inquiries[5]), HTTP/3
specs and adoption thoughts[6], as well as subjects on race conditions in
cleanups and maintainer mode builds.
(with httpd chiefly written in C, I thought I'd start the footnotes at index 0)
[0] https://travis-ci.org/apache/httpd
[1] https://s.apache.org/hyn24 : Time for httpd 2.6.x?
[2] https://s.apache.org/jinvq : Integration tests on docker
[3] https://s.apache.org/vivhy : Migrate to git?
[4] https://s.apache.org/gykrv : Opt in(/out?) for TLS protocol per vhost
[5] https://s.apache.org/bpioq : [..]possible to have in Apache 2.4[..]
[6] https://s.apache.org/jdgt3 : [..]Google Chrome, and Firefox Add HTTP/3[..]
## Community Health:
While the commit rate has dropped slightly this quarter, owing to a very busy
end of the previous quarter, the development process has actually picked up
steam, with a significant (+120%) increase in traffic to the dev list. As laid
out in the above paragraph, much of the discussion and work has been done
around improving continuous integration and unit testing, as well as the
2.6/3.0 discussions and standards and defaults going forward.
Our users list has also seen a significant (+30%) increase in traffic, which
is a nice thing to see. Questions and suggestions from our user-base are
actively being turned into improvements in our software.
There is ample oversight on the PMC (I counted at least 12 PMC members
actively participating in discussions this past quarter) and a good, diverse
distribution of active developers in both the code and documentation
department (in fact, a lot of documentation work has been done in the past
quarter, rocketing docs commits up by 420%). We saw a slightly increase (+2)
in the diversity of committers actively pushing code/docs this quarter.
-----------------------------------------
Attachment Y: Report from the Apache HttpComponents Project [Asankha Chamath Perera]
## Description:
The mission of HttpComponents is the creation and maintenance of software
related to Java toolset of low level HTTP components
## Issues:
- There are no issues requiring board attention at this time.
- There is a steady stream of small contributions in the projects in the form
of pull requests at Github but so far there is no one meriting a
consideration for project committership.
## Membership Data:
Apache HttpComponents was founded 2007-11-14 (12 years ago)
There are currently 19 committers and 10 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:3.
Community changes, past quarter:
- Ryan Schmitt was added to the PMC on 2019-08-28
- No new committers. Last addition was Ryan Schmitt on 2018-11-13.
## Project Activity:
We are preparing to release GA version 5.0 of our core and client component
libraries which would mark a formal completion of a 4 year long development
cycle. We are about start a discussion about directions and the scope of
future development efforts.
## Community Health:
- The project remains low-profile but overall healthy.
- We are seeing more and more project related questions posted to StackOverflow
rater than our user list.
- There is a decrease in the number of emails on the dev and users lists
as well as some drop in the number of PRs. We expect the overall activity to
pick up once 5.0 GA versions have been released.
-----------------------------------------
Attachment Z: Report from the Apache Ignite Project [Denis A. Magda]
## Description:
Apache Ignite is a memory-centric distributed database, caching, and processing
platform for transactional, analytical, and streaming workloads delivering
in-memory speeds at petabyte scale.
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache Ignite was founded 2015-08-18 (4 years ago)
There are currently 48 committers and 29 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 Ilya Kasnacheev on 2019-08-05.
- Maxim Muzafarov was added as committer on 2019-08-27
The community nominated Dmitry Pavlov as the next Ignite PMC Chair and waits
for the board approval.
## Project Activity:
- 2.7.5 was released on 2019-06-04
- 2.8 is in development and should be released in the next few months. This
release incorporates a lot of improvements that were added to the project
thoughout the last year.
## Community Health:
Both user and dev communities are active with a constant traffic increase and
bigger interest in the technology. Several new contributors joined the community
and experienced community members have been mentoring them to help with
contributions.
-----------------------------------------
Attachment AA: Report from the Apache Impala Project [Jim Apple]
## Description:
Apache Impala is a high-performance distributed SQL engine.
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache Impala was founded 2017-11-14 (2 years ago)
There are currently 50 committers and 32 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 Fredy Wijaya on 2019-07-27.
- No new committers. Last addition was Laszlo Gaal on 2019-06-19.
## Project Activity:
Notable activity in the last quarter includes:
- Version 3.3.0 was released on August 22
- A number of correctness and functional-parity fixes for
transactional tables and their tests. Transactional tables are
relatively new in Impala
- A number of minor improvements to the webui
- Improves memory estimation for clusters with dedicated coordinators
(i.e. nodes that are not acting as executors)
- Continued support for the new catalog version in the pre-merge
tests
- A JSON formatting of the query profile. For years, the query
profile has been unstable, in that the developers reserved the
right to change it or its formatting at any time. This is a first
step in the direction of stability, which could increase usability
and allow tooling built on top of the profile to be more reliable.
- Support for .DEFLATE text data files in tables
- By default, limits SQL statements to 16 million characters or fewer
- A variety of improvements to compatibility with other Apache
projects, including Knox, Tez, Derby, Kudu, Ranger, and Hive
- The publication of CVE-2019-10084
- Support for cookie-based authentication
- Numerous improvements to the end-stages of query lifespans,
including some enhancements in resource deallocation
- A large number of commits about spooling, which had zero presence
in the commit log before July of 2019
- Some support for ZORDER
- The addition of DATE support for Avro files; the removal of DATE
support for the year 0
- Support for distributable impala-shell. It can be installed
from pypi
## Community Health:
While the number of commits labeled a "fix" has held steady over the
last three quarters at 58, 54, and 59, this last quarter the number of
non-"fix" commits dropped to 196 from 252 and 247 the previous
quarters. Impala has not had this few commits (of any flavor) in an
August-September-October timeframe before (although the repository
contains an anomaly in which almost all pre-2014 commits landed in a
single moment in January 2014).
Overall activity is a mixed bag, but mostly down, with a decrease in
email traffic, JIRA activity, and number of distinct patch authors, in
addition to the commit number mentioned above. Furthermore, there is
usually a lull in activity during our November-December-January
reporting quarter due to US holidays.
While this is a slowdown, development activity is still high in the
context of open-source projects, with dozens of patch authors and
activity on hundreds of JIRAs.
-----------------------------------------
Attachment AB: Report from the Apache Incubator Project [Justin Mclean]
# Incubator PMC report for November 2019
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/November2019
There are presently 48 podlings incubating. In October, podlings executed
13 distinct releases. We added one new IPMC members and no IPMC members
retired. There were 5 IP clearances. There were some discussions about the
IP clearance process.
We have two new podlings this month Apisix and TubeMQ. StreamPipes will
soon to be added. Other project Sparklyr was discussed but decided not to
enter incubation due to a large number of GPL licensed dependencies it had.
SINGA graduated last month. The Amaterasu project was retired after the
PPMC failed to respond to queries about its status. Edgent also retired.
Omid and Tephra have decided to "graduate" and become sub-projects of the
Phoenix project. A couple of podlings are heading towards graduation in the
next few months.
BatchEE has now failed to report twice in a row. Looking at the low
activity in the project, it may be time to considering retirement.
It seem there was an attempt to transfer the project to Geronimo but
It's unknown if that was completed. All other projects reported.
Graduation of Weex was discussed but was withdrawn after the project
realised it needed to do some more work around branding and community
growth.
Further ongoing work was done on cleaning up the incubator web site, but
there are still a number of pages that need to be reviewed and updated.
Podlings have continued to use the new disclaimer policy, and this has
reduced the friction in making releases. Extra votes from the wider IPMC
community are needed to get the 3 +1 votes, with not all mentors voting on
releases.
A new straight to top level project has been proposed called Petri as
another way of educating external projects and the Apache Way with the
option of them bypassing the Incubator and going straight to being a top
level project. It's still under consideration by the board. A FAQ is being
worked on, but it currently unknown what impact this might have on the
Incubator in the short or long term.
At ApacheCon Europe there was a Podling's Shark Tank, a talk on incubating
process and talks involving several incubating projects.
The podling reporting groups have been rearranged so that there is an
evener distribution of projects reporting each month.
A couple of mentors were added and removed from projects.
## Community
### New IPMC members:
- Evans Ye
### People who left the IPMC:
- None
## New Podlings
- Apisix
- TubeMQ
## Podlings that failed to report, expected next month
- BatchEE
## Graduations
- SINGA
The board has motions for the following:
- None
## Releases
The following releases entered distribution during the month of
October:
- Datasketches hive 1.0.0
- Datasketches java 1.1.0
- Datasketches pig 1.0.0
- Datasketches postgresql 1.3.0
- Doris 0.11.0
- ECharts 4.4.0
- Hudi 0.5.0
- Iceberg 0.7.0
- IoTdb 0.8.1
- Milagro dta 0.1.0
- Superset 0.34.1
- Tuweni 0.9.0
- Weex 0.28.0
## IP Clearance
- ServiceComb toolkit contribution
- ServiceComb osa-validator
- python-dubbo
- NetBeans - dukescript presenters
- Weex Loader
## Legal / Trademarks
- N/A
## Infrastructure
- N/A
|----------------------------------------------------------------------
Table of Contents
[Annotator](#Annotator)
[APISIX](#APISIX)
[DataSketches](#DataSketches)
[DolphinScheduler](#DolphinScheduler)
[Doris](#Doris)
[ECharts](#ECharts)
[Heron](#Heron)
[PageSpeed](#PageSpeed)
[Pinot](#Pinot)
[Ratis](#Ratis)
[S2Graph](#S2Graph)
[SDAP](#SDAP)
[Tamaya](#Tamaya)
[Toree](#Toree)
[Training](#Training)
[Tuweni](#Tuweni)
|----------------------------------------------------------------------
--------------------
## Annotator
Annotator provides annotation enabling code for browsers, servers, and
humans.
Annotator has been incubating since 2016-08-30.
### Three most important unfinished issues to address before graduating:
1. Release initial versions (should happen this week!)
2. Increase activity from current committers and community.
3. Demonstrate good governance through voting and learning the Incubator
process (some more).
### Are there any issues that the IPMC or ASF Board need to be aware of?
None at this time.
### How has the community developed since the last report?
Community activity was quiet. However, code is underway for a first
release to be ready in the coming week(s) which we hope will increase
interest and activity.
### How has the project developed since the last report?
Code for a first release is hoped to be available in the coming days with
more community members participating in review and critique.
Additionally, work in the W3C's ARIA (accessibility) Working Group and on
various browser vendor repositories has highlighted new annotation related
activity and opportunity for this project. Sadly, we've mostly failed at
raising awareness on the list, so the communities "radar" looks quieter
than it should...
### 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:
None yet, but we hope to release before the end of November 2019.
### When were the last committers or PPMC members elected?
No new committers nor PPMC members have been added since the last report.
### Have your mentors been helpful and responsive?
No check-ins with/from/by mentors in the last 4 months, but we should do
one over email within this next quarter.
### Signed-off-by:
- [X] (annotator) Nick Kew
Comments:
- [ ] (annotator) Steve Blackmon
Comments:
- [X] (annotator) Tommaso Teofili
Comments:
### IPMC/Shepherd notes:
Justin Mclean: Please provide the dates that you last voted in committers
and PPMC members even ion this hasn't happen in the last reporting period.
The project has been 3 years in incubator why has it taken so long to
made a release? Can we expect faster progress in the future?
--------------------
## 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. Make an Apache release
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?
- Learning Apache way and its value behind rules, working in Apache way.
- Our Apache website is constructed.
- We have 12 committers and 35 contributors (including 12 committers)
contributing to Apache APISIX.
- Over 13 company users have announced that they are using APISIX and
more than 50% of them also submitted code or fixed the documentation for
APISIX : https://github.com/apache/incubator-apisix/issues/487
### How has the project developed since the last report?
The project has been quite health, with ~50 pull requests being merged in
October. These pull requests are authored by a diverse set of
contributors(~30 authors last month).
Some highlights of recent developments:
- APISIX support etcd V3.
- Supported cluster limit-req and limit-conn.
We are planning to have a 0.9.0 release in November.
### 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:
None
### When were the last committers or PPMC members elected?
No new committers nor PPMC members have been added.
### Have your mentors been helpful and responsive?
Mentors are responsive and helpful. Things tend to be on the right way.
### Signed-off-by:
- [X] (APISIX) Willem Ning Jiang
Comments: APISIX is growing well and I'm quite impressed.
- [X] (APISIX) Justin Mclean
Comments:
Off to a good start.
- [x] (APISIX) Kevin Ratnasekera
Comments:
- [ ] (APISIX) Von Gosling
Comments:
### IPMC/Shepherd notes:
--------------------
## DataSketches
DataSketches is an open source, high-performance library of stochastic
streaming algorithms commonly called "sketches" in the data sciences.
Sketches are small, stateful programs that process massive data as a stream
and can provide approximate answers, with mathematical guarantees, to
computationally difficult queries orders-of-magnitude faster than
traditional, exact methods.
DataSketches has been incubating since 2019-03-30.
### Three most important unfinished issues to address before graduating:
1. Finish the transfer and bring-up of our website to
github.com/apache/... This is now in process.
2. __Team Interactions:__ We want to have our exchanges on the ASF
Slack DataSketches-dev channel posted to our dev@datasketches.a.o
list on a daily basis for improved visibility and searchability.
We have an open INFRA ticket on this issue.
We are searching for a solution to provide more open access to
our video conference sessions when we have them. We are in the
process of moving more of our interactions into the slack
DS-dev channel and dev@ list. This is a culture change for us
and will take some getting used to. We clearly want open
access to our team discussions.
3. We would like to see a few more folks
join our contributors list. We have several folks that
have come forward and offered help because they are interested
in the project. This is great. It is our hope that they will
grow into active contributors.
### 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 have added 1 new Mentor, Dave Fisher (thank you!) to our project
and we have been approached by another Apache member
who would also like to be a mentor, and eventually a contributor
as well. This is very positive!
### How has the project developed since the last report?
* We have now managed 7 releases, 6 Java releases and 1 C++ release.
We have one more C++ release pending. These are across 6 different
components of the DataSketches library. With the last pending C++
release, all of the code components targeted for release will
be complete.
### 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-10-19 01:55 GMT DataSketches-pig
### When were the last committers or PPMC members elected?
* Dave Fisher: 16 Sep 2019
### Have your mentors been helpful and responsive?
* Helpful and responsive, Yes.
Having additional mentors has helped the voting
move forward more expeditiously!
* I want to thank Dave Fisher for jumping in and helping us
with a number of issues!
### Signed-off-by:
- [X] (datasketches) Liang Chen
Comments:
- [x] (datasketches) Kenneth Knowles
Comments:
- [X] (datasketches) Furkan Kamaci
Comments:
- [X] (datasketches) Dave Fisher
Comments:
### IPMC/Shepherd notes:
--------------------
## Dolphin Scheduler
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 progress)
2. Fix the content of official website about Non-ASF release and notice.
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 besides 8 PPMC members who
contributes codes to github.
2. We held a offline Meetup in Shanghai. 5 Speakers (including 4 PPMC
member and 1 user) gave their presentation. 30 people came and 10
people online watch the meetup.
3. Github star grew from 2291 to 2648 in October.
4. Over 61 company users is willing to announce that he is using Dolphin
Scheduler:
<https://github.com/apache/incubator-dolphinscheduler/issues/57>
#### How has the project developed since the last report?
1. Solid Apache verson plan is created and we planed to start a Apahce
release in November.
2. Some new important feature developerd by contributor was merge to
project(Docker file, S3 support, Flink job support, job import/export,
etc.)
3. 178 issues created，181 PRs merged (from #932 to #1113) .
4. Developers and Contributors are steadily developing the project
<https://github.com/apache/incubator-dolphinscheduler/issues/690
### 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:
None.
### When were the last committers or PPMC members elected?
2019-8-29
### Have your mentors been helpful and responsive?
Yes, our mentors noticed some issue of DolphinScheduler and give useful
advice to PPMC especially on first Apache version. I want to thank
Wusheng for many good advice for community operation and Apache first
release.
### Signed-off-by:
- [x] (dolphinscheduler) Sheng Wu
Comments:
- [x] (dolphinscheduler) ShaoFeng Shi
Comments: LGTM
- [X] (dolphinscheduler) Liang Chen
Comments:
- [X] (dolphinscheduler) Furkan KAMACI
Comments:
- [X] (dolphinscheduler) Kevin Ratnasekera
Comments:
### IPMC/Shepherd notes:
Dave Fisher: A good start. Please listen about labeling of non-Apache
Releases.
I'd like to see discussion on email threads on dev@ in addition to
announcements.
Listen to Sheng Wu regarding the branding of Events.
--------------------
## Doris
Doris is a MPP-based interactive SQL data warehousing for reporting and
analysis.
Doris has been incubating since 2018-07-18.
### Three most important unfinished issues to address before graduating:
1. Continue to build our community. It is glad to see that more
developers joined us and became contributors. But we still need more
leading developers to join the community who can participate in the
discussion of Doris' road map, not just start-up members.
2. Improve the documents and website as well. Currently, most of
documents are in Chinese and most of English docs are translated by
machine. We are working on it.
3. The discussion on dev mail list is still very few. Most of discussion
and decisions are still make in private or in GitHub issues. We should
improve the utilization of mailing lists and discuss more public.
### 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 we have 58 contributors, 1 more committers, and 1 committer became
PPMC member.
2. 3 more other companies are cooperating with us on developing Doris and
try to make Doris as part of their data infrastructure.
### How has the project developed since the last report?
1. We released one new version: 0.11.0.
2. And the website (http://doris.incubator.apache.org) is built with more
docs, both in Chinese and English version.
### 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-10-29: Apache Doris (incubating) 0.11.0
### When were the last committers or PPMC members elected?
Ling Miao: New Committer 2019-08-28
Kaisen Kang: New PPMC 2019-09-20
### Have your mentors been helpful and responsive?
Dave Fisher helped us a lot, such as Release process, and mail management.
Willem helped us to build english website, nominate new committer and
PPMC. All mentors helped us to verify our release.
### Signed-off-by:
- [X] (doris) Dave Fisher
Comments: Having discussions on dev@ is a critical improvement. Focus
on that for the next three months.
- [X] (doris) Willem Ning Jiang
Comments: We still need to improve the public discussion.
- [ ] (doris) Shao Feng Shi
Comments:
### IPMC/Shepherd notes:
Justin Mclean: It would seem you could solve the first issue listed in
the three issues before graduation, by working on the other 2 issues
listed?
--------------------
## ECharts
ECharts is a charting and data visualization library written in JavaScript.
ECharts has been incubating since 2018-01-18.
### Three most important unfinished issues to address before graduating:
1. Solve CDN issue and redirect echarts.baidu.com to echarts.apache.org.
2. Vote for more PPMC and bring diversity to it.
3. Check tutorials and other documents to make sure users can find what
they need, and the information is up-to-date. Keep the content of Chinese
version and English version to be the same.
### Are there any issues that the IPMC or ASF Board need to be aware of?
We are still working on the Website speed problem before we can transfer
it to Apache server.
We are trying the CDN as suggested by Dave and York Shen. It may take
several days before we can get conclusion. If this works, we will ask the
infra for help with this CDN, if not, we should find other solutions.
Currently, we put a banner stating "Apache ECharts is an effort
undergoing incubation at The Apache Software Foundation (ASF), sponsored
by the Apache Incubator.We are working on redirecting this Website to
https://echarts.apache.org. You may visit our new official Website now.".
Hopefully, this can help with the branding before we do the redirection.
### How has the community developed since the last report?
1. We got more contributors from the community. Last month alone, there
are more than 10 non-committer contributors whose pull requests were merged
in incubator-echarts project or doc project.
2. The mailing list has been much more active these months. We are
publicly discussing issues,monthly release plans, future plans and so on.
And more people asked for help and have their problem solved from the
mailing list.
3. We are using social medias like YouTube, Twitter and Medium to help
promote our project internationally and grow the community.
4. We used labels to state the difficulty of fixing to make it easier for
contributors to find bugs that are supposed to be fixed by beginners.
### How has the project developed since the last report?
We have released 2 versions since the last report and we are working on
the vote of the third one these days. We have formed a monthly release
procedure and made the process public.
We made an automatic visual test framework, so that the testing job can
be made more easily and more bugs can be found during pull request or
testing stage before release.
### 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-10-15
### When were the last committers or PPMC members elected?
2019-10-16
### Have your mentors been helpful and responsive?
Yes. They helped us a lot on the Website and suggestion of how to grow
our community.
### Signed-off-by:
- [X] (echarts) Kevin A. McGrail
Comments: Continuing to make good and stready progress!
- [X] (echarts) Dave Fisher
Comments: Making progress. Looking forward to the resolution of the
CDN issues.
- [ ] (echarts) Ted Liu
Comments:
- [x] (echarts) Sheng Wu
Comments: Project PPMC has made a good progress toward the Apache
way. Look forward you could make the community more active
and diversity.
### IPMC/Shepherd notes:
--------------------
## Heron
A real-time, distributed, fault-tolerant stream processing engine.
Heron has been incubating since 2017-06-23.
### Three most important unfinished issues to address before graduating:
1. Fixing issues with licensing in the repo. [mostly done]
2. Making several Releases. [two src only releases so far]
3. Updating the heron documentation site [mostly done]
### Are there any issues that the IPMC or ASF Board need to be aware of?
* n/a
### How has the community developed since the last report?
* The community is gradually growing.
* Community support is growing in conversations via email and slack.
* Monthly meetups have been regularly and successfully organized.
* We are working to increasing activity in the Apache mailing lists.
### How has the project developed since the last report?
There have been bug fixes and feature improvements. Some to note are:
* Documentation updates
* License fixes
* Two phase commit support
* UI improvements
* Optimization
* New improvement proposals
### 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-10-31 0.20.2-incubating-rc1.
* The release has been created in the repo.
* New committers are learning the process as they work through this
release.
* It is currently in flight still a new release vote has not been sent
out as of 2019/11/04
### When were the last committers or PPMC members elected?
* Two new committers (Xiaoyao Qian, Siming Weng) were elected and invited
on Oct 18th, 2019.
No new PPMC members were elected.
### Have your mentors been helpful and responsive?
* Yes, we have got some suggestions from mentors. They have been helpful
and responsive.
### Signed-off-by:
- [ ] (heron) Jake Farrell
Comments:
- [ ] (heron) Julien Le Dem
Comments:
- [ ] (heron) P. Taylor Goetz
Comments:
- [X] (heron) Dave Fisher
Comments: Voting on New PPMC members and committers is nearly
complete.
### 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. Currently the CI system is managed using drone, an open-sourced
CI infrastructure. It requires R+W access to the Github organization to
set up the webhooks. However, the INFRA team does not grant W access to
3rd party infrastructure. Should we migrate to Github Action, or try to
get a way to keep using drone? We started a discussion in dev mailing
list, but the answer from mentor differs from the answer from INFRA team.
The bootstrapping process seems slow due to the above problem. If we
cannot find a way to properly set up the CI system, we cannot merge any
codes after the repo transfer completed. To this end, we are doing our
best on fitting into Github Action.
Lack of communication in dev mailing list. We, the PPMC members, realized
that we cannot only talk offline. So we are starting to use the dev
mailing list for discussion and issue tracking, and we received lots of
comments and feedbacks from mentors. Next time I think we will do better
on the collaboration and be more interactive with the lovely mentors.
Since Baidu does not donate the brand name "MesaTEE" to ASF, we need a
new brand name. To solve this, PODLINGNAMESEARCH issue 169 is initiated
one month ago. And recently the discussion on new name seems come to an
conclusion in dev mailing list. The next step is to do the rename as
discussed.
### How has the community developed since the last report?
Now we have 12 contributors for MesaTEE main repo, and 16 contributors
for MesaTEE-SGX. Since the first day of incubation, MesaTEE merged 3 PRs
from the community, and MesaTEE-SGX merged 7 PRs from the community.
### How has the project developed since the last report?
Since the MesaTEE project joined incubator, we improved its build system,
SDK, CLI, and fit it to the latest Intel SGX SDK v2.6. MesaTEE-SGX and
its ecosystem has been periodically updated so as to eliminate
bugs/vulnerabilities from 3rd party libraries.
We just finished repo transfer for MesaTEE-SGX, and we are still working
on repo transfer for MesaTEE main repo.
It is worth mention that the comprehensive tests of MesaTEE and
MesaTEE-SGX helped finding bugs in their dependencies, and we managed to fix
them in upstream libraries. One case is the "official" numeric library family
of Rust ecosystem: rust-num. It's build script did not work well with
MesaTEE's build system and we filed [num-traits issue
139](https://github.com/rust-num/num-traits/issues/139). Then we fixed in
[PR 140](https://github.com/rust-num/num-traits/pull/140). More fixes in
this family are pending to merge. Another case is in the official Intel
SGX SDK. MesaTEE-SGX's CI reported failure after migrating to Intel SGX SDK
v2.7 release. We created [linux-sgx issue
457](https://github.com/intel/linux-sgx/issues/457) and Intel resolved it
a week later in [PR 461](https://github.com/intel/linux-sgx/pull/461).
### 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?
Luciano helped us a lot. He helped with catching up the schedule and the
SGA. We learned a lot from him and started managing MesaTEE in Apache's
style.
Zhijie Shen helped us a lot with the initial setup, such as signing the
iCLA, account creation, mailing lists.
Justin Mclean helped us a lot on this report. We received a lot of
feedbacks from him and we updated this report according to these
comments. These comments are really helpful and make us realize how to
work in the Apache way. Thanks Justin!
We appreciate the help from the mentor group. Mentors are really
professional and helpful!
### Signed-off-by:
- [x] (MesaTEE) Felix Cheung
Comments:
- [X] (MesaTEE) Furkan Kamaci
Comments:
- [ ] (MesaTEE) Jianyong Dai
Comments:
- [x] (MesaTEE) Luciano Resende
Comments: For the rename, I would recommend only performing the rename
after a namesearch is completed. Please close the old one, and create a
new one for the new name.
- [x] (MesaTEE) Matt Sicker
Comments: Slow start, but renaming is being done early on to minimize
problems.
- [ ] (MesaTEE) Zhijie Shen
Comments:
### IPMC/Shepherd notes:
--------------------
## PageSpeed
PageSpeed represents a series of open source technologies to
help make the web faster by rewriting web pages to reduce
latency and bandwidth.
PageSpeed has been incubating since 2017-09-30.
### Three most important unfinished issues to address before graduating:
1. Produce first release
2. Grow the number of active developers
3.
### Are there any issues that the IPMC or ASF Board need to be aware of?
We need more IPMC votes on a proposed release candidate which has passed our
own PMC review.
### How has the community developed since the last report?
User-activity is healthy as always. Developer activity is still limited
to the original contributor group, plus recently a new committer (lofesa@).
### How has the project developed since the last report?
- There is a release staged in review with some good fixes & features.
- Work on modernizing the project's build system has progressed well.
- Also, there is a PoC for running PageSpeed via Envoy, which opens a great
path towards materializing a 2.0 version.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [X] Working towards first release
- [X] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
None.
### When were the last committers or PPMC members elected?
May 27 2019 (Longinos Ferrando, elected as both committer and PMC member)
### Have your mentors been helpful and responsive?
No answer.
### Signed-off-by:
- [ ] (pagespeed) Jukka Zitting
Comments:
- [ ] (pagespeed) Leif Hedstrom
Comments:
- [X] (pagespeed) Nick Kew
Comments:
- [ ] (pagespeed) Phil Sorber
Comments:
### IPMC/Shepherd notes:
Justin Mclean: I think you may have a misunderstanding about the release
process, you need to post to general to get IPMC votes on releases.
--------------------
## Pinot
Pinot is a distributed columnar storage engine that can ingest data in real-
time and serve analytical queries at low latency.
Pinot has been incubating since 2018-10-17.
### Three most important unfinished issues to address before graduating:
1. Streamline Pinot releases (currently blocked due to helix bugs)
2. More commits from wider community
### 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?
Multiple design and code checkins from the community:
1. Parquet/ORC support for ingestion
2. Better integration with Kubernetes
3. (In progress) Null value support
4. Other contributions
- https://github.com/apache/incubator-pinot/pull/4770
- https://github.com/apache/incubator-pinot/pull/4615
- https://github.com/apache/incubator-pinot/pull/4750
- https://github.com/apache/incubator-pinot/pull/4571
- https://github.com/apache/incubator-pinot/pull/4293
- https://github.com/apache/incubator-pinot/pull/4020
- https://github.com/apache/incubator-pinot/pull/3977
### How has the project developed since the last report?
1. Significant progress in SQL support (distinct, order by)
2. Completed design of schema updates, implementation starting
3. Progress in design of realtime segment completion, some implementation
### 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:
2019-02-15
### When were the last committers or PPMC members elected?
No answer.
### Have your mentors been helpful and responsive?
No answer.
### Signed-off-by:
- [ ] (pinot) Kishore Gopalakrishna
Comments:
- [X] (pinot) Jim Jagielski
Comments:
- [ ] (pinot) Roman Shaposhnik
Comments:
- [X] (pinot) Olivier Lamy
Comments:
- [X] (pinot) Felix Cheung
Comments: good progress.. how can we grow more committers? also dev@
traffic is very light - only 9 threads in the last 3 months.
### IPMC/Shepherd notes:
Dave Fisher - I see the start of a VOTE for a committer on private@
There has been no response from other PPMC members. That is disappointing.
This could be because most of the PPMC members are not subscribed to
private@. This includes one of the Mentors who signed off on the report.
Justin Mclean: The items listed under community development seem more
about project development. How has the community developed?
I'd also like to see answer to all questions, it make it hard to
judge process and for us to help if information is not supplied.
--------------------
## Ratis
Ratis is a java implementation for RAFT consensus protocol
Ratis has been incubating since 2017-01-03.
### Three most important unfinished issues to address before graduating:
1. Podling name search.
2. Complete graduation template
3. Expand PPMC members
### 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?
- 4 new contributors. 65 contributors in total.
- 1 new committer
- 1 new PPMC members
- Total 22 committers and PPMC members.
### How has the project developed since the last report?
60 commits. Version 0.4.0 released.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [X] Initial setup
- [X] Working towards first release
- [X] Community building
- [X] Nearing graduation
- [ ] Other:
### Date of last release:
2019-09-19
### When were the last committers or PPMC members elected?
- 09/11/2019 - Ankit Singhal as Committer
- 09/13/2019 - Shashikant Banerjee as PPMC member
### Have your mentors been helpful and responsive?
No answer.
### Signed-off-by:
- [ ] (ratis) Jakob Homan
Comments:
- [X] (ratis) Uma Maheswara Rao G
Comments:
- [ ] (ratis) Devaraj Das
Comments:
### IPMC/Shepherd notes:
--------------------
## S2Graph
S2Graph is a distributed and scalable OLTP graph database built on Apache
HBase to support fast traversal of extremely large graphs.
S2Graph has been incubating since 2015-11-29.
### Three most important unfinished issues to address before graduating:
1. Make the third release.
2. Attract more users and contributors.
3. Build the developer community in both size and diversity.
### 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?
* Not much activities.
* There was a meetup with active committers and a mentor to discuss how
to grow the community. Summary in @dev list: [1]
https://lists.apache.org/thread.html/39e014ba2f345557dbc3351a62a158b9c20a10155f356308a70e6a3d@%3Cdev.s2graph.apache.org%3E
### How has the project developed since the last report?
* No issues has been resolved.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [ ] Working towards first release
- [X] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
2017-08-26
### When were the last committers or PPMC members elected?
2019-02-05
### Have your mentors been helpful and responsive?
* Our mentor is very helpful and responsive.
### Signed-off-by:
- [ ] (s2graph) Sergio Fernández
Comments:
- [X] (s2graph) Woonsan Ko
Comments: In my visit in Seoul, I met the three active committers -
Daewon, Do Yung and
Hwansung - over lunch, chatting informally face-to-face for the first time
about how to grow our community. There has not been much project /
community activity for last 1 year, but they were passionate to stay in the
community and started reorganizing their work/time, trying to improve
developer's experience and accessibility, considering to support Java
Client or even Spring Boot for new people, by which they believe they can
help grow the community. There's no specific decision made yet but we
agreed to continue discussion in the mailinglist. It was great for me as a
mentor too to understand each other. See [1] for detail.
### IPMC/Shepherd notes:
--------------------
## SDAP
SDAP is an integrated data analytic center for Big Science problems.
SDAP has been incubating since 2017-10-22.
### Three most important unfinished issues to address before graduating:
1. Make official SDAP (Incubating) Release
2. Improve/create user guide documentation
3. Improve committer participation
### 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?
Interest in the project has increased after presentation at ApacheCon.
New `#sdap` channel created on the-asf.slack.com
### How has the project developed since the last report?
Frank Greguska attended ApacheCon NA and presented an overview of SDAP.
Discussion about what is necessary to produce a release were beneficial
and the path forward is clear. Goal is to get a source release before the
end of the year.
### How would you assess the podling's maturity?
There are several deployments of SDAP actively being used and interest is
high. However, active participation from project members is low. First
source release should be coming soon.
Please feel free to add your own commentary.
- [x] Initial setup
- [x] Working towards first release
- [x] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
XXXX-XX-XX
### When were the last committers or PPMC members elected?
Maya Debellis was elected as a committer on 2019-02-08
### Have your mentors been helpful and responsive?
Yes, Trevor has been helpful and responsive. Have not heard from Jörn
recently.
### Signed-off-by:
- [ ] (sdap) Jörn Rottmann
Comments:
- [x] (sdap) Trevor Grant
Comments:
### IPMC/Shepherd notes:
--------------------
## Tamaya
Tamaya is a highly flexible configuration solution based on an modular,
extensible and injectable key/value based design, which should provide a
minimal but extendible modern and functional API leveraging SE, ME and EE
environments.
Tamaya has been incubating since 2014-11-14.
### Three most important unfinished issues to address before graduating:
1. Finish getting our release candidate out.
2. Grow the PPMC from the existing community.
3. Blog and publish more about Tamaya.
### Are there any issues that the IPMC or ASF Board need to be aware of?
Release candidate vote is still pending (2 more +1 votes are needed to
get the RC out).
### How has the community developed since the last report?
No changes, Julian helped out as a new mentor.
### How has the project developed since the last report?
Started forging a new release, had 5 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
- [X] Nearing graduation
- [ ] Other:
### Date of last release:
2017-05-28 0.3-incubating
### When were the last committers or PPMC members elected?
* 2018-12: Aaron Coburn
* 2018-12: William Lieurance
### Have your mentors been helpful and responsive?
New mentor Julian is very helpful as he is present to help out and guide.
### Signed-off-by:
- [ ] (tamaya) John D. Ament
Comments:
- [ ] (tamaya) David Blevins
Comments:
- [ ] (tamaya) Kanchana Pradeepika Welagedara
Comments:
- [x] (tamaya) Julian Feinauer
Comments:
### IPMC/Shepherd notes:
Justin Mclean: I can see the RC vote issues has been resolved. Sometimes
a little patience is needed to get votes on releases. Be sure to ping
your mentors first and make sure they vote.
--------------------
## Toree
Toree provides applications with a mechanism to interactively and remotely
access Apache Spark.
Toree has been incubating since 2015-12-02.
### Three most important unfinished issues to address before graduating:
1.Increase active contributors
2.
3.
### 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?
Toree was presented at ApacheCon Las Vegas with a good set of
users/contrinutors present to the talk. On the community side,
a few contributions coming on around making the current implementation
a little more flexible for concurrent code as well as support for
Spark 2.4 and Scala 2.12.
### How has the project developed since the last report?
Slow, but steady stream of issues and PRs.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [ ] Working towards first release
- [ ] Community building
- [X] Nearing graduation
- [ ] Other:
### Date of last release:
2018-11-13
### When were the last committers or PPMC members elected?
Kevin Bates was added to the PPMC on 2019-08-14
### Have your mentors been helpful and responsive?
There was nothing requiring mentor intervention on the last quarter.
### Signed-off-by:
- [X] (toree) Luciano Resende
Comments:
- [ ] (toree) Julien Le Dem
Comments:
- [X] (toree) Ryan Blue
Comments:
Does the community plan to do another release? It's been nearly a
year since the last. With a "slow, but steady stream of issues and
PRs" I suspect that some of those contributors would like to get a
released version with their contributions. For this community, it
may be a good idea to consider time-based releases to ensure that
contributors get to use their contributions in an official release.
### IPMC/Shepherd notes:
--------------------
## Training
The Training project aims to develop resources which can be used for
training purposes in various media formats, languages and for various Apache
and non-Apache target projects.
Training has been incubating since 2019-02-21.
### Three most important unfinished issues to address before graduating:
1. Promote the information about Apache Training Project with increased
participation from community
2. Take the technology stack to become more user-friendly
3. Scout for more content and ingest it in the project
### Are there any issues that the IPMC or ASF Board need to be aware of?
no critical issues at this point in time
### How has the community developed since the last report?
- The dev mailing list is active. Community is gaining traction with
new contributors getting added to Apache Training project.
- The total number of posts in August 60, September 94, October 174.
In October, some new contributors have started active discussions
on the Training project. There are ongoing discussions to use
Docker, and new kind of review commit model for content contribution.
- We created JIRA contributors group.
### How has the project developed since the last report?
- We added more content to the Training project. E.g. Spark slides,
Apache Ignite intro slides, Github workshop slides, ApacheCon slides
- We also added a GitHub puzzle to Training content.
- We initiated work to Dockerize the tools used in project.
- We started new policy for reviewing content contribution.
- We have delivered our first release during which we ironed out a
few issues.
- The release contains the training slides in Asciidoctor, so that
these can be run as slideshow.
- The release followed the voting process and was made available on
Github for general public.
- There were multiple talks about the Training project at both
ApacheCons this year
### 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-10-04: Apache Training (incubating) - Navigating the ASF
Incubator Process 1.0, Announce https://s.apache.org/9g5fl
It can be viewed online here: https://s.apache.org/t4h7v
### When were the last committers or PPMC members elected?
n.a.
### Have your mentors been helpful and responsive?
Mentors were responsive. Things are not falling through the cracks.
### Signed-off-by:
- [X] (training) Craig Russell
Comments:
- [X] (training) Christofer Dutz
Comments:
- [X] (training) Justin Mclean
Comments:
I'm concerned that lack of activity by the PPMC is resulting in
slower community growth.
- [X] (training) Lars Francke
Comments:
### IPMC/Shepherd notes:
--------------------
## Tuweni
Tuweni is a set of libraries and other tools to aid development of
blockchain and other decentralized software in Java and other JVM languages.
Tuweni has been incubating since 2019-03-25.
### Three most important unfinished issues to address before graduating:
1. Building community
2. Building a roadmap for the next few major releases
3. Perform the last checks for official releases wrt crypto
### 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 have had more contributions from at least one developer.
### How has the project developed since the last report?
We have successfully released 0.9, with a nice participation
of the existing developer community.
### 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-10-16
### When were the last committers or PPMC members elected?
Gordon Martin as committer on 2019-08-01.
### Have your mentors been helpful and responsive?
Yes, very much so, thank you!
### Signed-off-by:
- [X] (tuweni) Jim Jagielski
Comments:
- [ ] (tuweni) Kenneth Knowles
Comments:
- [X] (tuweni) Jean-Baptiste Onofré
Comments: I plan to take a deeper look on code soon, and see
interactions with other communities.
- [X] (tuweni) Michael Wall
Comments: Currently working on growing community.
- [X] (tuweni) Furkan Kamaci
Comments:
### IPMC/Shepherd notes:
-----------------------------------------
Attachment AC: Report from the Apache Joshua Project [Tommaso Teofili]
## Description:
The mission of Apache Joshua is the creation and maintenance of software
related to statistical and other forms of machine translation.
## Issues:
The only issue within the project relates to low activity.
## Membership Data:
Apache Joshua was founded 2018-10-17 (a year ago)
There are currently 10 committers and 10 PMC members in this project.
The Committer-to-PMC ratio is 1:1.
Community changes, past quarter:
- No new PMC members. Last addition was Felix Hieber on 2018-10-17.
- No new committers were added.
## Project Activity:
Project activity is low, however we are planning a minor 6.2 release and
discussing interesting features (language packs for CJK languages) that may
help raise interest and activity from the community
## Community Health:
No new contributors for a while now, main contributors are still around (we
had a roll call in September) but mostly quiet.
-----------------------------------------
Attachment AD: 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.
## Activity:
- jUDDI - last release was 04 DEC 2018. Resolved several requisite bugs for
updating SCOUT.
- 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.
- 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:
- 0 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 (-100% decrease)
- 0 code contributors in the past quarter (-100% decrease)
-----------------------------------------
Attachment AE: Report from the Apache Juneau Project [James Bognar]
## Description:
The mission of Apache Juneau is the creation and maintenance of software
related to a toolkit for marshalling POJOs to a wide variety of content types
using a common framework, and for creating sophisticated self-documenting REST
interfaces and microservices using VERY little code
## Issues:
No issues to report at this time.
## Membership Data:
Apache Juneau was founded 2017-10-17 (3 years ago) There are currently 12
committers and 12 PMC members in this project. The Committer-to-PMC ratio is
1:1.
Community changes, past quarter:
- No new PMC members. Last addition was Ayeshmantha Perera on 2019-01-02.
- No new committers. Last addition was Ayeshmantha Perera on 2019-01-02.
## Project Activity:
Two new versions were released this quarter:
- 8.1.1 was released on 2019-09-20.
- 8.1.0 was released on 2019-08-21.
Currently working with several interested intern candidates through the
Outreachy program.
## Community Health:
Healthy increases in community discussion on our dev channel.
- dev@juneau.apache.org had a 338% increase in traffic in the past quarter
(342 emails compared to 78)
- 33 issues opened in JIRA, past quarter (65% increase)
- 22 issues closed in JIRA, past quarter (no change)
- 4 code contributors in the past quarter (100% increase)
-----------------------------------------
Attachment AF: Report from the Apache Kafka Project [Jun Rao]
Apache Kafka is a distributed event streaming platform for efficiently storing
and processing a large number of records in real time.
Development
===========
We are in the process of preparing 2.4.0 release which includes new features
such as allowing consumers to fetch from closest replica, incremental consumer
rebalance, sticky partitioner for better producer throughput, administrative API
for replica assignment, and MirrorMaker 2.
We released 2.3.1, which fixes more than 40 critical issues.
We accepted KIP-500, a significant effort to remove ZooKeeper dependency in
Kafka for simplified deployment and more scalability.
Community
===========
Lots of activities in the mailing list. We had 2,758 emails in the dev
mailing list, 13% more than the last 3 months. We had 771 emails in the
in the user mailing list, 15% more than the last 3 months. We had 3,350
JIRA activity, 7% more than the last 3 months.
We added two new committers Mickael Maison and John Roesler in November.
We didn't add any new PMC member in the last 3 months. We last added
a new PMC member on Apr. 18, 2019.
Kafka Summit San Francisco occurred on Sep. 30 and Oct. 1, 2019, with more
than 2,100 participants.
Releases
===========
2.3.1 was released on Oct. 24, 2019.
-----------------------------------------
Attachment AG: Report from the Apache Kibble Project [Rich Bowen]
## Description:
The mission of Apache Kibble is the creation and maintenance of software
related to an interactive project activity analyzer and aggregator
## Issues:
We have no issues that require board input or intervention at this time.
## Membership Data:
Apache Kibble was founded 2017-10-17 (2 years ago)
There are currently 12 committers and 12 PMC members in this project.
The Committer-to-PMC ratio is 1:1.
Community changes, past quarter:
- No new PMC members. Last addition was Rafael Weingärtner on 2017-12-08.
- No new committers. Last addition was Rafael Weingärtner on 2017-12-09.
## Project Activity:
We had another very quiet quarter, with the dev list almost entirely silent.
There were only a handful of commits, once again all coming from one person.
It is hoped that we are able to make connections at CHAOSSCon which will
parlay into more active developers.
## Community Health:
Daniel Gruno presented on Kibble at the recent ApacheCon North America in
Las Vegas. https://www.apachecon.com/acna19/s/#/scheduledEvent/1099
Kibble hopes to participate in the upcoming CHAOSSCon at FOSDEM, on Friday,
January 31st in Brussels.
Sharan Foga reports that the Gnome Foundation is interested in using Kibble to
generate statistics on their projects.
The ASF Board Report Wizard, which is powered by Kibble, has seen an uptick in
usage over the past quarter.
-----------------------------------------
Attachment AH: Report from the Apache Knox Project [Larry McCay]
## Description:
The mission of Knox is the creation and maintenance of software related to
Simplify and normalize the deployment and implementation of secure Hadoop
clusters
## Issues:
There are no issues requiring board attention
## Membership Data:
Apache Knox was founded 2014-02-18 (6 years ago)
There are currently 21 committers and 17 PMC members in this project.
The Committer-to-PMC ratio is roughly 6:5.
Community changes, past quarter:
- No new PMC members. Last addition was Kevin Risden on 2018-04-02.
- No new committers. Last addition was Kevin Risden on 2018-04-03.
- We have an active VOTE for a new committer and PMC member now which
we expect to pass.
## Project Activity:
- Planning for the Apache Knox 1.4.0 release has begun and
continues with the approach of using KIPs to communicate larger
design and feature changes and goals.
- We plan to concentrate on the client library and shell for
interacting with remote Knox instances/Hadoop clusters and
Cloudera Manager based service discovery.
- 1.3.0 was released on 2019-07-23.
- 1.2.0 was released on 2018-12-18.
## Community Health:
There does seem to be an uptick in use of Apache Knox in Hadoop
and other big data deployments across the industry. We have
received contributions from new contributors with varying sizes
and level of impact. Pull requests are a relatively new mechanism
for the Knox community which explains the large increase over
previous quarters.
The large increase in email traffic on the dev list is likely a
result of additional traffic from github PR activity and commits.
- dev@knox.apache.org had a 72% increase in traffic in the
past quarter (2117 emails compared to 1229)
- user@knox.apache.org had a 125% increase in traffic in the
past quarter (36 emails compared to 16)
- 135 issues opened in JIRA, past quarter (8% increase)
- 141 issues closed in JIRA, past quarter (22% increase)
- 147 commits in the past quarter (24% increase)
- 22 code contributors in the past quarter (22% increase)
- 62 PRs opened on GitHub, past quarter (44% increase)
- 61 PRs closed on GitHub, past quarter (52% increase)
-----------------------------------------
Attachment AI: Report from the Apache Kylin Project [Shao Feng Shi]
## Description:
Apache Kylin is an open source Distributed Analytics Engine designed
to provide SQL interface and multi-dimensional analysis (OLAP) on
Hadoop supporting extremely large datasets.
## Issues:
There are no issues requiring board attention at this time
## Membership Data:
Apache Kylin was founded 2015-11-18 (4 years ago)
There are currently 37 committers and 22 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:3.
Community changes, past quarter:
- No new PMC members. Last addition was Gang Ma on 2019-05-29.
- Chao Long was added as committer on 2019-10-01
- Shaohui Liu was added as committer on 2019-10-25
## Project Activity:
3.0.0-beta was released on 2019-10-24.
2.6.4 was released on 2019-10-12.
3.0.0-alpha2 was released on 2019-07-30.
Apache Kylin Meetup @OLX, Berlin, Germany; 7:00PM - 8:30PM, Thursday, 2019-10-24
Apache Kylin Meetup @Shenzhen, China; 12:30PM - 17:00PM, Saturday, 2019-09-07
## Community Health:
The discussions in mailing list has a small drop (10%) compared with previous
quarter. One reason we think is that the stable branch 2.6.x has less change
and the v2.6.4 release is more stable than before, so less problem and issue
be reported. The 3.0 release is in beta now, most of the users haven't
upgraded to it yet.
dev@kylin.apache.org had a 10% decrease in traffic in the past quarter (303
emails compared to 333) 113 issues opened in JIRA, past quarter (-11%
decrease)
129 issues closed in JIRA, past quarter (48% increase)
209 commits in the past quarter (-16% decrease)
39 code contributors in the past quarter (-4% decrease)
-----------------------------------------
Attachment AJ: Report from the Apache Lens Project [Amareshwari Sriramadasu]
## Description:
Lens provides an Unified Analytics interface. Lens aims to cut the Data
Analytics silos by providing a single view of data across multiple tiered data
stores and optimal execution environment for the analytical query. It
seamlessly integrates Hadoop with traditional data warehouses to appear like
one.
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache Lens was founded 2015-08-19 (4 years ago)
There are currently 23 committers and 18 PMC members in this project.
The Committer-to-PMC ratio is roughly 6:5.
Community changes, past quarter:
- No new PMC members. Last addition was Puneet Gupta on 2016-09-20.
- No new committers. Last addition was Rajitha R on 2018-02-09.
## Project Activity:
- There is discussion on the Roadmap of the project on dev list. One of the
organization who is using the project in production has proposed
improvements and changes, and PMC had a discussion on this and vote the way
forward. Changes to be suggested by the contributors for the same.
- Planning for release 2.8 in next quarter.
## Community Health:
There is no change in contributors and overall activity is the same(low), as
seen in earlier quarter.
-----------------------------------------
Attachment AK: Report from the Apache Libcloud Project [Tomaž Muraus]
-----------------------------------------
Attachment AL: Report from the Apache Logging Services Project [Matt Sicker]
## Description:
The mission of the Apache Logging Services project is to create and maintain of
software for managing the logging of application behavior, and for related
software components.
## Issues:
There are no issues requiring board attention at this time.
## Membership Data:
Apache Logging Services was founded 2003-12-16 (16 years ago)
There are currently 35 committers and 14 PMC members in this project.
The Committer-to-PMC ratio is 5:2.
Community changes, past quarter:
- No new PMC members. Last addition was Carter Kozak on 2018-07-29.
- No new committers. Last addition was Andrei Ivanov on 2019-04-18.
## Project Activity:
- No new releases since the last report (Log4j 2.12.1 in August).
- Ongoing discussions and experiments on plugin system overhauls
continues with inspiration from projects like OpenWebBeans and
Guice.
- Work done to update our CI configurations is ongoing, though we
seem to have stabilized our Jenkins builds for now. Travis builds
are still questionable due to our use of multiple versions of the
JDK during build time.
- A new feature in JDK 14 involving NVMe storage looks promising to
improve our memory-mapped log file appenders to allow for maximum
performance in persisting log data.
## Community Health:
We had a bit of a traffic decrease since last quarter.
However, there has been some new interest in the log4php, log4net, and
log4cxx components which is promising.
-----------------------------------------
Attachment AM: Report from the Apache ManifoldCF Project [Karl Wright]
Project description
==============
ManifoldCF is an effort to provide an open source framework for connecting
source content repositories like Microsoft Sharepoint and EMC Documentum, to
target repositories or indexes, such as Apache Solr, OpenSearchServer or
ElasticSearch. ManifoldCF also defines a security model for target
repositories that permits them to enforce source repository security policies.
Releases
========
ManifoldCF graduated from the Apache Incubator on May 16, 2012. Since then,
there have been numerous major releases, including a 2.14 release on October
3, 2019. The next major release is due on December 31, 2019.
Committers and PMC membership
=============================
We nominated and approved Cihad Guzel as committer on 8/16/2019. We nominated
and approved Markus Schuch as a PMC member on 12/29/2017. We did not sign up
any new PMC members this quarter. We continue to be on the lookout for new
PMC members and committers.
This quarter saw the development of a replacement connector for the
discontinued OpenText LiveLink LAPI connector originally developed before
ManifoldCF became an Apache project. This development included much effort by
committers old and new who had access to a more modern LiveLink installation.
Despite significant frustrations, we were able to finally succeed, but it did
take many months, and we had communications and skill-set difficulties of all
kinds in the process. Other connectors that will be requiring this level of
work in the near future include the SharePoint connector.
Mailing list activity
=====================
Mailing list activity has been fairly active this quarter. Requests for
connector development continue to be significant.
I am unaware of any mailing list question that has gone unanswered.
-----------------------------------------
Attachment AN: Report from the Apache Marmotta Project [Jakob Frank]
## Description:
Apache Marmotta, an Open Platform for Linked Data. Apache Marmotta was founded
in December 2012, and has graduated from the Incubator in November 2013.
## Issues:
There are no major issues requiring board attention at this time.
## Activity:
A very quiet quarter again, no recent activities to report on.
## Health report:
The project was considered feature-complete since 3.3.0 and has recently
published version 3.4.0. Currently there are no active development activities.
## PMC changes:
- Currently 11 PMC members.
- Last PMC addition was Mark A. Matienzo on Thu Aug 18 2016
## Committer base changes:
- Currently 13 committers.
- Xavier Sumba was added as a committer on Mon Mar 27 2017
## Releases:
- Last release was 3.4.0 on Tue Jun 12 2018
## Mailing list activity:
- users@marmotta.apache.org:
- 2 emails sent to list (24 in previous report)
- dev@marmotta.apache.org:
- 9 emails sent to list (10 in previous report)
## JIRA activity:
- 0 JIRA tickets created in the last 3 months
- 3 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AO: Report from the Apache MetaModel Project [Kasper Sørensen]
## Description:
Providing a common interface for discovery, exploration of metadata and
querying of different types of data sources.
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache MetaModel was founded 2014-11-19 (5 years ago)
There are currently 13 committers and 12 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:6.
Community changes, past quarter:
- Arjan Seijkens was added to the PMC on 2019-08-29
- No new committers. Last addition was Jörg Unbehauen on 2018-05-03.
## Project Activity:
MetaModel 5.3.1 was released on 2019-09-13.
A fairly big change/PR (#229) was just recently merged, upgrading to newer
versions of ElasticSearch. This will break some existing behaviour due
to upstream changes in ElasticSearch itself.
Another sizeable change/PR (#230) is pending more review and agreement. It
attempts to autodetect data types in our MS Excel module.
## Community Health:
The MetaModel 5.3.1 release was the first release in a long time done by a
new release engineer: Arjan Seijkens. This was a good exercise to go through
to ensure that someone else than myself could perform the release.
Other than that, most if not all communication recently has been about specific
changes/PRs.
-----------------------------------------
Attachment AP: Report from the Apache Oozie Project [Gézapeti]
## Description:
The mission of Oozie is the creation and maintenance of software related to A
workflow scheduler system to manage Apache Hadoop jobs.
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache Oozie was founded 2012-08-28 (7 years ago)
There are currently 25 committers and 21 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:6.
Community changes, past quarter:
- No new PMC members. Last addition was Kinga Marton on 2019-07-16.
- No new committers. Last addition was Andras Salamon on 2019-02-14.
## Project Activity:
- 5.2.0 release is on it's way, rc0 has been build already by Andras Salamon
who is the Release Manager.
- Development is slow, but steady with minor bug fixes and security-related
library upgrades
## Community Health:
Community activity is down, but we do see new contributors from time to time.
The community is prioritizing patches from new contributors in reviews and
commits.
-----------------------------------------
Attachment AQ: Report from the Apache Open Climate Workbench Project [Huikyo Lee]
## Description:
The mission of Open Climate Workbench is the creation and maintenance of
software related to Climate model evaluation
## Issues:
The PMC needs to have a conversation on whether retirement is the best
next move. Project activity is extremely low and mailing list activity is
the same.
## Membership Data:
Apache Open Climate Workbench was founded 2014-02-18 (6 years ago)
There are currently 30 committers and 30 PMC members in this project.
The Committer-to-PMC ratio is 1:1.
Community changes, past quarter:
- No new PMC members. Last addition was Ibrahim Jarif on 2016-04-25.
- No new committers. Last addition was Christopher Douglas on 2016-04-26.
## Project Activity:
Extremely low. Contributions are not being reviewed or closed out
and the project is therefore not doing a good job at attracting
new quality contributors.
## Community Health:
The community could be said to be unhealthy. It is time to discuss
possible retirement of OCW.
-----------------------------------------
Attachment AR: Report from the Apache OpenJPA Project [Mark Struberg]
## Description:
The mission of OpenJPA is the creation and maintenance of software related to
OpenJPA: Object Relational Mapping for Java
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache OpenJPA was founded 2007-05-16 (13 years ago)
There are currently 35 committers and 19 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 Maxim Solodovnik on 2019-04-13.
- No new committers. Last addition was Matt Pavlovich on 2019-05-22.
## Project Activity:
Project activity was really low the last month. I hope we'll get this up
again and continue working on improving JPA-2.2 compatibility. Otoh there
are enough people still active to not worry about activity IF something
very urgent pops up.
## Community Health:
Yes, we should somehow attract more people. But the codebase is old and stable.
And due to the JavaEE/JakartaEE pause right now there is not much action
in sight which might attract new developers.
-----------------------------------------
Attachment AS: Report from the Apache OpenWhisk Project [Dave Grove]
## Description:
The mission of Apache OpenWhisk is the creation and maintenance of software
related to a platform for building serverless applications with functions
## Issues:
There are no issues requiring board attention.
In feedback from last month's board report, DF asked us to verify that "the
Redis included in Composer is still an acceptable Open Source Software
license." OpenWhisk Composer depends/uses only Redis Core which continues to
be made available under a BSD 3-Clause license. The apigateway component of
OpenWhisk also uses the same Redis Core functionality.
## Membership Data:
Apache OpenWhisk was founded 2019-07-16 (4 months ago)
There are currently 42 committers and 20 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 Rob Allen on 2019-07-16.
- Justin Halsall was added as committer on 2019-08-22
## Project Activity:
Recent releases: openwhisk-runtime-go-1.14.0 was released on 2019-10-10.
With the merging of the last of the "playground ui" PRs on November 1, we
should finally be feature-complete for the standalone configuration of
OpenWhisk. We are now working towards making a source release containing this
feature. We hope to get this release out before the end of 2019.
## Community Health:
Community health is good with plenty of activity on dev list and slack.
Statistically, the decline in all metrics vs. the previous quarter is mainly
due to the compare against the one-time surge of activity associated with
graduating from the incubator.
-----------------------------------------
Attachment AT: Report from the Apache Perl Project [Philippe Chiasson]
--- mod_perl --
mod_perl 2.0.11 was released on October 5th 2019
This release contains multiple bugfixes and one notable security fix for
CVE-2011-2767
Many thanks to Steve Hay for pushing this release through.
-- Activity --
The activity levels went up a little, seeing many of the PMC members
contribute feedback and test results on the 2.0.11 RCs
Distros were quick at picking it up, as usual.
-- Users --
The mod_perl users list is seeing little activity, as usual.
Patches and bug reports are few, but keep on coming.
-- Commiters --
Currently 22 committers.
No new changes to the committer base since last report.
Last Commiter addition was Jan Kaluza in April 2013
-- PMC --
Currently 11 PMC members.
No new PMC members added in the last 3 months
Last PMC addition was Steve Hay on Wed Feb 29 2012
-----------------------------------------
Attachment AU: Report from the Apache Phoenix Project [Josh Elser]
## Description:
The mission of Phoenix is the creation and maintenance of software related to
High performance relational database layer over Apache HBase for low latency
applications
## Issues:
No issues for the board at this time.
## Membership Data:
Apache Phoenix was founded 2014-05-20 (5 years ago)
There are currently 44 committers and 31 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:2.
Community changes, past quarter:
- Chinmay Kulkarni was added to the PMC on 2019-09-09
- No new committers. Last addition was Kadir Ozdemir on 2019-05-30.
## Project Activity:
Business as usual for the community overall.
We continue to have active development on the 4.x and 5.x release lines. There
was an rc0 for a 4.15.0 release which is the next-up release to be had. The
5.x line still needs an owner to step up and drive a release cadence.
There was a suggestion that the Omid and Tephra podlings graduate into
sub-projects of the Apache Phoenix PMC. This suggestion was made as both Omid
and Tephra have integration into Phoenix and provide some direct, end-user
value. Both podlings were struggling to retain active podling memberships.
The Phoenix community voted in favor of this graduation for both podlings, and
all podling members who request it will be made Apache Phoenix committers.
At this point, the 72hr lazy-consensus/notice on general@incubator to perform
this double-podling subproject graduation has passed. VP-Phoenix and podling
mentors need to sync and make a plan to start combining these resources.
## Community Health:
Developer (dev/issues) mailing list traffic is down slightly, but user mailing
list traffic is actually up over the past quarter. We continue to see an up-tick
in the use of Github pull requests over patches on Jira (which may be related
to the change in dev/issues traffic volume). As a project, continuing to ensure
that Github-based code contributions are being integrated is ever more
important.
In general, we continue to see the same developers participating, with a
reasonable number of new contributors to keep the committer pipeline active.
-----------------------------------------
Attachment AV: Report from the Apache POI Project [Dominik Stadler]
Report from the Apache POI committee [Dominik Stadler]
## Description:
- Apache POI is a Java library for reading and writing Microsoft Office file
formats
The Apache POI PMC also handles bugfixes for the XMLBeans project: XMLBeans
is a tool that allows you to map XML files to generated Java classes via
XML Schema definitions.
## Issues:
- There are no issues requiring board attention at this time
## Project Activity:
- We released version 4.1.1 after a security issue was reported to us, this
release also includs a bunch of other changes, new image handling
functionality for PowerPoint files and fixes for a regression for memory
usage of XSSF.
Testing of JDK 13 was finished and some pre-testing of JDK 14 done as well.
## Health report:
- There are some ongoing discussions with users about features/behavior which
indicates that the popularity of Apache POI is still high. Questions via
email or on Stackoverflow usually get answers quickly.
Activity from committers was again low, most developers seem to be tied up
with other stuff right now, we would like to broaden the developer base but
not many potential committers show up on the mailing lists which has
historically been our main source of recruitment.
We sent out one invitation to join as Comitter/PMC and the applicant
accepted, onboarding is still in-progress.
Bug-numbers unfortunately increase steadily, some bug influx and some could
be fixed, but overall the rate of creation is higher than resolving, also
due to some invalid bugs being entered which need to be analyzed/triaged as
well.
### XMLBeans
- Nearly no changes for XMLBeans this quarter, the project is in maintenance
mode, some discussion about updating required Java to JDK 8, but no changes
made in that regard yet.
Bug influx for XMLBeans is very low because it is a stable project in
maintenance-mode.
## Membership Data:
Apache POI was founded 2007-05-16 (12 years ago) There are currently 38
committers and 31 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 Vladislav Galas on 2018-12-30.
- No new committers. Last addition was Vladislav Galas on 2018-12-26.
## Bugzilla Statistics:
### Apache POI
- 564 bugs are open overall (+25)
- Having 154 enhancements (+4)
- Thus having 410 actual bugs (+21)
- 89 of these are waiting for feedback (+-0)
- Thus having 321 actual workable bugs (+21)
- 5 of the workable bugs have patches available (+1)
- Distribution of workable bugs across components: {HSSF=84, XSSF=82, SS
Common=42, HWPF=35, XWPF=25, SXSSF=13, POI Overall=12, XSLF=9, OPC=4,
POIFS=4, HPSF=3, HSMF=3, XDDF=2, HPBF=1, HSLF=1, SL Common=1}
### Apache XMLBeans
- 176 open issues (+4)
- Bug 131 (+3)
- Improvement 22 (+-0)
- New Feature 19 (+1)
- Wish 4 (+-0)
-----------------------------------------
Attachment AW: Report from the Apache Qpid Project [Robbie Gemmell]
Apache Qpid is a project focused on creating software based on the
Advanced Message Queuing Protocol (AMQP), currently providing a protocol
engine library, message brokers written in C++ and Java, a message router,
and client libraries for C, C++, Go, Java/JMS, Python, and Ruby.
# Releases:
- Qpid Proton-J 0.33.2 was released on 13th August 2019.
- Qpid Proton 0.29.0 was released on 16th August 2019.
- Qpid JMS 0.45.0 was released on 24th August 2019.
- Qpid Dispatch 1.9.0 was released 19th September 2019.
- Qpid JMS 0.46.0 was released on 27th September 2019.
- Qpid Broker-J 7.1.5 was released on 10th October 2019.
- Qpid JMS 0.47.0 was released on 5th November 2019.
# Community:
- The main user and developer mailing lists continue to be active and JIRAs
are being raised and addressed in line with prior activity levels.
- Ben Hardesty was added as committer on 20th September 2019.
- There were no new PMC additions in this quarter.
The most recent new PMC member is Ganesh Murthy, added on 30th Jan 2017.
# Development:
- Dispatch router had its 1.9.0 release including various bug fixes, feature
changes, and work on improving performance. Work on more fixes and
improvements toward a 1.10.0 release is well progressed, with a release
planned in the next couple of weeks.
- Proton-C and its language bindings had their 0.29.0 release, incorporating
various bug fixes. Work on more toward a 0.30.0 release continues.
- The AMQP 1.0 JMS client had its 0.45.0 - 0.47.0 releases which included
various bug fixes and improvements, work continues on more.
- Broker-J had its 7.1.5 release, including various bug fixes
and improvements. Work continues on more toward an 8.0.0 release, with
backports to the 7.1.x line as appropriate.
- Proton-J had a 0.33.2 bug fix releases, with more fixes and improvements
occurring as needed for its various dependent components.
# Issues:
There are no Board-level issues at this time.
-----------------------------------------
Attachment AX: Report from the Apache REEF Project [Sergiy Matusevych]
## Description:
- Apache REEF (Retainable Evaluator Execution Framework) is a library for
developing portable applications for cluster resource managers such as
Apache Hadoop YARN or Apache Mesos.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- Still working on updating the dependencies.
Plan for a minor release in November.
- Finishing work on .Net elastic broadcast. Planning a new release this year.
## Health report:
- The engagement from the community has been declining perhaps because the
codebase has been stable.
- We've decided to do a minor release this quarter to update the project's
dependencies.
- Work continues in the elastic broadcast pull request (600+ comments/fixes).
There was a delay in this effort due to the principal committer's paternity
leave; We will resume that work after publishing a minor release of REEF.
- We plan to issue a new release as soon as we merge the elastic group
communication into master.
## PMC changes:
- Currently 22 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Doug Service on Thu Sep 28 2017
## Committer base changes:
- Currently 35 committers.
- No new committers added in the last 3 months
- Last committer addition was Scott Inglis at Thu Sep 27 2018
## Releases:
- Last release was 0.16 on Wed Aug 09 2017.
- Release 0.16.1 planned for November 2019.
- Release 0.17 planned before the end of year 2019.
## Mailing list activity:
- dev@reef.apache.org:
- 86 subscribers (up 0 in the last 3 months):
- 2 emails sent to list (8 in previous quarter)
- user@reef.apache.org:
- 20 subscribers (up 0 in the last 3 months):
- 0 emails sent to list (0 in previous quarter)
## JIRA activity:
- 1 JIRA tickets created in the last 3 months
- 1 JIRA tickets closed/resolved in the last 3 months
## Commit activity:
- 6 commits in the past quarter (0 last quarter)
- 2 code contributors in the past quarter (0 last quarter)
## GitHub PR activity:
- 6 PRs opened on GitHub, past quarter (0 last quarter)
- 1 PR closed on GitHub, past quarter (0 last quarter)
-----------------------------------------
Attachment AY: Report from the Apache River Project [Peter Firmstone]
## Description:
- Apache River provides a platform for dynamic discovery and lookup search of
network services. Services may be implemented in a number of languages,
while clients are required to be jvm based (presently at least), to allow
proxy jvm byte code to be provisioned dynamically.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- Minimal activity at present, initial work on the modular build structure
has commenced. The current monolithic build is complex, with it's own
build tool classdepandjar, it adds complexity for new developers. In
recent months I have had work committments that have limited my ability to
integrate the modular build. The other committers are waiting for the
modular build and I have done a lot of work on this locally, this work has
been a significant undertaking integrating the works of Dennis Reedy, Dan
Rollo and myself. This is also a mature codebase, having been in
development since the late 1990's.
- The monolithic code has been svn moved into modules into an initial maven
build structure, next step is to move junit tests to each module.
Release roadmap:
River 3.1 - Modular build restructure (& binary release) River 3.2 - Input
validation 4 Serialization, delayed unmarshalling& safe ServiceRegistrar
lookup service.River 3.3 - OSGi support
## Health report:
- River is a mature codebase with existing deployments, it was primarily
designed for dynamic discovery of services on private networks. IPv4 NAT
limitations historically prevented the use of River on public networks,
however the use of IPv6 on public networks removes these limitations. Web
services evolved with the publish subscribe model of todays internet, River
has the potential to dynamically discover services on IPv6 networks, peer
to peer, blurring current destinctions between client and server, it has
the potential to address many of the security issues currently experienced
with IoT and avoid any dependency on the proprietary cloud for "things".
- Future Direction:
* Target IOT space with support for OSGi and IPv6 (security fixes required
prior to announcement)
* Input validation for java deserialization - prevents DOS and Gadget
attacks.
* IPv6 Multicast Service Discovery (River currently only supports IPv4
multicast discovery).
* Delayed unmarshalling for Service Lookup and Discovery (includes
SafeServiceRegistrar mentioned in release roadmap), so authentication can
occur prior to downloading service proxy's, this addresses a long
standing security issue with service lookup while significantly improving
performance under some use cases.
* Security fixes for SSL endpoints, updated to TLS v1.2 with removal of
support for insecure cyphers.
* Secure TLS SocketFactory's for RMI Registry, uses the currently logged in
Subject for authentication. The RMI Registry still plays a minor role in
service activation, this allows those who still use the Registry to
secure it.
* Maven build to replace existing ant built that uses classdepandjar, a
bytecode dependency analysis build tool.
* Updating the Jini specifications.
## Project Composition:
There are currently 16 committers and 12 PMC members in this project. The
Committer-to-PMC ratio is 4:3.
## Community changes, past quarter:
No new PMC members. Last addition was Dan Rollo on 2017-12-01. No new
committers. Last addition was Dan Rollo on 2017-11-02.
## Project Release Activity:
- Recent releases:
River-3.0.0 was released on 2016-10-06. river-jtsk-2.2.3 was released on
2016-02-21. river-examples-1.0 was released on 2015-08-10.
## JIRA activity:
1 issue opened in JIRA, past quarter (no change) 0 issues closed in JIRA,
past quarter (-100% decrease)
-----------------------------------------
Attachment AZ: Report from the Apache RocketMQ Project [Xiaorui Wang]
## Description:
The mission of Apache RocketMQ is the creation and maintenance of software
related to a fast, low latency, reliable, scalable, distributed, easy to use
message-oriented middleware, especially for processing large amounts of
streaming data
## Issues:
here are no issues requiring board attention.
## Membership Data:
There are currently 23 committers and 13 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 Qipeng Li on 2019-08-12.
- Wenfeng Wang was added as committer on 2019-10-19
## Project Activity:
ROCKETMQ-CLIENT-CPP-1.2.3 was released on 2019-09-10.
ROCKETMQ-4.5.2 was released on 2019-08-12.
## Community Health:
dev@rocketmq.apache.org had a 39% increase in traffic
in the past quarter (2950 emails compared to 2113)
users@rocketmq.apache.org had a 50% decrease in traffic
in the past quarter (59 emails compared to 116)
534 commits in the past quarter (38% increase)
62 code contributors in the past quarter (-7% decrease)
243 PRs opened on GitHub, past quarter (3% increase)
211 PRs closed on GitHub, past quarter (-13% decrease)
280 issues opened on GitHub, past quarter (10% increase)
261 issues closed on GitHub, past quarter (48% increase)
-----------------------------------------
Attachment BA: Report from the Apache Roller Project [David M. Johnson]
## Description:
Apache Roller is a full-featured, Java-based blog server that works well on
Tomcat and MySQL, and is known to run on other Java servers and relational
databases. The latest release is 5.2.4 and the ASF blog site at blogs.apache.org
runs on Roller 5.2.4 Tomcat and MySQL.
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache Roller was founded 2007-02-21 (13 years ago)
There are currently 10 committers and 6 PMC members in this project.
The Committer-to-PMC ratio is 5:3.
Community changes, past quarter:
- Aditya Sharma was added to the PMC on 2019-08-04
- Swapnil Mane was added as committer on 2019-09-15
## Project Activity:
The Roller community worked on some UI/UX enhancements for future release 6.0.
In addition to it, there were some JS library upgrades for release 5.2.x.
We plan to release it soon.
The community also worked on migrating docs from ODT to Ascii Doc format.
The plan is to migrate most of the documents for easy maintainability.
We plan to have 2 releases along with a new Roller logo in the next quarter.
## Community Health:
Overall community health is good.
We have recently defined a Contributors onboarding process to attract new
contributors, and are seeing a steady entry of new people
with contributions, both programming and documentation-wise.
Here are some stats that back that up:
- 33% increase in mailing list traffic
- No change in issues opened in JIRA
- 14% decrease in issues closed in JIRA
- 18% decrease in commits in the past quarter
- 14% increase in code contributors
- 137% increase in PRs opened on GitHub
- 133% increase in PRs closed on GitHub
-----------------------------------------
Attachment BB: Report from the Apache Samza Project [Yi Pan]
## Description:
- Apache Samza is a distributed stream processing engine that are highly
configurable to process events from various data sources, including
real-time messaging system (e.g. Kafka) and distributed file systems (e.g.
HDFS).
## Issues:
- No issues requires board attention
## Health report:
- Project is in healthy status with 1.2 released in June 2019
## PMC changes:
- Currently 16 PMC members.
- Boris Shkolnik was added to the PMC on Thu Jun 06 2019
## Committer base changes:
- Currently 26 committers.
- Rayman Preet Singh was added as a committer on July 8 2019
## Releases:
- Last release was 1.2.0 on June 11 2019
## Mailing list activity:
- dev@samza.apache.org:
- 56 emails sent to list (133 in previous quarter)
## JIRA activity:
- 78 JIRA tickets created in the last 3 months
- 26 JIRA tickets closed/resolved in the last 3 months
## Commit activity
- 90 commits in the past quarter (-23% decrease)
- 27 code contributors in the past quarter (12% increase)
## GitHub PR activity:
- 80 PRs opened on GitHub, past quarter (-27% decrease)
- 79 PRs closed on GitHub, past quarter (-28% decrease)
## Other activities:
- Samza stream processing meetup @LinkedIn was held on Oct 3, 2019
(https://www.meetup.com/Stream-Processing-Meetup-LinkedIn/events/264589317/)
-----------------------------------------
Attachment BC: Report from the Apache Santuario Project [Colm O hEigeartaigh]
## Description:
The mission of Santuario is the creation and maintenance of software related to
XML Security in Java and C++
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache Santuario was founded 2006-06-27 (13 years ago)
There are currently 17 committers and 7 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 Daniel Kulp on 2018-10-01.
- No new committers. Last addition was Daniel Kulp on 2018-10-01.
## Project Activity:
There were no releases over the last quarter. 4 JIRA issues were resolved for
the next minor Java release, so we will probably get this release done over
the next quarter.
There was some initial discussion on the project about moving to git. We will
revive this discussion shortly, and anticipate making the switch over the
next quarter.
## Community Health:
Apache Santuario is a mature and stable project that has reached a point
where not too many fixes are required, as it is a set of implementations
of some specifications that are quite old now. It is actively managed by
the PMC.
-----------------------------------------
Attachment BD: Report from the Apache Serf Project [Branko Čibej]
Report from the Apache Serf Project [Branko Čibej]
## Description:
The serf library is a high performance C-based HTTP client library
built upon the Apache Portable Runtime (APR) library. Serf is the
default client library of Apache Subversion, Apache OpenOffice and
mod_pagespeed.
## Issues:
Activity on the project seems to have come to a halt in the last year.
## Activity:
There has been no move towards getting Serf 1.4.0 released in the last
twelve months. A release candidate for internal testing was produced,
but never released. The last Serf release is now 3+ years old.
The only active user of Serf seems to be Apache Subversion.
Apache OpenOffice uses a version of Serf that was released before
Serf became a Apache TLP.
## Health report:
The last commit in the public repository was made on 11th June, being
a minor fix to the build scripts. The commit previous to that was
made in November 2018.
The feeling amongst PMC members is that Serf is a mature product
and thus a low level of activity is expected.
## PMC & Committer changes:
Currently 13 PMC members and 13 committers.
- No new committers added in the last 3 months.
- Last new committer added in April 2017 (Evgeny Kotkov).
- Last new PMC member added in September 2018 (Branko Čibej).
## Releases:
Apache Serf 1.3.9 was released on Thu Sep 01 2016
## Mailing list and Jira activity:
The last message on the dev@ mailing list is six months old.
It's a follow-up from a discussion with a user on IRC who had
trouble building our sources.
-----------------------------------------
Attachment BE: Report from the Apache ServiceComb Project [Willem Ning Jiang]
## Description:
The mission of Apache ServiceComb is the creation and maintenance of software
related to a microservice framework that provides a set of tools and components
to make development and deployment of cloud applications easier.
## Issues:
- There are no issues requiring board attention at this time
## Membership Data:
Apache ServiceComb was founded 2018-10-17 (a year ago)
There are currently 21 committers and 20 PMC members in this project.
The Committer-to-PMC ratio is roughly 6:5.
Community changes, past quarter:
- MabinGo was added to the PMC on 2019-10-09
- Xiaoliang Tian was added to the PMC on 2019-08-22
- Lei Zhang was added to the PMC on 2019-08-22
- Daniel Qian was added as committer on 2019-11-08
## Project Activity:
Software development activities
ServiceComb Service-Center 1.3.0 was released on 2019-11-07.
ServiceComb Java Chassis 1.3.0 was released on 2019-10-31.
ServiceComb Mesher 1.6.3 was released on 2019-09-09.
ServiceComb Pack 0.5.0 was released on 2019-08-26.
Meetups and Conferences:
- A meetup about ServiceComb was hold in Shanghai on 2019-09-20
## Community Health:
The community discussion are increased:
dev@(35% increase), issues@(52% increase)
(we use github issue as user@ maillist)
github opened issues(38% increased)
github closed issues(47% increase)
There are a drop of the code commits number(-56% decrease)
as some sub projects just did release recently.
-----------------------------------------
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
## Status and health report
- The project graduated from the incubator in October. Currently, we have 13
PMC members and 17 committers. Recently, we are developing the ONNX module,
a standard representation of deep learning models. We are also doing the
optimization of existing components in terms of efficiency.
## PMC changes
- We are inviting a committer to join the PMC (not completed).
## Last release
- The last release was v2.0.0 on 20 April 2019
## Activity
- 126 emails in October
- 26 commits in October
## Plan
- Update the website with a new template and remove outdated pages
- Release v2.1.0 in two months
-----------------------------------------
Attachment BG: Report from the Apache SIS Project [Martin Desruisseaux]
## Description:
Apache Spatial Information System (SIS) is a Java library
for developing geospatial applications. SIS enables better
representation of spatial objects for searching, archiving,
or other relevant spatial needs. The base of the SIS library
is modeled according international standards published jointly
by the Open Geospatial Consortium (OGC) and the International
Organization for Standardization (ISO).
## Issues:
No issue to report this month. Previous reports mentioned the very
long delay since last release, but SIS 1.0 has finally been released.
## Membership Data:
Apache SIS was founded 2012-09-19 (7 years ago).
There are currently 22 committers and 20 PMC members in this project.
The Committer-to-PMC ratio is roughly 6:5.
Community changes, past quarter:
- No new PMC members. Last addition was Johann Sorel on 2017-09-07.
- No new committers. Last addition was Alexís Manin on 2019-07-05.
## Project Activity:
Apache SIS 1.0 has been released last September, about 2 years after the
previous release. This long delay was due to the effort required for
integrating a large user contribution (upgrade metadata XML schema to the
latest ISO 19115 standard), followed by compatibility issues with Java 9+
that we had time to resolve only recently. SIS is now compatible with latest
Java release and there is no reason to delay SIS 1.1 as much as SIS 1.0 has
been.
Current development work includes more spatial filters, a query language
(CQL) for applying those filters, and the beginning of a JavaFX application
for those who have JavaFX pre-installed (we do not redistribute it).
The JavaFX work started as a Google Summer of Code 2018 project but required
cleanup, which we have been able to do only now. We hope that a graphical
user application would help to demonstrate SIS capabilities.
Other developments in separated branches are GeoJSON support and
improvements in the use of vector data stored in a spatial database
(e.g. PostGIS, but not limited to).
Number of downloads from Maven central repository fluctuates between 100,000
and 200,000 per month (20,000 ~ 25,000 unique IPs), but I suspect that a lot
of them are side-effects of Apache Tika downloads (through dependency)
rather than users seeking specifically for SIS.
## Community Health:
The number of active contributors is 3, with Johann and Alexis activity on
SIS increasing. Those 3 contributors are from the same company; we do not
yet have a diversity at this level. The busiest topic in September has been
fixes and stabilization before SIS 1.0 release.
The traffics on mailing lists fluctuate a lot (with both increases and
decreases), but this is hardly significant because of the low amount of
emails (between 10 and 35). We have not observed a significant evolution
of this situation for many years, except during Google Summer of Code.
-----------------------------------------
Attachment BH: Report from the Apache Spark Project [Matei Alexandru Zaharia]
Apache Spark is a fast and general engine for large-scale data processing. It
offers high-level APIs in Java, Scala, Python and R as well as a rich set of
libraries including stream processing, machine learning, and graph analytics.
Project status:
- We made the first preview release for Spark 3.0 on November 6th. This
release aims to get early feedback on the new APIs and functionality
targeting Spark 3.0 but does not provide API or stability guarantees. We
encourage community members to try this release and leave feedback on JIRA.
More info about what's new and how to report feedback is available at
https://spark.apache.org/news/spark-3.0.0-preview.html.
- We published Spark 2.4.4. and 2.3.4 as maintenance releases to fix bugs in
the 2.4 and 2.3 branches.
- We added one new PMC members and six committers to the project in August and
September, covering data sources, streaming, SQL, ML and other components of
the project.
Trademarks:
- Nothing new to report since August.
Latest releases:
- Spark 3.0.0-preview was released on Nov 6th, 2019.
- Spark 2.3.4 was released on Sept 9th, 2019.
- Spark 2.4.4 was released on Sept 1st, 2019.
Committers and PMC:
- The latest PMC member was added on Sept 4th, 2019 (Dongjoon Hyun).
- The latest committer was added on Sept 9th, 2019 (Weichen Xu). We also added
Ryan Blue, L.C. Hsieh, Gengliang Wang, Yuming Wang and Ruifeng Zheng as
committers in the past three months.
-----------------------------------------
Attachment BI: Report from the Apache Stanbol Project [Rafa Haro]
-----------------------------------------
Attachment BJ: Report from the Apache Submarine Project [Wangda Tan]
# [REPORT] Submarine - Nov 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
### Talks about Submarine
We have talked about Submarine during Apache Con Las Vegas (September), and
Strata Data Conf New York (September).
### Submarine spin-off from Hadoop
Submarine is voted spin-off from Hadoop on Oct 16 to TLP.
### New website
Submarine new website is online now: https://submarine.apache.org
## 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:
- Currently 7 PMC members.
- New PMC members since spin-off: 1
- Keqiu Hu was added as PMC on Nov 8.
### Committer base changes, past quarter:
- Currently 22 committers.
- New committers since spin-off: 16
## Project Activity:
### Releases
- Community is actively working on 0.3.0 release and target to ship by Dec,
2019.
## Community Health:
### JIRA Activity
Significantly up compared to last quarter
- 171 JIRA tickets created since the past quarter [ project in ("Apache
Submarine") AND createdDate >= 2019-08-05
]
- 121 JIRA tickets resolved since the past quarter [ project in ("Apache
Submarine") AND resolutiondate >= 2019-08-05
]
### Mailing list, slack channel, activity:
We just created mailing lists @submarine.apache.org, will promote it for
contributors to subscribe.
-----------------------------------------
Attachment BK: Report from the Apache Subversion Project [Stefan Sperling]
The Apache Subversion® version control system exists to be universally
recognized and adopted as an open-source, centralized version control solution
characterized by its reliability as a safe haven for valuable data; the
simplicity of its model and usage; and its ability to support the needs of
a wide variety of users and projects, from individuals to large-scale
enterprise operations.
* Board Issues
There are no Board-level issues of concern.
* Community
The Subversion development community is fairly quiet these days. A
small trickle of development is ongoing. The community usually
responds to bug reports and is willing to help the reporter or any
other volunteer to develop a fix. However, in many cases there is no
such volunteer, and those bug reports are filed but often remain
unresolved.
Our user support forums (Email and IRC) receive questions and answers
regularly.
We have added two PMC members since the last report: Nathan Hartman
(hartmannathan@) and Yasuhito Futatsuki (futatuki@).
* Releases
Subversion 1.13.0-rc1 and 1.13.0 have been released. Subversion 1.12.x
reaches end of life.
Subversion 1.10 and Subversion 1.9 are still supported.
Discussions about the frequency of minor releases have taken place on dev@.
The community is still evaluating the cost and benefits of the time-based
release schedule which was introduced in 2018.
https://subversion.apache.org/roadmap.html#release-planning
-----------------------------------------
Attachment BL: Report from the Apache Syncope Project [Francesco Chicchiriccò]
## Description:
The mission of Syncope is the creation and maintenance of software related to
managing digital identities in enterprise environments.
## Issues:
There are no issues requiring board attention at this time.
## Membership Data:
Apache Syncope was founded 2012-11-21 (7 years ago)
There are currently 24 committers and 11 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 Matteo Alessandroni on 2017-12-22.
- Misagh Moayyed was added as committer on 2019-10-04
## Project Activity:
After recent releases, branch 2_0_X is now in pure maintenance mode, while
2_1_X is currently under work for small improvements and bugfixes. Work to
finalize and implement the many features planned for next stable version 3.0.0
is in progress.
We started seeing an increase in contributions via pull requests from GitHub.
Latest releases:
- 2.0.14 was released on 2019-09-12
- 2.1.5 was released on 2019-09-12
## Community Health:
New and returning users use mailing lists to query for help and customization
and get supported by the community, as incremented traffic seem to validate.
We welcome a new committer (Misagh Moayyed) and also decided to report in our
team page a contributor, which has not responded yet to our invitation.
-----------------------------------------
Attachment BM: Report from the Apache SystemML Project [Jon Deron Eriksson]
## Description:
SystemML provides declarative large-scale machine learning (ML) that aims at
flexible specification of ML algorithms and automatic generation of hybrid
runtime plans ranging from single node, in-memory computations, to distributed
computations such as Apache Hadoop MapReduce and Apache Spark.
## Issues:
There were no commits to the project this quarter. Activity on the project has
largely stopped.
## Membership Data:
Apache SystemML was founded 2017-05-16 (2 years ago)
There are currently 26 committers and 23 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:6.
Community changes, past quarter:
- No new PMC members. Last addition was Arvind Surve on 2017-05-16.
- No new committers. Last addition was Guobao Li on 2018-08-28.
## Project Activity:
There has been only 1 commit since May.
No pull requests have been opened or closed since May.
The most recent release was 1.2.0 on Aug 24, 2018.
## Community Health:
The community is unhealthy.
There is little email activity.
Adding significant features to the project in the future will be difficult
without support from existing contributors with a deep knowledge of SystemML,
and these contributors do not appear to be active anymore.
## Answers to Board Questions:
myrle: Thank you for answering my question. Are there any plans to
add new committers or make the existing committers PMC
members? It might help with project activity levels and with
working through your hanging pull requests
Currently there are no plans to add new committers since there is so little
activity on the project. There are only 2 commits from people who are
not already committers in the last year. WRT PMC members, 23 of the 26
committers are already PMC members, and there is no activity in the last year
from 2 of the 3 committers who are not PMC members, and only 3 commits from
the other committer, so my feeling is that making existing committers PMC
members probably would not help jumpstart project activity.
-----------------------------------------
Attachment BN: Report from the Apache Tajo Project [Hyunsik Choi]
-----------------------------------------
Attachment BO: Report from the Apache Tapestry Project [Thiago Henrique De Paula Figueiredo]
## Description:
The mission of Tapestry is the creation and maintenance of software related to
Component-based Java Web Application Framework
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache Tapestry was founded 2006-02-14 (14 years ago)
There are currently 27 committers and 12 PMC members in this project.
The Committer-to-PMC ratio is 9:4.
Community changes, past quarter:
- Dmitry Gusev was added to the PMC on 2019-09-02
- No new committers. Last addition was Balázs Palcsó on 2019-01-17.
## Project Activity:
A new beta, 5.5.5-beta-3 was released in September 15th. We've been preparing
for the new major release, 5.5.0, and waiting for user feedback, specially the
CSS changes (being able to use Twitter Bootstrap 3 out of the box, Bootstrap 4
out of the box, or no Bootstrap at all.
## Community Health:
dev@tapestry.apache.org had a 1283% increase in traffic in the
past quarter (83 emails compared to 6)
users@tapestry.apache.org had a 46% decrease in traffic in the
past quarter (43 emails compared to 79)
6 issues opened in JIRA, past quarter (200% increase)
4 issues closed in JIRA, past quarter (400% increase)
14 commits in the past quarter (180% increase)
3 code contributors in the past quarter (50% increase)
3 PRs opened on GitHub, past quarter (300% increase)
-----------------------------------------
Attachment BP: Report from the Apache Tez Project [Jonathan Turner Eagles]
## Description:
Apache Tez is an effort to develop a generic application framework which can be
used to process arbitrarily complex DAGs of data-processing tasks and also a
re-usable set of data-processing primitives which can be used by other projects.
## Issues:
Last release was 6 months ago, seeking new release manager.
## Membership Data:
Apache Tez was founded 2014-07-15 (5 years ago)
There are currently 38 committers and 35 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 Kuhu Shukla on 2018-03-25.
- No new committers. Last addition was Kuhu Shukla on 2017-05-10.
## Project Activity:
Last release: 0.9.2 was released on 2019-03-29.
Work toward JDK 11 support is almost completed.
## Community Health:
Overall more activity in the last quarter than the previous.
- dev@tez.apache.org had a 116% increase in traffic in the past quarter (67
emails compared to 31)
- issues@tez.apache.org had a 251% increase in traffic in the past quarter
(267 emails compared to 76)
- 18 issues opened in JIRA, past quarter (63% increase)
- 6 issues closed in JIRA, past quarter (50% increase)
- 7 commits in the past quarter (600% increase)
- 3 code contributors in the past quarter (200% increase)
- 10 PRs opened on GitHub, past quarter (400% increase)
- 4 PRs closed on GitHub, past quarter (300% increase)
-----------------------------------------
Attachment BQ: Report from the Apache TomEE Project [David Blevins]
## Description:
Apache TomEE delivers enterprise application containers and services based
on, but not limited to the Enterprise JavaBeans Specification and Java
Enterprise Edition Specifications.
## Health
Both the dev@ and user@ mailing lists have seen increased traffic over the
last quarter, with messages numbers up 20% and 100% on the two lists
respectively compared with the previous quarter. The project tends to see
increased activity over the Christmas period with new users and contributors
trying the project out for the first time over the holidays.
## Activity
The community released TomEE 8.0.0 in September, after 3 milestoned
releases. The TomEE 8 branch targets compliance with Jakarta EE 8. Although
compliance has not yet been achieved with the Web MicroProfile it is deemed
production ready. TomEE 8 runs on both Java SE 8 and Java SE 11.
Work continues to achieve full Jakarta EE 8 Web Profile compliance.
The community is about to release 7.1.2 and 7.0.7 maintenance releases which
provide dependency updates and bug fixes.
The dependency updates mitigate CVE issues in upstream components, including
Jackson-Databind, Commons-Beanutils and Mojarra:
CVE-2019-17091 (XSS in Mojarra)
CVE-2019-13990 (XXE in Quartz)
CVE-2019-10086 (ability for an attacker to access the classloader
via the class property in commons-beanutils)
Additionally, these will include fixes from commons-daemon for JVM crashes
with X86 JVMs on certain X64 Windows servers, and fixes for transaction
handling with JMS2.
## PMC changes:
- Currently 11 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Andy Gumbrecht on Tue Aug 11 2015
## Committer base changes:
- Currently 31 committers.
- Last committer added was Cesar Hernandez on July 1st 2019.
## Releases:
- Apache TomEE 8.0.0 on September 16, 2019
-----------------------------------------
Attachment BR: Report from the Apache Traffic Control Project [David Neuman]
## Description:
The mission of Apache Traffic Control is the creation and maintenance of
software related to building, monitoring, configuring, and provisioning large
scale content delivery networks (CDN)
## Issues:
There are no issues requiring board attention at this time.
## Membership Data:
Apache Traffic Control was founded 2018-05-15 (a year and a half 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 Derek Gelinas on 2019-03-17.
- No new committers. Last addition was Brennan Fieck on 2019-07-26.
## Project Activity:
Took part in ApacheCon NA as part of the Content Delivery Track. This was a
great experience for our community and something we look forward to doing
again.
Release Apache Traffic Control 3.0.2 to address a security issue.
Released Apache Traffic Control 3.1.0
## Community Health:
The community is healthy! We have definitely seen the "post summit bump" where
the community gets re-invested after a conference/summit that has lead us to
having more contributions and activity on the mailing lists. We are starting
to become more mature as a community by agreeing to get better at how we do
releases and working towards a more consistent cadence.
-----------------------------------------
Attachment BS: Report from the Apache Turbine Project [Georg Kallidis]
## Description:
The mission of Turbine is the creation and maintenance of software related
to a Java Servlet Web Application Framework and associated component library.
Turbine is a matured and well established framework that is used as the
base of many other projects. It allows experienced Java developers to quickly
build web applications.
## Issues:
- The SVN-GIT Mirror was reactivated again successfully.
## Membership Data:
- Apache Turbine was founded 2007-05-16 (12 years ago)
- There are currently 11 committers and 9 PMC members in this project. The
Committer-to-PMC ratio is roughly 6:5.
Community changes, past quarter:
- No new PMC members. Last addition was Jeffery Painter on 2017-11-12.
- No new committers were added.
## Project Activity:
- Hackathon took place at Apache Europe and was attended by two PMC members.
Focus has been on upstream component Apache Torque 4.1 (version label may be
changed to 5.0) and finally Turbine 5.
- Java Docker Testcontainer integration in Turbine 5 (and prospectively
Torque-Test)
- Discussions about Turbine pipeline components
- Last quarters backlog / discussion are still in follow-up work/work in
process.
- No releases were done this quarter.
## Community Health:
- The Turbine project's quarter activity has been mainly in the dev
mailing list with ongoing code changes on low/medium level.
-----------------------------------------
Attachment BT: Report from the Apache Usergrid Project [Michael Russo]
## Description:
The mission of Usergrid is the creation and maintenance of software related to
The BaaS Framework you run
## Issues:
- There are no issues requiring board attention at this time.
## Membership Data:
Apache Usergrid was founded 2015-08-18 (4 years ago)
There are currently 28 committers and 25 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 Mike Dunker on 2016-01-18.
- No new committers. Last addition was Keyur Karnik on 2019-03-18.
## Project Activity:
- CI setup with ASF Jenkins still in progress. Daily builds are in place but
configuration needs to be investigated as builds are not green.
- Various Bugfixes around index querying and maintenance.
- Improved test stability.
- Experimentation with using newer versions(5.x) of Elasticsearch vs.
supported older version (1.7).
## Community Health:
Growth is flat. Some of the historical core contributors are no longer active
with the project. However, there is a new committer and additional interest
for modernizing Usergrid -- upgrading Cassandra to the latest version and
containerizing Usergrid. Getting the project to a healthier state will
continue to be a focus. This includes more discussion on the mailing lists,
better use of JIRA, and planning of a new release -- master branch is
currently stable and contains many stability fixes over the last release in
2016.
-----------------------------------------
Attachment BU: Report from the Apache Velocity Project [Nathan Bubna]
## Description:
The mission of Velocity is the creation and maintenance of software related to
A Java Templating Engine
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache Velocity was founded 2006-10-24 (13 years ago)
There are currently 14 committers and 9 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:5.
Community changes, past quarter:
- No new PMC members. Last addition was Michael Osipov on 2017-07-27.
- No new committers. Last addition was Michael Osipov on 2017-01-30.
## Project Activity:
VelocityTools has seen some light improvements. Our Maven build infrastructure
has gotten a few patches. Velocity Engine 2.2rc1 is out with some nice log,
custom parser, and backwards-compatibility improvements. It has received two
PMC votes for GA release. It is waiting on a third.
## Community Health:
We are getting community input and contributions, but development is still
largely handled by a single PMC member. Dormant PMC members also outnumber
active ones. As the project is extremely stable by intent, the minimal
committer activity is appropriate, but it should not take this long to get
more PMC response on a release candidate quality.
-----------------------------------------
Attachment BV: Report from the Apache Whimsy Project [Sam Ruby]
## Description:
The mission of Apache Whimsy is the creation and maintenance of software
related to tools that help automate various administrative tasks or information
lookup activities
## Issues:
I (Sam) remain concerned that there are not enough developers on the board
agenda tool. Current status is that if something is broken, the fix waits
until I am available. For things that are not broken but merely are feature
requests, I tend to respond with pointers to how/where the fix needs to be
made, and generally that's as far as it goes. Given how important this
particular tool is to the foundation, this represents a "bus factor" concern.
Tools other than the board agenda tool have multiple people who attend to
problems and suggestions.
## Membership Data:
Apache Whimsy was founded 2015-05-19 (4 years ago)
There are currently 10 committers and 9 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 John D. Ament on 2017-06-11.
- No new committers. Last addition was John D. Ament on 2017-06-08.
## Project Activity:
Notable changes over the last quarter:
* Updates to the MACOSX developer instructions.
* Updates to agenda template and logic to reflect new Zoom and Directors.
* Increased test coverage
* Centralized unsubscribable checks
* Move away from usage of .archives
* Bug fixes: terminate resolution and time zones
* Strengthen non-standard resolution checks
* Allow directors to update the board list in the roster tool
* Update collate minute tool and incubator signoff tool to handle Wiki markup
in the incubator report
## Community Health:
More than enough oversight, no new committers for over two years.
One tool (as noted above) has a bus factor isssue.
-----------------------------------------
Attachment BW: Report from the Apache Xalan Project [Gary D. Gregory]
## Description:
Apache Xalan exists to promote the use of XSLT. We view XSLT (Extensible
Stylesheet Language Transformations) as a compelling paradigm that transforms
XML documents, thereby facilitating the exchange, transformation, and
presentation of knowledge. The ability to transform XML documents into usable
information has great potential to improve the functionality and use of
information systems. We intend to build freely available XSLT processing
components in order to engender such improvements.
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache Xalan was founded 2004-09-30 (15 years ago)
There are currently 57 committers and 5 PMC members in this project.
The Committer-to-PMC ratio is roughly 8:1.
Community changes, past quarter:
- No new PMC members. Last addition was Bill Blough on 2019-02-19.
- No new committers. Last addition was Bill Blough on 2019-03-20.
## Project Activity:
No significant activities to report. No new releases.
## Community Health:
The project is not really active at the moment, there is a desire to create a
release but nothing's happened yet. Low mailing list activity aside from a ton
of SPAM I must reject every day.
-----------------------------------------
Attachment BX: Report from the Apache Xerces Project [Michael Glavassevich]
-----------------------------------------
Attachment BY: Report from the Apache XML Graphics Project [Clay Leeds]
Apache XML Graphics Project Board Report
==================================
The Apache XML Graphics Project is responsible for software intended for the
creation & maintenance of the conversion of XML formats to graphical output &
related software components.
ISSUES FOR THE BOARD
=====================
No issues at present.
ACTIVITY
========
* Apache Batik 1.12
* Apache FOP 2.4
* Apache XML Graphics Commons 2.4
PROJECT HEALTH REPORT
=======================
The level of community and developer activity remains at a consistent,
moderate, level with respect to the previous reporting period.
RECENT PMC CHANGES
==================
Currently 11 PMC members.
* Simon Steiner was added to the PMC on Tue Jan 19 2016
* Clay Leeds became XML Graphics PMC Chair on March 26, 2018
Committers
==========
Currently 21 committers.
* No new committers added in the last 3 months
* Former PMC member Glenn Adams is re-engaging in the project
* Last committer added was Matthias Reischenbacher at Wed May 13 2015
Most Recent Releases
====================
* XMLGraphics Commons 2.4 was released on Sat October 31, 2019
* XMLGraphics FOP 2.4 was released on Sat October 31, 2019
* XMLGraphics Batik 1.12 was released on Sat October 31, 2019
= SUB PROJECTS =
================
XML GRAPHICS COMMONS
====================
Community activity was light, although there were a few bugs resolved.
New Release?
------------
XMLGraphics Commons 2.4 was released on Sat October 31, 2019
Latest Release
--------------
XML Graphics Commons 2.4 was released on Sat October 31, 2019
FOP
===
A number of patches have been processed into TRUNK and several bugs fixed.
New Release?
------------
XMLGraphics FOP 2.4 was released on Sat October 31, 2019
Latest Release
--------------
XML Graphics FOP 2.4 was released on Sat October 31, 2019
BATIK
=====
Apache Batik 1.12 was released on Sat October 31, 2019
New Release?
------------
Apache Batik 1.12 was released on Sat October 31, 2019
Latest Release
--------------
Apache Batik 1.12 was released on Sat October 31, 2019
-----------------------------------------
Attachment BZ: Report from the Apache Zeppelin Project [Lee Moon Soo]
## Description:
- Apache Zeppelin is a collaborative data analytics and visualization tool
for general-purpose data processing systems.
## Issues:
- PMCs are trying to fix and announce security issues that have been
addressed and released. Most of them are PR ready, waiting for review and
get merged. We are sorry that we didn't pay much attention on this instead
of working new features. We would fix them by the end of this year when we
plan to make the next release 0.9
## Activity:
- Jetbrain integrate Zeppelin into their IDEA plugin Big data tools, we are
working closely with Jetbrain on this.
- There're 2 major frontend rework in community, one is via VUE, another is
via Angular. These work will improve the frontend user experience of
Zeppelin much. We expect user can experience these new changes pretty
soon(maybe next release)
- And we plan to move the frontend modules into sub projects of Zeppelin, so
that we can make Zeppelin frontend more pluggable and customizable.
- Several new interpreters are added, KSQL, Kotlin(in review)
Overall the ecosystem of Zeppelin is pretty healthy in our perspective.
## Health report:
- +4 new code contributors since last report. 291 total
## PMC changes:
- Currently 11 PMC members.
- Last PMC addition was Jeff Zhang on Thu Jan 25 2018
## Committer base changes:
- Currently 18 committers.
- Last committer addition was Xun Liu at April 18 2019
## Releases:
- 0.8.2 was released on Wed Sep 29 2019
- 0.8.1 was released on Wed Jan 23 2019
- 0.8.0 was released on Wed Jul 18 2018
- 0.7.3 was released on Wed Sep 20 2017
- 0.7.2 was released on Mon Jun 12 2017
- 0.7.1 was released on Fri Mar 31 2017
- 0.7.0 was released on Sun Feb 05 2017
- 0.6.2 was released on Fri Oct 14 2016
- 0.6.1 was released on Aug 15 2016
- 0.6.0 was released on Jul 02 2016
- 0.5.6-incubating was released on Jan 22 2016
- 0.5.5-incubating was released on Nov 18 2015
- 0.5.0-incubating was released on Jul 23 2015
## Mailing list activity:
- users@zeppelin.apache.org:
- 237 emails sent to list ( 153 in previous quarter)
- dev@zeppelin.apache.org:
- 1182 emails sent to list ( 947 in previous quarter)
## JIRA activity:
- 143 JIRA tickets created in the last 3 months
------------------------------------------------------
End of minutes for the November 20, 2019 board meeting.
Index