Contributing to Notebooks Extended

July 2, 2026 · View on GitHub

Contributions to notebooks-extended fall into the following 4 categories.

1. Find bugs in existing notebooks:

Sometimes things unexpectedly break in our notebooks
- File an issue describing what you encountered or what you want to see changed
- The RAPIDS team will evaluate the issues and triage them, scheduling them for a release
  - If you believe the issue needs priority attention, please comment on the issue to notify the team

2. Implement a bug fix or satisfy a feature request

To implement a feature or bug-fix for an existing outstanding issue, please follow the code contributions guide below
- If you need more context on a particular issue, please ask in a comment

3. Propose and create a new notebook:

To propose and implement a new notebook, please file a new feature request issue
- Describe the intended feature and discuss the design & implementation with the community
- Once the team agrees that the plan looks good, implement it using the code contributions guide below
- Test your notebook using our testing guide!
- Be sure that your PR includes an update the notebooks-contrib REAMDE with your notebook(s)'s title, location, description, and link. Failure to do so will delay your PR's merge until completion.

4. Create a tutorial or code walk through:

Show your expertise in RAPIDS while teaching people how to use RAPIDS in their data science pipeline

Code contributions

Your first issue

Follow the guide at the bottom of this page for Setting Up Your Build Environment.
Find an issue to work on. The best way is to look for the good first issue or help wanted labels.
Comment on the issue stating that you are going to work on it.
Code! Make sure to update unit tests!
When done, create your pull request.
Verify that CI passes all status checks. Fix if needed.
Wait for other developers to review your code and update code as needed.
Once reviewed and approved, a RAPIDS developer will merge your pull request.

Remember, if you are unsure about anything, don't hesitate to comment on issues and ask for clarifications!

Seasoned developers

Once you have gotten your feet wet and are more comfortable with the code, you can look at the prioritized issues for our next release in our project boards.

Pro Tip: Always look at the release board with the highest number for issues to work on. This is where RAPIDS developers also focus their efforts.

Look at the unassigned issues, and find an issue to which you are comfortable contributing. Start with Step 3 above, commenting on the issue to let others know you are working on it. If you have any questions related to the implementation of the issue, ask them in the issue instead of the PR.

Setting Up Your Build Environment

The following instructions are for developers and contributors to cuDF OSS development. These instructions are tested on Linux Ubuntu 16.04 & 18.04. Use these instructions to build cuDF from source and contribute to its development. Other operating systems may be compatible, but are not currently tested.

Signing Your Work

We require that all contributors "sign-off" on their commits. This certifies that the contribution is your original work, or you have rights to submit it under the same license, or a compatible license.
- Any contribution which contains commits that are not Signed-Off will not be accepted.
To sign off on a commit you simply use the --signoff (or -s) option when committing your changes:
```
$ git commit -s -m "Add cool feature."
```
This will append the following to your commit message:
```
Signed-off-by: Your Name <your@email.com>
```

Full text of the DCO (https://developercertificate.org/):

  Developer Certificate of Origin
  Version 1.1

  Copyright (C) 2004, 2006 The Linux Foundation and its contributors.

  Everyone is permitted to copy and distribute verbatim copies of this
  license document, but changing it is not allowed.


  Developer's Certificate of Origin 1.1

  By making a contribution to this project, I certify that:

  (a) The contribution was created in whole or in part by me and I
      have the right to submit it under the open source license
      indicated in the file; or

  (b) The contribution is based upon previous work that, to the best
      of my knowledge, is covered under an appropriate open source
      license and I have the right under that license to submit that
      work with modifications, whether created in whole or in part
      by me, under the same open source license (unless I am
      permitted to submit under a different license), as indicated
      in the file; or

  (c) The contribution was provided directly to me by some other
      person who certified (a), (b) or (c) and I have not modified
      it.

  (d) I understand and agree that this project and the contribution
      are public and that a record of the contribution (including all
      personal information I submit with it, including my sign-off) is
      maintained indefinitely and may be redistributed consistent with
      this project or the open source license(s) involved.