I’m frequently building GTK+. Since I am using Fedora Atomic Workstation now, i have to figure out how to do GTK+ development in this new environment. GTK+ may be a good example for the big middle ground of things that are not desktop applications, but also not part of the OS itself.

In essence, when a software developer contributes code to a project (i.e., the Work under the license), he or she becomes a Contributor. Under the above term, Contributors are granting permission to use any of their patents that may read on their contribution. This provides peace of mind to users since the Contributor would likely be prevented from pursuing patent royalties from any users of the software covering that contribution to the project.

Complexities arise when the software developer contributes code that is not claimed by any of the Contributor's patents by itself, but only when combined with the Apache 2.0 licensed open source program to which the contribution was made (i.e., the Work under the license). Thus, the Contributor owning such a patent could pursue patent royalties against a user of that revised Work. The authors of the Apache 2.0 license were forward thinking and account for this scenario. Section 3 states that the license applies to "patent claims licensable by such Contributor that are necessarily infringed... by a combination of their Contribution(s) with the Work to which such Contributions was submitted."

For the last three years or so, Red Hat has been on a collision course with CoreOS, with both firms aiming to grow their respective Kubernetes platform. On Jan. 30, the competition between the two firms ended, with CoreOS agreeing to be acquired by Red Hat in a $250 million deal.

Fedora developers are now discussing the possibility of naming a release manager each development cycle as a person in charge of wrangling together each release and seeing that the "Rawhide" development state is kept in better condition. Who knows, this also might actually help Fedora's longtime trouble of delivering releases on time.

Fedora Project Leader Matthew Miller started the mailing list discussion today about whether they should have a release manager each release cycle. His latest motivation for thinking about this is they haven't had a successful nightly compose of the latest Fedora Rawhide development state in about two weeks. While Red Hat employs QA and release engineering folks working on Fedora, their development tip isn't always kept in a release-able state unlike Ubuntu daily ISOs and some other Linux distributions.

Elisa said it will be demonstrating a cloud-ready mobile network automation system for telecommunication operators at Mobile World Congress in Barcelona from 26 February to 01 March. It will showcase Elisa SON (Self-Organising Networks) there with Red Hat. Elisa SON uses closed loop automation and tailored algorithms that can double user data throughput on an existing network.

Elisa offers unlimited data plans to subscribers, so its networks carry a high volume of mobile data. For this reason, it has focused on optimising network performance and getting maximum value out of its existing equipment.

David Egts, chief technologist for Red Hat public sector has some words of wisdom for Federal managers seeking ways to move from legacy applications to more agile environments: modernization is not just about adopting new technologies and practices, it is about what happens to the old ones.

Three application migration patterns are emerging as government agencies and commercial businesses attempt to modernize aging, mission-critical applications: Lift and Shift, Augment with New Layers, and Rewrite, Egts said. He noted that Red Hat’s PaaS Community of Practice leader, expounded on these approaches in a whitepaper, Making Old Applications New Again.

So, which approach is best? “There is no single right answer,” Egts said. It depends on the application, the business, and contextual factors, as well as what stage the applications are in their life cycle. However, for the best results, agencies should partner “with system integrators or vendors that can cover all three migrations, and join you in this journey,” Egts advised.

The kernel team is working on final integration for kernel 4.15. This version was just recently released, and will arrive soon in Fedora. This version has many security fixes included. As a result, the Fedora kernel and QA teams have organized a test day for Thursday, February 22. Refer to the wiki page for links to the test images you’ll need to participate.

FOSDEM is one of the largest open source conferences in the world, with over 8000 participants. As many developers gather not just from Europe but from all around the world, there are a number of pre- and post conferences timed to happen before and after FOSDEM. This year before FOSDEM, I also participated at the CentOS Dojo, a whole-day event about CentOS.

The Open Brand Project is a collaborative effort to evolve our corporate logo and brand system. A cross-functional team of in-house designers collaborating with Pentagram, a well-known international design consultancy, will work together to simplify and modernize our logo.

In any fast moving environment, there are going to be a certain amount of myths and misperceptions that get communicated and spread around a community. This week, in Part 1 of a 2-part series, we take a look at some of the common and recent myths and misperceptions about containers and Kubernetes.

About 2.5 years ago I left Red Hat to join Linaro in a move that surprised even me for the first few months. I still work on the GNU toolchain with a glibc focus, but my focus changed considerably. I am no longer looking at the toolchain in its entirety (although I do that on my own time whenever I can, either as glibc release manager or reviewer); my focus is making glibc routines faster for one specific server microprocessor; no prizes for guessing which processor that is. I have read architecture manuals in the past to understand specific behaviours but this is the first time that I have had to pore through the entire manual and optimization guides and try and eek out the last cycle of performance from a chip.

Red Hat, Inc. (NYSE: RHT), the world's leading provider of open source solutions, today announced that Follett School Solutions, SIX Group, ZTE Corporation, and Elo are transforming their IT infrastructure and embracing DevOps methodologies by adopting Red Hat OpenShift Container Platform as their enterprise Kubernetes solution of choice. These organizations, spanning each region, are representative of how customers around the world are embracing Red Hat OpenShift, the industry’s most comprehensive Kubernetes platform.