NVIDIA · sameerz · Aug 19, 2026 · Aug 20, 2026 · Aug 20, 2026 · Aug 20, 2026
@@ -1,6 +1,6 @@
 ---
 name: Bug report
-about: Create a bug report to help us improve the RAPIDS Accelerator JNI for Apache Spark
+about: Create a bug report to help us improve the NVIDIA cuDF plugin JNI for Apache Spark
 title: "[BUG]"
 labels: "? - Needs Triage, bug"
 assignees: ''

@@ -1,14 +1,14 @@
 ---
 name: Feature request
-about: Suggest an idea for the RAPIDS Accelerator JNI for Apache Spark
+about: Suggest an idea for the NVIDIA cuDF plugin JNI for Apache Spark
 title: "[FEA]"
 labels: "? - Needs Triage, feature request"
 assignees: ''
 
 ---
 
 **Is your feature request related to a problem? Please describe.**
-A clear and concise description of what the problem is. Ex. I wish the RAPIDS Accelerator JNI for Apache Spark would [...]
+A clear and concise description of what the problem is. Ex. I wish the NVIDIA cuDF plugin JNI for Apache Spark would [...]
 
 **Describe the solution you'd like**
 A clear and concise description of what you want to happen.

@@ -1,6 +1,6 @@
 ---
 name: Submit question
-about: Ask a general question about RAPIDS Accelerator JNI for Apache Spark
+about: Ask a general question about NVIDIA cuDF plugin JNI for Apache Spark
 title: "[QST]"
 labels: "? - Needs Triage, question"
 assignees: ''

@@ -1,6 +1,6 @@
 <!--
 
-Thank you for contributing to RAPIDS Accelerator for Apache Spark!
+Thank you for contributing to NVIDIA cuDF plugin for Apache Spark!
 
 Here are some guidelines to help the review process go smoothly.
 

diff --git a/.github/workflows/action-helper/python/submodule-sync b/.github/workflows/action-helper/python/submodule-sync
@@ -1,6 +1,6 @@
 #!/usr/bin/env python
 
-# Copyright (c) 2022, NVIDIA CORPORATION.
+# Copyright (c) 2022-2026, NVIDIA CORPORATION.
 #
 # Licensed under the Apache License, Version 2.0 (the "License");
 # you may not use this file except in compliance with the License.
@@ -55,7 +55,7 @@ def main():
                 'base': pr.base,
                 'body': "submodule-sync to create a PR keeping thirdparty/cudf up-to-date.\n"
                         f"HEAD commit SHA: {args.sha}, "
-                        f"cudf commit SHA: https://github.com/rapidsai/cudf/commit/{args.cudf_sha}\n\n"
+                        f"cudf commit SHA: https://github.com/nvidia/cudf/commit/{args.cudf_sha}\n\n"
                         "This PR will be auto-merged if test passed. "
                         "If failed, it will remain open until test pass or manually fix.",
                 'maintainer_can_modify': True
@@ -65,7 +65,7 @@ def main():
                 sys.exit(0)
 
         pr.comment(number, content=f"HEAD commit SHA: {args.sha}, "
-                                   f"CUDF commit SHA: https://github.com/rapidsai/cudf/commit/{args.cudf_sha}\n"
+                                   f"CUDF commit SHA: https://github.com/nvidia/cudf/commit/{args.cudf_sha}\n"
                                    f"Test passed: **{args.passed}**")
 
         if args.passed:

@@ -12,7 +12,7 @@
 # See the License for the specific language governing permissions and
 # limitations under the License.
 
-# A workflow to sync the clang-format version between spark-rapids-jni and cudf
+# A workflow to sync the clang-format version between cudf-spark-jni and cudf
 name: sync clang-format version with cudf
 
 on:
@@ -60,8 +60,8 @@ jobs:
         env:
           GH_TOKEN: ${{ secrets.AUTOMERGE_TOKEN }}
           NEW_VER: ${{ steps.update_clang_format_version.outputs.new_ver }}
-          GIT_AUTHOR_NAME: "spark-rapids automation"
-          GIT_COMMITTER_NAME: "spark-rapids automation"
+          GIT_AUTHOR_NAME: "cudf-spark automation"
+          GIT_COMMITTER_NAME: "cudf-spark automation"
           GIT_AUTHOR_EMAIL: "70000568+nvauto@users.noreply.github.com"
           GIT_COMMITTER_EMAIL: "70000568+nvauto@users.noreply.github.com"
         run: |

diff --git a/.gitmodules b/.gitmodules
@@ -1,4 +1,4 @@
 [submodule "thirdparty/cudf"]
 	path = thirdparty/cudf
-	url = https://github.com/rapidsai/cudf.git
+	url = https://github.com/nvidia/cudf.git
 	branch = main
diff --git a/.pre-commit-config.yaml b/.pre-commit-config.yaml
@@ -32,7 +32,7 @@ repos:
           cudf_ver=$(grep -A1 "repo: $clang_format_pattern" "thirdparty/cudf/.pre-commit-config.yaml" | grep "rev:" | tail -1 | sed "s/.*rev: *//");
           if [ -z "$our_ver" ] || [ -z "$cudf_ver" ] || [ "$our_ver" != "$cudf_ver" ]; then
             echo "ERROR: clang-format version mismatch or failed to extract version!";
-            echo "  spark-rapids-jni: ${our_ver:-(empty)}";
+            echo "  cudf-spark-jni: ${our_ver:-(empty)}";
             echo "  cudf:             ${cudf_ver:-(empty)}";
             echo "Please update .pre-commit-config.yaml to use the same rev as cudf";
             exit 1;

diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md
@@ -2,7 +2,7 @@
 
 ## Overview
 
-Define the code of conduct followed and enforced by the RAPIDS Accelerator for Apache Spark project
+Define the code of conduct followed and enforced by the NVIDIA cuDF plugin for Apache Spark project
 
 ### Intended audience
 
@@ -42,7 +42,7 @@ This Code of Conduct applies both within project spaces and in public spaces whe
 
 ## Enforcement
 
-Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at  [spark-rapids-conduct@nvidia.com](mailto:spark-rapids-conduct@nvidia.com)  All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at  [cudf-spark-conduct@nvidia.com](mailto:cudf-spark-conduct@nvidia.com)  All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
 
 Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project’s leadership.