👍🎉 First off, thanks for taking the time to contribute! 🎉👍
These are the specific contributing guidelines for the server repository. This is for those interested in optimizing the way we run inference or the algorithms we use to provide feedback. Checkout our general contributing guidelines here.
- Read the README.md file to understand the purpose of this repository.
- Read the DEVELOPMENT.md file to understand how to set up your local development environment. Important design decisions will also be documented here.
- Read the Code of Conduct to understand expectations while contributing to this project and take a look at the FAQ if you have any questions.
- Read through the issues to understand the current development priorities.
- All contributions start with an issue to discuss the change. See how to file a bug report, suggest a new feature, or make your first code contribution.
- Look for the issues tagged
good first issue
andhelp wanted
for things to work on. - Make sure to check the existing issues before creating a new one.
- Look for the issues tagged
- Maintainers with write access to the repository will assign willing contributors to issues they request. Once assigned, fork the repository and create a branch for your work.
- When you are ready, submit a pull request to the
main
branch. The pull request template contains a checklist to go through.
If you have any questions, feel free to reach out to alex@koellabs.com or open an issue. Security vulnerabilities should be reported to info@koellabs.com.
By making contributions to the Koel Labs project, you agree to retain all rights, title and interest in and to your contributions and confirm that Koel Labs can use, modify, copy, and redistribute said contributions, under its choice of terms.