├── README.md ├── .github ├── PULL_REQUEST_TEMPLATE.md └── ISSUE_TEMPLATE │ ├── submit-a-request.md │ ├── feedback.md │ ├── bug_report.md │ └── submit-a-design-proposal.md ├── SECURITY.md ├── CONTRIBUTING.md └── CODE_OF_CONDUCT.md /README.md: -------------------------------------------------------------------------------- 1 | # metaory/.github 2 | 3 | *Community health files for the ヘ [@metaory](https://github.com/metaory) organization* 4 | 5 | -------------------------------------------------------------------------------- /.github/PULL_REQUEST_TEMPLATE.md: -------------------------------------------------------------------------------- 1 | 5 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/submit-a-request.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: "⭐ Submit a request" 3 | about: Surface a feature or problem that you think should be solved 4 | title: '' 5 | labels: enhancement 6 | assignees: '' 7 | 8 | --- 9 | 10 | ### Describe the feature or problem you’d like to solve 11 | 12 | A clear and concise description of what the feature or problem is. 13 | 14 | ### Proposed solution 15 | 16 | How will it benefit the project and its users? 17 | 18 | ### Additional context 19 | 20 | Add any other context like screenshots or mockups are helpful, if applicable. 21 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/feedback.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: "\U0001F4E3 Feedback" 3 | about: Give us general feedback 4 | title: '' 5 | labels: feedback 6 | assignees: '' 7 | 8 | --- 9 | 10 | # Feedback 11 | 12 | You can use this template to give us structured feedback or just wipe it and leave us a note. Thank you! 13 | 14 | ## What have you loved? 15 | 16 | _eg "the nice colors"_ 17 | 18 | ## What was confusing or gave you pause? 19 | 20 | _eg "it did something unexpected"_ 21 | 22 | ## Are there features you'd like to see added? 23 | 24 | _eg "x needs mini-games"_ 25 | 26 | ## Anything else? 27 | 28 | _eg "have a nice day"_ 29 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/bug_report.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: "\U0001F41B Bug report" 3 | about: Report a bug or unexpected behavior 4 | title: '' 5 | labels: bug 6 | assignees: '' 7 | 8 | --- 9 | 10 | ### Describe the bug 11 | 12 | A clear and concise description of what the bug is. Include version 13 | 14 | ### Steps to reproduce the behavior 15 | 16 | 1. Type this '...' 17 | 2. View the output '....' 18 | 3. See error 19 | 20 | ### Expected vs actual behavior 21 | 22 | A clear and concise description of what you expected to happen and what actually happened. 23 | 24 | ### Logs 25 | 26 | Paste the activity from your command line. Redact if needed. 27 | 28 | -------------------------------------------------------------------------------- /SECURITY.md: -------------------------------------------------------------------------------- 1 | ## Security 2 | 3 | ## Reporting Security Issues 4 | 5 | If you believe you have found a security vulnerability in any org-owned repository, please report it to us through coordinated disclosure. 6 | 7 | **Please do not report security vulnerabilities through public GitHub issues, discussions, or pull requests.** 8 | 9 | Instead, please send an email to metaory@gmail.com. 10 | 11 | Please include as much of the information listed below as you can to help us better understand and resolve the issue: 12 | 13 | * The type of issue (e.g., buffer overflow, SQL injection, or cross-site scripting) 14 | * Full paths of source file(s) related to the manifestation of the issue 15 | * The location of the affected source code (tag/branch/commit or direct URL) 16 | * Any special configuration required to reproduce the issue 17 | * Step-by-step instructions to reproduce the issue 18 | * Proof-of-concept or exploit code (if possible) 19 | * Impact of the issue, including how an attacker might exploit the issue 20 | 21 | This information will help us triage your report more quickly. 22 | 23 | -------------------------------------------------------------------------------- /CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | ## Contributing 2 | 3 | Hi there! We're thrilled that you'd like to contribute to this project. Your help is essential for keeping it great. 4 | 5 | Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms. 6 | 7 | ## Submitting a pull request 8 | 9 | 0. Fork and clone the repository 10 | 0. Configure and install the dependencies: `script/bootstrap` 11 | 0. Make sure the tests pass on your machine: `script/cibuild` 12 | 0. Create a new branch: `git checkout -b my-branch-name` 13 | 0. Make your change, add tests, and make sure the tests still pass 14 | 0. Push to your fork and submit a pull request 15 | 0. Pat your self on the back and wait for your pull request to be reviewed and merged. 16 | 17 | Here are a few things you can do that will increase the likelihood of your pull request being accepted: 18 | 19 | - Follow standards for style and code quality. 20 | - Write tests. 21 | - Keep your change as focused as possible. If there are multiple changes you would like to make that are not dependent upon each other, consider submitting them as separate pull requests. 22 | - Write a [good commit message](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html). 23 | 24 | ## Resources 25 | 26 | - [How to Contribute to Open Source](https://opensource.guide/how-to-contribute/) 27 | - [Using Pull Requests](https://help.github.com/articles/about-pull-requests/) 28 | - [GitHub Help](https://help.github.com) 29 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/submit-a-design-proposal.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: "🎨 Submit a design proposal" 3 | about: Submit a design to resolve an open issue that has both `needs-design` and `help-wanted` labels 4 | title: '' 5 | labels: enhancement 6 | assignees: '' 7 | 8 | --- 9 | 10 | 11 | 12 | ### Link to issue for design submission 13 | 14 | 20 | 21 | ### Proposed Design 22 | 23 | 28 | 29 | ### Mockup 30 | 31 | 59 | -------------------------------------------------------------------------------- /CODE_OF_CONDUCT.md: -------------------------------------------------------------------------------- 1 | # Contributor Covenant Code of Conduct 2 | 3 | ## Our Pledge 4 | 5 | We as members, contributors, and leaders pledge to make participation in our 6 | community a harassment-free experience for everyone, regardless of age, body 7 | size, visible or invisible disability, ethnicity, sex characteristics, gender 8 | identity and expression, level of experience, education, socio-economic status, 9 | nationality, personal appearance, race, caste, color, religion, or sexual 10 | identity and orientation. 11 | 12 | We pledge to act and interact in ways that contribute to an open, welcoming, 13 | diverse, inclusive, and healthy community. 14 | 15 | ## Our Standards 16 | 17 | Examples of behavior that contributes to a positive environment for our 18 | community include: 19 | 20 | * Demonstrating empathy and kindness toward other people 21 | * Being respectful of differing opinions, viewpoints, and experiences 22 | * Giving and gracefully accepting constructive feedback 23 | * Accepting responsibility and apologizing to those affected by our mistakes, 24 | and learning from the experience 25 | * Focusing on what is best not just for us as individuals, but for the overall 26 | community 27 | 28 | Examples of unacceptable behavior include: 29 | 30 | * The use of sexualized language or imagery, and sexual attention or advances of 31 | any kind 32 | * Trolling, insulting or derogatory comments, and personal or political attacks 33 | * Public or private harassment 34 | * Publishing others' private information, such as a physical or email address, 35 | without their explicit permission 36 | * Other conduct which could reasonably be considered inappropriate in a 37 | professional setting 38 | 39 | ## Enforcement Responsibilities 40 | 41 | * Community leaders are responsible for clarifying and enforcing our standards of 42 | acceptable behavior and will take appropriate and fair corrective action in 43 | response to any behavior that they deem inappropriate, threatening, offensive, 44 | or harmful. 45 | 46 | * Community leaders have the right and responsibility to remove, edit, or reject 47 | comments, commits, code, wiki edits, issues, and other contributions that are 48 | not aligned to this Code of Conduct, and will communicate reasons for moderation 49 | decisions when appropriate. 50 | 51 | ## Scope 52 | 53 | * This Code of Conduct applies within all community spaces, and also applies when 54 | an individual is officially representing the community in public spaces. 55 | Examples of representing our community include using an official e-mail address, 56 | posting via an official social media account, or acting as an appointed 57 | representative at an online or offline event. 58 | 59 | ## Enforcement 60 | 61 | * Instances of abusive, harassing, or otherwise unacceptable behavior may be 62 | reported to the community leaders responsible for enforcement at 63 | metaory@gmail.com. 64 | 65 | * All complaints will be reviewed and investigated promptly and fairly. 66 | 67 | * All community leaders are obligated to respect the privacy and security of the 68 | reporter of any incident. 69 | 70 | ## Enforcement Guidelines 71 | 72 | * Community leaders will follow these Community Impact Guidelines in determining 73 | the consequences for any action they deem in violation of this Code of Conduct: 74 | 75 | ### 1. Correction 76 | 77 | **Community Impact**: Use of inappropriate language or other behavior deemed 78 | unprofessional or unwelcome in the community. 79 | 80 | **Consequence**: A private, written warning from community leaders, providing 81 | clarity around the nature of the violation and an explanation of why the 82 | behavior was inappropriate. A public apology may be requested. 83 | 84 | ### 2. Warning 85 | 86 | **Community Impact**: A violation through a single incident or series of 87 | actions. 88 | 89 | **Consequence**: A warning with consequences for continued behavior. No 90 | interaction with the people involved, including unsolicited interaction with 91 | those enforcing the Code of Conduct, for a specified period of time. This 92 | includes avoiding interactions in community spaces as well as external channels 93 | like social media. Violating these terms may lead to a temporary or permanent 94 | ban. 95 | 96 | ### 3. Temporary Ban 97 | 98 | **Community Impact**: A serious violation of community standards, including 99 | sustained inappropriate behavior. 100 | 101 | **Consequence**: A temporary ban from any sort of interaction or public 102 | communication with the community for a specified period of time. No public or 103 | private interaction with the people involved, including unsolicited interaction 104 | with those enforcing the Code of Conduct, is allowed during this period. 105 | Violating these terms may lead to a permanent ban. 106 | 107 | ### 4. Permanent Ban 108 | 109 | **Community Impact**: Demonstrating a pattern of violation of community 110 | standards, including sustained inappropriate behavior, harassment of an 111 | individual, or aggression toward or disparagement of classes of individuals. 112 | 113 | **Consequence**: A permanent ban from any sort of public interaction within the 114 | community. 115 | 116 | ## Attribution 117 | 118 | This Code of Conduct is adapted from the [Contributor Covenant][homepage], 119 | version 2.1, available at 120 | [https://contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1]. 121 | 122 | Community Impact Guidelines were inspired by 123 | [Mozilla's code of conduct enforcement ladder][Mozilla CoC]. 124 | 125 | For answers to common questions about this code of conduct, see the FAQ at 126 | [https://contributor-covenant.org/faq][FAQ]. Translations are available at 127 | [https://contributor-covenant.org/translations][translations]. 128 | 129 | [homepage]: https://contributor-covenant.org 130 | [v2.1]: https://contributor-covenant.org/version/2/1/code_of_conduct.html 131 | [Mozilla CoC]: https://github.com/mozilla/diversity 132 | [FAQ]: https://contributor-covenant.org/faq 133 | [translations]: https://contributor-covenant.org/translations 134 | --------------------------------------------------------------------------------