The Kubernetes team has released Kubernetes v1.29, which is the version that will be included in Fedora 40. There are four important changes to Kubernetes in Fedora associated with this release that may merit attention.
Continue reading
The Kubernetes team has released Kubernetes v1.29, which is the version that will be included in Fedora 40. There are four important changes to Kubernetes in Fedora associated with this release that may merit attention.
Continue readingPackage reviews are an important part of how Fedora delivers well-built RPMs. When one contributor wants to add a new package, another packager has to check it first. It’s how we all hold each other to the high standard we’ve set for ourselves. Of course, that means to add a new package to the repos, you first have to find someone to do the review. Last week, I added a new way to do that: the Package Review Swaps category on Fedora Discussion. Huge thanks to Felix Kaechele for the idea and initial process design.
Continue readingEd. note: The hackfest was rescheduled to 17 May.
Fedora Legal will be conducting a SPDX identifier hackfest on April 26, 2023 during a four hour block. Please join us on Wednesday, May 17, 2023 between 10:00 AM EDT / 1400 UTC / 16:00 CEST and 14:00 EDT / 1800 UTC / 20:00 (CEST) on Google Meet.
Continue readingHow do we – as in, the developers and package maintainers who are working on Fedora Linux – make sure people actually know about all the cool stuff we’re doing? That’s the question at the heart of previous discussions on the “devel” mailing list (How do we announce new packages?) and on discourse (Idea for collecting “Cool New Features / Cool New Packages” article ideas).
As it turns out, the answer to that question is: “If what you’ve worked on isn’t big or noteworthy enough, then there’s no place for you”. That’s not good, and it’s why I started working on “Feature Spotlight”.
Continue readingThis week, the Fedora Packager Dashboard left the testing period and is available for wide use. Why should you care about it? And what is it about?
Fedora Packager Dashboard is a web application designed to make the lives of Fedora Packagers easier. It aggregates and shows all the relevant data for package maintainers on one page, structured, searchable and filterable. You’ll see things like current bug reports, updates, issues regarding all your packages at one place, without needing to spend time reading your emails and/or monitoring dozens of different services one by one. Caring about your packages will be easier and less time-consuming with Fedora Packager Dashboard.
Continue readingSome time ago, we initiated a discussion on the devel list if dist-git is a good place to work. This thread received a great amount of wonderful feedback from you and we are so grateful for every message—it demonstrates the passion of the Fedora community.
If you are not familiar with how packages are being maintained in Fedora or what dist-git is, let me give you a quick summary. Every Fedora package has a dedicated git repository—a dist-git repository. It contains files needed to compile the sources and produce a binary RPM package which you can install on your Fedora Linux system. As an example, you can look at firefox dist-git repository.
This blog post is a followup to the discussion and lays out a concrete plan of what we want to do.
Continue readingThis is part of a recurring series between May – August 2019 on the Community Blog about Fedora Happiness Packets. These posts are published as part of a series of prompts from the Outreachy program.
From Outreachy.org: The theme for this week is “Modifying Expectations”. Outreachy mentors and interns start the internship with a specific set of project goals. However, usually those goals need to be modified, and that’s perfectly fine! Delays to projects happen. Maybe your project turned out to be more complicated than you or your mentor anticipated. Maybe you needed to learn some concepts before you could tackle project tasks. Maybe the community documention wasn’t up-to-date or was wrong. These are all perfectly valid reasons for projects to be a bit behind schedule, as long as you’ve been working full-time on the project. In fact, free and open source contributors have to deal with these kinds of issues all the time. Projects often seem simple until you start working on them. Project timelines are ususally a very optimistic view of what could happen if everything goes exactly as planned. It often doesn’t, but people still make optimistic plans. Modifying your project timeline to set more realistic goals is a skill all contributors need to learn.
Your goal for this week’s blog post is to write a report about your progress on your project. Talk about what you accomplished so far. Talk about what goals too more time than expected. The blog post should also detail what your modified goals for the second half of the internship is.
Continue readingBelow you will find my report from openSUSE Conference 2019 (oSC19) where I gave a talk Rust packaging: Cross-distro collaboration done right. Also I have decided to go some parts back on bicycle, so on the the bottom you will find story about that.
The openSUSE Conference is the annual openSUSE community event that brings people from around the world together to meet and collaborate. The organized talks, workshops, and BoF sessions provide a framework around more casual meet ups and hack sessions. A party here and there provides the time to relax and have fun, making connections on a more personal level. The conference was held in Germany, in the very nice city — and origin of SUSE — Nuremberg (Nürnberg).
Continue readingLong time we did not had any meetup at Pune, Maharashtra, India, so we decided to get started again. Details about this meetup are available at Fedora Wiki page.
Planning for meetup started 1 month before. Initially Ompragash proposed to have meetup.com account for Fedora Pune to get more awareness. Later dropped this plan, since this is not only Fedora Pune level topic but applicable for all Fedora events.
Event started well in time.
GNOME Software developer Richard Hughes recently e-mailed the Fedora developers mailing requesting Fedora package maintainers to update their AppData files to include age ratings using OARS.
“The latest feature we want to support upstream is age classifications
for games. I’ve asked all the maintainers listed in the various
upstream AppData files (using the update contact email address) to
generate some OARS metadata and add it to the.appdata.xmlfile, but
of course some AppData files do not have any contact details and so
they got missed. I’m including this email here as I know some AppData
files are included in the various downstream spec files by Fedora
packagers. Generating metadata is really as simple as visiting
https://odrs.gnome.org/oars then answering about 20 questions with
multiple choice answers, then pasting the output inside the
<component> tag.Using the <content_rating> tag means we can show games with an
appropriate age rating depending on the country of the end user. If
you have any comments about the questions on the OARS page please do
let me know. Before the pitchforks start being sharpened it’s an
anti-goal of the whole system to in any way filter the output of
search results dependent on age. The provided metadata is only used in
an informational way.”
If your package ships an AppData file, please consider updating it. If you have any queries about the addition or OARS, please discuss it on the Fedora developers mailing list.
Copyright © 2024 Fedora Community Blog
This work is licensed under a Creative Commons Attribution 4.0 International License.
Theme by Anders Noren — Up ↑
Recent Comments