├── .github ├── FUNDING.yml ├── ISSUE_TEMPLATE │ ├── add-api-user.yml │ ├── biodrop-review.yml │ ├── bug.yml │ ├── config.yml │ ├── delete-api-user.yml │ ├── gh-profile-review.yml │ ├── github-sponsors-profile-review.yml │ ├── ideas.yml │ ├── invitation.yml │ ├── opensource-review.yml │ ├── other.yml │ ├── portfolio-review.yml │ ├── resume-review.yml │ └── twitter-review.yml ├── pull_request_template.md └── workflows │ ├── community.yml │ ├── create-user.yml │ ├── invitation.yml │ ├── labels.yml │ └── md-lint.yml ├── .gitignore ├── .gitpod.yml ├── .markdownlint.json ├── CODE_OF_CONDUCT.md ├── CONTRIBUTING.md ├── LICENSE ├── README.md ├── docs ├── .nojekyll ├── _layout │ ├── navbar.md │ └── sidebar.md ├── aims-and-values.md ├── discord │ ├── discord-readme.md │ └── roles.md ├── icon.png ├── index.html ├── index.md ├── logo.png ├── mee6 │ └── welcome-dm.md ├── moderators │ ├── discord.md │ └── github.md ├── nightbot │ └── allowed-links.md ├── snippets │ ├── README.md │ ├── de │ │ ├── github-action-failing.md │ │ ├── issue-before-pr.md │ │ ├── join-discord.md │ │ ├── screenshots.md │ │ ├── smaller-pull-requests.md │ │ └── update-branch.md │ ├── en │ │ ├── github-action-failing.md │ │ ├── issue-before-pr.md │ │ ├── join-discord.md │ │ ├── screenshots.md │ │ ├── smaller-pull-requests.md │ │ └── update-branch.md │ ├── es │ │ ├── github-action-failing.md │ │ ├── issue-before-pr.md │ │ ├── join-discord.md │ │ ├── screenshots.md │ │ ├── smaller-pull-requests.md │ │ └── update-branch.md │ ├── id │ │ ├── github-action-failing.md │ │ ├── issue-before-pr.md │ │ ├── join-discord.md │ │ ├── screenshots.md │ │ ├── smaller-pull-requests.md │ │ └── update-branch.md │ ├── pt │ │ ├── github-action-failing.md │ │ ├── issue-before-pr.md │ │ ├── join-discord.md │ │ ├── screenshots.md │ │ ├── smaller-pull-requests.md │ │ └── update-branch.md │ └── ru │ │ ├── github-action-failing.md │ │ ├── issue-before-pr.md │ │ ├── join-discord.md │ │ ├── screenshots.md │ │ ├── smaller-pull-requests.md │ │ └── update-branch.md ├── tips │ ├── OpenSourceResources.md │ ├── OpenSourceTips.md │ ├── finding-open-source-projects.md │ ├── git.md │ ├── githubtips.md │ └── glossary.md └── youtube │ ├── generic.md │ └── reviews.md ├── package-lock.json └── package.json /.github/FUNDING.yml: -------------------------------------------------------------------------------- 1 | # These are supported funding model platforms 2 | 3 | github: [eddiejaoude] 4 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/add-api-user.yml: -------------------------------------------------------------------------------- 1 | name: EddieHub API add 2 | description: Add me to the EddieHub API 3 | title: "Please add me to the EddieHub API" 4 | labels: [EddieHub-API-add] 5 | body: 6 | - type: input 7 | id: discordname 8 | attributes: 9 | label: Discord Username (if applicable) 10 | placeholder: Insert your Discord username here 11 | validations: 12 | required: false 13 | - type: markdown 14 | attributes: 15 | value: | 16 | You can also join our Discord community [here](http://discord.eddiehub.org) 17 | Feel free to check out other cool repositories of the EddieHub Community [here](https://github.com/EddieHubCommunity) 18 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/biodrop-review.yml: -------------------------------------------------------------------------------- 1 | name: BioDrop Review 2 | description: Please review my BioDrop profile on a livestream 3 | title: "[REVIEW]" 4 | labels: [BioDrop review, live stream review] 5 | body: 6 | - type: input 7 | id: link 8 | attributes: 9 | label: BioDrop profile link 10 | placeholder: "e.g.: https://biodrop.io/eddiejaoude" 11 | validations: 12 | required: true 13 | - type: markdown 14 | attributes: 15 | value: | 16 | You can also join our Discord community [here](http://discord.eddiehub.org) 17 | Feel free to check out other cool repositories of the EddieHub Community [here](https://github.com/EddieHubCommunity) 18 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/bug.yml: -------------------------------------------------------------------------------- 1 | name: Bug report 2 | description: Create a bug report to help us address errors in the repository 3 | title: "[BUG] " 4 | labels: [bug] 5 | body: 6 | - type: textarea 7 | id: bugdescription 8 | attributes: 9 | label: Description of the bug 10 | validations: 11 | required: true 12 | - type: input 13 | id: stack 14 | attributes: 15 | label: Project stack or language (e.g. front-end) 16 | validations: 17 | required: true 18 | - type: textarea 19 | id: workingenvironment 20 | attributes: 21 | label: Working Environment (e.g. operating system, browser, device) 22 | validations: 23 | required: true 24 | - type: textarea 25 | id: screenshots 26 | attributes: 27 | label: Please add screenshots (if applicable) 28 | validations: 29 | required: false 30 | - type: textarea 31 | id: context 32 | attributes: 33 | label: Add any other context about the problem here 34 | validations: 35 | required: false 36 | - type: markdown 37 | attributes: 38 | value: | 39 | You can also join our Discord community [here](http://discord.eddiehub.org) 40 | Feel free to check out other cool repositories of the EddieHub Community [here](https://github.com/EddieHubCommunity) 41 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/config.yml: -------------------------------------------------------------------------------- 1 | blank_issues_enabled: false 2 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/delete-api-user.yml: -------------------------------------------------------------------------------- 1 | name: EddieHub API delete 2 | description: Delete me from the EddieHub API. By opting-out your previously recorded stats will get deleted as well. 3 | title: "Please delete me from the EddieHub API" 4 | labels: [EddieHub-API-delete] 5 | body: 6 | - type: input 7 | id: discordname 8 | attributes: 9 | label: Discord Username (if applicable) 10 | placeholder: Insert your Discord username here 11 | validations: 12 | required: false 13 | - type: markdown 14 | attributes: 15 | value: | 16 | You can also join our Discord community [here](http://discord.eddiehub.org) 17 | Feel free to check out other cool repositories of the EddieHub Community [here](https://github.com/EddieHubCommunity) 18 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/gh-profile-review.yml: -------------------------------------------------------------------------------- 1 | name: GitHub Profile Review 2 | description: Please review my GitHub profile on a livestream 3 | title: "[REVIEW] " 4 | labels: [gh profile review, live stream review] 5 | body: 6 | - type: input 7 | id: link 8 | attributes: 9 | label: GitHub Profile Link 10 | placeholder: https://github.com/ 11 | validations: 12 | required: true 13 | - type: markdown 14 | attributes: 15 | value: | 16 | You can also join our Discord community [here](http://discord.eddiehub.org) 17 | Feel free to check out other cool repositories of the EddieHub Community [here](https://github.com/EddieHubCommunity) 18 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/github-sponsors-profile-review.yml: -------------------------------------------------------------------------------- 1 | name: GitHub Sponsors Profile Review 2 | description: Please review my GitHub Sponsors profile on a livestream 3 | title: "[REVIEW] " 4 | labels: [gh sponsor review, live stream review] 5 | body: 6 | - type: input 7 | id: link 8 | attributes: 9 | label: GitHub Sponsor profile link 10 | validations: 11 | required: true 12 | - type: markdown 13 | attributes: 14 | value: | 15 | You can also join our Discord community [here](http://discord.eddiehub.org) 16 | Feel free to check out other cool repositories of the EddieHub Community [here](https://github.com/EddieHubCommunity) 17 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/ideas.yml: -------------------------------------------------------------------------------- 1 | name: Ideas 2 | description: Have a new idea or feature request 3 | title: "[FEATURE REQUEST] " 4 | labels: [enhancement] 5 | body: 6 | - type: textarea 7 | id: description 8 | attributes: 9 | label: Description of feature request, idea 10 | validations: 11 | required: true 12 | - type: textarea 13 | id: screenshots 14 | attributes: 15 | label: Add (multiple) screenshot links (if applicable) 16 | validations: 17 | required: false 18 | - type: textarea 19 | id: context 20 | attributes: 21 | label: Add any other context about the feature request here 22 | validations: 23 | required: false 24 | - type: markdown 25 | attributes: 26 | value: | 27 | You can also join our Discord community [here](http://discord.eddiehub.org) 28 | Feel free to check out other cool repositories of the EddieHub Community [here](https://github.com/EddieHubCommunity) 29 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/invitation.yml: -------------------------------------------------------------------------------- 1 | name: Invitation to the GitHub Community Organization 2 | description: I would like to be part of the awesome community 3 | title: "Please invite me to the GitHub Community Organization" 4 | labels: [invite me to the organisation] 5 | body: 6 | - type: input 7 | id: name 8 | attributes: 9 | label: Name 10 | placeholder: Insert your name here 11 | validations: 12 | required: true 13 | - type: input 14 | id: discordname 15 | attributes: 16 | label: Discord Username (if applicable) 17 | placeholder: Insert your Discord username here 18 | validations: 19 | required: false 20 | - type: textarea 21 | id: Additional 22 | attributes: 23 | label: Additional Context 24 | description: Where did you meet Eddie? What do you like about this community/Why do you want to join? 25 | validations: 26 | required: true 27 | - type: markdown 28 | attributes: 29 | value: | 30 | You can also join our Discord community [here](http://discord.eddiehub.org) 31 | Feel free to check out other cool repositories of the EddieHub Community [here](https://github.com/EddieHubCommunity) 32 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/opensource-review.yml: -------------------------------------------------------------------------------- 1 | name: Open Source Project Review 2 | description: Please review my project on a livestream 3 | title: "[REVIEW] " 4 | labels: [open source review, live stream review] 5 | body: 6 | - type: markdown 7 | attributes: 8 | value: "Your project doesn't have to be hosted at GitHub, it can also be on GitLab or other VCS" 9 | - type: input 10 | id: link 11 | attributes: 12 | label: Project link 13 | placeholder: https://github.com// 14 | validations: 15 | required: true 16 | - type: markdown 17 | attributes: 18 | value: | 19 | You can also join our Discord community [here](http://discord.eddiehub.org) 20 | Feel free to check out other cool repositories of the EddieHub Community [here](https://github.com/EddieHubCommunity) 21 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/other.yml: -------------------------------------------------------------------------------- 1 | name: Other 2 | description: Use this for any other issues. PLEASE do not create blank issues 3 | title: "[OTHER]" 4 | labels: [triage] 5 | body: 6 | - type: markdown 7 | attributes: 8 | value: "# Other issue" 9 | - type: textarea 10 | id: issuedescription 11 | attributes: 12 | label: What would you like to share? 13 | description: Provide a clear and concise explanation of your issue. 14 | validations: 15 | required: true 16 | - type: textarea 17 | id: extrainfo 18 | attributes: 19 | label: Additional information 20 | description: Is there anything else we should know about this issue? 21 | validations: 22 | required: false 23 | - type: markdown 24 | attributes: 25 | value: | 26 | You can also join our Discord community [here](http://discord.eddiehub.org) 27 | Feel free to check out other cool repositories of the EddieHub Community [here](https://github.com/EddieHubCommunity) 28 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/portfolio-review.yml: -------------------------------------------------------------------------------- 1 | name: Portfolio Review 2 | description: Please review my Portfolio on a livestream 3 | title: "[REVIEW]" 4 | labels: [portfolio review, live stream review] 5 | body: 6 | - type: markdown 7 | attributes: 8 | value: "**Please ensure that you don't have any personal details in your Portfolio that you don't want to share publicly.**" 9 | - type: input 10 | id: link 11 | attributes: 12 | label: Portfolio link 13 | placeholder: "e.g.: https://.github.io/portfolio" 14 | validations: 15 | required: true 16 | - type: input 17 | id: repo 18 | attributes: 19 | label: GitHub Repo Link 20 | placeholder: "e.g.: https://github.com/YOUR_USERNAME/REPO" 21 | validations: 22 | required: true 23 | - type: markdown 24 | attributes: 25 | value: | 26 | You can also join our Discord community [here](http://discord.eddiehub.org) 27 | Feel free to check out other cool repositories of the EddieHub Community [here](https://github.com/EddieHubCommunity) 28 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/resume-review.yml: -------------------------------------------------------------------------------- 1 | name: Resume Review 2 | description: Please review my resume on a live stream 3 | title: "[REVIEW]" 4 | labels: [resume review, live stream review] 5 | body: 6 | - type: markdown 7 | attributes: 8 | value: "**Remove all personal data, otherwise, the resume will be deleted**" 9 | - type: input 10 | id: link 11 | attributes: 12 | label: Resume link 13 | placeholder: "e.g.: https://drive.google.com/file/d//view" 14 | validations: 15 | required: true 16 | - type: markdown 17 | attributes: 18 | value: | 19 | You can also join our Discord community [here](http://discord.eddiehub.org) 20 | Feel free to check out other cool repositories of the EddieHub Community [here](https://github.com/EddieHubCommunity) 21 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/twitter-review.yml: -------------------------------------------------------------------------------- 1 | name: Twitter Profile Review 2 | description: Please review my Twitter on a livestream 3 | title: "[REVIEW] " 4 | labels: [twitter review, live stream review] 5 | body: 6 | - type: input 7 | id: link 8 | attributes: 9 | label: Twitter profile link 10 | placeholder: https://twitter.com/ 11 | validations: 12 | required: true 13 | - type: markdown 14 | attributes: 15 | value: | 16 | You can also join our Discord community [here](http://discord.eddiehub.org) 17 | Feel free to check out other cool repositories of the EddieHub Community [here](https://github.com/EddieHubCommunity) 18 | -------------------------------------------------------------------------------- /.github/pull_request_template.md: -------------------------------------------------------------------------------- 1 | 2 | 3 | closes #ISSUE-NO 4 | 5 | #### What does this PR do? 6 | 7 | #### Description of the task to be completed? 8 | 9 | #### How can this be manually tested? 10 | 11 | #### Any background context you want to provide? 12 | 13 | #### Is there any relevant issue to this PR? 14 | 15 | #### Screenshots (if appropriate) 16 | 17 | #### Questions 18 | -------------------------------------------------------------------------------- /.github/workflows/community.yml: -------------------------------------------------------------------------------- 1 | on: 2 | fork: 3 | push: 4 | branches: [develop] 5 | issues: 6 | types: [opened] 7 | issue_comment: 8 | types: [created] 9 | pull_request_target: 10 | types: [opened] 11 | pull_request_review_comment: 12 | types: [created] 13 | 14 | jobs: 15 | welcome: 16 | runs-on: ubuntu-latest 17 | steps: 18 | - uses: actions/checkout@v1 19 | - uses: EddieHubCommunity/gh-action-community/src/welcome@main 20 | with: 21 | github-token: ${{ secrets.GITHUB_TOKEN }} 22 | issue-message: "

