Hi friends 👋,

I'm participating in the #100DaysOfOSS challenge by OpenSauced. Inspired by the #100DaysOfCode challenge, #100DaysOfOSS is a challenge for everyone interested in open source to learn about open source, contribute, or maintain open source projects over 100 days, starting on July 23rd.

This challenge focuses on growth. So it's about more than just contributing code. You can learn about open source by reading or watching tutorials, engaging in the community by sharing information and knowledge, or any other ways you find comfortable and doable. You can read more about how you can participate here.

---

You can follow my #100DaysOfOSS daily progress in my journal below.

---

✅ Recap: Day 15-27

Learning and Supports

During this period, I focused more on writing blog posts to support the open source community and motivating others to dive into open source.

• I wrote and published a blog post about my #100DaysOfOSS journey; #100DaysOfOSS Recap: Day 1-14.

• I published an article; How to Communicate Better in Open Source.

• I revisited my posts with open-source topics and improved and edited one.

• I looked closer into OpenSauced Highlights and added my highlights.

• I attended two "Open Source Hour" Twitter spaces hosted by OpenSauced.

• I answered a question on Twitter about open source.

Contributions

Virtual Coffee

• I'm working on editing the previously improved Virtual Coffee Podcast transcriptions to follow the new guidelines and pushed them to a draft pull request.

• I created three issues to update the content of community guides in Virtual Coffee and made pull requests.

OpenSauced

I encountered some bugs and saw room for improvement when creating the highlights on OpenSauced. So I made a few issues on the open-sauced / insights repository.

• I created an issue to ask for a feature to order the highlights based on the selected date that now moved into a discussion.

• I made an issue to address a bug in the calendar's responsiveness.

• I created an issue to address a bug of avatars that are either empty or not the user.

• I raised an issue to address a bug in the sidebar's responsiveness on the big screens.

Challenges

• Whenever I want to raise an issue, I always look for the same or similar issues and pull requests to avoid duplications. But it's still challenging for me to find them — especially when there are hundreds of them! — even though I used many variations of keywords. It is one reason I often hesitate to create an issue on a repository I'm unfamiliar with 😣. But this time around, I pushed through 💪!

• Writing good titles and clear descriptions for issues is still challenging for me. I need to practice more. Now I make it a habit to create screen recordings (in GIFs) to make my point more straightforward when necessary.

Wins and Gratitudes

• I finally published the post that sat in my draft for almost a year!

• My article, How to Communicate Better in Open Source, got onto the OpenSauced newsletter, earned me a CodeNewbie badge on DEV, and was featured on Top Featured CodeNewbie Posts (8/17/23)!

• One of my highlights got featured on OpenSauced's weekly Highlight Reel!

• My pull request to update the README on OpenSauced 's 100-days-of-oss-template repository got merged!

• My pull request to update a guide at Virtual Coffee got merged!

Final Words

If you just heard about the #100DaysOfOSS challenge and want to participate, there is still time. You can start now and join us 🙌!

And if you're doing #100DaysOfOSS, how was your experience? Do share it with us in the comment below 😄!

---

🖼️ Credit cover image: unDraw

Thank you for reading! Last, you can find me on Twitter, Mastodon, and BlueSky. Let's connect! 😊