Hi Josh, Thanks for the feedback! I'm happy to break out “#3” into a separate “Dev Discussion Summary” thread going forward. I am glad it fits in with the overall Community Update.
As for automating with Claude, that’s a great idea. I’ve been using Claude mainly to help format the email before sending but a fully automated system would be wonderful. Thanks again for the feedback! Best, Himanshu From: Josh McKenzie <jmcken...@apache.org> Reply-To: "dev@cassandra.apache.org" <dev@cassandra.apache.org> Date: Tuesday, July 8, 2025 at 1:02 PM To: dev <dev@cassandra.apache.org> Subject: RE: [EXTERNAL] Sharing a Monthly Cassandra Community Update – Would This Be Useful Here? CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe. Definitely Himanshu! I've had a todo list item for, oh, two? three? months now to get to another one of these; I've sent them off and on over the past few years. Historically I tried to cover: 1. How to get started w/the community 2. Releases that have come out 3. Any discussions people might want to engage with 4. An overview of CI 5. And general project velocity (tickets closed out, per release, etc) If you wanted to break out #3 to a separate email thread like this it'd make it a lot easier for me to stay on top of the other 4 items. :) One thing I've toyed with is the idea of pipelining a summary from Claude on email threads from a time frame and potentially JIRA traffic and even visuals from butler<https://butler.cassandra.apache.org/#/>. Haven't gotten around to that yet but I feel like there's some real potential there. On Tue, Jul 8, 2025, at 12:47 PM, Jindal, Himanshu wrote: Hi everyone, I've been putting together a monthly Cassandra Community Update for my internal team. It highlights key conversations from mailing lists and summarizes technical discussions that I believe are valuable for anyone following Cassandra's evolution. I’m wondering if folks in the broader community would also find this useful. Below is a sample from the May/June timeframe. I’d love your feedback — is this something you'd want to receive monthly on this list? If so, I’m happy to start sharing future updates here. Thanks in advance for your thoughts! Cassandra Community Update – May/June 2025 [Developer List Archive Link<https://lists.apache.org/list?dev@cassandra.apache.org:2025-7>] Here’s a quick roundup of recent discussions in the Cassandra community. If you're looking to stay informed or contribute, these are great threads to dig into — lots of thoughtful technical debate and new ideas this month. ________________________________ 1. [DISCUSS] Seeking Guidance on Next Task and Areas to Contribute [Link<https://lists.apache.org/thread/7rjwq49r6frbmntpn8zqz9lmv00g53ty>] A helpful thread full of suggestions for new contributors. If you're looking for ways to engage with the Cassandra project, this is must-read. 2. A Roadmap to Cassandra Analytics 1.0 [Link<https://lists.apache.org/thread/r29nskkc3j183fl0k1sd91tp7z051zwt>] This post outlines a vision for evolving Cassandra Analytics from 0.1 to 1.0. Lots of actionable suggestions here — great entry points for contributors looking to get involved in analytics work. 3. [DISCUSS] CEP-48: First-Class Materialized View Support [Link<https://lists.apache.org/thread/wbn1kvz8yshcf1z0ozjf7wpsgmvmkwvj>] A lively and sometimes contentious discussion. The proposal aims to create “Materialized Views v2” to address performance issues in the current version. There’s still active debate around its interaction with repairs. Highly recommended reading for anyone interested in design tradeoffs and constructive disagreement. 4. [DISCUSS] CEP-50: Authentication Negotiation [Link<https://lists.apache.org/thread/cdx4fttq72j4dz7cyhxp14pt7k6rd6bc>] This proposal introduces a new, backward-compatible authentication negotiation mechanism. It’s now formally published as a CEP and is seeking feedback. 5. [VOTE] Clarifying Our JDK Support Policy [Link<https://lists.apache.org/thread/7640gzjlwo07kjmoyjpt8gq80qk5qhn9>] The community agreed to align GA branches with current JDK LTS releases. Older JDK-based branches will be deprecated moving forward — a step toward cleaner support and modernization. 6. [DISCUSS] Improving Operational Safety for Major Version Upgrades [Link<https://lists.apache.org/thread/gx69h26nvol5027lfrozr27hh9dxcjtl>] Initial proposal suggested tracking upgrade intent inside Cassandra, but community consensus leaned toward implementing it in the sidecar, which is viewed as Cassandra’s control plane of the future. 7. [DISCUSS] CEP-49: Hardware-Accelerated Compression [Link<https://lists.apache.org/thread/t766stj07rb9vgrg2cyyd5s7n3g2zdgt>] Proposes using Intel-specific hardware acceleration. While there’s interest, the community prefers to keep the core compression interface pluggable and house vendor-specific logic outside the main repo. ________________________________ Reply if you’d like to see future updates! Best, Himanshu
