├── .github ├── FUNDING.yml ├── ISSUE_TEMPLATE │ ├── bug.md │ ├── ideas.md │ └── open-source-questions.md ├── pull_request_template.md └── workflows │ ├── community.yml │ └── stale.yml ├── CODE_OF_CONDUCT.md ├── CONTRIBUTING.md ├── LICENSE ├── Learn-Git-And-GitHub.md ├── My-PR-Contribution-Practice.md ├── README.md └── chryz-hub-resources ├── chryz-hub-docs ├── access-open-source-projects.md ├── anatomy-of-open-source-communities.md ├── git-cmd.md ├── git.md ├── membership-visibility.md └── starting-open-source.md └── chryz-hub-tut-pics ├── membvispics ├── membvis2.jpg ├── membvs1jpg.jpg ├── membvs3.jpg └── membvs4.jpg └── pr-tut-pics ├── fork1.jpg ├── pr-1-4.jpg ├── pr-2-5.jpg ├── pr-3-6.jpg ├── work2.jpg └── worksave3jpg.jpg /.github/FUNDING.yml: -------------------------------------------------------------------------------- 1 | # These are supported funding model platforms 2 | 3 | custom: ["https://paystack.com/pay/chryzhub"] 4 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/bug.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Bug 3 | about: Create a bug-report to help us address errors in the repo. 4 | title: '' 5 | labels: bug 6 | assignees: '' 7 | 8 | --- 9 | 10 | **Description** 11 | 12 | 13 | 14 | **Stack** 15 | 16 | Project stack or language (eg. Frontend): 17 | 18 | **Working Environment** 19 | 20 | Operating System (eg Linux): 21 | 22 | Browser (eg. Chrome): 23 | 24 | Device (eg. Laptop or Phone): 25 | 26 | **Screenshots** 27 | 28 | Please add a screenshot if applicable 29 | 30 | [Optional] **Additional Context** 31 | 32 | Add any other context about the problem here. 33 | 34 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/ideas.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Ideas 3 | about: Bringing up ideas for the smooth running of the community 4 | title: 'I have an idea' 5 | labels: 'ideas' 6 | assignees: 'chryzcodez' 7 | 8 | --- 9 | 10 | 11 | **Description** 12 | 13 | A brief description of the ideas: 14 | 15 | **Goals** 16 | 17 | The aim and objectives of the ideas: 18 | 19 | 20 | 21 | 22 | 23 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/open-source-questions.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Open Source Question 3 | about: I am stuck please can someone help 4 | title: '' 5 | labels: question 6 | assignees: '' 7 | 8 | --- 9 | 10 | **Description** 11 | 12 | A brief description of the question , also include what you tried and what didn't work: 13 | 14 | **Screenshots** 15 | 16 | Please add a screenshot if applicable 17 | 18 | [Optional] **Additional Context** 19 | 20 | Add any other context about the problem here. 21 | 22 | 23 | 24 | 25 | -------------------------------------------------------------------------------- /.github/pull_request_template.md: -------------------------------------------------------------------------------- 1 | #ISSUE-NO 2 | 3 | #### What does this PR do? 4 | 5 | #### Description of Task to be completed? 6 | 7 | #### How can this be manually tested? 8 | 9 | #### Any background context you want to provide? 10 | 11 | #### What is the relevant issue link? 12 | 13 | #### Screenshots (if appropriate) 14 | 15 | #### Questions: 16 | 17 | 18 | -------------------------------------------------------------------------------- /.github/workflows/community.yml: -------------------------------------------------------------------------------- 1 | on: 2 | issues: 3 | types: [opened] 4 | pull_request_target: 5 | types: [opened] 6 | 7 | jobs: 8 | welcome: 9 | runs-on: ubuntu-latest 10 | steps: 11 | - uses: actions/first-interaction@v1 12 | with: 13 | repo-token: ${{ secrets.GITHUB_TOKEN }} 14 | issue-message: '

It''s great having you contribute to this community

Thank you for raising an Issue!
Welcome to Chryz-Hub

If you are willing to join the community, connect via the Chryz-Hub Connect Website
You can make a pratice pull request and also add your name been a member of the community ~~ here.

' 15 | pr-message: '

It''s great having you contribute to this community

Thank you for creating a Pull Request!
Welcome to Chryz-Hub

If you are willing to join the community, connect via Chryz-Hub Connect Website
You can make a pratice pull request and also add your name been a member of the community ~~ here.

