Fedora Magazine http://fedoramagazine.org Fri, 04 Sep 2015 14:54:04 +0000 en-US hourly 1 http://wordpress.org/?v=4.2.2 Add power to your terminal with powerline http://fedoramagazine.org/add-power-terminal-powerline/ http://fedoramagazine.org/add-power-terminal-powerline/#comments Fri, 04 Sep 2015 08:35:12 +0000 http://fedoramagazine.org/?p=9761 Continue Reading →]]> A while ago, Fedora Magazine posted this interview with Rackspace architect Major Hayden where he mentioned the powerline utility. If you often use a terminal, you too might find powerline useful. It gives you helpful status information, and helps you stay organized.

For the shell

By default, the shell plugin gives you plenty of helpful data:

  • Login name
  • Local time
  • Current working directory or path. The path is condensed automatically when it grows longer than the terminal width.
  • The number of active background jobs
  • The hostname, when you connect via SSH to a remote system where powerline is installed

This saves you a lot of twiddling with your shell environment and complex scripting! To install the utility, open a terminal and run this command:

sudo dnf install powerline

The rest of these instructions assume you’re using Fedora’s standard bash shell. If you’re using a different shell, check out the documentation for tips.

Next, configure your bash shell to use powerline by default. Add the following snippet to your ~/.bashrc file:

if [ -f `which powerline-daemon` ]; then
  powerline-daemon -q
  . /usr/share/powerline/bash/powerline.sh

To activate the changes, open a new shell or terminal. You should have a terminal that looks like this:

Terminal with powerline running in the bash shell

Try changing directories. Watch how the “breadcrumb” prompt changes to show your current location. Very handy! You’ll also be able to see number of pending background jobs. And if powerline is installed on a remote system, the prompt includes the hostname when you connect via SSH.

For tmux

If you’re a command line junkie, you probably also know tmux. It allows you to split your terminal into many windows and panes, each containing its own session. But the tmux standard status line is not quite as interesting as what powerline provides by default:

  • Window information
  • System load
  • Time and date
  • Hostname, if you’re connected to a remote system via SSH

Therefore, let’s install the plugin:

sudo dnf install tmux-powerline

Now add this line to your ~/.tmux.conf file:

source "/usr/share/tmux/powerline.conf"

Next, remove or comment out any lines in your tmux configuration for status bar length or content. Examples of these settings are status-left, status-right, status-left-length, and status-right-length.

Your user configuration is stored in ~/.tmux.conf. If you don’t have one, copy an example from the web or /usr/share/doc/tmux/examples to ~/.tmux.conf, and then edit.

When you next start tmux, you should see the powerline status bar:

A tmux session with powerline running the status bar

For vim

If you use the vim editor, you’re also in luck. There’s a powerful plugin for vim, too. By default, it shows:

  • Operating mode (normal, insert, replace)
  • Current path and file name
  • Text encodings
  • Document and line positions

To install it, use this command:

sudo dnf install vim-plugin-powerline

Now add the following lines to your ~/.vimrc file:

python from powerline.vim import setup as powerline_setup
python powerline_setup()
python del powerline_setup
set laststatus=2
set t_Co=256

Now you can start vim and see a spiffy new status line:

Vim running with powerline status

Configuring powerline

No command line utility is complete without configuration options. The configuration in this case isn’t exactly simple, though; it requires you to edit JSON formatted files. But there’s a complete configuration guide available in the official documentation. And since the utility is written in Python, it’s eminently hackable.

When you hack the configuration, it’s usually to add, change, or remove segments. There are plenty of segments available, such as:

  • Content of environment variables
  • Version control system data (such as git branch and status!)
  • Weather
  • …and many more.

To change the status layout in an environment, you create or edit configuration files in your ~/.config/powerline/ folder. These configurations are stored as themes for each plugin. You can use the powerline-lint utility to check your configuration for parsing errors after making changes.

