Outreachy 2026 – Enhancing the Fedora Release Schedule Planner API: Introduce yourself!

Project Discussion
1

Hello everyone, and welcome to the Fedora Project! :rocket:

Whether this is your first time interacting with an Open Source community or you are a seasoned contributor, we are thrilled you are here. :raising_hands: Fedora is a global, diverse community of people working together to build a free and open source operating system, and we are incredibly excited to see your interest in the Fedora Release Schedule Planner API project!

I am Justin Wheeler, the Fedora Community Architect. Alongside Fernando Fernandez Mancera (@ffmancera), I am one of your two Fedora Co-Coordinators for this Outreachy cohort. For this specific project, you will be guided by an amazing team of mentors: Tomáš Hrčka (@humaton), Antony Nyagah (@nyagah), and Samyak Jain (@jnsamyak)!

Because we have folks joining us from vastly different time zones and backgrounds, communication is the key to our success. In Fedora, we rely heavily on asynchronous, text-based communication. Before you dive in, we highly encourage you to read through our project guide, Communication in Fedora.

A quick note on how we evaluate contributions: We value quality over quantity. Please know that a high volume of forum posts does not equal a stronger application. Mentors evaluate the quality of your work on your specific project tickets (in Forgejo or GitLab). Please avoid posting in unrelated Fedora topics just to increase your activity metrics—it creates “noise” that makes it harder for mentors to review your work!

To help keep our forums organized, please reply directly to this thread to introduce yourself. In your reply, please tell us:

  1. Your Open Source journey: What is your current level of experience with open source software? (It is 100% okay if the answer is “none”!)
  2. Your “Why”: Why did you choose to participate in Fedora, and what drew you to this specific Release Schedule Planner API project?
  3. Your goals: What is the number one thing you hope to learn or take away from these next few weeks?
  4. Just for fun: If you could instantly become a world-class expert in any one non-technical skill or hobby, what would it be and why?

Take a deep breath, don’t be afraid to ask questions on your tickets, and have fun. We can’t wait to meet you!

7 Likes
3

Hello everyone, surprised to see me here​:sweat_smile:? I’m obsessed with Fedora!

My name is Olamide and I’ve contributed to various open source communities where I’ve worked on writing tests, fixing issues, and understanding large codebases. It’s been a mix of learning, breaking things and fixing things

I chose to participate in Fedora because I wanted to be part of a strong open source community. A community known for building widely used tools. This project caught my attention because it has to do with community engagement with technical work. Also, it’s interesting to see how contributions can be recognized and visualized in a meaningful way. I was an Outreachy applicant for the June 2025 cohort where I contributed to the release schedule planner

The main thing I hope to gain over the next few weeks is a deeper understanding of how a mature open source project is structured and to have my name registered as a contributor to Fedora which would give me bragging rights

I would say public speaking, being able to communicate ideas clearly and confidently in any setting is something I really admire, and it would be valuable in both tech and everyday life.

1 Like
4

Hi everyone, my name is Jamillah Bello.

My current level of experience with open source software cuts across different areas. More often than not, I don’t even realise they’re OSS until I do some research on them. I’ll start with Linux, I dual-booted my system with Ubuntu for 3 years until I switched to Fedora during a previous Fedora Outreachy project I contributed to.

In terms of media, I make use of OBS Studio for screen recording and VLC Media Player for watching videos. Nginx and Apache are always my go-to web servers, with Nginx taking the lead, and Apache only looking good to me when it’s specifically required. I’m pretty sure there are other open source tools I use that I’m not aware of, so I won’t go too deep into that so I don’t end up typing too much :sweat_smile: :sweat_smile: :sweat_smile:

I chose Fedora because of curiosity :thinking: :thinking: :thinking:. That’s what drew me in the first time I got interested in it and attempted the DEI project for my previous Outreachy contribution. I chose this particular project because I’ve recently been getting into API design and trying to learn all I can about it.