' 16 | -------------------------------------------------------------------------------- /.github/workflows/stale.yml: -------------------------------------------------------------------------------- 1 | name: 'Close stale issues and PRs' 2 | on: 3 | schedule: 4 | - cron: '30 1 * * *' 5 | 6 | jobs: 7 | stale: 8 | runs-on: ubuntu-latest 9 | steps: 10 | - uses: actions/stale@v3 11 | with: 12 | repo-token: ${{ secrets.GITHUB_TOKEN }} 13 | stale-issue-label: 'stale' 14 | stale-pr-label: 'stale' 15 | stale-issue-message: 'This issue is stale because it has been open 20 days with no activity. Remove stale label or comment or this will be closed in 10 days.' 16 | stale-pr-message: 'This PR is stale because it has been open 20 days with no activity. Remove stale label or comment or this will be closed in 20 days.' 17 | close-issue-message: 'This issue was closed because it has been stalled for 15 days with no activity.' 18 | close-pr-message: 'This PR was closed because it has been stalled for 15 days with no activity.' 19 | days-before-issue-stale: 20 20 | days-before-pr-stale: 20 21 | days-before-issue-close: 15 22 | days-before-pr-close: 15 23 | -------------------------------------------------------------------------------- /CODE_OF_CONDUCT.md: -------------------------------------------------------------------------------- 1 | # Contributor Covenant Code of Conduct 2 | 3 | ## Our Pledge 4 | 5 | In the interest of fostering an open and welcoming environment, we as 6 | contributors and maintainers pledge to making participation in our project and 7 | our community a harassment-free experience for everyone, regardless of age, body 8 | size, disability, ethnicity, sex characteristics, gender identity and expression, 9 | level of experience, education, socio-economic status, nationality, personal 10 | appearance, race, religion, or sexual identity and orientation. 11 | 12 | ## Our Standards 13 | 14 | Examples of behavior that contributes to creating a positive environment 15 | include: 16 | 17 | * Using welcoming and inclusive language 18 | * Being respectful of differing viewpoints and experiences 19 | * Gracefully accepting constructive criticism 20 | * Focusing on what is best for the community 21 | * Showing empathy towards other community members 22 | 23 | Examples of unacceptable behavior by participants include: 24 | 25 | * The use of sexualized language or imagery and unwelcome sexual attention or 26 | advances 27 | * Trolling, insulting/derogatory comments, and personal or political attacks 28 | * Public or private harassment 29 | * Publishing other's private information, such as a physical or electronic 30 | address, without explicit permission 31 | * Other conduct which could reasonably be considered inappropriate in a 32 | professional setting 33 | 34 | ## Our Responsibilities 35 | 36 | Project maintainers are responsible for clarifying the standards of acceptable 37 | behavior and are expected to take appropriate and fair corrective action in 38 | response to any instances of unacceptable behavior. 39 | 40 | Project maintainers have the right and responsibility to remove, edit, or 41 | reject comments, commits, code, wiki edits, issues, and other contributions 42 | that are not aligned to this Code of Conduct, or to ban temporarily or 43 | permanently any contributor for other behaviors that they deem inappropriate, 44 | threatening, offensive, or harmful. 45 | 46 | ## Scope 47 | 48 | This Code of Conduct applies both within project spaces and in public spaces 49 | when an individual is representing the project or its community. Examples of 50 | representing a project or community include using an official project e-mail 51 | address, posting via an official social media account, or acting as an appointed 52 | representative at an online or offline event. Representation of a project may be 53 | further defined and clarified by project maintainers. 54 | 55 | ## Enforcement 56 | 57 | Instances of abusive, harassing, or otherwise unacceptable behavior may be 58 | reported by contacting the project team at chryzhub@gmail.com. All 59 | complaints will be reviewed and investigated and will result in a response that 60 | is deemed necessary and appropriate to the circumstances. The project team is 61 | obligated to maintain confidentiality with regard to the reporter of an incident. 62 | Further details of specific enforcement policies may be posted separately. 63 | 64 | Project maintainers who do not follow or enforce the Code of Conduct in good 65 | faith may face temporary or permanent repercussions as determined by other 66 | members of the project's leadership. 67 | 68 | ## Attribution 69 | 70 | This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, 71 | available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html 72 | 73 | [homepage]: https://www.contributor-covenant.org 74 | 75 | For answers to common questions about this code of conduct, see 76 | https://www.contributor-covenant.org/faq 77 | -------------------------------------------------------------------------------- /CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | # Contributing 2 | 3 | When contributing to this repository, please first discuss the change you wish to make via issue, 4 | email, or any other method with the owners of this repository before making a change. 5 | 6 | Please note we have a [CODE of CONDUCT](https://github.com/chryz-hub/opensource-4-everyone/blob/master/CODE_OF_CONDUCT.md), please follow it in all your interactions with the project. 7 | 8 | 9 | ## Pull Request Process 10 | 11 | 1. Ensure any install or build dependencies are removed before the end of the layer when doing a 12 | build. 13 | 2. Update the README.md with details of changes to the interface, this includes new environment 14 | variables, exposed ports, useful file locations and container parameters. 15 | 3. Increase the version numbers in any examples files and the README.md to the new version that this 16 | Pull Request would represent. The versioning scheme we use is [SemVer](http://semver.org/). 17 | 4. You may merge the Pull Request in once you have the sign-off of two other developers, or if you 18 | do not have permission to do that, you may request the second reviewer to merge it for you. 19 | 20 | ## Commit Message Guidelines 😎 21 | 22 | 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. 23 | 24 | **Examples**: 25 | 26 | 27 | ``` 28 | docs(changelog): update changelog to beta.5 29 | docs: add API documentation to the bot 30 | test(server): add cache tests to the movie resource 31 | fix(web): add validation to phone input field 32 | fix(web): remove avatar image from being required in form 33 | fix(release): need to depend on latest rxjs and zone.js 34 | ``` 35 | 36 | ### Type 37 | 38 | Must be one of the following: 39 | 40 | - **build**: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm). 41 | - **ci**: Changes to our CI configuration files and scripts (example scopes: Circle, BrowserStack, SauceLabs) 42 | - **docs**: Documentation only changes 43 | - **feat**: A new feature 44 | - **fix**: A bug fix 45 | - **perf**: A code change that improves performance 46 | - **refactor**: A code change that neither fixes a bug nor adds a feature 47 | - **style**: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc) 48 | - **test**: Adding missing tests or correcting existing tests 49 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | MIT License 2 | 3 | Copyright (c) 2021 Chryz-Hub 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 | -------------------------------------------------------------------------------- /Learn-Git-And-GitHub.md: -------------------------------------------------------------------------------- 1 | # Git/GitHub Resources 2 | 3 | This file is allocated towards helping you understand the basics of Git and GitHub and how to get started. 4 | 5 | ## Index 6 | 7 | * [Git/GitHub Blogs](#gitgithub-blogs) - Blogs explaining git/github fundamentals and concepts. 8 | * [Git/GitHub Courses/Videos](#gitgithub-coursesvideos) - Videos explaining how to use git/github. 9 | * [Git/GitHub Repositories](#gitgithub-repositories) - Repositories to learn git and github 10 | 11 | # Git/GitHub Docs/Blogs 12 | 13 | - [GitHub Guides](https://guides.github.com/activities/hello-world/) 14 | - [How To Use GitHub – Developers Collaboration Using GitHub](https://www.edureka.co/blog/how-to-use-github/) 15 | - [The beginner’s guide to Git & GitHub](https://www.freecodecamp.org/news/the-beginners-guide-to-git-github/) 16 | - [How To Contribute to Open Source: Getting Started with Git](https://www.digitalocean.com/community/tutorials/how-to-contribute-to-open-source-getting-started-with-git) 17 | - [How Git Branches Work](https://www.freecodecamp.org/news/how-git-branches-work/) 18 | - [What is Commit Signing in Git?](https://www.freecodecamp.org/news/what-is-commit-signing-in-git/) 19 | - [How to Get Started with Version Control Using Git](https://www.freecodecamp.org/news/get-started-with-version-control-and-git/) 20 | - [How To Use Git: A Reference Guide](https://www.digitalocean.com/community/cheatsheets/how-to-use-git-a-reference-guide) 21 | - [How To Use Git Effectively](https://www.digitalocean.com/community/tutorials/how-to-use-git-effectively) 22 | - [How To Use Git Branches](https://www.digitalocean.com/community/tutorials/how-to-use-git-branches) 23 | - [How to Write a Git Commit Message](https://chris.beams.io/posts/git-commit/) 24 | - [How To Use Git: A Reference Guide](https://www.digitalocean.com/community/cheatsheets/how-to-use-git-a-reference-guide) 25 | - [Know how Git works: Behind the Scenes!](https://sohamsshah.hashnode.dev/know-how-git-works-behind-the-scenes-aa40567082ba) 26 | - [5 Git Tips To Level Up Your Workflow](https://ygnys.hashnode.dev/5-git-tips-to-level-up-your-workflow) 27 | - [Everything you need to know to get started with Git and GitHub on a Windows machine](https://chris.beams.io/posts/git-commit/) 28 | - [How to Write a Git Commit Message](https://mihaiviisan.hashnode.dev/everything-you-need-to-know-to-get-started-with-git-and-github-on-a-windows-machine) 29 | - [Git for beginners](https://sudoc.hashnode.dev/series/git-for-beginners) 30 | - [How to Connect GitHub to your GitBash in 5 simple steps](https://unclebigbay.com/how-to-connect-github-to-your-gitbash-in-5-simple-steps) 31 | - [Git & Github: All you need to know](https://nehasoni.hashnode.dev/git-and-github-all-you-need-to-know) 32 | - [How to Use Branches in Git – the Ultimate Cheatsheet](https://www.freecodecamp.org/news/how-to-use-branches-in-git/) 33 | - [Git Checkout Remote Branch Tutorial](https://www.freecodecamp.org/news/git-checkout-remote-branch-tutorial/) 34 | - [A Really Useful Git Command For Quickly Searching Text](https://blog.yogeshchavan.dev/a-really-useful-git-command-for-quickly-searching-text) 35 | - [Git Push to Remote Branch – How to Push a Local Branch to Origin](https://www.freecodecamp.org/news/git-push-to-remote-branch-how-to-push-a-local-branch-to-origin/) 36 | - [Git Switch Branch – How to Change the Branch in Git](https://www.freecodecamp.org/news/git-switch-branch/) 37 | - [How to Use Git and Git Workflows – a Practical Guide](https://www.freecodecamp.org/news/what-is-git-learn-git-version-control/) 38 | - [What is Git? A Beginner's Guide to Git Version Control](https://www.freecodecamp.org/news/how-git-branches-work/) 39 | - [How To Delete All Local Git Branches In One Go](https://catalins.tech/how-to-delete-all-local-git-branches-in-one-go) 40 | - [How To Delete a Git Branch Locally and Remotely](https://hashnode.com/post/how-to-delete-a-git-branch-locally-and-remotely-cknk32nc2004qwes12ck4hn3m) 41 | - [Renaming Your GitHub Projects](https://blog.benhammond.tech/renaming-your-github-projects) 42 | - [A Beginner's Guide to Git and Github](https://efeakhigbe.hashnode.dev/a-beginners-guide-to-git-and-github) 43 | - [Introduction to Git In 16 Minutes](https://vickyikechukwu.hashnode.dev/introduction-to-git-in-16-minutes) 44 | - [How to Create GitHub Draft Pull Requests](https://blog.idrisolubisi.com/how-to-create-github-draft-pull-requests) 45 | - [Start verifying your commits on GitHub in ~5 minutes](https://ozzie.sh/start-verifying-your-commits-on-github-in-5-minutes) 46 | - [List of all Git Commands](https://blog.vimalverma.in/list-of-all-git-commands) 47 | - [Git all-in-one cheat sheet: A collection of the most useful git commands](https://blog.learncodeonline.in/git-all-in-one-cheat-sheet-a-collection-of-the-most-useful-git-commands) 48 | - [GitHub - A complete guide](https://devhankering.hashnode.dev/github-a-complete-guide) 49 | - [A Git Cheatsheet Of Commands Every Developer Should Use](https://ravimengar.hashnode.dev/a-git-cheatsheet-of-commands-every-developer-should-use) 50 | - [An Intro to Git and GitHub for Beginners (Tutorial)](https://product.hubspot.com/blog/git-and-github-tutorial-for-beginners) 51 | - [Git and GitHub SSH Configuration](https://chrisdevcode.hashnode.dev/git-and-github-ssh-configuration) 52 | - [Getting Started with GitHub CLI](https://onyxcode.net/gh-cli-getting-started) 53 | - [How to use Git and GitHub inside of VS Code Editor](https://blog.thefierycoder.tech/how-to-use-git-and-github-inside-of-vs-code-editor) 54 | - [Two Git commands you probably missed in your daily routine](https://thelinuxli.ch/two-git-commands-you-probably-missed-in-your-daily-routine) 55 | - [How to setup GitHub Actions on your Github repository](https://blog.bhanuteja.dev/30-git-commands-that-i-frequently-use) 56 | - [The most basic and essential GIT commands walkthrough](https://bearcub3.hashnode.dev/the-most-basic-and-essential-git-commands-walkthrough-ckgmw77b3012po9s188vag2ig) 57 | - [Don't overcomplicate git](https://h.daily-dev-tips.com/dont-overcomplicate-git) 58 | - [Learn the Basics of Git in Under 10 Minutes](https://nand.blog/git101) 59 | - [The Ultimate Guide to Git Commands](https://ankits.hashnode.dev/the-ultimate-guide-to-git-commands) 60 | - [13 Git Commands Every Developer Should Know](https://svikashk.hashnode.dev/13-git-commands-every-developer-should-know-ckftd1wrm03wtv6s1bqmrgul6) 61 | - [GIT INIT (Part-1)](https://apoorvtyagi.tech/git-init-part-1) 62 | - [GIT INIT (Part-2)](https://apoorvtyagi.tech/git-init-part-2) 63 | - [GitHub CLI 1.0: All you need to know](https://ayushirawat.com/github-cli-10-all-you-need-to-know) 64 | - [Introduction to Git-Adding an SSH Key](https://laasyasettyblog.hashnode.dev/introduction-to-git-adding-an-ssh-key) 65 | - [Understanding Git Terminologies : The Fun Way](https://hafsah.hashnode.dev/understanding-git-terminologies-the-fun-way-ckdet27bd003c42s13lsm5ry5) 66 | - [Baby Steps to Git and Version Control - Series 1](https://amarachiazubuike.com/baby-steps-to-git-and-version-control-series-1-ck36ciz5200eib1s1l5rscbdr) 67 | - [How to Fix Git Always Asking for User Credentials](https://blog.bolajiayodeji.com/how-to-fix-git-always-asking-for-user-credentials) 68 | - [How to Fork a Repo on GitHub using your Mobile Device](https://sudoc.hashnode.dev/series/git-for-beginners) 69 | - [Git First Time Setup](https://blog.bolajiayodeji.com/git-first-time-setup) 70 | - [Git Cheat Sheet for Beginners and Intermediates](https://blog.bolajiayodeji.com/git-cheat-sheet-for-beginners-and-intermediates) 71 | - [Basics of Git](https://adarsh-thakur.hashnode.dev/series/basics-of-git) 72 | 73 | 74 | # Git/GitHub Courses/Videos 75 | - [Git In-depth](https://frontendmasters.com/courses/git-in-depth/) 76 | - [Introduction to Git and GitHub - Offered By Google](https://www.coursera.org/learn/introduction-git-github?specialization=google-it-automation&utm_source=gg&utm_medium=sem&utm_campaign=11-GoogleITwithPython-ROW&utm_content=11-GoogleITwithPython-ROW&campaignid=9733806670&adgroupid=119184274733&device=c&keyword=&matchtype=b&network=g&devicemodel=&adpostion=&creativeid=507191775308&hide_mobile_promo&gclid=CjwKCAjwxo6IBhBKEiwAXSYBs8cqMR-9WYlilq7CrcFTkE7wQT1K7qv1XDpTa5HtjEJckeoyiU6cpRoCyCgQAvD_BwE) 77 | - [Version Control with Git](https://www.coursera.org/learn/version-control-with-git) 78 | - [Git for Developers Using Github](https://www.coursera.org/projects/git-for-developers-using-github) 79 | - [Manage Your Versions with Git (Part I)](https://www.coursera.org/projects/git-1) 80 | - [Manage Your Versions with Git (Part II)](https://www.coursera.org/projects/git-2) 81 | - [Learn Gitpro-logo- Codecademy](https://www.codecademy.com/learn/learn-git) 82 | - [Version Control with Git](https://www.udacity.com/course/version-control-with-git--ud123) 83 | - [Git: Become an Expert in Git & GitHub in 4 Hours](https://www.udemy.com/course/git-expert-4-hours/) 84 | - [Git Essentials: Mini Course](https://www.udemy.com/course/git-essentials-mini-course/) 85 | - [How Git Works- Plurasight](https://www.pluralsight.com/courses/how-git-works) 86 | - [Introduction to GitHub- The GitHub Training Team](https://lab.github.com/githubtraining/introduction-to-github) 87 | - [Git and GitHub for Beginners - Crash Course](https://www.youtube.com/watch?v=RGOj5yH7evk&t=934s) 88 | - [How to use GitHub | What is GitHub | Git and GitHub Tutorial | Edureka](https://www.youtube.com/watch?v=PQsJR8ci3J0) 89 | - [Git & GitHub Tutorial for Beginners](https://www.youtube.com/watch?v=3RjQznt-8kE&list=PL4cUxeGkcC9goXbgTDQ0n_4TBzOO0ocPR) 90 | - [Github Tutorial For Beginners - Github Basics for Mac or Windows & Source Control Basics](https://www.youtube.com/watch?v=0fKg7e37bQE) 91 | - [Git and GitHub Tutorial For Beginners | Full Course](https://www.youtube.com/watch?v=3fUbBnN_H2c) 92 | - [Git Tutorial for Beginners: Learn Git in 1 Hour](https://www.youtube.com/watch?v=8JJ101D3knE) 93 | - [Git Tutorial - Telusko](https://www.youtube.com/watch?v=OdbBmvfThJY&list=PLsyeobzWxl7q2eaUkorLZExfd7qko9sZC) 94 | - [Git & GitHub Crash Course For Beginners - Traversy Media](https://www.youtube.com/watch?v=SWYqp7iY_Tc) 95 | - [Git Tutorial for Beginners - Git & GitHub Fundamentals In Depth](https://www.youtube.com/watch?v=DVRQoVRzMIY) 96 | - [Git And GitHub in ~30 Minutes](https://www.youtube.com/watch?v=jG4Vs81kMlc) 97 | - [Git Tutorial | Github Tutorial | Git Tutorial for Beginners | Intellipaat](https://www.youtube.com/watch?v=dnGeRjP8oxw) 98 | - [GitHub Basics Tutorial - How to Use GitHub](https://www.youtube.com/watch?v=x0EYpi38Yp4) 99 | - [Git Tutorial for Beginners: Command-Line Fundamentals](https://www.youtube.com/watch?v=HVsySz-h9r4) 100 | - [Git and GitHub Crash Course By Google Coursera](https://www.youtube.com/watch?v=PtBr0fpKyFg) 101 | - [Git And GitHub Full Course In 3 Hours | Git And GitHub Tutorial For Beginners ](https://www.youtube.com/watch?v=liwv7Hi68aI) 102 | - [Git Tutorial For Dummies](https://www.youtube.com/watch?v=mJ-qvsxPHpY) 103 | - [Git Tutorial for Beginners - The Basics](https://www.youtube.com/watch?v=ly4niPr9vUo) 104 | - [Git Tutorial for Beginners](https://www.youtube.com/watch?v=XF99kTmS2gg) 105 | - [Git & Github Tutorial for Absolute Beginners](https://www.youtube.com/watch?v=iCKAWxfVWUY) 106 | - [Git Tutorial For Beginners - Kudvenkat](https://www.youtube.com/watch?v=WEmvT2YFlQw&list=PL6n9fhu94yhVwbuqXKuPzchWNjZ8GVcJa) 107 | - [Git and GitHub Beginner Tutorials](https://www.youtube.com/watch?v=-U-eUHI6euM&list=PLhW3qG5bs-L8OlICbNX9u4MZ3rAt5c5GG) 108 | - [Git and GitHub Tutorials](https://www.youtube.com/watch?v=r50BKIFGCI0&list=PLB5jA40tNf3v1wdyYfxQXgdjPgQvP7Xzg) 109 | - [Git & GitHub Tutorials](https://www.youtube.com/watch?v=_bkT85B6n1U&list=PLzS3AYzXBoj8mX3WbzQDghYytnx2JqBrU) 110 | 111 | # Git/GitHub Repositories 112 | 113 | - [GitHub Actions Starter Pack](https://github.com/jasonbarry/github-actions-starter-pack) - Sample code project for automating various tasks via GitHub Actions. -------------------------------------------------------------------------------- /My-PR-Contribution-Practice.md: -------------------------------------------------------------------------------- 1 | # My-PR-Contribution-Practice 2 | 3 | [**➡️Short and Concise Pull Request Tutorial🟩**](https://github.com/chryz-hub/opensource-4-everyone#simple-guide-to-making-a-pull-request-or-contribution) 4 | 5 | ## This space is created for you to make your first pull request/ contribution as a firstimer in open source, also this might not be your first time but involve yourself in this, why? 6 | 7 | - To get an addtional 🟩 to your GitHub profile 8 | - To add to your pull request count 9 | - To add to your contributions count 10 | - To make connections, how? 11 | In this Pull Request/ contribution practice, these can be included: 12 | - Your name 13 | - Your GitHUb profile link 14 | - What you do 15 | 16 | By these data provided, connections can be made! 17 | 18 | - For example , 19 | 20 | `- [Full Name](https://github.com/your-username)` 21 | 22 | `

