|
1 | | -## Submitting Desktop Client issues |
2 | | - |
3 | | -If you have questions about how to use the Nextcloud Desktop Client, please |
4 | | -visit our [support site][support] or our [forum][forum]. |
5 | | -We are also available on [IRC][irc]. |
| 1 | +## Contributing by reporting issues |
| 2 | +* **Always report bugs via Github**: that is the most reliable way to contacts us since we do not follow any process to check the forum and social media. |
| 3 | +* **For questions about the Nextcloud Desktop Client, use the [📋 Forum](https://help.nextcloud.com)**. |
| 4 | +* Alternativately, we also have [🐣 Twitter](https://twitter.com/Nextclouders) and [🐘 Mastodon](https://mastodon.xyz/@nextcloud) accounts. |
6 | 5 |
|
7 | 6 | ### Bug Reporting Guidelines |
8 | | -* __Important__: Report the issue using our [template][template], it includes all the |
9 | | - information we need to track down the issue. |
10 | | -* __SECURITY__: Report any potential security bug by following our [security policy](https://nextcloud.com/security/) instead of filing an issue in our bug tracker |
| 7 | +* __Important__: [Complete the bug report form](https://github.com/nextcloud/desktop/issues/new/choose). If you fill it correctly, it should give us enough information to start working on the issue. |
| 8 | +* __SECURITY__: **Please do _not_ report security vulnerabilities through public GitHub issues.** |
| 9 | +If you have discovered a security matter with Nextcloud, please first read our [responsible disclosure guidelines](https://nextcloud.com/security/) and our [security policy](https://github.com/nextcloud/server/blob/9459724e72d647bb21d0bc36c6dc56b751771130/SECURITY.md). Then contact us at [hackerone.com/nextcloud](https://hackerone.com/nextcloud). |
11 | 10 | * This repository is *only* for issues within the Nextcloud desktop client. |
12 | 11 | Issues in other components should be reported in their own repositores: |
13 | 12 | - [Nextcloud server](https://github.com/nextcloud/server/issues) |
14 | 13 | - [Android client](https://github.com/nextcloud/android/issues) |
15 | 14 | - [iOS client](https://github.com/nextcloud/ios/issues) |
16 | 15 | * Search the existing issues first, it's likely that your issue was already |
17 | 16 | reported. |
18 | | - |
19 | | -If your issue appears to be a bug, and hasn't been reported, open a new issue. |
20 | | - |
21 | | -Help us to maximize the effort we can spend fixing issues and adding new |
22 | | -features, by not reporting duplicate issues. |
23 | | - |
24 | | -[template]: https://raw.githubusercontent.com/nextcloud/desktop/master/.github/issue_template.md |
25 | | -[support]: https://nextcloud.com/support/ |
26 | | -[forum]: https://help.nextcloud.com/categories |
27 | | -[irc]: https://webchat.freenode.net/?channels=nextcloud |
| 17 | +* If your issue appears to be a bug and hasn't been reported, open a new issue. |
| 18 | + Help us to maximize the effort we can spend fixing issues and adding new features, by not reporting duplicate issues. |
28 | 19 |
|
29 | 20 | ## Contributing to Source Code |
30 | | - |
31 | 21 | Thanks for wanting to contribute source code to Nextcloud. That's great! |
32 | 22 |
|
33 | | -You do not need to sign a Contributor Agreement, but we ask that you follow our |
34 | | -[Code of Conduct](https://nextcloud.com/code-of-conduct/). |
| 23 | +We ask that you follow our [Code of Conduct](https://nextcloud.com/code-of-conduct/). |
35 | 24 |
|
36 | 25 | Please read the [Contribution Guide](https://nextcloud.com/contribute/) to get |
37 | 26 | started and follow the [Coding Style](https://github.com/nextcloud/desktop/wiki/Coding-Style) |
38 | 27 | when writing new code. |
39 | 28 |
|
| 29 | +### Sign your work |
| 30 | + |
| 31 | +We use the Developer Certificate of Origin (DCO) as an additional safeguard |
| 32 | +for the Nextcloud project. This is a well established and widely used |
| 33 | +mechanism to assure contributors have confirmed their right to license |
| 34 | +their contribution under the project's license. |
| 35 | +Please read [contribute/developer-certificate-of-origin][dcofile]. |
| 36 | +If you can certify it, then just add a line to every git commit message: |
| 37 | + |
| 38 | +``` |
| 39 | +Signed-off-by: Random J Developer <random@developer.example.org> |
| 40 | +``` |
| 41 | + |
| 42 | +Use your real name (sorry, no pseudonyms or anonymous contributions). |
| 43 | +If you set your `user.name` and `user.email` git configs, you can sign your |
| 44 | +commit automatically with `git commit -s`. You can also use git [aliases](https://git-scm.com/book/tr/v2/Git-Basics-Git-Aliases) |
| 45 | +like `git config --global alias.ci 'commit -s'`. Now you can commit with |
| 46 | +`git ci` and the commit will be signed. |
| 47 | + |
| 48 | + |
40 | 49 | ## Translations |
41 | 50 | Please submit translations via [Transifex](https://www.transifex.com/nextcloud/nextcloud/). |
0 commit comments