A friend and I are building a health and safety app to give Nigerians access to verified healthcare safety information and incident reports. The project relies heavily on APIs, and I had to do a lot of research to carry out my tasks. In the process, my interest was really piqued, and when I saw this project, it honestly felt like fate.

My goal for this Outreachy cohort is to leave better than I started. The number one thing I hope to take away from these next few weeks is knowledge and a hunger for more. I want to learn new things, improve my technical skills, gain practical experience in API design, contribute meaningfully, and get hands-on experience with testing and API security. This is not just for the next few weeks, but hopefully for the internship period as well if I get selected.

For my non-technical skill, I would choose to be great at karate. I’d like to be a skilled martial artist, mainly for self-defense. I’ve been in situations where it would have come in handy. I recently started taking taekwondo classes and it’s been great. Aside from the main reason I started, it has really helped my mental health. I feel more centred and at peace while training. But that’s just one part, I’d love to become an MMA expert overall :martial_arts_uniform: :martial_arts_uniform: :martial_arts_uniform:

2 Likes
5

Hi everyone, my name is Roger Koranteng.

I’ve been exploring and contributing to open source through personal projects and learning in public. I’m comfortable with Python, Git, and REST APIs, and I’ve been deepening my skills in backend development — particularly building and testing APIs.

I chose Fedora because the community genuinely values collaboration, and the Release Schedule Planner API project stood out to me — modernizing a real tool the community depends on using FastAPI, Pydantic, and OpenID Connect. Taking something from legacy XML to a production-ready API is exactly the kind of work I want to be doing.

My goal for these next few weeks is to deepen my understanding of how production-grade APIs are built, tested, and secured — and to make meaningful contributions along the way.

For the fun question — I’d choose cooking. Good food brings people together, and that’s hard to beat.

Looking forward to learning with everyone here!

2 Likes
6

Hi everyone, I’m Joy Aruku from Nigeria.

I have experience contributing to open source, and lately I’ve been exploring Python to expand my skill set. My curiosity for how things work behind the scenes and my desire to be part of a collaborative, mission-driven community led me to the Fedora project.

I chose the Fedora Badges project for a few reasons. First, I already have experience with Node.js, and since this project uses both Python and Node.js, it felt like the perfect fit to deepen my Python skills while building on what I already know. But more importantly, I was drawn to the purpose behind Fedora Badges: it’s a system that celebrates contribution and community. I believe recognition infrastructure like this plays a huge role in keeping open source communities welcoming and motivating, and I want to contribute to something that directly supports that human side of open source. Having experience with Git and web development, I’m excited to bring my skills to a project with real impact while growing in new areas like Python.

My goal for this Outreachy cohort is to leave better than I started. I want to walk away with deeper technical knowledge, practical experience working across both Python and Node.js, meaningful contributions under my belt, and hands-on exposure to building and maintaining real-world open source tools. That’s my focus not just for the next few weeks, but for the internship period as well, if selected.

Looking forward to learning with everyone here!

7

Hey everyone, I’m Charles Moruri — and if there’s one thing that’s shaped how I think about technology, it’s the belief that the best code isn’t just written, it’s shared.

I’ve been around open source long enough to know that the real magic isn’t in the commits — it’s in the culture.

I’ve been a Fedora user for a while, and stepping into this project feels less like a new chapter and more like finally showing up to a place I already called home. The Release Schedule Planner API caught my attention because behind every clean API endpoint is a community that depends on it — and I want to understand that responsibility more deeply.

My goal here isn’t just to write better code. It’s to deepen my craft of giving back — through mentorship, knowledge sharing, organizing spaces where people grow. I give talks, I run events, I show up. This internship is my opportunity to do that within one of the most respected open source communities on the planet.

And if I could wake up tomorrow as a world-class expert in anything? Public speaking and community organizing — because the most powerful thing a technologist can do is make other people believe they belong in the room too.

