Fedora Magazine http://fedoramagazine.org Wed, 27 May 2015 15:20:23 +0000 en-US hourly 1 http://wordpress.org/?v=4.2.2 Running Vagrant on Fedora 22 http://fedoramagazine.org/running-vagrant-fedora-22/ http://fedoramagazine.org/running-vagrant-fedora-22/#comments Wed, 27 May 2015 02:00:20 +0000 http://fedoramagazine.org/?p=8914 Continue Reading →]]> Fedora 22 comes with a lot of great features and having Vagrant with libvirt support is one of them. Don’t know what Vagrant is good for? Vagrant is a program that enables you to create portable and reproducible development environments easily supporting many hosts and guests operating systems and various features such as synced folders, forwarded ports and support for famous provisioners such as Chef, Puppet or Ansible. And that’s still not everything. You can configure Vagrant to use Linux containers (Docker support is baked in) or famous cloud services so you don’t even have to run your development virtual machine on your computer.

Installing Vagrant

To install plain Vagrant package, run:

# dnf install vagrant

This will install base Vagrant package which is what you want in case you only need to use Vagrant with Docker or provider that is currently not directly supported in Fedora such as VirtualBox. This is esentially a stripped down Vagrant that does not come with any plugins.

# dnf install vagrant-libvirt

Run the above mentioned command if you wish to use Vagrant with QEMU/KVM virtualization via libvirt (recommended as this is what we can support). It will install base Vagrant package and vagrant-libvirt plugin. If you would also like to avoid typing password everytime you virtualize something from Vagrant, download also vagrant-libvirt-doc sub-package and run the following to allow vagrant group to manage libvirt without authentication:

# dnf install vagrant-libvirt-doc
# cp /usr/share/vagrant/gems/doc/vagrant-libvirt-0.0.26/polkit/10-vagrant-libvirt.rules /usr/share/polkit-1/rules.d/

And finally, if you prefer lxc to Docker, you can install vagrant-lxc plugin as well by running:

# dnf install vagrant-lxc

Vagrant for older Fedoras

Not running Fedora 22 yet? Packages have been already back-ported to Fedora 21 as well and are available for quite some time in the official repositories. And if you are running RHEL or CentOS, look at my Copr repository that contains a vagrant1 software collection.

Upstream packages

We packaged Vagrant as we wanted to see an easier way of installing and using Vagrant in Fedora, especially together with vagrant-libvirt provider. Our packages provide streightforward installation and updates for Vagrant and unlike from the RPMs provided by upstream we do not bundle Vagrant dependencies. This has however one limitation that we are unable to resolve; at the moment we don’t support uploading custom boxes to Atlas (official Vagrant cloud) as we are not shipping an internal Vagrant plugins that provide this functionality. This is due to the fact that upstream decided to use RubyEncoder binaries that we cannot ship in Fedora because of their licensing. Please note that this does not affect downloading images from Atlas. If you need uploading as well, you have to grab and install the upstream package (which is also available as RPM).

Getting started

If you don’t know Vagrant yet, you will need to spend a few minutes understanding how to setup your development environment. The first part is to understant what Vagrant boxes and Vagrantfiles are. Boxes are provider-specific images with some metadata and Vagrantfiles are configuration files of your projects. To set up an environment you need to create a Vagrantfile in the root directory of the project. Here is an example of minimal, rather empty, Vagrantfile:

Vagrant.configure(2) do |config|
  config.vm.box = "fedora-22"

As you can see, Vagrantfile is just a regular Ruby file that let’s you use Vagrant DSL to define your development environment. In our minimal example we set only ‘box’ parameter to define our Vagrant box. With this we can already tell Vagrant to virtualize our new development environment by running vagrant up. Dependending on our default provider (libvirt in Fedora, VirtualBox in upstream), Vagrant will try to create and boot up the virtual machine. It will also configure your environment by few default options like rsyncing your project’s directory to /vagrant on the newly created guest.

