Daft is an open-source project and we welcome contributions from the community. Whether you're reporting bugs, proposing features, or contributing code, this guide will help you get started.
- Found a bug? 🐛 Report it here
- Have a feature idea? 💡 Start a discussion
- Want to make your first PR? 🚀 Contribute new code
To report bugs and issues with Daft, please file an issue on our issues page.
Additionally, please include the following information in your bug report:
- Operating system
- Daft version
- Python version
- Daft runner (native or Ray)
We highly encourage you to propose new features or ideas. Please start a GitHub Discussion in our Ideas channel.
When proposing features, please include:
- Feature Summary (no more than 3 sentences)
- Example usage (pseudo-code to show how it is used)
- Corner-case behavior (how should this code behave in various corner-case scenarios)
For detailed development instructions, see our Development Guide.
The Daft contributor community celebrates and supports the contributors who have helped shape the project into what it is today. Whether you’re submitting your first pull request or enhancing the documentation, you’ll find a place in our growing community. Members contribute in different ways and take on a variety of roles.
A user is someone who interacts with our software. They support the Daft project by sharing feedback with developers through bug reports and feature requests. Users also enrich the Daft community by answering questions and assisting others on mailing lists and support forums.
A contributor is someone who actively adds to the project through code or documentation. They go beyond basic use by engaging with the developer mailing list, joining discussions, and offering patches, documentation, suggestions, or constructive feedback.
A committer is a developer who has consistently made meaningful contributions to the project and has been invited to this role based on the merit of their work. Committers are granted write access to specific parts of the code repository, have a signed committer agreement on file. With the ability to apply patches directly to code or documentation, they can make short-term decisions within their areas of expertise. These changes are then subject to review: the Daft Punqs may approve them as permanent or choose to reject them.
A Daft Punq is a committer who is part of the core Daft team, recognized for sustained and meaningful contributions to the project’s growth and direction over time. They hold write access to the code repository, voting rights on community decisions, and the ability to nominate other active contributors for committership.