Glad to be here. Let’s build something worth talking about.

1 Like
8

Hello everyone, my name is Jeanom Williams.

I love to to understand how things work, solve problems and streamline work flow and I got to understand that with coding I could do all that, so out of curiosity I decided to take a leap into the world of tech. I dedicated myself to taking online courses and watching videos and reading any books on tech I could get my hands on. This a summary and so far so go, this has brought me to this internship where I’ll be guided by mentors to collaborate and solve problems in the community.

I honestly want to have a deeper knowledge of system workflows and what better way to know than by doing the work? After reading the project details, I saw that the project would introduce me to the Linux OS( Fedora distro), help me understand workflow better , guide me on how to contribute in the FOSS community and also, the Fedora project uses a language (Python) I am quite familiar with.

I have read and watched videos, and I have completed some personal projects using some online-learning materials as a guide, but I haven’t had the chance to utilize the skills I have acquired in real-life situations. This cohort would enable and empower me to utilize my skills to solve real-life problems, understand how distributed systems work, collaborate with the community and make meaningful contributions to the Fedora project.

Adaptability and Flexibility would the my choice of non-technical skills because i believe change is the only constant thing and I want to be able to adjust/evolve to changing conditions.

1 Like
9

Hi everyone! I’m Mercy. I have used many open source softwares and have made contributions as well. I have contributed to projects like OpenTelemetry and Parsl, and my contributions were around Python and its libraries.

I am a native Linux user and will take advantage of any opportunity to improve any of its distributions, which is where Fedora comes in. The release schedule planner API project is built using Python and its libraries, which is one of the things that excites me about it.

In the next few weeks I hope to learn a lot of things, but specifically I hope to understand the backend logic behind the release scheduling system as well as how it works now and what needs to be done to enhance it further.

I play card games in my free time and enjoy them very often. I also love to read fictional books to fuel my imagination.

1 Like
10

Hi everyone!

My name is Faith Kariuki, and I’m a software engineering learner with a growing focus on backend development using Python and APIs. I also have some experience with JavaScript and React.

My Open Source Journey:
I’m relatively new to open source. This is my second time actively contributing to a project. I’ve already set up the Fedora Release Schedule Planner locally (both with Docker and without Docker), explored the codebase, and started engaging with issues. I’m excited to learn by doing and contributing meaningfully.

My “Why”:
I chose to participate in Fedora because of its strong open source culture and collaborative community. This particular project stood out to me because it involves building and improving a real-world API, which aligns perfectly with my interest in backend development. I’m especially interested in learning FastAPI and understanding how production-level systems are structured and maintained.

My Goals:
The main thing I hope to gain over the next few weeks is confidence in contributing to open source projects, from understanding codebases to making meaningful contributions and collaborating effectively with others.

Just for fun:
If I could instantly become a world-class expert in a non-technical skill, I’d choose public speaking. I think it’s such a powerful skill for communicating ideas clearly, building confidence, and connecting with people.

Looking forward to learning and contributing with you all!

1 Like
11

Hi, I’m Asma.

I’ve used open source tools for a while, but I’m fairly new to contributing. Recently, I started getting involved more directly by working on bugs, reviews, and understanding how the process works.

I recently graduated in Computer Science and Information Security, and I enjoy working with Linux. One of my goals is to build my own Linux based OS and strengthen my engineering skills. I chose this project because it’s backend focused and pushes me in that direction.

If I could instantly master a non technical skill, it would be communication!

2 Likes
12

My name is Sania Siddiqui. I’m a beginner to open source. I have experience with Git, APIs, and building projects, and I’m now looking to start contributing to real-world projects.
I chose Fedora because of its strong open-source community. The Release Schedule Planner API interested me as it aligns with my interest in backend development and APIs.
I want to learn how to contribute effectively to open source and work with real codebases and teams.
I would love to become a novel writer because I enjoy storytelling and expressing ideas creatively.

