April 26, 2015

Installing Red Hat Enterprise Linux 7 on MacBook Air 2015

Recently I've upgraded to a new MacBook Air (13 inch, early 2015) laptop and luckily enough I'm running Red Hat Enterprise Linux 7.1 on it. Here is how to install it.

Prepare boot media

The easiest method is to boot from a USB stick which holds either the entire DVD or just boot.iso. Since I happened to find a 1GB only USB stick I went for the boot.iso. dd if=boot.iso of=/dev/sdb is the only thing you need to prepare the boot media.

Initial boot

Mac boot menu

While computer is booting hold the (left) Alt (Option) key to enter Startup Manager. Wait a second or two before it displays your local hard drive and the USB boot media. Select the option EFI boot to boot the anaconda installer.


Booting from a boot.iso means I need to use the network to grab the rest of the installation. Because the wireless card needs proprietary drivers I've tried both USB to Ethernet adapter and USB tethering with my phone.

Note: initially I have forgotten to plug in my USB networking card which resulted in bug #1191286. After cold-plugging and rebooting the system everything was fine. Subsequently I don't see any problems with the USB networking card. The bug should be fixed in RHEL 7.2 btw.

Note: I've been using a USB docking station from Plugable for years because their products are Linux friendly. In particular the networking chip is ASIX and there is no problems with drivers for Linux.

In my case I've wiped out the entire SSD disk b/c I don't care about dual boot. Previously I've heard about anaconda crashing while it tries to detect the Mac OS file system. I've played around with Rawhide before going for RHEL 7.1 and didn't see any problems related to foreign filesystems.

I've gone with the default partitioning scheme while slightly modifing the partition sizes, etc.

Post install

There are several issues which still need attention. I didn't have enough time in the last few days to check these out:

  • GNOME 3 sucks big time. Fortunately I was able to install MATE Desktop from EPEL;
  • Wireless card needs drivers; I've managed to compile them myself, will share the info soon;
  • Display brightness doesn't seem to work at all. On top of that the display goes full black after suspend-resume. I could barely see anything on it.
  • The onboard keyboard is quite annoying for previous ThinkPad user like myself. Most importantly I need to press Fn to activate the F1, F2, etc keys which I use a lot in mcedit. I'll share more info aafter I figure out how to remap the keyboard;
  • There is a very annoying boot chime which I have no idea how to disable;
  • I do have a Thunderbolt to Ethernet adapter and hot-plug seems to work (at least partially) despite claims that this is not supported in Linux;
  • Power manager was reporting my battery life totally wrong but after a full discharge/recharge it seems to have calibrated itself. I need to fix brightness and other issues before doing more tests;
  • Output sound works out of the box, haven't tested camera and microphone input yet;
  • ATrpms and EPEL are still missing some codecs for RHEL 7 which means no movies;
  • Fan speed needs adjustments;
  • I have not yet tested presenting via projector but already have a few ideas how to make it work;

Fedora 22 on MacBook Air

I did try Fedora 22 Beta and experienced bug #1215458. Also for some reason the installation hit an error downloading a package and didn't let me retry but forced me to exit the process.

I'll continue posting my updates until the system runs smoothly like it is supposed to.

[Event Report] April Python Pune Meetup 26th April, 2015

After a successful Python Sprint in March, 2015, we hosted April Python Pune meetup, 2015 on 26th April, 2015 at Zlemma Analytics Pvt. Ltd., Baner Road, Pune (India). This meetup focused on python packaging workshop, writing simple automation scripts using fabric and interacting with MySQL and sqlite database using python.

About 35 people attended this meetup. Most of them were professionals.

The meetup started at 10:30 A.M. with package your python code workshop where we explained :

  • Why should i package my python code
  • Tools Required for packaging
  • Get familiar with pip, virtualenv and setuptools
  • Python Project Structure
  • Create a dummy project and package it
  • Create a source distribution
  • Register yourself on Pypi and upload package.

For that i had created a dummy project myls <https://pypi.python.org/pypi/myls/0.0.1> and explained the above steps.

After a small break, Suprith presented a talk on "My first automation script using Fabric". He started by introducing what is fabric, how it is different from other automation tools like Ansible, salt, puppet and chef and showed how to use fabric to write simple automation script.


The last talk was presented by Tejas on how to interact with MySQL and sqlite database using python and how to add crawled data from a website using beautifulsoap and crawler and store in the database. Here is the source code of the above demo.


By 01:30 P.M., Suraj had demonstrated his cool python application speedup, a simple python program to speedup internet speed on your LAN and Hardik demonstrated about his final year project on how to scan new virus on a windows machine by reading system calls over .exe files and analyzing those calls using data mining.


Finally, this awesome meetup came to an end at 02:00 P.M.

Below is the upcoming plan of 3 month meetup i.e from May, 2015 to July, 2015.

  • Workshop/Talk on Flask, Data Analytics, Automation using selinium and Robots and Security
  • Hackathon - Craft your idea into a real program and contribute to your favorite upstream OpenSource Python project.

Thanks to Ajit Nipunge and Zlemma for providing the venue arrangements, speakers and attendees who made the meetup successful.

LFNW Day 1
Saturday morning came early after the night of games and the hall was buzzing with many exhibitors setting up. All we needed to do was power up. The doors opened at 9:30 and the crush of attendees came in. Our booth was across from the raffle table and became very popular. Many guests asked about the musical instruments and what does that had to do with Linux. Brian Monroe showed off the Guitarx effects he developed, a mean metal distortion, a dreamy shoegaze sustain and a bouncy echo while explaining the app. Many guests tried out the guitar, bass, drums and keyboard and left with smiles.
Brian shows off Fedora Jam with attendees at Linux Fest North West 2015
LinuxFest NorthWest Day 0

Jeff Fitzmaurice, Brian Monroe and I met up at the Bellingham Technical College Friday night to set up the Fedora booth. We quickly got the tables dressed, the gear unpacked, plugged in and all the computers running, with some help from the Fest staff. We finished in enough time to get to Foxx Hall for game night. Jacob, the Game Night organizer was setting things up when we arrived. Jacob brought nearly 200 LFNW passes to the game night and Jeff Fitzmaurice processed the registrations. Brian handed out Fedora Shirts and we met up with Pete Travis and Adam Williamson. We had planned to give out guitar picks but we didn't get them in time, so I bought a gross of picks and wrote “fedora jam” on all of them. The games, Cards Against Humanity, Ticket to Ride, and others came to an end at 11:59. Tomorrow the Fedora Jam exhibit.

<lj-embed id="2">

April 25, 2015

New in virt-v2v

Setting up Yubikey for SSH two-factor with public key authentication
I just bought a Yubikey Neo. It is a tiny usb device which can be used for multi-factor authentication with many application. But setting it up can become tricky at times due to lack of documentation. Here is what I did to setup ssh with Yubikey two-factor for my Fedora 20 and Fedora 21:

Step1: Install the pam module for yubikey auth.
# yum install pam_yubico

Step 2: We need to create a mapping of user and the yubikey associated with it. We'll need the key id of the yubikey. To obtain that, we just need to open any text editor, plug the key in a usb slot and touch the golden button on the Yubikey. The first 12 characters is the id. Also note that, there can be multiple keys associated with one user. We'll create a file /etc/yubi-map:
# cat /etc/yubi-map

Step 3: Now we have to add the yubico pam module to the sshd auth. Change the /etc/pam.d/sshd so that first few lines look like this:
auth       required     pam_sepermit.so use_first_pass
auth sufficient pam_yubico.so id=1 authfile=/etc/yubi-map debug

Note that I have added the pam_yubico as a sufficient auth and also modified the pam_sepermit to use the user's initial password.

Step 4: We'll modify the /etc/ssh/sshd_config to allow challenge response and define the authentication method.
ChallengeResponseAuthentication yes
AuthenticationMethods publickey,keyboard-interactive

Optionally, disable the password auth as well
PasswordAuthentication no

Restart the sshd.
# systemctl sshd restart

Step 5: Now, here is the real catch. Yubikey needs to contact an authentication server before it can process. As far as I understand, we cannot use Yubikey when there is no internet (alternatively, you can run an authentication server in your own infra but more on that later). This also creates a problem, which is, that SELinux denies any network request during authentication. To handle the situation, Yubikey docs suggests setting a boolen.
# setsebool -P authlogin_yubikey 1
A month in QA

During the evening of 24th March, I’ve decided to join Fedora Project’s QA Team.
At first impact, I was really unsure. Actually, I really love testing new pieces of software, but I’ve always been a lone-wolf while building my computing experience. Since my daily job in the field of accountancy tires me because there are lots of deadlines, I thought that this new task could have driven me crazy. But… After my first month… I’m really glad I applied for it! Might this interest you too? So, try to read the following paragraphs and join us!

Felling as a part of a community
What I really enjoy, is that every folk works as a part of a big project. Feeling that the next Fedora will contain at least a simple 0,00000001% of my efforts, is a pleasant satisfaction. I’ve also had the chance to chat with lots of experts on IRC, including adamw and satellit, for example. Although they are power users and experienced testers, they also are always nice, they helped me a lot and provided lots of information. Yes! Learning new things and contributing to Fedora at the same time, is an activity worth doing.

Use of English
While reading, chatting and mailing, I’ve now also the chance to exercise my use of English. Since it’s not perfect, I hardly have the chance to improve it here in Italy. Writing with people which share common interests with me, but live around the world, sounds like a great enhancement for my skills.

QA Activity
I’ve filled some bug reports on Bugzilla in order to get in touch with maintainers when things didn’t seem to work properly. I’ve learned a lot during this activity: honestly, it’s the first time I’ve got the chance to see how a big IT Project is organized. The goal is, however, always the same: testers, developers and engineers contribute together in order to improve Fedora’s quality. Getting involved in TestDays, following cases for the various composes and giving karmas for new updates are other tasks I’ve enjoyed and played with. Every bit offers the chance to perform some nice exploratory testing, uncovers details, highlights strange behaviors and, overall, makes me learn something new!

If you are thinking about joining the Project… Stop wondering and JUST DO IT! I promise it will be an interesting and attracting experience!

Filed under: English, Fedora, Fedora QA, IT
Red Hat Connect for Business Partners: Tools and Resources


<iframe allowfullscreen="true" class="youtube-player" frameborder="0" height="289" src="https://www.youtube.com/embed/_rIwzsTwT0U?version=3&amp;rel=1&amp;fs=1&amp;showsearch=0&amp;showinfo=1&amp;iv_load_policy=1&amp;wmode=transparent" type="text/html" width="460"></iframe>

Red Hat Connect for Business Partners contains numerous tools to help our partners succeed in growing their business.






That Rugged Raw

It has been a more-busy-than-usual week on campus, and I've had a pretty packed conference schedule. I've been much too far behind on New Year's Resolution:

Ship Copy.

So, in it's most-purest most-rawest most-honest form, you can find a number of raw transcripts in the new repo: decause/raw

So, What does that look like?

├── libreplanet
│   └── 2015
│       ├── closingkeynote-libreplanet-karensandler.txt
│       ├── debnicholson-friday.txt
│       ├── freesoftwareawards.txt
│       └── highpriorityprojs-libreplanet-friday.txt
├── pycon
│   └── 2015
│       ├── ninapresofeedback.txt
│       ├── pycon-day2-keynotes.txt
│       ├── pyconedusummit2015.txt
│       └── scherer-pycon-ansible-day2.txt
└── RIT
    └── 2015
        ├── biella-astra-raw.txt
        ├── biella-molly-guest-lecture.txt
        └── molly-sauter-where-is-the-digital-street.txt

6 directories, 13 files

