First and foremost, thank you for your interest in contributing to fennecs! Your involvement makes this project truly special and helps shape its future.
There are numerous ways to contribute, each equally valuable:
- 🐛 Reporting bugs and issues
- 👀 Reviewing issues and Pull Requests (PRs)
- 🛠️ Submitting or reviewing PRs for bug fixes
- 📚 Improving documentation
- 🎮 Creating or enhancing demos (we can never have too many!)
- 🗣️ Sharing your fennecs-powered games or simulations
- 🧪 Adding unit and integration tests (the more, the merrier!)
fennecs is in its early stages, which means it's highly flexible and open to evolution. While this is exciting, it also means we need to be mindful of its direction.
However, we absolutely encourage you to experiment and build anything you like in your own forks of fennecs. We'd love to hear about your creations!
For support questions, please join our vibrant community on Discord. The issue tracker is reserved for bug reports and feature discussions.
- New contributors should submit their work as Pull Requests via GitHub.
- All contributions must be compatible with the MIT license. If you're including MIT-licensed work from others, please let us know so we can properly attribute them.
- As fennecs is distributed as a .NET package on NuGet (and potentially other registries), contributions should not introduce dependencies to other packages or include game-engine-specific code paths.
- Engine-specific code and bindings are welcome, but in supplementary packages (e.g., the
fennecs-godot
addon).
We value your contributions! Contributors will be listed in the project's MIT LICENSE file. We'll use your real name if provided, or your GitHub username otherwise. The order is based on commit counts as shown in the Contributors section on GitHub.
fennecs is crafted with 💘 love & foxes 🦊, but it's made by amazing people like you!
Your passion, creativity, and effort drive this project forward. Let's build something extraordinary together!