Some changes may require you to reload your session or possibly restart the daemon:

powerline-daemon --replace

Now you can enjoy more sophisticated status data in your favorite tools!

http://fedoramagazine.org/add-power-terminal-powerline/feed/ 5
F23 Cloud Base Test Day September 8th! http://fedoramagazine.org/f23-cloud-base-test-day-september-8th/ http://fedoramagazine.org/f23-cloud-base-test-day-september-8th/#comments Wed, 02 Sep 2015 12:43:27 +0000 http://fedoramagazine.org/?p=9841 Continue Reading →]]> Hey everyone! Fedora 23 has been baking in the oven. The Fedora Cloud WG has elected to do a temperature check on September 8th.

For this test day we are going to concentrate on the base image. We will have vagrant boxes (see this page for how to set up your machine), qcow images, raw images, and AWS EC2 images. In a later test day we will focus on the Atomic images and Docker images.

The landing page for the Fedora Cloud Base test day is here. If you’re available to test on the test day (or any other time) please go there and fill out your name and test results. Also, don’t forget that you can use some of our new projects testcloud (copr link) and/or Tunir to aid in testing.

Happy testing and we hope to see you on test day!

http://fedoramagazine.org/f23-cloud-base-test-day-september-8th/feed/ 0
Critical Firefox update (40.0.3) available now for Fedora http://fedoramagazine.org/critical-firefox-update-40-0-3-available-now-fedora/ http://fedoramagazine.org/critical-firefox-update-40-0-3-available-now-fedora/#comments Fri, 28 Aug 2015 00:30:27 +0000 http://fedoramagazine.org/?p=9815 Continue Reading →]]> Mozilla just released a new update to Firefox — the default web browser in Fedora — that resolves a pair of high priority security issues. These updates are now available in the Fedora 21, Fedora 22 and prerelease Fedora 23 repositories. It is highly recommended that all users of Firefox update to version 40.0.3 using the Software application in Fedora Workstation, or using the command sudo dnf update firefox from the terminal. Note also that these updates are still propagating to all the mirrors, so you might not see these updates yet, but they will appear soon.

The updated version of Firefox resolves the Add-on notification bypass through data URLs and Use-after-free when resizing canvas element during restyling issues, in addition to a handful of other bugfixes.

http://fedoramagazine.org/critical-firefox-update-40-0-3-available-now-fedora/feed/ 6
Update on Wayland support in Fedora http://fedoramagazine.org/update-wayland-support-fedora-23/ http://fedoramagazine.org/update-wayland-support-fedora-23/#comments Thu, 27 Aug 2015 06:21:49 +0000 http://fedoramagazine.org/?p=9799 Continue Reading →]]> Fedora developer Christian Schaller recently posted an update on the state of Wayland in Fedora Workstation, and it is looking promising.

One of the newest features outlined by Christian that is in the works for Fedora (and could appear in Fedora 24) is the ability to properly use two or more monitors with vastly different DPIs. This means that if you have a High DPI monitor and a standard DPI monitor the window and text sizes will no longer be tiny (or large) on one monitor and not the other. When dragging windows between the monitors the window will automatically scale to work with the DPI of the screen they are on.

There has also been a lot of work done by Fedora (and upstream) Developers to get some of the biggest applications ported to GTK+3 so they work natively with GNOME on Wayland. Caolan McNamara has finished porting LibreOffice to the GTK+3 toolkit and this work should be available in Fedora Workstation 23 as an option, with the goal of the GTK3 version being the default in Fedora 24. Martin Stransky is working on making Firefox run on Wayland with the basic GTK+3 port of Firefox completed.

Since Fedora 21, it has been possible to use Wayland on GNOME by logging into the GNOME on Wayland session from the Fedora Workstation login screen. The login screen itself is also runs on Wayland by default since Fedora 22.