This is of course just the beginning. There is really a lot of options how to further set up your project’s development environment and they are mostly provider specific, so read your provider’s documentation just after going through official one. A good start for defining the environment for your first project will be a default Vagrantfile which will be generated for you after running vagrant init. It contains a lot of commented-out options alongside with their descriptions that should help you to define your configuration quickly.

Another great way is to study Vagrantfiles for open-source projects; for instance OpenShift origin has one as well as Ruby on Rails upstream.

Getting a box

As I mentioned above, you won’t make it far without Vagrant boxes. Luckily, Vagrantfiles can be written in a way that fetching boxes happen automatically. This is either because the box is hosted in Atlas and Vagrant would automatically download the boxes from there by matching the username/box pattern, or by specifying config.vm.box_url option in Vagrantfile that sets the URL to the box. Because of this, new project developers don’t need to do more than installing Vagrant, checking out source code with accompying Vagrantfile and running vagrant up. Not to say that they can invoke the command on any supported platform (including various Linuxes, Mac OS and Windows).

In case you need to pick a box for your project, you can find one on Atlas, which is the official place for hosting boxes, or you can already try the upcoming official Fedora Cloud boxes. If you need something specific, you can always build your box from scratch. For that you might find veewee a helpful tool.

Sometimes it’s more convinient to base off your environment on a box with just basic OS installation since it’s easier to get for the others and the maintainence happens only regarding the provisioning process in Vagrantfile, but you can always create a box that is already provisioned and it’s way faster to boot up. For this, vagrant package --output mynew.box command might come in handy, since it can create a new box based on the current, already provisioned, state.

In our minimal example, Vagrant expects a box named ‘fedora-22′ already added. To do so, we can download the prelease box and add it (boxes come with a .box extension, but that’s not a hard requirement):

$ vagrant box add Fedora-Cloud-Base-Vagrant-22-20150521.x86_64.vagrant-libvirt.box --name fedora-22

Development process

Now that we have a minimal Vagrantfile in our project’s directory and box added, we are truly ready to run vagrant up to boot up our machine. Once that finishes, our project’s directory should be available at /vagrant inside our VM. That happened without any configuration, since a few things are default for any Vagrantfile. We are able to change it or add other shared folders later. To log inside we run vagrant ssh to log in as the vagrant user with sudo access (otherwise vagrant ssh-config shows us the IP we need) and we can develop the project as we would normally do on our host.

One thing that you notice is that our shared folder is not automatically synced. Vagrant sync them using rsync only at start up and when running vagrant rsync. To avoid that we can run vagrant rsync-auto which will do the syncing automatically as long as the command keep running. But if you find rsync somehow cumbersome, you can set up NFS, which is way faster.

Our example is completely simplified as Vagrant let’s you create a multi-machine envorinment, set up networking between the nodes, forward ports to host, and more.

Once finished with your changes, just vagrant halt the machine. You can always come back and run vagrant up to bring it back. If you want to remove the VM, run vagrant destroy. Very simple and keeps your host system clean. As it might have crossed your mind, Vagrant VMs are pretty much normal VMs so you can manage them via other software such as virt-manager. That’s true, but Vagrant associates some state with each machine so I suggest to administer them with Vagrant only. You can use virt-manager to open the graphical user interface or remove the domain if you won’t be able to do so using Vagrant though.

More on Vagrant

As this article can’t take you through everything there is about Vagrant, here you can find additinal resources to go though:

And here are people from the Fedora community whose blogs can help you to get up and running with Vagrant on Fedora (please mention yourself in the comments if you blog about Vagrant too):

http://fedoramagazine.org/running-vagrant-fedora-22/feed/ 1
Fedora 22 will contain some fc21 packages http://fedoramagazine.org/fedora-22-will-contain-fc21-packages/ http://fedoramagazine.org/fedora-22-will-contain-fc21-packages/#comments Tue, 26 May 2015 18:00:40 +0000 http://fedoramagazine.org/?p=8906 Continue Reading →]]> If you update your Fedora 22 install using DNF on the command line, you may notice that some of the packages that are downloaded and installed still have the release label of fc21 in the package name. For example, if you install or update GitPython on Fedora 22, you will get the following package:


