├── .nojekyll ├── .github ├── ISSUE_TEMPLATE │ ├── questions.md │ ├── bug_report.md │ └── feature_request.md ├── pull_request_template.md └── workflows │ └── reviewpad.yml ├── _coverpage.md ├── _sidebar.md ├── LICENSE ├── RESOURCES.md ├── README.md ├── STACKIES.md ├── reviewpad.yml ├── index.html ├── CONTRIBUTING.md └── CODE_OF_CONDUCT.md /.nojekyll: -------------------------------------------------------------------------------- 1 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/questions.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Questions 3 | about: Please state here about concerns regarding the project 4 | title: "[CONCERN]" 5 | labels: question 6 | assignees: '' 7 | 8 | --- 9 | 10 | **Describe the concern you are having** 11 | A clear and concise description of what your concern is. 12 | 13 | **Screenshot** 14 | Provide a screenshot if needed. 15 | 16 | **Additional context** 17 | Add any other context or screenshots about the feature request here. 18 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/bug_report.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Bug report 3 | about: Create a report to help us improve 4 | title: "[BUG]" 5 | labels: bug 6 | assignees: '' 7 | 8 | --- 9 | 10 | **Describe the bug** 11 | A clear and concise description of what the bug is. 12 | 13 | **Expected behavior** 14 | A clear and concise description of what you expected to happen. 15 | 16 | **Screenshots** 17 | If applicable, add screenshots to help explain your problem. 18 | 19 | **Additional context** 20 | Add any other context about the problem here. 21 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/feature_request.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Feature request 3 | about: Suggest an idea for this project 4 | title: "[FEAT]" 5 | labels: enhancement 6 | assignees: '' 7 | 8 | --- 9 | 10 | **Is your feature request related to a problem? Please describe.** 11 | A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] 12 | 13 | **Describe the solution you'd like** 14 | A clear and concise description of what you want to happen. 15 | 16 | **Describe alternatives you've considered** 17 | A clear and concise description of any alternative solutions or features you've considered. 18 | 19 | **Additional context** 20 | Add any other context or screenshots about the feature request here. 21 | -------------------------------------------------------------------------------- /.github/pull_request_template.md: -------------------------------------------------------------------------------- 1 | ## Fixes Issue 2 | 3 | 4 | 5 | 6 | ## Changes proposed 7 | 8 | 9 | 10 | 11 | 20 | 21 | ## Screenshots (If any) 22 | 23 | 24 | ## Questions 25 | 26 | 27 | ## Note to reviewers 28 | 29 | -------------------------------------------------------------------------------- /_coverpage.md: -------------------------------------------------------------------------------- 1 | 2 | 3 | # Stackie 2023 Resolution by Abbey 4 | 5 | > A compilation of Stackie's new year resolution for the year 2023. 6 | 7 | - Be a Stackie by signing up in [StackUp](https://app.stackup.dev/) 8 | 9 | [![GitHub license](https://img.shields.io/github/license/Naereen/StrapDown.js.svg?color=%23ff6a6a&style=flat-square)](https://github.com/AbbeyIT/Stackie-2023-resolution/blob/main/LICENSE) 10 | [![PRs Welcome](https://img.shields.io/badge/PRs-welcome-brightgreen.svg?color=%23ff6a6a&style=flat-square)](https://github.com/AbbeyIT/Stackie-2023-resolution/pulls) 11 | ![GitHub Repo stars](https://img.shields.io/github/stars/AbbeyIT/Stackie-2023-resolution?color=%23ff6a6a&style=flat-square) 12 | 13 | [GitHub](https://github.com/AbbeyIT) 14 | [Get Started](#Welcome) 15 | -------------------------------------------------------------------------------- /_sidebar.md: -------------------------------------------------------------------------------- 1 | 2 | 3 | - Start here 4 | - [Welcome](/#Welcome) 5 | 6 | - Resolution 7 | - [Resolution](STACKIES.md) 8 | 9 | - Guide 10 | 11 | - [Contributing](CONTRIBUTING.md) 12 | - [Code of Conduct](CODE_OF_CONDUCT.md) 13 | 14 | - Resources 15 | 16 | - [Resources](RESOURCES.md) 17 | 18 | - My Socials 19 | 20 | - [LinkFree](https://linkfree.eddiehub.io/AbbeyIT) 21 | - [Twitter](https://twitter.com/abbeywilltech) 22 | - [Hashnode](https://abbeywillblog.hashnode.dev/) 23 | - [GitHub](https://github.com/AbbeyIT) 24 | 25 | - StackUp's Socials 26 | 27 | - [StackUp website](https://app.stackup.dev/) 28 | - [Twitter](https://twitter.com/StackUpHQ) 29 | - [Facebook](https://www.facebook.com/StackUpHQ) 30 | - [LinkedIn](https://www.linkedin.com/company/stackupofficial/) 31 | - [Discord](https://discord.gg/3x3h2z6A63) 32 | -------------------------------------------------------------------------------- /.github/workflows/reviewpad.yml: -------------------------------------------------------------------------------- 1 | # This file configures Reviewpad action to run on Issues and Pull Requests! 🦄 2 | name: Reviewpad 3 | 4 | on: 5 | issues: 6 | types: 7 | - opened 8 | - edited 9 | issue_comment: 10 | pull_request_target: 11 | types: 12 | - opened 13 | - synchronize 14 | - edited 15 | 16 | # These permissions are necessary to automate pull requests from forks. 17 | permissions: 18 | pull-requests: write 19 | issues: write 20 | 21 | jobs: 22 | reviewpad_job: 23 | runs-on: ubuntu-latest 24 | name: Reviewpad 25 | steps: 26 | - name: Reviewpad 27 | uses: reviewpad/action@v3.x 28 | with: 29 | # Use a default configuration file. 30 | # Remove next line if you want to add your own configuration. 31 | #file_url: https://github.com/reviewpad/action/blob/main/templates/start.yml 32 | 33 | # Uncomment next line to use your own configuration file 💪 34 | file: reviewpad.yml 35 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | MIT License 2 | 3 | Copyright (c) 2023 Abbey Santos 4 | 5 | Permission is hereby granted, free of charge, to any person obtaining a copy 6 | of this software and associated documentation files (the "Software"), to deal 7 | in the Software without restriction, including without limitation the rights 8 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell 9 | copies of the Software, and to permit persons to whom the Software is 10 | furnished to do so, subject to the following conditions: 11 | 12 | The above copyright notice and this permission notice shall be included in all 13 | copies or substantial portions of the Software. 14 | 15 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 16 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 17 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE 18 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 19 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, 20 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE 21 | SOFTWARE. 22 | -------------------------------------------------------------------------------- /RESOURCES.md: -------------------------------------------------------------------------------- 1 | # Resources 2 | 3 | ## Resources to learn Open Source, Git and GitHub 4 | - [Open Source with Pradumna](https://github.com/Pradumnasaraf/open-source-with-pradumna) 5 | - [Kunal Kushwaha's Git and GitHub Tutorial](https://youtu.be/apGV9Kg7ics) 6 | - [The Net Ninja's Git and GitHub Tutorial](https://youtube.com/playlist?list=PL4cUxeGkcC9goXbgTDQ0n_4TBzOO0ocPR) 7 | 8 | ## Repositories 9 | These are the list of beginner-friendly repositories to make your first open source contribution. 10 | 11 | - [Hacktoberfest practice](https://github.com/EddieHubCommunity/hacktoberfest-practice) 12 | - [First Contributions](https://github.com/firstcontributions/first-contributions) 13 | - [Your First Open Source Project](https://github.com/Your-First-Open-Source-Project/Your-First-Open-Source-Project) 14 | - [Fitness Accountability](https://github.com/FitDevs-withKat/Fitness-Accountability) 15 | - [LinkFree](https://github.com/EddieHubCommunity/LinkFree) 16 | - [Awesome Tech Blogs](https://github.com/markodenic/awesome-tech-blogs) 17 | - [Community Library](https://github.com/cnu1812/Community-Library) 18 | 19 | ## Website 20 | Website where you can search beginner-friendly project to contribute with. 21 | 22 | - [OSWC](https://www.oswc.is/search-projects) 23 | 24 | ## Communities 25 | These are fantastic communities where you can expand your network and improve your skills. 26 | 27 | - [EddieHub Community](https://github.com/EddieHubCommunity) 28 | - [StackUp](https://discord.gg/3x3h2z6A63) -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Welcome 2 | 3 | Hi! Welcome to Stackie's 2023 Resolution. Feel free to see their [resolution](STACKIES.md), and you may get inspired too. 4 | 5 | ## What is this project all about? 6 | 7 | **Stackie 2023 resolution** is a project where Stackies will share their resolution for this year, 2023. This project is part of an event called ***"Level up your skills with open source"*** in StackUp. This event is intended to advocate open source to fellow Stackies. The goal of this project was to apply what Stackies learned to the event. I will encourage them to contribute to this project and add green squares to their accounts. I'm hoping that this will be the first step in bringing to their attention how open source really works and why it's beneficial to them. 8 | 9 | ## Who are "Stackies"? 10 | 11 | People who use the [StackUp](https://app.stackup.dev/) platform are called "Stackies." StackUp is a learn-to-earn platform, so if you are more curious about it, go check it out. So, in this project, only Stackies are allowed to add their name and resolution to the [STACKIES.md](STACKIES.md) file. However, if you see any bugs or suggest some features, *anyone* can contribute to this project. 12 | 13 | ## How to Contribute? 14 | 15 | In order to contribute to this project, I highly recommend that you please read the [Contributing](CONTRIBUTING.md) file. 16 | 17 | ## Feedback? Corrections? Comments? 18 | 19 | Feel free to open an [Issue](https://github.com/AbbeyIT/Stackie-2023-resolution/issues). 20 | 21 | ## Who am I? 22 | 23 | Hayo! I'm Abbey, and I'm currently a 2nd-year IT student. I am also currently a community moderator at StackUp. This project's goal is to get more people involved in open source, regardless of their occupation or whether they are still students. 24 | 25 | > Open source is for everyone. 26 | 27 | ## Share your support 28 | Please ⭐️ this project in [GitHub](https://github.com/AbbeyIT/Stackie-2023-resolution) if this project is awesome! 29 | 30 | ## License 31 | Stackie 2023 is open-source and licensed under the [MIT License](https://github.com/AbbeyIT/Stackie-2023-resolution/blob/main/LICENSE) 32 |
33 | -------------------------------------------------------------------------------- /STACKIES.md: -------------------------------------------------------------------------------- 1 | ## Stackies 2 | 3 | | Name | Resolution | 4 | |------------------------------------------------------|-----------------------------------------------------------| 5 | | [Abbey](https://github.com/AbbeyIT) | To focus on my health more | 6 | | [AugustHottie](https://github.com/AugustHottie) | To be kinder to myself, grow mentally and emotionally! | 7 | | [Brayan1a1](https://github.com/brayanrodallega) | To be more productive and learn more | 8 | | [Brian](https://github.com/brianmikht) | To live more independently by getting the right job | 9 | | [Complexlity](https://github.com/Complexlity) | To become an overall better person | 10 | | [Flov9](https://github.com/Flov9) | To find an internship and become better overall in what I do | 11 | | [haykay](https://github.com/Haykay2020) | To become a better software developer and learn a job | 12 | | [itscurious](https://github.com/ShantanuK86) | To explore more technologies and travel more | 13 | | [Kodyvim](https://github.com/emmydev9) | Be a better security researcher and live more happily | 14 | | [Nakul](https://github.com/nakul010) | To learn a new skill and start writing blogs | 15 | | [Nikunj](https://github.com/navdiya-nikunj) | To become intermediate data scientist | 16 | | [Onlybond](https://github.com/onlybond) | To improve my managerial skills and my leadership skills with parallely learning about web2 frameworks and web3 concepts | 17 | | [Raviz](https://github.com/gorvyz) | To become a better developer and be healthy and fit | 18 | | [Retr0.eth](https://github.com/Ayan-M-Dev) | To get better as a developer, get an internship & gain weight and become healthy | 19 | | [Roy.](https://github.com/rywndr) | To understand more about programming and get a job in the programming field | 20 | | [Ryuint](https://github.com/Ryuint) | To make more money for family and happy living | 21 | | [That_Boii](https://github.com/D-FOG) | To build my finances and coding skills | 22 | | [Tian](https://github.com/tianbuyung) | To become a open source developer and go on a diet | 23 | | [TimmyKwesi](https://github.com/TimmyKwesi) | To do way better this year than I did last year 😤 | 24 | 25 | | [Back To Top](#Stackies) | 26 | -------------------------------------------------------------------------------- /reviewpad.yml: -------------------------------------------------------------------------------- 1 | # Define the version of Reviewpad to be used. 2 | api-version: reviewpad.com/v3.x 3 | 4 | # Define the list of labels to be used by Reviewpad. 5 | # For more details see https://docs.reviewpad.com/guides/syntax#label. 6 | labels: 7 | small: 8 | color: "#76dbbe" 9 | medium: 10 | color: "#2986cc" 11 | large: 12 | color: "#c90076" 13 | 14 | # Define the list of workflows to be run by Reviewpad. 15 | # A workflow is a list of actions that will be executed based on the defined rules. 16 | # For more details see https://docs.reviewpad.com/guides/syntax#workflow. 17 | workflows: 18 | # This workflow praises contributors on their pull request contributions. 19 | # This helps contributors feel appreciated. 20 | - name: praise-contributors-on-milestones 21 | description: Praise contributors based on their contributions 22 | always-run: true 23 | if: 24 | # Praise contributors on their first pull request. 25 | - rule: $pullRequestCountBy($author()) == 1 26 | extra-actions: 27 | - $commentOnce($sprintf("Thank you @%s for this first contribution!", [$author()])) 28 | # Praise contributors on their 100th pull request. 29 | - rule: $pullRequestCountBy($author()) == 10 30 | extra-actions: 31 | - $commentOnce($sprintf("Way to go 🎉 This is your 10th pull request!", [$author()])) 32 | 33 | # This workflow labels pull requests based on the total number of lines changed. 34 | # This helps pick pull requests based on their size and to incentivize small pull requests. 35 | - name: size-labeling 36 | description: Label pull request based on the number of lines changed 37 | always-run: true 38 | if: 39 | - rule: $size() <= 5 40 | extra-actions: 41 | - $addLabel("small") 42 | - rule: $size() > 5 && $size() <= 15 43 | extra-actions: 44 | - $addLabel("medium") 45 | - rule: $size() > 15 46 | extra-actions: 47 | - $addLabel("large") 48 | 49 | # This workflow signals pull requests waiting for reviews. 50 | # This helps guarantee that pull requests are reviewed and approved by at least one person. 51 | - name: check-approvals 52 | description: Check that pull requests have the required number of approvals 53 | always-run: true 54 | if: 55 | # Label pull requests with `waiting-for-review` if there are no approvals; 56 | - rule: $isDraft() == false && $approvalsCount() < 1 57 | extra-actions: 58 | - $addLabel("waiting-for-review") 59 | 60 | # This workflow validates that pull requests do not contain changes to the license. 61 | # This helps avoid unwanted license modifications. 62 | - name: license-validation 63 | description: Validate that licenses are not modified 64 | always-run: true 65 | if: 66 | # Fail Reviewpad check on pull requests that modify any LICENSE; 67 | - rule: $hasFilePattern("**/LICENSE*") 68 | extra-actions: 69 | - $fail("License files cannot be modified") 70 | -------------------------------------------------------------------------------- /index.html: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | Stackie 2023 Resolution 6 | 7 | 8 | 9 | 10 | 16 | 17 | 18 |
19 | 20 | 84 | 85 | 86 | 90 | 91 | 92 | -------------------------------------------------------------------------------- /CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | # Contributing 2 | 3 | Hi Stackies! In order for you to add your resolution please **Add yourself** to the [list of stackies](STACKIES.md) in **Alphabetical Order** along with your first pull request. 4 | 5 | This document lays out how to get you started in contributing, so please read carefully and throughly. 6 | 7 | If you have any concerns or the steps are unclarified to you, you can approach your concern in the [discussions](https://github.com/AbbeyIT/Stackie-2023-resolution/discussions/1). 8 | 9 | --- 10 | 11 | ## Steps 12 | 13 | 1. [Fork](https://help.github.com/articles/fork-a-repo/) this project 14 | 15 | Click the fork button on the repo at [https://github.com/AbbeyIT/Stackie-2023-resolution](https://github.com/AbbeyIT/Stackie-2023-resolution) 16 | 17 | 2. [Clone](https://help.github.com/articles/fork-a-repo/#step-2-create-a-local-clone-of-your-fork) your forked version 18 | 19 | Your repo will now be in your GitHub. Clone the repo to your computer with the following command: 20 | ``` 21 | git clone https://github.com//Stackie-2023-resolution.git 22 | ``` 23 | 3. Switch to the cloned folder. 24 | ``` 25 | cd Stackie-2023-resolution 26 | ``` 27 | 28 | 4. Create a [branch](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches#working-with-branches) 29 | 30 | Branch away from the `main` branch and use the following schema for naming your branches: 31 | 32 | ``` 33 | git checkout -b 34 | ``` 35 | 36 | 5. Make changes 37 | - Open `STACKIES.md` file. 38 | - Add your details to the table with your name, github handle, and your resolution. 39 | - Make sure to add your name in **Alphabetical Order**. 40 | 41 | **Example Format** 42 | 43 | ``` 44 | | [Name](GitHub-Link) | Resolution | 45 | | [Abbey](https://github.com/AbbeyIT) | To focus on my health more | 46 | ``` 47 | 48 | 6. Staged your commit. 49 | 50 | Add your changes to the `STACKIES.md` file with the following command: 51 | 52 | ``` 53 | git add STACKIES.md 54 | ``` 55 | 56 | 7. [Commit](https://help.github.com/articles/adding-a-file-to-a-repository-using-the-command-line/) your changes (write a short descriptive message of what you have done) 57 | 58 | ``` 59 | git commit -m "add to Stackies" 60 | ``` 61 | If you are not sure how to make a good commit message, please read [here](https://www.freecodecamp.org/news/how-to-write-better-git-commit-messages/). 62 | 63 | 8. [Push](https://help.github.com/articles/pushing-to-a-remote/) your changes to your forked version 64 | 65 | Push your changes, use your branch name you created above 66 | 67 | ``` 68 | git push origin 69 | ``` 70 | 71 | 7. Go to the original project on GitHub & Create a [Pull Request](https://help.github.com/articles/about-pull-requests/) 72 | 73 | You now will get a link in the terminal to create the pull request you can go to that link or go into your forked repo and create the pull request. 74 | 75 | - On the GitHub website, navigate to your forked repo - on the top of the files section, you'll notice a new section containing a `Compare & Pull Request` button. 76 | 77 | - Click on that button, this will load a new page, comparing the local branch in your forked repository against the main branch in the Stackie 2023 resolution repository. Fill up the necessary details there and click the green `Create Pull Request` button. 78 | 79 | - Your pull request will be reviewed and then eventually merged. 80 | 81 | --- 82 | 83 | ## How can I fix a merge conflict? 84 | 85 | A GitHub conflict is when people make changes to the same area or line in a file. This must be fixed before it is merged to prevent collision in the main branch. 86 | 87 | - **To read more about this, go to [GitHub Docs - About Merge Conflicts](https://docs.github.com/en/github/collaborating-with-pull-requests/addressing-merge-conflicts/about-merge-conflicts)** 88 | 89 | - **To find out about how to fix a Git Conflict, go to [GitHub Docs - Resolve Merge Conflict](https://docs.github.com/en/github/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-on-github)** 90 | 91 | - You can also submit an issue in the [Issues](https://github.com/AbbeyIT/Stackie-2023-resolution/issues). 92 | 93 | --- 94 | 95 | ## Congratulations! 🥳 96 | You have now created your first pull request to this repo and have your first contribution. On to more green squares! 🟩 97 | -------------------------------------------------------------------------------- /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 abbeysantos@proton.me. 63 | All complaints will be reviewed and investigated promptly and fairly. 64 | 65 | All community leaders are obligated to respect the privacy and security of the 66 | reporter of any incident. 67 | 68 | ## Enforcement Guidelines 69 | 70 | Community leaders will follow these Community Impact Guidelines in determining 71 | the consequences for any action they deem in violation of this Code of Conduct: 72 | 73 | ### 1. Correction 74 | 75 | **Community Impact**: Use of inappropriate language or other behavior deemed 76 | unprofessional or unwelcome in the community. 77 | 78 | **Consequence**: A private, written warning from community leaders, providing 79 | clarity around the nature of the violation and an explanation of why the 80 | behavior was inappropriate. A public apology may be requested. 81 | 82 | ### 2. Warning 83 | 84 | **Community Impact**: A violation through a single incident or series of 85 | actions. 86 | 87 | **Consequence**: A warning with consequences for continued behavior. No 88 | interaction with the people involved, including unsolicited interaction with 89 | those enforcing the Code of Conduct, for a specified period of time. This 90 | includes avoiding interactions in community spaces as well as external channels 91 | like social media. Violating these terms may lead to a temporary or permanent 92 | ban. 93 | 94 | ### 3. Temporary Ban 95 | 96 | **Community Impact**: A serious violation of community standards, including 97 | sustained inappropriate behavior. 98 | 99 | **Consequence**: A temporary ban from any sort of interaction or public 100 | communication with the community for a specified period of time. No public or 101 | private interaction with the people involved, including unsolicited interaction 102 | with those enforcing the Code of Conduct, is allowed during this period. 103 | Violating these terms may lead to a permanent ban. 104 | 105 | ### 4. Permanent Ban 106 | 107 | **Community Impact**: Demonstrating a pattern of violation of community 108 | standards, including sustained inappropriate behavior, harassment of an 109 | individual, or aggression toward or disparagement of classes of individuals. 110 | 111 | **Consequence**: A permanent ban from any sort of public interaction within the 112 | community. 113 | 114 | ## Attribution 115 | 116 | This Code of Conduct is adapted from the [Contributor Covenant][homepage], 117 | version 2.1, available at 118 | [https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1]. 119 | 120 | Community Impact Guidelines were inspired by 121 | [Mozilla's code of conduct enforcement ladder][Mozilla CoC]. 122 | 123 | For answers to common questions about this code of conduct, see the FAQ at 124 | [https://www.contributor-covenant.org/faq][FAQ]. Translations are available at 125 | [https://www.contributor-covenant.org/translations][translations]. 126 | 127 | [homepage]: https://www.contributor-covenant.org 128 | [v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html 129 | [Mozilla CoC]: https://github.com/mozilla/diversity 130 | [FAQ]: https://www.contributor-covenant.org/faq 131 | [translations]: https://www.contributor-covenant.org/translations 132 | 133 | --------------------------------------------------------------------------------