Hi there,

Congratulations to the Geode community. I am glad tosee Apache Geode surviving 
and that community has been able to be active again.

 I am reflecting on my personal view on this community, andthe ONLY purpose is 
that I would like this community to stay healthy for a longperiod. 

 In my view the issue with Geode Community has been duringall these years the 
lack of diversity. The community has been driven"mainly" by committers working 
for 1 or 2 employers. And obviouslythat makes the community very sensible when 
those employers decide to changetheir strategy.

 The "Apache Way" clearly reflects: "At theASF, diversity of employers is a 
graduation requirement for Incubatingprojects. Incubator Podlings must show 
that they can attract committers fromvarious employers to ensure that the 
project and technology is likely to beuseful for a wider audience". Apache 
Geode has been an example of whatcould happen when this premise is not achieved.

Now there are new people in the community, and I hope thatthey (with ASF 
guidance) manage to keep the project healthy for a long period.

There are many ways to do open source, BUT there is only one"Apache way".

Congratulations again,

Evaristo









 

 





 






    El lunes, 16 de noviembre de 2026, 05:39:11 CET Jinwoo Hwang via user, 
<[email protected]> escribió:  
 
  Hello Apache Geode Community,
Ten years ago today, on November 15, 2016, Apache Geode graduated fromthe 
Apache Incubator and became a Top-Level Project. I want to mark theday by 
saying thank you, and by looking back honestly at the last fewyears, because 
what our community did in them is what I am proudest of.
The early years were busy. In 2016 alone the project saw more than 
2,300commits, and by 2018 over 80 people were contributing in a single 
year.Kirk Lund wrote nearly a thousand of those commits between 2015 and 
2022,more than anyone else in the project's history, most of them in thetests, 
the dunit framework and the logging that the rest of us stilldepend on. When 
Log4Shell hit in December 2021, it was Kirk who pushedthe log4j fixes across 
three support branches within days. And threepeople chaired the project in 
those years: Mark Bretl, Karen Miller andDan Smith.
Then corporate sponsorship faded. In November 2022, the PMC voted tomove Geode 
to the Attic. That vote was withdrawn after former PMCmembers and other ASF 
members offered to help. Calvin Kirs and RogerWhitcomb joined the PMC so there 
would still be a PMC, and Mark Bretl,the project's first chair at graduation in 
2016, returned to the chair. He held that seat through the two most challenging 
years in the project's history: 11 commits in 2023, and nothing merged to 
develop in 2024. In July 2024 Mark wrote that the project was not sustainable 
as it stood and asked for volunteers. When few came, he did the hard thing and 
ran the termination vote himself. In November 2024, with new volunteers 
beginning to appear, the PMC asked the board to wait one more cycle.
I am grateful to the people who kept the project alive through thatstretch. Sai 
Boorlagadda rebuilt our CI on GitHub Actions in 2023 whenthe old pipeline died 
with its hardware. Niall Pemberton added ourlicense headers in 2015 and ten 
years later was still the personreviewing stuck pull requests and fixing the 
SVN permissions that stoodbetween us and the 1.15.2 release. Each of you gave 
the rest of ussomething to come back to.
Then our community came together. We started small, with build scanpublishing 
and dependency upgrades in the first half of 2025. BryanBehrenshausen pulled 
reviewers back to stalled pull requests. In Augustand September more of us 
began sending fixes, upgrades anddocumentation updates, Arnout Engelen of the 
ASF Security Team amongthem, and in September we shipped 1.15.2, our first 
release in threeyears. It took four release candidates to get the release 
right, and CalvinKirs, Greg Chase and Nitin Lamba cast the three binding votes 
thatmade it official. That month’s board report recorded Geode as moving from 
dormant to ongoing after a group of users stepped up to keep it alive. The same 
week, we opened the 2.0 proposal, and Leon Finker, Charlie Black and Kishor 
Bachhav told us candidly what 2.0 should and should not carry forward.
The following three months were some of the most productive our projecthas seen 
in years. We moved to Java 17, completed the Jakarta EE 10migration along with 
Spring 6, Spring Shell 3, HttpComponents 5 andJetty 12, removed the unsafe 
reflection and internal-API access thatblocked the Java module system, and 
addressed a long backlog ofvulnerabilities. Geode 2.0.0 shipped on December 18, 
and the ASFannounced it on January 12. Since September 20, 2025, we have 
shipped tenreleases across the 1.15 and 2.0 lines, and about a dozen people 
have contributed to the repository for the first time.
I apologize that I cannot name every one of you who contributed overthese ten 
years. Please do not feel left out. We appreciate each andevery contributor, 
and the project is here today because of all of you.
None of this happens without you. Thank you to everyone who wrote code,reviewed 
pull requests, tested release candidates, voted on releases, orasked a question 
on user@ or dev@. Our project was voted to the Atticin 2022, voted to terminate 
in 2024, and spent the years between onlife support. Today it is alive and 
thriving again. That is entirelybecause of you.
The next ten years start now, and there is room for everyone. If youhave been 
thinking about your first pull request, a review, a doc fix,or a vote on the 
next release candidate, this is a good week to do it.We will be glad to have 
you.
Here's to ten years of Apache Geode, and to the next ten.
Best regards,Jinwoo Hwang (he/him/his)
Apache Geode, ASFResearch and Development, SAS Institutehttps://JinwooHwang.com 
 

Reply via email to