While some other packages have the fc22 label, like the main git package:


.. and this is perfectly all right. Usually, for a new release, the entire Fedora package set is rebuilt. This time around, however, there wasn’t enough time in the Fedora 22 cycle for this “mass rebuild” as it’s called. These packages from Fedora 21 will not cause any issues in your Fedora 22 installations at all. So, if you do run dnf commands and notice these in the transactions, please do not let them worry you.

If you do have questions, please ask the community at http://ask.fedoraproject.org!

http://fedoramagazine.org/fedora-22-will-contain-fc21-packages/feed/ 4
Fedora 22 released and available now http://fedoramagazine.org/fedora-22-released/ http://fedoramagazine.org/fedora-22-released/#comments Tue, 26 May 2015 14:00:37 +0000 http://fedoramagazine.org/?p=8927 Continue Reading →]]> We are proud to announce the official release of Fedora 22, the community-driven and community-built operating system now available in Cloud, Server, and Workstation editions.

If that’s all you need to hear, jump over to Get Fedora to download — or for current users, run the upgrade tool.

In addition to the latest versions of all your favorite free and open source software, Fedora 22 marks our second release with distinctly-targeted offerings for cloud computing, the server room, and the desktops and laptops of software developers and creators everywhere. Thanks to the hard work of developers, designers, packagers, translators, testers, documentation writers, and everyone else, we’re incredibly confident in saying that this is our best and most polished release yet.

Also with this release, we return to our traditional six-month cadence — we’ll see you back here sometime around Halloween!

Highlights in the Fedora 22 release

Every Fedora release has its own character. If this release had a human analogue, it’d be Fedora 21 after it’d been to college, landed a good job, and kept its New Year’s Resolution to go to the gym on a regular basis. What we’re saying is that Fedora 22 has built on the foundation we laid with Fedora 21 and the work to create distinct editions of Fedora focused on the desktop, server, and cloud (respectively). It’s not radically different, but there are a fair amount of new features coupled with features we’ve already introduced but have improved for Fedora 22.

Fedora Cloud

Fedora 22 Cloud edition has a number of interesting updates that should be exciting for users and developers.

  • Updated Docker Images – The Fedora 22 release includes updated Docker images that you can use as the base of your containerized applications.
  • Vagrant Boxes – One of the oft-requested features for Fedora is an “official” Vagrant box that developers can use to spin up images using the popular Vagrant tool for building development environments. With the Fedora 22 release we now offer Vagrant Boxes for libvirt and VirtualBox, so developers on Linux, Mac OS X, and Windows can spin up Fedora-based development environments with ease. Users can choose a Vagrant box for Fedora 22 Atomic Host and Fedora 22 Cloud base edition.
  • Atomic Improvements – Fedora 22 Atomic Host includes a number of interesting improvements, including the Atomic command, updated Docker, Kubernetes, Flannel, and rpm-ostree packages.
  • Dockerfiles – Fedora 22 also includes a fedora-dockerfiles package (and up-to-date git repository) for building applications with the base Fedora 22 Dockerfile and additional packages.

Fedora Server

  • Database Server Role. The Fedora Server edition focuses on easy of different server roles. Fedora 21 debuted with an Domain Controller Role featuring FreeIPA. For this release, we’ve added a Database Server role, built around PostgreSQL.
  • Default to XFS filesystem. The default file system type for Fedora Server installs will be XFS running atop LVM for all partitions except /boot. The /boot partition will remain a non-LVM, ext4 partition due to technological limitations of the bootloader.
  • Cockpit will be compatible between OS releases. Cockpit is a server manager that makes it easy to administer your GNU/Linux servers via a web browser.
    • Easy to use. Cockpit is perfect for new sysadmins, allowing them to easily perform simple tasks such as storage administration, inspecting journals and starting and stopping services.
    • No interference. Jumping between the terminal and the web tool is no problem. A service started via Cockpit can be stopped via the terminal. Likewise, if an error occurs in the terminal, it can be seen in the Cockpit journal interface.
    • Multi-server. You can monitor and administer several servers at the same time.

