Index
Links: 2019 - All years
- Original The Apache Software Foundation
Board of Directors Meeting Minutes
September 18, 2019
1. Call to order
The meeting was scheduled for 10:30am Pacific and began at 10:31
when a sufficient attendance to constitute a quorum was
recognized by the chairman.
Other Time Zones: https://timeanddate.com/s/3yvr
The meeting was held via teleconference, hosted by Doug Cutting
and Cloudera.
IRC #asfboard on irc.freenode.net was used for backup purposes.
2. Roll Call
Directors Present:
Danny Angus - disconnected at 11:20 PDT
Rich Bowen
Shane Curcuru
Ted Dunning
Myrle Krantz
Daniel Ruggeri
Roman Shaposhnik
Joan Touzet
Directors Absent:
Craig L Russell
Executive Officers Present:
David Nalley
Tom Pappas
Sam Ruby
Matt Sicker
Executive Officers Absent:
none
Guests:
Daniel Gruno
Greg Stein
Jim Jagielski
Kevin A. McGrail - left at 11:26 PDT
Paul Angus
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 August 21, 2019
See: board_minutes_2019_08_21.txt
Approved by General Consent.
4. Executive Officer Reports
A. Chairman [Craig]
Kudos to the ApacheCon NA 2019 planning and execution team for a
well-organized event in Las Vegas.
A number of board members were able to attend the celebration and had
many informal chats about how to work better together. No official
meeting was held.
Several of the IPMC members met with some of the podlings with a large
Chinese membership and we discussed some of the challenges of
integrating The Apache Way into the Chinese culture. Social barriers
include the preference for synchronous social media communications and
technical barriers include the sad performance of apache.org web sites
in China mainland.
The incubator DISCLAIMER-WIP was informally approved by the board to
make it easier for podlings to make early releases that are not in
accordance with a standard Apache release while making it clear to
downstream users that there are unresolved issues.
We're looking forward to another great ApacheCon EU next month in
Berlin.
B. President [Sam]
Financially we are ahead on revenue and behind on expenses. Timing
considerations may moderate this a bit, but we are doing well.
The most notable activity this month was ACNA which involved the
coordination of a number of operational areas. Otherwise a mostly
quiet month, where quiet is good.
No significant issues in Brand Management, Marketing and Publicity,
Finance, and Diversity and Inclusion.
Fundraising is exploring changing no-follow policy for bronze sponsors
in response to a blog entry describing the ASF as selling links for
SEO purposes.
Conferences is exploring ways to manage costs for the ACEU.
Additionally, please see Attachments 1 through 8.
@Roman: Update docs around legal FAQ
C. Treasurer [Ulrich]
Operating Cash on August 31st, 2019 was $2,450.4K, which is down
$22.6K from last month’s ending balance (Jul 19) of $2,473.1K. Total
Cash as of August 31st, 2019 is $3,844.3K (includes the Pineapple and
restricted Donation) as compared to $3,448.1K on August 31st 2018 (an
increase of $396.2K year over year). The August 2019 ending Operating
cash balance of $2,450.4K represents an Operating cash reserve of 9.9
months based on the FY20 Cash forecast average monthly spending of
$246.8K/month. The ASF actual Operating reserve of 9.9 months at the
end of August 2019 is ahead of the budgeted 7.1 month’s reserve for
YTD through August 2019. The ASF Operating reserve continues to be
very healthy for an organization of the ASF’s size and Operating
activity.
Reviewing the YTD Cash P&L, total Income is ahead of budget at this
point in the Fiscal year by $138.0K. As compared to FY19, YTD revenue
is ahead by $133.2K primarily due to Conference income year over year
at this point in time.
YTD expenses through August 31, 2019 are under budget by $530.9K. All
departments are either under budget or showing minor variances, which
is primarily due to timing of payments for depts. Conferences
expenses at this point are under budget due to timing and it is
expected to normalize over the next two months as ACNA and ACEU are
happening in September and October, respectively.
Regarding Net Income (NI), YTD FY20 the ASF finished with a positive
$30.1K NI vs a budgeted negative <$638.8K> NI or $668.9K ahead of
Budgeted NI for FY20 at this point in the Fiscal year. This is
attributable to timing of Conference payments, Timing of TAC as well
as underspending in most depts YTD vs the FY20 Budget. At this point
in the FY we are doing very well, ahead in Revenue and well under
budget in Expenses, even taking timing variances into account. With
regard to FY19, we are outpacing revenue, by $133.2K as noted above,
but we are also out pacing ahead on expenses by $104.4K; thus, year
over year NI for FY20 is ahead of FY19 by $28.8K.
I would like to inform the board that I am stepping down from the
office of the Treasurer effective Oct 31st 2019. I ask the board to
appoint a successor as soon as possible to ensure a smooth and
orderly handover of duties.
Current Balances:
Boston Private CDARS Account 2,261,344.76
Citizens Money Market 1,089,390.13
Citizens Checking 491,895.04
Paypal - ASF 1,676.13
Total Checking/Savings 3,844,306.06
Aug-19 Budget Variance
Income Summary:
Inkind Revenue 0.00 0.00 0.00
Public Donations 1,675.67 72,454.00 -70,778.33
Sponsorship Program 72,000.00 25,000.00 47,000.00
Programs Income 0.00 0.00 0.00
Conference/Event Income 61,729.96 91,000.00 -29,270.04
Other Income 591.92 18,506.00 -17,914.08
Interest Income 291.63 450.00 -158.37
Total Income 136,289.18 207,410.00 -71,120.82
Expense Summary
In Kind Expense 0.00 0.00 0.00
Infrastructure 83,774.73 107,733.08 -23,958.35
Programs Expense 0.00 3,333.33 -3,333.33
Publicity 31,182.37 52,733.34 -21,550.97
Brand Management 3,298.85 8,166.67 -4,867.82
Conferences 7,726.45 211,250.00 -203,523.55
Travel Assistance Committee 13,967.56 20,000.00 -6,032.44
Fundraising 11,494.76 16,080.00 -4,585.24
Treasury Services 3,350.00 3,350.00 0.00
General & Administrative 4,149.16 1,915.00 2,234.16
Diversity and Inclusion 0.00 5,833.33 -5,833.33
Total Expense 158,943.88 430,394.75 -271,450.87
Net Income -22,654.70 -222,984.75 200,330.05
YTD FY20 Budget Variance
Income Summary:
Inkind Revenue 0.00 0.00 0.00
Public Donations 7,887.60 79,210.48 -71,322.88
Sponsorship Program 302,000.00 287,000.00 15,000.00
Programs Income 0.00 0.00 0.00
Conference/Event Income 358,595.96 151,000.00 207,595.96
Other Income 7,718.59 20,788.40 -13,069.81
Interest Income 1,598.72 1,800.00 -201.28
Total Income 677,800.87 539,798.88 138,001.99
Expense Summary
In Kind Expense 0.00 0.00 0.00
Infrastructure 318,125.57 364,932.32 -46,806.75
Programs Expense 0.00 13,333.32 -13,333.32
Publicity 148,438.42 147,508.36 930.06
Brand Management 8,724.29 32,666.68 -23,942.39
Conferences 80,539.62 437,000.00 -356,460.38
Travel Assistance Committee 13,967.56 70,000.00 -56,032.44
Fundraising 51,762.27 64,320.00 -12,557.73
Treasury Services 13,400.00 13,400.00 0.00
General & Administrative 12,721.73 12,160.00 561.73
Diversity and Inclusion 0.00 23,333.32 -23,333.32
Total Expense 647,679.46 1,178,654.00 -530,974.54
Net Income 30,121.41 -638,855.12 668,976.53
@Myrle: look for a new assistant treasurer
D. Secretary [Matt]
In the month of August, we received 75 ICLAs, two CCLAs, one software
grant. GPG key verification using the recent Whimsy updates continues
to work rather reliably.
E. Executive Vice President [David]
I attended ApacheCon NA and found the conference to be well produced.
ApacheCon NA allowed me to have a number of good conversations with
members, committers, contributors, and sponsors.
As promised in last month's Board report, Tom and I spent time talking
about a call list and service level expectations for Virtual at
ApacheCon. We think we have a workable path forward with his key
deputies identified and a plan for how to cascade down the list. More
to come on this front, but I am substantially less worried now about
Tom as a SPoF for our connection to Virtual.
I've also asked Tom to look into travel insurance to cover employees
and officers who are traveling on behalf of the Foundation. The
current situation is that we are covering the employees provided to us
via Virtual's PEO, but not the contractors or officers. Tom's
researching this, expect it to land on operations@ after he has a few
answers.
TAC
===
TAC executed well at ACNA. ACEU is already lined up and appears to
be progressing well.
Infra
=====
Infra is overall running well. Infra had a presence at ACNA and had a
number of conversations with users and moved a number of projects
forward while in-person.
Git.a.o suffered an outage which is ongoing. This service translates
svn to git, and then mirrors that to Github. The outage was caused by
a service provider catastrophically losing storage that we consumed.
This was a widespread outage that affected a number of users other
than us. This service dates back to our earliest experimentation with
git. With our advent of writable git repos and gitbox/github
integration a good chunk of the functionality this service provided
has been obviated. Projects have been asked to tell us if they are
still making use of the service, and restoring just the portions that
remained needed and utilized.
F. Vice Chairman [Shane]
No specific Apache activity this month.
Executive officer reports approved as submitted by General Consent.
5. Additional Officer Reports
A. VP of W3C Relations [Andy Seaborne / Danny]
See Attachment 9
B. Apache Legal Affairs Committee [Roman Shaposhnik]
See Attachment 10
C. Apache Security Team Project [Mark J. Cox / Joan]
See Attachment 11
D. VP of Data Privacy [John Kinsella / Ted]
See Attachment 12
E. VP of Jakarta EE Relations [Mark Struberg / Myrle]
See Attachment 13
Additional officer reports approved as submitted by General Consent.
6. Committee Reports
Summary of Reports
The following reports required further discussion:
# Diversity and Inclusion [rs]
# Eagle [myrle]
# Lucene.Net [rb]
# Royale [myrle]
A. Apache Airflow Project [Bolke de Bruin / Roman]
See Attachment A
B. Apache Allura Project [David Philip Brondsema / Rich]
See Attachment B
C. Apache Any23 Project [Lewis John McGibbney / Shane]
See Attachment C
D. Apache Archiva Project [Olivier Lamy / Daniel]
See Attachment D
E. Apache Atlas Project [Madhan Neethiraj / Craig]
See Attachment E
F. Apache Aurora Project [Jake Farrell / Rich]
See Attachment F
G. Apache Axis Project [Robert Lazarski / Roman]
See Attachment G
H. Apache Bahir Project [Luciano Resende / Joan]
See Attachment H
I. Apache Beam Project [Kenneth Knowles / Ted]
See Attachment I
J. Apache Bigtop Project [Youngwoo Kim / Craig]
See Attachment J
K. Apache Bloodhound Project [Gary Martin / Shane]
No report was submitted.
L. Apache BVal Project [Matthew Jason Benson / Danny]
See Attachment L
M. Apache Camel Project [Andrea Cosentino / Daniel]
See Attachment M
N. Apache Cayenne Project [Michael Ray Gentry / Myrle]
See Attachment N
O. Apache Chemistry Project [Florian Müller / Craig]
See Attachment O
P. Apache CloudStack Project [Paul Angus / Rich]
See Attachment P
Q. Apache Commons Project [Gary D. Gregory / Danny]
See Attachment Q
R. Apache Cordova Project [Jesse MacFadyen / Ted]
See Attachment R
S. Apache cTAKES Project [Pei Chen / Shane]
See Attachment S
T. Apache Curator Project [Jordan Zimmerman / Roman]
See Attachment T
U. Apache DeltaSpike Project [Mark Struberg / Daniel]
See Attachment U
V. Apache Eagle Project [Edward Zhang / Myrle]
See Attachment V
W. Apache Falcon Project [Pallavi Rao / Daniel]
No report was submitted.
@Sam: get records updated @Daniel: get project moved to Attic
X. Apache Felix Project [Karl Pauls / Roman]
See Attachment X
Y. Apache Flex Project [Olaf Krüger / Rich]
See Attachment Y
Z. Apache Flink Project [Stephan Ewen / Shane]
See Attachment Z
AA. Apache Guacamole Project [Mike Jumper / Ted]
See Attachment AA
AB. Apache Gump Project [Stefan Bodewig / Craig]
See Attachment AB
AC. Apache Hama Project [Chia-Hung Lin / Ted]
No report was submitted.
@Ted: pursue Atticking
AD. Apache Helix Project [Kishore G / Myrle]
No report was submitted.
@Myrle: pursue a report for Helix
AE. Apache Hive Project [Ashutosh Chauhan / Joan]
See Attachment AE
@Joan: pursue a report for Helix next month
AF. Apache Incubator Project [Justin Mclean / Daniel]
See Attachment AF
AG. Apache Jackrabbit Project [Marcel Reutegger / Craig]
See Attachment AG
AH. Apache Karaf Project [Jean-Baptiste Onofré / Myrle]
See Attachment AH
AI. Apache Labs Project [Danny Angus]
See Attachment AI
AJ. Apache Lucene Project [Cassandra Targett / Danny]
See Attachment AJ
AK. Apache Lucene.Net Project [Shad Storhaug / Rich]
No report was submitted.
@Rich: pursue a report for Lucene.Net
AL. Apache Mesos Project [Benjamin Hindman / Joan]
See Attachment AL
AM. Apache Mnemonic Project [Gang Wang / Ted]
See Attachment AM
AN. Apache Mynewt Project [Justin Mclean / Daniel]
No report was submitted.
@Daniel: pursue a report for Mynewt
AO. Apache NetBeans Project [Geertjan Wielenga / Roman]
See Attachment AO
AP. Apache OFBiz Project [Jacopo Cappellato / Joan]
See Attachment AP
AQ. Apache Olingo Project [Michael Bolz / Daniel]
See Attachment AQ
AR. Apache OODT Project [Imesha Sudasingha / Joan]
See Attachment AR
AS. Apache OpenNLP Project [Jörn Kottmann / Craig]
No report was submitted.
@Craig: pursue a report for OpenNLP
AT. Apache OpenWebBeans Project [Mark Struberg / Danny]
See Attachment AT
AU. Apache OpenWhisk Project [Dave Grove / Rich]
See Attachment AU
AV. Apache Pig Project [Koji Noguchi / Ted]
See Attachment AV
AW. Apache Pivot Project [Roger Lee Whitcomb / Myrle]
See Attachment AW
AX. Apache PLC4X Project [Christofer Dutz / Roman]
See Attachment AX
AY. Apache Portable Runtime (APR) Project [Nick Kew / Shane]
See Attachment AY
AZ. Apache Portals Project [David Sean Taylor / Danny]
See Attachment AZ
BA. Apache PredictionIO Project [Donald Szeto / Myrle]
See Attachment BA
BB. Apache Pulsar Project [Matteo Merli / Rich]
See Attachment BB
BC. Apache Royale Project [Piotr Zarzycki / Craig]
See Attachment BC
@Myrle: follow up about build server breach
BD. Apache Sentry Project [Kalyan Kalvagadda / Daniel]
See Attachment BD
BE. Apache ServiceMix Project [Krzysztof Sobkowiak / Roman]
See Attachment BE
BF. Apache Shiro Project [Les Hazlewood / Joan]
See Attachment BF
BG. Apache Sling Project [Robert Munteanu / Shane]
See Attachment BG
BH. Apache SpamAssassin Project [Sidney Markowitz / Ted]
No report was submitted.
@Kevin: pursue a report for SpamAssassin
BI. Apache Stanbol Project [Rafa Haro / Joan]
No report was submitted.
@Joan: pursue a report for Stanbol
BJ. Apache Storm Project [P. Taylor Goetz / Rich]
See Attachment BJ
BK. Apache Synapse Project [Isuru Udana / Craig]
See Attachment BK
BL. Apache Tajo Project [Hyunsik Choi / Ted]
No report was submitted.
@Ted: pursue a report for Tajo
BM. Apache Tapestry Project [Thiago Henrique De Paula Figueiredo / Shane]
See Attachment BM
BN. Apache Tomcat Project [Mladen Turk / Daniel]
See Attachment BN
BO. Apache Trafodion Project [Pierre Smits / Myrle]
See Attachment BO
BP. Apache Twill Project [Terence Yim / Danny]
See Attachment BP
BQ. Apache UIMA Project [Marshall Schor / Roman]
See Attachment BQ
BR. Apache Unomi Project [Serge Huber / Danny]
See Attachment BR
BS. Apache VCL Project [Josh Thompson / Joan]
See Attachment BS
BT. Apache Wicket Project [Andrea Del Bene / Ted]
See Attachment BT
BU. Apache Xerces Project [Michael Glavassevich / Ted]
See Attachment BU
BV. Apache Yetus Project [Allen Wittenauer / Shane]
See Attachment BV
BW. Apache ZooKeeper Project [Flavio Paiva Junqueira / Craig]
See Attachment BW
Committee reports approved as submitted by General Consent.
7. Special Orders
A. Change the Apache Kylin Project Chair
WHEREAS, the Board of Directors heretofore appointed Luke Han (lukehan)
to the office of Vice President, Apache Kylin, and
WHEREAS, the Board of Directors is in receipt of the resignation of
Luke Han from the office of Vice President, Apache Kylin, and
WHEREAS, the Project Management Committee of the Apache Kylin project
has chosen by vote to recommend Shao Feng Shi (shaofengshi) as the
successor to the post;
NOW, THEREFORE, BE IT RESOLVED, that Luke Han is relieved and
discharged from the duties and responsibilities of the office of Vice
President, Apache Kylin, and
BE IT FURTHER RESOLVED, that Shao Feng Shi be and hereby is appointed
to the office of Vice President, Apache Kylin, 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 Kylin Project Chair, was
approved by Unanimous Vote of the directors present.
B. Change the Apache Avro Project Chair
WHEREAS, the Board of Directors heretofore appointed Thiruvalluvan M.
G. (thiru) to the office of Vice President, Apache Avro, and
WHEREAS, the Board of Directors is in receipt of the resignation of
Thiruvalluvan M. G. from the office of Vice President, Apache Avro, and
WHEREAS, the Project Management Committee of the Apache Avro project
has chosen by vote to recommend Sean Busbey (busbey) as the successor
to the post;
NOW, THEREFORE, BE IT RESOLVED, that Thiruvalluvan M. G. is relieved
and discharged from the duties and responsibilities of the office of
Vice President, Apache Avro, and
BE IT FURTHER RESOLVED, that Sean Busbey be and hereby is appointed to
the office of Vice President, Apache Avro, to serve in accordance with
and subject to the direction of the Board of Directors and the Bylaws
of the Foundation until death, resignation, retirement, removal or
disqualification, or until a successor is appointed.
Special Order 7B, Change the Apache Avro Project Chair, was
approved by Unanimous Vote of the directors present.
C. Change the Apache Johnzon Project Chair
WHEREAS, the Board of Directors heretofore appointed Hendrik Saly
(salyh) to the office of Vice President, Apache Johnzon, and
WHEREAS, the Board of Directors is in receipt of the resignation of
Hendrik Saly from the office of Vice President, Apache Johnzon, and
WHEREAS, the Project Management Committee of the Apache Johnzon project
has chosen by vote to recommend Romain Manni-Bucau (rmannibucau) as the
successor to the post;
NOW, THEREFORE, BE IT RESOLVED, that Hendrik Saly is relieved and
discharged from the duties and responsibilities of the office of Vice
President, Apache Johnzon, and
BE IT FURTHER RESOLVED, that Romain Manni-Bucau be and hereby is
appointed to the office of Vice President, Apache Johnzon, 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 Johnzon Project Chair, was
approved by Unanimous Vote of the directors present.
D. Change the Apache Aurora Project Chair
WHEREAS, the Board of Directors heretofore appointed Jake Farrell
(jfarrell) to the office of Vice President, Apache Aurora, and
WHEREAS, the Board of Directors is in receipt of a request from Apache
Aurora to change their Vice President, and
WHEREAS, the Project Management Committee of the Apache Aurora project
has chosen by vote to recommend Renan DelValle (renan) as the successor
to the post;
NOW, THEREFORE, BE IT RESOLVED, that Jake Farrell is relieved and
discharged from the duties and responsibilities of the office of Vice
President, Apache Aurora, and
BE IT FURTHER RESOLVED, that Renan DelValle be and hereby is appointed
to the office of Vice President, Apache Aurora, 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 Aurora Project Chair, was
approved by Unanimous Vote of the directors present.
E. Terminate the Apache Apex Project
WHEREAS, the Project Management Committee of the Apache Apex project
has chosen by vote to recommend moving the project to the Attic; and
WHEREAS, the Board of Directors deems it no longer in the best interest
of the Foundation to continue the Apache Apex project due to
inactivity;
NOW, THEREFORE, BE IT RESOLVED, that the Apache Apex project is hereby
terminated; and be it further
RESOLVED, that the Attic PMC be and hereby is tasked with oversight
over the software developed by the Apache Apex Project; and be it
further
RESOLVED, that the office of "Vice President, Apache Apex" is hereby
terminated; and be it further
RESOLVED, that the Apache Apex PMC is hereby terminated.
Special Order 7E, Terminate the Apache Apex Project, was
approved by Unanimous Vote of the directors present.
F. Change the Apache Mesos Project Chair
WHEREAS, the Board of Directors heretofore appointed Benjamin Hindman
(benh) to the office of Vice President, Apache Mesos, and
WHEREAS, the Board of Directors is in receipt of the resignation of
Benjamin Hindman from the office of Vice President, Apache Mesos, and
WHEREAS, the Project Management Committee of the Apache Mesos project
has chosen by vote to recommend Vinod Kone (vinodkone) as the successor
to the post;
NOW, THEREFORE, BE IT RESOLVED, that Benjamin Hindman is relieved and
discharged from the duties and responsibilities of the office of Vice
President, Apache Mesos, and
BE IT FURTHER RESOLVED, that Vinod Kone be and hereby is appointed to
the office of Vice President, Apache Mesos, to serve in accordance with
and subject to the direction of the Board of Directors and the Bylaws
of the Foundation until death, resignation, retirement, removal or
disqualification, or until a successor is appointed.
Special Order 7F, Change the Apache Mesos Project Chair, was
approved by Unanimous Vote of the directors present.
G. Establish the Apache Submarine Project
WHEREAS, the Board of Directors deems it to be in the best interests of
the Foundation and consistent with the Foundation's purpose to
establish a Project Management Committee charged with the creation and
maintenance of open-source software, for distribution at no charge to
the public, related to allowing infrastructure engineers and data
scientists to build deep learning applications (TensorFlow, PyTorch,
etc.) end to end on cluster management platforms (like YARN/K8s).
NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
(PMC), to be known as the "Apache Submarine Project", be and hereby is
established pursuant to Bylaws of the Foundation; and be it further
RESOLVED, that the Apache Apache Submarine be and hereby is responsible
for the creation and maintenance of software related to allowing
infrastructure engineers and data scientists to build deep learning
applications (TensorFlow, PyTorch, etc.) end to end on cluster
management platforms (like YARN/K8s); and be it further
RESOLVED, that the office of "Vice President, Apache Submarine" 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
Submarine Project, and to have primary responsibility for management of
the projects within the scope of responsibility of the Apache Submarine
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 Submarine
Project:
* Sunil G <sunilg@apache.org>
* Owen O'Malley <omalley@apache.org>
* Wangda Tan <wangda@apache.org>
* Zhankun Tang <ztang@apache.org>
* Liu Xun <liuxun@apache.org>
NOW, THEREFORE, BE IT FURTHER RESOLVED, that Wangda Tan be appointed to
the office of Vice President, Apache Submarine, 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.
RESOLVED, that the Apache Submarine Project be and hereby is tasked with
the migration and rationalization of the Apache Hadoop Submarine
sub-project; and be it further
RESOLVED, that all responsibilities pertaining to the Apache Hadoop
Submarine sub-project encumbered upon the Apache Hadoop Project are
hereafter discharged.
Special Order 7G, Establish the Apache Submarine Project, was
tabled.
H. Establish the Apache Rya Project
WHEREAS, the Board of Directors deems it to be in the best interests
of the Foundation and consistent with the Foundation's purpose to
establish a Project Management Committee charged with the creation and
maintenance of open-source software, for distribution at no charge to
the public, related to scalable storage, retrieval, and analysis of
RDF data.
NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
(PMC), to be known as the "Apache Rya Project", be and hereby is
established pursuant to Bylaws of the Foundation; and be it further
RESOLVED, that the Apache Rya Project be and hereby is responsible for
the creation and maintenance of software related to scalable storage,
retrieval, and analysis of RDF data; and be it further
RESOLVED, that the office of "Vice President, Apache Rya" 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 Rya
Project, and to have primary responsibility for management of the
projects within the scope of responsibility of the Apache Rya 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 Rya Project:
* Aaron Mihalik <mihalik@apache.org>
* Adina Crainiceanu <adina@apache.org>
* Billie Rinaldi <billie@apache.org>
* Caleb Meier <caleb@apache.org>
* David Lotts <dlotts@apache.org>
* David Rapp <dnrapp@apache.org>
* Jennifer Brown <jbrown@apache.org>
* Josh Elser <elserj@apache.org>
* Puja Valiyil <pujav65@apache.org>
* Roshan Punnoose <roshanp@apache.org>
* Steve R Wagner <swagner@apache.org>
NOW, THEREFORE, BE IT FURTHER RESOLVED, that Adina Crainiceanu be
appointed to the office of Vice President, Apache Rya, to serve in
accordance with and subject to the direction of the Board of Directors
and the Bylaws of the Foundation until death, resignation, retirement,
removal or disqualification, or until a successor is appointed; and be
it further
RESOLVED, that the Apache Rya Project be and hereby is tasked with the
migration and rationalization of the Apache Incubator Rya podling; and
be it further
RESOLVED, that all responsibilities pertaining to the Apache Incubator
Rya podling encumbered upon the Apache Incubator PMC are hereafter
discharged.
Special Order 7H, Establish the Apache Rya Project, was
approved by Unanimous Vote of the directors present.
8. Discussion Items
A. Bitergia contract for D&I projects: Survey Design + Contributor Experience Research
I'd like to get input from Roman/Tom on the contract I sent. It's fairly
straight forward and looks good to me, however I have outstanding
questions and would like to discuss them.
9. Review Outstanding Action Items
* Rich: open up attic discussions to dev list
[ Forrest 2019-05-15 ]
Status: There are still no responses to my email to the dev list -
https://lists.apache.org/thread.html/fda24957e049f10d282037594d2aa61ce9a31cf8fc5313959aa81672@%3Cdev.forrest.apache.org%3E
- and no discussion about retirement on the private@ list.
Recommend that we draft an attic proposal and run it by any
PMC members who are still awake.
* Myrle: follow up about trademark issue
[ Impala 2019-05-15 ]
Status:
* Rich: find out what the sentence in Issues means
[ Open Climate Workbench 2019-05-15 ]
Status: Still no response to my email -
https://lists.apache.org/thread.html/665fbb7879eb4b521812f6417c23c43b8e516dd408cb2b9140e43bba@%3Cprivate.climate.apache.org%3E
Pinging again.
* Rich: propose new PMC chair due to consistently late reports
[ TomEE 2019-05-15 ]
Status: I feel that this item is complete, and that TomEE is back on
the rails.
* Tom: research what other nonprofits do for CoCs for boards
[ Statement of Expectation of Conduct of Board Members 2019-05-15 ]
Status:
* Roman: pursue a report for Bloodhound
[ Bloodhound 2019-06-19 ]
Status:
* Rich: pursue a roll call for Joshua
[ Joshua 2019-06-19 ]
Status: Roll call requested. Had 3 +1s almost immediately. I don't
feel like there's a concern in that regard. Closed.
* Ted: follow up about trademark issue in Sling
[ Sling 2019-06-19 ]
Status: The project has been carrying this forward themselves. I don't
think that I need to follow up. I will continue to monitor
quietly.
* Daniel: Check in on treasurer availability
[ Treasurer 2019-07-17 ]
Status: Done 2019/09/11
* Danny: Document the data privacy needs of the organization.
[ Data Privacy 2019-07-17 ]
Status: Done. John has re-engaged with the role, and set and met smart
goals, I will suggest in my call-out that he do the same for
the next period, to reassure us that this is going to stay
fixed.
* Danny: pursue a roll call for Apex
[ Apex 2019-07-17 ]
Status: Done [Obsolete]. Apex have demonstrated that they have a
functioning PMC by successfully voting to move it to the
Attic.
https://lists.apache.org/thread.html/b732770cbf61d8818f546fd5297f0baac00c019f2fd06fa0b3c0d3a6@%3Cdev.apex.apache.org%3E
https://whimsy.apache.org/board/agenda/2019-09-18/Terminate-Apex
* Rich: Follow up about release vote concerns
[ Arrow 2019-07-17 ]
Status: Done. PMC gave a thorough and thoughtful response:
https://lists.apache.org/thread.html/0bfce94f7278cb8170167f6abd97ccd2104a4c827ad72a01026ca4ab@%3Cprivate.arrow.apache.org%3E
* Daniel: Reach out for choice on rebooting or atticing the project
[ ODE 2019-07-17 ]
Status: Done - ODE was voted to retire last board meeting
* Daniel: pursue a roll call for Tcl
[ Tcl 2019-07-17 ]
Status:
* Joan: pursue a report for Jakarta EE Relations
[ Jakarta EE Relations 2019-08-21 ]
Status: Report requested
* Daniel: pursue a report for W3C Relations
[ W3C Relations 2019-08-21 ]
Status: Done - report submitted this month, thanks.
* 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: Not done. This is due for next BM I believe
10. Unfinished Business
11. New Business
12. Announcements
13. Adjournment
Adjourned at 11:43 a.m. (Pacific)
============
ATTACHMENTS:
============
-----------------------------------------
Attachment 1: Report from the VP of Brand Management [Mark Thomas]
* ISSUES FOR THE BOARD
None.
* OPERATIONS
Covering the period August 2019
Responded to the following queries, liaising with projects as required:
- Provided advice on naming 3rd party produced tutorials for KAFKA and NIFI
- Provided advice on using the powered by logo for GEODE
- Provided advice to COUCHDB on ownership and management of non-ASF domains
- Chased counsel regarding review of the transfer agreement for dubbo.io
- Approved one podling name search (HUDI)
- Provided advice to DUBBO regarding 3rd party appreciation gifts
- Provided advice to a 3rd-party wanting to sell ASF project branded goods on
RedBubble
* REGISTRATIONS
- OPENOFFICE.ORG has been renewed for the EU
- Instructed counsel to allow OPENOFFICE.ORG registrations to lapse for
Croatia, Serbia, Turkey and Bosnia & Herzegovina
- Instructed counsel to renew OPENOFFICE.ORG registration for Russia
- Chased counsel regarding the transfer of the OPENWHISK marks
* INFRINGEMENTS
-----------------------------------------
Attachment 2: Report from the VP of Fundraising [Daniel Ruggeri]
Fundraising continues operating smoothly. We secured 3 new Bronze Sponsors
this past month. We are working on two Bronze and one Platinum renewals. We
are also finalizing consolidation of a combined (ASF + Targeted) Platinum
sponsorship.
After another successful ApacheCon North America, we are responding to final
event-closing inquiries and are preparing for 2020 events. We continue
supporting ApacheCon Europe.
During ApacheCon North America, we held a great Sponsor luncheon to spend time
with our ASF family. 22 Sponsor representatives and 13 ASF team members
(Board, Executive, and Sponsor Ambassadors) participated.
An article that scrutinized the ASF Sponsorship program at the Bronze level
was published
https://www.brinzan.com/2019/09/apache-software-foundation-selling-links-for-seo/,
causing some confusion and distress with a small handful of sponsors whose
links may be affected. We are discussing any potential changes needed.
After publishing the ASF FY2019 Annual Report
https://s.apache.org/FY2019AnnualReport Sally, along with ASF Sponsor
Ambassadors Ted Liu, Bob Paulin, and Craig Russell, connected with all
Sponsors to share news of this milestone and extend assistance during
ApacheCon.
We received ~$1,930 from individual donors via Hopsie, with an additional
$2,000 ACH payment pending. $1,105 of the above total donations was raised as
part of the ”Trillions” documentary campaign https://s.apache.org/trillions
-----------------------------------------
Attachment 3: Report from the VP of Marketing and Publicity [Sally Khudairi]
[REPORT] ASF Marketing & Publicity - September 2019
I. Budget: the majority of our annual budget has been expended in support of
three consecutive events (ApacheCon North America, Huawei Connect, and
ApacheCon Europe); expenses included both promotional items and travel/lodging
for service providers (documentary filmmakers, etc.) as well as select ASF
team members.
II. Cross-committee Liaison: as VP Sponsor Relations, Sally Khudairi is
supporting ASF Fundraising by engaging new sponsors (3 Bronze), securing
sponsorship renewals (2 Bronze), onboarding new sponsors, and liaising on
sponsorships for both ApacheCon North America and Europe.
She organized the ASF Sponsor Luncheon at ApacheCon for 36 attendees, 13 of
whom were ASF Board and Executive team members, plus ASF Sponsor Ambassadors
Ted Liu, Bob Paulin, and Craig Russell. The ASF FY2019 Annual Report was
published at https://s.apache.org/FY2019AnnualReport
III. Press Releases: the following formal announcement was issued via the
newswire service, ASF Foundation Blog, and announce@apache.org during this
timeframe.
13 August 2019: The Apache® Software Foundation Announces Annual Report for
2019 Fiscal Year
IV. Informal Announcements: 5 items were published on the ASF "Foundation"
Blog. 5 Apache News Round-ups were issued, with a total of 269 weekly
summaries published to date. We tweeted 46 items to 54.8K followers on
Twitter, and posted 14 items on LinkedIn that garnered more than 44.7K 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 and "Did You Know?" success stories are requested to
contact Sally at <press@apache.org> with at least 2-weeks' notice for proper
planning and execution.
VI. Media Relations: we welcomed 3 journalists and 4 bloggers at ApacheCon,
and we responded to 9 general media queries. The ASF received 1,024 press
clips vs. last month's clip count of 1,919. Media coverage of Apache projects
yielded 1,954 press hits vs. last month's 3,104. ApacheCon received 145 press
hits. We held Intermediate Media & Analyst Training during ApacheCon with four
first-time and three repeat- participants. For those Committers interested in
taking the Beginner session, it is now available from
http://apache.org/foundation/press/ to help offset the year-round demand for
the training without having to wait for the next ApacheCon.
VII. Analyst Relations: we received three analyst queries. Apache was
mentioned in 2 reports by Gartner; 1 report by Forrester; 5 reports by 451
Research; and 3 reports by IDC.
VIII. Central Services: we continue to build our support services for both the
Foundation and PMCs. This is a slow roll-out that began in January 2019
starting with creative projects (ASF 20th Anniversary logos, supporting
graphics in the ASF Press Kit http://apache.org/foundation/press/kit/ , and
signage for ApacheCon and third party events). We have counseled various
Apache projects and their communities on a variety of creative issues
pertaining to Websites and logos for Apache projects and their communities.
Kenneth Paskett has been named Creative Lead, having been involved with the
re-design of the Apache feather logo and Website relaunch in 2016 and for the
ASF’s 20th Anniversary in 2019, as well as the ApacheCon Website relaunch in
2019. Kenneth will be attending ApacheCon Berlin on behalf of ASF Marketing &
Publicity/Central Services and will be liaising with the Open Source Design
community to explore ways we can engage on future Apache-related projects. The
next focus of planning is dedicated editorial support services which will
include standing ASF communications, Sponsor promotional activities, and
special projects, amongst others. For the past 7 weeks, Swapnil Mane has
stepped up to edit and publish the Apache Weekly News Round-ups, and has
committed to publish future newsletters on a weekly basis. Over this past
week, four new contributors (not yet Committers) have expressed interest in
working with Sally in this area. This includes two individuals who offered to
assist after participating in Media & Analyst Training.
IX. Events liaison: ApacheCon North America concluded 48 hours ago. Our
contributions, from the ASF booth to 20th Anniversary promotions to “Trillions
and Trillions Served” documentary filming and “Community Over Code. Code Over
Community” PMC photoshoots, have been successfully executed and well received.
The “Trillions” documentary crew will continue filming their interviews with
ASF co-founders and individual community members at ApacheCon Berlin in 5
weeks. Sally continues to participate in weekly planning calls with ApacheCon
Europe event lead Myrle Krantz and conference producers newthinking/Plain
Schwarz. Additional promotions for the Berlin event are being posted on
Feathercast, with transcripts published on
https://blogs.apache.org/conferences/ . Sally is also coordinating the ASF’s
presence at the Cumbre de Contribuidores de Open Source Software (CCOSS) event
in Guadalajara (14-15 September), and Huawei Direct in Shanghai (18-20
September). Due to scheduling, the training for ASF Sponsors, Members, and
PMCs on how to host an "Apache@" event at corporate locations will be held at
as a virtual training session at a later date.
X. Newswire accounts: our pre-paid press release package with GlobeNewswire is
active and running through 2021.
# # #
-----------------------------------------
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
==========
The Infrastructure team met with the community during ApacheCon NA in
Las Vegas. This provided a good chance for the team/community to meet
each other, and to address specific queries from the community.
Launched new .asf.yaml self-service features[1], with some immediate
pickup and all-around happiness.
We lost a disk at one of our data centers, affecting the git.apache.org
service. We have decided to deprecate much of that host's functionality,
and are curretly rebuilding svn-to-github mirrors, with some limits.
Short Term Priorities
=====================
- Migrate our Ubuntu 14.04 systems up to 18.04 and puppet6.
- Complete the svn-master migration.
Long Range Priorities
=====================
- Our Ubuntu-based replacement of "hermes" (our primary MTA) is
looking great. But we still need many months to perform an orderly
transfer and rebuild of the service. This has been in-process for
very many years.
General Activity
================
- Stood up haproxy to spread outbound SMTP across several IPs, in
order to "warm them up". This will assist with future failovers and
system migrations.
- New backup system has been implemented, as a default for all
puppetized systems. The several outliers already have backups, and
others required various levels of maual work. This new work is to
simplify and ensure future backups-by-default.
- Documentation consolidation, and revamp.
- Continued migration to 18.04/p6. We are focusing on the oldest 1404
systems for migration, but will upgrade any system once it comes up.
- Major work across the Jenkins nodes, with updates and new packages.
----
[1] https://cwiki.apache.org/confluence/display/INFRA/.asf.yaml+features+for+git+repositories
-----------------------------------------
Attachment 5: Report from the VP of Conferences [Rich Bowen]
ApacheCon North America
Last week we held ApacheCon North America in Las Vegas. The final numbers are
not yet ready, but we can report that we had 700+ registered, and, last I
heard, around 640 signed in on-site.
All comments I have heard so far have been overwhelmingly positive, with the
exception of some complaints about the venue itself:
* Rooms were spread very widely, and some of them were hard to get to for
anyone with reduced mobility
* Session rooms were *very* cold - although this is not unusual for North
American venues.
Next month's report will have more detailed statistics and financial
information.
Session recordings have been uploaded to https://feathercast.apache.org/ but
have not been publicized yet. Videos have been uploaded to
https://www.youtube.com/TheApacheFoundation but have not yet been published.
We will be publishing, and publicizing, this content, over the coming weeks,
but are now focusing primarily on ACEU promotion.
ApacheCon Europe, Berlin
As ACNA winds down, the decorations and especially the signing feather have
been posted to Berlin. ACEU is our next big event.
ACEU ticket sales have seen an uptick, that is mainly related to speaker and
sponsor registrations. We sent out the speaker package with speaker
registration codes this week.
With the hope of continuing to drive ticket sales, we are preparing to reach
out to the PMC's of the projects speakers are mentioning with a description of
the relevant talks.
We continue to search for ways to increase sponsorship levels of ACEU
including face-to-face conversations with existing sponsors at ACNA in Las
Vegas.
We are moving on to the next level of finer detailed planning for audience
movement and volunteer engagement at the venue. Talk lists have already been
shared with TAC to support the creation of a TAC working plan.
-----------------------------------------
Attachment 6: Report from the Apache Travel Assistance Committee [Gavin McDonald]
Events
======
ApacheCon NA 2019 (Las Vegas)
-----------------------------
Leading up to the event, flights were finalised, and a top up amount was
provided on the TAC card to the Travel Agent to secure and book the remaining
flights. A successful applicant had their Visa rejected and so the flight was
not booked for this person.
At the event, we had a 'Welcome Dinner' for all TAC attendees and invited ASF
long time experts, Board Members, IPMC etc. As usual, this event went very
well, allowing the TAC folks to mix with the experienced ASFers and gain some
insights as to the inner workings etc. A couple of hours before this dinner
(held on the Sunday before ApacheCon started), we gathered with the TAC
attendees and went through the roles for the week, and divided out the tasks,
before handing out the subsistence monies to those that requested it in their
applications.
During the week TACers were tasked with mainly helping out the organisers by
introducing speakers, ensuring equipment was working and available etc. As we
have less TAC attend than we would have liked, and some days/times had 9 talks
or more at the same time, it made for a busy week for them.
After the event. At time of writing, TAC folks are still making their way
home, so sometime next week we'll be handing out post-ACNA surveys for them to
fill out, a way for us to see how well we did, where we could improve for next
time, how they enjoyed their time, how they handled the work expected of them
etc.
ApacheCon EU 2019 (Berlin)
--------------------------
Next month sees our second ApacheCon in as many months. All paperwork is in
place for our 17 successful applicants and we are ready to go!
-----------------------------------------
Attachment 7: Report from the VP of Finance [Tom Pappas]
VP Finance Aug 2019 report
D&O insurance renewed and paid for
Working on FY18 990
Continue working with Fundraising
Continue working on ACNA19
No major issues to report
-----------------------------------------
Attachment 8: Report from the VP of Diversity and Inclusion [Gris Cuevas]
## 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:
None
## Activity:
*** Project: Survey revamp***
- Scoped final agreement to work with Bitergia
- Submitted contract for review to legal-private@
*** Project: UX Research on new contributors ***
- Scoped final agreement to work with Bitergia
- Submitted contract for review to legal-private@
*** Project: Internships for underrepresented groups (Outreachy) ***
Outreachy's goal is to support people from groups underrepresented in the
technology industry. Outreachy interns will work remotely with mentors on
projects ranging from programming, user experience, documentation,
illustration and graphic design, to data science. Outreachy interns will
receive stipends for developing said projects full-time for three months.
- We sent emails calling for mentors. [1]
- We created a blog post announcing Outreachy at ASF and updated it to include
new information. [2]
- To create a friction log template, we opened a discussion in the dev@
mailing list and asked the community for their ideas and input regarding
what a friction log should contain, how could we track these
characteristics/conditions and their experiences with it. [3]
- We offered a workshop to scope projects and answer questions to potential
mentors. [4]
- Three projects have been submitted but only two were approved. We are
waiting for some answers from Outreachy regarding the rejected project. [5]
- Currently we have 4 mentors approved.
- We started to use Confluence meeting notes templates to track our meetings.
[6]
- We decided to migrate previous meeting minutes to Confluence to create a
report that includes all action items, to make the process more transparent.
More detailed reports on this work can be found on their update minutes[7].
*** Operations ***
*** Community Highlights ***
1. The V.P. of diversity and inclusion presented the Foundations strategy for
D&I at ApacheCon during a 50min session at ApacheCon.
2. The Foundation participated at www.ccoss.org, the first open source
contributor summit in Latin America
3. Board members (Daniel Ruggeri, Myrle Krantz, Joan Touzet) + 3 officers
(Gris Cuevas, Sharan Foga, Sam Ruby) in attendance Full ASF track delivered
on Saturday 2019-09-14: https://ccoss.org/schedule/2019-09-14 Lots of
interest - common theme expressed was "I've never been part of an Apache
event" and "Latin Americans want to get more involved in the ASF [now]!"
4. Sam Ruby gave a presentation on the Apache Way at the IBM Lab in
Guadalajara. The audience was 55 people: 55% male, 45% female, all Latinx.
## Health report:
Update on Diversity & Inclusion mailing lists moderation: No changes from
previous month.
Update on mailing lists status: No updates from previous month.
## Committee members changes:
None
## References
[1]http://mail-archives.apache.org/mod_mbox/diversity-dev/201908.mbox/%3cCA+eZaTaO0t4x_wdFFc-4H9sQfFi4E7opeTE8PXXJP7FFEE8UTg@mail.gmail.com%3e
[2]https://cwiki.apache.org/confluence/pages/viewrecentblogposts.action?key=EDI
[3]http://mail-archives.apache.org/mod_mbox/diversity-dev/201909.mbox/%3cCA+eZaTZsr6XTVQkyYxcEDJ_-si_yJRqP7zwZC_OAYz2+_ASZ=A@mail.gmail.com%3e
[4]http://mail-archives.apache.org/mod_mbox/diversity-dev/201909.mbox/%3cCA+eZaTZmhqZ+EXRmKWoAnid=b6Ue1bwY+tWx+zONWdma6DZ-dQ@mail.gmail.com%3e
[5]https://www.outreachy.org/apply/project-selection/
[6]https://cwiki.apache.org/confluence/display/EDI/Meeting+notes
[7]https://lists.apache.org/thread.html/c415b7e47d3a989b4a510bb5a015fe54890fe7474e2a9fa0c2ad1abf@%3Cdev.diversity.apache.org%3E
-----------------------------------------
Attachment 9: Report from the VP of W3C Relations [Andy Seaborne]
Andy Seaborne(andy@) has joined the SHACL Community Group. This is a follow-on
group to the RDF Data Shapes Working Group.
As this is the first ASF member to join, ASF has signed the W3C Community
Contributor License Agreement and acknowledged the W3C Code of Ethics and
Professional Conduct.
-----------------------------------------
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 down 2 to 20, unresolved
issues this month.
Our work with Eclipse foundation continues mainly around formalizing our
current relationship, but also discovery of prior ASF participation in JSR
Expert Group. See VP Jakarta report for more details.
Senior Vice President, Intellectual Property at one of the corporate
contributors to a major ASF project reached out for clarifications on early
(pre 2009) contributions to a few ASF projects and we've provided required
guidance.
At ApacheCON in Las Vegas we met with a few ASF sponsors during a scheduled
luncheon and answered their questions around IP management and licensing
policies within ASF. We also discussed potential opportunities and
challenges for new projects coming into the incubator.
-----------------------------------------
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 August 2019:
15 [license confusion]
14 [support request/question not security notification]
Security reports: 46 (last months: 26, 23, 44, 29)
6 [openoffice],[site]
5 [zeppelin]
2 [airflow],[hadoop],[infrastructure],[kafka],[lucene],
[trafficserver],[zookeeper]
1 [ambari],[apr],[cloudstack],[commons],[dubbo],[guacamole],
[jspwiki],[nifi],[ofbiz],[royale],[santuario],[subversion],
[tomcat],[trafficcontrol]
In total, as of 10th September 2019, we're tracking 82 (last month:
66) open issues across 36 projects, median age 88 (last month:
111) days. 47 of those issues have CVE names assigned.
8 (last month: 7) of these issues, across 5 projects, are older
than 365 days.
-----------------------------------------
Attachment 12: Report from the VP of Data Privacy [John Kinsella]
After too long a period of silence (emailed last report April 2019[1] - just
noticed it doesn’t seem to have made it to whimsy), renewing push to get Data
Privacy up and running.
Structure for data-privacy has been set up - mailing lists[2][3], jira
group[4], and wiki[5] created.
Since last board report, have talked with others with previous
experience/thoughts on ASF data privacy topics. Short-term goal is to start
outlining topics to address and areas of help needed on the wiki, then send
call for volunteers to members@a.o.
Goal right now is to start to get volunteers involved, come up with list of
priorities, and start being more useful to requests from projects.
I've been reviewing report formats from others, will be adding a bit more
structure to this in coming months, along with several calendar reminders.
Also planning a chat room for more interactive and regularly scheduled
discussions to continue to drive movement.
Stats for August, 2019:
* 1 still open Jira ticket (Intention is to move LEGAL-383 to PRIVACY)
* 0 closed issues
1: https://lists.apache.org/thread.html/6ac38660931f60d3634aaab569967c5261004c78ff070a56a1be3655@%3Coperations.apache.org%3E
2: privacy@apache.org - 1 person has already organically found and subscribed.
3: privacy-discuss@apache.org
4: https://issues.apache.org/jira/projects/PRIVACY/issues
5: https://cwiki.apache.org/confluence/display/PRIVACY/Home
-----------------------------------------
Attachment 13: Report from the VP of Jakarta EE Relations [Mark Struberg]
This is a report about the current status of the Eclipse JakarteEE relations.
I will reference the following documents in the further reading:
* Eclipse Foundation Specification License (EFSL [1])
* Eclipse Foundation TCK License (EFTL [2])
* Eclipse Foundation Specification Process (EFSP [3])
# Overview
The JakartaEE project hosts various specifications which are derived from
JavaEE JSRs. Each of them consists of 4 different parts.
1.) the APIs (e.g. JPA - Jakarta Persistence API)
2.) the Reference Implementation (RI, e.g. Eclipse EclipseLink)
3.) the TCKs (previously one big monolithic TCK with only a few specs having
their own separated ones)
4.) the spec documentation PDFs
# Ad 1 and 2 - APIs and RIs
The APIs owned by Oracle have been re-licensed to EPLv2 and donated to the
Eclipse Foundation. Other APIs - mostly owned by IBM and RedHat - have been
ALv2 ever since and afaik have also been donated to the EF. Reference
Implementations have to be licensed under an 'Open Source Lincense' as defined
by the EFSP. Which are EPLv2 or ALv2.
Future development of spec APIs will happen under either EPLv2 or ALv2
(based on what each specification decides). This is legally perfectly fine for
us to both contribute to and consume under (at worst) CatB [4].
# Ad 3 & 4 - TCKs and Specification Documents
Some TCKs are ALv2: JBatch, CDI, Bean Validation. Most others got donated from
Oracle to the Eclipse Foundation and are now licensed under EPLv2. I want to
take this opportunity to say thanks to Oracle for this gracious move!
There is one little complicated detail though. When a final specification gets
ratified it will be published and distributed under the EFSL resp EFTL. This
procedure is defined in the EFSP. Note that neither the EFSL nor EFTL are OSI
licensed and never will be due to not allowing any modifications which makes
them not an OSS license.
The Specification Document for the Final Specification must be distributed as
read-only text under the Eclipse Foundation Specification License. The
Ratified TCK in composite must be distributed under the Eclipse Foundation
Technology Compatibility Kit License.
This could legally be achieved via either sub-licensing or re-licensing. The
Eclipse ECA [5] explicitly talks about sublicensing. That means we would be
fine to contribute to and consume TCKs and Specs _under work_ as well.
The IP flow is that contributions to the TCK and Spec Documents are performed
under ALv2 or EPLv2. And we can also consume those bits. The final versions
though are ratified and bundled under very restrictive non-OSS licenses which
you only get if one passes the TCK and are certified.
There is also an Eclipse Foundation IP Policy [6] to which the EFSP refers to.
It only applies to Specification Reviews. It contains some patent grant
clauses which need to be further evaluated. In a first review they look
roughly equivalent to the patent grant we have in ALv2. But this needs some
more legal review. Interestingly this only becomes effective during the review
and not during contributing. But the review and voting on the specs is only a
small group of people/companies and not all contributors.
# Other business
The Eclipse Foundation reached out to us to help them collect IP for existing
specification documents. Oracle transferred their right to the EF as far as
they did hold them. They of course could only transfer IP they own themselves.
Whether there is anything uncovered is an open question. The EF now reached
out to us to also grant them rights for parts some ASF committers provided 'on
behalf of the ASF'. Our current legal conclusio is that the ASF itself cannot
do this but we will help to identify the individuals in question.
# Summary
* The ASF (or it's individuals) can both consume from and contribute to APIs
and Reference Implementations.
* The ASF can both consume from and contribute to TCKs and Spec Documents
_under development_.
* Consuming the final ratified EFSL and EFTCK licensed specs and TCKs are out
of scope for the ASF without restricting us in any way.
* The patent handling for contributors needs another review.
[1] https://www.eclipse.org/legal/efsl.php
[2] https://www.eclipse.org/legal/tck.php
[3] https://www.eclipse.org/projects/efsp/
[4] https://www.apache.org/legal/resolved#category-b
[5] https://www.eclipse.org/legal/ECA.php
[6] https://www.eclipse.org/org/documents/Eclipse_IP_Policy.pdf
-----------------------------------------
Attachment A: Report from the Apache Airflow Project [Bolke de Bruin]
## Description:
The mission of Apache Airflow is the creation and maintenance of software
related to workflow automation and scheduling that can be used to author and
manage data pipelines
## Issues:
* There are no issues requiring board attention
## Membership Data:
Apache Airflow was founded 2018-12-19 (9 months ago)
There are currently 28 committers and 17 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 Alex Van Boxel on 2018-12-19.
- Felix Uellendall was added as committer on 2019-09-05
- Chao-Han Tsai was added as committer on 2019-08-17
## Project Activity:
* Two new releases have been made since the last report
* A new logo has been designed and voted upon
## Community Health:
* We started the user mailing list to reduce the amount of message on dev. It
is not very active yet
* The slack community is very active across many channels
* We have grown to 922 contributors, with 198 active in the last quarter
* A ridiculous 1081 commits have been made in the past quarter
-----------------------------------------
Attachment B: Report from the Apache Allura Project [David Philip Brondsema]
## Description:
Apache Allura is an open source implementation of a software forge, a web site
that manages source code repositories, bug reports, discussions, wiki pages,
blogs, and more for any number of individual projects.
## Issues:
- No issues needing board attention.
## Activity:
- Our Google Summer of Code project finished successfully
- Various other improvements and fixes continue, including movement towards
Python 3
- A security report was handled and a fixed version released.
## Health report:
- Slow but steady development
- Not much from end-users/deployers this quarter
## PMC changes:
- Last PMC addition: Sun Oct 28 2018 (Shalitha Suranga)
- Currently 15 PMC members.
## Committer base changes:
- Last committer addition: Mon Oct 29 2018 (Shalitha Suranga)
- Currently 15 committers.
## Releases:
- 1.11.1 was released on 2019-07-15.
-----------------------------------------
Attachment C: Report from the Apache Any23 Project [Lewis John McGibbney]
## Description:
The mission of Apache Any23 is the creation and maintenance of software related
to automatic crawling, parsing, analyzing, producing, validating and converting
RDF (Resource Description Framework) data.
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache Any23 was founded 2012-08-27 (7 years ago)
There are currently 15 committers and 15 PMC members in this project.
The Committer-to-PMC ratio is 1:1.
Community changes, past quarter:
- No new PMC members. Last addition was Hans Brende on 2018-02-25.
- No new committers. Last addition was Hans Brende on 2018-02-21.
## Project Activity:
Any23 has seen some new activity from from non-PMC/Committer in
the last while which is positive. The project remains quiet generally.
## Community Health:
dev@ mailing list activity saw an increase in the last quarter.
This did not relate to much in the way of development but
involved discussion between new community members which is
great. There are no current epic development tasks planned
for Any23 so it might be time to kick that conversation off
on our mailing list.
-----------------------------------------
Attachment D: Report from the Apache Archiva Project [Olivier Lamy]
## Description:
The mission of Archiva is the creation and maintenance of software related to
Build Artifact Repository Manager
## Issues:
There are no issues requiring board attention
## Membership Data:
Apache Archiva was founded 2008-03-19 (11 years ago)
There are currently 21 committers and 9 PMC members in this project.
The Committer-to-PMC ratio is 7:3.
Community changes, past quarter:
- No new PMC members. Last addition was Martin Stockhammer on 2017-04-10.
- No new committers. Last addition was Martin Stockhammer on 2016-09-22.
## Project Activity:
We are working on having the project working with java 11.
There are still ongoing branch development to refactor:
- data storage
- artifact storage
## Community Health:
We still have active users.
The project has a low activity but we still have enough PMC to cut releases.
-----------------------------------------
Attachment E: Report from the Apache Atlas Project [Madhan Neethiraj]
## Description:
Apache Atlas is a scalable and extensible set of core foundational
governance services that enables enterprises to effectively and efficiently
meet their compliance requirements within Hadoop and allows integration with
the complete enterprise data ecosystem
## Issues:
There are no issues requiring board attention at this time.
## Activity:
- released 0.8.4 maintenance version
- added quick-search functionality, for a simpler search interface
- enhanced notification processing to handle multiple Kafka topics
- updated hook and bridges to replace object-type attributes with
relationships
- added support for dynamic attributes, whose value is derived from value of
other attribute(s)
- added support for add Keycloak authentication method
- enhancements to handle references to non-existing entities during
notification processing
- performance improvements in import/export functionality
- working on upgrading JanusGraph version to the most recent release, 0.4.0
## Health report:
- 3 new contributors added in last 3 months: Bolke, Sameer, SJQ
## PMC changes:
- Currently 34 PMC members
- Last addition to PMC role was on 5/13/2019
## Committer base changes:
- Currently 38 committers
- No new committers added in last 3 months
- Last addition to committer role was on 10/15/2018
## Releases:
0.8.4 was released on 06/21/2019
1.2.0 was released on 06/12/2019
2.0.0 was released on 05/14/2019
0.8.3 was released on 10/31/2018
1.1.0 was released on 09/17/2018
1.0.0 was released on 06/02/2018
0.8.2 was released on 02/05/2018
1.0.0-alpha was released on 01/25/2018
0.8.1 was released on 08/29/2017
0.8-incubating was released on 03/16/2017
0.7.1-incubating was released on 01/26/2017
0.7-incubating was released on 07/09/2016
0.6-incubating was released on 12/31/2015
0.5-incubating was released on 07/11/2015
-----------------------------------------
Attachment F: Report from the Apache Aurora Project [Jake Farrell]
## Description:
The mission of Aurora is the creation and maintenance of software related to
Mesos framework for long-running services and cron jobs
## Issues:
## Membership Data:
Apache Aurora was founded 2015-03-17 (4 years ago)
There are currently 23 committers and 22 PMC members in this project.
The Committer-to-PMC ratio is roughly 1:1.
Community changes, past quarter:
- Mauricio Garavaglia was added to the PMC on 2019-07-29
- Mauricio Garavaglia was added as committer on 2019-07-25
## Project Activity:
No recent releases.
Last release on 2018-09-10.
Planning for next release has begun and we hope to ship version 0.22.0
before the year ends.
## Community Health:
We have experienced a small surge in activity thanks to new developers
joining. The following metrics corroborate this increase in engagement:
9 PRs opened on GitHub, past quarter (900% increase)
7 PRs closed of GitHub, past quarter (700% increase)
6 commits in the past quarter (600% increase)
reviews@aurora.apache.org had a 1300% increase in traffic in the
past quarter (70 emails compared to 5)
We hope the project is able to sustain this level of engagement
as well as increasing the number of participants who are helping to maintain
this project.
Outside of a few members, responsiveness on the mailing list has decreased.
We hope to re-engage folks as they see more activity happening on the project.
-----------------------------------------
Attachment G: Report from the Apache Axis Project [Robert Lazarski]
# Apache Axis2 Board Report
## Description
The Apache Axis project is responsible for the creation and maintenance of
software related to the Axis Web Services frameworks and subsidiary components
(both Java and C).
## Issues
There are no issues requiring board attention at this time.
## Membership Data:
According to SVN, Apache Axis was created on 2001-01-19 (18 years ago).
There are currently 63 committers and PMC members in this project, a vote in
2010 made all committers automatically PMC members.
## Activity
- Axis2 Java 1.7.9 (stable)
- Maintenance only.
- Axis2 Java 1.8 (development)
- Axis2 C 1.7 (development)
## Health report:
We have enough PMC to cut releases. Axis2 is a mature project, but still
actively maintained.
Most of our users are using legacy SOAP services so we are lacking new
committers. We expect to grow our community by better docs on Axis2 with JSON
and REST.
The most significant event this past quarter was receiving and applying
patches for both Axis 1.x and Axis2 concerning JDK 11 support. See AXIS-2929
and AXIS2-5935.
Axis2 C PMC member Bill Blough has continued his progress via commits and Jira
issues this past quarter. The communication continues to be good.
## PMC/Committer changes:
- Currently 63 PMC/Commiters members.
- No new committers were added in the last 90 days, last committer added was
Bill Blough on December 7th 2017 who also was added to the PMC on May 9th
2018.
## Releases:
- Axis 2/Java 1.7.9 was released on November 16, 2018.
- Axis 2/C 1.6 was released on April 20, 2009.
- Axis 1.4 was last released in 2006.
## JIRA Activity for Axis2 java
- 7 JIRA tickets created in the last 90 days.
- 2 JIRA tickets closed/resolved in the last 90 days.
-----------------------------------------
Attachment H: Report from the Apache Bahir Project [Luciano Resende]
## Description:
Apache Bahir provides extensions to distributed analytic platforms such as
Apache Spark and Apache Flink. Currently, Bahir provides extensions to
multiple distributed analytic platforms, extending their reach with a
diversity of streaming connectors and SQL data sources.
## Issues:
There are no issues requiring board attention at this time
## Membership Data:
Apache Bahir was founded 2016-05-17 (3 years ago)
There are currently 40 committers and 11 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:2.
Community changes, past quarter:
- No new PMC members. Last addition was Prashant Sharma on 2018-10-19.
- No new committers. Last addition was Łukasz Antoniak on 2019-01-21.
## Project Activity:
Apache Bahir community continues to see a flow of contributions
enhancing the existing extensions for both Apache Spark and
Apache Flink.
The project has produced release candidates for
Apache Bahir 2.3.4 and 2.4.0 based on respective releases of
Apache Spark.
There is a need to produce a new release of the Flink extensions
and this has been discussed on the project mailing list but the
community have not started work on it yet.
## Community Health:
Activity levels on mailing lists and GitHub are normal for both Apache Spark
and Apache Flink extensions.
-----------------------------------------
Attachment I: Report from the Apache Beam Project [Kenneth Knowles]
## Description:
- Apache Beam is a unified programming model for both batch and streaming
data processing, enabling efficient execution across diverse distributed
execution engines and providing extensibility points for connecting to
different technologies and user communities.
## Issues:
- There are no issues requiring board attention at this time
## Activity:
Beam Summit NA occurred at ApacheCon NA. About 80 people attending 20 talks in
2 rooms over 2 days, plus a day-long Beam introductory workshop. Good
cross-pollination of talks and audience: 4 Beam related talks on other tracks;
2 non-Beam talks by Beam Summit organizers on community track; Beam Summit
attendees and speakers checked out the other tracks; other ApacheCon attendees
lured into Beam Summit :-)
Many large contributions:
- A translator from Google's recently open sourced ZetaSQL dialect into
Apache Calcite's relational algebra. This enables ZetaSQL as a choice of
dialect for using Beam SQL.
- An integration with ZetaSketch HyperLogLog algorithm, recently open sourced
as well.
- A new sort-merge join algorithm from Spotify. Still under discussion and
review.
Technically, there is a noticeable trend into schema-aware data processing,
expanding from Beam SQL to other proposals like dataframe-style APIs and
columnar processing using Apache Arrow.
A SQL collaboration: PMC from Flink, Beam, and Calcite, together with
researchers from Oakridge National Lab that sit on the ISO SQL committee,
wrote a proposal for what streaming SQL should look like across their projects
and the industry as a whole, to influence streaming SQL standardization.
Presented to SIGMOD industry track and later at ApacheCon (and other venues).
Other dev list discussions of interest, due to community relevance or
integrations with other Apache projects:
- A new integration - Ananas Analytics Desktop, a GUI for building pipelines.
Built without Beam's involvement; a sign of relevance and accessibility.
[0]
- How to support users best, across user@, StackOverflow, and Slack: Covered
tradeoffs between synchronous vs asynchonous, mostly. Did not get into
ASF-hosted vs third party, nor was licensing of code snippets discussed.
[1]
- Which Flink versions to support and how best to support multiple versions.
[2]
- One Google Summer of Code project wrapped up, on optimized inserts to
BigQuery. [3]
- We have improved issue triage significantly. We added a default Jira status
of "Needs Triage" to make sure all bugs get some attention from a
knowledgeable community member. I asked for help triaging, and the
community collaboratively kept untriaged issues steadily under 100, for the
first time in a long time. [4]
- Protocol for managing Beam's social media presence were discussed more, and
we have a system in place (after long discussion) where the community can
contribute easily and the PMC can review and approve. [5]
- Improvements to our release process of vendored artifacts and documentation
of it. [6]
[0] https://lists.apache.org/thread.html/ce3a051789868e362680e358569da26711d6b513cf2396094a242230@%3Cdev.beam.apache.org%3E
[1] https://lists.apache.org/thread.html/ed90f898d571856a5b92df23150d3417732a9f5f1b4c6ff2a41bf237@%3Cdev.beam.apache.org%3E
[2] https://lists.apache.org/thread.html/124200de15d88321d590bf83be3ba0e8bdfc3a161a0bcd66a12921ed@%3Cdev.beam.apache.org%3E
[3] https://gist.github.com/ttanay/80f84b7b852e0867d5a00d3b345e1dad
[4] https://lists.apache.org/thread.html/dd0048c68c1b5511ca5a0f668a848159fd441d51c21f332b43510163@%3Cdev.beam.apache.org%3E
[5] https://lists.apache.org/thread.html/babceeb52624fd4dd129c259db8ee9017cb68cba069b68fca7480c41@%3Cdev.beam.apache.org%3E
[6] https://lists.apache.org/thread.html/e2c49a5efaee2ad416b083fbf3b9b6db60fdb04750208bfc34cecaf0@%3Cdev.beam.apache.org%3E
## Health report:
Dev and user list subscription and traffic steady.
Each release continues to include commits from 60-100 contributors.
One sign of community bonding I've noticed happily was people letting dev@
know when they were going on vacation.
## PMC changes:
- Currently 21 PMC members.
- No new PMC members. Last addition was Pablo Estrada on 2019-05-13.
## Committer base changes:
- Currently 60 committers.
- New committers:
- Rui Wang was added as committer on 2019-07-30
- Kyle Weaver was added as committer on 2019-08-02
- Jan Lukavský was added as committer on 2019-07-25
- Robert Burke was added as committer on 2019-06-28
- Mikhail Gryzykhin was added as committer on 2019-06-16
- Valentyn Tymofieiev was added as committer on 2019-08-09
## Releases:
- 2.15.0 was released on 2019-08-22.
- 2.14.0 was released on 2019-08-01.
- 2.13.0 was released on 2019-06-04.
## Mailing list activity:
Mailing list activity does not indicate any significant change.
- dev@beam.apache.org:
- 627 subscribers (up 17 in the last 3 months):
- 1549 emails sent to list (2110 in previous quarter)
- user@beam.apache.org:
- 641 subscribers (up 14 in the last 3 months):
- 359 emails sent to list (416 in previous quarter)
## JIRA activity:
- 615 JIRA tickets created in the last 3 months
- 334 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment J: Report from the Apache Bigtop Project [Youngwoo Kim]
## Description:
Bigtop is a project for the development of packaging and tests of the Apache
Hadoop ecosystem. The primary goal of Bigtop is to build a community around the
packaging and interoperability testing of Hadoop-related projects. This
includes testing at various levels (packaging, platform, runtime, upgrade,
etc...) developed by a community with a focus on the system as a whole, rather
than individual projects. In short we strive to be for Hadoop what Debian is to
Linux.
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache Bigtop was founded 2012-09-19 (7 years ago)
There are currently 37 committers and 27 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:4.
Community changes, past quarter:
- No new PMC members. Last addition was Jun He on 2018-11-25.
- No new committers. Last addition was Jun He on 2018-02-23.
## Project Activity:
Software development activity:
- We released the 1.4.0 version on 2019-06-15.
- We are discussing to making release 1.x for existing users and reshaping of
current project for the future release.
Meetups and Conferences:
- Community members(including PMC members) will attend ApacheCon NA 2019.
- Jay Vyas will give a talk on prototype of modern big data and analytics
architecture and future direction of Apache Bigtop.
## Community Health:
After 1.4.0 release, activity of development is decreasing but overall
community health is good. We have been discussing maintenance release and
future release for the Cloud Native deployments.
-----------------------------------------
Attachment K: Report from the Apache Bloodhound Project [Gary Martin]
-----------------------------------------
Attachment L: Report from the Apache BVal Project [Matthew Jason Benson]
## Description:
The mission of BVal is the creation and maintenance of software related to
Apache BVal: JSR-303 Bean Validation Implementation and Extensions
## Issues:
No issues requiring board attention at this time.
## Membership Data:
Apache BVal was founded 2012-02-14 (8 years ago)
There are currently 15 committers and 14 PMC members in this project.
The Committer-to-PMC ratio is roughly 8:7.
Community changes, past quarter:
- No new PMC members. Last addition was Thomas Andraschko on 2019-05-15.
- No new committers. Last addition was Thomas Andraschko on 2019-05-16.
## Project Activity:
Apache BVal 2.0.3 was released on 2019-08-19. A maintenance release
along the 1.1.x branch of activity is planned for the near future.
## Community Health:
With last quarter's addition of a new volunteer to the PMC and
committer roster, our capacity to keep up with maintenance tasks has
increased. Our mailing list traffic is low; as noted in the past
our usual model is frenzied activity for a spec-compliant release,
then the maintenance cycle, much like the proverbial "periods of
boredom punctuated by periods of terror" commonly attributed to war.
Our JIRA activity also reflects this: two issues opened and closed
with patches provided, accepted, and applied during the quarter.
Another issue opened to request a release of those changes on a
dormant line of development (the aforementioned 1.1.3 release).
-----------------------------------------
Attachment M: Report from the Apache Camel Project [Andrea Cosentino]
## Description:
Apache Camel is a powerful open source integration library based on
Enterprise Integration Patterns. Rules for Camel's routing engine can be
defined in either a Java based DSL or XML.
## Issues:
there are no issues requiring board attention at this time
## Membership Data:
Apache Camel was founded 2008-12-17 (11 years ago)
There are currently 68 committers and 35 PMC members in this project.
The Committer-to-PMC ratio is roughly 9:5.
Community changes, past quarter:
- No new PMC members. Last addition was Dmitry Volodin on 2019-05-08.
- Denis Istomin was added as committer on 2019-07-30
- Jan Bednar was added as committer on 2019-08-01
## Project Activity:
- We are continuing our work towards Apache Camel 3.0.0: we released the
Milestone 4 on 11 July 2019 and the Release candidate 1 on 01 September 2019
- We are working already on the final release and we are focusing on bug
fixes, stabilization and code cleanup.
- We published the new website and we are improving the documentation and
looks and feel. The general feedback of the community was really good.
- We released a new 2.x version, the 2.24.1 on 23 June 2019. Also we released
2.23.3 on 17 June 2019 and 2.22.5 on 11 June 2019.
- We are working on a new minor release Apache Camel 2.25.0, we're working on
bug fixes and stabilisation of the codebase.
- We are preparing for the next minor release Apache Camel 2.24.2 expected for
the end of September/mid October: we are working on bug fixes mainly.
- We released Camel-K-Runtime 1.0.0 and 1.0.1, respectively on 26 July 2019
and 23 Aug 2019
- We released Camel-K 0.3.4 (on 11 June 2019) and 1.0.0-M1 (on 29 Jul 2019)
- We are continuing our work on Camel-K by improving the support for Camel 3
and keeping the same release timing as Apache Camel.
- We created an Apache Camel subproject, Camel-Quarkus. The aim of this
project is supporting Camel in the Quarkus framework.
- We released the following Camel-Quarkus versions:
- 0.0.2 on 29 Jul 2019
- 0.1.0 on 07 Aug 2019
- We completed the work with the students selected for Google Summer of Code
2019, the Apache Camel mentors are following three students. Two out of
three students passed successfully the Google Summer of code: the new
dataformat based on Any23 task and the new website task. Really nice
experience for mentors and students. We'll be part of the project again next
year
- This is the complete releases list
- 3.0.0-RC1 was released on 2019-09-01.
- 3.0.0-M4 was released on 2019-07-11.
- 2.24.1 was released on 2019-06-23.
- 2.23.3 was released on 2019-06-17.
- 2.22.5 was released on 2019-06-11.
- 3.0.0-M3 was released on 2019-06-07.
- Camel-K 0.3.4 was released on Tue Jun 11 2019
- Camel-K 1.0.0-M1 was released on Mon Jul 29 2019
- Camel-K 0.3.3 was released on Fri May 3 2019
- Camel-Quarkus 0.0.2 was released on Mon Jul 29 2019
- Camel-Quarkus 0.1.0 was released on Wed Aug 07 2019
## Community Health:
- dev@camel.apache.org had a 147% increase in traffic in the past quarter
(2482 emails compared to 1004) This is because we are near the new camel 3
final release
- issues@camel.apache.org had a 34% increase in traffic in the past quarter
(2921 emails compared to 2166) This is because we are near the new camel 3
final release and we're starting to have feedback and bugs reported
- users@camel.apache.org had a 60% increase in traffic in the past quarter
(317 emails compared to 198) This is mainly for announcements and discussion
around the new website
- 299 issues opened in JIRA, past quarter (-9% decrease)
- 319 issues closed in JIRA, past quarter (no change)
- 2828 commits in the past quarter (16% increase) This is mainly for Camel 3
activity
- 95 code contributors in the past quarter (3% increase) We have new
contributors for documentation and new website
- 446 PRs opened on GitHub, past quarter (41% increase)
- 442 PRs closed on GitHub, past quarter (38% increase)
- 176 issues opened on GitHub, past quarter (58% increase) In Apache Camel
main repository we don't use GitHub issues, this stats comes from Camel-k
and Camel-quarkus subprojects
- 130 issues closed on GitHub, past quarter (75% increase) In Apache Camel
main repository we don't use GitHub issues, this stats comes from Camel-k
and Camel-quarkus subprojects
-----------------------------------------
Attachment N: Report from the Apache Cayenne Project [Michael Ray Gentry]
## Description:
Apache Cayenne is a Java database persistence framework. It takes a
distinct approach to object persistence and provides an ORM runtime,
remote persistence services, and a cross-platform GUI mapping/modeling
tool.
## Issues:
There are no issues requiring board attention at this time.
## Membership Data:
Apache Cayenne was founded 2006-12-19 (13 years ago).
There are currently 23 committers and 9 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
Community changes, past quarter:
- No new PMC members. Last addition was Nikita Timofeev on 2017-06-25.
- No new committers. Last addition was Arseni Bulatski on 2018-12-10.
## Project Activity:
Development is focused on Cayenne 4.1 and 4.2. Prior versions are
maintenance-only.
- Cayenne 3.1.3 (aging)
- Maintenance only.
- Cayenne 4.0.1 (stable)
- Maintenance only.
- Cayenne 4.1.RC (beta)
- Expecting to release Cayenne 4.1 soon as final bugs are fixed and tested.
- Cayenne 4.2M1 (development)
- Most development work is focused on this version.
### Releases:
- Cayenne 3.1.3 on 2018-07-25.
- Cayenne 4.0.1 on 2018-12-28.
- Cayenne 4.1.B2 on 2019-05-13.
## Community Health:
Cayenne is healthy. Development activity is stable and and we have a
stable user and developer community.
### JIRA Activity:
- 30 issues opened in JIRA, past quarter (-6% decrease).
- 36 issues closed in JIRA, past quarter (9% increase).
-----------------------------------------
Attachment O: Report from the Apache Chemistry Project [Florian Müller]
## Description:
Apache Chemistry is an effort to provide an implementation of the
CMIS (Content Management Interoperability Services) specification in
Java, Python, PHP, .NET, Objective-C, and JavaScript (and possibly other
languages).
## Issues:
- There are no issues requiring board attention at this time.
## Membership Data:
- Apache Chemistry was founded 2011-02-16 (9 years ago)
- There are currently 38 committers and 36 PMC members in this
project.
- The Committer-to-PMC ratio is roughly 1:1.
Community changes, past quarter:
- No new PMC members. Last addition was Laurent Mignon on 2017-09-23.
- No new committers. Last addition was Laurent Mignon on 2017-09-20.
## Project Activity:
- There was almost no activity in the last three months.
## Community Health:
- We have a mature code base. No major development is expected.
- dev@chemistry.apache.org had a 47% increase in traffic in the
past quarter (31 emails compared to 21)
- 3 issues opened in JIRA, past quarter (-57% decrease)
- 1 issue closed in JIRA, past quarter (-50% decrease)
- 0 commits in the past quarter (-100% decrease)
- 0 code contributors in the past quarter (-100% decrease)
-----------------------------------------
Attachment P: Report from the Apache CloudStack Project [Paul Angus]
## Description:
Apache CloudStack (ACS) is an IaaS (Infrastructure as a Service) cloud
orchestration platform. ACS manages many types of hypervisors, storage and
networking devices.
## Issues:
- Mark Thomas is progressing the renewal of the CloudStack trademark
registration
- We received notification from ‘Read The Docs’ that they would be adding
‘paid for’ advertising to all pages of rendered documentation. Upon
consultation with the Board, we opted out of this advertising. nb: ASF will
work to develop a reciprocal relationship with Read The Docs to honourably
use Read The Docs for ‘free’
## Activity:
- The Apache CloudStack project received a Newsweek award for ‘Best Business
Tools 2019’ in the category ‘Cloud’
- PMC has discussed a number of committers/contributors for ‘promotion’ to
committership or PMC, which resulted in 5 new PMC members
- Many of the project’s members have been working to prepare for the
CloudStack Collaboration Conference within ApacheCon. We had 22
presentations covering new features in-development or recently completed as
well as sessions on how to use specific features in CloudStack and features
at a PoC stage.
- The project has benefited from the very recent ‘announcement’ that Apple
uses CloudStack to underpin many of its services. We hope that will bring a
bump in interest in the project, which we will endeavour to convert into
contributors
- The community discussed dropping IRC as an ‘advertised’ communication
channel as ‘no one’ hangs out there any more.
- As the community has just released a major version and has just had a large
conference, it is now ‘getting back to business’.
## Health report:
- Apropos of the activity report; the project is healthy
## PMC changes:
- Currently 51
- PMC members added since the last report:
- Andrija Panic
- Gabriel Beims Bräscher
- Bobby Stoyanov
- Nathan Johnson
- Sven Vogel
## Committer base changes (2 added since the last report):
- Currently 121 committers
- Most recently added committers: Sven Vogel on March 18th 2019 and Dennis
Konrad on March 21st 2019
## Releases:
- Release 4.11.3 (LTS release)
- Release 4.13.0.0 (New LTS release should be fully released by the time of
board meeting)
-----------------------------------------
Attachment Q: Report from the Apache Commons Project [Gary D. Gregory]
## Description:
The mission of Apache Commons is the creation and maintenance of Java focused
reusable libraries and components
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache Commons was founded 2007-06-19 (12 years ago)
The committer count and Committer-to-PMC ratio offered by the Apache
reporting tool is misleading since Apache Commons is open to all Apache
Committer.
Community changes, past quarter:
- No new PMC members. Last addition was Alex Herbert on 2019-05-09.
- No new committers. Last addition was Alex Herbert on 2019-01-30.
## Project Activity:
The project is healthy and active and released 7 components
in this reporting period:
- BEANUTILS-1.9.4 was released on 2019-08-14.
- BUILD-PLUGIN-1.11 was released on 2019-09
- COMPRESS 1.19 was released on 2019-08-27.
- DAEMON-1.2.1 was released on 2019-09-09.
- RELEASE-PLUGIN-1.7 was released on 2019-09-02.
- TEXT-1.8 was released on 2019-09-02.
- VFS-2.4.1 was released on 2019-08-14.
## Community Health:
We are handling the mailing lists, JIRA tickets, GitHub PRs in a timely manner.
-----------------------------------------
Attachment R: Report from the Apache Cordova Project [Jesse MacFadyen]
## Status report for the Apache Cordova project - September 2019
## Description:
A platform for building native mobile applications using HTML, CSS and
JavaScript.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
cordova-electron@1.1.1 was the only platform release in this quarter.
cordova-android@8.1.0 is being voted on currently, and will be released
shortly. We will also be making some large changes to iOS as Apple has made it
clear that they may soon reject app submissions for apps using deprecated
APIs. Discussions are happening currently so we can find the best solution
that does not break existing applications/plugins and meets Apple's
requirements.
## Health report:
Our status dashboard at http://status.cordova.io is mostly all green -
failures are usually due to external service issues that do device testing.
Our nightly builds remain extremely stable.
We are still working to resolve all existing issues in JIRA while also
maintaining all the new issues and pull requests in Github.
## PMC changes:
- Currently 96 PMC members.
- New PMC members:
- no new pmc members this quarter
- Last PMC addition: Tue Apr 30 2019 (Dave Alden)
## Committer base changes:
- Currently 99 committers.
- New commmitters:
- no new committers added this quarter
- Last committer addition: Tue Apr 30 2019 (Dave Alden)
## Releases:
### Platforms
- cordova-electron@1.1.1 was released on 2019-08-27.
### Plugins
- cordova-plugin-wkwebview-engine@1.2.1 was released on 2019-07-22.
- cordova-plugin-wkwebview-engine@1.2.0 was released on 2019-07-11.
- cordova-plugin-camera@4.1.0 was released on 2019-07-11.
- cordova-plugin-file@6.0.2 was released on 2019-07-11.
- cordova-plugin-geolocation@4.0.2 was released on 2019-07-11.
- cordova-plugin-inappbrowser@3.1.0 was released on 2019-07-11.
- cordova-plugin-media@5.0.3 was released on 2019-07-11.
## Mailing list activity:
- dev@cordova.apache.org:
- 189 emails sent to list (234 in previous quarter)
- issues@cordova.apache.org:
- 82 emails sent to list (139 in previous quarter)
## JIRA activity:
- 0 JIRA tickets created in the last 3 months (JIRA has been shut down)
- 53 JIRA tickets closed/resolved in the last 3 months
## Github activity:
Issue close rate of 63%:
- 268 Github Issues created in the last 3 months
- 170 Github Issues closed in the last 3 months
PR close rate of 180%:
- 78 Github Pull Requests created in the last 3 months
- 141 Github Pull Requests closed/merged in the last 3 months
-----------------------------------------
Attachment S: Report from the Apache cTAKES Project [Pei Chen]
## Description:
Apache clinical Text Analysis and Knowledge Extraction System (cTAKES) is
an open-source natural language processing system for information extraction
from electronic medical record clinical free-text.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
- Committee continues to work on the future release (4.0.1)
- Committee continues to work on bug fixes and improvements documented in Jira
## Health report:
- The community continues to be moderately active.
- There are new questions/suggestions from new users on the mailing lists
- There is steady increase in interest and growth in the community
based on the activity on the mailing lists
## PMC changes:
- Currently 31 PMC members.
- Last PMC addition was Gandhi Rajan on Thu Jul 12 2018
## Committer base changes:
- Currently 38 committers.
- Last committer addition was Gandhi Rajan at Tue Nov 14 2017
## Releases:
- Last release was 4.0.0 on Thu Apr 27 2017
- 3.2.2 was released on May 30 2015
- 3.2.1 was released on Dec 10 2014
## Mailing list activity:
There was an increase in number of emails/discussions sent to the dev @
mailing lists with less subscribers.
- dev@ctakes.apache.org:
dev@ had a 79% increase in traffic in the past quarter (106 emails
compared to 59)
- user@ctakes.apache.org:
user@ had a 80% decrease in traffic in the past quarter (7 emails
compared to 34)
-----------------------------------------
Attachment T: Report from the Apache Curator Project [Jordan Zimmerman]
## Description:
Apache Curator is a Java/JVM client library for Apache ZooKeeper, a
distributed coordination service. It includes a highlevel API framework and
utilities to make using Apache ZooKeeper much easier and more reliable. It
also includes recipes for common use cases and extensions such as service
discovery and a Java 8 asynchronous DSL.
## Issues:
there are no issues requiring board attention at this time
## Membership Data:
Apache Curator was founded 2013-09-17 (6 years ago)
There are currently 13 committers and 13 PMC members in this project.
The Committer-to-PMC ratio is 1:1.
Community changes, past quarter:
- No new PMC members. Last addition was Shay Shimony on 2019-04-17.
- No new committers. Last addition was Shay Shimony on 2019-04-18.
## Project Activity:
Activity is fairly normal. A few PRs here and there. Some emails, etc. No
issues.
## Community Health:
I believe the community health is good. Also, note, always activity on
Stackoverflow
-----------------------------------------
Attachment U: 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 (6 years ago)
There are currently 34 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.
- No new committers. Last addition was Alexander Falb on 2018-08-01.
## Project Activity:
Project Activity is right now on maintenance mode until
new requirements or new ideas pop up.
Apache DeltaSpike is widely used in JavaEE projects and we are
planing for a JakartaEE version once it is released with
the new package names.
## Community Health:
Community is ok, but in a 'maintenance mood' as well.
We are right now discussing a PMC chair rotate.
-----------------------------------------
Attachment V: Report from the Apache Eagle Project [Edward Zhang]
## Description:
- Apache Eagle is an open source analytics solution for identifying security
and performance issues instantly on big data platforms.
## Issues:
- There are no issues requiring board attention at this time
## Activity:
- One developer from siddhi open source project volunteered to upgrade siddhi
version from 3.x.x to 5.x.x
- Some users reported some Eagle compiling issue and out of memory issue,
community can provide help
## Health report:
- Eagle community can answer questions for users who have tried Eagle
## PMC changes:
- Currently 16 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Deng Lingang on Mon May 08 2017
## Committer base changes:
- Currently 18 committers.
- No new committers added in the last 3 months
- Last committer addition was Jay Sen at Thu Mar 16 2017
## Releases:
- Last release was 0.5.0 on Sat Sep 09 2017
## Jira activity
- 2 JIRA tickets created in the last 3 months
-----------------------------------------
Attachment W: Report from the Apache Falcon Project [Pallavi Rao]
-----------------------------------------
Attachment X: Report from the Apache Felix Project [Karl Pauls]
## Description:
Apache Felix is a project aimed at implementing specifications from the OSGi
Alliance as well as implementing other supporting tools and technologies
aligned with OSGi technology.
## Issues:
There are no issues requiring board attention at this time.
## Membership Data:
Apache Felix was founded 2007-03-28 (12 years ago)
There are currently 67 committers and 27 PMC members in this project.
The Committer-to-PMC ratio is roughly 9:4.
Community changes, past quarter:
- Georg Henzler was added to the PMC on 2019-06-10
- No new committers. Last addition was Bertrand Delacretaz on 2018-12-18.
## Project Activity:
- Existing implementations have been improved/enhanced based on community
feedback.
- Released 11 components.
## Community Health:
- Overall the project is in ok health.
- There wasn't a lot of activity in this quarter overall.
- Questions on the user list are answered, development concerns are either
discussed on the mailing list or directly in the JIRA issues.
- The project as well as the OSGi community in general is still in the process
of adapting to JPMS and its long term impact.
- We need to be on the lookout for new committers.
- We had no issues voting on releases and JIRA issues are generally addressed
promptly.
-----------------------------------------
Attachment Y: Report from the Apache Flex Project [Olaf Krüger]
## Description:
Apache Flex is an application framework for easily building Flash-based
applications for mobile devices, the browser and desktop.
## Issues:
There are no issues requiring board attention at this time.
## Flex runtimes
The available, free to use Flex runtimes are the Adobe Flash Player and Adobe
AIR. In 2017, Adobe already announced the EOL of the Flash Player for the end
of 2020. Since June 2019, Harman has undertaken AIR platform support and
feature development. Harman provides AIR on a commercial basis, with a free
version available for certain eligible individuals/companies. [1] Users can
subscribe to the Harman mailing list in order to get the latest AIR related
news.
## Activity:
Activity on the mailing lists among the users decreased by about an average of
50% the previous three months. It's obvious that the upcoming EOL of the
FlashPlayer has an impact on Flex and its user base. Some folks migrate to AIR
and stick with Flex, others porting their apps to other technologies.
## PMC changes:
- Currently 45 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Olaf Krüger on Mon Aug 28 2017
## Committer base changes:
- Currently 69 committers.
- No new committers added in the last 3 months
- Last committer addition was Greg Dove at Wed Sep 07 2016
## Releases:
- Apache Flex SDK 4.16.1 on 2017-11-22
- Apache Flex Installer 3.3.2 on 2018-07-09.
## JIRA activity:
- 3 JIRA tickets created in the last 3 months
- 0 JIRA tickets closed/resolved in the last 3 months
[1] https://airsdk.harman.com/
-----------------------------------------
Attachment Z: Report from the Apache Flink Project [Stephan Ewen]
## Description:
Apache Flink is a distributed data streaming system for batch and streaming
data analysis on top of a streaming dataflow engine. Flink's stack contains
functional batch and streaming analysis APIs in Java, Scala, Python, and
libraries for various use cases.
Flink interacts and integrates with several Apache projects in the broader
ecosystem of data storage and computing, such as Apache Beam, Calcite,
Hadoop, Mesos, Kafka, HBase, Cassandra, and various others.
## Issues:
- There are no issues that require board attention.
## Membership Data:
PMC members added since the last board report:
- Jincheng Sun joined the PMC on June 24th, 2019
- Kurt Young joined the PMC on July 23rd, 2019
- Kostas Kloudas joined the PMC on August 31st, 2019
Committers added since the last board report:
- Rong Rong was added as committer on July 15th, 2019
- Becket Qin was added as committer on July 18th, 2019
- Zhijiang Wang was added as committer on July 22nd, 2019
- Hequn Cheng was added as committer on August 5th, 2019
- Andrey Zagrebin was added as committer on August 17th, 2019
- Zili Chen was added as committer on September 12th, 2019
The newest PMC member is Kostas Kloudas, joined on August 31st, 2019.
The newest committer is Zili Chen, joined on September 12th, 2019.
Flink currently has 51 committers and 24 PMC members.
## Releases
The following releases were made since the last board report:
- 1.8.1 was released on July 7th, 2019.
- 1.8.2 was released on September 11th, 2019
- 1.9.0 was released on August 22nd, 2019.
- shaded-8.0 was released on August 8th, 2019.
## Project Activity:
- The community is in a strong growth phase. The past quarter saw the
addition of six new committers and three new PMC members to help support
the community growth.
- The Flink community passed its first set of bylaws to more formally define
how decisions are made for various types of contributions. The community
felt that with growing size of active committer base and with the
different backgrounds and experiences of the committers, bylaws will be
helpful to keep the project organized.
- Parts of the bylaws discussion resulted also in reinforcing the process
for new features (FLIPs - Flink Improvement Proposals), which resulted in
a big number of new proposals and high activity on their discussion
threads.
- Also for smaller contributions, the community is pushing more for early
discussions and checking whether there is capacity among committer to
shepherd proposed changes.
- The community is periodically summing up the ongoing development threads
on the roadmap page: https://flink.apache.org/roadmap.html
- The community started working on the Flink 1.10 release. The release will
continue many of the threads started for 1.9, like the Table API, SQL
engine, integration with Hive, support for Python. Other threads include,
for example, a new streaming state backend, sources, as well as making
configuration and resource management simpler.
- Flink Forward Berlin will be on October 7-9. The program is online:
https://europe-2019.flink-forward.org/speakers Apache committers can
contact the organizers for a free pass.
## Community Health:
Mailing lists continue to be very active:
- user@f.a.o (1767 mails/quarter)
- user-zh@f.a.o (714 mails/quarter)
- dev@f.a.o (3543 mails/quarter)
The dev mailing list saw a big increase in activity due to feature and design
discussions for the 1.10 release and the reinforced community processes.
The user-zh mailing list seems to be building momentum as well and more
than doubled in the last quarter.
JIRA continues to be active as well, 1212 JIRA tickets created, 910 JIRA
tickets resolved in the last 3 months.
-----------------------------------------
Attachment AA: Report from the Apache Guacamole Project [Mike Jumper]
## Description:
The mission of Apache Guacamole is the creation and maintenance of software
related to providing performant, browser-based remote access
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache Guacamole was founded 2017-11-14 (2 years ago)
There are currently 12 committers and 9 PMC members in this project.
The Committer-to-PMC ratio is 4:3.
Community changes, past quarter:
- No new PMC members. Last addition was Carl Harris on 2017-11-19.
- No new committers. Last addition was Joel Best on 2019-01-30.
## Project Activity:
Project activity is centered around finalizing the outstanding tasks blocking
release of 1.1.0. The main obstacle to releasing 1.1.0 is still GUACAMOLE-249,
as noted in last quarter's report. Significant progress has been made outside
of that issue, as most other issues within 1.1.0 scope have been resolved over
the course of the last quarter.
## Community Health:
The community continues to be involved and healthy. Overall commit activity
has increased, reflecting the accelerating effort to release 1.1.0. The number
of code contributors and pull requests opened/closed has also almost doubled
relative to last quarter.
-----------------------------------------
Attachment AB: Report from the Apache Gump Project [Stefan Bodewig]
Apache Gump is a cross-project continuous integration server. Gump's intention
isn't so much to be a CI server but rather a vehicle that makes people look
beyond their project's boundaries and helps the projects to collaborate.
Gump is written in Python and supports several build tools and version control
systems. The Apache installation of Gump builds ASF as well as non-ASF
projects and their dependencies. It started in the Java part of the foundation
but also builds projects like APR, HTTPd and XMLUnit.NET.
# Summary
Some infrastructure activity, but really no changes compared to the last
quarter.
# Releases
Gump has never done any releases. One reason for this is that the ASF
installations of Gump work on the latest code base almost all of the time
following its "integrate everything continuously" philosophy.
# Activity
Our migration to Confluence is complete and we've abandoned our Moin wiki
instance. Around at the same time Mark and the Infra team set up a new VM for
Gump which has become our workhorse by now.
The Tomcat and Forrest communities are still using Gump actively.
# Changes to the Roster
All ASF committers have write access to the metadata that configure the ASF
installations.
The last changes to the PMC have seen Konstantin Kolinko and Mark Thomas join
in November 2014.
-----------------------------------------
Attachment AC: Report from the Apache Hama Project [Chia-Hung Lin]
-----------------------------------------
Attachment AD: Report from the Apache Helix Project [Kishore G]
-----------------------------------------
Attachment AE: Report from the Apache Hive Project [Ashutosh Chauhan]
## Description:
The mission of Hive is the creation and maintenance of software related to Data
warehouse infrastructure using the Apache Hadoop Database
## Issues:
No issues requiring board attention at this time.
## Membership Data:
Apache Hive was founded 2010-09-21 (9 years ago)
There are currently 87 committers and 47 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 Zoltan Haindrich on 2018-10-29.
- David Mollitor was added as committer on 2019-09-11
- Miklos Gergely was added as committer on 2019-07-15
- Raj K Singh was added as committer on 2019-07-25
## Project Activity:
We made few maintenance releases in this quarter to facilitate
interoperability with other projects.
Recent releases:
3.1.2 was released on 2019-08-26.
2.3.6 was released on 2019-08-22.
2.3.5 was released on 2019-05-14.
## Community Health:
Overall community is healthy. Number of commits went down slightly (!7%) but
number of distinct committers were up (3%). Also activity on github has
increased this quarter. These metrics indicates our contributors and
committers are engaged in community. Also, we saw increase in mailing list
activity in user list this quarter which is encouraging.
-----------------------------------------
Attachment AF: Report from the Apache Incubator Project [Justin Mclean]
# Incubator PMC report for September 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/September2019
There are presently 48 podlings incubating. In August, podlings executed
9 distinct releases. We added three new IPMC members and no IPMC members
retired.
We have two new podlings this month DolphinScheduler and MesaTEE. There have
been a couple of ongoing enquires about new projects, and some proposals are
being worked on. A couple of podlings are heading towards graduation in the
next few months. Druid was up for graduation last month but withdrew as
there's a trademark issue with its name.
Several podlings Amaterasu, Tamaya and Tephra didn't submit a report and
have been asked to do so next month. Tamaya has now failed to report twice
in a row.
Amaterasu has failed to report three times in a row. It looks like the
PPMC is missing and there's little or no activity on the list. One final
chance will be given to the project to explain what it status it and how it
hopes to graduate before it is asked to retire.
Omid and ShardingSphere submitted insufficient reports and will be
asked to report next month.
A few mentors have been added and removed in various projects.
There were 3 IP clearances.
The incubator web site menu was reorganized to group similar content
together, and further work was done on simplifying the language used on the
incubator policy page. A few other pages were also improved.
The new disclaimer policy accepted by the board last month has received
good feedback, and we've had a podling already make a release with it. The
board asked for some updated documentation on the new disclaimer, and that
was undertaken.
Some podlings are still struggling to get 3 +1 votes on their release by
mentors and other IPMC votes are needed to make releases. However, those
votes seem to be happing quite quickly with several IPMC members checking
releases.
A new mentor guidance document is n the process of being created, so far
not many mentors have contributed to this. Given the many years of
experience over many mentors, it would be nice to see mentors contribute to
this. This document would help future mentors and podling deal with
everyday situations that come up that they may be unsure of how to deal
with.
The IPMC consider dropping that ASF member can join just back asking.
Looking at mentor it more than that mentors join this way go missing, other
than those who are voted it. Some IPMC member didn't think this was a good
idea, so the policy stands.
There was a long discussion on the requirement of IPMC vote on podling
release which included several suggested changes to policy and new ideas.
Consensus was not able to be reached on any changes, and the discussion has
stalled. The main issue being that PMC votes are needed on releases and
some IPMC members want to do away with IPMC votes on releases altogether.
A new project was suggested as an experiment to try this out (exact details
still to be worked out), but so far that has not happened. It was even
suggested by a couple of IPMC members that a new incubator project be made.
It may be best to wait until we see the impact of the work in progress
disclaimer before revisiting the IPMC vote situation.
There will be a Podling's Shark Tank at the upcoming ApacheCON North
America and server talks on incubating subjects and projects.
ECharts is showing slow progress and thought they were ready to graduate
when they were not. A face to face meeting with several experienced IPMC
members has been organized at ApacheCon to get them back on the right track.
There was a discussion on the private on some podlings that probably
should be retired.
## Community
### New IPMC members:
- Gian Merlino
- Zhijie Shen
- Jamie Mark Goodyear
### People who left the IPMC:
None
## New Podlings
DolphinScheduler
MesaTEE
## Podlings that failed to report, expected next month
- Amaterasu
- Tamaya
- Tephra
## Graduations
- None
The board has motions for the following:
- Apache Rya
- Apache SINGA
## Releases
The following releases entered distribution during the month of
August:
- Apache Flagon UserALE.js v2.0.2
- DataSketches memory 1.1.0
- Druid 0.15.1
- IoTDB 0.8.0
- Milagro crypto 1.0.0
- Myriad 0.4.0
- ShardingSphere 4.0.0
- Superset 0.34.0
- Tuweni 0.8.1
## IP Clearance
- Apache Milagro - Decentralized Trust Authority
- Apache Celix - Websocket pubsub admin
- Apache Beam ZetaSQL Translator
## Legal / Trademarks
None.
## Infrastructure
None.
## Miscellaneous
Nothing of interest.
|----------------------------------------------------------------------
Table of Contents
[BRPC](#BRPC)
[Crail](#Crail)
[Daffodil](#Daffodil)
[DLab](#DLab)
[Druid](#Druid)
[Hivemall](#Hivemall)
[Iceberg](#Iceberg)
[IoTDB](#IoTDB)
[Marvin-AI](#Marvin-AI)
[Myriad](#Myriad)
[Nemo](#Nemo)
[Omid](#Omid)
[PonyMail](#PonyMail)
[SAMOA](#SAMOA)
[SDAP](#SDAP)
[ShardingSphere](#ShardingSphere)
[SINGA](#SINGA)
[Spot](#Spot)
[Superset](#Superset)
[Taverna](#Taverna)
[Toree](#Toree)
[Warble](#Warble)
|----------------------------------------------------------------------
--------------------
## BRPC
brpc is an industrial-grade RPC framework for building reliable and high-
performance services.
brpc has been incubating since 2018-11-13.
### Three most important unfinished issues to address before graduating:
1. finish Apache release regularly
2. attract more users and contributors
3. build website
### 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?
brpc team had organized a forum on Aug 3rd in Shanghai China, over 100
engineers attended it,
Contributors from Baidu/bilibili/iQiyi shared their experience on using
brpc in their projects.
we hope to attract more engineers to use and contribute to brpc project.
A new team from baidu shanghai office have began to working on brpc,
including liuzhiwei, shizhan, tangjie, xingyongxu and yuhao.
### How has the project developed since the last report?
we proposed the first apache release,
the vote of rc1 was failed due to one 3rd party's license missed from
LICENSE.
the vote of rc2 was still on, waiting for JB's comments.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [x] Working towards first release
- [x] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
Still working on the first release
### When were the last committers or PPMC members elected?
No new ones.
### Have your mentors been helpful and responsive?
JB promised to check our release candidate 2.
Von gave us many suggestions about how to discuss in maillist.
### Signed-off-by:
- [X] (brpc) Kevin A. McGrail
Comments: None. Good work on the rc2 work. Thanks to Von and JB for
their input.
- [ ] (brpc) Jean-Baptiste Onofré
Comments:
- [X] (brpc) Von Gosling
Comments: There is some issues about rc2, begin to prepare rc3. What's
more, I'm encouraging them to interact more in the community,
and I'm sure their first major release will be back soon after enter
the incubator
### IPMC/Shepherd notes:
--------------------
## Crail
Crail is a storage platform for sharing performance critical data in
distributed data processing jobs at very high speed.
Crail has been incubating since 2017-11-01.
### Three most important unfinished issues to address before graduating:
1. Community building: Increase on number of contributors and users.
2. Further increase project visibility by establishing a convincing use
cases of Crail.
3. Make Crail better consumable / cooperate with other projects on Crail
integration.
### 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 presented an Apache Crail based, unified ephemeral data storage
architecture at USENIX ATC'19 in July.
- The USENIX ATC paper, lightening talk, and talk are online.
### How has the project developed since the last report?
- Incorporated pull requests to fix several resource management issues.
- Working towards new 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:
2018-11-26
### When were the last committers or PPMC members elected?
December 4th, 2018
### Have your mentors been helpful and responsive?
Our mentors are very helpful.
### Signed-off-by:
- [x] (crail) Julian Hyde
Comments: Activity is slow but steady. A paper & talk at a major
conference should help build community. It's also about time for a
release;
I will make a suggestion on the dev list.
- [x] (crail) Luciano Resende
Comments:
- [x] (crail) Felix Cheung
Comments: Agreed with report. Let's try to get more traffic on dev
list also.
### IPMC/Shepherd notes:
--------------------
## Daffodil
Apache Daffodil is an implementation of the Data Format Description Language
(DFDL) used to convert between fixed format data and XML/JSON.
Daffodil has been incubating since 2017-08-27.
### Three most important unfinished issues to address before graduating:
1. Increase community growth and participation from outside Tresys
(main priority)
2. Work with other Apache projects where Daffodil could provide
extra functionality
3. Establish a frequent release schedule
### Are there any issues that the IPMC or ASF Board need to be aware of?
- None
### How has the community developed since the last report?
- Voted to add two new PPMC members. One accepted and has been added.
One declined due to CLA concerns
- Accepted for talk at ApacheCon NA 2019
- Accepted for Podling SharkTank at ApacheCon NA 2019
- Gained a new involved contributor with multiple improvements and
bug fixes
- Outside contributor released tutorials related to DFDL and Daffodil
### How has the project developed since the last report?
- Released Apache Daffodil (incubating) 2.4.0
- 42 commits merged from 5 different contributors
- 54 issues created, 57 issues resolved--improvements made at keeping
up with new bugs
- Greatly improved compatibility with IBM DFDL implementation
- Added new features to continue to meet DFDL specification
- Added new extensions to be proposed as additions to future DFDL
versions
### 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:
Daffodil PPMC members are attendeding ApacheCon NA and are scheduled
for a talk and are taking place in the podling shark tank. Plan to
search out other opportunties at the conference to grow our community.
### Date of last release:
- 2019-07-12
### When were the last committers or PPMC members elected?
- 2019-06-20 - Brandon Sloane (PPMC and comitter)
### Have your mentors been helpful and responsive?
Yes, mentors have been helpful and responsive.
### Signed-off-by:
- [X] (daffodil) Dave Fisher
Comments: Once some more PPMC from other entities are brought onboard
the podling will be ready to graduate.
- [X] (daffodil) Christofer Dutz
Comments: I also hope the acna19 participation will help attract new
people.
### IPMC/Shepherd notes:
--------------------
## DLab
DLab is a platform for creating self-service, exploratory data science
environments in the cloud using best-of-breed data science tools.
DLab has been incubating since 2018-08-20.
### Three most important unfinished issues to address before graduating:
1. Come up with a new name for DLab
2. Extend the amount of committers. The plan here is to participate in
a number of conferences, starting with ApacheConf in Berlin on October 23,
EPAM SEC conference in Gansk on SolutionsHub area
3. After release 2.2 is made, the team will have to do major refactoring
of the code, updating of product documentation, which might potentially
slow down the process of releasing version 2.3
### 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?
A new committer is added:
- Adams Disturber (Andrii Dumych)
Also awaiting for committer Mykola Bodnar, pending account creation. ICLA
files are signed off and submitted, waiting for Apache ID to be created.
### How has the project developed since the last report?
Team is actively working on release 2.2 features.
There will be many new features and conceptual changes introduced in
upcoming release. We are introducing the concept of projects within DLab,
which will allow to control permissions for groups of DLab users,
improve collaboration capabilities.
Major improvements will be made in terms of GCP platform deployment.
GCP will support the majority of the features, currently available in
DLab for AWS and Azure Clouds.
One of the conceptual features implemented is the ability to provision
DLab's self-service noe in k8s and being able to integrate with many
identity providers, supporting OAuth2 and SAML2.0 via Keycloak.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [ ] Working towards first release
- [X] Working towards next release
- [X] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
2019-15-04
### When were the last committers or PPMC members elected?
2019-20-08
### Have your mentors been helpful and responsive?
Yes, mentors have been helpful and responsive.
### Signed-off-by:
- [ ] (dlab) P. Taylor Goetz
Comments:
- [X] (dlab) Henry Saputra
Comments:
- [ ] (dlab) Konstantin I Boudnik
Comments:
- [X] (dlab) Furkan Kamaci
Comments:
### IPMC/Shepherd notes:
--------------------
## Druid
Druid is a high-performance, column-oriented, distributed data store.
Druid has been incubating since 2018-02-28.
### Three most important unfinished issues to address before graduating:
1. Resolve trademark issues
### Are there any issues that the IPMC or ASF Board need to be aware of?
We will need to resolve the trademark issues before graduation, which the
board has been made aware of privately. We are grateful for the board's
support, and we will work with trademarks@ to resolve the issues.
### How has the community developed since the last report?
- A healthy, constant flow of bug fixes, quality improvements and new
features are still ongoing at https://github.com/apache/incubator-druid.
- Two Druid community meetups have been scheduled on 9/17 and 9/19.
### How has the project developed since the last report?
- Since the last report, we have had a total of 293 commits from 30
contributors.
- The project website has been migrated to Apache infrastructure.
- We have released 2 versions, 0.15.0 and 0.15.1.
- We have code frozen the upcoming 0.16.0 release branch and are preparing
the first release candidate.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [ ] Working towards first release
- [ ] Community building
- [x] Nearing graduation
- [ ] Other:
### Date of last release:
- Druid 0.15.1-incubating was released on Aug 15, 2019.
### When were the last committers or PPMC members elected?
The Druid PPMC elected 2 new committers to the project on Sep 2,
2019.
### Have your mentors been helpful and responsive?
Julian has continued to be very helpful.
### Signed-off-by:
- [x] (druid) Julian Hyde
Comments: We got very close to graduation this month;
the issues that prevented graduation were frustrating to
everyone but people are working hard to resolve them.
Well done.
- [ ] (druid) P. Taylor Goetz
Comments:
- [ ] (druid) Jun Rao
Comments:
### IPMC/Shepherd notes:
--------------------
## Hivemall
Hivemall is a library for machine learning implemented as Hive
UDFs/UDAFs/UDTFs.
Hivemall has been incubating since 2016-09-13.
### Three most important unfinished issues to address before graduating:
1. Community growth (committers and users)
2. One or more Apache Releases as an Incubator project
3. Documentation improvements
### Are there any issues that the IPMC or ASF Board need to be aware of?
None
### How has the community developed since the last report?
* Takuya (PPMC) will give a talk at ApacheCon, LAS VEGAS.
* Got and merged a pull request from new external contributor.
* Github watchers/stars are gradually increasing:
234 stars as of Mar 1 (was 199 on Mar 1)
* Twitter account @ApacheHivemall followers are gradually increasing:
208 followers as of Mar 1 (was 189 on Mar 1)
### How has the project developed since the last report?
* Working toward the 3rd Apache release. After HIVEMALL-245 is fixed,
it will be ready to the vote.
Since the last report, we have
* In the last 3 months, we opened 10 JIRA issues and closed 7 JIRA
issues as seen in https://goo.gl/QFQEF5 (as of Sept 5)
* Created 7 Pull Requests and closed 5 Pull Requests between May 1st and
Aug 31th
### How would you assess the podling's maturity?
The page of community growth is slow. No much active developers.
Considering a pivot of the project scope to get more attention:
moving from Hive/Spark to a standalone library focusing on Python/Jupyter
notebook integration.
- [ ] Initial setup
- [ ] Working towards first release
- [x] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
2018-12-03
### When were the last committers or PPMC members elected?
- Elected Jerome Banks as a committer on April 2, 2018.
### Have your mentors been helpful and responsive?
- Koji is active at mentoring.
### Signed-off-by:
- [ ] (hivemall) Xiangrui Meng
Comments:
- [ ] (hivemall) Daniel Dai
Comments:
- [x] (hivemall) Koji Sekiguchi
Comments:
### IPMC/Shepherd notes:
Justin Mclean: The included stats don't really mean much to anyone
outside of your project, please drop them from future reports.
--------------------
## Iceberg
Iceberg is a table format for large, slow-moving tabular data.
Iceberg has been incubating since 2018-11-16.
### Three most important unfinished issues to address before graduating:
1. Make the first Apache release.
(https://github.com/apache/incubator-iceberg/milestone/1)
2. Grow the Iceberg community
3. Add more committers and PPMC members
### 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?
The community continues to grow steadily. In the last month:
* 59 pull requests have been merged
* 17 people contributed the merged PRs
* 18 issues have been closed, 22 issues were opened
For comparison, the last report had 74 pull requests merged over 3 months.
### How has the project developed since the last report?
* License documentation has been completed for the Java project,
unblocking
the first release
* Added more documentation to iceberg.apache.org
* Started vectorized read branch with significantly better performance
* Added metadata tables
* Added configuration to control statistics and truncate long values
* Improved Hive Metastore integration
* A working python read path has been submitted in PRs
### How would you assess the podling's maturity?
- [ ] Initial setup
- [x] Working towards first release
- [x] Community building
- [x] Nearing graduation
- [ ] Other:
### Date of last release:
* No release yet
### When were the last committers or PPMC members elected?
* Anton Okolnychyi was added 30 August 2019
### Have your mentors been helpful and responsive?
Yes
### Signed-off-by:
- [x] (iceberg) Ryan Blue
Comments:
- [ ] (iceberg) Julien Le Dem
Comments:
- [X] (iceberg) Owen O'Malley
Comments:
The project also gave two presentations:
* Berlin Buzzwords (June 2019)
* ApacheCon NA (Sep 2019)
Iceberg is being used in production at Netflix on huge tables, up to
25 petabytes.
- [X] (iceberg) James Taylor
Comments:
- [X] (iceberg) Carl Steinbach
Comments:
Approval added by Ryan Blue, Carl had trouble editing the new report
location
### IPMC/Shepherd notes:
Justin Mclean: The included stats don't really mean much to anyone
outside of your project, please drop them from future reports.
The community growth section might as well be blank.
I find it surprising that this project thinks that it is near graduation.
Please discuss this with your mentors.
--------------------
## IoTDB
IoTDB is a data store for managing large amounts of time series data such
as timestamped data from IoT sensors in industrial applications.
IoTDB has been incubating since 2018-11-18.
### Three most important unfinished issues to address before graduating:
1. Make the community (both the contributors and committers/PPMCs)
more diverse and learn to discuss things on the mailing list.
2. More committers should know how to release a version.
3. Write more documentation to help new contributors.
### Are there any issues that the IPMC or ASF Board need to be aware of?
No.
### How has the community developed since the last report?
1. Some new contributors joined the community. E.g., PR#339 comes
from a new contributor and it is really an interesting feature.
2. Some contributors (who are not committers yet) are more active
than before. E.g., Boris Zhu and Jack Tsai.
3. More users began to report their issues. E.g., issue #171, #184
and #186.
As all the above contributions and contributors are not from the
institutions/companies where initial committers are, we think it is a
good signal that indicates more guys noticing the community.
### How has the project developed since the last report?
1. IoTDB releases its first Apache version: v0.8.0 !
2. IoTDB is more stable and the performance is far better than
before. However, the version is incompatible with previous version (which
are released before IoTDB is denoted to ASF).
3. In v0.8.0, many issues are resolved (see release notes:
http://iotdb.apache.org/#/Materials/Release%20Notes)
### 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-08-25
### When were the last committers or PPMC members elected?
2019-07-15
### Have your mentors been helpful and responsive?
They are helpful, especially in the process of releasing the first
version.
### Signed-off-by:
- [X] (iotdb) Justin Mclean
Comments: Good to see your first release out, but more active
involvement by the PPMC is needed in veting releases. While it improved,
still more discussion needs to happen on the mailing list.
- [X] (iotdb) Christofer Dutz
Comments: I really would like to see more mailing list usage, cause
the number of commit messages is in strong contrast to the discussions.
I as a mentor some time don't have a clue what the project is working
on.
- [ ] (iotdb) Willem Ning Jiang
Comments:
- [X] (iotdb) Kevin A. McGrail
Comments: Congrats on 0.8.0!!!!!
### IPMC/Shepherd notes:
----------------
## Marvin-AI
Marvin-AI is an open-source artificial intelligence (AI) platform that helps
data scientists, prototype and productionalize complex solutions with a
scalable, low-latency, language-agnostic, and standardized architecture
while
simplifies the process of exploration and modeling.
Marvin-AI has been incubating since 2018-08-21.
### Three most important issues to address in the move towards graduation:
1.Move development infrastructure to Apache
2.Build Community
3.Build Releases
### Are there any issues that the IPMC or ASF Board need to be aware of?
* None
### How has the community developed since the last report?
* Participation in the local PyData event with a presentation of the
project by Rafael Novello.
* Workshop participation in University of São Paulo with a presentation
of the project by Zhang Yifei.
* Participation in the B2W Summit event with a presentation of the
project by Zhang Yifei.
### How has the project developed since the last report?
* New public engine(post-purchase service prediction) in construction
by contributors from University of São Carlos.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [x] Working towards first release
- [x] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
XXXX-XX-XX
### When were the last committers or PPMC members elected?
* Wei Chen added as new PPMC member (2019-06-07)
### Have your mentors been helpful and responsive?
* At least two of the mentors are sometimes active.
### Signed-off-by:
- [x](marvin-ai) Luciano Resende
Comments:
Removed Jim as mentor per his resignation
The report mention that there are some collaboration
with University of São Carlos, but the dev list seems
very quiet since July. Where are the communications
and technical discussions happening ?
- [ ](marvin-ai) William Colen
Comments:
--------------------
## Myriad
Myriad enables co-existence of Apache Hadoop YARN and Apache Mesos together
on the same cluster and allows dynamic resource allocations across both
Hadoop and other applications running on the same physical data center
infrastructure.
Myriad has been incubating since 2015-03-01.
### Three most important unfinished issues to address before graduating:
1. Builds Apache Myriad releases regularly
2. Attract more users and contributors. Community growing.
3. Attract new mentors for helping the project towards the Apache Way.
### Are there any issues that the IPMC or ASF Board need to be aware of?
We need new mentors, we have only one active mentor right now.
We have to increase the community and we have to increase the number
of mentors too in order to help us to address the Apache way with solid
foundations.
### How has the community developed since the last report?
We have four active committers (PPMCs) right now. A new committer since
the last report.
This is a small increment from the community growing point of view, but
it helps regarding the minimal amount of PPMCs for achieving a release cycle
with regularity.
### How has the project developed since the last report?
The most important thing is the activity of creating new releases in a
regular way. The Apache resources (project page, documentation page, …)
are maintained and enhanced with new content. Taking into account the
effort of rebooting the
project (more than two years orphaned), the project is slowly addressing
the right way, and
we consider the project is successfully rebooted right now. This state
allow us working towards
attract new users and contributors in our humble opinion.
### 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: New important features focuses in production environments
for attracting new users.
### Date of last release:
The 0.4.0 release was issued on Aug 25, 2019
### When were the last committers or PPMC members elected?
2019-08-02 New committer/PMC member Oscar Fernandez
### Have your mentors been helpful and responsive?
We have only two mentors right now. One of the is for ever missing,
and the other is ready for help when the project needs. So we have only
one active mentor. This is an issue to address with the help of IPMC.
### Signed-off-by:
- [ ] (myriad) Benjamin Hindman
Comments:
- [X] (myriad) Ted Dunning
Comments:
### IPMC/Shepherd notes:
Justin Mclean: Please ask for another mentor on the incubator general list.
--------------------
## Nemo
Nemo is a data processing system to flexibly control the runtime behaviors
of a job to adapt to varying deployment characteristics.
Nemo has been incubating since 2018-02-04.
### Three most important unfinished issues to address before graduating:
1. Grow the community (committers, contributors, users)
2. Create more releases
### Are there any issues that the IPMC or ASF Board need to be aware of?
None.
### How has the community developed since the last report?
* Attracted new contributors through the GSoC program
* Two GSoC students finished up their projects successfully.
* Presented Nemo at Berlin Beam Summit 2019.
* Discussion with Google Beam, Shopify, Seznam,cz developers
At the Beam Summit Europe 2019, which occurred in Berlin from
June 19th to the 20th, there had been many discussions regarding
Nemo from engineers working in the industry, as well as
with engineers working with Apache Beam. There had been people
from various companies, as Shopify and Seznam.cz, facing problems
as large-shuffle and data skew, and had shown a lot of interest
in using the Apache Nemo runner. Also, in the following ApacheCon
summit happening in Vegas in September, the Apache Beam team will
demonstrate running their workloads using the Apache Nemo runner.
### How has the project developed since the last report?
* Integrate Apache Crail with Nemo
* Off-heap support to improve shuffle speed
* DirectByteBufferInput/OutputStream for
Off-heap SerializedMemoryStore
* Off-heap SerializedMemoryStore
* Off-heap memory management (reuse ByteBuffer)
* Separation of JVM heap region and off-heap memory region
* Enable Nemo single-stage programs to run on a serverless
framework, AWS Lambda
* Refactor Executor to support different types of execution
environment
* Add a Lambda Executor
* Add a compiler pass for Lambda
* Progress on a ML-based smart compiler
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [ ] Working towards first release
- [X] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
Release 0.1 on Dec. 31, 2018
### When were the last committers or PPMC members elected?
None yet.
Recent two contributors are good committer candidates.
### Have your mentors been helpful and responsive?
Yes.
### Signed-off-by:
- [X] (nemo) Davor Bonaci
Comments: Lots of good work on community building, awaiting results.
In-project activity lower than before.
- [X] (nemo) Hyunsik Choi
Comments:
- [X] (nemo) Byung-Gon Chun
Comments:
- [ ] (nemo) Jean-Baptiste Onofre
Comments:
- [X] (nemo) Markus Weimer
Comments:
### IPMC/Shepherd notes:
--------------------
## Omid
Omid is a flexible, reliable, high performant and scalable ACID
transactional framework that allows client applications to execute
transactions on top of MVCC key/value-based NoSQL datastores (currently
Apache HBase) providing Snapshot Isolation guarantees on the accessed data.
Omid has been incubating since 2016-03-28.
### Three most important unfinished issues to address before graduating:
1. Do podling name search.
2.
3.
### 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?
N/A
### How has the project developed since the last report?
N/A
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [ ] Working towards first release
- [ ] Community building
- [X] Nearing graduation
- [ ] Other: New important features focuses in production environments
### Date of last release:
2019-05-21
### When were the last committers or PPMC members elected?
2018-09-25
### Have your mentors been helpful and responsive?
Our mentors were amazingly helpful, they help us finding performance and
correctness bugs, as well as helped in the release process by evaluating
the release and vote internally and externally.
### Comments
Going forward, we need to document the additional features added for the
integration with Apache Phoenix, as well as, the low latency algorithm.
### Signed-off-by:
- [X] (omid) Alan Gates
Comments:
- [X] (omid) James Taylor
Comments:
- [ ] (omid) Lars Hofhansl
Comments:
### IPMC/Shepherd notes:
Justin Mclean: This report need more detail and tell us very little
about the podlings progress. Pleas include more detail in you next report.
I there any reason you have not added any committers/PPMC member for a
year?
--------------------
## PonyMail
Pony Mail is a mail-archiving, archive viewing, and interaction service,
that can be integrated with many email platforms.
Pony Mail has been incubating since 2016-05-27.
### Three most important unfinished issues to address before graduating:
1. Growing contributor base
2. Getting release processes nailed to a tee
3. Expanding unit tests
### Are there any issues that the IPMC or ASF Board need to be aware of?
### How has the community developed since the last report?
Not much to report, progress is slow-paced as usual. This isn't to say
that the project is dormant or in danger of retirement, just that the pace
is to be considered more casual. There is oversight, and important issues are
being addressed in a timely manner.
### How has the project developed since the last report?
No noteworthy change, we are operating at a pretty stable level.
### 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-04-20
### When were the last committers or PPMC members elected?
Sebb, 2017-06-01.
Perhaps we should be looking for more candidates :)
### Have your mentors been helpful and responsive?
No answer
### Signed-off-by:
- [ ] (ponymail) John D. Ament
Comments:
- [X] (ponymail) Sharan Foga
Comments: At least one request from a user has not yet been responded to.
Think it would be good to work on more engagement to ensure timely responses
to user queries.
### IPMC/Shepherd notes:
--------------------
## SAMOA
SAMOA provides a collection of distributed streaming algorithms for the most
common data mining and machine learning tasks such as classification,
clustering, and regression, as well as programming abstractions to develop
new algorithms that run on top of distributed stream processing engines
(DSPEs). It features a pluggable architecture that allows it to run on
several DSPEs such as Apache Storm, Apache S4, and Apache Samza.
SAMOA has been incubating since 2014-12-15.
### Three most important unfinished issues to address before graduating:
1. Revitalize the project by resuming development
2. Enlarge the user base and contributing community
### Are there any issues that the IPMC or ASF Board need to be aware of?
None
### How has the community developed since the last report?
* Mailing list activity:
* @dev: 12 messages
### How has the project developed since the last report?
* Retirement has been suggested due to its very low activity
* To restart engagement, Corey Sterling has been elected as commiter in
late August. With his help, we are preparing a new release of Apache
SAMOA in early September. Corey Sterling has experience on open source
software, as an example, he did the last release of MOA, an open source
software non-distributed for data streams very related to SAMOA. He works
at University of Waikato.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [ ] Working towards first release
- [X] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
2016-09-30
### When were the last committers or PPMC members elected?
August 2019
### Have your mentors been helpful and responsive?
Yes, the mentors have been helpful and responsive.
### Signed-off-by:
- [X] (samoa) Alan Gates
Comments: Happy to see a new committer, hopefully this will help
kickstart the project.
- [ ] (samoa) Ashutosh Chauhan
Comments:
### IPMC/Shepherd notes:
Dave Fisher: Let's see if bringing on a new committer revitalizes the
podling.
--------------------
## SDAP
SDAP is an integrated data analytic framework for Big Science problems.
SDAP has been incubating since 2017-10-22.
### Three most important issues to address in the move towards graduation:
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?
We are continuing to attract new committers.
### How has the project developed since the last report?
SDAP is still working towards its first release. Work towards a
repeatable build pipeline has been started.
New functionality has been added to the Distributed Oceanographic Matchup
Service (DOMS) and Extensible Data Gateway Environment (EDGE) components
that allow for filtering in situ measurements by a standardized quality
flag.
### 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. A push
is needed to cross the t's and dot the i's in regards to meeting the
requirements Apache has for releasing software so that we can claim a 1.0
version of SDAP.
Please feel free to add your own commentary.
- [X] Initial setup
- [X] Working towards first release
- [X] Community building
- [ ] Nearing graduation
### 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, mentors have been helpful and responsive.
### Signed-off-by:
- [ ](sdap) Jörn Kottmann
Comments:
- [ ](sdap) Trevor Grant
Comments:
- [ ](sdap) Lewis John McGibbney
Comments:
### IPMC/Shepherd notes:
Justin Mclean: Please use the format provided rather than an old format.
--------------------
## ShardingSphere
Sharding-Sphere is an ecosystem of transparent distributed database
middleware, focusing on data sharding, distributed transaction and database
orchestration.
ShardingSphere has been incubating since 2018-11-10.
### Three most important unfinished issues to address before graduating:
1. Continuing to grow the community
2. Make several candidate releases
3. Make a GA release to make user API stable
### 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?
The community has been growing. We have more contributors during those 3
months.
A UI project has already donate to ShardingSphere. We have finished the
second apache release on 24 August.
The count of GitHub issues are 1800+, the count GitHub pull requests are
1000+.
### How has the project developed since the last report?
We are merging new UI project to dev branch. The new features data mask
and distribute transaction have finished.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [X] Initial setup
- [X] Working towards first release
- [X] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
2019-08-24
### When were the last committers or PPMC members elected?
2019-01-21, but there are some active potential committers may prompt
soon.
### Have your mentors been helpful and responsive?
Mentors are responsive and helpful. Things tend to be on the right way.
### Signed-off-by:
- [x] (shardingsphere) Craig L Russell
Comments: The project is reviewing the "committer bar" which may
be set too high. There is plenty of activity, mainly focused on Github
dialog.
- [ ] (shardingsphere) Benjamin Hindman
Comments:
- [x] (shardingsphere) Willem Ning Jiang
Comments: It's good to see that shardingsphere PPMC put lot efforts on
building community, and making a good release.
- [x] (shardingsphere) Von Gosling
Comments: well in commuity activities, especially in Github Issues and
PRs
### IPMC/Shepherd notes:
Justin Mclean: The stats show don't mean much to people outside your
project, please drop them from future reports and include commentary
on how you project is growing instead.
Given there lots of activity I would expect this report to have a lot more
detail.
A quick look at that stats, without explanation, suggests to me that this
project is in trouble,. You have a large number of contributors, and
outstanding pull request, but are not voting committers in.
Please discuss with your mentors what the committer bar should be and
what it means to be a committer.
--------------------
## SINGA
SINGA is a distributed deep learning platform.
SINGA has been incubating since 2015-03-17.
### Three most important unfinished issues to address before graduating:
1. Fix the code grant issue being discussed in the general@ list.
2. Update the documentation and packages (e.g., docker images and conda
pacakges)
3.
### 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 has been discussing about the graduation
* Currently, we have 45 contributors, 1803 stars and 479 forks on github.
### How has the project developed since the last report?
* Since the last report, we have been focusing on enhancing the ONNX
feature and distributed training. More than 20 ONNX operators are added.
Distributed training using NCCL and MPI has been tested.
* 180 new commits are merged since last report.
* There are 57, 142 and 472 emails on dev@ list for June, July and August
respectively.
### 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-04-20
### When were the last committers or PPMC members elected?
2018-12-21
### Have your mentors been helpful and responsive?
Yes. The mentors raised very important issues like the code grant in the
graduation discussion.
### Signed-off-by:
- [X] (singa) Alan Gates
Comments: This podling is ready to graduate as soon as the IP
clearance is in place. I'm happy to see them ready to take their
place as a TLP.
- [X] (singa) Ted Dunning
Comments:
- [ ] (singa) Thejas Nair
Comments:
### IPMC/Shepherd notes:
Justin Mclean: It might be better to say that the issue is that a SGA was
never submitted.
--------------------
## Spot
Apache Spot is a platform for network telemetry built on an open data model
and Apache Hadoop.
Spot has been incubating since 2016-09-23.
### Three most important unfinished issues to address before graduating:
1. Revive community activity (Discussion in mailing lists, increase
frequency of commits)
2. Create a new roadmap and release plan that will improve adoption.
3. Make it easier to contribute to the project (e.g. documentation,
framework).
### Are there any issues that the IPMC or ASF Board need to be aware of?
No
### How has the community developed since the last report?
Unfortunately there has not been much more community activity. However,
we are need of more committers as there are only a couple of active
committers at this time. This creates a bottleneck which makes it hard
for the community to grow in interest.
### How has the project developed since the last report?
There are a series of PRs that have been evaluated for the SPOT-181 epic,
and Spot website branch (asf-site) that are in the process of being
merged. We have enough votes to merge, and have put out a request to
committers to review so they can be auto-merged if possible, otherwise we
will just manually merge them via cli.
Once those are merged, we will work on the plan to merge SPOT-181 into
master so that the Open Data Model is consolidated into the main branch
of our code.
We're also working on re-focusing the project release roadmap. Our first
step will be to re-engage with the community to better understand
how/where Spot is being used today, what features/enhancements would benefit
the community best, and which committers (existing and potential) are
interested in contributing to the roadmap and releases moving forward.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [x] Initial setup
- [x] Working towards first release
- [x] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
2017-09-08
### When were the last committers or PPMC members elected?
2019-09-05
### Have your mentors been helpful and responsive?
Yes, but we would welcome more mentors and further guidance on
positioning the project for future graduation.
### Signed-off-by:
- [X] (spot) Uma Maheswara Rao G
Comments: Low/no activities on the lists. Raised the same concern on spot dev lists. PPMC is planning to address this concern.
### IPMC/Shepherd notes:
Justin Mclean: Please ask on the incubator general@ list for more mentors.
--------------------
## Superset
Superset is an enterprise-ready web application for data exploration, data
visualization and dashboarding.
Superset has been incubating since 2017-05-21.
### Three most important issues to address in the move towards graduation:
* Build up towards a steady stream of Apache releases
* Address remaining project operations issues. See below.
### Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
For project operations, we have made the following progress and need the
following support:
N/A
### How has the community developed since the last report?
* Organic growth of our Github contributors (343->403), forks (4300->5076),
watchers (1170->)1212 and stars (23,326->26,021)
### How has the project developed since the last report?
* First official Apache release is out!!! “0.34.0”
* Started an effort around a community design-focussed interest group with
a set of community contributors from different organizations
* New committer Kim Truong, Erik Ritter
New features
* Dashboard interactive filters improvements
* See commit log / release notes
Bug fixes, code quality and housekeeping
* See the commit log, 169 PRs merged since July 1st
### 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-08-27
### When were the last committers or PPMC members elected?
* Kim Truong (2019-07-30)
* Erik Ritter (2019-08-29)
Signed-off-by:
- [ ](superset) Ashutosh Chauhan
Comments:
- [ ](superset) Luke Han
Comments:
- [X](superset) Alan Gates
Comments: Congratulations on the first release!
### IPMC/Shepherd notes:
--------------------
## Taverna
Taverna is a domain-independent suite of tools used to design and execute
data-driven workflows.
Taverna has been incubating since 2014-10-20.
### Three most important unfinished issues to address before graduating:
1. Re-engage PPMC members
2. Release IP-fixed repositories
3. Graduate!
### Are there any issues that the IPMC or ASF Board need to be aware of?
Considering retiring.
### How has the community developed since the last report?
Very quiet through the summer. Podling considering retirement from
incubator.
### How has the project developed since the last report?
No development since last report.
Release Candidates planned during June has not progressed further to a
vote.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [ ] Working towards first release
- [x] Community building
- [x] Nearing graduation
- [ ] Other:
### Date of last release:
2018-01-18
### When were the last committers or PPMC members elected?
2018-02-26 (PPMC)
### Have your mentors been helpful and responsive?
No answer
### Signed-off-by:
- [x] (taverna) Stian Soiland-Reyes
Comments: While the project has previously been active, done several
releases, and recruited PPMC and committers, it is now very
quiet.
For graduation it only needs a couple of maintenance releases
of the remaining code-bases (or not include those in
graduation).
I suggest the project use the next reporting period to
discuss retiring vs. graduation.
### IPMC/Shepherd notes:
Justin Mclean: I'm a little confused if you want to graduate or retire.
--------------------
## 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. Active community
2. Increase 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?
Toree will have a talk at ApacheCon Las Vegas where we will
talk about its overall status and current functionality as
well as try to attract more users and in particular contributors.
After the release of Toree 0.3.0 the community slowed down,
mostly due to Toree being somewhat stable and running on top
of Spark, where the public APIs in use are also stable.
The community needs to work on a release that supports Apache
Spark 2.4.x and Scala 2.12.
Toree might be one of those low activity projects which have enough
active PPMCs (see last ppmc voting thread), and we might
start graduation talks based on these facts.
### How has the project developed since the last report?
Very little activity on the last few months after the
Toree 0.3.0 release, mostly around some compatibility
issues with Spark 2.4.x and Scala 2.12.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [ ] Working towards first release
- [X] Community building
- [X] Nearing graduation
- [ ] Other:
### Date of last release:
2018-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?
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:
### IPMC/Shepherd notes:
Justin Mclean: Please use the format provided rather than an old format.
--------------------
## Warble
a distributed endpoint monitoring solution where the agent is hosted on your
own hardware.
Warble has been incubating since 2018-06-11.
### Three most important unfinished issues to address before graduating:
1. Develop documentation
2. Develop community
3. Develop community
### Are there any issues that the IPMC or ASF Board need to be aware of?
### How has the community developed since the last report?
### How has the project developed since the last report?
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [ ] Working towards first release
- [X] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
None.
### When were the last committers or PPMC members elected?
### Have your mentors been helpful and responsive?
No answer.
### Signed-off-by:
- [ ] (warble) Daniel Takamori
Comments:
- [X] (warble) Chris Lambertus
Comments: Warble continues to be stagnant. If no progress is made at
ACNA we will likely shutter the effort.
### IPMC/Shepherd notes:
Dave Fisher: A similar note was made last year. No trouble if this
retires and then returns as an Infra tool.
-----------------------------------------
Attachment AG: Report from the Apache Jackrabbit Project [Marcel Reutegger]
Apache Jackrabbit: Board Report September 2019
==============================================
## Description:
The Apache Jackrabbit™ content repository is a fully conforming implementation
of the Content Repository for Java™ Technology API
(JCR, specified in JSR 170 and 283). The Jackrabbit content repository is
stable, largely feature complete and actively being maintained. Jackrabbit
Oak is an effort to implement a scalable and performant hierarchical content
repository as a modern successor to the Apache Jackrabbit content repository.
It is targeted for use as the foundation of modern world-class web sites and
other demanding content applications. In contrast to its predecessor, Oak
does not implement all optional features from the JSR specifications and it
is not a reference implementation.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
Apache Jackrabbit Oak receives most attention nowadays. All maintenance
branches and the main development branch are continuously seeing moderate to
high activity.
We made our 8th feature release of Jackrabbit Oak (1.16) end of July.
Apache Jackrabbit itself is mostly in maintenance mode with most of the work
going into bug fixing and tooling. New features are mainly driven by
dependencies from Jackrabbit Oak.
The project stopped supporting Jackrabbit releases from the old
2.10 branch and encouraged users to upgrade to more recent stable versions
(https://s.apache.org/c2a1d).
Four new committers were added to the project and added to the PMC in the last
3 months. There is an increased interest in the filevault components, visible
in higher JIRA activity and mailing list discussions on that topic.
A hackathon planned for August was canceled because very few participants
registered and no proposals were submitted for the hackathon
(https://s.apache.org/i8be9).
## Health report:
The project is healthy with a continuous stream of traffic on all mailing
lists reflecting the activity of the respective component.
There is a wide range of topics being discussed on the dev and user lists as
well as on the various JIRA issues.
Commit activity is moderate to high mirroring the activity on the JIRA issues
and the desire of the individual contributors to bring features and
improvements in for the next Jackrabbit Oak release.
## PMC changes:
- Currently 56 PMC members.
- 4 new PMC members added in the last 3 months
- Dominik Süß was added to the PMC on 2019-07-25
- Konrad Windszus was added to the PMC on 2019-07-22
- Mohit Kataria was added to the PMC on 2019-08-08
- Nitin Gupta was added to the PMC on 2019-08-08
## Committer base changes:
- Currently 56 committers.
- 4 new committers added in the last 3 months
- Dominik Süß was added as committer on 2019-07-25
- Konrad Windszus was added as committer on 2019-07-22
- Mohit Kataria was added as committer on 2019-08-08
- Nitin Gupta was added as committer on 2019-08-08
## Releases:
- jackrabbit-oak-1.8.14 was released on 2019-07-04
- jackrabbit-oak-1.10.3 was released on 2019-07-15
- jackrabbit-oak-1.8.15 was released on 2019-07-16
- filevault-package-maven-plugin-1.0.4 was released 2019-07-18
- jackrabbit-oak-1.16.0 was released on 2019-07-29
- jackrabbit-oak-1.10.4 was released on 2019-08-16
- jackrabbit-2.19.4 was released on 2019-08-26
- jackrabbit-oak-1.8.16 was released on 2019-08-29
- jackrabbit-2.18.3 was released on 2019-08-30
- jackrabbit-2.16.5 was released on 2019-09-05
## JIRA activity:
- 250 JIRA tickets created in the last 3 months
- 234 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AH: Report from the Apache Karaf Project [Jean-Baptiste Onofré]
## Description:
Apache Karaf provides a modern and polymorphic applications runtime,
multi-purpose (microservices, cloud, IoT, OSGi, etc).
## Issues:
There are no issues requiring board attention at this time
## Membership Data:
Apache Karaf was founded 2010-06-16 (9 years ago)
There are currently 31 committers and 17 PMC members in this project.
The Committer-to-PMC ratio is roughly 8:5.
Community changes, past quarter:
- No new PMC members. Last addition was Francois Papon on 2018-11-29.
- No new committers. Last addition was Francois Papon on 2018-05-19.
## Project Activity:
We released Apache Karaf 4.2.6 with several fixes. Master update started to
fully support OSGi R7 and other update. The kloud initiative keeps on running
with new blog posts, and preparation on code base. The Karaf tooling (aka
Karaf Boot) is in our roadmap. The Karaf Vineyard donation should happen soon
as now the code base is done. We are preparing new releases on our
subprojects, especially Decanter and Cave. We are very happy to have a full
Apache Karaf track at ApacheCon NA with 3 talks about Apache Karaf (all on
Thursday, September, 12). Recent releases:
4.2.6 was released on 2019-06-09.
4.2.5 was released on 2019-04-20. Decanter 2.2.0 was released on 2019-03-21.
## Community Health:
Even if the activity is lower during summer, but we have a sustained activity
on the mailing list and interaction:
- dev@karaf.apache.org had a 53% decrease in traffic in the past quarter (125
emails compared to 262)
- issues@karaf.apache.org had a 46% decrease in traffic in the past quarter
(692 emails compared to 1261)
- user@karaf.apache.org had a 32% decrease in traffic in the past quarter (343
emails compared to 499)
- 77 issues opened in JIRA, past quarter (-44% decrease)
- 37 issues closed in JIRA, past quarter (-71% decrease)
- 95 commits in the past quarter (-67% decrease)
- 11 code contributors in the past quarter (-38% decrease)
- 53 PRs opened on GitHub, past quarter (-59% decrease)
- 45 PRs closed on GitHub, past quarter (-62% decrease)
-----------------------------------------
Attachment AI: Report from the Apache Labs Project [Danny Angus]
## Description:
Apache Labs is a place for innovation where committers of the foundation can
experiment with new ideas
## Issues:
There are no issues requiring board attention at this time.
## Membership Data:
Apache Labs was founded 2006-11-15 (13 years ago)
There are currently 31 committers and 10 PMC members in this project.
The Committer-to-PMC ratio is roughly 8:3.
Community changes, past quarter:
- No new PMC members. Last addition was Simone Tripodi on 2011-06-14.
- No new committers. Last addition was Juan P. Gilaberte on 2018-05-30.
## Project Activity:
There is one active Lab. Turbulence -
http://svn.apache.org/repos/asf/labs/turbulence/
Activity has been minimal, but Juan remains committed to his project.
## Community Health:
Labs is quiet, again, but not neglected and the nature of the project means
that we can always muster a roll-call.
-----------------------------------------
Attachment AJ: Report from the Apache Lucene Project [Cassandra Targett]
## Description:
- Lucene Core is a search-engine toolkit
- Solr is a search server built on top of Lucene Core
- PyLucene is a Python extension for accessing Lucene
## Issues:
There are no issues requiring board attention at this time.
## Membership Data:
Apache Lucene was founded 2005-01-18 (15 years ago)
There are currently 79 committers and 53 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:4.
Community changes, past quarter:
- Kevin Risden was added to the PMC on 2019-06-25
- Munendra S N was added as committer on 2019-06-19
- One committer nomination vote is in progress.
## Project Activity:
We have released Lucene and Solr 8.2 since the last report.
PyLucene 8.1.1 was released on September 11th, 2019.
With 8.2, we added Estonian language support in Lucene and Solr. Lucene added
a monitor subproject (formerly known as Luwak, donated to the project) which
allows monitoring an input stream of documents for matches to a stored query.
Solr also added OpenTracing support for distributed trace performance
monitoring.
On the project maintenance front, we have several changes. First, we migrated
two MoinMoin wikis to Confluence, and are discussing what to do with the old
content (which may be outdated) in the new environment. We also introduced two
new mailing lists to take some traffic from our main development list,
discussed in more detail below.
We are working to change our entire build system, currently based on Ant, to
use Gradle, which we hope to complete soon. This is a herculean effort, but is
making progress.
Two CVEs were announced last period and the project is actively responding to
incoming vulnerability reports.
## Community Health:
Community health is very strong. Our two main user lists, java-user and
solr-user, continue to be widely used.
Due to the very high volume in our main developer-focused list (8920 mails
last quarter), we have instituted two new lists: issues@lucene.a.o for Jira,
Github, and Gitbox notifications and builds@lucene.a.o for Jenkins build
notifications. We hope this will allow developer conversations to not get lost
in the flood of automated notifications.
Our Jira issue activity and code contributions are also very strong. 305
issues were created and 224 were closed, decreases of 14% and 21%
respectively. The project had 1646 commits (+5%) from 76 contributors (+20%)
in the last quarter.
-----------------------------------------
Attachment AK: Report from the Apache Lucene.Net Project [Shad Storhaug]
-----------------------------------------
Attachment AL: Report from the Apache Mesos Project [Benjamin Hindman]
## Description:
The mission of Mesos is the creation and maintenance of software related to a
cluster manager that provides efficient resource isolation and sharing across
distributed applications
## Issues:
The current PMC chair (Benjamin Hindman) has stepped down. Vinod Kone
(vinodkone@apache.org) has been nominated as the new PMC chair and received 14
+1 votes (and no -1 or 0 votes) on the private@mesos.apache.org email thread
https://lists.apache.org/thread.html/45071dfda2308f916bb15d7f7376e9b88786af16ae56cf400ed8fa36@%3Cprivate.mesos.apache.org%3E
We would request the board to approve the appointment of the new chair.
A PMC roll call was also conducted, per the board feedback, and it garnered
positive response (17 +1 votes) from the PMC.
https://lists.apache.org/thread.html/80ecc1c2b72dd17b9c4d9e80f4889f11ec7d08793f6f0501ec843783@%3Cprivate.mesos.apache.org%3E
## Membership Data:
Apache Mesos was founded 2013-06-18 (6 years ago) There are currently 48
committers and 48 PMC members in this project. The Committer-to-PMC ratio is
1:1.
Community changes, past quarter:
- No new PMC members. Last addition was Andrei Budnik on 2019-03-11.
- No new committers. Last addition was Andrei Budnik on 2019-03-06.
We have a new potential committer in the pipeline (Andrei Sekretenko) who will
likely be nominated in the next few months.
## Project Activity:
1.9.0 was released on 2019-09-05.
1.10 release is under active development.
## Community Health:
Rephrasing the response from the private email thread for posterity.
Mesosphere which employs significant number of Mesos committers have recently
rebranded itself to D2iQ, but there should be no cause to worry. The company
is still very much invested in the Mesos project as its DCOS platform (based
on Mesos) is still one of its major product lines.
There has been a significant downtick in JIRA and commit activity, but the
majority of it can be likely attributed to summer months and vacation. We
don't foresee such precipitous downtrend in commit activity to continue in the
next few quarters. That said, it is to be noted that with the rise of
kubernetes quite a bit of the developer/user interest has shifted from mesos
to kubernetes which contributes to the downtick.
All that said, there is still healthy development and user activity in the
project and the core committers are still very much active.
-----------------------------------------
Attachment AM: Report from the Apache Mnemonic Project [Gang Wang]
Description:
Apache Mnemonic is an open-source Java library for durable object-oriented
programming on hybrid storage-class memory(e.g. NVM) space. it comes up
with durable object model (DOM) and durable computing model(DCM) and
takes full advantages of storage-class memory to simplify the code
complexity, avoid SerDe/(Un)Marshal, mitigate caching for constructing
next generation computing platform. Mnemonic makes the storing and
transmitting of massive linked objects graphs simpler and more efficient.
The performance tuning could also be mostly converged to a single point
of tuning place if based on Mnemonic to process and analyze
linked objects. The programmer is able to focus on the durable object
oriented business logic instead of worrying about how to normalize/join,
serDe(un)marshal, cache and storing their linked business objects
with arbitrary complexity.
Issues:
There are no board-level issues at the moment.
Activity:
In this period of reporting, 4 of tickets has been created and
3 resolved, basically, we have corrected an issue of Ubuntu Dockerfile,
and upgraded PMDK to stable version 1.6 in both Dockerfiles of Ubuntu
and CentOs, that upgrades introduced non-trivial changes on both Linux
distributions. but it has not been verified on MacOS.
Regarding the GSoC, GSoC student has finially submitted the code
implementation as PR #118 to our mirrored Mnemonic Github repos.
We have reviewed the code and provided the feedbacks and suggestion.
Overall, the GSoC student has successfully delivered the result to our
community. I also have filled the final report according to student's
progress and results
Health Report:
Basically unchanged since the last report. Users are generally quiet
in public but development continues.
PMC Changes:
- Currently 12 PMC members.
- no new PMC member added since Jun. 2018.
Committer Base Changes:
- Currently 13 committers.
- No new committer added since Jun. 2018.
Releases:
- Last release was v0.12.0 on Sep. 04 2018
- Still active development on next major version (0.13)
-----------------------------------------
Attachment AN: Report from the Apache Mynewt Project [Justin Mclean]
-----------------------------------------
Attachment AO: Report from the Apache NetBeans Project [Geertjan Wielenga]
## Description:
The mission of Apache NetBeans is the creation and maintenance of software
related to development environment, tooling platform, and application framework
## Issues:
There are no issues, everything going well.
## Membership Data:
Apache NetBeans was founded 2019-04-17 (5 months ago)
There are currently 68 committers and 64 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 Sarvesh Kesharwani on 2019-06-06.
- No new committers. Last addition was Vikas Prabhakar on 2019-06-03.
## Project Activity:
Woeking towards the release of Apache NetBeans 11.2, the 2nd release of
the new quarterly release cycle, everything going to plan, with a range
of new features and fixes, including support for new JDK 13 language features.
## Community Health:
Community stable and working well together, the new quarterly release
cycle has brought stability and predictability, with many thanks to
Neil for suggesting it and leading the process towards adopting it.
-----------------------------------------
Attachment AP: Report from the Apache OFBiz Project [Jacopo Cappellato]
## Description:
Apache OFBiz is an open source product for the automation of enterprise
processes that includes framework components and business applications for ERP
(Enterprise Resource Planning), CRM (Customer Relationship Management),
E-Business / E-Commerce, SCM (Supply Chain Management), MRP (Manufacturing
Resource Planning), MMS/EAM (Maintenance Management System/Enterprise Asset
Management). Apache OFBiz provides a foundation and starting point for
reliable, secure and scalable enterprise solutions.
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache OFBiz was founded 2006-12-19 (13 years ago) There are currently 49
committers and 20 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 Paul Foxworthy on 2018-03-18.
- Deepak Nigam was added as committer on 2019-06-12
- Pawan Verma was added as committer on 2019-06-12
Please notice that the addition of the two new committers has been
included also in our previous report.
## Project Activity:
- Various bug fixes and enhancements have been contributed and committed to
the trunk and backported to the various release branches
- Trademarks: we do not have trademark related concerns at the moment and our
backlog of non-compliant parties is mostly empty [1]
- 16.11.06 was released on 2019-09-08; this is the 6th bug-fix release of the
16.11 series and fixes a series of bugs, including some vulnerability fixes
- More details about the community activities are published in the official
blog [2], on Twitter [3] and other social media [4]
[1] https://svn.apache.org/repos/private/pmc/ofbiz/trademarks/trademarks.txt
[2] https://blogs.apache.org/ofbiz/
[3] https://twitter.com/ApacheOfbiz
[4] https://www.facebook.com/Apache-OFBiz-1478219232210477/
## Community Health:
we have a few candidates in our watchlist for the committers and PMC groups
and we have started a vote to invite a new PMC member; as usual the
community is actively involved in improving the trunk, fixing vulnerabilities,
stabilizing the release branches and in various discussions and support
requests posted mostly in the mailing list and in our issue tracker.
-----------------------------------------
Attachment AQ: Report from the Apache Olingo Project [Michael Bolz]
## Description:
The Apache Olingo Project be and hereby is responsible for the creation and
maintenance of software related to providing an implementation of the OASIS
OData (Open Data Protocol) specifications, in server and client form;
## Issues:
There are no issues requiring board attention at this time
## Membership Data:
Apache Olingo was founded 2014-03-19 (5 years ago)
There are currently 25 committers and 15 PMC members in this project.
The Committer-to-PMC ratio is 5:3.
Community changes, past quarter:
- No new PMC members. Last addition was Ramya Vasanth on 2019-04-15.
- No new committers. Last addition was Archana Rai on 2017-05-26.
## Project Activity:
Recent releases:
- 4.6.0 was released on 2019-05-05.
- V2 2.0.11 was released on 2019-02-16.
- 4.5.0 was released on 2018-08-13.
We were informed that people from the community plan to do security
contributions in the form of a code review.
In addition they will create related JIRA issues in case of any findings.
## Community Health:
Overall community health is good.
The V4 code line is on steady development also reflected in
related discussions on mailing list and new created JIRA items.
We plan to release the next V4 version (4.7.0) this year.
The V2 code line had minor bugfix contributions as well as
open and new created JIRA items.
Over the last months there were more new JIRA issues created
then in the last quarter (+50% created).
We neither could keep up with this nor reach the performance
of last quarter (-30% closed).
Hence we closed less JIRA issues but we now know that we have
enough in our pipeline for at least the next half year.
-----------------------------------------
Attachment AR: Report from the Apache OODT Project [Imesha Sudasingha]
## Description:
Apache OODT is a software framework as well as an architectural style for the
rapid construction of scientific data systems. It provides components for
data capture, curation, metadata extraction, workflow management, resource
management, and data processing.
## Issues:
There are no issues requiring board attention
## Membership Data:
Apache OODT was founded 2010-11-17 (9 years ago) There are currently 46
committers and 45 PMC members in this project. The Committer-to-PMC ratio is
roughly 1:1.
Community changes, past quarter:
- No new PMC members. Last addition was Imesha Sudasingha on 2017-08-28.
- No new committers. Last addition was Imesha Sudasingha on 2017-08-29.
## Project Activity:
We have just completed 2 GSoC projects. One to improve OODT deployment with
docker and the other one was to implement a new UI for OODT OPSUI. Both were
completed successfully. However, there are few PRs still required to be merged
and some minor improvements requires to be made on top of GSoC contributions
for the new features to be usable. Those students will help us get through
this.
With those additions we are planning to release OODT 2.0. We have 1.9 release
on the backlog which is dev completed, but not yet properly tested. We intend
to finalize that as well.
- Last release was 1.2.5 on 2018-09-13.
## Community Health:
- 16 issues opened in JIRA, past quarter (300% increase)
- 9 issues closed in JIRA, past quarter (800% increase)
- 19 commits in the past quarter (216% increase)
- 7 code contributors in the past quarter (250% increase)
- 19 PRs opened on GitHub, past quarter (375% increase)
Overall development activity was very high compared to past quarters due to
the GSoC projects. We hope that we will be able to keep this momentum.
-----------------------------------------
Attachment AS: Report from the Apache OpenNLP Project [Jörn Kottmann]
-----------------------------------------
Attachment AT: Report from the Apache OpenWebBeans Project [Mark Struberg]
## Description:
Apache OpenWebBeans is an ALv2-licensed implementations of the
"Contexts and Dependency Injection for the Java EE platform"
specifications which are defined as JSR-299 (CDI-1.0), JSR-346
(CDI-1.1 and CDI-1.2 MR) and JSR-365 (CDI-2.0).
The OWB community also maintains a small server as
Apache Meecrowave subproject. Meecrowave bundles latest releases of
the ASF projects Tocmat9 + OpenWebBeans + CXF + Johnzon + log4j2.
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache OpenWebBeans was founded 2009-12-16 (10 years ago)
There are currently 20 committers and 13 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:4.
Community changes, past quarter:
- No new PMC members. Last addition was Reinhard Sandtner on 2017-10-09.
- No new committers. Last addition was John D. Ament on 2017-10-09.
## Project Activity:
We regularly get contributions from rather unexpected places.
Like the Jetty and Tomcat teams provided great feedback for
integrating OWB into their servlet engines.
We are right now preparing for a 2.0.12 release with bugfixes.
## Community Health:
Contributions are alright. Very ok-ish for such a mature project.
Otoh it's hard to attract new committers because of the complexity
of the topic.
-----------------------------------------
Attachment AU: 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
## Membership Data:
Apache OpenWhisk was founded 2019-07-16 (2 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 (project graduated recently).
- Justin Halsall was added as committer on 2019-08-22
## Project Activity:
- The project has completed updating its website, development tooling, and its
52 github repos and associated CI/CD jobs to reflect its graduation to a
top-level project. In the process, 17 github repos were identified as being
inactive and were archived (made read-only).
- We made our first two non-incubating releases of OpenWhisk sub-components:
- openwhisk-apigateway-0.11.0 was released on 2019-08-30.
- openwhisk-client-js-3.20.0 was released on 2019-08-28.
- Development work was completed on a new "standalone" configuration of
OpenWhisk that will enable significantly easier installation and
experimentation with the OpenWhisk programming model by end users. A major
focus for the next month will be to make a new release of the core system
component so we can then make the standalone OpenWhisk jar easily available
to end users via Maven.
## Community Health:
Overall community health is good.
There are active technical discussions on the dev list around several new
features that are being designed.
Overall, significant code contributions are holding steady. Statistically,
there was a large spike in GitHub PR activity (64% increase in opened PRs, 99%
increase in closed PRs) in this period, but at least half of the spike can be
attributed to fairly mechanical changes to "de-incubate" the repos, website,
and release tooling.
-----------------------------------------
Attachment AV: Report from the Apache Pig Project [Koji Noguchi]
## Description:
* Apache Pig is a platform for analyzing large data sets on Hadoop. It provides
a high-level language for expressing data analysis programs, coupled with
infrastructure for evaluating these programs.
## Issues:
* I was hoping we would have a Pig 0.18 release by now with hadoop 3 support
but couldn't.
> druggeri: RE: "However, we do need a release soon." Is there
> anything preventing a release?
>
Just some time from a couple of committers/PMC including myself to fix/review
blocking jiras. Please give us one more quarter.
## Membership Data:
Apache Pig was founded 2010-09-21 (9 years ago)
There are currently 31 committers and 17 PMC members in this project.
The Committer-to-PMC ratio is roughly 8:5.
Community changes, past quarter:
- No new PMC members. Last addition was Koji Noguchi on 2016-08-04.
- No new committers. Last addition was Nándor Kollár on 2018-09-06.
## Project Activity:
- Not much activity but we are looking into having a release to support Hadoop
3.
## Community Health:
- Overall activity is low as project is mostly stable and contributions are
mainly bug fixes.
-----------------------------------------
Attachment AW: Report from the Apache Pivot Project [Roger Lee Whitcomb]
Description:
Apache Pivot is an open-source platform for building installable Internet
applications (IIAs). It combines the enhanced productivity and usability
features of a modern user interface toolkit with the robustness of the
Java platform.
Issues:
No board-level issues at this time.
Activity:
A little bit of development work continued toward the 2.1.0 release. But
essentially no other traffic on either dev or user mailing lists.
Essentially the same theme as the last report (July 2019) in that after
this release some serious decisions need to be made about the future of
the project. I have some hope that we might pick up some interest from
the mobile (Android) community, and/or something, but this seems unlikely
given the current climate.
Health Report:
Basically unchanged again this quarter, although there was some small amount
of development activity. Users remain quiet.
PMC changes:
- Currently 7 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Niclas Hedhman on Wed Jan 13 2016
Committer base changes:
- Currently 9 committers.
- No new changes to the committer base since last report.
- No new committers added in the last 3 months
- Last committer addition was more than 2 years ago
Releases:
- Last release was 2.0.5 on Mon Jul 03 2017
- Still some development on next major version (2.1.0).
Mailing list activity:
- dev@pivot.apache.org:
- 13 emails sent to list (6 in previous quarter)
- user@pivot.apache.org:
- No emails sent to list (1 in previous quarter)
JIRA activity:
- Two (2) JIRA tickets opened in the last quarter.
- One (1) JIRA ticket closed/resolved in the last quarter.
-----------------------------------------
Attachment AX: Report from the Apache PLC4X Project [Christofer Dutz]
## Description:
The mission of the Apache PLC4X project is creating a set of libraries for
communicating with industrial programmable logic controllers (PLCs) using a
variety of protocols but with a shared API.
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache PLC4X was founded 2019-04-17 (5 months ago)
There are currently 9 committers and 9 PMC members in this project.
The Committer-to-PMC ratio is 1:1.
Community changes, past quarter:
- Łukasz Dywicki was added to the PMC on 2019-07-28
- Matthias Milan Strljic was added to the PMC on 2019-06-03
- Łukasz Dywicki was added as committer on 2019-07-28
- Matthias Milan Strljic was added as committer on 2019-06-03
## Project Activity:
Releases:
- 0.4.0 was released on 2019-05-26.
Community Events:
- 24.05.2019, Frankfurt (GER), Meetup: Industrial IoT goes Open Source: Apache
PLC4X Talks & Party
- 18.06.2019, Erfurt (GER), Meetup: Industrie & IoT: Die perfekte Verbindung
mit Flexibus & Apache PLC4X
- 29.08.2019, Frankfurt (GER), Meetup: Apache PLC4X Community Meetup
We have been working hard on the generated drivers side and are currently
approaching the finishing line on this feature. In parallel we had some major
refactoring of internal components such as the Scraper. A lot of work has
also been put into adding new integration modules (Logstash) as well as
improving existing ones (Apache Kafka Connect)
Also did we have some major improvements and bugfixes resulting from feedback
from enterprise usage.
Also the project is currently discussing the introduction of a computational
layer (most probably in a sub-project) mainly based on a proposed
code-donation.
## Community Health:
Slack has been more adopted for initial discussions and gossip, therefore
discussions on the mailing list have concentrated on technical discussions.
Also two of the main contributors have lately been very consumed with
outer-project activities.
- dev@plc4x.apache.org currently has 63 subscriptions (increase of 10 since
last report)
- dev@plc4x.apache.org had a 50% decrease in traffic in the past quarter (373
emails compared to 732)
- issues@plc4x.apache.org had a 48% decrease in traffic in the past quarter
(75 emails compared to 143)
- 11 issues opened in JIRA, past quarter (-73% decrease)
- 7 issues closed in JIRA, past quarter (-63% decrease)
- 380 commits in the past quarter (7% increase)
- 12 code contributors in the past quarter (-25% decrease)
- 9 PRs opened on GitHub, past quarter (-65% decrease)
- 9 PRs closed on GitHub, past quarter (-65% decrease)
- 26 contributors which have contributed code to the git repo
- 99 Github Stars (up by 18 since last report)
- 187 @ApachePLC4X Twitter account followers (up by 12 since last report)
Even if the mailing list numbers could give reason to feel otherwise, we think
our community is very healthy and growing at an increasing rate. More and
more potential committers are starting to work on different topics.
-----------------------------------------
Attachment AY: Report from the Apache Portable Runtime (APR) Project [Nick Kew]
## Description:
The mission of the Apache Portable Runtime (APR) project is to create and
maintain software libraries that provide a predictable and consistent interface
to underlying platform-specific implementations. The primary goal is to provide
an API to which software developers may code and be assured of predictable if
not identical behaviour regardless of the platform on which their software is
built, relieving them of the need to code special-case conditions to work
around or take advantage of platform-specific deficiencies or features.
## Issues:
No issues requiring board attention at this time.
On a personal note, this reporter has just moved house and currently
has no internet connection except a mobile one for the macbook,
which is not normally used for development or ASF work.
## Membership Data:
Apache Portable Runtime (APR) was founded 2000-12-01 (19 years ago)
There are currently 67 committers and 41 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 Evgeny Kotkov on 2017-09-12.
- No new committers. Last addition was Evgeny Kotkov on 2017-09-13.
## Project Activity:
Since the release of APR 1.7.0 in April, activity has been modest,
and focussed on bug fixing. One new suggestion has been raised:
a prospective apr-tools subproject providing commandline tools based
on the library. The suggestion met with mixed reaction.
## Community Health:
The community remains long-term stable. We maintain the steady hand
of a mature community more than the vigour of a youthful one.
-----------------------------------------
Attachment AZ: Report from the Apache Portals Project [David Sean Taylor]
## Description:
Apache Portals exists to promote the use of open source portal technology. We
intend to build freely available and interoperable portal software in order to
promote the use of this technology. With the Pluto project, we provide a
reference implementation for the Java portlet standard. The Jetspeed project
is a full feature enterprise open source portal. The Portals Applications
project is dedicated to providing robust, full-featured, commercial-quality,
and freely available portlet applications.
## Activity:
No new releases since April 25 (Pluto 3.1.0)
No additional members since last report
12 Feb 2017 - Two new PMC members added
27 April 2017 - Apache Portals Pluto
team released Pluto Maven Archetypes 3.0 to support to developing new portlets
to the new 3.0 spec
## Mailing list activity:
Low to medium activity. Primary activity on Pluto dev list, discussions around
the the Pluto releases and CVEs.
## Issues:
We have no board-level issues at this time.
## PMC/Committership changes:
Last Added PMC Members:
12 Feb 2017 - Scott Martin Nicklaus 12 Feb 2017 - Neil Griffin
Last Added Committers:
05 August 2016 Mohd Ahmed Kahn 11 Dec 2014 Martin Scott Nicklous 11 Dec 2014
Neil Griffin
## Releases:
Pluto 3.1.0 - 25 April 2019 Pluto 3.0.1 - 21 June 2018 Pluto Maven Portlet
Archetype 3.0.1 - 21 June 2018 Pluto Maven Generic Archetype 3.0.1 - 21 June
2018 Pluto Maven Archetype 3.0.0 - 27 April 2017 Pluto 3.0.0 - 18 January 2017
Jetspeed 2.3.1- 09 May 2016
-----------------------------------------
Attachment BA: Report from the Apache PredictionIO Project [Donald Szeto]
## Description
- PredictionIO is an open source Machine Learning Server built on top of
state-of-the-art open source stack, that enables developers to manage and
deploy production-ready predictive services for various kinds of machine
learning tasks.
## Issues
- There are no issues requiring board attention at this time.
## Project Activity
- Major dependencies upgrade work-in-progress
- Version 1.0 design pending review
- Bug fixes
## Membership Data
- Currently 28 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Mars Hall on Fri Jul 28 2017
- Currently 29 committers.
- No new changes to the committer base since last report.
## Releases
- 0.14.0 was released on Sun Mar 10 2019
## Community Health
- 2 JIRA tickets created in the last 3 months
- 1 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment BB: Report from the Apache Pulsar Project [Matteo Merli]
## Description:
Pulsar is a highly scalable, low latency messaging platform running on
commodity hardware. It provides simple pub-sub semantics over topics,
guaranteed at-least-once delivery of messages, automatic cursor management for
subscribers, and cross-datacenter replication.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- The project has released 2.4.0 in June and a subsequent patch release
2.4.1 in August. This was a very big release that included many new
features and improvements. Highlights include:
* Key-Shared Subscription type
* Delayed message delivery
* Negative acknowledgments
* Replicated subscriptions
* Kerberos authentication
* Go functions
* Schema versioning
- Conferences talk on Pulsar
* 5 Pulsar talks were presented at Apache Con NA 2019
- Using Apache Pulsar to Provide Real-Time IoT Analytics on the Edge by
David Kjerrumgaard
- Life beyond Kafka with Apache Pulsar - Alvaro Santos Andrés
- Building Zhaopin's enterprise event bus based on Apache Pulsar by Jia
Zhai and Penghui Li
- Interactive querying of streams using Apache Pulsar - Boyang Jerry
Peng
- Serverless Event Streaming with Pulsar Function: Use Cases and Best
Practices by Xiaolong Ran
* Two talks are scheduled for Strata NY in September:
- Posttransaction processing using Apache Pulsar at Narvar, by Karthik
Ramasamy
- How Orange Financial combats financial fraud over 50M transactions a
day using Apache Pulsar, by Sijie Guo
* One talk is scheduled for Flink Forward Berlin in October:
- Query Pulsar Streams using Apache Flink by Sijie
* One keynote on Pulsar at the "Workshop on Real-time & Stream Analytics"
at IEEE Big Data conference in Dec will be presented by Matteo Merli
* Several Pulsar specific meetups were held in China, Japan and US. Other
talks on Pulsar were also hosted in other meetups.
- Work is ongoing for next release (2.5.0) for which we plan to include:
* Transactional API
* Ruby Client
* Pulsar manager UI
* Kafka protocol handler
- Since last report sever PIPs (Pulsar improvement proposals) were
submitted:
* PIP 38: Batch Receiving Messages
* PIP 39: Namespace Change Events
* PIP 40: Pulsar Manager
* PIP 41: Pluggable Protocol Handler
* PIP 42: KoP - Kafka on Pulsar
* PIP 43: producer send message with different schema
* PIP 44: Separate schema compatibility checker for producer and consumer
- New client libraries have seen signifant work:
* NodeJS client: https://github.com/apache/pulsar-client-node
* Native Go client: https://github.com/apache/pulsar-client-go
* Ruby
* C# https://github.com/danske-commodities/dotpulsar
* F# https://github.com/fsharplang-ru/pulsar-client-dotnet
## Health report:
- There is healthy grow in the community, several users are starting to
become contributors to the project and engaging more and more with the
community.
- Activity on the Slack channel is still high, many first time users come to
ask questions while getting started. There are 148 weekly active users on
the channel, up from 103 in June.
## PMC changes:
- Currently 24 PMC members
- 1 new PMC member added since last report:
- Penghui Li - Sep 10th
## Committer base changes:
- Currently 28 committers
- 4 committers were added since last report
- Jennifer Huang - Jun 24th
- Ali Ahmed - Jul 25th
- Fangbin Sun - Jul 25th
- Xiaolong Ran - Jul 25th
## Releases:
- 2.4.0 was released on Jun. 30th 2019
- 2.4.1 was released on Aug. 30th 2019
## Mailing list activity:
- Activity on the mailing lists remains high with a mixture of new users,
contributors, and deeper more experienced users and contributors sparking
discussion and questions and filing bugs or new features.
- users@pulsar.apache.org:
- 121 subscribers (+18 from Jun 2019) - 110 emails sent to list in last 3
months
- dev@pulsar.apache.org:
- 135 subscribers (+27 from Jun 2019) - 290 emails sent to list in last 3
months
## Slack activity:
* 1041 Members
* 148 Active weekly users
## GitHub activity:
- 328 PRs from 60 contributors were merged in the last 3 months
- 261 Issues were created and 165 closed in the last 3 months
- 4130 Stars (up from 3540 in June 2019)
-----------------------------------------
Attachment BC: Report from the Apache Royale Project [Piotr Zarzycki]
## Description:
Apache Royale is a new implementation of the principles of Apache Flex,
designed for JavaScript instead of Adobe Flash/AIR runtimes. Apache Royale
improves developer productivity in creating applications to run wherever
JavaScript runs, including on browsers as well as in Apache Cordova
applications, Node, etc.
## Issues:
There are no issues requiring board attention at this time.
## Releases:
Apache Royale 0.9.2 was released on March 16 2018.
Apache Royale 0.9.4 was released on November 14 2018.
## Membership Data:
Community changes, past quarter:
- No new PMC members. Last addition was Alex Harui on 2017-09-20.
- No new committers. Last addition was Greg Dove on 2018-10-28.
- A committer was voted in as a new PMC member on 9/11. The board has been
notified.
## Project Activity:
- No releases this quarter; We have created 0.9.6 RC1
- A lot of time has been invested in obtaining more robust processes and
eliminating errors in the compiler.
- There are some activities and questions from users in area of porting Flex
applications to Royale. We have created special page where individuals and
companies who can help with port are listed.
- Great progress in documentation front:
- Added lots of new docs and relationships with our Reference doc and blog
examples, that should help users.
- Added search capabilities thanks to Algolia DocSearch.
- Great progress in simplify the release process so others can take the RM
role more easily.
- Now we have presence in StackOverflow since end of April under
"apache-royale" tag
- We had a lot of activity on social networks, sharing what is happening in
Apache Royale as we progress in the project. We think it is important to do
this so people outside the project and not following in a daily basis can
get a notion of how we are doing. The numbers are:
- Our Twitter account has gained 590 (previous 549) followers since we
opened it.
- Our Facebook page has 130 (previously 127) likes.
- Our LinkedIn Group has 126 (previously 125) people.
## Community Health:
- Users list:
- 73 subscribers (down 3 in the last 3 months)
- 118 emails sent in the past 3 months (348 in the previous cycle)
- Dev list:
- 76 subscribers (down 4 in the last 3 months)
- 1394 emails sent in the past 3 months (1457 in the previous cycle)
-----------------------------------------
Attachment BD: Report from the Apache Sentry Project [Kalyan Kalvagadda]
## Description:
Apache Sentry is a highly modular system for providing fine-grained role
based authorization to both data and metadata stored on an Apache Hadoop
Cluster.
## Issues:
- There are no issues requiring board attention at this time
## Membership Data:
Apache Sentry was founded 2016-03-15 (3 years ago)
There are currently 40 committers and 38 PMC members in this project.
The Committer-to-PMC ratio is roughly 1:1.
Community changes, past quarter:
- No new PMC members. Last addition was Na Li on 2018-12-10.
- No new committers. Last addition was Arjun Mishra on 2018-07-06.
## Project Activity:
HMS read protection is added. It will be released later this month.
## Community Health:
Contributions to sentry have slowed down in last few months.
dev@sentry.apache.org had a 37% increase in traffic in the past quarter
(11 emails compared to 8):
issues@sentry.apache.org had a 146% increase in traffic in the past quarter
(96 emails compared to 39):
## JIRA activity:
7 issues opened in JIRA, past quarter (-50% decrease)
3 issues closed in JIRA, past quarter (-40% decrease)
## Commit activity
2 commits in the past quarter (-50% decrease)
2 code contributors in the past quarter (no change)
-----------------------------------------
Attachment BE: Report from the Apache ServiceMix Project [Krzysztof Sobkowiak]
## Description:
Apache ServiceMix is a flexible, open-source integration container that
unifies the features and functionality of Apache ActiveMQ, Camel, CXF and
Karaf to provide a complete, enterprise-ready ESB powered by OSGi.
## Issues:
There are no outstanding issues requiring board attention.
## Membership Data:
Apache ServiceMix was founded 2007-09-19 (12 years ago) There are currently 50
committers and 21 PMC members in this project. The Committer-to-PMC ratio is
roughly 7:3.
Community changes, past quarter:
- No new PMC members. Last addition was Andrea Cosentino on 2017-03-15.
- No new committers. Last addition was Andrea Cosentino on 2016-03-13.
## Project Activity:
- During the last period we have released 3 sets of OSGi bundles:
- Apache ServiceMix Bundles 2019.06 on June 28 2019
- Apache ServiceMix Bundles 2019.07 on August 04 2019
- Apache ServiceMix Bundles 2019.08 on September 05 2019
- We should focus more intensively on ServiceMix assembly based on the
newestApache Camel and Apache Karaf, what was a bit outstanding last months.
- We should focus on documentation and samples improvement.
## Community Health:
Due to summer vacation the activity of the community (mailing lists, JIRA,
releases) has been a bit slower than during the last period.
- dev@servicemix.apache.org had a 44% increase in traffic in the past quarter
(49 emails compared to 34)
- issues@servicemix.apache.org had a 39% decrease in traffic in the past
quarter (191 emails compared to 309)
- users@servicemix.apache.org had a 366% increase in traffic in the past
quarter (14 emails compared to 3)
- 75 issues opened in JIRA, past quarter (-8% decrease)
- 72 issues closed in JIRA, past quarter (-13% decrease)
- 459 commits in the past quarter (-21% decrease)
- 6 code contributors in the past quarter (no change)
- 1 PR opened on GitHub, past quarter (-75% decrease)
- 1 PR closed on GitHub, past quarter (-75% decrease)
-----------------------------------------
Attachment BF: Report from the Apache Shiro Project [Les Hazlewood]
## Description:
Apache Shiro is a powerful and flexible open-source application security
framework that cleanly handles authentication, authorization, enterprise
session management and cryptography.
## Issues:
There are no issues requiring board attention at this time
## Membership Data:
Apache Shiro was founded 2010-09-22 (9 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 Francois Papon on 2018-12-20.
- No new committers. Last addition was Francois Papon on 2018-12-20.
## Project Activity:
We are continuing hard work on the preparing of the next 1.5.0 release with:
- upgrade min version of JDK to 8
- better OSGi support
- upgrading dependencies
We want to released the 1.5.0 in next month
We added a new maven-plugin (japicmp) to enforced Shiro api backward
compatibility
Recent releases:
1.4.1 was released on 2019-05-01.
## Community Health:
We have new contributors showing thier interest in the project by making
some PRs
dev@shiro.apache.org had a 24% increase in traffic in the past quarter
(286 emails compared to 230)
user@shiro.apache.org had a 433% increase in traffic in the past quarter
(32 emails compared to 6)
17 issues opened in JIRA, past quarter (-26% decrease)
15 issues closed in JIRA, past quarter (-42% decrease)
28 commits in the past quarter (-22% decrease)
7 code contributors in the past quarter (no change)
22 PRs opened on GitHub, past quarter (-8% decrease)
24 PRs closed on GitHub, past quarter (-20% decrease)
-----------------------------------------
Attachment BG: Report from the Apache Sling Project [Robert Munteanu]
## Description:
Apache Sling™ is a framework for RESTful web-applications based on an
extensible content tree.
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache Sling was founded 2009-06-17 (10 years ago)
There are currently 44 committers and 27 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:2.
Community changes, past quarter:
- Timothée Maret was added to the PMC on 2019-06-21
- Christian Schneider was added as committer on 2019-06-19
## Project Activity:
Good activity level overall, contributions from different people
continue.
## Community Health:
We seem to be getting better at managing contributions. 85 PRs were opened on
GitHub, past quarter (8% increase), but 86 PRs closed on GitHub, past quarter
(40% increase) .
The adaptTo conference took place in Berlin on 2-4 September, drawing over 220
participants. The Sling hackathon took place on the 5th of September.
-----------------------------------------
Attachment BH: Report from the Apache SpamAssassin Project [Sidney Markowitz]
-----------------------------------------
Attachment BI: Report from the Apache Stanbol Project [Rafa Haro]
-----------------------------------------
Attachment BJ: Report from the Apache Storm Project [P. Taylor Goetz]
## Description:
The mission of Storm is the creation and maintenance of software related to
Distributed, real-time computation system
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache Storm was founded 2014-09-16 (5 years ago)
There are currently 40 committers and 39 PMC members in this project.
The Committer-to-PMC ratio is roughly 1:1.
Community changes, past quarter:
- Aaron Gresch was added to the PMC on 2019-08-08
- Aaron Gresch was added as committer on 2019-08-09
## Project Activity:
- The community is currently working on releasing version 2.1.0
- The last release 2.0.0 was released on 2019-05-30.
## Community Health:
- We have begun rotating the release manager role so more members of the
community are familiar with the release process.
- We have had a discussion regarding rotating the PMC Chair, and I have decided
to step down to allow someone else assume the role. An announcement and VOTE
for a new Chair will take place in the near future.
- There has been a surge in developer activity across JIRA, GitHub, and the dev@
mailing list after the release of version 2.0.0 and the establishment of the
2.x.x version lines.
- The project is celebrating it's 5 year as a top-level project!
-----------------------------------------
Attachment BK: Report from the Apache Synapse Project [Isuru Udana]
## Description:
Apache Synapse is a high performance, flexible, lightweight Enterprise Service
Bus (ESB) and a mediation framework.
## Issues:
None identified.
## Membership Data:
Apache Synapse was founded 2007-12-19 (12 years ago) There are currently 34
committers and 26 PMC members in this project. The Committer-to-PMC ratio is
roughly 9:7.
Community changes, past quarter:
- No new PMC members. Last addition was Prabath Ariyarathna on 2017-05-04.
- No new committers. Last addition was Prabath Ariyarathna on 2017-02-10.
## Project Activity:
There was a slight increase in the activity in the project compared to the
last quarter. One of the major activity we did during this quarter is moving
the project source code into Github. Moving the source into Github make life
easier for new contributors to send contributions. We got several
contributions from three new contributors after we did this move. We are
planning to incorporate a build system (Travis or Jenkins) for Github pull
requests through Github webhooks to make the review process simpler.
## Community Health:
There is a slight drop in the mailing list activity compared to last quarter.
Activity in the Jira has also gone down. However, activity in Github and
commits has gone up. We see a positive trend in the project activity in the
latter half of the quarter after project source code is moved to Github. So
hopefully we will able to increase the project activity further in the next
quarter too. A new contributor has given a suggestion and submitted a pull
request to introduce a unit testing framework for Synapse configurations. It
is going to be a major feature addition that we couldn’t introduce so far. We
are looking forward to more new contributions with the positive trend created
with the Github move.
-----------------------------------------
Attachment BL: Report from the Apache Tajo Project [Hyunsik Choi]
-----------------------------------------
Attachment BM: 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:
As Shane Curcuru correctly noted, the Tapestry team was very slow in
responding and fixing the 3 vulnerabilities we got last year and we apologize
for that. Fixes for two of them were released in Tapestry 5.4.4, published in
December 18th, 2018. The other issue was fixed in 5.4.5, released in September
7th, 2019. We promise to do better next time.
## 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:
Tapestry 5.4.5 was released September 7th, 2019, and we're working towards the
next major release, 5.5.0.
## Community Health:
The Tapestry community has been shrinking over time for two main reasons:
* It was a niche project among other Java web frameworks since its beginning.
* The web development world has been steadily moving logic from server to
client. In other words, more logic is being coded in JavaScript to run in
the browser and less in the server, which is usually reduced to a set of
REST endpoints. This way, Java web frameworks, or similar frameworks in any
language, are losing users.
Commits have been sparse in the latest couple of years due to mainly three
factors:
* We don't have any committer which is paid to work full-time or even
part-time on Tapestry as other projects do. We're all working on Tapestry on
our free time, with the exception of a few cases of a company commissioning
us to work on some small enhancements.
* The project reached a maturity level so it doesn't really have many features
to be added.
* The codebase is very flexible, so many interesting things can and are done
outside of the Tapestry project. Our PMC has decided, a long time ago, to
not include more subprojects so it could focus on the Tapestry core. There's
a number of open source projects built on Tapestry, some integrating it with
other libraries and frameworks, and some provide components.
We may have a small community, but it's passionate.
We voted a new PMC member this month. There's one committer we may invite to
the PMC.
Stats:
* dev@tapestry.apache.org had a 284% increase in traffic in the past quarter
(50 emails compared to 13)
* users@tapestry.apache.org had a 76% increase in traffic in the past quarter
(88 emails compared to 50)
* 3 issues opened in JIRA, past quarter (200% increase)
* 1 issue closed in JIRA, past quarter (-50% decrease)
* 10 commits in the past quarter (42% increase)
* 3 code contributors in the past quarter (50% increase) 1 PR opened on
GitHub, past quarter (100% increase)
-----------------------------------------
Attachment BN: Report from the Apache Tomcat Project [Mladen Turk]
## Description:
- A Java Servlet, JavaServer Pages, Java WebSocket and Java
Unified Expression language specifications implementation.
## Issues:
- There are no issues requiring board attention at this time
## Activity:
- Continued healthy activity across multiple components and
responsiveness on both dev and user lists.
- Currently 6 PMC members are attending ApacheCon NA 2019
## PMC changes:
- Currently 28 PMC members.
- Igal Sapir was added to the PMC on Mar 18 2019
## Committer base changes:
- Currently 46 committers.
- Woonsan Ko was added as a committer on Dec 19 2018
## Releases:
- Apache Tomcat 9.0.24 was released on 2019-08-17
- Apache Tomcat 9.0.22 was released on 2019-07-09
- Apache Tomcat 8.5.45 was released on 2019-08-21
- Apache Tomcat 8.5.43 was released on 2019-07-09
- Apache Tomcat 7.0.96 was released on 2019-07-29
## Trademark:
- No new trademark issues in the last 3 months
and there are currently no outstanding trademark issues that the
Apache Tomcat PMC is working on.
- Detailed history is available at:
https://svn.apache.org/repos/private/pmc/tomcat/trademark-status.txt
## Security:
- Detailed status:
http://tomcat.apache.org/security.html
-----------------------------------------
Attachment BO: Report from the Apache Trafodion Project [Pierre Smits]
## Description:
Apache Trafodion is the creation and maintenance of software related to
webscale SQL-on-Hadoop solutions to ensure transactional integrity and
operational workloads for Big Data applications.
## Issues:
There are no issues requiring the attention of the board at this moment.
## Membership Data:
Apache Trafodion was founded 2017-12-20 (2 years ago) There are currently 24
committers and 15 PMC members in this project. The Committer-to-PMC ratio is
1.6:1.
The Subscriber-to-Committer ratio is 3.6:1.
Community changes, past quarter:
- No new PMC members. Last addition was Anoop Sharma on 2018-12-06.
- No new committers. Last addition was Prashanth Vasudev on 2018-11-13.
## Project Activity:
The latest release of the project was r2.3.0, which was released to the public
on 2019-02-27. The project continues to work on improving the products, and
working towards a new release. In the coming period the PMC will continue to
work on on boarding new committers.
## Community Health:
In the reporting quarter the project experienced significant decreases of
activities in the mailing lists, compared to the previous reporting quarter.
The decrease of activities seem to be anomalous, when the period is compared
to previous periods and the same period of the previous reporting year.
However, activities in the previous reporting period was quite high to get the
release out. The pull-request on GitHub and commit activities show similar
decreases.
At the moment, there is insufficient data to draw conclusion. Upcoming quarter
will prove whether this is the new reality.
The PMC regards the project, even though there are significant drops in
activities, still as healthy.
## Project statitics:
Mailing Lists:
- dev@trafodion.apache.org:
- 87 subscribers (down 5 in the last 3 months):
- 75 emails sent to list (Down 35%).
- codereview@trafodion.apache.org:
- 19 subscribers (down 5 in the last 3 months):
- 104 emails sent to list (Down 73%).
- issues@trafodion.apache.org:
- 28 subscribers (down 5 in the last 3 months):
- 139 emails sent to list (Down 70%).
- user@trafodion.apache.org:
- 99 subscribers (down 3 in the last 3 months):
- Currently no automated insights in number of ml postings provided by
ComDev-reporter services.
- security@trafodion.apache.org:
- 3 subscribers (down 0 in the last 3 months):
- Currently no automated insights in number of ml postings provided by
ComDev-reporter services.
- private@trafodion.apache.org:
- 16 subscribers (down 1 in the last 3 months):
- Currently no automated insights in number of ml postings provided by
ComDev-reporter services.
JIRA activities:
- 13 tickets created (down 50%)
- 11 tickets closed (Down 81%)
GitHub Actviities:
- PR opened: 10 (down 67%)
- PR closed: 11 (down 66%)
Commit activities:
- commits: 28 (Down 64%)
- active contributors: 5 (down 28%)
-----------------------------------------
Attachment BP: Report from the Apache Twill Project [Terence Yim]
## Description:
The mission of Twill is the creation and maintenance of software related to Use
Apache Hadoop YARN's distributed capabilities with a programming model that is
similar to running threads
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache Twill was founded 2016-06-15 (3 years ago)
There are currently 9 committers and 6 PMC members in this project.
The Committer-to-PMC ratio is 3:2.
Community changes, past quarter:
- No new PMC members. Last addition was Andreas Neumann on 2016-06-15.
- No new committers. Last addition was Yuliya Feldman on 2018-03-07.
## Project Activity:
We are planning to release 0.14.0 in the coming quarter to include some of
improvements and bug fixes. We are also working on support for Kubernetes,
which generated a lot of interests from the community via offline discussions
and meetups.
## Community Health:
There is no change in the number of subscribers in the dev@ and commits@
mailing lists, which are 66 and 16 subscribers respectively. There is slight
increase in activities in the dev@ mailing list, with a 16% increase in
traffic in the past quarter (7 emails compared to 6). There were 3 new JIRAs
created in the past quarter and no JIRA was closed.
-----------------------------------------
Attachment BQ: Report from the Apache UIMA Project [Marshall Schor]
Board report for Apache UIMA, for September 2019.
## Description:
Apache UIMA's mission: the creation and maintenance of open-source software
related to the analysis of unstructured data, guided by the UIMA Oasis
Standard. The software provides frameworks, tools and annotators,
facilitating the analysis of unstructured content such as text, audio and
video.
## Membership Data:
Apache UIMA was founded 2010-03-16 (9.5 years ago)
There are currently 25 committers and 16 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 Lou DeGenaro on 2016-05-02.
- No new committers. Last addition was Viorel Morari on 2018-09-20.
## Releases:
2 releases in last quarter
uimaj-3.1.0 was released on 2019-08-15.
uimaj-2.10.4 was released on 2019-08-09.
## Board question from last report: druggeri:
>> It's good to see new contributors.
>> Any prospects for new PMC members... it's been a while.
We do not currently have any new PMC member prospects,
but we keep our eye out for some.
Activity:
After the release of uimaj, we started the work to migrate
that project from SVN to GIT.
This has been a slow and difficult process,
due mainly to a couple of things
1) the documentation for GIT at apache
leaves several things undocumented, and also includes
apparently out-of-date information.
See for example,
https://issues.apache.org/jira/projects/LEGAL/issues/LEGAL-478
(read the comments)
2) simple modifications for one's project's GIT repository
such as renaming a branch, sometimes require filing of
INFRA Jira issues, and due to current load,
these appear in their KANBAN queue that's 100's of items long.
See https://issues.apache.org/jira/projects/INFRA, and
choose the KANBAN view on the left-hand navigation.
The result is that with the current INFRA staffing resources,
it can take more than a week to get these acted on.
Community Health: The community continues to be moderately active;
some new contributors doing patches.
Issues: No Board level issues at this time.
-----------------------------------------
Attachment BR: Report from the Apache Unomi Project [Serge Huber]
## Description:
The mission of Apache Unomi is the creation and maintenance of software related
to providing a reference implementation of the OASIS Customer Data Platform
specification currently being worked on by the OASIS Context Server Technical
Committee
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache Unomi was founded 2019-02-20 (6 months ago)
There are currently 12 committers and 6 PMC members in this project.
The Committer-to-PMC ratio is 2:1.
Community changes, past quarter:
- No new PMC members. Last addition was David Griffon on 2019-02-20.
- No new committers. Last addition was Taybou on 2019-04-01.
## Project Activity:
Following the release of Apache Unomi 1.4.0 we are now working on improving
the documentation & website to make the project more visible and easier to get
started with. We are also looking at recruiting new PMC members (looking first
at existing committers that are not yet PMC members) to address the concerned
raised in the last board report feedback. We are also preparing two
presentations to be giving at ApacheCon NA to help with project visibility and
community growth.
We are of course also working on improving the project, mostly focusing on
requests coming from the community.
## Community Health:
We are currently focusing on growing the community by making sure that the
newcomer's experience is as smooth as possible. There is still some work to be
done but already we are seeing more activity on the user mailing list (88%
increase). Because of this focus the dev mailing list activity has reduced a
little bit (56%) but should pick back up as focus on development comes back
after this effort.
In general we are happy with the way the user community is evolving but we want
to see more growth so presenting the project at ApacheCon NA is an important
part of that effort as, as seen last year in the stats following ApacheCon NA
2018, it really helps making the project a lot more visible.
-----------------------------------------
Attachment BS: Report from the Apache VCL Project [Josh Thompson]
## Description:
The mission of the Apache VCL project is to create and maintain a modular
cloud computing platform which dynamically provisions and brokers remote
access to compute resources. A self-service web portal is used to request
resources and for administration. Apache VCL is primarily used in college and
university computing environments.
## Issues:
No notable issues needing attention.
## Membership Data:
Apache VCL was founded 2012-06-19 (7 years ago)
There are currently 10 committers and 7 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:4.
Community changes, past quarter:
- No new PMC members. Last addition was Aaron Coburn on 2012-06-19.
- No new committers. Last addition was Mike Jennings on 2019-01-04.
## Project Activity:
Apache VCL 2.5.1 was released on July 25th, 2019.
## Community Health:
Community Health remains the same - slow progress. The release caused a
decrease in traffic on the dev list and an increase in traffic on the user
list.
-----------------------------------------
Attachment BT: Report from the Apache Wicket Project [Andrea Del Bene]
## Description:
Apache Wicket is an open source Java component oriented web application
framework.
## Issues:
- No issues require board attention.
## Membership Data:
Apache Wicket was founded 2007-06-20 (12 years ago)
There are currently 32 committers and 31 PMC members in this project.
The Committer-to-PMC ratio is roughly 1:1.
Community changes, past quarter:
- Ernesto Reinaldo Barreiro was added to the PMC on 2019-08-14
- Ernesto Reinaldo Barreiro was added as committer on 2019-08-13
## Project Activity:
- We have released the third milestones for Wicket 9 and we continue to work
to publish a new main release as soon as possible. We got in contact with
Sally Khudairi to prepare a public announce for Wicket 9. Works have been
slowed down a bit since our last contact as many people had their vacation
time in August. Things should proceed a little faster in the next months.
## Community Health:
- The community is stable as is to be expected from a mature server
side Java web framework. We don't anticipate a sudden large growth
or large decline.
- Questions to the user list and dev list are answered, resolved and
discussed.
## Releases:
- 7.15.0 was released on 2019-09-07.
- 8.6.0 was released on 2019-09-07
-----------------------------------------
Attachment BU: Report from the Apache Xerces Project [Michael Glavassevich]
Xerces-J
Xerces-J's Ant build has been updated so that it can now compile the source
using Java 9+. A few other fixes were made to address JIRA issues that had
been opened by users.
Mailing list traffic has been low; roughly 50+ posts on the j-dev and j-users
lists since the beginning of May 2019.
No new releases since the previous report. The latest release is Xerces-J
2.12.0 (April 30th, 2018).
Xerces-C
A request was made to migrate the source to Git in July. The infra folks
pointed out that this is a self-serve process now. No follow-up from the
developers yet.
Most of the activity since the previous report has been in responding to JIRA
issues from the community.
Mailing list traffic has been low; roughly 60+ posts on the c-dev and c-users
lists since the beginning of May 2019.
No new releases since the previous report. The latest release is Xerces-C
3.2.2 (September 19th, 2018).
Xerces-P
Nothing in particular to report. There was no development activity over the
reporting period.
XML Commons
No activity over the reporting period.
Committer / PMC Changes
The most recent committers were added in April 2017 (Xerces-C) and May 2017
(Xerces-J).
No new PMC members since the last report. The most recent addition to the PMC
was in June 2016.
Two committers have committed changes to SVN since May 2019.
Wiki
The Xerces Wiki was recently migrated to Confluence. The automation worked
well for the most part, but will need to manually fix up some pages.
-----------------------------------------
Attachment BV: Report from the Apache Yetus Project [Allen Wittenauer]
## Description:
Apache Yetus is a collection of libraries and tools that enable contribution
and release processes for software projects
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache Yetus was founded 2015-09-15 (4 years ago)
There are currently 12 committers and 9 PMC members in this project.
The Committer-to-PMC ratio is 4:3.
Community changes, past quarter:
- No new PMC members. Last addition was Akira Ajisaka on 2018-12-17.
- No new committers. Last addition was Akira Ajisaka on 2018-02-06.
## Project Activity:
We released 0.11.0! New in this release was adding more static linters for go,
markdown, and protobuf, emojis on Github posts, and support for Slack and
Cirrus CI.
So far this year, we've done really well on getting somewhat quarterly
releases out. This has been a goal from day one. Let's hope it continues!
* 0.11.0 was released on 2019-08-28.
* 0.10.0 was released on 2019-04-21.
* 0.9.0 was released on 2019-01-18.
Allen Wittenauer gave a talk on "Testing Contributions at Scale" at ACNA19
that featured the project.
## Community Health:
The past quarter has been relatively slow (with literally no traffic for a bit
over a month). This reflects that the busy-ness of the primary contributor to
the project:
* 12 commits in the past quarter (-85% decrease)
* 3 code contributors in the past quarter (-50% decrease)
* 6 PRs opened on GitHub, past quarter (-70% decrease)
* 6 PRs closed on GitHub, past quarter (-76% decrease)
-----------------------------------------
Attachment BW: Report from the Apache ZooKeeper Project [Flavio Paiva Junqueira]
## Description:
Apache ZooKeeper is a software system for distributed coordination. It enables
the implementation of a variety of primitives and mechanisms that are
critical for safety and liveness in distributed settings, e.g.,
distributed locks, master election, group membership, and configuration.
## Issues:
No specific issues to the board.
## Membership Data:
Apache ZooKeeper was founded 2010-11-17 (9 years ago)
There are currently 26 committers and 14 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:4.
Community changes, past quarter:
- No new PMC members. Last addition was Andor Molnar on 2019-04-08.
- No new committers. Last addition was Enrico Olivelli on 2019-05-19.
## Project Activity:
No new releases during the reporting period.The latest releases are:
* 3.5.5 was released on 2019-05-20.
* 3.4.14 was released on 2019-04-01.
* 3.4.13 was released on 2018-07-16.
## Community Health:
The traffic on the dev list has dropped during the period due to us shifting
some of the notification traffic from dev to the notifications@ list. We had a
spike on the issues@ list due to bulk changes to Jira issues (version
updates). We also observed more traffic on the user list, which are general
questions about ZooKeeper. We did observe a good number of questions around
the internals (Zab and reconfiguration) of ZooKeeper.
* dev@zookeeper.apache.org had a 44% decrease in traffic in the past quarter
(1231 emails compared to 2169)
* issues@zookeeper.apache.org had a 3130% increase in traffic in the past
quarter (1260 emails compared to 39)
* notifications@zookeeper.apache.org had a 1276% increase in traffic in the
past quarter (1666 emails compared to 121)
* user@zookeeper.apache.org had a 183% increase in traffic in the past
quarter (184 emails compared to 65)
* 112 issues opened in JIRA, past quarter (-1% decrease)
* 83 issues closed in JIRA, past quarter (2% increase)
* 102 commits in the past quarter (-18% decrease)
* 32 code contributors in the past quarter (39% increase)
* 96 PRs opened on GitHub, past
quarter (-29% decrease)
* 102 PRs closed on GitHub, past quarter (-7% decrease)
------------------------------------------------------
End of minutes for the September 18, 2019 board meeting.
Index