From c14857382f7904378648f97007be4f8588c9f72b Mon Sep 17 00:00:00 2001 From: Kamron Batman <3953314+kamronbatman@users.noreply.github.com> Date: Tue, 5 May 2020 08:51:04 -0700 Subject: [PATCH] Moves code of conduct --- CONTRIBUTING.md | 43 ++++++++++++++++++ Contributing.md | 117 ------------------------------------------------ 2 files changed, 43 insertions(+), 117 deletions(-) create mode 100644 CONTRIBUTING.md delete mode 100644 Contributing.md diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md new file mode 100644 index 000000000..7b3d39113 --- /dev/null +++ b/CONTRIBUTING.md @@ -0,0 +1,43 @@ +# How to contribute + +One of the easiest ways to contribute is to participate in discussions on GitHub issues. You can also contribute by submitting pull requests with code changes. + +## Bugs, feature requests, feedback, and general discussions? +Start a discussion on the [repository issue tracker](https://github.com/modernuo/modernuo/issues). + +## Reporting security issues and bugs +Security issues and bugs should be reported privately, via email, to hi@modernuo.com. +You should receive a response within 24 hours. +If for some reason you do not, please follow up via email to ensure we received your original message. + +## Other discussions +Our team members also monitor several other discussion forums: + +* [ClassicUO Discord](https://discord.gg/VdyCpjQ) +* [Twitter](https://www.twitter.com/modernuo) +* [Reddit](https://www.reddit.com/r/modernuo) + +## Contributing code and content + +We accept fixes and features! Here are some resources to help you get started on how to contribute code or new content. + +* ["Help wanted" issues](https://github.com/modernuo/modernuo/labels/help%20wanted) - these issues are up for grabs. Comment on an issue if you want to create a fix. +* ["Good first issue" issues](https://github.com/modernuo/modernuo/labels/good%20first%20issue) - we think these are a good for newcomers. + +### Submitting a pull request + +If you don't know what a pull request is read this article: https://help.github.com/articles/using-pull-requests. Make sure the repository can build and all tests pass. Familiarize yourself with the project workflow and our coding conventions. + +1. Sign a [Contributor License Agreement](https://cla-assistant.io/modernuo/ModernUO) when submitting your pull request. +1. Ensure all files have the appropriate [LICENSE](/LICENSE) header (Line 634-649) +1. Ensure any install or build dependencies are removed. +1. Update the README.md with details of changes to the interface, this includes new build process, + configurations, environment variables, dependencies, etc. +1. Increase the version numbers to the new version that this Pull Request would represent. + The versioning scheme we use is [SemVer](http://semver.org/). +1. You may merge the Pull Request in once you have the sign-off of two other developers, or if you + do not have permission to do that, you may request the second reviewer to merge it for you. + +[aspnet-contributing]: https://github.com/aspnet/AspNetCore/blob/456dbf1309f9fcae1d7b376784088dcd7818c01e/CONTRIBUTING.md +[homepage]: http://contributor-covenant.org +[version]: http://contributor-covenant.org/version/1/4/ diff --git a/Contributing.md b/Contributing.md deleted file mode 100644 index 64b88cc70..000000000 --- a/Contributing.md +++ /dev/null @@ -1,117 +0,0 @@ -# How to contribute - -One of the easiest ways to contribute is to participate in discussions on GitHub issues. You can also contribute by submitting pull requests with code changes. - -## Bugs, feature requests, feedback, and general discussions? -Start a discussion on the [repository issue tracker](https://github.com/modernuo/modernuo/issues). - -## Reporting security issues and bugs -Security issues and bugs should be reported privately, via email, to hi@modernuo.com. -You should receive a response within 24 hours. -If for some reason you do not, please follow up via email to ensure we received your original message. - -## Other discussions -Our team members also monitor several other discussion forums: - -* [ClassicUO Discord](https://discord.gg/VdyCpjQ) -* [Twitter](https://www.twitter.com/modernuo) -* [Reddit](https://www.reddit.com/r/modernuo) - -## Contributing code and content - -We accept fixes and features! Here are some resources to help you get started on how to contribute code or new content. - -* ["Help wanted" issues](https://github.com/modernuo/modernuo/labels/help%20wanted) - these issues are up for grabs. Comment on an issue if you want to create a fix. -* ["Good first issue" issues](https://github.com/modernuo/modernuo/labels/good%20first%20issue) - we think these are a good for newcomers. - -### Submitting a pull request - -If you don't know what a pull request is read this article: https://help.github.com/articles/using-pull-requests. Make sure the repository can build and all tests pass. Familiarize yourself with the project workflow and our coding conventions. - -1. Sign a [Contributor License Agreement](https://cla-assistant.io/modernuo/ModernUO) when submitting your pull request. -1. Ensure all files have the appropriate [LICENSE](/LICENSE) header (Line 634-649) -1. Ensure any install or build dependencies are removed. -1. Update the README.md with details of changes to the interface, this includes new build process, - configurations, environment variables, dependencies, etc. -1. Increase the version numbers to the new version that this Pull Request would represent. - The versioning scheme we use is [SemVer](http://semver.org/). -1. You may merge the Pull Request in once you have the sign-off of two other developers, or if you - do not have permission to do that, you may request the second reviewer to merge it for you. - -## Code of Conduct - -### Our Pledge - -In the interest of fostering an open and welcoming environment, we as -contributors and maintainers pledge to making participation in our project and -our community a harassment-free experience for everyone, regardless of age, body -size, disability, ethnicity, gender identity and expression, level of experience, -nationality, personal appearance, race, religion, or sexual identity and -orientation. - -### Our Standards - -Examples of behavior that contributes to creating a positive environment -include: - -* Using welcoming and inclusive language -* Being respectful of differing viewpoints and experiences -* Gracefully accepting constructive criticism -* Focusing on what is best for the community -* Showing empathy towards other community members - -Examples of unacceptable behavior by participants include: - -* The use of sexualized language or imagery and unwelcome sexual attention or -advances -* Trolling, insulting/derogatory comments, and personal or political attacks -* Public or private harassment -* Publishing others' private information, such as a physical or electronic - address, without explicit permission -* Other conduct which could reasonably be considered inappropriate in a - professional setting - -### Our Responsibilities - -Project maintainers are responsible for clarifying the standards of acceptable -behavior and are expected to take appropriate and fair corrective action in -response to any instances of unacceptable behavior. - -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. - -### Scope - -This Code of Conduct applies both within project spaces and in public spaces -when an individual is representing the project or its community. Examples of -representing a project or community include using an official project e-mail -address, posting via an official social media account, or acting as an appointed -representative at an online or offline event. Representation of a project may be -further defined and clarified by project maintainers. - -### Enforcement - -Instances of abusive, harassing, or otherwise unacceptable behavior may be -reported by contacting the project team at hi@modernuo.com. All -complaints will be reviewed and investigated 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. -Further details of specific enforcement policies may be posted separately. - -Project maintainers who do not follow or enforce the Code of Conduct in good -faith may face temporary or permanent repercussions as determined by other -members of the project's leadership. - -## Attribution - -This How to Contribute is adapted from the [AspNetCore/CONTRIBUTING](aspnet-contributing) file - -This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, -available at [http://contributor-covenant.org/version/1/4][version] - -[aspnet-contributing]: https://github.com/aspnet/AspNetCore/blob/456dbf1309f9fcae1d7b376784088dcd7818c01e/CONTRIBUTING.md -[homepage]: http://contributor-covenant.org -[version]: http://contributor-covenant.org/version/1/4/