View Full Version : Five Things in Fedora This Week

9th May 2014, 06:53 PM
Source: Fedora This Week (http://fedoramagazine.org/five-things-in-fedora-this-week-2014-05-06/) from Fedora Magazine

Fedora is a big project, and it’s hard to follow it all. This series highlights interesting happenings in five different areas every week. It isn’t comprehensive news coverage — just quick summaries with links to each. Here are the five things for May 6th, 2014:

Add Your Art to Fedora
Every Fedora release ships with a collection of non-default desktop wallpaper, provided by (and selected bynuancier-f21!) the Fedora community. On his blog, Fedora Design Team member Sirko Kemter announces that the artwork submission period for Fedora 21 is now ope (http://karl-tux-stadt.de/ktuxs/?p=4579)n. Entries must be licensed under a liberal open content license and meet some basic technical and content requirements (https://apps.fedoraproject.org/nuancier/contribute/). The deadline is August 16th, but it never hurts to start creating early.

Both submissions and voting are handled by Nuancier (https://apps.fedoraproject.org/nuancier/), a web application dedicated to the task. You can see last year’s results (https://apps.fedoraproject.org/nuancier/results/1/), too!

LinuxFest Northwest
The 15th annual LinuxFest Northwest (http://www.linuxfestnorthwest.org/) was held last week in (as it always is) Bellingham, Washington. Fedora was well-represented, of course. Jeff Sandys provides a brief blog report on the event (http://alg0rhythm.livejournal.com/8885.html), with a title implying more to come. Also worth watching is Bryan Lunduke’s annual “Linux Sucks (https://www.youtube.com/watch?v=5pOxlazS3zs)” report. Make sure to stick around for the second half — Fedora comes out rather well overall, despite the talk’s tongue-in-cheek title.

Fedora Regional Budgets
Fedora Ambassadors (https://fedoraproject.org/wiki/Ambassadors) are the outreach arm of the project — volunteers who spread the word of our collective greatness. Often, this is through organizing and attending events, and of course that takes money for travel, lodging, swag, and so on. Curious how this breaks down? Jiří Eischmann (a member of FAmSCo (https://fedoraproject.org/wiki/Fedora_Ambassadors_Steering_Committee), the Fedora Ambassadors Steering Committee) has a blog post reviewing the (just completed) Fiscal Year 2014 Regional Budgets (http://eischmann.wordpress.com/2014/04/30/fedora-regional-budgets-in-fy2014/).

Fedora.next QA Test Plans
Fedora’s Quality Assurance (https://fedoraproject.org/wiki/QA) team has been working with the various new Fedora Working Groups (see this article series (http://fedoramagazine.org/fedora-present-and-future-a-fedora-next-2014-update-part-i-why/) if you haven’t been following along) to create plans for testing the different products envisioned in the brave new world of Fedora 21 and beyond. At yesterday’s QA meeting (https://lists.fedoraproject.org/pipermail/test/2014-May/121261.html) (May 5), Adam Williamson, Ankur Sinha, and Mike Ruckman discussed draft plan documents for Server (https://fedoraproject.org/wiki/User:Adamwill/Draft_Server_test_outline), Workstation (https://fedoraproject.org/wiki/User:Ankursinha/Workstation_test_outline), and Cloud (https://fedoraproject.org/wiki/User:Roshi/QA/Cloud_Docs), and Adam is planning to put the three together and come up with an idea of what overall test coverage looks like.

Sound interesting to you? Take a look at the Join QA (https://fedoraproject.org/wiki/QA/Join) wiki page, or if you’re especially interested in a particular area, the corresponding Special Interest Group.

Fedora Dockerfiles Collection
You’ve probably heard of Docker (http://docker.io/) by now docker— containers have gained huge traction as an attractive alternative to full virtualization, and Docker may be the buzziest container-related technology of all. It provides a simple command-line tool for fetching special images and launching them as application containers, where each gets a special view of the system where it appears to be the only thing running — the process is isolated from the rest of the system.

Docker containers bring along their entire runtime, so each image is its own little Fedora (or, of course, other Linux system — CentOS or Ubuntu or whatever, if you want). And these images are created on top of a base image using a recipe called a Dockerfile. (It’s something like an RPM spec file or a kickstart script, if you’re familiar with those.) Fedora contributor Scott Collier maintains a collection of examples named, simply enough, fedora-dockerfiles, and this week he notes that there’s a new version (http://www.colliernotes.com/2014/05/new-fedora-dockerfiles-package-is-out.html). This contains examples including the Apache httpd webserver, PostgreSQL database, and many more… even a ready-to-go WordPress installation.

Scott also has quick instructions on building and running images from these Dockerfiles in an earlier blog post (http://www.colliernotes.com/2014/03/new-package-fedora-dockerfiles-is-now.html). It’s pretty simple, really — which is the appeal. Oh, and be aware that we are mostly talking about server applications here, not desktop apps (although containers are a big topic there too, and it’ll be interesting to see how the ideas come together).

9th May 2014, 09:23 PM
I really need to try out docker.

9th May 2014, 10:58 PM
Add Your Art to Fedora Been there, tried that. Didn't get the T-shirt.

Also worth watching is Bryan Lunduke’s annual “Linux Sucks” report.Not a big fan of this clod. I don't give two hoots in a hot place if there were kids in the audience or not. That sort of language is never called for in a public forum. <..:dis:..>

14th May 2014, 07:15 PM
Original link: Posted in Fedora Magazine (http://fedoramagazine.org/five-things-in-fedora-this-week-2014-05-13/)

Fedora is a big project, and it’s hard to follow it all. This series highlights interesting happenings in five different areas every week. It isn’t comprehensive news coverage — just quick summaries with links to each. Here are the five things for May 13th, 2014:

Pidora 2014: Fedora 20 for the Raspberry Pi

I was going to put this at the top of the list last week, and somehow missed it when it came to actually writing things up, so this is actually last week’s news. But it’s pretty cool, so here it is at the top of this week.

The Raspberry Pi is a very cheap (starting somewhere around $25) credit-card-sized computer. Unfortunately, Fedora doesn’t work on it without some modifications. But, fortunately, thospidora-logo-500pxe modifications have been made! The Centre for Development of Open Technology at Seneca College in Toronto produces a Fedora Remix called Pidora, specifically tailored for the Raspberry Pi. (A “remix” is different from a “spin” or other variants of Fedora because it is produced separately from the project itself and can contain software that isn’t in the official distribution.)

This project has just released its fourth version, Pidora 2014. This is based on Fedora 20, so you get all of the benefits of the new Fedora release, plus some specific improvements, including better performance, firstboot configuration tailored for the Raspberry Pi, enhancements for “headless” mode where no monitor is available, and more.
Big Data: Running Apache Hadoop in Docker on Fedora

Apache Hadoop is an open source software framework for processing big data sets. Like, really big data — it powers Yahoo’s search engine, and Facebook has a Hadoop cluster that was 100 petabytes two years ago. Of course, you can use it for smaller projects, and Robert Radi has written a nice little series of posts on getting started with Hadoop using Fedora and Docker, covering

Building Images,
Running Images,
Why It Works, and
Issues and Limitations.

Definitely worth a read if you’re curious about modern data processing, and the last part presents some interesting problems waiting to be solved.

Preview of Bodhi 2, the new Fedora updates feedback mechanism

One of the most important jobs in Fedora is testing package updates before they’re released to the general public. This makes sure that fixes actually work, and that they don’t introduce new problems. (As always, the help wanted sign is out!)

After testers check a package, they use a tool called Bodhi to provide feedback to package maintainers, who use this information to decide whether the update is good to go, either manually or through a preset threshold of positive reports. This system has served us pretty well, but has some pain points. Fedora hackers Luke Macken and Ralph Bean have been working on an update (creatively named Bodhi 2.0), and this week Ralph presents a video demonstrating one of the improvements, a more fine-grained feedback system, which allows testers to list what exactly was tested and which bugs are fixed, rather than just a big “up” or “down”.

Ralph notes that there is a Fedora Activity Day (“FAD”) focusing on Bodhi 2 and Tasktron (our upcoming QA automation system) in June, and a lot of progress should be made on both — great news for both the people directly involved in QA and all the rest of us who benefit from their labor.

Running Vagrant on Fedora with Libvirt

Vagrant is a tool for creating and managing virtual machine images containing software development environments. It’s particularly popular in the DevOps world. It’s also a thing we’ve been missing from the Fedora world, but the situation is getting better. James, from The Technical Blog of James, has an article about getting Vagrant running on Fedora.

Thanks to James for the clear, straightforward How-To. It ends with a call for help — it’d be great to have the mentioned vagrant-libvirt plugin packaged in in the distro, making it even easier for end-users. See some discussion in the comments there. And also see this ticket requesting an official Fedora Vagrant Base Box — so many great ways to get involved here.

Fedora Magazine Authors Wanted

Speaking of ways to get involved: we’re looking for people interested in writing for Fedora Magazine (the blog where I’m posting these articles, if you happen to be reading this somewhere else). Doesn’t need to be a big production number, but it’d be great to have a few more regularly-occurring features. If you might be interested, don’t be shy — join us in Fedora Marketing and we’ll get you what you need to get started.

15th May 2014, 01:58 AM
Threads merged.

15th May 2014, 02:07 AM
I did make it to Linux Fest NW a few weeks ago. There was a Fedora booth with a "One Laptop Per Child" focus. The Jupiter Broadcasting people were there. Got a few stickers. Oh, LibreOffice was there as well.

Oh, the desktop on the OLPC was Sugar which works pretty well cause OLPC was designed for children.

15th May 2014, 02:09 AM
As discussed with Bob via PM, edited thread title to be generic and keep all "Five things in Fedora this week" entries in this thread.

20th May 2014, 11:13 PM
Reposted from

Fedora is a big project, and it’s hard to follow it all. This series
highlights interesting happenings in five different areas every week. It
isn’t comprehensive news coverage — just quick summaries with links to
each. Here are the five things for May 20th, 2014:

Fedora Project Leader Robyn Bergeron announces her retirement

Robyn Bergeron has been the Fedora Project Leader since early 2012,
leading us through the F17, F18, F19, and F20 releases. I'll keep this
from becoming a eulogy, since in her retirement announcement, she
promises to stick around even after passing the FPL torch. But, thanks
to Robyn for many excellent things over the past two years, including
introducing the idea of reinventing FUDCon as Flock, championing Cloud,
Big Data, and DevOps as *actual important things* beyond the buzzwords,
and generally being awesome and supportive and above all deeply
committed to the community.

* http://robyn.io/2014/05/19/thanks-to-you-im-much-obliged/

FUDCon APAC 2014 in Beijing

Fedora's main planning and development conference is Flock, (this year,
in Prague in August), but we also have a number of "FUDCons" worldwide.
That stands for Fedora User and Developer Conference, and yes, it's a
little bit of a joke over the reference to Fear, Uncertainty, and Doubt
(we are against that... *con* to FUD, if you will). It's okay, you
don't all have to laugh at once.

Anyway, the important thing is that FUDCon Beijing 2014 is happening
this weekend. The schedule is posted on the wiki, and registration is
open. Read more in an earlier Fedora Magazine article, if you missed it
last week.

* http://flocktofedora.org/
* https://fedoraproject.org/wiki/FUDCon:Beijing_2014
* https://fedoraproject.org/wiki/FUDCon:Beijing_2014#Schedule
* http://2014-gf.eventdove.com/event/4394/page/11138
* http://fedoramagazine.org/fudcon-beijing-2014-featuring-richard-stallman/

Fedora Package Database, version 2

Fedora contributor Ryan Lerch scooped me on this one, posting an
article about this tool has been updated to a new version, called
`pkgdb2`. (The "Version 1.7" you see at that link is because it's
version 1.7 of the *rewrite*, following a grand tradition of confusing
software numbering schemes.)

This tool is primarily for Fedora packagers, but can also be useful to
other contributors or advanced users, because it's an easy way to see
who is responsible for software you're interested in, or to see what
packages a particular contributor takes care of. For example, you can
see the (small) list of packages I own.

* http://fedoramagazine.org/new-packagedb-now-available-for-fedora-packager%20this%20morning.%20The%20Fedora%20Packag e%20Database](https://admin.fedoraproject.org/pkgdb/
* https://admin.fedoraproject.org/pkgdb/packager/mattdm/

Help with release notes for Fedora 21

Perhaps you're one of the brave souls running Rawhide, Fedora's
development tree, or are otherwise involved in testing or developing
packages for the Fedora 21 release. Pete Travis from Documentation team
recently put out a call to testers to help with the release notes by
helping them track interesting things which should be documented. As he
notes, just mentioning these quietly to yourself doesn't help, but there
are a number of very easy things which *will*. You don't even need to
write anything — just point at what's needed.

* https://fedoraproject.org/wiki/Releases/Rawhide
* https://lists.fedoraproject.org/pipermail/test/2014-May/121319.html

CoreOS vs. Project Atomic: A Review

Major Hayden has an interesting blog post comparing CoreOS and Project
Atomic, basically from a systems administrator's perspective. (I talked
about Fedora Atomic in a 5tFTW post last month.) Major's review is
evenhanded and fair, but since this is a *Fedora* news post, I'm going
to tip a little bit towards bits we have in Fedora and pick out this
nice quote:

> There’s a helpful GUI called cockpit that gives you a great status
> readout on all of your connected servers. It lacks some functionality
> in the container and gear management arena, but it’s very useful for a
> pre-release application. One of the best features is the ability to
> open a console for your containers right there in the web browser. I
> find it to be more intuitive and more useful than more mature Docker
> GUIs like shipyard.

* http://major.io/2014/05/13/coreos-vs-project-atomic-a-review/
* https://coreos.com/
* http://www.projectatomic.io/
* http://fedoramagazine.org/five-things-in-fedora-this-week-2014-04-22/
* https://fedoraproject.org/wiki/Changes/CockpitManagementConsole
* http://shipyard-project.com/

21st May 2014, 12:06 AM
Fedora Project Leader Robyn Bergeron announces her retirement Hmmmm.

Okay. May her next endeavour be fully commensurate with her skills and talents, and may she be as completely successful as her temperament and vision can make her. <..:thumb:..>

28th May 2014, 12:05 PM
Reposter from http://fedoramagazine.org/five-things-in-fedora-this-week-2014-05-27/

Fedora is a big project, and it’s hard to follow it all. This series
highlights interesting happenings in five different areas every week.
It isn’t comprehensive news coverage — just quick summaries with links
to each. Here are the five things for May 27th, 2014:

Flock Schedule!

Flock is Fedora’s annual contributor conference, held this year in
Prague on August 6th through 9th. The schedule is now up on sched.org.
The organizers reserve the right to make tweaks as needed, but this
should mostly be the final schedule.

Last year’s conference was amazing, and I think this year will be even
better. There are a lot of great talks, hackfests, and workshops
planned over a busy four days, with a vibrant “hallway track” and fun
social events (yet to be detailed). In general, we will get a lot of
real planning and solid work done, all built on top of Fedora’s
“Friendship” foundation. If you’re a Fedora contributor and not sure if
you should come, *you should*. Register now at the Flock site.

Thanks to everyone who proposed talks and to everyone who voted on
those proposals. And thanks to Flock organizers Josh Boyer, Tom
Callaway, and Ruth Suehle, who used those votes as the primary source
for the difficult jigsaw puzzle that is putting together the schedule.
Thanks also to Miro Hrončok and Jiri Eischmann for working out venue

* http://flocktofedora.org/
* http://flock2014.sched.org/grid/

Fedora 21 Schedule Reminder

Speaking of schedules… as we get to the end of May, it seems like a
good time to give a reminder of the Fedora 21 schedule. The summer is
going to go fast! So, a refresher:

- **June 6:** *Mass Rebuild.* This means that Release Engineering
will cause every package in the distribution to be rebuilt from
source, with the newest compilers and toolchains. Package
maintainers need to be prepared to fix any problems that are
exposed. (Packages that don’t build and aren’t updated will
eventually be dropped from the distribution.)

- **July 8:** *Change Freeze* and *Branch from Rawhide*. The first of
these means that any official change proposals for F21 need to be
a) substantially complete and in a testable state and b) enabled by
default (if that’s the plan for that change). We have a rather
large change set planned for this release, and many of those
changes involve big new Fedora.next ideas. The second means that
Fedora 21 will become a distinct repository from Rawhide, our
rolling development tree. That means that any changes packagers
make that are intended for F21 will go through the normal package
updates process — and it means that testers can decide if they want
to divert their systems to the upcoming release, or to keep on
Rawhide to follow the bleeding edge of what will eventually become
the release *after* next.

- **July 22:** *Alpha Change Deadline* and *Software String Freeze*.
The change deadline basically means that except for accepted fixes,
everything that’s going to land in the alpha release should be
there already. And the string freeze means that packages for which
Fedora is the upstream should stop making user-visible changes so
that translators have time to work.

- **August 5:** *Alpha Release*. The Fedora 21 Dress Rehearsal — we’ll
get real picture of what the upcoming release will look like (and

- **August 26:** *Beta Change Deadline*, *Changes 100% Complete*, and
*Software Translation Deadline*. Similar to the deadlines for
Alpha, but more so. Proposed changes which are off-track at this
point may need to be scaled back or delayed until the next release.

- **September 9:** *Beta Release*. Everything will be shaping up, and
we’ll be more concerned with polish than development. If you have
an idea for a big change at this point, that’s awesome — the
Rawhide development tree continues to be open for business so
progress can continue.

- **September 30:** *Final Change Deadline*. All the last changes
should be in.

- **October 14:** ***Fedora 21 Final Release!*** Fedora Cloud, Fedora
Server, Fedora Workstation, and all the spins and the rest will go
into the world.

All of these dates are officially expressed as “no earlier than”. As
always the schedule may… flex… a little bit, but generally we aim to
actually hit these targets. That gives us just 20 weeks from now — mark
your calendars!

* http://fedoraproject.org/wiki/Releases/21/Schedule
* https://fedoraproject.org/wiki/Releases/21/ChangeSet
* http://fedoraproject.org/wiki/Package_update_HOWTO
* https://fedoraproject.org/wiki/L10N

Fedora.next Preliminary Branding

The Fedora Design Team is working on a plan for presentation of the
three different Fedora products we’ll be releasing this fall as part of
the Fedora.next initiative. Each of these will need their own logo, but
they also need a coherent look that ties them together as part of the
overall Fedora Project. Fedora Contributor Máirín Duffy kicks off the
process with some starting-point designs, which you can see at read
about at her blog.

What do you think? What ideas do you have?

* https://fedoraproject.org/wiki/Design
* http://fedoramagazine.org/fedora-present-and-future-a-fedora-next-2014-update-part-ii-whats-happening/
* http://blog.linuxgrrl.com/2014/05/22/fedora-next-brand-concept-1/

Fedora 21 Test Planning

Those three products will also need testing; that’s one of the reasons
the schedule is longer than the typical six months. Fedora Quality
Assurance “Community Monkey” Adam Williamson wrote a draft test plan
for Fedora 21 in general, outlining different areas of work and
responsibilities. If you’re interested in helping (or just curious),
read Adam’s message about this draft and join the conversation on the
Fedora Test Mailing List.

* https://fedoraproject.org/wiki/User:Adamwill/Draft_Fedora_21_test_plan
* https://lists.fedoraproject.org/pipermail/test/2014-May/121396.html
* https://lists.fedoraproject.org/pipermail/test/

Help Wanted (Soon) for Software Collection Package Reviews

Software Collections is a way to package software into RPMs which sit
in `/opt`, outside of the main part of the distribution. The main use
case of Software Collections (SCLs, for short) is to have a stack of
software which moves at a different speed from the distro proper — in
RHEL or CentOS, that usually means faster, but in Fedora, it could be a
way to provide consistent runtime environments across multiple

Specifically, we’re planning to have a Ruby 1.9.3 with Rails 3.2.8 SCL
in Fedora 21 as a first experiment, led by Fedora contributor Marcela
Mašláňová. Since F21 will have Ruby 2.1.x with Rails 4.1, this will let
users with code that isn’t ready for the new version update to newer
Fedora — but port their own code on their own schedule

The Fedora Packaging Committee has been working on draft guidelines,
and the remaining big hurdle is that the 60-some new packages will need
to go through the standard review process. The plan is to make this as
painless as possible, by organizing an online activity day to crank
through them. If you’ve done some package reviews (and ideally if you
know Ruby), and are interested in helping, watch the Environments and
Stacks mailing list for more soon.

* https://www.softwarecollections.org/
* https://fedoraproject.org/wiki/Changes/Ruby193_in_SCL
* https://fedoraproject.org/wiki/User:Toshio/SCL_Guidelines_%28draft%29
* https://lists.fedoraproject.org/mailman/listinfo/env-and-stacks

4th June 2014, 03:33 PM
Reposted from

Fedora is a big project, and it’s hard to follow it all. This series
highlights interesting happenings in five different areas every week.
It isn’t comprehensive news coverage — just quick summaries with links
to each. Here are the five things for June 3rd, 2014:

New Fedora Project Leader

So, there is a new Fedora Project Leader, and, despite inital rumors,
it’s not an anthropomorphic hotdog. I'm excited to be able to say: it's
me. I wrote a blog post about it: First Thoughts as Fedora Project

Right now, the practical consequence is that this is going to be a more
terse 5tFTW than usual. (I’m sure there will be more consequences

And, of course, thanks again to outgoing FPL Robyn Bergeron! Don't miss
her "parting thoughts" blog post.

* http://fedoramagazine.org/is-this-the-new-fedora-project-leader/
* http://fedoramagazine.org/first-thoughts-as-fedora-project-leader/
* http://robyn.io/2014/06/03/new-fpl/

Bodhi2 and Taskotron Activity Day

Bodhi is Fedora’s system for pushing out security and bugfix updates.
Taskotron is our new system for QA automation. The former is getting a
much-needed update and integration with the latter at the Bodhi2 and
Taskotron Fedora Activity Days going on right now in Denver, Colorado.
Fedora Infrastructure Lead Kevin Fenzi has reports from day 1 and day

* http://bodhi.fedoraproject.org
* https://fedoraproject.org/wiki/Taskotron
* http://fedoraproject.org/wiki/FAD_Bodhi2_Taskotron_2014
* http://www.scrye.com/wordpress/nirik/2014/06/01/bodhi2-taskotron-fad-day-1/
* http://www.scrye.com/wordpress/nirik/2014/06/03/bodhi2-taskotron-fad-day-2/

Fedora Server / CentOS SLS

As part of the new community-based direction, the CentOS project has
several new Special Interest Groups around Storage, Virtualization,
and so on. There is a proposal to create a Simplified Linux Server
(SLS) SIG. This has the mission to deliver

> [...] turnkey CentOS-based solutions that are managed via a web and/or
> REST-based interface. The focus is on taking the various application
> silos and providing a cohesive solution to simplify deployment and
> maintenance.

This has a lot of overlap with the upcoming Fedora Server, and the
groups working on each had a joint meeting to discuss common goals and
sharing effort. It looks like this will be a productive collaboration
for users and developers of both distros.

* http://wiki.centos.org/SpecialInterestGroup
* http://wiki.centos.org/SpecialInterestGroup/SLS]%20(not%20to%20be%20confused,%20of%20course,%20wit h%201992's%20Softlanding%20Linux%20System](http://en.wikipedia.org/wiki/Softlanding_Linux_System
* http://fedoraproject.org/wiki/Server
* https://lists.fedoraproject.org/pipermail/server/2014-May/001135.html

Fedora Regional Community Index

This one isn’t new, but it’s one of those things that’s been around for
a while which many people may not be aware of: the Region-Specific
Fedora Websites index, at http://fedoracommunity.org/. This site lists
different domains and subdomains with local resources all around the
world. Check it out to find groups in your area which you might not
have been aware of, or just to see what Fedora looks like around the

* http://fedoracommunity.org/

FUDCon Beijing 2014 Reports

FUDCon APAC (Asia-Pacific) was held last month in Beijing, China.
Reports are in from Aditya Patawari, Ankur Sinha, Somvannda Kong,
Nitesh Narayan Lal, Jiří Eischmann, and Robert Mayr.

* http://devel.adityapatawari.com/2014/05/fudcon-beijing-day-1/
* http://ankursinha.in/blog/2014/05/29/fudcon-beijing-day-1-and-day-0/
* http://fedoracambodia.wordpress.com/2014/05/31/my-first-trip-of-fedora-project-to-fudcon-beijing-china/
* http://niteshnarayanlal.blogspot.com/2014/05/fudcon-beijing-2014-kick-off.html
* http://eischmann.wordpress.com/2014/06/02/fudcon-apac-2014-in-beijing/
* http://morefedora.blogspot.com/2014/06/fudcon-apac-beijing-day-0-robert-mayr.html

18th June 2014, 06:39 PM
Reposted from <http://fedoramagazine.org/5tftw-2014-06-17/>.

Fedora is a big project, and it’s hard to follow it all. This series
highlights interesting happenings in five different areas every week.
It isn’t comprehensive news coverage — just quick summaries with links
to each. Here are the five things for June 17th, 2014:

Fedora 21 Is Not Delayed

It might seem a bit funny to report on something that’s *not*
happening, but this got picked up by some of the tech press so I
thought it best to clarify the actual situation. Short version: we’re
*not* currently planning any delay from the established target of
October 14th, 2014.

Longer version: the Fedora Server Working Group is writing new code
which will provide a programmatic interface (an API) for provisioning
servers with certain Server Roles. This doesn’t compete with existing
config management tools like Puppet, Chef, or Ansible — it provides a
framework that they (or the new Cockpit web GUI) can talk to. That’s
taking a little bit longer than planned, especially because new input
from the CentOS Simple Linux Server SIG was incorporated. However, at
last week’s meeting, FESCo (the Fedora Engineering Steering Committee,
which manages the overall schedule) decided to allow *just* this Server
Role Deployment Framework]framework] to land a little late in the
Fedora Alpha schedule, but with no delay to the rest of the project or
change to the overall F21 schedule.

* http://fedoraproject.org/wiki/Server
* http://fedoraserver-wgblog.rhcloud.com/primary-goals-for-fedora-server-in-fedora-21/
* https://fedoraproject.org/wiki/Changes/FrameworkForServerRoleDeployment
* http://cockpit-project.org/
* http://wiki.centos.org/SpecialInterestGroup/SLS
* http://meetbot.fedoraproject.org/fedora-meeting/2014-06-11/fesco.2014-06-11-17.02.html

Bill Nottingham Steps Down From FESCo; Kyle McMartin Steps Up

Long-time and almost omnipresent Fedora contributor Bill Nottingham
has started a new day job at open source config-management company
Ansible, and resigned his Fedora Engineering Steering Committee
seat in order to be able to focus on that. Our election policy
states that open seats are offered to previous runners-up, which
means Kyle McMartin is our newest FESCo member (although not, by
any means new to Fedora). Thank you Bill for years of work on
Fedora in FESCo and elsewhere, and welcome Kyle!

P.S. We use Ansible quite heavily in Fedora Infrastructure. Also:
Former Fedora Project Leader Greg DeKoenigsberg is also joining
Ansible, which already boasts quite the slate of former Red Hatters and
Fedora contributors. I’m looking forward to further collaboration
across our open source projects.

* http://fedoraproject.org/wiki/User:Notting
* https://twitter.com/ansible/status/478518891665432576
* http://fedoraproject.org/wiki/Development/SteeringCommittee/Nominations#Kyle_McMartin_.28kylem.29
* http://www.slideshare.net/AdityaPatawari/ansible-33223245
* http://www.ansible.com/management-team

DNF as Yum Replacement, Continued

Last week, I wrote about a proposal to replace Fedora’s Yum package
manager with DNF. That proposal — targeting next year’s Fedora 22,
_not_ Fedora 21 this fall — is now officially on the table for
discussion. That discussion continues on the Fedora devel mailing list.
Although there are several long threads, it looks like people are
generally open to the idea and advantages of the new code, but there
are differing opinions on whether DNF should keep that name or become
“Yum 4” — or even take a new generic name like `package`. Feel free to
join in, although please remember to be constructive and to follow the
Fedora Project Code of Conduct (which, basically, boils down to “be
excellent to each other”.

* http://fedoramagazine.org/5tftw-2014-06-10/
* http://yum.baseurl.org/
* http://dnf.baseurl.org/
* https://fedorahosted.org/fesco/ticket/1312
* https://lists.fedoraproject.org/pipermail/devel/2014-June/thread.html
* https://fedoraproject.org/code-of-conduct

Coming Soon to libguestfs: Smart Log Reading

The systemd journal brings a lot of useful features, including
structured log formats and reliable connection of messages to the
services they came from. But, its binary log format can be less
convenient when you’re not working *on* the system where the logs

This is often the case when using libguestfs, an almost-magically-
powerful tool for working with virtual machine disk images. Developer
Richard W.M. Jones blogs about a new feature: virt-log. This command
automatically does the right thing with several different guest system
log possibilities, including understanding the journald format, knowing
that Debian-based systems use `/var/log/syslog` instead of our
`/var/log/messages`, and in the future will even read the Microsoft
Windows Event Log.

* http://0pointer.de/blog/projects/journalctl.html
* http://libguestfs.org/
* http://rwmj.wordpress.com/2014/06/14/new-in-libguestfs-virt-log/

Add an Infobox to Your Fedora Wiki User Page

Our wiki serves many purposes (maybe too many!), but one of the the
most useful is providing simple autobiographical and contact
information for contributors. A neat little thing I stumbled across
this week is the Infobox template, defined and documented at
<https://fedoraproject.org/wiki/Template:Infobox_user>. Follow these
instructions and add the template to your page for a clean, consistent
presentation of your Fedora-relevant details.

As a bonus, display your Fedora Badges with `{{ #fedorabadges: fasname }}`

* https://fedoraproject.org/wiki/Template:Infobox_user
* https://badges.fedoraproject.org/
* http://fedoramagazine.org/wp-content/uploads/2014/06/badges.png
* https://badges.fedoraproject.org/user/mattdm

18th June 2014, 08:23 PM
DNF, huh. <..http://forums.fedoraforum.org//forum/images/icons/icon6.gif..>

Can't say I'm any too pleased about that ... but I'll wait until it fully raises its misshapen head before I summarily decide to hate it on general principles.

But I will start work on a database of suitable invectives, curses and outright slanders. Just in case they're needed later. <..:p..>

20th June 2014, 02:52 AM
Dan, so far dnf works fine for me. There are rough ends, sure. But, it's not bad at all - and I feel it's faster than yum.

20th June 2014, 04:08 AM
That may very well be, but in the meantime, this is, after all, a user powered forum community, and therefore there are some time honored traditions which must be observed. There are conclusions to be jumped to, assumptions to be made, evidence to be ignored ... knees to jerk, howls to wail, cloth to rend, woes to cry ... tables to be angrily pounded.

In the face of ever advancing progress ... the fine art of pitching a hide-bound fit is not to be dismissed so lightly!

Come on, man! You know these things.


20th June 2014, 02:13 PM
That may very well be, but in the meantime, this is, after all, a user powered forum community, and therefore there are some time honored traditions which must be observed. There are conclusions to be jumped to, assumptions to be made, evidence to be ignored ... knees to jerk, howls to wail, cloth to rend, woes to cry ... tables to be angrily pounded.

In the face of ever advancing progress ... the fine art of pitching a hide-bound fit is not to be dismissed so lightly!

Come on, man! You know these things.


Indeed. :)

Ha ha! :rtfl:

20th June 2014, 03:57 PM
DNF - to me that stands for did not finish in the Motorsport world so probably not the best acronym to use.

So personally I would prefer it to be called yum. The added bonus being the commands won't change? Anyhow as long as it works I really don't care what it is called.

The one thing I am not keen on at present with yum (or could be caused by yumex) is the waiting for multiple downloads of server and update information for one transaction. This is what happens:

1. start yumex and it automatically downloads updated information to find what is available on the repos.
2. select the updates and/or new programs to install.
3. go to apply the changes and the program downloads the same repository information again. sometimes this information is larger than the rpms/delta rpms that need downloading.

So unless there is a change in the 30 odd seconds between selecting what is going to be installed I can't see how this is necessary.

I very much like the deltarpm system, that works brilliantly. Try installing a fresh copy of Linux Mint 17 MATE and compare the update process. Using yumex and delta rpms Fedora MATE wins hands down for speed and total bandwidth usage.

1st July 2014, 11:48 PM
I missed this last week. Here is this week's Five Things in Fedora

Reposted from <http://fedoramagazine.org/5tftw-2014-07-01/>

Fedora is a big project, and it’s hard to follow it all. This series
highlights interesting happenings in five different areas every week.
It isn’t comprehensive news coverage — just quick summaries with links
to each. Here are the five things for July 1st, 2014:

What Does “Winning” Mean for Fedora?

The Fedora Project Board is exploring the question “What is success for
Fedora?”, brought to the board-discuss mailing list by Board member
Josh Boyer. This is a public mailing list for all Fedora community
members, and we welcome your thoughtful contributions to the

* http://fedoraproject.org/wiki/Board
* https://lists.fedoraproject.org/pipermail/board-discuss/2014-July/012613.html
* https://admin.fedoraproject.org/mailman/listinfo/board-discuss

FESCo Summer Election

We are holding an election for three open seats on FESCo, the Fedora
Engineering Steering Committee. More information on Fedora Magazine,
in an announcement I sent this morning, and of course directly on
the Fedora Project wiki.

* http://fedoramagazine.org/election-announced-for-the-fedora-engineering-steering-commitee/
* https://lists.fedoraproject.org/pipermail/devel-announce/2014-July/001413.html
* http://fedoraproject.org/wiki/Elections

Workstation To-Do List

Fedora Workstation Working Group member Christian Schaller recently
posted a message about the group’s new Tasklist wiki page, which
details current and future tasks for the subproject, and explains how
you can get involved (or simply better follow what’s currently going

* https://lists.fedoraproject.org/pipermail/desktop/2014-June/009929.html
* http://fedoraproject.org/wiki/Workstation/Tasklist

Google Summer of Code Project: Bugspad

Last week, I highlighted Google Summer of Code work in Fedora on the
Waartaa chat system. This week, take a look at Fedora contributor
Mayank Jha’s work on Bugspad, a new bug tracker focused on speed and
aimed at replacing Bugzilla. In last Thursday’s Fedora Infrastructure
meeting, Mayank notes that at test instance will be deployed on our
internal private cloud and that he’s currently testing it with a
million (auto-generated) bugs (the kind of load we need to handle in
real-world Fedora).

* http://fedoramagazine.org/5tftw-2014-06-24/
* https://www.google-melange.com/gsoc/homepage/google/gsoc2014
* https://www.waartaa.com/
* https://fedoraproject.org/wiki/User:Mjnovice
* http://bugspad.org/
* http://meetbot.fedoraproject.org/fedora-meeting/2014-06-26/infrastructure.2014-06-26-18.00.log.html

EPEL in CentOS 7

And finally, a quick note from our sibling project, CentOS.

EPEL (“Extra Packages for Enterprise Linux”) is a long-standing Fedora
subproject which targets Red Hat Enterprise Linux and CentOS, providing
a wide universe of packages that aren’t provided by Red Hat. Many of
these packages are very close to their Fedora equivalents, and it’s a
common entry-point to Fedora for sysadmins and other folks who work in
the enterprise world as their day job.

CentOS developer Jim Perrin notes on the centos-devel mailing list
that, as of the upcoming CentOS 7 release, the `epel-release` package
will be included in the centos-extras repository (although not
installed by default). That means to get Fedora-produced EPEL packages
on CentOS, you’ll just have to `yum install epel-release` and then
install whatever you like.

* http://lists.centos.org/pipermail/centos-devel/2014-June/011110.html

9th July 2014, 02:30 AM
Reposted from <http://fedoramagazine.org/5tftw-2014-07-08/>.

Fedora is a big project, and it’s hard to follow it all. This series
highlights interesting happenings in five different areas every week.
It isn’t comprehensive news coverage — just quick summaries with links
to each. Here are the five things for July 8th, 2014:

DNF and Protected Packages (and Mailing Lists)

DNF is a next-generation package manager, scheduled to replace Yum in
Fedora 22. Last week, there was a lengthy Fedora devel list thread,
largely centered on DNF’s lack of a “protected packages” feature, which
keeps users from inadvertently removing certain core software (like the
package manager itself, or the running kernel).

On Thursday, DNF version 0.5.3 was announced, along with Core DNF
Plugins 0.1.1, which contains a new protected_packages plugin. So,
there we go.

It think it’s worth noting, though, that this a good example of how
mailing list discussions often fail us. There were a lot of messages,
but almost no new information in hundreds of posts — it’s mostly people
going back and forth, feeling like they’re not being heard or listened
to. And then, many people feeling frustrated and driven out of
meaningful discourse by the noise.

That’s a dynamic we need to change. If something is really important
and you feel that your view isn't counted, there are other channels by
which issues can be raised — file a ticket with FESCo or the Fedora
Project Board]FESCo], for example. Or, tell the FPL that you have a
concern! Everyone *should* have a voice in Fedora, even though
sometimes decisions have to be made even when not everyone agrees.
Mailing list wars (even when the flames are smouldering rather than
explosive) just aren’t the best way.

I know I’ve been as guilty of this as anyone over the years, but we need
to get out of the Someone Is Wrong on the Internet trap — arguments
aren’t won by quantity, and it isn’t necessary to have the last word in
order to be heard. And, most importantly, try to steer the quality of
discourse *up* with each post. This is the Fedora Code of Conduct,
but more importantly, it’s our Friendship foundation.

* http://dnf.baseurl.org/
* http://yum.baseurl.org/
* https://lists.fedoraproject.org/pipermail/devel/2014-June/199808.html
* http://dnf.baseurl.org/2014/07/03/dnf-0-5-3-and-core-dnf-plugins-0-1-1-released/
* http://akozumpl.github.io/dnf-plugins-core/protected_packages.html
* https://fedorahosted.org/fesco/
* https://fedorahosted.org/board/
* http://fedoraproject.org/wiki/Project_Leader
* http://xkcd.com/386/
* https://fedoraproject.org/code-of-conduct
* https://fedoraproject.org/wiki/Foundations

Fedora 21 Branch and Changes Freeze

Today is the big day when the Fedora 21 package tree branches from the
always-latest “Rawhide” development tree. This branched F21 tree will
stabilize and become the Alpha, Beta, and — in October — Fedora 21 final

So, this is a big milestone — with a lot of work ahead! A lot of that
work will be in Quality Assurance, and we could use your help on that
front. There are lot of small and easy tasks which together make a big
difference — see the Fedora QA wiki page for ways to get involved.
(One simple thing you can do, even if you are not a a package
maintainer, is to create a test case for a package that you’re
familiar with.)

This is also the Changes Freeze — new features for Fedora 21 should
be substantially finished and testable at this point. Note that this
doesn’t mean that all changes are now blocked, just that the various
items in the F21 Change Set should be ready for testing. The next
big milestone in the schedule is the Alpha Change Deadline (which
*is* a “code freeze”) on July 22nd, in preparation for an Alpha release
on August 5th, just before Flock in Prague.

* https://fedoraproject.org/wiki/QA
* https://fedoraproject.org/wiki/QA:SOP_test_case_creation
* https://fedoraproject.org/wiki/Changes_Freeze_Policy
* http://fedoraproject.org/wiki/Releases/21/ChangeSet
* http://fedoraproject.org/wiki/Releases/21/Schedule
* http://flocktofedora.com/

FESCo Summer Election in Progress

FESCo is holding a special election to fill three empty seats. There
are five nominees, and there will be an IRC “townhall” meeting
sometime from July 10-15, with voting open for a week after that.

* http://fedoramagazine.org/election-announced-for-the-fedora-engineering-steering-commitee/
* http://fedoraproject.org/wiki/Development/SteeringCommittee/Nominations

Python 3.5 Nightly Builds

Fedora packager Miro Hrončok annouced that he and Slavek Kabrda have a
new Copr repository with nightly builds of development version of
Python 3. Fedora tries to be leading edge without “bleeding”, which
sometimes means we don’t move as fast as everyone would like. The
Copr system is an easy way to build and maintain personal RPM
repositories outside of the general package collection — so if you want
more risk, you can take it.

This repository uses the Software Collections technology to install
python35 into a parallel tree, so it won’t mess up your main system. You
*can* eat your cake and have it too!

* http://copr.fedoraproject.org/
* https://lists.fedoraproject.org/pipermail/devel/2014-July/200791.html
* https://www.softwarecollections.org/

Documentation Beats Are On!

Fedora Docs team member Petr Bokoc announces that it’s time to start
working on the Fedora 21 release notes. This is another great way to get
involved in Fedora or to branch out into a new area – see the wiki page
on beat writing for more.

* https://lists.fedoraproject.org/pipermail/docs/2014-July/015657.html
* https://fedoraproject.org/wiki/Docs_Project_workflow_-_beat_writing

*Remembering Seth*

One year ago, Seth Vidal was killed by a driver who struck his bicycle
from behind. One year later, it’s still hard to imagine Fedora without
Seth. We miss you.

24th July 2014, 03:48 AM
Fedora is a big project, and it’s hard to follow it all. This series highlights interesting happenings in five different areas every week. It isn’t comprehensive news coverage — just quick summaries with links to each. Here are the five things for July 22nd, 2014:

FESCo Election

The special election for FESCo (the Fedora Engineering Steering Committee) has concluded. New FESCo members are Josh Boyer, Kalev Lember, and Tomas Hozza. Since these seats are filling various vacancies, they aren’t for the normal two-release term. Since Josh lead the results, he will fill the spot which goes through next spring’s Fedora 22 release, and the others through this fall’s F21. Congratulations and welcome to Josh, Kalev, and Tomas; and thanks to outgoing members Bill Nottingham, Toshio Kurotami, and Peter Jones for all of your hard work on FESCo.

Fedora 21 Schedule Adjustment

This is nominally a Tuesday update, but since I’m late anyway, I’m going to slip in some important Wednesday news. In today’s FESCo meeting, we decided to push back the Fedora 21 by three weeks. The revised schedule is now online, with the alpha release on August 26th, beta on September 30th, and the “gold” release on November 4th.

Why so long? Is everything horribly broken? No — it’s just that we’re running into Flock, our big annual development and planning conference. Some issues putting together the test candidates mean that we do need to slip by at least a week, and given that, we didn’t want to be putting together the alpha release right on top of the conference. This way, our packaging, quality assurance, and release engineering people can participate fully in Flock rather than spending most of the time worrying about their release responsibilities.

Flock Behind the Scenes

And speaking of Flock, Fedora contributor Jiří Eischmann has put together a nice series of blog posts about what’s going on behind the scenes to put Flock together. Great reading for all of you who are planning on attending, and I think actually pretty interesting for everyone.

Flock: Behind the Scenes 1
Flock: Behind the Scenes 2
Flock: Behind the Scenes 3

AppStream: An Easy Open Source Contribution

On her blog, Máirín Duffy writes about a low-barrier opportunity to contribute to free and open source software by participating in a volunteer drive for AppStream metadata. AppStream is simply a format for providing screenshots, icons, and user-friendly descriptions of software, and it’s used by software installation apps in Fedora such as

GNOME Software and Apper.

Contributing AppStream data doesn’t take any special technical knowledge — just a willingness to write about your favorite open source software, or to research and learn about new software.

Right now, only about a quarter of applications in Fedora ship this metadata, and we’d like to get that to almost 100% by the Fedora 21 release.

Participants will be awarded a special Fedora badge and will also be featured in a future article on Fedora Magazine!

Introduce yourself in the Join Fedora SIG

I’ve written about the Join Fedora SIG again, but this is a good time to mention it again. This special interest group works to make Fedora friendly to new contributors, and to help those contributors — possibly including you! — get up to speed. SIG member Ankur Sinha (a.k.a. FranciscoD) recently launched a thread for self-introductions — if you’ve been interested in helping but aren’t sure how, here’s a great place to say hello. And if you already are a Fedora contributor, there are a lot of new folks who could use some assistance.

So, sign up for the mailing list, or drop by #fedora-join on Freenode IRC for a friendly chat (with no complicated signup or obligation!)

3rd August 2014, 05:35 AM
Flock: Missed Registration? No problem!

Flock, Fedora’s big contributor conference, is just a week away, from August 6th to 9th in Prague. Registration closed a while ago, but we’ve gotten several inquiries about the possibility of late sign-up. The answer is: You are still very welcome. Just show up! You won’t get a badge, lunch, or a t-shirt, but those are really the main reasons we ask for preregistration. If you missed your chance for that but want to come anyway, please do!

Unsigned Packages in Fedora 21?

An important notice from Rawhide Watch — a blog devoted to those of us who run Fedora’s bleeding-edge development branch — but about Fedora 21. Earlier this month, F21 split from Rawhide, in order to go through the stabilization process that leads to the alpha, beta, and (coming this fall) official final release. Even though the alpha isn’t ready yet, many testers are trying out the new branch already, and have discovered that some packages are not yet cryptographically signed.

As Adam Williamson explains on in the blog post, ) this is perfectly normal. Until the alpha “freeze” (currently slated for August 12th, after Flock), whenever a packager builds a package, it goes right into the tree, rather than going through the normal updates process. Once we get to that freeze, though, the normal updates system will be activated and package updates will need to be pushed just as they are for stable releases.

Fedora Security Team

Fedora contributor Eric “Sparks” Christensen announced the new Fedora Security Team. Fedora has had a Security Special Interest Group for a long time, and of course emergency security response and everything else you’d expect, but in general, the security update process put the burden on the maintainers of each individual software package in Fedora. The new community team will serve as a new resource for those packagers, working with each package’s upstream project to find the right fix — either a backported patch or identifying an updated version — and with the packager to help get these fixes into place and out to users.

Fedora Marketing

Meanwhile, the Fedora Marketing SIG held a meeting to discuss group organization and plans for the Fedora 21 release. Since Fedora 21 is going to be a little different from business as usual, with Fedora.next and the Cloud/Server/Workstation products, we’ve got a lot to think about and plan in order to best promote what we’re doing to the world. Check out the meeting minutes for details and join us on the mailing list if you’re interested in helping out.

Fedora Contributor Notifications

We have a system called fedmsg, the Fedora Infrastructure Message Bus. Many of the tools we use in Fedora send messages to this bus, including the Koji and Copr package build systems, the Fedora Wiki, question and answer site Ask Fedora, Fedora Badges, and more.

From the command line, you can yum install fedmsg and follow all activity with fedora-tail --really-pretty (or, of course, less pretty if you prefer). Or, you can use datagrepper to search historical data. Now, the Fedora Infrastructure team is working on Fedora Notifications, which can trigger e-mail or IRC alerts for messages from various apps which match your username or other criteria. Mobile phone app alerts are in the works too.