# outreachy Published articles for outreachy. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## From Contributor to Outreachy Intern: My Fedora Journey Begins DevFeed: [From Contributor to Outreachy Intern: My Fedora Journey Begins]() Original publisher: [Read original article]() Author: Aman . Published: 2026-06-16T12:00:00Z Content type: article Language: en Sources: [Fedora Community Blog]() Topics: [Fedora](), [FastAPI](), [API](), [release engineering](), [Authentication](), [CI/CD](), [forgejo](), [Pydantic](), [Swagger](), [Deployment](), [openid]() Tags: [apis](), [backend](), [blog](), [fedora-project-community](), [intern](), [journey](), [mentored-projects](), [open-source](), [outreachy]() ### AI overview Aman describes his first two weeks as an Outreachy intern with the Fedora community. He introduces the Fedora Release Schedule Planner API project and outlines planned work on testing, CI reliability, OpenID Connect authentication, Fedora infrastructure integration, and deployment preparation. ### Source excerpt Introduction Hi, I'm Aman, a software developer and open-source enthusiast who enjoys backend development, APIs, and building tools that are useful to others. I recently started my Outreachy internship with the Fedora community, and this is my first blog as an intern. In this post, I want to share what my first two weeks have [...] The post From Contributor to Outreachy Intern: My Fedora Journey Begins appeared first on Fedora Community Blog. ## Journey with Airflow as an Outreachy Intern DevFeed: [Journey with Airflow as an Outreachy Intern]() Original publisher: [Read original article]() Author: Apache Airflow Published: 2020-08-30T00:00:00Z Content type: opinion Language: en Sources: [Apache Airflow Blog]() Topics: [airflow](), [REST API](), [foss](), [Development](), [Pull Request]() Tags: [airflow](), [apache-airflow](), [community](), [contributions](), [foss](), [intern](), [outreachy](), [rest-api]() ### AI overview The article recounts an Outreachy intern's experience contributing to Apache Airflow, including choosing a REST API project, setting up the development environment, submitting and reviewing pull requests, learning from feedback, and understanding Airflow concepts such as pools, tasks, DAGs, and DAG runs. ### Source excerpt Outreachy is a program which organises three months paid internships with FOSS projects for people who are typically underrepresented in those projects. Contribution Period The first thing I had to do was choose a project under an organisation. After going through all the projects I chose "Extending the REST API of Apache Airflow", because I had a good idea of what REST API(s) are, so I thought it would be easier to get started with the contributions. The next step was to set up Airflow's dev environment which thanks to Breeze, was a breeze. Since I had never contributed to FOSS before so this part was overwhelming but there were plenty of issues labelled "good first issues" with detailed descriptions and some even had code snippets so luckily that nudged me in the right direction. These things about Airflow and the positive vibes from the community were the reasons why I chose to stick with Airflow as my Outreachy project. Internship Period My first PR was followed by many new experiences one of them being that I introduced a bug in it;). But nonetheless it made me familiar with the feedback loop and the feedback on my subsequent PRs was the focal point of the overall learning experience I went through, which boosted my confidence to contribute more and move out of my comfort zone. I wanted to learn more about the things that happen under the Airflow's hood so I started filtering out recent PRs dealing with different components and I would go through the code changes along with discussion that would help me get a better understanding of the whole workflow. Airflow's mailing list was also a great source of knowledge. The API related PRs that I worked on helped me with some of the important concepts like: Pool CRUD endpoints where pools limit the execution parallelism. Tasks determine the actual work that has to be carried out. DAG which represents the structure for a collection of tasks. It keeps track of tasks, their dependencies and the sequence in which they have ## Outreachy Internship Update: Learning Mozilla's Development Process and Refactoring Marionette's Python Test Runner DevFeed: [Outreachy Internship Update: Learning Mozilla's Development Process and Refactoring Marionette's Python Test Runner]() Original publisher: [Read original article]() Author: Anjana Sofia Vakil (contact@anjana.dev) Published: 2016-08-02T00:00:00Z Content type: opinion Language: en Sources: [Mozilla Automation]() Topics: [Development](), [Mozilla](), [Testing](), [Python](), [Refactoring](), [Test-driven development](), [Pytest](), [Firefox]() Tags: [development-process](), [firefox](), [internship](), [marionette](), [mozilla](), [mozreview](), [outreachy](), [pytest](), [python](), [refactoring](), [test](), [testing](), [treeherder]() ### AI overview An Outreachy intern reflects on the first part of an internship with Mozilla, describing the process of learning Mozilla's development tools and workflows. The article also outlines work on test-driven refactoring of Marionette's Python test runner and previews a follow-up post about its test runner and harness. ### Source excerpt It feels like yesterday that I started my Outreachy internship, but it was actually over 2 months ago! For the last couple of weeks I've been on Outreachy hiatus because of EuroPython, moving from Saarbrücken to Berlin, and my mentor being on vacation. Now I'm back, with 6 weeks left in my internship! So it seems like a good moment to check in and reflect on how things have been going so far, and what's in store for the rest of my time as an Outreachyee. What have I been up to? Learning how to do the work In the rather involved application process for Outreachy, I already had to spend quite a bit of time figuring out the process for making even the tiniest contribution to the Mozilla codebase. But obviously one can't learn everything there is to know about a project within a couple of weeks, so a good chunk of my Outreachy time so far was spent on getting better acquainted with: The tools I've already written about my learning experiences with Mercurial, but there were a lot of other components of the Mozilla development process that I had to learn about (and am still learning about), such as Bugzilla, MozReview, Treeherder, Try, Mach... Then, since the project I'm working focuses on testing, I had to grok things like Pytest and Mock. Since most everything I'm doing is in Python, I've also been picking up useful Python tidbits here and there. The project My internship project, "Test-driven refactoring of Marionette's Python test runner", relates to a component of the Marionette project, which encompasses a lot of moving parts. Even figuring out what Marionette is, what components it comprises, how these interrelate, and which of them I need to know about, was a non-trivial task. That's why I'm writing a couple of posts about the project itself - one down, one to go - to crystallize what I've learned and hopefully make it a little easier for other people to get through the what-even-is-it steps that I've been going through. This post is a sort of "intermission", so sta ## Mozilla London All Hands 2016 DevFeed: [Mozilla London All Hands 2016]() Original publisher: [Read original article]() Author: Anjana Sofia Vakil (contact@anjana.dev) Published: 2016-06-20T00:00:00Z Content type: opinion Language: en Sources: [Mozilla Automation]() Topics: [Mozilla](), [Web]() Tags: [culture](), [event](), [executive](), [intern](), [london](), [mozilla](), [organization](), [outreachy](), [taskcluster](), [technology](), [web]() ### AI overview An Outreachy intern recounts attending Mozilla London All Hands 2016, highlighting the event's talks, meetings, team activities, and the opportunity to connect with Mozilla colleagues and interns. The article also reflects on finding valued female role models across Mozilla. ### Source excerpt Last week, all of Mozilla met in London for a whirlwind tour from TARDIS to TaskCluster, from BBC1 to e10s, from Regent Park to the release train, from Paddington to Positron. As an Outreachy intern, I felt incredibly lucky to be part of this event, which gave me a chance to get to know Mozilla, my team, and the other interns much better. It was a jam-packed work week of talks, meetings, team events, pubs, and parties, and it would be impossible to blog about all of the fun, fascinating, and foxy things I learned and did. But I can at least give you some of the highlights! Or, should I say, Who-lights? (Be warned, that is not the last pun you will encounter here today.) Foxy, the TARDIS, and espionage in the park? All in a day's work at #MozLondon! pic.twitter.com/QPWdPRnJHY -- Anjana Vakil (@AnjanaVakil) June 14, 2016 Role models While watching the plenary session that kicked off the week, it felt great to realize that of the 4 executives emerging from the TARDIS in the corner to take the stage (3 Mozillians and 1 guest star), a full 50% were women. As I had shared with my mentor (also a woman) before arriving in London, one of my goals for the week was to get inspired by finding some new role moz-els (ha!): Mozillians who I could aspire to be like one day, especially those of the female variety. Why a female role model, specifically? What does gender have to do with it? Well, to be a good role model for you, a person needs to not only have a life/career/lego-dragon you aspire to have one day, but also be someone who you can already identify with, and see yourself in, today. A role model serves as a bridge between the two. As I am a woman, and that is a fundamental part of my experience, a role model who shares that experience is that much easier for me to relate to. I wouldn't turn down a half-Irish-half-Indian American living in Germany, either. At any rate, in London I found no shortage of talented, experienced, and - perhaps most importantly - valued women at Mo ## Outreachy: What It Is, How It Works, and Why It Matters DevFeed: [Outreachy: What It Is, How It Works, and Why It Matters]() Original publisher: [Read original article]() Author: Anjana Sofia Vakil (contact@anjana.dev) Published: 2016-05-23T00:00:00Z Content type: article Language: en Sources: [Mozilla Automation]() Topics: [Hacktoberfest](), [Open Source](), [rust refactoring](), [Python](), [Testing](), [The Lounge](), [Firefox](), [Puppeteer]() Tags: [foss](), [internship](), [irc](), [mozilla](), [open-source](), [outreachy](), [python](), [refactoring](), [software](), [testing]() ### AI overview The author describes starting an Outreachy internship with Mozilla and explains how the program helps people from underrepresented groups participate in free and open-source software. The article covers its remote, paid, three-month internships, mentoring, communication practices, and the author's project to test and refactor Marionette's Python test runner. ### Source excerpt Today was my first day as an Outreachy intern with Mozilla! What does that even mean? Why is it super exciting? How did I swing such a sweet gig? How will I be spending my summer non-vacation? Read on to find out! What is Outreachy? Outreachy is a fantastic initiative to get more women and members of other underrepresented groups involved in Free & Open Source Software. Through Outreachy, organizations that create open-source software (e.g. Mozilla, GNOME, Wikimedia, to name a few) take on interns to work full-time on a specific project for 3 months. There are two internship rounds each year, May-August and December-March. Interns are paid for their time, and receive guidance/supervision from an assigned mentor, usually a full-time employee of the organization who leads the given project. Oh yeah, and the whole thing is done remotely! For a lot of people (myself included) who don't/can't/won't live in a major tech hub, the opportunity to work remotely removes one of the biggest barriers to jumping in to the professional tech community. But as FOSS developers tend to be pretty distributed anyway (I think my project's team, for example, is on about 3 continents), it's relatively easy for the intern to integrate with the team. It seems that most communication takes place over IRC and, to a lesser extent, videoconferencing. What does an Outreachy intern do? Anything and everything! Each project and organization is different. But in general, interns spend their time... Coding (or not) A lot of projects involve writing code, though what that actually entails (language, framework, writing vs. refactoring, etc.) varies from organization to organization and project to project. However, there are also projects that don't involve code at all, and instead have the intern working on equally important things like design, documentation, or community management. As for me specifically, I'll be working on the project Test-driven Refactoring of Marionette's Python Test Runner. You can