Hey folks 
,
I just wanted to share some honest thoughts on why I think I was selected for the Community Architect Outreachy internship with Fedora (this is actually my second week. You can check my first week recap here) - and what you might want to keep in mind if you’re applying too.
This post is especially for anyone from underrepresented communities wondering if they’ll ever make it in open source. Spoiler: you absolutely can. Fedora is full of people rooting for you - you just need to show up and put in the work.
Real talk: Advice that helped me
From Jona Azizaj (@jonatoni - My mentor)
“It was your independence. You didn’t wait to be told what to do - you went for it. That’s what we want to see.”
Translation? Don’t sit around waiting for someone to hand you tasks. Take initiative. Fedora is an open playground - explore it, contribute, and show you’re here to grow and help.
From Roseline Bassey ( @roseline-bassey - Outreachy 2024 alum):
“Talk to your mentors. They should know what you’re doing. Communicate openly and often.”
Big facts. I messaged Roseline while applying, and she stressed that your mentor should be able to vouch for your work - which only happens if you’re visible, collaborative, and proactive.
From Mat H. (@theprogram - My Fedora Friend)
“Show your character, not just your code. We want people who care, who show kindness, curiosity, and follow-through.”
This advice was a game-changer. Fedora doesn’t just evaluate you based on contributions -they also pay attention to how you show up. Are you respectful? Do you support others? Do you actually care about what you’re working on?
That led to this amazing portfolio showcasing my work during the contribution period.
What worked for me
Here’s what I personally focused on:
- I picked a project that fit me.
I didn’t try to fake it. I chose the Community Architect role because it fit my strengths — writing, docs, project management, community work. You don’t need to “hack everything.” Choose something that aligns with what you’re naturally good at. (sometimes you might want to challenge yourself and find a challenging project: go for it!) - I aligned my work with the internship goals.
I didn’t just do “general Fedora work.” I contributed to docs, planned DEI events, created GitLab issues, collaborated with mentors - all things the internship was about. - I asked questions (a lot).
I wasn’t afraid to DM (what is really a game changer in my career to learn a lot from others - now engaging with you but being paid for it
) previous interns, new Friends(Mat H) who truly helped in some way <3. No shame in being new - the only L is not asking. - I documented everything.
From blog posts to GitLab contributions to Matrix chats. Leave a trail of proof. - I was helpful to others.
I gave feedback to other Outreachy applicants, cheered them on, and shared what I was learning. Community = contribution too.
For future applicants
If you’re applying to Fedora Outreachy:
- Start early
- Pick a project that fits you
- Don’t ghost - talk to mentors
- Document your work (blogs, GitLab, screenshots)
- Ask for help, offer help
- Be kind, curious, and committed
This internship isn’t just about skill. It’s about effort, mindset, and heart.
Mentors, your turn?
Calling the awesome folks who guided me and others - feel free to drop your tips and what you look for in an Outreachy applicant. Let’s pay it forward 
And any Outreachy alums — Nikita, Roseline, others — we’d love your voice here too.
Thanks for reading. And if you’re someone wondering if this opportunity is for you — I hope this gives you that extra push.
I’m proud to be part of this round. I’m here to keep learning, building, and supporting others. See you in the Matrix rooms or GitLab issues 
– Cornelius, Your friend in Open Source