Fedora Workstation

  • Better notifications. Thanks both to work done in GNOME 3.16 and other projects like the Automatic Bug Reporting Tool (ABRT), notifications keep you better informed, but interfere less with your work. They now appear anchored to the center of the top bar, and no longer cover up the bottom of the screen where you are often reading a terminal or browser. An unobtrusive marker appears in the calendar to let you know you have unread notifications. If ABRT detects a serious bug, a friendly notification appears and allows you to report the bug information, but doesn’t overload you with details. And if you’re a serious Terminal user, longer background jobs now notify you when they’re done, so you can get on with other work and pick up the results when you’re ready.
  • Refined themes. The GNOME Shell and other themes and design are refined and improved. Now you can more easily identify information on the screen, adjust window size and placement, and navigate your files and folders. Improved bridging between desktop environment themes allows apps from other environments like KDE to look and feel more like native apps as they’re updated to take advantage of this feature. Standard scrollbars have been replaced by a minimal, overlaid indicator, while a scrollbar trough is shown when needed. This create a cleaner, less distracting view which helps you focus on window content. These “overlay scrollbars” are also better suited to mouse scroll wheels and touchpad scrolling.
  • Application improvements
    • Software. The Software app has more and better data than ever before, and makes it easy for you to find a wide variety of useful free software. It also makes keeping your system up to date a snap. The Software app also can install all sorts of extras such as fonts or media helpers.
    • Files. The updated layout in Files gives a better view of your files and folders, and a new view popover makes it easy to change the zoom level and sort order from a single place. You can also now move files and folders to the trash intuitively using the Delete key, rather than the Ctrl+Delete keyboard combination.
    • Image Viewer. The Image Viewer has been redesigned to reduce the amount of window chrome and give more space to images.
    • Boxes. The user interface for Boxes, the application for virtual and remote machines, has a large number of improvements, including new preferences dialogs, a revamped box creation assistant, a feature to send keyboard shortcuts to a box, and display scaling by default.
    • Vagrant. Developers will appreciate the addition of software development environment software Vagrant into Fedora — it’ll work using our included virtualization technology, with no need to install third-party virtualization (like VirtualBox). Use this to work on top of the Cloud images mentioned above, or launch your own Vagrant boxes.

Spins, Labs, and ARM

Spins are alternative desktop environments for Fedora, including KDE, Xfce, LXDE, MATE-Compiz, and SOAS (Sugar on a Stick). We have a new website presenting these at https://spins.fedoraproject.org/. Of particular note for F22:

Fedora 22 KDE Plasma

Plasma 5, the successor to KDE Plasma 4, is now the default workspace in the Fedora KDE spin. It has a new theme called Breeze, which has cleaner visuals and better readability, improves certain work-flows and provides overall more consistent and polished interface. Changes under the hood include switch to Qt 5 and KDE Frameworks 5 and migration to a fully hardware-accelerated graphics stack based on OpenGL(ES).

Fedora 22 Xfce

The Xfce spin has been updated to Xfce 4.12. This release has an enormous number of improvements, including HiDPI support, improvements to window tiling, support for Gtk3 plugins, and many improvements for multi-monitor support.

Fedora Labs

We also have a new site, presenting functional bundles of software which were previously also collected as Spins. Visit https://labs.fedoraproject.org/ for collections focusing on gaming, audio production, robotics, security, and more.

ARM Architecture

Previously, images for the ARM architecture were mixed into the Spins page. They now have their own home at https://arm.fedoraproject.org/, with downloads for Fedora Server, Fedora Workstation, and for several Spins as well.

Other changes of note

Faster and better dependency management with DNF

