├── .github ├── FUNDING.yml ├── CODEOWNERS ├── ISSUE_TEMPLATE │ ├── feature_request.md │ ├── bug_report.md │ └── new_contribution.yml └── pull_request_template.md ├── LICENSE ├── .gitignore ├── CONTRIBUTING.md ├── data └── 2022-contributions.json ├── README.md └── CODE_OF_CONDUCT.md /.github/FUNDING.yml: -------------------------------------------------------------------------------- 1 | # These are supported funding model platforms 2 | 3 | github: [reactplay] 4 | -------------------------------------------------------------------------------- /.github/CODEOWNERS: -------------------------------------------------------------------------------- 1 | # Lines starting with '#' are comments. 2 | # Each line is a file pattern followed by one or more owners. 3 | 4 | # These owners will be the default owners for everything in the repo. 5 | * @atapas @koustov @joshi-kaushal 6 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/feature_request.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Feature request 3 | about: Suggest an idea for this project 4 | title: '' 5 | labels: '' 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/ISSUE_TEMPLATE/bug_report.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Bug report 3 | about: Create a report to help us improve 4 | title: '' 5 | labels: '' 6 | assignees: '' 7 | 8 | --- 9 | 10 | **Describe the bug** 11 | A clear and concise description of what the bug is. 12 | 13 | **To Reproduce** 14 | Steps to reproduce the behavior: 15 | 1. Go to '...' 16 | 2. Click on '....' 17 | 3. Scroll down to '....' 18 | 4. See error 19 | 20 | **Expected behavior** 21 | A clear and concise description of what you expected to happen. 22 | 23 | **Screenshots** 24 | If applicable, add screenshots to help explain your problem. 25 | 26 | **Desktop (please complete the following information):** 27 | - OS: [e.g. iOS] 28 | - Browser [e.g. chrome, safari] 29 | - Version [e.g. 22] 30 | 31 | **Smartphone (please complete the following information):** 32 | - Device: [e.g. iPhone6] 33 | - OS: [e.g. iOS8.1] 34 | - Browser [e.g. stock browser, safari] 35 | - Version [e.g. 22] 36 | 37 | **Additional context** 38 | Add any other context about the problem here. 39 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | MIT License 2 | 3 | Copyright (c) 2022 ReactPlayIO 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 | -------------------------------------------------------------------------------- /.github/pull_request_template.md: -------------------------------------------------------------------------------- 1 | 2 | > First thing, PLEASE READ THIS: [ReactPlay Code Review Checklist](https://github.com/reactplay/react-play/wiki/ReactPlay-Code-Review-Checklist) 3 | 4 | # Description 5 | 6 | Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change. 7 | 8 | Fixes # (issue) 9 | 10 | ## Type of change 11 | 12 | Please delete options that are not relevant. 13 | 14 | - [ ] Bug fix (non-breaking change which fixes an issue) 15 | - [ ] New feature (non-breaking change which adds functionality) 16 | - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) 17 | - [ ] This change requires a documentation update 18 | 19 | # How Has This Been Tested? 20 | 21 | Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. 22 | 23 | # Checklist: 24 | 25 | - [ ] I have performed a self-review of my own code 26 | - [ ] I have commented my code, particularly in hard-to-understand areas 27 | - [ ] I have made corresponding changes to the documentation 28 | - [ ] My changes generate no new warnings 29 | - [ ] I have added tests that prove my fix is effective or that my feature works 30 | - [ ] New and existing unit tests pass locally with my changes 31 | - [ ] Any dependent changes have been merged and published in downstream modules 32 | -------------------------------------------------------------------------------- /.gitignore: -------------------------------------------------------------------------------- 1 | # Logs 2 | logs 3 | *.log 4 | npm-debug.log* 5 | yarn-debug.log* 6 | yarn-error.log* 7 | lerna-debug.log* 8 | 9 | # Diagnostic reports (https://nodejs.org/api/report.html) 10 | report.[0-9]*.[0-9]*.[0-9]*.[0-9]*.json 11 | 12 | # Runtime data 13 | pids 14 | *.pid 15 | *.seed 16 | *.pid.lock 17 | 18 | # Directory for instrumented libs generated by jscoverage/JSCover 19 | lib-cov 20 | 21 | # Coverage directory used by tools like istanbul 22 | coverage 23 | *.lcov 24 | 25 | # nyc test coverage 26 | .nyc_output 27 | 28 | # Grunt intermediate storage (https://gruntjs.com/creating-plugins#storing-task-files) 29 | .grunt 30 | 31 | # Bower dependency directory (https://bower.io/) 32 | bower_components 33 | 34 | # node-waf configuration 35 | .lock-wscript 36 | 37 | # Compiled binary addons (https://nodejs.org/api/addons.html) 38 | build/Release 39 | 40 | # Dependency directories 41 | node_modules/ 42 | jspm_packages/ 43 | 44 | # TypeScript v1 declaration files 45 | typings/ 46 | 47 | # TypeScript cache 48 | *.tsbuildinfo 49 | 50 | # Optional npm cache directory 51 | .npm 52 | 53 | # Optional eslint cache 54 | .eslintcache 55 | 56 | # Microbundle cache 57 | .rpt2_cache/ 58 | .rts2_cache_cjs/ 59 | .rts2_cache_es/ 60 | .rts2_cache_umd/ 61 | 62 | # Optional REPL history 63 | .node_repl_history 64 | 65 | # Output of 'npm pack' 66 | *.tgz 67 | 68 | # Yarn Integrity file 69 | .yarn-integrity 70 | 71 | # dotenv environment variables file 72 | .env 73 | .env.test 74 | 75 | # parcel-bundler cache (https://parceljs.org/) 76 | .cache 77 | 78 | # Next.js build output 79 | .next 80 | 81 | # Nuxt.js build / generate output 82 | .nuxt 83 | dist 84 | 85 | # Gatsby files 86 | .cache/ 87 | # Comment in the public line in if your project uses Gatsby and *not* Next.js 88 | # https://nextjs.org/blog/next-9-1#public-directory-support 89 | # public 90 | 91 | # vuepress build output 92 | .vuepress/dist 93 | 94 | # Serverless directories 95 | .serverless/ 96 | 97 | # FuseBox cache 98 | .fusebox/ 99 | 100 | # DynamoDB Local files 101 | .dynamodb/ 102 | 103 | # TernJS port file 104 | .tern-port 105 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/new_contribution.yml: -------------------------------------------------------------------------------- 1 | name: New Contribution 2 | description: Submitting a new low/no code contribution to ReactPlay 3 | body: 4 | - type: markdown 5 | attributes: 6 | value: | 7 | Thank-you for contributing to ReactPlay in this Hacktoberfest. We appriciate your contribution. Please help us to understand what did you do: 8 | - type: input 9 | id: name 10 | attributes: 11 | label: Contributor's Name 12 | description: Your Name 13 | placeholder: ex. John Doe 14 | validations: 15 | required: true 16 | - type: input 17 | id: username 18 | attributes: 19 | label: GitHub Username 20 | description: The username you are using right now 21 | placeholder: ex. cool-john-doe 22 | validations: 23 | required: true 24 | - type: textarea 25 | id: description 26 | attributes: 27 | label: Description 28 | description: Explain what you did. Please be specific. 29 | placeholder: I wrote a cool blog. 30 | validations: 31 | required: true 32 | - type: dropdown 33 | id: category 34 | attributes: 35 | label: Contribution Category 36 | description: Was it a low-code or no-code? 37 | options: 38 | - low-code 39 | - no-code 40 | validations: 41 | required: true 42 | - type: dropdown 43 | id: type 44 | attributes: 45 | label: What was it about? 46 | options: 47 | - design 48 | - writing 49 | - advocacy 50 | validations: 51 | required: true 52 | - type: dropdown 53 | id: contribution 54 | attributes: 55 | label: Select the exact contribution you did 56 | multiple: true 57 | description: If your contribution is not listed, contact @atapas or @joshi-kaushal 58 | options: 59 | - docs 60 | - translating 61 | - copy-editing 62 | - testing 63 | - UX-testing 64 | - design 65 | - video 66 | - talks 67 | - presentations 68 | - workshops 69 | - case-studies 70 | - thread 71 | - podcasts 72 | - blogs 73 | - type: input 74 | id: link 75 | attributes: 76 | label: Link to your Contribution 77 | description: Link to your blog/video/paper/etc 78 | placeholder: https://reactplay.io/ 79 | validations: 80 | required: true 81 | - type: markdown 82 | attributes: 83 | value: "If you are unable to provide links, attach photos, or any proof so we can understand." 84 | - type: checkboxes 85 | id: terms 86 | attributes: 87 | label: Code of Conduct 88 | description: This contribution is made by me and I am not copying/plagiarizing/misusing anyone else's content. 89 | options: 90 | - label: I agree to the above statement 91 | required: true 92 | -------------------------------------------------------------------------------- /CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | # Contributing 2 | 3 | When contributing to this repository, please first discuss the change you wish to make via [issue](https://github.com/reactplay/react-play/issues), 4 | [email](mailto:ioreactplay@gmail.com), or any other method with the owners of this repository before making a change. 5 | 6 | Please note we have a [Code of Conduct](https://github.com/reactplay/react-play/blob/main/CODE_OF_CONDUCT.md), please follow it in all your interactions with the project. 7 | 8 | ## Pull Request Process 9 | 10 | 1. Ensure any install or build dependencies are removed before the end of the layer when doing a 11 | build. 12 | 2. Update the README.md with details of changes to the interface, this includes new environment 13 | variables, exposed ports, useful file locations and container parameters. 14 | 3. Increase the version numbers in any examples files and the README.md to the new version that this 15 | Pull Request would represent. The versioning scheme we use is [SemVer](http://semver.org/). 16 | 4. You may merge the Pull Request in once you have the sign-off of two other developers, or if you 17 | do not have permission to do that, you may request the second reviewer to merge it for you. 18 | 19 | ## Code of Conduct 20 | 21 | ### Our Pledge 22 | 23 | In the interest of fostering an open and welcoming environment, we as 24 | contributors and maintainers pledge to making participation in our project and 25 | our community a harassment-free experience for everyone, regardless of age, body 26 | size, disability, ethnicity, gender identity and expression, level of experience, 27 | nationality, personal appearance, race, religion, or sexual identity and 28 | orientation. 29 | 30 | ### Our Standards 31 | 32 | Examples of behavior that contributes to creating a positive environment 33 | include: 34 | 35 | * Using welcoming and inclusive language 36 | * Being respectful of differing viewpoints and experiences 37 | * Gracefully accepting constructive criticism 38 | * Focusing on what is best for the community 39 | * Showing empathy towards other community members 40 | 41 | Examples of unacceptable behavior by participants include: 42 | 43 | * The use of sexualized language or imagery and unwelcome sexual attention or 44 | advances 45 | * Trolling, insulting/derogatory comments, and personal or political attacks 46 | * Public or private harassment 47 | * Publishing others' private information, such as a physical or electronic 48 | address, without explicit permission 49 | * Other conduct which could reasonably be considered inappropriate in a 50 | professional setting 51 | 52 | ### Our Responsibilities 53 | 54 | Project maintainers are responsible for clarifying the standards of acceptable 55 | behavior and are expected to take appropriate and fair corrective action in 56 | response to any instances of unacceptable behavior. 57 | 58 | Project maintainers have the right and responsibility to remove, edit, or 59 | reject comments, commits, code, wiki edits, issues, and other contributions 60 | that are not aligned to this Code of Conduct, or to ban temporarily or 61 | permanently any contributor for other behaviors that they deem inappropriate, 62 | threatening, offensive, or harmful. 63 | 64 | ### Scope 65 | 66 | This Code of Conduct applies both within project spaces and in public spaces 67 | when an individual is representing the project or its community. Examples of 68 | representing a project or community include using an official project e-mail 69 | address, posting via an official social media account, or acting as an appointed 70 | representative at an online or offline event. Representation of a project may be 71 | further defined and clarified by project maintainers. 72 | 73 | ### Enforcement 74 | 75 | Instances of abusive, harassing, or otherwise unacceptable behavior may be 76 | reported by contacting the project team at [ioreactplay@gmail.com](mailto:ioreactplay@gmail.com). All 77 | complaints will be reviewed and investigated and will result in a response that 78 | is deemed necessary and appropriate to the circumstances. The project team is 79 | obligated to maintain confidentiality with regard to the reporter of an incident. 80 | Further details of specific enforcement policies may be posted separately. 81 | 82 | Project maintainers who do not follow or enforce the Code of Conduct in good 83 | faith may face temporary or permanent repercussions as determined by other 84 | members of the project's leadership. 85 | 86 | ### Attribution 87 | 88 | This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, 89 | available at [http://contributor-covenant.org/version/1/4][version] 90 | 91 | [homepage]: http://contributor-covenant.org 92 | [version]: http://contributor-covenant.org/version/1/4/ 93 | -------------------------------------------------------------------------------- /data/2022-contributions.json: -------------------------------------------------------------------------------- 1 | { 2 | "nishasen": { 3 | "name": "Nisha Sen", 4 | "username": "nishasen", 5 | "category": "no-code", 6 | "type": "advocacy", 7 | "contribution": "blogs", 8 | "description": "I am handling the linkedin page and account for ReactPlay. I try sharing blogs, quotes and events everyday. The page is being created by ReactPlay and I am one of the maintainer of that page, I try to invite more and more people everyday and share about plays in React play.", 9 | "link": "https://www.linkedin.com/company/reactplay" 10 | }, 11 | "supminn": { 12 | "name": "Supriya M", 13 | "username": "supminn", 14 | "category": "no-code", 15 | "type": "dvocacy", 16 | "contribution": "blogs", 17 | "description": "FinSaver is a web application that helps track your income and expenses. It's developed using the mobile-first approach of responsive design to provide a smooth experience on all kinds of devices. I have built this application for Hack-R-Play hackathon.", 18 | "link": "https://blog.reactplay.io/building-finsaver-for-hack-r-play" 19 | }, 20 | "daryllukas": [ 21 | { 22 | "name": "Daryl Lukas", 23 | "username": "daryllukas", 24 | "category": "no-code", 25 | "type": "advocacy", 26 | "contribution": "blogs", 27 | "description": "I wrote on blog post on Form Validation in React", 28 | "link": "https://blog.reactplay.io/form-validation-in-react-using-formik" 29 | }, 30 | { 31 | "name": "Daryl Lukas", 32 | "username": "daryllukas", 33 | "category": "no-code", 34 | "type": "advocacy", 35 | "contribution": "blogs", 36 | "description": "I wrote on blog post on Error Boundaries in React", 37 | "link": "https://hashnode.com/draft/635be79a93b35e2fb5d817a7" 38 | }, 39 | { 40 | "name": "Daryl Lukas", 41 | "username": "daryllukas", 42 | "category": "no-code", 43 | "type": "advocacy", 44 | "contribution": "blogs", 45 | "description": "I wrote on blog post on automatically assigning keys to Lists in React", 46 | "link": "https://hashnode.com/draft/635be9e793b35e2fb5d817db" 47 | } 48 | ], 49 | "aashishpanthi": { 50 | "name": "Aashish Panthi", 51 | "username": "aashishpanthi", 52 | "category": "no-code", 53 | "type": "advocacy", 54 | "contribution": "blogs", 55 | "description": "I wrote a blog explaining about the recent project I built using React and Nhost. It is a email status finder.", 56 | "link": "https://blog.reactplay.io/mailsbe-an-email-status-finder" 57 | }, 58 | "Amyx000": { 59 | "name": "Arman Kazi", 60 | "username": "Amyx000", 61 | "category": "no-code", 62 | "type": "advocacy", 63 | "contribution": "blogs", 64 | "description": "This is React Resume Builder created during Hack-R-Play Hackathon using this developer can fill their details and get their resume ready in few seconds.", 65 | "link": "https://blog.reactplay.io/react-resume-builder-with-react-and-nhost" 66 | }, 67 | "ammaaraslam": { 68 | "name": "Ammaar Aslam", 69 | "username": "ammaaraslam", 70 | "category": "no-code", 71 | "type": "writing", 72 | "contribution": "blogs", 73 | "description": "Wrote a blog on blog.reactplay.io about my HACK-R-PLAY submission, WriteOnce.", 74 | "link": "https://blog.reactplay.io/introducing-writeonce-a-markdown-editor-for-devs-who-blog" 75 | }, 76 | "utsavbhattarai007": { 77 | "name": "Utsav bhattarai", 78 | "username": "utsavbhattarai007", 79 | "category": "no-code", 80 | "type": "advocacy", 81 | "contribution": "blogs", 82 | "description": "I wrote on blog post on the web app which click the high quality screenshot.", 83 | "link": "https://blog.reactplay.io/introducing-shotz-a-high-quality-screen-clicker" 84 | }, 85 | "GeekyChakri": { 86 | "name": "Chakri", 87 | "username": "GeekyChakri", 88 | "category": "no-code", 89 | "type": "advocacy", 90 | "contribution": "blogs", 91 | "description": "I wrote a post on ReactPlay's blog about my Hack-R-Play project.", 92 | "link": "https://blog.reactplay.io/introducing-classroom-learning-with-youtube-made-exciting", 93 | }, 94 | { 95 | "username": { 96 | "name": "Kaushal Joshi", 97 | "username": "joshi-kaushal", 98 | "category": "no-code", 99 | "type": "advocacy", 100 | "contribution": "talks", 101 | "description": "I co-hosted an online event with Tapas Adhikary on Aviyel. I talked about ReactPlay community, blogging and hacktobefest contribution.", 102 | "link": "https://aviyel.com/events/468/closer-look-at-reactplay-with-tapas-adhikary" 103 | } 104 | }, 105 | { 106 | "username": { 107 | "name": "Senali", 108 | "username": "senali-d", 109 | "category": "no-code", 110 | "type": "writing", 111 | "contribution": "blog", 112 | "description": "I wrote a blog post about my Hack-R-Play project.", 113 | "link": "https://sen-d.hashnode.dev/mini-encyclopedia-site" 114 | } 115 | } 116 | } 117 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Hacktoberfest x ReactPlay 2 | 3 | This repository contains a record of all low-code and no-code contributions made during the Hacktoberfest event in the ReactPlay community. 4 | 5 | ## What is Hacktoberfest 6 | 7 | Hacktoberfest is a virtual event organized by DigitalOcean and its partners throughout October. It is aimed toward open source and introducing it to as many developers as possible. Anyone regardless of their programming experience are encouraged to contribute to open-source. 8 | 9 | 🔗 Read more [here](https://blog.reactplay.io/hacktoberfest-101-with-reactplay). 10 | 11 | ## No-code/Low-code Contributions 12 | 13 | Until last year, hacktoberfest contributions were only valid for coding or maintaining a project. Since this year, Hacktoberfest has also been allowing low-code and no-code contributions. 14 | Here's the table that explains some of the ways of no-code/low-code contributions. 15 | 16 | | Contribution Type | Low-code | No-code | 17 | | ----------------- | --------------------------------------------------- | --------------------------------------------- | 18 | | Writing | Technical Documentation | Translating, Copy editing | 19 | | Design | Testing | UX Testing, Graphics design, video production | 20 | | Advocacy | Talks, presentations, blogs, podcasts, case studies | social media blog posts | 21 | 22 | 🔗 Read more [here](https://blog.reactplay.io/hacktoberfest-101-with-reactplay#heading-new-changes-introduced-this-year). 23 | 24 | ## Hacktoberfest with ReactPlay 25 | 26 | We are already having active code contributions in our [main project](https://github.com/reactplay/react-play). However, if you have contributed to us in some other way, you need to submit it in this repository. 27 | The valid contributions will be merged to the repository with `hacktoberfest-accepted` tag. 28 | 29 | ## What Are Valid Contributions 30 | 31 | Anything that you have done that helps the ReactPlay community to grow, and improve in either low-code or no-code categories will be considered as a valid contribution. You need to provide detailed information about the contribution along with a URL that validates your contribution. 32 | 33 | ## How to Submit Your Contribution 34 | 35 | 1. Go to the [Issues](https://github.com/reactplay/hacktoberfest/issues/new/choose) section of the repository and add a new issue with **New Contribution** template 36 | 37 | ![issues](https://user-images.githubusercontent.com/53049546/193395979-38a09dae-a057-4e3e-bcfb-20475b0f47bf.png) 38 | 39 | 2. Fill in the required details with appropriate information. And then Submit the issue. 40 | 3. Wait until someone from the community assigns you to the issue. 41 | 4. Fork this repository in your own account once you are assigned to the issue. 42 | 43 | ![fork](https://user-images.githubusercontent.com/53049546/193394469-43960255-6ad3-443d-872d-024bc552da3c.png) 44 | 45 | 5. Create a new branch with your github username. 46 | 47 | ![new-branch](https://user-images.githubusercontent.com/53049546/193394454-afb7c208-188e-40c5-9a6a-b8e27344b27d.png) 48 | 49 | 6. Inside `/data` directory in the root folder, open the `json` file named with current year (eg: `2022-contributions.md`) . 50 | 7. Use your github username as a key and use the following template to add your data. 51 | ```json 52 | { 53 | "username": { 54 | "name": "", 55 | "username": "", 57 | "type": "", 58 | "contribution": "", 59 | "description": "", 60 | "link": "" 61 | } 62 | } 63 | ``` 64 | 8. Once you are finished, commit your changes. 65 | 66 | ![commit](https://user-images.githubusercontent.com/53049546/193394645-6f83839e-659c-4626-9e16-199a04c06105.png) 67 | 68 | 9. Go to the `Code` section of the repository. You will see a yellow box asking you to compare & create a pull request, click it. 69 | 70 | ![image](https://user-images.githubusercontent.com/53049546/193394767-199612ee-416c-40fd-89b9-4516797d3902.png) 71 | 72 | 10. If the above step doesn't work, go to `Pull Request` section and create a a new request. 73 | 11. Select the `main` branch of `reactplay/hacktoberfest` repository, and solve merge conflicts if any. 74 | 12. Wait until someone from our team approves it. 75 | 76 | ## Example 77 | 78 | ```json 79 | { 80 | "joshi-kaushal": { 81 | "name": "Kaushal Joshi", 82 | "username": "joshi-kaushal", 83 | "category": "no-code", 84 | "type": "writing", 85 | "contribution": "blogs", 86 | "description": "I wrote a blog discussing why reactplay is cool", 87 | "link": "https://blog.kaushaljoshi.dev" 88 | } 89 | } 90 | ``` 91 | 92 | ## Get in Touch 93 | If you are stuck somewhere, or have some doubts; join our [Discord server](https://discord.com/channels/982239924227031070/983209230729379901) and mention it there. 94 | -------------------------------------------------------------------------------- /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, religion, or sexual identity 10 | 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 26 | overall community 27 | 28 | Examples of unacceptable behavior include: 29 | 30 | * The use of sexualized language or imagery, and sexual attention or 31 | advances of 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 35 | address, 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 | contact@reactplay.io. 64 | All complaints will be reviewed and investigated promptly and fairly. 65 | 66 | All community leaders are obligated to respect the privacy and security of the 67 | reporter of any incident. 68 | 69 | ## Enforcement Guidelines 70 | 71 | Community leaders will follow these Community Impact Guidelines in determining 72 | the consequences for any action they deem in violation of this Code of Conduct: 73 | 74 | ### 1. Correction 75 | 76 | **Community Impact**: Use of inappropriate language or other behavior deemed 77 | unprofessional or unwelcome in the community. 78 | 79 | **Consequence**: A private, written warning from community leaders, providing 80 | clarity around the nature of the violation and an explanation of why the 81 | behavior was inappropriate. A public apology may be requested. 82 | 83 | ### 2. Warning 84 | 85 | **Community Impact**: A violation through a single incident or series 86 | of actions. 87 | 88 | **Consequence**: A warning with consequences for continued behavior. No 89 | interaction with the people involved, including unsolicited interaction with 90 | those enforcing the Code of Conduct, for a specified period of time. This 91 | includes avoiding interactions in community spaces as well as external channels 92 | like social media. Violating these terms may lead to a temporary or 93 | permanent ban. 94 | 95 | ### 3. Temporary Ban 96 | 97 | **Community Impact**: A serious violation of community standards, including 98 | sustained inappropriate behavior. 99 | 100 | **Consequence**: A temporary ban from any sort of interaction or public 101 | communication with the community for a specified period of time. No public or 102 | private interaction with the people involved, including unsolicited interaction 103 | with those enforcing the Code of Conduct, is allowed during this period. 104 | Violating these terms may lead to a permanent ban. 105 | 106 | ### 4. Permanent Ban 107 | 108 | **Community Impact**: Demonstrating a pattern of violation of community 109 | standards, including sustained inappropriate behavior, harassment of an 110 | individual, or aggression toward or disparagement of classes of individuals. 111 | 112 | **Consequence**: A permanent ban from any sort of public interaction within 113 | the community. 114 | 115 | ## Attribution 116 | 117 | This Code of Conduct is adapted from the [Contributor Covenant][homepage], 118 | version 2.0, available at 119 | https://www.contributor-covenant.org/version/2/0/code_of_conduct.html. 120 | 121 | Community Impact Guidelines were inspired by [Mozilla's code of conduct 122 | enforcement ladder](https://github.com/mozilla/diversity). 123 | 124 | [homepage]: https://www.contributor-covenant.org 125 | 126 | For answers to common questions about this code of conduct, see the FAQ at 127 | https://www.contributor-covenant.org/faq. Translations are available at 128 | https://www.contributor-covenant.org/translations. 129 | --------------------------------------------------------------------------------