├── resources └── video-content-resources.md ├── LICENSE ├── Resources.md ├── README.md └── CONTRIBUTING.md /resources/video-content-resources.md: -------------------------------------------------------------------------------- 1 | ## Livestreaming Resources 2 | ### Software 3 | - Zoom 4 | - Discord 5 | - VDO.ninja 6 | 7 | ### Talks on Livestreaming 8 | - Nick Taylor [Starting to Stream on Twitch Slides](https://www.iamdeveloper.com/stream2021) 9 | 10 | ## Video Resources 11 | 12 | 13 | ## Virtual Setup 14 | - [Improve your Virtual Setup](https://medium.com/google-developer-experts/improve-your-virtual-setup-video-3b0b9dc15833) by Gant Laborde 15 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | Copyright (c) 2020 Virtual Coffee 2 | 3 | Permission is hereby granted, free of charge, to any person obtaining 4 | a copy of this software and associated documentation files (the 5 | "Software"), to deal in the Software without restriction, including 6 | without limitation the rights to use, copy, modify, merge, publish, 7 | distribute, sublicense, and/or sell copies of the Software, and to 8 | permit persons to whom the Software is furnished to do so, subject to 9 | the following conditions: 10 | 11 | The above copyright notice and this permission notice shall be 12 | included in all copies or substantial portions of the Software. 13 | 14 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, 15 | EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF 16 | MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND 17 | NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE 18 | LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION 19 | OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION 20 | WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. -------------------------------------------------------------------------------- /Resources.md: -------------------------------------------------------------------------------- 1 | # Resources 2 | 3 | A list of resources shared by Virtual Coffee members but everyone is welcome to contribute. 4 | To contribute add a resource on the list below using this template. 5 | 6 | ``` 7 | [Name of the resource](the Link) - a brief description. Add by [Your name](link to your github user) 8 | ``` 9 | 10 | ## Documentation 11 | 12 | - [MDN HTML](https://developer.mozilla.org/en-US/docs/Web/HTML) - the MDN page that contains tutorials, references and advanced topics on HTML. Add by [Vanessa Poppe](https://github.com/vanessacor) 13 | 14 | ## Accessibility 15 | 16 | - [W3C Accessibility Principles](https://www.w3.org/WAI/fundamentals/accessibility-principles/) - a list of web accessibility requirements for websites, web applications, browsers and other tools. Add by [Vanessa Poppe](https://github.com/vanessacor) 17 | 18 | ## Cheatsheets 19 | 20 | - [GitHub CheatSheet](https://github.github.com/training-kit/downloads/github-git-cheat-sheet.pdf) - commonly Git command line instructions for quick reference. Add by [Vanessa Poppe](https://github.com/vanessacor) 21 | 22 | ## Design 23 | 24 | ### Color tools 25 | 26 | - [Color Space](https://mycolor.space/) - color palette generator. Add by [Sara McCombs](https://github.com/saramccombs) 27 | 28 | - [CSS Gradiente](https://cssgradient.io/) - is a free tool that lets you create a gradient background for websites. Add by [Sara McCombs](https://github.com/saramccombs) 29 | 30 | ### Images 31 | 32 | - [Unsplash](https://unsplash.com/) - source of freely-usable images. Add by [Sara McCombs](https://github.com/saramccombs) 33 | - [Pexels](https://www.pexels.com/) - free stock photos. Add by [Sara McCombs](https://github.com/saramccombs) 34 | 35 | ### Icons 36 | 37 | - [fontawesome](https://fontawesome.com/) - Icons and social logos for websites. Add by [Vanessa Poppe](https://github.com/vanessacor) 38 | - [Ion Icons](https://ionicons.com/v4/) - premium icons for use in Web, IOS, Android and desktop apps. Add by [Vanessa Poppe](https://github.com/vanessacor) 39 | 40 | ### Lorem Ipsum 41 | 42 | - [Cat Ipsum](http://www.catipsum.com/) - a Lorem Ipsum generator for cat lovers. Add by [Vanessa Poppe](https://github.com/vanessacor) 43 | 44 | ## Markdown 45 | 46 | - [Markdown Table Generator](https://www.tablesgenerator.com/markdown_tables) - Generate a MD table quick and easy. Add by [Sara McCombs](https://github.com/saramccombs) 47 | 48 | ## Libraries 49 | 50 | ### JavaScript 51 | 52 | - [Moment](https://momentjs.com/) - parse, manipulate, format and display dates in JavaScript. Add by [Vanessa Poppe](https://github.com/vanessacor) 53 | 54 | ## Learning to Learn 55 | 56 | - [Fixed vs. Growth: The Two Basic Mindsets That Shape Our Lives](https://www.brainpickings.org/2014/01/29/carol-dweck-mindset/) - How to fine-tune the internal monologue that scores every aspect of our lives, from leadership to love. Add by [BekahHW](https://github.com/bekahhw) via [NickT](https://github.com/nickytonline) 57 | 58 | - [How to Teach Code](https://welearncode.com/teaching-code/) - ways you can teach code, how to coach students on a learning mindset, the mechanics of teaching a lesson, and oodles of tips for teaching. Add by [BekahHW](https://github.com/bekahhw) via [NickT](https://github.com/nickytonline) 59 | 60 | ## Learning Resources 61 | 62 | ### JavaScript 63 | - [Operator Lookup](https://joshwcomeau.com/operator-lookup/) - Enter or choose a JS operator to learn more about it. Add by [BekahHW](https://github.com/bekahhw) via [NickT](https://github.com/nickytonline) 64 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Virtual Coffee Open-Source 2 | 3 | This repository serves as a resource for developers at all levels interested in learning Open Source Software best practice and methodology. We hope it can become a welcoming and educational space for developers who want to get more experience in contributing to open source projects. 4 | 5 | This project was an organic initiative by attendees of the virtual coffee meetup who all found that the typical OSS experience is not very friendly to people unfamiliar with OSS contributions. 6 | 7 | # What is Virtual Coffee? 8 | 9 | Virtual Coffee is a bi-weekly online meetup where developers of all types, backgrounds, and experience meet up to discuss basically anything and everything so they can learn and grow from each other's experiences. The path of a software developer can often be arduous and uncertain and having a community of peers to interact with can help all of us grow as competent and confident engineers. 10 | 11 | # Features 12 | 13 | As of right now, this repo is simply a hosting place for resources and examples, starting with this README, which will eventually serve as an example for well, a good README. Our contributors may decide to add accompanying web platform functionality in the future. 14 | 15 | # Contributing 16 | 17 | Being able to contribute is one of the core reasons the Virtual Coffee folks wanted to create this space. 18 | 19 | See this project's [contributions file](https://github.com/Virtual-Coffee/open-source/blob/main/CONTRIBUTING.md) for a full breakdown of how you can add to the repository! 20 | 21 | Also check out the wonderful article [How to contribute to open source](https://dev.to/janessatran/a-beginner-s-guide-to-contributing-to-open-source-4fen) by Janessa Tran 22 | 23 | # Projects 24 | 25 | Projects related to the Virtual Coffee community or recommended by virtual coffee members that you can contribute to. 26 | 27 | * [Footnote.](https://github.com/cambardell/footnote2) An iOS app written with Swift and SwiftUI. Current tasks include accessibility support and supporting multiple platforms, although new features of any kind are encouraged. 28 | 29 | * [Gisla](https://github.com/jwcarman/gisla) It’s a distributed saga coordinator app created by the illustrious James Carman. 30 | 31 | * [Free Code Camp Newbie Friendly Issues](https://github.com/freeCodeCamp/chapter/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+label%3A%22help+wanted%22) Free Code Camp maintains a nice list of issues new folks can get started on. 32 | 33 | * [Moms-Learn-Tech](https://github.com/BekahHW/Moms-Learn-Tech) Resources for moms coming back into the tech field or learning to code for the first time by Bekah Hawrot Weigel 34 | 35 | * [Horcrux](https://github.com/jesseduffield/horcrux/issues) Split your file into encrypted fragments so that you don't need to remember a passcode. Created by Jesse Duffield and recommended by Gant Labourde. 36 | 37 | * [Forem Browser Extension](https://github.com/forem/forem-browser-extension) The Forem browser extension which allows users to seamlessly navigate between communities. Submitted by Nick Taylor 38 | 39 | * [Ifme](https://github.com/ifmeorg/ifme) Free, open source mental health communication web app to share experiences with loved ones. 40 | 41 | * [Good First Issues With Next.js](https://dev.to/github/good-first-issues-with-next-js-hfg) Highlighting good issues for first timers in the Next.js repo. Suggested by Nick Taylor. 42 | 43 | * [Free Code Camp](https://github.com/freeCodeCamp/chapter/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+label%3A%22help+wanted%22) Beginner Issues in the Free Code Camp open source repository, submitted by Bekah Hawrot Weigel 44 | 45 | * [Drone](https://github.com/harness/drone) and [Drone Documentation](https://github.com/drone/docs) Most Starred OSS Continuous Integration tool created by Brad Rydzewski. Suggested by Marie Antons, reach out directly on Slack or join the [Harness Community Slack](https://join.slack.com/t/harnesscommunity/shared_invite/zt-y4hdqh7p-RVuEQyIl5Hcx4Ck8VCvzBw) to get assistance contributing 46 | 47 | # Acknowledgments 48 | 49 | A special thank you to all the members of the Virtual Coffee community who donate their time, labour, and love to making the tech community a better place. 50 | -------------------------------------------------------------------------------- /CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | # Virtual Coffee Open Source Contributions Guide 2 | 3 | **Note:** this guide is intended for absolute beginners to collaborations on OSS projects, but we would absolutely love more experienced developers to read it and give feedback on how to improve! 4 | 5 | ## Getting Started 6 | 7 | If you're looking to start learning how to work with the Virtual Coffee Open Source Repo, this doc tries to provide all the resources to get you from confusion to productivity. 8 | 9 | We're not here to reinvent the wheel, so where we feel appropriate, we reference and link to resources we feel do a good job of helping a newbie through that particular section of setup. 10 | 11 | Most of the project is currently written using [markdown](https://www.markdownguide.org/basic-syntax/) to make it easy to add, modify, and edit what we need to. 12 | 13 | We try not to take anything for granted, but in case we miss something, please reach out to us in the Virtual Coffee slack group and let us know! 14 | 15 | **Note:** If you're already in the Virtual Coffee slack, feel free to skip the section below and go straight to **Step 3: Find/Make An Issue** 16 | 17 | ## Step 1. Joining Virtual Coffee and the Slack 18 | 19 | As of right now, there's no explicit restriction to who can contribute to this repo. However, we typically recommend that anyone wishing to contribute attend at least one Virtual Coffee Zoom meetup (you can find the meeting details [here](https://meetingplace.io/virtual-coffee)). 20 | 21 | After attending the meeting, you're free to join the Virtual Coffe Slack group where attendees can chat and communicate in between meet-ups sessions. The slack is another great place for finding resources. Spefically, the **#open-source** channel is where we chat all things OSS, incluing contributions here, as well as other projects. If you've never used Slack before you can [learn about it here](https://slack.com/help/articles/115004071768-What-is-Slack-). 22 | 23 | Once you've done that, you're good to go! 24 | 25 | ## Step 2. Setting up a Github Account 26 | 27 | We're going to assume you know what [github](https://www.howtogeek.com/180167/htg-explains-what-is-github-and-what-do-geeks-use-it-for/) is about and how it works (otherwise, how would you be reading this?) 28 | 29 | If you haven't made a github account as yet, make one [now](https://github.com). It's free! 30 | 31 | ## Step 3. Find/Make An Issue 32 | 33 | Github uses a feature called _issues_. Issues are essentially a way to highlight bugs, features, problems, or any sort of suggestion or action you wish to happen on a github hosted project (you can find a more comprehensive explanation [here](https://guides.github.com/features/issues/)). 34 | 35 | We highly recommend looking at the [Virtual Coffee open-source repo](https://github.com/Virtual-Coffee/open-source/issues) to find a good open issue to start with. We always try to keep them populated with some beginner friendly issues that anyone can attempt to solve. We also use a `PR Submitted` tag to indicate when an Pull Request has been submitted for an issue, but it hasn't yet been merged, as most people would rather would on an issue with no attempted PRs yet. 36 | 37 | If you feel like there's a contribution you would like to make that isn't represented by an already existing issue, feel free to create your own! 38 | 39 | ## Step 4. Creating a PR 40 | At this point, you have two options. 41 | 42 | **The first option** is using the github interface to fork the repo and submit a Pull Request (no code or terminals or IDE required). [This guide](https://guides.github.com/activities/hello-world/) shows just how to do that for a small personal repo. You would simply replace the step of creating a new repository to just navigating to the virtual coffee open source one and forking that instead. This is a great idea if you simply plan to add to or edit one of the markdown files we use for documentation in this project. 43 | 44 | **The second option** is go the traditional route of forking the repo, creating a local copy of that fork, and working on your changes that way. This is also the only way to go if this project expands to include an associated application. For that we recommend [this guide](https://www.dataschool.io/how-to-contribute-on-github/). 45 | 46 | If you want some additional tips before submitting a Pull Request, I recommend 47 | 48 | **Note:** The guide referenced above uses _master_ as the naming convention for the default branch in all its repos. Here at Virtual Coffee, _main_ is the default branch name. When following the instructions in the guide, simply replace _master_ with _main_ wherever it appears and it should proceed as normal. [this guide](https://www.hanselman.com/blog/EasilyRenameYourGitDefaultBranchFromMasterToMain.aspx) can help you transition with your own personal repos from master to main, and explains the methodology as to why you should. 49 | 50 | ## Step 5. Awaiting Review 51 | 52 | Once you've submitted your pull request, the only thing left is to wait from feedback from one of the project maintainers. Since this is volunteer work for all of course, we ask for patience if you don't see a response immediately. Sometimes it takes about a day for someone's schedule to clear up to have the sit to properly review incoming PRs. We'd rather not rush a response after someone has put time and effort into submitted. If it's been over 24 hours and you haven't received any acknowledgement, you can post a message in the **#open-souce** channel in the slack reminded of your PR, and someone will get back to you. 53 | 54 | If the PR looks good, a maintainer will typically give feedback and merge the request immediately, otherwise they'll let you know what questions they have or what needs to change before your work can be accepted. Once it is, you'll see your changes on the main branch and VOILA, open source contribution complete! 55 | 56 | ## Step 6. Tips, Tricks and Gotchas 57 | 58 | This section is just little notes and bits of info that can smooth over some of the bumps and hiccups that can come along with contributiong. 59 | 60 | - While this isn't absolutely required, we highly recommend **associating your Pull Requests with the Issue that they're intended to address**. This makes review much easier and avoids confusion when looking back at past commits. Github allows you to link a PR to an issue both during and after the PR's creation (the option should located in rightmost panel of the github PR interface). 61 | - **Please do not hesitate to ask for help** in any part of this process if you feel confused. As soon as they can, project maintainers can try and get you through the parts which are confusing you. Just be aware that no one here is a github expert :), we're just folks happy and willing to help others get some experience. 62 | - Be extra careful when working with git in the command line. Incorrectly typed names or commands can have strange results, and navigating git issues can be very perplexing. Fortunately, there's a plethora of resources on fixing said issues, and rest assured that any error you make has already been done, and solved, by someone. 63 | 64 | That's all for now. If you feel like anything is missing from this document that you wish were included, let us know. Or hey, open up a fresh issue and take a shot at helping us make it better! 65 | --------------------------------------------------------------------------------