mirrors/NewPipe
1
0
Fork 0
mirror of https://github.com/TeamNewPipe/NewPipe synced 2024-11-17 23:34:54 +00:00
Code Issues Releases Wiki Activity
1984436b41
NewPipe/.github/CONTRIBUTING.md

47 lines
4.0 KiB
Markdown
Raw Normal View History

update contribution guidelines
2016-09-27 11:43:43 +00:00
NewPipe contribution guidelines
===============================
Add contribution guidelines Contribution guidelines are a helpful way to inform new potential contributors about the way in which they can help with the project. It's also a helpful way to enforce some consistent coding style and quality among the contributions.
2015-12-22 15:14:56 +00:00
update contribution guidelines once again
2016-09-27 12:14:59 +00:00
## Crash reporting
Add contribution guidelines Contribution guidelines are a helpful way to inform new potential contributors about the way in which they can help with the project. It's also a helpful way to enforce some consistent coding style and quality among the contributions.
2015-12-22 15:14:56 +00:00
Contributing guidelines reworked (#4318) * Contributing guidelines reworked Co-authored-by: opusforlife2 <53176348+opusforlife2@users.noreply.github.com> Co-authored-by: bopol <bopol@e.email> Co-authored-by: Tobias Groza <TobiGr@users.noreply.github.com>
2020-11-28 11:00:00 +00:00
Report crashes through the automated crash report system of NewPipe.
This way all the data needed for debugging is included in your bugreport for GitHub.
You'll see exactly what is sent, be able to add your comments, and then send it.
Add contribution guidelines Contribution guidelines are a helpful way to inform new potential contributors about the way in which they can help with the project. It's also a helpful way to enforce some consistent coding style and quality among the contributions.
2015-12-22 15:14:56 +00:00
Fix bugs in CONTRIBUTING.md Spelling and grammar bugs, a few additions here and there, make it sound like a team project instead of a one-man show.
2017-08-02 21:34:46 +00:00
## Issue reporting/feature requests
Add contribution guidelines Contribution guidelines are a helpful way to inform new potential contributors about the way in which they can help with the project. It's also a helpful way to enforce some consistent coding style and quality among the contributions.
2015-12-22 15:14:56 +00:00
Contributing guidelines reworked (#4318) * Contributing guidelines reworked Co-authored-by: opusforlife2 <53176348+opusforlife2@users.noreply.github.com> Co-authored-by: bopol <bopol@e.email> Co-authored-by: Tobias Groza <TobiGr@users.noreply.github.com>
2020-11-28 11:00:00 +00:00
* **Already reported**? Browse the [existing issues](https://github.com/TeamNewPipe/NewPipe/issues) to make sure your issue/feature hasn't been reported/requested.
* **Already fixed**? Check whether your issue/feature is already fixed/implemented.
* **Still relevant**? Check if the issue still exists in the latest release/beta version.
* **Can you fix it**? If you are an Android/Java developer, you are always welcome to fix an issue or implement a feature yourself. PRs welcome! See [Code contribution](#code-contribution) for more info.
* **Is it in English**? Issues in other languages will be ignored unless someone translates them.
* **Is it one issue**? Multiple issues require multiple reports, that can be linked to track their statuses.
* **The template**: Fill it out, everyone wins. Your issue has a chance of getting fixed.
Add contribution guidelines Contribution guidelines are a helpful way to inform new potential contributors about the way in which they can help with the project. It's also a helpful way to enforce some consistent coding style and quality among the contributions.
2015-12-22 15:14:56 +00:00
Update CONTRIBUTING.md
2017-02-11 23:16:41 +00:00
update resources names to match naming convention & cleanup & start working on themes
2016-01-05 19:56:40 +00:00
## Translation
Add contribution guidelines Contribution guidelines are a helpful way to inform new potential contributors about the way in which they can help with the project. It's also a helpful way to enforce some consistent coding style and quality among the contributions.
2015-12-22 15:14:56 +00:00
Contributing guidelines reworked (#4318) * Contributing guidelines reworked Co-authored-by: opusforlife2 <53176348+opusforlife2@users.noreply.github.com> Co-authored-by: bopol <bopol@e.email> Co-authored-by: Tobias Groza <TobiGr@users.noreply.github.com>
2020-11-28 11:00:00 +00:00
* NewPipe is translated via [Weblate](https://hosted.weblate.org/projects/newpipe/strings/). Log in there with your GitHub account, or register.
* Add the language you want to translate if it is not there already: see [How to add a new language](https://github.com/TeamNewPipe/NewPipe/wiki/How-to-add-a-new-language-to-NewPipe) in the wiki.
Add contribution guidelines Contribution guidelines are a helpful way to inform new potential contributors about the way in which they can help with the project. It's also a helpful way to enforce some consistent coding style and quality among the contributions.
2015-12-22 15:14:56 +00:00
update contribution guidelines
2016-09-27 11:43:43 +00:00
## Code contribution
Update and rename contributing.md to CONTRIBUTING.md
2015-12-23 08:31:11 +00:00
Contributing guidelines reworked (#4318) * Contributing guidelines reworked Co-authored-by: opusforlife2 <53176348+opusforlife2@users.noreply.github.com> Co-authored-by: bopol <bopol@e.email> Co-authored-by: Tobias Groza <TobiGr@users.noreply.github.com>
2020-11-28 11:00:00 +00:00
* If you want to help out with an existing bug report or feature request, leave a comment on that issue saying you want to try your hand at it.
* If there is no existing issue for what you want to work on, open a new one describing your changes. This gives the team and the community a chance to give feedback before you spend time on something that is already in development, should be done differently, or should be avoided completely.
* Stick to NewPipe's style conventions of [checkStyle](https://github.com/checkstyle/checkstyle). It runs each time you build the project.
* Do not bring non-free software (e.g. binary blobs) into the project. Make sure you do not introduce Google
update contribution guidelines
2018-12-01 08:21:57 +00:00
libraries.
Update .github/CONTRIBUTING.md Co-Authored-By: Tobias Groza <TobiGr@users.noreply.github.com>
2020-04-04 10:28:20 +00:00
* Stick to [F-Droid contribution guidelines](https://f-droid.org/wiki/page/Inclusion_Policy).
Contributing guidelines reworked (#4318) * Contributing guidelines reworked Co-authored-by: opusforlife2 <53176348+opusforlife2@users.noreply.github.com> Co-authored-by: bopol <bopol@e.email> Co-authored-by: Tobias Groza <TobiGr@users.noreply.github.com>
2020-11-28 11:00:00 +00:00
* Make changes on a separate branch with a meaningful name, not on the _master_ branch or the _dev_ branch. This is commonly known as *feature branch workflow*. You may then send your changes as a pull request (PR) on GitHub.
* Please test (compile and run) your code before submitting changes! Ideally, provide test feedback in the PR description. Untested code will **not** be merged!
* Make sure your PR is up-to-date with the rest of the code. Often, a simple click on "Update branch" will do the job, but if not, you must rebase the dev branch manually and resolve the problems on your own. You can find help [on the wiki](https://github.com/TeamNewPipe/NewPipe/wiki/How-to-merge-a-PR). That makes the maintainers' jobs way easier.
* Please show intention to maintain your features and code after you contribute a PR. Unmaintained code is a hassle for core developers. If you do not intend to maintain features you plan to contribute, please rethink your submission, or clearly state that in the PR description.
* Respond if someone requests changes or otherwise raises issues about your PRs.
* Send PRs that only cover one specific issue/solution/bug. Do not send PRs that are huge and consist of multiple independent solutions.
Fix bugs in CONTRIBUTING.md Spelling and grammar bugs, a few additions here and there, make it sound like a team project instead of a one-man show.
2017-08-02 21:34:46 +00:00
* Try to figure out yourself why builds on our CI fail.
Update and rename contributing.md to CONTRIBUTING.md
2015-12-23 08:31:11 +00:00
Add contribution guidelines Contribution guidelines are a helpful way to inform new potential contributors about the way in which they can help with the project. It's also a helpful way to enforce some consistent coding style and quality among the contributions.
2015-12-22 15:14:56 +00:00
## Communication
Contributing guidelines reworked (#4318) * Contributing guidelines reworked Co-authored-by: opusforlife2 <53176348+opusforlife2@users.noreply.github.com> Co-authored-by: bopol <bopol@e.email> Co-authored-by: Tobias Groza <TobiGr@users.noreply.github.com>
2020-11-28 11:00:00 +00:00
* The [#newpipe](irc:irc.freenode.net/newpipe) channel on freenode has the core team and other developers in it. [Click here for webchat](https://webchat.freenode.net/?channels=newpipe)!
* You can also use a Matrix account to join the Newpipe channel at [#freenode_#newpipe:matrix.org](https://matrix.to/#/#freenode_#newpipe:matrix.org).
* Post suggestions, changes, ideas etc. on GitHub or IRC.
Reference in New Issue Copy Permalink