Contributing to Tusk ❤
Thank you for taking the time to contribute to Tusk!
Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms.
How to contribute!
Typo corrections, error fixes, better explanations, more examples etc. Open an issue regarding anything that you think it could be improved! You can use the
docs label to find out what others have suggested!
Sometimes reported issues lack information, are not reproducible, or are even plain invalid. Help us out to make them easier to resolve. Handling issues takes a lot of time that we could rather spend on fixing bugs and adding features.
Give feedback on issues
We're always looking for more opinions on discussions in the issue tracker. It's a good opportunity to influence the future direction of the project.
question label is a good place to find ongoing discussions.
You can use issue labels to discover issues you could help us out with!
enhancementissues are features we are open to including
bugissues are known bugs we would like to fix
needs testingissues are features that we are still working on improving
futureissues are those that we'd like to get to, but not anytime soon. Please check before working on these since we may not yet want to take on the burden of supporting those features
- on the
help wantedlabel you can always find something exciting going on
You may find an issue is assigned, or has the
assigned label. Please double-check before starting on this issue because somebody else is likely already working on it
Come over and say hi anytime you feel like on Gitter.
- Make sure that the document is not already translated in that language.
- Add the name of the language to the document as an extension, e.g:
- Place the translated document inside the
- Create a Pull Request including the language in the title, e.g:
Readme: Japanese Translation
Submitting an issue
- Search the issue tracker before opening an issue
- Ensure you're using the latest version of Tusk:
- Use a descriptive title
- Include as much information as possible;
- Steps to reproduce the issue
- App settings
- Error message
- Tusk version
- Operating system etc
Submitting a pull request
- Non-trivial changes are often best discussed in an issue first, to prevent you from doing unnecessary work
- Try making the pull request from a topic branch if it is of crucial importance
- Use a descriptive title for the pull request and commits
- You might be asked to do changes to your pull request, you can do that by just updating the existing one
Inspired by project AVA's contributing.md