Index
Links: 2019 - All years
- Original The Apache Software Foundation
Board of Directors Meeting Minutes
August 21, 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/3xqa
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
Rich Bowen
Shane Curcuru
Ted Dunning
Daniel Ruggeri
Craig L Russell
Roman Shaposhnik - parted ~11:00
Joan Touzet
Directors Absent:
Myrle Krantz
Executive Officers Present:
David Nalley
Tom Pappas
Sam Ruby
Matt Sicker
Executive Officers Absent:
Ulrich Stärk
Guests:
Daniel Gruno
Gavin McDonald
Geoff Macartney
Greg Stein
Jim Jagielski
Kevin A. McGrail - parted 11:05 Pacific
3. Minutes from previous meetings
Published minutes can be found at:
http://www.apache.org/foundation/board/calendar.html
A. The meeting of July 17, 2019
See: board_minutes_2019_07_17.txt
Approved by General Consent.
B. The meeting of May 16, 2019
See: board_minutes_2019_05_16.txt
Approved by General Consent.
4. Executive Officer Reports
A. Chairman [Craig]
Several board members plan to attend the 20th anniversary celebration
at ApacheCon NA in Las Vegas. Timing does not work for a regular board
meeting during the conference but there will be ample opportunity for
individual directors to meet informally.
Work continues to better understand how Apache can be more welcoming
to underrepresented communities. A call from the Diversity and
Inclusion VP was issued to solicit volunteer mentors to work with
Outreachy to engage mentees. All Apache communities are encouraged to
participate. https://s.apache.org/seeking-mentors
The incubator has made progress on a new DISCLAIMER-WIP for
non-compliant podling releases. See discussion topic 8A.
Discussion continues on how to make board@apache.org a productive
environment to conduct the board's work.
Discussion continues on socializing the concept of non-code
contributions being a factor in moving contributors along the path to
become committers.
B. President [Sam]
Financially, we are doing very well even after taking into
consideration timing considerations, which generally are breaking in
our favor at this time making the picture look even better.
Brand management responded to four queries, processed four
registrations, and resolved one infringement.
Fundraising is operating smoothly, and focusing on restructuring and
conference sponsors.
Marketing and publicity focused on cross-committee, graphics, and
events liaisons, while also producing an annual report as well as
handling a number of informal announcements and one analyst query.
ACNA is coming together, with strong sponsorship, though possibly
falling a bit short on attendees. ACEU is tying up loose ends.
Finance renewed D&O and is working closely with conferences and
fundraising.
Diversity and Inclusion made progress on each of its three
initiatives, outlined a moderation policy, and added one new committee
member
Additionally, please see Attachments 1 through 8.
C. Treasurer [Ulrich]
Operating Cash on July 31st, 2019 was $2,473K, which is up $170.2K
from last month’s ending balance (Jun 19) of $2,302.8K. Total Cash as
of July 31st, 2019 is $3,866.9K (includes the Pineapple and restricted
Donation) as compared to $3,435.3K on July 31st 2018 (an increase of
$431.6K year over year). The July 2019 ending Operating cash balance
of $2,473K represents an Operating cash reserve of 10 months based on
the FY20 Cash forecast average monthly spending of $247.9K/month. The
ASF actual Operating reserve of 10 months at the end of July 2019 is
ahead of the budgeted 8.1 month reserve for YTD through July 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 $209.1K. As compared to FY18, YTD revenue
is ahead by $205.1K primarily due to Conference income year over year
at this point in time
YTD expenses through July 31, 2019 are under budget by $259.5K. All
departments, except for Publicity, are under budget at the end of July
2019, which is primarily due to timing and expenses for ACNA19.
Conference are at this point under budget due to timing and it is
expected to normalize over the next two months as ACNA and ACEU are
happening in the next few months.
Regarding Net Income (NI), YTD FY20 the ASF finished with a positive
$52.8K NI vs a budgeted negative <$415.9K> NI or $468.7K ahead of
Budget, 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 $205.1K as noted above,
but we are also out pacing expenses by $125.9K; thus, year over year
NI for FY20 is ahead of FY19 by $79.2K.
Current Balances:
Boston Private CDARS Account 2,261,344.76
Citizens Money Market 1,084,270.11
Citizens Checking 520,360.73
Paypal - ASF 985.16
Total Checking/Savings 3,866,960.76
Jul-19 Budget Variance
Income Summary:
Inkind Revenue 0.00 0.00 0.00
Public Donations 1,262.66 988.07 274.59
Sponsorship Program 137,000.00 126,000.00 11,000.00
Programs Income 0.00 0.00 0.00
Conference/Event Income 195,232.00 60,000.00 135,232.00
Other Income 499.59 1,247.35 -747.76
Interest Income 324.03 450.00 -125.97
Total Income 334,318.28 188,685.42 145,632.86
Expense Summary
In Kind Expense 0.00 0.00 0.00
Infrastructure 89,195.44 85,733.08 3,462.36
Programs Expense 0.00 3,333.33 -3,333.33
Publicity 24,244.17 44,233.34 -19,989.17
Brand Management 5,425.44 8,166.67 -2,741.23
Conferences 28,334.00 211,250.00 -182,916.00
Travel Assistance Committee 0.00 30,000.00 -30,000.00
Fundraising 11,398.76 16,080.00 -4,681.24
Treasury Services 3,350.00 3,350.00 0.00
General & Administrative 2,136.29 1,915.00 221.29
Diversity and Inclusion 0.00 5,833.33 -5,833.33
Total Expense 164,084.10 409,894.75 -245,810.65
Net Income 170,234.18 -221,209.33 391,443.51
YTD FY20 Budget Variance
Income Summary:
Inkind Revenue 0.00 0.00 0.00
Public Donations 6,211.93 6,756.48 -544.55
Sponsorship Program 230,000.00 262,000.00 -32,000.00
Programs Income 0.00 0.00 0.00
Conference/Event Income 296,866.00 60,000.00 236,866.00
Other Income 7,126.67 2,282.40 4,844.27
Interest Income 1,307.09 1,350.00 -42.91
Total Income 541,511.69 332,388.88 209,122.81
Expense Summary
In Kind Expense 0.00 0.00 0.00
Infrastructure 234,350.84 257,199.24 -22,848.40
Programs Expense 0.00 9,999.99 -9,999.99
Publicity 117,256.05 94,775.02 22,481.03
Brand Management 5,425.44 24,500.01 -19,074.57
Conferences 72,813.17 225,750.00 -152,936.83
Travel Assistance Committee 0.00 50,000.00 -50,000.00
Fundraising 40,267.51 48,240.00 -7,972.49
Treasury Services 10,050.00 10,050.00 0.00
General & Administrative 8,572.57 10,245.00 -1,672.43
Diversity and Inclusion 0.00 17,499.99 -17,499.99
Total Expense 488,735.58 748,259.25 -259,523.67
Net Income 52,776.11 -415,870.37 468,646.48
D. Secretary [Matt]
In July, there were 68 ICLAs, two CCLAs, five software grants, and one
member emeritus request received.
The tooling issue around GPG signature verification has since been
fixed by the Whimsy PMC. Documentation on apache.org around submitting
digitally signed documents was updated to reflect our current accepted
methods and in particular, it points to sks-keyservers.net instead of
keyservers we had previous problems with.
E. Executive Vice President [David]
During some of the activities of the month we discovered some fragile
bits of the Foundation operations that have a single or tenuous links
to external service providers. In particular, most of our liaison with
Virtual happens via Tom, making him a single point of failure. In the
course of our relationship with Virtual it's grown considerably in
scope from accounting work to providing significant finance
capabilities, handling our PEO duties, event planning, and more. At
the same time, Tom's responsibilities at Virtual have also grown
considerably, and a lot of our operations now have a component that
Virtual is involved in. Accordingly, Tom and I are discussing how we
might best increase the connective tissue between Ops at the ASF and
Virtual. More to come on this in coming months.
Infrastructure
==============
Infrastructure completed a datacenter exit in a very short timeframe,
which will result in a large cost savings for the Foundation.
There was additionally a mail issue with Virtual, where no mail from
apache.org was being delivered. This situation happened twice, with no
obvious blips in monitoring. While this affected destinations other
than Virtual as well, none of them were as painful. There is now in
place a temporary workaround, and some robust monitoring that looks
for any queue of messages sent to Virtual that sit around for more a
short period of time.
Travel Assistance
=================
This month also saw significant progress in documenting tribal
knowledge around the process and tools for running TAC, which also
eliminates some single points of failure.
Flights for EU are booked. Significant delays and problems securing
ACNA tickets from our travel agency has been an issue. Those are
mostly resolved, but I expect it will result in some changes in the
future.
F. Vice Chairman [Shane]
No activity to report this month.
Executive officer reports approved as submitted by General Consent.
5. Additional Officer Reports
A. VP of W3C Relations [Andy Seaborne / Daniel]
No report was submitted.
@Daniel: pursue a report for W3C Relations
B. Apache Legal Affairs Committee [Roman Shaposhnik]
See Attachment 10
C. Apache Security Team Project [Mark J. Cox / Craig]
See Attachment 11
D. VP of Data Privacy [John Kinsella / Joan]
See Attachment 12
E. VP of Jakarta EE Relations [Mark Struberg / Rich]
No report was submitted.
@Joan: pursue a report for Jakarta EE Relations
Additional officer reports approved as submitted by General Consent.
6. Committee Reports
Summary of Reports
The following reports required further discussion:
# Apex [rb]
# Data Privacy [clr]
# Hama [td]
# Mesos [wohali]
# RocketMQ [myrle, wohali, clr]
# Serf [druggeri]
# Spark [myrle]
# Tapestry [curcuru]
A. Apache Ambari Project [Jayush Luniya / Myrle]
See Attachment A
B. Apache Ant Project [Jan Materne / Roman]
See Attachment B
C. Apache Apex Project [Thomas Weise / Ted]
See Attachment C
D. Apache Archiva Project [Olivier Lamy / Danny]
See Attachment D
E. Apache Avro Project [Thiruvalluvan M. G. / Shane]
See Attachment E
F. Apache BookKeeper Project [Sijie Guo / Ted]
See Attachment F
G. Apache Brooklyn Project [Geoff Macartney / Danny]
See Attachment G
H. Apache Buildr Project [Antoine Toulme / Rich]
See Attachment H
I. Apache Cassandra Project [Nate McCall / Craig]
See Attachment I
J. Apache Clerezza Project [Hasan Hasan / Shane]
See Attachment J
K. Apache Cocoon Project [Cédric Damioli / Roman]
See Attachment K
L. Apache Community Development Project [Sharan Foga / Joan]
See Attachment L
M. Apache CouchDB Project [Jan Lehnardt / Daniel]
See Attachment M
N. Apache Creadur Project [Brian E Fox / Myrle]
See Attachment N
O. Apache DeltaSpike Project [Mark Struberg / Roman]
No report was submitted.
@Daniel: pursue a report for DeltaSpike
P. Apache DRAT Project [Tom Barber / Daniel]
See Attachment P
Q. Apache Drill Project [Arina Ielchiieva / Ted]
See Attachment Q
R. Apache Dubbo Project [Ian Luo / Danny]
See Attachment R
S. Apache Empire-db Project [Rainer Döbele / Joan]
See Attachment S
T. Apache Flume Project [Ferenc Szabo / Rich]
See Attachment T
U. Apache Forrest Project [David Crossley / Shane]
See Attachment U
V. Apache FreeMarker Project [Dániel Dékány / Craig]
See Attachment V
W. Apache Geode Project [Karen Miller / Myrle]
See Attachment W
X. Apache Giraph Project [Dionysios Logothetis / Shane]
See Attachment X
Y. Apache Gora Project [Kevin Ratnasekera / Myrle]
See Attachment Y
Z. Apache Groovy Project [Paul King / Daniel]
See Attachment Z
AA. Apache Hama Project [Chia-Hung Lin / Ted]
No report was submitted.
@Ted: pursue a report for Hama
AB. Apache HTTP Server Project [Daniel Gruno / Craig]
See Attachment AB
AC. Apache HttpComponents Project [Asankha Chamath Perera / Joan]
See Attachment AC
AD. Apache Ignite Project [Denis A. Magda / Rich]
See Attachment AD
AE. Apache Impala Project [Jim Apple / Danny]
See Attachment AE
AF. Apache Incubator Project [Justin Mclean / Roman]
See Attachment AF
AG. Apache jUDDI Project [Alex O'Ree / Danny]
See Attachment AG
AH. Apache Juneau Project [James Bognar / Daniel]
See Attachment AH
AI. Apache Kafka Project [Jun Rao / Roman]
See Attachment AI
AJ. Apache Kibble Project [Rich Bowen]
See Attachment AJ
AK. Apache Knox Project [Larry McCay / Craig]
See Attachment AK
AL. Apache Kylin Project [Luke Han / Shane]
See Attachment AL
AM. Apache Lens Project [Amareshwari Sriramadasu / Ted]
See Attachment AM
AN. Apache Libcloud Project [Tomaž Muraus / Rich]
See Attachment AN
AO. Apache Logging Services Project [Matt Sicker / Joan]
See Attachment AO
AP. Apache ManifoldCF Project [Karl Wright / Myrle]
See Attachment AP
AQ. Apache Marmotta Project [Jakob Frank / Myrle]
See Attachment AQ
AR. Apache Mesos Project [Benjamin Hindman / Joan]
See Attachment AR
@Joan: follow up with more detailed board report for next
month
AS. Apache MetaModel Project [Kasper Sørensen / Roman]
See Attachment AS
AT. Apache Oozie Project [Gézapeti / Craig]
See Attachment AT
AU. Apache Open Climate Workbench Project [Huikyo Lee / Daniel]
See Attachment AU
AV. Apache OpenWhisk Project [Dave Grove / Shane]
See Attachment AV
AW. Apache Perl Project [Philippe Chiasson / Rich]
No report was submitted.
AX. Apache Phoenix Project [Josh Elser / Danny]
See Attachment AX
AY. Apache POI Project [Dominik Stadler / Ted]
See Attachment AY
AZ. Apache Qpid Project [Robert Gemmell / Joan]
See Attachment AZ
BA. Apache REEF Project [Sergiy Matusevych / Danny]
See Attachment BA
BB. Apache River Project [Peter Firmstone / Rich]
See Attachment BB
BC. Apache RocketMQ Project [Xiaorui Wang / Shane]
See Attachment BC
@Ted: clarify red tape and release process
BD. Apache Roller Project [David M. Johnson / Myrle]
See Attachment BD
BE. Apache Santuario Project [Colm O hEigeartaigh / Craig]
See Attachment BE
BF. Apache Serf Project [Branko Čibej / Roman]
See Attachment BF
BG. Apache ServiceComb Project [Willem Ning Jiang / Ted]
See Attachment BG
BH. Apache SIS Project [Martin Desruisseaux / Daniel]
See Attachment BH
BI. Apache Spark Project [Matei Alexandru Zaharia / Myrle]
See Attachment BI
BJ. Apache Subversion Project [Stefan Sperling / Daniel]
See Attachment BJ
BK. Apache Syncope Project [Francesco Chicchiriccò / Rich]
See Attachment BK
BL. Apache SystemML Project [Jon Deron Eriksson / Danny]
See Attachment BL
BM. Apache Tapestry Project [Thiago Henrique De Paula Figueiredo / Shane]
See Attachment BM
@Shane: pursue a more detailed report
BN. Apache TomEE Project [David Blevins / Joan]
See Attachment BN
BO. Apache Traffic Control Project [David Neuman / Ted]
See Attachment BO
BP. Apache Turbine Project [Georg Kallidis / Craig]
See Attachment BP
BQ. Apache Usergrid Project [Michael Russo / Roman]
See Attachment BQ
BR. Apache Velocity Project [Nathan Bubna / Shane]
See Attachment BR
BS. Apache Whimsy Project [Sam Ruby / Rich]
See Attachment BS
BT. Apache Xalan Project [Gary D. Gregory / Roman]
See Attachment BT
BU. Apache Xerces Project [Michael Glavassevich / Myrle]
No report was submitted.
@Ted: pursue a report for Xerces
BV. Apache XML Graphics Project [Clay Leeds / Craig]
See Attachment BV
BW. Apache Zeppelin Project [Lee Moon Soo / Danny]
See Attachment BW
@Danny: follow up to get a report for the normal reporting
cycle
BX. Apache Griffin Project [William Guo / Daniel]
See Attachment BX
BY. Apache Lucene.Net Project [Shad Storhaug / Joan]
See Attachment BY
Committee reports approved as submitted by General Consent.
7. Special Orders
A. Change the Apache Kudu Project Chair
WHEREAS, the Board of Directors heretofore appointed Todd Lipcon (todd)
to the office of Vice President, Apache Kudu, and
WHEREAS, the Board of Directors is in receipt of the resignation of
Todd Lipcon from the office of Vice President, Apache Kudu, and
WHEREAS, the Project Management Committee of the Apache Kudu project
has chosen by vote to recommend Adar Dembo (adar) as the successor to
the post;
NOW, THEREFORE, BE IT RESOLVED, that Todd Lipcon is relieved and
discharged from the duties and responsibilities of the office of Vice
President, Apache Kudu, and
BE IT FURTHER RESOLVED, that Adar Dembo be and hereby is appointed to
the office of Vice President, Apache Kudu, 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 Kudu Project Chair, was
approved by Unanimous Vote of the directors present.
B. Change the Apache Drill Project Chair
WHEREAS, the Board of Directors heretofore appointed Arina Ielchiieva
(arina) to the office of Vice President, Apache Drill, and
WHEREAS, the Board of Directors is in receipt of the resignation of
Arina Ielchiieva from the office of Vice President, Apache Drill, and
WHEREAS, the Project Management Committee of the Apache Drill project
has chosen by vote to recommend Charles Givre (cgivre) as the successor
to the post;
NOW, THEREFORE, BE IT RESOLVED, that Arina Ielchiieva is relieved and
discharged from the duties and responsibilities of the office of Vice
President, Apache Drill, and
BE IT FURTHER RESOLVED, that Charles Givre be and hereby is appointed to
the office of Vice President, Apache Drill, 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 Drill Project Chair, was
approved by Unanimous Vote of the directors present.
C. Terminate the Apache ODE Project
WHEREAS, the Project Management Committee of the Apache ODE 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 ODE project due to inactivity;
NOW, THEREFORE, BE IT RESOLVED, that the Apache ODE 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 ODE Project; and be it further
RESOLVED, that the office of "Vice President, Apache ODE" is hereby
terminated; and be it further
RESOLVED, that the Apache ODE PMC is hereby terminated.
Special Order 7C, Terminate the Apache ODE Project, was
approved by Unanimous Vote of the directors present.
8. Discussion Items
A. Incubator DISCLAIMER-WIP
The Incubator proposes to make use of a new DISCLAIMER-WIP that
addresses non-compliant releases.
The IPMC can allow non-compliant releases to be distributed without
IPMC VP or legal VP approval, based on a documented list of issues
which are acceptable for such non-compliant incubating releases. Such
releases will include an alternative "work in progress" DISCLAIMER-WIP
to make users aware of the issues . When this occurs, podlings
document the issues as blocking graduation and carry on incubating.
They will not be allowed to graduate until all such release issues
have been fixed.
The board informally considers this a great idea.
9. Review Outstanding Action Items
* Rich: open up attic discussions to dev list
[ Forrest 2019-05-15 ]
Status: Done: thread started.
* 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:
* Rich: propose new PMC chair due to consistently late reports
[ TomEE 2019-05-15 ]
Status:
* Tom: research what other nonprofits do for CoCs for boards
[ Statement of Expectation of Conduct of Board Members 2019-05-15 ]
Status:
* Daniel: begin a discussion on the lists about this
[ Publishing of vote records 2019-05-15 ]
Status:
* Roman: create a framework of vote meanings
[ Convention of semantics of Board votes 2019-05-15 ]
Status:
* Roman: pursue a report for Bloodhound
[ Bloodhound 2019-06-19 ]
Status:
* Craig: work with IPMC to clarify podling release policy
[ Incubator 2019-06-19 ]
Status: https://issues.apache.org/jira/browse/LEGAL-469
https://cwiki.apache.org/confluence/display/INCUBATOR/New+Incubator+Disclaimer
Done unless new feedback is received
* Shane: pursue a report for Lucene.Net
[ Lucene.Net 2019-06-19 ]
Status: Done, submitted (and nicely written report too)
* Rich: pursue a roll call for Joshua
[ Joshua 2019-06-19 ]
Status:
* Ted: follow up about trademark issue in Sling
[ Sling 2019-06-19 ]
Status: Community is making progress
* Myrle: Follow up with ODE PMC about options regarding rebooting the project
[ Action Items 2019-06-19 ]
Status: ODE PMC has decided to move to attic.
* Roman: Discuss metagovernance of VPs
[ President 2019-07-17 ]
Status:
* Daniel: Check in on treasurer availability
[ Treasurer 2019-07-17 ]
Status: Still waiting on me...
* Danny: Document the data privacy needs of the organization.
[ Data Privacy 2019-07-17 ]
Status: On going. Will revert in September board report.
* Danny: pursue a roll call for Apex
[ Apex 2019-07-17 ]
Status: Apex have initiated an Attic vote. I will follow up with this
for next month.
* Rich: Follow up about release vote concerns
[ Arrow 2019-07-17 ]
Status:
* Rich: pursue a report for Avro
[ Avro 2019-07-17 ]
Status: Done: Report submitted for August.
* Myrle: Look into getting a better report
[ Griffin 2019-07-17 ]
Status: I believe the current report meets the necessary standards.
* Craig: pursue a roll call for Mesos
[ Mesos 2019-07-17 ]
Status:
* Daniel: Reach out for choice on rebooting or atticing the project
[ ODE 2019-07-17 ]
Status: Complete: it was determined to send the project to the attic
* Joan: pursue a report for Tapestry
[ Tapestry 2019-07-17 ]
Status: Pushed to next month
* Daniel: pursue a roll call for Tcl
[ Tcl 2019-07-17 ]
Status:
* Myrle: Pursue a roll call for Archiva
[ Archiva 2019-07-17 ]
Status:
10. Unfinished Business
11. New Business
12. Announcements
13. Adjournment
Adjourned at 11:29 a.m. (Pacific)
============
ATTACHMENTS:
============
-----------------------------------------
Attachment 1: Report from the VP of Brand Management [Mark Thomas]
* ISSUES FOR THE BOARD
None.
* OPERATIONS
Covering the period July 2019
Responded to the following queries, liaising with projects as required:
- Provided advice for a company wishing to use project logos in a UI.
- Reviewed http://openwhisk.incubator.apache.org/trademarks.html
- Referred a request for co-branded stickers using the APACHE logo to press and
marketing.
- Approved a request to use the FLINK mark for an event, highlighting the
relatively new requirement for an anti-harassment policy.
* REGISTRATIONS
Directed counsel to renew OPENOFFICE.ORG in India.
The IGNITE registration in the EU is now complete.
Directed counsel to file the 8&15 declaration for HAWQ in the US.
Directed counsel to file the 8&15 declaration for PREDICTIONIO in the US.
* INFRINGEMENTS
I was pleased to see the ACCUMULO PMC resolved an issue with a non-ASF
controlled website without assistance from Brand Management.
-----------------------------------------
Attachment 2: Report from the VP of Fundraising [Daniel Ruggeri]
Fundraising business is operating smoothly. We are pleased to welcome 1 new
Silver and 2 new Bronze foundation sponsors this month. We also renewed 1
Platinum, 2 Silver, and 3 Bronze sponsors. Work continues consolidating terms
of a combined (ASF + Targeted) Platinum sponsorship.
The previously reported email issues with a sponsor in China have been
resolved. They have renewed their sponsorship and are also becoming an
ApacheCon sponsor, and are in the final stages of document signature.
Restructuring continues, with updated records, new forms, and online account
maintenance. The online form-based onboarding is working well and new sponsor
agreements and renewals are successfully being processed using DocuSign.
We are continuing to work with Virtual to sign on new sponsors for
ApacheCon/Las Vegas, and continue working with new thinking/Plain Schwarz on
bolstering their sponsor activities.
~$900 received from individual donors via Hopsie, which is not uncommon during
the holiday period.
We are using the publishing of the annual report as a prompt to engage
sponsors through our ambassadors.
-----------------------------------------
Attachment 3: Report from the VP of Marketing and Publicity [Sally Khudairi]
[REPORT] ASF Marketing & Publicity - August 2019
I. Budget: we are on budget and are on an accelerated schedule to support
three events in a month (ApacheCon North America, Huawei Connect, and
ApacheCon Europe). HALO Worldwide is supporting the overflow on expenses that
are unable to be covered by the M&P credit card (maximum limit): this includes
20th Anniversary promotional items and travel for select team members.
II. Cross-committee Liaison: Sally Khudairi continues to support ASF
Fundraising by engaging new sponsors (1 Silver), securing sponsorship renewals
(1 Platinum, 2 Silver, and 3 Bronze), signing and onboarding new sponsors, and
working on ApacheCon sponsorships. Work with ASF Conferences continues with
expanded activities for ApacheCon/Las Vegas in 4 weeks. The latest "Success
at Apache" post, “The Path To Berlin,” is live at https://s.apache.org/xqvbo
. The ASF FY2019 Annual Report has been published: press release
https://s.apache.org/w7bw1 full report at
https://s.apache.org/FY2019AnnualReport
III. Press Releases: there were no formal announcements issued via the
newswire service, ASF Foundation Blog, or announce@apache.org during this
timeframe.
IV. Informal Announcements: 5 items were published on the ASF "Foundation"
Blog. 4 Apache News Round-ups were issued, with a total of 264 weekly
summaries published to date. We tweeted 20 items to 54.2K followers on
Twitter. We posted 4 items on LinkedIn, which garnered more than 31K organic
impressions. Sally was on medical leave for most of July; special thanks to
Swapnil Mane for stepping up to publish the Apache Weekly News Round-ups
during this time, and for his commitment to publish future newsletters on a
weekly basis. Thanks also to Daniel Gruno for supporting the effort and
facilitating the publishing process.
V. Future Announcements: 3 announcements are in development. Projects planning
to graduate from the Apache Incubator as well as PMCs wishing to announce
major project milestones and "Did You Know?" success stories are requested to
contact Sally at <press@apache.org> with at least 2-weeks' notice for proper
planning and execution.
VI. Media Relations: we responded to 3 media queries. The ASF received 1,919
press clips vs. last month's clip count of 865. Media coverage of Apache
projects yielded 3,104 press hits vs. last month's 2,130. ApacheCon received
97 press hits. We will be offering Intermediate Media & Analyst Training
during ApacheCon, and will be offering the Beginner session online for any
Apache Committer to take at their convenience. This will help offset the
year-round demand for the training materials and to help folks unable to
attend or wait for the next ApacheCon to get started.
VII. Analyst Relations: we received one analyst query. Apache was mentioned in
1 report by Gartner; 2 reports by Forrester; 5 reports by 451 Research; and 5
reports by IDC.
VIII. Graphics: members of the new Central Services sub-group under Marketing
& Publicity are successfully collaborating on the development of new creative
assets to promote the ASF and ApacheCon, and are developing plans/processes
for new projects. We launched the new #LoveApache badge for third parties to
include their logos/images with the Apache brand for stickers and online
applications http://apache.org/foundation/press/kit/#badges . We reached out
to the Open Source Design community for possible future collaboration and
Kenneth Paskett from Central Services will be meeting them during ApacheCon
Europe.
IX. Events liaison: we continue to work closely with Virtual and
newthinking/Plain Schwarz on various advisory and tactical support across
ApacheCon/Las Vegas and Berlin. This includes ASF 20th Anniversary projects
taking place onsite, such as the Peter Adams “Apache: Community Over Code.
Code Over Community” photography project in Las Vegas as well as the
“Trillions and Trillions Served” documentary being filmed in both Las Vegas
and Berlin. New ApacheCon promotions are being posted on Feathercast, with
transcripts published on blogs.apache.org, and will feature the same for
ApacheCon Europe keynoters. We posted 3 items on the ASF Events/ApacheCon
pages on LinkedIn, and the event producers have been very active in promoting
the talks for both events. Sally continues to work closely with ASF VP
Conferences Rich Bowen, and has scaled back day-to-day tactics with event
sponsorship. She is also overseeing Sponsor Ambassador activities and the
ASF’s presence at upcoming events including, Cumbre/CCOSS (September), and
Huawei Direct (September). In addition, for the first time, as part of
Central Services’ “Education and Outreach” activity, we are offering a new
immersive session on how to host an "Apache@" event at corporate locations.
Originally offered as a benefit for ASF Sponsors only, ASF Members and PMC
members are invited to participate and learn best practices to help corporate
teams succeed when contributing to Apache projects.
X. Newswire accounts: our pre-paid press release package with GlobeNewswire
has auto-renewed 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
==========
We experienced email delivery issues for a couple days due to a
misconfiguration on our server. That was corrected, and a variant
appeared some days later. This would not normally be an issue to
highlight to the Board, but in this case it affected our delivery to
Virtual Inc, our service provider for finances, fundraising, and
conferences. These three topics are particularly acute leading into
ACNA19 next month. Our apologies to Virtual, in specific.
Infra has coded up some special warning systems to detect similar
problems in the future, and applied additional monitoring should this
scenario reoccur under any other adverse condition.
Second: we completed the datacenter exit mentioned last month. This
occupied the team's highest priority for much of July.
Short Term Priorities
=====================
- Migrate and upgrade Jira on Sunday, August 18th (should be finished
before the Board's meeting).
- Warm up a new IP address for outbound email. This includes an
improved email system configuration for reliability, and to avoid
future delivery problems noted in our Highlights.
- Restart our process to hire a Technical Writer/Editor.
- ApacheCon North America, in Las Vegas.
- Move svn-master.a.o onto a modern VM (18.04/p6).
Long Range Priorities
=====================
- Deprecate the old Content Management System (cms.apache) that is
running on old hardware, and unmaintained software. We are exploring
"turnkey website publishing" for the Foundation's projects.
General Activity
================
- Moved our primary backup server off a failing machine onto newer
hardware with more storage, at a lower cost.
- Many migrations from our old datacenter, primarily into Hetzner. At
the same time, we upgraded to 18.04/p6.
- Completed the migration of moin wiki content over to Confluence,
enabling us to turn off MoinMoin and its host machine.
- Improvements in our account creation tooling, along with some LDAP-y
goodness in our Python support library.
- Lots of work on our underlying email systems, towards our migration
to a modern, fully-puppetized system (and away from our old FreeBSD
setup that is difficult to maintain).
- Lifting our runbooks off reference.a.o onto cwiki, and refining them
to modern-day actuals. ref.a.o is deprecated.
- Moving off our own SonarQube installation to SonarCloud (a
complementary service for F/OSS projects)
- Fixing up the fingerprint system on www.a.o/dev/machines.html
-----------------------------------------
Attachment 5: Report from the VP of Conferences [Rich Bowen]
Conferences
ACNA 19
Nothing much to report, other than that everything is coming together for the
event, which is now less than a month out. Registration is clipping along,
although it may fall a little short of our goals. Sponsorship is strong, and
our final promotion efforts are running. See you in Las Vegas!
ACEU 19
Organization continues apace. Despite this being vacation time in Europe,
NewThinking continues to work hard providing visas for speakers, finalizing
organization of details like the speaker dinner, and etc. We are in the
process of organizing space and food for the Movie Night, and finding a room
for the filming crew. We’ve received confirmation from all but one of our
invited speakers. We are holding two speaking slots open for potential
sponsors, but will need to send notification to our waitlisted speakers soon.
The attendees of the Founder’s panel also remain uncertain.
We are currently up to 4 accredited press attendees: Heise, Linux Magazine,
Deutschland Funk, and D-Zone. Press work to promote attendance has been
extensive, including local and international news organizations, event
calendars, and social media engagement both directly by us and via our
partners.
We need an organizer for the Hackathon in ACEU to send out an invitation to
the communities attending.
-----------------------------------------
Attachment 6: Report from the Apache Travel Assistance Committee [Gavin McDonald]
ApacheCon NA Las Vegas
======================
Behind the scenes work is proceeding, booking flights etc. All Hotel rooms are
confirmed booked, and Conference passes should all be registered.
ApacheCon EU Berlin
===================
Judging completed, and we accepted 17 of 49 applicants. Work is under way to
get their flights done from a new Travel Agent (to us) local to Berlin. Hotel
rooms are all booked. Conference passes to be handed out.
(Chris informs that all flights are now booked!)
General
=======
With a new lead organiser for Berlin, and Chris going through the process for
the first time, some Tribal Knowledge and holes in our TAC internal
documentation were revealed; and, ultimately fixed.
TAC Membership
==============
No changes in the TAC Membership.
Mailing List
============
We currently have 20 subscribers to our main list.
Not much in the way of list activity other than the list being kept upto date
on progress.
-----------------------------------------
Attachment 7: Report from the VP of Finance [Tom Pappas]
VP of Finance report July 2019 performed worked on the following:
- Renewing the ASF Director and Officers Insurance
- Obtaining a $2 million Event and Liquor insurance policy for ACNA19
that includes a Terrorism clause
- Worked with the Fundraising team on a number of sponsors both
Foundation and ACNA related
-----------------------------------------
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***
Vetted 8 potential vendors, got quotes from 3 finalist and decided to move
forward into negotiation of deliverables with one: Bitergia. See JIRAs [1][2]
for complete context on vendor selection.
*** Project: UX Research on new contributors ***
Vetted 3 potential vendors, decided to move forward into negotiation with
Bitergia in a joint project to do the Contributor survey + User Experience
research.
*** 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 registered ASF with Outreachy [6]. Listed the sponsors [7]. We setup
communication tools (Jira, Confluence etc.) for D&I to communicate with each
other and communicate progress of initiatives. Created two project trackers:
“Outreachy Program Setup” to monitor the implementation of the program due to
the first time collaborating with the Outreachy Program, and “Outreachy
Internship Tracking” to monitor the schedule and onboarding actions [8]. We
schedule two calls with Mozilla to get information about the templates: July
18th and August 6th. We have created Apache labels for Outreachy in JIRA [9].
We created the outreachy mentors mailing list mentor@diversity.apache.org
[10]. We are working in a blog post [11]. We will send a call for mentor
e-mail to the announcements lists on the 17th of August, almost a week ahead
of the official launch of the initial applications [12].
More detailed reports on this work can be found on their update minutes[3].
*** Operations ***
Nothing to report.
*** Community Highlights ***
We have successfully set up the ASF as an Outreachy community, progress with
this program seems to be going smooth, and it gave a new community member the
opportunity to engage in an important project for the committee.
Discussions to find a vendor for the diagnosis work (survey & research)
started interesting connections with people in the CHAOSS community and
thought leasders in the topic of diversity and inclusion.
## Health report:
Update on Diversity & Inclusion mailing lists moderation: From the events that
occurred last month in the D&I mailing list, 4 components of a strong
moderation practice were outlined:
>Successful moderation requires at least a few things:
>
> 1. a clear, short list of rules people must follow
> 2. reasons provided to the poster on violation
> 3. a stated appeals process
> 4. consistent application of those rules
The committee has brought an initial draft of these guidelines to a Confluence
page[4] and feedback has been provided on an email thread in dev@[5]. Thanks
to everyone who has provided input.
Next steps are: Finalize moderation guidelines and publish them in D&I wiki,
and establish a process for appeals. We’ll work on these two points next.
Update on mailing lists status: We are back to normal cadence and volume. Work
in the three main projects for 2019 has started to show progress and tone and
interaction has re focused on core work.
## Committee members changes:
1 new member added to the committee
References
[1] https://issues.apache.org/jira/projects/DI/issues/DI-9?filter=allopenissues
[2] https://issues.apache.org/jira/projects/DI/issues/DI-10?filter=allopenissues
[3]https://lists.apache.org/thread.html/c415b7e47d3a989b4a510bb5a015fe54890fe7474e2a9fa0c2ad1abf@%3Cdev.diversity.apache.org%3E
[4] https://cwiki.apache.org/confluence/display/EDI/Draft+moderation+guidelines
[5]https://lists.apache.org/thread.html/2cd7f831c869a69644a5c681a2c8ca8d8df31737cfe96ebc2e6f1662@%3Cdev.diversity.apache.org%3E
[6] https://issues.apache.org/jira/browse/DI-17
[7] https://issues.apache.org/jira/browse/DI-18
[8] https://issues.apache.org/jira/browse/DI-22
[9] https://issues.apache.org/jira/browse/DI-20
[10] https://issues.apache.org/jira/browse/DI-21
[11] https://issues.apache.org/jira/browse/DI-19
[12] https://issues.apache.org/jira/browse/DI-26
-----------------------------------------
Attachment 9: Report from the VP of W3C Relations [Andy Seaborne]
-----------------------------------------
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 1 to 22, unresolved
issues this month.
We have finally submitted Legal sections of the ASF annual report.
We have finalized our recommendations for how ASF may decide to engage with
Eclipse Jakarta EE Platform.
We continue to evaluate additional options for counsel to augment the work of
DLA Piper. We expect to have an update on this in a month or two. Mishi
Choudhary from SFLC is looking into refreshing the relationship with us. In
additional to that we also had Cliff Allen reaching out offering his help.
-----------------------------------------
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.
Some of the security team will be presents at ApacheCon NA and running
a BoF https://www.apachecon.com/acna19/s/#/scheduledEvent/1337
Stats for July 2019:
12 [license confusion]
14 [support request/question not security notification]
Security reports: 26 (last months: 23, 44, 29, 39)
7 [ambari]
4 [httpd]
3 [infrastructure], [site]
2 [tika], [tomcat]
1 [geode], [hadoop], [ranger], [spark], [thrift]
In total, as of 1st August 2019, we're tracking 66 (last month:
64) open issues across 33 projects, median age 111 (last month:
120) days. 46 of those issues have CVE names assigned.
7 (last month: 8) of these issues, across 4 projects, are older
than 365 days.
-----------------------------------------
Attachment 12: Report from the VP of Data Privacy [John Kinsella]
There has been no report from the VP.
Activity: I have kicked off call for volunteers on board@ and reached out to
incumbent VP today 21-Aug
Next steps: Engage volunteers and agree definition of done, define next
steps/mechanism to clarify the role, report back to the board.
danny@
-----------------------------------------
Attachment 13: Report from the VP of Jakarta EE Relations [Mark Struberg]
-----------------------------------------
Attachment A: Report from the Apache Ambari Project [Jayush Luniya]
## Description:
- Apache Ambari simplifies provisioning, managing, and monitoring of
Apache Hadoop clusters.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- The community is actively working on an Apache Ambari 2.7.4 maintenance
release.
## Health report:
- The development community and engagement remains strong, however few
committers and PMC members have moved to other projects. We have 105
committers and 48 PMC members on the project.
## PMC changes:
- Currently 48 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Ishan Bhatt on Thu Oct 25 2018
## Committer base changes:
- Currently 105 committers.
- No new committers added in the last 3 months
- Last committer addition was Amarnathreddy Pappu at Sat Apr 13 2019
## Releases:
- Last release was 2.7.3 on Fri Nov 16 2018
## Mailing list activity:
- Apache Ambari has moved from ReviewBoard to GitBox for code reviews and
hence there is no activity on reviews@ambari.apache.org
- dev@ambari.apache.org:
- 304 subscribers (up 0 in the last 3 months):
- 0 emails sent to list (1 in previous quarter)
- issues@ambari.apache.org:
- 41 subscribers (down -7 in the last 3 months):
- 468 emails sent to list (883 in previous quarter)
- reviews@ambari.apache.org:
- 61 subscribers (up 0 in the last 3 months):
- 0 emails sent to list (0 in previous quarter)
- user@ambari.apache.org:
- 441 subscribers (down -33 in the last 3 months):
- 6 emails sent to list (5 in previous quarter)
## JIRA activity:
- 78 JIRA tickets created in the last 3 months
- 88 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment B: Report from the Apache Ant Project [Jan Materne]
## Description:
Apache Ant is a Java based build tool along with associated tools.
It consists of 3 main projects:
- Ant - core and libraries (AntLibs)
- Ivy - Ant based dependency manager
- IvyDE - Eclipse plugin to integrate Ivy into Eclipse
Additionally Ant provides several extensions to Ant (antlibs).
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- We are now on https://snapcraft.io/ant and intend to publish convenience
builds of upcoming releases there as well.
- Migrated Wiki to Confluence
- Started migrating Sonar to SonarCloud.io
## Health report:
For Ant we feel healthy enough to apply patches, and get a release done.
But basically we are in "maintenance mode". There isn't much development.
## PMC changes:
- Currently 23 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Magesh Umasankar on Fri Jul 06 2018
## Committer base changes:
- Currently 29 committers.
- No new committers added in the last 3 months
- Last committer addition was Jaikiran Pai at Wed Jun 14 2017
## Releases:
- Last release was Ant 1.10.6 on Wed May 08 2019
-----------------------------------------
Attachment C: Report from the Apache Apex Project [Thomas Weise]
## Description:
Apache Apex is a distributed, large-scale, high-throughput, low-latency, fault
tolerant, unified stream and batch processing platform.
## Issues:
The project is practically dormant and attic vote has been initiated. PMC
failed to get nomination for new chair on the way since April report.
## Membership Data:
Apache Apex was founded 2016-04-19 (3 years ago)
There are currently 41 committers and 17 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 Chinmay Kolhatkar on 2018-05-15.
- No new committers. Last addition was Ananth Gundabattula on 2017-10-19.
## Project Activity:
No real activity in the project. Following are the most recent releases:
- Core 3.7.0 released 2018-04-19
- Malhar 3.8.0 released 2017-11-12
## Community Health:
Commit activity has been zero for several reporting periods. No new or active
contributors. No indication of user interest.
-----------------------------------------
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.
Apache Archiva software is an extensible repository management tool that
helps taking care of your own personal or enterprise-wide build artifact
repository.
## Issues:
There are no issues requiring board attention at this time
## 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:
Low activity. We are currently working:
- Java upgrade (fix some issues running with Java11)
- refactor Artifact storage to be able to support
more artifact format (npm, docker etc..)
## Community Health:
We have enough PMC to cut release. Activity is low during summer.
Project activity have some details.
-----------------------------------------
Attachment E: Report from the Apache Avro Project [Thiruvalluvan M. G.]
August 2019
Apache Avro is a data serialization system with a compact binary format. It is
used for storing and transporting schema driven serialized data. The unique
features of Avro include automatic schema resolution - when the reader's
expected schema is different from the actual schema with which the data was
serialized the data is automatically adapted to meet reader's requirements.
This report is for the four months ending Jul 31 2019 (previous report covered
until Mar 31)
Activity
65 JIRA tickets opened by 25 developers
103 Pull requests opened in Github
90 issues resolved by 25 contributors
84 Pull requests merged
45 pull requests pending
Last release: version 1.9.0 16th May 2019.
Last time a new committer elected: 27 June 2019, Michael A. Smith
Last time a new PMC elected: 14 May2019, Ismael Mejia
Finally, after a gap of two years, we managed to release a new version 1.9.0.
It was well received with a lot of feedback from the community. Kudos to the
new members of PMC and committers who worked hard to get this out.
-----------------------------------------
Attachment F: Report from the Apache BookKeeper Project [Sijie Guo]
## Description:
BookKeeper is a scalable, fault-tolerant, and low-latency storage
service optimized for append-only workloads. It has been used as
a fundamental service to build high available and replicated services
in companies like Twitter, Yahoo and Salesforce. It is also the log
segment store for Apache DistributedLog and message store for Apache Pulsar.
Apache DistributedLog is a high-level API and service layer for
Apache BookKeeper, providing easier access to the BookKeeper
primitives. It is a subproject of Apache BookKeeper.
## Issues:
There are no issues requiring board attention at this time.
## Membership Data:
Apache BookKeeper was founded 2014-11-19 (5 years ago)
There are currently 21 committers and 16 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:2.
Community changes, past quarter:
- Charan Reddy G was added to the PMC on 2019-07-24
- No new committers. Last addition was Andrey Yegorov on 2018-02-10.
## Project Activity:
Recent releases:
4.9.2 was released on 2019-05-17.
4.9.1 was released on 2019-04-06.
4.8.2 was released on 2019-03-18.
4.8.0 was released on 2018-09-25.
Currently the community is working on releasing 4.10.0.
The two releases will be going out soon.
## Community Health:
The community is a bit slow. Because the committers and
PMC members have a bit overlapped between Pulsar and BookKeeper.
So a lot of them have been focused on growing the adoptions of
Pulsar and hence BookKeeper. The adoptions of Pulsar has been
increased a lot and so does BookKeeper. The members are able to
put more focuses on BookKeeper in the next month.
-----------------------------------------
Attachment G: Report from the Apache Brooklyn Project [Geoff Macartney]
## Description:
- Apache Brooklyn is a software framework for modelling, monitoring and
managing cloud applications through autonomic blueprints.
## Issues:
- there are no issues requiring board attention at this time
## Membership Data:
- Apache Brooklyn was founded 2015-11-18 (4 years ago)
- There are currently 16 committers and 16 PMC members in this project.
- The Committer-to-PMC ratio is 1:1.
Community changes, past quarter:
- No new PMC members. Last addition was Duncan Grant on 2018-08-30.
- No new committers. Last addition was Duncan Grant on 2018-06-13.
## Project Activity:
- Brooklyn is quite stable at present, with a low level of development
activity. Discussions and assistance to users continues on the mailing
list.
## Releases:
- Last release was 1.0.0-M1 on Mon Sep 17 2018
## Community Health:
- The project continues with a small steady turnover of pull requests
and commits.
- We continue to monitor our community for potential new committers and PMC
members with the aim of regularly adding individuals.
- There has been further discussion over the summer about releasing Brooklyn
1.0.0, hopefully this will go ahead in the next month or two.
-----------------------------------------
Attachment H: Report from the Apache Buildr Project [Antoine Toulme]
## Description:
Apache Buildr is a build system for Java-based applications, including
support for Scala, Groovy and a growing number of JVM languages and
tools. We wanted something that’s simple and intuitive to use, so
we only need to tell it what to do, and it takes care of the rest.
But also something we can easily extend for those one-off tasks, with
a language that’s a joy to use. And of course, we wanted it to be
fast, reliable and have outstanding dependency management.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- We have released 1.5.8 in July. The project is still otherwise very quiet,
with some good patches helping keep up with maintenance.
## Health report:
- We still have a small PMC presence of 3 active members still able
to vote releases.
## PMC changes:
- Currently 7 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Peter Donald on Tue Oct 15 2013
## Committer base changes:
- Currently 10 committers.
- Olle Jonsson was added as a committer on Wed Dec 12 2018
## Releases:
- Last release was 1.5.8 on July 14th 2019
-----------------------------------------
Attachment I: Report from the Apache Cassandra Project [Nate McCall]
## Description:
The Apache Cassandra database is the right choice when you need scalability
and high availability without compromising performance. Linear scalability and
proven fault-tolerance on commodity hardware or cloud infrastructure make it
the perfect platform for mission-critical data. Cassandra's support for
replicating across multiple datacenters is best-in-class, providing lower
latency for your users and the peace of mind of knowing that you can survive
regional outages.
## Issues:
We have sent off a trademark violation to aiven.io and have not heard a
response after five days.
We have moved off of IRC onto the ASF's Slack Instance. This has (anecdotally
as we don't have exact numbers) driven a large uptick in active conversations
on both #cassandra and #cassandra-dev over their IRC counterparts.
## Membership Data:
Apache Cassandra was founded 2010-02-17 (9 years ago) There are currently 54
committers and 32 PMC members in this project. The Committer-to-PMC ratio is
roughly 7:4.
We have had no new committers added this quarter. We think this may be the
result of feature work being frozen and we are primarily focused on testing
for our upcoming 4.0 release. Given that last quarter saw the addition of
three committers, we do not see this as a negative for the project's health.
Community changes, past quarter:
- No new PMC members. Last addition was Alex Petrov on 2019-04-09.
- No new committers. Last addition was Dinesh Joshi on 2019-03-05.
## Project Activity:
We are eagerly anticipating this year's ApacheConNA as we have expanded our
track to three days.
We have been assigned a doc writer through Google Season
of Docs and will begin working with them on our outstanding documentation
projects shortly.
## Community Health:
We are continue to track and prioritize issues as we approach 4.0:
https://cwiki.apache.org/confluence/display/CASSANDRA/4.0%3A+Open+Issues+by+Component
Interesting statistics this quarter:
- dev@cassandra.apache.org had a 39% decrease in traffic in the past quarter
(133 emails compared to 217)
- 84 issues closed in JIRA, past quarter (35% increase)
- 66 commits in the past quarter (17% increase)
The dip in development list activity could be a result of the increased
participation in our slack channel. We have both an increase in the number of
commits and the number of closed issues for this quarter, so overall the
numbers seem healthy.
-----------------------------------------
Attachment J: Report from the Apache Clerezza Project [Hasan Hasan]
DESCRIPTION
Apache Clerezza models the RDF abstract syntax in Java and provides supports
for serializing, parsing, managing and querying triple collections (graphs).
Apache Clerezza modules aim at supporting the development of Semantic Web
applications and services.
ISSUES FOR THE BOARD
There are no issues requiring board attention at this time.
RELEASE
Latest release was created on May 13, 2016.
A new release is targeted in Q3 2019.
ACTIVITY
Further refactoring of the Apache Clerezza codes to improve the structure
of the API and its implementation has been made. The pull request of the
newly refactored Apache Clerezza codes has been applied to the master branch.
Reto or Hasan is going to create a release candidate.
COMMUNITY
Latest change was addition of a new committer and PMC member on 27.12.2018
INFRASTRUCTURE
Latest update of the Apache Clerezza Website was in February 2018.
-----------------------------------------
Attachment K: Report from the Apache Cocoon Project [Cédric Damioli]
## Description:
Web development framework: separation of concerns, component-based.
## Issues:
there are no issues requiring board attention at this time
## Activity:
Still very few activity on the project. Last report was followed by the board
questioning us being somewhat dormant. As usual, this question is actually
fair regarding the activity, and as usual, many PMC members (8 IIRC) answered
they're still there. The most recent release is 2.1.12 on 2013-03-14 A few
JIRA issues opened or resolved since last report. A little activity on both
users and dev mailing-lists, even if still at a low level. The project is
mainly in maintenance mode.
## PMC changes:
None. Most recent addition: 2012-07-06
## Committer base changes:
None. Most recent addition: 2012-07-06
-----------------------------------------
Attachment L: Report from the Apache Community Development Project [Sharan Foga]
## Description:
The mission of Community Development is the creation and maintenance of
software related to Resources to help people become involved with Apache
projects
## Issues:
- No issues require board attention at the moment
## Membership Data:
Apache Community Development was founded 2009-11-01 (10 years ago) There are
currently 33 committers and 31 PMC members in this project. The
Committer-to-PMC ratio is roughly 9:8.
Community changes, past quarter:
- Christofer Dutz was added to the PMC on 2019-06-21
- Christofer Dutz was added as committer on 2019-06-21
## Project Activity:
Diversity & Inclusion With the establishment of the separate D&I mailing list,
discussions and topics related to D&I have been moved to that list.
Apachecon
We have been busy helping support Apachecon NA and EU. We are
organising the Apache booth and have called for volunteers from our community.
Several people from various projects have offered to spend time on the booth
others about their projects.
We are also ordering giveaways and stickers for the boot and have had an
amazing response from our communities wanting have some of their own stickers
available. Due to the demand, we are preparing an additional sticker order.
Redbubble
The Redbubble store was setup in April 2018 as an easy way for ASF
projects to order their own branded item such as t+shirts, mugs, etc. In
preparation for Apachecon many projects have asked to have their logos added
to the store so they can buy their own merchandise and promote their projects
visually.
Some additional volunteers have offered to help Mark Thomas who has been the
main administrator for the Redbubble site and a training session is planned.
Community Track NA & EU
The CFP for both Apachecons provided a lot of
submissions around community related topics. As a result we have a 3 day
Community track at Apachecon NA and a 2 day Community track at Apachecon EU.
To help promote our track a Feathercast interview [1] and blog post has been
published.
GSoC
GSoC is coming to an end and the final evaluations will start next week.
We are currently deciding who to send to the mentor summit in Germany.
Events We are still investigating opportunities for Apache Roadshows in 2020
including the possibility of one in India. We have also been invited to
participate with an Apache track in CCOSS 2019 [2] in Mexico
## Community Health:
Mailing list traffic has decreased this quarter probably due to the holiday
season. dev@community.apache.org:
- 884 subscribers (down -7 in the last 3 months):
- 545 emails sent to list (763 in previous quarter)
We are starting to track some task via Jira so this has increased activity
this quarter.
- 8 JIRA tickets created in the last 3 months
- 7 JIRA tickets closed/resolved in the last 3 months
[1] https://s.apache.org/lt4a8
[2] https://ccoss.org/
-----------------------------------------
Attachment M: Report from the Apache CouchDB Project [Jan Lehnardt]
## Description:
Seamless multi-master sync, that scales from Big Data to Mobile,
with an Intuitive HTTP/JSON API and designed for Reliability.
## Issues:
There are no issues requiring board attention
## Membership Data:
Apache CouchDB was founded 2008-11-19 (11 years ago)
There are currently 64 committers and 15 PMC members in this project.
The Committer-to-PMC ratio is roughly 4:1.
Community changes, past quarter:
- No new PMC members. Last addition was Nick Vatamaniuc on 2017-11-07.
- No new committers. Last addition was Jay Doane on 2019-01-05.
## Project Activity:
The Vote[1] to adopt FoundationDB as CouchDB’s future underlying distribution
and storage technology has passed unanimously.
See the two previous board reports for more context.
Current planning includes both a CouchDB 3.0 and a CouchDB 4.0 milestone. 3.0
will include the best version of the current, mostly Erlang-based project,
with many new features contributed by various project partners (but notably
IBM). This will be the LTS version for people who won’t be able to migrate to
the newer technology foundation. There are a number of technical limitations
that we are happy to adopt as a project going forward, but that might be deal-
breakers for some users. As such, we’ll serve those users best with an excellent
edition of the original technology stack. LTS-timelines are TBD.
CouchDB 4.0 which is already under development concurrently will include a
mostly[tm] API compatible version of CouchDB built on top of FoundationDB. API
differences are going to be communicated clearly and migration paths documented
thoroughly.
For a little bit of context: with the addition of clustering, CouchDB 2.x turned
from an accidentally strongly consistent database (because it was a single-node
database) to an eventually consistent database, losing some essential properties
in favour of scalability and fault tolerance.
With the help of FoundationDB, those properties lost after 1.x are going to be
regained, while retaining scalability and fault tolerance, and while putting the
CouchDB foundational underpinnings on a modern distributed database stack that
would easily take us 10+ years to build.
IBM is spearheading this effort within the ASF and is adding more resources to
the CouchDB project in terms of development, release management, infrastructure
as well as project management
[1]: https://s.apache.org/couchdb-fib-vote
## Community Health:
All parts of the existing community are participating in the 3.x and 4.x
efforts. While no new committer-candidates have emerged yet, there is a small
influx of new and promising voices.
-----------------------------------------
Attachment N: Report from the Apache Creadur Project [Brian E Fox]
Same as the off cycle report last month:
Apache Creadur creates and maintains a suite of open source software
related to the auditing and comprehension of software distributions.
Any language and build system are welcomed.
Status
------
Creadur is primarily used by other Apache projects to help check for
conformity to ASF standards. This is why the project team is primarily
comprised of members and committers from other ASF projects. The risk
of the project foundering is therefore very low despite the ongoing
lack of progress.
If someone has an itch to scratch, it will no doubt get fixed.
Community
---------
In September 2016 Karl Heinz Marbaise was elected to join the PMC /
Commit.
Releases
--------
Apache Rat 0.13 was released Nov 5th, 2018
Apache Rat 0.12 was released in June 2016
Apache Rat 0.11 was released in August, 2014
Apache Rat 0.10 was released in September, 2013
-----------------------------------------
Attachment O: Report from the Apache DeltaSpike Project [Mark Struberg]
-----------------------------------------
Attachment P: Report from the Apache DRAT Project [Tom Barber]
## Description:
- Apache DRAT is a distributed, parallelized (Map Reduce) wrapper around
Apache RAT™ and other code auditing tools to allow it to complete on large
code repositories of multiple file types.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- There has been some work on DRAT in this reporting period. It is currently
waiting for the next OODT release so it can hit its own 1.0 release. There
has also been additional community involvement with UI fixes and
enhancements these are due for submission to the main codebase shortly.
## Health report:
- Slow pace of development, but functioning PMC and look to get 1.0 released.
## PMC changes:
- Currently 14 PMC members.
- Ahmed Ifhaam was added to the PMC on Thu Aug 30 2018
## Committer base changes:
- Currently 14 committers.
- Ahmed Ifhaam was added as a committer on Tue Aug 28 2018
## Releases:
- Work is ongoing to ready a 1.0 release
## Mailing list activity:
- Mailing list activity was pretty flat, but expected
- dev@drat.apache.org:
- 16 subscribers (down -1 in the last 3 months):
- 0 emails sent to list (50 in previous quarter)
- issues@drat.apache.org:
- 10 subscribers (up 0 in the last 3 months)
-----------------------------------------
Attachment Q: Report from the Apache Drill Project [Arina Ielchiieva]
## Description:
- Drill is a Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud
Storage.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- Drill User Meetup was held on May 22, 2019.
- Drill 1.17.0 release is planned in the end of August / beginning of
September.
## Health report:
- Development activity is almost 50% down due to acquisition of one of the
main Drill vendors.
- Activity on the dev and user mailing lists is slightly down compared to
previous periods.
- Four committers were added in the last period.
## PMC changes:
- Currently 24 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Sorabh Hamirwasia on Fri Apr 05 2019
## Committer base changes:
- Currently 55 committers.
- New commmitters:
- Anton Gozhiy was added as a committer on Mon Jul 22 2019
- Bohdan Kazydub was added as a committer on Mon Jul 15 2019
- Igor Guzenko was added as a committer on Mon Jul 22 2019
- Venkata Jyothsna Donapati was added as a committer on Mon May 13 2019
## Releases:
- Last release was 1.16.0 on Thu May 02 2019
## Mailing list activity:
- dev@drill.apache.org:
- 403 subscribers (down -5 in the last 3 months):
- 1156 emails sent to list (2222 in previous quarter)
- issues@drill.apache.org:
- 17 subscribers (up 0 in the last 3 months):
- 1496 emails sent to list (2315 in previous quarter)
- user@drill.apache.org:
- 575 subscribers (down -6 in the last 3 months):
- 157 emails sent to list (230 in previous quarter)
## JIRA activity:
- 96 JIRA tickets created in the last 3 months
- 68 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment R: Report from the Apache Dubbo Project [Ian Luo]
## Description:
- Apache Dubbo is a high-performance, lightweight, java based RPC framework.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- Apache Dubbo Developer Day Shenzhen was held on 2019-07-20, which is by far
the event with most attendees. There was 900+ registration, 9k+ live
watches, 400+ attendees. It was such a great success.
- Apache Dubbo Developer Day Shanghai will be held on 2019-08-17. The
schedule has been annouced.
- Projects under dubbo group that not transferred to ASF have been
transferred to thubbo group. There is only one project left in dubbo group,
which is dubbo.github.io. The Dubbo community is still working with ASF
trademarks/legal in order to transfer dubbo.io to ASF. A
"Domain Name Assignment" has been drafted and being reviewed by ASF
trademarks/legal.
- dubbo-go-hessian2 project has been accepted by communitity. After finishing
the IP clearance, it has been successfully transferred to ASF.
- The Github metric "Used by" of Dubbo has reached 1k, which is good metric
to indicate the penetration of a frameowrk.
- The Dubbo community works with JProfiler to provide free license for
committers.
## Health report:
- The overall status of Dubbo community is good.
## PMC changes:
- Currently 16 PMC members.
- Victory Cao was added to the PMC on Mon Jun 03 2019
## Committer base changes:
- Currently 43 committers.
- New commmitters:
- Xinming He was added as a committer on Mon Jul 15 2019
## Releases:
- Dubbo 2.7.3 has been released on 2019-7-19.
- Dubbo 2.6.7 has been released on 2019-7-19.
- dubbo-spring-boot-starter 2.7.3 finishes release vote on 2019-8-9.
- dubbo-go 1.0 is udner release vote.
## Mailing list activity:
- dev@dubbo.apache.org:
- 376 subscribers (up 70 in the last 3 months):
- 605 emails sent to list (963 in previous quarter)
## GitHub activity:
The Active and closed issues/pull request both have increased than last month.
- 103 Active Pull Requests, 30 merged pull request during the last 1 month
- 163 Active Issues, 105 closed issues during in the last 1 months
-----------------------------------------
Attachment S: Report from the Apache Empire-db Project [Rainer Döbele]
## Description:
- Apache Empire-db is a relational database access engine that takes an
SQL-centric approach in contrast to object-relational-mapping like with JPA
It encapsulates the functionality of a RDBMS in a powerful, vendor
independent, intuitive and maintenance friendly API providing a maximum of
compile-time-safety.
## Issues:
- there are no issues requiring board attention at this time.
## Activity:
- Recently development of the new version 2.5.0 has picked up steam and many
new issues for improvement have been created. With the upcoming release we
want to introduce more dramatic changes and want to improve both
consistency and intuitivity of the API.
## Health report:
- The project remains healthy.
## PMC changes:
- Currently 10 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Jan Glaubitz on Sun Jul 10 2016
## Committer base changes:
- Currently 9 committers.
- No new committers added in the last 3 months
- Last committer addition was Jan Glaubitz at Mon Oct 05 2015
## Releases:
- Last release was empire-db-2.4.7 on Wed Oct 31 2018
## Mailing list activity:
- dev@empire-db.apache.org:
- 31 subscribers (down -2 in the last 3 months):
- 43 emails sent to list (1 in previous quarter)
- user@empire-db.apache.org:
- 51 subscribers (up 0 in the last 3 months):
- 1 emails sent to list (1 in previous quarter)
## JIRA activity:
- 16 JIRA tickets created in the last 3 months
- 12 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment T: Report from the Apache Flume Project [Ferenc Szabo]
## Description:
The mission of Flume is the creation and maintenance of software related to A
reliable service for efficiently collecting, aggregating, and moving large
amounts of log data
## Issues:
There are no issues requiring board attention at this time.
## Membership Data:
Apache Flume was founded 2012-06-20 (7 years ago)
There are currently 31 committers and 24 PMC members in this project.
The Committer-to-PMC ratio is roughly 4:3.
Community changes, past quarter:
- No new PMC members. Last addition was Ferenc Szabo on 2019-01-28.
- No new committers. Last addition was Attila Simon on 2017-11-04.
## Project Activity:
- A few minor bugs and documentation fixes
- Work on 3rd party library updates should happen, after that, we can have
a new release
## Community Health:
- The contributions have slowed down recently
- A few new contributors appeared
-----------------------------------------
Attachment U: Report from the Apache Forrest Project [David Crossley]
Apache Forrest mission is software for generation of aggregated multi-channel
documentation maintaining a separation of content and presentation.
Issues needing board attention:
None.
Changes in the PMC membership:
None.
Last modified: 2013-04-08
Most recent addition: 2009-06-09
New committers:
None.
Most recent addition: 2009-06-09
None on the horizon.
General status:
The most recent release is 0.9 on 2011-02-07.
At this report, three other PMC members responded to my draft report.
This confirms that there are sufficient people hanging around for us to
potentially be able to make a decision.
Project status:
Activity: Idle
4 people indicated presence: potential for sufficient oversight.
None of the remaining project members have yet found time to raise the
topic on the dev list about moving to the Apache Attic.
So it falls to me as Chair. I am too busy at the moment, but intend
to commence the next steps on my return in early September.
By the way, many thanks to Rich Bowen for commencing an initial notice
on our dev mail list.
Security issues published:
None.
Progress of the project:
None.
-----------------------------------------
Attachment V: Report from the Apache FreeMarker Project [Dániel Dékány]
## Description:
Apache FreeMarker is a template engine, i.e. a generic tool to generate text
output based on templates. Apache FreeMarker is implemented in Java as a class
library for programmers.
FreeMarker 2 (the current stable line) produces releases since 2002. The
FreeMarker project has joined the ASF in 2015, and graduated from the
Incubator in early 2018.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
Activity was low in the last 3 months. There were some more developments on
2.3.29, and release voting has started recently.
## Health report:
Activity is low but steady, as it's usual for this project. User questions
(mostly on StackOverflow) and new Jira issues are being answered promptly. The
short term goal is to develop the next micro version (2.3.30). The long term
goal is continuing the ongoing development on the 3.0 branch, so that the
project can innovate and the code base can become much cleaner and more
attractive for new committers.
## PMC changes:
- Currently 7 PMC members.
- No changes since the graduation on 2018-03-21
## Committer base changes:
- Currently 7 committers.
- No changes since the graduation on 2018-03-21
## Releases:
- 2.3.28 was released on Wed Apr 04 2018
-----------------------------------------
Attachment W: Report from the Apache Geode Project [Karen Miller]
## Description:
The mission of Apache Geode is the creation and maintenance of software
related to a data management platform that provides real-time, consistent
access to data-intensive applications throughout widely distributed cloud
architectures.
## Issues:
There are no issues requiring board attention at this time.
## Membership Data:
Apache Geode was founded 2016-11-15 (3 years ago) There are currently 102
committers and 50 PMC members in this project. The Committer-to-PMC ratio is
roughly 2:1.
Community changes, past quarter:
- No new PMC members. Last additions were Juan Ramos and Robert Houghton on
2019-02-20
- Dale Emery was added as committer on 2019-06-19
- Mark Hanson was added as committer on 2019-06-19
## Project Activity:
Release 1.10 is in progress.
An Apache Geode Summit is scheduled the day before the SpringOne Platform 2019
conference, on 7 October 2019, in Austin, TX. Several Geode contributors will
present talks and sessions aimed at a variety of levels.
## Community Health:
Mailing lists remain active and productive.
- dev@geode.apache.org had a 13% increase in traffic in the past quarter
(505 emails compared to 443)
- Topics of discussion included:
- Pull request review requirements
- OQL method invocation security
- Lightweight RFC process
- Refactoring performance statistic structure
- Coding standards
- Criteria for admitting committers, PMC members
JIRA tickets show that issues continue to be identified and resolved.
- 289 issues opened in JIRA in the past quarter
- 296 issues closed in JIRA in the past quarter
- 454 commits in the past quarter
The community is actively contributing to the Apache Geode code base:
- 62 code contributors in the past quarter
- 344 PRs opened on GitHub in the past quarter
- 356 PRs closed on GitHub in the past quarter
-----------------------------------------
Attachment X: Report from the Apache Giraph Project [Dionysios Logothetis]
## Description:
- Giraph is a Bulk Synchronous Parallel framework for writing programs that
analyze large graphs on a Hadoop cluster. Giraph is similar to Google's
Pregel system.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- Only minor improvements in terms of commits.
## Health report:
- No significant activity in the last quarter.
- We expect to have at least a couple of contributions in the next half, one
is being currently developed, the other one is under discussion with one of
our contributors (decoupling the Giraph counter collection mechanism from
Hadoop).
## PMC changes:
- Currently 13 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Dionysios Logothetis on Sun Apr 22 2018
## Committer base changes:
- Currently 20 committers.
- No new committers added in the last 3 months
- Last committer addition was Dionysios Logothetis at Mon Apr 23 2018
## Releases:
- Last release was 1.2.0 on Thu Oct 20 2016
## Mailing list activity:
- We continue to have small but constant activity.
- dev@giraph.apache.org:
- 263 subscribers (down -1 in the last 3 months):
- 12 emails sent to list (30 in previous quarter)
- user@giraph.apache.org:
- 439 subscribers (down -2 in the last 3 months):
- 1 emails sent to list (5 in previous quarter)
## JIRA activity:
- 4 JIRA tickets created in the last 3 months
- 0 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment Y: Report from the Apache Gora Project [Kevin Ratnasekera]
## Description:
- The Apache Gora open source framework provides an in-memory data model
and persistence for big data. Gora supports persisting to column stores,
key-value stores, document stores, distributed in-memory key-value stores,
in-memory data grids, in-memory caches, distributed multi-model stores
and hybrid in-memory architectures. Gora also enables analysis of data
with extensive Apache Hadoop MapReduce, Apache Spark, Apache Flink,
and Apache Pig support.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- We formally released Apache Gora 0.9 after several release candidates.
- We are currently completing mentoring activities for 4 Google summer
of code projects this year. All 4 projects are nearly completed in extremely
positive way, that will end up 4 new modules for us.
- There was one external developer who contributed a new Apache Hive
datastore module for the project.
- Currently we are reviewing PR s for these 5 new modules.
## Health report:
- Apache Gora project is in very good health. There were a lot of involvement
from PMC members with related to reviewing PRs, verifying and voting
on release candidates.
- Also there were a lot of mailing lists discussions on GSoC projects.
- We are extremely positive on contributions from 4 GSoC students and an
external contributor, we will probably evaluate to extend our committer base
for these 5 individuals, once their major contributions are merged to
Apache Gora project.
## PMC changes:
- Currently 27 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Carlos Muñoz on Wed Dec 05 2018
## Committer base changes:
- Currently 27 committers.
- No new committers added in the last 3 months
- Last committer addition was Carlos Muñoz at Tue Nov 13 2018
## Releases:
- 0.9 was released on Thu Aug 15 2019
## Mailing list activity:
- Our main communication medium is Apache Gora development mailing list.
There is a significant rise in email traffic compared to the previous quarter
and is mainly due to GSoC project discussions and 0.9 release activities.
- dev@gora.apache.org:
- 75 subscribers (up 1 in the last 3 months):
- 514 emails sent to list (431 in previous quarter)
- user@gora.apache.org:
- 75 subscribers (up 1 in the last 3 months):
- 15 emails sent to list (3 in previous quarter)
## JIRA activity:
- 9 JIRA tickets created in the last 3 months
- 11 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment Z: Report from the Apache Groovy Project [Paul King]
## Description:
Apache Groovy is responsible for the evolution and maintenance of the Groovy
programming language. Groovy is a multi-faceted JVM programming language.
## Issues:
There are no issues requiring board attention at this time.
Wrt the Maven Coordinate namespace: we are planning to move to
org.apache.groovy for Groovy 4 with alphas expected soon.
## Membership Data:
Apache Groovy was founded 2015-11-18 (4 years ago)
There are currently 17 committers and 10 PMC members in this project.
Community changes, past quarter:
- No new PMC members. Last addition was Daniel Sun on 2019-05-06.
- No new committers. Last addition was Remko Popma on 2018-07-07.
A new committer has been invited and has accepted but the ICLA is
still pending. We anticipate including this in our next report.
## Project Activity:
Recent releases:
2.5.8 was released on Wed Aug 07 2019
3.0.0-beta-2 was released on Mon Jul 08 2019
3.0.0-beta-3 was released on Wed Aug 07 2019
This quarter, 327 commits were contributed from 9 contributors
including 5 non-committer contributors (1 new).
## Community Health:
We recently did an assessment of health across commits,
contributors, issues resolved, releases and downloads
over the last 15 years including approx 4 yrs with Apache.
Commits and issues resolved have remained steady for most
of the life of the project. Releases dropped in 2016 while
we were becoming accustomed to the Apache Way but is now
inline with pre-Apache cadence. Number of contributors has
increased since joining Apache. Downloads have always
increased and continue to do so. Groovy artifacts have been
downloaded more than a quarter of a billion times since its inception.
According to the TIOBE index for this month, Apache Groovy
is the 13th most popular programming language putting it ahead of:
Go (17), Swift (18), Perl (19), R (20), Scala (36) and Kotlin (45).
-----------------------------------------
Attachment AA: Report from the Apache Hama Project [Chia-Hung Lin]
-----------------------------------------
Attachment AB: Report from the Apache HTTP Server Project [Daniel Gruno]
## Description:
The Apache HTTP Server Project is an effort to develop and maintain an
open-source HTTP server for modern operating systems including UNIX and
Windows. The goal of this project is to provide a secure, efficient and
extensible server that provides HTTP services in sync with the current HTTP
standards.
## Issues:
There are no issues for the board at present.
## Membership Data:
Apache HTTP Server was founded 1995-02-27 (24 years ago)
There are currently 122 committers and 53 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
Community changes, past quarter:
- No new PMC members. Last addition was Stefan Sperling on 2019-01-24.
- No new committers. Last addition was Sebastian Bazley on 2018-07-14.
## Project Activity:
- 2.4.41 was released on 2019-08-12 (2.4.40 tag was burned). This release
contained fixes for four moderate and two low level CVEs. I personally want
to thank the developers and the security team for their work on these tasks.
As evident in the community health section, a lot of work was put into
making this release a reality.
- 2.4.39 was released on 2019-03-31.
- 2.4.38 was released on 2019-01-21.
- At ApacheCon North America in September, we have five httpd talks lined up.
- At ApacheCon Europe in October, we have two httpd-related talks (that I
could find...the schedule page doesn't allow for searching)
## Community Health:
I will keep things a tad shorter this quarter, and attempt to incorporate some
of the helpful hints from the new reporting tool (eating my own dog-food):
There is more than sufficient oversight on the PMC, with more than a dozen PMC
members active on a monthly basis.
Commit activity has held pretty steady over the summer, with a moderate (30%)
increase - somewhat impressive for a summer quarter! Contributor count has
likewise held up, with 16 active contributors during this quarter.
Pony Factor[1], a measurement of the diversity and size of the 'core'
developers, is holding steady at 5, which is a relatively good number[2] for a
project of this age.
The development mailing list saw a sizeable increase (>80%) in traffic, where
some gritty technical issues and general business logic was heavily discussed
- some of it point towards a needed documentation fix (aka "what does this
thing actually do?"). On the user mailing list side, things are business as
usual, with no notable change.
[1] https://s.apache.org/vpzhm for an intro to PF.
[2] https://s.apache.org/21vui for original excerpts from the paper on PF.
-----------------------------------------
Attachment AC: Report from the Apache HttpComponents Project [Asankha Chamath Perera]
## Description:
- The Apache HttpComponents project is responsible for creating and
maintaining a toolset of low-level Java components focused on HTTP and
associated protocols.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- The team is still working toward completing HttpCore 5.0 and HttpClient
5.0 BETA development phase and reaching GA milestone. Formal release votes
can be expected in Q3 2019.
## Health report:
- Overall the project remains active. With 5.0 development phase almost
complete we expect the main focus to shift from development to maintenance
and user support. There are no immediate goals for 5.1 development phase.
## PMC changes:
- Currently 9 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Michael Osipov on Mon Aug 24 2015
## Committer base changes:
- Currently 19 committers.
- No new committers added in the last 3 months
- Last committer addition was Ryan Schmitt at Wed Nov 14 2018
## Releases:
- HttpClient 4.5.9 GA was released on Wed Jun 12 2019
- HttpClient 5.0-beta5 was released on Mon Jul 22 2019
- HttpCore 5.0-beta8 was released on Mon Jul 15 2019
## Mailing list activity:
- The activity on mailing lists continues to decline. However more
development related discussions now tend to take place on Github and user
support questions tend to get asked on StackOverflow. Often people
subscribe and post quesstions to the user list only if their questions fail
to get enough attention on StackOverflow.
- dev@hc.apache.org:
- 168 subscribers (down -3 in the last 3 months):
- 551 emails sent to list (600 in previous quarter)
- httpclient-users@hc.apache.org:
- 514 subscribers (down -5 in the last 3 months):
- 95 emails sent to list (30 in previous quarter)
## JIRA activity:
- 30 JIRA tickets created in the last 3 months
- 35 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AD: Report from the Apache Ignite Project [Denis A. Magda]
## Description:
- Ignite is is a memory-centric distributed database, caching, and processing
platform for transactional, analytical, and streaming workloads delivering
in-memory speeds at petabyte scale.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- Scoping down Ignite 3.0 release that will split Ignite into modules and
introduce new APIs. Both changes are for the sake of usability and ease of
usage.
- Ignite 2.8 is being planned with a new metrics & tracing framework that
will simplify monitoring, management, troubleshooting of Ignite production
environments.
- Ignite 2.7.6 is being scheduled for August to release critical bug fixes
and improvements.
## Health report:
- There are some contributors that are planned to be promoted to committers.
As for the new contributors, there are not many of them. The community
needs to see how to draw more attention from the developer audience.
## PMC changes:
- Currently 29 PMC members.
- Ilya Kasnacheev was added to the PMC on Mon Aug 05 2019
## Committer base changes:
- Currently 47 committers.
- No new committers added in the last 3 months
- Last committer addition was Ivan Pavlukhin at Thu Apr 18 2019
## Releases:
- 2.7.5 was released on Mon Jun 03 2019
## Mailing list activity:
- dev@ignite.apache.org:
- 433 subscribers (up 4 in the last 3 months):
- 975 emails sent to list (1480 in previous quarter)
- ci@ignite.apache.org:
- 5 subscribers (up 0 in the last 3 months)
- issues@ignite.apache.org:
- 32 subscribers (down -1 in the last 3 months):
- 1747 emails sent to list (5986 in previous quarter)
- notifications@ignite.apache.org:
- 8 subscribers (up 0 in the last 3 months):
- 2638 emails sent to list (2142 in previous quarter)
- services@ignite.apache.org:
- 7 subscribers (up 0 in the last 3 months)
- user@ignite.apache.org:
- 800 subscribers (up 19 in the last 3 months):
- 940 emails sent to list (1252 in previous quarter)
## JIRA activity:
- 213 JIRA tickets created in the last 3 months
- 190 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AE: Report from the Apache Impala Project [Jim Apple]
## Description:
Apache Impala is a high-performance distributed SQL engine.
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache Impala was founded 2017-11-14 (2 years ago)
There are currently 50 committers and 32 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:4.
Community changes, past quarter:
- Bikramjeet Vig was added to the PMC on 2019-05-29
- Fredy Wijaya was added to the PMC on 2019-07-27
- Gabor Kaszab was added to the PMC on 2019-05-22
- Andrew Sherman was added as committer on 2019-06-07
- Laszlo Gaal was added as committer on 2019-06-19
- Sahil Takiar was added as committer on 2019-05-22
- Vihang Karajgaonkar was added as committer on 2019-05-14
## Project Activity:
Notable activity in the last quarter includes:
- Numerous commits related to support for Hive's ACID table format
- Improvements to the consideration of nodes as individual executors
or coordinators, including:
- Improvements to admission control and executor pool management when
there is a dedicated coordinator
- "Executor groups", a feature that allows users to run different
queries in disjoint sets of executors
- The addition of admission control parameters that scale with
the number of executors
- Improvements the developer experience on Docker
- Increased compatibility with Apache projects, including Hive 3,
erasure coding and S3Guard in HDFS, page skipping and Zstd and lz4
compression in Parquet, and miscellaneous compatibility improvements
for Ranger, Knox, Kudu, and Atlas
- The addition of several built-in functions for the DATE type as
well as the ability to read and write DATE in Parquet
- Move closer to deprecating the Beeswax protocol by adding HS2
support to the Impala shell
- Numerous patches improving tracing, logging, and metrics
- Multiple improvements to build times or isolation
- The addition of a data cache for remote reads, improving TPC-DS
performance on S3 by 30% in one scenario, which made S3 performance
as good as HDFS-on-EBS
## Community Health:
By almost all metrics, Impala activity is down quarter-over-quarter
and year-over-year. That said, the project is still very active, with
each day featuring approximately:
- Three commits
- Two dev@ emails
- 25 JIRA updates
- 70 code reviews or patch updates
-----------------------------------------
Attachment AF: Report from the Apache Incubator Project [Justin Mclean]
# Incubator PMC report for August 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/August2019
There are presently 47 podlings incubating. In July, podlings executed 9
distinct releases. We added five IPMC members and no IPMC members retired.
We have no new podlings this month, but there have been a couple of enquires
about new projects, and some proposals are being worked on. A couple of
podlings are heading towards graduation in the next few months, including
Druid.
Some podlings Amaterasu, SDAP, Tamaya, Toree didn't submit a report and have
been asked to do so next month.
Two podlings that failed to report last month reported this month. However,
Amaterasu didn't report for a second time. A couple of podlings had
trouble getting previous months reports signed off have attracted new
mentors.
TVM also gained a new mentor. Some podlings are reporting on or after the
deadline and not allowing time to discussing the content on list. The
quality of those reports may suffer as a result.
There were three IP clearances.
Apache Druid has brought up it graduation and may have an issue with its
name being the same as a project by another company. The problem is being
dealt with, but this may delay graduation depending on the outcome of those
discussions.
The Incubator made a podling release (MXNet) that contained stock photos of
unknown origin and licensing. Another release (from Tuweini) included
Category X (GPL) licensed software.
The incubator policy page has been cleaned up and updated to be easier to
understand. Anything that was guidelines and not policy has been removed.
This material was included elsewhere in the incubator and ASF websites, and
there was no need for the duplication. Podlings can always request to do
things in a different way as long as it is in line with the Apache Way.
Further work was done on a page outlining some of the issues are that
podlings might encounter during incubation and on the Incubator cookbook.
The incubator homepage was also updated to be more friendly and service
orientated.
There were several lengthy discussions of the role of the Incubator, and
its purpose, and while they were a little heated in a few places, they
were constructive.
There seems to be consensus on how the Incubator should handle podling
releases (see proposal below). It's thought that education of mentors
and podlings on the Apache Way is lacking. The Incubator will discuss what
can be done about that.
A couple of podlings have not been able to attract IPMC votes on their
releases in the usual 72 hours.
The missing incubator report wiki pages have been transferred to the new
wiki.
Based on several months discussion, the Incubator has a proposal for the
Board to consider.
*Summary*
The Incubator PMC has been discussing allowing podlings to make releases
which are not fully compliant with the ASF release policies.
Such releases would include a DISCLAIMER-WIP statement of being a "work in
progress", pointing to the specific issues that make them non-compliant.
The IPMC is seeking approval from the Board to proceed based on the details
of this proposal, below.
*Some Background*
The IPMC requires clarity from the Board if podlings need to follow ASF's
release policy and distribution policy while in incubation. This question
has been asked before, and the answer was unclear or strongly suggested
that podling releases must follow ASF policy. What is happening in practice
is that the IPMC allows releases with minor issues to go ahead and assumes
they will be fixed in a later release (before graduation) and stops
releases with any serious problem from going ahead (with an IPMC member or
two voting -1). A -1 vote is not a veto but usually stops a release,
there's only been a handful of successful releases with -1 votes. We have
consensus among IPMC members that allowing podling releases with
minor issues is a correct approach even it doesn't follow ASF policy.
Serious problems, such as; including GPL licensed software, including
compiled code, or copyright violations, in a release are currently seen as
a reason to vote -1 on a release. Podlings do try and do the right thing
but about 1 in 5 podling releases has a problem like this. Historically
there's been a few releases with serious issues that have got legal and
Incubator VP approval to make a release on a one by one, once-off basis.
The Incubator wants to allow podling to make non compliant releases to
ease their progress through the incubating process. We've come up with
an alternate disclaimer that clearly states that the release may not be
compliant with ASF release or distribution policy and lists known issues.
The legal committee have confirmed that the the Incubator as a TLP needs
to follow release policy and can only make releases with issues if it
considered to be special in some way.
*Proposal*
The IPMC can allow non-compliant releases to be distributed without IPMC VP
or legal VP approval, based on a documented list of issues which are
acceptable for such non-compliant incubating releases. Such releases will
include an alternative "work in progress" DISCLAIMER-WIP to make users aware
of the issues . When this occurs, podlings document the issues as blocking
graduation and carry on incubating. They will not be allowed to graduate
until all such release issues have been fixed.
*Notes*
The IPMC and legal committee have come up with a well-defined list of those
issues. See https://issues.apache.org/jira/browse/LEGAL-469
This list will be distributed to mentors, IPMC members and podlings so
that everyone's expectations are clear. This proposal does not change the
need for an IPMC vote on podling releases, which will be considered
separately.
The new DISPLACMER-WIP disclaimer can be found here:
https://incubator.apache.org/policy/incubation.html#disclaimers
## Community
### New IPMC members:
- Julian Feinauer
- Jamie Mark Goodyear
- Venkat Ranganathan
- Tianqi Chen
- Tim Allison
### People who left the IPMC:
None
## New Podlings
None
## Podlings that failed to report, expected next month
- Amaterasu
- SDAP
- Tamaya
- Toree
## Graduations
- Druid
## Releases
The following releases entered distribution during the month of
July:
- Flagon UserALE.JS 2.0.0
- Weex 0.26.0
- Daffodil 2.4.0
- Dubbo 2.6.7 [1]
- Mxnet 1.5.0
- Rya 4.0.0
- Heron 0.20.1
- OpenWhisk Catalog 0.10.0
- Apache Doris 0.10.0
1. Has graduated so not sure why it was placed there, will follow up.
## IP Clearance
- Celix - TCP pubsub admin
- Celix - HTTP admin
- ServiceComb Mesher
## Legal / Trademarks
Legal has confirmed how podlings releases need to comply with policy.
## Infrastructure
None.
## Miscellaneous
- An IPMC member, Sharan Foga, completed a cultural analysis paper
featuring several Apache Incubator projects. https://s.apache.org/8uaw3
- It was confirmed that only VPs of TLP need to subscribe to board@
- New cross-project IoT mailing list has been created
|----------------------------------------------------------------------
Table of Contents
[DataSketches](#DataSketches)
[Doris](#Doris)
[ECharts](#ECharts)
[Edgent](#Edgent)
[Heron](#Heron)
[Livy](#Livy)
[Milagro](#Milagro)
[PageSpeed](#PageSpeed)
[Pinot](#Pinot)
[Ratis](#Ratis)
[S2Graph](#S2Graph)
[Training](#Training)
[Tuweni](#Tuweni)
|----------------------------------------------------------------------
--------------------
## DataSketches
DataSketches is an open source, high-performance library of stochastic
streaming algorithms commonly called "sketches" in the data sciences.
Sketches are small, stateful programs that process massive data as a stream
and can provide approximate answers, with mathematical guarantees, to
computationally difficult queries orders-of-magnitude faster than
traditional, exact methods.
DataSketches has been incubating since 2019-03-30.
### Three most important unfinished issues to address before graduating:
1. Our vote letter on general@ had no responses from anyone (not just
IPMC members) for the first 73 hours. After sending a pleading
reminder email I finally got 3 +1 binding votes. I'm trying to be
polite and not needle folks, but I need guidance on how to get IPMC
members' attention. I realize the vote must stay open for at least
72 hours, but having to wait until the last minute get any response
is very aggravating. Would it be fair to send out reminder notices on
24 hour intervals?
2. Continue to perfect the release process.
3. After we get this first release, we need to finish migrating the
remaining repos.
### Are there any issues that the IPMC or ASF Board need to be aware of?
1. Yes. In addition to #1 above, not all of our Mentors have been
involved. Why do Mentors sign up if they do not or cannot mentor?
### How has the community developed since the last report?
Not too much at the committer level. We have drawn the
interest of a few new scientists in our work, but they did not
learn of our work from Apache.
It is still very early. I am speaking at ApacheCon
In September, hopefully we can attract some interest there.
I am hoping to attract some committers.
### How has the project developed since the last report?
We continue to evolve the project and make commits to the code base.
We are also heavily integrated into the Druid platform.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [X] Initial setup
- [X] Working towards next release
- [ ] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
2019-08-02 Our First release of our first component!
Thanks to: Kenneth Knowles, Furkan Kamaci, Paul King and
Justin Mclean for their help.
### When were the last committers or PPMC members elected?
When we entered incubation.
### Have your mentors been helpful and responsive?
Two (of 3) of our Mentors have been responsive when they are not
otherwise unavailable (vacation, work, etc.)
### Signed-off-by:
- [X] (datasketches) Liang Chen
Comments:
- [ ] (datasketches) Kenneth Knowles
Comments:
- [X] (datasketches) Furkan Kamaci
Comments:
### IPMC/Shepherd notes:
Justin Mclean: 72 hours is a minimum and a podling may not attract
all needed votes in that time. I understand it may be frustrating
but remember IPMC member are volunteers and mostly do this work
unpaid in their spare time. If you need more Mentors just ask on
the incubator general list.
--------------------
## Doris
Doris is a MPP-based interactive SQL data warehousing for reporting and
analysis.
Doris has been incubating since 2018-07-18.
### Three most important unfinished issues to address before graduating:
1. Develop communities and involve more people
2. Make version release more frequent
3. Podling name search
### 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?
Now we have 43 contributors, and 1 more committers.
### How has the project developed since the last report?
250+ PR have been merged into code base. 0.10.0 version has been released.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [ ] Working towards first release
- [X] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
2019-07-02
### When were the last committers or PPMC members elected?
2019-07-02
### Have your mentors been helpful and responsive?
All mentors have been helpful.
### Signed-off-by:
- [X] (doris) Dave Fisher
Comments:
- [X] (doris) Willem Ning Jiang
Comments:
- [ ] (doris) Shao Feng Shi
Comments:
### IPMC/Shepherd notes:
--------------------
## ECharts
ECharts is a charting and data visualization library written in JavaScript.
ECharts has been incubating since 2018-01-18.
### Three most important unfinished issues to address before graduating:
1. Redirecting echarts.baidu.com to echarts.apache.org. Because we found
some speed problem of Apache CDN in China, we haven't done the redirecting
job yet. We will do more test and ask for help if necessary.
2. Podling name search. We will try to complete it within this month.
3. Releasing new versions more frequently.
### 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?
Two new committers are accepted.
### How has the project developed since the last report?
We received more pull requests from the community.
### 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-03-21
### When were the last committers or PPMC members elected?
2019-06-11
### Have your mentors been helpful and responsive?
Yes.
### Signed-off-by:
- [ ] (echarts) John D. Ament
Comments:
- [X] (echarts) Kevin A. McGrail
Comments: I agree with Dave. I saw the close to graduation and it
surprised me as well. How is the CDN solution working so we can
unblock the website transition?
- [X] (echarts) Dave Fisher
Comments: I don't think that the polling is close to graduation at
all. I missed any communication about the CDN issues. There needs
to be more communication on dev@.
- [ ] (echarts) Ted Liu
Comments:
### IPMC/Shepherd notes:
--------------------
## Edgent
Apache Edgent is a programming SDK and micro-kernel style runtime
that can be embedded in gateways and small footprint edge devices enabling
local, real-time, analytics on the continuous streams of data coming
from equipment, vehicles, systems, appliances, devices and sensors of
all kinds (for example, Raspberry Pis or smart phones). Working in
conjunction with centralized analytic systems, Apache Edgent provides
efficient and timely analytics across the whole IoT ecosystem: from the
center to the edge.
Edgent has been incubating since 2016-02-29.
### Three most important unfinished issues to address before graduating:
1. Re-creating a working community
2. Re-populating the PPMC
3. Replenishing the group of mentors
### Are there any issues that the IPMC or ASF Board need to be aware of?
For the past months, there has been very few activity in the project
There have been a hand full of Emails from external peoples in the
last 3 months but the activity in the project has been solely by me
(Julian).
Julian started an Approach for „Edgent Next“. This is a suggestion to
re-activate activities in the edgent community and integrate it as a
middle layer between several other IoT or Edge relared Projects.
This was also announced on the new iot@apache.org<mailto:iot@apache.org>
Mailing list but on both lists no feedbackl was responded yet.
The main problem we have is that the only active people in the project
came in Late and are not that firm with the codebase. Currently, we
have a codebase for which we have a detailed understanding of the build,
but almost none of the code itself. Furthermore, there has been a lot of
activity in other projects and generally edge processing has developed
further in the recent years.
Thus, there is some discussion going on about the core or the aim of the
project to keep its significance and uniqueness.
### How has the community developed since the last report?
* Total, we have 82 subscribers to our mailing list, an increase of 5
since the last report.
* There have been four questions asked by users and little discussions
about these issues on the list
* On April, 4th, Julian Feinauer has Talked about Edgent on the building
iot 2019
* On July 16th Julian Feinauer started a discussion About „Edgent Next“
on the edgent and iot Mailing lists
### How has the project developed since the last report?
According to JIRA, 0 new issue were added and none were resolved in the
last 90 days
### How would you assess the podling's maturity?
After the withdrawal of most of the active committers and PPCM members
currently a new committer, PPMC and mentor-base has to be built.
Currently we try to re-gain the focus of edgent to
Start to rebuild the community and resume development.
- [ ] Initial setup
- [ ] Working towards first release
- [X] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
2017-12-14 Apache Edgent 1.2.0
### When were the last committers or PPMC members elected?
* In August 2017, we added Christofer Dutz as a new committer and PPMC
member.
* In November 2018, we added Julian Feinauer as a new committer and PPMC
member.
### Have your mentors been helpful and responsive?
I just double checked, but it seems our mentors are not existent
there had been one or two issues where feedback was explicitly
asked for, but both the PPMC as well as all mentors remained silent.
Except Justin mentioning the absence of mentors. Christofer Dutz
joined as new Mentor and is active in the project.
### Signed-off-by:
- [x] (edgent) Luciano Resende
Comments:
- [X] (edgent) Justin Mclean
Comments:
- [X] (edgent) Christofer Dutz
Comments:
### IPMC/Shepherd notes:
--------------------
## Heron
A real-time, distributed, fault-tolerant stream processing engine.
Heron has been incubating since 2017-06-23.
### Three most important unfinished issues to address before graduating:
* Fixing issues with licensing in the repo.
* Making several Releases
* Updating the heron documentation site
### Are there any issues that the IPMC or ASF Board need to be aware of?
- n/a
### How has the community developed since the last report?
The community is gradually growing. Monthly meetups have been regularly
and successfully organized.
### How has the project developed since the last report?
There have been bug fixes and feature improvements. Some to note are:
* More memory leak fixes
* Documentation updates
* License fixes
* UI improvements
* Kryo serializer support
* Spouts improvements
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [ ] Working towards first release
- [x] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
2019-07-29
### When were the last committers or PPMC members elected?
March 2019
### Have your mentors been helpful and responsive?
Dave has been helpful and responsive, but other mentors have been much
less
responsive
### Signed-off-by:
- [ ] (heron) Jake Farrell
Comments:
- [ ] (heron) Julien Le Dem
Comments:
- [ ] (heron) P. Taylor Goetz
Comments:
- [X] (heron) Dave Fisher
Comments:
### IPMC/Shepherd notes:
--------------------
## Livy
Livy is web service that exposes a REST interface for managing long running
Apache Spark contexts in your cluster. With Livy, new applications can be
built on top of Apache Spark that require fine grained interaction with many
Spark contexts.
Livy has been incubating since 2017-06-05.
### Three most important unfinished issues to address before graduating:
1. Grow the community to get more reviews and content
2. Improve the code quality and expand its scope
3. Get more content
### 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?
There're not so many activities since the last report. But we do saw some
new contributors were start working on this project.
### How has the project developed since the last report?
Working on feature development and bug fix, planning to hive a 0.7.0
release this year.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [ ] Working towards first release
- [X] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
2019-04-01
### When were the last committers or PPMC members elected?
2019-01-22
### Have your mentors been helpful and responsive?
Yes.
Are things falling through the cracks? If so, please list any
open issues that need to be addressed.
### Signed-off-by:
- [ ] (livy) Bikas Saha
Comments:
- [ ] (livy) Brock Noland
Comments:
- [x] (livy) Luciano Resende
Comments:
- [ ] (livy) Jean-Baptiste Onofre
Comments:
### IPMC/Shepherd notes:
--------------------
## Milagro
Milagro is core security infrastructure and crypto libraries for
decentralised networks and distributed systems.
Milagro has been incubating since 2015-12-21.
### Three most important unfinished issues to address before graduating:
1. Continue to build relevant and useful crypto libs
and applications for decentralised networks in order
to grow the ecosystem of users and contributors to the project.
2. Get all functions of the project in line with the Apache Way
so we stay in compliance and can get a release under our belts.
3. Get a release under our belts!
### 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 continue to garner a lot of interest in the project from the
crypto community.
### How has the project developed since the last report?
We're going to move to have the IPMC vote to approve a release
of the crypto-c and crypto-js libraries next week.
We will be scheduling releases of the Decentralized Trust Authority, along
with an upgrade of the website and documentation site this month.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [X] Initial setup
- [X] Working towards first release
- [ ] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
XXXX-XX-XX
### When were the last committers or PPMC members elected?
Last month.
### Have your mentors been helpful and responsive?
Yes.
### Signed-off-by:
- [X] (milagro) Nick Kew
Comments: OK, I need to post to dev list about detail in the report!
- [ ] (milagro) Jean-Frederic Clere
Comments:
- [ ] (milagro) Drew Farris
Comments:
### IPMC/Shepherd notes:
--------------------
## PageSpeed
PageSpeed represents a series of open source technologies to
help make the web faster by rewriting web pages to reduce
latency and bandwidth.
PageSpeed has been incubating since 2017-09-30.
### Three most important unfinished issues to address before graduating:
1. Produce a release
2. Grow more active contributors
3.
### Are there any issues that the IPMC or ASF Board need to be aware of?
What has been falling through the cracks is actually producing a release
for review. That has been looked into [1] but the artifact needs a few
tweaks to get it right according to ASF standards before it makes sense to
enter the process.
[1] http://people.apache.org/~oschaaf/mod_pagespeed/
### How has the community developed since the last report?
One new committer/ppmc member was voted in after contributing
a series of code changes to the core product.
### How has the project developed since the last report?
A significant effort is in progress to modernize some aspects of
the project as well as simplify the build and dependency management
by porting the build system from gyp to bazel.
This is a first step towards the PageSpeed 2.0 plan that was initially
proposed when entering the incubator.
### 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?
May 27 2019 (Longinos Ferrando, elected as both committer and PMC member)
### Have your mentors been helpful and responsive?
Mentors have been helpful.
### Signed-off-by:
- [x] (pagespeed) Jukka Zitting
Comments: The community needs more help from mentors to get the first
ASF release out. Unfortunately my availability continues to be fairly
limited, to the point where I might need to resign and ask someone else
to fill in. I'll try to help push things along before our next report,
and will re-evaluate my usefulness as mentor then.
- [ ] (pagespeed) Leif Hedstrom
Comments:
- [X] (pagespeed) Nick Kew
Comments:
- [ ] (pagespeed) Phil Sorber
Comments:
### IPMC/Shepherd notes:
--------------------
## Pinot
Pinot is a distributed columnar storage engine that can ingest data in real-
time and serve analytical queries at low latency.
Pinot has been incubating since 2018-10-17.
### Three most important unfinished issues to address before graduating:
1. Increasing frequency of release
2. Adding more committers from open source community
3. Getting word out from community (blogs, etc.)
### Are there any issues that the IPMC or ASF Board need to be aware of?
Pinot release is scheduled to happen quarterly but has been delayed due
to a bug we found in helix that was very hard to track down.
https://github.com/apache/helix/issues/331. We finally
found the issue, and should be cutting the next release shortly.
### How has the community developed since the last report?
We have had open-source contributions to integrate Calcite SQL parser,
support for transforms in selections and filters, support for kafka-2.0,
and several other bug fixes and performance enhancements. Other
contributions on upsert feature, and deep-store commit are in the design
process.
Contributions from outside of Linkedin:
- UDF support in filter predicates:
https://github.com/apache/incubator-pinot/pull/4365
- Kafka 2.0 support (work authored across open source community):
https://github.com/apache/incubator-pinot/pull/4397
- Variable length bytes dictionary support:
https://github.com/apache/incubator-pinot/pull/4321
- PQL to SQL enhancement Phase-1 :
https://github.com/apache/incubator-pinot/pull/4216
- Ideas and discussions on null value support:
https://github.com/apache/incubator-pinot/issues/4230
- Ideas and discussions on SQL support:
https://github.com/apache/incubator-pinot/issues/4219
### How has the project developed since the last report?
1. Support for Kafka-2.0 added
2. Work in progress to move closer to SQL syntax and semantics for
constructs supported.
3. Helix and Pinot controller separation in final phase of development.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [ ] Working towards first release
- [ ] Community building
- [X] Nearing graduation
- [ ] Other:
### Date of last release:
2019-02-15
### When were the last committers or PPMC members elected?
No new PPMC members or committers since incubation
### Have your mentors been helpful and responsive?
Yes, mentors have been super-helpful and respond to questions in a timely
manner.
### Signed-off-by:
- [ ] (pinot) Kishore Gopalakrishna
Comments:
- [X] (pinot) Jim Jagielski
Comments:
- [ ] (pinot) Roman Shaposhnik
Comments:
- [ ] (pinot) Olivier Lamy
Comments:
- [X] (pinot) Felix Cheung
Comments: Nice improvements to the project. Agreed next steps would
be on community building.
### IPMC/Shepherd notes:
--------------------
## Ratis
Ratis is a java implementation for RAFT consensus protocol
Ratis has been incubating since 2017-01-03.
### Three most important unfinished issues to address before graduating:
1. Establish a release cadence.
2. Podling name search.
3. Complete graduation template
### Are there any issues that the IPMC or ASF Board need to be aware of?
None
### How has the community developed since the last report?
2 new contributors, 61 contributors in total.
20 committers and PPMC members.
### How has the project developed since the last report?
50 commits, 0.4.0 version RC is out for voting.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [X] Initial setup
- [X] Working towards a release cadence.
- [X] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
2019-04-26
### When were the last committers or PPMC members elected?
2018-12-05
### Have your mentors been helpful and responsive?
Mentors are helpful.
### Signed-off-by:
- [x] (ratis) Jakob Homan
Comments:
- [X] (ratis) Uma Maheswara Rao G
Comments:
- [ ] (ratis) Devaraj Das
Comments:
### IPMC/Shepherd notes:
--------------------
## S2Graph
S2Graph is a distributed and scalable OLTP graph database built on Apache
HBase to support fast traversal of extremely large graphs.
S2Graph has been incubating since 2015-11-29.
### Three most important unfinished issues to address before graduating:
1. Make the third release.
2. Attract more users and contributors.
3. Build the developer community in both size and diversity.
### Are there any issues that the IPMC or ASF Board need to be aware of?
None
### How has the community developed since the last report?
- There were some questions and answers from the community about how to
getting started.
- New feature requests are opened on JIRA.
### How has the project developed since the last report?
- Providing OpenAPI documentation for REST API is pending since there was
lack of discussion.
- It has been very quiet since the last report(only 1 JIRA issue opened).
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [ ] Working towards first release
- [x] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
2017-08-26
### When were the last committers or PPMC members elected?
2019-02-05
### Have your mentors been helpful and responsive?
Our mentor is very helpful and responsive.
### Signed-off-by:
- [ ] (s2graph) Sergio Fernández
Comments:
- [X] (s2graph) Woonsan Ko
Comments:
### IPMC/Shepherd notes:
--------------------
## Training
The Training project aims to develop resources which can be used for
training purposes in various media formats, languages and for various
Apache and non-Apache target projects.
Training has been incubating since 2019-02-21.
### Three most important unfinished issues to address before graduating:
1. Grow the community to get more & faster reviews and content
2. Improve the technology stack
3. Get more content
### Are there any issues that the IPMC or ASF Board need to be aware of?
- no critical issues at this point in time
### How has the community developed since the last report?
- The dev mailing list activity has died down a bit. The total number of
posts in May was 165, June 66, July 36
- Total number of subscribers to the dev list is 31 (-1 since last report)
### How has the project developed since the last report?
- We have delivered our first release during which we ironed out a few
issues: https://s.apache.org/jclr6
- We decided upon a logo which was created by Daniel Gruno after we
reached out to Central Services. Thank you very much for your help!
- We had more content donations (ZooKeeper, Ignite, GitHub, Spark)
- The ZooKeeper community helped us review the ZooKeeper contribution
which was greatly improved due to their reviews. Thank you!
- A few of the Training members will be present at both ApacheCons this
year and there will be multiple talks about the project
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [ ] Working towards first release
- [X] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
2019-07-13: Apache Training (incubating) - Navigating the ASF Incubator
Process 1.0, Announcement: https://s.apache.org/h8bct
It can be viewed online here: https://s.apache.org/wl3w2
### When were the last committers or PPMC members elected?
n.a.
### Have your mentors been helpful and responsive?
Not answered.
### Signed-off-by:
- [X] (training) Justin Mclean
Comments:
- [X] (training) Craig Russell
Comments:
- [X] (training) Christofer Dutz
Comments:
- [X] (training) Lars Francke
Comments:
### IPMC/Shepherd notes:
--------------------
## Tuweni
Tuweni is a set of libraries and other tools to aid development of
blockchain and other decentralized software in Java and other JVM languages.
Tuweni has been incubating since 2019-03-25.
### Three most important unfinished issues to address before graduating:
1. address some issues in releases and fix pushing to Maven central
2. attract more committers
3. build a better 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?
We invited a new committer over to the project,
based on their contributions.
### How has the project developed since the last report?
We voted successfully on release 0.8.1 and are ironing out
issues raised in the release 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:
2019-07-24
### When were the last committers or PPMC members elected?
no elections yet, we have an invite out to a new committer.
### Have your mentors been helpful and responsive?
Yes, no problem.
### Signed-off-by:
- [X] (tuweni) Jim Jagielski
Comments:
- [X] (tuweni) Dave Fisher
Comments: I don't think that this podling is near graduation.
- [ ] (tuweni) Kenneth Knowles
Comments:
- [ ] (tuweni) Jean-Baptiste Onofré
Comments:
- [X] (tuweni) Michael Wall
Comments: Congrats on your first release!!
- [X] (tuweni) Furkan Kamaci
Comments:
### IPMC/Shepherd notes:
-----------------------------------------
Attachment AG: Report from the Apache jUDDI Project [Alex O'Ree]
## Description:
- jUDDI (pronounced "Judy") is an open source Java implementation of the
Universal Description, Discovery, and Integration (UDDI v3) specification
for (Web) Services. The jUDDI project includes Scout. Scout is an
implementation of the JSR 93 - Java API for XML Registries 1.0 (JAXR).
## Issues:
- There are no issues that require the board's attention at this time.
## Activity:
- jUDDI - last release was 04 DEC 2018. Resolved several requisite bugs for
updating SCOUT.
- SCOUT - last release 10 DEC 2018. Resolved several bugs and dependencies.
## Health report:
- Low development activity is a factor for low mailing list volume, but in all
likelihood, it's from a general lack of interest in the protocol.
- There has been some new feature development recently.
- There are enough active PMC members to approve releases and respond to
potential security issues. There were no issues raised since the last
report.
## PMC changes:
- Currently 7 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Alex O'Ree on Sun Mar 17 2013
## Committer base changes:
- There are currently 7 committers and 7 PMC members in this project.
- The Committer-to-PMC ratio is 1:1.
- No new changes to the committer base since last report.
## Releases:
- 3.3.6 was released on Tue Dec 04 2018
- SCOUT-1.2.8 was released on Mon Dec 10 2018
## Mailing list activity:
- dev@juddi.apache.org:
- 67 subscribers (up -1 in the last 3 months):
- 38 emails sent to list (106 in previous quarter)
- user@juddi.apache.org:
- 105 subscribers (up -3 in the last 3 months):
- 1 emails sent to list (4 in previous quarter)
## JIRA activity:
- 3 JIRA tickets created in the last 3 months
- 2 JIRA tickets closed/resolved in the last 3 months
## Commit activity:
- 6 commits in the past quarter (600% increase)
- 1 code contributor in the past quarter (100% increase)
-----------------------------------------
Attachment AH: Report from the Apache Juneau Project [James Bognar]
## Description:
The mission of Apache Juneau is the creation and maintenance of software
related to a toolkit for marshalling POJOs to a wide variety of content types
using a common framework, and for creating sophisticated self-documenting REST
interfaces and microservices using VERY little code
## Issues:
No issues to report.
## Membership Data:
Apache Juneau was founded 2017-10-17 (2 years ago) There are currently 12
committers and 12 PMC members in this project. The Committer-to-PMC ratio is
1:1.
Community changes, past quarter:
- No new PMC members. Last addition was Ayeshmantha Perera on 2019-01-02.
- No new committers. Last addition was Ayeshmantha Perera on 2019-01-02.
## Project Activity:
Version 8.0.0 was released on 2018-12-13. The community is currently voting
on version 8.1.0 which includes significant new functionality for use in
Spring Boot applications. We hope to have this released within the next 1-2
weeks.
One of our newer members is working on a new component for a configuration
server.
## Community Health:
dev@juneau.apache.org had a 95% increase in traffic in the past quarter (92
emails compared to 47) 20 issues opened in JIRA, past quarter (66% increase)
21 issues closed in JIRA, past quarter (320% increase) 120 commits in the past
quarter (15% increase)
Our active community continues to be small and we have struggled to attract
new developers willing to make code contributions. Our code base is rather
mature/complex and can be daunting for new developers to pick up. Most of the
current JIRA issues are rather complex feature requests. Low-hanging fruit
for new developers is not always available. All code commits within the past
6 months have come from 2 developers.
The PMC Chair believes the project needs more exposure through external
articles which current members have not had time to devote.
-----------------------------------------
Attachment AI: Report from the Apache Kafka Project [Jun Rao]
Apache Kafka is a distributed event streaming platform for efficiently storing
and processing a large number of records in real time.
Development
===========
We released 2.3.0 which includes new features such as incremental cooperative
rebalancing in Connect, external configuration stores, in-memory session store
and window store in KStreams, improved metrics and AdminClient.
We also released 2.2.1 which fixes more than 40 critical issues.
We are working on some of the new Kafka Improvement Proposals (KIP). In
particular, KIP-500 proposes to remove the dependency on Zookeeper to improve
the scalability and the dependency in Kafka.
Community
===========
Lots of activities in the mailing list. We have 2824 subscribers in the user
mailing list, slightly more than the last 3 months. We have 1341 subscribers
in the dev mailing list, slightly more than the last 3 months. We have 432
JIRA tickets created and 220 JIRA tickets closed in the last 3 months.
We didn't add any new committer/PMC member in the last 3 months. We last added
a new committer on Feb. 14, 2019 and we last added a new PMC member on Apr.
18, 2019.
Kafka Summit London completed on May 14, 2019, with more than 1000
participants.
Releases
===========
2.3.0 was released on Jun. 24, 2019.
2.2.1 was released on Jun. 2, 2019.
-----------------------------------------
Attachment AJ: Report from the Apache Kibble Project [Rich Bowen]
## Description:
The mission of Apache Kibble is the creation and maintenance of software
related to an interactive project activity analyzer and aggregator
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache Kibble was founded 2017-10-18 (2 years ago)
There are currently 12 committers and 12 PMC members in this project.
The Committer-to-PMC ratio is 1:1.
Community changes, past quarter:
- No new PMC members. Last addition was Rafael Weingärtner on 2017-12-09.
- No new committers. Last addition was Rafael Weingärtner on 2017-12-09.
## Project Activity:
The Kibble demo moved to new hardware, where we were able to expand our demo
project to cover all of the ASF's repositories, mailing lists and bug
trackers. This should hopefully mean a wider use from the Apache community,
and thus more feedback.
Issues were raised[1] about, and efforts put into, scanning GitHub and other
resources at a massive scale (like the ASF). We were able to work with the
respective APIs and rules and come up with a process that works well at large
scale.
ComDev have started pulling data from the Kibble demo into the new reporter
tool wizard. (This report was drafted and published via that tool.) There
are talks about also implementing metrics in Whimsy from Kibble.
A paper was written[2] by a member of the PMC using data gathered from Kibble to
support the validity of the claims in it.
[1] https://s.apache.org/e5wgi
[2] https://s.apache.org/w2gy6
## Community Health:
With Kibble being a relatively small and slow project in mind, we saw a good
uptick in issues opened, and discussions surrounding them.
We continue to be concerned (as we say almost every quarter) by the fact that
practically all of the actual code/doc commits are being made by one person,
and most comments/issues raised are of the "please do this for me" type. We
clearly need to focus on attracting developer/committer interest in the
project.
-----------------------------------------
Attachment AK: Report from the Apache Knox Project [Larry McCay]
## Description:
- The Apache Knox Gateway is a REST API Gateway for interacting with Apache
Hadoop clusters. The Knox Gateway provides a single access point for all
REST/HTTP interactions with Apache Hadoop clusters.
- The mission of Knox is the creation and maintenance of software related to
simplify and normalize the deployment and implementation of secure Hadoop
clusters.
## Issues:
- there are no issues requiring board attention at this time
## Membership Data:
Apache Knox was founded 2014-02-18 (5 years ago)
There are currently 21 committers and 17 PMC members in this project.
The Committer-to-PMC ratio is roughly 6:5.
Community changes, past quarter:
- No new PMC members. Last addition was Kevin Risden on 2018-04-02.
- No new committers. Last addition was Kevin Risden on 2018-04-03.
## Project Activity:
- Apache Knox 1.3.0 was released in July with over 200 fixes, upgrades and
improvements.
- Planning for the 1.4.0 release will begin with the backlock of JIRAs and
discussion around cloud usecases.
## Community Health:
- activity on the JIRAs and commits appear to continue to grow and seem rather
healthy. Email list traffic seems to be trending down however I believe this
to be due to much fewer infra related test failures that artificially
inflated those numbers previously. Community Health Score 4.7
-----------------------------------------
Attachment AL: Report from the Apache Kylin Project [Luke Han]
## Description:
Apache Kylin is an open source Distributed Analytics Engine designed
to provide SQL interface and multi-dimensional analysis (OLAP) on
Hadoop supporting extremely large datasets.
## Issues:
There are no issues requiring board attention at this time
## Membership Data:
Apache Kylin was founded 2015-11-18 (4 years ago)
There are currently 35 committers and 22 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:2.
Community changes, past quarter:
- Gang Ma was added to the PMC on 2019-05-29
- JiaTao Tao was added as committer on 2019-06-13
## Project Activity:
- The community is actively working on a release next
generation of Kylin: v3.0 for realtime capability.
the Alpha2 is released on July 30.
- June 16, 2019, "Accelerate big data analytics with Apache
Kylin" by Shaofeng Shi @ Berlin Buzzwords 2019
- July 12 2019, Kylin Data Summit @ Shanghai
- Aug 1 2019, Kylin meetup @ Seattle,
- Aug 7 2019, Kylin meetup @ San Jose
Recent releases:
3.0.0-alpha2 was released on 2019-07-30.
2.6.3 was released on 2019-07-05.
2.6.2 was released on 2019-05-18.
## Community Health:
Community is health with more adoption are on-boarding and
new features are developing.
-----------------------------------------
Attachment AM: Report from the Apache Lens Project [Amareshwari Sriramadasu]
## Description:
Lens provides an Unified Analytics interface. Lens aims to cut the Data
Analytics silos by providing a single view of data across multiple tiered data
stores and optimal execution environment for the analytical query. It
seamlessly integrates Hadoop with traditional data warehouses to appear like
one.
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache Lens was founded 2015-08-19 (4 years ago)
There are currently 23 committers and 18 PMC members in this project.
The Committer-to-PMC ratio is roughly 6:5.
Community changes, past quarter:
- No new PMC members. Last addition was Puneet Gupta on 2016-09-20.
- No new committers. Last addition was Rajitha R on 2018-02-09.
## Project Activity:
A couple of bug fixes done in the code. No new releases done, after the past
release 2.7
## Community Health:
Committers and PMC are active and committed to help the project. One
contributor suggesting changes and contributing to the project.
-----------------------------------------
Attachment AN: Report from the Apache Libcloud Project [Tomaž Muraus]
## Description:
Libcloud is a Python library that abstracts away the differences among
multiple cloud provider APIs.
## Issues:
There are no issues which require board attention at this time.
## Activity:
Since the last report we added one new committer (Clemens Wolff) and started
a voting thread for another one.
We are also working on a new release which should be out some time in the next
month.
External contributor activity is similar as in the past and we still receive
a good amount of contributions.
To decrease the barrier to entry and contribution for committers and
external contributions, we decided to move the whole development workflow to
Github.
This means committers can now directly merge user contributions on Github and
we also utilize Github issues for issue tracking and project management.
## Answers to board questions / feedback added to the previous report
1. jj: Concerned that it seems like there is insufficient critical mass
in the PMC to handle what looks to be a goodly amount of
external interest
Yes, we had some committer activity issues.
As mentioned in the past, Libcloud utilizes adapter / plugin pattern which
means that even if we have some active committers they might not be an expert
in driver for some specific provider so they can't always effectively review
the code changes / troubleshoot the bug / similar.
2. druggeri: Agreed with Jim. I would encourage addition to the PMC and
committer pools even if those individuals are only
interested in one area of the codebase.
Agreed, we are working on that.
3. rb: Am I correctly understanding that you don't extend committer
rights to people who only care about one driver? If so, I'd
encourage you to rethink that policy, as those people are as
much in ownership of the project as those who care about more
than one aspect.
We do extend committer rights to people who only care about a single driver /
provider. In fact, a big chunk of our current committer base primarily works
and is interested in a single provider.
## PMC changes:
- Currently 13 PMC members.
- No new PMC members added in the last 3 months
## Committer base changes:
- Currently 22 committers.
- Clemens Wolff was added as committer on 2019-07-15
## Releases:
- 2.4.0 was released on Thu Nov 08 2018
- 2.3.0 was released on March 03, 2018
- 2.2.1 was released on September 21, 2017
-----------------------------------------
Attachment AO: Report from the Apache Logging Services Project [Matt Sicker]
## Description:
The Apache Logging Services Project creates and maintains open-source
software related to the logging of application behavior and released
at no charge to the public.
## Issues:
There are no issues requiring board attention at this time.
## Membership Data:
Apache Logging Services was founded 2003-12-16 (16 years ago)
There are currently 35 committers and 14 PMC members in this project.
The Committer-to-PMC ratio is 5:2.
Community changes, past quarter:
- No new PMC members. Last addition was Carter Kozak on 2018-07-29.
- No new committers. Last addition was Andrei Ivanov on 2019-04-18.
## Project Activity:
- In June, we released Log4j 2.12.0 which added support for runtime
reconfiguration via HTTP/HTTPS, Docker, and Spring Cloud Configuration,
along with numerous bug fixes and dependency updates.
- In August, we just released Log4j 2.12.1 which contains more bugfixes,
a performance improvement to logger callsite location calculation,
as well as an improvement to the Log4j 1.2 compatibility layer to not
require log4j-core as a dependency.
- Discussions over IDE setup complications regarding multiple JDKs in a
single Maven project raised an interesting point about a current barrier
to entry in the project. No ideal solution has been identified yet beyond
requesting IDEs to support Maven toolchains properly.
- A new discussion about the health of Log4net was started back in June
by a contributor.
- Experiments with a fluent logging API inspired by the current FLogger
and SLF4J fluent logger APIs discovered interesting performance
improvements for logger callsite location calculation. After making some
microbenchmarks, an improvement to the internals of log4j-core was made
to significantly reduce the number of stack frames that need to be traversed
to calculate callsite location info.
- In July, we began discussions around potentially adopting a formal
code of conduct for the project to make the project more welcoming
to contributors and community members. The general consensus seems to
be to adopt the ASF's CoC, though there has been no formal action taken
at this time.
- Discussions began on dropping Java 7 support in Log4j 2.x. This was
originally deferred to Log4j 3.x, though we want to decouple the Java
update.
- Early discussions on making new releases of Log4j Audit and Log4j Scala API.
## Community Health:
- Development and mail activity have increased over 100% since last quarter.
This is explained in more detail in the project activity.
- Discussions around adopting a code of conduct were positive.
- Health of the Log4net subproject was brought up on the mailing lists.
-----------------------------------------
Attachment AP: Report from the Apache ManifoldCF Project [Karl Wright]
Project description
==============
ManifoldCF is an effort to provide an open source framework for connecting
source content repositories like Microsoft Sharepoint and EMC Documentum, to
target repositories or indexes, such as Apache Solr, OpenSearchServer or
ElasticSearch. ManifoldCF also defines a security model for target
repositories that permits them to enforce source repository security policies.
Releases
========
ManifoldCF graduated from the Apache Incubator on May 16, 2012. Since then,
there have been numerous major releases, including a 2.13 release on May 1,
2019. The next major release is due on August 31, 2019.
Committers and PMC membership
=============================
We nominated and approved Markus Schuch as committer on 11/25/2016. We
nominated and approved Markus Schuch as a PMC member on 12/29/2017. We did not
sign up any new committers or PMC members this quarter. We continue to be on
the lookout for new PMC members and committers. There is an open discussion
for an additional committer at this time but summer vacations are apparently
interfering with this right now.
The lack of quality engagement from the community of users continues to be a
concern. Many demands exist for redevelopment of, or improvement of, existing
connectors. Our model of relying on assisted contributions for these
redevelopment efforts cannot succeed if the user community has few competent
developers. We thank the Board for its inquiry as to whether ComDev might get
involved here, but there is still no plan in place.
Mailing list activity
=====================
Mailing list activity has been fairly quiet this quarter, but requests for
connector development have been significant. Some connector redevelopment that
was expected to be completed by now is still underway, because of lack of
competent development skill in the new development environment. Without such
skills, development stalls over very basic issues, like how to debug in a Java
environment, or how to write a single class that can be used to exercise the
new API.
I am unaware of any mailing list question that has gone unanswered.
-----------------------------------------
Attachment AQ: Report from the Apache Marmotta Project [Jakob Frank]
## Description:
The mission of Marmotta is the creation and maintenance of software related to
An Open Platform for Linked Data
## Issues:
As previously reported by the Board, there is a concern about the viability of
the community after the core team has moved to other areas. The PMC is
discussing the issue, and it will be discussed with the community in the
following days. At this stage all options are on the table.
## Membership Data:
Apache Marmotta was founded 2013-11-19 (6 years ago)
There are currently 13 committers and 11 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:6.
Community changes, past quarter:
- No new PMC members. Last addition was Mark A. Matienzo on 2016-08-17.
- No new committers. Last addition was Xavier Sumba on 2017-03-27.
## Project Activity:
Another quiet quarter to report without significant development activities.
Recent releases:
* 3.4.0 was released on 2018-06-11.
* 3.3.0 was released on 2014-12-05.
* 3.2.1 was released on 2014-05-20.
## Community Health:
The project was considered feature-complete since 3.3.0 and few months ago has
published version 3.4.0 with some updates and fixes. Currently there are no
active development activities.
* dev@marmotta.apache.org had a 30% decrease in traffic in the past quarter
(7 emails compared to 10)
* users@marmotta.apache.org had a 96% decrease in traffic in the past quarter
(1 emails compared to 24)
* 3 issues opened in JIRA, past quarter (300% increase)
* 0 commits in the past quarter (no change)
* 0 code contributors in the past quarter (no change)
-----------------------------------------
Attachment AR: Report from the Apache Mesos Project [Benjamin Hindman]
## Description:
Apache Mesos abstracts CPU, memory, storage, and other compute
resources away from machines (physical or virtual), enabling
fault-tolerant and elastic distributed systems to easily be built and
run effectively.
## Issues:
There are no issues requiring board attention at this time.
## 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.
PMC changes, past quarter:
- No new PMC members added in the past quarter.
- Last PMC addition was Benno Evers on 2019-03-11.
Committership changes, past quarter:
- No new committers added in the past quarter.
- Last committer addition was Andrei Budnik on 2019-03-06.
## Project Activity:
- 1.9.0 release is in active development.
- 1.8.0 was released on Wed May 01 2019
- 1.8.1 RC got required binding votes on July 17th 2019
- 162 JIRA tickets created in the last 3 months
- 129 JIRA tickets closed/resolved in the last 3 months
## Community Health:
- The project continues to see new bug reports, bug fixes, features,
reviews and releases.
- Messages in mailing lists have seen a downtick but we believe part of it is
due to more people preferring to interact over Slack.
-----------------------------------------
Attachment AS: Report from the Apache MetaModel Project [Kasper Sørensen]
## Description:
The mission of MetaModel is the creation and maintenance of software related to
common interface for discovery, exploration of metadata and querying of
different types of data sources
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache MetaModel was founded 2014-11-19 (5 years ago)
There are currently 13 committers and 11 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:6.
Community changes, past quarter:
- No new PMC members. Last addition was Dennis Du Krøger on 2016-09-06.
- No new committers. Last addition was Jörg Unbehauen on 2018-05-03.
## Project Activity:
We are getting ready for another release soon after a handful of good
contributions coming from several members of the community.
## Community Health:
We see a few new contributors as of late, breaking the otherwise slowing
traffic that we where seeing earlier.
-----------------------------------------
Attachment AT: Report from the Apache Oozie Project [Gézapeti]
## Description:
The mission of Oozie is the creation and maintenance of software related to A
workflow scheduler system to manage Apache Hadoop jobs.
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache Oozie was founded 2012-08-28 (7 years ago)
There are currently 25 committers and 21 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:6.
Community changes, past quarter:
- Kinga Marton was added to the PMC on 2019-07-16
- No new committers. Last addition was Andras Salamon on 2019-02-14.-
## Project Activity:
- Kinga drove the work on making Oozie compatible with Java 11. She did an
outstanding job in OOZIE-3459.
- Many third party libraries were upgraded to mitigate vulnerabilities in them
- 5.1.0 was released on 2018-12-19
- Discussion started about a 5.2 release. There are more than a 100 commits
since 5.1.0 and we'd like to make them available for the public. We're
looking for a release manager and hoping to get one after the summer.
## Community Health:
Commit and Jira activity remained steady over the summer with busier and
quieter weeks depending on vacations. There were a couple new authors showing
up, but the code contributor count is still pretty low. We're keeping an open
eye for new potential committers among the new contributors.
-----------------------------------------
Attachment AU: Report from the Apache Open Climate Workbench Project [Huikyo Lee]
## Description:
- The OCW includes a Python open-source library for common climate model
evaluation tasks as well as a set of user-friendly interfaces for quickly
configuring a model evaluation task. OCW also allows users to build their
own climate data analysis tools, such as the statistical downscaling
toolkit.
## Issues:
- there are no issues requiring board attention at this time
## Activity:
- We are refactoring and testing OCW by using xarray and pandas and developing
Jupyter Notebook interface.
## Health report:
- Some of the newly developed codes are tested in private github repositories.
## PMC changes:
- Currently 30 PMC members.
- The Committer-to-PMC ratio is 1:1
- No new PMC members added in the last 3 months
- Last PMC addition was Ibrahim Jarif on Mon Apr 25 2016
## Committer base changes:
- Currently 30 committers.
- No new committers added in the last 3 months
- Last committer addition was Christopher Douglas at Tue Apr 26 2016
## Releases:
- Last release was 1.3.0 on Mon Apr 23 2018
## JIRA activity:
- 2 JIRA tickets created in the past quarter
- 2 JIRA tickets closed/resolved in the past quarter
## Commit activity:
- 2 commits in the past quarter
- 1 code contributor in the past quarter
## Github PR activity:
- 2 PRs opened on Github in the past quarter
- 2 PRs closed on Github in the past quarter
-----------------------------------------
Attachment AV: 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 (21 days ago)
There are currently 41 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).
- No new committers were added.
## Project Activity:
In the first few weeks post-graduation, there has been a focus on executing
the transfer of the project's resources out of the Incubator. At graduation,
the project owned 52 github repos; an initial wave of 28 have been renamed and
we are in the midst of updating associated build tasks, cross-links, etc. to
reflect the renaming. A community discussion to identify inactive github repos
that should be archived has been started (most likely about a dozen will be
archived). We anticipate completing the transfer of resources before the
September board report is due.
A "standalone" OpenWhisk jar that enables easy local execution of the
OpenWhisk programming model is nearing completion and has generated community
excitement. We anticipate making a release within the next month to make this
capability widely available. It will greatly simplify the "kick the tires"
experience of trying OpenWhisk by potentially interested users.
## Community Health:
Overall community health is good. There is active technical discussion and
development activity across the various levels of the OpenWhisk stack.
-----------------------------------------
Attachment AW: Report from the Apache Perl Project [Philippe Chiasson]
--- mod_perl --
Apache-Test 1.41 was released on July 11th 2019
-- Activity --
Since the last report was late, there is very little activity to report
to the board this time around.
There was a flurry of activity surrounding the successfull testing and
release of Apache-Test 1.41.
-- Users --
The mod_perl users list is seeing little activity, as usual.
Patches and bug reports are few, but keep on coming.
-- Commiters --
Currently 22 committers.
No new changes to the committer base since last report.
Last Commiter addition was Jan Kaluza in April 2013
-- PMC --
Currently 11 PMC members.
No new PMC members added in the last 3 months
Last PMC addition was Steve Hay on Wed Feb 29 2012
-----------------------------------------
Attachment AX: Report from the Apache Phoenix Project [Josh Elser]
## Description:
The mission of Phoenix is the creation and maintenance of software related to
High performance relational database layer over Apache HBase for low latency
applications
## Issues:
No issues at this time!
## Membership Data:
Apache Phoenix was founded 2014-05-20 (5 years ago)
There are currently 44 committers and 30 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 Chenglei on 2019-04-09.
+ New PMC member(s) under vote presently.
- Kadir Ozdemir was added as committer on 2019-05-30
## Project Activity:
The community continues to have two active release lines: 4.x and 5.x.
Since the last report, 4.14.2 was released and a 4.14.3 has its second release
candidate out for a vote now.
The 5.x release line has slowed since the initial 5.0.0 release. There was
interest expressed in both 5.0 and 5.1 releases happening, but there is still
significant progress required to get to a first release candidate for either.
One impediment around the 4.x and 5.x release lines was ensuring that code
changes make it to all relevant release branches. This continues to be an
operational challenge for Phoenix as supporting a wide breadth of
compatibility for Apache Hadoop and Apache HBase versions is challenging.
This challenge is constantly being worked. For example, one community member
took the time to re-vamp our automated testing on the ASF Jenkins which now
shows largely passing test results, whereas the test results were essentially
noise (no meaningful data could be parsed from the job output).
On top of release stabilization, we can also be proud of a new significant
feature (PHOENIX-5156 on ASF Jira) which took roughly 6 months to design,
iterate, and commit. This is the hallmark of continuing innovation in Phoenix,
rearchitecting one of the major enticing features of Phoenix to be more stable
for our users.
## Community Health:
Phoenix continues to be an active community with a strong core committership.
Mailing list traffic, Jira issue activity, and commits are up (at least
double-digit percents) over the last quarter.
We did have a rather negative thread[1] on our user list since the last report
in which a number of users expressed dissatisfaction with Phoenix. It is
frustrating to have individuals come to your project's list, ultimately
soliciting "what should I use instead?". Perhaps this is a good reminder to
take a step back and make sure we are doing enough as a community to help make
those who are not committers successful. However, as with all internet-based
communities, I'm sure there are some hyper-critical individuals on our lists
who aren't looking for a solution from Phoenix.
[1] https://s.apache.org/44hy7
-----------------------------------------
Attachment AY: Report from the Apache POI Project [Dominik Stadler]
Report from the Apache POI committee [Dominik Stadler]
## Description:
- Apache POI is a Java library for reading and writing Microsoft Office file
formats
The Apache POI PMC also handles bugfixes for the XMLBeans project: XMLBeans
is a tool that allows you to map XML files to generated Java classes via
XML Schema definitions.
## Issues:
- There are no issues requiring board attention at this time
## Activity:
- No new release in this quarter, but a bugfix-release 4.1.1 or 4.2.0 is
discussed, some changes/enhancements in various areas were performed, one
regression for memory usage of XSSF were analyzed, but not yet
fixed/circumvented.
Early testing of JDK 13 was finished and some pre-testing of JDK 14
started.
## Health report:
- There are some ongoing discussions with users about features/behavior which
indicates that the popularity of Apache POI is still high. Questions via
email or on Stackoverflow usually get answers quickly.
Activity from committers was rather low, some developers seem to be tied up
with other stuff right now, still not critical, but active developer base
should be expanded again when potential committers show up on the mailing
lists.
Bug influx was moderate this quarter, bug-numbers increased a bit, some bug
influx and some could be fixed, but overall the rate of creation is a bit
higher than resolving, also due to some invalid bugs being entered which
need to be analyzed/triaged as well.
### XMLBeans
- Some work continued on the buildsystem and JDK 9+ support of XMLBeans,
however not much of it landed in SVN yet.
Bug influx for XMLBeans is very low because it is a stable project in
maintenance-mode.
## PMC changes:
- Currently 31 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Vladislav Galas on Sun Dec 30 2018
## Committer base changes:
- Currently 38 committers.
- No new committers added in the last 3 months
- Last committer addition was Vladislav Galas at Wed Dec 26 2018
## Releases:
- Last release was 4.1.0 on Mon Apr 08 2019
## Mailing list activity:
- Overall a few unsubscribtions, no apparent reason, user base still fairly
large and active
- dev@poi.apache.org:
- 217 subscribers (down -4 in the last 3 months):
- 354 emails sent to list (507 in previous quarter)
- general@poi.apache.org:
- 125 subscribers (up 1 in the last 3 months):
- 0 emails sent to list (6 in previous quarter)
- user@poi.apache.org:
- 559 subscribers (down -3 in the last 3 months):
- 52 emails sent to list (51 in previous quarter)
## Bugzilla Statistics:
### Apache POI
- 37 Bugzilla tickets created in the last 3 months
- 25 Bugzilla tickets resolved in the last 3 months
- 539 bugs are open overall (+11)
- Having 150 enhancements (+3)
- Thus having 389 actual bugs (+8)
- 89 of these are waiting for feedback (+1)
- Thus having 300 actual workable bugs (+7)
- 4 of the workable bugs have patches available (+-0)
- Distribution of workable bugs across components: {HSSF=81, XSSF=76, SS
Common=40, HWPF=38, XWPF=22, SXSSF=11, XSLF=8, POI Overall=7, POIFS=4,
HPSF=3, HSMF=3, OPC=2, XDDF=2, HPBF=1, HSLF=1, SL Common=1}
### Apache XMLBeans
- 172 open issues (+-0)
- Bug 128 (+-0)
- Improvement 22 (+-0)
- New Feature 18 (+-0)
- Wish 4 (+-0)
-----------------------------------------
Attachment AZ: Report from the Apache Qpid Project [Robert Gemmell]
Apache Qpid is a project focused on creating software based on the
Advanced Message Queuing Protocol (AMQP), currently providing a protocol
engine library, message brokers written in C++ and Java, a message router,
and client libraries for C, C++, Go, Java/JMS, Python, and Ruby.
# Releases:
- Qpid Proton 0.28.0 was released on 10th May 2019.
- Qpid JMS 0.42.0 was released on 10th May 2019.
- Qpid Broker-J 7.1.3 was released on 14th May 2019.
- Qpid JMS AMQP 0-x 6.3.4 was released on 17th May 2019.
- Qpid Proton-J 0.33.1 was released on 3rd June 2019.
- Qpid JMS 0.43.0 was released on 7th June 2019.
- Qpid Dispatch 1.8.0 was released 11th June 2019.
- Qpid JMS 0.44.0 was released on 2nd July 2019.
- Qpid Broker-J 7.0.8 was released on 8th July 2019.
- Qpid Broker-J 7.1.4 was released on 8th July 2019.
- Qpid Proton-J 0.33.2 was released on 13th August 2019.
# Community:
- The main user and developer mailing lists continue to be active and JIRAs
are being raised and addressed in line with prior activity levels.
- There were no new committer additions in this quarter.
The most recent new committer is Jiri Danek, added on 23rd February 2019.
- There were no new PMC additions in this quarter.
The most recent new PMC member is Ganesh Murthy, added on 30th Jan 2017.
# Development:
- Proton-C and its language bindings had their 0.28.0 release,
incorporating various bug fixes and improvements, including some internal
rework of the Python bindings. A candidate for a 0.29.0 release with
various fixes and improvements is currently under vote.
- The AMQP 1.0 JMS client had its 0.42.0 - 0.44.0 releases with various bug
fixes and improvements. Work continues on more, with aim to prepare a
0.45.0 release in the coming days.
- Dispatch router had its 1.8.0 release, and work is under way toward a
1.9.0 with various bug fixes and improvements, including some work on
increasing performance.
- Broker-J had 7.0.8 and 7.1.3 + 7.1.4 releases, adding various bug fixes
and improvements. Work continues on more toward 8.0.0, with backports to
the 7.1.x line as appropriate.
- Proton-J had 0.33.1 and 0.33.2 bug fix releases. Work continues on more
fixes and improvements as needed for its dependent components.
# Issues:
There are no Board-level issues at this time.
-----------------------------------------
Attachment BA: Report from the Apache REEF Project [Sergiy Matusevych]
## Description:
- Apache REEF (Retainable Evaluator Execution Framework) is a library for
developing portable applications for cluster resource managers such as
Apache Hadoop YARN or Apache Mesos.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- Updating the project dependencies for a minor release in September.
- Finishing work on .Net elastic broadcast. Planning a new release this year.
## Health report:
- The engagement from the community has been declining perhaps because the
codebase has been stable.
- We've decided to do a minor release this quarter to update the project's
dependencies.
- Work continues in the elastic broadcast pull request (600+ comments/fixes).
There was a delay in this effort due to the principal committer's paternity
leave; We will resume that work after publishing a minor release of REEF.
- We plan to issue a new release as soon as we merge the elastic group
communication into master.
## PMC changes:
- Currently 22 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Doug Service on Thu Sep 28 2017
## Committer base changes:
- Currently 35 committers.
- No new committers added in the last 3 months
- Last committer addition was Scott Inglis at Thu Sep 27 2018
## Releases:
- Last release was 0.16 on Wed Aug 09 2017.
- Release 0.16.1 planned for Sep 2019.
- Release 0.17 planned before the end of year 2019.
## Mailing list activity:
- dev@reef.apache.org:
- 86 subscribers (up 0 in the last 3 months):
- 8 emails sent to list (9 in previous quarter)
- user@reef.apache.org:
- 20 subscribers (up 0 in the last 3 months):
- 0 emails sent to list (0 in previous quarter)
## JIRA activity:
- 1 JIRA tickets created in the last 3 months
- 0 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment BB: Report from the Apache River Project [Peter Firmstone]
## Description:
- Apache River provides a platform for dynamic discovery and lookup
search of network services. Services may be implemented in a number
of languages, while clients are required to be jvm based (presently at
least), to allow proxy jvm byte code to be provisioned dynamically.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- Minimal activity at present, initial work on the modular build structure
has commenced. The current monolithic build is complex, with it's own
build tool classdepandjar, it adds complexity for new developers. In recent
months I have had work committments that have limited my ability to
integrate the modular build. The other committers are waiting for the
modular build and I have done a lot of work on this locally, this work has
been a significant undertaking integrating the works of Dennis Reedy, Dan
Rollo and myself. This is also a mature codebase, having been in
development since the late 1990's.
Release roadmap:
River 3.1 - Modular build restructure (& binary release)
River 3.2 - Input validation 4 Serialization, delayed unmarshalling&
safe ServiceRegistrar lookup service.River 3.3 - OSGi support
## Health report:
- River is a mature codebase with existing deployments, it was primarily
designed for dynamic discovery of services on private networks. IPv4 NAT
limitations historically prevented the use of River on public networks,
however the use of IPv6 on public networks removes these limitations. Web
services evolved with the publish subscribe model of todays internet, River
has the potential to dynamically discover services on IPv6 networks, peer to
peer, blurring current destinctions between client and server, it has the
potential to address many of the security issues currently experienced with
IoT and avoid any dependency on the proprietary cloud for "things".
- Future Direction:
* Target IOT space with support for OSGi and IPv6 (security fixes
required prior to announcement)
* Input validation for java deserialization - prevents DOS and
Gadget attacks.
* IPv6 Multicast Service Discovery (River currently only supports
IPv4 multicast discovery).
* Delayed unmarshalling for Service Lookup and Discovery (includes
SafeServiceRegistrar mentioned in release roadmap), so
authentication can occur prior to downloading service proxy's,
this addresses a long standing security issue with service lookup
while significantly improving performance under some use cases.
* Security fixes for SSL endpoints, updated to TLS v1.2 with removal
of support for insecure cyphers.
* Secure TLS SocketFactory's for RMI Registry, uses
the currently logged in Subject for authentication.
The RMI Registry still plays a minor role in service activation,
this allows those who still use the Registry to secure it.
* Maven build to replace existing ant built that uses
classdepandjar, a bytecode dependency analysis build tool.
* Updating the Jini specifications.
## PMC changes:
- Currently 12 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Dan Rollo on Fri Dec 01 2017
## Committer base changes:
- Currently 16 committers.
- No new committers added in the last 3 months
- Last committer addition was Dan Rollo at Thu Nov 02 2017
## Releases:
- Last release was River-3.0.0 on Thu Oct 06 2016
## Mailing list activity:
- dev@river.apache.org:
- 90 subscribers (up 0 in the last 3 months):
- 4 emails sent to list (4 in previous quarter)
- user@river.apache.org:
- 90 subscribers (up 0 in the last 3 months):
- 1 emails sent to list (1 in previous quarter)
## JIRA activity:
- 1 JIRA tickets created in the last 3 months
- 0 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment BC: Report from the Apache RocketMQ Project [Xiaorui Wang]
## Description:
Apache RocketMQ is a distributed messaging and streaming platform with low
latency, high performance and reliability, trillion-level capacity and
flexible scalability.
## Issues:
Some of the new PMC members, even including release manager,
make some unofficial release without notice to release packages
to apache's dist directory. RocketMQ will soon release docker
images, which needs to be avoided. The ASF is supposed to
make it easier for developers to develop. It is not
supposed to be creating red tape to guard the entrance to
the hallowed halls. However, according to the summary of
several release managers, for China, Networking instability
is the biggest obstacle, such as when typing the command
"mvn -Psigned_release release:perform -Darguments="-DskipTests"
" or "svn commit".
## Membership Data:
Apache RocketMQ was founded 2017-09-20 (2 years ago)
There are currently 22 committers and 13 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
Community changes, past quarter:
- ShannonDing was added to the PMC on 2019-06-13
- Kevin Wang was added as committer on 2019-06-29
- John Xu was added as committer on 2019-06-13
- Qipeng Li was added as PMC on 2019-08-12
## Project Activity:
- ROCKETMQ-4.5.2 was released on 2019-08-12.
- Apache RocketMQ Meetup Beijing, China ended
on Sat Jun. 29 2019, 140+ spectators attended.
- Apache RocketMQ & Apache Flink Shanghai, China
ended on Sat Jul. 6 2019, 160+ spectators attended.
- Apache RocketMQ Meetup Shenzhen, China
ended on Sat Jul. 27 2019, 150+ spectators attended.
## Community Health:
Potentially useful observations on community health
are clearly show in the new version of the ASF Board
Report Wizard. So, there is no need to mention it here.
In the past year, the community focused on the
core feature development of the messging industry
and the development of multi-language projects.
At present, several stable versions of each language
are released, and there are also good use cases
in some companies. Overall community health
is good. We have been performing extensive outreach
to related projects, such as embracing k8s, microservice capability enhancement.
-----------------------------------------
Attachment BD: Report from the Apache Roller Project [David M. Johnson]
## Description:
Apache Roller is a full-featured, Java-based blog server that works well on
Tomcat and MySQL, and is known to run on other Java servers and relational
databases. Latest release is 5.2.4 and the ASF blog site at blogs.apache.org
runs on Roller 5.2.4 Tomcat and MySQL.
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache Roller was founded 2007-02-20 (12 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:
- Aditya Sharma was added to the PMC on 2019-08-03
- Aditya Sharma was added as committer on 2019-05-19
## Project Activity:
The Roller community fixed a security vulnerability, fixed a series of bugs
and made a 5.2.3 release on July 12. There was a regression that broke Roller's
rich text editor, so the community made a 5.2.4 release on July 22.
The blogs.apache.org site has been updated to the latest release.
The Roller web UI has been rewritten to use Twitter Bootstrap via the
Struts 2 Bootstrap plugin. The Roller code base has been updated to
run in Java 11. All of this work has been merged to master and the
next step is a Roller 6.0.0 release. Roller 6 will be a major
revision to Roller, but it will have the same database schema as
Roller 5 and so should be an easy and no-risk upgrade.
## Community Health:
There has been an uptick in Roller activity with new committer and PMC
member Aditya Sharma. Two releases and major features (Bootstrap UI
+ Java 11 support) were merged to master. Also a contributor has provided
the project with a set of new logos to consider. These are good signs
for community health.
Here are some stats that back that up:
* dev@roller.apache.org had a 785% increase in traffic in the past
quarter (124 emails compared to 14)
* 9 issues opened in JIRA, past quarter (80% increase)
* 7 issues closed in JIRA, past quarter (16% increase)
* 37 commits in the past quarter (146% increase)
* 5 code contributors in the past quarter (150% increase)
* 7 PRs opened on GitHub, past quarter (133% increase)
* 6 PRs closed on GitHub, past quarter (20% increase)
-----------------------------------------
Attachment BE: Report from the Apache Santuario Project [Colm O hEigeartaigh]
## Description:
The mission of Santuario is the creation and maintenance of software related to
XML Security in Java and C++
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache Santuario was founded 2006-06-27 (13 years ago)
There are currently 17 committers and 7 PMC members in this project.
The Committer-to-PMC ratio is roughly 9:4.
Community changes, past quarter:
- No new PMC members. Last addition was Daniel Kulp on 2018-10-01.
- No new committers. Last addition was Daniel Kulp on 2018-10-01.
## Project Activity:
There was one new release over the last quarter - Apache Santuario - XML
Security for Java 2.1.4 was released on 2019-07-20. This release fixed a
few bugs and included a fix for a security issue which will be
published shortly.
## Community Health:
Apache Santuario is a mature and stable project that has reached a point
where not too many fixes are required, as it is a set of implementations
of some specifications that are quite old now. It is actively managed by
the PMC.
-----------------------------------------
Attachment BF: Report from the Apache Serf Project [Branko Čibej]
Report from the Apache Serf Project [Branko Čibej]
## Description:
The serf library is a high performance C-based HTTP client library built
upon the Apache Portable Runtime (APR) library. Serf is the default client
library of Apache Subversion, Apache OpenOffice and mod_pagespeed.
## Issues:
Activity on the project seems to have come to a halt in the last year.
## Activity:
There has been no move towards getting Serf 1.4.0 released in the last nine
months. A release candidate for internal testing was produced, but never
released. The last Serf release is now 3 years old.
The only active user of Serf seems to be Apache Subversion. Apache
OpenOffice uses a version of Serf that was released before Serf became a
Apache TLP.
## Health report:
The last commit in the public repository was made on 11th June, being a
minor fix to the build scripts. The commit previous to that was made in
November 2018.
## PMC & Committer changes:
Currently 13 PMC members and 13 committers.
- No new committers added in the last 3 months.
- Last new committer added in April 2017 (Evgeny Kotkov).
- Last new PMC member added in September 2018 (Branko Čibej).
## Releases:
Apache Serf 1.3.9 was released on Thu Sep 01 2016
## Mailing list and Jira activity:
The last message on the dev@ mailing list is three months old. It's a
follow-up from a discussion with a user on IRC who had trouble building our
sources.
-----------------------------------------
Attachment BG: Report from the Apache ServiceComb Project [Willem Ning Jiang]
## Description:
- A microservice framework that provides a set of tools and components to
make development and deployment of cloud applications easier.
## Issues:
- There are no issues requiring board attention at this time
## Activity:
- ServiceComb PMC is prepare a new around release of ServiceComb this month.
- We just add a new Committer last month.
## Health report:
- The mails and development activity are as good as usual.
## PMC changes:
- Currently 17 PMC members.
- Haishi Yao was added to the PMC on Mon Jun 10 2019
## Committer base changes:
- Currently 21 committers.
- New committers:
- MabinGo was added as a committer on Wed Jul 31 2019
- Xiaoliang Tian was added as a committer on Thu Jun 20 2019
## Releases:
- ServiceComb Java-Chassis 1.2.1 was released on Sun May 19 2019
## Mailing list activity:
- Current we found more and more user are using github issue to interact with
the development team. Here is the discussion[1] about enable the issue to
interact with the users directly.
[1]https://lists.apache.org/thread.html/3dd98077a6631cb005a2d7cda912789fc7c0b01756eba1d9008a7e76@%3Cdev.servicecomb.apache.org%3E
- Current we just redirect all the github related message to
committes@servicecomb.apache.org through GitBox
- This month there are 1320 emails sent by 51 people, divided into 798 topics.
Top 5 members: GitBox: 712 email(s), ningjiang@apache.org: 199 email(s), Lei
Zhang (JIRA): 57 email(s), Willem Jiang (JIRA): 49 email(s),
zhanglei@apache.org: 40 email(s)
- dev@servicecomb.apache.org:
- 126 subscribers (up 9 in the last 3 months):
- 242 emails sent to list (234 in previous quarter)
- issues@servicecomb.apache.org:
- 8 subscribers (up 0 in the last 3 months):
- 456 emails sent to list (547 in previous quarter)
## JIRA activity:
- 142 JIRA tickets created in the last 3 months
- 74 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment BH: Report from the Apache SIS Project [Martin Desruisseaux]
## Description:
Apache Spatial Information System (SIS) is a Java library for developing
geospatial applications. SIS enables better representation of spatial
objects for searching, archiving, or other relevant spatial needs.
The base of the SIS library is modeled according international standards
published jointly by the Open Geospatial Consortium (OGC) and the
International Organization for Standardization (ISO).
## Issues:
Latest release (0.8) was in November 2017. I wrote in reports for about one
year that SIS 1.0 release will come soon, but it has not yet happened. Apache
SIS is receiving active development, but most work has been for new
functionalities considered critical for some clients; we have been able to
allocate resources only a few weeks for preparing the release. The blocking
point is to resolve compatibility issues for all Java versions from 8 to 13.
More details in the "activity" section.
## Membership Data:
Apache SIS was founded 2012-09-19 (7 years ago)
There are currently 22 committers and 20 PMC members in this project.
The Committer-to-PMC ratio is roughly 6:5.
Community changes, past quarter:
- No new PMC members. Last addition was Johann Sorel on 2017-09-07.
- Alexís Manin was added as committer on 2019-07-05
## Project Activity:
Developments in this quarter were mostly about improvements in raster data
support (coverage), tuning the API for reading/writing geospatial resources,
and spatial filters applied in queries. Work is starting in map display
capabilities (portrayal). Those core GIS concepts bring Apache SIS to a higher
level compared to previous functionalities, which explain the slight increase
in committers diversity (see "community health" section).
Regarding the SIS 1.0 release, some work has been done in June. This work was
about adjusting above-cited API in the hope to avoid need for API changes
after the release. In addition a new committer (Alexis Manin) provided a patch
for resolving a blocking compatibility issue with Java 11+, but we may want to
do a Maven profile for Java 8 before to apply that patch.
We will miss the geospatial track at ApacheCon this year, but George Percivall
from OGC accepted to insert some slides about Apache SIS in his presentation.
We made a presentation about Apache SIS to the Vietnamese space agency (VNSC)
and to some students of the Vietnam National University.
## Community Health:
We got an increase of email traffic in last quarter, but actually those
numbers fluctuate a lot from quarter-to-quarter and can not be taken as a
long-term trend yet. The most important number is that we had 4 code
contributors this quarter and that those contributors have done an increasing
amount of commits. Apache SIS is still a project with ~95% of the commits done
by a single contributor, but we hope that the recent increase in amount of
other commits will be a long term trend for the reasons cited in the "project
activity" section.
-----------------------------------------
Attachment BI: Report from the Apache Spark Project [Matei Alexandru Zaharia]
Apache Spark is a fast and general engine for large-scale data processing. It
offers high-level APIs in Java, Scala, Python and R as well as a rich set of
libraries including stream processing, machine learning, and graph analytics.
Project status:
- Discussions are continuing about our next feature release, which will
likely be Spark 3.0, on the dev and user mailing lists. Some key questions
include whether to remove various deprecated APIs, and which minimum
versions of Java, Python, Scala, etc to support. There are also a number of
new features targeting this release. We encourage everyone in the community
to give feedback on these discussions through our mailing lists or issue
tracker.
- We announced a plan to stop supporting Python 2 in our next major release,
as many other projects in the Python ecosystem are now dropping support
(https://spark.apache.org/news/plan-for-dropping-python-2-support.html).
- We added three new PMC members to the project in May: Takuya Ueshin, Jerry
Shao and Hyukjin Kwon.
- There is an ongoing discussion on our dev list about whether to consider
adding project committers who do not contribute to the code or docs in the
project, and what the criteria might be for those. (Note that the project
does solicit committers who only work on docs, and has also added
committers who work on other tasks, like maintaining our build
infrastructure).
Trademarks:
- We are continuing engagement with various organizations.
Latest releases:
- May 8th, 2018: Spark 2.4.3
- April 23rd, 2019: Spark 2.4.2
- March 31st, 2019: Spark 2.4.1
- Feb 15th, 2019: Spark 2.3.3
Committers and PMC:
- The latest committer was added on Jan 29th, 2019 (Jose Torres).
- The latest PMC members were added on May 21st, 2019 (Jerry Shao, Takuya
Ueshin and Hyukjin Kwon).
-----------------------------------------
Attachment BJ: Report from the Apache Subversion Project [Stefan Sperling]
Apache Subversion exists to be universally recognized and adopted as
an open-source, centralized version control system characterized by
its reliability as a safe haven for valuable data; the simplicity of
its model and usage; and its ability to support the needs of a wide
variety of users and projects, from individuals to large-scale
enterprise operations.
* Board Issues
There are no Board-level issues of concern.
* Community
The Subversion development community is fairly quiet these days. A
small trickle of development is ongoing. The community usually
responds to bug reports and is willing to help the reporter or any
other volunteer to develop a fix. However, in many cases there is no
such volunteer, and those bug reports are filed but often remain
unresolved.
In July 2019, a handful of developers has managed to put new releases
out the door. Concerns over potential lack of testing and release
signatures from PMC members were raised beforehand, but these problems
did not materialize. Regardless, the project would do better with more
active developers. The good news is that these issues are being openly
discussed on our mailing lists, with even non-PMC members contributing
to these discussions.
Our user support forums (Email and IRC) receive questions and answers
regularly.
No new committers were added since the one reported in February.
* Releases
Subversion 1.12.2, 1.10.6, and 1.9.12 were released on July 24 2019.
These releases contain fixes for two security issues, CVE-2018-11782
and CVE-2019-0203 (these affect Subversion 'svnserve' servers only.)
We are currently discussing the possibility of dropping support for
the 1.9 release series.
Subversion 1.11 is no longer supported.
* Delayed patching of known security issues
Patches for the pending security issues mentioned in the previous
report have now been released.
-----------------------------------------
Attachment BK: Report from the Apache Syncope Project [Francesco Chicchiriccò]
## Description:
Apache Syncope is an Open Source system for managing digital identities in
enterprise environments.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
Small maintenance work around 2_0_X and 2_1_X branches, we are at work to
implement the many features planned for next stable version 3.0.0, in the
master branch.
## Health report:
Users keep asking for basic and advanced features and customization in user@
and are eventually getting supported by the community.
We have been notified of some people submitting their ICLAs with reference to
Syncope, we are eagerly waiting for their contributions.
We are seeing a small increment in both users@ and dev@ subscribers, despite
the relative calm with message exchange.
## PMC changes:
- Currently 11 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Matteo Alessandroni on Fri Dec 22 2017
## Committer base changes:
- Currently 23 committers.
- No new committers added in the last 3 months
- Last committer addition was Dima Ayash at Mon Jul 09 2018
## Releases:
- 2.0.13 was released on Fri Apr 19 2019
- 2.1.4 was released on Fri Apr 19 2019
-----------------------------------------
Attachment BL: Report from the Apache SystemML Project [Jon Deron Eriksson]
## Description:
SystemML provides declarative large-scale machine learning (ML) that aims at
flexible specification of ML algorithms and automatic generation of hybrid
runtime plans ranging from single node, in-memory computations, to distributed
computations such as Apache Hadoop MapReduce and Apache Spark.
## Issues:
Project activity has dropped off significantly this quarter.
## Membership Data:
Apache SystemML was founded 2017-05-17 (2 years ago)
There are currently 26 committers and 23 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:6.
Community changes, past quarter:
- No new PMC members. Last addition was Arvind Surve on 2017-05-17.
- No new committers. Last addition was Guobao Li on 2018-08-29.
## Project Activity:
Activity has dropped significantly.
- There were 3 emails on the dev list this quarter.
- There has been only 1 commit since May.
- No pull requests have been opened or closed this quarter.
The most recent release was 1.2.0 on Aug 24, 2018.
## Community Health:
The SystemML community currently is unhealthy.
Email activity appears to indicate a declining interest in the project.
Activity has dropped off from the two most active committers to the
project in the last year (114 of the 135 total commits). This is concerning
in terms of community health because it will make it difficult to review
new contributions without the assistance of existing committers with a
deep knowledge of the project.
## Answers to Board Questions:
mk: I notice you have some very old pull requests that haven't
received feedback. j143-bot in particular seems to be getting
"starved". Do you have enough active committers to handle
contributions from non-committers?
Great question. I believe j143-bot/j143-zz/j143 all refer to one of our
most active committers (with over 30 commits) in the past 2 years. I
believe the SystemML community has done a great job of welcoming
contributions from both committers and non-committers in the past. However,
I do believe this will be difficult to do in the future (not enough active
committers) if the current activity trend continues.
-----------------------------------------
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:
There are no issues requiring board attenttion.
## Membership Data:
Apache Tapestry was founded 2006-02-14 (14 years ago)
There are currently 27 committers and 11 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 Kalle Korhonen on 2019-01-16.
- No new committers. Last addition was Balázs Palcsó on 2019-01-17.
## Project Activity:
Some work being done on the upcoming Tapestry 5.5.0 release. We expect it to
be released this year.
## Community Health:
Community size and participation was a little lower in the last quarter. This
should improve when the next version is released.
-----------------------------------------
Attachment BN: Report from the Apache TomEE Project [David Blevins]
## Description:
Apache TomEE delivers enterprise application containers and services based
on, but not limited to the Enterprise JavaBeans Specification and Java
Enterprise Edition Specifications.
## Activity
The community released 7.1.1 and 7.0.6 in June. These 2 releases are very
similar, with the key difference being 7.1.1 having a requirement of Java SE
8, and includes a number of MicroProfile specifications.
This is a maintenance release which includes dependency updates for Tomcat to
mitigate against:
CVE-2019-0232 (RCE via CGI Servlet)
CVE-2019-0199 (DoS via HTTP/2)
CVE-2018-11784 (potential Open redirect attack)
These releases also include some key fixes for the CMP support, which is
based on dynamically translating CMP entity beans to JPA at deploy
time. Specifically the fixes address issues for users providing custom ORM
metadata in their applications.
Apache TomEE makes use of Commons-Daemon for its Windows service which has
seen recent updates to enable applications using UCRT to get correct
environment variables.
Work on Java 11 continues with intentions of releasing an Apache TomEE 8.0.0
final once complete.
## PMC changes:
- Currently 11 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Andy Gumbrecht on Tue Aug 11 2015
## Committer base changes:
- Currently 31 committers.
- Last committer added Roberto Cortez on Thu Sep 6 2018
- Cesar Hernandez invited to become a committer on July 1st 2019. Invitation
accepted so we'll proceed with legal requirements and then with the
announcement. Cesar started contributing on the mailing list in October
2018. He did some great contributions with examples, documentation. But
more important he has been key in terms of enabling other contributors. He
is responsive on the mailing list and he's also the most active in
there. He's very welcoming and helps reviewing PRs.
## Releases:
- Apache TomEE 8.0.0-M3 on May 29, 2019
- Apache TomEE 7.1.1 on June 21, 2019
- Apache TomEE 7.0.6 on June 21, 2019
-----------------------------------------
Attachment BO: Report from the Apache Traffic Control Project [David Neuman]
## Description:
The mission of Apache Traffic Control is the creation and maintenance of
software related to building, monitoring, configuring, and provisioning a large
scale content delivery network (CDN)
## Issues:
There are no issues requiring board attention at this time.
## Membership Data:
Apache Traffic Control was founded 2018-05-15 (a year ago)
There are currently 24 committers and 15 PMC members in this project.
The Committer-to-PMC ratio is 8:5.
Community changes, past quarter:
- No new PMC members. Last addition was Derek Gelinas on 2019-03-17.
- Jonathan Gray was added as committer on 2019-06-12
- Brennan Fieck was added as committer on 2019-07-26
## Project Activity:
- Planned a Content Delivery Track for ApacheCon NA
- Agreed to do a 3.1 release before our next major release. This release will
contain fixes for some regressions found in the 3.0.1 release as well as
some key performance improvements made since the 3.0.1 release was made.
- There has been a lot of discussion around a few new features, github
milestones, and LTS for our releases
- We have also agreed that it is time to start planning our next major
release, but we haven't nailed down a scope yet.
## Community Health:
The community is healthy. We have less commits and code contributors since our
last report, but we have had an increase in issues closed. This is due to
some of our key committers working on larger features and our community being
focused on product stability over new features. We also switched to a squash
and merge strategy for pull requests, which leads to less overall commits.
We have had conversations with several new users which is encouraging for the
overall diversity of our communities.
We are looking forward to having to getting the community together at
ApacheCon which always helps to inject enthusiasm into the project.
See below for specifics on mailing list and github activity:
- dev@trafficcontrol.apache.org had a 21% decrease in traffic in the past
quarter (167 emails compared to 209)
- 96 commits in the past quarter (-35% decrease)
- 16 code contributors in the past quarter (-51% decrease)
- 138 PRs opened on GitHub, past quarter (6% increase)
- 113 PRs closed on GitHub, past quarter (-15% decrease)
- 154 issues opened on GitHub, past quarter (31% increase)
- 51 issues closed on GitHub, past quarter (8% increase)
-----------------------------------------
Attachment BP: Report from the Apache Turbine Project [Georg Kallidis]
## Description:
The mission of Turbine is the creation and maintenance of software related to
a Java Servlet Web Application Framework and associated component library.
Turbine is a matured and well established framework that is used as the base
of many other projects. It allows experienced Java developers to quickly build
web applications.
## Issues:
The Turbine project has no board-level issues at this time.
## Membership Data:
Apache Turbine was founded 2007-05-16 (12 years ago)
There are currently 11 committers and 9 PMC members in this project.
The Committer-to-PMC ratio is roughly 6:5.
Community changes, past quarter:
- No new PMC members. Last addition was Jeffery Painter on 2017-11-12.
- No new committers were added.
## Project Activity:
Three releases were done: Turbine Core 5.0, Maven parent (build) component
and a fixed Fulcrum component. Ongoing discussion about cleaning up
components, git release of Turbine archetypes, site updates and how to define
upcoming Turbine Core 5.1.
Releases:
- Fulcrum Parser 2.0.1 was released on Tue Jul 30 2019
- Turbine 5.0 Core was released on Tue May 28 2019
- Turbine Parent 6 was released on Tue Jul 23 2019
## Community Health:
- The Turbine project's quarter activity has been mainly in the dev mailing
list with ongoing code changes on low/medium level.
- Providing a ready-to-use development environment, which is in preparation,
is still important as well as probably (more) svn 2 git migrations (to be
discussed). While Turbine might seem not to be up front from an outsiders
viewpoint (which any newcomer is at the beginning), considering, that we are
still using Avalon as a backbone, it is developed by at least three
active committers, and has potential with new web
features added to be an alternative to other java web frameworks with small
footprint.
-----------------------------------------
Attachment BQ: Report from the Apache Usergrid Project [Michael Russo]
## Description:
The mission of Usergrid is the creation and maintenance of software related to
The BaaS Framework you run
## Issues:
- There are no issues requiring board attention at this time.
## Membership Data:
Apache Usergrid was founded 2015-08-18 (4 years ago)
There are currently 28 committers and 25 PMC members in this project.
The Committer-to-PMC ratio is roughly 1:1.
Community changes, past quarter:
- No new PMC members. Last addition was Mike Dunker on 2016-01-18.
- No new committers. Last addition was Keyur Karnik on 2019-03-18.
## Project Activity:
- CI setup with ASF Jenkins in progress.
- Various Bugfixes around index querying and maintenance.
- Improved test stability.
- Experimentation with using newer versions(5.x) of Elasticsearch vs.
supported older version (1.7).
## Community Health:
Growth is flat. Some of the historical core contributors are no longer active
with the project. However, there is a new committer and additional interest
for modernizing Usergrid -- upgrading Cassandra to the latest version and
containerizing Usergrid. Getting the project to a healthier state will
continue to be a focus. This includes more discussion on the mailing lists,
better use of JIRA, and planning of a new release -- master branch is
currently stable and contains many stability fixes over the last release in
2016.
-----------------------------------------
Attachment BR: Report from the Apache Velocity Project [Nathan Bubna]
## Description:
The mission of Velocity is the creation and maintenance of software related to
A Java Templating Engine
## Issues:
There are no issues requiring board attention at this time.
## Membership Data:
Apache Velocity was founded 2006-10-24 (13 years ago)
There are currently 14 committers and 9 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:5.
Community changes, past quarter:
- No new PMC members. Last addition was Michael Osipov on 2017-07-27.
- No new committers. Last addition was Michael Osipov on 2017-01-30.
## Project Activity:
Several of the devs have been working on custom parser support to allow
configurable grammars. There have also been some contributions for
dependency security notices and the Maven build.
## Community Health:
Better than usual. Multiple contributors. One dev is still leading
the bulk of the work, but others are involved in feedback and oversight.
-----------------------------------------
Attachment BS: Report from the Apache Whimsy Project [Sam Ruby]
## Description:
The mission of Apache Whimsy is the creation and maintenance of software
related to tools that help automate various administrative tasks or information
lookup activities
## Issues:
There are no issues requiring board attention
## Membership Data:
Apache Whimsy was founded 2015-05-19 (4 years ago)
There are currently 10 committers and 9 PMC members in this project.
Community changes, past quarter:
- No new PMC members. Last addition was John D. Ament on 2017-06-11.
## Project Activity:
Some highlights for the quarter:
- We now have Travis testing of tools other than just the board agenda
- Experimental list-traffic and survey tools
- Secretary workbench workarounds to PGP keyserver issues
- Agenda updates to support Jakarta EE, D&I and new chair
- Support for TAC, Brand Management and D&I to maintain their own membership
- New APIs created to support reporter.apache.org
## Community Health:
While I, like others, have never been a fan of quoting numbers in this
section, the following reporter generated statistics caught my eye:
- 196 commits in the past quarter (44% decrease)
- 6 code contributors in the past quarter (40% decrease)
That's not bad for a "down" month. :-)
Sebb continues to outpace the rest of us. The board agenda tool continues to
have essentially only a single maintainer. This project has ample oversight.
-----------------------------------------
Attachment BT: Report from the Apache Xalan Project [Gary D. Gregory]
## Description:
Apache Xalan exists to promote the use of XSLT. We view XSLT (Extensible
Stylesheet Language Transformations) as a compelling paradigm that transforms
XML documents, thereby facilitating the exchange, transformation, and
presentation of knowledge. The ability to transform XML documents into usable
information has great potential to improve the functionality and use of
information systems. We intend to build freely available XSLT processing
components in order to engender such improvements.
## Issues:
There are no issues requiring board attention at this time.
## Membership Data:
Apache Xalan was founded 2004-09-30 (15 years ago)
There are currently 57 committers and 5 PMC members in this project.
The Committer-to-PMC ratio is roughly 8:1.
Community changes, past quarter:
- No new PMC members. Last addition was Bill Blough on 2019-02-19.
- No new committers. Last addition was Bill Blough on 2019-03-20.
## Project Activity:
- Xalan is undergoing a reboot.
- We have ported repositories from Subversion to Git.
- Research on builds is on-going but we cannot find folks with build knowledge.
## Community Health:
Despite the recent reboot, the community is not very active.
The dev mailing list shows some activity around both the C and Java components.
-----------------------------------------
Attachment BU: Report from the Apache Xerces Project [Michael Glavassevich]
-----------------------------------------
Attachment BV: Report from the Apache XML Graphics Project [Clay Leeds]
Apache XML Graphics Project Board Report
==================================
The Apache XML Graphics Project is responsible for software intended for the
creation & maintenance of the conversion of XML formats to graphical output &
related software components.
ISSUES FOR THE BOARD
=====================
No issues at present.
ACTIVITY
========
* Apache Batik 1.11
* Bug Fix for Apache FOP 2.3 to remove Avalon MERGE'd to TRUNK (Avalon is no longer
maintained & doesn't compile under Java 9)
PROJECT HEALTH REPORT
=======================
The level of community and developer activity remains at a consistent,
moderate, level with respect to the previous reporting period.
RECENT PMC CHANGES
==================
Currently 11 PMC members.
* Simon Steiner was added to the PMC on Tue Jan 19 2016
* Clay Leeds became XML Graphics PMC Chair on March 26, 2018
Committers
==========
Currently 21 committers.
* No new committers added in the last 3 months
* Last committer added was Matthias Reischenbacher at Wed May 13 2015
Most Recent Releases
====================
There were no releases in the last quarter.
* XMLGraphics Commons 2.3 was released on Mon May 14, 2018
* XMLGraphics FOP 2.3 was released on Mon May 14, 2018
* XMLGraphics Batik 1.11 was released on Wed Feb 13, 2019
= SUB PROJECTS =
================
XML GRAPHICS COMMONS
====================
Community activity was light, although there were a few bugs resolved.
New Release?
------------
There were no releases this quarter.
Latest Release
--------------
XML Graphics Commons 2.3 was released on Mon May 14, 2018
FOP
===
A number of patches have been processed into TRUNK and several bugs fixed.
New Release?
------------
* There were no releases this quarter.
* Bug Fix for FOP 2.3 to remove Avalon committed to TRUNK (no longer
maintained & doesn't compile under Java 9)
Latest Release
--------------
XML Graphics FOP 2.3 was released on Mon May 14, 2018
BATIK
=====
Apache Batik 1.11 was released on Wed Feb 13, 2019
New Release?
------------
* There were no releases this quarter.
* Apache Batik 1.11 was released on Wed Feb 13, 2019
Latest Release
--------------
* Apache Batik 1.11 was released on Wed Feb 13, 2019
-----------------------------------------
Attachment BW: Report from the Apache Zeppelin Project [Lee Moon Soo]
## Description:
- Apache Zeppelin is a collaborative data analytics and visualization tool
for general-purpose data processing systems.
## Issues:
- PMCs are trying to fix and announce security issues that have been
addressed and released.
## Activity:
- No new release in the last 3 months
## Health report:
- +2 new code contributors since last report. 281 total
## PMC changes:
- Currently 11 PMC members.
- Last PMC addition was Jeff Zhang on Thu Jan 25 2018
## Committer base changes:
- Currently 18 committers.
- Last committer addition was Xun Liu at April 18 2019
## Releases:
- 0.8.1 was released on Wed Jan 23 2019
- 0.8.0 was released on Wed Jul 18 2018
- 0.7.3 was released on Wed Sep 20 2017
- 0.7.2 was released on Mon Jun 12 2017
- 0.7.1 was released on Fri Mar 31 2017
- 0.7.0 was released on Sun Feb 05 2017
- 0.6.2 was released on Fri Oct 14 2016
- 0.6.1 was released on Aug 15 2016
- 0.6.0 was released on Jul 02 2016
- 0.5.6-incubating was released on Jan 22 2016
- 0.5.5-incubating was released on Nov 18 2015
- 0.5.0-incubating was released on Jul 23 2015
## Mailing list activity:
- users@zeppelin.apache.org:
- 108 emails sent to list ( 152 in previous quarter)
- dev@zeppelin.apache.org:
- 802 emails sent to list ( 783 in previous quarter)
## JIRA activity:
- 141 JIRA tickets created in the last 3 months
- 39 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment BX: Report from the Apache Griffin Project [William Guo]
## Description:
- Apache Griffin is an open source Data Quality solution for Big Data, which
supports both batch and streaming mode. It offers an unified process to
measure your data quality from different perspectives, helping you build
trusted data assets, therefore boost your confidence for your business.
## Issues:
- There are no issues requiring board attention at this time.
## Membership Data:
Apache Griffin was founded 2018-11-21 (9 months ago) There are currently 18
committers and 17 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 chemikadze on 2018-11-21.
- No new committers were added.
- A new committer has been invited and has accepted but the account is still
pending. We anticipate including this in our next report.
## Project Activity:
- Recent releases: 0.5.0 was released on 2019-04-10.
- Support JDBC connection to metastore.
- Support Kerberos Authentication when connecting through livy.
- Preparing the presentation for the coming ApacheCon Las Vegas.
## Community Health:
- dev@griffin.apache.org had a 22% decrease in traffic in the past quarter
(326 emails compared to 414)
- 28 issues opened in JIRA, past quarter (40% increase)
- 13 issues closed in JIRA, past quarter (44% increase)
- 16 commits in the past quarter (no change)
- 8 code contributors in the past quarter (14% increase)
- 22 PRs opened on GitHub, past quarter (10% increase)
- 18 PRs closed on GitHub, past quarter (-14% decrease)
-----------------------------------------
Attachment BY: Report from the Apache Lucene.Net Project [Shad Storhaug]
Apache Lucene.Net is a port of the Lucene search engine library, written in C#
and targeted at .NET runtime users.
== Summary ==
We have been stalled in the first half of 2019 with limited progress:
* New Website went live: http://lucenenet.apache.org/
* The team was looking at our CI options, the consensus was to try to get on
Azure DevOps
However, over the past few months the community has submitted pull requests to
patch some important stability and thread safety bugs. We also got enough of
ICU4J ported to support Lucene.Net, which has been an issue that has been
blocking progress for some time. The previous dependency (icu-dotnet) was both
extremely large and unstable, and was causing lots of issues with getting the
tests to run reliably.
We have set up CI on Azure DevOps, which has also addressed another
long-standing issue: the amount of time it takes to increment and test.
Parallel testing was setup to reduce the testing time from around 1 hour and
15 minutes to around 45 minutes. The new setup also allows us to test on Linux
and macOS for the first time.
We released 4.8.0-beta00006 this month with the patches the community provided
as well as some bugs that were newly discovered with the new CI process. The
Lucene.Net.ICU module is now feature-complete. There was a command line tool
named lucene-cli included in the binary distribution of beta00005 but this
time around it has been packaged up as a dotnet tool on NuGet so it can be
installed directly from the command line.
We are currently working on finishing up the test framework module. It was
previously ported, but the fact that it was meant to be an end-user module was
overlooked, so there are several issues to address to ready it for wide use.
We are also working on more automation for generating API documentation to
keep it in sync with releases.
== Releases ==
* Last Release 3.0.3 - Oct 2012
* Working toward 4.8.0 - Currently beta0006, released 2019-08-13
== People ==
* Last PMC Member added May 2017, Shad Storhaug (nightowl888)
* Last committer added Sept 2016, Shad Storhaug (nightowl888)
* PMC Chair rotated 20 June 2018 to Shad Storhaug (nightowl888)
== Statistics ==
As of 2019.08.19 Metric are as follows:
Release 3.0.3
* Lucene.Net 3.0.3: 2,507,308
* Lucene.Net.Contrib 3.0.3: 554,455
* Lucene.Net Contrib Spatial: 32,467
* Lucene.Net Contrib Spatial.NTS: 6,829
Beta 4.8.0-beta00005 (Published 10/24/2017)
* Lucene.Net: 155,313
* Lucene.Net.Analysis.Common: 142,723
* Lucene.Net.Analysis.Kuromoji: 4,484
* Lucene.Net.Analysis.Phonetic: 1,962
* Lucene.Net.Analysis.SmartCn: 541
* Lucene.Net.Analysis.Stempel: 1,090
* Lucene.Net.Benchmark: 507
* Lucene.Net.Classification: 1,030
* Lucene.Net.Codecs: 2,835
* Lucene.Net.Expressions: 5,577
* Lucene.Net.Facet: 7,369
* Lucene.Net.Grouping: 8,311
* Lucene.Net.Highlighter: 4,695
* Lucene.Net.ICU: 868
* Lucene.Net.Join: 7,624
* Lucene.Net.Memory: 8,121
* Lucene.Net.Misc: 6,035
* Lucene.Net.Queries: 125,839
* Lucene.Net.QueryParser: 119,881
* Lucene.Net.Replicator: 549
* Lucene.Net.Sandbox: 125,906
* Lucene.Net.Spatial: 4,615
* Lucene.Net.Suggest: 5,185
Beta 4.8.0-beta00006 (Published 08/13/2019)
* Lucene.Net: 133
* Lucene.Net.Analysis.Common: 98
* Lucene.Net.Analysis.Kuromoji: 50
* Lucene.Net.Analysis.Phonetic: 42
* Lucene.Net.Analysis.SmartCn: 42
* Lucene.Net.Analysis.Stempel: 44
* Lucene.Net.Benchmark: 36
* Lucene.Net.Classification: 41
* Lucene.Net.Codecs: 43
* Lucene.Net.Expressions: 41
* Lucene.Net.Facet: 44
* Lucene.Net.Grouping: 45
* Lucene.Net.Highlighter: 51
* Lucene.Net.ICU: 41
* Lucene.Net.Join: 46
* Lucene.Net.Memory: 57
* Lucene.Net.Misc: 49
* Lucene.Net.Queries: 90
* Lucene.Net.QueryParser: 90
* Lucene.Net.Replicator: 40
* Lucene.Net.Sandbox: 118
* Lucene.Net.Spatial: 42
* Lucene.Net.Suggest: 44
* lucene-cli: 49
------------------------------------------------------
End of minutes for the August 21, 2019 board meeting.
Index