Index
Links: 2023 - All years
- Original The Apache Software Foundation
Board of Directors Meeting Minutes
December 20, 2023
1. Call to order
The meeting was scheduled for 21:00 UTC and began at 21:00 when
a sufficient attendance to constitute a quorum was recognized by
the chair.
Other Time Zones: https://timeanddate.com/s/43a0
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
Willem Ning Jiang
Justin Mclean
Craig L Russell
Sander Striker
Directors Absent:
Sharan Foga
Executive Officers Present:
Craig R. McClanahan
David Nalley
Matt Sicker
Ruth Suehle - joined :05
Executive Officers Absent:
none
Guests:
Brian Proffitt - joined :01
Chris Wells
Daniel Gruno
Greg Stein
Jarek Potiuk
3. Minutes from previous meetings
Published minutes can be found at:
https://www.apache.org/foundation/board/calendar.html
A. The meeting of October 18, 2023
See: board_minutes_2023_10_18.txt
Approved by General Consent.
B. The meeting of November 15, 2023
See: board_minutes_2023_11_15.txt
Approved by General Consent.
4. Executive Officer Reports
A. Board Chair [Sander Striker]
First of all I'd like to thank Sharan for running last months' meeting
in my absense. We now have a date set for our annual members meeting,
which I'll start preparations for over the holidays.
I observe there is only 11 more days in 2023. Between world events
and personal challenges I don't mind to put this year behind us. That
said I am grateful for all of the great people in our community that
contribute creating software for the public good.
I would like to wish everyone a healthy 2024!
B. President [David Nalley]
Following the resignation of Rich Bowen as VP, Conferences, I've
appointed Brian Proffitt to the position. While it's less than ideal
to have Brian serving in two operational officer roles at once, the
different workstreams are well aligned, and Brian is confident about
being able to scale and execute in the various roles.
I'd like to thank Rich for his long and storied history of running
first ApacheCon and then Community Over Code.
Mark Cox and I have been invited to the US Cybersecurity and
Infrastructure Security Agency's Open Source Security Summit in March
2024. Based on what we know now, the agency is trying to invite key
open source organizations for participation at the conference.
Additionally, please see Attachments 1 through 9.
C. Treasurer [Craig R. McClanahan]
As with previous months, things are running smoothly.
We (Treasury) are making plans to update the "Treasurer Internal"
section of the ASFP wiki in the coming months.
D. Secretary [Matt Sicker]
In November, the secretary received 77 ICLAs and one CCLA.
E. Executive Vice President [Ruth Suehle]
Dates secured and contract signed for CoC NA. More info in VP
Conferences report.
F. Vice Chair [Sharan Foga]
- Chair unavailable to attend previous meeting (November) due to illness
- As Vice Chair ran board meeting in their place
Executive officer reports approved as submitted by General Consent.
5. Additional Officer Reports
A. VP of W3C Relations [Andy Seaborne / Christofer]
No report was submitted.
B. Apache Legal Affairs Committee [Roman Shaposhnik / Rich]
See Attachment 11
C. Apache Security Team Project [Mark J. Cox / Bertrand]
See Attachment 12
D. VP of Jakarta EE Relations [Rob Tompkins / Willem]
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:
# Data Privacy [jmclean]
A. Apache Airflow Project [Bolke de Bruin / Bertrand]
See Attachment A
B. Apache Allura Project [David Philip Brondsema / Sander]
No report was submitted.
C. Apache Ant Project [Jan Materne / Justin]
See Attachment C
D. Apache Archiva Project [Olivier Lamy / Sharan]
No report was submitted.
E. Apache Atlas Project [Madhan Neethiraj / Shane]
See Attachment E
F. Apache Axis Project [Robert Lazarski / Craig]
See Attachment F
G. Apache Bahir Project [João Boto / Shane]
No report was submitted.
H. Apache Beam Project [Kenneth Knowles / Rich]
No report was submitted.
I. Apache Bigtop Project [Yuqi Gu / Sander]
No report was submitted.
J. Apache Bloodhound Project [Gary Martin / Christofer]
No report was submitted.
K. Apache BuildStream Project [Tristan Van Berkom / Bertrand]
No report was submitted.
L. Apache BVal Project [Matthew Jason Benson / Justin]
See Attachment L
M. Apache Camel Project [Andrea Cosentino / Willem]
See Attachment M
N. Apache Cayenne Project [Michael Ray Gentry / Sharan]
See Attachment N
O. Apache CloudStack Project [Rohit Yadav / Craig]
See Attachment O
P. Apache Commons Project [Gary D. Gregory / Rich]
See Attachment P
Q. Apache Cordova Project [Jesse MacFadyen / Bertrand]
See Attachment Q
R. Apache cTAKES Project [Pei Chen / Shane]
See Attachment R
S. Apache Curator Project [Enrico Olivelli / Sharan]
See Attachment S
T. Apache Daffodil Project [Mike Beckerle / Justin]
See Attachment T
U. Apache Doris Project [Mingyu Chen / Craig]
See Attachment U
V. Apache Drill Project [Charles Givre / Christofer]
See Attachment V
W. Apache Druid Project [Gian Merlino / Willem]
No report was submitted.
X. Apache ECharts Project [Wenli Zhang / Sander]
No report was submitted.
Y. Apache Felix Project [Karl Pauls / Willem]
See Attachment Y
Z. Apache Flex Project [Harbs / Shane]
No report was submitted.
AA. Apache Flink Project [Robert Metzger / Justin]
See Attachment AA
AB. Apache Gobblin Project [Abhishek Tiwari / Christofer]
See Attachment AB
AC. Apache Gora Project [Kevin Ratnasekera / Sander]
No report was submitted.
AD. Apache Guacamole Project [Mike Jumper / Craig]
See Attachment AD
AE. Apache Gump Project [Stefan Bodewig / Rich]
See Attachment AE
AF. Apache Helix Project [Junkai Xue / Bertrand]
See Attachment AF
AG. Apache Hive Project [Naveen Gangam / Sharan]
See Attachment AG
AH. Apache HttpComponents Project [Michael Osipov / Rich]
See Attachment AH
AI. Apache Hudi Project [Vinoth Chandar / Craig]
See Attachment AI
AJ. Apache Iceberg Project [Ryan Blue / Sander]
No report was submitted.
AK. Apache Impala Project [Jim Apple / Shane]
No report was submitted.
AL. Apache Incubator Project [Justin Mclean]
See Attachment AL
AM. Apache IoTDB Project [Xiangdong Huang / Sharan]
See Attachment AM
AN. Apache Jackrabbit Project [Marcel Reutegger / Justin]
No report was submitted.
AO. Apache Karaf Project [Jean-Baptiste Onofré / Christofer]
See Attachment AO
AP. Apache Kvrocks Project [Hulk Lin / Willem]
See Attachment AP
AQ. Apache Kyuubi Project [Kent Yao / Bertrand]
See Attachment AQ
AR. Apache Linkis Project [Shuai Di / Sander]
See Attachment AR
AS. Apache Lucene Project [Greg Miller / Bertrand]
See Attachment AS
AT. Apache Lucene.Net Project [Shad Storhaug / Craig]
No report was submitted.
AU. Apache Mnemonic Project [Gordon King / Shane]
No report was submitted.
AV. Apache Mynewt Project [Szymon Janc / Christofer]
See Attachment AV
AW. Apache NetBeans Project [Geertjan Wielenga / Rich]
No report was submitted.
AX. Apache OFBiz Project [Jacopo Cappellato / Willem]
See Attachment AX
AY. Apache Olingo Project [Michael Bolz / Sharan]
See Attachment AY
AZ. Apache OpenNLP Project [Jeff Zemerick / Justin]
See Attachment AZ
BA. Apache OpenWebBeans Project [Mark Struberg / Willem]
No report was submitted.
BB. Apache Pig Project [Koji Noguchi / Shane]
No report was submitted.
BC. Apache Pivot Project [Roger Lee Whitcomb / Craig]
No report was submitted.
BD. Apache PLC4X Project [Christofer Dutz]
See Attachment BD
BE. Apache Portable Runtime (APR) Project [Yann Ylavic / Bertrand]
See Attachment BE
BF. Apache Portals Project [Neil Griffin / Sharan]
See Attachment BF
BG. Apache Pulsar Project [Matteo Merli / Rich]
See Attachment BG
BH. Apache Ranger Project [Selvamohan Neethiraj / Sander]
See Attachment BH
BI. Apache Royale Project [Yishay Weiss / Justin]
See Attachment BI
BJ. Apache SeaTunnel Project [Jun Gao / Craig]
No report was submitted.
BK. Apache ServiceMix Project [Krzysztof Sobkowiak / Christofer]
See Attachment BK
BL. Apache Shiro Project [Brian Demers / Christofer]
See Attachment BL
BM. Apache SINGA Project [Wang Wei / Craig]
See Attachment BM
BN. Apache Sling Project [Robert Munteanu / Sharan]
No report was submitted.
BO. Apache Solr Project [David Smiley / Shane]
See Attachment BO
BP. Apache SpamAssassin Project [Sidney Markowitz / Sander]
See Attachment BP
BQ. Apache Storm Project [P. Taylor Goetz / Bertrand]
See Attachment BQ
BR. Apache Submarine Project [Kevin Su / Willem]
No report was submitted.
BS. Apache Synapse Project [Isuru Udana / Justin]
No report was submitted.
BT. Apache Tomcat Project [Mladen Turk / Rich]
See Attachment BT
BU. Apache TomEE Project [David Blevins / Sharan]
See Attachment BU
BV. Apache TsFile Project [Jialin Qiao / Rich]
No report was submitted.
BW. Apache TVM Project [Tianqi Chen / Christofer]
See Attachment BW
BX. Apache UIMA Project [Richard Eckart de Castilho / Justin]
See Attachment BX
BY. Apache Unomi Project [Serge Huber / Craig]
See Attachment BY
BZ. Apache VCL Project [Josh Thompson / Christofer]
See Attachment BZ
CA. Apache Velocity Project [Nathan Bubna / Willem]
No report was submitted.
CB. Apache Wicket Project [Andrea Del Bene / Sander]
See Attachment CB
CC. Apache Xalan Project [Gary D. Gregory / Bertrand]
See Attachment CC
CD. Apache Yetus Project [Allen Wittenauer / Shane]
See Attachment CD
CE. Apache ZooKeeper Project [Flavio Paiva Junqueira / Sander]
No report was submitted.
Committee reports approved as submitted by General Consent.
7. Special Orders
A. Change the Apache Calcite Project Chair
WHEREAS, the Board of Directors heretofore appointed Stamatis Zampetakis
(zabetak) to the office of Vice President, Apache Calcite, and
WHEREAS, the Board of Directors is in receipt of the resignation of Stamatis
Zampetakis from the office of Vice President, Apache Calcite, and
WHEREAS, the Project Management Committee of the Apache Calcite project has
chosen by vote to recommend Benchao Li (libenchao) as the successor to the
post;
NOW, THEREFORE, BE IT RESOLVED, that Stamatis Zampetakis is relieved and
discharged from the duties and responsibilities of the office of Vice
President, Apache Calcite, and
BE IT FURTHER RESOLVED, that Benchao Li be and hereby is appointed to the
office of Vice President, Apache Calcite, to serve in accordance with and
subject to the direction of the Board of Directors and the Bylaws of the
Foundation until death, resignation, retirement, removal or disqualification,
or until a successor is appointed.
Special Order 7A, Change the Apache Calcite Project Chair, was
approved by Unanimous Vote of the directors present.
B. Change the Apache ManifoldCF Project Chair
WHEREAS, the Board of Directors heretofore appointed Karl Wright
(kwright) to the office of Vice President, Apache ManifoldCF, and
WHEREAS, the Board of Directors is in receipt of the resignation of
Karl Wright from the office of Vice President, Apache ManifoldCF, and
WHEREAS, the Project Management Committee of the Apache ManifoldCF
project has chosen by vote to recommend Piergiorgio Lucidi
(piergiorgio) as the successor to the post;
NOW, THEREFORE, BE IT RESOLVED, that Karl Wright is relieved and
discharged from the duties and responsibilities of the office of Vice
President, Apache ManifoldCF, and
BE IT FURTHER RESOLVED, that Piergiorgio Lucidi be and hereby is
appointed to the office of Vice President, Apache ManifoldCF, to serve
in accordance with and subject to the direction of the Board of
Directors and the Bylaws of the Foundation until death, resignation,
retirement, removal or disqualification, or until a successor is
appointed.
Special Order 7B, Change the Apache ManifoldCF Project Chair,
was approved by Unanimous Vote of the directors present.
C. Change the Apache Cordova Project Chair
WHEREAS, the Board of Directors heretofore appointed Jesse MacFadyen
(purplecabbage) to the office of Vice President, Apache Cordova, and
WHEREAS, the Board of Directors is in receipt of the resignation of
Jesse MacFadyen from the office of Vice President, Apache Cordova, and
WHEREAS, the Project Management Committee of the Apache Cordova project
has chosen by vote to recommend Bryan Ellis (erisu) as the successor to
the post;
NOW, THEREFORE, BE IT RESOLVED, that Jesse MacFadyen is relieved and
discharged from the duties and responsibilities of the office of Vice
President, Apache Cordova, and
BE IT FURTHER RESOLVED, that Bryan Ellis be and hereby is appointed to
the office of Vice President, Apache Cordova, 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 Cordova Project Chair, was
approved by Unanimous Vote of the directors present.
D. Decision Regarding 401k Matching and Profit Sharing
WHEREAS, the 401k plan adopted by the Foundation, provided to
its US employees via ADP TotalSource and Voya, requires a formal
end of year decision regarding 401k contribution matching and
profit sharing;
NOW, THEREFORE, BE IT RESOLVED, that no 401k contribution matching,
nor profit sharing, will occur during Plan Year 2023.
Special Order 7D, Decision Regarding 401k Matching and Profit
Sharing, was approved by Unanimous Vote of the directors
present.
8. Discussion Items
A. Add security to board reports?
Security is becoming more of an issue in public discourse. Is the
board comfortable with letting projects handle (or not) security
issues without including the board in any way, including board
reports?
Craig L Russel suggests the board ask for a discussion of security in
each board report. A generic "any issues for the board" is
consistently not used for this purpose.
The board defers to the security team on this topic.
9. Review Outstanding Action Items
* Bertrand: follow up with Mark about Zeppelin
[ Security Team 2023-09-20 ]
Status: Duplicate, see 2023-11-15 item
* Christofer: pursue a roll call for VCL
[ VCL 2023-09-20 ]
Status: So far I got 3 people at least responding, however mostly
stating to be inactive and not expecting this to change. I
didn't see anyone actually saying: Yup I am there and I am
active.
* Rich: find out more about community health
[ Aries 2023-10-18 ]
Status: Done: There's been a considerable up-tick in activity since
this report, and it appears that the community is really
stepping up to get stuff done.
* Christofer: stage release candidate for final release and begin discussion
[ Cocoon 2023-10-18 ]
Status: Done: Cocoon 2.3.0 has been released and we are now discussing
the future of the project. Update: The project has decided to
retire 2.1 and 3.0 branches and to concentrate on 2.3 (the
latest release)
* Justin: follow up about the attic and how to plan for it
[ Geronimo 2023-10-18 ]
Status:
* Justin: follow up on current status of project
[ HAWQ 2023-10-18 ]
Status:
* Rich: follow up on project sustainability
[ JMeter 2023-10-18 ]
Status: Done. In poking around the project over the past 2 months, it
seems to me that it is, in fact, moderately active. I am not
concerned.
* Sharan: follow up on committer and PMC membership changes
[ MADlib 2023-10-18 ]
Status: Sent email https://s.apache.org/c1mk4 to request removing
committers from private list (or voting them in as full PMC
members) and PMC is following up.
* Sander: follow up about PMC removal process
[ Mahout 2023-10-18 ]
Status:
* Sander: clarify members of committers and PMC
[ ManifoldCF 2023-10-18 ]
Status:
* Shane: follow up about attic
[ Mesos 2023-10-18 ]
Status:
* Craig: follow up on attic
[ Pivot 2023-10-18 ]
Status: Pivot are preparing their expected "final release" in
anticipation of moving to the Attic.
* Justin: follow up on direction
[ Streams 2023-10-18 ]
Status:
* Shane: follow up about trademark usage policy
[ Traffic Server 2023-10-18 ]
Status:
* Sander: follow up about upcoming release
[ Zeppelin 2023-10-18 ]
Status:
* Rich: follow up on subproject governance on board list
[ Cassandra 2023-11-15 ]
Status: Done: Discussed this with various PMC members at Cassandra
Summit, and I believe I conveyed the importance of practively
reporting on subprojects. Will re-evaluate the next time they
report.
* Bertrand: follow up with security team about zeppelin roll call
[ Security Team 2023-11-15 ]
Status: This month's report says the security team is expecting a
roadmap from Zeppelin this month
* Justin: follow up on mentioning people's names in reports
[ ManifoldCF 2023-11-15 ]
Status:
* Sharan: check with Chris about vendor neutrality concerns
[ Ozone 2023-11-15 ]
Status: Followed up with Chris and waiting for confirmation if this
item is resolved
* Willem: follow up with PMC about community health
[ Traffic Control 2023-11-15 ]
Status: I'm sorry to see the Comcast ATC Open Source Withdrawal
Announcement here.
https://lists.apache.org/thread/36o316wxlk6jjp0cl3zc8w7dgnxr40qs
10. Unfinished Business
11. New Business
12. Announcements
13. Adjournment
Adjourned at 21:31 UTC
============
ATTACHMENTS:
============
-----------------------------------------
Attachment 1: Report from the VP of Brand Management [Mark Thomas]
Covering the period November 2023
* ISSUES FOR THE BOARD
None.
* OPERATIONS
Made some progress on the downstream distribution policy.
Responded to the following queries, liaising with projects as required:
- Referred one event request to planners@ due to CoC date conflict
- Provided advice to AVRO on permitted logo usage
- Provided advice to SOLR on sharing information on external training courses
- Approved names for TSFILE and RESILIENTDB
- Worked with CASSANDRA to improve planetcassandra.org
- Provided advice to FINERACT regarding a request to use the mark in a domain
name
- Provided advice to SDAP regarding the proposed logo
* REGISTRATIONS
The FINERACT registration in the US is complete.
The LOG4J registration in the US is complete.
Worked with counsel to maintain the NUTTX registration in the US.
Worked with counsel to transfer the remaining SERVICECOMB registrations to the
ASF.
* INFRINGEMENTS
Provided advice to OZONE regarding a potential infringement.
Provided feedback on some potentially infringing uses of the ICEBERG name and
logo on some conference stand material.
-----------------------------------------
Attachment 2: Report from the VP of Fundraising [Bob Paulin]
1) ASF Sponsors:
a --New: we onboarded one new Silver and one new Bronze Sponsor during this
timeframe.
b --Renewals: one Gold Sponsor and one Silver Sponsor have confirmed their
renewal.
c --Payments: 1 --New: we received no new Sponsor payments during this time
2a --Renewing: we received one Gold Sponsor renewal payment.
2b --Incoming: we await payment from two renewing Gold, two renewing
Silver, and one new Silver Sponsor.
2) Targeted Sponsors: we are onboarding a new Targeted Sponsor, and have
confirmed two Platinum Targeted sponsor renewals during this time.
3) Sponsor Relations: Sponsor outreach and engagement continues with increased
face-time as we approach the end of the year. We are also seeking new
points-of-contact with some of our Sponsors who have implemented reductions in
force.
4) Event Sponsorship: we are promoting the Community Over Code/Europe CFP and
will be socializing the 2024 event sponsorship prospectus when available. We
continue to pursue the final outstanding sponsorship payment from ApacheCon NA
2022.
5) Individual Donations and Corporate Giving: we launched this year’s Giving
Tuesday and End-of-Year giving campaigns in collaboration with Marketing &
Publicity. We received $3.16K in donations during this timeframe, which
includes a $1K corporate contribution.
6) Administrivia: we are working closely with the Treasury and Accounting
teams on a few remaining Sponsor invoicing issues.
-----------------------------------------
Attachment 3: Report from the VP of Marketing and Publicity [Brian Proffitt]
**Foundation Comms**
* Developed one-page guidance and form fill[1] for ASF projects to receive M&P
services; added to Wiki[2]
* Developed blog Q&A template to showcase ASF projects and use cases
* Published Apache Airflow security blog[3] on security
* Published Giving Tuesday blog[4] and promoted heavily across ASF social
channels
**Proactive Storytelling**
* First Contribution Campaign: technical documentation blog published[5] and
promoted
* Software for Public Good: Outreach to ComDev list began to solicit stories
underway
**Branding Project**
* Compiled research from Phase I into the Brand Landscape Document to inform
Phase II efforts including creation of Brand Book that includes messaging
**Website**
* Updated homepage to include Donation button for Giving Tuesday efforts
* Fundraising Support developed added to ASF private Wiki
**Social Media Posts**
November social content focused on Community Over Code EU CFP and
registration; project announcements; Giving Tuesday; the #FirstASFcontribution
campaign; and open source security efforts (Apache Airflow and OS3I response).
* In total, 26 Tweets + 7 LinkedIn posts were issued.
* Twitter impressions rose in November by 4.1%
* LinkedIn continues to be the largest contributor to network growth
month-over-month
**Social Engagement Stats (X + LinkedIn)**
* Total engagement: 2,073 (down 26% from October)
* Total clicks: 916 (down 29.8% from October)
* Click to engagement ratio: 44% (down 2% from September)
* New followers: 695 (up 8% from October)
**Website Analytics**
* 919,405 visits, 919,364 unique visitors -11%
* 2 min 44s average visit duration -6.3%
* 46% visits have bounced (left the website after one page) +2.2%
* 5.9 actions (page views, downloads, outlinks, internal site searches) per
visit +103.4%
* 10.006 max actions in one visit +10.2%
* 4,477,212 pageviews, 1,106,221 unique pageviews +111.4%
* 16 total searches on your website, 5 unique keywords +300%
* 539,185 downloads, 374,633 unique downloads -14.8%
* 368,430 outlinks, 207,948 unique outlinks +36.8%
[1] https://docs.google.com/forms/d/1jNmJJ0UzOaEvs8Vcc17oMiaoNVd-Dsn8j0NtP8ywqBE/edit
[2] https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=278466116
[3] https://news.apache.org/foundation/entry/strengthening-security-for-apache-airflow
[4] https://news.apache.org/foundation/entry/give-back-to-the-apache-community-with-a-year-end-donation
[5] https://news.apache.org/foundation/entry/first-time-asf-contributors-improve-technical-documentation-for-asf-projects-and-its-users
-----------------------------------------
Attachment 4: Report from the VP of Infrastructure [Myrle Krantz]
General
=======
Infrastructure is operating as expected, and has no current issues
requiring escalation to the President or the Board.
Finances
========
- An unexpected US$2700 cost for a contractor was needed, but not
budgeted for FY24. There should be available funds for this as part
of our Staffing costs.
Short Term Priorities
=====================
- Get the agenda tool into shape for running a Board meeting.
- Get ASF/Okta/Atlassian working together.
Long Range Priorities
=====================
- Artifact Distribution Platform
- Code Signing workflow
General Activity
================
- Lots of extensive work on moving the Agenda Tool fowards. It _may_
be ready to assist with running the December meeting, and certainly
for January.
- Continued struggling with Okta integration, in order to use the
Atlassian cloud products, synchronized with our LDAP database. We
have engaged a third-party to work through these issues.
- Additional work on our Kopia proof-of-concept for backups.
- Implemented an SMS-to-email gateway. The primary motivation here is
to assist the Treasurer office with SMS-based 2FA.
- Our oauth.a.o solution is now based on keycloak, rather than custom
in-house code. This will enable 2FA during the OAuth workflow.
- Some various Ansible work to manage a few boxes and processes. Infra
does not have a specific demand for a move to Ansible, but we're
using it for key tasks with an eye to future expansion.
- Working on Cassandra docker space/cleanup issues.
- Found/fixed a GitHub GraphQL issue that was holding up our account
and group synchronization.
- With MarkT, movement on a new set of code signing services for our
projects. Linux and Windows are easy, macOS is hard but it appears
we have solutions for all platforms. Next up is to dev/test these
new workflows. The result should open up code signing to ALL
projects, in a simplified manner.
- Infra will stop auto-subscribing third-party email archives to our
mailing lists, when they get created. We have been doing this for
years, but it is improper to favor specific parties. It has also
created minor issues with some of our email management.
- Continued work on setting up Azure/AWS VMs on demand. Spinning up
new images and stabilizing the service.
- On December 6, Infra hosted a Roundtable that was well-attended and
seemed to be very successful with the community.
- Upgrading a bunch of Ubuntu 18.04 boxes to 22.04 in order to use
mod_md for LetsEncrypt certificates (rather than relying on our
wildcard cert). The Bugzilla and Reviews boxes have presented some
challenges to this process.
-----------------------------------------
Attachment 5: Report from the VP of Conferences [Brian Proffitt]
Planning for Community Over Code EU[1] proceeds apace. A joint (with C/C NA)
prospectus has gone out, and social media content is continuing to be posted
about the CFP, closing January 12, 2024. The planning team is doing solid work
coordinating all the different parts of this new EU flagship event.
Community Over Code NA[2] has announced its date and venue, and will open its
CFP in January, after the close of the EU event's CFP. I will be asking for
tracks and chairs this week.
Community Over Code Asia 2024 will be held from July 26 to 28 in Hangzhou,
China.
[1] https://eu.communityovercode.org/
[2] https://communityovercode.org/
-----------------------------------------
Attachment 6: Report from the Apache Travel Assistance Committee [Gavin McDonald]
Current Events
==============
None
TAC App
=======
TAC App is closed currently.
Future Events
=============
Looking into a few events, discussion started on the mailing list. Fosdem has
been ruled out this year due to no booth/stand approval.
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
=====================
Discussion started around events to support for the coming months, as we may
need to get applications ready in the next month or two.
Membership
==========
No changes to the membership this month.
-----------------------------------------
Attachment 7: Report from the VP of Diversity and Inclusion [David Nalley]
-----------------------------------------
Attachment 8: Report from the VP of Data Privacy [Christian Grobmeier]
# General
There are no issues that need urgent attention.
Please see this report for decision to make shortly:
"Should the website policy be enforced? If yes, how?"
## Non-Policy conform websites
The projects using Google Analytics remains almost unchanged:
https://github.com/search?q=org%3Aapache+analytics.com&type=code&p=2
More than 100 projects appear to have Google Analytics on their sites.
On occasional check, I have seen the Apache Beam project is not only using
Google Analytics, but also Hotjar which is used for even more critical user
tracking. I have sent an e-mail with my recommendations to the Beam private
list, but no response:
https://lists.apache.org/thread/hsxpb3j4m3k3gpcj7hysbxv8gsz53q01
This raises an important question to me:
According to the GDPR, the DPO is only responsible for recognizing these kind
of issues, but not for enforcing their correction. Enforcement is done (or
not) by the Board.
I recommend to decide if the website policy should be enforced on projects or
not. If it should be enforced, there needs to be a decision who should enforce
it and how.
## Increased questions around licenses
There has been a spike of questions around our license. All questions are not
related to data privacy and could be ommitted, but demonstrate a confusion on
our license.
Example:
"I have a phone, and I found the Apache license on it. I never allowed you to
install software. Please remove it."
This is non critical, and will provide the responses I write on the privacy
website for future DPOs soon.
Note: most of these request go to vp-privacy directly and not to the mailing
list.
## Question on SurveyTools from ASF Cordova
The Apache Cordova project raised the question of a survey tool. I recommended
sticking with their idea of Google Forms, but to make it very clear what kind
of tooling is used, that the survey is optional and that not further personal
data is asked.
The Cordova team wrote an excellent invitation to the survey that made it
possible to use Google Forms.
## Confirmation of RingCentral
RingCentral bought Hopin with which we have a DPA. While RingCentral seems not
to be that supportive to the GDPR as Hopin was, I recommended to stick with
the platform for now. The DPA should be still valid.
## Subscription information for every new subscriber
Thanks to the good work of our Infra team and @Sebb, we now have subscriber
information on every mailing list.
https://issues.apache.org/jira/browse/INFRA-23011?filter=-2
While this may not seem like a big deal, this change allows us to justify to
*not* delete mailing list messages.
-----------------------------------------
Attachment 9: Report from the VP of Public Affairs [Dirk-Willem van Gulik]
The CRA got finalised in a marathon meeting between the countries, parliament
and commission that saw a lot of last-minute changes and an almost complete
reversal with respect to the situation around open source.
The first good thing is that the concept of `open source stewards' was solidly
introduced; whose `products' where placed under a much lighter regimen &
fines. And this is combined with an actual definition of open source and much
better definition of `commercial' that is not as close to placing things on
the market as before. Also good is that development and supply are no longer
seen as one; but pulled apart. That also gives room for individual developers;
i.e. natural persons, to be shielded for their upstream contributions (these
no longer are under the CRA; i.e. they & SMEs are not `liable' for that - e.g.
when their security fix boomerangs back through the ASF to the EU market).
Unfortunately we do not have the actual, final, text yet as approved; so a
decent analysis will have to wait for a few more weeks. The signing may still
happen this year; but is likely to be early Januari; with it coming into force
20 days later. There is then a 3 year period in which some 40-odd
(international) standards and other details need to be refined before the CRA
has all its `teeth'.
So we've gone from truly bad to possibly quite workable, and if one is
optimistic, to a situation where it may actually improve security.
That said - like similar regulation such as MRR/MRD, the industry will be
impacted; cost increases of about a third are generally expected. I am hopeful
that the ASF, and similar organisations, can help buffer some of that impact
by providing a place for the community to coordinate \& prevent double work.
Most of these implementation processes will be kicked off around FOSDEM, early
Feb, with a series of meetings and workshop. The ASF has expressed that it is
willing to work with its peers (e.g. the Python, Eclipse, etc) to assess
impact and develop best practices.
PLD - proceeding as expected; and has a workable `exceptions' subject to some
more thorough legal analysis (which will aid understanding - it won't make any
difference).
However there is now an odd situation; the CRA was way worse than the PLD; but
with the recent CRA changes - it now actually becomes interesting to improve
the PLDs definitions of open source and align these with the CRA. Both to
improve them -and- to make it easier to implement (i.e. no odd issues at the
fringes - as one will always need to implement the superset; both CRA and
PLD).
Regardless - this still means full, strict, liability will be in place
sometime early next year. These will void our `waivers' to a large extent
downstream from us; i.e. `after' our commercial downstream parties. While a
massive change for the industry - the impact on us appears very limited still.
With a bit of luck we have enough final text in late December to start doing a
proper legal analysis.
Various other acts, including the AI act, got through as well - but these by
and large contain the right sort of foundation/component exceptions that work
for communities such as the ASF that want to collectively work on code or
models.
US & Standards
Nothing to report in this cycle.
-----------------------------------------
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 made a
significant dent in the number and are standing flat at 17 issues.
-----------------------------------------
Attachment 12: Report from the Apache Security Team Project [Mark J. Cox]
- A fix for a serious issue in ActiveMQ (CVE-2023-46604) has been
released, but unfortunately it seems installations that have not
been upgraded are actively exploited. The issue has been added to
the CISA Known Exploited Vulnerabilities (KEV) Catalog.
- Based on input from various parts of the ASF, we have formulated a
response to the White House Office of the National Cyber Director
(ONCD) Request for Information (RFI) on "Open-Source Software
Security and Memory Safe Programming
Languages". https://www.regulations.gov/comment/ONCD-2023-0002-0106
- We have worked closely with DolphinScheduler to get back to security
health. While there is still significant work to do, the project
has been active and we are confident they will turn things around.
- We have worked with the Logging team supporting their efforts around
reproducibile builds and providing SBOM/VEX/VDR information.
- We have set up and experimental platform to collect and aggregate
SBOMs and information about advisories for 3rd-party
dependencies. This is already populated with information from 257
artifacts across 13 Apache projects, which we plan to expand and use
to get more actionable information.
Stats for Nov 2023:
34 [license confusion]
24 [report/question relating to dependencies]
15 [support request/question not security notification]]
Security reports: 74 (last months: 76, 66, 65)
17 ['website or other infrastructure']
8 ['airflow']
3 ['apr', 'arrow'']
2 ['doris', 'drill', 'guacamole', 'httpd', 'mxnet', 'nifi',
'struts', 'superset', 'vince', 'zeppelin']
1 ['answer', 'beam', 'cloudstack', 'commons', 'flink',
'gobblin', 'hive', 'iceberg', 'james', 'kylin', 'logging',
'mina', 'ofbiz', 'openoffice', 'poi', 'ranger', 'shiro',
'spark', 'streampark', 'tiles', 'tvm', 'wicket',
'zookeeper']
In total, as of 1st December 2023, we're tracking 180 (last
months: 183, 172) open issues across 59 projects, median age 122
days (last months: 116, 104). 52 of those issues have CVE names
assigned.
22 (last month: 20) of these issues, across 8 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
Issues for the board: See the events section
## Membership Data:
Apache Airflow was founded 2018-12-19 (5 years ago)
There are currently 61 committers and 32 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 Hussein Awala on 2023-07-29.
- Amogh Desai was added as committer on 2023-09-13
- Jens Scheffler was added as committer on 2023-11-07
- Pankaj Koti was added as committer on 2023-09-13
- Utkarsh Sharma was added as committer on 2023-11-29
## Project Activity:
- We continue the steady release of bug fixes (2.7.*) and new feature releases
(2.8) as well as regular Provider releases, Helm Chart and Python client.
- The 2.8 release (Release Candidate is up for voting) is about to be
released with new, important user-visible features: most notably fsspec
integration became first-class citizen for Airflow (Python ecosystem
de-facto standard for Object Storage interaction), consolidating logs from
multiple components, new listener for datasets, ability to cache virtualenvs
created dynamically.
- 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). Work is ongoing on connecting Datasets, Object
Storage, Event driven scheduling into a coherent modern way of interacting
with data and datasets. Most of these efforts are supposed to land in
Airflow 2.9.
- The funding from Sovereign Tech Fund for the 4 individuals resulted in
serious improvements and on-going work continues in that area. We have
already a complete set of tools to prepare and publish SBOM information for
Airflow and all 80+ providers. We are yet to publish information about it to
our users. We have implemented reproducible builds for all providers which
significantly improved reliability and robustness of verification of
releases (work is on-going to implement them also for core Airflow in the
way to not impact the development environment). We’ve added proactive
scanning for security issues. Most importantly we reviewed and significantly
improved security of the release process of our release/CI to add extra
layers of protection - following a security report we received in October,
where a typo/flaw in our CI process could make it potentially possible for
malicious users to inject code into the release process of ours. We checked
it did not happen and we introduced changes in the release process to make
sure that similar issues will not happen again. Blog post about it (TODO:
link to it) has been posted on Airflow Medium publication. We also iterated
on our security model and security policies based on our interaction with
security issue reporters and work on communicating better with our users and
reporters with regards to security.
- We are planning to improve the setup of the security team of ours by
introducing rotation among the members.
- We are planning to start regular Town-Hall online meetings (first planned in
January). During the Airflow Summit we had an informal meeting (using the
opportunity that a number of stakeholders, PMC members, committers were
physically present, and one of the takeaways there was that synchronous
(even remote ones) might work great
(of course providing that no decisions will be made there, minutes will be
posted, meetings will be recorded and agenda published well in advance) -
and we are attempting to experiment with it and start regular meetings.
- We started to actively pin-point some of the out-dated/not used providers
and remove them from active maintenance. We proposed and approved the
complete maintenance lifecycle for providers, with the goal of making sure
we do not have to maintain the code and that it does not slow us down, but
at the same time users will still be able to use the old providers and we
are ready to address security issues for them. We are doing it with
`daskexecutor`, `plexus` and `apache.sqoop` provider first following
discussions and lazy consensus. This is part of our continuous effort to
keep Airflow lean and adapt to changing reality
- We accepted a contribution (from Astronomer) of 5 LLM-related providers
- which is part of our continuous effort to adapt to
the changing environment and make Airflow a viable platform for LLM based
workflows.
## Community Health:
- We exceeded the milestone of 2700 contributors on GitHub this month (2600 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
- We continue getting new publications at our medium publication
https://medium.com/apache-airflow - whooping 18 new publications since last
report by various contributors
## Events
The Airflow Summit 2023 September 19-21 in Toronto, Canada was a great
success. We had around 500 attendees, the event broke-even financially and
sponsors, speakers and attendees satisfaction rate was high. We recorded and
published all talks on the Airflow Summit youtube channel. We gave free passes
to all the committers, we funded 15 scholarships for under-represented
attendees and our sponsors and organizers are looking forward to the 2024
event that will mark the 10th anniversary of Airflow. The organizers work
closely with the PMC, they’ve already started preparation and planning and the
date is set for the week 9th-11th of September 2024 in the Bay Area in the US
(details to be finalized), the plan is to have at least 1000 attendees. The
organizers obtained permission from the ASF trademarks, the efforts continue
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).
-----------------------------------------
Attachment B: Report from the Apache Allura Project [David Philip Brondsema]
-----------------------------------------
Attachment C: Report from the Apache Ant Project [Jan Materne]
## Description:
The mission of Apache Ant is the creation and maintenance of the Ant build
system and related software components.
It consists of the following main projects:
- Ant - core and libraries (AntLibs)
- Ivy - Ant based dependency manager
## Project Status:
Current project status: Primarily in bug fix mode and maintenance mode.
Issues for the board: None for now.
## Membership Data:
Apache Ant was founded 2002-11-18 (21 years ago)
There are currently 29 committers and 22 PMC members in this project.
The Committer-to-PMC ratio is roughly 4:3.
Community changes, past quarter:
- No new PMC members. Last addition was Magesh Umasankar on 2018-07-06.
- No new committers. Last addition was Jaikiran Pai on 2017-06-15.
## Project Activity:
The primary goal of Ant these days is to make sure that it can be
used to build projects using recent releases of Java.
Ant 1.10.14 was released on 20th August 2023 and is meant to be
usable with Java 8 and above. This release specifically introduced
necessary changes around its SecurityManager usage to allow using
Ant to build projects with Java 21. We haven't heard any major issues
with this released version. There have been few fixes after this
release which we will plan to release in the coming months.
Until recently, Apache IvyDE project was under the Ant PMC.
Given our inability to maintain it, the Ant PMC proposed a vote
to archive IvyDE project
https://lists.apache.org/thread/wo32q8s8o8z9m126gz3m533q2fnqq21o.
The vote passed and as of November 26th 2023, the IvyDE project
has been archived.
## Community Health:
Although we don't see too much development activity in Ant,
there are several active users of the Ant build tool. We
occasionally also see pull requests on GitHub.
For a project that's in maintenance mode, this amount of
activity, I believe, is decent.
-----------------------------------------
Attachment D: Report from the Apache Archiva Project [Olivier Lamy]
-----------------------------------------
Attachment E: 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.
- No new committers. Last addition was Umesh Padashetty on 2023-06-14.
## Project Activity:
- enhancements to support aging of entity audits
- added bridge for Couchbase
- performance improvement in notification processing with optimization in
fetching relationships
- removed references to Python2 with Python3
- improvements in dynamic index recovery
- fixes in Impala hook
- published Atlas client Python library 0.0.15
- updated versions of Okio, Apache Ivy
## Community Health:
- dev@atlas.apache.org had a 41% increase in traffic in the past quarter (247
emails compared to 174)
- 17 issues opened in JIRA, past quarter (-48% change)
- 14 issues closed in JIRA, past quarter (-30% change)
- 33 commits in the past quarter (3% increase)
- 11 code contributors in the past quarter (22% increase)
- 2 PRs opened on GitHub, past quarter (-71% change)
- 4 PRs closed on GitHub, past quarter (no change)
## 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 F: 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.
## Project state: Ongoing, with moderate activity
## Health report:
In this past quarter, committers in the Axis2 project who are also committers
in the Apache Web Services sub project Axiom committed fixes in the latter
project as described in Jira issue AXIOM-506 - a prerequisite to move Axis2
Java off of javax packages and into jakarta.
See AXIS2-6051 for the discussion on the Axis2 side, which resulted in commits
this quarter that changed hundreds of files and with a lot of work passed our
unit tests.
Work continues on the major refactoring of our sub project 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.
Rampart got a huge help this past quarter by a contribution that fixed unit
test problems that were difficult to debug. See RAMPART-449. Challenges for
this project includes no active committers use Rampart on their own projects.
The code contributions of two individuals in RAMPART-449 indicate likely
committer candidates and we are planning invitations.
Releases are planned this upcoming quarter in the order of Apache Axiom,
Apache Axis2, and Apache Rampart. Axis2 will continue to expand its JSON based
features in its next release and in general JSON developers are the best
chance of future growth in the project.
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: 2
## Axis2 java Jira issues closed in the last 90 days: 1
-----------------------------------------
Attachment G: Report from the Apache Bahir Project [João Boto]
-----------------------------------------
Attachment H: Report from the Apache Beam Project [Kenneth Knowles]
-----------------------------------------
Attachment I: Report from the Apache Bigtop Project [Yuqi Gu]
-----------------------------------------
Attachment J: Report from the Apache Bloodhound Project [Gary Martin]
-----------------------------------------
Attachment K: Report from the Apache BuildStream Project [Tristan Van Berkom]
-----------------------------------------
Attachment L: Report from the Apache BVal Project [Matthew Jason Benson]
## Description:
The mission of BVal is the creation and maintenance of software related to
Apache BVal: JSR-303 Bean Validation Implementation and Extensions
## Project Status:
Current project status: Ongoing-low/dormant
Issues for the board: none
## 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:
Version 3.0.0 of Apache BVal was released this quarter, hence the "ongoing"
status. Qualified as "low" due to the relatively "maintenance" nature of the
release. "Dormant" is the usual and anticipated-future state of the project.
## Community Health:
Community health remains unchanged overall. Things that need to get done are
getting done, typically by more recent participants in the community which
perhaps says something positive about the evolution of the community
composition. Small increases in commit/PR/email traffic look huge in
comparison to the near-zero levels we usually observe, but all told things
are business as usual.
-----------------------------------------
Attachment M: 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:
Current project status: Ongoing with high activity
Issues for the board: 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 91 committers and 45 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 Andrea Tarocchi on 2023-09-11.
- Aurélien Pupier was added as committer on 2023-11-13
- Jono Morris was added as committer on 2023-11-04
- Vignesh Nayak Manel was added as committer on 2023-09-12
## Project Activity:
Apache Camel:
- We released Camel 3.14.10
- We released Camel 3.20.7
- We released Camel 3.20.8
- We are about to release 3.20.9 at the time of writing (on vote)
- We released Camel 3.21.1
- We released Camel 3.21.2
- We are about to release 3.21.3 at the time of writing (on vote)
- We released Camel 4.0.1
- We released Camel 4.0.2
- We released Camel 4.0.3
- We released Camel 4.1.0
- We released Camel 4.2.0
- We are about to release 4.3.0 at the time of writing (on vote)
- 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.
- The next Camel 4.x LTS release will be 4.4.0 and we're working on that.
- We continued the release train for 3.20.x LTS, and we are about to release
the last 3.20.x release before the EOL.
- We are still supporting Camel 3.14.x, an LTS train. The release 3.14.10 will
be the last one before EOL.
- We continued the release train for 3.21.x LTS
- We are working on having also a 3.22.x LTS release in the near future
- The situation is really healthy and the community is super. We are doing a
lot of improvements and we are introducing new features.
Apache Camel K:
- For Camel K we released a really important 2.1.0 and a 2.0.1 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 3.2.0
- At the time of writing two releases are on vote too 3.2.3 and 3.6.0
- Camel K is in good shape and we are doing the best we can to improve the
developer experience.
Apache Camel Kamelets:
- We released Camel Kamelets 4.0.0
- We released Camel Kamelets 4.0.1
- We released Camel Kamelets 4.1.0
- We released Camel Kamelets 4.2.0
- We are working on releasing 4.3.0
- Camel-Kamelets is not only related to camel k anymore so it could be used
with all the Camel's flavours
- We are improving the overall experience and cleaning up the codebase to make
Kamelets runtime agnostic
Apache Camel Quarkus:
- 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.2.1
- We released Camel-quarkus 3.2.2
- We released Camel-quarkus 3.2.3
- We released Camel-quarkus 3.4.0
- We released Camel-quarkus 3.5.0
- We released Camel-quarkus 3.6.0
- The health of the project is really good and we are receiving a lot of
positive feedback and contribution
Camel-Karavan:
- Camel-Karavan is improving and more and more contributors are continuing to
help.
- We released the 4.0.0 version matching the LTS release
- We released also the 4.1.0 version
- The work is going really well and the community is starting to give
feedback.
Camel-Kafka-Connector:
- Camel Kafka Connector release based on Camel 4.0.0 has been released.
- We have a lot of feedback and issues opened and we are working on the
backlog
- We plan to release a new 4.3.0 release or at most we'll align to the 4.4.0
Overall:
- The Camel project and all the subprojects are in good shape and all of them
are growing in terms of community involvement.
## Community Health:
- 313 issues opened on GitHub, past quarter (3% decrease) and 307 issues
closed on GitHub, past quarter (8% decrease): Some of the subproject are
using github issues, but Camel core is still on JIRA. We focused mostly on
the LTS 4.4.x and some of the Github Issues based projects were focused on
backlog activities and alignments.
- 4598 commits in the past quarter (15% decrease) and 119 code contributors in
the past quarter (9% decrease):The camel core team is focusing on Camel
4.4.x. We saw a good number of contributions from new contributors in
subprojects and main Camel. The number of commits is related also to the
fact we are starting to use the squash and merge approach instead of the
rebase and merge.
- 1719 PRs opened on GitHub, past quarter (1% decrease) and 1723 PRs closed on
GitHub, past quarter (no change): The number are in line with what we are
doing right now, we expect an increase of PRs in the next quarter for two
reasons: we introduce dependabot on core Camel and we are going to release
multiple LTS releases, so we expect bug fixing and new PRs.
- dev@camel.apache.org had a 3% increase in traffic in the past quarter (427
emails compared to 411): There was a spike in the dev ML because of
questions and discussions around the development and final decision for
Camel 4.4.0, releases schedule, Spring Boot upgrade to 3.2.0 etc.
- issues@camel.apache.org had a 18% decrease in traffic in the past quarter
(2423 emails compared to 2935): We were focusing on backlog and the clean up
done in the last quarter justify the decrease.
- users@camel.apache.org had a 7% increase in traffic in the past quarter
(228 emails compared to 244): Users are starting to move and ask questions
on Zulip
- Jira Activity: The number doesn't seem to be accurate in the statistics
page. We saw an increase in terms of opened issues. The stats are the
following from the reporter: 324 issues opened in JIRA, past quarter (-22%
change) 343 issues closed in JIRA, past quarter (-16% change)
-----------------------------------------
Attachment N: Report from the Apache Cayenne Project [Michael Ray Gentry]
# Apache Cayenne Board Report, December 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 and developer mailing list activity increased due to 5.0 activity and
discussions. User mailing list traffic was low, but questions are actively
addressed.
-----------------------------------------
Attachment O: 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:
- There are currently 133 committers and 54 PMC members in this project.
- The Committer-to-PMC ratio is roughly 9:4.
PMC changes:
- Most recently added PMC member:
Abhishek Kumar was added to the PMC on 2023-11-23
Committer base changes:
- Most recently added committers: Bryan Lima
Bryan Lima was added as committer on 2023-11-30
Vladimir Petrov was added as committer on 2023-12-11
## Project Activity:
- The Apache CloudStack project released the current LTS version
4.18.0.0 on 20th March 2023. 4.18.1.0 was released on 2023-09-12.
- Apache CloudStack 4.19.0 is the next major release the
community is working towards, with RC1 to be cut in Dec 2023.
- Next releases, 4.18.2.0 and 4.20.0.0, are being discussed
in the community.
- The PMC is actively discussing new PMC Candidates and new
committers. There are one new PMC member and two new committers
added since the previous report.
- PMCs have voted to have download.cloudstack.org point to CDN77
sponsored CDN and caching services, making CloudStack repository
downloads faster for users.
- PMC and the community have voted to try and adopt Github Discussions
as a users forum alongside the users mailing list.
- The project is working to migrate to a new website that uses the same
Docusauras static-site generator as the blog. This is work in progress and
shared with the community for feedback and review of the proposed design.
The staging site is accessible at https://cloudstack.staged.apache.org
- The annual community organised CloudStack Collaboration Conference 2023
was successfully held during November 23-24th in Paris and online.
https://cloudstack.apache.org/blog/ccc2023-roundup
- Along with the Ceph community, the next CloudStack community event is
announced to be the CloudStack and Ceph Day Netherlands 2024 in Amsterdam
on Thursday, February 8, 2024. Registration and CFP is open for this event.
https://ceph.io/en/community/events/2024/cloudstack-and-ceph-day-netherlands/
- We have an approved CloudStack Track for Community Over Code Europe, 2024
and we're actively seeking for talks submissions for the same.
- The next CloudStack India User Group (CSIUG) meetup is being
discussed to be organised in Feb-March 2024.
## 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:
520 commits in the past quarter (63% increase)
53 code contributors in the past quarter (43% increase)
- GitHub PR activity:
257 PRs opened on GitHub, past quarter (7% increase)
287 PRs closed on GitHub, past quarter (22% increase)
- GitHub issues:
153 issues opened on GitHub, past quarter (7% increase)
79 issues closed on GitHub, past quarter (-44% change)
- Mailing lists Statistics:
- dev@cloudstack.apache.org had a 31% increase in traffic
in the past quarter (602 emails compared to 459)
- issues@cloudstack.apache.org had a 54% decrease in traffic
in the past quarter (7 emails compared to 15)
- marketing@cloudstack.apache.org had a 41% decrease in traffic
in the past quarter (16 emails compared to 27)
- users@cloudstack.apache.org had a 25% increase in traffic
in the past quarter (629 emails compared to 502)
- Recent releases:
- 4.18.1.0 was released on 2023-09-12.
- 4.18.0.0 was released on 2023-03-20.
- 4.17.2.0 was released on 2022-12-16.
-----------------------------------------
Attachment P: 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.
Issues for the board: None.
## Membership Data:
Apache Commons was founded 2007-06-19 (16 years ago)
There are currently 149 committers and 43 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:2.
Community changes, past quarter:
- Phil Steitz was added to the PMC on 2023-09-13
- No new committers. The last addition was Claude Warren on 2022-02-01.
## Project Activity:
We have released many new versions of components, specifically:
- VALIDATOR-1.8.0 was released on 2023-12-07.
- BCEL-6.8.0 was released on 2023-12-07.
- LOGGING-1.3.0 was released on 2023-11-30.
- IO-2.15.1 was released on 2023-11-29.
- LANG-3.14.0 was released on 2023-11-22.
- PARENT-65 was released on 2023-11-21.
- COMPRESS-1.25.0 was released on 2023-11-15.
- TEXT-1.11.0 was released on 2023-10-29.
- CLI-1.6.0 was released on 2023-10-26.
- IO-2.15.0 was released on 2023-10-25.
- PARENT-64 was released on 2023-10-09.
- NET-3.10.0 was released on 2023-10-05.
- PARENT-63 was released on 2023-10-05.
- POOL-2.12.0 was released on 2023-09-30.
- IO-2.14.0 was released on 2023-09-29.
- JCS-3.2 was released on 2023-09-18.
- DBUTILS-1.8.1 was released on 2023-09-14.
## Community Health:
We are busy processing PRs from GitHub, Jira tickets, and releasing new
versions of components regularly. On average, the statistics reveal a more or
less even activity level. It seems that more and more people are requesting
Jira accounts to contribute, the Jira moderation allows us to avoid spam.
-----------------------------------------
Attachment Q: Report from the Apache Cordova Project [Jesse MacFadyen]
## Status report for the Apache Cordova project - December 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.
## 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-inappbrowser@6.0.0 was released on 2023-11-23.
- cordova-plugin-device-orientation@3.0.0 was released on 2023-11-05.
- cordova-plugin-file@8.0.1 was released on 2023-11-05.
- cordova-plugin-screen-orientation@3.0.4 was released on 2023-11-05.
- cordova-plugin-statusbar@4.0.0 was released on 2023-11-05.
- cordova-plugin-geolocation@5.0.0 was released on 2023-09-21.
## Github activity:
Issue close rate of 81% 89 issues opened on GitHub, past quarter (-21% change)
72 issues closed on GitHub, past quarter (-35% change)
PR close rate of 127% 48 PRs opened on GitHub, past quarter (-69% change) 61
PRs closed on GitHub, past quarter (-60% change)
Commits 65 commits in the past quarter (-61% decrease) 11 code contributors in
the past quarter (-21% change)
-----------------------------------------
Attachment R: 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 (11 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 building/testing a 5.x release.
- 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:
dev@ctakes.apache.org had a 66% increase in traffic in the past quarter
(30 emails compared to 18) mainly regarding a new release.
There are few new user questions on user@.
The project is fairly niche and not as active as other ASF projects.
There are occasional quiet times as cdutz noticed in the last report,
but there is activity.
-----------------------------------------
Attachment S: 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:
In the past quarter we didn't see much activity but we saw PRs from new
contributors. We will probably cut a release soon in order to deliver the
changes to the community.
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:
As reported above we had some contributions by new users. Not enough to say
they they can be invited as committers. There is one in progress work to add
support for a new feature (OpenTelemetry support) and this is good for the
project, that tends to be tied to ZooKeeper lifecycle.
Some interesting data:
- dev@curator.apache.org had a 42% decrease in traffic in the past quarter (44
emails compared to 75)
- user@curator.apache.org had a 66% increase in traffic in the past quarter
(10 emails compared to 6)
- 9 commits in the past quarter (-35% change)
- 4 code contributors in the past quarter (33% increase)
-----------------------------------------
Attachment T: 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:
Current project status: The project is healthy based on ongoing activity and
releases. Daffodil version 3.6.0 was released on 2023-10-27.
The VSCode extension for Daffodil version 1.3.1 was released on 2023-09-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:
- No new PMC members. Last addition was Regis Thomas on 2023-07-31.
- No new committers. Last addition was Regis Thomas on 2023-08-01.
## Project Activity:
Collaboration with the Apache Drill project is ongoing and a draft PR of a
first cut integration of Daffodil and Drill now exists. It handles only flat
(row-like) data containing integers at this point, but represents a large step
forward in integrating two large code bases.
Daffodil Version 3.6.0 contains important performance improvements in Daffodil
unparsing (data serialization). It also supports the latest LTS Java (which is
Java 21).
## Community Health:
Activity level is acceptable, end of calendar year is always slower, and our
metrics reflect that, but overall there is good participation.
-----------------------------------------
Attachment U: Report from the Apache Doris Project [Mingyu Chen]
## Description:
The mission of Apache Doris is the creation and maintenance of software related
to a MPP-based interactive SQL data warehousing for reporting and analysis
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache Doris was founded 2022-06-15 (a year ago)
There are currently 59 committers and 17 PMC members in this project.
The Committer-to-PMC ratio is roughly 8:3.
Community changes, past quarter:
- No new PMC members. Last addition was Yongqiang Yang on 2023-01-10.
- No new committers. Last addition was Xin Gao on 2023-06-13.
## Project Activity:
We have released:
1. doris-flink-connector 1.5.0 on 4th Dec.
2. doris-spark-connector 1.3.0 on 4th Dec.
And we are voting on releasing Doris 2.0.3
## Community Health:
We held the Doris Summit Asia 2023 on Oct,
with more than 1000 people attended.
-----------------------------------------
Attachment V: 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: Ongoing
Issues for the board: No issues requiring board attention.
## 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:
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.
We are planning a maintenance release (v 1.21.2) which we will release before
the end of the year.
Additionally, for the last few months, we have been collaborating with
Mike Bekerle from the Apache Daffodil project. The goal being to enable
Drill to use Daffodil schemata to read and parse data. We are maybe 60%
complete with this task. This also has a dependency on Apache Daffodil
as Mike is developing some custom features for Daffodil.
Big thanks to Mike for taking on this project.
## Community Health:
Overall the community is healthy. We are working on some major improvements
such as the Daffodil integration and an XSD reader so the total number of
tickets is lower this quarter.
* 11 issues opened in JIRA, past quarter (-21% change)
* 10 issues closed in JIRA, past quarter (150% increase)
* 20 commits in the past quarter (-20% change)
* 7 code contributors in the past quarter (-12% change)
* 18 PRs opened on GitHub, past quarter (38% increase)
* 15 PRs closed on GitHub, past quarter (15% increase)
* 11 issues opened on GitHub, past quarter (57% increase)
* 3 issues closed on GitHub, past quarter (-25% change)
-----------------------------------------
Attachment W: Report from the Apache Druid Project [Gian Merlino]
-----------------------------------------
Attachment X: Report from the Apache ECharts Project [Wenli Zhang]
-----------------------------------------
Attachment Y: 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 (17 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 move to the Jakarta API (away from javax.*) is basically
done.
- We got some contributions and activity around iPOJO again so we took it out
of retirement and cut a new release (mostly porting to Java 17).
- Released 15 components. Some are bug fixes/minor improvements but most are
related to the move to the Jakarta API.
### Releases
- Apache Felix iPOJO Manipulator 1.13.0 was released on 2023-12-08.
- org.apache.felix.cm.json-2.0.4 was released on 2023-11-21.
- org.apache.felix.cm.json-2.0.2 was released on 2023-11-09.
- org.apache.felix.http.bridge-4.2.14 was released on 2023-11-06.
- org.apache.felix.http.jetty-4.2.20 was released on 2023-11-04.
- org.apache.felix.http.jetty-5.1.4 was released on 2023-11-04.
- org.apache.felix.webconsole-4.9.6 was released on 2023-10-07.
- org.apache.felix.http.base-5.1.2 was released on 2023-10-02.
- org.apache.felix.http.bridge-5.1.2 was released on 2023-10-02.
- org.apache.felix.http.jetty-5.1.2 was released on 2023-10-02.
- org.apache.felix.http.servlet-api-3.0.0 was released on 2023-10-02.
- org.apache.felix.http.wrappers-1.0.2 was released on 2023-10-02.
- org.apache.felix.http.wrappers-1.1.2 was released on 2023-10-02.
- org.apache.felix.healthcheck.core-2.2.0 was released on 2023-09-16.
- org.apache.felix.http.wrappers-1.1.0 was released on 2023-09-16.
## Community Health:
- Overall the project is in ok health with 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.
- After reducing our surface area by retiring components that haven't seen
activity in while (see last report), we did see some requests and
contributions for iPOJO again - hence, we moved it back and cut a release.
Hopefully this will result in new contributors.
- 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 Z: Report from the Apache Flex Project [Harbs]
-----------------------------------------
Attachment AA: 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 Issues for the board: none
## Membership Data:
Apache Flink was founded 2014-12-17 (9 years ago) There are currently 108
committers and 48 PMC members in this project. The Committer-to-PMC ratio is
9:4.
Community changes, past quarter:
- No new PMC members. Last addition was Matthias Pohl on 2023-08-03.
- Jane Chan was added as committer on 2023-10-13
- liu ron was added as committer on 2023-10-13
The Flink PMC is actively monitoring and discussing new PMC and committers.
## Project Activity:
Recent releases:
* connector-kafka-3.0.2 was released on 2023-12-01.
* connector-aws-4.2.0 was released on 2023-11-30.
* kubernetes-operator-1.7.0 was released on 2023-11-21.
* connector-kafka-3.0.1 was released on 2023-10-30.
* 1.18.0 was released on 2023-10-27.
From this list, the Flink 1.18 release is a major highlight with improvements
around Flink SQL (jdbc driver, extended DDL support, querying on historic
data), streaming engine improvements (per-operator state ttl, watermark
alignment for SQL), as well as the batch execution, with performance
improvements. For improved cloud/scaling support, fine-grained resource
elasticity and rescaling improvements for RocksDB have been added. The 1.7
release of the K8s operator decouples the autoscaler, drops legacy Flink
versions and other improvements.
The PMC has been handling a few security@ reports, as well as trademark issues
with various vendors offering Flink-based products.
## Community Health:
The Flink community is very healthy and active. There's a 14% increase in
activity on the dev@ mailing list, with discussions around various FLIPs and
proposals, such as contributing the collection of CDC connectors to Flink,
migrating from Azure Pipelines to Github Actions, planning Flink 1.19 as well
as Flink 2.0.
The commit activity is also going up. Some metrics around Jira tickets and
pull requests are going down, but there are no concerns by the PMC about this.
Flink Forward Seattle was held early November, with 45 talks and 400
registrations.
Flink Forward Asia was held on Dec 8 and 9th in Beijing with 78
talks and 550 attendees on site, as well as 110k unique viewers of the keynote
live stream.
-----------------------------------------
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: None.
## Membership Data:
Apache Gobblin was founded 2021-01-19 (3 years ago)
There are currently 20 committers and 12 PMC members in this project.
The Committer-to-PMC ratio is 5:3.
Community changes, past quarter:
- No new PMC members. Last addition was Abhishek Tiwari on 2021-01-19.
- Arjun Singh Bora was added as committer on 2023-10-09
## Project Activity:
- Improved logging for PasswordManager in Gobblin
- Added capability for Apache Iceberg Catalog to override dataset descriptor
for Iceberg Tables
- Addition of immutability for job names in GaaS
- Added capability to execute flows in multi-active scheduler state
- Addition of external data node for generic ingress/egress on GaaS
- Improvement in DistCp logic to compare permissions of soure and destination
files
- Support added in IcebergDatasetFinder to use separate names for source vs
destination DB and Tables
- Improved IcebergTable dataset descriptor to use DB-qualified table ID
- Added emission of audit counts after commit in IcerbergMetadataWriter
- Addition of semantics for failure on partial success
- Added consistentcy in handling of flow executions errors for Kill and Resume
actions
- Early stage Temporal integration
- Improved GobblinORCWriter to handle large records
- Kafka streaming pipeline improved to configure max poll records during
runtime
- Addition of metric to tune LeaseArbiterLinger metric
- Added capability to extend functions in GobblinMCEPublisher and
customization of fileList file metrics
- Added capability to detect malformed ORC during commit
- Added framework and unit tests for DAGActionStoreChangeMonitor
- Added implementation of Distributed Data Movement (DDM) Gobblin-on-Temporal
Workunit evaluation
- Added gobblin-temporal load generator for a single subsuming super-workflow
with a configurable number of activites
- Made KafkaTopicGroupingWorkUnitPacker configurable with desired number of
containers
- Developed Temporal abstractions including Workload for workflows of
unbounded size through sub-workflow nesting
- Added functions to fetch record partionColumn value and customize default
record timestamp
- Added quantification of Missed Work completed by Reminders
- Added capability to skip null DAG action types
- Updated logic in completeness verifier to support multi-reference tier
- Added monitoring of High Level Consumer queue size
- Added capability to monitor x bit in manifest file based copy
- Added custom partioner partioning based on record timestamp
- Implementation of fet dataset path for IcerbergDataset and
RecursiveCopyableDataset
- Addition of function in Kafka Source to recompute workunits for filtered
partitions
- Code improvements like consolidation of all DAG actions processing to one
code path, addition of exception message in ORC writers, emission of GTE
when corrupted ORC files are deleted, refactor of DAG actions, multi-active
related logs and metrics
- Various fixes like avoiding CopyDataPublisher committing workunits before
they actually run, prevention of NPE in FlowCompilationValidationHelper,
FlowSpec update function bug, FlowExecutionId made consistent across
participants
Last Release date: 30th August, 2023
## Community Health:
- There have been 80 commits since September 2023.
- 60 commits have been from non-committers.
- Arjun Singh Bora was voted in October, 2023 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]
-----------------------------------------
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 15 committers and 10 PMC members in this project.
The Committer-to-PMC ratio is 3:2.
Community changes, past quarter:
- No new PMC members. Last addition was Luke on 2023-02-22.
- Alexander Leitner was added as committer on 2023-11-13
## Project Activity:
The project recently released its latest patch release (1.5.4) and has started
work on the next (1.5.5). There is at least one apparent regression in 1.5.4
that should be addressed. The project is also pleased to welcome a new
committer: Alexander Leitner.
Recent releases:
- 1.5.4 was released on 2023-12-07.
- 1.5.3 was released on 2023-07-31.
- 1.5.2 was released on 2023-05-25.
## Community Health:
The community continues to be active and healthy. Activity level is largely
the same as at the time of last report, with a recent uptick correlating with
the release of 1.5.4.
-----------------------------------------
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. 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. During the past
quarter Gump has been migrated to use an early access version of Java
22 for its Java builds (thanks to Mark Thomas).
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 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.
- No new committers. Last addition was Molly Gao on 2023-06-06.
## Project Activity:
- 1.3.1 was released on 2023-09-28
- 1.3.0 was released on 2023-07-25
## Community Health:
Recently, Helix finished two projects:
1. Instance evacuate support: gracefully bootstrap data to new instances and
remove the partition from the old one.
2. Swap instance support: smoothly bootstrapping all replicas to new instance
and deprecate the old instance, which is transparent to user.
Additionally, there are several ongoing discussion about Helix logging in Helix
slack channel.
For next quarter, continuously improvement on evacuate need to be done:
1. Standardize the operation states including evacuate, disable and etc.
2. Transactionally get evacuated partition assignment align with eventual
assignment to avoid multi round shuffling.
A new release of 1.4.0 will come soon.
-----------------------------------------
Attachment AG: Report from the Apache Hive Project [Naveen Gangam]
## Description:
The mission of Hive is the creation and maintenance of software related to Data
warehouse infrastructure using the Apache Hadoop Database
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache Hive was founded 2010-09-22 (13 years ago)
There are currently 107 committers and 55 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 Krisztian Kasa on 2023-01-30.
- Sourabh Badhya was added as committer on 2023-09-24
- Butao Zhang was added as committer on 2023-11-30
## Project Activity:
4.0.0-beta-1 was released on 2023-08-14.
The community is working towards the 4.0.0 GA(expected Jan-24) and 3.2.X release
## Community Health:
Overall, community is very healthy. Almost 60 code contributors and 169
commits along with several discussions on User and Dev mailing lists.
-----------------------------------------
Attachment AH: Report from the Apache HttpComponents Project [Michael Osipov]
## Description:
- The Apache HttpComponents project is responsible for creating and
maintaining a toolset of low-level Java components focused on HTTP and
associated protocols.
## Issues:
- There are no issues requiring board attention at this time.
## Project Status
- All good
## Project Activity:
- Active feature developments happens on master (5.3.x) with Java 8
- 4.x. is open for security fixes only.
## Community Health:
- Overall the project remains active. Issues and dicussions are
resolved in time.
## Membership Data:
- No new PMC members. Last addition was Ryan Schmitt on 2019-08-28.
- New committer accepted: Arturo Bernal on 2022-06-18.
## Releases:
- HttpComponents HttpClient 5.3 2023-12-07
- HttpComponents HttpClient 5.2.3 was released on 2023-12-04
- HttpComponents HttpCore 5.2.4 was released on 2023-12-04
- HttpComponents HttpCore 5.2.3 was released on 2023-09-25
- HttpComponents HttpClient 5.3-alpha1 was released on 2023-08-21
-----------------------------------------
Attachment AI: 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 (4 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:
- Sagar Sumit was added to the PMC on 2023-11-05
- Prashant Wason was added to the PMC on 2023-11-05
- Hui An was added as committer on 2023-12-01
- Qijun Fu was added as committer on 2023-11-13
- Voon Hou was added as committer on 2023-12-01
## Project Activity:
The community made two big releases since the last report. 0.14.0 shipped with
a new fast indexing mechanism and ease-of-use around Spark SQL. We community
is now working towards a 0.14.1 patch release on top. We expect 0.14 to be the
last major release in the 0.X release line.
Over the past few months, a re-imagination and redesign of the project has
been proposed for 1.0 release and is been worked on actively. 1.0.0-beta-1 was
released to allow community to test early versions and provide feedback. This
has been particularly useful around brand new features like non-blocking
concurrency control. Development is continuing to make a GA release in Q1.
## Community Health:
Project continues to see healthy developer and user engagement. There are
couple PMC members who are helping with the PR review backlog. We are not
aware of any particular reason for drops in PR opened for e.g.Scaling the
review process and merging contributions remains an active area of investment.
We have had couple of CI instability issues. Some ongoing efforts to reduce
the test runtimes will help ease some of these challenges.
On the user side, we have had users share their usage of Hudi and vendors also
launch new product integrations around Hudi. Good chunk of the dev email spike
is new contributors requesting access. Another key process is to scale is
supporting community questions on a day-to-day basis. We have about 442 total
open support issues, (of which we closed 200 in the last quarter per wizard).
We are continuing to explore creative ways to scale this.
-----------------------------------------
Attachment AJ: Report from the Apache Iceberg Project [Ryan Blue]
-----------------------------------------
Attachment AK: Report from the Apache Impala Project [Jim Apple]
-----------------------------------------
Attachment AL: Report from the Apache Incubator Project [Justin Mclean]
=== Report content ===
# Incubator PMC report for December 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 28 podlings incubating. In December, podlings executed
5 distinct releases.
A new podling has joined the incubator HoraeDB, and there has been
discussion on several incubating proposals.
There was some cleanup of retired podlings.
The java-driver donation from the Cassandra project did not follow the
correct process.
Teaclave has not reported for some time, and a roll call will be undertaken.
## Community
### New IPMC members:
- Enrico Olivelli
- Ismaël Mejía
- Kent Yao
- Rakesh Radhakrishnan
### People who left the IPMC:
- none
## New Podlings
- HoraeDB
## Podlings that failed to report, expected next month
- KIE
- Teaclave
## Graduations
- None
The board has motions for the following:
- None
## Releases
The following releases entered distribution during the month of
November:
- Answer 1.2.0
- Opendal 0.42.0
- Pekko connectors 1.0.1
- Pekko persistence dynamodb 1.0.0
- Pekko 1.0.2
## IP Clearance
- Cassandra java-driver
## Legal / Trademarks
N/A
## Infrastructure
N/A
## Miscellaneous
N/A
## Table of Contents
[Answer](#answer)
[Baremaps](#baremaps)
[Livy](#livy)
[Nemo](#nemo)
[Pony Mail](#ponymail)
[ResilientDB](#resilientdb)
[Uniffle](#uniffle)
[Wayang](#wayang)
--------------------
## Answer
A Q-and-A platform software for teams at any scale.
Answer has been incubating since 2023-10-09.
### Three most important unfinished issues to address before graduating:
1. Release more ASF-compliant versions.
2. Build and grow a diverse community, attracting more committers and PPMC
members.
### Are there any issues that the IPMC or ASF Board need to be aware of?
Currently no
### How has the community developed since the last report?
- 6 new contributors have joined the community (48 in total).
- We have launched the contributors' documentation on our official website
and will keep it regularly updated, aiming to guide users in quickly
getting involved with contributions.
https://answer.apache.org/community/contributing
- We have preliminarily set out our community event plan for 2024, which
includes participating in events such as GSoC and OSPP to increase external
contributions, as well as organizing cross-community events in Q1 and Q4 to
motivate external developers to contribute.
- We plan to initiate open bi-weekly community meetings after the Chinese
Lunar New Year in 2024, to which we will invite all external contributors
and anyone interested in the development of the Answer community.
### How has the project developed since the last report?
- The first ASF-compliant version (v1.2.0) was released.
- 1 new feature, 7 bug fixes, 2 improvements.
- answer.dev has been redirected to answer.apache.org
### 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:
29 Nov, 2023
### When were the last committers or PPMC members elected?
It was in October since Apache Answer was accepted into the Apache
Incubator.
### Have your mentors been helpful and responsive?
Yes, all the mentors are helpful and responsive.
### Is the PPMC managing the podling's brand / trademarks?
There are no known brand and naming issues.
### Signed-off-by:
- [ ] (answer) Willem Ning Jiang
Comments:
- [ ] (answer) tison
Comments:
- [ ] (answer) Justin Mclean
Comments:
- [ ] (answer) Christofer Dutz
Comments:
### IPMC/Shepherd notes:
--------------------
## 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?
We acknowledge that we need to make progress on community building and will
try to focus on this aspect in 2024.
### How has the community developed since the last report?
We had a few external contributions to the project, but no new committer
joined the community. Most notably, Joe Polastre, from FlightAware, the
world's largest flight tracking and data platform, created a fast tile
exporter for Baremaps written in Go [1]. Some of his ideas have already
been contributed back to the project. We also started interesting
discussions with the Apache SIS community regarding spatial data codecs [2].
[1] https://github.com/flightaware/baremaps-exporter
[2] https://github.com/apache/incubator-baremaps/discussions/805
### How has the project developed since the last report?
- We addressed many of the podling requirements for the latest release.
- We also added support for PMTiles, 3D building extrusion, and
minutely/hourly/daily diffs from OpenStreetMap.
### 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-11-20
### 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 in addressing
issues that appeared during the last release.
### 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: Podling is going well. The discussions with SIS are
encouraging.
- [ ] (baremaps) Calvin Kirs
Comments:
- [ ] (baremaps) George Percivall
Comments:
- [ ] (baremaps) Martin Desruisseaux
Comments:
### IPMC/Shepherd notes:
--------------------
## Livy
Livy is web service that exposes a REST interface for managing long running
Apache Spark contexts in your cluster. With Livy, new applications can be
built on top of Apache Spark that require fine grained interaction with
many Spark contexts.
Livy has been incubating since 2017-06-05.
### Three most important unfinished issues to address before graduating:
1. Revitalization of the Community
2. Dependable Release Cadence
3. Focus on Contributors rather than primarily on Users (Docs for
processes)
### 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?
New PPMC, committers and contributors have emerged through the 0.8.0
release effort.
Focus on security fixes and CI processes in github as well as reviews and
merges of contributions from other contributors have been most active.
0.8.0 Release was security and bug fix oriented with CVEs and log4j being
a lot of the recent work but with meaningful features as well.
### How has the project developed since the last report?
Apache Livy 0.8.0 was released and addressed the previously stated goals
of security and log4j related fixes as well as numerous improvements and
features from the community that were long awaited due to lack of community
and recently added.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [X] Initial setup
- [X] Working towards first release (with revitalized community)
- [X] Community building
- [ ] Nearing graduation
- [X] Other: Nearing graduation in code stability but with a re-emerging
a dev community supporting it and working toward 0.8.0 release
### Date of last release:
2023-10-10
### When were the last committers or PPMC members elected?
October 2023
### Have your mentors been helpful and responsive?
No issues with mentors to report.
### Is the PPMC managing the podling's brand / trademarks?
No issues to report.
Signed-off-by:
- [ ] (livy) Bikas Saha
Comments:
- [ ] (livy) Luciano Resende
Comments:
- [X] (livy) Jean-Baptiste Onofré
Comments: The activity has restarted, mostly maintenance. I think we
can have new features and improvements soon, helping to extend the
community.
- [ ] (livy) Madhawa Kasun Gunasekara
Comments:
- [X] (livy) Larry McCay
Comments:
- [ ] (livy) Sunil Govindan
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?
This is a project initiated from academia, and the major problem here is
that many of us have graduated and moved on to something else now. Although
the project itself is very promising and is a well-developed system (proved
by a number of academic papers), the project is losing a bit of its
momentum, and there isn't a clear breakpoint where this can get itself back
on track in building its community and users. This project, I personally
think, is an unlucky one in the sense that Covid-19 hit at the time when it
was actively being promoted in ASF conferences and so, trying to build its
user base, and hasn't been able to climb up to TLP since then. I think that
there are enough resources for users to pick up on where it stands at the
moment, but it is unclear on how it should get back on track, where the
lack of community action being the major problem on its way to TLP. Any
suggestions or help would be nice, but we may also consider archiving the
project as well at this point.
### How has the community developed since the last report?
We have 1 new contributor.
### How has the project developed since the last report?
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?
Please refer to the issue raised above.
### 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:
--------------------
## PonyMail
Pony Mail is a mail-archiving, archive viewing, and interaction service,
that can be integrated with many email platforms.
Pony Mail has been incubating since 2016-05-27.
### Three most important unfinished issues to address before graduating:
1. Growing the community, in particular the user interactions
2. Growing the co....
3. Gro....
### Are there any issues that the IPMC or ASF Board need to be aware of?
None of note
### How has the community developed since the last report?
No material development since last report.
### How has the project developed since the last report?
No new developments. Stalled by lack of user engagement.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [X] Initial setup
- [X] Working towards first release
- [X] Community building
- [X] Nearing graduation
- [ ] Other:
### Date of last release: 2019-04-20
### When were the last committers or PPMC members elected?
Sean Palmer was elected committer on 2021-04-02
### Have your mentors been helpful and responsive?
No mentor engagement this quarter, though it has been very quiet, so no
need.
### Is the PPMC managing the podling's brand / trademarks?
No issues here.
### Signed-off-by:
- [ ] (ponymail) John D. Ament
Comments:
### IPMC/Shepherd notes:
--------------------
## ResilientDB
ResilientDB is a distributed blockchain framework that is open-source,
lightweight,
modular, and highly performant.
ResilientDB has been incubating since 2023-10-21.
### Three most important unfinished issues to address before graduating:
1. Transfer the codebase to
[Apache](https://issues.apache.org/jira/browse/INFRA-25211)
2. Grow the community by facilitating more applications being built on
ResDB
3. Improve and extend documentation
### Are there any issues that the IPMC or ASF Board need to be aware of?
The current codebase is still in GitHub and we have a few repositories
rather than
only one. We need some help to transfer these repositories to Apache.
### How has the community developed since the last report?
Our community channels on Discord are active and many users are asking
questions on
how to develop their applications based on ResilientDB. We have a live
testnet of
ResilientDB been operational on 5 replicas/replicas for the past two months
([ResDB explorer](https://explorer.resilientdb.com/)) utilized by over 100
students at both grad/undergrad levels.
There have been exciting new projects developed over ResDB. We are
expecting to
launch/showcase these projects in the coming weeks (e.g.,
[Debitable](https://debitable.resilientdb.com/)).
### How has the project developed since the last report?
The project is being processed on transferring.
We also addressed the feedback from the users and improved our service.
We had a new release last week (v1.9) that provided multi-version retrieval
functionality to allow fetching the history of each key.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [X] Initial setup
- [ ] Working towards first release
- [X] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
2023-11-29
### When were the last committers or PPMC members elected?
November of 2023
### Have your mentors been helpful and responsive?
The mentors helped tremendously throughout the project build-up and
transfer.
### Is the PPMC managing the podling's brand / trademarks?
There are no known brand and naming issues as reported
[here:](https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-215)
### Signed-off-by:
- [ ] (resilientdb) Junping Du
Comments:
- [X] (resilientdb) Calvin Kirs
Comments:
- [ ] (resilientdb) Kevin Ratnasekera
Comments:
- [ ] (resilientdb) Roman Shaposhnik
Comments:
- [X] (resilientdb) Christian Grobmeier
Comments:
### IPMC/Shepherd notes:
--------------------
## 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. Regular meeting continues every two weeks.
2. We're preparing a new post in our website.
3. 6 new contributors
### How has the project developed since the last report?
1. We released 0.8.0.
2. We have finished many exciting features such as the support of
dashboard, dynamic allocation, etc.
3. 106 pull requests are created, 91 pull requests are merged.
4. 75 issues are created, 61 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-12-13, we released 0.8.0 version
### When were the last committers or PPMC members elected?
Chenyu Zheng, elected as the committer on 2023.11.04
Junfan Zhang, elected as the PPMC on 2023.06.25
### Have your mentors been helpful and responsive?
Yes, they'are helpful in guiding the podding project.
### Is the PPMC managing the podling's brand / trademarks?
Yes.
### Signed-off-by:
- [ ] (uniffle) Felix Cheung
Comments:
- [ ] (uniffle) Junping Du
Comments:
- [ ] (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. Growing community
2. New website (in progress)
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?
Community has been growing. We received commits from multiple individuals
and organizations. Also we have a new PPMC member.
### How has the project developed since the last report?
We released Wayang 0.7.1. Next release 1.0.0 will have significant
additions and code base restructuring.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [ ] Working towards first release
- [ ] Community building
- [X] Nearing graduation
- [ ] Other:
### Date of last release:
2023-09-03
### When were the last committers or PPMC members elected?
2023-06-05
### Have your mentors been helpful and responsive?
Yes, no problems.
### Is the PPMC managing the podling's brand / trademarks?
Yes, no issues 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
Issues for the board: no
## Membership Data:
Apache IoTDB was founded 2020-09-16 (3 years ago)
There are currently 61 committers and 29 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
Community changes, past quarter:
- Steve Yurong Su was added to the PMC on 2023-09-28
- Xinyu Tan was added to the PMC on 2023-09-28
- No new committers. Last addition was Sicheng Yu on 2023-08-01.
## Project Activity:
This quotar IoTDB community mainly focus on system performance and stability.
Release:
IOTDB-1.2.2 was released on 2023-10-15.
IOTDB-1.2.1 was released on 2023-09-19.
IOTDB-1.2.0 was released on 2023-09-08.
And, we are releasing v1.3.0.
New project:
IoTDB Community desides to seperate the TsFile from IoTDB to Apache
as a top-level-project.
TsFile is a columnar storage file format designed for time series data,
which supports efficient compression, high throughput of read and write,
and compatibility with various frameworks, such as Spark and Flink.
It is easy to integrate TsFile into IoT big data processing frameworks.
## Community Health:
We hold an IoTDB Summit 2023 in Beijing on 2023-12-03,
nearly 300 people attended on-site and there are about 70k watch online.
dev@ traffic needs PMC's attention in the next season.
-----------------------------------------
Attachment AN: Report from the Apache Jackrabbit Project [Marcel Reutegger]
-----------------------------------------
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:
There are no issues requiring board attention.
## Membership Data:
Apache Karaf was founded 2010-06-16 (14 years ago)
There are currently 32 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.
- Robert Varga was added as committer on 2023-10-31
## Project Activity:
We released:
- Karaf runtime 4.3.10 was released on 2023-09-20.
- Karaf runtime 4.4.4 was released on 2023-09-17.
We are now preparing Karaf runtime 4.4.5 including
fixes on top of 4.4.4. This release is expected between Christmas and New
Year. We are also preparing Karaf runtime 4.5.0 which will be a main milestone
with Jakarta namespace support. We plan this release in January 2024. This
release requires updates/activities on other projects (Aries, etc).
## Community Health:
The karaf-integration distribution is planned for Karaf 4.5.0 (see KARAF-7792
- Provide karaf-integration distribution OPEN ). The Karaf community started
to help on camel-karaf, restarting this project to support Camel 4.x in Karaf
(as requested by users). 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: Ongoing Issues for the board: none
## Membership Data:
Apache Kvrocks was founded 2023-06-21 (6 months 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 Alfejik Liu on 2023-06-21.
- Shixi Yang was added as committer on 2023-12-06
## Project Activity:
The last release of Apache Kvrocks 2.6.0 was on 2023-09-26, and the 2.7.0
release vote is planned to be sent in the middle of December. During the last
quarter, we mainly focused on implementing the new data structure JSON and now
is close to done. In addition, some of the user-heavy-request features like
the namespace replication will also be introduced in 2.7.0, guess they will
make many users happy since then.
At the same time, the community also donated kvrocks-controller as a
subproject of Kvrocks, which will make the cluster mode easier to use and
maintain.
## Community Health:
Overall community health is good. The total number of contributors is more
than 100 now, it's a small milestone for the community.
The development traffic decreased greatly(-43%) in the last quarter. The main
reason is we have many bug fixes in release 2.6.0, which held up the count of
contributions and contributors. The number of bug reports has been back to
normal since then, so I think it's fine.
-----------------------------------------
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 with moderate activity.
57 contributors committed 511 patches
Issues for the board: none
## Membership Data:
Apache Kyuubi was founded 2022-12-21 (a year 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:
- Bowen Liang was added to the PMC on 2023-10-30
- Zhen Wang was added to the PMC on 2023-11-07
- Binjie Yang was added as committer on 2023-10-11
- Bogdan Kyryliuk was added as committer on 2023-11-14
## Project Activity:
Software development activity:
- We released the bug fix release 1.7.2 for Apache Kyuubi on 2023 Sep 18.
- We released the bug fix release 1.7.3 for Apache Kyuubi on 2023 Sep 25.
- We released the minor release 1.8.0 for Apache Kyuubi on 2023 Nov 7.
- We released the minor release 0.2.0 for Apache Kyuubi Shaded on 2023 Dec 7.
- We accepted the donation of PyHive project and the IP Clearance is ongoing.
- We have add authoriazation support for Apache Hudi, Apache Iceberg, Deta Lake
. Supporting for others, like Apache Paimon(Incubating) is ongoing.
Meetups and Conferences:
- 2023-10-13(Shanghai), 2 PMC members went to Bilibili to have a discussion
with the users
- 2023-10-18(Hangzhou), A Kyuubi & Celeborn meetup held both online and offline
- 2023-10-28(Hangzhou), A Kyuubi & Spark meetup held both online and offline
- 2023 Kyuubi Code Contribution Program
- 2023/10/10 18:00 GMT+8 to 2023/12/08 18:00 GMT+8
- https://github.com/apache/kyuubi/issues/5357
## Community Health:
1. Due to the 2023 Kyuubi Code Contribution Program, we have observed
an increase in community activities and new contributors. The program
will be scheduled semi-annually.
-----------------------------------------
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 (a year ago)
There are currently 37 committers and 25 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:4.
Community changes, past quarter:
- Fei Guo was added to the PMC on 2023-11-02
- Jie Cheng was added as committer on 2023-10-05
- GuoHua Liu was added as committer on 2023-12-06
## Project Activity:
Apache Linkis released version 1.4.0 on August 6th. This version involved
more than 26 contributors, including 10 new contributors (currently: 154),
and contained over 34 new features. Apache Linkis 1.5.0 are currently
under integration testing.
Software development activity:
We released 1.4.0 four months ago.At this time,
We are preparing to release 1.5.0 in the coming month.
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.
- The data source module supports data source SQL generation and supports more
data sources with the Spark ETL function.
- Monitor service added.
- Add task positioning troubleshooting script.
- Support user engine template parameter support.
Meetups and Conferences:
- Community meeting(1) to discuss development progress and how to build
an actively governance community.
## Community Health:
Overall community health is good.
- 75 PRs closed on GitHub, past quarter.
- 81 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 67 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:5.
Community changes, past quarter:
- Luca Cavanna was added to the PMC on 2023-10-19
- Guo Feng was added to the PMC on 2023-10-23
- Patrick Zhai was added to the PMC on 2023-11-09
- No new committers. Last addition was Ben Trent on 2023-01-27.
## Project Activity:
9.8 was released on 2023-09-28
- Release notes are available at:
https://lucene.apache.org/core/9_8_0/changes/Changes.html
- Some highlights released with 9.8 include:
-- Performance optimizations: 20-30% speedup for boolean query disjunctions and
11-13% speedup for conjunctions for "top-k" searches; 7-33% speedup for
field-sorted searches (as compared to 9.7 using luceneutil benchmarks); lazy
evaluation improvements to expression-based doc-value computations; added
support for recursive graph bisection, an algorithm for reordering docIDs that
results in more compact postings and faster queries
-- New LeafCollector#finish API introduced to make post-collection logic simpler
and more idiomatic for users that need custom collection behavior
9.9 was released on 2023-12-04
- Release notes are available at:
https://lucene.apache.org/core/9_9_0/changes/Changes.html
- Some highlights released with 9.9 include:
-- Added int8 scalar quantization to the HNSW vector format to optionally allow
a more compact, lossy format for vectors, requiring ~4x less memory for fast
HNSW search
-- Multi-threaded HNSW graph merging enabled
-- FSTCompiler can now approximately limit how much RAM it uses to share
suffixes during FST construction
-- Lucene99PostingsFormat introduced that uses an un-patched version of
FOR for query-time performance improvements
- NOTE: A serious bug was discovered in 9.9 post-release,
causing read corruption in some cases when attempting to read terms
dictionaries created with 9.8 versions of Lucene. A fix is in progress
and a 9.9.1 release with the fix is planned as soon as it is ready.
## Community Health:
Community interactions remain healthy, with a general increase in activity in
all areas (discussions, PRs, etc.).
- dev@ mailing list traffic increased by 176% compared to last quarter
(426 emails compared to 154). There were no particularly "hot topics," but
rather a healthy amount of discussion on a breadth of subjects (and welcoming
our newest PMC members!)
- Development has remained active with significantly increased volume compared
to last quarter:
-- 277 commits (+360% compared to last quarter)
-- 251 PRs opened (+386% compared to last quarter)
-- 245 26 PRs closed (+942% compared to last quarter)
- Some of this is likely the result of increased activity after a relatively
quieter summer period, but there's been a healthy surge of activity from new
contributor engagement as well.
- 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]
-----------------------------------------
Attachment AU: Report from the Apache Mnemonic Project [Gordon King]
-----------------------------------------
Attachment AV: 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:
Community work in several areas including:
improved GUI support (LVGL), CI improvements, new MCUs
support (STM32G4) and continued work on Bluetooth LE Audio.
## Community Health:
Number of contributors is stable, "core" developers are contributing code on
regular basis. We see more support request from new users.
Mailing list see little activity as most discussions happen on Slack and Github.
-----------------------------------------
Attachment AW: Report from the Apache NetBeans Project [Geertjan Wielenga]
-----------------------------------------
Attachment AX: 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:
* two new releases have been published since our last report:
** 18.12.09 was released on 2023-11-05
** 18.12.10 was released on 2023-12-04
* with the two releases two security vulnerabilities have been disclosed and
fixed: CVE-2023-46819 and CVE-2023-49070
* trademarks: there are no trademark related concerns at the moment; as
regards the ofbiz.info domain (Christofer Dutz posted a question about it
through the agenda tool), considering that it is currently free, the PMC is
inclined to leave it as is rather than asking the ASF to register it
## Community Health:
Community activity over the last quarter has been on average with various
topics discussed both in the users and the dev list. One interesting topic
that the community is discussing is about the stabilization branches: whether
a new one will be created from trunk (e.g. 24.01) or not (keeping the
existing, 22.01).
No new committers or PMC members have been invited during
the last quarter but we are in the process of voting for new PMC members: if
everything goes well, they will be announced soon.
-----------------------------------------
Attachment AY: Report from the Apache Olingo Project [Michael Bolz]
## Description:
The Apache Olingo Project is responsible for the creation and
maintenance of software related to providing an implementation of the
OASIS OData (Open Data Protocol) specifications, in server and client form;
## 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 (10 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.13 was released on 2023-10-22.
- 4.10.0 was released on 2023-10-22.
For both versions a feature release is planned by end of 2023.
For V4 it will be version 5.0.0 and it is on track.
For V2 it will be version 3.0.0 and it is delayed.
## Community Health:
Overall community health is okay.
Activity on the mailing lists increased in the last quarter.
Some new JIRA items and new PRs got opened.
Several JIRA items and PRs could be closed,
resulting in 50 commits (big increase) by 7 contributors.
Roadmap for feature release was discussed and decided, resulting
in feature release for both, V2 and V4, which are in progress/planned.
-----------------------------------------
Attachment AZ: 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:
- No new PMC members. Last addition was Martin Wiesner on 2023-06-24.
- No new committers. Last addition was Atita Arora on 2023-02-28.
## Project Activity:
The project released version 2.3.1 on November 22, 2023. This was largely a
maintenance release and to support an effort in Apache Solr. OpenNLP was
represented at Community over Code.
## Community Health:
The project has had contributions from a few new contributors this quarter
which is very exciting. The community is healthy. We are very happy to have
had Martin Wiesner be the release manager for the first time for the 2.3.1
release.
-----------------------------------------
Attachment BA: Report from the Apache OpenWebBeans Project [Mark Struberg]
-----------------------------------------
Attachment BB: Report from the Apache Pig Project [Koji Noguchi]
-----------------------------------------
Attachment BC: Report from the Apache Pivot Project [Roger Lee Whitcomb]
-----------------------------------------
Attachment BD: 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 moderate activity
Issues for the board: none
## Membership Data:
Apache PLC4X was founded 2019-04-17 (5 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 most noteworthy points for the last 3 months were definitely:
- Our last release after exactly one year (didn't copy+paste that)
- Work on the Profinet Driver
- Initiation of a new Web-Based UI tool
- Major updates in the S7 driver (datatype-handling)
- Major updates in the handling of secure OPC-UA connections
- Work on PLC4PY which now has a first working Modbus driver
- Refactored the way transports are configured
- Prepared the build for reproducible builds
- Multiple Bugfixes
Recent releases:
0.11.0 was released on 2023-10-06.
0.10.0 was released on 2022-10-06.
0.9.1 was released on 2021-09-21.
## Community Health:
While I was a bit worried about activity inside the project in my last
reports, things are looking a bit different now. There's currently plenty
activity on various initiatives.
Following the last release we received a number of new bug-reports and fixes
by new folks. We're definitely not going to wait another year for a new
release.
-----------------------------------------
Attachment BE: 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:
Latest apr-1.7.4 was released on 2023-04-16 and apr-util-1.6.3 on 2023-02-01.
The quarter was quiet, nothing unusual.
Usual commits/PRs to keep up with new compilers (warnings) and API
changes for the dependencies.
After some discussions about the lack of thread-safety for some legacy and
lightweight DB drivers, it was decided to not address this inside the APR
but let users select a safe driver or provide their own locking. A new
thread-safe/lightweight DB driver was contributed and committed to provide
a native/builtin alternative still.
## Community Health:
The project remains healthy, though quiet.
Low activity on the dev@ mailing list and bugzilla/github.
-----------------------------------------
Attachment BF: 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. Issues under consideration at this point largely (if not
entirely) consist of 3rd party security vulnerabilities that need to be fixed
by updating dependencies.
Issues for the board: None 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:
The "[VOTE]" email for the release Apache Portals Pluto 3.1.2 was sent earlier
this week. Provided that enough +1 votes are received, the release will be
published during the week of December 18, 2023.
As indicated by the release notes, version 3.1.2 largely contains upgrades of
3rd party dependencies:
https://issues.apache.org/jira/projects/PLUTO/versions/12351085
## 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 BG: Report from the Apache Pulsar Project [Matteo Merli]
## Description:
Pulsar is a highly scalable, low latency messaging platform running on
commodity hardware. It provides simple pub-sub semantics over topics,
guaranteed at-least-once delivery of messages, automatic cursor management for
subscribers, and cross-datacenter replication.
## Project Status:
- There are no issues requiring board attention at this time.
- Responses to the feedback questions:
1. Could you please explain what this pulsar-private repo is all
about? We wanted to have a look, but don't seem to have
access to it.
The repository was created in order for PMC member to review changes
to address security fixes for Pulsar. In general there is a private
discussion that can end up in creating a CVE. In the same way, we
want to make sure we have a fix reviewed and ready to be released
by the time the CVE is published. The repository itself is just a
copy of Pulsar repo, all the PMC members do have access and can
create pull-request for private reviews.
2. You say both that you invited 8 new committers
and that there are no new committers. Can you clarify?
The 8 committers number was a mistake. I carried over the number from
the precedent quarter.
## Project Activity:
- 3.0.2 was released on December 7th 2023
- 3.1.1 was released on October 28th 2023
- 2.11.2 was released on July 18th 2023
- Pulsar C++ releases:
- 3.4.2 on Dec 12th 2023
- Pulsar Python releases:
- 3.3.0 was released on August 29th 2023
- Pulsar Go releases:
- 0.11.1 was released on November 7th 2023
- Pulsar reactive client:
- 0.5.1 was released on December 16th 2023
- Pulsar NodeJS client:
- 1.9.0 was released on July 10th 2023
- We continue to have a very high number of "Pulsar Improvement
Proposal" getting submitted, discussed and voted by the
community:
PIP-276: Add metric `pulsar_topic_load_times`
PIP-275: Introduce topicOrderedExecutorThreadNum to deprecate
numWorkerThreadsForNonPersistentTopic in configuration
PIP-278: Support pluggable topic compaction service
PIP-280: Refactor CLI for measurement units (time and byte)
PIP-279: Reformat property in generateResponseWithEntry
PIP-281: Add notifyError method on PushSource
PIP 289: Secure Pulsar Connector Configuration
PIP-293: Delete config `disableBrokerInterceptors`
PIP-290: Provide a way to implement WSS E2E encryption and not need to
expose the private key to the WebSocket Proxy
PIP-264: Enhanced OTel-based metric system
PIP-297: Support terminating Function & Connector with the fatal exception
PIP-277: Add `current` option in the Clusters list cmd
PIP-301: Introduce LoadBalanceResources to unify the load-date CRUD
PIP-286: Make the TopicCompactionService to support find entry based
on publishTime or index
PIP-299: Stop dispatch messages if the individual acks will be lostin the
persistent storage
PIP-307: Optimize Bundle Unload(Transfer) Protocol for ExtensibleLoadManager
PIP-302: Introduce refreshAsync API for TableView
PIP-298: Consumer supports specifying consumption isolation level
PIP-307: Support subscribing multi topics for WebSocket
PIP-305: Customize DNS servers to use for Pulsar Client
PIP-300: Add custom dynamic configuration for plugins
PIP-318: Don't retain null-key messages during topic compaction
PIP-312: Use StateStoreProvider to manage state in Pulsar Functions
endpoints
PIP-303: Add optional parameters for getPartitionedStats
PIP-315: Configurable max delay limit for delayed delivery
PIP-320: OpenTelemetry Scaffolding
PIP-300: Add custom dynamic configuration for plugins
PIP-322: Pulsar Rate Limiting Refactoring
PIP-313: Support force unsubscribe using consumer api
- Pulsar has reached 639 contributors on the main Github repo
(It was 623 contributors in June 2023)
## Health report:
- There is healthy growth in the community, and several users are starting
to become contributors to the project and engage more and more with
the community. In this quarter, 8 contributors were invited as
committers to the project.
## Membership Data:
Apache Pulsar was founded 2018-09-18 (5 years ago)
There are currently 80 committers and 40 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
Community changes, past quarter:
* Daniel Blankensteiner was added to the PMC on 2023-11-19
* Yubiao Feng was added to the PMC on 2023-11-07
* David Jensen was added as committer on 2023-11-22
* Yan Zhao was added as committer on 2023-11-06
* Chris Bono was added as committer on 2023-11-18
* Vineeth Polamreddy was added as committer on 2023-10-09
## Community Health:
- Activity on the mailing lists remains high with a mixture of new users,
contributors, and deeper, more experienced users and contributors sparking
discussion and questions and filing bugs or new features.
- users@pulsar.apache.org:
- 44% decrease in traffic in the past quarter (17 emails compared to 30)
- dev@pulsar.apache.org:
- 3% decrease in traffic in the past quarter (613 emails compared to 627)
## Slack activity:
- 10071 Members (9807 in June 2023)
- 143 Active weekly users (212 in June 2023)
## GitHub activity:
- 741 commits in the past quarter (-40% decrease)
- 90 code contributors in the past quarter (-34% change)
- 451 PRs opened on GitHub, past quarter (-25% change)
- 428 PRs closed on GitHub, past quarter (-24% change)
- 174 issues opened on GitHub, past quarter (-24% change)
- 95 issues closed on GitHub, past quarter (-55% change)
-----------------------------------------
Attachment BH: 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 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 Sailaja Polavarapu on 2019-09-18.
- Last addition to Committer was Dineshkumar Yadav on 2023-02-06.
- One PMC member has resigned (Colm O hEigeartaigh) on 2023-10-10.
## Project Activity:
- Working on ranger 3.0.0 version features and bugfixes (886 resolved jira(s)
includes 448 bugfixes).
- new UI developed in react framework is made as the default
- docker setup updates to support validation of earlier version plugins with
later version of Ranger server
- security-zone updates to support roles for admin and auditor privileges
- Updated ranger website with new blogs and updated team member information.
- Will be working on moving the ranger doc content from SVN based to GIT repo
- Will be planning to do the release of 3.0.0
## Community Health:
- 1472 emails in dev@ranger.apache.org in this quarter
(+46% change from past quarter)
- 7 emails in user@ranger.apache.org in this quarter
(+ 0% change from past quarter)
- 165 issues opened in JIRA in this quarter
(+28% change from past quarter)
- 121 issues closed in JIRA in this quarter
(+45% change from past quarter)
- 137 commits in this quarter
(+53% change from past quarter)
- 22 code contributors in this quarter
(- 4% change from past quarter)
- 8 PRs opened on GitHub in this quarter
(-46% change from past quarter)
- 5 PRs closed on GitHub in this quarter
(-37% 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 BI: Report from the Apache Royale Project [Yishay Weiss]
## Description:
The mission of Apache Royale is the creation and maintenance of software
related to improving developer productivity in creating applications for
wherever JavaScript runs (and other runtimes)
## Project Status:
Current project status: Ongoing. Issues for the board: in response to concerns
raised previously by board members, we now have 2 VM instances dedicated to
release and CI. We have an additional VM subscription which has not yet been
set up for release/CI purposes. Recent releases have been done by the same PMC
member; we are hoping the next release will be performed by a different
member.
## Membership Data:
Apache Royale was founded 2017-09-20 (6 years ago)
There are currently 20 committers and 16 PMC members in this project.
The Committer-to-PMC ratio is 5:4.
Community changes, past quarter:
- 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.
## Project Activity:
Various bug fixes and improvements to asjs and compiler repos. ASFormatter
improved and rolled into dev process of users.
## Community Health:
We are seeing a rise in dev posts and a decrease in user posts. This is likely
due to a combination of 2 factors: (a) many of the more active users are
project developers as well, and (b) there is a typically shorter response time
to issues posted on the dev list, which leads users to post there. This might
imply that we need to expand our 'layman' user base and dispel the notion that
Royale users are implicitly 'experts'.
-----------------------------------------
Attachment BJ: Report from the Apache SeaTunnel Project [Jun Gao]
-----------------------------------------
Attachment BK: 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:
No issue requiring board attention.
## Membership Data:
Apache ServiceMix was founded 2007-09-19 (16 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:
Recent Releases:
- bundles-2023.08
- bundles-2023.09
We are now preparing bundles-2023.11/12 release.
## Community Health:
Still in maintenance mode. The karaf-integration distribution should
be provided by the Karaf community soon as an alternative to SMX
distribution. It's planned for Karaf 4.5.0.
The ServiceMix community also restarted the work on camel-karaf to
support camel 4.x.
-----------------------------------------
Attachment BL: 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-4 was released on 2023-11-07
- 1.13.0 was released on 2023-11-03
## Community Health:
Shiro's activity dipped a little this quarter, with most of the
development going into maintenance releases.
-----------------------------------------
Attachment BM: 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: Dormant
Issues for the board: N.A
## Membership Data:
Apache SINGA was founded 2019-10-16 (4 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.1.0 on 05 November 2023.
The release note is at
https://github.com/apache/singa/blob/master/RELEASE_NOTES
The main features of this release include
1. Add new examples including malaria detection and structured data
learning.
2. Add support for in-database model definition and selection in RDBMS.
3. Enhance example code by adding support for flexible setting of training
configurations and adding implementations for dynamic models.
4. Enhance the online documentation for database integration.
5. Promote code quality.
6. Fix bugs in the Dockerfile and the wheel file.
Apart from this release, the community has been working on:
1. Adding horizontal federated learning examples.
2. Adding support for models running on top of more PostgreSQL variants.
## Community Health:
According to the statistics, there are increase of email traffic, Commits and
GitHub PR activities, which indicates that the community is active in the
development.
-----------------------------------------
Attachment BN: Report from the Apache Sling Project [Robert Munteanu]
-----------------------------------------
Attachment BO: Report from the Apache Solr Project [David Smiley]
## Description:
The mission of Apache Solr is the creation and maintenance of software related
to highly scalable distributed document search and analytics
## Project Status:
Current project status: Ongoing with moderate activity.
Issues for the board: none.
## Membership Data:
Apache Solr was founded 2021-02-16 (3 years ago) after 15 years as a Lucene
sub project.
There are currently 95 committers and 61 PMC members in this project.
Many are inherited from the Lucene project split.
The Committer-to-PMC ratio is roughly 3:2.
Community changes, past quarter:
- No new PMC members. Last addition was Michael Gibney on 2022-12-20.
- No new committers. Last addition was Alex Deparvu on 2023-08-02.
## Project Activity:
Recent releases:
* solr-operator-v0.8.0 was released on 2023-10-20.
* 9.4.0 was released on 2023-10-15.
Areas of development & interest:
* Builds: Embracing Gradle Enterprise. Improving Crave builds.
* API: Continued progress on our revamped "V2" API with JAX-RS & OpenAPI
* Upcoming releases: 9.4.1 mostly to address a JSON Query bug,
and 8.11.3 just for CVEs
* Tracing improvements, like the switch to OTel.
* CircuitBreaker improvements
* The k8s Solr Operator
* Cross-DC in the sandbox
* ... there are always more ...
Security:
We are finally addressing a backlog of security vulnerability threads;
most of which are being granted CVEs (5) and are actively being pursued. I'd
like to thank Houston Putman in particular, and the support from the ASF by
Arnout Engels. We still want to develop/refine a Solr "security model"
to clarify expectations of users around securing Solr, and assumptions that
might invalidate proposed vulnerabilities.
Project branding & social media:
There is a Twitter/X.com account "ApacheSolr" that was the subject of internal
debate. The PMC now considers it as its own, not the PMC member who created it.
I set up "Delegate" access to other PMC members for shared use. Also debated
improper use / favoritism of promoting a single vendor. We would like to
diversify this but have yet to solicit / notify other vendors.
## Community Health:
* Virtual meetups: We continue to have monthly online meetups open to the
public, which have been a key element of Solr's health.
* Newsletter: This is a key initiative but it has stalled at the moment.
* Conference: Community over Code participation. About a dozen Solr community
members gathered; several presentations featured Solr. Included a useful
all-day Hackathon for free-form gathering & discussion.
* Forum software: Considering switching the users mailing list to Discourse
or GitHub Discussions; TBD.
Some numbers:
* lists: dev & users lists have major increases; to be expected because the
summer is always low
* issues opened / PRs, & commits — down maybe 10% ish. I’m a bit surprised.
* unique contributors: 17% increase
-----------------------------------------
Attachment BP: Report from the Apache SpamAssassin Project [Sidney Markowitz]
Apache SpamAssassin report to Board for December 2023
## 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 of a bug fix release 4.0.1 is in progress.
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 BQ: 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)
Issues for the board: None
## Membership Data:
Apache Storm was founded 2014-09-17 (9 years ago)
There are currently 47 committers and 46 PMC members in this project.
The Committer-to-PMC ratio is roughly 1:1.
Community changes, past quarter:
- Rui Abreu was added to the PMC on 2023-09-13
- Nikhil Singh was added to the PMC on 2023-10-23
- Rui Abreu was added as committer on 2023-09-12
- Nikhil Singh was added as committer on 2023-10-23
## Project Activity:
Project activity has slowed in recent years. Storm is essentially in
maintenance mode.
We have upgraded many third party libraries to recent versions in order
to reduce technical debt. In addition, we added an additional CI step
in order to build Storm with Java 21, which succeeded. However, some
real world testing for a longer period of time needs to be done.
Luckily, we already received some feedback and it seems the newest
Storm release runs fine with Java 21.
In order to reduce maintainance burden, we completed our survey and
decided (on the basis of that feedback) to prune some of our
outdated and unmaintained external modules.
The new PMC / committership also actively started to review pull
requests on GitHub, which had been stale for a very long time. This
activity resulted in some code inclusions and bug fixes.
Moreover, we are able to release Apache Storm 2.6.0 including a fix for
a recent CVE. The vote only took one week, which is a good thing for
this project as the last release votes were pending for weeks.
Before the actual vote we shared some SNAPSHOT builds with the
community to gather some feedback on the recent dependency updates and
changes, which resulted in some additional fixes before we were finally
able to vote. We now provide such SNAPSHOT
builds via nightlies.apache.org (+ Nexus), so people can get a
chance to play with it while it is hot.
Recent releases:
2.6.0 was released on 2023-11-16.
## Community Health:
Community engagement is currently healthy but could benefit from new
contributors or users. We are currently onboarding our new PMC members
(some of them never contributed to an ASF project before) to teach them
the Apache way and to make them active contributors.
-----------------------------------------
Attachment BR: Report from the Apache Submarine Project [Kevin Su]
-----------------------------------------
Attachment BS: Report from the Apache Synapse Project [Isuru Udana]
-----------------------------------------
Attachment BT: 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-M15 was released on 2023-12-12.
- Apache Tomcat 11.0.0-M14 was released on 2023-11-15.
- Apache Tomcat 11.0.0-M13 was released on 2023-10-14.
- Apache Tomcat 10.1.17 was released on 2023-12-12.
- Apache Tomcat 10.1.14 was released on 2023-10-10.
- Apache Tomcat 9.0.84 was released on 2023-12-12.
- Apache Tomcat 9.0.82 was released on 2023-10-13.
- Apache Tomcat 9.0.81 was released on 2023-10-10.
- Apache Tomcat 8.5.97 was released on 2023-12-12.
- Apache Tomcat 8.5.94 was released on 2023-10-10.
## Community Health:
- Continued healthy activity across multiple components and
responsiveness on both dev and user lists.
- 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 BU: 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 remains low with approximately
23 commits to main since our previous report (9/17). We started a "Health of
this project -- should we keep going?" thread on our user list in attempt to
create more awareness of our need for more contributors. Three people
identified themselves as interested, but have not followed through in the
months since.
A thread "TomEE 10 in the pipe or not ?" was started by cross posting on both
the users list and dev lists asking for updates on the community's progress.
These kinds of posts do not give us hope that the project's need for more
resources and consequence of not having them is being understood.
## Activity
As mentioned above, activity has been low. The 20-ish commits to main in the
last quarter have largely been for library upgrades. One of those commits
did come a contibutor who is not a committer was a small tweak on existing
code, with roughly 9 lines added and 8 removed.
A release of Apache TomEE 8.0.x was created containing library upgrades to
address CVEs. This may be the last version of 8.0.x unless one is made before
the EOL date of December 31st.
Efforts to do a release of Apache TomEE 9.1.x are in progress, also
containing library upgrades. A second vote is up and likely to complete.
## 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:
- Apache TomEE 8.0.16 on November 11th, 2023
-----------------------------------------
Attachment BV: Report from the Apache TsFile Project [Jialin Qiao]
-----------------------------------------
Attachment BW: 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: none
## Membership Data:
Apache TVM was founded 2020-11-17 (3 years ago)
There are currently 72 committers and 28 PMC members in this project.
The Committer-to-PMC ratio is roughly 9:4.
Community changes, past quarter:
- Bohan Hou was added to the PMC on 2023-09-24
- Ruihang Lai was added to the PMC on 2023-09-27
- Qiang Zhang was added as committer on 2023-09-27
## Project Activity:
Recent releases:
- 0.14.0 was released on 2023-11-03.
- 0.13.0 was released on 2023-08-08.
The project continues to push the frontiers of machine learning compilation.
Some feature highlights include:
- Better dynamic shape support
- Enablement of genAI and LLM models.
We have observed major participation in the unity branch development due to
the overall shift of the ML community toward emerging foundational models. The
developers also continue to bring maintaiance to main and keep the branches in
sync.
## Community Health:
The field of machine learning is evolving very fast this year with the
arrivial of genAI and LLMs. They shape sthe overall interest of open source
machine learning ecosystem.
Being able to support genAI models timely is likely critical for the community
given the focus of the broader ML community we sypport. We continue to see
contributions to the projects with ~120 commits monthly from 40 authors. We
also observe that in the case of contributions, most new contributions now go
to the unity branch due to the heavy interest in genAI directions.
The community held conversations about core development strategy in the age of
genAI and had a broad consensus about bringing unity branch as main while
ensuring all the main modules remain supported and synced. Over the past
quarter, the community has continued to maintain and sync the unity branch to
make such a transition seamless while still giving some time for all community
members. We will likely see such a transition in the incoming
quarter, given the broad support from the community.
-----------------------------------------
Attachment BX: 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 (14 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:
- uimafit-3.5.0 was released on 2023-11-13.
- uimaj-3.5.0 was released on 2023-11-06.
## Community Health:
At present, there is little activity. Occasional user activity on the mailing
list / issue tracker, but not much overall.
-----------------------------------------
Attachment BY: 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
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:
The project was a bit quiet in this last period, but it did release two
versions in the previous period. Some preparation worked was needed in
external projects to be able to upgrade GraphQL and the GraphQL UI so that
should land soon. This will also help remove a lot of obsolete dependencies
that were being flagged by Github. Version 2 is maturing nicely and a lot of
work had gone into improving migration scenarios so less activity is also
explained by the fact that most current tasks are completed and the code has
matured nicely.
## Community Health:
The community traffic is pretty low, but this isn't any different from other
periods. Development is also a bit lower but still active. Here are the usual
stats:
- 13 issues opened in JIRA, past quarter (-38% change)
- 2 issues closed in JIRA, past quarter (-89% change)
- 5 commits in the past quarter (-91% change)
- 2 code contributors in the past quarter (-71% change)
- 2 PRs opened on GitHub, past quarter (-90% change)
- 1 PR closed on GitHub, past quarter (-94% change)
-----------------------------------------
Attachment BZ: 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: We have moved from dormant to ongoing with a little
activity.
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 have finally started making some progress toward a new release. A plan
was sent to the dev@ list with several things listed that should be included
in the next release. We also went through JIRA issues and updated relevant
ones to tag them with the next release number (2.6). A few of the JIRA
issues have had commits made to resolve them. All but one of the waiting
pull requests on GitHub have been handled (the one remaining is by someone
who is now a committer and PMC member and is unsure about incorporating it
now).
## Community Health:
The health of the community is improving. We've gone from being dormant with
no activity to having some traffic on our user and dev lists as well as having
some JIRA and commit activity.
-----------------------------------------
Attachment CA: Report from the Apache Velocity Project [Nathan Bubna]
-----------------------------------------
Attachment CB: 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 a good level of activity.
Issues for the board: none.
## 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:
During the last quarter we released two new versions for 9.x branch (versions
9.15.0 and 9.16.0) and a new milestone release for 10.x branch (version
10.0.0-M2). We had collected a good number of positive feedback about version
10.0.0-M2 so we decide to go ahead toward the official release for the new
main version 10.0.0. We just got in contact with press staff to start working
to the official statement for the new release.
## Community Health:
Contributions from our community has increased in the last quarter, with both
more PRs and more feedback. Just like our internal activity community
contributions were mainly focused on improving and fixing milestone version
10.0.0-M2 in order to make Wicket 10 GA.
-----------------------------------------
Attachment CC: Report from the Apache Xalan Project [Gary D. Gregory]
## Description:
Apache Xalan exists to promote the use of XSLT. We view XSLT (Extensible
Stylesheet Language Transformations) as a compelling paradigm that transforms
XML documents, thereby facilitating the exchange, transformation, and
presentation of knowledge. The ability to transform XML documents into usable
information has great potential to improve the functionality and use of
information systems. We intend to build freely available XSLT processing
components to engender such improvements.
## Project Status:
Current project status: Ongoing.
Issues for the board: None.
## Membership Data:
Apache Xalan was founded 2004-09-30 (19 years ago)
There are currently 57 committers and 5 PMC members in this project.
The Committer-to-PMC ratio is roughly 8:1.
Community changes, past quarter:
- No new PMC members. The last addition was Joseph Kessselman on 2023-08-07.
- No new committers. The last addition was Joseph Kessselman on 2023-06-29.
## Project Activity:
The Xalan-J project is active with a push toward releasing again, XSLT 3, and
switching from Ant to Maven. We are processing Jira tickets and PRs from
GitHub. The last recent release was Java-2.7.3 was released on 2023-04-01.
## Community Health:
Project activity has increased tremendously as can be seen on GitHub and
mailing lists. The PMC has gratefully welcomed back Joseph Kessselman, one of
our original contributors, back into the fold.
-----------------------------------------
Attachment CD: 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
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.15.0 was released on 2023-11-14.
Obviously this quarter was geared towards finishing up the 0.15.0 release. It
has been a "slow burn" for a while so it was good to finally get it out. This
release was also the first one with some signicant changes in our written
release process, so those had to be worked out as well.
## Community Health:
Given the project is near the bottom of the pecking order for our
contributors, Q4 is usually pretty quiet... unless a release is happening. The
community health metrics clearly demonstrate that--vote emails, release
process improvement issues filed, etc. With the release being in the middle of
the quarter, stats are a bit wacky this time since most of the core
development was done in previous quarters.
* dev@yetus.apache.org had a 200% increase in traffic in the past quarter (12
emails compared to 4)
* 9 issues opened in JIRA, past quarter (50% increase)
* 13 commits in the past quarter (-38% change)
-----------------------------------------
Attachment CE: Report from the Apache ZooKeeper Project [Flavio Paiva Junqueira]
------------------------------------------------------
End of minutes for the December 20, 2023 board meeting.
Index