Category: Development (page 1 of 5)

All articles in this category are related to the various Development teams in the Fedora Project, such as package maintainers, quality assurance, and more. https://fedoraproject.org/wiki/Development

Elections Retrospective, January 2017

The results are in! The Fedora Elections for the Fedora 25 release cycle of FESCo, FAmSCo and the Council concluded on Tuesday, January 17th. The results are posted on the Fedora Voting Application and announced on the mailing lists. You can also find the full list of winning candidates below. I would also like to share some interesting statistics in this January 2017 Elections Retrospective.

January 2017 Elections Retrospective Report

In this election cycle, the voter turnout is above its average level. It is great news as it shows increased interest of the Fedora people in community affairs.

This election cycle was hit by some planning issues as we were running the Elections over Christmas 2016 period. At the beginning I was worrying about the turnout due to the Christmas, but fortunately this was odd and we are more than good from this point of view.

Continue reading

FESCo Elections: Interview with Justin Forbes (jforbes)

Fedora Engineering Steering Council badge, awarded after Fedora Elections - read the Interviews to learn more about candidates

Fedora Engineering Steering Council badge

This is a part of the FESCo Elections Interviews series. Voting is open to all Fedora contributors. The voting period starts on Tuesday, January 10th and closes promptly at 23:59:59 UTC on Monday, January 16th. Please read the responses from candidates and make your choices carefully. Feel free to ask questions to the candidates here (preferred) or elsewhere!

Interview with Justin Forbes (jforbes)

  • Fedora Account: jforbes
  • IRCjforbes (found in #fedora-kernel, #fedora-devel, #fedora-cloud)
  • Fedora User Wiki Page

Continue reading

FESCo Elections: Interview with Adam Miller (maxamillion)

Fedora Engineering Steering Council badge, awarded after Fedora Elections - read the Interviews to learn more about candidates

Fedora Engineering Steering Council badge

This is a part of the FESCo Elections Interviews series. Voting is open to all Fedora contributors. The voting period starts on Tuesday, January 10th and closes promptly at 23:59:59 UTC on Monday, January 16th. Please read the responses from candidates and make your choices carefully. Feel free to ask questions to the candidates here (preferred) or elsewhere!

Interview with Adam Miller (maxamillion)

  • Fedora Account: maxamillion
  • IRC: maxamillion (found in #fedora-devel, #fedora-releng, #fedora-cloud)
  • Fedora User Wiki Page

Continue reading

FESCo Elections: Interview with Kevin Fenzi (kevin)

Fedora Engineering Steering Council badge, awarded after Fedora Elections - read the Interviews to learn more about candidates

Fedora Engineering Steering Council badge

This is a part of the FESCo Elections Interviews series. Voting is open to all Fedora contributors. The voting period starts on Tuesday, January 10th and closes promptly at 23:59:59 UTC on Monday, January 16th. Please read the responses from candidates and make your choices carefully. Feel free to ask questions to the candidates here (preferred) or elsewhere!

Interview with Kevin Fenzi (kevin)

Continue reading

Fedora Docker Layered image build service now available

Announcing: Fedora Docker Layered Image Build Service is GO!

It is with great pleasure that the Fedora Project Announces the availability of the Fedora Docker Layered Image Build Service to the Fedora Contributor Community!

With this announcement we open the availability of the Docker Layered Image Build Service for the Docker Layered Images. The Fedora Cloud WG has been the primary maintainers of this project on GitHub. But now the service is available in dist-git as official components of Fedora. From there we will extend an invitation to all Fedora Contributors to maintain Docker Layered Image Containers for official release by the Fedora Project. Currently this effort is to enable the Fedora Cloud/Atomic Working Group goals of targeting Fedora Atomic Host as a primary deliverable to power the future of Cloud. This is also to enable the Fedora Modularity work be delivered as Containers in the future as Fedora becomes fundamentally more modular in nature.

Continue reading

Base Runtime and the Generational Core

A Quick Primer on Modularity

lego_chicago_city_view_2001Modularity (formerly, Modularization) is an ongoing initiative in Fedora to resolve the issue of divergent, occasionally conflicting lifecycles of different components. A module provides functionality (such as a web server) and includes well-integrated and well-tested components (such as Apache httpd and the libraries on which it depends). It can be deployed into production in various ways: as “classic” RPM packages or a container image, and is updated as a whole. Different modules can emphasize new features, stability, security, etc. differently.

Modules differ from traditional packaging in certain important ways. Perhaps most importantly, they allow us to separate internal implementation details from the exposed interfaces of the module. Historically in Fedora, if a packager wanted to deliver a new web application, that would also often mean that they needed to package and carry the framework or other libraries used by that application. This tended to be a double-edged sword: on the one hand, those libraries were now available for anyone to pick up and use in Fedora. However, in many cases, this meant that the primary maintainer of that package might actually have no specific knowledge or understanding of it except that its lack would mean their application didn’t work. This can be a problem if a person is carrying around a library for the use of a single helper function and don’t want to be responsible for issues in the rest of the library.

Continue reading

FOSS Wave: CMR Institute of Technology, Bengaluru, India

On 18 October 2016, we organized a workshop at the CMR Institute of Technology in Bengaluru, India. In the workshop, we covered topics of free and open source software (FOSS), Fedora, and git. Before talking about the event, I would like to thank a few people whose presence made this event a huge success. I would like to thank

  • Anirban Ghosh and Arun Teja for organizing the event at CMR IT.
  • All the attendees who came in a huge number and made this event a grand success.
  • Sumantro Mukherjee for being an amazing mentor and guiding us through the event.

Continue reading

FOSS Wave: Indore, India

FOSS Wave arrives at another destination! On 24th September 2016, we conducted an event at the Indian Institute of Technology in Indore, India. The event was a joint effort of Mozilla Indore community and FOSS Wave.

The main agenda of our event was:

  • Introduction to open source
  • Web development
  • Internet of Things (IoT)
  • Web-powered Virtual Reality (Web VR)

Continue reading

Outreachy with Fedora, Fall 2016

What is Outreachy?

GNOME Outreachy is a global program that offers historically underrepresented people of gender and race stipends to write code for several participating FOSS projects . Inspired by Google Summer Of Code, Outreachy offers participants hands-on internships for contributing to open source projects.

In 2016, the Outreachy internship dates are from December 6, 2016 to March 6, 2017. Participants work remotely from home while getting guidance from an assigned mentor and collaborating within their project’s community.

Why open source and Fedora?

Free and Open Source Software (FOSS) is software that gives the user the freedom to use, share, study, and improve it. FOSS contributors believe that this is the best way to develop software because it benefits society, creates a fun collaborative community around a project, and allows anyone to make creative changes that reach many people.

Fedora is participating in Outreachy 2016, with a goal to welcome underrepresented minorities to contribute to the project.  Fedora mentors Outreachy interns and helps them get a hands-on experience with developing for an open source project.

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.

Olderposts

Copyright © 2017 Fedora Community Blog

Theme by Anders NorenUp ↑