UPDATE: This article previously stated that the High DPI on multi monitors was slated for release in Fedora 23 — however this is looking more likely for a Fedora 24 release.

http://fedoramagazine.org/update-wayland-support-fedora-23/feed/ 5
Videos from Flock 2015 in Rochester are available now http://fedoramagazine.org/videos-flock-2015-rochester-available-now/ http://fedoramagazine.org/videos-flock-2015-rochester-available-now/#comments Thu, 27 Aug 2015 01:23:06 +0000 http://fedoramagazine.org/?p=9789 Continue Reading →]]> Recently, the Fedora community gathered in Rochester, New York for Flock 2015, our annual conference for contributors. There were dozens of workshops and presentations at Flock, covering subjects like new technology, documentation, and grassroots promotion of Fedora.

Were you not able to attend Flock, but interested in any of the sessions? You’re in luck, because Fedora has published all the videos we captured on our YouTube channel in a Flock 2015 playlist.

You can view the whole playlist below, or by visiting it directly on YouTube.

http://fedoramagazine.org/videos-flock-2015-rochester-available-now/feed/ 1
Build a network router and firewall with Fedora 22 and systemd-networkd http://fedoramagazine.org/build-network-router-firewall-fedora-22-systemd-networkd/ http://fedoramagazine.org/build-network-router-firewall-fedora-22-systemd-networkd/#comments Tue, 25 Aug 2015 08:27:48 +0000 http://fedoramagazine.org/?p=9572 Continue Reading →]]> One of my favorite features of Fedora 22 is systemd-networkd and all of the new features that came with it in recent systemd versions. The configuration files are easy to read, bridging is simple, and tunnels are resilient.

I’ve recently started using a small Linux server at home again as a network router and firewall. However, I used systemd-networkd this time and had some great results. Let’s get started!


