Contribute to gsplat

Contribute to gsplat#

2025-09-26

2 min read time

Applies to Linux

If you are interested in contributing to gsplat, your contributions will generally fall into three categories:

  1. Reporting a bug, feature request, or documentation issue:

    • File an issue describing what you encountered or what you want to see changed.

    • The gsplat team will evaluate and triage issues, scheduling them for a release.

    • If you believe an issue needs priority attention, add a comment to notify the team.

  2. Proposing and implementing a new feature:

    • Post about your intended feature so the team can discuss the design and implementation.

    • Once the plan looks good, implement it following the Code contributions guide.

  3. Implementing a feature or bug fix for an existing issue:

    • Follow the Code contributions guide.

    • If you need more context about a particular issue, ask in the issue thread.

Code contributions#

Before contributing to ROCm documentation, read through the ROCm documentation contribution guidelines.

Create your first issue#

  1. Read the project README to learn how to set up the development environment.

  2. Find an issue to work on.

  3. Comment on the issue stating you plan to work on it.

  4. Write your code and update or add unit tests.

  5. When finished, create a pull request.

  6. Verify that continuous integration (CI) passes all status checks and fix any problems.

  7. Wait for other developers to review your code and make updates if needed.

  8. After approval, a gsplat developer will merge your pull request.

Note

If you are unsure about anything, comment on issues and ask for clarification.

Contribute as a seasoned developer#

Once you are comfortable with the codebase, you can look at prioritized issues for the next release in the project boards.

Always look at the release board with the highest number to find issues to work on, since this is where gsplat developers focus their efforts.

Check the unassigned issues, and choose one you are comfortable contributing to. Start with Step 3 from the Code contributions section by commenting on the issue to let others know you are working on it.

Tip

If you have questions about implementing the issue, ask them in the issue thread instead of in the pull request.