Maxwell-Guo commented on code in PR #4327:
URL: https://github.com/apache/cassandra/pull/4327#discussion_r2292145171


##########
CONTRIBUTING.md:
##########
@@ -18,16 +18,23 @@
 #
 -->
 
-# Apache Cassandra and Pull Requests
+# How to Contribute
 
-Apache Cassandra doesn't use GitHub pull requests as part of the development 
process.
-In fact, this repository is a GitHub mirror of [the official 
repo](https://gitbox.apache.org/repos/asf/cassandra.git).
+There are many opportunities to contribute code to Apache Cassandra, including 
documentation updates, test improvements,
+bug fixes, changes to the Java code base, and tooling improvements (both 
Python and Java). The basic workflow is the

Review Comment:
   tooling improvements means ? nodetool or cassandra drivers(python / go/ 
java) or tools like cassandra-dtest,cassandra-spark-connector or service like 
cassandra-analytics?
   



##########
CONTRIBUTING.md:
##########
@@ -18,16 +18,23 @@
 #
 -->
 
-# Apache Cassandra and Pull Requests
+# How to Contribute
 
-Apache Cassandra doesn't use GitHub pull requests as part of the development 
process.
-In fact, this repository is a GitHub mirror of [the official 
repo](https://gitbox.apache.org/repos/asf/cassandra.git).
+There are many opportunities to contribute code to Apache Cassandra, including 
documentation updates, test improvements,
+bug fixes, changes to the Java code base, and tooling improvements (both 
Python and Java). The basic workflow is the
+same for all:
+1. Find or create an issue in the [Cassandra 
JIRA](https://issues.apache.org/jira/browse/CASSANDRA/) that describes the work 
you plan to do.
+2. Clone the [Apache Cassandra GitHub 
repo](https://github.com/apache/cassandra).
+3. Create your feature branch. Suggestion: name your branch with the related 
JIRA id: e.g. CASSANDRA-12345 .
+4. Make, build, test and self-review your changes on your feature branch.
+5. Submit the patch, either by attaching a patch file to your JIRA, creating a 
GitHub pull request, or posting a

Review Comment:
   it seems that ”attaching a patch file to your JIRA“ has not been used for a 
long time. @michaelsembwever  am i right ?



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to