Index
Links: 2023 - All years
- Original The Apache Software Foundation
Board of Directors Meeting Minutes
September 20, 2023
1. Call to order
The meeting was scheduled for 21:00 UTC and began at 21:02 when
a sufficient attendance to constitute a quorum was recognized by
the chair.
Other Time Zones: https://timeanddate.com/s/4359
The meeting was held via teleconference, hosted by the Secretary
via Zoom.
The #asfboard channel on the-asf.slack.com was used for backup.
2. Roll Call
Directors Present:
Rich Bowen
Shane Curcuru
Bertrand Delacretaz
Christofer Dutz
Sharan Foga - joined :03
Willem Ning Jiang
Justin Mclean
Craig L Russell
Sander Striker
Directors Absent:
none
Executive Officers Present:
Craig R. McClanahan
David Nalley
Matt Sicker
Ruth Suehle
Executive Officers Absent:
none
Guests:
Brian Proffitt
Daniel Gruno
Dave Fisher
David Blevins
Dirk-Willem van Gulik
Drew Foulks
Greg Stein
Henri Yandell
Tianqi Chen
3. Minutes from previous meetings
Published minutes can be found at:
http://www.apache.org/foundation/board/calendar.html
A. The meeting of July 19, 2023
See: board_minutes_2023_07_19.txt
Approved by General Consent.
B. The meeting of August 16, 2023
See: board_minutes_2023_08_16.txt
Approved by General Consent.
4. Executive Officer Reports
A. Board Chair [Sander Striker]
Due to personal circumstances I regrettably have little to report this
month.
We are a volunteer led organization, and I remain extremely grateful
for the time and energy everyone dedicates to the Foundation month
over month.
B. President [David Nalley]
I received confirmation of D&O Insurance Renewal
On a personal note, I am traveling intensely for the next ~6 weeks.
Additionally, please see Attachments 1 through 9.
C. Treasurer [Craig R. McClanahan]
Normal operations continue, nothing special to report.
D. Secretary [Matt Sicker]
In July, the secretary team received 49 ICLAs, 2 CCLAs, 1 software
grant, and 3 CoI affirmations.
In August, the secretary team received 59 ICLAs, 1 CCLA, and 4 CoI
affirmations.
The secretary would like to clarify that when individuals file an
ICLA, they may use a pen name as their public name if desired. Pen
names are subject to secretarial discretion; we will not accept
offensive names, impersonations, or names that cannot be written or
pronounced. The secretary will confirm with individuals filing under a
pen name that it is indeed their intention to do so as most times when
we receive ICLAs with what appear to be a pen name, this was done by
accident by confusing the public name field with a username field.
E. Executive Vice President [Ruth Suehle]
Budget is unusually tight this year for Community Over Code, mostly due to a tough year for sponsorships and tight budgets all around the industry. Hoping to come close to breaking even.
F. Vice Chair [Sharan Foga]
- Help chair with facilitation of various admin tasks
Executive officer reports approved as submitted by General Consent.
5. Additional Officer Reports
A. VP of W3C Relations [Andy Seaborne / Craig]
No report was submitted.
B. Apache Legal Affairs Committee [Roman Shaposhnik / Christofer]
See Attachment 11
C. Apache Security Team Project [Mark J. Cox / Sander]
See Attachment 12
@Bertrand: follow up with Mark about Zeppelin
D. VP of Jakarta EE Relations [Rob Tompkins / Rich]
No report was submitted.
Additional officer reports approved as submitted by General Consent.
6. Committee Reports
Summary of Reports
The following reports required further discussion:
# DeltaSpike [striker]
# OpenWebBeans [striker]
# Security Team [striker]
# TVM [jmclean]
# VCL [striker]
A. Apache Airflow Project [Bolke de Bruin / Sander]
See Attachment A
B. Apache Allura Project [David Philip Brondsema / Sharan]
See Attachment B
C. Apache Archiva Project [Olivier Lamy / Shane]
No report was submitted.
D. Apache Atlas Project [Madhan Neethiraj / Bertrand]
See Attachment D
E. Apache Axis Project [Robert Lazarski / Willem]
See Attachment E
F. Apache Bahir Project [João Boto / Justin]
See Attachment F
G. Apache Beam Project [Kenneth Knowles / Bertrand]
See Attachment G
H. Apache Bigtop Project [Yuqi Gu / Shane]
See Attachment H
I. Apache Bloodhound Project [Gary Martin / Shane]
See Attachment I
J. Apache BVal Project [Matthew Jason Benson / Sander]
See Attachment J
K. Apache Camel Project [Andrea Cosentino / Justin]
See Attachment K
L. Apache Cayenne Project [Michael Ray Gentry / Rich]
See Attachment L
M. Apache CloudStack Project [Rohit Yadav / Sharan]
See Attachment M
N. Apache Cocoon Project [Cédric Damioli / Craig]
No report was submitted.
O. Apache Commons Project [Gary D. Gregory / Willem]
See Attachment O
P. Apache Cordova Project [Jesse MacFadyen / Christofer]
See Attachment P
Q. Apache cTAKES Project [Pei Chen / Craig]
See Attachment Q
R. Apache Curator Project [Enrico Olivelli / Christofer]
See Attachment R
S. Apache Daffodil Project [Mike Beckerle / Willem]
See Attachment S
T. Apache DeltaSpike Project [Mark Struberg / Sander]
See Attachment T
@Christofer: follow up on a roll call for DeltaSpike
U. Apache Drill Project [Charles Givre / Bertrand]
See Attachment U
V. Apache Druid Project [Gian Merlino / Justin]
See Attachment V
W. Apache ECharts Project [Wenli Zhang / Shane]
See Attachment W
X. Apache Felix Project [Karl Pauls / Sharan]
See Attachment X
Y. Apache Flex Project [Harbs / Rich]
See Attachment Y
Z. Apache Flink Project [Robert Metzger / Justin]
See Attachment Z
AA. Apache Giraph Project [Dionysios Logothetis / Christofer]
No report was submitted.
AB. Apache Gobblin Project [Abhishek Tiwari / Bertrand]
See Attachment AB
AC. Apache Gora Project [Kevin Ratnasekera / Shane]
See Attachment AC
AD. Apache Guacamole Project [Mike Jumper / Willem]
See Attachment AD
AE. Apache Gump Project [Stefan Bodewig / Christofer]
See Attachment AE
AF. Apache Helix Project [Junkai Xue / Sharan]
See Attachment AF
AG. Apache Hive Project [Naveen Gangam / Craig]
No report was submitted.
AH. Apache Hop Project [Hans Van Akelyen / Rich]
See Attachment AH
AI. Apache HTTP Server Project [Joe Orton / Sander]
See Attachment AI
AJ. Apache Hudi Project [Vinoth Chandar / Bertrand]
See Attachment AJ
AK. Apache Iceberg Project [Ryan Blue / Shane]
See Attachment AK
AL. Apache Incubator Project [Justin Mclean]
See Attachment AL
AM. Apache IoTDB Project [Xiangdong Huang / Justin]
See Attachment AM
AN. Apache Jackrabbit Project [Marcel Reutegger / Craig]
See Attachment AN
AO. Apache Karaf Project [Jean-Baptiste Onofré / Christofer]
See Attachment AO
AP. Apache Kvrocks Project [Hulk Lin / Sander]
See Attachment AP
AQ. Apache Kyuubi Project [Kent Yao / Rich]
See Attachment AQ
AR. Apache Linkis Project [Shuai Di / Willem]
See Attachment AR
AS. Apache Lucene Project [Greg Miller / Sharan]
See Attachment AS
AT. Apache Lucene.Net Project [Shad Storhaug / Justin]
See Attachment AT
AU. Apache ManifoldCF Project [Karl Wright / Christofer]
No report was submitted.
AV. Apache Mnemonic Project [Gordon King / Shane]
No report was submitted.
AW. Apache MXNet Project [Sheng Zha / Shane]
No report was submitted.
AX. Apache Mynewt Project [Szymon Janc / Willem]
See Attachment AX
AY. Apache NetBeans Project [Geertjan Wielenga / Sharan]
See Attachment AY
AZ. Apache OFBiz Project [Jacopo Cappellato / Sander]
See Attachment AZ
BA. Apache Olingo Project [Michael Bolz / Justin]
See Attachment BA
BB. Apache OpenNLP Project [Jeff Zemerick / Craig]
See Attachment BB
BC. Apache OpenWebBeans Project [Mark Struberg / Rich]
See Attachment BC
BD. Apache Pig Project [Koji Noguchi / Bertrand]
No report was submitted.
BE. Apache Pinot Project [Kishore G / Sharan]
See Attachment BE
BF. Apache Pivot Project [Roger Lee Whitcomb / Sander]
No report was submitted.
BG. Apache PLC4X Project [Christofer Dutz]
See Attachment BG
BH. Apache Portable Runtime (APR) Project [Yann Ylavic / Bertrand]
See Attachment BH
BI. Apache Portals Project [Neil Griffin / Craig]
See Attachment BI
BJ. Apache Pulsar Project [Matteo Merli / Justin]
No report was submitted.
BK. Apache Ranger Project [Selvamohan Neethiraj / Christofer]
See Attachment BK
BL. Apache Royale Project [Piotr Zarzycki / Rich]
See Attachment BL
BM. Apache Santuario Project [Colm O hEigeartaigh / Willem]
See Attachment BM
BN. Apache SeaTunnel Project [Jun Gao / Shane]
See Attachment BN
BO. Apache Serf Project [Justin Erenkrantz / Sander]
No report was submitted.
BP. Apache ServiceMix Project [Krzysztof Sobkowiak / Justin]
See Attachment BP
BQ. Apache Shiro Project [Brian Demers / Rich]
See Attachment BQ
BR. Apache SINGA Project [Wang Wei / Christofer]
See Attachment BR
BS. Apache Sling Project [Robert Munteanu / Sander]
See Attachment BS
BT. Apache SpamAssassin Project [Sidney Markowitz / Craig]
See Attachment BT
BU. Apache Storm Project [P. Taylor Goetz / Bertrand]
See Attachment BU
BV. Apache Streams Project [Steve Blackmon / Willem]
No report was submitted.
BW. Apache Submarine Project [Kevin Su / Sharan]
See Attachment BW
BX. Apache Synapse Project [Isuru Udana / Shane]
No report was submitted.
BY. Apache Tomcat Project [Mladen Turk / Willem]
See Attachment BY
BZ. Apache TomEE Project [David Blevins / Sander]
See Attachment BZ
CA. Apache TVM Project [Tianqi Chen / Rich]
See Attachment CA
CB. Apache UIMA Project [Richard Eckart de Castilho / Sharan]
See Attachment CB
CC. Apache Unomi Project [Serge Huber / Craig]
See Attachment CC
CD. Apache VCL Project [Josh Thompson / Christofer]
See Attachment CD
@Christofer: pursue a roll call for VCL
CE. Apache Whimsy Project [Shane Curcuru]
See Attachment CE
CF. Apache Wicket Project [Andrea Del Bene / Shane]
See Attachment CF
CG. Apache Xerces Project [Michael Glavassevich / Bertrand]
See Attachment CG
CH. Apache Yetus Project [Allen Wittenauer / Justin]
See Attachment CH
CI. Apache ZooKeeper Project [Flavio Paiva Junqueira / Shane]
See Attachment CI
Committee reports approved as submitted by General Consent.
7. Special Orders
A. Terminate the Apache MXNet Project
WHEREAS, the Board of Directors deems it no longer in the best interest
of the Foundation to continue the Apache MXNet project due to
inactivity;
NOW, THEREFORE, BE IT RESOLVED, that the Apache MXNet 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 MXNet Project; and be it
further
RESOLVED, that the office of "Vice President, Apache MXNet" is hereby
terminated; and be it further
RESOLVED, that the Apache MXNet PMC is hereby terminated.
Special Order 7A, Terminate the Apache MXNet Project, was
approved by Unanimous Vote of the directors present.
B. Terminate the Apache Giraph Project
WHEREAS, the Project Management Committee of the Apache Giraph project
has arrived at a consensus 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 Giraph project due to
inactivity;
NOW, THEREFORE, BE IT RESOLVED, that the Apache Giraph 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 Giraph Project; and be it
further
RESOLVED, that the office of "Vice President, Apache Giraph" is hereby
terminated; and be it further
RESOLVED, that the Apache Giraph PMC is hereby terminated.
Special Order 7B, Terminate the Apache Giraph Project, was
approved by Unanimous Vote of the directors present.
C. Change the Apache Royale Project Chair
WHEREAS, the Board of Directors heretofore appointed Piotr Zarzycki
(piotrz) to the office of Vice President, Apache Royale, and
WHEREAS, the Board of Directors is in receipt of the resignation of
Piotr Zarzycki from the office of Vice President, Apache Royale, and
WHEREAS, the Project Management Committee of the Apache Royale project
has chosen by vote to recommend Yishay Weiss (yishayw) as the successor
to the post;
NOW, THEREFORE, BE IT RESOLVED, that Piotr Zarzycki is relieved and
discharged from the duties and responsibilities of the office of Vice
President, Apache Royale, and
BE IT FURTHER RESOLVED, that Yishay Weiss be and hereby is appointed to
the office of Vice President, Apache Royale, to serve in accordance
with and subject to the direction of the Board of Directors and the
Bylaws of the Foundation until death, resignation, retirement, removal
or disqualification, or until a successor is appointed.
Special Order 7C, Change the Apache Royale Project Chair, was
approved by Unanimous Vote of the directors present.
8. Discussion Items
A. OSI Affiliate
https://whimsy.apache.org/board/minutes/Accept_Offer_from_OSI_to_become_Affiliate.html#2011-11-16
Early on opensource.org and the ASF had some overlap in directors; but
we disengaged at some point. VP Public Affairs suggests we re-engage.
As there now is an affiliate agreement
(https://opensource.org/affiliateAgreement/) VP Public Affairs is
asking for the board to OK re-engagement subject to an legal OK; with
our President as the person to vote in the OSI board election; our VP
of Marketing for the marketing contact and the VP of Public Affairs as
the contact for their Public Policy angle. There is no budget
associated with this.
The board approves by general consent the request to join the OSI
affiliation.
B. Open Forum Europe
We need to decide if we want to be publicly listed on their site as a
supporter. VP Public Affairs suggests that we do that; as it is a win-win for
us & the wider open source community (and we can rescind this any time we
want).
There is no paperwork needed. They would need an email confirming this, the
payment made & which logos we’d want them to use - and our contacts.
The board approves by general consent for VP Public Affairs to
contract with OFE to provide situational awareness of proposed
legislation in the EU.
9. Review Outstanding Action Items
* Rich: continue with PMC advice around communication tooling
[ ASF practices in the context of tooling landscape developments 2023-04-19 ]
Status: Done. Or, at least, doesn't need to remain on the Board agenda
any longer. ComDev is tackling this in several ways, the first
of which rolls out on Oct 1.
* Sander: follow up on comments from board
[ BuildStream 2023-05-17 ]
Status: Website in progress - effort not being driven by me.
* Christofer: pursue a roll call for Giraph
[ Giraph 2023-07-19 ]
Status: This was done and led to next action.
* Shane: pursue a roll call for Libcloud
[ Libcloud 2023-07-19 ]
Status: Done; successful; they also made a new release.
https://lists.apache.org/thread/0191sz3nomyvd6yw2sf0ns09mohq1f9w
* Willem: also follow up on Zeppelin security
[ Security Team 2023-07-19 ]
Status: Jongyoul promised to put some effort into security-related
issues.
* Sander: work with Brian around messaging this out
[ Security Team 2023-08-16 ]
Status: Not Done. Ideally connect Brian and mjc directly.
* Shane: pursue a report for Bloodhound
[ Bloodhound 2023-08-16 ]
Status: Done
* Justin: follow up on brand usage
[ Cassandra 2023-08-16 ]
Status: Followed up and also found more branding issues. PMC was not
very responsive, so followed up with trademarks. Currently
vendors' commercial content is being advertised on
PMC-controlled community website.
* Willem: follow up around contributors
[ Geode 2023-08-16 ]
Status:
* Christofer: pursue an Attic resolution for Giraph
[ Giraph 2023-08-16 ]
Status: Temrination resolution added to board agenda
* Christofer: direct discussion over lazy consensus releases to appropriate
[ Logging Services 2023-08-16 ]
Status: The discussion moved from comdev, to board and spread out to
legal and public-affairs and is currently mostly waiting on
Legal to respond (asked on public affairs due to possible link
to CRA)
* Justin: pursue a report for Lucene.Net
[ Lucene.Net 2023-08-16 ]
Status: Done
* Sander: pursue a chair change for Serf
[ Serf 2023-08-16 ]
Status: Not done.
* Justin: follow up on trademark concern
[ ServiceComb 2023-08-16 ]
Status: Done. There is an issue around transferring a trademark, VP
branding is on top of it.
* Justin: follow up on seeking help on release packaging
[ Superset 2023-08-16 ]
Status: Done. Minor issue with release version numbers.
10. Unfinished Business
11. New Business
12. Announcements
13. Adjournment
Adjourned at 22:10 UTC
============
ATTACHMENTS:
============
-----------------------------------------
Attachment 1: Report from the VP of Brand Management [Mark Thomas]
Covering the period August 2023
* ISSUES FOR THE BOARD
Received a request from the board to comment on branding questions related to
CASSANDRA. The response has been sent to the board and CC'd to the CASSANDRA PMC.
* OPERATIONS
Responded to the following queries, liaising with projects as required:
- one request to use project logos within an external software product
- one query from CASSANDRA regarding a potential infringement
- one request to use the PINOT logo on a t-shirt
- one query whether ASF letterhead could be used for a personal recommendation
* REGISTRATIONS
Directed counsel to renew the class 9 registrations for APACHE in Australia,
Norway and Switzerland but allow the class 42 registrations to lapse.
The FINERACT and LOG4J registrations in the US are progressing.
Responded to the GUACAMOLE PMC regarding a query associated with their in
progress registration.
Worked with counsel to maintain the TEZ registration.
Directed counsel to allow all registrations in all jurisdictions for
PREDICTIONIO to lapse.
Counsel in India continues to work on progressing our APACHE registration.
ASF counsel highlighted that the process of transferring SERVICECOMB
registrations has not been completed. I reached out to HUAWEI and this should
be completed soon. The PMC has been made aware that if this process is not
completed, the project will be required to change name.
* INFRINGEMENTS
Worked with the SPARK PMC to address a couple of issues in a commercial
website.
Refused to authorize an Amazon seller to sell download links for OpenOffice
after Amazon suspended their account for doing the same.
The Maven PMC has indicated they they do consider the previously mentioned
issue as an infringement. I will start to address this in September.
Informed counsel that the ASF has no objections to a registration in Brazil
that was viewed as potentially conflicting with the ASF's IMPALA registration.
-----------------------------------------
Attachment 2: Report from the VP of Fundraising [Bob Paulin]
1) ASF Sponsors:
a --New: no new Sponsors were onboarded during this timeframe.
b --Renewals: one Gold Sponsor has confirmed their renewal.
c --Payments: 1 --New: no new Sponsor payments were received.
2a --Renewing: we received payment from one renewing Gold Sponsor.
2b --Incoming: we await payment from one Platinum, one Gold, one Silver,
and one Bronze Sponsor.
2) Targeted Sponsors: we are in the process of onboarding a new Platinum
Targeted Sponsor.
3) Sponsor Relations: Sponsor engagement continues, including dispatching our
monthly news updates. We are helping organize Sponsor meetings, both virtually
as well as one-on-one at the upcoming Community Over Code/Halifax event in
October.
4) Event Sponsorship: we received payment for the proceeds from ApacheCon Asia
2022. We continue to liaise event sponsorship activities, including
coordinating with Community Over Code/North America 2023 sponsorships and
Europe 2024 planners, as well as assisting with collections on final
outstanding sponsorship payments from ApacheCon NA (October 2022).
5) Individual Donations and Corporate Giving: we received $15.6K in donations
this month, which includes one corporate contribution.
6) Administrivia: we continue to work with the Treasury and Accounting teams
on the few remaining outstanding Sponsor invoicing issues.
-----------------------------------------
Attachment 3: Report from the VP of Marketing and Publicity [Brian Proffitt]
**Foundation Comms**
* Finalized written and formatted draft of FY 2023 Annual Report; should be
posted week of Sept. 18.
* Created Annual Report Guidelines and began FY24 outline.
* Announced schedule for Community Over Code NA event (blog[1], wire[2]).
* Drafted response for CISA’s press release mentioning ASF; monitored news.
* Promoted Community Over Code NA reg, Europe’s call for tracks, and Airflow
Summit.
**Proactive Storytelling**
* #FirstContributions Campaign: new blog post[3], editorial calendar, & social
cards.
* Continued interviewing stakeholders for story platform.
* Drafted Generative AI byline for Roman.
**Branding Project**
* Drafted public-facing post for ASF blog.
* Branding Committee met Sept 11 (minutes[4]), also posted an overview of the
re-brand process with estimated timeline [5]
* Continued to monitor and counsel on reactive comms around ASF branding.
**Website**
* Updated and a/b testing fundraising buttons and navigation.
**Social Media Posts**
In August, we continued to drive community engagement across social media,
sharing:
* 76 Tweets + 43 LinkedIn posts covering ASF, project, and industry news.
Posts included project releases, Community Over Code NA promotion (call for
speakers), and original ASF blog posts.
* Continued to react to select posts in which we were mentioned or tagged.
**Social Engagement Stats (Twitter + LinkedIn)**
* Total engagement: 7,240 (up 26% from July)
* Total clicks: 3,156 (up 18% from July)
* Click to engagement ratio: 44% (down 2% from July)
* New followers: 493 (up 15% from July - 22 lost on X)
**Website Analytics**
* 4,690 visits, 4,690 unique visitors
* 2 min 41s average visit duration
* 76% visits have bounced (left the website after one page)
* 3.8 actions (page views, downloads, outlinks, internal site searches) per
visit
* 1,921 max actions in one visit
* 16,699 pageviews, 5,815 unique pageviews
* 0 total searches on your website, 0 unique keyboards
* 74 downloads, 67 unique downloads
* 796 outlinks, 663 unique outlinks
Note: We installed analytics in late July, so growth numbers will not be
posted for this report. September onward will become more useful, as August is
a first full-month baseline.
[1] https://news.apache.org/foundation/entry/apache-software-foundation-announces-schedule-for-community-over-code-north-america
[2] https://www.globenewswire.com/en/news-release/2023/08/07/2720020/17401/en/Apache-Software-Foundation-Announces-Schedule-for-Community-Over-Code-North-America.html
[3] https://news.apache.org/foundation/entry/first-time-contributors-enhance-code-for-asf-projects
[4] https://lists.apache.org/thread/bkwv9rqro2bng5s731s2lz9z94o17tmr
[5] https://cwiki.apache.org/confluence/pages/viewpage.action?spaceKey=ASFP&title=Brand+Project
-----------------------------------------
Attachment 4: Report from the VP of Infrastructure [Myrle Krantz]
-----------------------------------------
Attachment 5: Report from the VP of Conferences [Rich Bowen]
We're now in the final month leading up to Community Over Code North America.
This year is posing new challenges - in particular, visas are extraordinarily
hard to come by, and we have lost an unusually large number of speakers to
that reality. But we are still forging ahead and looking forward to a great
event in Halifax.
There are a large number of other events happening around the Foundation in
the coming weeks and months. These can be seen at https://events.apache.org
Planning is going well for the EU event in 2024, which we hope to formally
announce in Halifax.
-----------------------------------------
Attachment 6: Report from the Apache Travel Assistance Committee [Gavin McDonald]
Current Events
==============
Community Over Code Halifax
---------------------------
Just over 2 weeks until the event. We have most flights booked.
We are awaiting final call for 2 peoples Visa applications.
We have Hotel rooms all sorted and conference passes.
TAC App
=======
TAC App is closed currently.
Future Events
=============
Keeping an eye on things for Fosdem in Feb '24 if we have budget, and also how
things progress with Community Over Code Europe '24.
Short/Medium Term Priorities
============================
Keeping an eye out for other smaller events to support. We are keen to hear
about projects events.
Mailing List Activity
=====================
None this month, other than automated.
Membership
==========
No changes to the membership this month.
-----------------------------------------
Attachment 7: Report from the VP of Diversity and Inclusion [Katia Rojas]
-----------------------------------------
Attachment 8: Report from the VP of Data Privacy [Christian Grobmeier]
# General
No issue requiring board attention at this time.
There have been many unfounded requests to vp-privacy@
related to "privacy requests." These requests look a lot
like spam.
-----------------------------------------
Attachment 9: Report from the VP of Public Affairs [Dirk-Willem van Gulik]
Europe
======
Over the parliament recess, significant work and various analyses done on the
3(4) versions of the CRA by the open source foundations; coordinated by Open
Forum Europe. Which will lead to outreach to national stakeholders/cabinet
offices and the EU/EC that is coordinated between all of us. With consensus
inside and outside the ASF. This analysis is expected to become public this
week (with earlier versions used by some of our members in talks with NL, DE
and IT). Note that this will be under the OFE banner - we, the ASF, merely
supports their work.
Conversations with DE suggest that the CRA is getting slowed down; with
trialogue completion now expected no earlier than end of October. The PLD
(plain, simple, strict liability for software) is still on schedule for the
end of this year.
The situation around the 3 versions sees some of our large peer organsions
deciding to wait the outcome of the Trialogues before a more
public/public-outcry oriented campaign. Consensus at the ASF (and various
other peer organisations) seems to be that this is too late; as 1) the
regulation has been carved into stone at that point; and you generally assume
a complete reversal. And 2) as the current Council version (which generally
`win's) is not that problematic for a pure volunteer ran organisation like us
(i.e. where the open source organisation does not pay its developers; where
the baord does not tell PMCs what to do).
I am currently looking into engaging some legal expertise around a few, ASF
specific, narrow interpretation questions: 1) confirmation that distributing
source code with make/build/rel-notes, version numbers. etc, i.e. alll that
`signal that this code is expected to be used' meets the current (and not yet
final) definitions of placing it into the market of the Blue Guide/NLF. 2)
what the boundary would be if the ASF where to avoid itself to place a product
on the market/have the CRA read on it and 3) the implications for both our EU
based committers -and- their employers.
CRA P(review) Week
==================
There is discussion on the mailing list about the need for a "louder
action", especially the concept of CRAP Week, but the exact definition of
this, the goals of this action, the impact of said action on the community,
and the required infrastructure resources and timing continue to be
debated. There is not a consensus that the action would accomplish the
stated goals of attracting attention and getting our community fired up
against the CRA. Indeed, this could easily alienate our supporters. If we
are to contemplate this for the future and anticipate the need for this
action of "last resort", it would require Board approvals as it falls
outside the purview of the Public Affairs remit. Meanwhile we are seeing
large, powerful industries waking up to the reality and the action may not
be needed.
USA
===
No changes - but NIST is increasingly engaging with industry. Given the lack
of progress on the normative standards organisations in Europe -- this makes
it increasingly likely that it is ultimately the US that will define the
global standards in this area.
International
=============
There is a Linux Foundation organised Open Source Summit in Bilbao. ASF folks
known to attend have been briefed - but we've postponed/declined to engage
with lawmakers/regulators in prepared meetings & avoided a public appearance.
(Background: Bilbao is in Spain, and Spain is the current president of the EU
& hence sets agenda/etc for the next months). Instead people attending have
been given a number of talking points to have ready should they happen to be
put in a position where they need to respond/have the right opportunity.
Standards
=========
No changes over the summer / no new conversations.
-----------------------------------------
Attachment 10: Report from the VP of W3C Relations [Andy Seaborne]
-----------------------------------------
Attachment 11: Report from the Apache Legal Affairs Committee [Roman Shaposhnik]
Past month has been pretty calm. Committee members took good care of resolving
most issues on time. After resolving a handful of LEGAL issues, we are
slightly up at 24 outstanding issues (from 22 last month).
Otherwise the month was extremely calm and uneventful.
-----------------------------------------
Attachment 12: Report from the Apache Security Team Project [Mark J. Cox]
* CISA released their '2022 Top Routinely Exploited Vulnerabilities'
report, mentioning "malicous cyber actors continued to show high
interest in CVE-2021-44228 through the first half of
2022". (Log4Shell). The 'Additional Routinely Exploited
Vulnerabilities' table also lists some HTTP Server vulnerabilities
and a follow-up on Log4Shell:
https://www.cisa.gov/news-events/cybersecurity-advisories/aa23-215a
* Nucleus Security made a visual representation of vendors in CISA's
Known Exploited Vulnerabilities report. With 28 of the 989
vulnerabilities, Apache is visible on the chart:
https://nucleussec.com/cisa-kev-art/
Stats for Aug 2023:
25 [license confusion]
20 [support request/question not security notification]]
8 [report/question relating to dependencies]
Security reports: 65 (last months: 88, 73, 59, 73)
11 ['airflow', 'website or other infrastructure']
3 ['tomcat']
2 ['beam', 'commons', 'dolphinscheduler', 'hive', 'hop',
'kafka', 'linkis', 'nifi', 'pulsar', 'seatunnel', 'shiro',
'superset']
1 ['ant', 'couchdb', 'druid', 'dubbo', 'fineract', 'geode',
'groovy', 'hadoop', 'httpd', 'inlong', 'openoffice', 'pinot',
'ranger', 'spark', 'struts', 'trafficserver']
In total, as of 1st September 2023, we're tracking 181 (last
months: 171, 170) open issues across 54 projects, median age 108
days (last months: 106, 104). 46 of those issues have CVE names
assigned.
13 (last month: 12) of these issues, across 7 projects, are older
than 365 days.
-----------------------------------------
Attachment 13: Report from the VP of Jakarta EE Relations [Rob Tompkins]
-----------------------------------------
Attachment A: Report from the Apache Airflow Project [Bolke de Bruin]
## Description:
The mission of Apache Airflow is the creation and maintenance of software
related to workflow automation and scheduling that can be used to author and
manage data pipelines.
## Project Status:
Current project status: Ongoing, High Activity
Issues for the board: No issues worth board attention
## Membership Data:
There are currently 57 committers and
32 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
Community changes, past quarter:
* Hussein Awala was added to the PMC on 2023-07-29
* Dennis Ferruzzi was added as committer on 2023-07-04
* Maciej Obuchowski was added as committer on 2023-06-28
* Pankaj Singh was added as committer on 2023-06-13
* Phani Kumar was added as committer on 2023-06-28
* Vincent Beck was added as committer on 2023-06-26
We are also just about to announce two new -
just voted-in - committers:
* Pankaj Koti
* Amogh Desai
We plan to announce them at the Airflow Summit
during our “The Faces of Airflow”
discussion panel where ampng others we will
praise the community of Airflow, committers,
contributors and everyone who makes
Airflow such a great community
## Project Activity:
• We continue the steady release of bugfixes (2.6.*) and new feature releases
(2.7) as well as regular Provider releases, Helm Chart and Python client.
• The 2.7 release (https://airflow.apache.org/blog/airflow-2.7.0/) was packed
with new, important user-visible features: Setup/Teardown, New Cluster
activity and Gantt Chart UI, but also a number of changes that move Airflow
in the general direction of becoming “Workflow Platform” rather than
“Workflow solution”. Those changes include completion of Executor Coupling
removal (AIP-51) culminated by separation of Celery, Kubernetes and Dask
executors to providers (including configuration separation), allowing to
extend airflow with fully-featured 3rd-party executors OpenLineage
integration, but also making it clear what is and what is not Public
Interface of Airflow covered by our SemVer promises.
• There is an on-going work including efforts led by various stakeholders and
individual community members: Internal API (AIP-44) and External
Authentication and Authorisation framework (AIP-56 - part of Multi-Tenancy)
- both step towards enabling Airflow to multi-tenant deployments, Next steps
of the Open Telemetry integration (AIP-49), Strengthening Open Lineage
integration (AIP-53)).
• With the help and involvement of the ASF Security team, we managed to
establish a highly functional security team that operates in a much more
efficient way and delivered great results: we managed to fix all outstanding
issues and we have a working process to manage influx of new issues in a
much better organized and efficient way. We also implemented structural
changes that eliminated a wide range of potential security issues as well as
improved our communication around the Security Model of Airflow towards
users and researchers. Findings and learnings from building the team will be
shared at the Community Over Code conference in Halifax at the talk of Jarek
Potiuk who led the effort and Arnount Engelen - who is part of the ASF
security team https://communityovercode.org/schedule-list/#CY011. Work
continues on improving the process and tooling.
Releases:
* Provider packages 2023-08-29 was released on 2023-09-01.
* Provider packages 2023-08-26 was released on 2023-08-29.
* Apache Airflow Python Client 2.7.0 was released on 2023-08-24.
* Apache Airflow 2.7.0 was released on 2023-08-18.
* Provider packages 2023-08-11 was released on 2023-08-14.
* Provider packages google 2023-08-09 was released on 2023-08-10.
* Provider packages redis 2023-08-08 was released on 2023-08-09.
* Provider packages 2023-08-05 was released on 2023-08-08.
* Provider packages 2023-07-29 was released on 2023-08-01.
* Provider package elasticsearch 2023-07-17 was released on 2023-07-21.
* Provider packages 2023-07-12 was released on 2023-07-16.
* Apache Airflow 2.6.3 was released on 2023-07-10.
* Provider packages ad hoc release 2023-07-09 was released on 2023-07-10.
* Provider packages 2023-07-06 was released on 2023-07-09.
* Apache Airflow Helm Chart 1.10.0 was released on 2023-06-27.
* Apache Airflow Python Client 2.6.2 was released on 2023-06-25.
* Provider packages 2023-06-20 was released on 2023-06-23.
* Apache Airflow 2.6.2 was released on 2023-06-17.
## Community Health:
* The Airflow Summit 2023 is happening September 19-21 in Toronto, Canda. And
it’s just round the corner. We have a full program and the number of attendees
that already registered surpassed our expectations (we are estimating 470 -
500 attendees). We gave free passes to all the committers, we funded 15
scholarships for under-represented attendees and we have a healthy set of
sponsors and we are increasing our promotional efforts in cooperation with
Software Guru who are producers of the event. The event is organized by
representatives of the biggest stakeholders (Amazon, Google, Astronomer), PMC
members and other community members).
* We had a number of local Airflow Meetups: Washington DC, Toronto, New York,
and Portland
* We just reached the milestone of 2600 contributors on GitHub this month
(2500 in the last report). We see continuous interest in new contributors
joining Airflow
* We have regular monthly newsletter and voting on PR of the month that
regularly gets somewhat enthusiastic reactions from the community
* Despite the holiday period, we continue getting new publications at our
medium publication https://medium.com/apache-airflow - 7 new publications
since last report
-----------------------------------------
Attachment B: Report from the Apache Allura Project [David Philip Brondsema]
## Description:
The mission of Apache Allura is the creation and maintenance of software
related to a software development infrastructure platform commonly known as a
"forge"
## Issues:
- No issues needing board attention.
## Membership Data:
Apache Allura was founded 2014-03-18 There are currently 17 committers and 17
PMC members in this project. The Committer-to-PMC ratio is 1:1.
Community changes, past quarter:
- No new PMC members. Last addition was Guillermo Cruz on 2021-11-09.
- No new committers. Last addition was Guillermo Cruz on 2021-11-09.
## Project Activity:
- discussed dropping python 3.7
- small feature improvements and bugfixes
- dependency upgrades
## Community Health:
- We are voting on our next release currently.
- Last release was 1.14.0 on 2022-09-23
- Good maintenance and support of the codebase continues
- But not much of significant changes or updates lately
-----------------------------------------
Attachment C: Report from the Apache Archiva Project [Olivier Lamy]
-----------------------------------------
Attachment D: Report from the Apache Atlas Project [Madhan Neethiraj]
## Description:
The mission of Apache Atlas is the creation and maintenance of software related
to a scalable and extensible set of core foundational governance services -
enabling enterprises to effectively and efficiently meet their compliance
requirements
## Project Status:
Current project status: Ongoing, with moderate activity
Issues for the board: There are no issues requiring board attention.
## Membership Data:
Apache Atlas was founded 2017-06-20 (6 years ago)
There are currently 48 committers and 32 PMC members in this project.
The Committer-to-PMC ratio is 3:2.
Community changes, past quarter:
- No new PMC members. Last addition was Ashutosh Mestry on 2019-04-16.
- Umesh Padashetty was added as committer on 2023-06-14
## Project Activity:
- updated build and docker setup to support Apple M1 chip env
- fixed initialization failures in HBase and Hive hooks
- fixes in Atlas client Java library
- enhancement to support Hook notifications via REST API
- UI fixes in glossary terms page
- updated versions of Spring framework, jettison, Netty
## Community Health:
- dev@atlas.apache.org had a 6% decrease in traffic in the past quarter (208
emails compared to 220)
- 32 issues opened in JIRA, past quarter (6% increase)
- 17 issues closed in JIRA, past quarter (54% increase)
- 30 commits in the past quarter (-9% change)
- 9 code contributors in the past quarter (-18% change)
## Response to comments on previous report
13 PMC members weren't subscribed to private mailing list. Atlas PMC reached
out to these members
- 3 PMCs agreed to update their subscription to private list
- 2 PMCs asked their status to be updated to emeritus
- no response from 8 PMCs
## Recent releases:
Apache Atlas 2.3.0 was released on 2022-12-06.
Apache Atlas 2.2.0 was released on 2021-08-17.
Apache Atlas 2.1.0 was released on 2020-07-15.
-----------------------------------------
Attachment E: Report from the Apache Axis Project [Robert Lazarski]
# Apache Axis Board Report
## Description
The Apache Axis project is responsible for the creation and maintenance of
software related to the Axis Web Services frameworks and subsidiary
components (both Java and C).
## Issues
There are no issues requiring board attention at this time.
## Membership Data:
Axis was created on 2001-01-19 (22 years ago). It is listed as
established in 2009-12 but really the first Apache commit was in 2001.
There are currently 63 committers and 62 PMC members in this project,
a vote in 2010 made all committers automatically PMC members. One PMC
member resigned.
Community changes, past quarter:
- Currently 62 PMC/ 63 Committers members.
- No new committers were added in the last 90 days, last committer added
was Bill Blough on December 7th 2017 who also was added to the PMC on
May 9th 2018.
## Project Activity:
Recent releases:
- Axis 2/Java 1.8.2 was released on July 14, 2022.
- Axis 2/Rampart 1.7.1 was released on July 30, 2017.
- Axis 2/C 1.6 was released on April 20, 2009.
- Axis 1.4 was last released in 2006.
## Health report:
In this past quarter, there was further progress made adapting Apache Axiom
SNAPSHOT release changes as described in Jira issue AXIOM-506 into
Axis2 Java.
Related work this next quarter is expected to culminate in the complete move
of Axis2 off of the old javax packages and into new jakarta packages.
See AXIS2-6051.
Work continues on passing the unit tests after a major refactoring effort
of Apache Rampart - an implementation of WS-Security standards -
that was required from commits upgrading OpenSAML from 2.x to 4.3.0, and
Apache WS-WSS4J from 1.6 to 3.0.0. See RAMPART-449.
There is developer interest in adding OpenAPI support, also known as
Swagger, that may result in commits this next quarter. It is an
example of Axis further moving into contemporary Open Source JSON based
REST frameworks that we expect will attract committers in a way that
legacy SOAP no longer can.
A question was raised about it being five years since our last committer was added.
We made an offer for a committer this past quarter but nothing came of it.
We have a strong candidate that has submitted patches in RAMPART-449. We
plan to make an offer this quarter as we vote for a Rampart release.
Long term, our bet is that Axis can transition into a modern and competitive
REST based JSON framework, as shown by our increasing spring-boot
support and potentially offering OpenAPI integration.
Axis2 C PMC member Bill Blough continues to help users on the mailing list
and he also participates in release votes.
## Axis2 java Jira issues opened in the last 90 days: 4
## Axis2 java Jira issues closed in the last 90 days: 1
-----------------------------------------
Attachment F: Report from the Apache Bahir Project [João Boto]
## Description:
Apache Bahir provides extensions to distributed analytic platforms such as
Apache Spark and Apache Flink. Currently, Bahir provides extensions to
multiple distributed analytic platforms, extending their reach with a
diversity of streaming connectors and SQL data sources.
## Project Status:
Current project status: Not enough active PMC members (roll call made)
Issues for the board: Advice as to how to proceed in this situation
## Membership Data:
Apache Bahir was founded 2016-05-18 (7 years ago)
There are currently 40 committers and 12 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:2.
Community changes, past quarter:
- No new PMC members. Last addition was João Boto on 2020-07-10.
- No new committers. Last addition was Łukasz Antoniak on 2019-01-21.
## Project Activity:
We keep seeing activity arround flink connectors (especially kudu, redis
and pinot).
We have some new account searching to help on this connectors.
## Community Health:
Asked on dev list for help to keep the project as we see some traction on
Flink side [https://lists.apache.org/thread/4lfpt4w3kf6g8z0zln4qtd7r30kr0tsh]
Maybe we should ask on user list, but is barely used.
-----------------------------------------
Attachment G: Report from the Apache Beam Project [Kenneth Knowles]
## Description:
The mission of Apache Beam is the creation and maintenance of software related
to a unified programming model for both batch and streaming data processing,
enabling efficient execution across diverse distributed execution engines and
providing extensibility points for connecting to different technologies and
user communities.
## Project Status:
Current project status: Ongoing
Issues for the board: none
## Membership Data:
Apache Beam was founded 2016-12-20 (7 years ago)
There are currently 92 committers and 23 PMC members in this project.
The Committer-to-PMC ratio is approximately 9:2.
Community changes, past quarter:
- No new PMC members. Last addition was Jan Lukavský on 2023-02-14.
- Ahmed Abualsaud was added as committer on 2023-08-24
## Project Activity:
Top-level technical notes to show direction of the project:
- The "Prism Runner", mentioned in prior reports, is now complete enough and
the default for the Go SDK. Next up is to make it the best local runner
for other SDKs to test multi-language pipelines (which are expected to
be the norm, not the exception, as major libraries are built in one language
and used in all languages).
- Multi-language pipelines continue to get easier and more transparent to
author, this time with a new automatically launched and managed subprocess
that can serve multiple "external" transforms.
- BigTable Change Streams support was added. While it is just one connector,
it is notable for being part of an increased interest in streaming
applications, in which most storage may be shipping changes around,
including those not traditionally considered "streaming" systems.
- ML conveniences continue to be added to Beam Python, such as:
- hugging face model handler
- Vertex AI model handler
- new "MLTransform" for pre/postprocessing, complementing RunInference
- prebuilding docker containers to bundle large dependencies
- All Beam released container images are now multi-arch images that support
both x86 and ARM CPU architectures.
- Go SDK requires Go 1.2.0 to build
- SparkRunner now defaults to Spark 3.2.2
Community:
- Beam Summit 2023 was a huge success. Beam Summit 2023
<https://beamsummit.org/> was the eighth and the biggest edition of the
flagship conference for the Apache Beam community. Beam Summit 2023 took
place on June 13 - 15, 2023 as an in-person event, bringing the community
together in NYC, and on July 18-20, 2023 as a virtual edition. [impact
report]
[impact report] https://lists.apache.org/thread/l7hxz8wpl9rqt8jotv64620sl2zmdx2p
Recent releases:
- 2.50.0 was released on 2023-08-30.
- 2.49.0 was released on 2023-07-17.
Our 6 week release cadence is going quite well. Increased release automation
has reduced the time from cutting a release branch to finalizing a release.
## Community Health:
Issues and code traffic are within normal variation, aka flat. No growth or
shrinking trends.
Community faced email delivery issues, causing friction when communicating on
the email lists, and making project activities (e.g. release validation)
difficult to coordinate. Even though issues were addressed, we are not sure if
we will run into these issues again because there was not a permanent fix.
(Examples: https://issues.apache.org/jira/browse/INFRA-24574
https://issues.apache.org/jira/browse/INFRA-24790
https://issues.apache.org/jira/browse/INFRA-24872)
-----------------------------------------
Attachment H: Report from the Apache Bigtop Project [Yuqi Gu]
## Description:
Bigtop is a project for the development of packaging and tests of the Apache
Hadoop ecosystem. The primary goal of Bigtop is to build a community around the
packaging and interoperability testing of Hadoop-related projects. This
includes testing at various levels (packaging, platform, runtime, upgrade,
etc...) developed by a community with a focus on the system as a whole, rather
than individual projects. In short we strive to be for Hadoop what Debian is to
Linux.
## Project Status:
Current project status: 3.2.1 was released on 2023-08-22, CHI: 7.15 (Healthy)
Issues for the board: There are no issues requiring board attention.
## Membership Data:
Apache Bigtop was founded 2012-09-19 (11 years ago)
There are currently 42 committers and 29 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:2.
Community changes, past quarter:
- No new PMC members. Last addition was Masatake Iwasaki on 2021-03-11.
- No new committers. Last addition was Zhiguo Wu on 2023-05-17.
## Project Activity:
- 3.2.1 was released on 2023-08-22, which is a patch release of 3.2.0
for addressing some security issues of Hadoop.
- We are working on adding support for openEuler to Bigtop based on
the branch 'openEuler-support':
OpenEuler Bigtop-toolchain images have been supported,
along with Puppet deployment scripts.
In addition, support has been added for several components,
including Hadoop, Phoenix, Alluxio, Oozie, Ycsb, and Kafka.
## Community Health:
Community health is good. Several contributors were actively fixing issues
and developing the 3.2.1 release. The number of code contributors was a
bit decreased, but all other metrics were positive and reflect our
active development and interactions.
- 9 code contributors in the past quarter (-10% change)
- 57 PRs opened on GitHub, past quarter (119% increase)
- 49 PRs closed on GitHub, past quarter (133% increase)
- 71 commits in the past quarter (195% increase)
- [dev@bigtop.apache.org](mailto:dev@bigtop.apache.org) had a 128% increase
in traffic in the past quarter (534 emails compared to 234)
- [issues@bigtop.apache.org](mailto:issues@bigtop.apache.org) had a 89%
increase in traffic in the past quarter (258 emails compared to 136)
-----------------------------------------
Attachment I: Report from the Apache Bloodhound Project [Gary Martin]
Apache Bloodhound is a software development collaboration tool, including
issue tracking, wiki and repository browsing
Issues
======
There are no issues to raise to the Board at this time.
Releases
========
There have been no releases since the last report. The last release was
towards the end of 2014:
* apache-bloodhound-0.8 (11th December 2014)
PMC/Committer Changes
=====================
There are currently 14 PMC members on the project. The last changes were in
April 2017.
The last new committers were added in May 2014.
The last addition to the PMC was in January 2017 (dammina)
Community & Development
=======================
Following the welcome intervention of the board, suggesting that Apache
Bloodhound should be moved to the Attic, there has been some renewed
discussions from a number of members of the community expressing interest in
continuing the project outside of the Attic.
While the activity following this has died down a bit, we saw a number of
people who appeared to be willing to be involved, along with all the recently
active PMC members (chambej, dammina, gjm and gstein) engaging to various
extents with the community.
The activity resulted in the following actions:
* The original Apache Bloodhound svn repo has been made readonly reflecting
previous decisions to use git for development to make it easier for new
contributors.
* The Apache Bloodhound website has been converted to use Pelican and has
been given its own bloodhound-site repo.
Given this interest and activity it is still believed to be premature to move
the project to the attic.
-----------------------------------------
Attachment J: Report from the Apache BVal Project [Matthew Jason Benson]
## Description:
The mission of BVal is the creation and maintenance of software related to
Apache BVal: JSR-303 Bean Validation Implementation and Extensions
## Project Status:
Current project status: Apache BVal's development has been dormant this quarter.
Issues for the board: There are no issues requiring board attention at this
time.
## Membership Data:
Apache BVal was founded 2012-02-14 (12 years ago)
There are currently 16 committers and 15 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 Jean-Louis Monteiro on 2020-11-29.
- No new committers. Last addition was Jean-Louis Monteiro on 2020-11-17.
## Project Activity:
There has been no significant committer activity to the project this period.
## Community Health:
There has been no new interest registered; however, there are no signs that our
voting quorum of "obligated" PMC members is in any sort of jeopardy.
-----------------------------------------
Attachment K: Report from the Apache Camel Project [Andrea Cosentino]
## Description:
The mission of Apache Camel is the creation and maintenance of an open-source
integration framework based on known Enterprise Integration Patterns.
## Project Status:
Project status: Ongoing with high activity
Issues: There are no issues requiring board attention at this time.
## Membership Data:
Apache Camel was founded 2008-12-17 (15 years ago)
There are currently 88 committers and 44 PMC members in this project.
The Committer-to-PMC ratio is 2:1.
Community changes, past quarter:
- No new PMC members. Last addition was Nicolas Filotto on 2023-04-05.
- Kengo Seki was added as committer on 2023-07-04
## Project Activity:
- We released Camel 3.14.9
- We released Camel 3.18.8
- We released Camel 3.20.6
- We released Camel 3.21.0
- We released Camel 4.0.0-RC1
- We released Camel 4.0.0
- Note: Camel releases have synchronized releases of Camel-Karaf and
Camel-Spring-Boot too for 3.x, while for 4.x only Camel-Spring-Boot is
synchronized.
- We released Camel 4.0.0, our main effort in the last 10 months.
- We are continuing release 3.18.x LTS release train and we are in the process
of releasing the next patch release.
- We started the release train for 3.20.x LTS, and we are already at the sixth
patch release. We want to release another patch release soon.
- We are still supporting Camel 3.14.x, an LTS train, but it's going EOL,
there will be another release 3.14.10.
- We released another 3.x LTS Release the 3.21.0
- For Camel K we released a really important 2.0 release with a lot of good
work from community. It has no coupled dependency from the runtime and its
release cycle will be decoupled from the core/runtime release cycle.
- Camel K Runtime dependency is now matching the release cycle with Camel
Quarkus.
- For Camel-K-runtime we released 2.16.0
- For Camel-Kamelets releases
- We released Camel Kamelets 3.20.6
- We released Camel Kamelets 3.21.0
- We released Camel Kamelets 4.0.0-RC1
- We are working hard on releasing version 4.0.0 too
- Camel-Kamelets is not only related to camel k anymore so it could be used
with all the Camel's flavours
- The Camel-Quarkus work is going ahead following the main camel releases with
multiple releases
- We released Camel-quarkus 2.16.0
- We released Camel-quarkus 3.0.0-RC1
- We released Camel-quarkus 3.0.0-RC2
- We released Camel-quarkus 3.2.0
- Camel-Kameleon and Camel-Karavan are improving and more and more
contributors are continuing to help. We are improving the projects by
supporting new features and aligning with LTS releases 3.21.0 as in the last
report
- Camel Kafka Connector release based on Camel 3.20.6 has been released.
- Camel Kafka Connector release based on Camel 3.21.0 has been released.
- Work for supporting Camel 4.0.0 is going ahead
- Generally speaking we are working on supporting Camel 4 in all the runtimes
provided and this is taking a lot of effort.
## Community Health:
- 296 issues opened on GitHub, past quarter (15% decrease) and 308 issues
closed on GitHub, past quarter (5% decrease): Since we were working on
releasing Camel 4.0.0 some of the subprojects using gh issues have seen less
focused work, Camel is using JIRA for tracking the work. We focused on 4.0.0
for a long time.
- 4992 commits in the past quarter (14% decrease) and 133 code contributors in
the past quarter (3% increase): The commits decrease is related to the work
done for Camel 4.0.0, at some point in the development we choose to slow
down a bit. The camel core team was focusing on Camel 4.x. We saw sporadic
contributions from new contributors in subprojects and main Camel.
- 1601 PRs opened on GitHub, past quarter (4% decrease) and 1602 PRs closed on
GitHub, past quarter (4% deccrease): on some of the subprojects the activity
was slowing down for stabilization reasons and for the focus on Camel 4.0.0.
- dev@camel.apache.org had a 23% increase in traffic in the past quarter (412
emails compared to 334): There was a spike in the dev ML because of
questions and discussions around the development and final decision for
Camel 4.0.0
- issues@camel.apache.org had a 56% increase in traffic in the past quarter
(2964 emails compared to 1888): There was activity in JIRA mostly for Camel
4 work and cleaning up. We also went through opened and future issues and
cleaned up again.
- users@camel.apache.org had a 6% increase in traffic in the past quarter
(260 emails compared to 243): Some users are starting to ask about migration
from 3.x to 4.x, but also from 2.x to 3.x
- Note: JIRA statistics are not available in the statistics report provided by
reporter. So we cannot comment numbers.
-----------------------------------------
Attachment L: Report from the Apache Cayenne Project [Michael Ray Gentry]
# Apache Cayenne Board Report, September 2023
## Description
Apache Cayenne is a Java database persistence framework. It takes a
distinct approach to object graph persistence and provides an ORM
runtime, remote persistence services, and a cross-platform GUI
database mapping/modeling/development tool.
## Project Status
### Project State
Ongoing
### Issues for Board
None
## Membership Data
Apache Cayenne was founded 2006-12-19 (17 years ago).
There are currently 23 committers and 9 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
Community changes, past quarter:
- No new PMC members. Last addition was Nikita Timofeev on 2017-06-25.
- No new committers. Last addition was Arseni Bulatski on 2018-12-10.
## Project Activity
After the release of 4.2, development has shifted to 5.0 (unreleased).
Prior versions are maintenance-only.
- Cayenne 4.0.x (stable)
- Maintenance only.
- Cayenne 4.1.x (stable)
- Maintenance only.
- Cayenne 4.2.x (stable)
- Maintenance only.
- Cayenne 5.0 (unreleased)
- Features being defined.
### Releases
- Cayenne 4.0.3 on 2023-03-02.
- Cayenne 4.1.1 on 2021-12-24.
- Cayenne 4.2 on 2023-05-25.
## Community Health
Cayenne is healthy.
JIRA activity increased while developer mailing list and commit traffic
were roughly the same. User mailing list traffic saw a large decline,
but questions are actively addressed.
-----------------------------------------
Attachment M: Report from the Apache CloudStack Project [Rohit Yadav]
## Description:
Apache CloudStack (ACS) is an IaaS (Infrastructure as a Service) cloud
orchestration platform. ACS manages many types of hypervisors, storage, and
networking devices.
## Project Status:
No issues to report.
## Membership Data:
- Apache CloudStack was founded 2013-03-20 (10 years ago)
- There are currently 131 committers and 53 PMC members in this project.
- The Committer-to-PMC ratio is roughly 9:4.
Community changes, past quarter:
- Daniel Augusto Veronezi Salvador was added to the PMC on 2023-09-05
- John Bampton was added as committer on 2023-08-01
- Sina Kashipazha was added as committer on 2023-08-25
## Project Activity:
- The Apache CloudStack project released the current LTS version
4.18.0.0 on 20th March 2023 and 4.18.1.0 on 12th September 2023.
- The previous LTS version received an updated release to 4.17.2.0 on
16th December, 2022.
- Apache CloudStack 4.19.0 is the next major release the
community is working towards, with a tentative release timeline
in Q4 of 2023.
- The PMC is actively discussing new PMC Candidates and new
Committers. There are two new committers added since the
previous report.
- The project is working to migrate to a new website that uses the
same static-site generator as the blog. This is work in progress and
shared with the community for feedback, review and testing. The
staging site is accessible at https://cloudstack.staged.apache.org
- Community organised one-day CloudStack India User-Group meetup
in Bangalore on 18th August 2023.
- The annual community organised CloudStack Collaboration conference
has been announced with registration and CFP open. The two-day hybrid
event will be taking place on November 23-24th in Paris and online.
https://www.cloudstackcollab.org
## Community Health:
Apropos of the activity report; the project is considered healthy.
- According to the apache statistics, the project achieved the
Community Health Score (Chi): 10.00 (Super Healthy)
- Commit activity:
315 commits in the past quarter (-10% decrease)
37 code contributors in the past quarter (15% increase)
- GitHub PR activity:
230 PRs opened on GitHub, past quarter (14% increase)
230 PRs closed on GitHub, past quarter (21% increase)
- GitHub issues:
132 issues opened on GitHub, past quarter (-19% change)
135 issues closed on GitHub, past quarter (6% increase)
- Mailing lists statistics:
dev@cloudstack.apache.org had a 26% decrease in traffic
in the past quarter (432 emails compared to 580)
issues@cloudstack.apache.org had a 87% decrease in
traffic in the past quarter (15 emails compared to 114)
marketing@cloudstack.apache.org had a 26% decrease in
traffic in the past quarter (26 emails compared to 35)
users@cloudstack.apache.org had a 20% decrease in traffic
in the past quarter (502 emails compared to 620):
## Releases:
Latest:
- 4.18.1.0 was released on 12th September 2023 -- EOL 1st Oct 2024.
- 4.18.0.0 was released on 20th March 2023 -- EOL 1st Oct 2024.
Reaching EOL:
- 4.17.2.0 was released on 16th December 2022 -- EOL 1st Jan 2024.
-----------------------------------------
Attachment N: Report from the Apache Cocoon Project [Cédric Damioli]
-----------------------------------------
Attachment O: Report from the Apache Commons Project [Gary D. Gregory]
## Description:
The mission of Apache Commons is the creation and maintenance of Java-focused
reusable libraries and components.
## Project Status:
Current project status: Ongoing with moderate activity.
Issues for the board: None.
## Membership Data:
Apache Commons was founded 2007-06-19 (16 years ago)
There are currently 149 committers and 42 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:2.
Community changes, past quarter:
- No new PMC members. Last addition was Matt Juntunen on 2021-06-25.
- No new committers. Last addition was Claude Warren on 2022-02-01.
## Project Activity:
Our recent releases are:
- COMPRESS-1.24.0 was released on 2023-09-08.
- PARENT-62 was released on 2023-09-05.
- DBCP-2.10.0 was released on 2023-09-03.
- PARENT-61 was released on 2023-08-29.
- PARENT-60 was released on 2023-08-23.
- DBUTILS-1.8.0 was released on 2023-08-08.
- LANG-3.13.0 was released on 2023-07-28.
- PARENT-59 was released on 2023-07-26.
- FILEUPLOAD-2.0.0-M1 was released on 2023-07-19.
- BUILD-PLUGIN-1.13 was released on 2023-06-28.
- RELEASE-PLUGIN-1.8.1 was released on 2023-06-28.
- CODEC-1.16.0 was released on 2023-06-21.
## Community Health:
We have had much more activity on the mailing lists, Jira, and GitHub. We are
also reviewing security reports as they come in and have been working through
that backlog. We had a successful participant in the Google Summer of
Code 2023 working on the Commons Statistics component.
-----------------------------------------
Attachment P: Report from the Apache Cordova Project [Jesse MacFadyen]
## Status report for the Apache Cordova project - September 2023
## Description:
- A platform for building native mobile applications using HTML, CSS and
JavaScript.
## Activity
Current work continues to be keeping up with changes to iOS and Android, our
most used platforms, and updating plugins.
Github discussions has become how our community supports each other.
Committers made large releases this quarter with major version bumps to
cordova-ios@7, cordova-plugin-file@8, cordova-plugin-media-capture@5,
cordova-plugin-camera@7, cordova-plugin-file-transfer@2,
cordova-plugin-media@7
## Issues:
- There are no issues requiring board attention at this time.
## Health report:
Our status dashboard at http://status.cordova.io remains mostly all green and
our nightly builds are still extremely stable.
ASF Project Statistics gives the project a Community Health Score (Chi): 4.70
Healthy
A small group of dedicated individuals continue to contribute and make
incremental releases. The project remains stable and continues to see good
traffic.
Our discussion area is live at https://github.com/apache/cordova/discussions
and activity is forwarded to the 'issues' list.
## Membership Data:
- There are currently 99 committers and 96 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 Pieter Van Poyer on 2021-04-05.
- No new committers. Last addition was Pieter Van Poyer on 2021-04-05.
## Releases:
- cordova-plugin-file-transfer@2.0.0 was released on 2023-09-13.
- cordova-plugin-media@7.0.0 was released on 2023-09-13.
- cordova-plugin-camera@7.0.0 was released on 2023-09-12.
- cordova-ios@7.0.1 was released on 2023-09-06.
- cordova-android@12.0.1 was released on 2023-08-28.
- cordova-plugin-media-capture@5.0.0 was released on 2023-08-18.
- cordova-ios@7.0.0 was released on 2023-07-10.
- cordova-plugin-file@8.0.0 was released on 2023-07-10.
## Github activity:
Issue close rate of 99% 101 issues opened on GitHub, past quarter (-15%
change) 100 issues closed on GitHub, past quarter (-55% change)
PR close rate of 91% 141 PRs opened on GitHub, past quarter (-4% change) 128
PRs closed on GitHub, past quarter (-27% change)
Commits 146 commits in the past quarter (-30% decrease) 14 code contributors
in the past quarter (-41% change)
-----------------------------------------
Attachment Q: Report from the Apache cTAKES Project [Pei Chen]
## Description:
The mission of cTAKES is the creation and maintenance of software related to
Natural language processing (NLP) tool for information extraction from
electronic medical record clinical free-text
## Project Status:
Current project status: Ongoing with moderate/low activity.
Issues for the board: There are no issues requiring board attention at
this time.
## Membership Data:
Apache cTAKES was founded 2013-03-19 (10 years ago)
There are currently 40 committers and 31 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:4.
Community changes, past quarter:
- No new PMC members. Last addition was Gandhi Rajan on 2018-07-12.
- No new committers. Last addition was Dennis Johns on 2023-01-06.
## Project Activity:
- Committee continues to work on the future release (5.x.x)
- Few volunteers came forward in testing a potential 5.x release.
- Committee migrating the website repo to git
- Last release was 4.0.0.1 patch on Jan 20 2021
- 4.0.0 was released on Apr 27 2017
- 3.2.2 was released on May 30 2015
## Community Health:
Mailing lists remain steady with moderate traffic.
dev@ctakes.apache.org had a 20% increase in traffic in the past quarter
(18 emails compared to 15)
-----------------------------------------
Attachment R: Report from the Apache Curator Project [Enrico Olivelli]
## Description:
The mission of Curator is the creation and maintenance of software related to
Java libraries that make using Apache ZooKeeper easier
## Project Status:
Current project status: Ongoing
Issues for the board: none
## Membership Data:
Apache Curator was founded 2013-09-18 (10 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 Kezhu Wang on 2023-03-25.
- No new committers. Last addition was Kezhu Wang on 2023-03-24.
## Project Activity:
We have reworked our website: https://curator.apache.org
Recent releases:
5.5.0 was released on 2023-04-28.
5.4.0 was released on 2022-10-28.
5.3.0 was released on 2022-07-04.
## Community Health:
During this quarter activity slowed down a little bit, but we are still
accepting patches, almost all the patches are contributed by committers. The
contributions are about small fixes and enhancements, driver by user requests.
Overall the community is small but healthy.
-----------------------------------------
Attachment S: Report from the Apache Daffodil Project [Mike Beckerle]
## Description:
The mission of Apache Daffodil is the creation and maintenance of software
related to an implementation of the Data Format Description Language (DFDL)
used to convert between fixed format data and more readily processed forms such
as XML or JSON
## Project Status:
The project is healthy based on ongoing steady activity and releases.
Daffodil version 3.5.0 was released. The Daffodil VSCode Extension version
1.3.0 was released in June, and release 1.3.1 was released on Sept 12.
Issues for the board: none.
## Membership Data:
Apache Daffodil was founded 2021-02-16 (3 years ago)
There are currently 19 committers and 18 PMC members in this project.
The Committer-to-PMC ratio is roughly 1:1.
Community changes, past quarter:
- Robert Strickland was added to the PMC on 2023-07-05
- Regis Thomas was added to the PMC on 2023-07-31
## Project Activity:
In addition to the releases mentioned above, Daffodil project status was
presented at the CDTF (Cross Domain Technology Forum - a cyber-security
related event attended by ~600 people)
Our submission for the Community Over Code 2023 conference was not accepted,
but at least 2 project members plan to attend anyway.
Collaboration with the Apache Drill project is ongoing toward adding a
Daffodil capability to Drill. This will allow Drill SQL queries against data
files having DFDL Schemas describing their format.
## Community Health:
Activity level is good/steady, and we added two committers/members to our PMC
this period. Their primary work thusfar contributes to the VSCode Extension
sub-project.
-----------------------------------------
Attachment T: Report from the Apache DeltaSpike Project [Mark Struberg]
## Description:
Apache DeltaSpike is a suite of portable CDI (Contexts & Dependency
Injection) extensions intended to make application development easier when
working with CDI and Java EE. Some of its key features include:
- A core runtime that supports component configuration, type safe messaging
and internationalization, and exception handling.
- A suite of utilities to make programmatic bean lookup easier.
- A plugin for Java SE to bootstrap various CDI containers.
- JSF integration
- JPA integration and transaction support.
- A Data module, to create an easy to use repository pattern on top of JPA.
- Testing support to allow low level unit testing of CDI enabled projects.
## Issues:
There are no issues requiring board attention at this time.
## Activity
Finishing the work on CDI-2.0 was blocked by the relase of OWB.
With this done we expect a native Jakarta EE release soonish.
## Community Health
Still a few around, although not as many as we'd love to see.
## Releases
- 1.9.6 was released on 2022-04-12.
- 1.9.5 was released on 2021-03-10.
- 1.9.4 was released on 2020-06-12.
## Project Composition:
- There are currently 35 committers and 19 PMC members in this project.
- The Committer-to-PMC ratio is roughly 9:5.
## Community changes, past quarter:
- No new PMC members. Last addition was Harald Wellmann on 2016-05-19.
- No new committers. Last addition was Christian Beikov on 2019-10-21.
-----------------------------------------
Attachment U: Report from the Apache Drill Project [Charles Givre]
## Description:
The mission of Drill is the creation and maintenance of software related to
Schema-free SQL Query Engine for Apache Hadoop, NoSQL and Cloud Storage
## Project Status:
Current project status: Project is ongoing.
Issues for the board: No issues for the Board.
## Membership Data:
Apache Drill was founded 2014-11-18 (9 years ago)
There are currently 62 committers and 27 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 James Turton on 2022-01-23.
- No new committers. Last addition was Maksym Rymar on 2022-10-19.
## Project Activity:
We had a relatively quiet quarter. Our last bug fix release was in April.
We will likely release 1.21.2 in the next quarter.
Recent releases:
1.21.1 was released on 2023-04-29.
1.21.0 was released on 2023-02-21.
1.20.3 was released on 2023-01-07.
## Community Health:
The Drill community remains strong and engaged, but we did have a quieter
summer. We have a fairly significant component which we are working on
which is the integration of Apache Daffodil and Drill, as well as an XSD
reader for XML.
* dev@drill.apache.org had a 18% decrease in traffic
in the past quarter (198 emails compared to 239)
* issues@drill.apache.org had a 48% decrease in traffic
in the past quarter (129 emails compared to 245)
* user@drill.apache.org had a 39% increase in traffic
in the past quarter (32 emails compared to 23)
14 issues opened in JIRA, past quarter (-51% change)
4 issues closed in JIRA, past quarter (-81% change)
25 commits in the past quarter (-50% change)
8 code contributors in the past quarter (-27% change)
13 PRs opened on GitHub, past quarter (-45% change)
13 PRs closed on GitHub, past quarter (-53% change)
7 issues opened on GitHub, past quarter (-36% change)
4 issues closed on GitHub, past quarter (100% increase)
-----------------------------------------
Attachment V: Report from the Apache Druid Project [Gian Merlino]
Report date: 9/10/2023
## Description
Apache Druid is a high performance real-time analytics database. It is
designed for workflows where low-latency query and ingest are the main
requirements. It implements ingestion, storage, and querying subsystems. Users
interface with Druid through built-in SQL and JSON APIs, as well as
third-party applications.
Druid has an extensive web of connections with other Apache projects: Calcite
for SQL planning, Curator and ZooKeeper for coordination, Kafka and Hadoop as
data sources, Avro, ORC, or Parquet as supported data input formats, and
DataSketches for scalable approximate algorithms. Druid can also be used as a
data source by Superset.
## Issues
There are no issues requiring board attention at this time.
## Activity
Our last major release was Druid 27.0.0, which contained 316 new features, bug
fixes, performance enhancements, documentation improvements, and additional
test coverage from 50 contributors.
The project recently decided to resolve a security issue that has been open
for over a year by deciding it was not a vulnerability, after much sporadic
back-and-forth between the project, security team, and original reporter over
that time. We regret that this took so long and are reminded of the importance
of promptly resolving these reports.
Druid Summit 2023 was recently announced, a virtual conference being held
December 5–6, 2023. It is being organized by Imply with permission from the
project.
In the past three months (mid Jun–mid Sep 2023), mailing list traffic is down
10% relative to the prior three months. This is a smaller change than we have
seen in prior reports, perhaps indicating that mailing list activity has
reached an equilibrium.
Meanwhile, development activity on GitHub is up for both PRs (10%) and commits
(17%). The number of unique contributors (61) is similar to last report (64).
Our Slack workspace at https://apachedruidworkspace.slack.com/ stands at
1,949 members, up 438 members (29%) since our last report.
A Helm chart for Druid was contributed after the helm/charts repository on
GitHub was deprecated. However, we have not included this in any release since
then, due to uncertainty about whether or not we need to perform formal IP
clearance for this contribution, and a lack of volunteers willing to spend the
time to sort this out. We hope to be able to sort this out for a subsequent
release.
## Recent PMC changes
- Currently 35 PMC members.
- 2 new PMC members since the last report:
- Karan Kumar (2023-07-17)
- Kashif Faraz (2023-07-17)
## Recent committer changes
- Currently 64 committers.
- 4 new committers since the last report:
- Raul Gidwani (2023-08-27)
- Adarsh Sanjeev (2023-08-17)
- Abhishek Balaji Radhakrishnan (2023-08-17)
- Soumyava Das (2023-08-17)
## Recent releases
- 27.0.0, a major release, on 2023-08-11.
- 26.0.0, a major release, on 2023-05-23.
## Development activity by the numbers
In the last quarter:
- 1084 commits from 61 contributors
- 1006 pull requests opened
- 1024 pull requests merged/closed
- 96 issues opened
- 696 issues closed
-----------------------------------------
Attachment W: Report from the Apache ECharts Project [Wenli Zhang]
## Description:
The mission of Apache ECharts is the creation and maintenance of software
related to a charting and data visualization library written in JavaScript
## Project Status:
Current project status: Dormant
Issues for the board: NA
## Membership Data:
Apache ECharts was founded 2020-12-16 (3 years ago)
There are currently 29 committers and 14 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 He Hao on 2022-07-06.
- Linghao Su was added as committer on 2023-08-01
## Project Activity:
The Apache ECharts project has been actively working on various features
and bug fixes, as evidenced by recent contributions from community members
and version 5.4.3 was released on 2023-07-18.
## Community Health:
The Apache ECharts project has seen a decrease in mailing list traffic and
contributors but an increase in commits and PRs opened on GitHub.
Overall, the project maintains a healthy level of activity and engagement,
with ongoing development and community involvement.
-----------------------------------------
Attachment X: Report from the Apache Felix Project [Karl Pauls]
## Description:
Apache Felix is a project aimed at implementing specifications from the OSGi
Alliance as well as implementing other supporting tools and technologies
aligned with OSGi technology.
## Project Status:
Current project status: Ongoing, with low activity.
Issues for the board: none.
## Membership Data:
Apache Felix was founded 2007-03-28 (16 years ago)
There are currently 68 committers and 27 PMC members in this project.
The Committer-to-PMC ratio is roughly 9:4.
Community changes, past quarter:
- No new PMC members. Last addition was Georg Henzler on 2019-06-10.
- No new committers. Last addition was Robert Munteanu on 2020-07-20.
## Project Activity:
- Existing implementations have been improved/enhanced based on community
feedback.
- We retired quite some components that have not seen activity in years.
- The http subproject is moving to the Jakarta API (away from javax.*).
- Released 34 components. Some are bug fixes/minor improvements but most are
related to the move to the Jakarta API.
### Releases
- org.apache.felix.webconsole-4.9.4 was released on 2023-09-11.
- org.apache.felix.http.jetty-4.2.18 was released on 2023-09-09.
- org.apache.felix.healthcheck.webconsoleplugin-2.2.0 was released on
2023-09-06.
- org.apache.felix.http.webconsoleplugin-1.1.0 was released on 2023-09-06.
- org.apache.felix.webconsole-4.9.2 was released on 2023-09-06.
- org.apache.felix.webconsole.plugins.ds-2.3.0 was released on 2023-09-06.
- org.apache.felix.webconsole.plugins.event-1.2.0 was released on 2023-09-06.
- org.apache.felix.webconsole.plugins.memoryusage-1.1.0 was released on
2023-09-06.
- org.apache.felix.webconsole.plugins.obr-1.1.0 was released on 2023-09-06.
- org.apache.felix.webconsole.plugins.packageadmin-1.1.0 was released on
2023-09-06.
- org.apache.felix.http.sslfilter-1.2.8 was released on 2023-08-31.
- org.apache.felix.http.sslfilter-2.0.2 was released on 2023-08-31.
- org.apache.felix.inventory-2.0.0 was released on 2023-08-31.
- org.apache.felix.webconsole-4.9.0 was released on 2023-08-31.
- org.apache.felix.healthcheck.core-2.1.0 was released on 2023-08-27.
- org.apache.felix.healthcheck.generalchecks-3.0.8 was released on 2023-08-27.
- org.apache.felix.http.base-5.1.0 was released on 2023-08-27.
- org.apache.felix.http.bridge-5.1.0 was released on 2023-08-27.
- org.apache.felix.http.jetty-5.1.0 was released on 2023-08-27.
- org.apache.felix.http.wrappers-1.0.0 was released on 2023-08-27.
- org.apache.felix.http.base-4.2.10 was released on 2023-08-21.
- org.apache.felix.http.base-5.0.4 was released on 2023-08-21.
- org.apache.felix.http.bridge-4.2.12 was released on 2023-08-21.
- org.apache.felix.http.bridge-5.0.6 was released on 2023-08-21.
- org.apache.felix.http.jetty-4.2.16 was released on 2023-08-21.
- org.apache.felix.http.jetty-5.0.6 was released on 2023-08-21.
- org.apache.felix.webconsole-4.8.12 was released on 2023-08-04.
- configadmin.plugin.interpolation-1.2.8 was released on 2023-07-24.
- org.apache.felix.http.base-4.2.8 was released on 2023-07-23.
- org.apache.felix.http.bridge-4.2.10 was released on 2023-07-23.
- org.apache.felix.http.jetty-4.2.14 was released on 2023-07-23.
- org.apache.felix.webconsole-4.8.10 was released on 2023-07-23.
- org.apache.felix.healthcheck.webconsoleplugin-2.1.0 was released on
2023-07-21.
- org.apache.felix.healthcheck.generalchecks-3.0.6 was released on 2023-07-08.
## Community Health:
- Overall the project is in ok health with very little ongoing activity.
- There is a decline in community activity and in general, we don't see a lot
of new development right now. We are at the lookout for new topics and
contributors but for now, we started reducing our surface area by retiring
components that haven't seen activity in while and don't have a clear
commitment to be maintained by somebody. Hopefully, that will lessen the
load on the existing maintainers.
- Questions on the user list are answered, development concerns are either
discussed on the mailing list or directly in the JIRA issues.
- We had no issues voting on releases and JIRA issues are generally addressed.
-----------------------------------------
Attachment Y: Report from the Apache Flex Project [Harbs]
## Description:
The mission of the Apache Flex project is to create and maintain software
related to the development of expressive web applications that deploy to all
major browsers, desktops and devices (including smartphones, tablets and tv)
## Project Status:
Current project status: The project is stable with little activity
Issues for the board: None
## Membership Data:
Apache Flex was founded 2012-12-19 (11 years ago)
There are currently 68 committers and 46 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 Greg Dove on 2023-03-03.
- No new committers. Last addition was Greg Dove on 2016-09-07.
## Project Activity:
The is little activity. There was a bit of work done on BlazeDS this quarter
and the website was updated with some BlazeDS information.
- Apache Flex BlazeDS 4.8.0 was released on 2023-04-17.
- flex-maven-tools/flex-sdk-converter 1.1.0 was released on 2023-02-20.
- Install Apache Flex 3.3.2 was released on 2018-07-09.
## Community Health:
No significant change. There has been a slight increase in activity this
quarter mostly related to BlazeDS.
- dev@flex.apache.org had a 18% increase in traffic in the past quarter (26
emails compared to 22)
- 1 issue opened in JIRA, past quarter (100% increase)
- 22 commits in the past quarter (175% increase)
- 4 code contributors in the past quarter (no change)
- 4 PRs opened on GitHub, past quarter (33% increase)
- 3 PRs closed on GitHub, past quarter (300% increase)
-----------------------------------------
Attachment Z: Report from the Apache Flink Project [Robert Metzger]
## Description:
The mission of Flink is the creation and maintenance of software related to
platform for scalable batch and stream data processing
## Project Status:
Current project status: Ongoing, with high activity
Issues for the board: none
The project is wrapping up the 1.18 release of Flink, with major (auto-)scaling
and performance improvements, planned for end of September.
At the same time, the community is actively planning the release of Flink 2.0.
## Membership Data:
Apache Flink was founded 2014-12-17 (9 years ago)
There are currently 106 committers and 48 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:3.
Community changes, past quarter:
- Matthias Pohl was added to the PMC on 2023-08-03
- Hangxiang Yu was added as committer on 2023-08-07
- Hong Liang Teoh was added as committer on 2023-08-02
- Weihua Hu was added as committer on 2023-08-10
- Yanfei Lei was added as committer on 2023-08-07
- Fang Yong was added as committer on 2023-07-24
## Project Activity:
The project is actively preparing the 1.18 release. The feature freeze was on
July 24th, we are currently testing and stabilizing the release, with a planned
release end of September.
The discussions about Flink 2.0 are still ongoing. The release managers have
driven a vote on "must have" items for the 2.0 release. Many of them are
removal of deprecated APIs (such as the DataSet batch processing API, the Scala
API), rework of configuration options, the REST API etc.
The goal is to ship Flink 2.0 by end of 2024 (after Flink 1.20), while
deprecating everything affected by 2.0 in the releases to come.
Recent releases:
- connector-mongodb-1.0.2 was released on 2023-08-15
- Flink Kubernetes operator 1.16.0 was relesed on 2023-08-15
- flink-connector-jdbc was released on 2023-06-29
- connector-pulsar-3.0.1 was released on 2023-06-07
## Community Health:
After reporting slight declines in the dev@ activity (-12%) in the last report,
we finally see a (tiny) 2% increase in the dev@ activity again (2362 emails).
user@ even saw an increase of 11%, despite the Flink Slack channel being quite
active.
The # of commits is down -36%, same for contributors (-22%) and PRs
closed (-23%). However, as mentioned before, the project is actively moving
all Flink connectors to separate repositories, so this is expected (assuming
the community health data is only generated from the main repo).
-----------------------------------------
Attachment AA: Report from the Apache Giraph Project [Dionysios Logothetis]
-----------------------------------------
Attachment AB: Report from the Apache Gobblin Project [Abhishek Tiwari]
## Description:
The mission of Apache Gobblin is the creation and maintenance of software
related to a distributed data integration framework that simplifies common
aspects of big data integration such as data ingestion, replication,
organization and lifecycle management for both streaming and batch data
ecosystems
## Project Status:
Current project status: Ongoing
Issues for the board: No issues worth board attention
## Membership Data:
Apache Gobblin was founded 2021-01-19 (3 years ago)
There are currently 19 committers and 12 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:3.
Community changes, past quarter:
- No new PMC members. Last addition was Abhishek Tiwari on 2021-01-19.
- No new committers. Last addition was William Lo on 2022-08-31.
## Project Activity:
- Salesforce Source was refactored for improved testability
- Generalize WorkUnit persistence to support frameworks other that MR
- Performance of ORC Writer improved
- Ability added in Kafka source to filter topics
- Support added to process GMCEs from different Kafka brokers
- Total DAG count metric added for DAG state store
- Self tuning buffered ORC writer added
- High watermark metadata query for SFDC optimized for performance
- Apache Helix integration upgraded to Helix 1.0
- Improved encapsulation of FlowTriggerHandler and related helper functions
- Standardized all logging to UTC
- Support for multiple tokens in ProxiedFileSystem
- Set default trigger time for adhoc flows
- Improved handling of invalid cron schedules
- Enhance ManifestBasedDatasetFinder with config for specifying an alternate
FS solely for reading manifests
- Improve Kafka source / extractor utility to get simple names for Kafka
brokers
- Enabled scheduler for non-leader in multi-active scheduler configuration
- Fixed HiveMetadataWriter bug to ensure that hive schema columns are
consistent with the Avro.schema.literal
- Fixed missing flow execution id causing SQL Errors
- New instrumend ORC writer added
- Introduced FlowCompilationValidationHelper & SharedFlowMetricsSingleton for
sharing between Orchestrator & DagManager
- Support added to preserve sticky bit across distcp copies
- Override flag added to force generate a job execution id based on Gobblin
cluster system time
- Metadata writer tests improved to work with Iceberg 1.2.0
- Flow trigger handler leasing metrics added
- Reduced number of Hive calls during schema related updates in metadata
registration
- Support to emit warning for retention of Snapshot Hive Tables instead of
failing job
- Added Flow Group & Name to Job Config for Job Scheduler
- Tags added to dagmanager metrics for extensibility
- Support to delete existing workflows on exceptions in the JobLauncher
- Improve calculation of container count based on workflows marked for
deletion
- Optimized disabling of current live instances at GobblinClusterManager
startup
- Changed parallelstream to stream in DatasetsFinderFilteringDecorator to
prevent classloader issues
- Utility added for detecting non optional unions and convert dataset urn to
hive compatible format
- Fixed Helix Job scheduler to prevent replacement of running workflow if
within configured time
- Multi-active, non blocking host leader was added for better performance
- Task Reliability was improved by handling Job Cancellation and Graceful
Exits for Error-Free Completion
- Apache Iceberg integration was upgraded from v0.11.1 to v1.2.0
- Improved Container Calculation and Allocation Methodology
- Improved logging, additional unit tests added, and multiple bug fixes
Last Release date: 0.17.0 on 30th Aug, 2023.
## Community Health:
- There have been 65 commits since June 2023.
- 53 commits have been from non-committers.
- William Lo was voted in Aug, 2022 as a committer. We constantly look for
consistent contributors to vote them in as Committers.
-----------------------------------------
Attachment AC: 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.
## Project Status:
Current project status: Ongoing project with low activity
Issues for the board: None
## Membership Data:
Apache Gora was founded 2012-01-24 (12 years ago)
There are currently 31 committers and 29 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 Lahiru Jayasekara on 2020-04-30.
- No new committers. Last addition was Lahiru Jayasekara on 2020-04-27.
## Project Activity:
- Received several contributions from external people and several
PMC members volunteered to review and merge to main branch.
- Several PMC members volunteered in mentoring GSoC for this year, we were
able to successfully complete these projects, all contributions were
merged to main branch. We will explore the possibilities of expand our
committer base further with GSoC participants.
- As stated with previous reports as well, except for major activities
related to GSoC projects, we have not been able to make significant progress
on our next major release, 0.9 was released on 2019-08-15.
## Community Health:
- We observed the usual activity level on both Github and mailing lists for
the past quarter. So nothing significant that worth mentioning for the this
quarterly report compared to previous reports. Activity level for past
quarter on Github and mailing lists was mainly influenced by the GSoC
work and external contributions which was previously mentioned.
-----------------------------------------
Attachment AD: Report from the Apache Guacamole Project [Mike Jumper]
## Description:
The mission of Apache Guacamole is the creation and maintenance of software
related to providing performant, browser-based remote access
## Project Status:
Current project status: Ongoing with moderate activity
Issues for the board: none
## Membership Data:
Apache Guacamole was founded 2017-11-14 (6 years ago)
There are currently 14 committers and 10 PMC members in this project.
The Committer-to-PMC ratio is 7:5.
Community changes, past quarter:
- No new PMC members. Last addition was Luke on 2023-02-22.
- No new committers. Last addition was Luke on 2020-02-07.
## Project Activity:
The project is currently working towards a 1.5.4 release, continuing the new
minor/bugfix release cycle that we adopted to allow more frequent releases.
Larger in-progress efforts that will more likely be part of a 1.6.0+ release
include support for fine-grained scheduling restrictions, fine-grained
application events and logging, and an experimental X.org driver.
Recent releases:
- 1.5.3 was released on 2023-07-31.
- 1.5.2 was released on 2023-05-25.
- 1.5.1 was released on 2023-04-13.
## Community Health:
The community continues to be active and healthy. Among other community
contributions is an extremely large and involved set of changes for migrating
the main web application UI from AngularJS to Angular (~150K+ lines). We are
extremely thankful for this, though it will take significant time to review.
-----------------------------------------
Attachment AE: Report from the Apache Gump Project [Stefan Bodewig]
# Description
Apache Gump is a cross-project continuous integration server. Gump's
intention isn't so much to be a CI server but rather a vehicle that
makes people look beyond their project's boundaries and helps the
projects to collaborate.
Gump is written in Python and supports several build tools and version
control systems. The Apache installation of Gump builds ASF as well as
non-ASF projects and their dependencies. It started in the Java part of
the foundation but also builds projects like APR, HTTPd and OpenSSL.
# Project Status
Current Status: dormant - when things need to be done, they get done
Issues: There are no issues requiring board attention.
# Membership Data
Apache Gump was founded 2004-02-18 (17 years ago) There are currently 16
committers and 10 PMC members in this project. The Committer-to-PMC
ratio is 8:5.
Community changes, past quarter:
* No new PMC members. Last addition was Mark Thomas on 2014-12-03.
* No new committers. Last addition was Konstantin Kolinko on 2015-02-11.
# Project Activity
The Tomcat community is the only one still using Gump actively and the
only activity in Gump is around keeping the infrastructure alive and
tweaking things for the benefit of Tomcat builds.
We will certainly support any other project that wants to get the
benefit of the early warning system for backwards incompatible changes
Gump provides, but we are not actively recruiting projects.
## Releases
Gump has never done any releases. One reason for this is that the ASF
installations of Gump work on the latest code base almost all of the
time following its "integrate everything continuously" philosophy.
# Community Health
There isn't much happening but help is there when anybody needs it.
Apart from foundation wide announcements or infrastructure team messages
nobody has posted any message to the Gump mailing list or asked for a
change who is not a member of the Gump PMC already for the last almost
five years.
-----------------------------------------
Attachment AF: Report from the Apache Helix Project [Junkai Xue]
## Description:
The mission of Helix is the creation and maintenance of software related to A
cluster management framework for partitioned and replicated distributed
resources
## Project Status:
Current project status: ongoing, moderate
Issues for the board: no major issue.
## Membership Data:
Apache Helix was founded 2013-12-17 (10 years ago)
There are currently 28 committers and 18 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 Jiajun Wang on 2022-11-02.
- Molly Gao was added as committer on 2023-06-06
## Project Activity:
- 1.3.0 was released on 2023-07-25
- 1.2.0 was released on 2023-05-02
- 1.1.0 was released on 2023-01-04
## Community Health:
The better operability improvement project is in the progress:
1. Ondemand partition rebalance - completed
2. Node evacuation partition from a target node - completed
3. Node 1:1 partition swapping - in progress
Next target for the coming quarter:
The Helix REST have management API for users to do fleet management,
including health check, customized check, parallel instance pre stop, etc.
But now the REST has performance issue with fanout querying Zookeeper. It can
lead regular shard management to slow reading ZK data.
Concrete target:
1. Improve Helix REST service with caching + ZK notification
2. Improve management APIs usability including cross fault zone parallel
pre instance stop, more flexible customized check.
3. Node auto populate toplogical information.
-----------------------------------------
Attachment AG: Report from the Apache Hive Project [Naveen Gangam]
-----------------------------------------
Attachment AH: Report from the Apache Hop Project [Hans Van Akelyen]
## Description:
The mission of Apache Hop is the creation and maintenance of software related
to a platform for data orchestration
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache Hop was founded 2021-12-15 (2 years ago)
There are currently 23 committers and 10 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 Bart Maertens on 2021-12-15.
- No new committers. Last addition was Shuiliang Xue on 2022-09-28.
## Project Activity:
It has been a slower period over the summer but we are preparing our 2.6
release. We expect activity to increase again in the coming period.
## Community Health:
Overall the community is in a good spot from a user perspective, we have
increased activity on the mailing lists and on our socials. We are trying to
get more users move from direct communication (chat) to the mailing list but
that is a hard sell. We also hope to start onboarding a couple extra
committers in the near future.
-----------------------------------------
Attachment AI: Report from the Apache HTTP Server Project [Joe Orton]
## Description:
The mission of HTTP Server is the creation and maintenance of software related
to Apache Web Server (httpd)
## Project Status:
Current project status: Ongoing, moderate activity
Issues for the board: none
## Membership Data:
Apache HTTP Server was founded 1995-02-27 (29 years ago)
There are currently 128 committers and 55 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 Giovanni Bechis on 2021-06-11.
- No new committers. Last addition was Emmanuel Dreyfus on 2022-11-05.
## Project Activity:
There have been no new releases since 2.4.57 shipped in April this year as
covered in the last quarterly report. A recent mailing list discussion showed
some interest from committers in rolling and testing a new 2.4.x release.
As mentioned in my previous report a formal vote was held in May on moving the
read/write repository from Subversion to git. This was carried with a strong
consensus in favour of the move, but is yet to be put into action.
The project continues to see moderately active development, with a faster pace
and volume of change in some areas (HTTP/2 support in particular), and smaller
feature work and bug fixing across the rest of the code base. Most work is
being actively backported to the 2.4.x branch after review.
## Community Health:
Community activity was relatively quiet compared to previous quarter, likely
since we did not see the usual uptick of commits and discussion around a
release cycle. The number of GitHub PRs being used continues to increase,
again with a significant number of PRs being submitted by non-committers.
-----------------------------------------
Attachment AJ: Report from the Apache Hudi Project [Vinoth Chandar]
## Description:
The mission of Apache Hudi is the creation and maintenance of software related
to providing atomic upserts and incremental data streams on Big Data
## Project Status:
Current project status: Ongoing
Issues for the board: none.
## Membership Data:
Apache Hudi was founded 2020-05-19 (3 years ago)
There are currently 33 committers and 17 PMC members in this project.
The Committer-to-PMC ratio is roughly 9:5.
Community changes, past quarter:
- No new PMC members. Last addition was Y Ethan Guo on 2023-03-13.
- No new committers. Last addition was Yue Zhang on 2022-12-31.
## Project Activity:
Hudi community is going through the process of voting on the 0.14 release,
with brings record level indexing to Hudi, with RC1 voted down and RC2 being
worked on. The community hopes to release 0.14 by end of the month.
In parallel, the community is also working on finalizing all the various
design details for the upcoming Hudi 1.0, which will introduce major revamp in
Hudi's storage format aimed at generalizing the core transactional layer, with
database like semantics. The project's master has already moved to
1.0.0-SNAPSHOT and a bunch of major changes are already been landed. We have
public tracking of the effort maintained in cwiki.
https://cwiki.apache.org/confluence/display/HUDI/1.0+Execution+Planning
## Community Health:
Project continues to see healthy engagement from tons of users and
contributors. Other than the increase in backlog of pull requests due to
committers/PMCs being busy with the two releases, we don't cite any specific
reasons for the drop in code commits. We expect to pick up pace once 0.14 is
finalized and more resources are available.
-----------------------------------------
Attachment AK: Report from the Apache Iceberg Project [Ryan Blue]
## Description:
Apache Iceberg is a table format for huge analytic datasets that is designed
for high performance and ease of use.
## Project Status:
Current project status: Ongoing
Issues for the board: none
## Membership Data:
Apache Iceberg was founded 2020-05-19 (3 years ago)
There are currently 24 committers and 16 PMC members in this project.
The Committer-to-PMC ratio is 3:2.
Community changes, past quarter:
- No new PMC members. Last addition was Szehon Ho on 2023-04-20.
- No new committers. Last addition was Amogh Jahagirdar on 2023-04-25.
## Project Activity:
Releases:
* PyIcberg 0.4.0 was released on 2023-07-23
* 1.3.1 was released on 2023-07-25
Java:
* Preparing for a 1.4.0 release in Sept/Oct
* Added dependency bundles for AWS, GCP, and Azure
* Added Azure FileIO implementation
* Added API for multi-table commits
* Performance optimizations for delete file scan planning
* Spark: Implemented adaptive split sizing
* Spark: Implemented function pushdown in v2 expressions
* Flink: Added bucketing only key-by strategy
* Build: Updated to Gradle version catalog
* Making progress on the reference implementation of common views
* Continuing work on table encryption
Python:
* 0.5.0 rc1 vote is under way
* Added support for serverless environments
* Implemented schema evolution
* Moved to Pydantic v2
* Added support for positional deletes
* Substantially improved Avro read performance
* Added conversion from Parquet to Iceberg schemas
* Added support for FSSpec and HDFS data
* Added SQL filter parsing
Rust:
* Created a repository for the Rust implementation, iceberg-rust
* 25 PRs merged
* Implemented base table metadata (e.g., types, transforms)
* Implemented visitors for working with nested structures
* Added Avro/Iceberg schema conversion
* Added build tooling
Go:
* Created a repository for the Go implementation, iceberg-go
* Added schema and types
## Community Health:
The largest development in the community is the addition of the Rust and Go
repositories, which is shown in the increase in code contributors this quarter.
The new implementations will also lead to new committers and PMC members. The
community has had good discussions about how manage contributions, to build
confidence in the implementations as well as to help new contributors become
familiar with the way the Apache community operates. (Along with ASF
requirements like license documentation.)
Two community metrics show decreases. Dev list traffic tends to vary because of
how the community uses the dev list -- that is, mostly for large design
discussions. The number of issues closed was also lower than normal and is not
expected to fluctuate. We will take a look and see what the difference is.
-----------------------------------------
Attachment AL: Report from the Apache Incubator Project [Justin Mclean]
# Incubator PMC report for September 2023
The Apache Incubator is the entry path into the ASF for projects and
codebases wishing to become part of the Foundation's efforts.
There are presently 24 podlings incubating. In August, podlings executed 6
distinct releases.
Datalab has completed a retirement vote, while Liminal still needs to
submit the report, and we will take a PPMC roll call. As some inactive
projects are retiring, the number of absent reports each month is
decreasing.
There is a new project, Hexagon Toolkit, seeking a mentor, but the project
may have applied too early and needs to do more work on building a
community around the project first. IPMC members also provided other useful
feedback. Another new project, ResilientDB, a Blockchain Platform, also
seeks entry into the incubator. Several IPMC members have expressed
interest, and we may see it entering the incubator in the coming months.
There has also been some off-list discussion about several other projects
that wish to join the ASF via the Incubator.
## Community
### New IPMC members:
- None
### People who left the IPMC:
- None
## New Podlings
- None
## Podlings that failed to report, expected next month
- Liminal
## Graduations
- None
The board has motions for the following:
- None.
## Releases
The following releases entered distribution during the month of
August:
- pekko-connectors-kafka 1.0.0
- pekko-http 1.0.0
- pekko-management 1.0.0
- pekko-grpc 1.0.0
- pekko-sbt-paradox 1.0.0
- OpenDAL 0.39.0
## IP Clearance
- None
## Legal / Trademarks
- None
## Infrastructure
- None
## Table of Contents
[Baremaps](#baremaps)
[KIE](#kie)
[Liminal](#liminal)
[Nemo](#nemo)
[Uniffle](#uniffle)
[Wayang](#wayang)
--------------------
## Baremaps
Apache Baremaps is a toolkit and a set of infrastructure components for
creating, publishing, and operating online maps.
Baremaps has been incubating since 2022-10-10.
### Three most important unfinished issues to address before graduating:
1. Getting the code and documentation website in compliance with Apache
standards
2. Growing the community
3. Making releases
### 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 have had several new commiters join the project. We are also seeing
new activity from people asking questions and creating issues.
### How has the project developed since the last report?
- We addressed most of the podling website requirements and updated the
content and layout of the website
- We implemented new features and fixed numerous issues.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [X] Initial setup
- [X] Working towards first release
- [X] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
2023-04-04
We are working on a new release (the vote for the first release candidate
failed).
### When were the last committers or PPMC members elected?
2023-08-31
### Have your mentors been helpful and responsive?
Yes, the mentors' advice has been very helpful especially to comply to
Apache licensing issues and guidelines.
### Is the PPMC managing the podling's brand / trademarks?
Yes
### Signed-off-by:
- [ ] (baremaps) Bertrand Delacretaz
Comments:
- [ ] (baremaps) Martin Desruisseaux
Comments:
- [X] (baremaps) Julian Hyde
Comments: Community seems to be growing and evolving well
(judging by commit activity, new committers, moderate dev
list activity, bugs being logged). I would like to hear
more about Baremaps' efforts to grow community (e.g. talks
at meetups, online demos) and will ask them for an update
next reporting cycle.
- [X] (baremaps) Calvin Kirs
Comments:
- [ ] (baremaps) George Percivall
Comments:
- [ ] (baremaps) Martin Desruisseaux
Comments:
### IPMC/Shepherd notes:
--------------------
## KIE
KIE (Knowledge is Everything) is a community of solutions and supporting
tooling for knowledge engineering and process automation, focusing on
events, rules, and workflows.
KIE has been incubating since 2023-01-13.
### Three most important unfinished issues to address before graduating:
1. Finish code migration and IP clearance
2. Release
3. Grow the community
### Are there any issues that the IPMC or ASF Board need to be aware of?
I do not believe so.
### How has the community developed since the last report?
There has been more interest in KIE over the last couple of months. No
new members yet, but we have had people asking about it and expressing
interest once we get the code moved over.
### How has the project developed since the last report?
We were finally able to get legal documents signed! SGA has been accepted
by the ASF, trademarks will be coming once we graduate, as agreed upon by
the ASF. We’re working on migrating code, getting headers in place, and
exploring CI/CD options.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup - Pretty good, code migration of a large repo is not
easy :)
- [ ] Working towards first release - Slow progress, but we’re getting
there.
- [ ] Community building - Glad to see interest from people, I expect
this to continue
- [ ] Nearing graduation - It is a goal that’s out there, we’re
progressing, albeit slowly.
- [ ] Other:
### Date of last release:
N/A
### When were the last committers or PPMC members elected?
Middle of August
### Have your mentors been helpful and responsive?
Brian has been very helpful. The others have also pitched in, no concerns.
### Is the PPMC managing the podling's brand / trademarks?
We have not yet turned over the brand, per an agreement with the ASF and
Red Hat.
### Signed-off-by:
- [X] (kie) Brian Proffitt
Comments:
- [ ] (kie) Claus Ibsen
Comments:
- [X] (kie) Andrea Cosentino
Comments:
### IPMC/Shepherd notes:
--------------------
## Liminal
Apache Liminal is an end-to-end platform for data engineers and scientists,
allowing them to build, train and deploy machine learning models in a robust
and agile way.
Liminal has been incubating since 2020-05-23.
### Three most important unfinished issues to address before graduating:
1.
2.
3.
### Are there any issues that the IPMC or ASF Board need to be aware of?
### How has the community developed since the last report?
### How has the project developed since the last report?
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [ ] Working towards first release
- [ ] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
XXXX-XX-XX
### When were the last committers or PPMC members elected?
### Have your mentors been helpful and responsive?
### Is the PPMC managing the podling's brand / trademarks?
### Signed-off-by:
- [ ] (liminal) Jean-Baptiste Onofré
Comments: I think it's a good time to discuss about the concrete
state of the podling and roadmap.
- [ ] (liminal) Henry Saputra
Comments:
- [ ] (liminal) Uma Maheswara Rao G
Comments:
- [ ] (liminal) Davor Bonaci
Comments:
- [ ] (liminal) Liang Chen
Comments:
### IPMC/Shepherd notes:
--------------------
## Nemo
Nemo is a data processing system to flexibly control the runtime behaviors
of a job to adapt to varying deployment characteristics.
Nemo has been incubating since 2018-02-04.
### Three most important unfinished issues to address before graduating:
1. Motivate growth in the community
2. Address remaining items before graduation
### Are there any issues that the IPMC or ASF Board need to be aware of?
None.
### How has the community developed since the last report?
- We have published a paper, Sponge, at ATC 2023 conference
(https://www.usenix.org/conference/atc23/presentation/song) and promoted
Nemo in the publication in order to grow our community and work on further
potential projects based on Nemo.
### How has the project developed since the last report?
- We have published a paper on supporting features regarding offloading
bottleneck tasks to serverless frameworks with Nemo in ATC 2023.
- Introducing Nemo to researchers that were interested in the publication
through the academic conference.
- Discussions for community growth.
### 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:
2022-09-02
### When were the last committers or PPMC members elected?
September 28, 2021
### Have your mentors been helpful and responsive?
- The mentors have been helpful.
### Is the PPMC managing the podling's brand / trademarks?
- The PPMC manages the podling's brand / trademarks.
### Signed-off-by:
- [ ] (nemo) Hyunsik Choi
Comments:
- [X] (nemo) Byung-Gon Chun
Comments:
- [X] (nemo) Jean-Baptiste Onofré
Comments:
- [ ] (nemo) Markus Weimer
Comments:
### IPMC/Shepherd notes:
PJ Fanning: Activity on the mailing lists is quite low. It's difficult to
see if there is progress towards graduation. The podling has been
in incubation for more than 5 years.
--------------------
## Uniffle
Uniffle is an unified Remote Shuffle Service
Uniffle has been incubating since 2022-06-06.
### Three most important unfinished issues to address before graduating:
Promote the project and grow the user and dev community.
### Are there any issues that the IPMC or ASF Board need to be aware of?
No.
### How has the community developed since the last report?
1. More companies choose Uniffle and join the community such as Beike,
Huolala, etc. More important features were developed by more companies.
2. We have a regular meeting once every two weeks now. We discuss the
important issues and send discussion results to the dev mail list.
3. We post a new blog in our website and repost the blog in the Linedin,
Reddit.
4. 11 new contributors.
### How has the project developed since the last report?
1. We released 0.7.1. We're trying to release 0.8.0 version.
2. We have finished many important features such as Tez support, data
transport, Hadoop 3 support.More exciting features will come soon, such as
Flink Support, object storage support, dynamic allocation, server based on
Rust implement, dashboard and so on.
3. 115 pull requests are created, 136 pull requests are merged.
4. 150 issues are created, 94 issues are closed.
### 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:
2023-07-10
### When were the last committers or PPMC members elected?
Xianming Lei, elected as the committer on 2023-08-19
Junfan Zhang, elected as the PPMC on 2023-0625
### Have your mentors been helpful and responsive?
Yes, they're helpful in guiding the podding project.
### Is the PPMC managing the podling's brand / trademarks?
Yes.
### Signed-off-by:
- [ ] (uniffle) Felix Cheung
Comments:
- [X] (uniffle) Junping Du
Comments:
- [X] (uniffle) Liu Xun
Comments:
- [ ] (uniffle) Weiwei Yang
Comments:
- [ ] (uniffle) Zhankun Tang
Comments:
### IPMC/Shepherd notes:
--------------------
## Wayang
Wayang is a cross-platform data processing system that aims at decoupling
the business logic of data analytics applications from concrete data
processing platforms, such as Apache Flink or Apache Spark. Hence, it tames
the complexity that arises from the "Cambrian explosion" of novel data
processing platforms that we currently witness.
Wayang has been incubating since 2020-12-16.
### Three most important unfinished issues to address before graduating:
1. Grow the community, we really need some help here
2. Website issues not solved
3.
### 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?
Stagnating, see unfinished issues (1)
### How has the project developed since the last report?
We are in the process to create our next release, fixed bugs and added
features. We do a 0.71 release before we prepare 1.0 which involves code
base restructuring.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [X] Initial setup
- [X] Working towards first release
- [X] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
2021-12-13
### When were the last committers or PPMC members elected?
2023-06-05
### Have your mentors been helpful and responsive?
Yes.
### Is the PPMC managing the podling's brand / trademarks?
Yes, everything good here.
### Signed-off-by:
- [ ] (wayang) Christofer Dutz
Comments:
- [ ] (wayang) Lars George
Comments:
- [ ] (wayang) Bernd Fondermann
Comments:
- [X] (wayang) Jean-Baptiste Onofré
Comments:
### IPMC/Shepherd notes:
-----------------------------------------
Attachment AM: Report from the Apache IoTDB Project [Xiangdong Huang]
## Description:
The mission of Apache IoTDB is the creation and maintenance of software related
to an IoT native database with high performance for data management and analysis
## Project Status:
Current project status: Ongoing with high activity.
A good news is IoTDB's performance ranks first on Benchant.com.
(https://benchant.com/ranking/database-ranking)
Issues for the board: no.
## Membership Data:
Apache IoTDB was founded 2020-09-16 (3 years ago)
There are currently 61 committers and 27 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 Chao Wang on 2022-12-12.
- Yanze Chen was added as committer on 2023-07-25
- Lanyu Liao was added as committer on 2023-07-25
- Sicheng Yu was added as committer on 2023-08-01
New PMC election is in progress.
## Project Activity:
IOTDB-1.2.0 was released on 2023-09-08.
IOTDB-1.1.2 was released on 2023-07-28.
IOTDB-1.1.1 was released on 2023-06-14.
- Import a new feature pipe framework for lightweight streaming
processing. This could be used for CDC (data synchronization from
IoTDB to another system) and data subscription.
- Extend the IT framwork to support multiple cluster instance in one
test case, for testing data synchronization between two IoTDB cluster.
- Optimized the load balance strategy of data insertion. Now we could
spread the newly created data partition among the datanodes.
## Community Health:
The community looks healthy and we are trying to develop its ecosystem.
At the IoT Meetup Hessen on July 14, 2023, in Frankfurt am Main,
insights into the technology and use cases of Apache IoTDB and
Apache PLC4X in bridging IT & OTwere shared.
-----------------------------------------
Attachment AN: Report from the Apache Jackrabbit Project [Marcel Reutegger]
## Description:
The Apache Jackrabbit™ content repository is a fully conforming
implementation of the Content Repository for Java™ Technology API
(JCR, specified in JSR 170 and 283). The Jackrabbit content
repository is stable, largely feature complete and actively being
maintained.
Jackrabbit Oak is an effort to implement a scalable and performant
hierarchical content repository as a modern successor to the Apache
Jackrabbit content repository. It is targeted for use as the
foundation of modern world-class websites and other demanding
content applications. In contrast to its predecessor, Oak does not
implement all optional features from the JSR specifications, and it
is not a reference implementation.
## Project Status:
The project is ongoing with moderate activity.
There are no issues requiring board attention at this time.
## Membership Data:
There are currently 58 committers and 58 PMC members in this project.
The Committer-to-PMC ratio is 1:1.
Community changes, past quarter:
- Dominique Pfister resigned on 2023-07-17
- No new committers. Last addition was Rishabh Daim on 2023-04-06.
## Project Activity:
Apache Jackrabbit Oak receives most attention nowadays. All
maintenance branches and the main development branch are
continuously seeing moderate to high activity.
Apache Jackrabbit itself is mostly in maintenance mode with most of
the work going into bug fixing and tooling. New features are mainly
driven by dependencies from Jackrabbit Oak.
The project team introduced a shaded version of Guava and replaced
usage of plain Guava with the shaded version. Only one transitive
dependency through an Azure SDK library is left. The plan is to remove
this final dependency in the next Jackrabbit Oak release.
On June 29th a vulnerability was reported to the security mailing list.
The remote code execution in Jackrabbit RMI was handled with
CVE-2023-37895 and releases with a fix published on July 25th.
## Community Health:
The project is generally healthy with a continuous stream of traffic
mostly on JIRA issues and GitHub pull requests reflecting activity of
the respective component.
Commit activity is moderate, mirroring the activity on the
JIRA issues and the desire of the individual contributors to bring
features and improvements in for the next Jackrabbit Oak release.
## Releases:
- jackrabbit-oak-1.22.16 was released on 2023-07-17
- jackrabbit-filevault-3.7.0 was released on 2023-07-19
- jackrabbit-2.21.18 was released on 2023-07-24
- jackrabbit-2.20.11 was released on 2023-07-24
- filevault-package-maven-plugin-1.3.4 was released on 2023-07-24
- jackrabbit-oak-1.54.0 was released on 2023-07-24
- jackrabbit-2.21.19 was released on 2023-08-11
- jackrabbit-oak-1.56.0 was released on 2023-09-01
## JIRA activity:
- 156 JIRA tickets created in the last 3 months
- 118 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AO: Report from the Apache Karaf Project [Jean-Baptiste Onofré]
## Description:
The mission of the Apache Karaf project is the creation and maintenance of
open-source software related to a generic platform providing higher level
features and services specifically designed for creating OSGi-based servers for
distribution at no charge to the public.
## Project Status:
Ongoing, with moderate activity due to summer break, but still active.
## Membership Data:
Apache Karaf was founded 2010-06-16 (13 years ago)
There are currently 31 committers and 17 PMC members in this project.
The Committer-to-PMC ratio is roughly 8:5.
Community changes, past quarter:
- No new PMC members. Last addition was Francois Papon on 2018-11-29.
- No new committers. Last addition was Francois Papon on 2018-05-19.
## Project Activity:
Due to summer break, the activity was pretty slow. Releases preparation:
* karaf osgi runtime 4.3.10 and 4.4.4 are still in preparation, the vote will
start in the coming days
* karaf decanter 2.11.0 and 3.0.0 are in preparation, vote is planned in
September
* karaf osgi runtime 4.5.0 preparation will start just after 4.3.10 and 4.4.4
releases, with major upgrade
## Community Health:
The karaf-integration distribution will be part of new releases. Karaf 4.5.x
series will start just after 4.4.4 release, in September. The new bundle URL
handler implementation also started and a PR will be created soon. Following
the vote, Karaf Cave and Karaf Winegrower have been removed from the mailing
list.
-----------------------------------------
Attachment AP: Report from the Apache Kvrocks Project [Hulk Lin]
## Description:
The mission of Apache Kvrocks is the creation and maintenance of software
related to a distributed key-value NoSQL database, supporting the rich data
structure
## Project Status:
Current project status: New Issues for the board: None
## Membership Data:
Apache Kvrocks was founded 2023-06-21 (3 months ago) There are currently 22
committers and 10 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).
- Aleks Lozoviuk was added as committer on 2023-07-11
- Binbin Zhu was added as committer on 2023-07-20
- Xuwei Fu was added as committer on 2023-07-20
## Project Activity:
Apache Kvrocks completed the release process for 2.5.1 on 2023-08-05 which
fixed some critical bugs, and we're now planning the next minor version. It
will include some notable features like:
- Supports the restore command which will make Redis to Kvrocks process more
smooth
- New Commands like LPOS/LASTSAVE/MPUBLISH, and so on
At this time, we're focusing on the development of the new data structure:
BloomFilter and JSON.
## Community Health:
The overall is healthy and good, more and more committers are active to help
review and drive PRs. We're now putting our efforts into attracting more users
and contributors by enriching the economy of Kvrocks, like supporting the
restore command to make the migration process simple and smooth. As well as
building projects like kvrocks-operator and kvrocks-controller to help users
manage Kvrocks deployments.
-----------------------------------------
Attachment AQ: Report from the Apache Kyuubi Project [Kent Yao]
## Description:
The mission of Apache Kyuubi is the creation and maintenance of software
related to a distributed and multi-tenant gateway to provide serverless SQL on
data warehouses and lakehouses
## Project Status:
Current project status: Ongoing(moderate)
Issues for the board: none
## Membership Data:
Apache Kyuubi was founded 2022-12-21 (9 months ago)
There are currently 23 committers and 13 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:2.
Community changes, past quarter:
- No new PMC members. Last addition was Fu Chen on 2023-01-31.
- No new committers. Last addition was Paul Lin on 2023-06-02.
## Project Activity:
### Code
Apache Kyuubi just passed the vote for 1.7.2, which is a maintenance
releases release, carrying several bug fixes.
This September, we are about to start the vote for 1.8.0, which is
a feature release, carrying improvements like,
- A brand new Web UI and Batch API V2
- Support Apache Flink application-mode
- Support Scala 2.13 compilation
- Support Apache Spark 3.4
In addition to the ongoing work on the 1.9 line, early discussion and
exploratory work for Kyuubi 3.x has begun. 1.9 might mainly achieve
these goals:
- Support Java up to 21, including 17+
- Support Scala 3.x
- Native Support for MPP engines, such as Apache Doris, Impala, etc
### Meetup & conference
- 2023-8-18(Beijing), more than 8 kyuubi community members attended
'Community Over Code Asia 2023', and one of our PMC gave a speech
- 2023-9-23(Hangzhou), A Kyuubi & Spark meetup will be held
- 2023-10-13(Shanghai), A Kyuubi Journey into Bilibili
- 2023-10-18(Hangzhou), A Kyuubi & Celeborn meetup will be held
### Developer event
We've been planning `2023 Kyuubi Coding Contribution Program` in this
quater and it will be luanched this October.
## Community Health:
We've received new usecases and contributions from Nivida, AWS, Shopee,
etc., it's good sigh for us to see kyuubi being adopted in large vendors.
The dev mailing list had big decrease in the past quarter, as the users and
contributors are more likely to use tools like Wechat group, Github Issues.
We don't have a proper solution for it right now.
-----------------------------------------
Attachment AR: Report from the Apache Linkis Project [Shuai Di]
## Description:
The mission of Apache Linkis is the creation and maintenance of software
related to a distributed computation middleware to facilitate connection,
governance and orchestration between the upper applications and the underlying
data engines
## Project Status:
Current project status: New
Issues for the board: There are no issues requiring board attention.
## Membership Data:
Apache Linkis was founded 2022-12-21 (9 months ago)
There are currently 35 committers and 24 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 Chen Xia on 2023-02-06.
- No new committers. Last addition was Fei Guo on 2023-05-31.
## Project Activity:
Apache Linkis released version 1.4.0 on August 6th. This version involved
more than 26 contributors, including 10 new contributors (currently: 150),
and contained over 34 new features. Apache Linkis 1.5.0 are currently
under development.
Software development activity:
We released 1.4.0 last month. At this time, we are currently developing 1.5.0
and have completed most of the features. This version mainly contains some
new features:
- Entrance supports task HA (running task support is taken over).
- Support task submission to the K8S cluster.
- Support spark job to K8S cluster using operator.
- Support Nacos.
- Entrance supports Orchestrator pluggable.
- The once-mode task supports recording information through the entrance.
- The data source module supports data source SQL generation and supports more
data sources with the Spark ETL function.
- Spring Cloud gateway upgrade version, spring boot upgrade version.
- Monitor service added.
- Add task positioning troubleshooting script.
- Support user engine template parameter support.
Meetups and Conferences:
- At the CommunityOverCode Asia 2023, Linkis community shared three topics,
respectively from three companies, Postal Savings Bank of China, Li Auto,
and WeBank.
## Community Health:
Overall community health is good.
- 161 PRs closed on GitHub, past quarter.
- 146 issues closed on GitHub, past quarter.
-----------------------------------------
Attachment AS: Report from the Apache Lucene Project [Greg Miller]
## Description:
The mission of Lucene is the creation and maintenance of software related to
Search engine library
## Project Status:
Current project status: Ongoing
Issues for the board: none
## Membership Data:
Apache Lucene was founded 2005-01-18 (19 years ago)
There are currently 98 committers and 64 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:4.
Community changes, past quarter:
- Chris Hegarty was added to the PMC on 2023-06-18
- No new committers. Last addition was Ben Trent on 2023-01-27.
## Project Activity:
9.7 was released on 2023-06-03
- Release notes are available at:
https://lucene.apache.org/core/9_7_0/changes/Changes.html
- Some highlights released with 9.7 include:
-- A number of KNN search improvements, including the ability to take advantage
of Java's incubating vector API (when running in Java 20 or 21), the ability to
execute concurrently across index slices, and exposure of similarity measures
behind "function" queries.
-- Improvements to indexing, including the ability to update multiple documents
at once that match a query, and reduced merge-time overhead when computing the
number of soft deletes.
PyLucene 9.7 was released on 2023-07-12
- Tracks core 9.7 changes
- Release notes are available at:
https://svn.apache.org/repos/asf/lucene/pylucene/tags/pylucene_9_7_0/CHANGES
## Community Health:
Community interactions remain healthy.
- dev@ mailing list traffic decreased by 55% compared to last quarter
(168 emails compared to 372). This is not particularly surprising though given
that dev@ traffic was high last quarter with a lot of discussion around KNN
search dimension limits (137 emails on that topic alone in the previous quarter)
- Development has remained active:
-- 77 commits (+28% compared to last quarter)
-- 65 PRs opened (+27% compared to last quarter)
-- 26 PRs closed (-50% compared to last quarter)
- PR volume remains healthy, with open PRs trending in a steady state
while closed PRs continue to increase at the same trend
(https://home.apache.org/~mikemccand/lucenebench/github_pr_counts.html).
-----------------------------------------
Attachment AT: Report from the Apache Lucene.Net Project [Shad Storhaug]
## Description:
The mission of Lucene.Net is the creation and maintenance of software related
to Search engine library targeted at .NET runtime users.
## Project Status:
Current project status: Ongoing Issues for the board: There was a flurry of
activity over the previous quarter but over the summer it has been
quieter.
(The reports in reporter.apache.org don't show commit or PR or issue activity
correctly it seems)
## Membership Data:
Apache Lucene.Net was founded 2012-08-14 (11 years ago)
There are currently 16 committers and 14 PMC members in this project.
The Committer-to-PMC ratio is 8:7.
Community changes, past quarter:
- No new PMC members. Last addition was Ron Clabo on 2022-03-02.
- No new committers. Last addition was Ron Clabo on 2021-06-02.
## Project Activity:
There was a big push last quarter to get another beta 4.8.0 beta00017 shipped,
but that hasn't been completed quite yet. The community is definitely onboard
to try to get an RTM release shipped but another beta is first required due to
some breaking API changes.
## Community Health:
Quite a few PRs opened up by new community members which is great to see and
lots of conversations going on in GitHub tickets.
-----------------------------------------
Attachment AU: Report from the Apache ManifoldCF Project [Karl Wright]
-----------------------------------------
Attachment AV: Report from the Apache Mnemonic Project [Gordon King]
-----------------------------------------
Attachment AW: Report from the Apache MXNet Project [Sheng Zha]
-----------------------------------------
Attachment AX: Report from the Apache Mynewt Project [Szymon Janc]
## Description:
Mynewt is a real-time operating system for constrained embedded systems like
wearables, lightbulbs, locks and doorbells. It works on a variety of 32-bit
MCUs (microcontrollers), including ARM Cortex-M, RISC-V and MIPS
architectures
The mission of Apache Mynewt is the creation and maintenance of software
related to an embedded OS optimized for networking and built for remote
management of constrained devices that are incapable of running either Linux or
Android
## Project Status:
No issues.
## Membership Data:
Apache Mynewt was founded 2017-06-21 (6 years ago)
There are currently 36 committers and 19 PMC members in this project.
The Committer-to-PMC ratio is roughly 9:5.
Community changes, past quarter:
- No new PMC members. Last addition was Jerzy Kasenberg on 2019-10-24.
- No new committers. Last addition was Krzysztof Kopyściński on 2021-01-26.
## Project Activity:
Apache Mynewt 1.11.0 (along with Apache Nimble 1.6.0) were released in September
2023. This release includes number of new features like touchscreens support
(along LVGL integration), external modules and initial work on Bluetooth LE
Audio support.
Project is working towards more automated testing which would decrease
testing effort on releases and allow for more frequent releases (3-4 per year).
Development is focusing on Bluetooth LE Audio as well as improving support for
USB and GUI.
## Community Health:
Most discussions happen on project Slack and github. Mailing list seems to be
less used. Number of code changes is stable. We see increased interest in NimBLE
(Bluetooth stack) usage outside of Mynewt.
-----------------------------------------
Attachment AY: Report from the Apache NetBeans Project [Geertjan Wielenga]
## Description:
The mission of Apache NetBeans is the creation and maintenance of software
related to development environments, tooling platforms, and application
frameworks.
## Project Status:
Current project status: Ongoing with moderate to high activity.
There are no issues requiring the board's involvement at this time.
## Membership Data:
Apache NetBeans was founded 2019-04-17 (4 years ago)
There are currently 82 committers and 65 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 Michael Bien on 2022-05-01.
- No new committers. Last addition was Tomas Hurka on 2023-05-24.
## Project Activity:
- Apache NetBeans 19 was released on 2023-09-01.
- Apache NetBeans 18 was released on 2023-05-30.
- Apache NetBeans 17 was released on 2023-02-21.
- Aside from the above, the related installers and VSCode extensions were
released.
- In short, we're continuing to keep to the quarterly release schedule:
https://cwiki.apache.org/confluence/display/NETBEANS/Release+Schedule
## Community Health:
- Community involvement in the releases is good, e.g., approximately 30
contributors per release, with approximately 5 new each time. For example,
see these stats automatically generated at the end of 'What's Changed' for
19: https://github.com/apache/netbeans/releases/tag/19
- dev@netbeans.apache.org had a 40% decrease in traffic in the past quarter
(217 emails compared to 360).
- users@netbeans.apache.org had a 39% decrease in traffic in the past quarter
(134 emails compared to 218).
- 37 code contributors in the past quarter (-5% change).
- 127 issues closed on GitHub, past quarter (19% increase).
- In short, the project and the community are stable, working well together.
-----------------------------------------
Attachment AZ: Report from the Apache OFBiz Project [Jacopo Cappellato]
## Description:
Apache OFBiz is an open source product for the automation of enterprise
processes that includes framework components and business applications for ERP
(Enterprise Resource Planning), CRM (Customer Relationship Management),
E-Business / E-Commerce, SCM (Supply Chain Management), MRP (Manufacturing
Resource Planning), MMS/EAM (Maintenance Management System/Enterprise Asset
Management). Apache OFBiz provides a foundation and starting point for
reliable, secure and scalable enterprise solutions.
## Project Status:
Current project status: Ongoing.
Issues for the board: none.
## Membership Data:
Apache OFBiz was founded 2006-12-20 (17 years ago)
There are currently 58 committers and 33 PMC members in this project.
The Committer-to-PMC ratio is roughly 8:5.
Community changes, past quarter:
- No new PMC members. Last addition was Daniel Watford on 2023-01-18.
- No new committers. Last addition was Mekika Leila on 2022-09-28.
## Project Activity:
No release was published since our last report: the last one was 18.12.08,
released on 2023-06-01. The branch 18.12 is currently our release branch, and
bug fix releases are published from it when needed. New features and work is
contributed to the trunk, from which we will create the new release branch to
replace the 18.12 branch.
## Community Health:
The last quarter has been a bit slower than the average, possibly because of
the summer season. However the community is engaged in various exchanges in
our mailing lists, in which both technical and feature related questions and
topics are posted, answered and discussed. We need to look more closely for
new candidates for the PMC and committer roles since it has been a while since
our last additions.
-----------------------------------------
Attachment BA: Report from the Apache Olingo Project [Michael Bolz]
## Description:
The Apache Olingo Project be and hereby is responsible for the creation and
maintenance of software related to providing an implemention of the OASIS OData
(Open Data Protocol) specifications, in server and client form;
## Project Status:
Current project status: Dormant
Issues for the board: No issues requiring board attention at this time.
## Membership Data:
Apache Olingo was founded 2014-03-19 (9 years ago)
There are currently 25 committers and 15 PMC members in this project.
The Committer-to-PMC ratio is 5:3.
Community changes, past quarter:
- No new PMC members. Last addition was Ramya Vasanth on 2019-04-15.
- No new committers. Last addition was Archana Rai on 2017-05-26.
## Project Activity:
Recent releases:
- V2 2.0.12 was released on 2022-04-24.
- 4.9.0 was released on 2022-03-09.
Planned maintenance release for 4.x and 2.x
are further delayed, but 2.x is in progress.
Current plan is to have both releases done
by end of September.
In addition it is planned to do for both
versions a feature release by end of 2023.
## Community Health:
Overall community health is okay.
Activity on the mailing lists increased in the last quarter.
New JIRA items got created and new PRs got opened.
Some JIRA items and some PRs could be closed,
resulting in 9 commits (minor increase) by 3 contributors.
Release of V2 and V4 versions are in progree / planned.
Roadmap for feature release will be discussed soon.
-----------------------------------------
Attachment BB: Report from the Apache OpenNLP Project [Jeff Zemerick]
## Description:
The mission of OpenNLP is the creation and maintenance of software related to
Machine learning based toolkit for the processing of natural language text
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache OpenNLP was founded 2012-02-14 (12 years ago)
There are currently 25 committers and 17 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:5.
Community changes, past quarter:
- Martin Wiesner was added to the PMC on 2023-06-24
- Richard Zowalla was added to the PMC on 2023-06-24
- No new committers. Last addition was Atita Arora on 2023-02-28.
## Project Activity:
OpenNLP 2.3.0 was released on July 31, 2023. We have been able to release more
often this year, with releases happening about every 3 months. The project now
has integration tests running on the ASF Jenkins and that has helped with the
release process. A lot of work has been done by the community to address tech
debt and make a lot of usability improvements.
## Community Health:
Mailing list traffic remains low but the project is healthy. The project added
two new PMC members since the last report.
-----------------------------------------
Attachment BC: Report from the Apache OpenWebBeans Project [Mark Struberg]
## Description:
Apache OpenWebBeans is an ALv2-licensed implementations of the
"Contexts and Dependency Injection for the Java EE platform"
specifications which are defined as JSR-299 (CDI-1.0), JSR-346
(CDI-1.1 and CDI-1.2 MR), JSR-365 (CDI-2.0) and
Jakarta CDI (CDI-4.0).
The OWB community also maintains a small server as
Apache Meecrowave subproject. Meecrowave bundles latest releases of
the ASF projects Tomcat + OpenWebBeans + CXF + Johnzon + log4j2.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
We've now rolled the first release of our our CDI-4.0 implementation.
The next step will be to work towards a Jakarta EE release of
Apache Meecrowave.
## Community Health
4 different committers in the last quarter shows that there is still
decent activity if necessary although there is not much fresh blood
on the horizon.
## PMC changes:
- Currently 13 PMC members, 20 committers
- Last PMC addition was Reinhard Sandtner on 2017-10-09.
- Last committer addition was John D. Ament on 2017-10-09.
## Recent Releases
- 4.0.0 was released on 2023-09-07
- 2.0.27 was released on 2022-06-07.
- meecrowave-1.2.14 was released on 2022-05-11.
-----------------------------------------
Attachment BD: Report from the Apache Pig Project [Koji Noguchi]
-----------------------------------------
Attachment BE: Report from the Apache Pinot Project [Kishore G]
## Description:
The mission of Apache Pinot is the creation and maintenance of software related
to distributed OLAP data store to provide Real-time Analytics to power wide
variety of analytical use case
## Project Status
Top-level project with high activity
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache Pinot was founded 2021-07-20 (2 years ago)
There are currently 31 committers and 12 PMC members in this project.
The Committer-to-PMC ratio is roughly 8:3.
Community changes, past quarter:
- Rong Rong was added to the PMC on 2023-09-11
- Xiaobing Li was added as committer on 2023-06-14
## Project Activity:
- We changed plans to release 1.0.0 instead of 0.13.0 as reported earlier.
1.0.0 is still compatible with all major features except for stream level
realtime consumers which is not being used in the community at all.
https://github.com/apache/pinot/issues/10996
This feature was removed. This release is under vote now, and is expected
to be completed in a few days.
## Community Health:
- 67 code contributors in the past quarter
- 447 commits in the past quarter
- 36k messages initiated in the #troubleshooting channel alone, that
gives us a good idea of the wide aoption and engagement.
The channel has 3430 unique members.
- The #pinot-dev channel has 486 members now.
-----------------------------------------
Attachment BF: Report from the Apache Pivot Project [Roger Lee Whitcomb]
-----------------------------------------
Attachment BG: Report from the Apache PLC4X Project [Christofer Dutz]
## Description:
The mission of the Apache PLC4X project is creating a set of libraries for
communicating with industrial programmable logic controllers (PLCs) using a
variety of protocols but with a shared API.
## Project Status:
Current project status: Ongoing with slightly less than usual activity
Issues for the board: None
## Membership Data:
Apache PLC4X was founded 2019-04-17 (4 years ago) There are currently 21
committers and 13 PMC members in this project. The Committer-to-PMC ratio is
roughly 3:2.
Community changes, past quarter:
- No new PMC members. Last addition was César García on 2021-10-01.
- No new committers. Last addition was Jinlin Hong on 2022-11-02.
## Project Activity:
The project has mostly been working on scratching individual contributor's
itches, implementing features needed for their every day work.
- New IEC 60870-5-104 java driver
- New UPC-UA go driver
- Continued work on the Go C-Bus Driver
In general the project is aiming for a new release, as the time since our last
release has been way too long.
## Community Health:
It's been a pretty slow quarter, the expected boost of activity after one of
the PMC members switching jobs didn't quite come as expected, but we're still
hopefully it will come.
The project knows that we need to grow the contributor base, however we need
to put in a lot more effort into this. Admittedly PLCs and writing drivers for
communicating with them is probably not the sexiest of things to do.
We've started planning a hackathon, which we are hopefully going to run this
December, there the existing and possibly future community would be able to
re-unite and hopefully re-spark the activity levels a bit.
-----------------------------------------
Attachment BH: Report from the Apache Portable Runtime (APR) Project [Yann Ylavic]
## Description:
The mission of the Apache Portable Runtime (APR) project is to create and
maintain software libraries that provide a predictable and consistent interface
to underlying platform-specific implementations. The primary goal is to provide
an API to which software developers may code and be assured of predictable if
not identical behaviour regardless of the platform on which their software is
built, relieving them of the need to code special-case conditions to work
around or take advantage of platform-specific deficiencies or features.
## Project Status:
Current project status: ongoing.
Issues for the board: no issues requiring board attention.
## Membership Data:
Apache Portable Runtime (APR) was founded 2000-12-01 (23 years ago)
There are currently 68 committers and 43 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 Steffen Land on 2023-03-02.
- No new committers. Last addition was Steffen Land on 2023-02-27.
## Project Activity:
Northern summertime was quiet, nothing unusual.
No new release this quarter, latest apr-1.7.4 was released on 2023-04-16
and apr-util-1.6.3 on 2023-02-01.
New apr-1.8.0 and apr-util-1.7.0 versions with interesting features are
considered/discussed for release, though no progress was made this quarter.
## Community Health:
The project remains healthy, though quiet.
Low activity on the dev@ mailing list and bugzilla/github.
-----------------------------------------
Attachment BI: Report from the Apache Portals Project [Neil Griffin]
## Description:
The mission of Portals is the creation and maintenance of software related to
Portal technology
## Project Status:
Current project status:
Apache Pluto is a stable implementation of a JCP standard and is currently in
a maintenance mode. As a mature project, issues are rarely filed by the
community. The annual release is scheduled for Q4 2023, which is expected to
simply be an update of 3rd party dependencies if any security vulnerabilities
are reported by that time.
Issues for the board: No issues at this time
## Membership Data:
Apache Portals was founded 2004-02-17 (20 years ago)
There are currently 40 committers and 17 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:3.
Community changes, past quarter:
- No new PMC members. Last addition was Neil Griffin on 2017-02-11.
- No new committers. Last addition was Ahmed on 2016-08-06.
## Project Activity:
There has been no project activity since the last report. Since the project is
in maintenance mode, activity will typically only occur at the time of the
annual release.
## Community Health:
There is no recent activity on the dev lists, and no recent community
contributions. Again, the project is in a maintenance mode.
-----------------------------------------
Attachment BJ: Report from the Apache Pulsar Project [Matteo Merli]
-----------------------------------------
Attachment BK: Report from the Apache Ranger Project [Selvamohan Neethiraj]
## Description:
Apache Ranger is a framework to enable, monitor and manage comprehensive data
security - consistently across various data processing services.
## Issues:
There are no issues requiring board attention at this time
## Membership Data:
- Apache Ranger was founded 2017-01-17 (6 years ago).
- There are 32 committers and 18 PMC members in this project.
- The Committer-to-PMC ratio is roughly 8:5.
##Community changes, past quarter:
- No new PMC members. Last addition was Sailaja Polavarapu on 2019-09-18.
- Last addition to Committer was Dineshkumar Yadav on 2023-02-06.
- One PMC member has resigned (Allan Gates) on 2023-04-05.
## Project Activity:
- Working on ranger 3.0.0 version features and bugfixes.
- Updated ranger website with new look and feel.
- Working to move ranger docs (ranger website content) from ranger source
repo to ranger-site repo.
- Generally, less activities in the community after our 2.4.0 release; After
we publish the release plan for 3.0.0, community activities will increase.
## Community Health:
-1105 emails in dev@ranger.apache.org in this quarter
(-26% change from past quarter)
- 7 emails in user@ranger.apache.org in this quarter
(-59% change from past quarter)
- 112 issues opened in JIRA in this quarter
(-16% change from past quarter)
- 78 issues closed in JIRA in this quarter
(-30% change from past quarter)
- 92 commits in this quarter
(-46% change from past quarter)
- 22 code contributors in this quarter
(-26% change from past quarter)
- 16 PRs opened on GitHub in this quarter
(-50% change from past quarter)
- 10 PRs closed on GitHub in this quarter
(-58% change from past quarter)
## Most Recent releases:
- Apache Ranger 2.4.0 was released on 2023-03-30
- Apache Ranger 2.3.0 was released on 2022-07-06
- Apache Ranger 2.2.0 was released on 2021-11-01
-----------------------------------------
Attachment BL: Report from the Apache Royale Project [Piotr Zarzycki]
DESCRIPTION
Apache Royale implements the principles of Apache Flex to support development
of applications designed for JavaScript instead of Adobe Flash/AIR runtimes.
Apache Royale improves developer productivity in creating applications to run
wherever JavaScript runs, including on browsers, in Apache Cordova
applications, on Node, and on other platforms.
Project Status
Current project status: There are couple of PMC members who are constantly
improving some areas of the project and responding to the questions on mailing
list.
Issues for the board: There are no issues requiring board attention at
this time.
Membership Data
No new PMC members. Last addition was Hugo Ferreira on 2022-10-27.
No new committers. Last addition was María José Esteve on 2021-11-23.
Last release of Apache Royale 0.9.10 was on June 05 2023.
Activity on social media:
Our Twitter account has 697 followers. Our Facebook page has 214 likes. Our
LinkedIn Group has 156 people. Our StackOVerFlow "apache-royale" tag currently
has 65 questions.
Project Activity
We are seeing among our PMC members activity in several modules of our project.
They are providing small improvements/fixes. Compiler part is being even more
actively developed by one of our PMC members.
Unfortunately, we don't have any social media activity,
which is quite important these days - there is no volunteer who would take
care of at least weekly news about our activity.
Community Health
We are seeing fewer emails in our Users list, while our development list is
more active recently.
-----------------------------------------
Attachment BM: 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++
## Project Status:
Current project status: The Java project is actively maintained and PRs are
getting merged and releases made. The C++ project is in a dormant state.
There are no issues requiring board attention.
## Membership Data:
Apache Santuario was founded 2006-06-27 (17 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:
Two new releases were made over the last quarter: a bugfix release on the
2.2.x branch as well as a milestone release of a new major version. We took
action based on the last board report feedback to remove a few people from the
private mailing list that weren't on the PMC any more.
## 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 BN: Report from the Apache SeaTunnel Project [Jun Gao]
## Description:
The mission of Apache SeaTunnel is the creation and maintenance of software
related to a very easy-to-use ultra-high-performance distributed data
integration platform that supports real-time synchronization of massive data
## Project Status:
Current project status: Ongoing
Issues for the board: none
## Membership Data:
Apache SeaTunnel was founded 2023-05-17 (4 months ago)
There are currently 29 committers and 19 PMC members in this project.
The Committer-to-PMC ratio is roughly 8:5.
Community changes, past quarter:
- Hailin Wang was added to the PMC on 2023-07-10
- Chengyuan Ma was added as committer on 2023-07-15
## Project Activity:
- We released 2.3.3 on 2023-08-23
- A online sharing meetup on 2023-08-15
## Community Health:
As in July, the project is undergoing significant architecture upgrades, and
the new connector PR is being carefully merged to prevent them from becoming
outdated as soon as they are merged.I believe that the situation will improve
in the next quarter.
-----------------------------------------
Attachment BO: Report from the Apache Serf Project [Justin Erenkrantz]
-----------------------------------------
Attachment BP: Report from the Apache ServiceMix Project [Krzysztof Sobkowiak]
## Description:
The mission of Apache ServiceMix project is to create and maintain a flexible,
open-source integration container, powered by OSGi, that unifies the features
and functionality of Apache ActiveMQ, Camel, CXF, and Karaf into a powerful
runtime platform you can use to build your own integrations solutions.
## Project Status:
Low activity, target is to move key features to Karaf community.
No issue requiring board attention.
## Membership Data:
Apache ServiceMix was founded 2007-09-19 (15 years ago)
There are currently 50 committers and 21 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:3.
Community changes, past quarter:
- No new PMC members. Last addition was Andrea Cosentino on 2017-03-15.
- No new committers. Last addition was Andrea Cosentino on 2016-03-13.
## Project Activity:
Releases preparation:
- bundles-2023.08 release is in preparation. The vote will start very soon.
## Community Health:
Still in maintenance mode. The karaf-integration distribution should
be provided by the Karaf community soon as an alternative to SMX
distribution.
-----------------------------------------
Attachment BQ: Report from the Apache Shiro Project [Brian Demers]
## Description:
The mission of Shiro is the creation and maintenance of software related to
Powerful and easy-to-use application security framework
## Project Status:
Current project status: Ongoing with low activity.
Issues for the board:
We have no issues that require Board assistance at this time.
## Membership Data:
Apache Shiro was founded 2010-09-21 (13 years ago)
There are currently 14 committers and 12 PMC members in this project.
The Committer-to-PMC ratio is 7:6.
Community changes, past quarter:
- No new PMC members. Last addition was Lenny Primak on 2022-12-04.
- No new committers. Last addition was Lenny Primak on 2022-11-02.
## Project Activity:
The Shiro team is actively working on 2.0, and 1.x is in maintenance mode.
- 2.0.0-alpha-3 was released on 2023-07-25.
- 1.12.0 was released on 2023-07-11.
- patch releases for v1 and v2 are expected shortly
## Community Health:
GitHub pull requests (by humans) have double this quarter.
NOTE: It's hard to parse the stats for a couple reasons:
- Last quarter we moved to GH issues, diffs are skewed
- The generated stats don't filter bots (COMDEV-536)
-----------------------------------------
Attachment BR: Report from the Apache SINGA Project [Wang Wei]
## Description:
The mission of Apache SINGA is the creation and maintenance of software related
to a distributed deep learning platform
## Project Status:
Current project status: under development
Issues for the board: N.A
## Membership Data:
Apache SINGA was founded 2019-10-16 (3 years ago)
There are currently 23 committers and 16 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:2.
Community changes, past quarter:
- No new PMC members. Last addition was Chris Yeung on 2020-04-17.
- No new committers. Last addition was Naili Xing on 2022-11-19.
## Project Activity:
The team has released SINGA 4.0.0 on 07 April 2023.
In the past quarter, the community is working on the following
features/changes:
* Adding more models for the malaria detection application
* Implementing dynamic models for the model selection application
* Implementing new error loss function and updating the optimizer
* Enhancing the distributed training, e.g., iterative checking for return
values
* Creating the DOAP file, updating the NOTICE file and website
## Community Health:
According to the statistic, there are increases of email traffic, commit
activity (commits and contributors), GitHub PR activity and GitHub issues,
which shows that the community is active in the development.
-----------------------------------------
Attachment BS: Report from the Apache Sling Project [Robert Munteanu]
## Description:
Apache Sling™ is a framework for RESTful web-applications based on an
extensible content tree.
## Project Status:
Current project status: Ongoing, with moderate activity.
Issues for the board: none.
## Membership Data:
Apache Sling was founded 2009-06-17 (14 years ago)
There are currently 49 committers and 29 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:4.
Community changes, past quarter:
- No new PMC members. Last addition was Joerg Hoh on 2022-06-13.
- No new committers. Last addition was Julian Reschke on 2023-02-08.
## Project Activity:
We released version 12 of our sample application, the Sling Starter, on March
18th, 2022. We have not yet made plans for version 13, but individual modules
are being developed and released, with 28 releases for this reporting period.
adaptTo(), a conference that, amongst others, targets Apache Sling
enthusiasts, will take place 25th-27th September 2023 at KulturBrauerei in
Berlin.
## Community Health:
The community is at a healthy level. The level of contribution is lower
compared to the last quarter, but that can probably be tied to the summer
holidays.
-----------------------------------------
Attachment BT: Report from the Apache SpamAssassin Project [Sidney Markowitz]
## Description:
SpamAssassin is a mail filter to identify spam. The project provides a
framework/engine and regular rule updates that reflect the changing nature of
spam email seen in the wild. Updated rules are generated through a combination
of hand crafted contributions and automated processing of spam and anonymized
processed non-spam that are contributed by volunteers.
## Project Status:
Project state: Ongoing with low to moderate activity
Primary focus for development is now ongoing maintenance bug fixes to the
recently released 4.0.0.
Preparation has begun of a bug fix release 4.0.1.
Issues for the board: None
## Membership Data:
Apache SpamAssassin was founded 2004-06-01 (19 years ago)
There are currently 32 committers and 14 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 Paul Stead on 2021-03-23.
- No new committers. Last addition was Paul Stead on 2018-09-12.
## Project Activity:
Last release: Apache SpamAssassin version 4.0.0 on 17 December 2022.
We maintain online rule updates that are continuously updated through a
combination of developer contributions and automated processing via our
mass-check facility.
## Community Health:
Maintenance of our rule update infrastructure, developer community submissions
for rule update testing, and our dev and user mailing lists, are continuing
smoothly.
-----------------------------------------
Attachment BU: Report from the Apache Storm Project [P. Taylor Goetz]
## Description:
The mission of Storm is the creation and maintenance of software
related to
Distributed, real-time computation system
## Project Status:
Current project status: Ongoing (reactivated)
## Membership Data:
Apache Storm was founded 2014-09-17 (9 years ago)
There are currently 45 committers and 44 PMC members in this project.
The Committer-to-PMC ratio is roughly 1:1.
Community changes, past quarter:
- Alexandre Vermeerbergen was added to the PMC on 2023-08-16
- Richard Zowalla was added to the PMC on 2023-08-01
- Julien Nioche was added as committer on 2023-08-01
We invited two additiona individuals to join the PMC. However, they
still need to complete the paperwork, so we can add them to the roster.
## Project Activity:
Project activity has slowed in recent years. Storm is essentially in
maintenance mode.
Current focus is the upgrade of many third party libraries to recent
versions
in order to reduce techincal debt. A first positive effect is the
active
review of pull requests on GitHub, which has been stale for a long
time.
The project successfully raised the minimal Java version required to
run Storm to 11.
The build now also success with Java 17 and work is done to reduce the
technical impact
to run Storm on even newer Java versions. We expect to do some testing
with the next Java release (21) soon.
In addition, the project has started a survey to collect user feedback
to decide over the
future of external modules. These modules were created a long time ago
and were
mostly maintained by volunteers, who were not necessarily part of the
PMC/committership.
These volunteers are mostly inactive, creating a technical burden in
maintaining Storm as
most of these modules are using outdated third party libraries and are
not well documented.
By doing so, we hope to get community feedback in order to decide,
which modules we want to
abandon or remove from future Storm versions.
Currently, developing Storm while using Eclipse as IDE is nearly
impossible. Work is done to address
those issues in order to ease the onboarding process of contributors
without the necessity to switch to another
unfamiliar IDE.
Since our last report, we updated our website to be compliant with the
latest GDPR changes and ASF policies.
Moreover, we included the ASF Matomo instance for analytics, so we get
a better view about our users.
Recent releases:
2.5.0 was released on 2023-08-04.
## Community Health:
Community engagement is currently healthy but could benefit from new
contributors or users. There are several initiatives and discussions
started by our new additions to the PMC. In addition, users are
activley participating in our survey regarding the future of the
external modules and questions are asked on the dev@ or user@ list. We
are currently onboarding our new PMC members (some of them never
contributed to an ASF project before) to teach them the Apache way.
-----------------------------------------
Attachment BV: Report from the Apache Streams Project [Steve Blackmon]
-----------------------------------------
Attachment BW: Report from the Apache Submarine Project [Kevin Su]
## Description:
The mission of Apache Submarine is the creation and maintenance of software
related to allowing infrastructure engineers and data scientists to build deep
learning applications (TensorFlow, PyTorch, etc.) end to end on cluster
management platforms (like YARN/K8s)
## Project Status:
Current project status: We're working on the 0.8 release and will release it
within the next two weeks. Currently, we are designing and implementing a new
feature called Submarine Manager, which can automatically manage and deploy ML
infrastructure, such as training operators and Ray servers.
Issues for the board: [None]
## Membership Data:
Apache Submarine was founded on 2019-10-15 (4 years ago)
There are currently 36 committers and 11 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:1.
Community changes, past quarter:
- The latest committer was added on 2023-01-05 (Xiang Chen).
- The latest PMC member was added on 2022-07-25 (Brandon Lin).
## Project Activity:
- We are preparing to make release candidates for 0.8 in the coming week
- Refactor code base.
- Bug fixes, and update the contribution guide.
## Community Health:
The number of contributors on github increased, and more people have asked
questions about deployment, and been trying to adopt Submarine internally. The
community sync has two new members.
-----------------------------------------
Attachment BX: Report from the Apache Synapse Project [Isuru Udana]
-----------------------------------------
Attachment BY: Report from the Apache Tomcat Project [Mladen Turk]
## Description:
- A Java Servlet, JavaServer Pages, Java WebSocket and Java
Unified Expression language specifications implementation
and Jakarta EE equivalents.
## Project Status:
- There are no issues requiring board attention at this time
## Membership Data:
- Apache Tomcat was founded 2005-05-18 (18 years ago)
- There are currently 48 committers and 29 PMC members in this project.
- Han Li was added to the PMC on 2023-03-06.
- No new committers. Last addition was Han Li on 2022-08-23.
## Project Activity:
- Apache Tomcat 11.0.0-M11 was released on 2023-08-25.
- Apache Tomcat 11.0.0-M10 was released on 2023-08-14.
- Apache Tomcat 11.0.0-M9 was released on 2023-07-10.
- Apache Tomcat 10.1.13 was released on 2023-08-25.
- Apache Tomcat 10.1.12 was released on 2023-08-14.
- Apache Tomcat 10.1.11 was released on 2023-07-10.
- Apache Tomcat 9.0.80 was released on 2023-08-25.
- Apache Tomcat 9.0.79 was released on 2023-08-15.
- Apache Tomcat 9.0.78 was released on 2023-07-10.
- Apache Tomcat 8.5.93 was released on 2023-08-15.
- Apache Tomcat 8.5.92 was released on 2023-08-14.
- Apache Tomcat 8.5.91 was released on 2023-07-10.
- Apache Tomcat Native 2.0.5 was released on 2023-08-07.
- Apache Tomcat Native 1.2.38 was released on 2023-08-07.
## Community Health:
- Continued healthy activity across multiple components and
responsiveness on both dev and user lists.
- Participating in the web-server/Tomcat track at
ApacheCon/Community Over Code(CON?) in Halifax in October
- The Apache Tomcat will end support for
Apache Tomcat 8.5.x on 31 March 2024.
https://tomcat.apache.org/tomcat-85-eol.html
## Trademark:
- No new trademark issues in the last 3 months
and there are currently no outstanding trademark issues that the
Apache Tomcat PMC is working on.
-----------------------------------------
Attachment BZ: Report from the Apache TomEE Project [David Blevins]
## Description:
Apache TomEE delivers enterprise application containers and services based
on, but not limited to the Enterprise JavaBeans Specification and Java
Enterprise Edition Specifications.
## Health
Activity on the project over the last quarter has been low with just 10
commits to main in the previous three months from today (9/17). We seem to
be steadily trending downward over the years. Here's an analysis of commits
broken up by calendar quarter since work first started on TomEE 1.0.
Year Q1 Q2 Q3 Q4 Average
---- --- --- --- --- -------
2023 30 42 7 26
2022 248 175 78 107 152
2021 66 141 41 34 70
2020 33 147 123 94 99
2019 446 190 214 120 242
2018 156 58 141 555 227
2017 58 88 108 104 89
2016 116 114 174 69 118
2015 234 263 65 127 172
2014 234 353 396 363 336
2013 434 264 195 188 270
2012 632 671 632 597 633
2011 111 266 486 400 315
The project has actively been trying to increase participation. Users on the
user list are frequently encouraged to help and given the "every contribution
helps" perspective.
The few that have shown interest are given very warm and encouraging
responses with a great deal of coaching to feel comfortable asking questions,
not get discouraged, not be hard on themselves and are encouraged to start
small and get the encouragement a quick win before trying bigger tasks.
Despite our efforts, almost no one makes it to the point where they can
contribute to core code in any capacity. Contributions typically stop at
minor doc updates and library upgrades.
Those that do show enough promise to make it to committer tend to not
continue contributing very long. We've added 7 committers in the last 6
years and of that list only one contributes regularly. Two in the list
stopped contributing once they gained the committer title, three stopped
committing in the first year. Lowering the bar to commit hasn't really
helped.
A significant bar to entry has always been that the TCKs we implement were
restricted and not available to the public. These were all open sourced in
2018/2019 and we had hoped this would be key in enabling more members of the
community to help with the main work of the project, getting compliance tests
to pass and shipping certified releases. This hasn't really helped and in
fact the new faster pace at which specifications are released seems to only
hurt us.
We had reported build times as a potential deterrent (they were 4-5 hours)
and worked with Infra to help setup builds in AWS. This was complete last
quarter. So far we have had only one PR from a contributor to test out this
new system and that PR has remained in a breaks-the-build state for 2 weeks.
We will keep trying, but overall it seems like very few are in a position to
contribute. There is a high bar in terms of time and experience we simply
cannot control or reduce. Fixing one TCK test can take a very experienced
person one week full-time. You need to research cryptic text in
specifications, do deep debugging in code you don't know to find causes, and
find intricate solutions that do not cause new failures elsewhere. Due to
the time involved it isn't something you can do without the support of your
employer and it doesn't appear anyone who uses TomEE has interest in
investing in the project at that level.
## Activity
As mentioned above, activity has been low -- 10 commits to main in the last
90 days. No new releases have been shipped.
The work done has largely been around the integration between TomEE and CXF,
specifically to get CXF 4.0 fully integrated. We have seen a new face arrive
and offer to help in this area and has openend a PR to help setup the new
Jakarta REST TCK suite from Jakarta EE 10. It's not fully working and breaks
the build, but is still very positive. Any kind of start is a good start.
## PMC changes:
- Currently 13 PMC members.
- Last PMC addition Richard Zowalla on May 23rd, 2022
## Committer base changes:
- Currently 33 committers.
- Last committer added was Richard Zowalla on January 6th 2021
## Releases:
None
-----------------------------------------
Attachment CA: Report from the Apache TVM Project [Tianqi Chen]
## Description:
The mission of Apache TVM is the creation and maintenance of software related
to compilation of machine learning models to run on a wide range of hardware
platforms
## Project Status:
Current project status: Ongoing
Issues for the board: there is no specific issue that need board action.
We would like to inform board about some of the latest community resolutions
(please see more on community healthy section).
## Membership Data:
Apache TVM was founded 2020-11-17 (3 years ago)
There are currently 71 committers and 26 PMC members in this project.
The Committer-to-PMC ratio is roughly 9:4.
Community changes, past quarter:
- There is on going threads bringing in new PMC members and committers
- Yong Wu was added as committer on 2023-06-13
## Project Activity:
Recent releases:
0.13.0 was released on 2023-08-08.
0.12.0 was released on 2023-05-13.
The project continues to push the frontiers of machine learning compilation.
Some feature highlights include:
- Better dynamic shape support in low-level codegen
- Various importer improvements
- Initial foundations to support H100 GPUs
The community also continues to participate in the unity branch development.
We have observed growing interest and participation in tvm unity development,
especially around enabling emerging foundational models. The majority of the
community, including members developing the core modules, also supports the
need to put more investment into foundational models. Such sentiment is also
shared among volunteer developers who would like enable the latest models.
## Community Health:
We get about 140 monthly commits from ~50 authors. We start to see a growing
demand from the community to empowering emerging directions like foundational
models and bring strategic innovations for the community.
In August, the community had a series of discussions on the desire to bring in
innovations for emerging directions (foundational models) as well as the
overall process for enabling strategic decisions in the community. These
discussions are follow-ups to help us address stagnation and continue to
empower everyone, see also the previous actions that were brought in the board
report [2].
As the community pushes for different goals that help each other, naturally,
there are strategy decision points about overall directions and new module
adoptions. These decisions are not fine-grained code-level changes but are
important for a community to be viable in the long term. The evolution pace of
the ML/AI landscape is also very fast; the cost of stagnation is high, and it
is critical for the community to be able to make collective strategic
decisions together and empower the community.
Taking these and the past year's context into consideration, we follow the ASF
process that enables the community to have a collective conversation that
gains clarity of everyone's view and then comes to a resolution for the
process of strategic decisions. The community passed a clear and
concise process for strategy decisions[1].
This item does not need board action, as the TVM PMC handled the case through
the standard ASF process and empowers the community. We believe it is
important to keep the board informed, so we are bringing it up in the report.
--
[1] https://lists.apache.org/thread/ywwsdfxqv0wvz3wz19w6nqgqx23kswql
[2] https://github.com/apache/tvm-rfcs/pull/89#issuecomment-1404170556
-----------------------------------------
Attachment CB: Report from the Apache UIMA Project [Richard Eckart de Castilho]
## Description:
Apache UIMA (*) software provides frameworks, tools and annotators,
facilitating the analysis of unstructured content such as text, audio and
video. (*) Unstructured Information Management Architecture.
## Project Status:
Current project status: Ongoing (low)
Issues for the board: none
## Membership Data:
Apache UIMA was founded 2010-03-17 (13 years ago)
There are currently 25 committers and 17 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:5.
Community changes, past quarter:
- No new PMC members. Last addition was Pablo Duboue on 2023-03-07.
- No new committers. Last addition was Pablo Duboue on 2023-03-06.
## Project Activity:
- Pablo has picked up work on the UIMA-CPP project again.
- Working on new releases of UIMA Java SDK, uimaFIT and UIMA Ruta
hopefully to be completed with the next weeks.
## Community Health:
At present, there is little activity. Occasional user activity on the mailing
list / issue tracker, but not much overall.
-----------------------------------------
Attachment CC: Report from the Apache Unomi Project [Serge Huber]
## Description:
The mission of Apache Unomi is the creation and maintenance of software related
to providing a reference implementation of the OASIS Customer Data Platform
specification currently being worked on by the OASIS Context Server Technical
Committee
## Project Status:
Current project status: Ongoing with moderate activity
Issues for the board: None
## Membership Data:
Apache Unomi was founded 2019-02-20 (5 years ago)
There are currently 16 committers and 7 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 Taybou on 2021-03-19.
- No new committers. Last addition was Francois Gerthoffert on 2022-09-15.
## Project Activity:
We've had two releases since the last report, one on the maintenance branch
1.9.1 and one on the main branch (2.4.0). Overall the project is improving the
behavior of the new 2.x version and making sure that the upgrade from the
previous main version 1.x is as smooth as possible. A lot of bugfixes for
large data sets were also released as well as other corrections requested by
the community of users. The focus will remain on improving overall quality and
migration for a while, before focusing on introducing new features.
## Community Health:
The community is quite active on the development side, but there is less
activity on the users side. We attribute this mostly to the fact that people
are using the
1.x version and are happy with it for the moment, but we expect more activity
as they move to version 2.x. Also we do need to promote the project a bit
better, notably by announcing the new version in the Apache announce mailing
list. Here are the usual stats:
- dev@unomi.apache.org had a 61% decrease in traffic in the past quarter (265
emails compared to 674)
- 58 commits in the past quarter (-40% change)
- 7 code contributors in the past quarter (-22% change)
- 23 PRs opened on GitHub, past quarter (-51% change)
- 16 PRs closed on GitHub, past quarter (-69% change)
-----------------------------------------
Attachment CD: Report from the Apache VCL Project [Josh Thompson]
## Description:
The mission of the Apache VCL project is to create and maintain of software
related to a modular cloud computing platform which dynamically provisions and
brokers remote access to compute resources.
## Project Status:
Current project status: Dormant
Issues for the board: There are no issues requiring board attention.
## Membership Data:
Apache VCL was founded 2012-06-19 (11 years ago)
There are currently 10 committers and 8 PMC members in this project.
The Committer-to-PMC ratio is 5:4.
Community changes, past quarter:
- No new PMC members. Last addition was Mike Jennings on 2020-08-24.
- No new committers. Last addition was Mike Jennings on 2019-01-04.
## Project Activity:
- Last release: 2019-07-25
- We still remain a dormant community. VCL is still in use at various
locations. We still have members who would really like to make time to get
another release out.
## Community Health:
Even though the community is quiet on the lists, Apache VCL is still actively
being used.
-----------------------------------------
Attachment CE: Report from the Apache Whimsy Project [Shane Curcuru]
## 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
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache Whimsy was founded 2015-05-19 (8 years ago)
There are currently 12 committers and 10 PMC members in this project.
The Committer-to-PMC ratio is 6:5.
Community changes, past quarter:
- No new PMC members. Last addition was Matt Sicker on 2020-04-11.
- No new committers. Last addition was Matt Sicker on 2020-04-09.
## Project Activity:
Project activity is low but steady, with any critical bugs getting attention.
## Community Health:
As usual we rely primarily on one committer although do have several other PMC
members present. While Infra is building a new supported Board Agenda tool to
replace the Whimsy one, the other critical and complex tool that Whimsy
provides is the Secretary Workbench. Long term, that needs to be our next
maintenance focus.
-----------------------------------------
Attachment CF: Report from the Apache Wicket Project [Andrea Del Bene]
## Description:
The mission of Wicket is the creation and maintenance of software related to
Component-based Java Web Application Framework.
## Project Status:
Current project status: Ongoing with moderate activity
Issues for the board: There are no issues requiring board attention.
## Membership Data:
Apache Wicket was founded 2007-06-20 (16 years ago)
There are currently 33 committers and 32 PMC members in this project.
The Committer-to-PMC ratio is roughly 9:8.
Community changes, past quarter:
- No new PMC members. Last addition was Thomas Heigl on 2020-08-14.
- No new committers. Last addition was Thomas Heigl on 2020-05-18.
## Project Activity:
On the last quarter we released versions 9.14.0 and 8.15.0. As I'm writing we
are about to start the release for 9.15.0 and the next 10 milestone M2. After
M2 we decide to proceed with final release of Wicket 10 as there are no more
active developments on its branch, so we gonna get in touch with ASF press stuff
shortly :-)!
## Community Health:
community remains healthy and still submit PRs and its interest in Wicket 10
remains at high level. At the same time cumulative downloads have increased on
the last quarter reaching a new all-time record of > 600k downloads.
-----------------------------------------
Attachment CG: Report from the Apache Xerces Project [Michael Glavassevich]
Description
Apache Xerces is a collaborative software development project dedicated to
providing robust, full-featured, commercial-quality, and freely available XML
parsers and closely related technologies on a wide variety of platforms
supporting several languages.
========
Xerces-J
We have been having votes to add new committers and PMC members and just
extended an invitation to the first individual after that vote completed.
Activity since the previous report has been limited to discussion on JIRA
issues, most recently concerning a user request to support a security feature
that was added to the JDK.
Mailing list traffic has been low; roughly 20+ posts on the j-dev and j-users
lists since the beginning of May 2023.
No new releases since the previous report. The latest release is Xerces-J
2.12.2 (January 24th, 2022).
========
Xerces-C
Since the last report there was some minor activity in GitHub. A few pull
requests were reviewed or commented on and one from a member of the community
was merged.
Mailing list traffic has been low; roughly 20+ posts on the c-dev and c-users
lists since the beginning of May 2023.
No new releases since the previous report. The latest release is Xerces-C
3.2.4 (October 17th, 2022).
========
Xerces-P
Nothing in particular to report. There was no development activity over the
reporting period.
========
XML Commons
No activity over the reporting period.
========
Committer / PMC Changes
The most recent committers were added in April 2017 (Xerces-C) and May 2017
(Xerces-J).
No new PMC members since the last report. The most recent addition to the PMC
was in June 2016.
One committer has merged a PR in GitHub since May 2023. There were no commits
made to SVN.
-----------------------------------------
Attachment CH: Report from the Apache Yetus Project [Allen Wittenauer]
## Description:
Apache Yetus provides libraries and tools that enable contribution and
release processes for software projects.
## Project Status:
Current project status: Ongoing, low activity
Issues for the board: None
## Membership Data:
Apache Yetus was founded 2015-09-15 (8 years ago)
There are currently 12 committers and 9 PMC members in this project.
The Committer-to-PMC ratio is 4:3.
Community changes, past quarter:
- No new PMC members. Last addition was Akira Ajisaka on 2018-12-17.
- No new committers. Last addition was Akira Ajisaka on 2018-02-06.
## Project Activity:
0.14.1 was released on 2022-10-17.
Work is continuing on getting a new release out, hopefully this upcoming
quarter. There are no critical bugs and downstream users have been mostly
quiet. Still we have some things we need to get out sooner rather than
later, given that the container image will need to switch to the newer
Ubuntu LTS image before it EOLs.
## Community Health:
Release work is happening, so there has been some movement:
6 issues opened in JIRA, past quarter (-50% change)
16 issues closed in JIRA, past quarter (128% increase)
21 PRs opened on GitHub, past quarter (250% increase)
21 PRs closed on GitHub, past quarter (162% increase)
-----------------------------------------
Attachment CI: Report from the Apache ZooKeeper Project [Flavio Paiva Junqueira]
## Description:
Apache ZooKeeper is a system for distributed coordination. It enables
the implementation of a variety of primitives and mechanisms that are
critical for safety and liveness in distributed settings, e.g.,
distributed locks, master election, group membership, and configuration.
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache ZooKeeper was founded 2010-11-17 (13 years ago)
There are currently 32 committers and 16 PMC members in this project.
The Committer-to-PMC ratio is 2:1.
Community changes, past quarter:
- No new PMC members. Last addition was Mate Szalay-Beko on 2022-03-28.
- No new committers. Last addition was Li Wang on 2023-03-17.
## Project Activity:
Recent releases:
3.9.0 was released on 2023-08-03.
3.8.2 was released on 2023-07-17.
## Community Health:
There has been two releases in the past quarter, including a major release,
which led to an overall increase of project traffic.
- dev@zookeeper.apache.org had a 257% increase in traffic in the past
quarter (168 emails compared to 47)
- notifications@zookeeper.apache.org had a 173% increase in traffic
in the past quarter (353 emails compared to 129)
- user@zookeeper.apache.org had a 100% increase in traffic in the
past quarter (62 emails compared to 31)
- 35 issues opened in JIRA, past quarter (45% increase)
- 22 issues closed in JIRA, past quarter (-38% change)
- 57 commits in the past quarter (185% increase)
- 18 code contributors in the past quarter (260% increase)
- 48 PRs opened on GitHub, past quarter (128% increase)
- 35 PRs closed on GitHub, past quarter (52% increase)
------------------------------------------------------
End of minutes for the September 20, 2023 board meeting.
Index