1 Like
13

Good day, everyone!
:woman_raising_hand:t4:

My name is Cynthia Uche.
You can call me Priestess.

I’m a contributor for this year’s May round of Outreachy Internship.

I’m still somewhat new to open source.
I already have experience writing code and working on personal projects, but right now, I am focused on learning the practical side of open source development: using Git effectively in a collaborative environment, and becoming comfortable working with real project codebases.

I chose to participate in Fedora because it has a well-organized and welcoming community, especially for new contributors.
The Release Schedule Planner API project stood out to me because it looks like a real-world project where I can apply my existing development skills while also learning how to work within an open source team and workflow.

My main goal for the next few weeks is to understand how to contribute to this project independently; from reading an issue and understanding it, to making the change, writing a good commit, and successfully submitting it for review.

If I could instantly become a world-class expert in any non-technical skill, I would choose language learning.
I am already learning Korean and Spanish, so becoming highly skilled at learning languages quickly would be incredibly useful to me.
It would make it easier to connect with people from different cultures and communicate more effectively in both personal and professional environments.

I look forward to working with you all.
:hugs:

1 Like
14

Hello everyone,

My name is Aman, and I’m an Outreachy applicant for the “Enhancing the Fedora Release Schedule Planner API” project.

Open Source Journey:

My open source journey began in May 2025 with Meshery, where I explored service mesh technologies, followed by contributions to RISC-V projects. Currently, I am contributing to Oppia and some ML projects. These experiences have given me practical exposure to real-world projects; for example, I learned GitHub Actions (CI/CD) while contributing to Meshery.

Why Fedora:

I am a Linux enthusiast and currently use Linux Mint, which has strengthened my interest in open-source software and communities. Fedora appeals to me because it provides an opportunity to contribute to a meaningful open-source project, collaborate with an active community, and gain real-world development experience.

I also want to give back to the Linux and open-source community, as I have personally benefited from using Linux and open-source tools throughout my learning journey.

Why Release Schedule Planner API project:

I chose the Fedora Release Schedule Planner API project because it closely matches my Python background and backend interests. Through open-source contributions (including Oppia) and my GitHub projects, I’ve built practical systems and now want to grow in scalable API design, automation, and AI/ML powered tooling. I’m also excited to gain real-world CI/CD experience while learning from Fedora’s amazing mentors and community.

My Goals:

My goal is to enhance my Python and REST API skills, gain hands-on experience with FastAPI and Pydantic, and contribute meaningfully to Fedora. I also want to improve my skills in CI/CD pipelines, secure authentication systems (OpenID Connect), and integrating APIs with live infrastructure data.

Just for fun:
If I could instantly become a world-class expert, it would be leadership, because it involves guiding teams, making decisions, and bringing out the best in people.

Excited to be part of this community and contribute wherever I can.

1 Like
15

Hello everyone, it really feels good to join this amazing Fedora community. I am an active open source Software Engineer who specializes in architecting robust, scalable backends and event-driven distributed systems. With expertise across multiple technology stacks, I craft robust server-side solutions using Python (FastAPI). My experience spans from architecting RESTful APIs and microservices to implementing real-time communication systems and integrating cloud-based solutions. I thrive on solving complex problems, optimizing system performance, and delivering clean, maintainable code.

I am currently an active open source contributor with Zulip - a powerful, open-source team chat application designed for both real-time and asynchronous communication where I have worked on several features including migration of legacy code.

I am particularly drawn to this project: Enhancing the Fedora Release Schedule Planner API as it focuses on refining the current test suite, implementing secure authentication using OpenID Connect, and integrating the API with live Fedora infrastructure data to fully replace the legacy XML-heavy system. I believe being part of the team that is tasked with migrating legacy code to a more modern tool will vastly improve my skills in security, reliability and scalability on a large-scale platform working with Fedora.

