intro VS virtualcoffee.io

Walk reviewers through your code, highlighting your changes' "what" and "why." Be generous with examples and explanations. Think of it as a user guide for your changes. If your PR contains several changes, as in this example, consider using bullet points or checklists. Bottom line: The PR description should give reviewers an immediate understanding of your changes.

If you're new to open source, and you're not sure where to start, check out our Intro to Open Source course. We recently created a new feature for Repository Pages, so if you want to see how your repository has progressed, you can go to:

If you like this post, watch our Intro repo where we'll be launching a new intro course for maintainers soon!

As one of the docs maintainers for OpenSauced, I find it helpful to track our docs team to make sure I'm supporting them and to see the progress we're making. (You'll see some huge work shipped from this team in the next couple of weeks on the Intro Repo, when we launch our maintainer course!)

At OpenSauced, we’ve been working to curate a contributor journey that allows for contributors to grow. We have repositories made for new contributors, like our Intro Course, pizza-verse, and guestbook. We also include good first issue labels on some of the issues in our app, which is generally geared towards someone leaving the new stage and entering the intermediate stage. In the same way, our docs repo has a variety of issues open to different levels. And finally, there’s always space for our expert contributors across the repositories.

This guestbook is a place for people who have taken OpenSauced's Intro to Open Source course to take their first steps into contributing to open source.

- name: Post comment for course contributors if: contains(github.event.pull_request.title, 'as a contributor') run: | PR_COMMENT="Congratulations on completing Chapter 5 of the Intro to OSS Course with your contribution to this repository! You're almost to the end of the course. Create a [highlight](https://app.opensauced.pizza/feed) of your contribution to our guestbook using the instructions in [chapter 6](https://github.com/open-sauced/intro/blob/main/06-the-secret-sauce.md) and share it with us!" curl -s -H "Authorization: token ${{ secrets.GITHUB_TOKEN }}" -X POST -d "{\"body\":\"$PR_COMMENT\"}" "https://api.github.com/repos/${{ github.repository }}/issues/${{ github.event.pull_request.number }}/comments"

If you're new to open source, and you're not sure where to start, check out our Intro to Open Source course.

Yet, technical prowess was only a part of my journey. I was drawn into the enchanting realm of open-source development. It was as if I had stumbled upon a hidden treasure trove of collaboration and innovation. With bated breath, I clicked on a link that read https://github.com/open-sauced/intro. Little did I know that this click would forever alter the course of my story.

If you want to get some hands-on experience using git, check out OpenSauced's Intro to Open Source Course or sign-up for one of our workshops that are listed on the bottom of our #100DaysOfOSS Challenge docs.

Let’s go back to April of 2020. The early days of the pandemic when the world seemed to close in around us. The pandemic had left us isolated, uncertain, and craving connection. It was in this time that something beautiful was born: Virtual Coffee. I put out one, simple tweet: Is anyone interested in Virtual Coffee. And what started as one coffee turned into finding hope together in the one place we could safely gather: online. Virtual Coffee was built out of necessity but grown through compassion and shared experiences.

Thankfully I am part of an awesome online community of developers: https://virtualcoffee.io

I've been learning how to code for the past five months and let me tell you, it really is a whirlwind of emotions! After an amazing mentorship that ended too soon, I realized something: I thrive when I learn with others. That's when I found Virtual Coffee, a tech community that uplifts and celebrates wins of all kinds! Just one virtual coffee in, Chris Nowicki, a generous full stack developer in the community, already dropped a goldmine with us--learning and building in public!

I joined an online developer community called Virtual Coffee last year and saw Klesta’s post about Web Dev Path on their Slack channel. I remember I read her interview to know better about it. I was familiar with building something on my own but I didn’t have much experience to develop within a team. Web Dev Path sounded like a good place to improve skills to work in a team.

Next month at Virtual Coffee, we're doing a monthly challenge for public speaking. What are your favorite tips or resources?

VC Link

Since last September, I have had the opportunity to be an open source project maintainer. I help maintain some project repositories at Virtual Coffee, OpenSauced, and SheSharp communities. And now, I can see the view from a different perspective.

I'm part of some tech communities and love documentation. Together with the core team of the Virtual Coffee Community, I actively discuss ideas and contribute to creating and shaping the community documentation. From there, I was trusted to be the Documentation Team Lead.

Virtual Coffee

Update monthly challenge page to Hacktoberfest — Virtual Coffee