The Cassandra community includes people from around the globe who are developing and using the open source NoSQL database the world relies on. We welcome and encourage participation by everyone.
If you are a Cassandra user or want to learn more, we invite you to join these channels created specifically for end user questions and discussions.
To participate and join the #cassandra channel for user questions and general discussions.
You can also check the Q&A about using Cassandra on Stack Overflow.
Those who wish to contribute to the project or want to stay up-to-date on Cassandra development should join these channels.
An informal meeting to create real-time collaboration for questions, issues and discussion.
A special interest group (SIG) to discuss the creation of a community-based operator to make it easy to run C* on K8s.
Like all Apache projects, Cassandra is independently managed by its Project Management Committee (PMC). The Cassandra PMC is tasked with project management—especially technical direction, votes on new committers and PMC members for the project, and sets policies as well as formally voting on software product releases. Our guiding philosophies are to default to the dev list and “decide as a community,” and to favor PMC minimalism.
Contributors are individuals who contribute patches—source code, documentation, help on mailing lists, website—to Apache projects. While contributors do not have a specific governance role, they are crucial to the project’s success. Read the docs to learn how to contribute to Cassandra, and review our governance page to understand how we vote on code contributions.
Committers are members of a project development community who have been granted write access to an Apache project. New committers and PMC members are elected by the Cassandra PMC based on merit. More on committers.
If, after having asked for help, you suspect that you have found a bug in Cassandra, you should report it by opening a ticket through the Apache Cassandra JIRA tracking system. Please provide as much detail as you can on your problem. Don’t forget to indicate which version of Cassandra you are running and on which environment.
To report a vulnerability for Cassandra, contact the Apache Security Team.
The Cassandra Enhancement Proposal (CEP) provides a process for the proposal, discussion and endorsement of new feature development in Cassandra. Anyone can initiate a CEP, but it should only be done if you have the intention and capability to complete the proposed change. Learn how to propose and shepherd a CEP.
Aleksey Yeschenko, Alex Petrov, Aaron Morton, Anthony Elder, Ariel Weisberg, Blake Eggleston, Benedict Elliott Smith, Benjamin Lerer, Brandon Williams, Chris Goffinet, Chris Lohfink, David Brosius, Eric Evans, Gary Dusbabek, T Jake Luciani, Jason Brown, Jon Haddad, Jonathan Ellis, Jake Farrell, Jeff Jirsa, Josh McKenzie, Jun Rao, Sankalp Kohli, Marcus Eriksson, Michael Semb Wever, Matthieu Riou, Michael Shuler, Nate McCall, Paulo Motto, Pavel Yaskevich, Sam Tunnicliffe, Sylvain Lebresne, Stefan Podkowinski, Stefania Alborghetti, Tyler Lee Hobbs