News and updates for about the Fedora Project community that develops supports and promotes Fedora. For more information, and to download the Fedora OS head to Get Fedora. For general news about the Fedora OS, check out the Fedora Magazine

Page 2 of 72

Fedora program update: 2020-06

Here’s your report of what has happened in Fedora this week.

I have weekly office hours in #fedora-meeting-1. Drop by if you have any questions or comments about the schedule, Changes, elections, or anything else.

Continue reading

Contribute at the Fedora Test Week for Kernel 5.5

The kernel team is working on final integration for kernel 5.5. This version was just recently released, and will arrive soon in Fedora. As a result, the Fedora kernel and QA teams have organized a test week from Monday, February 10, 2020 through Monday, February 17, 2020. Refer to the wiki page for links to the test images you’ll need to participate. Read below for details.

Continue reading

Introducing: fedora-update-feedback

I was recently able to finally finish my Rust bindings for the Bodhi REST API. And since fedora-easy-karma is still unable to submit feedback from the terminal, I thought I could put the new Bodhi bindings to good use, and implement an alternative. Enter: fedora-update-feedback.

Continue reading

Call for Projects and Mentors – GSoC 2020

Fedora at Google Summer of Code 2020

Google Summer of Code is a global program focused on bringing more student developers into open source software development.
Students work with an open source organization on a 3 month programming project during their break from school.  In the previous year, Fedora had an awesome participation
and we would like to continue to be mentoring Org this year too.

Fedora needs your help!

Fedora is currently looking for mentors and projects, it’s very staright forward to propose yourself as a mentor and a project.
The project encourages mentors to come forward and propose project ideas by 2020-02-10. More details are given below.

How to Propose a Project?

If you want to mentor a specific project, think carefully about several things:

  • Do you have enough time to work on this with the student during the entire project.
    You will be helping someone else when they get stuck. You don’t want to become a blocker because you’re busy.
  • It is harder to find success when you are completely certain of how an idea needs to be implemented; finding a student with the skills and interest to implement a specific solution is a lot harder than finding a student with enough skills to respond to a use case need. Also, students learn more when they help design and guide the project. In other words, provide guidance and direction but let the student do some of the “driving.”
  • Where you can have looser ideas, you may be able to find a student who works as a sort-of intern who can implement a solution to a use case you have. In past experiences, students going after a use case are more likely to get somewhere with self-direction and support from you.
  • Who can help you?

Try to find a second mentor for the project.

If you’re interested in working with a student on a specific project you should post your idea to the Mentored Projects Issue Tracker. Your issue should be tagged GSoC and use the Google Summer of Code template. We strongly encourage you to find a second person to help with mentoring and to solicit feedback on your proposal

Can I be a Mentor Without a Project?

Yes! You can either:

Work with a student who brings an idea to your sub-project. This requires a different level of communication throughout the project, but can be the most rewarding.

Be a general mentor. This is a person who works with all students regardless of their project. To become a general mentor please open an issue in the Mentored Projects Issue Tracker offering your help. Please tag the issue with the GSoC tag.

Fedora program update: 2020-05

Here’s your report of what has happened in Fedora this week.

I hold weekly office hours in #fedora-meeting-1, but if you’ll be at FOSDEM or Copyleft Conf, you can catch me in person. The mass rebuild is underway. Here’s what to do if your build fails.



Open Source Summit NAAustin, TX, US22–24 Jun 2020closes 16 Feb

Help wanted

Upcoming meetings

  • FPgM office hours: 1400 UTC Wednesday in #fedora-meeting-1
  • Fedora Council: 1500 UTC Wednesday in #fedora-meeting-1


Fedora 32


  • 2020-02-11: Mass rebuild ends
  • 2020-02-11: Branch day
  • 2020-02-11: Code Complete (testable) deadline
  • 2020-02-25: 100% Code complete deadline
  • 2020-02-25: Beta freeze begins


Enable EarlyOOMSystem-WideReady for FESCo
Provide OpenType Bitmap FontsSelf-ContainedReady for FESCo
Additional buildroot to test x86-64 micro-architecture updateself-ContainedReady for FESCo
Reduce installation media size by improving the compression ratio of SquashFS filesystemSystem-WideReady for FESCo
Deprecate python-noseSelf-ContainedReady for FESCo
Update Haskell packages to Stackage LTS 14Self-ContainedReady for FESCo
Python3-rdiff-backupSelf-ContainedReady for FESCo
PostgreSQL 12Self-ContainedReady for FESCo
LTO by default for packagesSystem-WideDeferred to F33

Changes approved, rejected, or withdrawn will be removed from this table the next week. See the ChangeSet page for a full list of approved changes.

Fedora 33


Retire python26Self-ContainedAccepted
Retire python34Self-ContainedAccepted

Changes approved, rejected, or withdrawn will be removed from this table the next week. See the ChangeSet page for a full list of approved changes.

Fedora program update: 2020-04

Here’s your report of what has happened in Fedora this week.

I will not hold office hours next week due to travel, but if you’ll be at FOSDEM, you can catch me in person.

Continue reading

Tales from Google CodeIn’19

As you may know, Google CodeIn (GCI) is a global, online contest introducing teenagers to the world of open source development. With a wide variety of bite-sized tasks, it’s easy for beginners to jump in and get started no matter what skills they have.

Continue reading

Git Forge requirements

This document lays out a problem statement, requirements, and constraints according to the Open Decision Framework. The aim is to arrive at a transparent decision about the future of a git forge for the communities that represent the platforms that the Community Platform Engineering (CPE) team manages. Those communities are the CentOS and Fedora platforms and also include the Red Hat Enterprise Linux (RHEL) platform from a tooling and integration perspective. This document is the first in a series of documents capturing the conversation about the problems we face and driving the conversation to implement the decisions captured.

Continue reading

Fedora program update: 2020-03

Here’s your report of what has happened in Fedora this week.

I will not hold office hours next week due to travel, but if you’ll be at DevConf.CZ, you can catch me in person.

Continue reading

Let’s write a new vision statement for Fedora

This is part one of a four-part series recapping the Fedora Council’s face-to-face meeting in November 2019.

A few years ago, the Fedora Council set out to update the project’s guiding statements. At the time, we were particularly focused on the mission statement, because we felt that what we had previously was too broad to be actionable. The result of that is:

Fedora creates an innovative platform for hardware, clouds, and containers that enables software developers and community members to build tailored solutions for their users.

… which we quite like. But, this focus has somewhat of a downside: it’s functional but not particularly inspiring. It talks about what we’re doing, but not much about the why. So, this year, we worked on a new vision statement to serve as the proverbial “banner on a hilltop” that we can use to rally our existing community and to attract new contributors.

Continue reading
« Older posts Newer posts »

Copyright © 2020 Fedora Community Blog

Creative Commons License
This work is licensed under a Creative Commons Attribution 4.0 International License.

Theme by Anders NorenUp ↑