|
| 1 | +# Contributing to Monitorian |
| 2 | + |
| 3 | +Thanks to your interest in contributing to this project. |
| 4 | + |
| 5 | +## 1. Issues |
| 6 | + |
| 7 | +Please take following steps to open an issue. |
| 8 | + |
| 9 | +- Read through [Detection of external monitors](https://github.com/emoacht/Monitorian#detection-of-external-monitors) and [Reporting](https://github.com/emoacht/Monitorian#reporting) in readme. |
| 10 | + |
| 11 | +- Search [Issues](https://github.com/emoacht/Monitorian/issues) to date. To search open and closed issues at once, remove `is:open` from default syntax in Filters box and use only `is:issue` syntax. |
| 12 | + |
| 13 | +- Include all information necessary for a reader who has no knowledge about your monitor or other devices to understand the issue. Include how to reproduce the issue as well. |
| 14 | + |
| 15 | +- Add logs. A video clip is not so helpful because it will not give information on what is happening internally. |
| 16 | + |
| 17 | +- <ins>Be prepared to respond to a request after opening an issue.</ins> It is merely a startig point and you will be requested to provide additional information in most cases. |
| 18 | + |
| 19 | +## 2. Feature requests or suggestions |
| 20 | + |
| 21 | +Do not open feature requests or suggestions in __Ideas__ of __Discussions__ in this project. It is for aggregating them in __Issues__. |
| 22 | + |
| 23 | +Please take following points into account to open a feature request or suggestion. |
| 24 | + |
| 25 | +- This app's main focus and competence is brigtness of monitors. This app uses DDC/CI for this purpose, and not vice versa. The importance for keeping focused cannot be overemphasized. |
| 26 | + |
| 27 | +- Search [Issues](https://github.com/emoacht/Monitorian/issues) to date. |
| 28 | + |
| 29 | +- Explain the necessity and added value of the feature. Describe how the feature could be useful in actual use cases or scenarios. An existing feature of other app will not be reason for adding the same to this app. |
| 30 | + |
| 31 | +- Include technical information to implement the feature as much as possible. A feature which is not technically feasible cannot be added anyways. |
| 32 | + |
| 33 | +- <ins>Be prepared to respond to a request after opening a feature request or suggestion.</ins> It is merely a starting point and you will be requested to provide additional information in most cases. |
| 34 | + |
| 35 | +## 3. Pull requests |
| 36 | + |
| 37 | +### 3.1 PR for language |
| 38 | + |
| 39 | +- Read [Globalization](https://github.com/emoacht/Monitorian#globalization) in readme. |
| 40 | +- Use a phrase used by the OS as much as possible. |
| 41 | +- Do not try to explain everything. You cannot create a flawless expression in a short sentence like menu item. |
| 42 | + |
| 43 | +### 3.2 PR for functionality |
| 44 | + |
| 45 | +- Open an issue and get agreement for your proposed change before starting your work. |
| 46 | +- It is recommended to use the latest features of C#. |
0 commit comments