Fedora Project Community Archives – Fedora Community Blog

Category: Fedora Project Community (page 1 of 33)

All articles in this category are relevant to ALL teams and subgroups across the entire Fedora Project community.

Simplifying Package Submission Progress (8 July – 15 July) – GSoC ’25

Hi, I am Mayank Singh, welcome back to this blog series on the progress of the new package submission prototype, if you aren’t familiar with the project, feel free to check out the previous blogpost here.

Event Handling, Forgejo Support, and Source Management (July 8 – July 15)

This week was focused on the service’s forge and tackling the challenge of source management.

Migrating to Forgejo and Handling Events

Based on community feedback, advantages and assessing our requirements, I moved the service’s forge to Forgejo. This minimal, open-source alternative to GitHub and GitLab is simpler to self-host and has significantly smoothed out our testing process.

On the implementation front, I added support for parsing issue and push events in packit-service, which allow to support parsing commands from issue comments. That being done adding support for pull_request is only trivial now and have a solid understanding of packit-service‘s event model to trigger task execution.

Package Source Handling

I hit a technical dilemma when considering handling the case of packages with new dependencies in a single Pull Request and handle their sources. The workflow requires accessing the PR’s diff, resolving it into individual files, and submitting those sources to be built in COPR.

My initial solution to this problem was to create a dedicated organization in Forgejo where every new package would get its own repository to store its sources. However, my mentor advised against this model, we discussed and realized it would become too complex and non-intuitive to work with. Instead, he clarified the path forward to focus on simple packages for now and investigate how Packit already solves this by cloning the source repository.

What’s Next?

Enhancing Forgejo Integration: Implementing methods to allow the service to post comments and add reactions on Forgejo.
Implementing Source Fetching: Building the logic to fetch source files from Pull Requests for package builds.
Expanding Commands: Adding new commands and tasks to support this workflow.

Stay tuned, more things to share next week 🙂

Simplifying Fedora Package Submission Progress (27 June – 14 July) – GSoC ’25

July 14, 2025 / Mayank Singh / 0 Comments

Hi everyone, I am Mayank Singh, currently working on a new service for simplifying the Fedora Package Submission Process, if you’d like to know more check my previous post here.

Diving Deep into Packit Service

(27 June – 8 July):

I began working on the packit-service codebase as the foundation for our project. The first goal was to prototype the user flow by creating new APIs and handlers for functionalities like detecting new packages and linting.

Pretty early on, I hit a roadblock during a test run. When the service was deployed to listen for GitHub events, it wouldn’t reject any incoming events sent through the tunnel to the local deployment. After a lot of digging, I traced the issue to the Apache configuration in the mod_wsgi-express server. This server, responsible for serving the Flask-RESTx endpoints, was misbehaving and causing all the trouble.

Another hiccup was that the service was too heavy for my system to run locally in an OpenShift environment with GitHub. My mentor stepped in and suggested a helpful workaround, disable the unnecessary services for our use case and use GitLab instead in plain docker containers, as it’s much easier to spin up and test locally. Reported a few other problems in the deployment process for development regarding Bitwarden for secrets.

With those issues resolved, I went ahead and trimming the parts of the packit-service codebase that weren’t needed for onboarding new packages. This helped me better understand its event model and the use of Celery in task execution.

This week was mostly about reusing the existing packit-service codebase and resolving issues.

What’s Next?

With the hard parts of setup and architecture done, the next steps would be to:

Add new API endpoints and corresponding event types for task handling

Integrate the current setup with COPR for builds.

Begin work on testing and validation workflows

Stay tuned for more updates in the next blog post!

From Open Source User to Fedora Contributor

July 10, 2025 / Antony Nyagah / 0 Comments

This is the story of how I became a contributor on the Fedora Release Schedule Planner application hosted on Codeberg.

I started my open-source journey when I got my first laptop. It was old and slow, but I needed it for school, so I started looking into how to fix this.

Fedora DEI Outreachy Intern – My first month Recap 🎊

July 1, 2025 / Cornelius Emase / 0 Comments

Hey everyone!

It’s already been a month, I can’t imagine how time flies so fast, busy time?? Flock, Fedora DEI and Documentation workshop?? All in one month.

As a Fedora Outreachy intern, my first month has been packed with learning and contributions. This blog shares what I worked on and how I learned to navigate open source communities.

Simplifying Fedora Package Submission Progress Report – GSoC ’25

July 1, 2025 / Mayank Singh / 0 Comments

Student: Mayank Singh

Fedora Account: manky201

About Project

Hi everyone, I’m working on building a service to make it easier for packagers to submit new packages to Fedora, improving upon and staying in line with the current submission process. My main focus is to automate away trivial tasks, provide fast and clear feedback, and tightly integrate with Git-based workflows that developers are familiar with.

GSOC Summer 2025 – ExplainMyLogs

June 10, 2025 / Ruhika Sai Tanvi Pentakota / 0 Comments

AI-Powered Natural Language Log Analyzer

This blog post is a brief documentation of my journey for Google Summer Of Code – 2025 with the Fedora Community.

Strategy 2028 Update

June 4, 2025 / Matthew Miller / 0 Comments

As we head into Flock, It’s time again to talk about #strategy2028 — our high-level plan for the next few years.

Since it’s been a while since I’ve given an update, I’m going to start at the top. That way, If this is new to you, or if you’ve forgotten all about it, you don’t need to go sifting through history for a refresher. If you’ve been following along for a while, you may want to skip down to the “Process section”, or if you just want to get to the practical stuff, all the way down to “Right Now”.

A banner image with a black background, dotted with various stars, much like a galaxy system. Four rockets with colors of the Fedora Four Foundations leave a colored trail behind them that overlaps, as the rockets propel toward the right-side of the image in lockstep. White text is overlaid on the image, reading "The Fedora Project community." This image is often used with Fedora elections.

Image by Ryan Lerch. CC BY-SA 4.0

F42 Elections Results

June 3, 2025 / amoloney / 1 Comment

The Fedora Linux 42 election results are in! After one of our most hotly contested elections recently, we can now share the results. Thank you to all of our candidates, and congratulations to our newly elected members of Fedora Council, Fedora Mindshare, FESCo and EPEL Steering Committee.

Fedora 43 Wallpaper Under Way

June 3, 2025 / madelinepeck / 3 Comments

We are currently working on the Fedora 43 Wallpaper and wanted to update the community while also looking for contributors!

Each wallpaper is inspired by someone in STEM in history with the letter in the alphabet we’re on. We are currently on the letter R, and voted here with the winner resulting in Sally Ride.

Announcing the Fedora 42 Release Party – May 29, 2025

May 22, 2025 / amoloney / 3 Comments

Join us on Thursday, May 29 2025 for the Fedora 42 release party! Free registration is now open for the event, and you can find an early draft of the event schedule on the wiki page. We will be hosting the event in a dedicated matrix room, which registration is required to gain access, and will stream a mix of live and pre-recorded short sessions via Restream from 1300 UTC – 1600 UTC.

Read on for more information, although that intro might cover most of it 🙂