From a93db25d8d28c471f4f163e76e82664a96b2110b Mon Sep 17 00:00:00 2001 From: Titus Wormer Date: Wed, 26 Jun 2019 16:04:40 +0200 Subject: [PATCH] Remove community health files --- .github/issue_template.md | 23 ----- .github/pull_request_template.md | 7 -- code-of-conduct.md | 74 ---------------- contributing.md | 144 ------------------------------- 4 files changed, 248 deletions(-) delete mode 100644 .github/issue_template.md delete mode 100644 .github/pull_request_template.md delete mode 100644 code-of-conduct.md delete mode 100644 contributing.md diff --git a/.github/issue_template.md b/.github/issue_template.md deleted file mode 100644 index 9219e646b..000000000 --- a/.github/issue_template.md +++ /dev/null @@ -1,23 +0,0 @@ -### Subject of the issue - -Describe your issue here. Remember, this is _not_ a place to ask questions. For that, go to [spectrum](https://spectrum.chat/unified/remark) - -### Your environment - -* Name and version of operating system -* Names and version of required packages -* Version of node, npm, yarn, or names and versions of browser - -### Steps to reproduce - -Tell us how to reproduce this issue. Please provide a working and simplified example. - -🎉 BONUS POINTS for creating a [minimal reproduction](https://stackoverflow.com/help/mcve) and uploading it to GitHub. This will get you the fastest support. 🎉 - -### Expected behaviour - -What should happen? - -### Actual behaviour - -What happens instead? diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md deleted file mode 100644 index 5924167f7..000000000 --- a/.github/pull_request_template.md +++ /dev/null @@ -1,7 +0,0 @@ - diff --git a/code-of-conduct.md b/code-of-conduct.md deleted file mode 100644 index 96d2d0418..000000000 --- a/code-of-conduct.md +++ /dev/null @@ -1,74 +0,0 @@ -# Contributor Covenant 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 behaviour 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 behaviour by participants include: - -* The use of sexualised 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 -behaviour and are expected to take appropriate and fair corrective action in -response to any instances of unacceptable behaviour. - -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 behaviours 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 behaviour may be -reported by contacting the project team at tituswormer@gmail.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 Code of Conduct is adapted from the [Contributor Covenant][homepage], -version 1.4, available at . - -[homepage]: https://www.contributor-covenant.org diff --git a/contributing.md b/contributing.md deleted file mode 100644 index 0f82a5eb3..000000000 --- a/contributing.md +++ /dev/null @@ -1,144 +0,0 @@ -# Contributing - -> This project has a [Code of Conduct][coc]. -> By interacting with this repository, organisation, or community you agree to -> abide by its terms. - -Hi! 👋 -We’re excited that you’re interested in contributing! -Take a moment to read the following guidelines. -And thanks for contributing to **remark**! 👏👌✨ - -If you’re raising an issue, please understand that people involved with this -project often do so for fun, next to their day job; you are not entitled to -free customer service. - -## Table of Contents - -* [Ecosystem](#ecosystem) -* [Questions](#questions) -* [Contributions](#contributions) - * [Financial support](#financial-support) - * [Improve documentation](#improve-documentation) - * [Improve issues](#improve-issues) - * [Give feedback on issues](#give-feedback-on-issues) - * [Write code](#write-code) -* [Submitting an issue](#submitting-an-issue) -* [Submitting a pull request](#submitting-a-pull-request) -* [Resources](#resources) - -## Ecosystem - -The ecosystem consists of several organisations and separate projects: most of -them are tiny, and many of them have a utility -([`mdast-util-to-hast`][mdast-util-to-hast]), a plugin -([`remark-rehype`][remark-rehype]), and relate to an ecosystem -([`remark`][remark]). -Try and pick the right place to contribute to so we can help you faster. - -## Questions - -Please chat and ask questions on [spectrum][chat]! -Jump in there and lurk, talk to us, and help others. - -* [**unified**](https://spectrum.chat/unified) - — Topics relating to [**unified**][unified] in general -* [**vfile**](https://spectrum.chat/unified/vfile) - — Topics relating to [**vfile**][vfile]: virtual files -* [**syntax-tree**](https://spectrum.chat/unified/syntax-tree) - — Topics relating to [**syntax-tree**][syntax-tree] and [**unist**][unist] -* [**remark**](https://spectrum.chat/unified/remark) - — Topics relating to the [**remark**][remark] ecosystem, markdown, - and [**mdast**][mdast] - -## Contributions - -There’s several ways to contribute, not just by writing code. - -### Financial support - -It’s possible to support us financially by becoming a backer or sponsor through -[Open Collective][collective]. -With this support, we can pay for project leadership, finance non-coding work, -or to do fun things for the community like getting stickers for contributors. -You’ll be helping unified’s maintainers manage and improve existing projects, -and additionally support our work to develop new and exciting projects, such -as [micromark][]. - -### Improve documentation - -As a user of this project you’re perfect for helping us improve our docs. -Typo corrections, error fixes, better explanations, new examples, etcetera. -Anything! - -### Improve issues - -Some issues lack information, aren’t reproducible, or are just incorrect. -Help make them easier to resolve. - -### Give feedback on issues - -We’re always looking for more opinions on discussions in the issue tracker. - -### Write code - -Code contributions are very welcome. It’s often good to first create an issue -to report a bug or suggest a new feature before creating a pull request to -prevent you from doing unnecessary work. - -## Submitting an issue - -* The issue tracker is for issues. Use chat for support -* Search the issue tracker (including closed issues) before opening a new - issue -* Ensure you’re using the latest version of projects -* Use a clear and descriptive title -* Include as much information as possible: steps to reproduce the issue, - error message, version, operating system, etcetera -* The more time you put into an issue, the more we will -* The best issue report is a [failing test][unit-test] proving it - -## Submitting a pull request - -* Non-trivial changes are often best discussed in an issue first, to prevent - you from doing unnecessary work -* For ambitious tasks, you should try to get your work in front of the - community for feedback as soon as possible -* New features should be accompanied with tests and documentation -* Don’t include unrelated changes -* Lint and test before submitting code by running `$ npm test` -* Write a convincing description of why we should land your pull request: - it’s your job to convince us - -## Resources - -* [How to Contribute to Open Source](https://opensource.guide/how-to-contribute/) -* [Making your first contribution](https://medium.com/@vadimdemedes/making-your-first-contribution-de6576ddb190) -* [Using Pull Requests](https://help.github.com/articles/about-pull-requests/) -* [GitHub Help](https://help.github.com) - -[coc]: https://github.com/remarkjs/rehype/blob/master/code-of-conduct.md - -[vfile]: https://github.com/vfile - -[syntax-tree]: https://github.com/syntax-tree - -[unist]: https://github.com/syntax-tree/unist - -[unified]: https://github.com/unifiedjs/unified - -[remark]: https://github.com/remarkjs/remark - -[mdast]: https://github.com/syntax-tree/mdast - -[mdast-util-to-hast]: https://github.com/syntax-tree/mdast-util-to-hast - -[remark-rehype]: https://github.com/remarkjs/remark-rehype - -[unit-test]: https://twitter.com/sindresorhus/status/579306280495357953 - -[collective]: https://opencollective.com/unified - -[micromark]: https://github.com/micromark/micromark - -[chat]: https://spectrum.chat/unified