With Fedora 22, we’re introducing a major change under the hood. Specifically, we’re now using DNF and hawkey to manage packages. DNF is much like the Yum software package manager (it’s largely command-line compatible), but re-written and re-engineered to provide optimal performance and (along with Hawkey) provide a strict API definition for plugins and extending projects. DNF also makes use of the libsolv library initially pioneered by the openSUSE Project to provide faster and better dependency management.

It also boasts a better performance and memory footprint vs. Yum, and is designed to have a cleaner codebase and be easier to maintain.

If you’re using the Fedora 22 Workstation edition, and managing packages with the Software Application, odds are you won’t notice a difference. Server and Cloud users who fall back on Yum commands will receive a reminder (courtesy of dnf-yum) that Yum is deprecated and DNF is now the default package manager. DNF has been in development for quite some time, so we’re confident it’s ready for prime time. The classic Yum command line tool has been renamed to yum-deprecated as a transitional step for tools still using it. See Read The Docs for compatibility changes from Yum to DNF in detail.


Elasticsearch is full-featured and very popular self-standing open source indexing server, and now it’s available by with just a yum install elasticsearch — no, wait, make that dnf install elasticsearch!

GNU Compiler Collection 5

Fedora 22 comes with GCC 5.1 as the primary compiler suite.

Downloads, upgrades, documentation, and common bugs

You can start by downloading Fedora 22:


If you are upgrading from a previous release of Fedora, refer to:


Fedora’s FedUp utility enables an easy upgrade to Fedora 22 from previous releases. See the FedUp page on the Fedora wiki for more information:



Read the full release notes for Fedora 22, guides for several languages, and learn about known bugs and how to report new ones:


Fedora 22 common bugs are documented at:


This page includes information on several known non-blocker bugs in Fedora 22. Please be sure to read it before installing!

http://fedoramagazine.org/fedora-22-released/feed/ 34
Fedora 22 is “Go” for May 26! http://fedoramagazine.org/fedora-22-go-may-26/ http://fedoramagazine.org/fedora-22-go-may-26/#comments Fri, 22 May 2015 18:32:48 +0000 http://fedoramagazine.org/?p=8901 That’s right — the bits are heading out the door (and onto our mirror network)! Expect the official announcement around 10am US Eastern time Tuesday morning.

http://fedoramagazine.org/fedora-22-go-may-26/feed/ 52
Firefox 38 available now in the Fedora repositories http://fedoramagazine.org/firefox-38-available-now-fedora-repositories/ http://fedoramagazine.org/firefox-38-available-now-fedora-repositories/#comments Tue, 19 May 2015 00:47:16 +0000 http://fedoramagazine.org/?p=8855 Continue Reading →]]> Mozilla released version 38 of the Firefox web browser last week, and the updated version is available now in the Fedora repositories for Fedora 21, and for users running Fedora 22 pre-release versions. As has been the case since Firefox starting rapidly releasing new versions every 6 weeks or so, there are a handful of new shiny features, and many, many bugfixes.

Two notable new features provided by the release of Firefox 38 are the tabbed preferences, and better high DPI support.

Tabbed Preferences

In previous versions, the Firefox preferences were contained in a pop-up dialog box. In version 38, the preferences are now moved into a dedicated tab, much like the add-ons tab that has been in Firefox for many releases:


High DPI support

Previously, users running Firefox on high DPI screens on Fedora had to tweak a setting in the about:config to get Firefox to play nicely with their high DPI screens. Now, if the layout.css.devPixelsPerPx value in about:config is set to the default of -1.0, Firefox renders pages and its chrome at the DPI setting of the desktop. Note that if you previously followed our instructions for manually setting this value, you may want to reset it to the default by finding it again in about:config, right clicking on it, and choosing Reset



http://fedoramagazine.org/firefox-38-available-now-fedora-repositories/feed/ 6
Minimap coming to the gedit text editor http://fedoramagazine.org/minimap-coming-gedit-text-editor/ http://fedoramagazine.org/minimap-coming-gedit-text-editor/#comments Mon, 18 May 2015 06:10:02 +0000 http://fedoramagazine.org/?p=8845 Continue Reading →]]> Gedit, the default GUI text editor in Fedora Workstation has a neat new minimap feature in the works. This feature provides a shrunk-down version of the document you are editing on the right of the screen to make it easier to jump between different parts of larger documents.