Our example router in this example has two network interfaces:

  • eth0: public internet connectivity
  • eth1: private LAN (

We want machines on the private LAN to route their traffic through the router to the public internet via NAT. Also, we want clients on the LAN to get their IP addresses assigned automatically.

Network configuration

All of the systemd-networkd configuration files live within /etc/systemd/network and we need to create that directory:

mkdir /etc/systemd/network

We need to write a network configuration file for our public interface that systemd-networkd can read. Open up /etc/systemd/network/eth0.network and write these lines:



If we break this configuration file down, we’re telling systemd-networkd to apply this configuration to any devices that are called eth0. Also, we’re specifying a public IP address and CIDR mask (like /24 or /22) so that the interface can be configured. The gateway address will be added to the routing table. We’ve also provided DNS servers to use with systemd-resolved (more on that later).

I added IPForward=yes so that systemd-networkd will automatically enable forwarding for the interface via sysctl. (That always seems to be the step I forget when I build a Linux router.)

Let’s do the same for our LAN interface. Create this configuration file and store it as /etc/systemd/network/eth1.network:



We don’t need to specify a gateway address here because this interface will be the gateway for the LAN.

Prepare the services

If we’re planning to use systemd-networkd, we need to ensure that it runs instead of traditional network scripts or NetworkManager:

systemctl disable network
systemctl disable NetworkManager
systemctl enable systemd-networkd

Also, let’s be sure to use systemd-resolved to handle our /etc/resolv.conf:

systemctl enable systemd-resolved
systemctl start systemd-resolved
rm -f /etc/resolv.conf
ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf


We’re now set to reboot! It’s possible to bring up systemd-networkd without rebooting but I’d rather verify with a reboot now than get goosed with a broken network after a reboot later.

Once your router is back up, run networkctl and verify that you have routable in the output for both interfaces:

[root@router ~]# networkctl
IDX LINK             TYPE               OPERATIONAL SETUP     
  1 lo               loopback           carrier     unmanaged 
  2 eth0             ether              routable    configured
  3 eth1             ether              routable    configured


Now that both network interfaces are online, we need something to tell our clients about the IP configuration they should be using. There are plenty of good options here, but I prefer dnsmasq. It has served me well over the years and it provides some handy features along with DHCP, such as DNS caching, TFTP and IPv6 router announcements.

Let’s install dnsmasq and enable it at boot:

dnf -y install dnsmasq
systemctl enable dnsmasq

Open /etc/dnsmasq.conf in your favorite text editor and edit a few lines:

  • Uncomment dhcp-authoritative
  • This tells dnsmasq that it’s the exclusive DHCP server on the network and that it should answer all requests
  • Uncomment interface= and add eth1 on the end (should look like interface=eth1 when you’re done)
  • Most ISP’s filter DHCP replies on their public networks, but we don’t want to take chances here. We need to restrict DHCP to our public interface only.
  • Look for the dhcp-range line and change it to dhcp-range=,,12h
  • We’re giving clients 12 hour leases on

Save the file and start dnsmasq:

systemctl start dnsmasq


We’re almost done! Now it’s time to tell iptables to masquerade any packets from our LAN to the internet. But wait, it’s 2015 and we have tools like firewall-cmd to do that for us in Fedora.

Let’s enable masquerading, allow DNS, and allow DHCP traffic. We can then make the state permanent:

firewall-cmd --add-masquerade
firewall-cmd --add-service=dns --add-service=dhcp
firewall-cmd --runtime-to-permanent


Put a client machine on your LAN network and you should be able to ping some public sites from the client:

[root@client ~]# ping -c 4 icanhazip.com
PING icanhazip.com ( 56(84) bytes of data.
64 bytes from lax.icanhazip.com ( icmp_seq=1 ttl=52 time=69.8 ms
64 bytes from lax.icanhazip.com ( icmp_seq=2 ttl=52 time=69.7 ms
64 bytes from lax.icanhazip.com ( icmp_seq=3 ttl=52 time=69.6 ms
64 bytes from lax.icanhazip.com ( icmp_seq=4 ttl=52 time=69.7 ms

--- icanhazip.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3005ms
rtt min/avg/max/mdev = 69.659/69.758/69.874/0.203 ms


If you need to adjust your network configuration, just run systemctl restart systemd-networkd afterwards. I’ve found that it’s quite intelligent about the network devices and it won’t reconfigure anything that hasn’t changed.

The networkctl command is very powerful. Check out the status and lldp functions to get more information about your network devices and the networks they’re connected to.

When something goes wrong, look in your systemd journal:

[root@router ~]# journalctl -u systemd-networkd
-- Logs begin at Fri 2015-07-31 01:22:38 UTC, end at Fri 2015-07-31 02:11:24 UTC. --
Jul 31 01:46:14 router systemd[1]: Starting Network Service...
Jul 31 01:46:14 router systemd-networkd[286]: Enumeration completed
Jul 31 01:46:14 router systemd[1]: Started Network Service.
Jul 31 01:46:15 router systemd-networkd[286]: eth1            : link configured
Jul 31 01:46:15 router systemd-networkd[286]: eth0            : gained carrier
Jul 31 01:46:15 router systemd-networkd[286]: eth0            : link configured
Jul 31 01:46:16 router systemd-networkd[286]: eth1            : gained carrier
http://fedoramagazine.org/build-network-router-firewall-fedora-22-systemd-networkd/feed/ 15
Precise audio control with Fedora http://fedoramagazine.org/precise-audio-control-with-fedora/ http://fedoramagazine.org/precise-audio-control-with-fedora/#comments Tue, 18 Aug 2015 07:32:06 +0000 http://fedoramagazine.org/?p=9474 Continue Reading →]]> Audio routing in Fedora is very flexible. This simple Sound settings panel comes with Fedora Workstation. It has everything most users need:


But what if you want a little more power over the sound on your system? The PulseAudio system that handles audio in Fedora can do a lot. Although the Sound panel doesn’t expose all this power, other utilities do. One of these is the PulseAudio Volume Control, also known as pavucontrol.

To install this tool, open Software and type the keyword “pulseaudio” or “volume” in the search bar. The software list shows the PulseAudio Volume Control. Click Install, or in a Terminal run this command:

su -c "dnf install pavucontrol"

When you launch the tool, you’ll see a display like this. Your list will reflect your system hardware and apps:


Enabling or disabling devices

If your system has audio devices you don’t use, you can disable them. Start by selecting the Configuration page. To disable a device, select the profile “Off.”

A disabled device won’t show up on other pages of the PulseAudio Volume Control. Note that if you run the standard Sound tool, it may reactivate a device you’ve disabled.

Selecting a default device

You can also select the default devices for input and output. The default is kept even after a logout or reboot. The default device can be different for input or output.

To select a default device, go to the Input or Output page. Then select the green check box tool next to the device.

Moving streams around

Normally, the Sound panel switches the active audio device. All active sound input or output then goes to the selected device. The PulseAudio Volume Control, on the other hand, gives you additional control. You can select audio from each app to come from, or go to, a different device.

Go to the Recording or Playback page to see available input or output streams. Click on the sound device list button next to the stream to select a different device. Remember that only enabled devices appear in the list.

This function also lets you use other PulseAudio devices on your network! For more information, check out this useful Fedora Magazine article. It shows you how to set up network audio access on Fedora Workstation.


Some devices offer multiple profiles. The PulseAudio Volume Control allows you to switch the profile in the Configuration page. PulseAudio uses a profile to set the device hardware for different sound configurations. For example, a capable sound device might offer:

  • standard analog stereo for two computer speakers — left and right
  • digital 5.1 surround for six speakers — left front, center, right front, left rear/surround, right rear/surround, and subwoofer

The list of profiles depends on several variables, including device support and PulseAudio’s available profile sets. Not every profile may be usable with your hardware.

http://fedoramagazine.org/precise-audio-control-with-fedora/feed/ 14
F23 NetworkManager Test Day August 20th! http://fedoramagazine.org/f23-networkmanager-test-day-august-20th/ http://fedoramagazine.org/f23-networkmanager-test-day-august-20th/#comments Fri, 14 Aug 2015 15:19:18 +0000 http://fedoramagazine.org?p=9744&preview_id=9744 Continue Reading →]]> Fedora 23 is scheduled to be released at the end of the October. Among many other improvements, this release includes a new version of NetworkManager to manage network connectivity. We’ve been busy fixing bugs and adding functionality. Now we need your help to make sure we didn’t miss or break anything important!

You’re encouraged to grab a pre-release version of Fedora, give it a try and let us know how it worked for you. We’ll be available on #fedora-test-day freenode IRC channel.

The landing page where we are organizing instructions and information is here. If you’re available to help on the test day, or any other time, please visit the page and fill out your name and test results.


http://fedoramagazine.org/f23-networkmanager-test-day-august-20th/feed/ 2
Make Fedora 23 Beautiful – Contribute Your Wallpaper http://fedoramagazine.org/make-fedora-23-beautiful-wallpaper-submission-open/ http://fedoramagazine.org/make-fedora-23-beautiful-wallpaper-submission-open/#comments Wed, 12 Aug 2015 18:17:44 +0000 http://fedoramagazine.org/?p=9550 Continue Reading →]]> Fedora 23 development is moving on and the time to release is not long anymore, so it is time to open the submission phase for Fedora 23 Supplemental Wallpapers.

What are supplemental wallpapers?

Supplemental wallpapers are the non-default wallpapers provided with Fedora. Usually Fedora ships GNOME upstream supplemental wallpapers. We try to collect a set for each release of Fedora and offer it as an option package. Wallpaper shipped with Fedora that is not the default wallpaper is called ‘supplemental’ wallpaper.

How to contribute to this package?

Fedora uses for the submission application Nuancier for managing the submissions and the voting process.
For an submission you need an Fedora account. For being allowed to vote, you must have a membership in another group as cla_done or cla_fpca.
For inspiration you can look to former submissions and winner wallpaper.

Here are some of the last election:


There is no limit how many contribution you are make but there are some rules

Technical Requirements:

  • Submitted wallpapers must use a format that can be read by software available in Fedora Package Collection. Preferred image formats is PNG.
  • Originals for landscape formats must be a minimum of 1600 pixels wide and 1200 pixels high. The larger the better. Photographic submissions should be made at the highest resolution the camera is capable of.
  • Submitted wallpapers should be provided in a 16 x 9 aspect ratio if possible.
  • No watermarks, signatures, photographer or creator names, or messages may be included in any part of the work.

Other Requirements:

  • Submissions must not contain material that violates or infringes anothers rights, including but not limited to privacy, publicity or intellectual property rights, or that constitutes copyright infringement.
    If your submissions include or derive from artwork created by other people, please make sure the license of the original work you incorporate is compatible with Fedora and that you are not violating any of the provisions of its license.
    Make sure you provide attribution to artists that license their work with a CC Attribution clause.
  • Submission should have the consent and approval of the author or creator
  • Submissions are thereby licensed to the public for reuse under CC-BY-SA unless another accepted approved liberal open source license.
    See a list of approved licenses for Fedora.
    Note that we can not accept NC or ND submissions.


The deadline for submissions is the September 12 2015 at 23:59 UTC.

The voting will open automatically after the deadline and is open until September 17 2015 at 23:59 UTC


You can earn badges for contributing. One badge for a accepted submission. Another one if your submission is under the selected ones and a third if you participate in the voting.


So get your camera and do some nice shots or start your favorite vector editor, 3D graphic editor or image manipulation program to produce some nice wallpaper for Fedora 23.

http://fedoramagazine.org/make-fedora-23-beautiful-wallpaper-submission-open/feed/ 21
The State of Fedora: 2015 Edition http://fedoramagazine.org/state-fedora-2015-edition/ http://fedoramagazine.org/state-fedora-2015-edition/#comments Wed, 12 Aug 2015 15:44:46 +0000 http://fedoramagazine.org/?p=9724 Continue Reading →]]> Fedora’s third Flock conference kicked off Wednesday morning with a keynote by Matthew Miller, the Fedora Project Leader (FPL). How’s Fedora doing? Says Miller, “The actual state of Fedora is awesome, we’re doing very well as a project and it’s thanks to all of you.”

Miller says that the project is doing very well, and brought out some stats to prove it – with the caveat that stats can be misinterpreted and “dangerous” if used wrong. After a period of “disconcerting down releases” the Yum connection stats for Fedora 21 and 22 are showing that those releases are back up to the same levels as Fedora 14. Miller also walked through a number of other stats on downloads, and which releases are in use currently.

According to Yum connection stats, Fedora 22 is in the lead with Fedora 21 nearly as popular, and Fedora 20 sporting almost as many users as F21. Other releases and Rawhide make up just a little bit of the active user base today, according to Yum connection stats.

Fedora Workstation has about 68% of the downloads, Fedora Server carries about 14%, with Cloud clocking in at about 4%. The KDE spin is getting about 5% of downloads, and LXDE and Xfce each have about 2.5%. Of course, as Miller pointed out, we don’t know how many people use a release based on downloads. For example, folks could be spinning up hundreds of instances of the Cloud image – or they may be using Amazon Web Services and AMIs, which aren’t counted as downloads at all.2015-Flock-State-of-Fedora

2015-Flock-State-of-Fedora-cpuAnother trend is sharply away from 32-bit x86 CPUs. Miller brought up a chart that displayed the decline of downloads for 32-bit images from 2009 to 2015. Does that mean that Fedora should be dropping 32-bit? Maybe not yet, but it’s worth discussing where 32-bit x86 fits in Fedora’s future.

Beyond Downloads

Another area of the project that’s doing well is Fedora Magazine, which had an all-time high in May of this year. The most popular posts are for user-facing topics, like GNOME and other desktop topics. “In the future we’re working on a separate contributor blog, and make the magazine more and more user focused.”

If you look at visitors to the magazine by region, the United States leads by a large margin. The next countries are Germany, United Kingdom, India, Brazil, France, Italy, Canada, and Russia.

Fedorans do like to work together. Last year there were 1,066 IRC meetings (official meetings, not just being in IRC talking), and 765 IRC meetings in 2015 alone. “This shows how vibrant we are, but also is buried in IRC. There’s a lot of Fedora activity you don’t see on the Fedora Web site… I want to look at ways to make that more visible,” says Miller.

There are efforts to make the activity more visible, says Miller. “If I want to interact with the project, is somebody there? Yes, but we have millions of dead pages on the wiki… we need to make this more visible.”

IRC is “definitely a measure of engagement” but it’s also a high barrier of entry, says Miller. “Wow that’s complicated. Wow, that’s still around?” is a common response from new contributors to IRC. The technology, and “culture” can be confusing.


Again, there are many caveats with using the statistics we do gather as an accurate measure of Fedora’s health, or a clear picture of the existing Fedora user base. To that end, Miller says he’d like to have a more accurate census of Fedora users and usage, but is aware that previous efforts have met limited success and there’s privacy concerns with automatically surveying users.

Miller says he’d like to have an opt-out system that takes care of privacy concerns, but still gives better information about counting the popularity of spins, architectures, etc. He’d like to address this over the next “release or so.”

Copr vs. Koji

For some time now, Fedora has been providing Copr as a build system for packages outside the main Fedora build system (Koji). In the last year, Copr has become very popular amongst the Fedora community. “We’re sure doing a lot more in Koji, but Copr is taking off even more,” says Miller.

Koji’s increase can be attributed to a few factors, but one major factor is the mass rebuild being done due to GCC 5 for Fedora 23 this year. Last year, Fedora didn’t have a mass rebuild of packages.

Looking ahead to Fedora 23

“We’re nominally on track for a Halloween release of Fedora 23,” says Miller. Fedora 23 alpha was released on time, though Miller cautioned against “looking at how the sausage is made” for the alpha readiness.

Though the release is on track, Miller noted that we’re still working on the “story” for the release – above and beyond “this is an improvement on the last release.” He encouraged Fedorans to help craft the message for the release, and to work with the marketing team to surface themes for work that’s going into the Fedora 23 release that might not be obvious.


“Last Flock we had an awesome meeting about how we were going to reform Fedora top-level governance. Over the last year, we’ve done it.” The new governance model (Fedora Council) is in place, and is responding to requests for resources and providing leadership for direction.

The Council uses a “consensus-based model” to operate, rather than holding on approval from all folks unless there’s a specific objection. “A lot of this is set up so the FPL doesn’t get burned out as much,” and Miller pointed to the Council and the new Community Impact Lead Remy DeCausemaker helping to keep the project day to day activities going as well as putting on events like Flock. Miller also says that the search is continuing for the Fedora Diversity Lead.

On the council we have objectives, select those and move towards making those happen. Would like to use those in the future, to decide where funding goes for “all sorts of things,” focus marketing efforts, and more. The current objectives are the editions, university outreach, Fedora “rings”/modularization, and then … what’s next? We have empty objectives, so where do we want to go in the next year or 18 months? Miller says he wants to grow the user base, improve visibility into the project, but he also wants to get input from the larger community.

With that, and a few housekeeping comments from Flock organizers, the “state of Fedora” wrapped for 2015.

The full slides for this talk are available from http://mattdm.org/fedora/.

http://fedoramagazine.org/state-fedora-2015-edition/feed/ 19