Getting Started

Initial Contributions

Writing a new feature is just one way to contribute to the Cassandra project. In fact, making sure that supporting tasks, such as quality testing, documentation, and helping users are completed is just as important. Tracking the development of new features is an ongoing challenge for this project, like most open source projects. We suggest learning how this project gets things done before tackling a new feature. Here are some suggestions for ways to contribute:

• Update the documentation
• Answer questions on the user list
• Review and test a submitted patch
• Investigate and fix a reported bug
• Create unit tests and d-tests

  Updating documentation

  patch.

  Answering questions on the user list

  community page for details on how to subscribe to the mailing list.

  Reviewing and testing a submitted patch

  How to review or alternatively, create a build with the patch and test it with your own workload. Add a comment to the JIRA ticket to let others know you’ve reviewed and tested, along with the results of your work. For example: “I tested this performance enhancement on our application’s standard production load test and found a 3% improvement.”

  Investigate and/or fix a reported bug

  patch. the #cassandra or #cassandra-dev channels on ASF Slack, or on the user or dev mailing list.

  Create unit tests and Dtests

  testing and patches for more detail.