In a blog post announcing the new feature, gedit developer Ignacio Casal Quinteiro points out that this new feature was actually developed by Christian Hergert as part of the GNOME Builder editor, and because Christian actually made the bulk of the changes in the upstream widget, GTKSourceView, it was easy to add the same support to gedit.

It was only recently added to the gedit master branch, so this new gedit feature is likely to make an appearance in Fedora 23 Workstation.


http://fedoramagazine.org/minimap-coming-gedit-text-editor/feed/ 10
F22 countdown, video presentation on Fedora Marketing, and more… http://fedoramagazine.org/5tftw-2015-05-15/ http://fedoramagazine.org/5tftw-2015-05-15/#comments Fri, 15 May 2015 18:26:00 +0000 http://fedoramagazine.org/?p=8835 Continue Reading →]]> Fedora is a big project, and it’s hard to keep up with everything. 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 15th, 2015:

Countdown to the Fedora 22 release

Fedora 22 is currently scheduled to be released on May 26th — 11 days to go! This will include our Cloud, Server, and Workstation editions, along with other variants like Fedora Atomic (designed for running containerized apps) and of course KDE and Xfce desktop spins.

As always, the last few weeks before release are a little hectic as we iron out the last blocker bugs, but as of right now — knock on wood — the general sense is that we’re in pretty good shape. (We’ll know for sure by Thursday of next week, and hopefully sooner.) I know people sometimes get frustrated with schedule “slips”, and hopefully that won’t happen, but remember, a somewhat-elastic schedule is part of the plan for delivering high-quality releases (as Joe Brockmeier wrote last year).

If you’re feeling impatient, grab the F22 beta (Server, Cloud, or Workstation) and help us iron out any last-minute problems. As is usually the case, if you start with a Fedora beta release, you’ll be upgraded seamlessly to the final release when that comes out, so you won’t have to reinstall.

Fedora Marketing Status

On Monday, the Fedora Council held our first video-based council meeting, featuring a presentation from Chris Roberts of the Fedora Marketing team. Watch the video here:

or download in VP8/webm format, or read the real-time transcription log (thanks to Fedora Community Action and Impact Lead Remy DeCausemaker).

Upcoming Video Meeting on “Three Editions”

That worked well, so we’re going to do it again this coming Monday, with Stephen Gallagher presenting on the official project objective which he’s leading, Fedora Editions, Phase 2. This is scheduled as a G+ event, plus we’ll have a text-based live transcription (and place for questions) in the #fedora-meeting channel on Freenode IRC, and I’ll post the video in open video format webm/VP8 shortly after. We’re also planning a similar presentation from Fedora QA on June 8, and from various Fedora Engineering subteams in July.

FAD planning changes — impact!

A “FAD” is a “Fedora Activity Day” — a Fedora premiere event funded from our community budget. In order to make sure that this is spent most effectively, that we can communicate to our sponsors how we are making the most of their money, and that the rest of the community feels good about these allocations, we’ve rearranged the FAD organization process to focus on not just what will be done, but on the benefits of those activities to the project as a whole.

Priority for funding will be given to FADs which are directly connected to our 12-18 month community objectives. If you have an idea where getting a bunch of Fedora contributors together to work on something would have a big, positive effect on a current Objective, put together proposal. Or, if you have an idea for a new Objective which would have a big, positive effect on our mission in a well-defined timeframe (and know the right person to lead the work!), put together a proposal for that, too! (For either of these, contact the Fedora Council to start the discussion.)

Auto-update your systems with DNF

I was a sysadmin in a former life, and like many sysadmins, had more machines to maintain than one person could really give individual attention to. For many of those systems, I appreciated the ability to automatically apply updates without intervention. With Fedora 22, our command-line package tool switches from Yum to DNF, and Rackspace (and Fedora) hacker Major Hayden has a nice howto on his blog for configuring your system for automatic package updates with dnf.

