Tag: news for Fedora packagers

Collecting ideas for “Feature Spotlight” articles

How 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 reading

Fedora Packager Dashboard

This 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 reading

Interviews on the Fedora Infrastructure Hackathon 2018

This week, the Fedora Infrastructure team is convening for a Hackathon from April 9-13 at Fredericksburg, VA. You can also attend/partake remotely in #fedora-admin from 09:30 UTC-5 daily. The hackathon is intended to help the team leap ahead for several critical Fedora and CentOS initiatives. We interviewed members of the Fedora Infrastructure team to ask what the goals for the hackathon are and why it is needed.

Continue reading

AppData content ratings for games shipped in Fedora

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.xml file, 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.

Globalization improvements in Fedora 24

Fedora 24 remained a happening release from the Globalization contributors’ side. There were a number of events including Test Days, translation sprints, bug triaging, and many result-oriented meetings. This post provides outcomes and results from this dedicated efforts from over 50 contributors.

Localization

User Interface

Translated Fedora user interfaces available for the following languages with percentage of translations in brackets.

Continue reading

Another way to push package updates to stable in Fedora Bodhi

This article was originally published on Trishna Guha’s blog,


Bodhi is a web application that facilates the process of publishing package updates of Fedora. Once a package is submitted to Bodhi it goes through various stages: Pending, Testing, Stable, Obsolete. The details can be found here Package States.Fedora Bodhi Update System

There exist two types of policies in Bodhi, using any of them maintainers can publish their package updates (Pushing updates to Stable from Testing). Updates Policy documentation: https://fedoraproject.org/wiki/Updates_Policy

Updates Policy in Bodhi:

  • Manually push to stable based on time :
    • Auto-karma is disabled.
    • Update spends 14 days in testing.
    • Maintainer pushes the update to stable manually.
  • Automatic push  to stable based on karma :
    • Auto-karma is enabled.
    • Stable Karma threshold is reached.
    • The update is pushed to stable automatically.

Continue reading

Copyright © 2024 Fedora Community Blog

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

Theme by Anders NorenUp ↑