You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to make participation in our project and our community a positive experience for everyone, regardless of age, body size, disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
7
+
8
+
## Our Standards
9
+
10
+
Examples of behavior that contribute to creating a positive environment include:
11
+
12
+
- Using welcoming and inclusive language
13
+
- Being respectful of differing viewpoints and experiences
14
+
- Gracefully accepting constructive criticism
15
+
- Focusing on what is best for the community
16
+
- Showing empathy towards other community members
17
+
18
+
Examples of unacceptable behavior by participants include:
19
+
20
+
- The use of sexualized language or imagery and unwelcome sexual attention or advances
21
+
- Trolling, insulting/derogatory comments, and personal or political attacks
22
+
- Public harassment
23
+
- Publishing others' private information, such as a physical or electronic address, without explicit permission
24
+
- Other conduct which could reasonably be considered inappropriate in a professional setting
25
+
26
+
## Our Responsibilities
27
+
28
+
Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
29
+
30
+
## Enforcement
31
+
32
+
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the project team at [INSERT CONTACT METHOD HERE]. All complaints will be reviewed and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident.
33
+
34
+
## Attribution
35
+
36
+
This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org/), version 1.4, available at https://www.contributor-covenant.org/version/1/4/
Thank you for considering contributing to CountryData.Net We appreciate all forms of contributions, whether it's fixing bugs, adding new features, updating documentation, or even just discussing ideas. Your input is invaluable to us.
6
+
7
+
## Getting Started
8
+
9
+
Before you start contributing, please go through our [Code of Conduct](CODE_OF_CONDUCT.md) to ensure a positive experience for everyone involved.
10
+
11
+
### How Can I Contribute?
12
+
13
+
There are many ways you can contribute to CountryData.Net:
14
+
15
+
#### Reporting Bugs
16
+
17
+
If you find a bug, please create an issue on GitHub. Make sure to describe the problem in detail, including steps to reproduce the issue, what you expect to happen, and what actually happens.
18
+
19
+
#### Suggesting Enhancements
20
+
21
+
For feature requests and enhancements, open an issue first to discuss the change you wish to make. This allows us to better coordinate efforts, prevent duplicate work, and help define the scope of the proposal.
22
+
23
+
#### Creating Pull Requests
24
+
25
+
Pull requests are the best way to propose changes to the project. They allow us to review your modifications before merging them into the main branch. Please follow these steps to create a pull request:
26
+
27
+
1. Fork the Project Repository.
28
+
2. Create a new branch for your changes.
29
+
3. Commit your changes to the new branch.
30
+
4. Push your branch to GitHub.
31
+
5. Open a Pull Request against the original repository.
32
+
33
+
Please ensure your pull request adheres to the following rules:
34
+
35
+
- Each pull request should implement one feature or fix a bug.
36
+
- Avoid mixing unrelated changes.
37
+
- Update the README.md with details of changes to the interface.
38
+
- Increase coverage by writing unit tests.
39
+
- Check existing open issues/pull requests first to avoid duplicating effort.
40
+
41
+
### Style Guide
42
+
43
+
- Follow the existing style guide. Consistency is key!
44
+
- Keep commits small and focused. Large commits are hard to review and often lead to merge conflicts.
45
+
- Write meaningful commit messages. Good practice is to write clear, concise messages that explain what was changed and why.
46
+
47
+
48
+
Remember, every contribution counts, no matter how big or small. Thank you for taking the time to improve CountryData.Net!
0 commit comments