With the pre-release crunch next week, 5tFTW will be taking a little break. I’ll be back the week after that.

http://fedoramagazine.org/5tftw-2015-05-15/feed/ 1
Introducing Fedora’s students for Google Summer of Code 2015 http://fedoramagazine.org/introducing-fedoras-students-google-summer-code-2015/ http://fedoramagazine.org/introducing-fedoras-students-google-summer-code-2015/#comments Fri, 15 May 2015 13:30:43 +0000 http://fedoramagazine.org/?p=8810 Continue Reading →]]> What is Google Summer of Code?

Google Summer of Code is a global program that offers student developers stipends to write code for various open source software projects. Fedora has participated in this program for many years now. It is an excellent way to introduce a new generation of engineers to the Fedora Project. This year, Fedora has been granted seven slots in the program, allowing us to bring on seven talented students to work on exciting projects for Fedora.

So what are the students working on?

I’m glad you asked that! This year, we have seven tasks shared among six Fedora communities:


Fresque is the new Fedora review server. This project aims to provide a powerful web-application to streamline the process of putting new software packages into the Fedora collection. This summer, student Rahul Ranjan will be working to add git support to the Fresque server to keep track of changes made during the package review process. Rahul will be publishing his progress regularly on his personal blog.


Nuancier is a voting application used to select the supplementary (non-default) wallpapers that are shipped with each Fedora release. Parth P. Panchal will be working on enhancing this system to support high-resolution, multi-monitor wallpapers. Parth will be publishing his progress regularly on his personal blog.

Ask Fedora

Ask Fedora is a question-and-answer site dedicated to helping Fedora users aid each other in solving problems. Over the next several months, Kalpani Anuradha Welivita will be working on a complete user-experience design overhaul of the Ask Fedora site. This is an ambitious (but sorely needed!) effort and we’re all excited to see the end product. Kalpani will be publishing her progress regularly on her personal blog.

Glitter Gallery

Glitter Gallery is a social platform for collaboration around design and user-experience. This summer, Aditya Prakash will be working on a very ambitious set of UI and integration efforts, bringing together SparkleShare, Inkscape and other tools together in a single collaborative environment. Aditya will be publishing his progress regularly on his personal blog.


The Cockpit Project is a web-based administrative console for servers. It is used by both the Fedora Server and the Fedora Atomic Image as the primary graphical interface for those systems. This summer, we have selected students to work on two tasks within the Cockpit Project.

The first task is Cockpit integration with rolekit. Student Turner England will be spending his summer developing a user interface in Cockpit to easily and effectively deploy a FreeIPA Domain Controller onto a Fedora Server system. During this time, he will be publishing his progress regularly on his personal blog.
The second task under the Cockpit Project is to add support for managing systemd timer events to the Cockpit UI. This task will be undertaken by Jakub Skořepa and you will be able to follow his progress on his personal blog (it is not yet available).

Mozilla Thunderbird

Mozilla Thunderbird is a fully-featured email client developed by the Mozilla Foundation. Regrettably, this year the Mozilla Foundation was not itself selected as a participant in the Google Summer of Code. However, thanks to our long-standing relationship, the Fedora Project has selected to provide one of our Google Summer of Code participation slots to them to support this mutually-beneficial email client. Suyash Agarwal will be spending his summer vacation working with the Fedora Project under the tutelage of R Kent James, a long-time Mozilla contributor. His efforts this year will be to enhance Mozilla Thunderbird to support the JMAP protocol for synchronizing the client with a mail server. Throughout the summer, Suyash will be blogging regularly.

Final Thoughts

Let’s give a warm welcome to these new members of our community! It will be exciting to see their hard work in production in the autumn.

http://fedoramagazine.org/introducing-fedoras-students-google-summer-code-2015/feed/ 0
Flock presentations & registration, websites update, and more http://fedoramagazine.org/5tftw-2015-05-08/ http://fedoramagazine.org/5tftw-2015-05-08/#comments Fri, 08 May 2015 17:09:18 +0000 http://fedoramagazine.org/?p=8794 Continue Reading →]]> Fedora is a big project, and it’s hard to keep up with everything. 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 8th, 2015:

