thank you for your interest in contributing to bevy_gaussian_splatting! contributions of all forms are welcome and appreciated. this includes code contributions, bug reports, documentation, or any other form of support.
as bevy_gaussian_splatting is a smaller project, the contribution process is more informal. feel free to contribute in a way that aligns with your interests and expertise. if you have any questions or need guidance, don't hesitate to reach out.
-
code contributions: if you have improvements or new features in mind, feel free to open a pull request. for larger changes, it's a good idea to discuss them first through a github issue.
-
bug reports: if you find any bugs, please open an issue describing the problem, including any relevant details that could help in resolving it.
-
documentation: improvements or additions to documentation are always welcome. this can include both inline code comments and updates to readme or other markdown files.
-
ideas and suggestions: have ideas for new features or ways to improve the project? open an issue to discuss your suggestions!
- ensure that any new code complies with the existing code style and structure.
- update the readme.md or other documentation with details of changes, if applicable.
- open a pull request with a clear description of the changes.
if you're unsure about something or need help, feel free to open an issue asking for guidance. as the project grows, we aim to make contributing as accessible and straightforward as possible.
while we don't have a formal code of conduct, we expect contributors to be respectful, open-minded, and collaborative. let's work together to maintain a welcoming and inclusive environment.