If I could become an instant world-class expert in a non-technical hobby, that would be Animal commentary in the wild. It is one of my adduring hobbies, watching commentary of Animal behaviour in the wild.

1 Like
16

Hi everyone! I’m Akintewe Oluwasola (nathanakin on Codeberg), from Nigeria.

I’m fairly new to open source but I’ve been learning fast. I’ve been exploring codebases, running projects locally and making contributions. Every PR teaches me something new and I’m enjoying the process.

I chose Fedora because it’s a community that builds tools people actually use. The Release Schedule Planner caught my attention because it sits right at the heart of how Fedora organizes its releases. Working on something that the release engineering team depends on feels like real, meaningful work not just practice.

The number one thing I want to take away is a deeper understanding of how production APIs are built, documented and maintained in a real open source project. I want to leave better than I came.

Swimming, I already love it but I’d love to be world class at it :grinning_face_with_smiling_eyes: There’s something about being in the water that just clears everything.

Looking forward to learning from everyone here!

18

  • Your Open Source journey: What is your current level of experience with open source software? (It is 100% okay if the answer is “none”!)

    I’d describe my current level as intermediate and also actively hands-on. I’m not just exploring open source passively—I’m already working within a real project environment, specifically the Fedora Release Schedule Planner.

    With this project Release Schedule Planner I’ve been dealing with practical challenges like setting up Vagrant with libvirt, troubleshooting networking issues, working with Docker containers, and packaging Python applications using Poetry. These experiences have pushed me beyond just writing code into understanding how real-world systems are built, configured, and debugged.

    So while I’m still growing in open source, I’m already engaging with the kind of problems contributors actually face, which has been a valuable shift from purely academic or personal projects.

  • Your “Why”: Why did you choose to participate in Fedora, and what drew you to this specific Release Schedule Planner API project?

    I chose to participate in Fedora because I wanted exposure to real production-grade open source workflows, not just isolated coding tasks. Fedora stands out because it’s deeply tied to the Linux ecosystem, which aligns with my interest in systems, networking, and backend engineering.

    The Release Schedule Planner API project specifically caught my attention because it sits at the intersection of backend development and real-world coordination problems. It’s not just about building endpoints—it’s about handling structured data, scheduling logic, and reliability in a collaborative environment.

    Also, since I’ve been working with tools like FastAPI, Docker, and Poetry, this project feels like a natural extension where I can apply and stress-test those skills in a meaningful way.

  • Your goals: What is the number one thing you hope to learn or take away from these next few weeks?

    The number one thing I want to take away from these next few months is confidence working in a real open source codebase.

    Not just understanding the code but being able to:

    • Navigate an unfamiliar repository quickly
    • Debug issues in a shared environment
    • Contribute code that meets project standards
    • Collaborate effectively with other contributors

    I want to reach a point where contributing to open source feels natural, not intimidating. Everything else such as better Python practices, API design, DevOps exposure is a bonus, but that confidence is the main goal.

  • Just for fun: If you could instantly become a world-class expert in any one non-technical skill or hobby, what would it be and why?

    If I could instantly become world-class at one non-technical skill, it would be public speaking and storytelling.

    I’ve realized that being a great engineer isn’t just about writing good code—it’s also about explaining ideas clearly, pitching projects, and communicating impact. Whether it’s presenting a project, leading a team, or even just explaining a bug, strong communication makes a huge difference.

    Given that I’ve already worked on structuring presentations and technical explanations, mastering storytelling would amplify everything else I do.

19

Hi everyone! I’m Prosper Anyanwu, and I’m glad to be here.

I’ve been around open-source software for quite a while, both as a user and as someone who enjoys getting hands-on with the tools that power modern technology. On the OS side, I’ve worked with Ubuntu and Fedora, and over time I’ve building a good footing in the DevOps and infrastructure space. My toolkit there includes technologies like Docker, Kubernetes, Terraform, Ansible, Jenkins, Git, and Linux-based server environments, learning how systems are built, deployed, and maintained.