It's great having you contribute to this project

Welcome to the community :nerd_face:" 23 | pr-message: "

It's great having you contribute to this project

Welcome to the community :nerd_face:" 24 | footer: 'If you would like to continue contributing to open source and would like to do it with an awesome inclusive community, you should join our Discord Server and our GitHub Organisation - we help and encourage each other to contribute to open source little and often 🤓 . Any questions let us know.' 25 | -------------------------------------------------------------------------------- /.github/workflows/create-user.yml: -------------------------------------------------------------------------------- 1 | on: 2 | issues: 3 | types: [labeled] 4 | 5 | jobs: 6 | create-user: 7 | runs-on: ubuntu-latest 8 | steps: 9 | - uses: actions/checkout@v1 10 | - uses: EddieHubCommunity/gh-action-community/src/api-user@main 11 | with: 12 | repo-token: ${{ secrets.GITHUB_TOKEN }} 13 | api-key: ${{ secrets.API_TOKEN }} 14 | api-url: ${{ secrets.API_URL }}/github 15 | -------------------------------------------------------------------------------- /.github/workflows/invitation.yml: -------------------------------------------------------------------------------- 1 | on: 2 | issues: 3 | types: [labeled] 4 | 5 | jobs: 6 | automate_invite: 7 | runs-on: ubuntu-latest 8 | steps: 9 | - name: Invite on label 10 | uses: vj-abigo/invite-on-label@v1.4 11 | with: 12 | organization: EddieHubCommunity 13 | label: invite me to the organisation 14 | repo-token: ${{ secrets.GITHUB_TOKEN }} 15 | comment: "Invitation sent to join the GitHub Organisation. Welcome to the community 🎉

Don't forget after accepting to make it public so it appears on your GitHub profile for everyone else to see. You can do this by finding your name in the GitHub organisation list and change the dropdown to public https://github.com/orgs/EddieHubCommunity/people

Tips for practising:

Customise your GitHub profile, here is a course on that: https://www.udemy.com/course/make-your-github-profile-stand-out/
Practice repo, instructions on how to add your name to the README https://github.com/EddieHubCommunity/hacktoberfest-practice
Remember contributing to open source is not just about code, it's about collaboration, communication and adding value
I hope that helps" 16 | env: 17 | INVITE_TOKEN: ${{ secrets.INVITE_TOKEN }} 18 | -------------------------------------------------------------------------------- /.github/workflows/labels.yml: -------------------------------------------------------------------------------- 1 | name: Import open source standard labels 2 | 3 | on: 4 | push: 5 | branches: [main] 6 | 7 | jobs: 8 | labels: 9 | runs-on: ubuntu-latest 10 | 11 | steps: 12 | - uses: actions/setup-node@v2 13 | with: 14 | node-version: "14" 15 | - uses: EddieHubCommunity/gh-action-open-source-labels@main 16 | with: 17 | github-token: ${{ secrets.GITHUB_TOKEN }} 18 | owner-name: ${{ github.repository_owner }} 19 | repository-name: ${{ github.event.repository.name }} 20 | force: false 21 | -------------------------------------------------------------------------------- /.github/workflows/md-lint.yml: -------------------------------------------------------------------------------- 1 | name: Markdown Lint 2 | on: 3 | push: 4 | branches: 5 | - main 6 | pull_request: 7 | branches: 8 | - main 9 | 10 | jobs: 11 | ci: 12 | name: Run Linter 13 | runs-on: ubuntu-latest 14 | 15 | strategy: 16 | matrix: 17 | node-version: [16.x] 18 | 19 | steps: 20 | - name: Checkout Source Files 21 | uses: actions/checkout@v2 22 | 23 | - name: Use Node.js v${{ matrix.node-version }} 24 | uses: actions/setup-node@v2 25 | with: 26 | node-version: ${{ matrix.node-version }} 27 | 28 | - name: Install Dependencies 29 | run: npm ci 30 | 31 | - name: Lint Source Files 32 | run: npm run lint 33 | -------------------------------------------------------------------------------- /.gitignore: -------------------------------------------------------------------------------- 1 | /node_modules/ 2 | -------------------------------------------------------------------------------- /.gitpod.yml: -------------------------------------------------------------------------------- 1 | # List the start up tasks. Learn more https://www.gitpod.io/docs/config-start-tasks/ 2 | tasks: 3 | - init: npm install 4 | command: npm start 5 | 6 | # List the ports to expose. Learn more https://www.gitpod.io/docs/config-ports/ 7 | ports: 8 | - port: 3200 9 | onOpen: open-preview 10 | -------------------------------------------------------------------------------- /.markdownlint.json: -------------------------------------------------------------------------------- 1 | { 2 | "line-length": false, 3 | "no-bare-urls": false 4 | } 5 | -------------------------------------------------------------------------------- /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 | Project Maintainers 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 | Project Maintainers 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 email 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 (this can be done anonymously) to the Project Maintainers responsible for enforcement at http://eddiejaoude.io/contact. 63 | All complaints will be reviewed and investigated promptly and fairly. 64 | 65 | All Project Maintainers are obligated to respect the privacy and security of the 66 | reporter of any incident. 67 | 68 | ## Enforcement Guidelines 69 | 70 | Project Maintainers will follow these 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 Project Maintainers, 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 | -------------------------------------------------------------------------------- /CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | # Contributing to Support 2 | 3 | Thank you for taking the time to contribute. Please read the [CODE of CONDUCT](CODE_OF_CONDUCT.md). 4 | As a contributor, here are the guidelines we would like you to follow: 5 | 6 | - [Commit Message Guidelines](#commit) 7 | 8 | --- 9 | 10 | ## Commit Message Guidelines 😎 11 | 12 | In order to make git commit messages **easier to read** and faster to reason about, we follow some guidelines on most commits to keep the **format predictable**. Check [Conventional Commits specification](https://conventionalcommits.org) for more information about our guidelines. 13 | 14 | **Examples**: 15 | 16 | ``` 17 | docs(changelog): update changelog to beta.5 18 | docs: add API documentation to the bot 19 | test(server): add cache tests to the movie resource 20 | fix(web): add validation to phone input field 21 | fix(web): remove avatar image from being required in form 22 | fix(release): need to depend on latest rxjs and zone.js 23 | ``` 24 | 25 | ### Type 26 | 27 | Must be one of the following: 28 | 29 | - **build**: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm). 30 | - **ci**: Changes to our CI configuration files and scripts (example scopes: Circle, BrowserStack, SauceLabs) 31 | - **docs**: Documentation only changes 32 | - **feat**: A new feature 33 | - **fix**: A bug fix 34 | - **perf**: A code change that improves performance 35 | - **refactor**: A code change that neither fixes a bug nor adds a feature 36 | - **style**: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc) 37 | - **test**: Adding missing tests or correcting existing tests 38 | 39 | ### Becoming an EddieHub Maintainer 40 | 41 | EddieHub is all about open source collaboration. We want it to be a place which is inclusive and welcoming for all and therefore, our maintainers are carefully chosen from those we see upholding the EddieHub guiding principles of collaboration first, code second, making quality contributions to EddieHub over a longer period of time and those that follow the [CODE of CONDUCT](CODE_OF_CONDUCT.md). 42 | 43 | Please don’t ask to become a maintainer; instead, show your interest and potential through quality contributions. Our moderation team regularly discusses which contributors make a positive impact on the community. Those seen regularly making a positive impact in line with our code of conduct will be extended an invite to join the maintainer team. 44 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | MIT License 2 | 3 | Copyright (c) 2020-2021 Eddie Jaoude 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 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/#https://github.com/eddiehubcommunity/support) 2 | 3 | # Community Support 4 | 5 | 6 | 7 | [![Discord](https://img.shields.io/discord/699608417039286293?style=flat-square)](http://discord.eddiehub.org) 8 | 9 | 10 | 11 | [Join the Discord Community](http://discord.eddiehub.org) — [Subscribe to Eddie Jaoude's YouTube channel](https://www.youtube.com/user/eddiejaoude) 12 | 13 | --- 14 | 15 | ## Guides 16 | 17 | - Raise an [issue to join the EddieHub GitHub organisation](https://github.com/EddieHubCommunity/support/issues/new?assignees=&labels=invite+me+to+the+organisation&template=invitation.yml&title=Please+invite+me+to+the+GitHub+Community+Organization). 18 | 19 | - Actions go under [issues](https://github.com/EddieHubCommunity/support/issues) 20 | 21 | - Bugs 22 | 23 | - Add me to the organization 24 | 25 | - Miscellaneous go under [Discussions](https://github.com/EddieHubCommunity/support/discussions) 26 | 27 | - Questions 28 | 29 | - Ideas (once discussed, an Issue could be created and linked to the Discussion thread) 30 | 31 | - Showcase of Open Source Portfolios to get feedback from community members. 32 | 33 | - Feel free to check out other cool repositories of EddieHub [here](https://github.com/EddieHubCommunity) 34 | 35 | --- 36 | 37 | ## FAQs 38 | 39 | - **What is a GitHub Organization?** Essentially it's a way to group many repositories in an entity called an organization. An organization also allows us to group people who contribute and are a part of the community. Some examples would be - [Netflix](https://github.com/Netflix), [Facebook](https://github.com/facebook), and of course [EddieHub](https://github.com/EddieHubCommunity). 40 | Learn more on [GitHub docs](https://docs.github.com/en/github/setting-up-and-managing-organizations-and-teams/about-organizations). 41 | - **How do I join the Github Organization?** Raise an issue on this repository asking to join ([invite me](https://github.com/EddieHubCommunity/support/issues/new?assignees=&labels=invite+me+to+the+organisation&template=invitation.md&title=Please+invite+me+to+the+GitHub+Community+Organization)). 42 | - **How do I set the Organization to Public?** 43 | 44 | - Navigate to our community page: https://github.com/EddieHubCommunity 45 | 46 | - Click on the highlighted area: 47 | 48 | ![screenshot](https://user-images.githubusercontent.com/13745974/101496938-47da5000-3962-11eb-8ab3-8fd3ea327d1d.png) 49 | 50 | - Enter your username in the highlighted search bar: 51 | 52 | ![screenshot](https://user-images.githubusercontent.com/13745974/102218327-b3c63680-3ed5-11eb-9295-aafa5e59ebfd.png) 53 | 54 | - Click `Private` (the default) and set it to `Public` 55 | 56 | ![Screenshot_20200916_231045](https://user-images.githubusercontent.com/17693494/93422970-26d9f580-f872-11ea-870d-4406db20e9d5.png) 57 | 58 | - **How do I keep my Git fork up to date?** Add a new remote called `upstream` targeting the original repository. Check out more information on [this issue](https://github.com/EddieHubCommunity/support/issues/94). 59 | - **What is DevRel?** Check out the discussion on [this issue](https://github.com/EddieHubCommunity/support/issues/64) or on [this YouTube video](https://www.youtube.com/watch?v=iUZerHctTB8&t=1534s). 60 | - **How do I get started with open source?** You can make your first pull request in this [repository](https://github.com/EddieHubCommunity/hacktoberfest-practice). Follow the instructions in the README, and don't forget – contributing to open source is not just about code – it's about collaboration, communication, and adding value. Don't be afraid to open an issue with a question :smiley:. If you have any trouble, you can ask questions in our Discord. We have a channel for `first-timers` and `opensource`. 61 | 62 | Here is a list of resources that also might help you start contributing to open source: 63 | 64 | - [How to get started in hackathons](https://github.com/EddieHubCommunity/support/issues/32) 65 | - [Open source tips from EddieBot](./docs/tips) 66 | 67 | - **How to look for an open-source project to contribute?** Check [Finding Open Source Projects](./docs/tips/finding-open-source-projects.md) 68 | 69 | ## Our Pledge 70 | 71 | We take participation in our community as a harassment-free experience for everyone and we pledge to act in ways to contribute to an open, welcoming, diverse and inclusive community. 72 | 73 | If you have experienced or been made aware of unacceptable behaviour, please remember that you can report this. Read our [Code of Conduct](https://github.com/EddieHubCommunity/support/blob/main/CODE_OF_CONDUCT.md). 74 | -------------------------------------------------------------------------------- /docs/.nojekyll: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/EddieHubCommunity/support/52f7d86c79248f336189aa2783f34aa88e72bc6c/docs/.nojekyll -------------------------------------------------------------------------------- /docs/_layout/navbar.md: -------------------------------------------------------------------------------- 1 | 2 | - [Discord](http://discord.eddiehub.org) 3 | - [Twitter](https://twitter.com/eddiejaoude) 4 | - [YouTube](https://youtube.com/c/eddiejaoude) 5 | -------------------------------------------------------------------------------- /docs/_layout/sidebar.md: -------------------------------------------------------------------------------- 1 | 2 | - Discord 3 | - [Rules](/discord/discord-readme.md) 4 | - [Moderation Guide](/moderators/discord.md) 5 | - [Self-Roles](/discord/roles.md) 6 | - [Welcome DM](/mee6/welcome-dm.md) 7 | - [Allowed Links](/nightbot/allowed-links.md) 8 | 9 | - GitHub 10 | - [GitHub Maintainer Guide](/moderators/github.md) 11 | 12 | - Tips 13 | - [Finding Open Source Projects](/tips/finding-open-source-projects.md) 14 | - [Git Tips and Tricks](/tips/git.md) 15 | - [How to Use GitHub](/tips/githubtips.md) 16 | - [Common Terms](/tips/glossary.md) 17 | - [Open Source Resources](/tips/OpenSourceResources.md) 18 | - [Open Source Tips](/tips/OpenSourceTips.md) 19 | - [Glossary](/tips/glossary.md) 20 | 21 | - Templates 22 | - [YouTube Generic Template](/youtube/generic.md) 23 | -------------------------------------------------------------------------------- /docs/aims-and-values.md: -------------------------------------------------------------------------------- 1 | # EddieHub Aims and Values 2 | 3 | ## Our Background 4 | 5 | EddieHub was founded by Eddie Jaoude, GitHub Star, GitHub Star of the Year 2020 and winner of the GitHub Community Growth Award 2021. As a passionate advocate of Open Source who has always believed in giving back to the tech community, Eddie’s particular focus is creating and supporting opportunities for those wanting to start a career in tech. 6 | 7 | Recognising that starting in Open Source can be daunting, Eddie was keen to build a community which focused on Open Source for those with varying tech abilities and at different stages of their tech journey. 8 | 9 | The main objective was for members to share their experiences by adopting both a mentor and mentee role on the premise that everyone has something to teach but also something to learn. “Collaboration First, Code Second” quickly became what the community members live by. 10 | 11 | 12 | ## Our Aims 13 | 14 | EddieHub’s overall aim is to support members in: accelerating their learnings so that they can have the career they want. 15 | 16 | This can be broken down into two components: 17 | 18 | **1. Improving your technical expertise through Open Source** 19 | 20 | Through tutorials explaining key concepts of Open Source ranging from; how to get started on Github, to Documentation, Automated Testing and Continuous Delivery (CI and CD), guest interviews with experts in the field to live streams where your projects can be reviewed and you can receive feedback and encouragement. 21 | 22 | Technical knowledge is also built upon in the Discord channels and GitHub Discussions where members can ask questions and share their projects, whilst getting the guidance and support from Eddie, our expert moderators as well as all members of the community. 23 | 24 | **2. Building upon your communication skills** 25 | 26 | For EddieHub, learning how to collaborate is key and we believe that a vital part of knowing how to collaborate with others is through effective communication skills. 27 | 28 | Often there are limited opportunities to expand upon these skills. You may work within a small team and liaise with the same colleagues on a daily basis, work on your own or, as a result of geographic location, there may not be opportunities (such as clubs or meet-up groups) to develop your communication style and confidence. 29 | 30 | By creating a community with members from all around the world and with different technical levels, EddieHub has generated an opportunity for members to interact with a large diversity of people. This constant interaction between members means that the way they receive feedback has an impact on how they communicate feedback to others. 31 | 32 | Recognising that at the outset these communication skills were primarily through the Discord written messages and GitHub Issues and Pull Requests, EddieHub has launched initiatives for regular Public Speaking events, tutorials and “Ask me Anything” sessions to further support its members. 33 | 34 | We are pleased that members have reported that this approach has been invaluable to them. Had they not made their projects Open Source, they would not have been able to progress these in the same way as a private project. In addition, whilst feedback was either not sought or viewed as a negative critique, it is now both actively encouraged and more confidently given. 35 | 36 | 37 | ## Our Core Values 38 | 39 | Behind these aims are EddieHub’s core values: 40 | 41 | **1. An inclusive and welcoming environment** 42 | 43 | As with many other communities, EddieHub has a Code of Conduct and Equality, Diversity & Inclusion policy. In addition we have excellent moderators who keep a close eye to ensure that members feel EddieHub is a safe space where they can learn, network and share their experiences. 44 | 45 | We had observed that many other communities had a very “male orientated” language, as well as making assumptions that everyone went by the “he/him” gender pronoun. We wanted EddieHub to be different and use gender neutral language to ensure that we did not alienate any members whilst making a clear stance against the “bro culture” which often dominates the tech space. 46 | 47 | Through a community discussion we achieved this through our Discord bot named “EddieBot”, which picks up and suggests alternatives to gender favouring, polarising, race related, religion inconsiderate or other unequal phrasing. In addition, Eddiebot was built by the community members and we feel this is an accurate reflection to members’ commitment to these core values. 48 | 49 | **2. The wellbeing of our community members** 50 | 51 | Moderators and members advocate for taking time for self care and avoiding burning out. We have a Discord channel dedicated to our members sharing what they do in their down time, which in turn reminds others to take a break. We want to lead by example in the tech space and stop glamourising overworking and the “hustle” culture, through sharing tips and tutorials on the EddieHub Blog as to how you can ensure you are looking after yourself. 52 | 53 | **3. Achieve your goals whilst having fun!** 54 | 55 | Whilst no EddieHub member is the same, one thing we all have in common - Open Source is our hobby, our passion - not just a job. 56 | 57 | At EddieHub we will always encourage members to make their next Open Source contribution and we are their biggest cheerleaders. Whether we might nudge members directly to check on how their project is going, to hackathons and challenges as well as asking them to come out of their comfort zone to moderate a call or speak in public for the first time. 58 | -------------------------------------------------------------------------------- /docs/discord/discord-readme.md: -------------------------------------------------------------------------------- 1 | # Welcome to the EddieHubCommunity Discord server 2 | 3 | We believe Open Source is for everyone, yes you! 4 | OPEN SOURCE is NOT about code, it is about people and collaboration. 5 | We are invested in getting you those green squares on GitHub! Contributing to Open Source Software (OSS) is a great way for you to learn, work with different people and also network. You'll find awesome people here who will guide you and if you're a beginner in open source, keep an eye on #first-timers. If you get stuck somewhere feel free to ask for help in the community, you'll find someone who can help you for sure and others will learn along too! 6 | 7 | **Please try to adhere by our Code Of Conduct (COC):** 8 | 9 | We as members, contributors, and leaders pledge to make participation in our 10 | community a harassment-free experience for everyone, regardless of age, body 11 | size, visible or invisible disability, ethnicity, sex characteristics, gender 12 | identity and expression, level of experience, education, socio-economic status, 13 | nationality, personal appearance, race, religion, or sexual identity 14 | and orientation. 15 | We pledge to act and interact in ways that contribute to an open, welcoming, 16 | diverse, inclusive, and healthy community. 17 | The following are the guidelines regarding chat on the discord server: 18 | 19 | - Using welcoming and inclusive language 20 | - Being respectful of differing viewpoints and experiences 21 | - Gracefully accepting constructive criticism 22 | - Focusing on what is best for the community 23 | - Showing empathy towards other community members 24 | - Full details can be found at 25 | - In addition to our code of conduct, members should follow Discord's community guidelines () as well 26 | 27 | **Enforcement:** 28 | 29 | Instances of abusive, harassing or otherwise unacceptable behaviour may be reported by contacting the @moderators. 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. 30 | 31 | EddieBotDev (or EddieBot) would be monitoring language used on the Discord server to ensure the inclusive and welcoming language in the Discord server. EddieBot suggests alternatives and it would be a good practice to edit your message reflecting the suggestion. 32 | 33 | **NOTE:** EddieBot is still in development, and there might be a few words flagged by it that should not have been flagged. Open an issue on the repo and get a green square! 34 | 35 | **Information Regarding Channels:** 36 | 37 | BROWSE CHANNELS: Consists of search and also lists all available channels in the discord, you are able to follow specific channels or entire category. 38 | 39 | TEXT CHANNELS: These consist of the server's main text channels, that are for discourse regarding topics that aren't very tech-specific, and aren't off-topic. 40 | 41 | VOICE CHANNELS: #RadioEddieStage intended for community public speaking events 42 | 43 | **GENERAL DISCUSSION:** 44 | 45 | - **#readme**: EddieHub's onboarding information 46 | 47 | - **#roles**: add or remove roles that apply to you 48 | 49 | - **#general**: main text chat 50 | 51 | - **#help**: ask for help or provide help to the members of the community 52 | 53 | - **#content-share**: share web content 54 | 55 | - **#career**: perm / freelance, digital nomad discussion (no job/project offers) 56 | 57 | **DAILY:** 58 | 59 | - **#wellness:** share your tips on health and fitness so we can be healthy together. 60 | 61 | - **#standup**: every day of code, give us your standup updates! What you did yesterday, what you plan to do today, and any blockers? 62 | 63 | - **#achievements**: share your (personal) achievements with the community 64 | 65 | **COMMUNITY DISCUSSION:** 66 | 67 | - **#ideas**: got an idea / suggestion for the community? We love hearing new ideas 🤓 68 | 69 | - **#first-timers**: discussion about getting 🟩 70 | 71 | - **#public-speaking**: improve your soft skills, public speaking, and build communities 72 | 73 | - **#eddihub-contributors**: contributing to EddieHub, get help and support here! https://github.com/EddieHubCommunity?view_as=public 74 | 75 | - **#maintainers**: maintaining discussions 76 | 77 | - **#bot-chat**: discuss bots, esp. regarding development of EddieBot. This is also a place to check your profile and ranks in the community using the bot or use the other bot commands. 78 | 79 | You can raise an issue or a Pull request here https://github.com/EddieHubCommunity/support/blob/main/docs/discord/discord-readme.md 80 | 81 | If you find any necessary changes to be made in the README, get started with open source and get your 🟩 right away! 82 | 83 | **Where to join our GitHub community?** 84 | 85 | - Click on this link to get invited to the community! https://github.com/EddieHubCommunity/support/issues/new?assignees=&labels=invite+me+to+the+organisation&template=invitation.yml&title=Please+invite+me+to+the+GitHub+Community+Organization 86 | 87 | **How to ask for help** 88 | Tips to help you ask questions that will give you a better chance to get the best answers from everyone. 89 | 90 | 1. **Read through your code first.** Your problem could be as simple as a typo or a missing closing tag. 91 | 2. **Ask Google.** Many code problems can be solved with a quick Google, so give this a try first. If that doesn't help, head back here to ask your question, and follow the tips below. 92 | 3. **Clearly describe the problem.** Explain what is happening and what you want to happen. 93 | 4. **Share your code.** It’s very unlikely that anyone will be able to solve your problem without seeing your code. Share a GitHub repository, a GitHub gist link, or format the code by wrapping it in backticks, like the example below. 94 | 95 | ````txt 96 | ```ts 97 | // Your code goes here 98 | ``` 99 | ```` 100 | 101 | 102 | 103 | 5. **Send screenshots, if relevant.** It often helps people to see the browser output, so send over a screenshot of what you can see, in this case. 104 | 6. **Explain what you have already tried.** You don't want people to suggest things you have already done. 105 | 7. **Send updates so people know whether their answer has helped you.** 106 | 8. **Help other people out when you can.** If people see you helping others, they will be even more likely to help you when you need it. 107 | 108 | ## Roles 109 | 110 | Our server has several roles you can assign to yourself, such as roles for your specific tech stack or roles that we ping for certain events. 111 | 112 | To see the roles that are available, head over to #bot-chat and use the command `becca!role`. Becca will send a list of the roles you can assign to yourself. 113 | 114 | To assign a role, use `/community role ` and Becca will give you that role. For example, if I wanted the `angular` role, I would send the command `/community role angular`. 115 | -------------------------------------------------------------------------------- /docs/discord/roles.md: -------------------------------------------------------------------------------- 1 | # Roles 2 | 3 | Description of each roles in the EddieHub Discord community. 4 | 5 | --- 6 | 7 | | Role | Description | Additional Info | 8 | | :---: | :---: | :---: | 9 | | Admin | The people who manage the server. | They also get the permissions manage the server settings. | 10 | | Moderators | Volunteers who help us make the community more inclusive. | May take necessary actions (kick/ban) for violating the rules. | 11 | | GitHub Star | People who have been recognized as GitHub Stars! | Program that empowers Stars to inspire, educate and influence communities. | 12 | | Sponsors | Folks who support Eddie's work with a sponsorship. | Access to a private channel and a monthly sponsor call! | 13 | | Community Partner | Communities who've partnered with us to help provide even more awesome value! | Represent one of our partner communities. | 14 | | Repository Maintainer | Volunteers who help us maintain our open source projects. | They help us handle our projects. | 15 | | Public Speaking Helpers | Helpers who schedule, plan and organise our weekly public speaking call. | They also create reminders/notification by pinging @public speaking. | 16 | | Team Eddie | Enthusiastic people who have added a lot of value to our community! | Participate in private discussions and get access to share links. | 17 | | MLH Guild Mentors | Mentors for our MLH Guild in MLH Guild Events. | A mentor can inspire someone to continue to build and learn after a hackathon. | 18 | | Bio | A role assigned when you add a bio to EddieBot (Legacy). | - | 19 | | MLH Guild | Members of our MLH Guild in MLH Guild Events. | - | 20 | | Community Chat | Let people connect more deeply with communities in real time. | - | 21 | | public speaking | Get notified about Public Speaking Events. | - | 22 | | Battlesnake | A role for [Battlesnake](https://play.battlesnake.com/) participants. | - | 23 | | Among Us | Get notified about game nights and such events. | - | 24 | | Tech Stack Roles | Self assignable roles, to mark your skills. | - | 25 | -------------------------------------------------------------------------------- /docs/icon.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/EddieHubCommunity/support/52f7d86c79248f336189aa2783f34aa88e72bc6c/docs/icon.png -------------------------------------------------------------------------------- /docs/index.html: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 13 | 15 | EddieHub Support 16 | 17 | 18 | 19 | 20 |
21 |