Bio:_________________________________________` 23 | 24 | On a new line in alphabetical order, add your name, bio and the link to your Github profile 25 | 26 | --- 27 | 28 | ### START CONTRIBUTING BY ADDING YOUR DATA 29 | 30 | --- 31 | 32 | - [Ademosu Adeola](https://github.com/Adecodess) 33 | Bio: Frontend Developer,proficient in javascript, reactjs, html, css 34 | 35 | - [Alaba Olanrewaju](https://github.com/chryzcodez) 36 | Bio: A developer, technical writer/ blogger, an open-source personnel and an aspiring data scientist. 37 | 38 | - [Amjad Noor](https://github.com/AmjadNoor) 39 | Bio: I'm a front-end developer. 40 | 41 | - [Anshul Mehta](https://github.com/Anshul7sp1) 42 | Bio: CS undergrad. Interested in contributing to opensource 43 | 44 | - [Challenge Handler](https://github.com/challengehandler) 45 | Bio: A full-stack web developer. Always be anonymous as a contributor. 46 | 47 | - [Damilare Oyedeji](https://github.com/fuglydami) 48 | Bio: I'm a frontend developer who's also passionate about backend technologies 49 | 50 | 51 | - [Festus Michael](https://github.com/MichaelFestus) 52 | Bio: Self taught Fron-End developer, Aspiring reactjs developer 53 | 54 | - [Franklin Ohaegbulam](https://github.com/frankiefab100) 55 |

Bio: A visual designer and Frontend/UI Developer.

56 | 57 | - [FREDVUNI](https://github.com/FREDVUNI) 58 |

Bio: Software Developer | Open source enthusiast | DevOps newbie | Actively learning and collaborating with fellow developers

59 | 60 | - [Hemant](https://github.com/hemantwasthere) 61 | Bio: Frontend Dev || Open Source Enthusiast 62 | 63 | - [Ibrahim Ayodeji](https://github.com/hackEibrahim) 64 | Bio: aspiring full stack developer | practicing HTML and CSS | learning JavaScript | open source contributor 65 | 66 | - [JayantGoel001](https://github.com/JayantGoel001) 67 | 68 | - [Jyotsna Doonga](https://github.com/jyotsnad246) 69 | Bio: Data Analytics, Frontend Development 70 | 71 | - [Kesavan](https://github.com/kesavan-hex) 72 | 73 | - [Mrinaal Arora](https://github.com/aroramrinaal) 74 | Bio: Computer Science Undergrad and Open Source Contributor. 75 | 76 | - [Mubeen Ahmad](https://github.com/MubeenAhmad571) 77 | 78 | - [Naman Garg](https://github.com/naman-ng) 79 | Bio: I'm a full stack developer and web3 enthusiast 80 | - [Naman Gupta](https://github.com/namangupta1399) 81 | Bio: Computer Science Undergraduate, Aspiring Web Developer. 82 | 83 | - [Poonam Rajput](https://github.com/Poonam-raj) 84 | Bio: Frontend Developer-in-training primarily working on Javascript 85 | 86 | - [Rohit Tewari](https://github.com/rtewari056) 87 | Bio: MERN Stack Developer and Competitive Coder 88 | 89 | - [Sachin Mauyra](https://github.com/slayer321) 90 | Bio: Passionate about cybersecurity and Open source 91 | 92 | - [Sakhil](https://github.com/Sakhil2014) 93 | Bio:A free time Web Dev. Trying hard to become a fullstack 94 | 95 | - [Shittu Titilola](https://github.com/lhorla) 96 | Bio: Frontend developer and writer 97 | 98 | - [Shivam Chandra](https://github.com/magicBeans23) 99 | 100 | - [Tanimowo Emmanuel](https://github.com/mannuel25) 101 | Bio: I'm an aspiring back-end engineer. 102 | 103 | - [Tonatiuh Morales](https://github.com/blackc0mb) 104 | Bio: Developer in my free time and interested in collaborating in a project. 105 | 106 | - [Udeagbala Anthony](https://github.com/izudada) 107 | Bio: A growing python developer, more interested in building web applications with python. 108 | 109 | - [Uzoma Rita](https://github.com/i-am-rita) 110 | Bio: Frontend Developer 111 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Open-Source-4-Everyone 2 | 3 | 4 | 5 | 6 | 7 | 8 | #### This repo is for everything open source! 9 | 10 | **Feel free to create an [issue](https://github.com/chryz-hub/opensource-4-everyone/issues) or make a Pull Request. Please see our [Contributing file](https://github.com/chryz-hub/opensource-4-everyone/blob/master/CONTRIBUTING.md) 11 | first and our [Code of Conduct](https://github.com/chryz-hub/opensource-4-everyone/blob/master/CODE_OF_CONDUCT.md), before making new commits or opening a Pull Request, we appreciate it! 12 | In order for us not to ignore your effort, please check well not to make a duplicate of a Pull Request (contribution)/issue!** 13 | 14 | # Contributing 15 | 16 | If you want to contribute to a project and make it better, your help is very welcome. Contributing is also a great way to learn more about social coding on GitHub, new technologies and their ecosystems and how to make constructive, helpful bug reports, feature requests and the noblest of all contributions: a good, clean Pull Request. To learn how to use Git or GitHub here is a [resource](Learn-Git-And-GitHub.md) allocated for that. 17 | 18 | ### How to make a clean Pull Request 19 | 20 | Look for a project's contribution instructions. If you find any, then let's follow these steps. 21 | 22 | - Create a personal fork of the project on GitHub. 23 | - Clone the fork on your local machine. Your remote repo on GitHub is called `origin`. 24 | - Add the original repository as a remote called `upstream`. 25 | - If you created your fork a while ago be sure to pull upstream changes into your local repository. 26 | - Create a new branch to work on! Branch from `develop` if it exists, else from `master`. 27 | - Implement/ fix your feature, comment your code. 28 | - Follow the code style of the project, including indentation. 29 | - If the project has tests run them! 30 | - Write or adapt tests as needed. 31 | - Add or change the documentation as needed. 32 | - Squash your commits into a single commit with the community [git tips](https://github.com/chryz-hub/opensource-4-everyone/blob/master/chryz-hub-resources/chryz-hub-docs/git.md). Create a new branch if necessary. 33 | - Push your branch to your fork on GitHub, the remote `origin`. 34 | - From your fork open a Pull Request in the correct branch. Target the project's `develop` branch if there is one, else go for `master`! 35 | - If the maintainer requests further changes just push them to your branch. The Pull Request will be updated automatically. 36 | - Once the Pull Request is approved and merged you can pull the changes from `upstream` to your local repo and delete 37 | your extra branch(es). 38 | 39 | And last but not least: Always write your commit messages in the present tense. Your commit message should describe what the commit, when applied, does to the code – not what you did to the code. 40 | 41 | **But wait before you start contibuting, you've got to know us better. This would really aid you to :** 42 | 43 | - Fit more into the community. 44 | - Understand our modes of operation. 45 | - Know the community moderators and members as well. 46 | - Know the goals and aim of the community. 47 | - Including your presence as a member/ contributor, if you wish and many more! 48 | 49 | ## The Pull Request Practice! 50 | 51 | Eager to make your first Pull Request or make out connections with lot of people or fishing out your choice[stack]-anyone, we've got you covered. Make a [Pull Request](https://github.com/chryz-hub/opensource-4-everyone/blob/master/My-PR-Contribution-Practice.md) but before that, check out our short tutorial on how to easily make a contribution 👇 52 | 53 | **Note:** 54 | 55 | - To be a member; Raise an [invitation issue here](https://github.com/chryz-hub/chryz-hub.github.io/issues/new?assignees=&labels=invite+me+to+the+organisation&template=invitation.md&title=Please+invite+me+to+the+GitHub+Community+Organization)! 56 | 57 | ## Simple Guide to Making a Pull Request or Contribution 58 | 59 | ### 1. Fork/ Edit 60 | 61 | What is a fork? 62 | 63 | This is cloning a repository to have a personal version of that same/ main repository. 64 | So, this is advisable to first fork the repository you want to contribute to and then move to check for it in your personal GitHub repositories, there you would find the forked 65 | repository. You can also click the edit(pencil) button, and this automatically forks the repo to your version. Make sure you are in the right repository before forking or editing it, can you see the name of the repository used as a sample! 66 | 67 | 68 | ### 2. Start Making contribution/ changes 69 | 70 | Do you notice any change ~~ the naming of the repository, the first name there is your forked version while the other is that of the real repository. So, I already got my personal version of the repository because I forked or edited it. Then, you can start making your changes and add anything you feel neccesary/ right. 71 | 72 | 73 | ### 3. Commit Changes 74 | 75 | Just like using git, you have to put down a commit message, without putting down any message GitHub defaultly give you a commit message exactly as what I used as my commit message. There is a second space for more description, you can fill this up if you see it as dimmed fit or necessary and be precise. So, I would be committing this on the master(default) of my forked GitHub repository. There would be no much sense in commiting this in a new branch because I run this, there are no other contributors and you are sure on what you want but if it is a GitHub community it is advisable to create a new branch. Then commit changes! 76 | 77 | 78 | ### 4. Create Pull Request 79 | 80 | After the commit, then click the Pull Request tab and make new Pull Request 81 | 82 | 83 | ### 5. Comparing Changes 84 | 85 | This is all about the comparism between your own forked version and the real repository to check if there was a change and if the change is mergeable. You can see the word `comparing across forks` and a transitional line with an arrow in the middle. You must set this well to avoid issue, now we are sending from mine to the main/real repository using the direction of the arrow, then you can make your Pull request. If it is not mergeable, you can still make the Pull Request and resolve it `resolve conflicts`, GitHub would point out the issue which makes it easier for you to resolve. 86 | 87 | 88 | ### 6. Create Pull Request Message 89 | 90 | Just same process as a commit message. Some community have a pull Request template which makes it easier to fill in important and appropriate details concerning a Pull Request, 91 | which is shown on the image. I didn't add any description because there wasn't really a change,the change here was only a space, but yours could be way far than this. So fill 92 | it up with neccessary details and concerning the Pull Request title, do not forget to make it precise. You can see a check button there, clicking it simply means that the Pull Request can be edited by the mainteners of the repository. I really advise you to always check this, although it's automatically checked by github by default, so the choice is left to you. Then click the `create Pull Request` button. 93 | 94 | 95 | 96 | ### Congratulations🎉 You've made your first contribution 97 | 98 | After your Pull Request has been reviewed by the Team of the community and everything there is appropriate. Then, your Pull Request would be merged and this makes your Pull Request a contribution! 99 | 100 | ## Chryz-hub Resources 101 | 102 |
103 | 104 | Docs 105 | 106 | 115 |
116 | 117 |
118 | 119 | YouTube Videos 120 | 121 | 125 |
126 | 127 | #### We hope you found that, useful! 128 | 129 | ## Direct GitHub searches 130 | 131 | Search links that point directly to suitable issues to contribute to on GitHub. 132 | 133 | - [is:issue is:open label:beginner](https://github.com/issues?q=is%3Aissue+is%3Aopen+label%3Abeginner) 134 | - [is:issue is:open label:easy](https://github.com/issues?q=is%3Aissue+is%3Aopen+label%3Aeasy) 135 | - [is:issue is:open label:first-timers-only](https://github.com/issues?q=is%3Aissue+is%3Aopen+label%3Afirst-timers-only) 136 | - [is:issue is:open label:good-first-bug](https://github.com/issues?q=is%3Aissue+is%3Aopen+label%3Agood-first-bug) 137 | - [is:issue is:open label:"good first issue"](https://github.com/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22) 138 | - [is:issue is:open label:starter](https://github.com/issues?q=is%3Aissue+is%3Aopen+label%3Astarter) 139 | - [is:issue is:open label:up-for-grabs](https://github.com/issues?q=is%3Aissue+is%3Aopen+label%3Aup-for-grabs) 140 | 141 | ## Resources 142 | 143 |
Websites
144 |
    145 |
  • CodeTriage - CodeTriage helps by picking a handful of open issues and delivering them directly to your inbox. After you sign up for CodeTriage, you pick the repos you want to help with, and we periodically send you issues.
    • 146 |
  • goodfirstissue.dev - Curates easy pickings from popular open-source projects, and helps you make your first contribution to open-source.
    • 147 |
  • goodfirstissue.com - A site made for new contributors to find great Open Source projects, discover issues and repositories with good first issue and help wanted labels.
    • 148 |
  • Up For Grabs - This is a list of projects which have curated tasks specifically for new contributors. These are a great way to get started with a project, or to help share the load of working on open source projects.
    • 149 |
  • First contributions - A hands-on tutorial that walks you through contributions workflow on GitHub. It help beginners to contribute to open source projects.
    • 150 |
  • Contributor Ninja - A platform to find issues in several languages to fix on GitHub.
    • 151 |
  • Gauger - With this site, you can find beginner friendly open source projects to work on.
    • 152 |
  • Open Sauced - Open Sauced provides guidance for new contributors finding their next contribution. Our approach towards onboarding offers a way to track contributions through a GitHub powered dashboard.
    • 153 |
  • 24 Pull Requests - 24 Pull Requests' goal is to encourage contribution to open source projects during December. The site suggests open projects, highlights tickets that are good for new contributors, provides guides for contributing and promotes good contributions submitted each day.
    • 154 |
  • Issue Hub - Contribute to open source by searching issue labels to find the right project for you!
    • 155 |
  • Pull Request Roulette - On this site, there's a list of pull requests submitted for review, belonging to open source projects hosted on GitHub.
    • 156 |
157 |
158 | 159 | 160 |
Repositories
161 | 182 |
183 | 184 | 185 |
Books
186 | 211 |
212 | 213 | 214 |
Paid Open-Source Internship
215 | 221 |
222 | 223 | 224 |
YouTube Channels/Videos
225 | 226 |
Channels
227 | 234 |
235 | 236 |
Videos
237 | 274 |
275 |
276 | 277 |
Open-Source Docs/Blogs
278 | 353 |
354 | 355 | 356 |
Podcasts
357 |
    358 |
  • The ReadME Podcast - On The ReadME Podcast, we take a look behind the scenes of the most impactful open source projects and the developers who make them happen.
    • 359 |
  • Open Source Underdogs - A podcast for entrepreneurs about open-source software. In each episode, we chat with a founder or leader to explore how they are building thriving businesses around open-source software. Our goal is to demystify how entrepreneurs can stay true to their open-source objectives while also building sustainable, profitable businesses that fuel innovation and ensure longevity.
    • 360 |
  • The Open Source Way - This podcast is about the difference, value or drop that open source can be. Each episode we talk with experts about open source related topics and why they do it the open source way.
    • 361 |
  • FINOS Open Source in Finance Podcast - The FINOS Open Source in Finance Podcast celebrates open source projects and interesting topics at the cross section of financial services and open source.
    • 362 |
  • The Craft Of Open Source - This bi-weekly show is focused on the ins and outs of the Open Source Software Community. Join Ben as he speaks with the brightest minds that have brought us some of the most adopted technologies on earth. Each episode is an interview with creators, maintainers, entrepreneurs, and key contributors to the open-source community.
    • 363 |
  • Percona's HOSS Talks FOSS: The Open Source Database Podcast - Percona's head of open source strategy (The HOSS) Matt Yonkovit talks with developers, dba's, and engineers from around the open source community about the latest news and events in the FOSS space.
    • 364 |
  • FLOSS Weekly - FLOSS all about Free Libre Open Source Software with talks with the most interesting and important people in the Open Source and Free Software community.
    • 365 |
  • The Changelog: Software Development, Open Source - Conversations with the hackers, leaders, and innovators of the software world. This is a polyglot podcast. All programming languages, platforms, and communities are welcome. Open source moves fast. Keep up.
    • 366 |
  • LINUX Unplugged - An open show powered by community LINUX Unplugged takes the best attributes of open collaboration and turns it into a weekly show about Linux.
    • 367 |
  • Linux Weekly Daily Wednesday - A weekly dose of all thing Linux and open source with a slice of Pi for good measure.
    • 368 |
  • Open Source – Software Engineering Daily - Open source technology episodes of Software Engineering Daily. At the gym or on your commute, you can listen to long-form interviews about software engineering. After every episode, you should feel like you are 1% better at understanding how the software works.
    • 369 |
  • Reality 2.0 - Join Linux and Open Source advocates, Doc Searls and Katherine Druckman, as they navigate the new digital world, covering topics related to Linux and Open Source, as well as digital privacy, security, and other current issues.
    • 370 |
  • Open Source Voices - Affter years of producing Linux, BSD, and Other Open Source Podcasts, I came to the realization that we almost always focus on technology. It makes sense, we all love tech, that's why we are who we are. But the community we are apart of is full of varied and fascinating people that make that tech. This is my attempt to highlight the people who are helping us dream up and build the future around us.
    • 371 |
  • The Craft Of Open Source - This bi-weekly show is focused on the ins and outs of the Open Source Software Community. Join Ben as he speaks with the brightest minds that have brought us some of the most adopted technologies on earth. Each episode is an interview with creators, maintainers, entrepreneurs, and key contributors to the open-source community.
    • 372 |
  • Open source for business - Your company uses open-source software but needs to better understand how to effectively manage it. In this podcast, Eunice Chendjou and Henry Badgery host interviews with some of the world's top experts that sit at the intersection of business and open source.
    • 373 |
  • Impactful Open Source - We seek out stories of open source successes, moving from beyond source code and into the world at large. We focus on code that didn't just turn into a large enterprise business, but which passed through universities, cities, governments, and the world to make a real difference in people's lives. Our guests are open sorcerers, academics, open-source program officers, and everyone in between.
    • 374 |
  • Free as in Freedom - A bi-weekly discussion of legal, policy, and other issues in the open-source and software freedom community (including occasional interviews) from Brooklyn, New York, USA.
    • 375 |
  • Open Source Creative - A weekly podcast where I ramble about creativity, process, and open-source software. The show features in-depth discussions about the nature of open-source software and how it relates to doing creative work. And interviews!
    • 376 |
  • FLOSS for Science - Interviews with scientists who are using or developing free and libre open-source software.
    • 377 |
  • Humans of Open Source - A podcast where we explore the human side of working on open-source software. We talk to contributors about how, what, and why they contribute in order to uncover the human element behind the open-source communities that power our digital infrastructure.
    • 378 |
  • The Binary Times Audiocast - ogg - Linux and open-source tips, tricks, and discussion. Free software, hardware, and modern culture.
    • 379 |
  • Breaking Into Open Source - Have you ever wondered what would it be to contribute to open-source software? Or is curious about how to get started? Well, wonder no more! In this podcast we let Bob and Josh take us through the tour of the wonderful world of open source, as seen through developers.
    • 380 |
  • Open Source System Podcast - The Open Source System Podcast brings you the latest open source projects and news. We try to focus only on open source software and cover projects that are created in any programming language. If you have a goal to become more involved with open source software then this podcast is for you!
    • 381 |
  • Sustain - Sustain brings together practitioners, sustainers, funders, researchers and maintainers of the open source ecosystem. We have conversations about the health and sustainability of the open source community. We learn about the ins and outs of what ‘open source’ entails in the real world.
    • 382 |
  • Scotland Open Source - Scotland Open Source talks to maintainers, advocates and companies from Scotland’s vibrant open source community.
    • 383 |
  • Creators and Consumers of Open Source - Team Aviyel is sitting together Maintainers on the Journey they took to reach here.
    • 384 |
385 |
386 | 387 | 388 | ## Find us on 389 | 390 |
391 |
392 |
393 |
394 | 395 | -------------------------------------------------------------------------------- /chryz-hub-resources/chryz-hub-docs/access-open-source-projects.md: -------------------------------------------------------------------------------- 1 | # How to look for an open-source project to contribute? 2 | 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? 3 | 4 | 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:. 5 | 6 | 7 | ## Tips 8 | - Look at our projects in the [chryz-hub](https://github.com/chryz-hub) GitHub organization. 9 | - Have a look at your friends and community projects. 10 | - A good place to find projects is Twitter. People share projects on what they are working on, or simply repositories they found interesting. 11 | - Look at the projects/libraries/frameworks you already use, are there improvements you can make, or look at their issues list. 12 | - 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=) 13 | - Take a look at the [Explore](https://github.com/explore) feature on GitHub. You can see the trending repositories or choose by topic (e.g. python) 14 | 15 | -------------------------------------------------------------------------------- /chryz-hub-resources/chryz-hub-docs/anatomy-of-open-source-communities.md: -------------------------------------------------------------------------------- 1 | # Anatomy of an open source project: 2 | 3 | Every open source community is different. 4 | 5 | Spending years on one open source project means you’ve gotten to know _one_ open source project. Move to a different project, and you might find the vocabulary, norms, and communication styles are completely different. 6 | 7 | That said, many open source projects follow a similar organizational structure. Understanding the different community roles and overall process will help you get quickly oriented to any new project. 8 | 9 | A typical open source project has the following types of people: 10 | 11 | **Author**: The person/s or organization that created the project. 12 | 13 | **Owner**: The person/s who has administrative ownership over the organization or repository (not always the same as the original author). 14 | 15 | **Maintainers**: Contributors who are responsible for driving the vision and managing the organizational aspects of the project (may also be authors or owners of the project). 16 | 17 | **Contributors**: Everyone who has contributed something back to the project. 18 | 19 | **Community Members**: People who use the project. They might be active in conversations or express their opinion on the project’s direction. 20 | 21 | Bigger projects may also have subcommittees or working groups focused on different tasks, such as tooling, triage, community moderation, and event organizing. Look on a project’s website for a “team” page, or in the repository for governance documentation, to find this information. **Note: You can checkout our [community team](https://github.com/chryz-hub/chryz-hub.github.io#meet-the-team)** 22 | 23 | 24 | A project also has documentation. These files are usually listed in the top level of a repository. 25 | 26 | **LICENSE**: By definition, every open source project must have an open source license. If the project does not have a license, it is not open source. 27 | 28 | **README**: The README is the instruction manual that welcomes new community members to the project. It explains why the project is useful and how to get started. 29 | 30 | **CONTRIBUTING**: Whereas READMEs help people use the project, contributing docs help people contribute to the project. It explains what types of contributions are needed and how the process works. While not every project has a CONTRIBUTING file, its presence signals that this is a welcoming project to contribute to. 31 | 32 | **CODE_OF_CONDUCT**: The code of conduct sets ground rules for participant’s behavior associated and helps to facilitate a friendly, welcoming environment. While not every project has a CODE_OF_CONDUCT file, its presence signals that this is a welcoming project to contribute to. **Do well to check our [code of conduct](https://github.com/chryz-hub/opensource-4-everyone/blob/master/CODE_OF_CONDUCT.md)** 33 | 34 | **Other documentation**: There might be additional documentation, such as tutorials, walkthroughs, or governance policies, especially on bigger projects. 35 | 36 | Finally, open source projects use the following tools to organize discussion. Reading through the archives will give you a good picture of how the community thinks and works. 37 | 38 | **Issue tracker**: Where people discuss issues related to the project. 39 | 40 | **Pull requests**: Where people discuss and review changes that are in progress. 41 | 42 | **Discussion forums or mailing lists**: Some projects may use these channels for conversational topics (for example, “How do I…“ or “What do you think about…“ instead of bug reports or feature requests). Others use the issue tracker for all conversations. 43 | 44 | **Synchronous chat channel**: Some projects use chat channels (such as Discord or IRC) for casual conversation, collaboration, and quick exchanges. 45 | 46 |
47 |
48 |
49 | 50 | -------------------------------------------------------------------------------- /chryz-hub-resources/chryz-hub-docs/git-cmd.md: -------------------------------------------------------------------------------- 1 | Git Commands 2 | ============ 3 | 4 | 5 | 6 | ### Getting & Creating Projects 7 | 8 | | Command | Description | 9 | | ------- | ----------- | 10 | | `git init` | Initialize a local Git repository | 11 | | `git clone ssh://git@github.com/[username]/[repository-name].git` | Create a local copy of a remote repository | 12 | 13 | ### Basic Snapshotting 14 | 15 | | Command | Description | 16 | | ------- | ----------- | 17 | | `git status` | Check status | 18 | | `git add [file-name.txt]` | Add a file to the staging area | 19 | | `git add -a` | Add all new and changed files to the staging area | 20 | | `git commit -m "[commit message]"` | Commit changes | 21 | | `git rm -r [file-name.txt]` | Remove a file (or folder) | 22 | 23 | ### Branching & Merging 24 | 25 | | Command | Description | 26 | | ------- | ----------- | 27 | | `git branch` | List branches (the asterisk denotes the current branch) | 28 | | `git branch -a` | List all branches (local and remote) | 29 | | `git branch [branch name]` | Create a new branch | 30 | | `git branch -d [branch name]` | Delete a branch | 31 | | `git push origin --delete [branch name]` | Delete a remote branch | 32 | | `git checkout -b [branch name]` | Create a new branch and switch to it | 33 | | `git checkout -b [branch name] origin/[branch name]` | Clone a remote branch and switch to it | 34 | | `git branch -m [old branch name] [new branch name]` | Rename a local branch | 35 | | `git checkout [branch name]` | Switch to a branch | 36 | | `git checkout -` | Switch to the branch last checked out | 37 | | `git checkout -- [file-name.txt]` | Discard changes to a file | 38 | | `git merge [branch name]` | Merge a branch into the active branch | 39 | | `git merge [source branch] [target branch]` | Merge a branch into a target branch | 40 | | `git stash` | Stash changes in a dirty working directory | 41 | | `git stash clear` | Remove all stashed entries | 42 | 43 | ### Sharing & Updating Projects 44 | 45 | | Command | Description | 46 | | ------- | ----------- | 47 | | `git push origin [branch name]` | Push a branch to your remote repository | 48 | | `git push -u origin [branch name]` | Push changes to remote repository (and remember the branch) | 49 | | `git push` | Push changes to remote repository (remembered branch) | 50 | | `git push origin --delete [branch name]` | Delete a remote branch | 51 | | `git pull` | Update local repository to the newest commit | 52 | | `git pull origin [branch name]` | Pull changes from remote repository | 53 | | `git remote add origin ssh://git@github.com/[username]/[repository-name].git` | Add a remote repository | 54 | | `git remote set-url origin ssh://git@github.com/[username]/[repository-name].git` | Set a repository's origin branch to SSH | 55 | 56 | ### Inspection & Comparison 57 | 58 | | Command | Description | 59 | | ------- | ----------- | 60 | | `git log` | View changes | 61 | | `git log --summary` | View changes (detailed) | 62 | | `git log --oneline` | View changes (briefly) | 63 | | `git diff [source branch] [target branch]` | Preview changes before merging | 64 | -------------------------------------------------------------------------------- /chryz-hub-resources/chryz-hub-docs/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 | 19 | ## Rebasing a Fork 20 | 21 | 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 Pull Request back to the source. 22 | 23 | Instead, to keep the commit history clean, you can `rebase` your fork against the source. Here are the steps to do so: 24 | 25 | - Step one: Make sure you are on your primary branch with `git checkout `. Most commonly, this will be `git checkout main`. 26 | - 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 ↓ 27 | - 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. 28 | - 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`. 29 | - Step four: Force your fork repo to match this new state with `git push -f`. 30 | - Step five: Celebrate your success! 31 | 32 | ## Rebasing a PR 33 | 34 | 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 Pull Request against the base branch of the fork and resolve the merge conflicts. 35 | 36 | - Step one: Make sure you are on the branch you used for that pull request with `git checkout `. 37 | - 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 ↓ 38 | - 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. 39 | - 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`.) 40 | - 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. 41 | - 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! 42 | - Step six: As you fix each file, you will need to `git add ` and `git commit` to commit the resolved changes. 43 | - Step seven: Once all conflicts are resolved, `git` will allow you to `git push` those changes. Your Pull Request should automatically update and reflect the new state, with no merge conflicts! 44 | - Step eight: Celebrate your success! Merge conflicts can definitely be tricky! 45 | 46 | ## Squashing Your Commits 47 | 48 | A maintainer might have a contributing requirement that Pull Request's have only one commit, or they might ask you to squash your Pull Request's commits into one. These steps will help you do so! 49 | 50 | - Step one: Make sure you are on the branch you used for that pull request with `git checkout `. 51 | - 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`). 52 | - 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. 53 | - Step four: Force your remote branch to accept this new commit history with `git push -f`. 54 | - Step five: Celebrate your success! 55 | -------------------------------------------------------------------------------- /chryz-hub-resources/chryz-hub-docs/membership-visibility.md: -------------------------------------------------------------------------------- 1 | # Membership Visibilty Tutorial 2 | 3 | This would be a short tutorial on how to make a your membership to a community visible or maybe hidden for a particular reason. I know we would all want 4 | our membership to be visible and that's why this was created. 5 | 6 | ### Initially 7 | 8 | After joining a community as a member, Github automatically makes it hidden(private), making only the members of the same 9 | community to see your membership, not the public at large. So, you need to enable this yourself, for people to discover you! 10 | 11 | This is mine, it is visible to everyone, why? 12 | Because I enabled it myself! 13 | ![chryzcodez](https://github.com/chryz-hub/opensource-4-everyone/blob/master/chryz-hub-resources/chryz-hub-tut-pics/membvispics/membvs1jpg.jpg) 14 | 15 | ### So, let's make yours🚀 16 | 17 | 1. Click the people tab 18 | 19 | You have to be on the community page, where you are a member and click the `people` tab. 20 | ![](https://github.com/chryz-hub/opensource-4-everyone/blob/master/chryz-hub-resources/chryz-hub-tut-pics/membvispics/membvis2.jpg) 21 | 22 | 2. Search and find out your name 23 | 24 | Then you would find a list of the community members, then search out and find your name and we can all see from the picture below, that there is a difference, 25 | only an account is made public and the others private. So you would have to click the `private` button to toggle it `public` 26 | ![](https://github.com/chryz-hub/opensource-4-everyone/blob/master/chryz-hub-resources/chryz-hub-tut-pics/membvispics/membvs3.jpg) 27 | 28 | 3. Changing the visiblity 29 | 30 | After clicking it, something like this, as shown in the image below would show up. Then you would have to pick any one of your choice, either 31 | public or private. 32 | ![](https://github.com/chryz-hub/opensource-4-everyone/blob/master/chryz-hub-resources/chryz-hub-tut-pics/membvispics/membvs4.jpg) 33 | 34 |
I feel this has helped out in making your membership visiblilty either public or private!
35 | -------------------------------------------------------------------------------- /chryz-hub-resources/chryz-hub-docs/starting-open-source.md: -------------------------------------------------------------------------------- 1 | # Getting Started 2 | 3 | Getting started with open-source can be a difficult task, not only because we are being introduced to some new technologies, but also because most of us have never worked in a collaborative environment before. Being able to work in a collaborative environment is one of the most important skills anyone could acquire, not only in the coding and programming area, but in life. 4 | 5 | It may appear a very challenging and overwhelming task at first, but it is, in fact, a fun and rewarding experience. 6 | 7 | # Community Led Collaboration Projects 8 | Providing the opportunity for you to flex your developer muscles, whilst working within a team of developers. Gaining valuable skills, employers are always seeking, such as: 9 | - **Communication and collaboration** - Being able to work in a team and communicating effectively is a very important skill. 10 | - **Github and source control** - In these projects you will have the opportunity to understand why branching is important along with other key github skills. 11 | - **New stacks and technologies** - Each project is likely to use slightly varying stacks, providing the opportunity to jump into something new. 12 | 13 | # How You Benefit 14 | Along with learning new skills, you will also gain experience on projects you can start to list on your Resume/CV. In addition, you will build out your commit history on Github, which employers love! But most importantly, you will learn to work in teams which is one of the most important skills to be a top developer. 15 | 16 | # You have 2 options: Join an existing project or Create a new project: 17 | 18 | ## Option 1: Join a project 19 | Joining a project is pretty simple, checkout the [current projects](https://github.com/zero-to-mastery) and find one you would like to participate in. Check out the project README in its repo as it will have a guide on how to get started! 20 | 21 | **Please note:** Whilst working on any project in the Zero To Mastery community, you must adhere to our code of conduct, which can be found [here](https://github.com/zero-to-mastery/CodeofConduct). 22 | 23 | ## Option 2: Create a project 24 | We are always on the look out for new and exciting project to add to Zero to Mastery for you all to collaborate on! If you think you have a new and exciting project/idea the community would love to get involved in, here is the process for getting it listed: 25 | - Reach out to a member of the Management Team on our Discord server, with a detailed project brief 26 | - Management team will consider if the project is something that would work well with the community 27 | - A Repository will be created and the project will be announced in #current-project channel in our Discord server and featured during an upcoming announcement by Andrei. 28 | - If the project has enough demand, a dedicated channel will be created to accomodate discussions. 29 | 30 | ### **Rules** 31 | In order to ensure that students hard work and time are not exploited, there are a couple of rules that will need to be followed for any project: 32 | - The project repo and discussion channels, will be hosted under the Zero To Mastery Github organization/Discord Server. 33 | - The project must use the [Creative Commons Attribution 4.0 International License](https://creativecommons.org/licenses/by/4.0/). 34 | - The project must contain and adhere to the `code of conduct` guide found [here](https://github.com/zero-to-mastery/CodeofConduct). 35 | 36 | ## Current Projects 37 | You can view all current projects [here](https://github.com/zero-to-mastery) or you can view the specific #current-projects channel in our Discord Community that gives you a little more detail on each project. 38 | 39 | ## What is open source? 40 | 41 | Open source is the original way of creating software – in an open, transparent and collaborative manner. “[What is free software?](https://www.gnu.org/philosophy/free-sw.en.html)" and “[What is open source?](https://opensource.com/resources/what-open-source)" are good overviews of the subject. 42 | 43 | Open source means that you get the final executable for a software project, and also have access to the source code from which it was produced. Having access to the source code means that you can better understand how the program functions and more importantly you can modify it to fix any problems you have with the software or add new features which you desire. 44 | 45 | What might look like a chaotic way of creating software (everybody focusing on their own needs) works surprisingly well: for example the Linux kernel contains more than 4,000 man years worth of effort. 46 | 47 | ## Why would I want to contribute? 48 | 49 | Here, practicing would be our primary objective but there are also many pragmatic reasons for contributing to open source projects: 50 | 51 | **1.** To add a new feature / improvement to a project; or to fix an issue with a project. 52 | 53 | **2.** To practice and learn about software development – contributing to a project is a great way to learn about the more hands on aspects of software development like using debuggers, version control systems, issue trackers, etc. 54 | 55 | **3.** To practice/learn a particular programming language or technology which you are interested in. 56 | 57 | **4.** To build your online presence – highlighting open source contributions relevant to the job makes your resume stand out from the rest. 58 | 59 | ## How can I contribute to projects? 60 | 61 | **1.** **Test :** Start with testing the code for any bugs, if found raise an issue about it. (Always check first if someone has already raised an issue for the same.) 62 | 63 | **2.** **Suggest features:** Look for possible improvements and provide suggestions in the comment section. 64 | 65 | **3.** **Design:** Considering the fact that practice is the main objective, try to make little changes on your forked repository and make a pull-request about it. *Commit often and provide appropriate messages to your commits.* 66 | 67 | **4.** You can also help in providing proper documentation of the various projects. 68 | -------------------------------------------------------------------------------- /chryz-hub-resources/chryz-hub-tut-pics/membvispics/membvis2.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chryz-hub/opensource-4-everyone/3a5087944b18825a91258917bc092abf4e7859ae/chryz-hub-resources/chryz-hub-tut-pics/membvispics/membvis2.jpg -------------------------------------------------------------------------------- /chryz-hub-resources/chryz-hub-tut-pics/membvispics/membvs1jpg.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chryz-hub/opensource-4-everyone/3a5087944b18825a91258917bc092abf4e7859ae/chryz-hub-resources/chryz-hub-tut-pics/membvispics/membvs1jpg.jpg -------------------------------------------------------------------------------- /chryz-hub-resources/chryz-hub-tut-pics/membvispics/membvs3.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chryz-hub/opensource-4-everyone/3a5087944b18825a91258917bc092abf4e7859ae/chryz-hub-resources/chryz-hub-tut-pics/membvispics/membvs3.jpg -------------------------------------------------------------------------------- /chryz-hub-resources/chryz-hub-tut-pics/membvispics/membvs4.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chryz-hub/opensource-4-everyone/3a5087944b18825a91258917bc092abf4e7859ae/chryz-hub-resources/chryz-hub-tut-pics/membvispics/membvs4.jpg -------------------------------------------------------------------------------- /chryz-hub-resources/chryz-hub-tut-pics/pr-tut-pics/fork1.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chryz-hub/opensource-4-everyone/3a5087944b18825a91258917bc092abf4e7859ae/chryz-hub-resources/chryz-hub-tut-pics/pr-tut-pics/fork1.jpg -------------------------------------------------------------------------------- /chryz-hub-resources/chryz-hub-tut-pics/pr-tut-pics/pr-1-4.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chryz-hub/opensource-4-everyone/3a5087944b18825a91258917bc092abf4e7859ae/chryz-hub-resources/chryz-hub-tut-pics/pr-tut-pics/pr-1-4.jpg -------------------------------------------------------------------------------- /chryz-hub-resources/chryz-hub-tut-pics/pr-tut-pics/pr-2-5.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chryz-hub/opensource-4-everyone/3a5087944b18825a91258917bc092abf4e7859ae/chryz-hub-resources/chryz-hub-tut-pics/pr-tut-pics/pr-2-5.jpg -------------------------------------------------------------------------------- /chryz-hub-resources/chryz-hub-tut-pics/pr-tut-pics/pr-3-6.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chryz-hub/opensource-4-everyone/3a5087944b18825a91258917bc092abf4e7859ae/chryz-hub-resources/chryz-hub-tut-pics/pr-tut-pics/pr-3-6.jpg -------------------------------------------------------------------------------- /chryz-hub-resources/chryz-hub-tut-pics/pr-tut-pics/work2.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chryz-hub/opensource-4-everyone/3a5087944b18825a91258917bc092abf4e7859ae/chryz-hub-resources/chryz-hub-tut-pics/pr-tut-pics/work2.jpg -------------------------------------------------------------------------------- /chryz-hub-resources/chryz-hub-tut-pics/pr-tut-pics/worksave3jpg.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/chryz-hub/opensource-4-everyone/3a5087944b18825a91258917bc092abf4e7859ae/chryz-hub-resources/chryz-hub-tut-pics/pr-tut-pics/worksave3jpg.jpg --------------------------------------------------------------------------------