Tag: packaging

Outreachy FHP week 7: Django, Docker, and fedora-messaging

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

Chameleon and the dragons

Below 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.

About conference

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 reading

Fedora meetup at Pune – March 2018

Long 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.

  • 15 Attendees were present including college students.
  • Ompragash welcomed all the attendees and had a short introduction from everyone. He delivered his first talk “Telling the Fedora Story”, in this he explained how Fedora project started.
  • Parag explained different ways to contribute in Fedora in his talk. He kept on answering queries in between, it was engaging session.

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 © 2019 Fedora Community Blog

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

Theme by Anders NorenUp ↑