If you are anything like me, joining an established open-source community for the first time can feel like walking into a room where everyone already knows each other.
The BugSigDB project has an active community on Zulip, where contributors, maintainers, mentors, and Outreachy applicants interact across different channels and discussions. There are conversations dating back several years, discussions about ongoing projects, questions from contributors, and people sharing their progress.
And then there is you. A newcomer trying to figure out where everything is and where you fit in.
The Crash Landing
When I first joined the community, I was honestly overwhelmed.
You will meet other Outreachy applicants who may have been around the community for years. Some have contributed to several projects, are familiar with the codebase, and understand how things work.
Meanwhile, you are probably still trying to understand the project description and figure out what everyone is talking about.
That's okay.
Let those initial emotions wash over you. Breathe, accept where you are, and remember that everyone was a beginner at some point.
You are not expected to know everything when you arrive. You are there to learn, contribute, and become part of the community.
First Things First: Introduce Yourself!
Do not be afraid to introduce yourself or ask for help. Seriously!
One of the biggest advantages of open-source communities is the opportunity to interact with people who have experience in areas you are just beginning to explore.
Start with a simple introduction. Tell people who you are, what brought you to the community, and what you are interested in working on.
For example:
Hello everyone! My name is Jane Doe. I'm an Outreachy applicant interested in contributing to BugSigDB. I'm new to the project and would appreciate some guidance on where to begin. Looking forward to learning and contributing alongside everyone!
You don't need a lengthy introduction. Just be polite, friendly, and genuine.
Also, take some time to understand how the community communicates. Every community has its own norms and guidelines. Be respectful, read the available instructions, search previous discussions before asking questions, and remember that there are real people on the other side of the screen.
When you eventually need help, make your questions specific.
Instead of simply saying, "I'm stuck," explain:
- What you are trying to accomplish.
- What you have done so far.
- Where exactly you are having difficulties.
For example:
I'm working on my first study curation. I've gone through the paper and identified the relevant comparisons, but I'm having difficulty determining the appropriate study design. Could someone point me in the right direction?
This makes it much easier for others to understand your problem and help you.
Don't Rush: Get Familiar with the Project
My advice? Slow down.
I spent approximately three days familiarizing myself with the project description, internship requirements, BugSigDB's Contents, its About page, its video guides , and the Curation Policy.
And I recommend that you do the same.
When you first join Zulip, you will see contributors working on curations, asking questions, sharing updates, and discussing different aspects of the project. It can be tempting to jump straight into the work because everyone else seems to be making progress.
Resist that temptation.
You need to understand what you are contributing to before you start contributing.
Here is what I recommend:
- Understand the project: Read the project description and BugSigDB's About page.
- Understand your responsibilities: Review the Outreachy internship or contribution requirements.
- Explore the platform: Go through BugSigDB's documentation and video guides to understand how the database works.
- Study the curation rules: Read the Curation Policy carefully. This will become one of your most important references when extracting and entering scientific findings.
Take a notebook, grab a pen, and work through the documentation in manageable sessions. You don't have to understand every technical detail on your first read. Write down unfamiliar terms, questions, and anything you would like to revisit.
I would give yourself up to three days for this initial orientation, as I did. You can always return to the documentation as you gain experience.
The goal isn't to memorize everything. It is to build enough understanding to make your first contribution meaningful.
What's Next?
Once you are comfortable with the project and its documentation, you can begin your first contribution: the mini-curation.
A quick but important note!
Before starting your mini-curation, request a BugSigDB account if you haven't already. Account creation may take some time, so it's best to submit your request early. You can continue familiarizing yourself with the project and preparing for your mini-curation while waiting for your account.
This is where things start getting interesting!
In the next article, I'll walk you through the documentation you need to pay particular attention to, what the mini-curation involves, and how to approach your first study.
Remember, you don't have to arrive as an expert. You just have to be willing to learn.