$ wc -w libreplanet/2015/*.txt
 2287 libreplanet/2015/closingkeynote-libreplanet-karensandler.txt
  139 libreplanet/2015/debnicholson-friday.txt
  586 libreplanet/2015/freesoftwareawards.txt
 2297 libreplanet/2015/highpriorityprojs-libreplanet-friday.txt
5309 total

$ wc -w pycon/2015/*.txt
  106 pycon/2015/ninapresofeedback.txt
 2233 pycon/2015/pycon-day2-keynotes.txt
 1844 pycon/2015/pyconedusummit2015.txt
   63 pycon/2015/scherer-pycon-ansible-day2.txt
4246 total

$ wc -w RIT/2015/*.txt
 4521 RIT/2015/biella-astra-raw.txt
 2489 RIT/2015/biella-molly-guest-lecture.txt
 1964 RIT/2015/molly-sauter-where-is-the-digital-street.txt
8974 total

18529 total total

18,529 words, or, just over 41 pages total of raw text.

There is a flaw in my workflow. Though there is some utility in a raw transcript, really it is mostly when delivered in real-time. After the fact, there is much post-production work to be done, like spell checking. Even after, if there is a video, then the transcript is partial, and incomplete. This is bothersome to many potential downstream consumers of raw text. So where does that leave us?

Word Clouds

I've played with word_cloud before within my decause/presignaug for building presidential inauguration visualizations last year. Since then, word_cloud has gotten much more sophisticated--now using scikitlearn, and numpy, and providing the ability to fit word clouds within images!

List of Issues/Fixes

  • you'll need to pip install cython first
  • You'll need to sudo yum install freetype-devel (probably not necessary, since this is alleviated by pointing at a diff .ttf typeface...)
  • you'll have to edit your FONT_PATH within word_cloud.py
  • image masks *must* be saved as greyscale, not rgb images (this was a biggie, and I wouldn't have figured it out if GIMP didn't display the color encoding in the file statusbar when you opened things :) )
I went ahead and uploaded the changes I made to my fork on GitHub: http://github.com/decause/word_cloud if you'd like to see them. The important files are pycon.py and pycon-greys.py.
Using systemd tmpfiles

As part of my regular duties at my day job, I provide some community support on the HTCondor users’ mailing list. At the beginning of the week, someone came to the list with Fedora RPM troubles. I was able to track it down to the fact that the RPM didn’t correctly create some temporary directories.

But why not? It’s been a while since I did any RPM building, but at first glance, the spec file looked fine. The systemd tmpfiles configuration looked good, too. Then someone else found the cause of the problem: according to the Fedora packaging guidelines, a package should write the config file andcreate the directory. It turns out that tmpfiles.d is only processed at boot time (or when manually invoked), so a package that needs a file/directory to exist needs to create it at install time (or require a restart).

I was going to file an RFE, but I found a related one marked as CLOSED->WONTFIX. I understand the reasoning here, so I won’t reopen it to argue. It’s just a surprising behavior if it’s not something you regularly deal with.

April 24, 2015

Cómo subir tu blog a Fedora Planet y no morir en el intento

Recuerdo hace un par de días atrás cuando logré al fin subir mi blog a Fedora Planet, después de estar dos días haciendo todo lo necesario. Y es que, como dice un compañero que igual no tiene mucho tiempo en este ambiente, es algo confuso efectuar correctamente los pasos sino tiene una idea clara de comandos básico o intermedios. De igual manera la documentación que es posteada en la wiki es muy completa. Esta publicación es solamente un complemento dirigido a personas que tienen poco tiempo en la comunidad.

Antes de empezar con los pasos debe tener ya creado su FAS y debe ser patrocinado por un grupo. Por ejemplo, yo estoy en el grupo CLA (estos no cuentan) pero aparte formo parte de Fedora Panamá.

Creación de llaves SSH

SSH significa SecureShell y es un nombre de protocolo y del programa que lo implementa y que sirve para acceder a máquinas remotas a través de una red. Permite manejar por completo la computadora mediante un intérprete de comandos (…) Fuente.

Lo primero que debe efectuar es la creación de llaves SSH que nos permitirá posteriormente comunicarnos con el servidor, esta es una cláve pública que, al subirla a nuestro FAS nos ayudará a entrar a los servidores y evitar que otras personas modifiquen nuestros datos. Los SSH también son utilizados en Github para crear una forma segura de reconocimiento de equipos, pero ya ese es otro tema (aunque ayuda en lo que trato de explicar).

  1. Abra la terminal y escriba
    $ ssh-keygen -t rsa
    (Recuerde que las lineas con $ refieren a acceso de usuario y cuando la línes empiezan con # refieren a acceso root)
  2. Nos saldrá una línea que dirá lo siguiente:
    Enter file in which to save the key (/Users/you/.ssh/id_rsa):
    Así que lo que debemos hacer es apretar ENTER.
  3. Te pedirá que ingreses una clave segura “Enter passphrase (empty for no passphrase):“, lo recomendable es que lleve mayúsculas, minúsculas, números y signos para que se lo más segura posible. La ingresamos y luego apretamos ENTER.
  4. Por último te pedirá que la ingreses de nuevo “Enter same passphrase again:” efectúa lo que se requiere y ya se genrará su clave SSH que se almacena en la ruta ~/.ssh/id_rsa
  5. Lo siguiente es subir tu clave a tu cuenta, para eso entra a tu FAS luego entra en “My Account”, haga clic en “Editar”, se desplaza hasta donde dice “Public RSA SSH Key” y luego presione “Examinar” esto le abrirá el explorador de archivos, en donde dice “Lugar” define la ruta ~/.ssh/id_rsa.pub justo así:
    Captura de pantalla de 2015-04-24 13:09:05Le da a “Abrir” y ya tendrá la id_rsa lista para subir.
  6. Lo último será hacer clic el “save” y ya tendrá su clave RSA vinculada a su FAS.
    (Importante: La clave SSH se activará una hora luego de haberla colgado a su FAS)

Subiendo tu Blog

Luego de haber subido la RSA lo siguiente es conectarnos con nuestra cuenta de fedorapeople.org desde la terminal, crear nuestro archivo .planet y luego subirlo mediante SCP.

    1. Debe conectarse a su fedorapeople.org para esto abrimos la terminal y escribimos el siguiente comando:
      ssh -i ~/.ssh/id_rsa [su_nombre_usuario_aquí]@fedorapeople.org
      Si todo esta correcto le pedirá su clave SSH, aprieta ENTER y listo, entrará a su cuenta de Fedora People.
    2. Salimos de la sesión apretando el comando exit y luego lo que vamos a efectuar es el código para tu .planet

Luego, lo que vamos a hacer es crear nuestro archivo .planet para su posterior subida a nuestro fedorapeople.org, para esto vamos a utilizar vim. Si somos nuevos lo que recomiendo es instalarlo así que en la terminal nos ‘logueamos’ como usuario root e ingresamos el comando # yum install vim aceptamos la instalación y podremos proceder. Salimos de la opción root escribiendo el comando exit. Lo siguiente es crear nuestro archivo, para esto primero debemos confirmar primero que estamos en nuestra carpeta personal,escribimos pwd y debe aparecer una línea así: /home/[aqui va su nombre de usuario]. Si se encuentra en esta ruta puede proceder con la creación del archivo .planet para esto escribimos $ vim .planet y nos mostrará algo como esto:

Captura de pantalla de 2015-04-24 14:49:47Lo que en realidad tenemos aquí es nuestro editor de texto listo para ingresar lo que necesitamos, en la wiki de cómo crear Planet no muestra un pequeño texto que es el que debemos editar para que nuestro blog esté en éste sitio, el cual es el siguiente:

name = Your Name
face = http://yourname.fedorapeople.org/yourpicture.png

(Importante, para pegar este texto a la terminal donde tiene el vim deberá hacerlo seleccionar y copiar, luego dirigirte a la terminal y hacer clic derecho, luego pegar. Para editar el texto deberás hacerlo moviendo las flechas del teclado y borrando. Igual para los enlaces, deberás copiar y luego pegar con el clic derecho. Al principio debe apretar la tecla I para poder editar o escribir en el archivo.)

Deberá notar que debe crear un feed de su blog, todo el tiempo recomiendo que utilicen wordpress aunque la mayoría -para no decir todos, no estoy seguro de ello- tiene compatibilidad para feed, pero en este momento lo explicaré como wordpress, otro punto importante es que si tu blog no sólo será para hablar de Fedora entonces debes crear categorías o etiquetas para que este contenido sea visible en el Planet, sino todo lo que subas será publicado, y no sería algo bonito que hablaras de, no sé “Gatos” y que saliera en la página principal de Planet.

Luego que creas tu categoría o tag debes llegar a el, en mi caso sería algo así: http://safeshadow.info/category/software-libre/ lo único debes hacer es escribir feed al final y quedará algo así: http://safeshadow.info/category/software-libre/feed y listo, esto es lo que va en la primera linea, remplazamos.

En la siguiente línea debemos escribir nuestro nombre o el nombre del blog, dependiendo de cual sea. En la tarcer línea debemos insertar la dirección de la imagen en donde esté nuestro rostro (si es un blog personal) o el logo del blog. Al terminar debemos tener algo así:

Captura de pantalla de 2015-04-24 15:25:11

Cuando ya tenemos todo esto hacemos tocamos la tecla Esc, podremos notar que en la parte de abajo al principio aparecía “Insertar” y ahora no aparece nada, lo siguiente que debemos escribir es el comando :x esto lo que hace es guardar el documento y luego cerrar o salir, nos aparecerá la terminal de nuevo. Para comprobar que el archivo ha sido creado escribiemos el comando $ find .planet y nos mostrará abajo .planet, esto nos confirma que existe.

Lo último es subir este archivo a nuestro fedorapeople.org, para esto en nuestra terminal escribimos el siguiente comando: $ scp -r .planet [su_nombre_de_usuario_aquí]@fedorapeople.org:/home/fedora/[su_nombre_de_usuario_aquí]
Con esto ya hemos cumplido con subir nuestro .planet a nuestro fedorapeople.org, para poder comprobar que lo hemos hecho bien podría ser ‘loguearnos’ en nuestro Fedora People y luego escribir el comando $ find -planet sino nos manda algún error es que ya existe.

Posible error: Algo que me pasó en mis ciertos intentos fue que trataba de poner el comando scp cuando estaba en la sesión de mi fedorapeople.org eso me tiraba un error de llave de autenticación, este comando sólo se utiliza en su terminal normal, no dentro de su sesión de fedora people.

Espero que esta publicación le sea de ayuda para poder subir su blog a Fedora Planet, por ahora ha sido todo y dentro de poco estaré escribiendo más en este blog. Será hasta la próxima.

F22 Beta, feedback for Fedora Workstation, security challenge, better Spins website, and PyCon report

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 April 24th, 2015:

Fedora 22 Beta released

In case you missed it, Fedora 22 Beta was released this week, and we’re well on our way to the planned final release at the end of May. This release seems pretty solid, so if you are interested in seeing what’s coming, check out the known common bugs list and then either install fresh or upgrade using FedUp. Note that once you’ve got the beta running, regular updates will put you on track for the final release — you won’t need to reinstall or follow a special procedure.

Your feedback feeds Fedora Workstation

Fedora Workstation contributor Christian Schaller posted Fedora Workstation: More than the sum of its parts, explaining some of the ongoing work in Fedora development, and he concluded with a question: especially if you are using GNOME on another distribution than Fedora, what are we still missing at this point for you to consider making a switch to Fedora Workstation?

This prompted a long and still-ongoing conversation in the comments. Join in if you have something to add!

Meanwhile, Jiří Eischmann wrote about a more specific issue: the state of instant messaging in Fedora Workstation, with an eye towards finding what our users want and need and the best way to support Fedora’s mission of the advancement of free and open source software. See also part 2 and a followup on the desktop list.

Fedora Security Team’s 90-day challenge

Fedora Security team member Eric Christensen (a.k.a. Sparks) blogged about the Fedora Security Team‘s 90-day challenge to close all outstanding critical and important known security issues in Fedora. Eric invites anyone interested in helping to get involved.

Fedora @ PyCon

PyCon is the annual conference for the Python programming language, which we use heavily in Fedora for infrastructure software and for many utilities in the distribution itself. Therefore, we tend to have a few Fedora hackers every year, this year including Aurelien Bompard, Kushal Das, Luke Macken, Pierre-Yves Chibon, Ralph Bean, and Remy DeCausemaker. Ralph provides a brief report — part 1 and part 2.

Redesigned Fedora Spins page

For Fedora 21, we launched a the new getfedora.org site, which showcases our three primary editions: Fedora Cloud, Fedora Server, and Fedora Workstation. But, of course, there’s more to Fedora than that, and for the upcoming release, Robert Mayr (a.k.a. robyduck) and Máirín Duffy (mizmo) are working on a redesign of the Spins page. “Spins” are alternate versions of Fedora provided for several different cases, and represent the strength and depth of our contributor commmunity. On her blog, Mo breaks down the different types of spins, and presents ideas for the new design — along with a big call for help and feedback.

Do you use a Fedora spin? Do you work on one? If so, take a look at this post and contact the Websites team with your feedback.


Tangerine 0.15
New badge: flisol-2015-organizer !
flisol-2015-organizerYou helped organize the Fedora booth for FLISOL, 2015
New badge: flisol-2015-speaker !
flisol-2015-speakerYou spoke at FLISOL 2015!
New badge: flisol-2015-attendee !
flisol-2015-attendee You visited the Fedora booth at FLISOL, 2015
[PAAS] Openshift Enterprise @ University

Openshift @ University



The Middleware Services Group within Information Technology Services (ITS) at the University of North Carolina at Chapel Hill needed a comprehensive, dynamic solution for frequent server provisioning requests and, in particular, managed servers. Without such a solution, the likelihood that users would employ outside vendors significantly increased. Use of outside vendors would potentially increase security concerns, present additional costs, and further complicate system administration. Moving to a fully-interoperable Platform-as-a-Service (PaaS) offering, built on OpenShift Enterprise by Red Hat®, has allowed the middleware services team to deliver a flexible development and hosting environment that has fostered innovation and increased peace of mind.

Ref :







Instant Messaging in Fedora Workstation 2

Last week I wrote about the suboptimal state of instant messaging in Fedora Workstation with some thoughts how it could be improved. I also asked Fedora users on Facebook and Google+ what IM clients they use. Especially in the case of Google+, I gathered votes from a number of people which is large enough to draw some conclusions.

I used different methods on FB and G+ because unlike G+ FB doesn’t support polls, so I asked people to submit their answers in comments. That grew much fewer answers, but people were not biased by pre-picked answers. Here are the results:

fb-clients-chartAs you can see there are pretty much just four IM clients that are widely used by Fedora users: Pidgin, Skype, Empathy, Telegram.

Google+ supports polls, so I created a poll where users could pick one of those answers: Empathy, Pidgin, KDE Telepathy, Other, or “I don’t use a desktop client”. Over 1200 users voted which is significantly more than on Facebook and gives a good statistical sample. And the results?

gplus-clients-chartPidgin is a clear winner, winning by a larger margin than among FB users. What is also interesting is the number of people who don’t use IM desktop clients any more – 37 %. This group is probably over-represented in this poll because it’s obvious that G+ users will favor web tools more than others since Google is such a proponent of web apps. I also asked users to add the name of their favorite IM client in the comments under the poll if it’s not among given options. And these are the results:

gplus-clients-othersEven though I was asking about desktop clients, most people voted for Hangouts which is not surprising on Google+. Some of them even consider Hangouts a desktop app because the Chrome app can partly behave that way. Telegram is also very popular among Fedora users on Google+.

And some conclusions?

Empathy – in both surveys Empathy lost to Pidgin which is not a good score for a default client. If alternative clients are more popular than the default one, then the default one is not doing a good job. Based on the comments, what people don’t like about Empathy is that how it behaves in GNOME 3. Transforming it into a single window would probably solve most of the complaints, but in the long run Empathy would need much more than that and is anyone interested in developing it? Now, it’s totally dead upstream.

Pidgin – is the most popular IM client among Fedora users even though it was ousted from the position of the default client many years ago. People don’t seem to be very enthusiastic about it, it hasn’t seen any higher development activity for years, but it’s still the best what we have according to most users. Going back to Pidgin as the default client would probably be the safest option. Unlike Empathy, it doesn’t have integration with GNOME Online Accounts, but apparently it’s not a significant inconvenience for users if they still prefer Pidgin to Empathy. However, in the long run we will hit problems that are related to very little upstream development activity – no GTK 3 port, no Wayland support, no HiDPI support etc.

KDE Telepathy & Kopete – I was quite surprised that KDE clients got so few votes. KDE is not as popular as GNOME among Fedora users, but it has a sizable user base. Does this mean that KDE users don’t use desktop IM clients any more or do they prefer Pidgin? In comments, I found several users saying that they use Pidgin in KDE.

Telegram – I was really surprised by the popularity of Telegram. I personally don’t know anyone who uses it, but it looks like it could be the new #1 IM service for open source enthusiasts as Jabber was in the last decade. It’s the only (at least a bit popular) modern IM service that is trying to be open and focused on privacy. It has a Linux desktop app written in Qt. You can find it in Copr although it’s not packaged very well and the app is missing an icon. I’m not sure how easy it would be for the package to make it into the official repositories. The website says they’re using slightly modified Qt which could make it difficult. There is also a plugin for Pidgin which doesn’t support advanced features, but works well for simple chat communication (again available in Copr). If we pick Pidgin as the default browser again, we should have this plugin pre-installed since Telegram seems to be becoming more and more popular.

Skype – ended second among Fedora users on Facebook. This IM service seems to be very popular even after a decade of its existence. Skype can’t be included in Fedora due to its license, but they provide an RPM package and it’s pretty easy to install it. Its protocol is closed, so we can’t really have support for it in open source clients, but maybe we can do a better job in integrating it to the desktop since it’s so popular among our users?

Hangouts – another popular closed service. Well, it’s not closed completely. Google still allows users to connect via XMPP, but you won’t get the advanced features and according to their plans they want to drop XMPP support anyway. So looks like the only way to give users Hangouts in the future will be the Chrome web app. Integrating web apps is in our Fedora Workstation tasklist. So things like converting Chrome Rich Notifications into standard desktop notifications, or installing the most popular Chrome web apps directly in Software would be worth looking into.

Facebook Chat/Messenger – no one really mentioned Facebook Chat which now has its own app – Messenger. People probably still don’t see it as a standalone service or don’t consider it a desktop app in any way (unlike Hangouts). However, it’s probably the most popular IM service nowadays. It still supports XMPP, but AFAIK they’re planning to drop it as well. Until then it works well with both Empathy and Pidgin. But after they drop XMPP, we won’t have many choices left. Maybe we could at least provide the web app messenger.com through Software?

GNOME Chat – some people also suggested that we drop Empathy and create a new app that should be part of the GNOME core apps. It would be based on Telepathy, so nothing like building it from scratch. It would fit very well to GNOME 3 (unlike Empathy) and it wouldn’t suffer from problems of Pidgin (Wayland, HiDPI support,…). There are even some designs and even some existing code, but no one has touched it for two years. So it hasn’t really stirred a lot of interest among GNOME contributors.

It all comes down to a question whether we want to provide one well integrated client that supports several IM services and whether it will even be possible in the future because the most popular services are closed or going to be closed, or whether we should give up our client and rather focus on supporting and integrating those dedicated, very often closed source clients. I always preferred to have one integrated tool for all IM networks, but the world seems to be going the other direction.

FUDCon Pune Planning Meeting - 21 Apr
It's coming little bit late but we know it never too late so as per schedule we had planning meeting on Tuesday (21 Apr.) at Red Hat pune office. Most of us gathered together in meeting room and discussed about what we have done and what are the blocker we need to look at.

As usual we used http://piratepad.net/FUDConPunePlanning to keep notes and discussed different topic/blockers.

  • PJP and Niranjan to make a wiki page of speakers/travellers. 
  • Huzaifa and PJP in touch with Global Mobility for visa invitation letters.
  • First round of accepted talks are out - http://fudcon.in/program/sessions/accepted
  • Reworked by Siddhesh and Praveen to include twitter feed, news feed, etc. to website.
Entire minutes are appended below:

21 April 2015

Agenda + Minutes
 * Travel updates?
   * PJP and Niranjan to make a wiki page of speakers/travellers
   * Start meeting regarding this in #fudcon-planning
     * Accepted several tickets
     * Deferred some; we'll keep going over the list.
     * All tickets https://fedorahosted.org/fudcon-planning/report/3
   * Prepare an invitation letter for them (for visa).
     * Huzaifa and PJP in touch with Global Mobility
   * Ask Ruth about us booking tickets instead of getting speakers/requestors to book tickets and reimburse after the conference
     * There is progress on this; Ruth has reimbursed a ticket already

 * Budget
   * (no update this week)
   * Make and maintain a publicly visible sheet to track expenses?
   * Need to keep tab on the number of accommodation requests
   * Sent a reminder to Ruth
     * Ruth replied; she's OK with using RH expense system

 * Scheduling
   * http://fudcon.in/program/sessions/accepted
   * Next task: create a schedule
     * Names of rooms and capacity from MITCOE
     * Volunteers to prepare the schedule

 * Outreach
   * http://piratepad.net/FudCon-outreach-list
     * this is for industry + mailing lists (communities)
     * we need help here with more lists + more volunteers to do the outreach.
   * http://piratepad.net/FUDCon-College-Outreach
     * Reach out to MIT to let them know about the event (mid/late May)
     * Do some sessions in colleges after exams over (exams get over mid-April)
     * Let's do in:
       * MIT-COE
       * Cummins
       * COEP
       * PCCOE
       * Sinhagad
     * 12 weekends before our event to do these sessions
   * Video series
     * Shreyank spoke with some video editors to get an idea of things to keep in mind; and also give them an idea of what we are looking for.
     * Videos from FPL (Matthew Miller), jsmith, Kushal, Parag, Rahul, Joerg, etc. -- extolling the virtues of FUDCon + Pune
       * Kushal and Shreyank to work on this
       * Two videos:
         * One in April
         * One in May
       * Reach out to design/marketing team for editing help.

 * Marketing
   * no updates this week
   * Fedora magazine
   * Twitter
   * Facebook
   * Google Plus
   * LinkedIn group (Reach out to Soni)
   * http://piratepad.net/marketing-plan-fudcon

 * FUDCon.next planning
   * We should start a tradition to announce the next fudcon at the current one
   * We should start the bid process beforehand and get a bid selected before the current one starts
   * The FUDCon pages on the Fedora wiki already mention 1 yr of lead time is needed for starting the fudcon planning process.
   * https://fedoraproject.org/wiki/FUDCon_organization_process
   * Tuanta taken ownership of driving this at last APAC ambassadors meeting

 * Website/Graphics
   * Reworked by Praveen and Siddhesh to include twitter feed, news feed, etc.
   * Graphics status update?
     * Name tag sticker design (Reuse the Going to FUDCon graphic)
     * Brochure for speakers
     * T-shirt design
     * Going to FUDCon
       * https://jurankdankkal.fedorapeople.org/FUDCon/FUDConPune2015/final/goingto/goingto.png
       * https://jurankdankkal.fedorapeople.org/FUDCon/FUDConPune2015/final/flyer/flyer.svg
       * https://jurankdankkal.fedorapeople.org/FUDCon/FUDConPune2015/final/badges/badges.png
       * Please provide feedback on https://fedorahosted.org/design-team/ticket/359
       * 2011 designs
         * http://fudcon.in/2011/conference/promte-fudcon.html

 * FUDPub
   * Rupali reached out to Venue1
   * Potential Venue 1
     * Space for 100 people
     * Reasonable (approx 1800 per person)
     * RH has relationship; payments are easier
     * Close to cocoon
     * No limitation on sound limits - a nice party can be had.
   * Amit suggsts place where there is bowling option.
     * Reached out to one place
       * Option 1: $5600 for unlimited games, food and drinks for unlimited people (max 250)
       * Option 2: $4800 for 150 people, limited to 12 lanes and unlimited food, drinks, games.
   * On paud road there is go-carting place, not sure if they have bowling too.
   * Rupali continuing to reach out to others
     * Another venue visit next week

 * Swag
   * Let's start thinking about this now; approach vendors.
   * Swag for Volunteers
     * tshirts (200)
   * Swag for Organisers?
   * Swag for Speakers
     * Mugs (200)?
       * siddhesh's quote:
       * shreyank's quote:
     * Umbrellas (200) (for sweet Pune rains)
   * Swag in general <- br="" shreyank="">     * buttons (3000)
     * tattoo pasties
     * stickers (5000) <- br="" siddhesh="">     * pens (3000)
     * caps (300)
     * cloth bags (300)
     * diaries (200)  <- br="" siddhesh="">     * bottles (200)
     * pen drives (200)
     * magic mint dispenser (200) <- amita="" br="">   * Fedora badge for attendees?(added to the FAS account)

 * Venue
   * WiFi
     * Siddhesh, Huzaifa, Rupali had a call with MIT sysadmin
     * MIT COE are keen on doing it; they need input from us.
       * Also talk about the Fedora mirror with them.
   * Power connector extensions
     * MIT are going to set this up.  Follow up
   * Note to speakers (include in prep email): In seminar hall: projectors are 4:3, screen quite small (don't include small text)
   * Refreshments for speakers lounge / otherwise

 * MIT meetups
   * What to do?
     * Packaging?
     * Bugzapping
   * Siddhesh to reach out to MCUG (this week, I promise!)

 * Volunteers
   * College reopens on Jun 15
   * Many students will be on leave till Jun 15
   * We should identify students who will be available in the break - e.g. students from Pune who don't plan to travel elsewhere; we don't need too much of their time anyway
     * Rupali to get a list of volunteers from MITCOE.

 * Mobile Application
   * No updates
   * Siddharth + Rohan had volunteered

 * Videographing
   * No updates
     * kpoint: Not an option. Rates too high (20k per day just for recording)
       * asked for clarification on rates; they might have subsidised options for us
     * hasgeek
       * They're  allowing us use of their equipment + train a few volunteers who can do  the recording.   Equipment needs to be brought from BLR to Pune.  Nice  gesture by them; but sounds complicated given the expensive equipment +  need to get volunteers to be trained.
     * Look for cheaper quotes from other professionals (Bipin)
     * Buy our own cameras? (Rupali)
     * Open source solutions for streaming (amit)
     * Last option will be to have a tiny webcam doing live Hangout -- advantage is it has auto-archival on youtube.
       * amit: +1 for this option (or using the open source one for streaming)
Looking for Android ADB and Fastboot at Fedora?

It's simple, the tools are in the repository. It's no longer required to install manually.

Just type dnf install android-tools and enjoy system wide adb and fastboot! :-)

Souvenirs, pro Flisol 2015 y más eventos…

A pocos días del FLISOL 2015 la comunidad Fedora Perú como el año anterior está apoyando en la organización del evento, en las ciudades de Lima, Cusco, Puno e Iquitos se realizarán diversas charlas y talleres con representantes de la comunidad, para hacer mayor difusión y llegar a más gente se han elaborado banners, dvds y pines que serán distribuidos en el evento a las personas interesas en Fedora. Esperar contar con gran participación de estudiantes, profesionales, aficionados y otros interesados en el Software Libre, de nuestra parte haremos todo lo posible para que los eventos cumplan con los objetivos propuestos. Acompañamos a este  documento algunas imágenes tomadas al momento de recoger los trabajo enviados a hacer.

1 2 4 IMG_20150421_172640972 IMG_20150421_173253593 IMG_20150421_173259673 IMG_20150421_173458678_HDR IMG_20150421_173506546 IMG_20150421_175636905 IMG_20150421_175640617_HDR IMG_20150421_175702885 IMG_20150423_175739915 IMG_20150423_175754478 IMG_20150423_175804587 IMG_20150423_175925358

April 23, 2015

App curso de C++

Estoy interesado en crear una app que brinde tutoriales de c++ para los estudiantes que estén empezando a estudiar sistemas y para todo aquel que este interesado en este tema y así hacer mas accesible la educación.

La aplicación contaría con una introducción y guía de los primeros pasos así como también de ejercicios que podrá desarrollar desde el móvil y una guía del ejercicio que solo se desbloqueara una vez aya completado el 70% del ejercicio.

Me surgió la idea al ver a unos compañeros en la Universidad de nuevo ingreso que tenían problemas con este lenguaje prácticamente no entendían nada y decidí ayudarlos en ese momento se me ocurrió ya que no e visto ninguna app así y así poder ayudar a estudiantes a entender este maravilloso lenguaje ya que muchos desisten de estudiar sistema porque al principio se les hace difícil entender la lógica de programación y de esta forma podemos ayudarlos a no renunciar.

Todo el que este interesado en este proyecto comuníquese conmigo a mi correo belzasar2@gmail.com

Fedora: Comandos básicos para la terminal [Parte I]

Hoy a eso de las 10 de la mañana, tal vez un poco más estaba como siempre entregando un poco de ocio a mis contactos por mi mensajero, cuando me pareció gracioso -en el grupo de Fedora en el que estoy afiliado- hacer la típica broma de arreglar un problema con rm -rf, por lo que me hicieron un llamado de atención -dar de baja- si daba tal sugerencia ya que algunos de los integrantes no sabían el significado de ese comando. Claro que el comando por sí sólo era inofensivo sin determinar una ruta, pero el problema de mi compañero venía por los lares de Fedora People por lo que podría hacer un problema grave si en la ruta utilizaba ~/. Para no alargar las miles de complicaciones -y que por mi gran broma hubiera hecho- decidí crear un post con una leve recopilación de los principales comandos que debes conocer para manejar -de manera básica- la terminal.

Crear, copiar, mover y eliminar

Es básico saber navegar entre directorios, para esto lo primero que debes conocer es la ruta en la que te encuentras, por lo que $ pwd es el primer comando que les enseñaré. Al ingresarlo nos liberará la información requerida, en este caso nos dirá que estamos en nuestra carpeta persona /home/[su_nombre_de_usuario], el siguiente sería $ ls este nos permite saber que hay en el directorio en el que nos encontramos, como sabemos nos encontramos en nuestra carpeta personal (/home/[su_nombre_de_usuario]) por lo que nos enlistará si tenemos archivos o directorios dentro de esta ruta, los directorios se nos muestra con color azul y los archivos de color blanco. $ ls -t nos mostraría una lista de directorios y archivos que contenga la ruta en donde estamos con la añaditura de que serán ordenados por fecha de modificación y $ ls -a nos muestra todos los archivos y directorios contando los ocultos. Por cuestión de agilizar la información a continuación los mostraré en una pequeña lista:

Creación de directorios:

$ mkdir [nombre_del_directorio]: Es el comando que utilizamos para crear directorios.

$ mkdir -v [nombre_del_directorio]:  Se crea el directorio pero con un mensaje de confirmación.


$ rm [archivo o directorio]: utilizado para eliminar tanto archivos como directorios.

$ rm -rf [archivo o directorio]: (el comando de la broma) se nos elimina a fuerza y sin preguntar el archivo o directorio que determinemos en la ruta.

Mover archivos:

$ mv [ruta del archivo a mover] [ruta a donde lo vamos a mover]: en el primer recuadro debemos mostrarle a la terminal que archivo vamos a mover y en el segundo a donde será movido. Por ejemplo, tengo el archivo en la ruta ~/Descargas/imagen.jpg y quiero moverlo a ~/Imagenes entonces sería algo así:

$ mv  ~/Descargas/imagen.jpg ~/Imagenes

Copiar archivos o ficheros:

$ cp [ruta original] [ruta destino]: Nos copia de una ruta a otra.

Por ahora estos son los comandos más básicos que se debe conocer antes de utilizar la terminal, gracias a que con esta información te ayudará a deducir futuros comandos o acciones que hagas en Fedora. Será hasta la próxima publicación.

Redesign of spins.fedoraproject.org; Help make your spin rock!

Robyduck and I have been working on a total revamp of spins.fedoraproject.org. Behold, what spins.fpo looks like today:

spins.fedoraproject.org front page screenshot

spins.fedoraproject.org front page screenshot

Design Suite spin details page screenshot from the current spins.fedoraproject.org.

Design Suite spin details page screenshot from the current spins.fedoraproject.org.

Different kinds of spins

So one issue we have with spins is that there are different *kinds* of spins:

  • Desktop Spins There are desktop spins that each feature a different desktop environment on top of Fedora. While you can install multiple desktop environments by default, most people stick to one most of the time, and you certainly can’t use more than one in a given session. These spins are much more about the environment you use Fedora in rather than applications layered on top.
  • Functional Spins There are functional spins that consist of application bundles and configuration that you could honestly package-group install on any desktop and be able to use productively – Games, Design Suite, Robotics, etc. They are more purpose-directed than the desktop spins, which are more for general computing environments.
  • ARM builds (These aren’t actually spins but fell into the fray as they needed a home too!) Now that ARM is a top-level / supported architecture, we have ARM builds for many versions of Fedora. These images are solely architecture-based and cater to a very specific community and very specific use cases / hardware beyond traditional servers, workstations, and laptops.

We made a decision to split the desktop spins away from the functional spins. Functional spins will be housed at a new site catered specifically for them: labs.fedoraproject.org. ARM builds will also have their own one-page site with references to important documentation and the Fedora ARM community as well.

Here’s a rough diagram to illustrate:

diagram showing four different fedora sites

Desktop Spins (spins.fpo)

(These mockups are huge by the way. Sorry :) )

For the front page of the spins.fedoraproject.org site – since they are all desktops, we thought a full-width, large-size screenshot of what the desktop looks like in that spin would help folks figure out which ones they wanted to explore. (Note this mockup does not include Sugar but Sugar will be included in the final design:)

spins.fpo mockup

spins.fpo mockup

Rather than the tabbed approach we use today, we decided to consolidate all of the information on each spin’s individual details page to a one-pager. Spin SIGs can provide as much or as little data about the spin as they like. There are section they can use to highlight specific apps or features of their desktop, or they can opt to not use that display and instead just focus on the description and support content.

Desktop spin details page

Desktop spin details page

Functional Spins (labs.fpo)

The functional spins are more domain / goal-oriented than the desktop spins, so the previews on the front page are smaller and don’t necessarily feature desktop screenshots.

labs.fpo front page mockup

labs.fpo front page mockup

Similar to how the desktop spins’ details pages work, the lab spins details pages are one-pagers as compared to their current multi-tab incarnations. Again, the SIGs in charge can get as detailed or as brief as they’d like. Here’s the Design Suite’s details page:

labs.fpo details page mockup

labs.fpo details page mockup


So I’m still sorting out some issues with the usage of the ARM trademark here, so none of this is super-final in terms of the graphic design / lack of trademark notices / disclaimers / etc. This is strictly an incomplete work-in-progress. That being said, I’ve been picking the #fedora-arm folks’ brains a lot lately to understand our ARM offerings, their use cases, and ideal ways to represent them for the target audience. My thinking here is a simple one-pager that lists out all of the options by the major usage categories – headless and desktop computing – and just making it really easy to find the version you need across all of the many available options. The other thing here that the #fedora-devel and #fedora-arm folks suggested are links to the ARM wiki documentation for installing these images as well as references to the Fedora ARM mailing list and IRC channels to provide some support for folks using the page.

Anyway here’s where that mockup is at now:

Fedora builds for ARM mockup

Fedora builds for ARM mockup

Whoah cool. You guys have it all under control then?



We need your help. There are so many spins and versions of Fedora we’re juggling here, and neither of us is an expert in all or even most of them. We’re trying to adapt / convert the existing content / assets for these spins/versions of Fedora, but we really need help from the folks who maintain / use these spins to fully develop the content we need for their pages to come out looking great.

Robyduck sent out a bunch of messages to the various SIGs involved but we haven’t gotten a great response yet. Time is short to get these pages built in time for F22, so we really need all the help we can get. If you are an owner or even interested user in any of the spins featured in these mockups (or ARM,) can you get in touch and help us perfect the content for your spin / ARM build of interest?

Thanks :)

By the way, you can follow the process of the mockups here in the git repo for them. Robyduck is coding them up about as fast as I can crank designs out but I am sure he would appreciate some coding assistance too!!

Thank you for your feedback!

I just wanted to say that you to everyone who commented and provided Feedback on my last blog entry where I asked for feedback on what would make you switch to Fedora Workstation. We will take all that feedback and incorporate it into our Fedora Workstation 23 planning. So a big thanks to all of you!

Fedora Security Team’s 90-day Challenge

Earlier this month the Fedora Security Team started a 90-day challenge to close all critical and important CVEs in Fedora that came out in 2014 and before.  These bugs include packages affected in both Fedora and EPEL repositories.  Since we started the process we’ve made some good progress.

Of the thirty-eight Important CVE bugs, six have been closed, three are on QA, and the rest are open.  The one critical bug, rubygems-activesupport in EPEL, still remains but maybe fixed as early as this week.

Want to help?  Please join us in helping make Fedora (and EPEL) and safer place and pitch in to help close these security bugs.

All systems go
New status good: Everything seems to be working. for services: Fedora Wiki, Fedora People, Zodbot IRC bot, The Koji Buildsystem, Darkserver, Tagger, Package Database, Fedora pastebin service, Blockerbugs, Badges, FedoraHosted.org Services, Mirror Manager, FedOAuth, Mirror List, Package maintainers git repositories, Account System, Fedora websites, Documentation website, COPR Build System, Package Updates Manager, Ask Fedora, Fedora Packages App, FreeMedia, Fedora Messaging Bus, Fedora elections, Mailing Lists, Fedora Calendar
Minor service disruption
New status minor: Unplanned outage in one of our datacenter, may affect most of our application depending on your location for services: Fedora Wiki, Fedora People, Zodbot IRC bot, The Koji Buildsystem, Darkserver, Tagger, Package Database, Fedora pastebin service, Blockerbugs, Badges, FedoraHosted.org Services, Mirror Manager, FedOAuth, Mirror List, Package maintainers git repositories, Account System, Fedora websites, Documentation website, COPR Build System, Package Updates Manager, Ask Fedora, Fedora Packages App, FreeMedia, Fedora Messaging Bus, Fedora elections, Mailing Lists, Fedora Calendar
First beta of syslog-ng 3.7 released with Java and Python support, interactive configuration debugger
The first beta of syslog-ng 3.7 was released last week. The highlights of this release include Java and Python support merged from the syslog-ng incubator and an interactive syslog-ng.conf debugger. Other features include batched event sending to riemann, IPv6 netmask filter, and the HOSTID and UNIQID macros. For a complete list of changes, check https://github.com/balabit/syslog-ng/releases/tag/syslog-ng-3.7.0beta1 […]
Resource optimization capabilities introduced in latest JBoss BPM Suite and JBoss BRMS releases

Resources Optimization

Organizations of all sizes and across many industries must orchestrate and plan daily business operations, such as scheduling, vehicle routing, or timetabling. Many organizations must be able to cope with changing and increasing demands on the business with a limited set of resources, and quickly adapt plans when established processes are interrupted by unanticipated resource changes.

<iframe allowfullscreen="true" class="youtube-player" frameborder="0" height="289" src="https://www.youtube.com/embed/f4jIWbQpjdE?version=3&amp;rel=1&amp;fs=1&amp;showsearch=0&amp;showinfo=1&amp;iv_load_policy=1&amp;wmode=transparent" type="text/html" width="460"></iframe>

Red Hat’s business resource planning technology helps enterprises use limited resources in a more cost effective manner. Applying rules-based technology in conjunction with business resource planning provides a unique and powerful combination that allows for greater scale and adaptability. The planner is included with a subscription to JBoss BRMS at no additional cost. All of the resource planning and business rules management components are included in Red Hat’s business process management offering, JBoss BPM Suite.

Ref :






Copr Repositories for Geany and Terminator are now Fedora 22 compatible
A Short note for everyone using one of my Copr repositories providing Geany, Geany-Plugins, Geany Tags or Terminator: With the release of Fedora 22 Beta I've built some new packages from current Git masters (Bazaar for Terminator) to be available for Fedora 22 as well.

You can use the dnf copr command set to enable the repositories in Fedora 22:

dnf copr enable dmaphy/Geany
dnf copr enable dmaphy/Geany-Plugins
dnf copr enable dmaphy/geany-tags
dnf copr enable dmaphy/Terminator
Flisol Panama

Flisol Panamá Conferencia de Software Libre Asiste este sábado 25 de abril de 2015 de 9:00 AM a 4:00 PM a la conferencia de software libre en la Universidad del Istmo UDI habrán charlas y talleres sobre el software libre como lo es Linux se estará instalando Linux Fedora a quien lo desee también se presentara la Raspberry Pi una computadora que cabe en la palma de tu mano. Este es el mayor evento de difusión de software libre que se realiza en latinoamérica y totalmente gratis no te lo pierdas.

April 22, 2015

Another amazing conf.kde.in !

Conf.kde.in 2015 –  KDE conference organized by passionate KDE India team. This year it took place in Amrita college, Kerala from 17th to 18th April.  Schedule of these two days conference included talks on various KDE applications, Qt tutorial,  how to contribute to KDE, etc. We also organized Qt workshop to give a hands-on feeling to attendees.  Slides and pictures from conference are available.


Compared to past conf.kde.in, I felt venue of this year pretty different because this college had very cultural touch as it was near to Ahsram, it also had beautiful beach around 10 minutes walking distance from venue, beautiful backwater flowing very near to Guest house we were staying, also teachers of college were interested and involved as well throughout conference and were personally taking care whether everything is fine or not.



After registration, first day of conference started with opening ceremony where college teachers involved in FOSS community, Pradeepto Bhattacharya and Noufal Ibrahim addressed it by lighting lamp and traditional college prayer.


This year we did something different and as a result we had a keynote speaker Noufal Ibrahim who is Kerala based and is founder of PyCon India and PSF board member since 2012. It was pleasure in listening to his talk Reusable software – the UNIX way. In his talk he showed how easily you can come to know what exactly a book is about by using few UNIX command – sort, ls, wc, grep, awk, tail, uniq. It was good to see the power of UNIX commands and people appreciating it.

Further Pradeepto gave brief introduction to what KDE is, its aim and objective. In addition to that Shantanu gave a glimpse of different awesome KDE applications and showed how beautiful KDE software and helpful community is.  To keep conference interactive, Shantanu announced among audience that whoever will ask or answer question will get Qt/KDE stickers and goodies and it really worked :D

In order to keep audience curious and interested, next talk was on Krita– Awesome digital Painting Software by Somsubhra Bair who is contributing to Krita from around 2 years.  He showed couple of beautiful videos about painting in Krita and talked what other powerful and amazing work you can do using krita.


Later Pinak Ahuja talked about his SoK experience and how he started contributing to KDE. This talk was quite motivating to attendees in order to getting started with KDE. To add more motivation and building confidence in attendees,  Shantanu gave Qt/QML basic tutorial and showed how easily you can create basic elements like Rectangle, images, etc in QML and how easily you can add animation to it. To give a hands-on experience we also added workshop for students in college lab where Qt creator and needed libraries were already set-up by local volunteers. Everyone enjoyed building basic application themselves and few of them were also able to do what Shantanu gave task. We all speakers were helping out attendees with problem and queries.



Day 2

Second day started with A tour to Marble project  by Sanjiban Bairagya where he talked about  different features of Marble like virtual tour from one place to another comprises of earth and also other planets like Mars. He also demonstrated how easily you can navigate from one place to another over globe.

Next was my talk where I talked this time on a different topic – Qt on Android.  I opted this topic because I knew there is lot of craze among students for creating android apps. So, I thought let me learn how to make Android app using Qt and talk on same. I demonstrated how easily you can run your Qt application on android and distribute generated .apk file to others and also how to publish app to Google play store. Android app which I created was Imgs and somehow I managed to publish it to Google play store. Attendees were very much interested in listening to this talks and it seems more than  50% of them had android phone and most of them were interested in creating their own Android application.



Further, talks were going on in conference room and in parallel we also conducted Qt/QtQuick workshop for few first year students who missed out in Day1. I was helping students with their doubts, issues and monitoring ensuring if everyone is on track. It was good to see that all first year college students were able to grasp whatever Shantanu demonstrated and were able to do it by own.

Interesting talk from Ashish Madeti on MPRIS support for multimedia applications. Ashish started his KDE journey from conf.kde.in 2014 and in one year he did really great work in KDE and especially in Plasma Media Center and Simon project in order to add MRIS support and enabling voice command in PMC. It was very good to see a student  giving talk who started his KDE journey from same conference, it felt rewarding and worth doing KDE conference in India :)


Last talk of the day and conference was by Karan Luthra on Trojitá project. Karan talked about what all features Trojitá provides and why to use it and how  to contribute into it. It was good to see a fast and lightweight  email client. Looking forward to try it out in my system and will see whether it fits my need or I should continue using Kmail.


At the end of conference, attendees and speakers were talking to each other and having discussion on  KDE projects they were interested on. I also distributed Fedora stickers sheets among attendees which I got from my Fedora friends and talked to few attendees/teachers regarding attending upcoming FudCon APAC conference.

Another conf.kde.in ended with the help of hard work involved by Organizers, volunteers and local college authorities. I was so excited to know how Harish who took initiation for organizing this year conf.kde.in met Pradeepto and rest all happened.  Many thanks to KDE eV for sponsoring me as well as other speakers to make this event successful. I am proud to be a KDE contributor and being a part of such an awesome and loving community. I hope with this year conf.kde.in we will get another few new member in our KDE family :)


Hackademics on Campus
I'd love to give a proper reckoning of the past 48 hours, but it would take a not-so-insignificant feat of editing...
[decause@chapeauxrouge story []]$ wc -w biella-*
 4521 biella-astra-raw.txt
 2486 biella-molly-guest-lecture.txt
 7007 total
7007 words total
Fedora: Multimedia y entretenimiento


Cuando llegué a Fedora lo primero que quise instalar fue Spotify y Steam ya que son las dos plataformas que utilizo para entretenerme (Música y video juegos respectivamente). Ya había tenía cierta experiencias de Spotify en Ubuntu por lo que tenía la certeza de que podría haber compatibilidad con Fedora -y así fue-. También utilizo VLC para ver vídeos ya sea locales o streaming, es el reproductor más completo y de open source que se puede encontrar en este aspecto. A continuación mostraré de manera rápida como instalar cada uno de ellos.


Al principio no encontraba como instalar adecuadamente Spotify, pero no fue difícil una respuesta concreta. Lo primero que debemos tener son los codecs de sonido, para esto utilizaremos rpmfusion. Los # quiere decir que debe habilitar el usuario root en ese momento. También es de considerar que todas las instalaciones elaboradas aquí son compatibles con Fedora 21.

# yum -y install gstreamer-plugins-bad gstreamer-plugins-bad-free-extras gstreamer-plugins-bad-nonfree gstreamer-plugins-ugly gstreamer-ffmpeg

#yum -y install gstreamer1-libav gstreamer1-plugins-bad-free-extras gstreamer1-plugins-bad-freeworld gstreamer1-plugins-base-tools gstreamer1-plugins-good-extras gstreamer1-plugins-ugly gstreamer1-plugins-bad-free gstreamer1-plugins-good gstreamer1-plugins-base gstreamer1

Luego de esto tendremos instalados los codecs ffmpeg lo siguiente que debemos hacer es instalar Spotify, que es muy simple:
# yum install Spotify
Y listo, con esto tendremos instalado Spotify en nuestro sistema.


Para instalar el repositorio de Steam soportado para fedora debemos, al igual que el tutorial anterior ingresar como root, luego copiar el siguiente comando:
yum-config-manager --add-repo=http://negativo17.org/repos/fedora-steam.repo
Así el siguiente paso será el siguiente:
yum -y install steam
Si ya está ejecutando un escritorio de 32 bits, es muy probable que usted tenga la mayoría de las dependencias ya instalados. Si está ejecutando un escritorio de 64 bits con drivers de Nvidia o AMD asegúrese de que tiene las librerías OpenGL de 32 bits apropiados instalados, de lo contrario Steam arrojará un “error GLX” al arrancar y los juegos no funcionarán.

Para terminar VLC es el más simple de instalar, la mayoría de las veces se puede deducir facilmente como instalar las aplicaciones de la siguiente forma: # yum install [nombre del repositorio] de este modo sabremos que para instalar VLC sólo debemos teclear# yum install VLC y listo, VLC en nuestro equipo.

Por ahora eso es todo y estaré proximamente compartiendo más acerca de Fedora.

Linux, camino y perseverancia.


Es fácil para cualquier persona hablar mal de GNU/Linux cuando en realidad nunca lo han utilizado. Recuerdo cuando era más jóven diambulaba por internet y me encontré con Ubuntu, no era la primera vez que escuchaba al respecto de este sistema, mi padre en más de una ocasión lo escuché mencionarlo. Fue en el colegio donde más lo utilicé, ya que en informática estabamos aprendiendo a utilizar los comandos, desde copiar archivos hasta crear nuevos usuarios, otorgar permisos entre otras cosas. Me gustó la interfaz aunque no me terminó de convencer la serie de bugs que algunas veces hacía inestable el sistema, en fin lo utilicé al rededor de medio año en toda mi vida pero admito que fue la distro con la que aprendí los comandos básicos de la terminal.

Había visto un par de veces elementary OS pero este sistema creaba una incompatibilidad con la tarjeta de red, por lo que fue el motivo principal que nunca me dispuse a utilizarlo y también por la simple razón de que se basaba en Ubuntu, después de ese odio-amor no quise saber más. Me atreví a probar OzonOS, me convenció un tanto la parte visual pero aún no existía -o existe- una versión estable así que lo eliminé, busco estabilidad no tanto visual, es lo menos que debe ofrecer un SO aunque no podía pedir mucho a un sistema que se mantiene en Beta. No fue hasta hace unas semanas cuando empezó mi verdadero amor por GNU/Linux y todo gracias a Fedora.


Muchos usuarios buscan comodidad, tener solamente un SO instalado en la computadora y poder realizar las tareas básicas: email, redes sociales, ofimática y juegos casuales si se les permite. Pero nunca se han preguntado como funciona, que beneficios trae o más que todo que contras. Ven a Linux como algo difícil, que deben saber una X cantidad de comandos para que funcione, cuando en cierta parte no es así. Existe una gran importancia en la terminal ya que es la principal herramienta que tenemos a nuestra disposición cuando llegamos a GNU/Linux ¿Por qué?

Un interfaz gráfico es beneficioso para usuarios nuevos ya que cualquiera podría controlar el sistema -con ciertas restricciones- pero el detalle es que, si el interfaz tiene algún error el funcionamiento no va a ser adecuado. Hubo un tiempo en el que también esperaba más una interfaz gráfica y detestaba buscar soluciones sobre como arreglar el sistema, yo sólo quería sacarle provecho y fin. Como dije anteriormente Ubuntu me creaba bugs que hacían más difícil el poder realizar las tareas básicas, pero al llegar a Fedora -de ahora en adelante hablaré sólo de este sistema- eso cambió ya que este sistema tiene la peculiaridad que sino puede descargar de la fuente todos los repositorios no instala nada, en pocas palabras: estabilidad. Regresando a la terminal, el eliminar la interfaz te queda sólo texto plano el cual puede ser revisado y estudiar el problema para su pronta solución. La comunidad ayuda a solucionar los problemas o a guiar a personas que no tenga ni pizca de conocimiento, esto gracias a la gran cantidad de colaboradores que ofrecen su tiempo para mantener el proyecto vivo.

Hablo de perseverancia ya que el compromiso hace que ames a Fedora. Por ejemplo, actualmente me encuentro en el grupo de Fedora Panamá en donde no llevo mucho tiempo pero me he comprometido a ayudar en cualquier aspecto que pueda, pero se preguntarán ¿Por qué unirse a un grupo de software libre o invertir mi tiempo en el?

Verán, estudio sistemas y el unirme a este tipo de proyectos me ayuda en la parte práctica de mi carrera ya que actualmente los servidores linux son los más utilizados y se usan lenguajes modernos que en mi universidad no se dictan, tales como Python o Ruby, esto asegura que me prepare para el futuro que me espera. Pero no sólo Fedora es útil para un estudiante de sistemas, sino para diseñadores, oficinistas, escritores, etc. Por el gran número de herramientas que ofrecen de manera gratuita gracias a sus licencias Creative Commons.
Apenas llevo un par de semanas en el proyecto y me encuentro muy a gusto por la cantidad de contenido que he podido aprender, además de que la comunidad me ha tratado muy bien y poseen paciencia -debido a que pregunto demasiado para así aprender-, espero disponer del tiempo necesario para seguir contribuyendo.  Un dato cuiroso es la cantidad de paises hispano-hablantes que han creado leyes apoyando el software libre alegando poder tener más control y flexibilidad que el software privativo. Por ahora me despido, planeo fecuentemente escribir por este medio contando mis experiencias y enseñanzas dentro del universo Fedora.

Enter the Soylent

Thank you everyone for your input and advice on my previous post about Soylent. Folks seem pretty divided on this particular lifehack, and now I have a much better idea of why, and what the shortcomings of Soylent's current formula are.

Though there is much to be desired in the 1.4 version of Soylent, it is better than the 1.0 version of Drive-Thru nutrition that I've been apt to subsist upon as of late.

I've only got enough for a couple of days, but that should be enough to know whether or not I can stomach it. So far, I've lucked out and I don't hate the taste, though I did wait until I was *rilly* hungry before "eating" to trick my body into enjoying it more ;)

Meal #1 was a success, and I'm bringing Meal #2 with me today to campus.

Fedora Design Team Update

Fedora Design Team Logo

Fedora Design Team Meeting 21 April 2015



  • Libre Graphics Meeting: decause asked if any team members are planning to go to Libre Graphics Meeting 2015 next week. He and riecatnor were thinking about going. Nobody else in the meeting had plans to go.
  • Flock talk proposal deadline extension: The deadline for Flock talk proposals has been extended to May 2, so we reminded folks to get their design team talk proposals in.
  • Fedora websites update: Mo noted that she and robyduck have made a lot of progress on the spins.fedoraproject.org redesign and the new labs.fpo website. If you are interested in the work it’s in github: https://github.com/fedoradesign/fedora-spins.

Tickets Needing Feedback

Tickets Needing Updates

Tickets Needing Triage

  • Update Design Team Wiki – Kirk and Yogi decided to take this one on as a team and have already made some progress!

Completed Tickets

LinuxFest NorthWest Ad


Maria did a beautiful job on this design. We closed the ticket since it’s all complete!

Tickets Open For You to Take!

We triaged this ticket in the meeting and it’s all ready for a designer to pick it up and work on it! Could that be you? :)

See you next time?

Our meetings are every 2 weeks; we send reminders to the design-team mailing list and you can also find out if there is a meeting by checking out the design team category on FedoCal.

Regular expressions and recommended practices

Whenever a security person crosses a vulnerability report, one of the the first steps is to ensure that the reported problem is actually a vulnerability. Usually, the issue falls into well known and studied categories and this step is done rather quickly. Occasionally, however, one can come across bugs where this initial triage is a bit more problematic. This blog post is about such an issue, which will ultimately lead us to the concept of “recommended practice”.

What happened?

On July 31st 2014, Maksymilian Arciemowicz of cxsecurity reported that “C++11 [is] insecure by default.”, with upstream GCC bugs 61601 and 61582. LLVM/Clang’s libc++ didn’t dodge the bullet either, more details are available in LLVM bug 20291.

Not everybody can be bothered to go through so many links, so here is a quick summary: C++11, a new C++ standard approved in 2011, introduced support for regular expressions. Regular expressions (regexes from here on) are an amazingly powerful processing tool – but one that can become extremely complex to handle correctly. Not only can the regex itself become hideous and hard to understand, but also the way how the regex engine deals with it can lead to all sorts of problems. If certain complex regexes are passed to a regex engine, the engine can quickly out-grow the available CPU and memory constraints while trying to process the expression, possibly leading to a catastrophic event, which some call ReDoS, a “regular expression denial of service”.

This is exactly what Maksymilian Arciemowicz exploits: he passes specially crafted regexes to the regex engines provided by the C++11 implementations of GCC and Clang, causing them to use a huge amount of CPU resources or even crash (e.g. due to extreme recursion, which will exhaust all the available stack space, leading to a stack-overflow).

Is it a vulnerability?

CPU exhaustion and crashes are often good indicators for a vulnerability. Additionally, the C++11 standard even suggests error return codes for the exact problems triggered, but the implementations at hand fail to catch these situations. So, this must be a vulnerability, right? Well, this is the point where opinions differ. In order to understand why, it’s necessary to introduce a new concept:

The “recommended practice” concept

“Recommended practice” is essentially a mix of common sense and dos and don’ts. A huge problem is that they are informal, so there’s no ultimate guide on the subject, which leaves best practices open to personal experiences and opinion. Nevertheless, the vast majority of the programming community should know about the dangers of regular expressions; dangers just like the issues Maksymilian Arciemowicz reported in GCC/Clang. That said, passing arbitrary, unfiltered regexes from an untrusted source to the regex engine should be considered as a recommended practice case of “don’t do this; it’ll blow up in your face big time”.

To further clear this up: if an application uses a perfectly reasonable, well defined regex and the application crashes because the regex engine chocked when processing certain specially crafted input, it’s (most likely) a vulnerability in the regex engine. However, if the application uses a regex thought to be well defined, efficient and trusted, but turns out to e.g. take overly long to process certain specially crafted input, while other, more efficient regexes will do the job just fine, it’s (probably) a vulnerability in the application. But if untrusted regexes are passed to the regex engine without somehow filtering them for sanity first (which is incredibly hard to do for anything but the simplest of regexes, so better to avoid it), it is violating what a lot of people believe to be recommended practice, and thus it is often not considered to be a strict vulnerability in the regex engine.

So, next time you feel inclined to pass regexes verbatim to the engine, you’ll hopefully remember that it’s not a good idea and refrain from doing so. If you have done so in the past, you should probably go ahead and fix it.

"Achieving Community Goals with Fedora" + Anroid Humla @FUDCon India 2015
now that the list of speakers for fudcon.in 2015 is up, i am sad and happy at the same time.
I am really sad not to attend this year - but more than happy to see some of the projects/partnerships we tried to catalyze and to connect to the Fedora community have been selected for talks!
Thanks to the organizers for the amazing work with organization and the smart choice ;)

Maybe you remember our efforts to support the tibetan community -
if you want to get to get it first hand, please do not miss the talk by Tenzin Chokden from the tibetan community in Dharamsala

Also, some of you know the story from my last fudcon in Pune in 2011 where the founders of the the nullcon wanted to meet me and i ignored them completely, because i was to excited about giving my talk? ;)
In the end, all turned out into becoming a close friendship with the indian null community and  especially with Payatu the company behind it  - and now that FUDCon is coming back to Pune - Sneha Rajguru and Rutwij Kulkarni as part of the tireless nullcon team are giving a humla session on Android.

If you are around Pune end of June - please visit the fudcon and please give these guys your support by attending the sessions! 
Fedora 22 beta disponible
Ya se ha liberado la beta de Fedora 22, se pueden descargar las imágenes desde los siguientes enlaces Fedora 22 Beta Server Fedora 22 Beta Workstation Fedora 22 Beta Cloud
On Average
SO mentioned today that the npm packages have low quality standard than NuGet ones. User of a package usually need to specify a version, or one must prepare for unexpected breakage. This is so true that even npm or NuGet itself can upgrade without taking any kind of compatibility measure, a best approach of using NuGet is usually first "nuget --update self", which does not always work. SO also mentioned that a company should not spend too much effort on improving the platform, which unfortunately is becoming harder because all the trending open source projects have fewer commercial support than before.

What happened?

Software is become easier because the number of tools, documents, workers, are exploding. Previously only a few people can define a language, create standard libraries, debate on standards. Now everything has to be fast because so many people are doing it. Make a prototype, make it run on most cases, and then move on because it is obsoleted on the day it is created. It is a great time to have so many alternatives, it is also a bad time that few can get consolidated and perfected.

On the other hand, software is becoming personal. Previously when we use any commercial company backed software, such as CLR, there is not a single name related with it. There must be lots of genius developers and talented teams, but in the end what user will know is the M$ company product. There was no such thing as using a company's product to build a personal brand. I remember many books will introduce authors as "have ever worked on core CLR" or something similar, and that is the best those authors can get. How about now? Anything is backed by a concrete person. When there is a nice npm library, it often does not have its own website, but comes from some GitHub repository belonged to someone, who often created it single-handedly. Software is no longer a mystery. It used to be hard to know who voted for and implemented which feature in a standard library. But now the process is largely open, the commit history is there to read, there are ways to know and reach out to a name, and -- not only look up to those genius that made all kinds of decisions -- but debate and fork and do many more, or simply watch for stupidity/failure of a giant. The software world is so large and there are so many hero to worship, then people stopped to worship heros anymore.

In the age of "thinking in Java" or "thinking in C++", there are handful of authors who can write such books, capitalize all the knowledge before a new standard for better C++ can be made. Nowadays who is going to write such books for each new technology? Even a minor version change can have huge updates in design. No one should wait until a book is published to learn a technology. Read the documents or even source code is faster. That is another level of destruction. One way to look at this is on average the worker's quality is steadly rising. When everyone is thinking in something and get reasonable understanding, such books are no longer catch-all or ultimate sources of information.

Going forward, people will waste fewer time to think, because the high level of education will make learning new technology so easy, also the new technology will be so easy to use. And new things will come out even more quickly, have more personal color (which means user have to tolerate more instability, but enjoy more specialized enhancements.) The competition goes that way. Andrew gives, Bill takes. In the near future we'll see a project referenced not by its pet name, but simply by an author name plus the year/month it is made, and it is perfect for that moment and for nothing else.
On the last Saturday, apr 18, it was my fifth participation and second as organizer of SoliSC located...
On the last Saturday, apr 18, it was my fifth participation and second as organizer of SoliSC located in Florianopolis in Santa Catarina state.
The people who participated of event could pick up stickers of Fedora Next and install Fedora at Makers Space, a hackerspace of embedded systems. #fedora #solisc2015 #linux #Next  

SoliSC 2015

Ssst Telah Hadir Fedora 22 versi Beta
Info mengenai versi beta ini silahkan langsung ke Fedora Magazine
Fedora @ HackRU Spring 2015

Fedora attended HackRU spring 2015, a hackathon centered around students. Hackathons are events where developers from surrounding areas or even across the world gather to create cool projects over a period of time, usually a weekend.

HackRU was held on April 18th to 19th at Rutgers University in New Brunswick, NJ. Around a thousand hackers attended the 24-hour event, using their imagination and skills to create a minimum viable product during the allocated time. Fedora sponsored the event; we were able to obtain a booth and distribute our swag while answering their questions and mentoring hackers. We gave away stickers, F21 install disks, and shirts.

Overall, the atmosphere at HackRU was filled with ambition, music, and the hackers’ chatter. I received many questions while running the Fedora booth, from both long-term Linux users and newbies. Some queried on the nature of our organisation, while others asked us about our advantages over other distributions. Many of the attendees of the event were somewhat familiar with Linux, but only a handful actively used Fedora. The stack of F21 Workstation DVDs was quickly depleted, requiring frequent restocking. By the end of the event, we were able to give out all of our DVDs, many hundred disks.

We were asked questions about Linux, Fedora, and our benefits over other distros. Some interested users also asked about contributing. The most surprising question that we received on a stable basis, however, was whether Fedora was free. We answered positively, free as in beer and free as in freedom. Some were still doubtful, asking whether it was only free at the event or free forever. We answered “free forever”, of course. We were glad to be able to inform these attendees about FOSS, and the free goodies that collaboration can create.



The friendly hackers at MLH were able to capture the whole event on camera. The photo album can be found on their Facebook page, or at the link below:

MLH HackRU Pictures

When we asked how many people had open sourced their hacks at the closing ceremonies, almost everyone raised their hands. We were glad many hackers knew of open source and were willing to allow the community to inspect their hack’s code.

We were thoroughly impressed by many of the creative hacks that the event attendees created, but we especially loved reusable hacks that could benefit the community beyond simple use. The best reusable hacks we found included a college book exchange application that could possibly be expanded to many schools across the country, a Pebble authentication tool, a Pebble remote, and a Bluetooth mesh network. We picked out some of the best possibly reusable hacks and described them below.

The app that we saw the most reuse potential in was a college book exchange app, by Shawn Pan. The app was very simplistic and worked smoothly, but also had the potential, as a MVP, to be expanded to schools around the country. Having a college book exchange website in every campus would greatly reduce the costs of a college education, expanding opportunities to many more people. His app can be found on GitHub here: https://github.com/shawniscool/TricoBookExchange 

In addition, we found another useful and reusable hack created by Fox Wilson. He worked on his app by himself, creating SignIn with Pebble. His app allows website owners to authenticate users using their Pebble watches. His app was very well-polished, and included one of the highest-quality code we found at the fast-paced event. You can find his app on GitHub, and even reuse his code in your own projects: https://github.com/fwilson42/signin-for-pebble

The Bluetooth mesh network was created by Grant Butler and Michael Selsky, as an iOS application. The source can be found on GitHub, here: https://github.com/grantjbutler/cork. We loved the idea of being able to communicate independently of the Internet, while using the devices we are already familiar with.

Another group of hackers, Vedant Mehta and Rishi Masand, created a cool “remote” app, named PebKey. It allows users to perform actions on their computer by a simple hand motion, with an accuracy we were impressed by. For instance, raising your hand could open a new window of your app of choice, without needing to perform any actions on your keyboard. Their app can be found on GitHub as well, here: https://github.com/darthbatman/KeyPeb

Altogether, HackRU was an amazing experience, both as a sponsor and as a maker. Lots of creativity flowed, ambitions achieved, and FOSS spread. We would love to interact with these students again, hopefully fostering a community of free and open source makers that will collaborate on future innovations that are not limited by proprietary licenses.

I think it was really neat to see a community-led open-source project like Fedora sponsoring a hackathon. It was definitely a great event, and I had a lot of fun developing my application and releasing it as a free and open source app. I hope future involvement of open source projects in the student hacker phenomenon can really spark the light of collaboration and create innovations that will be free for everyone to use and modify.

– event attendee, Fox Wilson



April 21, 2015

Sortie de Fedora 22 Beta

En ce mardi 21 avril, le Projet Fedora est fier de vous annoncer la sortie de Fedora 22 Béta. Bien entendu, qui dit Alpha, dit instabilité, développement, tests et bugs. Ne l'installez pas si vous ne savez pas ce que vous faites.

Cependant, il est important de la tester. En rapportant les bogues maintenant, la Fedora 22 stable sera plus stable encore et aura moins de risque de sortir en retard. Les versions en développements manquent de testeurs et de retours pour mener à bien leurs buts. La Fedora 22 stable devrait sortir aux alentours du 26 mai.

Par rapport à l'Alpha, si ce n'est des logiciels plus stables, il n'y a pas de changements importants. Voici un rappel de ce qu'il nous apporte :


  • Gnome 3.16 ;
  • Les notifications de Gnome-Shell ont été refondues, elles apparaissent dorénavant au sein du widget calendrier ;
  • Gnome terminal peut vous donner une notification quand une longue tâche est terminée ;
  • GDM, l'écran de connexion, utilise Wayland en lieu et place de X11. Le reste de Gnome utilise X11 par défaut (bien que Wayland soit disponible pour les plus courageux) ;
  • Gnome Logiciel prend la place de Gnome Packagekit pour installer les codecs ou polices additionnelles à la volée ;
  • ABRT (l'assistant de rapport de bogues) exploite les notifications et les contrôles de confidentialité de Gnome pour mieux réussir sa mission ;
  • L'intégration de Qt au sein du thème de Gnome Shell (Adwaita) est fini. De plus le thème par défaut de Gnome-Shell a été remanié ;
  • Nautilus a subi une plus forte intégration à Gnome-Shell, notamment pour les menus contextuels ;
  • libinput, celui qui gère les entrées de périphériques de Wayland, est utilisé par défaut dans X11 et Wayland, amorçant la transition vers Wayland ;
  • Plasma 5 est maintenant la version par défaut de KDE spin ;
  • WINE utilise le support de mesa pour Direct3D pour la vidéo (meilleures performances et meilleure compatibilité) ;
  • Support de qtile, un gestionnaire de fenêtre pavant en Python ;

Administration système

  • Le gestionnaire de paquet Yum, par défaut depuis Fedora Core 1, laisse place à DNF par défaut ;
  • DNF cherche et installe les extensions de langages de vos logiciels préférés (comme Libreoffice ou KDE) depuis la langue du système ;
  • Python 3 poursuit sa progression comme version par défaut du langage du système ;
  • Ajout d'un assistant de migration de version de Fedora pour s'assurer que tout se passe bien et qu'on n'oublie rien ;
  • Ajout de Vagrant, un utilitaire pour automatiser la création de VM de développement ;
  • Par ailleurs, Vagrant peut exploiter les images Fedora Atomic Host et Fedora Cloud pour générer les images ;
  • Ajout de Tunir, un logiciel d'aide à intégration continue utilisée notamment pour les images de Fedora Cloud ;
  • Ajout de dbxtool, pour autoriser la mise à jours de logiciels signés pour l'UEFI si la version utilisée du programme est vulnérable tout en refusant dans les autres cas ;
  • BIND 9.10 ;

Projet Fedora

  • Gradle 2.0 ;
  • Fedora Atomic Host : une implémentation du projet Fedora du Projet Atomic ;


  • DJango 1.8 ;
  • wXPython 3.0 ;
  • Python dateutil 2.4 ;
  • Boost 1.58 ;
  • GCC 5 ;
  • Ruby 2.2 ;
  • Ruby on Rails 4.2 ;
  • Perl 5.20 ;
  • GHC 5.8 ;
  • Glibc supporte Uricode 7.0 ;

Et d'autres encore ! Notons que les préparatifs pour Fedora 23 débutent doucement. Il est annoncé que Wayland remplacera X11 par défaut avec XWayland pour la compatibilité en option. De même, Python 3 sera installé par défaut, Python 2 ne sera disponible que dans les dépôts.

Si l'aventure vous intéresse, les images sont disponibles par Torrent : http://torrent.fedoraproject.org/ En cas de bogue, n'oubliez pas de relire la documentation pour signaler les anomalies sur le BugZilla.

Bons tests à tous !

Effective continuous integration for Spark projects

Silex is a small library of helper code intended to make it easier to build real-world Spark applications;1 most of it is factored out from applications we’ve developed internally at Red Hat. We have a couple of long-term goals for the Silex project:

  • We want to make it very easy for us to spin up on new data-processing problems without spending a lot of time dealing with accidental complexity, and
  • we want to have a generally-useful standard library atop Spark that provides primitives and solutions to simplify common tasks and reflects best practices as we discover them.

Part of having a library that people will want to use is having a quality test suite and continuous integration. There are some tricks to developing automated tests for Spark applications, but even keeping those in mind may not be sufficient to let you test your Spark apps in a hosted CI environment. This post will show you how to bridge the gap.

Continuous integration challenges

Since we want to make it easy to review contributions to Silex, I set up Travis CI to watch branches and pull requests. Travis CI is a great service, but if you’re used to running tests locally, you might have some problems running Spark-based tests under hosted CI environments. Here’s what we learned:

  • When running tests locally, creating a Spark context with local[*] (in order to use all of the available cores on your machine) might be a good idea. However, a hosted CI environment may offer you a lot of cores but relatively little memory, so your tests might be killed because each Spark executor has nontrivial memory overhead. Instead, consider limiting your code to use fewer cores.
  • If you’re using Kryo serialization and have set the spark.kryoserializer.buffer.mb property to something large (perhaps because you often have serialization buffer crashes in production), don’t be surprised if you run out of memory while running in CI. Spark doesn’t share serializers between threads, so you could be allocating a huge buffer for each thread even if your test code doesn’t need to serialize anything all that large.2
  • Spark SQL (at least as of version 1.3.1) defaults to creating 200 partitions for shuffles. This is probably a good starting place for real-world data, but it’s overkill for test cases running on a single machine. Furthermore, since each partition has some extra memory overhead, it’s another possible cause of OOMEs.

Fixing the problems

Silex provides an application skeleton trait, and we use a class extending this trait to package up Spark and SQL contexts for test cases. That class isn’t currently part of the public Silex API, but you can see what it looks like here:

<figure class="code"><figcaption>excerpt from app.scala</figcaption>
private [silex] class TestConsoleApp(val suppliedMaster: String = "local[2]") extends AppCommon {
  override def master = suppliedMaster
  override def appName = "console"

  addConfig( {(conf: SparkConf) => conf.set("spark.kryoserializer.buffer.mb", "2")})

  def appMain(args: Array[String]) {
    // this never runs

As you can see, we allow users to specify a Spark master URL but default to using two cores locally. Furthermore, we use the addConfig function from AppCommon — which takes a SparkConf and returns a modified SparkConf — to ensure that our Kryo buffer size is the Spark default of 2 mb, rather than the larger Silex default.

If you’re used to writing test code that exercises Spark, you probably already have boilerplate (using something like ScalaTest’s BeforeAndAfterEach) to set up and tear down a Spark context for each test case. We set the Spark SQL property to control parallelism in data frame and SQL shuffles in the test setup code itself:

<figure class="code"><figcaption>excerpt from app.scala</figcaption>
import org.scalatest._

import com.redhat.et.silex.app.TestConsoleApp

trait PerTestSparkContext extends BeforeAndAfterEach {
  self: BeforeAndAfterEach with Suite =>

  private var app: TestConsoleApp = null

  def context = app.context
  def sqlContext = app.sqlContext

  override def beforeEach() {
    app = new TestConsoleApp()

    app.sqlContext.setConf("spark.sql.shuffle.partitions", "10")


  override def afterEach() {


Good CI is one of those things that makes it fun to develop software, but the accidental differences between a hosted environment and your local environment can be totally frustrating. By taking into account the constraints you’re likely to see when running in a resource-limited container on a CI server, you can help to ensure that your tests only fail when your code is actually broken.

  1. “Silex” is Latin for “flint,” which seemed like a good name for something that was intended to help people make things with sparks.

  2. Thanks to Erik Erlandson for noticing this (it even affected him in a test case he was running locally).

OVN and OpenStack Status – 2015-04-21

It has been a couple weeks since the last OVN status update. Here is a review of what has happened since that time.

ovn-nbd is now ovn-northd

Someone pointed out that the acronym “nbd” is used for “Network Block Device” and may exist in the same deployment as OVN.  To avoid any possible confusion, we renamed ovn-nbd to ovn-northd.

ovn-controller now exists

ovn-controller is the daemon that runs on every hypervisor or gateway.  The initial version of this daemon has been merged.  The current version of ovn-controller performs two important functions.

First, ovn-controller populates the Chassis table of the OVN_Southbound database.  Each row in the Chassis table represents a hypervisor or gateway running ovn-controller.  It contains information that identifies the chassis and what encapsulation types it supports.  If you run ovs-sandbox with OVN support enabled, it will run the following commands to configure ovn-controller:

ovs-vsctl set open . external-ids:system-id=56b18105-5706-46ef-80c4-ff20979ab068
ovs-vsctl set open . external-ids:ovn-remote=unix:"$sandbox"/db.sock
ovs-vsctl set open . external-ids:ovn-encap-type=vxlan
ovs-vsctl set open . external-ids:ovn-encap-ip=
ovs-vsctl add-br br-int

After setup is complete, we can check the OVN_Southbound table’s contents and see the corresponding Chassis entry:

Chassis table
_uuid                                encaps                                 gateway_ports name                                  
------------------------------------ -------------------------------------- ------------- --------------------------------------
2852bf00-db63-4732-8b44-a3bc689ed1bc [e1c1f7fc-409d-4f74-923a-fc6de8409f82] {}            "56b18105-5706-46ef-80c4-ff20979ab068"

Encap table
_uuid                                ip          options type 
------------------------------------ ----------- ------- -----
e1c1f7fc-409d-4f74-923a-fc6de8409f82 "" {}      vxlan

The other important task performed by the current version of ovn-controller is to monitor the local switch for ports being added that match up to logical ports created in OVN.  When a port is created on the local switch with an iface-id that matches the OVN logical port’s name, ovn-controller will update the Bindings table to specify that the port exists on this chassis.  Once this is done, ovn-northd will report that the port is up to the OVN_Northbound database.

$ ovsdb-client dump OVN_Southbound
Bindings table
_uuid                                chassis                                logical_port                           mac parent_port tag
------------------------------------ -------------------------------------- -------------------------------------- --- ----------- ---
2dc299fa-835b-4e42-aa82-3d2da523b4d9 "81b0f716-c957-43cf-b34e-87ae193f617a" "d03aa502-0d76-4c1e-8877-43778088c55c" []  []          [] 

$ ovn-nbctl lport-get-up d03aa502-0d76-4c1e-8877-43778088c55c

The next steps for ovn-controller are to program the local switch to create tunnels and flows as appropriate based on the contents of the OVN_Southbound database.  This is currently being worked on.

The Pipeline Table

The OVN_Southbound database has a table called Pipeline.  ovn-northd is responsible for translating the logical network elements defined in OVN_Northbound into entries in the Pipeline table of OVN_Southbound.  The first version of populating the Pipeline table has been merged. One thing that is particularly interesting here is that ovn-northd defines logical flows.  It does not have to figure out the detailed switch configuration for every chassis running ovn-controller.  ovn-controller is responsible for translating the logical flows into OpenFlow flows specific to the chassis.

The OVN_Southbound documentation has a good explanation of the contents of the Pipeline table.  If you’re familiar with OpenFlow, the format will be very familiar.

As a simple example, let’s just use ovn-nbctl to manually create a single logical switch that has 2 logical ports.

ovn-nbctl lswitch-add sw0
ovn-nbctl lport-add sw0 sw0-port1 
ovn-nbctl lport-add sw0 sw0-port2 
ovn-nbctl lport-set-macs sw0-port1 00:00:00:00:00:01
ovn-nbctl lport-set-macs sw0-port2 00:00:00:00:00:02

Now we can check out the resulting contents of the Pipeline table.  The output of ovsdb-client has been reordered to group the entries by table_id and priority. I’ve also cut off the _uuid column since it’s not important for understanding here.

Pipeline table
match                          priority table_id actions                                                                 logical_datapath
------------------------------ -------- -------- ----------------------------------------------------------------------- ------------------------------------
"eth.src[40]"                  100      0        drop                                                                    843a9a4a-8afc-41e2-bea1-5fa58874e109
vlan.present                   100      0        drop                                                                    843a9a4a-8afc-41e2-bea1-5fa58874e109
"inport == \"sw0-port1\""      50       0        resubmit                                                                843a9a4a-8afc-41e2-bea1-5fa58874e109
"inport == \"sw0-port2\""      50       0        resubmit                                                                843a9a4a-8afc-41e2-bea1-5fa58874e109
"1"                            0        0        drop                                                                    843a9a4a-8afc-41e2-bea1-5fa58874e109

"eth.dst[40]"                  100      1        "outport = \"sw0-port2\"; resubmit; outport = \"sw0-port1\"; resubmit;" 843a9a4a-8afc-41e2-bea1-5fa58874e109
"eth.dst == 00:00:00:00:00:01" 50       1        "outport = \"sw0-port1\"; resubmit;"                                    843a9a4a-8afc-41e2-bea1-5fa58874e109
"eth.dst == 00:00:00:00:00:02" 50       1        "outport = \"sw0-port2\"; resubmit;"                                    843a9a4a-8afc-41e2-bea1-5fa58874e109

"1"                            0        2        resubmit                                                                843a9a4a-8afc-41e2-bea1-5fa58874e109

"outport == \"sw0-port1\""     50       3        "output(\"sw0-port1\")"                                                 843a9a4a-8afc-41e2-bea1-5fa58874e109
"outport == \"sw0-port2\""     50       3        "output(\"sw0-port2\")"                                                 843a9a4a-8afc-41e2-bea1-5fa58874e109

In table 0, we’re dropping anything with a broadcast/multicast source MAC. We’re also dropping anything with a logical VLAN tag, as that doesn’t make sense. Next, if the packet comes from one of the ports connected to the logical switch, we will continue processing in table 1. Otherwise, we drop it.

In table 1, we will output the packet to all ports if the destination MAC is broadcast/multicast. Note that the output action to the source port is implicitly handled as a drop. Finally, we’ll set the output variable based on destination MAC address and continue processing in table 2.

Table 2 does nothing but continue to table 3. In the ovn-northd code, table 2 is where entries for ACLs go. ovn-nbctl does not currently support adding ACLs. This table is where Neutron will program security groups, but that’s not ready yet, either.

Table 3 handles sending the packet to the right output port based on the contents of the outport variable set back in table 1.

The logical_datapath column ties all of these rows together as implementing a single logical datapath, which in this case is an OVN logical switch.

There is one other item supported by ovn-northd that is not reflected in this example. The OVN_Northbound database has a port_security column for logical ports. Its contents are defined as “A set of L2 (Ethernet) or L3 (IPv4 or IPv6) addresses or L2+L3 pairs from which the logical port is allowed to send packets and to which it is allowed to receive packets.” If this were set here, table 0 would also handle ingress port security and table 3 would handle egress port security.

We will look at more detailed examples in future posts as both OVN and its Neutron integration progress further.

Neutron Integration

There have also been several changes to the Neutron integration for OVN in the last couple of weeks.  Since ovn-northd and ovn-controller are becoming more functional, the devstack integration runs both of these daemons, along with ovsdb-server and ovs-vswitchd.  That means that as you create networks and ports via the Neutron API, they will be created in OVN and result in Bindings and Pipeline updates.

We now also have a devstack CI job that runs against every patch proposed to the OVN Neutron integration.  It installs and runs Neutron with OVN.  Devstack also creates some default networks.  We still have a bit more work to do in OVN before we can expand this to actually test network connectivity.

Also related to testing, Terry Wilson submitted a patch to OVS that will allow us to publish the OVS Python bindings to PyPI.  The patch has been merged and Terry will soon be publishing the code to PyPI.  This will allow us to install the library for unit test jobs.

The original Neutron ML2 driver implementation used ovn-nbctl.  It has now been converted to use the Python ovsdb library, which should be much more efficient.  neutron-server will maintain an open connection to the OVN_Northbound database for all of its operations.

I’ve also been working on the necessary changes for creating a port in Neutron that is intended to be used by a container running inside a VM.  There is a python-neutronclient change and two changes needed to networking-ovn that I’m still testing.

There are some edge cases where a resource can be created in Neutron but fail before we’ve created it in OVN.  Gal Sagie is working on some code to get them back in sync.

Gal Sagie also has a patch up for the first step toward security group support.  We have to document how we will map Neutron security groups to rules in the OVN_Northbound ACL table.

One piece of information that is communicated back up to the OVN_Northbound database by OVN is the up state of a logical port.  Terry Wilson is working on having our Neutron driver consume that so that we can emit a notification when a port that was created becomes ready for use.  This notification gets turned into a callback to Nova to tell it the VIF is ready for use so the corresponding VM can be started.

Fedora 22 Beta Release!

Fedora 22 Beta Release Announcement

The Fedora 22 Beta release has arrived, with a preview of the latest free and open source technology under development. Take a peek inside!

What is the Beta release?

The Beta release contains all the exciting features of Fedora 22's editions in a form that anyone can help test. This testing, guided by the Fedora QA team, helps us target and identify bugs. When these bugs are fixed, we make a Beta release available. A Beta release is meant to be feature complete and bears a very strong resemblance to the third and final release. The final release of Fedora 22 is expected in May.

We need your help to make Fedora 22 the best release yet, so please take some time to download and try out the Beta and make sure the things that are important to you are working. If you find a bug, please report it – every bug you uncover (and/or help fix!) is a chance to improve the experience for millions of Fedora users worldwide.

Together, we can make Fedora rock-solid. We have a culture of coordinating new features and pushing fixes upstream as much as feasible, and your feedback will help improve not only Fedora but Linux and free software on the whole.

Base platform

  • Faster and better dependency management: Yum has been replaced with dnf as the default package manager. Dnf has very similar command line options and configuration files compared to yum but also has several major internal changes including using libsolv in coordination with friends from the openSUSE project for faster and better dependency management. dnf-yum provides automatic redirection from yum to dnf in the command line for compatibility. The classic yum command line tool renamed to yum-deprecated as a transitional step for tools still using it.

Fedora 22 Cloud

The Fedora 22 Cloud Edition builds on the work completed during the Fedora 21 cycle, and brings in a number of improvements that make Fedora 22 a superb choice for running Linux in the cloud.

Ready for the Fedora 22 release, we have:

  • The latest versions of rpm-ostree and rpm-ostree-toolbox. You can even use rpm-ostree-toolbox to generate your own Atomic hosts from a custom set of packages.

  • Introduction of the Atomic command line tool to help manage Linux containers on Atomic Hosts and update Atomic Hosts.

Fedora 22 Server

Fedora 22 Server Edition brings several changes that will improve Fedora for use as a server in your environment.

  • Database Server Role: Fedora 21 introduced Rolekit, a daemon for Linux systems that provides a stable D-Bus interface to manage deployment of server roles. The Fedora 22 release adds onto that work with a database server role based on PostgreSQL.

  • Cockpit Updates: The Cockpit Web-based management application has been updated to the latest upstream release which adds many new features as well as a modular design for adding new functionality.

  • XFS as default filesystem. XFS scales better for servers and can handle higher storage capacity and we have made it the default filesystem for Fedora 22 server users. Other filesystems including Ext4 will continue to be supported and the ability to choose them have been retained.

Fedora 22 Workstation

As always, Fedora carries a number of improvements to make life better for its desktop users and developers! Here's some of the goodness you'll get in Fedora 22 Workstation edition.


  • The GNOME Shell notification system has been redesigned and subsumed into the calendar widget.
  • The Terminal now notifies you when a long running job completes.
  • The login screen now uses Wayland by default with automatic fallback to Xorg when necessary. This is a transitional step towards replacing Xorg with Wayland by default in the next release and should have no user visible difference.
  • Installation of GStreamer codecs, fonts, and certain document types is now handled by Software, instead of gnome-packagekit.
  • The Automatic Bug Reporting Tool (ABRT) now features better notifications, and uses the privacy control panel in GNOME to control information sent.


  • The Nautilus file manager has been improved to use GActions, from the deprecated GtkAction APIs, for a better, more consistent experience.
  • The GNOME Shell has a refreshed theme for better usability.
  • The Qt/Adwaita theme is now code complete, and Qt notifications have been improved for smoother experience using Qt-based apps in Workstation.

Under the covers:

  • Consistent input handling for graphical applications is provided using libinput library which is now used for both X11 and Wayland.


Fedora spins are alternative versions of Fedora, tailored for various types of users via hand-picked application sets or customizations. You can browse all of the available spins via http://spins.fedoraproject.org. Some of the popular ones include:

Fedora 22 KDE Plasma spin

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 fully hardware-accelerated graphics stack based on OpenGL(ES).

Fedora 22 Xfce spin

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.

Issues and Details

This is an Beta release. As such, we expect that you may encounter bugs or missing features. To report issues encountered during testing, contact the Fedora QA team via the mailing list or in #fedora-qa on freenode.

As testing progresses, common issues are tracked on the Common F22 Bugs page:



While Fedora 22 is still under active development, we have a number of new features developed in parallel for Fedora 23 as well. While all of these features are work in progress and the plans have not been finalized, we want to highlight a few major changes expected and invite your early testing and feedback.

  • Wayland by default for Fedora 23 Workstation. XWayland will continue to be provided for compatibility with applications using X.

  • Python 3 by default for Fedora 23 Workstation: While most of the default applications are already using Python 3 in Fedora 22, Fedora 23 Workstation will only include Python 3 by default. Python 2 will continue to be included in the repositories.

  • A Vagrant image for Fedora 23 Atomic Host and Cloud Images. We're supplying Vagrant boxes that work with KVM or VirtualBox, so users on Fedora will be able to easily consume the Vagrant images with KVM, and users on Mac OS X or Windows can use the VirtualBox image.

For tips on reporting a bug effectively, read "how to file a bug report":


Release Schedule

The full release schedule is available on the Fedora wiki. The current schedule calls for a final release in the end of May.


These dates are subject to change, pending any major bugs or issues found during the testing process.

PyCon 2015 (Part II)

I wrote last week about how a few of us from Fedora were at PyCon US in Montreal for the week. It's all over and done with and we're back home now (I got a flu-like bug for the second time this season on the way home...) So, these are just some quick notes on what I did at the sprints!

  • Early on, I ported python-fedora to python3 and afterwards bkabrda picked up the torch and ported fedmsg and the expansive fedmsg_meta module. The one thing standing in the way of full-on python3 fedmsg is the M2Crypto library which will probably not see python3 compatibility anytime soon. Slavek courageously ported half of fedmsg's crypto stack to the python3-compatible cryptography library only to find that it didn't support the other half of the equation. We're keeping those changes in a branch until that gets caught up.

  • The most exciting bit was helping Nolski with his tool that puts fedmsg notifications on the OSX desktop. It totally works. Crazy, right?

  • Later in the week, I helped decause a bit with his new cardsite app. Load it up and let it run for a while. It's yet another neat way to visualize the activity of the Fedora community in realtime.

  • I started a prototype of fedora-hubs which doesn't do much but display little dummy widgets, but it is useful for reflecting on how the architecture ought to work.

  • I wrote some code to get the fedmsg-notify desktop tool to pull its preferences from the FMN service. The changes work, but they required some server-side patches to FMN that are done, but haven't yet been rolled out to production (and we're in freeze for the Beta release anyways..).

    In order to use your FMN preferences, you currently have to set a gsettings value by hand which is unacceptable and gross, but I'm not sure how to present it in the config UI. We can't just go all-in with FMN because there are other distros out there (Debian) which use fedmsg-notify but which don't run their own FMN service. We'll have to think on it and let it sit for a while.

  • Lastly, Bodhi2 saw some good work. (We fixed some bugs that needed to be hammered out before release and we actually have an RPM and installed it on a cloud node! Staging will be coming next once some el7 compat deps get sorted out.)

  • ncohglan introduced us to the authors of kallithea which led to some conversations about pagure and where we can collaborate.

  • I was really glad to meet sijis for fun-time late-night hackery in the hotel lobby.

That's all I can remember. It was a whirlwind, as always. Happy Hacking!