-
Notifications
You must be signed in to change notification settings - Fork 49
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add CODE_OF_CONDUCT and CONTRIBUTING
- Loading branch information
1 parent
4c79b5e
commit 6f195dc
Showing
2 changed files
with
80 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,43 @@ | ||
# Code of Conduct | ||
|
||
## Our Commitment | ||
|
||
In the interest of fostering an open and friendly community, we, as contributors and maintainers, pledge to make participation in our project and our community a harassment-free experience for everyone. | ||
|
||
## Standards of Behavior | ||
|
||
1. **Respect**: Be respectful and considerate of different viewpoints and experiences. | ||
|
||
2. **Collaboration**: Collaborate with community members, uphold principles of openness, and assist each other. | ||
|
||
3. **Friendliness**: Remember that diversity of opinions and experiences is valuable for our community. Be friendly and supportive. | ||
|
||
4. **Responsibility**: Be mindful of your words and actions. If you make a commitment, strive to fulfill it. | ||
|
||
## Unacceptable Behavior | ||
|
||
Unacceptable behavior includes but is not limited to: | ||
|
||
1. **Discrimination**: No forms of discrimination or harassment based on race, gender, sexual orientation, nationality, religion, or other characteristics. | ||
|
||
2. **Insults and Threats**: No offensive comments, threats, or bullying. | ||
|
||
3. **Hostile Conduct**: No actions intended to create a hostile atmosphere in the community. | ||
|
||
## Reporting Procedure | ||
|
||
If you believe you're experiencing a violation of the code of conduct, please report it by sending an email to darkmoonight2022@gmail.com. | ||
|
||
## Conclusion | ||
|
||
We encourage all participants to adhere to this code of conduct. Violation of these principles may result in temporary or permanent exclusion from the community. | ||
|
||
Thank you for your contribution and cooperation in creating an open and friendly community! | ||
|
||
## Changes | ||
|
||
This code of conduct may be revised from time to time. The most current version will always be available in this file. | ||
|
||
## Attribution | ||
|
||
This code of conduct is adapted from [Contributor Covenant](https://www.contributor-covenant.org/). |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,37 @@ | ||
# Contribution Guidelines | ||
|
||
Thank you for considering contributing to our project! We welcome your input and appreciate your efforts. To ensure a smooth collaboration, please take a moment to review the following guidelines. | ||
|
||
## Code of Conduct | ||
|
||
This project and everyone participating in it are governed by our [Code of Conduct](CODE_OF_CONDUCT.md). By participating, you are expected to uphold this code. Please report unacceptable behavior to [project email]. | ||
|
||
## How to Contribute | ||
|
||
1. Fork the repository and clone it locally. | ||
2. Create a new branch for your feature or bug fix. | ||
3. Make your changes and commit them. | ||
4. Push your changes to your fork on GitHub. | ||
5. Open a pull request in the original repository. Provide a clear title and description of your changes. | ||
|
||
## Coding Standards | ||
|
||
Follow the coding standards and style guide used in the project. If there's no specific guide, stick to the existing code style. | ||
|
||
## Testing | ||
|
||
Ensure that your code changes do not break existing functionality. Write tests for new features or bug fixes if applicable. | ||
|
||
## Documentation | ||
|
||
Update the documentation if your changes affect it. This includes the README.md file and any additional documentation files. | ||
|
||
## Issues | ||
|
||
Before starting work on a new feature or bug fix, check the issue tracker for related discussions or known issues. | ||
|
||
## License | ||
|
||
By contributing, you agree that your contributions will be licensed under the project's license. | ||
|
||
Thank you for your contribution! |