On the development side, I have working familiarity with JavaScript including Node.js and Astro.js as well as Python, where I’ve spent time with Django and data structures and algorithms. When it comes to APIs, I’m comfortable working with REST APIs and FastAPI for backend development. For databases, SQLite, PostgreSQL, and MongoDB are my go-to choices depending on what a project calls for.

All of that brought me naturally to Fedora, and more specifically to the #release-schedule-planner project. As someone who uses Linux server, I’m always looking for opportunities to go deeper into its distributions, to understand them better and, where I can, to help make them better. What drew me to this particular project is how well it aligns with my existing stack: it’s Python-based, involves backend logic, and sits at the intersection of infrastructure and software development which is exactly the kind of work I find most engaging.

Over the next few weeks, I’m hoping to learn a great deal. More than anything, I want to get a solid understanding of the backend logic that powers the release scheduling system how it currently works, what decisions shaped it, and where there’s room to take it further. I believe understanding the “why” behind a system is just as important as understanding the “how”, and that’s the lens I’m bringing into this.

Outside of tech, I do short-distance runs and play basketball as a way to unwind, and I love getting lost in a good movie.

Looking forward to learning from everyone here and contributing meaningfully to the project. :blush:

20

Hi everyone! :innocent:
I am Zainab Amin.

My open source Journey:
I first learn about open source from hacktoberfest back in college. Since then I have been exploring and learning about codebases on GitHub. This is my first time learning about FOSS projects.

Why I chose Fedora:
I chose Fedora because I have a prior knowledge about Fedora Linux OS. I wanted to learn more about the Fedora project and how these large projects are maintained. Luckily I found the project with my familiar techstack which helped me to understand codebase relatively easily.

My goal for this outreachy cohort is to:

  • to learn how big FOSS are maintained.
  • I want to learn how the current project will transform into production level code.
  • and I also want to make atleast one end to end contribution.

My wish
I want to become a highly skilled calligrapher. Why?
– because this is my fav. hobby (to relax). And everytime when I see an imperfect line or letter, the relaxation turns into disdain very quickly. :sweat_smile: :sweat_smile:

21

Hi, I’m Omar Agiez, an Applied Statistics graduate and a Python developer. I’m interested in Python open-source projects. I worked as a session lead at Udacity, teaching CS. Last year, I won a GenAI hackathon sponsored by AWS in North Africa.

  1. My Open Source journey:
    I’ve been actively involved in open source for 1.5 years now. I’ve contributed to projects like Wikimedia’s Scribe-Data and worked with a team on building the i18n-check Python package, which is published on PyPI. Through these experiences, I’ve worked on CI/CD pipelines, testing, and writing production-ready Python code. Open source has been a big part of how I’ve grown as an engineer, especially learning how to collaborate across distributed teams.
  2. My “Why”:
    I chose Fedora because it sits at the intersection of real-world impact and strong open-source values. The scale at which Fedora operates and its role in the Linux ecosystem makes it exciting to contribute to.
    The RamaLama/AI project specifically caught my attention because it combines two areas I’m deeply interested in: machine learning and systems-level problem solving. I’m particularly excited about applying ML in a practical infrastructure context, not just building models but integrating them into real workflows.
  3. My goals:
    The number one thing I want to gain from this experience is a deeper understanding of how large-scale open-source systems are designed and maintained especially within Fedora. I also want to improve my ability to contribute code that is not just functional, but maintainable, well-tested, and aligned with community standards.
  4. Just for fun:
    If I could instantly master a non-technical skill, it would be communication specifically the ability to explain complex ideas in a simple and engaging way. I think this skill is incredibly powerful because it helps bridge gaps between people with different backgrounds, making knowledge more accessible. Whether in teaching, writing, or collaborating in open source, being able to communicate clearly can have a huge impact.