mirror of
https://github.com/TeamNewPipe/NewPipe
synced 2024-11-18 15:54:58 +00:00
34 lines
1.4 KiB
Markdown
34 lines
1.4 KiB
Markdown
#Contribution
|
|
|
|
This document contains guidelines on making contributions to NewPipe.
|
|
|
|
## Programming
|
|
|
|
* Follow the [Google Style Guidelines](https://google.github.io/styleguide/javaguide.html)
|
|
* Make a new feature on a separate branch, not on the master branch
|
|
* Make a [pull request](https://github.com/theScrabi/NewPipe/pulls) if you're done with your changes
|
|
* When submitting changes, you agree that your code will be GPLv3 licensed
|
|
|
|
## Commit messages
|
|
|
|
* The subject line of your commit message shouldn't be longer than 72 characters
|
|
* Try to keep each line of your commit message 72 characters to ensure proper
|
|
compatibility with all git tools
|
|
* [This guide](http://chris.beams.io/posts/git-commit/) goes more in depth on what makes a good commit message
|
|
|
|
## Translation
|
|
|
|
* NewPipe can be translated on [weblate](https://hosted.weblate.org/projects/newpipe/strings/)
|
|
|
|
## Issue reporting
|
|
|
|
* Search the [existing issues](https://github.com/theScrabi/NewPipe/issues) first to make sure your issue hasn't been reported before
|
|
* Check if this issue is already fixed in the repository
|
|
* When making bug reports, be sure to tell which version of NewPipe you are using and the steps to reproduce the problem
|
|
* Please include a log if you can
|
|
|
|
## Communication
|
|
|
|
* For the time being, [Slack](http://invite.chschtsch.ml/) is being used for project communication
|
|
* Feel free to post suggestions, changes, ideas etc!
|