EddieHub Support Repo

22 |

Resources to help our community grow and thrive.

23 |
24 | 25 | 97 | 98 | 99 | 101 | 102 | 103 | 104 | 105 | 106 | 107 | 108 | 109 | -------------------------------------------------------------------------------- /docs/index.md: -------------------------------------------------------------------------------- 1 | # Welcome 2 | 3 | Welcome to the EddieHub Support resource. 4 | 5 | Imagine the scenario where you are helping a stranger, a friend, or a colleague on Discord / MS Teams / Slack / YouTube, etc. They may have found an old article from 5+ years ago about Docker that is not supported or a Node.js article that isn't supported in Node v14. That sort of thing... 6 | 7 | You volunteer to help that person and pair on it. You fix it and they get super happy. 8 | 9 | The unfortunate thing about this is that it lacks a write-up on what was used. It's important to know the articles that were used for reference purpose. This is where a GitHub issue queue comes in. That way, folks could Google for somebody with the same problem! 10 | 11 | Unfortunately, StackOverflow has a bit of a broken reputation system where folks with the "worst accepted answer" can actually start to get privileges to do more things. 12 | 13 | ## Join our Community 14 | 15 | Join our Discord community [here](http://discord.eddiehub.org) 16 | Subscribe our YouTube channel [here](https://www.youtube.com/user/eddiejaoude) 17 | -------------------------------------------------------------------------------- /docs/logo.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/EddieHubCommunity/support/52f7d86c79248f336189aa2783f34aa88e72bc6c/docs/logo.png -------------------------------------------------------------------------------- /docs/mee6/welcome-dm.md: -------------------------------------------------------------------------------- 1 | # Welcome DM 2 | 3 | This is the template for the welcome message MEE6 sends when someone joins our server. 4 | 5 | > Have a great time here in **{server}**. We are a friendly and inclusive community. Please set a profile picture (it can be a pet or cartoon character if you prefer not to have your face on there), dont forget to play nicely and collaborate with the community. If you have any issues please make the **Moderators** aware. Lets geek out! 6 | -------------------------------------------------------------------------------- /docs/moderators/discord.md: -------------------------------------------------------------------------------- 1 | # Moderating Discord 2 | 3 | Coming soon! :) 4 | -------------------------------------------------------------------------------- /docs/moderators/github.md: -------------------------------------------------------------------------------- 1 | # Maintaining Repositories 2 | 3 | This page is intended to provide guidelines for maintaining EddieHub's various repositories. 4 | 5 | ## When To Merge PRs 6 | 7 | Pull requests should be merged only after: 8 | 9 | - At least 2 maintainers have provided an approving review. 10 | - All requested changes have been resolved (no "unresolved conversations"). 11 | - All CI checks (GitHub Actions) are passing. 12 | 13 | ## How to Merge PRs 14 | 15 | When merging a pull request, you should generally perform a "Squash and Merge". This will squash all of the commits into one. 16 | 17 | When you do this, GitHub's UI will give you a chance to edit the commit message. Be sure to follow the [Conventional Commit](https://www.conventionalcommits.org/en/v1.0.0/) format: 18 | 19 | ```txt 20 | (): 21 | ``` 22 | 23 | - `type` is the nature of the change: 24 | - `feat` for new features 25 | - `fix` for bug fixes 26 | - `docs` for documentation changes 27 | - `chore` for changes such as updating developer configs (`.eslintrc.json`) or similar changes that don't affect the end user. 28 | - `scope` is **optional**, and explains the part of the codebase the change touches: 29 | - `api` for a backend change 30 | - `client` for a front end change 31 | - `tools` for things like actions 32 | - `tests` for adding tests 33 | - ...and so on. 34 | - `message` is a brief description of the changes the pull request makes. 35 | 36 | For example, the commit message which created this file was `docs: add drafts for moderation guide`. 37 | 38 | Additionally, GitHub will automatically append the pull request number at the end of the default commit message. **DO NOT REMOVE THIS**, as it allows people to reference the pull request that created the commit to check the full commit history. 39 | 40 | ## Handling Inactive PRs 41 | 42 | If a contributor has not responded to reviews or comments on a PR, follow this general timeline for how to respond: 43 | 44 | - After 7 days (one week) of inactivity, a maintainer should comment on the PR. 45 | - This comment should ping the author, ask for a status update, and remind them that we have a Discord server if they need assistance with contributing. 46 | - After 14 days (two weeks) of inactivity **since the contributor's last comment**, a maintainer should close the pull request. 47 | - Be sure to leave a friendly message thanking them for their efforts and inviting them to request that we re-open the PR when they are available to complete the changes. 48 | 49 | In general, only _one_ maintainer should be reaching out to the contributor. If multiple maintainers reach out, we could inadvertently make our contributors feel pressured/rushed. We are all busy and want to respect each others' time. 50 | 51 | ## Handling Inactive Issues 52 | 53 | In general, inactive issues are handled by `Stalebot`, which will add a label after a period of inactivity and close the issue a few days later. 54 | 55 | If an issue should not be closed, remove the `stale issue` label that the action has added, and then leave a comment on the issue explaining why it is still necessary. If an issue is repeatedly being labeled by the bot, it may indicate that it is not a priority and we should re-evaluate the need. 56 | -------------------------------------------------------------------------------- /docs/nightbot/allowed-links.md: -------------------------------------------------------------------------------- 1 | # Nightbot Config 2 | 3 | This file documents our configuration for Nightbot. 4 | 5 | ## Allowed links 6 | 7 | These links are on Nightbots allowed list 8 | 9 | ```txt 10 | github.com 11 | ~/[\s]*\.github\.com/i 12 | gist.github.com 13 | lab.github.com 14 | stars.github.com 15 | tenor.com 16 | ~/[\s]*\.tenor.com\.io/i 17 | ~/[\s]*\.giphy.com\.io/i 18 | shields.io 19 | ~/[\s]*\.mlh\.io/i 20 | figma.com 21 | repl.it 22 | codepen.io 23 | git.io 24 | b.tech 25 | eddiejaoude.io 26 | eddiehub.org 27 | asp.net 28 | githubstatus.com 29 | ``` 30 | -------------------------------------------------------------------------------- /docs/snippets/README.md: -------------------------------------------------------------------------------- 1 | # Pull Request Saved Replies 2 | 3 | > When commenting on an issue or pull request, you can add a saved reply that you've already set up. The saved reply can be the entire comment or if you want to customize it, you can add or delete content. 4 | 5 | Official docs https://docs.github.com/en/get-started/writing-on-github/working-with-saved-replies/using-saved-replies 6 | -------------------------------------------------------------------------------- /docs/snippets/de/github-action-failing.md: -------------------------------------------------------------------------------- 1 | ## GitHub Actions sind fehlgeschlagen 2 | 3 | ### TLDR; 4 | 5 | Vielen Dank für den PR. Eine GitHub Action ist fehlgeschlagen. Bitte prüfe 6 | den Output, um mehr über den Fehler zu erfahren. 7 | 8 | Falls du Fragen haben solltest, kannst du diese gerne im [EddieHub Discord Channel](http://discord.eddiehub.org) stellen. 9 | 10 | --- 11 | 12 | ### 13 | 14 | GitHub Actions führen automatisierte Tests durch. Sie ersetzen nicht die manuelle Überprüfung, aber helfen uns, den Fokus auf eine wertvollere Zusammenarbeit zu legen. 15 | 16 | GitHub Actions beinhalten normalerweise... 17 | 18 | - Erstellen des Projekts 19 | - Automatisiertes Testen 20 | - Linting zur Überprüfung einer konstanten Formatierung des Codes 21 | 22 | --- 23 | 24 | - Sprachen: alle 25 | - Labels: Styleguide 26 | -------------------------------------------------------------------------------- /docs/snippets/de/issue-before-pr.md: -------------------------------------------------------------------------------- 1 | ## Erstellen Sie ein Issue vor dem Pull Request (PR) 2 | 3 | ### TLDR; 4 | 5 | Vielen Dank für den PR. Es empfiehlt sich, zuerst ein Issue zu erstellen. 6 | 7 | --- 8 | 9 | ### 10 | 11 | Vorteile, zuerst ein Issue zu erstellen 12 | 13 | - Optionen können vorab diskutiert werden, noch bevor Zeit für die Umsetzung der 14 | Änderungen aufgewendet wird 15 | - Andere können sich an der Durchführung der Änderungen beteiligen 16 | 17 | --- 18 | 19 | - Sprachen: alle 20 | - Labels: Styleguide 21 | -------------------------------------------------------------------------------- /docs/snippets/de/join-discord.md: -------------------------------------------------------------------------------- 1 | ## Treten Sie Discord bei 2 | 3 | ### TLDR; 4 | 5 | Kommen und nehmen Sie an Echtzeit-Diskussionen und Kollaborationen teil http://discord.eddiehub.org 6 | 7 | --- 8 | 9 | ### 10 | 11 | GitHub ist großartig für asynchrone Unterhaltungen und die Aufrechterhaltung der 12 | Zusammenarbeit. Aber manchmal brauchen wir auch Echtzeit-Diskussionen 13 | 14 | - Schnellere Antworten 15 | - Mehrere Personen können sich an der Konversation beteiligen 16 | - Anrufe und Screen-Sharing 17 | 18 | --- 19 | 20 | - Sprachen: alle 21 | - Labels: Styleguide 22 | -------------------------------------------------------------------------------- /docs/snippets/de/screenshots.md: -------------------------------------------------------------------------------- 1 | ## Screenshots helfen bei der Überprüfung 2 | 3 | ### TLDR; 4 | 5 | Deine PR-Änderungen zu erläutern ist großartig. Bitte ziehe auch in Betracht, einen Vorher/Nachher-Screenshot hinzuzufügen. 6 | 7 | --- 8 | 9 | ### 10 | 11 | Ein Bild sagt mehr als 1000 Worte - in unserem Fall ein Screenshot. 12 | 13 | - Es unterstützt den Reviewer dabei, die Änderungen zu verstehen. 14 | - Mache es dem Reviewer so einfach wie möglich, indem du einen Vorher/Nachher-Screenshot hinzufügst. 15 | 16 | --- 17 | 18 | - Sprachen: alle 19 | - Labels: Styleguide 20 | -------------------------------------------------------------------------------- /docs/snippets/de/smaller-pull-requests.md: -------------------------------------------------------------------------------- 1 | ## Kleinere und fokussierte Pull Requests (PR) 2 | 3 | ### TLDR; 4 | 5 | Je kleiner und fokussierter der PR ist, desto einfacher ist es für den Reviewer 6 | und desto wahrscheinlicher ist es, dass der PR schneller gemergt wird. 7 | 8 | --- 9 | 10 | ### Warum sind kleinere PRs besser? 11 | 12 | - Einfacher für den Reviewer 13 | - Werden schneller gemergt - Reduziert Konflikte mit anderen Änderungen 14 | - Sie erhalten mehr grüne Quadrate, wenn Sie PRs in fokussierte Änderungen aufteilen 15 | 16 | --- 17 | 18 | - Sprachen: alle 19 | - Labels: Styleguide 20 | -------------------------------------------------------------------------------- /docs/snippets/de/update-branch.md: -------------------------------------------------------------------------------- 1 | ## Aktualisieren Sie den Branch Ihres Forks 2 | 3 | ## TLDR; 4 | 5 | Vielen Dank für den PR. Dein Branch scheint hinter dem Default Branch `main` zu 6 | liegen. Bitte aktualisiere deinen Branch mit den aktuellen Änderungen. 7 | 8 | --- 9 | 10 | ### Vollständige Details 11 | 12 | Wenn Änderungen eingebunden/gemerged werden, können andere PRs veraltet sein und 13 | müssen aktualisiert werden. 14 | 15 | - Aktualisieren Sie den Default-Branch `main` Ihres Forks 16 | - Merge `main` in deinen Branch 17 | 18 | --- 19 | 20 | - Sprachen: alle 21 | - Labels: Styleguide 22 | -------------------------------------------------------------------------------- /docs/snippets/en/github-action-failing.md: -------------------------------------------------------------------------------- 1 | ## GitHub Actions are failing 2 | 3 | ### TLDR; 4 | 5 | Thank you for the PR. There is a GitHub Action failing, please check the Action output to find out more about the error. 6 | 7 | Any questions feel free to ask in the EddieHub Discord http://discord.eddiehub.org 8 | 9 | --- 10 | 11 | ### 12 | 13 | GitHub Actions perform automated tests. They do not replace manual review but help us focus on the more valuable collaboration. 14 | 15 | GitHub Actions usually include... 16 | 17 | - Building the project 18 | - Automated testing 19 | - Linting to check consistent in code formatting 20 | 21 | --- 22 | 23 | - Languages: all 24 | - Labels: Style guide 25 | -------------------------------------------------------------------------------- /docs/snippets/en/issue-before-pr.md: -------------------------------------------------------------------------------- 1 | ## Create an Issue before the Pull Request (PR) 2 | 3 | ### TLDR; 4 | 5 | Thank you for the PR. It is better to make an issue first. 6 | 7 | --- 8 | 9 | ### 10 | 11 | Benefits of creating an Issue first 12 | 13 | - We get to discuss options before time is spent on making the changes 14 | - Others can get involved in helping make the changes 15 | 16 | --- 17 | 18 | - Languages: all 19 | - Labels: Style guide 20 | -------------------------------------------------------------------------------- /docs/snippets/en/join-discord.md: -------------------------------------------------------------------------------- 1 | ## Join Discord 2 | 3 | ### TLDR; 4 | 5 | Come and join the realtime discussion and collaboration http://discord.eddiehub.org 6 | 7 | --- 8 | 9 | ### 10 | 11 | GitHub is great for async conversations and persisting the collaboration. But sometimes we need that realtime conversation too 12 | 13 | - Faster responses 14 | - Multiple can join in the conversation 15 | - Call and screensharing 16 | 17 | --- 18 | 19 | - Languages: all 20 | - Labels: Style guide 21 | -------------------------------------------------------------------------------- /docs/snippets/en/screenshots.md: -------------------------------------------------------------------------------- 1 | ## Screenshots help with review 2 | 3 | ### TLDR; 4 | 5 | Explaining your PR changes is great. Please also consider adding a before/after screenshot. 6 | 7 | --- 8 | 9 | ### 10 | 11 | A picture speaks a 1000s words, well in our case a screenshot. 12 | 13 | - It really helps the reviewer to understand the changes. 14 | - Make it as straight forward as possible for the reviewer by adding a before/after screenshot. 15 | 16 | --- 17 | 18 | - Languages: all 19 | - Labels: Style guide 20 | -------------------------------------------------------------------------------- /docs/snippets/en/smaller-pull-requests.md: -------------------------------------------------------------------------------- 1 | ## Smaller and focused Pull Requests (PR) 2 | 3 | ### TLDR; 4 | 5 | The smaller and more focused the PR the easier for the reviewer and the more likely it is to merge faster. 6 | 7 | --- 8 | 9 | ### 10 | 11 | Why are smaller PRs better 12 | 13 | - Easier for the reviewer 14 | - Will get merged faster 15 | - Reduces conflicts with other changes 16 | - You get more green squares if you separate PRs out into focused changes 17 | 18 | --- 19 | 20 | - Languages: all 21 | - Labels: Style guide 22 | -------------------------------------------------------------------------------- /docs/snippets/en/update-branch.md: -------------------------------------------------------------------------------- 1 | ## Update your fork's branch 2 | 3 | ### TLDR; 4 | 5 | Thank you for the PR. Your branch seems to be behind the default branch `main`. Please can you update with the latest changes. 6 | 7 | --- 8 | 9 | ### Full details 10 | 11 | As changes are merged in, other PRs can get out of date, and will need to be updated. 12 | 13 | - Update your fork's default branch `main` 14 | - Merge `main` into your branch 15 | 16 | --- 17 | 18 | - Languages: all 19 | - Labels: Style guide 20 | -------------------------------------------------------------------------------- /docs/snippets/es/github-action-failing.md: -------------------------------------------------------------------------------- 1 | ## Las acciones de GitHub están fallando 2 | 3 | ### TLDR; 4 | 5 | Gracias por la PR. Hay una acción de GitHub que falla, por favor verifica la salida de la acción para obtener más información sobre el error. 6 | 7 | Cualquier pregunta siéntate libre de preguntar en el Eddie Hub Discord http://discord.eddiehub.org 8 | 9 | --- 10 | 11 | ### 12 | 13 | Las acciones de GitHub realizan pruebas automatizadas. No reemplazan la revisión manual, sino que nos ayudan a centrarnos en la colaboración más valiosa. 14 | 15 | Las acciones de GitHub generalmente incluyen... 16 | 17 | - Construyendo el proyecto 18 | - Pruebas automatizadas 19 | - Linting para comprobar la consistencia en el formato del código 20 | 21 | --- 22 | 23 | - Idiomas: Todos 24 | - Etiquetas: Guía de estilo 25 | -------------------------------------------------------------------------------- /docs/snippets/es/issue-before-pr.md: -------------------------------------------------------------------------------- 1 | ## Crear un problema antes de la Solicitud de extracción (PR) 2 | 3 | ### TLDR; 4 | 5 | ## Gracias por la PR. Es mejor crear un problema primero. 6 | 7 | ### 8 | 9 | Beneficios de crear un problema primero 10 | 11 | - Tenemos la oportunidad de discutir las opciones antes de gastar tiempo en hacer los cambios 12 | - Otros pueden participar en ayudar a hacer los cambios 13 | 14 | --- 15 | 16 | - Idiomas: todas 17 | - Etiquetas: Guía de estilo 18 | -------------------------------------------------------------------------------- /docs/snippets/es/join-discord.md: -------------------------------------------------------------------------------- 1 | ## Únete a Discord 2 | 3 | ### TLDR; 4 | 5 | Ven y únete a la discusión y colaboración en tiempo real http://discord.eddiehub.org 6 | 7 | --- 8 | 9 | ### 10 | 11 | GitHub es ideal para conversaciones asincrónicas y para persistir en la colaboración. Pero a veces también necesitamos esa conversación en tiempo real 12 | 13 | - Respuestas más rápidas 14 | - Múltiples pueden unirse a la conversación 15 | - Uso compartido de llamadas y pantallas 16 | 17 | --- 18 | 19 | - Idiomas: todas 20 | - Etiquetas: Guía de estilo 21 | -------------------------------------------------------------------------------- /docs/snippets/es/screenshots.md: -------------------------------------------------------------------------------- 1 | ## Capturas de pantalla ayuda con la revisión 2 | 3 | ### TLDR; 4 | 5 | Explicar tus cambios en una PR es genial. También considera agregar una captura de pantalla antes/después. 6 | 7 | --- 8 | 9 | ### 10 | 11 | Una imagen habla a mil palabras, bueno en nuestro caso una captura de pantalla. 12 | 13 | - Realmente ayuda al revisor a comprender los cambios. 14 | - Haz que sea lo más sencillo posible para el revisor agregando una captura de pantalla antes/después. 15 | 16 | --- 17 | 18 | - Idiomas: todas 19 | - Etiquetas: Guía de estilo 20 | -------------------------------------------------------------------------------- /docs/snippets/es/smaller-pull-requests.md: -------------------------------------------------------------------------------- 1 | ## Solicitudes de extracción más pequeñas y enfocadas (PR) 2 | 3 | ### TLDR; 4 | 5 | Cuanto más pequeño y centrado sea el PR, más fácil será para el revisor y más probable será que se fusione más rápido. 6 | 7 | --- 8 | 9 | ### 10 | 11 | Por qué son mejores las PR más pequeñas 12 | 13 | - Más fácil para el revisor 14 | - Se fusionarán más rápido 15 | - Reduce los conflictos con otros cambios 16 | - Obtienes más cuadrados verdes si separas las PR en cambios enfocados 17 | 18 | --- 19 | 20 | - Idiomas: todas 21 | - Etiquetas: Guía de estilo 22 | -------------------------------------------------------------------------------- /docs/snippets/es/update-branch.md: -------------------------------------------------------------------------------- 1 | ## Actualiza la rama de tu bifurcación 2 | 3 | ### TLDR; 4 | 5 | Gracias por la PR. Tu rama parece estar detrás de la rama predeterminada `main`. Por favor, puedes actualizar con los últimos cambios. 6 | 7 | --- 8 | 9 | ### Detalles completos 10 | 11 | A medida que los cambios se fusionan, otras PR pueden quedar obsoletas y deberán actualizarse. 12 | 13 | - Actualiza la rama `main` predeterminada de tu bifurcación 14 | - Fusiona `main` en tu rama 15 | 16 | --- 17 | 18 | - Idiomas: todas 19 | - Etiquetas: Guía de estilo 20 | -------------------------------------------------------------------------------- /docs/snippets/id/github-action-failing.md: -------------------------------------------------------------------------------- 1 | ## GitHub Actions gagal 2 | 3 | ### TLDR; 4 | 5 | Terima kasih atas PR Anda. Ada kegagalan GitHub Action. Silakan periksa keluaran pada Action untuk mengetahui lebih lanjut tentang kesalahan yang terjadi. 6 | 7 | Jika ada pertanyaan, silakan sampaikan di [Discord EddieHub](http://discord.eddiehub.org). 8 | 9 | --- 10 | 11 | ### 12 | 13 | GitHub Actions melakukan pengujian otomatis. Mereka tidak menggantikan tinjauan manual, tetapi membantu kita fokus kepada kolaborasi yang lebih berharga. 14 | 15 | GitHub Actions biasanya mencakup... 16 | 17 | - Membangun proyek 18 | - Pengujian otomatis 19 | - Linting untuk memeriksa konsisten dalam pemformatan kode 20 | 21 | --- 22 | 23 | - Bahasa: semua 24 | - Label: Panduan gaya 25 | -------------------------------------------------------------------------------- /docs/snippets/id/issue-before-pr.md: -------------------------------------------------------------------------------- 1 | ## Buat Isu sebelum Pull Request (PR) 2 | 3 | ### TLDR; 4 | 5 | Terima kasih atas PR Anda. Lebih baik Anda membuat isu terlebih dahulu. 6 | 7 | --- 8 | 9 | ### 10 | 11 | Manfaat membuat isu terlebih dahulu 12 | 13 | - Sebelum waktu dihabiskan untuk membuat perubahan, kita dapat mendiskusikan opsi 14 | - Orang lain dapat ikut membantu membuat perubahan 15 | 16 | --- 17 | 18 | - Bahasa: semua 19 | - Label: Panduan gaya 20 | -------------------------------------------------------------------------------- /docs/snippets/id/join-discord.md: -------------------------------------------------------------------------------- 1 | ## Bergabung di Discord 2 | 3 | ### TLDR; 4 | 5 | Mari bergabung dalam diskusi dan kolaborasi secara langsung di [Discord EddieHub](http://discord.eddiehub.org). 6 | 7 | --- 8 | 9 | ### 10 | 11 | GitHub sangat baik untuk percakapan asinkron dan mempertahankan kolaborasi. 12 | Tapi terkadang kita juga membutuhkan percakapan secara langsung. 13 | 14 | - Respon yang lebih cepat 15 | - Beberapa orang dapat bergabung dalam percakapan 16 | - Panggilan dan berbagi layar 17 | 18 | --- 19 | 20 | - Bahasa: semua 21 | - Label: Panduan gaya 22 | -------------------------------------------------------------------------------- /docs/snippets/id/screenshots.md: -------------------------------------------------------------------------------- 1 | ## Tangkapan layar membantu peninjauan 2 | 3 | ### TLDR; 4 | 5 | Menjelaskan perubahan PR Anda sangat baik. Harap pertimbangkan juga untuk menambah tangkapan layar sebelum dan sesudah perubahan. 6 | 7 | --- 8 | 9 | ### 10 | 11 | Sebuah gambar berbicara 1000 kata. Dalam hal ini, sebuah tangkapan layar. 12 | 13 | - Tangkapan layar sangat membantu peninjau untuk memahami perubahan. 14 | - Buatlah selugas mungkin untuk peninjau dengan menambahkan tangkapan layar sebelum dan sesudah perubahan. 15 | 16 | --- 17 | 18 | - Bahasa: semua 19 | - Label: Panduan gaya 20 | -------------------------------------------------------------------------------- /docs/snippets/id/smaller-pull-requests.md: -------------------------------------------------------------------------------- 1 | ## Pull Request (PR) yang lebih kecil dan terfokus 2 | 3 | ### TLDR; 4 | 5 | Semakin kecil dan lebih terfokusnya PR, semakin mudah bagi peninjau dan semakin besar kemungkinannya untuk digabungkan lebih cepat. 6 | 7 | --- 8 | 9 | ### 10 | 11 | Mengapa PR yang lebih kecil lebih baik 12 | 13 | - Lebih mudah bagi peninjau 14 | - Akan digabung lebih cepat 15 | - Mengurangi konflik dengan perubahan lainnya 16 | - Anda mendapatkan lebih banyak kotak hijau jika Anda memisahkan PR menjadi perubahan terfokus 17 | 18 | --- 19 | 20 | - Bahasa: semua 21 | - Label: Panduan gaya 22 | -------------------------------------------------------------------------------- /docs/snippets/id/update-branch.md: -------------------------------------------------------------------------------- 1 | ## Perbarui cabang garpu Anda 2 | 3 | ### TLDR; 4 | 5 | Terima kasih untuk PR Anda. Cabang Anda tampaknya berada di belakang cabang default `main`. Harap perbarui dengan perubahan terbaru. 6 | 7 | --- 8 | 9 | ### Detail Lengkap 10 | 11 | Ketika perubahan digabungkan, PR lainnya dapat tertinggal dan perlu diperbarui. 12 | 13 | - Perbarui cabang default `main` garpu Anda 14 | - Gabung `main` ke dalam cabang Anda 15 | 16 | --- 17 | 18 | - Bahasa: semua 19 | - Label: Panduan gaya 20 | -------------------------------------------------------------------------------- /docs/snippets/pt/github-action-failing.md: -------------------------------------------------------------------------------- 1 | ## GitHub Actions estão a falhar 2 | 3 | ### TLDR; 4 | 5 | Obrigado pelo seu PR. Como há uma GitHub Action que está a falhar, por favor verifique a saída da Action para estabelecer qual é o erro. 6 | 7 | Se tiver qualquer duvida não hesite em perguntar no EddieHub Discord http://discord.eddiehub.org 8 | 9 | --- 10 | 11 | ### 12 | 13 | As GitHub Actions executam certos testes automatizados. Elas não substituem revisões manuais, mas ajudam nos a focar na colaboração que é mais valiosa. 14 | 15 | GitHub Actions normalmente incluem: 16 | 17 | - Construção de um projeto 18 | - Testes automatizados 19 | - Linting para verificar a consistência na formatação do código 20 | 21 | --- 22 | 23 | Línguas: todas 24 | Rótulo: Guia de estilo 25 | -------------------------------------------------------------------------------- /docs/snippets/pt/issue-before-pr.md: -------------------------------------------------------------------------------- 1 | ## Criar um Assunto (Issue) antes to Pull Request (PR) 2 | 3 | ### TLDR; 4 | 5 | Obrigado pelo seu PR. Será melhor criar um assunto primeiro 6 | 7 | --- 8 | 9 | ### 10 | 11 | Benefícios em criar uma Assunto primeiro: 12 | 13 | - Temos a oportunidade de discutir opções antes de gastarmos tempo nas alterações 14 | - Outros participantes podem ajudar a fazer as alterações 15 | 16 | --- 17 | 18 | - Languages: all Línguas: todas 19 | - Labels: Style guide Rótulo: Guia de estilo 20 | -------------------------------------------------------------------------------- /docs/snippets/pt/join-discord.md: -------------------------------------------------------------------------------- 1 | ## Junte-se ao Discord 2 | 3 | ### TLDR; 4 | 5 | Venha participar na discussão e colaboração em tempo real http://discord.eddiehub.org 6 | 7 | --- 8 | 9 | ### 10 | 11 | GitHub é óptimo para conversas assíncronas e manter a colaboração. No entanto as vezes é necessário ter conversas em tempo real 12 | 13 | - Respostas mais rápidas 14 | - Vários participantes podem juntar-se à conversa 15 | - Chamadas e partilha de ecrã 16 | 17 | --- 18 | 19 | - Línguas: todas 20 | - Rótulo: Guia de estilo 21 | -------------------------------------------------------------------------------- /docs/snippets/pt/screenshots.md: -------------------------------------------------------------------------------- 1 | ## A captura de ecrã (screenshots) ajuda as revisões 2 | 3 | ### TLDR; 4 | 5 | Providenciar uma explicação das mudanças do seu PR é óptimo. Considere também adicionar uma imagem da captura de ecrã do antes e depois. 6 | 7 | --- 8 | 9 | Uma imagem vale por mil palavras ou, neste caso, a captura de ecrã (screenshot). 10 | 11 | - Ajuda o revisor a entender as alterações. 12 | - Se adicionar uma imagem do antes e depois tornasse mais simples para o revisor 13 | 14 | --- 15 | 16 | - Línguas: todas 17 | - Rótulo: Guia de estilo 18 | -------------------------------------------------------------------------------- /docs/snippets/pt/smaller-pull-requests.md: -------------------------------------------------------------------------------- 1 | ## Pull Requests (PR) pequenos e focados 2 | 3 | ### TLDR; 4 | 5 | Quanto mais pequeno e focado o PR, mais fácil será para o revisor e maior a probabilidade da fusão do PR ser mais rápida. 6 | 7 | --- 8 | 9 | ### 10 | 11 | Porque é que os PR pequenos são melhores 12 | 13 | - Mais fácil para o revisor 14 | - A fusão será mais rápida 15 | - Reduz conflitos com outras alterações 16 | - Terás mais quadrados verdes se separares os PRs em mudanças focadas 17 | 18 | --- 19 | 20 | - Línguas: todas 21 | - Rótulo: Guia de estilo 22 | -------------------------------------------------------------------------------- /docs/snippets/pt/update-branch.md: -------------------------------------------------------------------------------- 1 | ## Atualizar o ramo da sua bifurcação 2 | 3 | ### TLDR; 4 | 5 | Obrigado pelo seu PR. O seu ramo parece estar atrás da predefinição do ramo main. Por favor atualize com as ultimas mudanças. 6 | 7 | --- 8 | 9 | ### Detalhes completos 10 | 11 | À medida que as mudanças são fundidas, outros PRs ficarão desatualizados e precisarão ser atualizados. 12 | 13 | - Atualize o ramo main para uma bifurcação prédefinida 14 | - Merge main into your branch 15 | - Funda o main no seu ramo 16 | 17 | --- 18 | 19 | - Línguas: todas 20 | - Rótulo: Guia de estilo 21 | -------------------------------------------------------------------------------- /docs/snippets/ru/github-action-failing.md: -------------------------------------------------------------------------------- 1 | ## GitHub Actions не выполняются 2 | 3 | ### TLDR; 4 | 5 | Спасибо Вам за PR. Произошел сбой GitHub Action, пожалуйста проверьте Action output чтобы узнать больше об ошибке. 6 | 7 | По любым вопросам обращайтесь в Discord EddieHub http://discord.eddiehub.org 8 | 9 | --- 10 | 11 | ### 12 | 13 | GitHub Actions выполняют автоматизированные тесты. Они не заменяют ручную проверку, но помогают нам сосредоточиться на более ценном сотрудничестве. 14 | 15 | GitHub Actions обычно включают... 16 | 17 | - Создание проекта 18 | - Автоматическое тестирование 19 | - Linting для проверки согласованности форматирования кода 20 | 21 | --- 22 | 23 | - Языки: все 24 | - Теги: Руководство по стилю 25 | -------------------------------------------------------------------------------- /docs/snippets/ru/issue-before-pr.md: -------------------------------------------------------------------------------- 1 | ## Создайте Issue перед запросом на Pull Request (PR) 2 | 3 | ### TLDR; 4 | 5 | Спасибо Вам за PR. Лучше сначала создать Issue. 6 | 7 | --- 8 | 9 | ### 10 | 11 | Преимущества создания Issue в первую очередь 12 | 13 | - Возможность обсудить варианты до того как будет потрачено время на внесение изменений 14 | - Другие могут помогать, участвуя во внесении изменений 15 | 16 | --- 17 | 18 | - Языки: все 19 | - Теги: Руководство по стилю 20 | -------------------------------------------------------------------------------- /docs/snippets/ru/join-discord.md: -------------------------------------------------------------------------------- 1 | ## Присоединяйтесь к Discord 2 | 3 | ### TLDR; 4 | 5 | Заходите и присоединяйтесь к обсуждению и совместной работе в реальном времени на http://discord.eddiehub.org 6 | 7 | --- 8 | 9 | ### 10 | 11 | GitHub отлично подходит для асинхронных разговоров и стойкого сотрудничества. Но иногда нам также необходимо обсуждение в реальном времени 12 | 13 | - Более быстрые ответы 14 | - Несколько человек могут присоединиться к обсуждению 15 | - Звонок и демонстрация экрана 16 | 17 | --- 18 | 19 | - Языки: все 20 | - Теги: Руководство по стилю 21 | -------------------------------------------------------------------------------- /docs/snippets/ru/screenshots.md: -------------------------------------------------------------------------------- 1 | ## Скриншоты облегчают обзор 2 | 3 | ### TLDR; 4 | 5 | Объяснение ваших изменений в PR — это здорово. Пожалуйста, также рассмотрите возможность добавления скриншота "до/после". 6 | 7 | --- 8 | 9 | ### 10 | 11 | Изображение может заменить 1000 слов, в нашем случае это скриншот. 12 | 13 | - Это действительно помогает рецензенту понять изменения. 14 | - Сделайте обзор как можно более простым для рецензента, добавив скриншот "до/после". 15 | 16 | --- 17 | 18 | - Языки: все 19 | - Теги: Руководство по стилю 20 | -------------------------------------------------------------------------------- /docs/snippets/ru/smaller-pull-requests.md: -------------------------------------------------------------------------------- 1 | ## Мелкие и целенаправленные Pull Requests (PR) 2 | 3 | ### TLDR; 4 | 5 | Чем меньше и сфокусированнее PR, тем проще для рецензента и тем больше шансов, что PR будет объединен быстрее. 6 | 7 | --- 8 | 9 | ### 10 | 11 | Почему меньшие PR лучше 12 | 13 | - Легче для рецензента 14 | - Будет сливаться быстрее 15 | - Уменьшает конфликты с другими изменениями 16 | - Вы получите больше зеленых квадратов, если разделите PR на целенаправленные изменения 17 | 18 | --- 19 | 20 | - Языки: все 21 | - Теги: Руководство по стилю 22 | -------------------------------------------------------------------------------- /docs/snippets/ru/update-branch.md: -------------------------------------------------------------------------------- 1 | ## Обновите ветку вашего форка 2 | 3 | ### TLDR; 4 | 5 | Спасибо за Ваш PR. По умолчанию Ваша ветка находится позади основной ветки. Пожалуйста, сделайте обновление с последними изменениями. 6 | 7 | --- 8 | 9 | ### Полная информация 10 | 11 | По мере объединения изменений другие PR могут устареть, и их необходимо будет обновить. 12 | 13 | - Обновите основную ветку вашего форка по умолчанию 14 | - Объедините main в свою ветку 15 | 16 | --- 17 | 18 | - Языки: все 19 | - Теги: Руководство по стилю 20 | -------------------------------------------------------------------------------- /docs/tips/OpenSourceResources.md: -------------------------------------------------------------------------------- 1 | # Here are some open source resources for fast improvement 2 | 3 | - Take a look at [firsttimersonly](https://www.firsttimersonly.com/). Some projects have a label for "first timers only", so look for that if you haven't contributed to the project before (e.g. [Spring Boot's repo](https://github.com/spring-projects/spring-boot/issues?q=label%3A%22status%3A+first-timers-only%22+is%3Aclosed)) 4 | - [A practical guide to open source contribution](https://medium.com/@mbbroberg/an-even-more-practical-guide-to-open-source-contribution-dbdaa6ff1994) 5 | - [Awesome README](https://github.com/matiassingers/awesome-readme) 6 | - [Complete Guide to Open Source - How to Contribute](https://www.youtube.com/watch?v=yzeVMecydCE&ab_channel=freeCodeCamp.org) 7 | - [How to contribute to open source by FreeCodeCamp](https://github.com/freeCodeCamp/how-to-contribute-to-open-source) 8 | - [Open Source Guide](https://opensource.guide/) 9 | - [Hacktoberfest beginner resources](https://hacktoberfest.com/participation/#beginner-resources) 10 | -------------------------------------------------------------------------------- /docs/tips/OpenSourceTips.md: -------------------------------------------------------------------------------- 1 | # Open Source tips for beginners 2 | 3 | - Read projects' contribution guidelines (usually on the `CONTRIBUTING.md` file at the root or inside the `.github` folder). 4 | - Contribute small and often. 5 | - Fixing typos and adding documentation is valuable! Don't feel the need to make a PR with just code :slightly_smiling_face: 6 | - Sharing your experience with the project is as much a contribution as a code contribution! For example, write a blog post about how you use a certain library and what problem solves. 7 | - If you are a maintainer of a big project, using Saved Replies can be very helpful when you find yourself repeating the same thing over and over :sweat_smile: Take a look at a [GitHub's blog post](https://github.blog/2016-03-29-saved-replies/). 8 | -------------------------------------------------------------------------------- /docs/tips/finding-open-source-projects.md: -------------------------------------------------------------------------------- 1 | # How to look for an open-source project to contribute? 2 | 3 | So, you decided you want to start contributing to open source. Great :thumbsup:! Now you just need to pick a project to contribute to... but how do you do that? Where do you look for projects? Are all projects open to contributions? 4 | 5 | We know this can be a difficult process, especially if it's your first time contributing to open source. For that reason, we have assimilated a list of tips to help you find a project to contribute to. The list also contains links to other resources about this topic from various authors, to help you further in finding projects that welcome contributors such as yourself :smiley: 6 | 7 | ## Tips 8 | 9 | - Look at our projects in the [EddieHub](https://github.com/EddieHubCommunity) GitHub organization. 10 | - Have a look at your friends and community projects 11 | - A good place to find projects is Twitter. People share projects on what they are working on, or simply repositories they found interesting (e.g.: take a look at this [tweet](https://twitter.com/SimonHoiberg/status/1312048992604258313)). 12 | - Look at the projects/libraries/frameworks you already use, check for improvements you can make, or look at their issues list. 13 | - Search issues on GitHub and filter by labels like `hacktoberfest` or [good-first-issue](https://github.com/search?q=label%3Agood-first-issue+state%3Aopen&type=Issues&ref=advsearch&l=&l=) 14 | - Take a look at the [Explore](https://github.com/explore) page on GitHub. You can also see the trending repositories or choose by topic (e.g.: TypeScript) 15 | 16 | ## Resources 17 | 18 | - [How to contribute to Hacktoberfest and Open Source - finding Issues YouTube video](https://www.youtube.com/watch?v=tjH6txTiC6E) 19 | - [Finding a project to contribute to](http://opensource.guide/how-to-contribute/#finding-a-project-to-contribute-to) 20 | - [First Timers Only website](https://www.firsttimersonly.com/) 21 | - [Awesome First PR Opportunities repository](https://github.com/MunGell/awesome-for-beginners) 22 | - [First Contribution Website](https://firstcontributions.github.io/) 23 | -------------------------------------------------------------------------------- /docs/tips/git.md: -------------------------------------------------------------------------------- 1 | # Git-related tips 2 | 3 | This file contains various tips and tricks for using the `git` CLI (and GitHub too!) 4 | 5 | ## Glossary 6 | 7 | Some helpful `git` and GitHub related terms. 8 | 9 | | Name | Abbreviation | Description | 10 | | :--- | :--- | :--- | 11 | | `repository` | **repo** | A repository is like a folder that holds a project's files, but unlike other folders, a repository is tracked for changes by `git` | 12 | | `commit` | - | A commit holds the specific changes to files that were made since the last `commit` | 13 | | `pull request` | **PR** | Short for "Pull Request", this is a request to merge the changes made on one repository or branch into another repository or branch | 14 | | `branch` | - | A branch is like a new workspace for the same project, allowing you to work on changes, commit them, and push them to a repository without affecting the original branch | 15 | | `fork` | - | A forked repository is a "copy" of a repository that has references to the original. GitHub will track differences between a fork and a source for you, and show the number of different commits | 16 | | `clone` | - | Cloning a repository is the process of bringing the files and configuration from the online/external location to your local machine | 17 | | `remote` | - | A remote repository is a repository stored outside your local computer (so, on GitHub or GitLab for example) | 18 | | `stash` | - | Save the uncommitted work locally | 19 | 20 | ## Rebasing a Fork 21 | 22 | You'll likely run in to situations where your forked version of a project "falls behind" the state of the source version. GitHub will allow you to make a pull request to bring the changes from the source into your fork, which _does work_, but creates a merge commit that will show up every time you create a PR back to the source. 23 | 24 | Instead, to keep the commit history clean, you can `rebase` your fork against the source. Here are the steps to do so: 25 | 26 | - Step one: Make sure you are on your primary branch with `git checkout `. Most commonly, this will be `git checkout main`. 27 | - Step two: Get the current state of the source repository with `git fetch upstream`. If it throws an error that there is no upstream, you'll need to set it ↓ 28 | - Step two.five: To set the upstream, you'll use `git remote add upstream `, where the URL is the clone URL for the source repository. 29 | - Step three: Reset the state of your local repository to match the source with `git reset --hard upstream/`, where `branchname` is the name of the primary branch. So, most likely `git reset --hard upstream/main`. 30 | - Step four: Force your fork repo to match this new state with `git push -f`. 31 | - Step five: Celebrate your success! 32 | 33 | ## Rebasing a PR 34 | 35 | Sometimes you end up with merge conflicts in your pull request, because the target repository has had changes that do not mesh with _your_ changes. GitHub offers a handy GUI for fixing merge conflicts, but this is only available for "non-complex" merge conflicts. If this GUI is _not_ available, you can follow these steps to rebase your PR against the base branch of the fork and resolve the merge conflicts. 36 | 37 | - Step one: Make sure you are on the branch you used for that pull request with `git checkout `. 38 | - Step two: Get the current state of the _source_ repository with `git fetch upstream`.If it throws an error that there is no upstream, you'll need to set it ↓ 39 | - Step two.five: To set the upstream, you'll use `git remote add upstream `, where the URL is the clone URL for the source repository. 40 | - Step three: Trigger the interactive rebase flow with `git rebase -i upstream/branchname` where "branchname" is the name of the *default/primary* branch (most likely `main`.) 41 | - Step four: Using the file that your editor opens up, ensure that all commits are marked as `pick` (they should be, by default.) Save and close the file. 42 | - Step five: Your editor and `git` will now walk you through each commit that generates a merge conflict. Adjust the files, choosing which version of changes you want to keep. Make sure you remove the `<<<<<`, `>>>>>`, and `=====` that `git` adds to show the conflicts! 43 | - Step six: As you fix each file, you will need to `git add ` and `git commit` to commit the resolved changes. 44 | - Step seven: Once all conflicts are resolved, `git` will allow you to `git push` those changes. Your PR should automatically update and reflect the new state, with no merge conflicts! 45 | - Step eight: Celebrate your success! Merge conflicts can definitely be tricky! 46 | 47 | ## Squashing Your Commits 48 | 49 | A maintainer might have a contributing requirement that PRs have only one commit, or they might ask you to squash your PR's commits into one. These steps will help you do so! 50 | 51 | - Step one: Make sure you are on the branch you used for that pull request with `git checkout `. 52 | - Step two: Using `git`'s interactive rebasing feature, we are going to rebase against your current default branch with `git rebase -i origin/` (the branch name is most likely `main`). 53 | - Step three: Using the file that opens in your editor, set the commit at the *top* of the list to `pick` and the rest of the commits to `squash`. Save and close the file. 54 | - Step four: Force your remote branch to accept this new commit history with `git push -f`. 55 | - Step five: Celebrate your success! 🎉 56 | 57 | > **Note**: Force-pushing a branch can have unintended side effects, so be very careful when force-pushing. 58 | 59 | ### Squashing the latest commit 60 | 61 | If you want to squash the latest commit _only_, you can run one single command which is much shorter. 62 | 63 | 1. Be sure to verify that you're on the correct branch. 64 | 2. Stage all your changes by using `git add .` or `git add ` for certain file. 65 | 3. Run the following command. This command will squash the current staged changes with the other commit's changes. 66 | 67 | ```bash 68 | git commit --amend -m "commit message" -m "commit description (optional)" 69 | ``` 70 | 71 | 72 | 4. Force-push your changes to the desired branch. 73 | 74 | ```bash 75 | git push -f 76 | ``` 77 | 78 | 5. You're done now! 🎉 The latest commit has been successfully changed. 79 | -------------------------------------------------------------------------------- /docs/tips/githubtips.md: -------------------------------------------------------------------------------- 1 | # GitHub Tips 2 | 3 | ## Procedural steps to make contributions 4 | 5 | - Fork the project (done via website) 6 | - Clone your fork (to your system) 7 | - Run `git status` 8 | - Create a branch to work from `git checkout -b ` 9 | - Check status `git status` 10 | - Make your code/changes/etc. 11 | - Run `git add ` 12 | - Commit your changes `git commit -m "appropriate note"` 13 | - Push your changes `git push` 14 | - Configure a remote for the fork `git remote add upstream https://github.com/original-owner-username/original-repository.git` 15 | - Update the latest version of the upstream to avoid conflicts `git fetch upstream` 16 | - Switch to main branch in your local fork `git checkout main` 17 | - Merge the upstream changes to your local main branch thus avoiding PR conflicts `git merge upstream/main` 18 | - Request a PR on GitHub (website) after you have done your changes. 19 | 20 | ## Learning more 21 | 22 | - Use GitHub's learning tool 23 | - Short helpful reads 24 | - Digital Ocean Tutorial Series for Open Source 25 | - Thanks to the opensourceTips page, we discovered this 26 | 27 | ## Extra 28 | 29 | - Use [**SSH**](https://docs.github.com/en/github/authenticating-to-github/connecting-to-github-with-ssh) where possible 30 | -------------------------------------------------------------------------------- /docs/tips/glossary.md: -------------------------------------------------------------------------------- 1 | # Glossary 2 | 3 | You will find a bunch of useful programming terms that you must know. 4 | 5 | ## Anonymous Function 6 | 7 | It's a function declared without any named identifier to refer to it. 8 | 9 | ### Code examples 10 | 11 | ```javascript 12 | window.addEventListener("click", function () { 13 | // This is An Anonymous Function 14 | }); 15 | ``` 16 | 17 | ### Frequently Used Terms Definitions 18 | 19 | **git**: an open source, distributed version-control system 20 | 21 | **GitHub**: a platform for hosting and collaborating on Git repositories 22 | 23 | **commit**: a Git object, a snapshot of your entire repository compressed into a SHA 24 | 25 | **branch**: a lightweight movable pointer to a commit 26 | 27 | **clone**: a local version of a repository, including all commits and branches 28 | 29 | **remote**: a common repository on GitHub that all team member use to exchange their changes 30 | 31 | **fork**: a copy of a repository on GitHub owned by a different user 32 | 33 | **pull request**: a place to compare and discuss the differences introduced on a branch with reviews, comments, integrated 34 | tests, and more 35 | 36 | **HEAD**: representing your current working directory, the HEAD pointer can be moved to different branches, tags, or commits 37 | when using git checkout 38 | 39 | **push**: to send committed changes to a remote repository 40 | 41 | **upstream**: of a branch or a fork, the primary branch on the original repository is referred as "upstream" 42 | 43 | **fetch**: to add changes from the remote repository to a local working branch without committing them 44 | 45 | **merge**: to take changes from one branch (in the same repository or from a fork), and apply them into another 46 | 47 | **pull**: to fetch changes and merge them 48 | 49 | ### Additional Resources 50 | 51 | - [Anonymous Function](https://en.wikipedia.org/wiki/Anonymous_function) 52 | - [Frequently Used Terms Definitions](https://docs.github.com/en/get-started/quickstart/github-glossary) 53 | -------------------------------------------------------------------------------- /docs/youtube/generic.md: -------------------------------------------------------------------------------- 1 | # YouTube Channel 2 | 3 | Don't forget to support my channel by subscribing to it! It’s free: https://youtube.com/eddiejaoude?sub_confirmation=1 4 | 5 | MAKE SURE TO TELL YOUR FRIENDS ABOUT IT, SO THAT THEY CAN ALSO LEARN SOMETHING NEW! 6 | 7 | ## YouTube Shorts 8 | 9 | I have another YouTube channel for short clips, please take a moment subscribing to it: https://youtube.com/eddiejaoudetv?sub_confirmation=1 10 | 11 | ## Newsletter 12 | 13 | Make sure to checkout my website and sign up to our community NEWSLETTER: https://www.eddiejaoude.io for my live stream + video schedule and community calls 14 | 15 | ## Join Our Community 16 | 17 | Join our inclusive open source community EddieHub now for FREE at https://www.eddiehub.org 18 | 19 | 1. Go to https://github.com/EddieHubCommunity/support/issues/new/choose 20 | 21 | 2. Choose The Issue Type Of Invite Me To The Organization 22 | 23 | 3. Open The Issue 24 | 25 | 4. You get an invitation to the community by our GitHub Action 🎉 26 | 27 | --- 28 | 29 | ## Community Sponsors 30 | 31 | Stephen Mount https://github.com/stemount 32 | 33 | Nicholas Carrigan https://github.com/nhcarrigan 34 | 35 | Santosh Yadav https://github.com/santoshyadavdev 36 | 37 | Andrew Cunliffe https://github.com/andrew-cunliffe 38 | 39 | Alexander Stoichkov https://github.com/SashoStoichkov 40 | 41 | Allan Regush https://github.com/AllanRegush 42 | 43 | --- 44 | 45 | ## Services I use and recommend 46 | 47 | Some of these might be affiliate links, no extra cost to you, but I get a little $ if you sign up, plus you might get a discount, too. 48 | 49 | \- NoSQL serverless database with DataStax, you will get $25 FREE credit every month http://links.eddiejaoude.io/t/bBM0STvCi2a4 50 | \- Live streaming with Streamyard http://links.eddiejaoude.io/t/pYlzGjcta1a4 51 | \- Cloud hosting with Digital Ocean, you will get $100 FREE credit http://links.eddiejaoude.io/t/EAaCRWhsnZlF 52 | \- Membership, Newsletters, CRM all in one with Kartra http://links.eddiejaoude.io/t/pQ5W3FRLk8Cp 53 | \- Awesome backup platform, BackBlaze http://links.eddiejaoude.io/t/4rqTZjLbwmCp 54 | 55 | --- 56 | 57 | ## Find me on socials 58 | 59 | Website: https://www.eddiejaoude.io 60 | 61 | GitHub: https://github.com/eddiejaoude 62 | 63 | YouTube: https://youtube.com/eddiejaoude 64 | 65 | Twitter: https://twitter.com/eddiejaoude 66 | Instagram: https://instagram.com/eddiejaoude 67 | 68 | LinkedIn: https://linkedin.com/in/eddiejaoude 69 | 70 | GitHub Community Organization link: https://github.com/EddieHubCommunity 71 | 72 | ## Meet our Community 73 | 74 | Join the Conversation at Discord: http://discord.eddiehub.org/ 75 | -------------------------------------------------------------------------------- /docs/youtube/reviews.md: -------------------------------------------------------------------------------- 1 | # YouTube Live Stream Review Template 2 | 3 | You have submitted your open source projects, let's go through them together on a live stream!! If you have not submitted your open source project yet, you can create an issue here https://github.com/EddieHubCommunity/support/issues?q=is%3Aissue+is%3Aopen+label%3A%22live+stream+review%22 4 | 5 | I now have a 2nd YouTube channel for short video clips of 60s or less, subscribe... 6 | https://youtube.com/eddiejaoudetv 7 | 8 | JOIN our inclusive open source community now for FREE... https://www.eddiehub.org, also checkout my website and sign up to our community NEWSLETTER... https://www.eddiejaoude.io for my live stream + video schedule and community calls 9 | 10 | Reviewing your Open Source projects #OpenSource #GitHub #DevRel 11 | 12 | ## SERVICES I USE AND RECOMMEND 13 | 14 | Some of these might be affiliate links, no extra cost you to, but I get a little $ if you sign up, plus you might get a discount too 15 | 16 | - Live streaming with Streamyard http://links.eddiejaoude.io/t/pYlzGjcta1a4 17 | - Cloud hosting with Digital Ocean, you will get $100 FREE credit http://links.eddiejaoude.io/t/EAaCRWhsnZlF 18 | - Membership, Newsletters, CRM all in one with Kartra http://links.eddiejaoude.io/t/pQ5W3FRLk8Cp 19 | - Awesome backup platform, BackBlaze http://links.eddiejaoude.io/t/4rqTZjLbwmCp 20 | - Descript for video editing, audiograms and transcription http://links.eddiejaoude.io/t/RlpGwZtj0KCp 21 | 22 | ## COMMUNITY SPONSORS 23 | 24 | A BIG thank you to my GitHub Sponsors: 25 | *** 26 | Stephen Mount http://github.com/stemount 27 | DailyDotDev https://github.com/dailydotdev 28 | *** 29 | 30 | - Nicholas Carrigan https://github.com/nhcarrigan 31 | - Santosh Yadav https://github.com/santoshyadavdev 32 | - Andrew Cunliffe https://github.com/andrew-cunliffe 33 | - Alexander Stoichkov https://github.com/SashoStoichkov 34 | - Allan Regush https://github.com/AllanRegush 35 | - CORE Multi-Chain Framework https://github.com/CORE-Blockchain 36 | 37 | FIND ME ON OTHER SOCIAL PLATFORMS 38 | 39 | Don’t forget to support my channel by subscribing below, it’s free, and also share with your friends. Subscribe now! 40 | https://www.youtube.com/eddiejaoude?sub_confirmation=1 41 | 42 | Follow on other socials for behind the scenes footage and join the Discord server to continue the conversation. 43 | 44 | https://www.eddiejaoude.io/ 45 | https://github.com/eddiejaoude 46 | https://youtube.com/eddiejaoude 47 | https://twitter.com/eddiejaoude 48 | https://instagram.com/eddiejaoude 49 | https://linkedin.com/in/eddiejaoude 50 | http://discord.eddiehub.org/ 51 | https://github.com/EddieHubCommunity 52 | -------------------------------------------------------------------------------- /package.json: -------------------------------------------------------------------------------- 1 | { 2 | "name": "eddiehub-support", 3 | "version": "1.0.0", 4 | "description": "A Docsify site providing various information relevant to our community.", 5 | "main": "null", 6 | "scripts": { 7 | "lint": "markdownlint ./docs/**/*.md", 8 | "start": "docsify serve ./docs -o --port 3200" 9 | }, 10 | "repository": { 11 | "type": "git", 12 | "url": "git+https://github.com/nhcarrigan/support.git" 13 | }, 14 | "keywords": [ 15 | "docsify", 16 | "support", 17 | "markdown" 18 | ], 19 | "engines": { 20 | "node": "^16.10.0", 21 | "npm": "^8.0.0" 22 | }, 23 | "author": "", 24 | "license": "MIT", 25 | "bugs": { 26 | "url": "https://github.com/EddieHubCommunity/support/issues" 27 | }, 28 | "homepage": "https://github.com/EddieHubCommunity/support#readme", 29 | "dependencies": { 30 | "docsify-cli": "^4.4.3" 31 | }, 32 | "devDependencies": { 33 | "markdownlint": "^0.24.0", 34 | "markdownlint-cli": "^0.30.0" 35 | } 36 | } 37 | --------------------------------------------------------------------------------