Index
Links: 2023 - All years
- Original The Apache Software Foundation
Board of Directors Meeting Minutes
July 19, 2023
1. Call to order
The meeting was scheduled for 21:00 UTC and began at 21:03 when
a sufficient attendance to constitute a quorum was recognized by
the chair.
Other Time Zones: https://timeanddate.com/s/434x
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 - joined :12
Justin Mclean
Craig L Russell
Sander Striker
Directors Absent:
Sharan Foga
Executive Officers Present:
Matt Sicker
Executive Officers Absent:
Craig R. McClanahan
David Nalley
Ruth Suehle
Guests:
Brian Proffitt
Christian Grobmeier - joined :14
Daniel Gruno
Dave Fisher
Dirk-Willem van Gulik
Drew Foulks
Greg Stein
James Dailey
Jarek Potiuk
Sally Khudairi
3. Minutes from previous meetings
Published minutes can be found at:
http://www.apache.org/foundation/board/calendar.html
A. The meeting of May 17, 2023
See: board_minutes_2023_05_17.txt
Tabled.
B. The meeting of June 21, 2023
See: board_minutes_2023_06_21.txt
Tabled.
4. Executive Officer Reports
A. Board Chair [Sander Striker]
On June 20-21st we had a board face to face meeting in Berlin. I'd like
to thank Sharan Foga for her persistence in making the event happen in
the first place. And I'd like to thank the participants for making the
time in their schedules and to travel for the occasion. I will also
call out Willem Ning Jiang, who couldn't make it in person and
participated through video call the entire meeting.
I really appreciated the positive and constructive engagement of
all present. Having polled directors and observers, the perception
was overwhelmingly positive.
I still have notes and actions to process, and to update the
membership on take aways.
B. President [David Nalley]
I've been working with Dirk and others on issues surrounding CRA, and
our participation at Open Source Congress.
Roman and I've been sorting out different legal use cases, and think
we have that more easily defined now, and should soon have a
member-facing documentation to outline all of this.
Additionally, please see Attachments 1 through 9.
C. Treasurer [Craig R. McClanahan]
A fairly quiet month, nothing of significance to report.
D. Secretary [Matt Sicker]
In June, the secretary office filed 47 ICLAs, 1 software grants, and
19 CoI affirmations. We are still waiting for some CoI affirmations
for this board term.
E. Executive Vice President [Ruth Suehle]
Though planning for Community Over Code proceeds well, we are coming
up short on sponsors this year, and thus I'm planning spending rather
more conservatively until/unless that changes. From talking to folks
at other events, this is a common problem this year.
David and I will be representing the ASF at the Open Source Congress
next week. I will be on a keynote panel ("Impact of Policy for
Decentralized Organizations: Challenges & Opportunities") and then
moderating a breakout session about better inter-organizational
collaboration.
F. Vice Chair [Sharan Foga]
- Assisted Chair by helping moderate during the Board Face to Face
- General Tidy Up of notes and actions post Board Face to Face
Executive officer reports approved as submitted by General Consent.
5. Additional Officer Reports
A. VP of W3C Relations [Andy Seaborne / Craig]
See Attachment 10
B. Apache Legal Affairs Committee [Roman Shaposhnik / Sharan]
See Attachment 11
C. Apache Security Team Project [Mark J. Cox / Bertrand]
See Attachment 12
@Bertrand: keep an eye on Zeppelin's progress in security
fixes
@Willem: also follow up on Zeppelin security
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:
# Accumulo [rbowen]
# Mesos [bdelacretaz]
# Public Policy [clr]
A. Apache Accumulo Project [Ed Coleman / Shane]
See Attachment A
B. Apache ActiveMQ Project [Bruce Snyder / Justin]
No report was submitted.
C. Apache Airavata Project [Suresh Marru / Rich]
See Attachment C
D. Apache APISIX Project [Ming Wen / Bertrand]
No report was submitted.
E. Apache Aries Project [Christian Schneider / Sander]
No report was submitted.
F. Apache Arrow Project [Andrew Lamb / Christofer]
See Attachment F
G. Apache AsterixDB Project [Till Westmann / Shane]
See Attachment G
H. Apache Attic Project [Herve Boutemy / Christofer]
See Attachment H
I. Apache Avro Project [Ryan Skraba / Justin]
See Attachment I
J. Apache Bloodhound Project [Gary Martin / Craig]
No report was submitted.
K. Apache bRPC Project [James Ge / Bertrand]
No report was submitted.
L. Apache Calcite Project [Stamatis Zampetakis / Sander]
See Attachment L
M. Apache CarbonData Project [Liang Chen / Sharan]
See Attachment M
N. Apache Causeway Project [Johan Doornenbal / Rich]
See Attachment N
O. Apache Celix Project [Pepijn Noltes / Willem]
See Attachment O
P. Apache CXF Project [Daniel Kulp / Craig]
No report was submitted.
Q. Apache DataFu Project [Eyal Allweil / Justin]
See Attachment Q
R. Apache DB Project [Bryan Pendleton / Rich]
See Attachment R
S. Apache Directory Project [Shawn McKinney / Christofer]
No report was submitted.
T. Apache DolphinScheduler Project [Lidong Dai / Shane]
See Attachment T
U. Apache Druid Project [Gian Merlino / Sharan]
No report was submitted.
V. Apache Dubbo Project [Jun Liu / Sander]
See Attachment V
W. Apache Fineract Project [James Dailey / Bertrand]
See Attachment W
X. Apache Flagon Project [Joshua C. Poore / Willem]
No report was submitted.
Y. Apache Fluo Project [Keith Turner / Bertrand]
See Attachment Y
Z. Apache Geronimo Project [Jean-Louis Monteiro / Sharan]
See Attachment Z
AA. Apache Giraph Project [Dionysios Logothetis / Christofer]
No report was submitted.
@Christofer: pursue a roll call for Giraph
AB. Apache Griffin Project [William Guo / Rich]
No report was submitted.
AC. Apache Hadoop Project [Wei-Chiu Chuang / Justin]
See Attachment AC
AD. Apache HAWQ Project [Lei Chang / Sander]
No report was submitted.
AE. Apache HBase Project [Duo Zhang / Craig]
See Attachment AE
AF. Apache Incubator Project [Justin Mclean]
See Attachment AF
AG. Apache InLong Project [Charles Zhang / Willem]
See Attachment AG
AH. Apache James Project [Benoit Tellier / Christofer]
See Attachment AH
AI. Apache jclouds Project [Andrew Gaul / Shane]
See Attachment AI
AJ. Apache Jena Project [Andy Seaborne / Justin]
See Attachment AJ
AK. Apache JMeter Project [Bruno Demion / Christofer]
See Attachment AK
AL. Apache Johnzon Project [Jean-Louis Monteiro / Sharan]
See Attachment AL
AM. Apache JSPWiki Project [Juan Pablo Santos Rodríguez / Willem]
No report was submitted.
AN. Apache Kudu Project [Andrew Wong / Rich]
No report was submitted.
AO. Apache Kvrocks Project [Hulk Lin / Shane]
See Attachment AO
AP. Apache Libcloud Project [Tomaž Muraus / Shane]
No report was submitted.
@Shane: pursue a roll call for Libcloud
AQ. Apache Lucene.Net Project [Shad Storhaug / Sander]
No report was submitted.
AR. Apache MADlib Project [Ed Espino / Bertrand]
See Attachment AR
AS. Apache Mahout Project [Andrew Musselman / Craig]
See Attachment AS
AT. Apache Maven Project [Karl Heinz Marbaise / Christofer]
See Attachment AT
AU. Apache Mesos Project [Qian Zhang / Bertrand]
No report was submitted.
@Bertrand: pursue a roll call for Mesos
AV. Apache MINA Project [Guillaume Nodet / Rich]
See Attachment AV
AW. Apache MyFaces Project [Bernd Bohmann / Sharan]
See Attachment AW
AX. Apache NiFi Project [Joe Witt / Justin]
See Attachment AX
AY. Apache Nutch Project [Sebastian Nagel / Shane]
See Attachment AY
AZ. Apache NuttX Project [Alin Jerpelea / Sander]
See Attachment AZ
BA. Apache OpenJPA Project [Mark Struberg / Willem]
See Attachment BA
BB. Apache OpenMeetings Project [Maxim Solodovnik / Craig]
See Attachment BB
BC. Apache OpenOffice Project [Dave Fisher / Sander]
See Attachment BC
BD. Apache ORC Project [William Hyun / Craig]
See Attachment BD
BE. Apache Parquet Project [Xinli Shang / Justin]
See Attachment BE
BF. Apache PDFBox Project [Andreas Lehmkühler / Shane]
See Attachment BF
BG. Apache Petri Project [Dave Fisher / Bertrand]
See Attachment BG
BH. Apache Pig Project [Koji Noguchi / Christofer]
No report was submitted.
BI. Apache Ranger Project [Selvamohan Neethiraj / Willem]
No report was submitted.
BJ. Apache Ratis Project [Tsz-wo Sze / Sharan]
See Attachment BJ
BK. Apache Rya Project [Adina Crainiceanu / Rich]
See Attachment BK
BL. Apache Samza Project [Yi Pan / Willem]
No report was submitted.
BM. Apache SeaTunnel Project [Jun Gao / Rich]
See Attachment BM
BN. Apache Serf Project [Justin Erenkrantz / Craig]
No report was submitted.
@Craig: pursue a roll call for Serf
BO. Apache SkyWalking Project [Sheng Wu / Justin]
See Attachment BO
BP. Apache Steve Project [Daniel Gruno / Christofer]
See Attachment BP
BQ. Apache Storm Project [P. Taylor Goetz / Sander]
No report was submitted.
BR. Apache Streams Project [Steve Blackmon / Bertrand]
No report was submitted.
BS. Apache Struts Project [René Gielen / Sharan]
See Attachment BS
BT. Apache Tapestry Project [Thiago Henrique De Paula Figueiredo / Shane]
See Attachment BT
BU. Apache Tcl Project [Georgios Petasis / Bertrand]
See Attachment BU
BV. Apache Tez Project [László Bodor / Sander]
See Attachment BV
BW. Apache Thrift Project [Jens Geyer / Shane]
See Attachment BW
BX. Apache Tika Project [Tim Allison / Christofer]
See Attachment BX
BY. Apache TinkerPop Project [Florian Hockmann / Sharan]
See Attachment BY
BZ. Apache Traffic Server Project [Bryan Call / Rich]
See Attachment BZ
CA. Apache Web Services Project [Daniel Kulp / Willem]
No report was submitted.
CB. Apache Zeppelin Project [Jongyoul Lee / Craig]
See Attachment CB
CC. Apache Helix Project [Junkai Xue / Willem]
See Attachment CC
Committee reports approved as submitted by General Consent.
7. Special Orders
A. Change the Apache Submarine Project Chair
WHEREAS, the Board of Directors heretofore appointed Liu Xun (liuxun)
to the office of Vice President, Apache Submarine, and
WHEREAS, the Board of Directors is in receipt of the resignation of Liu
Xun from the office of Vice President, Apache Submarine, and
WHEREAS, the Project Management Committee of the Apache Submarine
project has chosen by vote to recommend Kevin Su (pingsutw) as the
successor to the post;
NOW, THEREFORE, BE IT RESOLVED, that Liu Xun is relieved and discharged
from the duties and responsibilities of the office of Vice President,
Apache Submarine, and
BE IT FURTHER RESOLVED, that Kevin Su be and hereby is appointed to the
office of Vice President, Apache Submarine, to serve in accordance with
and subject to the direction of the Board of Directors and the Bylaws
of the Foundation until death, resignation, retirement, removal or
disqualification, or until a successor is appointed.
Special Order 7A, Change the Apache Submarine Project Chair,
was approved by Unanimous Vote of the directors present.
B. Change the Apache TinkerPop Project Chair
WHEREAS, the Board of Directors heretofore appointed Florian Hockmann
(florianhockmann) to the office of Vice President, Apache TinkerPop,
and
WHEREAS, the Board of Directors is in receipt of the resignation of
Florian Hockmann from the office of Vice President, Apache TinkerPop,
and
WHEREAS, the Project Management Committee of the Apache TinkerPop
project has chosen by vote to recommend Kelvin Lawrence (krlawrence) as
the successor to the post;
NOW, THEREFORE, BE IT RESOLVED, that Florian Hockmann is relieved and
discharged from the duties and responsibilities of the office of Vice
President, Apache TinkerPop, and
BE IT FURTHER RESOLVED, that Kelvin Lawrence be and hereby is appointed
to the office of Vice President, Apache TinkerPop, 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 TinkerPop Project Chair,
was approved by Unanimous Vote of the directors present.
C. Update Legal Affairs Committee Membership
WHEREAS, the Legal Affairs Committee of The Apache Software Foundation
(ASF) expects to better serve its purpose through the periodic update
of its membership; and
WHEREAS, the Legal Affairs Committee is an Executive Committee whose
membership must be approved by Board resolution.
NOW, THEREFORE, BE IT RESOLVED, that the following contributor be
added as a Legal Affairs Committee member:
Henri Yandell <bayard@apache.org>
Special Order 7C, Update Legal Affairs Committee Membership,
was approved by Unanimous Vote of the directors present.
8. Discussion Items
A. Board face to face evaluation
Reflect on the June board face-to-face in Berlin
Reflecting on the logistics and cost, it is desireable to coordinate
a face to face with one of our conferences. We don't need a face
to face meeting every term, but having one when the board sees a lot
of turn over post the annual election is beneficial. One of the
downsides here is that elections and our annual event are typically
more than half a term apart.
Very productive face-to-face meeting. Location choice in Berlin to
coincide with Buzzwords was not as useful as expected. Would like to
have some sort of travel policy for future events and have it planned
further ahead of time (such as directly after the election ratifies a
new board). Past face-to-face meetings had most travel costs covered
by employers which made these costs invisible which were made apparent
this time around.
9. Review Outstanding Action Items
* Rich: continue with PMC advice around communication tooling
[ ASF practices in the context of tooling landscape developments 2023-04-19 ]
Status: Ongoing
* Sander: follow up on comments from board
[ BuildStream 2023-05-17 ]
Status: Not Done. Personal project for August.
* Craig: follow up with monthly reporting for next three months
[ Helix 2023-05-17 ]
Status: Junkai Xue has submitted a Helix report for July 2023
* Rich: follow up with Ozone PMC about committers
[ Ozone 2023-05-17 ]
Status: Done. I am confident that the Ozone PMC understands the
concerns, and are taking them seriously.
* Sander: follow up on the issues section for Subversion
[ Subversion 2023-05-17 ]
Status: Done. VP Legal sent email to private@subversion.
* Sander: follow up with security team about CVE data on sites
[ Superset 2023-05-17 ]
Status:
* Bertrand: Follow up with Zeppelin roll call
[ Security Team 2023-06-21 ]
Status: Needs discussion. Out of three PMC members who replied to roll
call, two indicate not really being able to help. See two
messages to private@zeppelin.a.o, "project is at risk due to
security issues" and "roll call request".
* Christofer: pursue a report for Giraph
[ Giraph 2023-06-21 ]
Status: I sent an email to the private list explicitly mentioning that
failing to report would result in a role-call ... so-far
nothing happened. I guess it might be time to do a roll-call.
It does feel as if nobody is left in the project.
* Shane: pursue a report for Libcloud
[ Libcloud 2023-06-21 ]
Status: Will run a roll call; if not enough response then we do an
Attic next month. Essentially no work except for dependabot
for ages.
* Shane: Follow up with Mnemonic about PMC Chair
[ Mnemonic 2023-06-21 ]
Status: PMC misunderstood process and emails were dropped; will do for
next month.
* Justin: Follow up with the PMC Chair
[ MXNet 2023-06-21 ]
Status: Sent email and got response. Done.
* David: Follow up with VP, Legal, on budget
[ Budget 2023-06-21 ]
Status: David is absent, carrying over.
10. Unfinished Business
11. New Business
The board would like to change the title of VP, Public Policy, to
VP, Public Affairs. The board has approved this change by a vote of
7-1 with Craig's no.
12. Announcements
13. Adjournment
Adjourned at 22:09 UTC
============
ATTACHMENTS:
============
-----------------------------------------
Attachment 1: Report from the VP of Brand Management [Mark Thomas]
Covering the period June 2023
* ISSUES FOR THE BOARD
None.
* OPERATIONS
Responded to the following queries, liaising with projects as required:
- approved a 3rd-party event usage of the DRUID mark
- approved a 3rd-party event usage of the FLINK mark
- replied to a query regarding registering an additional domain for
CommunityOverCode
- Rejected one podling name search
- Approved one request to use the JMETER mark for a training event
- Provided advice to NUTTX regarding organizing an event
- Provided feedback to Press and Marketing on the "original creator of" phrase
- OPENOFFICE reviewed some sellers of installation CDs on Amazon
- Provided feedback on the proposed CASSANDRA Ambassador program
- Placed one podling name search on hold as the project has yet to approach
the Incubator
* REGISTRATIONS
- DOLPHINSCHEDULER is now registered in China
- Worked with counsel to renew the CASSANDRA registration in the US
* INFRINGEMENTS
Our opposition to the registration of a mark in Columbia that conflicted with
our CASSANDRA mark was accepted and the registration of the conflicting mark
denied.
-----------------------------------------
Attachment 2: Report from the VP of Fundraising [Bob Paulin]
1) ASF Sponsors:
a --New: we have welcomed a new Silver Sponsor.
b --Renewals: two Gold and one Silver Sponsor have confirmed their renewal.
One Silver Sponsor has stated their inability to renew for the upcoming
sponsorship year.
c --Payments: 1 --New: no new Sponsor payments were received.
2a --Renewing: we received payment from one renewing Platinum, one Gold,
and one Silver Sponsor.
2b --Incoming: we await payment from one Platinum, one Gold, one Silver,
and one Bronze Sponsor.
2) Targeted Sponsors: no changes with our Targeted Sponsors have taken place
during this timeframe.
3) Sponsor Relations: we are liaising introductions with a Gold Sponsor
seeking select ASF community speakers for an internal event. We are preparing
speaking points and communications tools to help spread the word on ways to
support the ASF, and are also connecting with Sponsor contacts who are new to
the ASF community/ecosystem. Our Sponsor monthly news updates include project
release highlights and event deadlines and opportunities (e.g., CFP and
sponsorship).
4) Event Sponsorship: we have guided ASF Sponsors to the prospectus for the
upcoming Community Over Code conference(s), and are liaising 2023 event
sponsorship activities. We continue to assist with collections on several
outstanding sponsorship payments from ApacheCon NA (October 2022).
5) Individual Donations and Corporate Giving: we received $1.8K in individual
donations this month.
6) Administrivia: we are working with the Treasury and Accounting teams on a
few outstanding Sponsor invoicing issues, as well as review/correct some
reporting inconsistencies.
-----------------------------------------
Attachment 3: Report from the VP of Marketing and Publicity [Brian Proffitt]
Rebrand update
I have selected a vendor to handle the rebranding process for ASF and have
requested a Statement of Work (SOW) from them. Once the SOW is in hand and
agreed to, I will request additional funding from the Board for M&P's FY24
budget.
I will also convene the Rebrand Steering Committee and begin discussions on:
* Committee logistics (vendor workflow, meetings, objectives, etc.)
* Creating a member survey form to obtain themes and ideals members think
represent the ASF
Website update
In an effort to better serve the ASF’s open source community and projects,
we’ve implemented some updates to Apache.org, including simplified site
navigation and updated content pages.
* Apache.org site navigation now has one menu (reduced from two menus
previously), in an effort to reduce confusion and make exploration of the
site seamless.
* By removing duplicated and outdated links that were present throughout
Apache.org, we hope to improve the overall user experience.
See pull request 238[1] for more information on recent web updates.
I would like to take this opportunity to acknowledge the great work by Paul Au
and the rest of the Constantia team, as well as the Apache Infrastructure team
for all of their work on this project. Thanks to all!
Please take a moment to provide your feedback[2] and help inform future site
updates.
Foundation Comms
Announced Kvrocks as TLP via the ASF blog, wire, and social
channels. Continued stakeholder outreach for FY 2023 Annual Report; started
draft. Provided edits for ASF project social media plan and podling publicity
page. Began drafting response for Traffic Control fork (Comcast news). Drafted
M&P planning overview to help prep for June ASF Board meeting. Promoted
Community Over Code Asia and NA events, including CFP deadlines.
Proactive Storytelling
#FirstContributions Campaign: new blog post, editorial calendar, & social
cards.
Began interviewing stakeholders for story platform.
Website Finalized content and navigation in preparation for launch. Submitted
Jira ticket for site redirects.
Social Media Posts
In June, we continued to drive community engagement across social media,
sharing: 56 Tweets + 16 LinkedIn posts covering ASF, project, and industry
news. Posts included project releases, Community Over Code Asia promotion
(call for speakers), case studies, and how-to articles. Continued to react to
select posts in which we were mentioned or tagged.
Social Engagement Stats (Twitter + LinkedIn)
Total engagement: 7,594 (up 10% from May) Total clicks: 3,558 (up 17% from
May) Click to engagement ratio: 47% (up 3% from May) New followers: 675 (down
18% from May)
[1] https://github.com/apache/www-site/pull/238
[2] https://forms.gle/LikYQzDPTB7HSNPMA
-----------------------------------------
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.
General Activity
================
- Forward movement of our Pelican website generation system. A number
of outstanding pull requests were merged, and the underlying stack
is being updated.
- We are assembling an "Infra track" for C>C this fall.
- Our PubSub system had a surprising defect in the payload size, which
was throwing off many parts of our systems. Found and corrected.
- The Gradle Enterprise installation is effectively complete, and we
will start rolling it out to more projects.
- Jira (re)activation is complete. The new workflow has greatly
reduced spam accounts and spam tickets. There have been some
escalation of initial rejections and other issues, but the process
is becoming smoother and cleaner.
- The Agenda Tool is progressing, with a focus for assisting the Chair
to run the meeting.
- Wrap-up of LastPass -> BitWarden migration.
- Improved mail handling and spam prevention.
- gitbox grew a "file diff" feature for Apache Tomcat, to backfill the
turned-off gitweb that was disabled last month.
- Continued work for ephemeral build nodes, with a lot of focus on
constructing AMI images and using Ansible to manage the process.
-----------------------------------------
Attachment 5: Report from the VP of Conferences [Rich Bowen]
The CFP for Community Over Code North America has closed and talk selection is
ongoing.
Registration is now open at https://communityovercode.org/registration/
Community over Code Asia will be held in August in Beijing. Details at
https://apachecon.com/acasia2023/index.html
-----------------------------------------
Attachment 6: Report from the Apache Travel Assistance Committee [Gavin McDonald]
Current Events
==============
Community Over Code Beijing
---------------------------
Of 11 applications we have rejected 2, and passed on the other 9 for
consideration, recommending a Yes for 5 of those 9 and the remaining 4 we
marked as undecided. As the budget is not ours and the total amount available
is still unclear we decided to pass over the results for final decision to the
event organizers.
Also a first for TAC, is that the Hotel and Travel will be handled in full by
the Organizers. So details of the accepted people will be passed over to them.
Community Over Code Halifax
---------------------------
With a few days until applications close, we have 12 applications so far. This
is lower than we would normally achieve, a reminder of the deadline will go
out today; and we do usually get some last minute applications.
Judging for this event will take place a couple of days after closing.
TAC App
=======
TAC App is still open for the Halifax event, deadline is currently July 22nd,
however is it likely we shall extend by a week or so. TAC App also needed a
bug fix, related to scoring weightings, which was done locally by Humbedooh.
Future Events
=============
Keeping an eye on things for Fosdem in Feb '24 if we have budget, and also how
things progress with Community Over Code Europe '24.
Short/Medium Term Priorities
============================
Keeping an eye out for other smaller events to support. We are keen to hear
about projects events.
Mailing List Activity
=====================
Some activity regarding the upcoming events, and judging.
Membership
==========
Chris Wells (iroh) was added as a new Committee Member, and has been active
judging the Community Over Code Asia 2023 event.
Welcome Chris!
===
-----------------------------------------
Attachment 7: Report from the VP of Diversity and Inclusion [Katia Rojas]
-----------------------------------------
Attachment 8: Report from the VP of Data Privacy [Christian Grobmeier]
-----------------------------------------
Attachment 9: Report from the VP of Public Policy [Dirk-Willem van Gulik]
Public Policy
======================
0) Discussion was moved to the members only public-affairs-private@apache.org
mailing list.
There is a companion wiki page with recent documents
https://cwiki.apache.org/confluence/display/ASFP/Public+Affairs (members
only). About 38 members sat in on an introduction presentation I gave (same as
given to the board@).
1) CRA - `plot twist'
Prior to the ASF/OpenSSL meeting - the open source community assumed that the
CRA's 'bad definitions' of open source were just that. And that the intentions
were right - to keep (the ASF type of) open source out of the CRA.
This shifted last week.
First: both the policy & political side of the 3 law making powers confirmed
that they want foundations such as the ASF under the CRA regulation. Otherwise
it would be `too costly' for SMEs to comply. Open Source Foundations are
expected to carry that burden. Second: this is broadly-carried consensus; it
is not controversial.
The open source community (coordinated by OFE) has since started to respond
and is (slowly) adjusting strategy -- this will mean a focus on country level
(that indirectly influences the third power, the Council (consilium).
The more loud options (e.g. go black, geolocked-messaging, the blocking of
distribution, intentionally break CI/CD via maven/npm, etc) were discussed
between the code-producing foundations -- and the ASF steered away from these
as unlikely to have the right effect at this stage.
BKP and I are preparing a muted blog post for both the community and policy
makers.
2) PLD, US acts
No changes or updates -- these are progressing and are not a particular cause
for concern (yet).
3) Open Source Congress.
The Linux Foundation (on request/tied to sponsorship by Huawei/FutureWei) is
organising an invite-only, chatham house rules event in Geneva at the end of
this month. About 1/3 of the people there are from open source foundations
that create code; about 1/3 are from the Linux Foundation (most of whom are
not on the code producing side); 1/3 are from organisations supportive of open
source (e.g. funding, OSI, OpenUK, etc). With the sponsors - and noteworthy,
several representatives of the (normative) standards body will be present.
The various risks were discussed with the other code-producing open source
organisations.
4) Situational Awareness - EUROPE
As per the last board meeting - to give the ASF situational awareness - I
propose that we join the OFE as a partner;
as the low-key visibility and association gives the right message. And makes
us a natural `ask us anything' sort of non pushing partner in the ecosystem.
I.e. you are consulted about impact.
OFE has more than proven itself in the past 18 months (with the CRA, working
with us and in their advisory rather than pushly lobbyist relation to the
folks in Brussels).
That said - it is also common for organisations to 'just' subscribe to their
situational awareness feed. And do so silently.
So I am requesting permission to make this so, work with Legal to dot any i's,
and submit something for board final OK.
5) Situational Awareness - USA
There is currently no OFE equivalent in the USA. Deb Bryant is trying to
create such under the name of the Open Policy Alliance. She has however not
detailed this to any meaningful level.
I ask permission from the board to tentatively support her in this effort -
with, for us, the focus on 1) this being about awareness in the US, and 2) for
the code-producing open source organisations (as opposed to those that, say,
are more about dispersing money, etc). And 3) with a heavy slant towards the
volunteer ran open source; with a modus operandi that fits that type of
organisation
.
6) Registration on the transparency register
Although there are no legal requirements (see earlier reports on the legal
analysis) - it is generally considered good practice and `wise' to register in
the transparency register in Brussels
https://ec.europa.eu/transparencyregister/public/homePage.do
Given our own high level of openness, transparency and the fact that want to
stay far away from lobbying (and radiate such) - I hereby ask permission to
register the ASF in there as a Delaware corporation.
7) New EU/US data sharing agreement
There is a new political agreement between the US and the EU on data sharing.
Our VP of Privacy and I agree that it is very likely that this will shortly be
voided in a Schrems-III ruling. And that it thus behoves the ASF to not change
its current approach.
-----------------------------------------
Attachment 10: Report from the VP of W3C Relations [Andy Seaborne]
The W3C is holding a "Secure the Web Forward" Virtual Workshop. It is a joint
event with OpenSSF, OWASP and OpenJS. The first attempt with mostly in-person
event failed to attract enough interest.
https://www.w3.org/blog/news/archives/9969
------------
henry story (bblfish@) has joined RDF surfaces community group.
ASF has agreed to the W3C Community Contributor License Agreement
-----------------------------------------
Attachment 11: Report from the Apache Legal Affairs Committee [Roman Shaposhnik]
Past month has been pretty calm. Committee members took good care of resolving
most issues on time. After resolving a handful of LEGAL issues, we are flat at
22 outstanding issues.
Henri Yandell's draft of formal guidance for ASF contributors on using
generative AI code assist tools (e.g. GitHub Co-pilot, etc.) has been
successfully reviewed by Legal Committee and is ready to be published.
Board resolution to add Henri Yandell to the Legal Committee has been
submitted.
We have cleaned up membership of legal-private@ to correspond to the current
Legal Committee roster. legal-internal@ has been cleaned up to be
legal-private@ plus some folks working in the office of the President.
We have reached a consensus on the division of labor when it comes to legal
matters between the Legal Committee and the office of the President. We're
working on an official FAQ to clarify our joint understanding. Expect it to be
sent for review and published in the next few weeks.
We have clarified an outstanding issue for the Apache SVN community regarding
licensing of old open.collab.net content to the ASF for re-hosting.
VP Legal is expected to attend an Open Source Congress in Geneva hosted by the
Linux Foundation last week of July.
-----------------------------------------
Attachment 12: Report from the Apache Security Team Project [Mark J. Cox]
- We have engaged with the Trivy SBOM/security scanner project to
discuss how we can help reduce noise and make security reports more
accurate, possibly using VEX. This is challenging because it
requires the scanner to have access to not just a list, but the
graph of dependencies.
- The Airflow project are working on publishing SBOM information with
their binary artifacts.
- We helped publish https://apache.org/.well-known/security.txt
Stats for June 2023:
46 [license confusion]
22 [support request/question not security notification]
9 [report/question relating to dependencies]
Security reports: 73 (last months: 59, 73, 64)
18 ['website or other infrastructure']
5 ['tomcat']
4 ['airflow']
3 ['httpd', 'openoffice']
2 ['activemq', 'hadoop', 'nifi', 'superset', 'trafficserver', 'xalan']
1 ['accumulo', 'apisix', 'aries', 'baremaps', 'camel',
'carbondata', 'cloudstack', 'cordova', 'doris',
'felix', 'guacamole', 'iotdb', 'jackrabbit', 'jena',
'jspwiki', 'myfaces', 'netbeans', 'openmeetings',
'ozone', 'pekko', 'pig', 'pinot', 'rocketmq',
'roller', 'sling', 'storm', 'xerces', 'zeppelin']
In total, as of 3 July 2023, we're tracking 170 (last months: 165,
173) open issues across 57 projects, median age 104 days (last months:
76, 69). 54 of those issues have CVE names assigned.
11 (last month: 12) of these issues, across 5 projects, are
older than 365 days.
-----------------------------------------
Attachment 13: Report from the VP of Jakarta EE Relations [Rob Tompkins]
-----------------------------------------
Attachment A: Report from the Apache Accumulo Project [Ed Coleman]
## Description:
The mission of Apache Accumulo is the creation and maintenance of software
related to a robust, scalable, distributed key/value store with cell-based
access control and customizable server-side processing.
## Project Status:
Current project status: Ongoing with moderate activity.
Issues for the board: none.
Accumulo is currently working two significant development efforts. Improving
the performance and stability of the 2.1.x line and the evolution of the
processing model to support dynamic scaling and provide elasticity.
## Membership Data:
Apache Accumulo was founded 2012-03-21 (11 years ago)
There are currently 41 committers and 38 PMC members in this project.
The Committer-to-PMC ratio is roughly 6:5.
Community changes, past quarter:
- No new PMC members. Last addition was Christopher L. Shannon on 2022-09-27.
- No new committers. Last addition was Christopher L. Shannon on 2022-09-27.
## Project Activity:
Releases:
- accumulo-2.1.1 was released on 2023-06-19.
- accumulo-1.10.3 was released on 2023-04-13. 1.x is planned to be end of
life on or around 2023-11-01, with an expected final release of any
ready-to-ship bug fixes.
The 2.1.1 release closes CVE-2023-34340. Accumulo 2.1.0 contains a defect in
the user authentication process that may succeed when invalid credentials are
provided. The CVE was reported on 2023-06-01 and was closed with the release
on 2023-06-19.
Activity on 2.1 has been very active with bug-fixes and performance
improvements that are being driven by increased community adoption of 2.1.x as
1.10.x approaches end of life. Accumulo is planning on a 2.1.2 release this
quarter that includes items that were slated for 2.1.1, but were bumped
because of the need for a quick release to resolve the CVE.
A release of 3.0 is also expected this quarter. It is planned to be a removal
of deprecated items as permitted by semver, but with minimal other changes.
The 3.0 release will also complete the removal of potentially offensive terms.
Work continues on the evolution of the Accumulo processing model to support
dynamic scaling and provide elasticity. The goal for Accumulo is to move from
a model where active table metadata and table data management is hosted in
active processes to a model that can dynamically scale server components
on-demand to provide configurable latency and higher scalability. The
community has not decided if the redesign will be a 3.x or a 4.0 release.
## Community Health:
Overall community health is good and GitHub activity remains consistent.
- Accumulo development centers on GitHub as reflected in the GitHub activity
(both pull requests and issues) compared to email list activity. Community
discussions also occur on the the-asf Accumulo slack channel.
- The increase in GitHub activity is due to robust development on the 2.1.1
and 2.1.2 (planned) releases and the work on providing dynamic scaling and
elasticity.
- (as of 2023-07-10) The large number of issues opened (133) vs closed (77)
reflects issues being created as work on elasticity changes are identified.
Currently there are 71 open issues against the elasticity project, compared
with 10 open and 2 in progress issues against the 2.1 branch and 2 open and
5 in progress issues against the 3.0 branch.
## Links
[1] https://www.cve.org/CVERecord?id=CVE-2023-34340
-----------------------------------------
Attachment B: Report from the Apache ActiveMQ Project [Bruce Snyder]
-----------------------------------------
Attachment C: Report from the Apache Airavata Project [Suresh Marru]
## Description:
The mission of Apache Airavata is the creation and maintenance of software
related to executing and managing computational jobs on distributed computing
resources including local clusters, supercomputers, national grids, academic
and commercial clouds.
## Project Status:
Current project status: The Project is active and community is healthy.
Issues for the board: No issues to report.
## Membership Data:
Apache Airavata was founded 2012-09-18 (11 years ago)
There are currently 42 committers and 26 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 Isuru Ranawaka on 2022-03-06.
- No new committers. Last addition was Dinuka DeSilva on 2021-07-22.
## Project Activity:
Two google summer of code students are contributing this summer. Transition
from large community repository to individual sub systems is progressing well.
Contributors have increased on smaller projects as opposed to larger code
base.
## Community Health:
The community is active, with pull requests being contributed, discussed and
merged.
-----------------------------------------
Attachment D: Report from the Apache APISIX Project [Ming Wen]
-----------------------------------------
Attachment E: Report from the Apache Aries Project [Christian Schneider]
-----------------------------------------
Attachment F: Report from the Apache Arrow Project [Andrew Lamb]
## Description:
The mission of Apache Arrow is the creation and maintenance of software
related to columnar in-memory processing and data interchange. More
information can be found at https://arrow.apache.org/overview/
## Project Status:
Current project status: Ongoing (high activity)
Issues for the board: None
## Membership Data:
Apache Arrow was founded 2016-01-19 (7 years ago)
There are currently 97 committers and 50 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:4.
Community changes, past quarter:
- Ben Baumgold was added to the PMC on 2023-06-19
- Jie Wen was added to the PMC on 2023-06-10
- Dewey Dunnington was added to the PMC on 2023-06-22
- Matthew Topol was added to the PMC on 2023-05-02
- Gang Wu was added as committer on 2023-05-15
- Kevin Gurney was added as committer on 2023-07-04
- Marco Neumann was added as committer on 2023-05-11
- Mehmet Ozan Kabak was added as committer on 2023-06-10
- Ruihang Xia was added as committer on 2023-04-15
## Project Activity:
There has been healthy debate about adding new formats, [StringArray] and
[ListView], focused on increasing Arrow’s appeal in high performance
computation engines.
We have completed the transition from JIRA to using GitHub issues for the mono
repo and that appears to be going well.
The DataFusion subproject is considering applying to become its own top level
Apache project (see DataFusion update below)
[StringArray]: https://lists.apache.org/thread/c6frlr9gcxy8qdhbmv8cn3rdjbrqxb1v
[ListView]: https://lists.apache.org/thread/r28rw5n39jwtvn08oljl09d4q2c1ysvb
## Sub Project Updates
Arrow has several subprojects, as listed on https://arrow.apache.org/
### ADBC
We have released 2 new minor versions. They include new drivers and new
implementations.
### Arrow Flight
We have added new features to the Arrow Flight specification:
1. Ordered data support: https://github.com/apache/arrow/issues/34852
2. Resultset expiration support: https://github.com/apache/arrow/issues/35500
### Arrow Flight SQL
We have updated the Arrow Flight SQL specifications based on the above Arrow
Flight update.
### DataFusion
DataFusion continues to grow and mature. The community added many new features
as described in the latest [blog] post, and discussed and came to consensus on
the [goals] of the project and is discussing a [move to its own top level
Apache project]. Current development focus is on performance and adding better
support for structured types such as Lists and Structs. We expect more work on
improving documentation and communicating externally over the next quarter.
[blog]: https://arrow.apache.org/blog/2023/06/24/datafusion-25.0.0/
[goals]: https://github.com/apache/arrow-datafusion/discussions/6441
[move to its own top level Apache project]:
https://github.com/apache/arrow-datafusion/discussions/6475
## Language Area Updates
Arrow has at least 12 different language implementations, as explained in
https://arrow.apache.org/overview/
Arrow 12.0.0 was released from the monorepo:
https://arrow.apache.org/blog/2023/05/02/12.0.0-release/
### C++
PRs have been created with example implementations of two new layouts, Array
View and String View. These layouts are motivated by Arrow-compatible engines
which found these layouts to be more efficient for their workflows.
As mentioned in the previous report, the C++ compute engine Acero was broken
out into a separate module and Arrow-C++ can now be built without it, allowing
for more modular feature configuration.
### C#
C# now has a complete implementation of the C data interface, allowing for
efficient intra-process communication between C# and other languages. In
addition, there has been some early discussion
### Go
PRs were created with the example implementation of StringView for Go to be
the second implementation in order to vote on the layout. Changes were
introduced to improve compatibility with x86 (32-bit) systems and TinyGo
builds for WebAssembly builds, along with corresponding CI builds.
A default Arrow Flight middleware was added for handling Cookies via gRPC
headers.
Usage of the Go implementation continues to grow and expand in the community.
### Java
Ongoing maintenance of the Arrow Java implementation remains steady.
### JavaScript
### Julia
We have released new versions rapidly when we fix a problem.
New PMC member who focuses on Julia has joined. There are 2 PMC members who
focus on Julia now.
### nanoarrow
The 0.2.0 release of nanoarrow featured support for decoding the Arrow IPC
format and included a number of interface improvements and bugfixes resulting
from early usage. Ongoing work includes support for non-CPU data via the Arrow
C Device interface and documentation improvements suggested by early users of
the library.
### Rust
The Rust implementation has been focused on improving the UX of the API, the
speed, consistency and correctness (timezones!) of the kernels.
### C (GLib)
We have added new bindings continually as usual.
### MATLAB
New committer who focuses on MATLAB has joined. The committer is the first
committer who focuses on MATLAB. We’ll expand the MATLAB community.
Integrated support for mathworks/libmexclass, enabling streamlined development
of the MATLAB interface. As a result, significant progress has been made on
public MATLAB APIs, including support for Array and RecordBatch construction
from equivalent MATLAB types (e.g. table).
Recently merged Windows and ccache CI support, bridging the platform gap for
MATLAB qualification. This will help ensure quality of PRs and improve
developer confidence when making changes.
Next steps for the MATLAB interface include working on compound / nested data
types and tabular file I/O workflows.
### Python
The python community is embracing “protocols”, which allow for
library-agnostic interchange and duck-typing. Pyarrow has added support for
the dataframe interchange protocol which maps to pyarrow’s Table class. In
addition, some early discussion has begun around a dataset protocol based on
pyarrow’s datasets API.
### R
The R bindings now support JSON Datasets and continue to benefit from ongoing
performance enhancements and feature additions in the C++ library.
### Ruby
Ruby related questions/issue reports were increased. It shows that user base
of the Ruby bindings is increasing.
### Swift
We have started implementing Arrow Flight.
## Community Health:
Community communication continues to be strong.
There have been 9 blog posts published to https://arrow.apache.org/blog/ in
the last 3 months, including two from community members on their use of Arrow
The mailing lists are active
* dev@arrow.apache.org had a 10% decrease in traffic in the past quarter (779
emails compared to 858)
* jira@arrow.apache.org had a 100% decrease in traffic in the past quarter (0
emails compared to 10778)
For the mono repo:
* 2275 commits in the past quarter (5% increase)
* 254 code contributors in the past quarter (1% increase)
* 1986 PRs opened on GitHub, past quarter (-6% change)
* (1954 PRs closed on GitHub, past quarter (-11% change)
* 1573 issues opened on GitHub, past quarter (-11% change)
* 1342 issues closed on GitHub, past quarter (-5% change)
-----------------------------------------
Attachment G: Report from the Apache AsterixDB Project [Till Westmann]
## Description:
The mission of AsterixDB is the creation and maintenance of software related to
open source Big Data Management System
## Project Status:
Current project status: ongoing
Issues for the board: none
## Membership Data:
Apache AsterixDB was founded 2016-04-19 (7 years ago)
There are currently 40 committers and 27 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:4.
Community changes, past quarter:
- No new PMC members. Last addition was Xikui Wang on 2018-02-01.
- Peeyush Gupta was added as committer on 2023-05-12
## Project Activity:
Releases:
Apache AsteriDB 0.9.8.1 was released on 2023-05-09.
Apache Hyracks 0.3.8.1 was released on 2023-05-09.
Activity:
Release 0.9.9 is nearly ready, just waiting on a few fixes.
## Community Health:
APE was adopted but is still a fledgling and needs to gain more mindshare.
APE 1 (Apache Iceberg support) was adopted and merged for the next
release.
The convention of tying fixes/features to JIRA entities has become
more consistent over time.
There is still discussion about how to make dev@ more active. APE was part
of the plan for this as the process entails at least a few +1 emails.
-----------------------------------------
Attachment H: Report from the Apache Attic Project [Herve Boutemy]
## Description:
The mission of Attic is the creation and maintenance of a home for dormant
projects.
## Project Status:
Current project status: Ongoing
Issues for the board: none
## Membership Data:
Apache Attic was founded 2008-11-19 (15 years ago)
There are currently 19 committers and 17 PMC members in this project.
The Committer-to-PMC ratio is roughly 1:1.
Community changes, past quarter:
- No new PMC members. Last addition was Herve Boutemy on 2015-07-19.
- No new committers. Last addition was Herve Boutemy on 2016-01-27.
## Project Activity:
Attic retired 2 projects this quarter: OODT and Any23.
Work has been done to improve Wiki retirement.
## Community Health:
Last retirements went well with our tools and documented process.
-----------------------------------------
Attachment I: Report from the Apache Avro Project [Ryan Skraba]
## Description:
Apache Avro is a data serialization system with a compact binary format. It is
used for storing and transporting schema-driven serialized data. The unique
features of Avro include automatic schema resolution: when the reader's
expected schema is different from the actual schema with which the data was
serialized the data is automatically adapted to meet reader's requirements.
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache Avro was founded 2010-04-21 (13 years 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:
- No new PMC members. Last addition was Martin Tzvetanov Grigorov on 2022-09-08.
- No new committers. Last addition was Zoltan Csizmadia on 2022-03-28.
## Project Activity:
The last release of Apache Avro 1.11.2 was 2023-07-03. Although this release
was in demand for bug and security fixes for months, it took much longer than
expected to prepare and execute for a few concrete reasons (discussed below).
There were a few regressions discovered since the release, and we will likely
do another minor release very soon. We are on track to do a major release
(1.12.0) if necessary.
## Community Health:
Mailing Lists:
- dev@avro.apache.org had 438 emails (+30% change)
- issues@avro.apache.org (mostly notifications) had 658 emails (-5% change)
- user@avro.apache.org continues to have very little traffic, less than 10 total
JIRA:
- 59 issues opened (96% decrease)
- 40 issues closed (73% decrease)
Code Repository:
- 369 commits in the past quarter (-2% change)
- 25 code contributors in the past quarter (-3% change)
GitHub:
- 153 PRs opened on GitHub, past quarter (13% change)
- 148 PRs closed on GitHub, past quarter (14% change)
Although the numbers for the mailing lists and JIRA look high, we mentioned an
unexplained sharp drop last quarter. These statistics are in line with our
January report.
It was disappointing that the minor release took so long to prepare, but there
are a number of reasons that mostly affect minor releases:
- our branching strategy makes identifying and doing cherry-picks and merges
complicated,
- our build process for testing pull requests has diverged from the build
process we use to release, and
- we have limited release manager resources across many artifact repositories.
These aren't new problems and we've had some discussions in the past on how
to address them, such as by doing more regular releases, releasing SDKs
separately, changing the process for committers to cherry-pick, and having the
current release manager "shadowed" by the next release manager to share
expertise. In this next reporting period, we would like to revisit these
discussions for a concrete vote.
Because of the minor release, we didn't progress on the IP Clearance for the
code donation for the popular gradle-avro-plugin. This could be a compelling
reason to release the next major version of avro.
-----------------------------------------
Attachment J: Report from the Apache Bloodhound Project [Gary Martin]
-----------------------------------------
Attachment K: Report from the Apache bRPC Project [James Ge]
-----------------------------------------
Attachment L: Report from the Apache Calcite Project [Stamatis Zampetakis]
## Description:
Apache Calcite is a highly customizable framework for parsing and planning
queries on data in a wide variety of formats. It allows database-like
access,
and in particular a SQL interface and advanced query optimization, for data
not residing in a traditional database.
Avatica is a sub-project within Calcite and provides a framework for
building
local and remote JDBC and ODBC database drivers. Avatica has an independent
release schedule and its own repository.
## Project Status:
Current project status: ongoing
Issues for the board: none
## Membership Data:
Apache Calcite was founded 2015-10-22 (8 years ago)
There are currently 67 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 Benchao Li on 2023-01-27.
- Jacky Lau was added as committer on 2023-06-28
- Oliver Lee was added as committer on 2023-06-13
- Tanner Clary was added as committer on 2023-05-25
- Zhe Hu was added as committer on 2023-06-28
## Project Activity:
There were no releases during this quarter. The last release was Apache
Calcite 1.34.0 on 2023-03-14.
We are actively working towards Apache Calcite 1.35.0 and we plan to release
the new version during July 2023.
On 2023-06-29, the Calcite community organised a Virtual key signing party for
expanding the Web of trust and empowering the cryptographic signatures of our
members and future release managers. 4 PMC members and 2 committers attended
the event.
## Community Health:
The project remains super healthy.
The traffic in JIRA, GitHub, issues@, commits, has increased overall, while
dev@ has dropped by 18%. During this quarter there were more discussions and
exchanges under specific issues/tickets shifting the traffic from dev@ to
issues@ and other places.
The number of non-committer (contributor) commits per month:
+---------------------+---------------------+---------------------+
| year | month | contributor_commits |
+---------------------+---------------------+---------------------+
| 2023 | 4 | 17 |
| 2023 | 5 | 21 |
| 2023 | 6 | 35 |
+---------------------+---------------------+---------------------+
The number of active reviewers per month:
+---------------------+---------------------+---------------------+
| year | month | active_reviewers |
+---------------------+---------------------+---------------------+
| 2023 | 4 | 6 |
| 2023 | 5 | 6 |
| 2023 | 6 | 11 |
+---------------------+---------------------+---------------------+
Top-3 reviewers in the last quarter:
+-----------+---------------------+
| committer | reviews |
+-----------+---------------------+
| Julian Hyde <jhyde@apache.org> | 28 |
| Benchao Li <libenchao@gmail.com> | 12 |
| rubenada <rubenql@gmail.com> | 8 |
| Jiajun <jiajunbernoulli@foxmail.com> | 8 |
+-----------+---------------------+
The number of non-committer commits has increased roughly by 43% from the last
quarter (51 commits in Q1 vs. 73 commits in Q2) which is promising for
inviting new committers in the near term.
The number of active reviewers increased slightly compared to the last quarter
with June being the most active month for everyone. The preparation for the
1.35.0 release and the call for action did help in bringing those numbers up
during June.
In terms of sharing the review load things are a bit better this quarter but
still far from being completely balanced. There have been discussions around
the topic in the last quarter but we obviously need more involvement from the
community members.
-----------------------------------------
Attachment M: Report from the Apache CarbonData Project [Liang Chen]
## Description:
- The Apache CarbonData is data store solution for fast analytics on Big Data
platforms (including Apache Hadoop, Apache Spark, Apache Flink among others)
to help speed up queries an order of magnitude faster over petabytes of
data, with the aim of using a unified file format to satisfy all kinds of
data analysis cases.
## Issues:
- There are no new issues requiring board attention at this time.
## Activity:
- Last 3 months, we focused on fixing some issues:
- Fixed performance issues by changing index id.
- Fixed Secondary Index till segment level with SI as datamap, make
Secondary Index as a coarse grain Datamap and use SI for Presto queries
- Fixed Exception in loading data with overwrite on partition table.
## Health Report:
- Commit activity:
- 11 commits in the past quarter
- 4 code contributors in the past quarter
## Releases:
- we are preparing 2.3.x, the community focus on fixing issues
- 2.3.0 was released on 2022-01-24
- 2.2.0 was released on 2021-08-05
- 2.1.1 was released on 2021-03-29
## Project Composition:
- Brijoo Bopanna was added to the PMC on 2022-09-24
- Brijoo Bopanna was added as committer on 2022-09-20
- There are currently 28 committers and 18 PMC members in this project.
- The Committer-to-PMC ratio is roughly 7:5.
- In private mailing list, we are discussing a new PMC.
## Community changes, past quarter:
- Brijoo Bopanna was added to the PMC on 2022-09-24
- Indhumathi was added to the PMC on 2022-02-16
- Vikram Ahuja was added as committer on 2022-02-10
- Akash R Nilugal was added to the PMC on 2021-04-11
## Notable mailing list trends:Mailing list activity stays at a high level
- dev@carbondata.apache.org:
- 161 subscribers (change 13):
- dev@carbondata.apache.org had a 23% decrease in traffic in the past
quarter (28 emails compared to 36)
## Github issues activity:
- 5 issues opened on Github.
## Github PR activity:
- 5 PRs opened on Github.
- 7 PRs closed.
-----------------------------------------
Attachment N: Report from the Apache Causeway Project [Johan Doornenbal]
## Description:
The mission of Causeway is the creation and maintenance of software related to
Framework for rapidly developing domain-driven apps in Java
## Project Status:
Current project status: Ongoing with moderate activity
Issues for the board:
There are no issues requiring board attention at this time.
## Membership Data:
Apache Causeway was founded 2012-10-17 (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:
- One new PMC member. Last addition was Martin Hesse on 2023-07-05.
- One new committer. Last addition was Martin Hesse on 2023-07-05.`
## Project Activity:
In the last quarter we released Causeway 2.0.0-RC2 [1], continuing our progress
to "re-platform" the framework to run on top of Spring Boot. With this release
we have fleshed out our "reference app" [2] as well as removed lingering TODOs
in our website [3]. We expect to issue an 2.0.0-RC3 within the next quarter.
## Community Health:
This is a mature project and the framework is generally stable. Although our
user community is small, we continue to see good engagement on our slack
channel, which the community seems to prefer over the users mailing list. (We
do continue to ensure that all relevant information are cross-posted to users@
and dev@ where necessary).
We were pleased to add a new committer/PMC member to our ranks, our first for
some time.
## References (links)
[1] https://causeway.apache.org/relnotes/2.0.0-RC2/about.html
[2] https://github.com/apache/causeway-app-referenceapp
[3] https://causeway.apache.org
-----------------------------------------
Attachment O: Report from the Apache Celix Project [Pepijn Noltes]
## Description:
Apache Celix is a framework for C, C++14 and C++17 to develop dynamic modular
software applications using component and in-process service-oriented
programming.
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache Celix was founded 2014-07-16 (9 years ago)
There are currently 17 committers and 10 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 Peng Zheng on 2022-10-16.
- No new committers. Last addition was Zhenbao on 2022-10-19.
## Project Activity:
- The .asf.yaml has been updated to produce more readable / understandable
mailing-list, triggered / supported by cdutz
- A coding guideline has been make to support the increased development
activities.
- Support for scheduled events on the Apache Celix event queue has been added
- A thread specific error log message storage for plain library has been added
and used in several Apache Celix libs.
- Start for a requirement-capability-model lib has been added
- Bundle cache and specifically cache clean has been improved for better
error handling and to minimize write actions.
- Support for export headers has been added together with default symbol
hiding to minimize lib size and dynamic loading times
- Many more small fixes, improvements and overall code quality and coverage
improvements.
## Community Health:
dev@celix.apache.org had a 28% increase in traffic in the
past quarter (463 emails compared to 361)
296 commits in the past quarter (10% increase)
7 code contributors in the past quarter (-12% change)
42 PRs opened on GitHub, past quarter (90% increase)
43 PRs closed on GitHub, past quarter (79% increase)
23 issues opened on GitHub, past quarter (-20% change)
25 issues closed on GitHub, past quarter (38% increase)
The development activities on Apache Celix is still growing and
because of the adding coding guide style more pull requests use github
tickets.
-----------------------------------------
Attachment P: Report from the Apache CXF Project [Daniel Kulp]
-----------------------------------------
Attachment Q: Report from the Apache DataFu Project [Eyal Allweil]
## Description:
The mission of Apache DataFu is the creation and maintenance of software
related to well-tested libraries that help developers solve common data
problems in Hadoop and similar distributed systems
## Project Status:
Current project status: low - we we released all our pending changes, and will
start working on a new version now (our first to support Spark 3.x).
Issues for the board: none
## Membership Data:
Apache DataFu was founded 2018-02-21 (5 years ago)
There are currently 19 committers and 12 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:3.
Community changes, past quarter:
- No new PMC members. Last addition was Ohad Raviv on 2023-02-06.
- No new committers. Last addition was Ohad Raviv on 2019-07-27.
## Project Activity:
DataFu-Spark 1.8.0 was just released, on 2023-07-08.
## Community Health:
Not much going on, but hopefully the community will join in in the tasks
necessary for our next release (some of which already exist as Jira tasks)
-----------------------------------------
Attachment R: Report from the Apache DB Project [Bryan Pendleton]
## Description:
The mission of the Apache DB project is to create and maintain
commercial-quality, open-source, database solutions based on software licensed
to the Foundation, for distribution at no charge to the public.
The Apache DB TLP consists of the following subprojects:
o Derby : a relational database implemented entirely in Java.
o JDO : focused on building the API and the TCK for compatibility
testing of Java Data Object implementations providing data
persistence.
o Torque : an object-relational mapper for Java.
## Project Status:
Current project status: Ongoing, with moderate activity.
Issues for the board: none
## Membership Data:
Apache DB was founded 2002-07-16 (21 years ago)
There are currently 48 committers and 44 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 Georg Kallidis on 2020-08-26.
- Max Philipp Wriedt was added as committer on 2023-04-14
## Project Activity:
Recent releases:
Derby-10.16.1.1 was released on 2022-06-15.
JDO 3.2.1 was released on 2022-05-25.
JDO 3.2 was released on 2022-02-01.
Torque team are happy that we have a new committer, Max Philip Wriedt!
Find the announcement here in torque-dev mailing list:
https://lists.apache.org/thread/n3mdmpb4jmj67l9rh6d1gd029f5zohl3
Status of JDO is ongoing, low activity.
No new releases since the last report.
The JDO project is continuing to work on improving support for
current and future JDKs. Currently supporting JDK 7, 11, and 17.
Looking to JDK 21 for the next supported release. We are also
upgrading the JUnit dependency from JUnit 3 to JUnit 5 so
we can more easily take advantage of potential
performance improvements.
Derby was very quiet this quarter, though the team did fix
an error in the Derby DOAP release paperwork.
## Community Health:
JDO and Torque teams saw a continuation of the increased
community activity from last winter, which is great!
Mailing list and development activity in the Torque
and JDO communities has been quite healthy.
Derby project activity has been very low throughout 2023.
Although Derby development activity continues at its normal (low)
pace, Derby user community activity has dropped to nearly
nothing, probably indicating that external usage of Derby
is dropping as well.
-----------------------------------------
Attachment S: Report from the Apache Directory Project [Shawn McKinney]
-----------------------------------------
Attachment T: Report from the Apache DolphinScheduler Project [Lidong Dai]
## Description:
Apache DolphinScheduler is a cloud-native workflow orchestration platform with
powerful user interface, dedicated to solving complex task dependencies in the
data pipeline and providing various types of jobs available `out of the box`
## Project Status:
Apache DolphinScheduler Ongoing with high, we have 274 issues closed and 267
PRs closed
## Membership Data:
Apache DolphinScheduler was founded 2021-03-17 (2 years ago)
There are currently 54 committers and 25 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:4.
Community changes, past quarter:
- Xin Cheng was added as committer on 2023-05-12
- YuXiang Wang was added as committer on 2023-07-01
## Project Activity:
Software development activity:
- We released the bug fix release 2.0.9 on 2023-06-05.
- We released 3.0.6 on 2023-05-30.
- We released 3.1.7 on 2023-05-26.
- Meetups and Conferences: We hosted 1 offline
Shenzhen DolphinScheduler meetup
## Community Health:
dev@dolphinscheduler.apache.org had a 2% increase in traffic in the past
quarter (115 emails compared to 112) users@dolphinscheduler.apache.org had a
1000% increase in traffic in the past quarter (22 emails compared to 2) 295
issues opened on GitHub, past quarter (12% increase)
-----------------------------------------
Attachment U: Report from the Apache Druid Project [Gian Merlino]
-----------------------------------------
Attachment V: Report from the Apache Dubbo Project [Jun Liu]
## Description:
Apache Dubbo is an easy-to-use Web and RPC framework that provides different
language implementations, service discovery, traffic management,
observability, security, tools, and best practices for building
enterprise-ready microservices.
## Issues:
No issues need board attention in this quarter.
## Membership Data:
Apache Dubbo was founded 2019-05-15 (4 years ago)
There are currently 94 committers and 29 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:1.
Community changes, past quarter:
- YouWei Chen was added to the PMC on 2023-04-21
- Robert Lu was added as committer on 2023-05-09
## Project Activity:
The project development and release activities can be found here
https://reporter.apache.org/wizard/statistics?dubbo
We enrolled into 3 programming camping events in the last quarter with
now around 12 projects in progress.
The community has actively participated in the promotion of the
Community Over Code 2023 conference in the last quarter. Now we have 8
topics related to Dubbo from different committers, contributors, and
enterprise users submitted to the committee.
## Community Health:
Developing activities and discussions are extremely healthy according
to the data collected by the reporter:
https://reporter.apache.org/wizard/statistics?dubbo
-----------------------------------------
Attachment W: Report from the Apache Fineract Project [James Dailey]
#Fineract July 2023 Report
## Description:
The mission of Apache Fineract is the creation and maintenance of software
related to a core banking platform that provides a reliable, robust, and
affordable solution for entrepreneurs, financial institutions, and service
providers to offer financial services to the world's underbanked and unbanked.
## Issues:
There are no significant issues requiring Board attention
## Membership Data:
Apache Fineract was founded 2017-04-18 (6 years ago, contributed by Mifos)
There are currently 51 committers and 24 PMC members in this project. The
Committer-to-PMC ratio is roughly 2:1. Community changes, past quarter:
- Adam Saghy agreed to join the PMC (He initially declined but then later
accepted.) and was added July 10th, 2023.
- No new committers. Last addition was Bharath Gowda on 2022-12-14.
## Project Activity:
The last release was a patch release:
1.7.3 was released on 2023-03-24.
1.8.4 was released on 2023-03-24.
Although we had communicated a plan for a release 1.9 in May 2023, we are
delayed. There are many changes coming in, some of them breaking changes to
the environment and to the APIs. This may create issues for our widespread
community, but there have been no on-list objections.
On the plus side, these improvements go a long way toward making Fineract
scalable and highly performant in a cloud environment. Given that they are
uneven across the modules we have a separate effort that should start soon to
try to address that.
## Community Health:
Community engagement is trending up but we remain at some risk. We are
focused on addressing issues of confusion and approachability, making the
project more visible, and addressing the documentation gap. We have had a
modest increase in postings to the listserv this quarter. We hope these
tactics will help clarify the situation and generate more interest.
###Deprecating Fineract-CN
The Fineract-CN code project was an effort to re-engineer the Fineract project
from the ground up as a micro services architecture. After five years it has
not had a formal release at Apache and discussions have waned. Because of the
confusion it creates on list and elsewhere, in May we discussed ending the
Fineract-CN code project.
[https://lists.apache.org/thread/pkfg773zjnxt87v5y8m93gnv9kbzsys6]
We subsequently took a vote to Deprecate all content related to that code
base, including removing mention of it from the landing page.
[https://lists.apache.org/thread/zz9jhzs0d0fnjsr0p5b943t2yzmffvop].
"Resolution: the Fineract community agrees that despite some good ideas and
early interest, the lack of a formal release of FineractCN after five years
indicates that the project is not a major focus of the community. Therefore
the community will deprecate the FineractCN project, removing language from
the front landing page and some wiki pages. If there is NOT renewed interest
before October 1st then the vote is to remove and archive the FineractCN
project".
If members of the Community wish to revisit this, we remain open. This has
ZERO effect on the Fineract1.x project.
###Approachability:
We find that even experienced developers have difficulty setting up the
project environment for Fineract. Recognizing this, we've had some discussion
on list around documentation and approachability of the project. We are
heading in the direction of asciidoc generated files and moving content from
the wiki to that infrastructure.
###KeyCloak and Security Framework:
There is an active discussion to replace the existing security framework
within Fineract - the current package includes an internally developed
authentication and roles based permissions engine - with a new concept that
brings in the KeyCloak project (apache 2.0 license, managed at IBM). The
strategy is aimed at improving the credibility of the project within the
security-minded banking sector and taking something that works rather than
building and maintaining our own.
###Emeritus status:
Given a number of inactive Committers, I have proposed and we are currently
voting on the idea of moving inactive people to Emeritus status after 60
months of no activity.
[https://lists.apache.org/thread/dhjo4ty5ymgsbobg8hy7n746kbw3z8ol] Vote is not
yet finalized but it would appear to be passing with 6 binding +1, all other
votes supportive, and no other votes.
"Resolved: To remove from active status anyone who has been in-active on the
fineract project for more than 60 months. A person will be deemed inactive
if they have not done at least one thing during the last 60 months: posted on
the listserv, created or commented on a ticket, proposed or reviewed code or
documentation, written or edited content for wiki or other documentation, or
attended a meeting in person or virtually. The PMC will remove the persons'
access as Committer. If the person comes back to the Project, a simple email
or communication will suffice for reinstatement. At that time, they should be
re-oriented to the project in case they have missed any important changes to
the internal processes and standards. The same shall also apply to PMC
members as they are also Committers." Final thought: Research indicates that
developers take breaks from projects, but that if a break lasts more than a
single year then the likelihood of returning to the project falls
dramatically. (https://dl.acm.org/doi/10.1007/s10664-021-10012-6)
###Powered By listing
We (I) have started discussing the idea of putting "powered by" listings of
companies using the software on our site, and the potential for thank you
pages. https://apache.org/foundation/marks/linking#projectthanks We will be
keeping ASF Marketing & Publicity in the loop.
###Other topics:
There was no GSOC project at Fineract, although we did have an approved
mentor. An outside group (Mifos) is participating in GSOC for code
improvements, some of which may be proposed to fineract. These will follow
normal contribution patterns for code review. Thinking broadly, we've
discussed on list the need for jr devs to have a sandbox and some separate
recognition that doesn't necessarily rely on having code accepted into the
main release branch. / There are a number of proposed talks for Community
over Code Conference in Halifax and talk selections will begin shortly. / I
forgot to mention in previous report, PMC chair @jdailey became an Apache
member in January 2023.
-----------------------------------------
Attachment X: Report from the Apache Flagon Project [Joshua C. Poore]
-----------------------------------------
Attachment Y: Report from the Apache Fluo Project [Keith Turner]
## Description:
The mission of Apache Fluo is the creation and maintenance of software related
to the storage and incremental processing of large data sets
## Project Status:
Current project status: Dormant
Issues for the board: none
## Membership Data:
Apache Fluo was founded 2017-07-18 (6 years ago)
There are currently 15 committers and 12 PMC members in this project.
The Committer-to-PMC ratio is 5:4.
Community changes, past quarter:
- No new PMC members. Last addition was Brian Frank Loss on 2022-02-01.
- No new committers. Last addition was Brian Frank Loss on 2022-02-02.
This quarter, the following individual stepped down from the PMC and are now
considered PMC Emeritus:
- Karthick Narendran
## Project Activity:
- Fluo 2.0.0 was released on 4/18/23 with 6 +1 votes and no -1 votes
- Updated Uno for latest Accumulo versions.
- Added an option to run Accumulo jshell to uno
## Community Health:
There were 6 commits from 2 people, one being a new contributor. With the low
engagement and activity on the project there was discussion of what the
project should do, if anything. We decided its ok for now as long as we can
get votes for a release. The codebase is fairly stable. If a release is
needed in the future and there are not enough votes then that would be cause
to panic.
-----------------------------------------
Attachment Z: Report from the Apache Geronimo Project [Jean-Louis Monteiro]
## Description:
The mission of Geronimo is the creation and maintenance of software related to
Java2, Enterprise Edition (J2EE) container
## Project Status:
Current project status: the project is at risk due to the lack of resources
(most committers also are committers on other projects). MicroProfile
implementations haven't been updated and most project switched to other
implementations. The specifications part used to be included widely at Apache,
but since Jakarta is now under Apache license, most projects use them. We
have a few tools left used and maintained such as BatchEE, XBean, Arthur,
Transaction Manager and Mail. Since that's the only left, it might be better
to find a another home for them. Issues for the board: No issue requiring
board attention.
## Membership Data:
Apache Geronimo was founded 2004-05-26 (19 years ago)
There are currently 71 committers and 41 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:2.
Community changes, past quarter:
- No new PMC members. Last addition was Francois Papon on 2021-03-09.
- No new committers. Last addition was Francois Papon on 2021-03-09.
## Project Activity:
The project went quiet for a few months. A lot of committers are currently
working on other projects like Apache TomEE, Apache OpenJPA, Apache
OpenWbeBeans, Apache BVal to name a few. We have done some maintenance
releases as follow
- xbean-4.23 was released on 2023-05-19.
- arthur 1.0.6 was released on 2023-04-21.
- geronimo-mail_2.1_mail-1.0.0 was released on 2022-06-23.
## Community Health:
One person only under radar but again the amount of contributions is too low to
move him to a committer.
-----------------------------------------
Attachment AA: Report from the Apache Giraph Project [Dionysios Logothetis]
-----------------------------------------
Attachment AB: Report from the Apache Griffin Project [William Guo]
-----------------------------------------
Attachment AC: Report from the Apache Hadoop Project [Wei-Chiu Chuang]
## Description:
The mission of Hadoop is the creation and maintenance of software related to
Distributed computing platform
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache Hadoop was founded 2008-01-16 (16 years ago)
There are currently 242 committers and 124 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 Mukund Thakur on 2023-01-21.
- No new committers. Last addition was Shilun Fan on 2022-11-22.
## Project Activity:
Recent releases:
3.3.6 was released on 2023-06-25.
3.3.5 was released on 2023-03-23.
3.3.4 was released on 2022-08-08.
## Community Health:
- Mailing list activity:
common-dev@hadoop.apache.org had a 2% increase in traffic in the past quarter
(529 emails compared to 518)
common-issues@hadoop.apache.org had a 7% increase in traffic in the past quarter
(5700 emails compared to 5309)
dev@hadoop.apache.org had a 500% increase in traffic in the past quarter
(6 emails compared to 1):
hdfs-dev@hadoop.apache.org had a 11% increase in traffic in the past quarter
(494 emails compared to 444)
hdfs-issues@hadoop.apache.org had a 27% increase in traffic in the past quarter
(2040 emails compared to 1603)
mapreduce-dev@hadoop.apache.org had a 0% increase in traffic in the past quarter
(297 emails compared to 297)
mapreduce-issues@hadoop.apache.org had a 24% increase in traffic in the past quarter
(116 emails compared to 93)
user@hadoop.apache.org had a 10% decrease in traffic in the past quarter
(28 emails compared to 31):
yarn-dev@hadoop.apache.org had a 9% increase in traffic in the past quarter
(409 emails compared to 372)
yarn-issues@hadoop.apache.org had a 19% increase in traffic in the past quarter
(1189 emails compared to 992)
- JIRA activity:
277 issues opened in JIRA, past quarter (8% increase)
238 issues closed in JIRA, past quarter (29% increase)
- Commit activity:
532 commits in the past quarter (53% increase)
75 code contributors in the past quarter (13% increase)
- GitHub PR activity:
288 PRs opened on GitHub, past quarter (11% increase)
271 PRs closed on GitHub, past quarter (34% increase)
In the recent board report feedback, some board members worried about 'a 100%
decrease in dev-list activity does sound quite serious'. We try to check it
and only happens for dev@hadoop.apache.org, the reason is that there are
several separate dev-list for every hadoop project sub-modules, and only few
people use this mailing list thus triffic of dev@hadoop.apache.org is big
moves, we are discussing if need to remove this dev-list, other sub-modules
dev-list traffic works actively.
We even added hadoop-api-shim as a sub-project in a new repo under hadoop:
https://github.com/apache/hadoop-api-shim
-----------------------------------------
Attachment AD: Report from the Apache HAWQ Project [Lei Chang]
-----------------------------------------
Attachment AE: Report from the Apache HBase Project [Duo Zhang]
## Description:
Apache HBase is an open-source, distributed, versioned, non-relational
database. Apache HBase gives you low latency random access to billions of rows
with millions of columns atop non-specialized hardware.
hbase-thirdparty is a set of internal artifacts used by the project to
mitigate the impact of our dependency choices on the wider ecosystem.
hbase-connectors is a collection of integration points with other projects.
The initial release includes artifacts for use with Apache Kafka and Apache
Spark.
hbase-filesystem contains HBase project-specific implementations of the Apache
Hadoop FileSystem API. It is currently experimental and internal to the
project.
hbase-operator-tools is a collection of tools for HBase operators. Now it is
mainly for hosting HBCK2.
hbase-native-client is a client library in C/C++, in its early days.
hbase-kustomize is for deploying HBase on kubernetes, still under development.
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache HBase was founded 2010-04-21 (13 years ago)
There are currently 103 committers and 58 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 Tak-Lon Wu on 2023-01-29.
- Nihal Jain was added as committer on 2023-04-29
## Project Activity:
Recent releases:
2.5.5 was released on 2023-06-13.
3.0.0-alpha-4 was released on 2023-06-07.
2.5.4 was released on 2023-04-14.
In the recent board report feedback, a board member suggested that we'd better
filter out the jira notification email from the dev list, otherwise it is
really hard to find out useful information. So we started a discussion thread
in the dev list about this, and the community members prefered to keep it as
is. We only send open/close notifications to the dev list and it is useful to
keep informed about what's happening.
https://lists.apache.org/thread/0wo98q9j93mkvn61wcwppwhkgfjm7mdn
We successfully held an online meet up on 04/19/2023, and discussed many
interesting topics.
https://lists.apache.org/thread/ostq5zqx96s7c2g3mdflvtzj6781orsh
We moved the stable pointer to 2.5.x.
https://lists.apache.org/thread/5crkzzxcnb471w4p0wqhppmjmln66pkd
We finally resolved all pending big features for 3.x and cut branch-3.
https://lists.apache.org/thread/np9bkln30zqm50k332h8bsjrtgzr9691
For better support for deploying HBase on top of kubernetes, we decided to
introduce a new repository for the kustomize files.
https://lists.apache.org/thread/wc0hs5pmhrcczox4ddl0942pd59sho6x
We submitted a presentation 'What's new in the recent and upcoming HBase
releases' to Community Over Code Asia 2023.
https://lists.apache.org/thread/fk1tr0sfk3zwbxxqcol3sbqz81mfdmrx
https://issues.apache.org/jira/browse/HBASE-27910
## Community Health:
- Mailing list activity:
dev@hbase.apache.org:
958 subscribers(959 in the previous quarter)
490 emails sent to list(595 in the previous quarter)
user@hbase.apache.org:
1990 subscribers(1987 in the previous quarter)
42 emails sent to list(43 in the previous quarter)
user-zh@hbase.apache.org
78 subscribers(78 in the previous quarter)
50 emails sent to list(43 in the previous quarter)
- JIRA activity:
183 issues opened in JIRA, past quarter (-17% change)
138 issues closed in JIRA, past quarter (-14% change)
- Commit activity:
579 commits in the past quarter (-1% decrease)
40 code contributors in the past quarter (-23% change)
- GitHub PR activity:
179 PRs opened on GitHub, past quarter (-21% change)
149 PRs closed on GitHub, past quarter (-36% change)
We are pleased to announce the long-awaited release of 3.0.0-alpha-4 and the
completion of branch-3. This represents a significant milestone in the
progress towards the final release of 3.0.0. In the 2.6.0 release, we have
successfully addressed multiple issues; however, there is still one critical
problem remaining. Under high load conditions, the server may encounter
out-of-memory errors if TLS is enabled. Fortunately, we have already
identified potential solutions, and we are optimistic that we will be able to
release 2.6.0 in the coming months.
-----------------------------------------
Attachment AF: Report from the Apache Incubator Project [Justin Mclean]
# Incubator PMC report for July 2023
The Apache Incubator is the entry path into the ASF for projects and
codebases wishing to become part of the Foundation's efforts. 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 25 podlings incubating.
This month we were missing reports from Annotator, Liminal, Pony Mail and
Toree. Kvrocks has graduated, and there are no new proposals to the board
for graduation. podlings executed 3 distinct releases. Discussion on the
general list have mostly been about podling releases.
## Community
### New IPMC members:
- None
### People who left the IPMC:
- None
## New Podlings
- None
## Podlings that failed to report, expected next month
- Annotator
- Liminal
- Pony Mail
- Toree
## Graduations
- Kvrocks
The board has motions for the following:
- None
## Releases
The following releases entered distribution during the month of
June:
- OpenDAL 0.37.0
- Paimon 0.4.0
- Streampark 2.1.1
## IP Clearance
- None
## Legal / Trademarks
- N/A
## Infrastructure
- N/A
## Table of Contents
[DataLab](#datalab)
[HugeGraph](#hugegraph)
[Liminal](#liminal)
[Livy](#livy)
[Milagro](#milagro)
[Pegasus](#pegasus)
[Pekko](#pekko)
[Pony Mail](#pony mail)
[Teaclave](#teaclave)
[Training](#training)
--------------------
## DataLab
DataLab is a platform for creating self-service, exploratory data science
environments in the cloud using best-of-breed data science tools.
DataLab has been incubating since 2018-08-20.
### Three most important unfinished issues to address before graduating:
1.
2.
3.
### Are there any issues that the IPMC or ASF Board need to be aware of?
No, there aren't any issues.
### How has the community developed since the last report?
New Commiitter, Yevhenii Vlasiuk
### How has the project developed since the last report?
In retirement discussion.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [ ] Working towards first release
- [ ] Community building
- [ ] Nearing graduation
- [X] Other: In retirement discussion
### Date of last release:
2022-11-30
### When were the last committers or PPMC members elected?
The last committer was added on April 10, 2023
### Have your mentors been helpful and responsive?
Yes, our mentors are helpful and responsive.
### Is the PPMC managing the podling's brand / trademarks?
Brand and naming issues are absent.
### Signed-off-by:
- [ ] (datalab) P. Taylor Goetz
Comments:
- [ ] (datalab) Henry Saputra
Comments:
- [ ] (datalab) Furkan Kamaci
Comments:
### IPMC/Shepherd notes:
--------------------
## HugeGraph
A large-scale and easy-to-use graph database
HugeGraph has been incubating since 2022-01-23.
### Three most important unfinished issues to address before graduating:
1. Release distributed storage module (include PD/store) & make graph
computer easy to use
2. Overall easier to use, more stable and reliable & more communication
with other Graph Community(Like Tinkerpop/JanusGraph etc)
3. At least 2 new PPMC & 5 committers selected and take deep part in the
community
### Are there any issues that the IPMC or ASF Board need to be aware of?
None
### How has the community developed since the last report?
1. We take part in 2 activities to let more students know the project &
the open source culture (working in the next Q3)
2. We take part in GOTC(Global Open-source Technology Conference) & share
our roadmap of next version (about distributed raft-based storage)
3. 10+ new contributors with 60+ PR (although most of the PR is tiny or
doc improvement, it helped a lot for normal users)
### How has the project developed since the last report?
1. Finish i18n translation task in all pages & enhance/update a string of
docs
2. Add more user friendly improvement case & update the experience of
docker usage
3. Support multi tasks scheduled by server & fix some bugs in
Spark-Loading mode in toolchain
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [X] Initial setup
- [X] Working towards first release
- [X] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
2023-02-22
### When were the last committers or PPMC members elected?
2023-03-12 (last committer)
### Have your mentors been helpful and responsive?
No issues to report now
### Is the PPMC managing the podling's brand / trademarks?
None
### Signed-off-by:
- [ ] (hugegraph) Lidong Dai
Comments:
- [ ] (hugegraph) Trista Pan
Comments:
- [ ] (hugegraph) Xiangdong Huang
Comments:
- [ ] (hugegraph) Yu Li
Comments:
- [X] (hugegraph) Willem Ning Jiang
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. Get 0.8.0 release out and release process clearly documented
2. More community engagement
3.
### Are there any issues that the IPMC or ASF Board need to be aware of?
None at this time.
### How has the community developed since the last report?
The community has been growing with new
### How has the project developed since the last report?
### How would you assess the podling's maturity?
Please feel free to add your own commentary.contributors and
- [ ] Initial setup
- [ ] Working towards first release
- [ ] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
2021-02-04
### When were the last committers or PPMC members elected?
2023-02-10
### Have your mentors been helpful and responsive?
No issues at the moment.
### Is the PPMC managing the podling's brand / trademarks?
No answer.
### Signed-off-by:
- [ ] (livy) Bikas Saha
Comments:
- [ ] (livy) Luciano Resende
Comments:
- [ ] (livy) Jean-Baptiste Onofré
Comments:
- [ ] (livy) Madhawa Kasun Gunasekara
Comments:
- [X] (livy) Larry McCay
Comments: ### IPMC/Shepherd notes:
--------------------
## Milagro
Milagro is core security infrastructure and crypto libraries for
decentralized networks and distributed systems.
Milagro has been incubating since 2015-12-21.
### Three most important unfinished issues to address before graduating:
1. Introduce policies for correct corporate involvement (see
https://github.com/orgs/apache/projects/171/views/1)
2. Continue to build relevant and useful crypto libraries and
applications for decentralized networks in order to grow the ecosystem of
users and contributors to the project.
3. Improve automated quality pipelines, improve existing releases and
demonstrate improved compliance with the Apache Way.
### Are there any issues that the IPMC or ASF Board need to be aware of?
No issues are known as of now.
### How has the community developed since the last report?
A new contributor started to submit patches. No big changes otherwise.
### How has the project developed since the last report?
- The path to graduation map has been updated [in a GitHub
project](https://github.com/orgs/apache/projects/171/views/1). This map is
our north start to lead us to graduation.
- New issues have been opened on the AMCL repo to open the roadmap
- Project committees are working to implement CG21
- No major bugs have been reported in the MPC release hopefully
indicating good code quality
### 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:
2022-11-11
### When were the last committers or PPMC members elected?
December 2022
### Have your mentors been helpful and responsive?
Yes
### Is the PPMC managing the podling's brand / trademarks?
No third party are using the brand's name incorrectly
### Signed-off-by:
- [ ] (milagro) Nick Kew
Comments:
- [X] (milagro) Jean-Frederic Clere
Comments:
### IPMC/Shepherd notes:
--------------------
## Pegasus
Pegasus is a distributed key-value storage system which is designed to be
simple, horizontally scalable, strongly consistent and high-performance.
Pegasus has been incubating since 2020-06-28.
### Three most important unfinished issues to address before graduating:
1. Grow the community(attracting more committers, contributors, users).
2. Make more releases in ASF policy regularly.
3. Improve the Pegasus project performance, stability, and usage
scenarios.
### 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?
An offline meetup has been held on May 16th, 2023 in Beijing, China.
### How has the project developed since the last report?
2.5.0 release is being prepared.
### 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:
2022-11-05
### When were the last committers or PPMC members elected?
2022-5-12, committer: Yifan Zhang(GitHub ID: zhangyifan27)
### Have your mentors been helpful and responsive?
Yes, our mentors gave us a lot of help, including version release,
holding meetup and etc.
### Is the PPMC managing the podling's brand / trademarks?
No issues that we are aware of.
### Signed-off-by:
- [X] (pegasus) Duo Zhang
Comments: Still, let's try to make more patch releases, instead of
just a big release after half a year...
- [ ] (pegasus) Liang Chen
Comments:
- [ ] (pegasus) Von Gosling
Comments:
- [ ] (pegasus) Liu Xun
Comments:
### IPMC/Shepherd notes:
--------------------
## Pekko
Pekko is a toolkit and an ecosystem for building highly concurrent,
distributed, reactive and resilient applications for Java and Scala.
Pekko has been incubating since 2022-10-24.
### Three most important unfinished issues to address before graduating:
1. Complete the work to mention all 3rd party source in the Pekko code
base.
2. Get a milestone release done - at least for the core modules. This
would facilitate the wider OSS community. We would hope that other OSS
projects that currently support Akka would look to also support Apache
Pekko.
3. Community Building.
### Are there any issues that the IPMC or ASF Board need to be aware of?
Nothing of note
### How has the community developed since the last report?
Community engagement is pretty low. We're hoping it will pick up if we
get a release out.
### How has the project developed since the last report?
We're close to getting a release done for the core modules.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [X] Working towards first release
- [X] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
None yet.
### When were the last committers or PPMC members elected?
2023-03-09 (new committer) -- no new PPMC members added
### Have your mentors been helpful and responsive?
There were some knotty issues to discuss about how to manage the license
headers and similar issues but the conversations were very constructive.
### Is the PPMC managing the podling's brand / trademarks?
VP, Brand has approved the name (https://s.apache.org/h2cwg)
### Signed-off-by:
- [X] (pekko) PJ Fanning
Comments:
- [X] (pekko) Justin McLean
Comments:
- [ ] (pekko) Roman Shaposhnik
Comments:
- [ ] (pekko) Wu Sheng
Comments:
- [ ] (pekko) Ryan Skraba
Comments:
- [ ] (pekko) JB Onofré
Comments:
- [ ] (pekko) Claude Warren
Comments:
### IPMC/Shepherd notes:
--------------------
## Teaclave
Teaclave is a universal secure computing platform.
Teaclave has been incubating since 2019-08-20.
### Three most important unfinished issues to address before graduating:
1. Grow the community (attracting more committers, contributors, users)
2. Publish Apache releases
3. Keep the project up-to-date with latest hardwares
### Are there any issues that the IPMC or ASF Board need to be aware of?
None.
### How has the community developed since the last report?
1. He Sun (Apache ID: hsun) was added to the PPMC
2. The Java SDK team gave a presentaion on The Global Open-source
Technology Conference (GOTC) 2023.
### How has the project developed since the last report?
Teaclave FaaS platform released 0.5.1 version. The 0.6.0 releaes is under
voting.
### 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-05-31
### When were the last committers or PPMC members elected?
2023-05-15
### Have your mentors been helpful and responsive?
Yes.
### Is the PPMC managing the podling's brand / trademarks?
Yes.
### Signed-off-by:
- [ ] (teaclave) Felix Cheung
Comments:
- [ ] (teaclave) Furkan Kamaci
Comments:
- [ ] (teaclave) Jianyong Dai
Comments:
- [ ] (teaclave) Matt Sicker
Comments:
- [ ] (teaclave) Zhijie Shen
Comments:
- [ ] (teaclave) Gordon King
Comments:
### IPMC/Shepherd notes:
--------------------
## Training
The Training project aims to develop resources which can be used for
training purposes in various media formats, languages and for various Apache
and non-Apache target projects.
Training has been incubating since 2019-02-21.
In June, we started adjusting the project goals.
Besides a pure focus on content creation tools we have identified the need
for two additional aspects:
(1) For ASF processes some documentation exists, e.g.
https://community.apache.org/contributor-ladder,
but the ASF member journey is still a challenge for many new members,
especially those with less coding experience.
As a solution it has been suggested to provide training material for the
following problems:
* You've just graduated to a TLP. What are the challenges you will now face?
* New committer onboarding
* New PMC member onboarding
* New PMC Chair onboarding
* New board member onboarding
(2) Creation of some general recommendations/guidelines for:
* managing/validation of training material contributions of arbitrary ASF
projects has been proposed.
Initial discussion of the topics have been started.
We expand our focus now on the following aspects:
We have to work on strategies to increase the participation and the
visibility of the project and its goals.
Besides requests for contributions from individual contributors from other
Apache projects we want to show what the Apache Training project can offer
to those projects.
We should build on the assumption that synergy and network effects can help
us to increase the community around training and skill management topics.
### Three most important unfinished issues to address before graduating:
1. Improve the community participation (other Apache projects should
actively be linked to this project, since they "have the content")
2. (Re)define the short-, mid-, and long-term goals of the project.
3. Review current policies around contribution review and releases to
find a pragmatic compromise
### Are there any issues that the IPMC or ASF Board need to be aware of?
The topic of retiring the project has been discussed multiple times but
someone (Mirko) from the community
has stepped up in a last effort to revive activities.
He's written most of the last two or three reports.
At least one mentor has mentioned that he'd step down if those attempts
are not successful.
### How has the community developed since the last report?
Activity has started to grow since the last report.
We again failed to provide the report on time, but this will change soon.
Two persons joined our conversation on the dev-list (Eric and Rich).
### How has the project developed since the last report?
Creation of a ASF onboarding training module has been announced.
A tool for inspecting documentation in Github repositories (ASF projects)
which will lead towards automatic training related content extraction has
been started.
PR activity continues on a low level since the last report.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [ ] Initial setup
- [ ] Working towards first release
- [X] Community building: The community is very small and attempts of
growing it have failed so far
- [ ] Other:
### Date of last release:
Not applicable
### When were the last committers or PPMC members elected?
November 2020
### Have your mentors been helpful and responsive?
Mentors have been responsive and helpful when reached out to.
### Is the PPMC managing the podling's brand / trademarks?
The name search process has not yet been started, as there is still time
to do that if and when graduation draws nearer.
The PPMC is actively monitoring usage of the Podlings current name on
other sites.
The Podling is not directly affiliating with any sponsors donating
content and presenting an independent image on the webpage.
### Signed-off-by:
- [ ] (training) Craig Russell
Comments:
- [ ] (training) Christofer Dutz
Comments:
- [X] (training) Justin Mclean
Comments:
- [X] (training) Lars Francke
Comments:
### IPMC/Shepherd notes:
Dave Fisher - this project does not really release software and it looks
like it is becoming more of an ASF Member Project.
I think that since it plans to document process that is more
traditionally part of ComDev's mission or related to helping
projects. I would support either graduating into ComDev or to a TLP as a
project similar to Whimsy. I really do not see
further Incubation to be helpful.
-----------------------------------------
Attachment AG: Report from the Apache InLong Project [Charles Zhang]
## Description:
The mission of Apache InLong is the creation and maintenance of software
related to a one-stop, full-scenario data integration framework that
provides automatic, secure, and reliable data transmission capabilities.
InLong supports both batch and stream data processing at the same time,
which offers great power to build data analysis, modeling, and other
real-time applications based on streaming data.
## Project Status:
Current project status: Ongoing, with moderate activity.
Issues for the board: There are no issues requiring board attention at this
time.
## Membership Data:
Apache InLong was founded 2022-06-15 (a year ago)
There are currently 45 committers and 26 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 Yunqing Mo on 2023-01-18.
- Zuofeng Zhang was added as committer on 2023-06-17
- Haif Xu was added as committer on 2023-05-10
- Wenkai Fu was added as committer on 2023-05-02
## Project Activity:
In the past quarter, InLong has successively released 1.7.0, and the project is
working on 1.8.0 now, which will be released next week. For the coming 1.8.0,
it close about 230 issues, including 8+ major features and 60+ optimizations,
for example:
- Add `full-scenario` for the project description
- Support multi-tenancy
- Support data preview
- Split data synchronization feature
And there is no meetups and conferences in the past quarter.
## Community Health:
The community health looks good overall. In the latest month,
- 6 new code contributors contributed to the project (142 in total).
- 131 commits to master (+15% increase).
- 29 active contributors (-6.4% decrease).
- 139 PRs opened on GitHub (+9.4% increase).
- 150 issues closed on GitHub (+12.7% increase).
The community is improving the project ecosystem and capabilities
through fixed-period version releases, and will enhance the project's
influence through some activities in the future.
-----------------------------------------
Attachment AH: Report from the Apache James Project [Benoit Tellier]
## Description:
The Apache James Project delivers a rich set of open source modules and
libraries, written in Java, related to Internet mail which build into an
advanced extensible mail server running on the JVM.
## Project Status:
Current project status: Ongoing, moderate activity.
Issues for the board: There are no issues
requiring board attention at this time.
## Membership Data:
Apache James was founded 2003-01-22 (20 years ago)
There are currently 42 committers and 17 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
Community changes, past quarter:
- No new PMC members. Last addition was Karsten Otto on 2022-09-20.
- No new committers. Last addition was Jean Helou on 2022-06-17.
## Project Activity:
Recent releases:
- JAMES-3.8.0 was released on 2023-05-30.
- JAMES-3.7.4 was released on 2023-03-31.
- JAMES-3.7.3 was released on 2023-01-06.
## Community Health:
We saw a sharp increase in mailing list exchanges this quarter:
- server-dev@james.apache.org had a 21% increase in traffic in the past
quarter (284 emails compared to 234)
- server-user@james.apache.org had a 229% increase in traffic in the past
quarter (112 emails compared to 34)
These exchanges resulted in some users contributions.
Code metrics (JIRA ticket, commits, contributor diversity) is stable.
-----------------------------------------
Attachment AI: Report from the Apache jclouds Project [Andrew Gaul]
There are no issues requiring board attention
A cloud-agnostic library that enables developers to access a variety of cloud
providers using one API.
== Project Status ==
During the last months, we initiated discussions to move the project to the
Attic, given the low activity and the concerns shared in previous reports.
The discussion started in October 2022 (https://s.apache.org/jclouds-attic)
and the Brooklyn and Karaf communities expressed interest in keeping the
project alive and helping the project. Despite the very welcomed good
intentions, however, nothing actually happened in the form of actual
contributions, further engagement with the project, etc, and for months we
have been just waiting for something to happen beyond the will to keep the
project alive.
The Attic discussion is a perfect example of the current status of the jclouds
community: there are people interested in keeping the project alive, but no
one has the time and/or energy to actually do it, and in this scenario, it has
been discussed that we would probably better serve the community by moving the
project to the Attic and set clear expectations for our users, instead of
keeping it in the current limbo of inactivity.
== Community ==
Last committer: 2018-07-23 (Daniel Estevez)
Last PMC member: 2021-03-14 (Jean-Baptiste Onofré)
== Community Objectives ==
Finalize the Attic movement discussion and release 2.6.0 in July 2023
which is planned to be the final release.
== Releases ==
The last major jclouds release, 2.5.0, took place on 2022-03-26.
The last bugfix release, 2.2.1, took place on 2020-05-14.
-----------------------------------------
Attachment AJ: Report from the Apache Jena Project [Andy Seaborne]
## Description:
The mission of Jena is the creation and maintenance of software related to
Java framework for building Semantic Web applications
## Project Status:
Current project status: Ongoing Issues for the board: none
## Membership Data:
Apache Jena was founded 2012-04-18 (11 years ago) There are currently 18
committers and 13 PMC members in this project. The Committer-to-PMC ratio is
roughly 9:7.
Community changes, past quarter:
- No new PMC members. Last addition was Aaron Coburn on 2019-01-22.
- Arne Bernhardt was added as committer on 2023-07-11.
## Project Activity:
The project added Arne Bernhardt as a new committer.
The project released version 4.8.0 on 2023-April-23 and 4.9.0 on 2023-July-08.
Both releases included addressing security issues.
The project is discussing version 5.0.0. There are two external changes in the
Java ecosystem that affect the project - a new LTS version (the project policy
is to support the last two LTS versions of Java) and the J2EE javax to jakarta
package transition. The project may make other incompatible changes that
affect Jena users who use the project as a code library.
## Community Health:
One part of 4.9.0 is a significant contribution to re-implement the in-memory
graphs. At the same time, the new implementations follow the W3C standards as
closely as possible. In 4.9.0, the new implementations are "opt-in". Whether
they become the default at 5.0.0 is not yet decided.
-----------------------------------------
Attachment AK: Report from the Apache JMeter Project [Bruno Demion]
## Description:
The mission of JMeter is the creation and maintenance of software related to
Java performance and functional testing
## Project Status:
Current project status: Ongoing, with moderate activity
Issues for the board: There are no issues requiring board attention at this
time.
## Membership Data:
Apache JMeter as TLP was created 2011-10-26 (12 years ago), before was Apache
Jakarta JMeter, first version was released 1998-12-15 (25 years ago)
There are currently 13 committers and 8 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 Vladimir Sitnikov on 2018-06-08.
- No new committers. Last addition was Maxime Chassagneux on 2017-02-15.
## Project Activity:
- The project has release (today) the last version with Java 8 support. Next
release will support Java 11 or later.
- So, the project will start to move code for Java 11+ for next weeks/months
- The project discuss to use GitHub Actions for automate upgrade dependencies
using a bot
- The project have start to discuss to use the Automated Release Signing with
GitHub Actions. Main objective is to have a quick release cycle.
- Recent releases:
5.6.2 final was released on 2023-07-11. (fix regression release)
5.6.1 final was released on 2023-07-10.
5.6 final was released on 2023-06-23.
5.5 final was released on 2022-06-14.
## Community Health:
- The project has a high activity during last quarter, because the project has
prepare and release 3 versions of JMeter.
-----------------------------------------
Attachment AL: Report from the Apache Johnzon Project [Jean-Louis Monteiro]
## Description:
The mission of Johnzon is the creation and maintenance of software related to
JSR-353 compliant JSON parsing; modules to help with JSR-353 as well as JSR-374
and JSR-367
## Project Status:
Current project status: project is healthy and stable. The Jakarta
implemention for EE 10 is almost done. We even got some help from a new
contributor. In parallel community is still providing patches and backporting
to latest javax based implementation. Issues for the board: no issue for the
board.
## Membership Data:
Apache Johnzon was founded 2016-04-20 (7 years ago)
There are currently 8 committers and 6 PMC members in this project.
The Committer-to-PMC ratio is 4:3.
Community changes, past quarter:
- No new PMC members. Last addition was Reinhard Sandtner on 2016-08-30.
- No new committers. Last addition was Jonathan Gallimore on 2018-05-09.
## Project Activity:
As mentioned, most of the effort is focused on the EE 10 compatible
implementation which is 90% done. But as you can see, we do issue regular
maintenance release for the latest javax based implementation. We also got one
security request that resulted in an accepted CVE. We fixed, released and CVE
has been disclosed per Apache process.
- 1.2.21 was released on 2023-06-27.
- 1.2.20 was released on 2023-04-20.
- 1.2.19 was released on 2022-08-17.
## Community Health:
We haven't noticed new potential committers. We had a few contributors, but
not enough to have the conversation.
-----------------------------------------
Attachment AM: Report from the Apache JSPWiki Project [Juan Pablo Santos Rodríguez]
-----------------------------------------
Attachment AN: Report from the Apache Kudu Project [Andrew Wong]
-----------------------------------------
Attachment AO: Report from the Apache Kvrocks Project [Hulk Lin]
## Description:
The mission of Apache Kvrocks is the creation and maintenance of software
related to a distributed key-value NoSQL database, supporting the rich data
structure
## Project Status:
Current project status: New
Issues for the board: There are no issues requiring board attention
## Membership Data
Apache Kvrocks was founded on 2023-06-21 (19 days ago) There are currently 19
committers and 10 PMC members in this project. The Committer-to-PMC ratio is
roughly 5:3.
Community changes, past quarter:
- No new PMC members (project graduated recently).
- No new committers were added
## Project Activity:
- The community is voting on the release 2.5.0
- Recent releases: Kvrocks 2.4.0 was released on 2023-05-06
- Submitted a topic in 2023 ApacheCon Asia Beijing
- Two candidate votes(Aleks Lozovyuk and mwish) have been passed and mwish has
accepted the invitation
For the development plans, the community is working:
- Building the controller and Kubernetes operator for Kvrocks, to make it
easier to maintain and deploy
- Support more Redis data structures and commands in Kvrocks like BloomFilter
and JSON to fulfill more user requirements
## Community Health:
Overall community health is good. We have done well in the code contributors
and issues, but the dev traffic has been a bit decreased, which is possibly
due to we are preparing for the graduate process. I think the dev traffic be
back after July.
- builds@kvrocks.apache.org had a 49% increase in traffic in the past quarter
(309 emails compared to 207)
- dev@kvrocks.apache.org had a 156% increase in traffic in the past quarter
(64 emails compared to 25)
- issues@kvrocks.apache.org had a 61% increase in traffic in the past quarter
(1847 emails compared to 1143)
- 132 commits in the past quarter (-18% change)
- 31 code contributors in the past quarter (55% increase)
- 138 PRs opened on GitHub, past quarter (-15% change)
- 127 PRs closed on GitHub, past quarter (-25% change)
- 69 issues opened on GitHub, past quarter (53% increase)
- 58 issues closed on GitHub, past quarter (45% increase)
-----------------------------------------
Attachment AP: Report from the Apache Libcloud Project [Tomaž Muraus]
-----------------------------------------
Attachment AQ: Report from the Apache Lucene.Net Project [Shad Storhaug]
-----------------------------------------
Attachment AR: Report from the Apache MADlib Project [Ed Espino]
## Description
Apache MADlib is an open-source library for scalable in-database analytics.
It provides data-parallel implementations of mathematical, statistical,
graph and machine learning methods for structured and unstructured data.
## Project Status
- The project completed a major (2.0.0) release. This is an important
milestone for the project.
- The project is maintaining a healthy Jira issue management level.
- There are no issues requiring board attention at this time.
## Membership Data
Apache MADlib was founded 2017-07-18 (6 years ago)
There are currently 23 committers and 12 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
## Project Activity
* v2.0.0 was released on 2023-06-23
* New features
- Build: Add support for python3
- Build: Add support for GP7 Beta, GP6 python3 extension, Postgres 13/14/15
* Improvements
- XGBoost: Add support for version 1.7.5
- DL: Add support for tensorflow 2.10.1 and keras 2.10.0
- DBScan: Add support for rtree 1.0.1
** Release Manager
Ed Espino served in the release manager capacity.
** Vote Results
The vote for releasing Apache MADlib 2.0.0 (RC1) passed with 4 binding
+1s and no 0 or -1 votes.
* Upgrading from MADlib 1.X to MADlib 2.X is not supported.
## Community Health
* We continue to have good voting participation from the newly formed
PMC members.
* The dev community has started discussions on expanding the Apache
MADlib adoption by discussing various projects (PostgreSQL, other
PostgreSQL compliant backends - e.g. https://neon.tech/).
-----------------------------------------
Attachment AS: Report from the Apache Mahout Project [Andrew Musselman]
## Description:
Apache Mahout is a distributed linear algebra framework with a math DSL
designed to let mathematicians, statisticians, and data scientists quickly
implement their own algorithms.
## Project Status:
Current project status: A slow quarter with team members' family
obligations
Issues for the board: None
## Membership Data:
Apache Mahout was founded 2010-04-20 (13 years ago)
There are currently 29 committers and 11 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 Shannon Quinn on 2023-02-12.
- No new committers. Last addition was Jowanza Joseph on 2023-03-02.
## Project Activity:
Slowed on community meetings and project planning, but we have a structure in
place.
## Community Health:
Similar to last quarter, same core team is in touch with each other and we
will pick back up on community calls this month.
-----------------------------------------
Attachment AT: Report from the Apache Maven Project [Karl Heinz Marbaise]
## Description:
The mission of Maven is the creation and maintenance of software related to
Java project management and comprehension tools
## Project Status:
There are no issues requiring board attention.
## Membership Data:
Apache Maven was founded 2003-03-01 (20 years ago)
There are currently 69 committers and 26 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 Sylwester Lachiewicz on 2023-03-21.
- No new committers. Last addition was Aleksandr Ashitkin on 2023-04-06.
## Project Activity:
Maven Fluido Skin 1.12.0 was released on 2023-07-06.
Maven Reporting API 4.0.0-M7 was released on 2023-07-06.
Apache Maven 3.9.3 was released on 2023-06-26.
Maven Resolver 1.9.13 was released on 2023-06-23.
Maven Doxia 2.0.0-M7 was released on 2023-06-21.
Maven Clean Plugin 3.3.1 was released on 2023-06-20.
Maven Resolver 1.9.12 was released on 2023-06-19.
Maven Indexer 7.0.3 was released on 2023-06-16.
Maven Resolver 1.9.11 was released on 2023-06-16.
Maven Shade Plugin 3.5.0 was released on 2023-06-16.
Maven Parent POMs 40 was released on 2023-06-12.
Apache Parent POM 30 was released on 2023-06-11.
Maven Invoker Plugin 3.6.0 was released on 2023-06-11.
Maven WAR Plugin 3.4.0 was released on 2023-06-11.
Apache Maven Build Cache Extension 1.0.1 was released on 2023-06-09.
Maven Project Info Reports Plugin 3.4.5 was released on 2023-06-03.
Maven Surefire 3.1.2 was released on 2023-06-03.
Maven Release 3.0.1 was released on 2023-05-30.
Maven Project Info Reports Plugin 3.4.4 was released on 2023-05-26.
Maven Checkstyle Plugin 3.3.0 was released on 2023-05-19.
Maven Dependency Plugin 3.6.0 was released on 2023-05-19.
Maven SCM 2.0.1 was released on 2023-05-18.
Maven Source Plugin. 3.3.0 was released on 2023-05-17.
Maven Indexer 7.0.2 was released on 2023-05-12.
Maven PMD Plugin 3.21.0 was released on 2023-05-12.
Maven Plugin Tools 3.9.0 was released on 2023-05-12.
Apache Maven 3.9.2 was released on 2023-05-11.
Maven Assembly Plugin 3.6.0 was released on 2023-05-11.
Maven Shared Utils 3.4.2 was released on 2023-05-11.
Maven Remote Resources Plugin 3.1.0 was released on 2023-05-08.
Maven GPG Plugin 3.1.0 was released on 2023-05-06.
Maven Resolver 1.9.10 was released on 2023-05-05.
Maven Surefire 3.1.0 was released on 2023-05-05.
Maven Dependency Analyzer 1.13.2 was released on 2023-05-01.
Maven Shared Utils 3.4.1 was released on 2023-04-30.
Maven Site Plugin 4.0.0-M8 was released on 2023-04-29.
Maven Doxia Sitetools 2.0.0-M10 was released on 2023-04-26.
Maven Fluido Skin 2.0.0-M6 was released on 2023-04-26.
Maven Reporting Exec 2.0.0-M8 was released on 2023-04-26.
Maven Reporting Impl 2.0.0-M8 was released on 2023-04-26.
Maven Checkstyle Plugin 3.2.2 was released on 2023-04-18.
Maven Plugin Tools 3.8.2 was released on 2023-04-18.
Maven Resolver 1.9.8 was released on 2023-04-16.
Maven Doxia Sitetools 2.0.0-M8 was released on 2023-04-15.
Maven Project Info Reports Plugin 3.4.3 was released on 2023-04-15.
Maven Reporting Exec 2.0.0-M7 was released on 2023-04-15.
Maven Reporting Impl 2.0.0-M7 was released on 2023-04-15.
Maven Shared Jar 3.0.0 was released on 2023-04-15.
Maven Dependency Analyzer 1.13.1 was released on 2023-04-12.
Based on the current ongoing effort we have reached the version 4.0.0
(alpha-7) of Apache Maven and getting a number of reports about issues.
The acceptances rate in the wild is low as expected because people
tend not to use alpha releases.
The Apache Maven 3.9.X-Release-Line is intended as an intermediate
step to integrate some needed (possibly) breaking changes for Apache
Maven 4.0.0 into the wild. A lot of our own plugins have
been upgraded in the meantime.
## Community Health:
On the users list as well as on the dev list we can observe
an decrease of activity. The decrease in activity on
JIRA issue list might be related to github issue usages
which corolates with the JIRA issue activity.
Also in general very active community on the mailing list
as well as on the slack channels.
-----------------------------------------
Attachment AU: Report from the Apache Mesos Project [Qian Zhang]
-----------------------------------------
Attachment AV: Report from the Apache MINA Project [Guillaume Nodet]
## Description:
The mission of MINA is the creation and maintenance of software related to
Multipurpose Infrastructure for Network Application
## Project Status:
Current project status: ongoing / dormant.
Issues for the board: none.
## Membership Data:
Apache MINA was founded 2006-10-25 (17 years ago)
There are currently 29 committers and 14 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
Community changes, past quarter:
- No new PMC members. Last addition was Thomas Wolf on 2021-09-30.
- No new committers. Last addition was Gary D. Gregory on 2022-03-24.
## Project Activity:
Recent releases:
* Apache MINA 2.0.24 was released on 2023-06-05.
* Apache MINA 2.1.7 was released on 2023-06-05.
* Apache MINA 2.2.2 was released on 2023-06-05.
Those 3 releases are bug-fix releases on maintained branches.
Not much other activity this quarter.
## Community Health:
Not much change since previous reports. The activity on SSHD has
decreased (it was the most active sub-project) and now slowly moves
into maintenance mode.
-----------------------------------------
Attachment AW: Report from the Apache MyFaces Project [Bernd Bohmann]
## Description:
The mission of MyFaces is the creation and maintenance of software related to
JavaServer(tm) Faces implementation and components
## Project Status:
Current project status: There are no issues.
Issues for the board: @cdutz there is no consensus on how to change
the .asf.yml and it's only used for tobago. Can you just send a PR for it?
## Membership Data:
Apache MyFaces was founded 2005-02-23 (18 years ago)
There are currently 80 committers and 46 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 Henning Nöth on 2021-06-01.
- No new committers. Last addition was Melloware on 2021-05-11.
## Project Activity:
- Apache MyFaces Core is working on small 4.0.x fixes.
- Apache Tobago the community is working on 5.x.
- Recent releases:
tobago-5.7.2 was released on 2023-06-22.
tobago-5.7.1 was released on 2023-05-30.
myfaces-core-4.0.1 was released on 2023-05-24.
tobago-5.7.0 was released on 2023-05-02.
myfaces-core-2.3-next-M8 was released on 2023-04-13.
## Community Health:
- Apache MyFaces Core is healthy.
UI-Component Sets:
- Apache Tobago is healthy.
- Apache Trinidad is in maintenance mode.
Last developer commit was Sept 2017.
- Myfaces Tomahawk is in maintenance mode.
Last developer commit was May 2016.
Last commit on behalf of a contributor was May 2016.
Add-ons and Extensions:
- Apache MyFaces Portlet Bridge is in maintenance mode.
Last developer commit was Jan 2014.
Last commit on behalf of a contributor was May 2015.
- Apache MyFaces CODI is in maintenance mode.
CODI was replaced by Apache DeltaSpike so new development
happens there. Last commit March 2014.
- Apache MyFaces Orchestra is in maintenance mode.
New projects use CDI and DeltaSpike instead.
Last commit on behalf of a contributor was August 2016.
- Apache MyFaces ExtVal is in maintenance mode.
Last commit June 2014.
- Apache MyFaces Commons is in maintenance mode.
Last commit August 2012.
- Apache MyFaces Ext-Scripting is in maintenance mode.
Last commit Sept 2017.
- Apache MyFaces Test is in maintenance mode (Used by Myfaces Core).
Last commit May 2017.
-----------------------------------------
Attachment AX: Report from the Apache NiFi Project [Joe Witt]
## Description:
The mission of NiFi is the creation and maintenance of software related to
providing an easy to use, powerful, and reliable system to process and
distribute data.
Apache NiFi MiNiFi is an edge data collection agent built to seamlessly
integrate with and leverage the command and control of NiFi. There are both
Java and C++ implementations.
Apache NiFi Registry is a centralized registry for key configuration items
including flow versions, assets, and extensions for Apache NiFi and Apache
MiNiFi.
Apache NiFi Nar Maven Plugin is a release artifact used for supporting the
NiFi classloader isolation model.
Apache NiFi Flow Design System is a theme-able set of high quality UI
components and utilities for use across the various Apache NiFi web
applications in order to provide a more consistent user experience.
## Project Status:
Current project status: Ongoing. High.
Issues for the board: None.
## Membership Data:
Apache NiFi was founded 2015-07-14 (9 years ago)
There are currently 63 committers and 34 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
Community changes, past quarter:
- Nándor Soma Abonyi was added to the PMC on 2023-06-25
- No new committers. Last addition was Ferenc Kis on 2023-03-23.
## Project Activity:
The NiFi community released NiFi 1.22.0 Jun 2023 and NiFi 1.21.0 in Apr 2023.
Each release provided new features, stability, and addressed reported
vulnerabilities within NiFi and dependencies. Meanwhile the community is
rapidly approaching a NiFi 2.0 major release already containing more than 466
changes. The MiNiFiCPP project also released 0.14.0 in April and we've
released the latest NiFi Nar Maven Plugin version 1.5.1 in June.
## Community Health:
Community health remains strong and we see high activity across the various
channels of contribution and engagement including JIRA, Github, Slack, Mailing
Lists and so on. Meetups are less common these days but we still see good
activity in conferences, blog posts, and more. We also continue to enjoy
excellent engagement for discussions, voting threads, and release candidate
evaluation. Slack remains a super popular point of engagement and we've grown
again this quarter to more than 2700 people in our 'general' slack channel
alone. The dev mailing list activity was 20% higher this quarter than last
while the user list is less active. Much of the user list activity has
moved to slack as we've reported for a while now but still the user list is
an effective tool for collaboration with more than 100 emails in this quarter.
Via JIRA, commits, and our issues list we still see a lot of activity and even
growth in activity this quarter. Importantly our rate of PR activity remains
high with more than 350+ PRs in the quarter again but importantly we have more
closed than opened showing we're finally turning the corner in this regard.
Some of the activity levels and commit levels reflect that we're managing
actively both the 1.x and 2.x release lines now so we do anticipate many of
these productivity metrics will drop in the coming quarters as we get the 2.0
release out and stable.
-----------------------------------------
Attachment AY: Report from the Apache Nutch Project [Sebastian Nagel]
## Description:
Apache Nutch is a highly extensible and scalable open source web crawler
software project based on Apache Hadoop® data structures and the MapReduce
data processing framework.
## Project Status:
Current project status: Ongoing with low activity
Issues for the board: none
## Membership Data:
Apache Nutch was founded 2010-04-21 (13 years ago)
There are currently 21 committers and 21 PMC members in this project.
The Committer-to-PMC ratio is 1:1.
Community changes, past quarter:
- No new committers and PMC members. Last addition was Shashanka Balakuntala
Srinivasa on 2020-08-01.
## Project Activity:
Nutch 1.19 was released on 2022-08-22.
Work on the next Nutch release continues with some bug fixes, improvements and
dependency upgrades. An indexer plugin for OpenSearch 2.x is under discussion.
## Community Health:
The number of contributions (Jira issues, commits, activity on the
mailing lists) is on a low level, below that of the previous quarter.
-----------------------------------------
Attachment AZ: Report from the Apache NuttX Project [Alin Jerpelea]
## Description:
The mission of Apache NuttX is the creation and maintenance of software related
to a mature, real-time embedded operating system (RTOS)
## Project Status:
Current project status: the community is active
Issues for the board: no issues to be reported
## Membership Data:
Apache NuttX was founded 2022-11-16 (8 months ago)
There are currently 29 committers and 21 PMC members in this project.
The Committer-to-PMC ratio is roughly 4:3.
Community changes, past quarter:
- Tiago Medicci was added to the PMC on 2023-05-30
- Tiago Medicci was added as committer on 2023-05-30
## Project Activity:
Recent releases:
12.2.0 was released on 2023-07-05.
12.1.0 was released on 2023-04-16.
## Community Health:
The community is healthy with several developers contributing daily
Several PPMC are organizing the annual conference (events.nuttx.apache.org/),
to facilitate the knowledge sharing and eventually get more contributors.
dev@nuttx.apache.org had a 6% decrease in traffic in the past quarter
(634 emails compared to 673):
1211 commits in the past quarter (-21% decrease)
102 code contributors in the past quarter (-14% change)
755 PRs opened on GitHub, past quarter (-29% change)
796 PRs closed on GitHub, past quarter (-21% change)
55 issues closed on GitHub, past quarter (14% increase)
-----------------------------------------
Attachment BA: Report from the Apache OpenJPA Project [Mark Struberg]
## Description:
The mission of OpenJPA is the creation and maintenance of software related to
JPA: Object Relational Mapping for Java
## Issues:
There are no issues requiring board attention.
## Project Activity:
We are actively working on a native Jakarta-3.1 (and later 4.0) release.
Right now we are getting rid of Serp, which is an ancient byte code library
which only supports up to Java-1.5. We are replacing it with native ASM
code to leverage Java22 and beyond.
All the packages have been migrated to the jakarta namespace.
## Community Health:
Small but active community. Good feedback cycles.
## Membership Data:
Apache OpenJPA was founded 2007-05-16 (15 years ago)
There are currently 35 committers and 18 PMC members in this project.
The Committer-to-PMC ratio is roughly 9:5.
## Community changes, past quarter:
- No new PMC members. Last addition was Maxim Solodovnik on 2019-04-13.
- No new committers. Last addition was Matt Pavlovich on 2019-05-22.
Recent releases:
3.2.2 was released on 2022-03-16.
3.2.1 was released on 2022-02-06.
3.2.0 was released on 2021-05-14.
4.0.x release expected in the next 3 Months.
-----------------------------------------
Attachment BB: Report from the Apache OpenMeetings Project [Maxim Solodovnik]
## Description:
The mission of OpenMeetings is the creation and maintenance of software related
to OpenMeetings: Web-Conferencing and real-time collaboration
## Project Status:
Current project status: Ongoing: With low activity
Issues for the board: none
## Membership Data:
Apache OpenMeetings was founded 2013-01-25 (10 years ago)
There are currently 30 committers and 28 PMC members in this project.
The Committer-to-PMC ratio is roughly 8:7.
Community changes, past quarter:
- No new PMC members. Last addition was Ali Alhaidary on 2021-03-22.
- No new committers. Last addition was Ali Alhaidary on 2021-04-07.
## Project Activity:
The development is currently limited to maintenance. Dependencies are updated
bugs are fixed, user questions are being answered
Recent releases:
- 7.1.0 was released on 2023-05-09.
- 7.0.0 was released on 2023-02-13.
- 6.3.0 was released on 2022-05-16.
## Community Health:
I was hoping new release will increase mail traffic, it seems it doesn't.
Hopefully adding new features will attract new users :)
-----------------------------------------
Attachment BC: Report from the Apache OpenOffice Project [Dave Fisher]
## Description
The mission of OpenOffice is the creation and maintenance of software related
to an open-source, office-document productivity suite
## Project Status
Current project status: Ongoing Low
Issues for the board: None
## Membership Data
Apache OpenOffice was founded 2012-10-16 (11 years ago)
There are currently 141 committers and 28 PMC members in this project.
The Committer-to-PMC ratio is roughly 9:2.
Community changes, past quarter
- No new PMC members. Last addition was Czesław Wolański on 2023-01-14.
- No new committers. Last addition was Francis Campos on 2022-06-06.
## Project Activity
Recent releases:
- 4.1.14 was released on 2023-02-27.
- 4.1.13 was released on 2022-07-22.
- 4.1.12 was released on 2022-05-04.
Download milestone as of June 30: 352,070,696
Project Website Updates in the OpenOffice-project repository:
- Mission statement.
- Migrated blogs from Roller.
Codebase in OpenOffice repository:
- Work continues slowly on the 4.2 future release including new icon options.
- The 4.1.x remains active for maintenance and security releases as well as
support for older operating systems.
Documentation:
- The OpenOffice-docs repository is where the small documentation team makes
updates. There was activity here.
- The OpenOffice-org repository has had the usual download count updates.
- MediaWiki (wiki.openoffice.org) is being maintained.
User support:
- User Forums (forum.openoffice.org) remain active in English, Spanish,
French, Hungarian, Italian, Japanese, Dutch, and Polish.
- users@openoffice.apache.org had a 33% decrease in traffic in the past
quarter (136 emails compared to 201)
- users-de@openoffice.apache.org had a 72% decrease in traffic in the past
quarter (42 emails compared to 145)
translation interface:
- currently we improve the import / export handling. This will be the first
service which will use a container structure.
## Community Health
Community overall health is improving.
### Project Mission
We have updated our project mission statement. Together with some tenets
like "Support for Linguistic and Cultural Diversity", "Open Standards" and
"Our Mission is Software for the Public Good" we want to give the project work
and software a little guideline when working on all the little things.
Here is the complete mission statement:
https://openoffice.apache.org/mission.html
## Infrastructure
Our Windows and Linux build bots are now migrated to new server. We are working
on a Mac build bot to enhance our changes.
### Binary Distributions
- SourceForge mirrors are still the main way to get an OpenOffice binary release.
- Windows builds are also published in the Microsoft Store (Windows 10/11).
Windows users are by far as our largest user group.
### Binary Code Signing
- Apple Code Signing. We do this, but would like to improve the process so that
our users do not encounter Apple's Gatekeeper warning.
- Windows Code Signing.
### Google Analytics
We will continue to check that our use of Google Analytics is eliminated.
## Marketing
### Facebook
We have no volunteer taking care on the presence. We will change to a static presence on Facebook.
For feedback we will guide to our standard channels.
### Twitter
One person maintains our Twitter account. We need to decide if this should be
continued.
## Development
### Unmaintained Python 2 code
Python 2 is unmaintained. We have in the development tree the external python3
support. Internal python 3 support is difficult. We are checking alternatives.
Planned for the next major release
### ODF Version 1.3
Our default file format, the Open Document Format, has received a new
Standard update. We plan to support this format.
-----------------------------------------
Attachment BD: Report from the Apache ORC Project [William Hyun]
## Description:
The mission of ORC is the creation and maintenance of software related
to the smallest, fastest columnar storage for Hadoop workloads.
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache ORC was founded 2015-04-21 (8 years ago)
There are currently 46 committers and 14 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:1.
- No new PMC members. Last addition was Pavan Lanka on 2023-03-30.
- No new committers. Last addition was Xin Zhang on 2023-02-06.
## Project Activity:
According to our release cadence, we released one minor and two
maintenance releases
in this quarter and helped other Apache communities use them.
- 1.9.0 was released on 2023-06-28.
- 1.8.4 was released on 2023-06-14.
- 1.7.9 was released on 2023-05-07.
In addition, we are preparing the following milestones.
- 2.0.0 (January)
- 1.9.1 (August)
- 1.8.5 (September)
- 1.7.10 (November)
## Community Health:
In this quarter, the number of closed GitHub and Jira issues increased
by 47% and 160% respectively, and the number of code contributors has
increased 13%.
-----------------------------------------
Attachment BE: Report from the Apache Parquet Project [Xinli Shang]
## Description:
The mission of Parquet is the creation and maintenance of software related to
columnar storage format available to any project in the Apache Hadoop ecosystem
## Project Status:
Current project status: green
Issues for the board: no issues
## Membership Data:
Apache Parquet was founded 2015-04-21 (8 years ago)
There are currently 38 committers and 27 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:4.
Community changes, past quarter:
- No new PMC members. Last addition was Gidon Gershinsky on 2021-11-23.
- No new committers. Last addition was Gang Wu on 2023-02-28.
## Project Activity:
Recent releases:
1.13.1 was released on 2023-05-18.
MR-1.11.2 was released on 2021-10-06.
MR-1.12.2 was released on 2021-10-06.
## Community Health:
dev@parquet.apache.org had a 28% decrease in traffic in the past quarter
43 issues opened in JIRA, past quarter (-15% change)
25 issues closed in JIRA, past quarter (-58% change)
109 commits in the past quarter (37% increase)
21 code contributors in the past quarter (-22% change)
65 PRs opened on GitHub, past quarter (-4% change)
68 PRs closed on GitHub, past quarter (17% increase)
-----------------------------------------
Attachment BF: Report from the Apache PDFBox Project [Andreas Lehmkühler]
## Description:
The mission of PDFBox is the creation and maintenance of software related to
Java library for working with PDF documents
## Project Status:
Current project status: Ongoing with moderate activity
Issues for the board: There are no issues requiring board attention at this time
## Membership Data:
Apache PDFBox was founded 2009-10-21 (14 years ago)
There are currently 21 committers and 21 PMC members in this project.
The Committer-to-PMC ratio is 1:1.
Community changes, past quarter:
- No new PMC members. Last addition was Matthäus Mayer on 2017-10-16.
- No new committers. Last addition was Joerg O. Henne on 2017-10-09.
## Project Activity:
Recent releases:
2.0.29 was released on 2023-07-01.
2.0.28 was released on 2023-04-13.
2.0.27 was released on 2022-09-29.
## Community Health:
- there is a steady stream of contributions, bug reports and questions on the
mailing lists
- there are a lot of refactorings, improvements and bugfixes
- 2.0.29 was released a few days ago
- the new release consists of small improvements and bug fixes. Two of the
latter fix two regressions introduced/revealed in the former 2.0.28 release
- a vote for the first beta version of PDFBox 3.0.0 is ongoing
-----------------------------------------
Attachment BG: Report from the Apache Petri Project [Dave Fisher]
## Description:
The mission of Apache Petri is the creation and maintenance of software related
to assessment of, education in, and adoption of the Foundation's policies and
procedures for collaborative development and the pros and cons of joining the
Foundation
## Project Status:
Current project status: Dormant
Issues for the board: None
## Membership Data:
Apache Petri was founded 2019-11-19 (4 years ago)
There are currently 8 committers and 5 PMC members in this project.
The Committer-to-PMC ratio is 8:5.
Community changes, past quarter:
- No new PMC members. Last addition was Daniel Shahaf on 2019-11-19.
- No new committers. Last addition was Justin Erenkrantz on 2020-04-23.
## Project Activity:
No activity. Could probably do some website refresh.
## Community Health:
Currently no communities or cultures involved.
We need to gauge what we want to accomplish given the fact that this TLP is
"secret"
-----------------------------------------
Attachment BH: Report from the Apache Pig Project [Koji Noguchi]
-----------------------------------------
Attachment BI: Report from the Apache Ranger Project [Selvamohan Neethiraj]
-----------------------------------------
Attachment BJ: Report from the Apache Ratis Project [Tsz-wo Sze]
## Description:
The mission of Apache Ratis is the creation and maintenance of software related
to a highly customizable Raft protocol implementation in Java
## Project Status:
Current project status: Ongoing with moderate activity.
Issues for the board: none.
## Membership Data:
Apache Ratis was founded 2021-02-17 (2 years ago)
There are currently 29 committers and 18 PMC members in this project.
The Committer-to-PMC ratio is roughly 8:5.
Community changes, past quarter:
- No new PMC members. Last addition was Attila Doroszlai on 2022-04-26.
- No new committers. Last addition was William Song on 2022-12-29.
## Project Activity:
We released Ratis 2.5.1 on 2023-05-05. It is a minor bug fix release
over Ratis 2.5.0, which was released on 2023-04-10.
## Community Health:
The project is healthy. In this quarter, the Ratis community mainly focused
on stabilizing the new features including Streaming and Linearizable Read. We
had less email traffic and less JIRAs/PRs compared to the last quarter.
-----------------------------------------
Attachment BK: Report from the Apache Rya Project [Adina Crainiceanu]
## Description:
The mission of Apache Rya is the creation and maintenance of software related
to scalable storage, retrieval, and analysis of RDF data
## Project Status:
Current project status: Dormant
Issues for the board: None
## Membership Data:
Apache Rya was founded 2019-09-17 (4 years ago)
There are currently 12 committers and 11 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 Adina Crainiceanu on 2019-09-17.
- No new committers were added.
## Project Activity:
No new activity. Last release 4.0.1 was on 2020-12-22
## Community Health:
The activity level in the project is low. The project is in "dormant" state:
not much happening on the code, but at least 3 PMC members ready to engage if
needed
-----------------------------------------
Attachment BL: Report from the Apache Samza Project [Yi Pan]
-----------------------------------------
Attachment BM: Report from the Apache SeaTunnel Project [Jun Gao]
## Description:
The mission of Apache SeaTunnel is the creation and maintenance of software
related to a very easy-to-use ultra-high-performance distributed data
integration platform that supports real-time synchronization of massive data
## Project Status:
Current project status: [
Apache SeaTunnel Ongoing with high, we have 82 issues closed and 50 PRs closed
]
Issues for the board: [none]
## Membership Data:
Apache SeaTunnel was founded 2023-05-17 (2 months ago)
There are currently 29 committers and 19 PMC members in this project.
The Committer-to-PMC ratio is roughly 8:5.
Community changes, past quarter:
- Hailin Wang was added to the PMC on 2023-07-10
- Chengyuan Ma was added as committer on 2023-07-15
## Project Activity:
[
1.SeaTunnel will soon have its own web system. I see that the community is
quickly completing it and preparing to release the version.
2.The Sink side automatic table creation feature has already been submitted by
contributors, which will be a very important feature. The community will
increase the promotion of this feature and hope that more users can use it.]
## Community Health:
[ dev@seatunnel.apache.org had a 28% decrease in traffic in the past quarter
(67 emails compared to 92) users@seatunnel.apache.org had a 533% increase in
traffic in the past quarter (19 emails compared to 3) 258 commits in the
past quarter (-44% change) At present, the community has found some issues
with the current architecture design, which have led to some features that
cannot be effectively implemented, such as DDL changes and Sink automatic
table creation. In order to improve the scalability of the architecture, we
have reduced the merging of connector related PR and focused our efforts on
architecture optimization. Now, more connectors mean greater repair workload
after architecture optimization is completed. This situation will soon
improve. In addition, the community has invested a lot of effort in
SeaTunnel Web, which will be another very important feature of SeaTunnel.
]
-----------------------------------------
Attachment BN: Report from the Apache Serf Project [Justin Erenkrantz]
-----------------------------------------
Attachment BO: Report from the Apache SkyWalking Project [Sheng Wu]
## Description:
The mission of Apache SkyWalking is the creation and maintenance of software
related to application performance management and monitoring (APM)
## Project Status:
No issue.
## Membership Data:
Apache SkyWalking was founded 2019-04-17 (4 years ago)
There are currently 57 committers and 33 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 Yihao Chen on 2023-02-22.
- Qiang Xu was added as committer on 2023-06-17
- Gong Dewei was added as committer on 2023-06-30
## Project Activity:
A dozen of releases are out in this quarter.
- cli-0.12.0: 2023-06-25
- rover-0.5.0: 2023-06-25
- satellite-1.2.0: 2023-06-25
- 9.5.0: 2023-06-14
- go-0.1.0: 2023-06-04
- java-8.16.0: 2023-06-02
- rust-0.7.0: 2023-05-27
- php-0.5.0: 2023-05-09
- java-8.15.0: 2023-04-10
The community is being involved in GSoC and OSPP(Open Source Promotion Program)
for this summer. 10 tasks are mentored by the committer team.
The Java agent is bumping up the version series to 9.x. 8.16 would be the
last v8 release. 9.x will be highly compatible with 8.x and share most
behaviors. The new version highlights some kernel level changes, which
didn't happen for years.
## Community Health:
The project is active and healthy.
Code traffic decreased as 9.5.0 is out. And the v9 series is becoming stable.
The bug trend is convergence. So, traffic of issues are not low too.
-----------------------------------------
Attachment BP: Report from the Apache Steve Project [Daniel Gruno]
## Description:
The mission of Steve is the creation and maintenance of software related to
Apache's Python based single transferable vote software system
## Project Status:
Current project status: Dormant, with sufficient oversight.
Issues for the board: There are no issues for the board.
## Membership Data:
Apache Steve was founded 2012-07-25 (11 years ago)
There are currently 10 committers and 6 PMC members in this project.
The Committer-to-PMC ratio is 5:3.
Community changes, past quarter:
- No new PMC members. Last addition was Jim Jagielski on 2022-04-16.
- No new committers. Last addition was Sean Palmer on 2022-03-04.
## Project Activity:
No activity of note since last report. Other priorities for the project
members have kept development at a minimum over the last couple of quarters,
but we do have sufficient oversight, as well as continuing use cases for the
software.
We have not yet had an official release of STeVe, but work has begun on our
third iteration of the software. The first iteration was the original
command-line system, the second iteration was the "PySTeVe" bundle that
currently powers vote.apache.org, and the now third iteration will build on
the previous work, adding in more modern approaches and technologies. There is
an expectation that this third iteration will result in an official release at
some point.
## Community Health:
No material changes over the past quarters, but as stated, we do have
sufficient oversight, should the need arise. A roll call was initiated on July
4th to ensure we meet the oversight requirements, and the responses indicated
that we do indeed meet them.
-----------------------------------------
Attachment BQ: Report from the Apache Storm Project [P. Taylor Goetz]
-----------------------------------------
Attachment BR: Report from the Apache Streams Project [Steve Blackmon]
-----------------------------------------
Attachment BS: Report from the Apache Struts Project [René Gielen]
The Apache Struts MVC framework is a solution stack for creating elegant and
modern action-based Java web applications. It favours convention over
configuration, is extensible using a plugin architecture, and ships with
plugins to support patterns and technologies such as REST, AJAX and JSON.
The Struts team made three releases in the last quarter:
- Struts 6.2.0 - Feature an bug fix release (2023-07-10) [1]
- Struts 6.1.2.1 - Security fix release (2023-06-13) [2]
- Struts 2.5.31 - Security fix release (2023-06-13) [3]
The last Struts releases besides the core framework were
- Struts Master 14 - Apply Apache Parent POM and plugin upgrades (2020-02-05)
- Struts Annotations 1.0.8 - Enhancements in preparation for the next
framework release (2022-11-05)
Within the last quarter we saw reasonable development and community activity.
We had 39 PRs (compared to 76 in previous reporting quarter) opened and 39
(76) closed in the main project.
These numbers are a slight drop compared to the last quarter, which is not
unusual for the main vacation season.
We counted 86 (146) commits by 11 (7) contributors in the report quarter. By
the time of writing this report, we are holding a vote on inviting one of
these contributors for committership.
We released two security bulletins in the last quarter [4][5], leading to the
two security fix releases 2.5.31 and 6.1.2.1. Based on the board feedback
received lately, we adjusted our security fix release process to cast the vote
on private@ rather than dev@.
We have no issues that require board assistance at this time.
## PMC changes:
- Currently 22 PMC members.
- No new PMC members added in the last 3 months
- James Chaplin (jchaplin) was added to the PMC on 2020-11-16
## Committer base changes:
- Currently 60 committers.
- No new committers added in the last 3 months
- James Chaplin (jchaplin) was added as committer on 2020-01-08
## Mailing list activity:
Mailing list activity was more calm as well:
- dev@struts.apache.org:
- 153 emails sent to list (239 in previous quarter)
- issues@struts.apache.org:
- 229 emails sent to list (488 in previous quarter)
- user@struts.apache.org:
- 47 emails sent to list (56 in previous quarter)
## JIRA activity:
- 14 JIRA tickets created in the last 3 months (29)
- 16 JIRA tickets closed/resolved in the last 3 months (30)
[1] https://struts.apache.org/announce-2023#a20230310
[2] https://struts.apache.org/announce-2023#a20230310
[3] https://struts.apache.org/announce-2023#a20230310
[4] https://cwiki.apache.org/confluence/display/WW/S2-063
[5] https://cwiki.apache.org/confluence/display/WW/S2-064
-----------------------------------------
Attachment BT: Report from the Apache Tapestry Project [Thiago Henrique De Paula Figueiredo]
## Description:
The mission of Tapestry is the creation and maintenance of software related to
Component-based Java Web Application Framework
## Project Status:
Current project status: ongoing
Issues for the board: none
## Membership Data:
Apache Tapestry was founded 2006-02-14 (17 years ago)
There are currently 29 committers and 13 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 Ben Weidig on 2021-12-02.
- No new committers. Last addition was Volker Lamp on 2022-04-14.
## Project Activity:
We have a release vote underway for a new release, 5.8.3, with 21
tickets, including bugs and enhancements, which is the highest
for a long time. We're also working on some stuff for future releases,
like improving our Gradle build and supporting Jakarta EE.
## Community Health:
Very active quarter, specially when compared to the previous ones:
dev@tapestry.apache.org had a 85% increase in traffic in the past quarter (37
emails compared to 20)
users@tapestry.apache.org had a 92% increase in traffic
in the past quarter (25 emails compared to 13)
19 issues closed in JIRA, past quarter (850% increase)
76commits in the past quarter (280% increase)
6 code contributors in the past quarter (50% increase)
5 PRs closed on GitHub, pastquarter (66% increase)
-----------------------------------------
Attachment BU: Report from the Apache Tcl Project [Georgios Petasis]
## Description:
The mission of Tcl is the creation and maintenance of software related to
Dynamic websites using TCL. Apache Tcl is home to the Tcl-Apache integration
efforts. The purpose of our project is to combine the power of the Apache
web server with the capabilities of the mature, robust and flexible Tcl
scripting language. Currently only the Apache Rivet project is actively
maintained.
## Project Status:
Current project status: Ongoing
Issues for the board: none
## Membership Data:
Apache Tcl was founded 2000-07-24 (23 years ago)
There are currently 12 committers and 7 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 Brice Hamon De Crevecoer on 2014-11-25.
- No new committers. Last addition was Brice B. Hamon on 2014-11-25.
## Project Activity:
No release has been made during the reporting period. The latest release
(rivet-3.2.2 was released on 2022-06-21) has received positive feedback, and
no problems have been identified so far.
## Community Health:
The traffic of the mailing lists has remained at similar levels to the
previous reporting period, which is normal for the project (as most traffic in
the list happens after new releases). The current increase in the traffic
relates to some usage questions performed by some new users (i.e. how to
handle POST requests, and how to log during initialisation). Also, I want to
report that I haven't received the usual e-mail reminders for submitting the
report this reporting period, I had to check about the report status.
-----------------------------------------
Attachment BV: Report from the Apache Tez Project [László Bodor]
## Description:
Apache Tez is an effort to develop a generic application framework which can be
used to process arbitrarily complex DAGs of data-processing tasks and also a
re-usable set of data-processing primitives which can be used by other projects.
## Project Status:
Current project status: Ongoing.
Issues for the board: Issues for the board: none.
## Membership Data:
Apache Tez was founded 2014-07-16 (9 years ago)
There are currently 35 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 László Bodor on 2020-11-24.
- No new committers. Last addition was László Bodor on 2020-01-23.
## Project Activity:
The last release was 0.10.2 which was released on 2022-07-15. We've already
started to discuss 0.10.3.
## Community Health:
I need to clarify some points regarding Cloudera (which was mentioned in the
last report and was confusing, sorry). Regarding community health, the board
might want to be aware that Tez project is in a local optimum for a long time,
there are no huge ongoing improvements, and it's stable and working, however,
it means that it might be challenging to get new committers, as sometimes we
expect 5-10-whatever commits, including some with deeper understanding of the
code and components. However, I really want to get new people involved,
because it would make it feel like a community, and that's how Cloudera came
into the picture. I'm currently working for Cloudera, and I figured out that
sometimes it's easier to advertise open tickets and invite people to
collaborate if they're your colleagues, team members, etc. That's what I was
doing recently, therefore it's a new active member around (Ayush Saxena,
already member of PMC in another projects btw.), which is cool I believe.
Needless to say that I'm aware of the need of a diverse community, I'm
happily, actively reviewing patchers from anyone.
-----------------------------------------
Attachment BW: Report from the Apache Thrift Project [Jens Geyer]
## Description:
Apache Thrift is a high performance cross platform RPC and serialization
solution.
## Project Status:
Current project status: Ongoing
Issues for the board: none
## Membership Data:
Apache Thrift was founded 2010-10-20 (13 years ago)
There are currently 41 committers and 21 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 Mario Emmenlauer on 2022-04-13.
- No new committers. Last addition was Liu Jiayu on 2022-06-25.
## Project Activity:
Right now we're working towards next release, which should take place in the
next few weeks.
## Community Health:
Project participation remains on a steady, yet still too low, level. One
indicator of this is the amount of unhandled PRs on Github we face for a while
now. Since Thrift is special in the regard that we support 20+ target
languages, we definitely could use more skilled hands to review those PRs. In
addition, since recent contributions especially from new people tend to be
only small and rare, finding good committer candidates becomes quite a
challenge.
-----------------------------------------
Attachment BX: Report from the Apache Tika Project [Tim Allison]
## Description:
Apache Tika is a dynamic toolkit for content detection, analysis, and
extraction. It allows a user to understand, and leverage information from, a
growing a list of over 1200 different file types including most of the major
types in existence (MS Office, PDF, Text, Images, Video, Code, and science
data) as recognized by IANA and other standards bodies.
## Project Status:
Current project status: Ongoing
Issues for the board: None
## Membership Data:
Apache Tika was founded 2010-04-20 (13 years ago)
There are currently 32 committers and 32 PMC members in this project.
The Committer-to-PMC ratio is 1:1.
Community changes, past quarter:
- No new PMC members. Last addition was Nicholas DiPiazza on 2021-07-05.
- No new committers. Last addition was Nicholas DiPiazza on 2021-06-03.
## Project Activity:
We released 2.8.0 on 15 May, and we've started the preliminary regression
tests in preparation for the next release. We've had some great contributions
from a new user of Tika for file type detection via a collaboration using
Common Crawl data.
We updated our regression corpus to remove most of the truncated PDFs from
Common Crawl and to add ~100k new PDFs from
https://digitalcorpora.org/corpora/file-corpora/cc-main-2021-31-pdf-untruncated/
## Community Health:
We've seen increases in issues opened and closed (largely driven by the new
mime patterns). Our CHI is 4.70 (Healthy).
-----------------------------------------
Attachment BY: Report from the Apache TinkerPop Project [Florian Hockmann]
## Description:
Apache TinkerPop is a graph computing framework for both graph databases
(OLTP) and graph analytic systems (OLAP).
## Issues:
There are no issues requiring board attention.
## Project Status: Ongoing
Activity is relatively high, considering we are actively working on releases,
have daily commits and development discussions on the dev list. We also have
an active user community on Discord where developers and users engage on
questions, as well as regular live events on Twitch for knowledge-sharing.
## Membership Data:
Community changes, past quarter:
- No new PMC members. Last addition was Yang Xia on 2023-03-15.
- Cole Greer was added as committer on 2023-05-30
## Project Activity:
TinkerPop released versions 3.5.6, 3.6.3, and 3.6.4. in the last quarter.
These releases were mostly maintenance releases. One noteworthy improvement in
3.5.6 and 3.6.3 is a new multi-architecture Docker image for Gremlin Server
which supports ARM64 in addition to AMD64. This release also included
important performance improvements for Gremlin Console and TraversalStrategy
applications for users and providers. 3.6.4 was a patch release that fixed a
critical bug in the Java driver and a memory leak in the .NET driver.
We are closing in on releasing 3.7.0 shortly, a release that includes work
from over a year. Major improvements in this release are support for JDK 17
and Groovy 4. This release will also include usability improvements in areas
that users often request, such as support for string manipulations directly in
Gremlin, returning vertices and edges with their properties by default instead
of only as reference elements, which often led to confusion, especially for
new users. We have also been working on adding transaction support to
TinkerGraph, the TinkerPop reference graph implementation. Together with
3.7.0, we plan to also publish maintenance releases 3.5.7 and 3.6.5.
In the wider TinkerPop ecosystem, we learned that Aerospike released the first
version of their graph database which supports TinkerPop. New graph
database.[1]
### Releases:
3.6.4 was released on 2023-05-12.
3.5.6 was released on 2023-05-01.
3.6.3 was released on 2023-05-01.
## Community Health:
We again had some live events on Twitch[2] where the recording are available on
our YouTube channel[3]:
* TinkerPop Wide: ArcadeDB - a Multi-Model Database with Gremlin - Presenter:
Luca Garulli - founder of ArcadeDB
* Contributorcast: Apache TinkerPop 3.5.6/3.6.3 Post-Release Review -
Presenter: Yang Xia, Valentyn Kahamlyk, Cole Greer, and Ken Hu
* TinkerPop Wide: Introducing Graph Notebook - Presenter: Kelving Lawrence and
Taylor Riggan from AWS, working on Amazon Neptune
## Links
[1]: https://s.apache.org/cl21t
[2]: https://www.twitch.tv/apachetinkerpop
[3]: https://www.youtube.com/@apachetinkerpop
-----------------------------------------
Attachment BZ: Report from the Apache Traffic Server Project [Bryan Call]
## Description:
The mission of Traffic Server is the creation and maintenance of software
related to a fast, scalable and extensible HTTP/1.1 and HTTP/2 compliant
caching proxy server.
## Project Status:
Current project status: Ongoing with moderate activity
Issues for the board: none
## Membership Data:
Apache Traffic Server was founded 2010-04-20 (13 years ago)
There are currently 70 committers and 57 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 Damian Meden on 2022-12-14.
- No new committers. Last addition was Chris McFarlen on 2022-10-11.
## Project Activity:
We had two security releases last quarter (8.1.7 and 9.2.1). We are working
on our next major release (ATS 10.0.0) that will have HTTP/3 client support
and HTTP/2 to the origin support. We are also going to have a JSON RPC for
clients to read stats and modify configuration. There is one company at the
moment testing the new release in production.
## Community Health:
We had a remote ATS Spring Summit on May and plan to have another remote
summit in October. It doesn't look like companies are opening up budgets to
travel until next year at this point.
We are continuing to have our weekly PR and issue scrub meetings every Monday
and HTTP/3 meetings on Tuesdays.
All of the community health metrics are up. We have a couple new people that
have joined the community during this time and are being paid to work on ATS
full time.
-----------------------------------------
Attachment CA: Report from the Apache Web Services Project [Daniel Kulp]
-----------------------------------------
Attachment CB: Report from the Apache Zeppelin Project [Jongyoul Lee]
## Description:
The mission of Zeppelin is the creation and maintenance of software related to
A web-based notebook that enables interactive data analytics
## Project Status:
Current project status: The Cummunity is preparing the next release on 0.11.0
Issues for the board: PMC is working on security issues.
## Membership Data:
Apache Zeppelin was founded 2016-05-18 (7 years ago)
There are currently 24 committers and 11 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
Community changes, past quarter:
- No new PMC members. Last addition was Jeff Zhang on 2018-01-25.
- No new committers. Last addition was Guanhua Li on 2022-12-03.
## Project Activity:
The community is refreshing the code base including dependencies. They are
upgrading major component like web server and major interpreters including
Spark and Flink. In case of CI, they upgraded the lastest version of Junit.
In the next few months, the community will focus on upgrading JDK version to 11.
## Community Health:
Most metrics were improved during three months. PMC is trying to find new
organization contributors as well as individual contributors. I, as PMC chair,
try to secure the time to focus the project only.
-----------------------------------------
Attachment CC: 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
As the board is interested in more details, here is what Helix targeted
recently: Helix is the framework focusing on managing large data systems. When
the data onboards cloud, more container maintenance/deployment can lead Helix
to believe instances lost. Active moving around partition data is not a proper
solution. Helix now is trying to build a smart solution to guarantee data
movement smooth
## Membership Data:
Apache Helix was founded 2013-12-17 (10 years ago)
There are currently 28 committers and 18 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:5.
Community changes, past quarter:
- No new PMC members. Last addition was Jiajun Wang on 2022-11-02.
- Molly Gao was added as committer on 2023-06-06
- Quincy Qu was added as committer on 2023-05-19
## Project Activity:
- 1.2.0 was released on 2023-05-02
- 1.1.0 was released on 2023-01-04.
- 1.0.4 was released on 2022-06-09.
## Community Health:
Helix has three major tasks:
1. Stabilize the integration test. So we saw see the CI failure rate going
down 212 commits in the past quarter (216% increase) 14 code contributors
in the past quarter (40% increase)
2. More discussion from users actually in Helix slack. We got several
questions from some company teams such as Uber, Pinterest.
3. Cloud support development. As mentioned above, Helix is trying to develop a
smart partition movement. Helix will bootstrap a new replica to a new
assigned instance. Once it bootstrapped, Helix started dropping the old
one. This require a lot of effort since we need to handle different edge
cases and rearchitect parts of Helix. Related to this, we have several
items: 1) fix N replica -> N + 1 issue 2) support one stop operation to
evacuate host and 3) support better deployment delay on partition movement.
------------------------------------------------------
End of minutes for the July 19, 2023 board meeting.
Index