|
1 | | -# Code of Conduct |
2 | | - |
3 | | -Welcome to the **Monitor My Solar** repository! To create a collaborative and productive environment, we ask that all contributors and users adhere to the following guidelines. |
4 | | - |
5 | | -## 1. Respect and Courtesy |
6 | | - |
7 | | -We are committed to providing a friendly, safe, and welcoming environment for everyone. Please treat others with respect and courtesy, and use welcoming and inclusive language. |
8 | | - |
9 | | -## 2. Search Issues Before Posting |
10 | | - |
11 | | -Before opening a new issue, **please check the existing issues** to see if your question or problem has already been reported. Duplicate issues can clutter the tracker and make it difficult to focus on current issues. If your issue is similar to an existing one, feel free to add a comment instead of opening a new issue. |
12 | | - |
13 | | -## 3. Issue and Pull Request Guidelines |
14 | | - |
15 | | -- **Issues**: Provide a clear and concise description of the problem, steps to reproduce, and any relevant screenshots or error messages. Make sure to use appropriate labels if applicable. |
16 | | -- **Pull Requests**: Ensure that your pull request includes a **detailed description** of the changes you are making. If it addresses an issue, reference the issue number. Describe the purpose of the feature or bug fix and provide any relevant context. |
17 | | - |
18 | | -## 4. License Compliance |
19 | | - |
20 | | -By contributing to this repository, you agree that all code is subject to the terms of our [LICENSE](../LICENSE). Ensure that your contributions do not include unlicensed or incompatible code from third-party sources. Respect the license terms for any code, dependencies, or resources included in your contributions. |
21 | | - |
22 | | -## 5. Constructive Feedback and Reviews |
23 | | - |
24 | | -When reviewing others’ contributions, focus on providing **constructive feedback**. Be clear, specific, and kind in your suggestions. If you receive feedback, consider it thoughtfully and respond courteously. |
25 | | - |
26 | | -## 6. Reporting Issues |
27 | | - |
28 | | -If you observe any behavior that violates this Code of Conduct or makes you feel uncomfortable, please report it by contacting the repository maintainers. We are committed to addressing and resolving all issues fairly and promptly. |
29 | | - |
30 | | -## 7. Consequences |
31 | | - |
32 | | -Failure to adhere to this Code of Conduct may result in actions ranging from warnings to more severe consequences, such as temporary or permanent restrictions on participation in the repository. |
33 | | - |
34 | | -## 8. Contact |
35 | | - |
36 | | -For questions or concerns about this Code of Conduct, please reach out to the repository maintainers directly. |
37 | | - |
38 | | -Thank you for contributing to a positive and productive community! |
| 1 | +# Code of Conduct |
| 2 | + |
| 3 | +Welcome to the **Monitor My Solar** repository! To create a collaborative and productive environment, we ask that all contributors and users adhere to the following guidelines. |
| 4 | + |
| 5 | +## 1. Respect and Courtesy |
| 6 | + |
| 7 | +We are committed to providing a friendly, safe, and welcoming environment for everyone. Please treat others with respect and courtesy, and use welcoming and inclusive language. |
| 8 | + |
| 9 | +## 2. Search Issues Before Posting |
| 10 | + |
| 11 | +Before opening a new issue, **please check the existing issues** to see if your question or problem has already been reported. Duplicate issues can clutter the tracker and make it difficult to focus on current issues. If your issue is similar to an existing one, feel free to add a comment instead of opening a new issue. |
| 12 | + |
| 13 | +## 3. Issue and Pull Request Guidelines |
| 14 | + |
| 15 | +- **Issues**: Provide a clear and concise description of the problem, steps to reproduce, and any relevant screenshots or error messages. Make sure to use appropriate labels if applicable. |
| 16 | +- **Pull Requests**: Ensure that your pull request includes a **detailed description** of the changes you are making. If it addresses an issue, reference the issue number. Describe the purpose of the feature or bug fix and provide any relevant context. |
| 17 | + |
| 18 | +## 4. License Compliance |
| 19 | + |
| 20 | +By contributing to this repository, you agree that all code is subject to the terms of our [LICENSE](../LICENSE). Ensure that your contributions do not include unlicensed or incompatible code from third-party sources. Respect the license terms for any code, dependencies, or resources included in your contributions. |
| 21 | + |
| 22 | +## 5. Constructive Feedback and Reviews |
| 23 | + |
| 24 | +When reviewing others’ contributions, focus on providing **constructive feedback**. Be clear, specific, and kind in your suggestions. If you receive feedback, consider it thoughtfully and respond courteously. |
| 25 | + |
| 26 | +## 6. Reporting Issues |
| 27 | + |
| 28 | +If you observe any behavior that violates this Code of Conduct or makes you feel uncomfortable, please report it by contacting the repository maintainers. We are committed to addressing and resolving all issues fairly and promptly. |
| 29 | + |
| 30 | +## 7. Consequences |
| 31 | + |
| 32 | +Failure to adhere to this Code of Conduct may result in actions ranging from warnings to more severe consequences, such as temporary or permanent restrictions on participation in the repository. |
| 33 | + |
| 34 | +## 8. Contact |
| 35 | + |
| 36 | +For questions or concerns about this Code of Conduct, please reach out to the repository maintainers directly. |
| 37 | + |
| 38 | +Thank you for contributing to a positive and productive community! |
0 commit comments