Hello! Welcome to the second blog of my Open Source journey with Outreachy and Ersilia Open Source Initiative.If you haven't already, check out my first blog post about "Beginning my Journey into Open Source". In this blog, I want to share an important aspect that transformed the way I approach open-source development: GitHub Issues.

What are GitHub Issues?🚀

GitHub issues are a feature of the GitHub platform that allows users to track ideas, feedback, tasks, or bugs for work on GitHub.

The Fear of open communication😰

Before this open source journey, I held reservations about open communication. I feared judgment, criticism, or the perception of incompetence.
During the contribution phase of the Outreachy application process, I chose to work on the Ersilia Model Hub project. To my surprise, one of the assigned tasks was to "Open an issue" on the project's repository. 'Use this issue as your personal thread of the contribution period', the task described. I asked, are GitHub issues private? Unfortunately, they are not. Would opening an issue mean that everyone would be scrutinizing my work? I wondered. This approach was new to me.

Understanding GitHub Issues 🤔

As someone who associated issues with bug reports, I struggled to understand how they could foster open communication and collaboration.
One resource that helped me grasp the essence of GitHub Issue-Driven Development was the GitHub documentation on issue tracking. It provided a comprehensive overview of creating, managing, and utilizing issues effectively. Through this documentation, I learned that GitHub issues are not just meant for reporting bugs; they are a powerful tool for initiating discussions, sharing progress, seeking feedback, and managing project tasks📚.

Learning through Active Engagement

Additionally, I engaged with the project's repository, observing how other contributors and mentors utilized issues to communicate their progress and share challenges. With time, it became clear that GitHub Issues was not only a place to report problems but also a powerful tool for initiating discussions, tracking progress, sharing ideas, and managing project tasks. Through this experience, it became evident that open communication through issues is essential for effective collaboration within the open source community🤝.

Embracing Open Communication 💪

After being awarded an Outreachy intern position with Ersilia Model Hub, I knew I had to communicate more often. Commenting on issues isn't about exposing my vulnerabilities; it is an invitation to collaborate, gather feedback, and make it easier for my mentor to manage projects.
Although I still face moments of self-doubt, I'm continuously growing more comfortable and confident in expressing my thoughts and seeking help when needed. Every day presents new opportunities for personal and professional growth, and I am committed to honing my communication skills💬.

The Role of Core Values✨

“Just be yourself and stay true to your core values.” — Ben Quayle.

Throughout this transformative journey, my core values of learning, determination, and contribution played a significant role. The value of continuous learning motivated me to seek understanding and explore resources that demystified GitHub Issue-Driven Development. Determination empowered me to push past my initial reservations, overcome the fear of judgment, and engage in open communication.

To anyone joining open-source, Open-source communities thrive on collaboration and knowledge sharing. Asking questions and seeking help is not a sign of weakness but a testament to your dedication to learning and growth.