Vote on Flock talks

Flock is Fedora’s big annual conference for contributors and developers, where we meet to plan for — and hack on — the future of the project. This year’s event will be August 12-15 in Rochester, New York. The call for papers is complete, and we received 132 submissions. That’s more than we can accommodate, of course, so please vote now on your favorites.

You may remember that last year, the voting required scoring each talk with a number between 0 and the total number of talks — something in the 100s. Thanks to work by our awesome Fedora engineering hackers, we’re now using simplified range voting — put a 3 by talks you love, 0 by ones you aren’t interested in (or 1 or 2 for the in-between cases).

Voting closes 2015-05-18 00:00:00 UTC, so don’t delay. (Tip: convert UTC to your local time with date -d "2015-05-18 00:00:00 UTC" in a terminal window.)

Flock registration still open

Also worth mentioning — conference preregistration was inadvertently closed along with the talk submissions. That’s been fixed, and registration is still open. Hope to see you there, whether you’re a long-time contributor or just getting started!

Kick the tires on new Fedora websites

Fedora designer Máirín Duffy invites us all to kick the tires on the new Fedora websites in staging. She notes that Fedora Websites has been working on several new websites, with a focus on better presentation for Fedora Spins — both alternate desktops like KDE or Xfce and “functional” spins like the Design Suite or Robotics. Robert Mayr (known to many as “robyduck”) has gotten these into the “staging” environment, and Máirín notes that the Websites Team now needs “help from the users of these spins and experts in the individual technologies of what we should be featuring and how we should be describing these spins.”

So, if that’s you, get in touch!

Fedora Marketing update presentation

The Fedora Council is our top-level leadership and governance body. We have a new plan where we will have monthly (at least, to start) reports from various parts of the project, with the first coming this next Monday (May 11) at 17:00 UTC — a report by Chris Roberts of the Fedora Marketing team.

We’re still working out the technical details, but the plan is for this to be a video conference. Details will be posted on the council-discuss mailing list beforehand. Join us to learn what’s going on in this Fedora subproject, and what’s needed in the future.

Packaging guidelines for config variations

This is a note primarily for people working on the separate Cloud, Server, and Workstation editions. Thanks to Stephen Gallagher, the Fedora Packaging Committee (FPC) has approved new guidelines which allow separate configuration in cases where defaults should vary. (For example, different firewall rules for server or desktop use.) We tried one approach for this in Fedora 21, and these new guidelines take the lessons learned from that.

Note that currently this is available only for the top-billed variants on which we are focusing, but theoretically the same mechanism could work for other Fedora Spins. However, such use would need to be first approved by FESCo (the Fedora Engineering Steering Committee).

http://fedoramagazine.org/5tftw-2015-05-08/feed/ 0
F22 Cloud/Atomic Test Day May 7th! http://fedoramagazine.org/f22-cloudatomic-test-day-may-7th/ http://fedoramagazine.org/f22-cloudatomic-test-day-may-7th/#comments Mon, 04 May 2015 21:20:01 +0000 http://fedoramagazine.org/?p=8753 Continue Reading →]]> Hey everyone! Fedora 22 is on the cusp of being released and the Fedora Cloud Working Group has elected to organize a test day for May 7th in order to work out some bugs before shipping it off to the rest of the world.

With a new release comes some new features and tools. We are working on Vagrant images as well as a testing tool called Tunir. Joe Brockmeier has a nice writeup about Vagrant and Kushal Das maintains some docs on Tunir.

On the test day we will be testing both the Cloud Base Image and the Fedora Atomic Host cloud image. The landing pages where we are organizing instructions and information are here (for Cloud Base) and here (for Atomic). 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.

Happy Testing!

http://fedoramagazine.org/f22-cloudatomic-test-day-may-7th/feed/ 0