January 21, 2016

¿Eres una chica Fedora? ¡Entonces anotate!

No es un secreto que la presencia femenina siempre ha estado ahí, pero la mayoría de las veces no lo sabemos debido a la falta de información. Hace varios años se inició una Página Wiki con la idea de tener un listado de aquellas Mujeres que pueden proveer consejos y ayuda a aquellas nuevas colaboradoras que se inician en nuestra comunidad.

Me encuentro en la lista que Bee(IRC nick : bee2502), quien es parte del Fedora Community Operations Team “Equipo de operaciones comunitarias de Fedora”(#fedora-commops en IRC) ha iniciado una “llamada a acción”, donde esperamos qe todas las féminas que hacen vida en Fedora puedan colocar sus nombres en la wiki para facilitarnos el trabajo de reunirnos y difundir información de interés mutuo. Como Bee dice en su email:


“La diversidad en Fedora es una discusión que ha resurgido en los meses pasados, incluyendo la creación de la posición de Fedora Diversity Adviser (Consejero de Diversidad en Fedora), una posición que actualmente tiene María “tatica” Leandro. Como parte de los objetivos identificados en el Consejo Fedora, una iniciativa para promover Fedora a nuevos colaboradores con diferentes características e historias, ha sido enfatizada para el 2016.

Fedora Women (Mujeres Fedora) es central para los esfuerzos de incrementar la diversidad. Sin embargo, para tener un mejor entendimiento de nuestras fortalezas y debilidades actuales, – trataremos de recopilar información sobre nuestra comunidad, su composición, y sus intereses y prioridades, para poder probar hipótesis, y así poder crear y ejecutar buenas estrategias. Un buen punto de inicio es simplemente agregar tus detalles FAS a la lista de mujeres actuales que colaboran en Fedora dentro de la Página Wiki de Mujeres Fedora – la cual solo tiene ocho mujeres actualmente!”

Así que no esperes ni un solo segundo y por favor, coloca tu nombre en la wiki!

Puedes encontrar más información y discusiones en el ticket, relacionados con la instancia del Equipo de Operaciones de Comunidación:

This post has a nicer formatting that can be seen at it's original source at tatica.org , so feel free to hit the link and read better version!

January 12, 2016

A post-mortem for the Romanian Wiki Loves Monuments 2015

For the foreseeable future I do not intend to return as an organizer for Wiki Loves Monuments, five years of working on the Romanian edition is enough for a person, the time has come for new blood and new enthusiasm. Myself I am burned enough. And, arguably, any community project has to attract new contributors, if not perhaps it lived its life.
Note: I won't be totally out of the picture, if there is a Wiki Loves Monuments in 2016, I will most likely contribute some pictures and if the organizers will feel a need for punctual help or want to borrow some experience, I should be available.

With this melodramatic intro over, is the time go back to the topic: a "post-mortem" is a cold analysis of a project, made after its end, looking at what worked and what didn't. The intention for it is to be as objective as possible, a learning experience for future similar projects.

Ansamblul bisericii evanghelice fortificate din Archita MS-II-a-A-15596Ansamblul bisericii evanghelice fortificate din Archita by Silvia Nichita, released under CC-BY-SA, winner of the Romanian competition.

The good

Having the fifth edition in a row happen and bring results in line with the previous editions is by itself a success. Is not trivial to have people volunteering to make it happen, sponsors to put money, contributors to participate... and having it work year after year.

It was also a success for the team when it managed to secure the funding, first with a sponsorship from Ixia which had put the things in motion and later a grant from the Wikimedia Foundation, which allowed for a lot of activities to take place. It was useful to have the infrastructure already set-up on Wikimedia Commons, Romanian Wikipedia and the website, which is hosted by RLUG/ProLinux, as it was useful to have Asociaţia ARCHÉ handling the money, as a legal entity (traditionally, the project is run by an informal group of people and needs such legal coverage).

~6000 images uploaded in one month (~5600 at Commons and ~400 at Romanian Wikipedia) is a success. Compared with previous years, is not the best, nor the worst, but in the international context, we are in the top third of the 33 participating countries.

At the first sight, 127 participants is kind of low compared with previous years (only 2013 was lower) and definitely under the 200 mark we hoped for. But that mark was optimistic, there are not many Romanian Free Software/Free Culture projects with so many contributors.

For the Wiki Weekend expedition we had a few empty places on the bus, but in the end there are 600 images (504 at Commons and 86 more at Romanian Wikipedia) within the expedition category, which is 10% of the total images.

Wiki Loves Monuments 2015 exhibition in Bucharest 52Photo exhibition in Bucharest

It was for the first time we held an Edit-a-thon, so we lack terms for comparison, but any way you take it, especially for a first, is a success to have 10 participants, 702 images (628 at Commons and 74 more at Romanian Wikipedia) and 11 Wikipedia articles.

Also a first time was the new article writing contest, where 6 people added a total of 343 Wikipedia articles, most of which are stubs, but they are at least an inviting start. Lacking a reference point, I don't know how to call this other than a success.

The photo exhibition with winning images was open at F64 Cafe in Bucharest for about 3 weeks. The exhibition was quite small and its opening was pretty much an intimate event, so the impact was not impressive, but there is a chance for the situation to improve, if we stick to the plan and the exhibition will move to several other (and more visible places) in the coming months.

Also, a positive is the top 10 of winning images, this is good stuff. Not only by my subjective opinion, but also the fact that one of ours makes on the international winners list.

I left this for the last, since the social media impact is kind of a mixed bag: we ran a "photo of the day" thing for the entire duration of the contest (the month of September), which on facebook it was really weak, with a top of 22 likes for an image but on Google Plus it was much better (tenfold or better). Here I assume total responsibility for selecting and sharing the images and not spamming at all.

Wiki Weekend 2015 la Conacul MarghilomanWiki Weekend expedition

The bad

From the things we did badly, the most important I consider is being late to everything. We were late to apply for the Wikimedia Foundation grant, which in turn was approved even more late. Not having the funds secured, we missed to opportunity to promote the contest in advance and may be an important cause for the somewhat weaker participation. We were late in planning and announcing the expedition, and this can explain the weak participation. We were late announcing the winners and were late awarding the prizes and opening the exhibition, thus breaking a few promises. In front of the community I can't say more than I am sorry, we did poorly with this, please don't judge us too badly for it.

We also had a problem with the jury: one of its members simply became silent exactly when he was needed to do his part of the work. So at the time when we were supposed to count the notes, sort the results and publish them, we were in fact searching for replacements for that jury member. That was a human resources error and a lesson: do not rely on people who don't care about your project.

Another failure was the attempt to collaborate with a traditional photography festival. There was no synergy and my estimate is that not even 1% of our final images came as a result of it. Personally I can't tell what went wrong here, as I was not involved at all with it, I could only speculate some obvious reasons, but prefer not to do that. Much like anyone else, I also wait for a more pertinent analysis.

We had no media partners, not for the contest, not for the exhibition, not for anything. This is related to the first bad point above, being late. We didn't know in advance what we will really do, so it was not possible to forge any media partnership nor to announce our intentions in advance.

There is also a problem with the source of the incoming images: the bulk of them came from very few people. 75% of the images were uploaded by the top 12 participants, or close to 60% by the top 5, or close to 23% by an one single person. This isn't healthy at all. Consider that the top contributor by number of images, who also was a big contributor last year, due to personal issues most likely won't be available next year, it starts to look grim. If it want to continue growing, the contest must find some new audience and new participants.

Biserica Calvaria de la Cluj-Mănăștur, vedere sud-vestică, 2014Biserica Calvaria de la Cluj-Mănăștur, vedere sud-vestică by Pan Ioan, released under CC-BY-SA, 2nd place in the national contest, 13rd place in the international contest

The ugly

The thing is, in any human activity there will be parts that go well (the good) and parts that go not so well (the bad), but there are also parts which are frustrating and no matter how hard you work, they will happen anyway. In my Wiki Loves Monuments 2015 experience, those all were related to the community.

Now I am not a newbie to the Free Software/Free Culture communities and know well what to expect: they do mirror closely any human community, so is to be expected to encounter politics, power plays, egos, hidden agendas, individuals with total lack of social skills and such. I do have the guts to deal with them, Hell! if needed I can be a versed troll too! I'm not crying here, just listing some ugly things people can expect.

Traditionally we targeted the Romanian Wiki Loves Monuments to people outside the existing Wikipedia community, since a major goal for the project was attracting new contributors. However, this edition we tried additional things, like the article contest, which was addressed to existing contributors and even to existing heavy contributors. It went with flames, accusation of cheating and strong language. Not nice at all!

Our organizing team as a whole was blamed for not having many Wikipedia contributions. Yes, it is true that myself, I contribute occasionally and my contributions are more likely to be to Commons than Romanian Wikipedia (as an user, I prefer to read the English Wikipedia anyway) and yes, is true two of my colleagues signed-up only a year before, when they joined the 2014 organizing team and their contributions were related strictly to the contest, but you know what else is true? For five years, every single year we ran calls for help and in all those years there was one single existing contributor even who really replied and joined the team (unfortunately, for logistic reasons his contributions were limited, he lives abroad, does not use social media and such). So I had no problem replying "pleas join the team and make this happen!"

But don't imagine this is limited to the local community! One example is when I had the idea that nominating some of the pictures as quality images can be in itself some kind of reward for their contributors. I did not run the nominations myself, so I was not the one to be the most frustrated, but I observed the process. Most of the pictures are rejected with negative feedback from a number of people, who sit themselves on large numbers (sometime thousands) of average pictures labeled as "quality" (while winners of national or even international competitions are not good enough).

And don't get me started on those clueless people who start talking trash on your grant request without reading it entirely or understanding the issue...

RO IL Crama Hagianoff 10
Almost random monument image from the contest


I guess any such writing needs a conclusion, so I'll try to come with one: running such a project can be fun, it can be even rewarding on a personal level, but for a finite while. Fresh air and a fresh perspective are needed.

January 11, 2016

Scribus 1.5.1svn available on COPR repository
Scribus 1.5.1svn running on Fedora 23

After several trials rebuilding Scribus 1.5.1 using Tom "Spot" Callaway's spec file, the effort and patience finally paid off. The rpm version successfully compiled (I had to disable the devel package due to some odd built issue I have yet to find out) and is now available for Fedora 22, 23 and Rawhide under COPR repository.

The reason for usinig the latest development version is mainly due to features not found on stable release which no longer cuts it:
  • Cleaner user interface
  • Better table implementation
  • Orphan and widow control for better typography
  • Ability to open/import other desktop publisher application like Adobe InDesgin, Quark Express and Microsoft Publisher
  • Better import of Adobe Illustrator files
  • ...and more
An interesting feature is the chat system allowing to directly contact the community which is very helpful and should be standard to the majority of application.

Download it, play with it, use it and report the issue to developers to make Scribus a better Desktop Publisher.

Plan for 24 Fedora Design Suite
  • Darktable is no longer available for 32-bits x86 devices since version 2.0.
  • Calligra Krita will be available as default alongside MyPaint to match the Lab section website.
  • Majority of features come from Fedora Workstation taking advantage of Gnome Shell technology.
  • More tutorials. Users are welcome to add them.
  • On technical side, the spec file uses design-suite group list for better synchronization (user can install the suite package with the command dnf install @design-suite).

December 01, 2015

Trying Talky.io
Talky.io have updated their website featuring their WebRTC chat. One of intriguing feature is the support up to 15 people highlighted below.
Revamped Talky.io website featuring WebRTC
It appears their systems is a worthy alterntive of Google HangOut. It will be nice project like Empathy carries more love.

November 23, 2015

On GIMP's 20th anniversary
I want to congratulate the people behind GIMP on the 20th anniversary since the initial announcement of the project, they came a long way. Myself, I switched to it as my primarily image editor long ago, can't point the date precisely but it was around 12 years ago, back in the GIMP 1.x days, when it's UI was... less than optimal, to say the least. Then I went to use it more and more, even write tutorials, give presentations and such (I rarely do such things these days not because of lack of enthusiasm but because of lack of time).
I do use GIMP on a daily basis and I earn my living based on it, but I should acknowledge this is a love-hate type of relation. On one hand, I like the power and degree of control it gives to me: it allows to get to the needed result in a predictable way. On the other hand, there are a couple of shortcomings which annoy me plenty and make me rely more and more on darktable for photography work, those are: slooooooooooow speed and poor noise removal in RAW import (which is done via the UFRaw plugin).

November 04, 2015

Running Fedora 23 Design Suite with ASUS X550ZE
Stable release of Fedora 23  Design Suite is now available with minimal changes like the inclusion of supplemental wallpapers posted from Nuancier. After installation on ASUS X550ZE laptop, no apparent change of the status is in sight. However, some hotkeys (home,end,pgup,pgdn) are functional. The author of asus-nb-wmi allowing to setup these hotkeys mentioned the inability to reach ASUS developers to address these common issues plaguing many ASUS laptops users and the lack of documentation.

Backlight is currently broken due to the controller issues as display on boot so bug is filed:
[    7.684288] [drm:radeon_acpi_init [radeon]] *ERROR* Cannot find a backlight controller

Battery optimization is still an issue due to the driver choosing to use a powerful GPU rather the power saving mode. AMD is currently working on new driver structure.

Dual Radeon is currently unsupported but works are under way.

November 03, 2015

gstreamer-python broke SoundConverter on Fedora 23
Users having installed SoundConverter on Fedora 23 may notice the app will silently fail to run. The issue is caused by gstreamer-python which possibly needs a rebuilt. Running via terminal lead with this message:

SoundConverter needs python-gstreamer 0.10!

Running python on terminal leads to the following result:

$ python
Python 2.7.10 (default, Sep  8 2015, 17:20:17)
[GCC 5.1.1 20150618 (Red Hat 5.1.1-4)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import gst
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/lib64/python2.7/site-packages/gst-0.10/gst/__init__.py", line 193, in <module>
    from _gst import *
ImportError: /usr/lib64/python2.7/site-packages/gst-0.10/gst/_gst.so: undefined symbol: libxml_xmlDocPtrWrap
>>> exit ()

 Current workaround is to downgrade it using Fedora 22 package via dnf

sudo dnf downgrade gstreamer-python --releasever=22

Bug is filed while waiting for a fix.
¡darktable-2.0~rc1 ya está aquí!

Estamos orgullosos de anunciar el primer candidato de la nueva versión de darktable 2.0

Como siempre, por favor no utilice el tarball auto-generado provisto por github, solo utilice nuestro tar.xz y verifique que el checksum sea:

sha256sum darktable-2.0~rc1.tar.xz
412f17131c8674e266c91c933de1aa2b04c2ab7efdc04a60b00faf3abffc0446 darktable-2.0~rc1.tar.xz

Los paquetes para plataformas individuales y distros vendrán breve, y el changelog preliminar puede ser encontrado abajo:

cuando esté actualizando la versión estable de la serie 1.6.x, por favor tenga en cuenta que es ediciones serán preservadas durante este proceso, pero ya no será posible bajar desde la versión 2.0 a la 1.6.x. ¡Tenga cuidado si necesita utilizar darktable para un trabajo en producción!

¡Feliz 2.0~rc1 a todos!

click para agrandar

click para agrandar

click para agrandar

click para agrandar

  • darktable a sido portado a gtk-3.0
  • La nueva caché de miniaturas reemplaza a la caché de mipmap ( muchas mejoras a la velocidad, menos problemas )
  • Modo de impresión agregado
  • Retrabajo del manejo de color en pantalla (pruebas en pantalla, revisión de gama, etc.)
  • Marcas de agua en texto
  • Módulo de reconstrucción de color
  • Módulo de punto blanco y negro puro
  • Nueva característica de mover a la papelera al borrar
  • Nuevas características a las sombras y luces altas
  • Temperatura Kelvin más apropiada, ajuste del afinado de la interpolación del iop balance de blancos
  • La reducción de ruido está ahora en un archivo externo JSON
  • Demosaico de monocromos en raw ( no estamos seguros si se quedará para este Release, como el deflicker, pero esperamos que sí se quede)
  • Relaciones de aspecto ahora pueden ser agregadas a la configuración de cortar y rotar
  • Navegar por la mesa de luz usando las flechas, la barra espaciadora y enter
  • Exportar en PDF — algunos cambios aún faltan por agregarse
  • Ahora el tamaño de la brocha, su dureza y opacidad tienen atajos de teclado
  • El proceso de logueo a Facebook es un poco diferente ahora
  • Ahora se puede sobre-dimensionar el tamaño de la imagen en el proceso de exportado
  • Al hacer clic sobre un elemento anterior del histórico de acciones no descartamos las anteriores ni al dejar el dr o cambiar de imagen
  • Texto, color y tipografías en marcas de agua
  • La información de la imagen ahora soporta altitud GPS
  • Ahora se puede agregar modos al tono y la curva base con control-click
  • Renombrados en las preferencias los mipmaps a miniaturas
  • Nuevo parámetro de “modo” en el panel de exportado
  • El exportador de alta calidad ahora permite disminuir la resolución antes de aplicar la marca de agua y el marco para garantizar un resultado consistente
  • Los scrips lua ahora permite agregar elementos a la interfaz de la vista de mesa de luz ( botones, deslizadores, etc)
  • Se ha iniciado el trabajo en un nuevo repositorio para scripts externos de Lua

This post has a nicer formatting that can be seen at it's original source at tatica.org , so feel free to hit the link and read better version!

October 27, 2015

Progreso de traducción del manual de usuarios de darktable

Por fin! 50% ! hace un mes cuando comencé con esta traducción pensé que no la terminaría a tiempo, sin embargo, ya estando en el 50% si veo luz al final del camino. Esta vez les quise dejar un poco las estadísticas de los avances de traducción del manual de usuarios de darktable en caso de que alguien tenga curiosidad. Para mi asombro, a pesar de que hay días en los que las labores personales (o simplemente la falta de energía) me han hecho desistir, siento que el avance ha sido progresivo y sin pausa.

En fin, para aquellos que quieran seguir leyendo el manual, les dejo el enlace de descarga. Recuerden que es una primera traducción con muchos errores (tanto de sintaxis como de sentido) por lo que si ven cosas extrañas no duden en dejarme sus comentarios.

<canvas class="vc_line-chart-canvas" height="1" width="1"></canvas>

This post has a nicer formatting that can be seen at it's original source at tatica.org , so feel free to hit the link and read better version!
An uncluttered LibreOffice layout
The current default layout

Layout with the main toolbar

Here is how LibreOffice Writer looks after removing the toolbar and only keep the sidebar located on the right. To achieve that result, set View -> Toolbars -> Standard unchecked. The benefit is a more focused and uncluttered layout without distraction and also more touchscreen friendly.
It will be nice that user interface layout will be more responsive depending the size of the screen.

This example is made with LibreOffice Writer running on Fedora 23 Release Candidate 3.

October 22, 2015

Fedora Design Team Update

Fedora Design Team Logo

I’ve been posting these to the design-team mailing list lately but thought it might be good to blog, too.

Meeting Summary

We had a meeting today. In attendance were myself, ryanlerch, gnokii,
mleonova, riecatnor, sam08, mbriza, garrett, and tatica.

Meetbot links:

Here’s a quick run-through of what we discussed:

Presentation to Council

Our presentation to the Fedora council is going to be at 5 PM UTC / 12 pm EST
(post DST) in #fedora-meeting on Monday, November 2. It will be an IRC
meeting and anyone is welcome to come.

The topics I’ll present to the council are covered pretty well in this
summary from last meeting:

The main change in the message I think is that swag distribution /
production varies by geo.

For the FAD we would like to bring up to them, it is looking like July
2016 in Boston would be a good time/location. It is close to Flock the
next month in EMEA, but EMEA in particular is expensive for our current
team makeup.

New Meeting Time

Our new meeting time is going to shift next meeting due to daylight
savings time. Today the meeting was 1200 UTC / 8 AM EDT… next meeting
(Thursday, November 5) will be at 1300 UTC / 8 AM EST. If you have a
daylight savings shift, the time won’t change for you; if you don’t, the
meeting will be one hour later. Here’s a breakdown of the new time for
future meetings:

  • 1300 UTC
  • 5 AM PST (US + Canada/Pacific)
  • 8 AM EST
  • 8:30 AM (Caracas)
  • 3 PM (Europe / Berlin + Rome)
  • 4 PM (Moscow)
  • 6:30 PM (Kolkata)
  • 8 PM (Phnom Penh)
  • 9 PM (Kuala Lumpur)
  • 11 PM (Queensland AU)

New Meeting Chairs

I’m not going to be around from about mid November-December until
February or March, so ryanlerch and gnokii volunteered to chair the
meetings when I’m out.

Completed Tickets

Ticket 373: Production of swag for F22

mleonova completed this one with sticker designs for the 3 Fedora editions.

Ticket 360: Fedora LiveUSB Icons


mleonova completed this one with icon designs for all of the various
Fedora images. There is some great new logo artwork in this ticket worth
checking out!

Ticket 398: AsciiBinder Logo

mleonova completed this one. It’s an excellent logo design worth taking
a look at. :)

Ticket 393: Cover for Getting Started with Fedora Guide

mleonova completed this one. She added a photo of the finished printed
book to the ticket so you can see how it came out.

Open Tickets

Ticket 401: Review: Updated cheat cube to use DNF instead of yum

This one is waiting on an update from Ankur; pinged him in the ticket.

Ticket 347:
Fedora Cloud, Server, and Worksation Stack Exchange community promotion

This one is waiting for feedback from mattdm; pinged him in the ticket.

Ticket 199: Interface and Usability refresh for ask.fedoraproject.org

anuradhaw gave us an update and pointed to her code; puiterwijk put some fixes in (the code was written to a newer version of askbot) and pushed her code to stage and you can see it here:


There are some minor issues that need to be addressed I think before we can push to prod. anuradhaw indicated she’s studying for exams but after her exams will have more time to come back to this project. We will wait for anuradha to finish her exams to try to address the issues.

Ticket 402: Need to scale down hackergotchi in planet rss feed css

This ticket needed an owner so ryanlerch grabbed it. Thanks, Ryan!

Ticket 210: Update fedoracommunity maps with Russia in EMEA

We thought we were finished with this one but it turns out there are
some issues. ryanlerch kindly picked it back up to fix.

Ticket 279: Design for “This week in Fedora”

This ticket needed an updating. We discussed this design at the Flock
design clinic; ryanlerch created a repo on pagure.io and added a mockup
at the event that he committed then; he also has newer work he did
post-Flock that he will upload later. I also have a mock from flock I
never uploaded so I’ll upload that too.

Ticket 367: Need logo design for the Fedora Security Team(FST)

This ticket is so close to being done, the logo just needs a few tiny
tweaks. Pinged Yogi on it.

Ticket 350: Anaconda banner template

Yogi completed the template work; we just need it to be posted to the
wiki. Yogi is going to work on this. (He contacted me after the meeting)

In-Progress / Feedback Tickets

Ticket 403: Icons for FAS 3

riecatnor asked for feedback on her work for this one:

– she designed three updated options for the group icon based on
feedback from before, and the 3rd one was the favorite.

– there’s an icon used in the dark blue bar in the upper left of this
screen; the group icon should hopefully work there as well:

– in context, the users icon stands out a bit in the full screen mockup
because the fedora logo isn’t square. we suggested riecatnor modify the
mockup to add a square border along the outside of the icon to see if
that fixes the issue

Ticket 407: Logo for mojefedora.cz

mleonova asked for feedback on this logo design. the favorites were the
upper left and lower left versions; the designs were well-liked :)

Ticket 404: F23 Release Posters


sam08 created these awesome designs. We don’t know if the reporter used
them, but they are all quite nice. I asked sam08 to post the SVGs and
we’ll close the ticket and advertise them more widely to the Fedora
community to use.

October 21, 2015

Corebird 1.1 Available in Fedora 22

Corebird 1.1 was recently released and it is now available in the official Fedora repos.

Major changes that this new version of corebird includes are:

  • The behavior in corebird on how tweets get hidden and shown is now more consistent.
  • Corebird now provides snippets that you are used to insert common phrases or emoticons. Simply type the keyword for the snippet, and press tab to autocomplete. Settings for adding and configuring snippets is found in the application settings in the “Snippets” tab.
  • Corebird now supports showing Twitter quote tweets in timelines as well as creating quote tweets. This replaces the old “Quote” item for tweets which would simply copy the original tweet’s text.
  • Twitter removed the 140 char limit on Direct Messages, so this limit is also removed in Corebird

Update via the Software application in Fedora, or on the command line with yum or dnf.

October 13, 2015

Fedora 22 and 23 backgrounds updated with extras
F23-backgrounds is recently updated with the newest wallpapers including extra and is now available in stable repository. Simply update via Software application on latest Fedora 23 Workstation or command pkcon update f23-backgrounds-base f23-backgrounds-extras
View the update

In addition f22-backgrounds received a much needed update with the inclusion of previous supplemental wallpapers winnners. Please test them for all version to push them to stable release.

Here is also the directory for distributions looking to package these wallpapers.

October 12, 2015

LIF 2015

For the last couple of years I didn't manage to attend myself the Linux Install Fest traditionally organized by ROSEdu at Politehnica University of Bucharest, which is a shame, since there is a lot of cool stuff going on. But such is life, there are so many things to do and so little time left...

However, I learned a bit from watching the graphs from the official website and the pretty pictures published by the local Ubuntu community.

I couldn't stop myself from playing a bit with the charts data and make my own one. Just don't read too much into it, I don't think it shows personal preferences or such (if you DO have a personal preference, you probably don't need an install fest):

lif 2015

Anyway, I just wanted to say: good work ROSEdu!

October 06, 2015

Gimp100Podcasts 41: Hackergotchis

Un hackergotchi es la imagen que utiliza cada usuario como avatar para que el lector sepa quien es el autor del articulo que está leyendo. Estas imágenes personalizadas son utilizadas en muchos planetas (websites donde se agregan las entradas de diversos blogs) como una forma divertida de mostrar la cara del autor.

Si eres parte de un planeta y no tienes tu hackergotchi, ve este corto tutorial para hacerlo fácilmente en Gimp utilizando curvas bezier icon-big.


This post has a nicer formatting that can be seen at it's original source at tatica.org , so feel free to hit the link and read better version!

October 04, 2015

Manual de Usuarios de darktable: Capítulo 1 y 2

<iframe allowfullscreen="allowfullscreen" frameborder="0" height="650" marginheight="0" marginwidth="0" scrolling="no" src="http://www.slideshare.net/slideshow/embed_code/key/JnaWF4eOJpPpAG" style="border: 1px solid #CCC; border-width: 1px; margin-bottom: 5px; max-width: 100%;" width="550"> </iframe>

Desde hace un par de años ayudo con la traducción oficial de darktable pero mi verdadera meta siempre ha sido traducir el manual de usuarios oficial. Es realmente una tarea inmensa porque estos chicos siempre andan agregando cosas nuevas y fabulosas a la aplicación, por lo que mi tiempo de traducción casi siempre se ve alejado del manual; sin embargo, por fin conseguí nuevamente el tiempo y las ganas para retomar mi trabajo de traducción y necesito de la ayuda de todos.

Los próximos meses estaré publicando capítulo por capítulo del primer borrador del manual de usuarios y necesito revisores! Si están interesados, solo deben leer el pdf que está adjunto a este artículo y dejarme sus comentarios. Es posible que encuentren errores de tipeo o de sintaxis, incluso cosas sin mucho sentido, pero espero todas las correcciones que puedan darme. El recurso original de comparación se encuentra siguiendo este enlace, en caso de que vean sentencias que no tengan mucho sentido y quieran compararlas para una mejor traducción.

De antemano, les agradezco a todos quienes se den el tiempo de leer aunque sea una o dos páginas y proveer comentarios.

Enlace de descarga del PDF: Descargar PDF

This post has a nicer formatting that can be seen at it's original source at tatica.org , so feel free to hit the link and read better version!

October 01, 2015

Crear imágenes para redes sociales

Uno de mis compañeros de trabajo me enlazó a este útil recurso para quienes siempre tienen problemas encontrando el tamaño adecuado para sus imágenes sociales. Este website provee algo que llaman “Social Media Image Maker” (Creador de imágenes sociales) que te permite redimensionar y retocar tus imágenes sociales.

Así que si te preguntas que tan largas o anchas deben ser tus imágenes de perfil o las imágenes de tus posts, deja de preguntarte y lee esto! El proceso es bastante simple, solo carga el arte deseado y la aplicación hará el re-dimensionado por ti. También tiene varios efectos de color que también podrás aplicar en caso de que quieras realizar una edición más completa.

Recuerda las medidas recomendadas para cada imagen:



  • Portada – 851 x 315 px
  • Imagen de perfil – 180 x 180 px
  • Post normal – 403 x 403 px
  • post realzado – 843 x 403 px
  • imagen de aplicación – 111 x 74 px
  • Imagen de perfil de evento – 714 x 264 px

Google Plus

  • Imagen de perfil – 250 x 250 px
  • Imagen de fondo completo – 2120 x 1192 px
  • Imagen de fondo HD – 1920 x 1080 px


  • Imagen de perfil – 300 x 300 px
  • Miniatura de Video 16/9 – 960 x 540 px
  • Miniatura de Video 4/3 – 720 x 540 px


  • Imagen de perfil – 64 x 64 px


  • Imagen de perfil – 420 x 420 px


  • Imagen de perfil – 140 x 185 px
  • Logo – 285 x 70 px


  • Imagen de perfil – 96 x 96 px


  • imagen de fondo – 1680 × 1050 px


  • Imagen de perfil – 240 x 240 px
  • imagen de cabecera – 1252 x 626 px
  • imagen de fondo – 2048 x 1707 px


  • Imagen de perfil – 200 x 200 px
  • imagen de fondo – 1600 x 1000 px


  • Imagen de perfil – 48 x 48 px


  • Imagen de perfil – 48 x 48 px


  • Imagen de perfil – 214 x 214 px


  • Imagen de perfil – 200 x 200 px
  • Logo – 120 x 60 px
  • Logo pequeño – 50 x 50 px
  • Banner – 640 x 220 px


  • Logo – 140 x 185 px
  • Logo 2 – 200 x 167 px


  • Imagen de perfil – 128 x 128 px

This post has a nicer formatting that can be seen at it's original source at tatica.org , so feel free to hit the link and read better version!

September 29, 2015

Blender Workshop at Smallworld

Last weekend it was time for another workshop at Smallworld Cambodia in Phnom Penh. This time a Blender workshop. There was 16 registrations and a lot of the participants showed up. So the lecture room in Smallworld was good filled. Smallworld was full that day anyway as also the WordPress Meetup took place that day. So a lot of Open Source topics that day in Smallworld.

Next thing, meeting for BarCamp, TranslationSprint and Installfest…. Lot to do

September 28, 2015

Update of Asus X550ZE status
I upgraded the Asus X550ZE to Fedora 23 Beta Design Suite. So far, the majority of hardware is functional except the Fn hotkeys and the poor power optimization.

For Fn hotkeys, after looking at all possible solutions, it turned out majority of Asus X series laptops is affected due to the lack of proper documentation of wapf function found within asus-nb-wmi module from the kernel. The ball is on ASUS to make hotkeys functional and provide needed information.

The second case related to poor power optimization is due to radeon driver. In addition, the lack of functional hybrid driver only make the laptop running on R7 265 GPU for performance while the R5 230 is permanently disabled for better power saving. It will be a while before Linux kernel will support hybrid graphics for Dual AMD Radeon.

September 23, 2015

FUDcon en cba24n

Durante el FUDcon tuvimos la oportunidad de realizar una pequeña entrevista cba24n en la que participamos Valentin, Neville y mi persona, explicando un poco sobre que es el FUDcon y porque promovemos las tecnologías libres como comunidad. El video habla por si mismo, así que…

<iframe allowfullscreen="true" class="youtube-player" frameborder="0" height="390" src="http://www.youtube.com/embed/DDEL22jFXYU?version=3&amp;rel=1&amp;fs=1&amp;autohide=2&amp;showsearch=0&amp;showinfo=1&amp;iv_load_policy=1&amp;wmode=transparent" type="text/html" width="640"></iframe>
<iframe allowfullscreen="true" class="youtube-player" frameborder="0" height="390" src="http://www.youtube.com/embed/CfdgWD4R0NQ?version=3&amp;rel=1&amp;fs=1&amp;autohide=2&amp;showsearch=0&amp;showinfo=1&amp;iv_load_policy=1&amp;wmode=transparent" type="text/html" width="640"></iframe>

This post has a nicer formatting that can be seen at it's original source at tatica.org , so feel free to hit the link and read better version!
Fedora 23 Beta Design Suite ready for testing
Fedora Magazine did a good job exposing more Fedora Labs notably Fedora 23 Design Suite Beta. No much update occurred other than the tutorial section currently under work thanks to one of notable contributors Andrew Walton, who also provided one of his excellent pictures available as part of Fedora 23 wallpaper.

Final phase will be tweaking and update the tutorials on the wiki section before passing to the incoming 24 release. Feedback is welcome for users looking to have their favourites applications and fonts included by default as long they abide to Fedora Project policies.

September 22, 2015

Supplemental Wallpaper Winners!

We broke this time nearly all records since we doing the Supplemental Wallpaper Contest with Nuancier. We had 199 submissions, where actually 157 ended up in the pot for the elections. These came from 73 submitters, a lot of them new contributors. Unfortunately we also broke the record for rejected submissions. The most of them contained a trademarked logo, notice that includes our own also! One thing was also more negative, a lot of participants uploaded, not just 3 pictures as many more. Some of them submitted a lot and mostly iterations. That leads to a problem, the Fedora community shows a strong love for “blue”, means if somebody submitting just iterations of a blue pattern, he has a good chance. But it can be that all of his iterations are elected, instead of other better submissions with higher quality.

So, with the next contest, we have to limit to amount of submissions that can be made. Hopefully we can implement also some other features to.

But for now here are the winners:


September 18, 2015

Construyendo una mejor experiencia de FUDcon

FUDcon siempre ha sido la forma de interactuar con otros, conocer a esos colaboradores que han sido tus compañeros de trabajo el último año ( y en muchos casos, por periodos mas largos). Con el paso del tiempo, Fedora ha experimentado una serie de cambios en un corto periodo y ha sido muy difícil mantener el ritmo, especialmente ya que la mayoría de los colaboradores tenemos una vida fuera de la comunidad.

Tenemos personas que nunca han asistido a un FUDcon pero han ido a un Flock, personas que nunca han ido a un Flock pero han ido a varios FADs, y personas que no tienen ni idea de donde comenzar. Los eventos de Fedora deberían funcionar como una forma de preparar a los colaboradores, desde el evento mas pequeño hasta el mas grande, para que puedan aprender a sacar el máximo provecho de sus viajes. Durante el FUDcon Córdoba 2015, tuvimos una larga charla sobre el futuro de las conferencias en Latinoamerica, las cuales necesitan con desesperación una renovación.

FADs: La mejor forma de prepararse para el reto

Aunque los FADs son eventos que se enfocan en un equipo en particular (la mayoría de las veces), deberíamos animar a nuestras comunidades locales a tener FADs mensuales para que no solo los organizadores, sino los asistentes, puedan experimentar lo que es ser parte de un Evento Premier de Fedora. La última vez que hubo un FAD en LATAM fue en el 2013 en Managua, así que, ¿Por qué nos detuvimos?

  • ¿Es un problema de Dinero? : LATAM nunca ha contado con un presupuesto enorme, y estamos tan acostumbrados que de hecho, rara vez pedimos algo. La mitad de las personas de LATAM no saben como recibir un reembolso, y aquellos que so.. bueno, es un trauma recibirlo. Nosotros lidiamos con problemas de retrasos, métodos de pago y en ocasiones, un simple NO es mas fácil porque nadie quiere lidiar con nuestros problemas internos.
  • Largas Distancias: Mientras que Centro America puede ser recorrida (al menos una parte de ella) tomando bus nocturnos, Sur America es una historia completamente diferente. Somos 15 países con un territorio inmenso que cubrir y dudo que algún día obtengamos suficiente patrocinio para mover tanta gente a FADs con la frecuencia con la que lo hacen EMEA y NA. Así que conversamos sobre una nueva forma de mejorar nuestro desempeño en los FADs y hacer más sin requerir de mayores gastos, FADs en Línea.
  • Equipos Fedora: Tenemos miembros de cada equipo Fedora en toda LATAM, pero no en cada país. Un FAD en Línea (en los casos requeridos) podría ayudarnos a reclutar mas personas en cada país con la mitad del esfuerzo del que ya le estamos poniendo.
  • Grabando los FADs: Siempre hemos tenido problemas al momento de tratar de grabar nuestras conferencias y talleres durante el FUDcon, donde la falta de hardware es usualmente el problema principal. En cambio, es muy fácil grabar una charla en línea utilizando software como Hangouts, BlueJeans, BBB y otros. De esa forma, podríamos mejorar nuestra base de datos de videos para que otros colaboradores la tuvieran a disposición.
  • El problema de la frecuencia: Tenemos 6 equipos principales en Fedora. Documentación, Diseño, Embajadores, Infra, L10N y Desarrollo. Considerando que el FUDcon es organizado solo una vez al año, podríamos tener 2 FADs anuales por cada equipo, lo cual crearía un impacto en la calidad de las charlas, el contenido y las metas que podrán ser alcanzadas en el próximo FUDcon.

Uno de los mayores problemas en los FUDcon de LATAM es que tenemos que esperar todo un año para reunirnos y esperamos que la gente asista simplemente por su amor a Fedora, cuando la verdad es que debemos cosechar durante todo el año los planes para que podamos ver los resultados en el FUDcon. Otra de las ideas de tener FADs en Línea es proveer una conferencia que pueda ser vista en cualquier rincón de LATAM, gastando menos tiempo/esfuerzo/dinero, permitiéndonos identificar el potencial de cada país, para que, una vez nos llegue el FUDcon a la puerta, sepamos cuales son nuestras fortalezas y debilidades, y podamos sacar el mayor provecho de la conferencia, pero además de difundir nuestro trabajo a una gran cantidad de personas, los equipos locales ganarán experiencia en la organización de reuniones, eventos pequeños y se conocerán mejor los unos a los otros. En países como Argentina y Brasil donde el territorio es realmente enorme, es normal encontrar colaboradores que jaman se han conocido cara a cara.


Equipo de Eventos: Utilizando la herramienta correcta para el cada trabajo.

¿Por qué le estamos pidiendo a Desarrolladores, Empaquetadores y colaboradores técnicos organizar conferencias si tenemos un equipo de Mercadeo? Esta es la pregunta que siempre ha venido a mi cabeza cada vez que voy a una conferencia. En LATAM, somos 15 países participando en el proyecto Fedora, pero solo tenemos miembros del equipo de Mercadeo en 4 de ellos. Tenemos países donde reclutamos muchos usuarios y los convertimos en colaboradores para hacer crecer a nuestra región, pero si por ejemplo, le pedimos a un empaquetador olvidar sus paquetes por 6 meses para organizar un FUDcon… ¿Estamos haciendo lo correcto?

Es bien sabido que parte de la organización debe ser realizada por el equipo local, pero esto no quiere decir que están preparados para hacerlo. Hay cartas que necesitan ser redactadas, reuniones, presupuestos, agendas y más cosas que deben ser organizadas, y muchos de los colaboradores que quieren asumir el reto no han organizado ni sus propios cumpleaños. Entonces, ¿Por qué estamos poniendo tanta presión sobre nuestros colaboradores si tenemos a nuestra disposición la herramienta correcta para hacer el trabajo? Deberíamos tener un pequeño equipo local para ayudar a liberar un poco la presión de nuestro talento principal. Acá algunas ideas para este equipo.

  • Documentación: A pesar de que hay una enorme guía sobre como organizar un FUDcon (o cualquier conferencia) hay algunas cosas locales que considerar que solo afectan a LATAM, y no están listadas en la guía general. Deberíamos trabajar este año en traducir la documentación actual y expandirla, incluyendo la experiencia de los organizadores anteriores a los cuales ya nos hemos enfrentado. También hay un enorme requerimiento de Visas, cartas, folletos y más que podría ya estar desarrollado y en donde los organizadores solo tengan que llenar la información pertinente al evento actual (o incluido podríamos hacer que el equipo local lo complete y solo entregue el producto final).
  • Presupuesto: Nuestro equipo podría también contar con un “Departamento de Finanzas” que recolecte información sobre precios, proveedores, costos de vuelos, hoteles, transporte y otros gastos; es usual que algunos países tengan que lidiar con distintos cambios monetarios que no aplican a otras regiones, por lo que es algo que debemos tener en consideración. El FUDcon Córdoba fue una excelente experiencia ya que fue el primer FUDcon donde todos los gastos fueron pagados a tiempo (en algunos casos, los organizadores anteriores habían tenido que esperar hasta 3 meses por un reembolso luego del evento.)
  • Aprobación de Charlas y Cronogramas: Una vez los organizadores locales tengan la información sobre la sede del evento (salas, horarios, etc) debería ser bastante fácil para alguien que no sea del equipo local organizar un cronograma que genere el mayor interés posible a los asistentes, de esa forma, el equipo local solo debería de preocuparse por imprimir las agendas y publicarlas. La información de las sedes también debería incluir sus intereses, actividades locales, carreras, horarios de trabajo local y otros para que podamos crear el mejor cronograma para todos.
  • Arte: Pines, afiches, folletos, calcomanias y otros elementos ya son realizados por el equipo Latinoamericano de diseño, sin embargo, una vez los organizadores realizan el requerimiento, también se necesitan pruebas de impresión, revisiones de escala y más. Al tener la información de los proveedores locales, el equipo de Diseño puede hacerse cargo personalmente de estas tareas por teléfono o correo y asegurarse de que  las impresiones salgan como debe ser, luego el equipo de Presupuesto o Contabilidad puede asegurar el pago a distancia (de ser posible) y los organizadores locales solo deberán de preocuparse por ir y retirar los elementos ordenados.Debe ser un trabajo en equipo y seguramente podemos hacerlo mejor.

Un mejor FUDcon: Reinventando la Rueda (o no)

FUDcon LATAM necesita adaptarse siempre al organizador local, lo cual significa cambio de horarios, distintas charlas, y otros temas que no son siempre iguales en cada país, sin embargo, con el equipo de eventos podemos asegurarnos de hacer un mejor trabajo. Acá algunas ideas:

  • Usuarios y Desarrolladores… AMBOS:  Cuando hablamos del FUDcon, usualmente nos olvidamos de la U y apuntamos a tener una conferencia mas técnica, lo cual no es malo… pero necesitamos incluirlos a todos. En nuestra reunión final en el FUDcon Córdoba hubo varias ideas para resolver este tema:

Las mitades: Considerando nuestra división interna por equipos, si dividimos nuestros 3 días de FUDcon en mitades, podríamos proporcionarle unas 4 horas a cada equipo de forma individual, para que aquellas personas que estén interesadas o involucradas en diversos equipo, puedan asistir a todas las charlas que les interesen sin perder ningún detalle. Para aquellos que no estén interesados en el tema actual, se puede proveer una sala general donde puedan reunirse y discutir otros temas sin interferir en el resto de la planificación.

Salas para equipos: Si la idea es tener un FUDcon donde todos trabajen 24/7, se podría organizar (si la ubicación lo permite) un salón para cada equipo, con su propia agenda. De esta forma, no habrá tiempo libre para nadie, pero nos podríamos asegurar de que el FUDcon sea utilizado por todos sin desperdiciar ni un solo mínimo. Es duro, pero posible.

El FUDcon amigable con el Usuario: Todos hemos sido usuarios, y algunos de nuestros colaboradores más brillantes nacieron en un FUDcon. Aunque organicemos un FUDcon 2/3 técnico, lleno de charlas y talleres que esperen obtener un resultado, podríamos designar fácilmente un miembro de cada equipo y designar una pequeña sala donde los usuarios puedan entrar y escuchar “6 charlas demostrativas” sobre como colaborar y unirse a Fedora.

En vez de mostrarles una presentación llena de cosas aburridas, podríamos organizar charlas de 1h a forma de talleres donde los asistentes puedan realizar una tarea, unirse a un equipo y ser parte de Fedora; de esta forma, podríamos detectar fácilmente a aquellos que en realidad quieren colaborar a los otros que solo quieren saciar su curiosidad. ¿Como podemos convertir esto en una realidad? Mostrando como hacer las cosas en vez de leerles una presentación aburrida.

El panel de Gurus: ¿Cuantos de nosotros hemos tenido una simple pregunta que no ha sido contestada en una de las charlas del FUDcon? Si un miembro (o varios) de cada equipo, dedica 15 minutos de su tiempo a la mesa de Gurus, para responder preguntas en menos de 1 minuto… solo imaginen las posibilidades…

El espacio de “hacedores” de Fedora: Una de las ideas que mas me gustó vino como sugerencia del equipo Brasilero. Ellos tienen algo llamado “Espacio de Hacedores” donde profesionales muestran lo que hacen y como les es útil a otros. Muchos de nosotros trabajamos con Software Libre a diario y sería muy interesante tener unas pocas charlas rápidas que le demuestren a los asistentes que puedes hacer una carrera en este mundo y aún así, tener tiempo para colaborar con Fedora.

Si leíste hasta aquí déjame decirte GRACIAS por tomarte el tiempo de leer este post enorme y aburrido que probablemente tenga mucha información que ya conocías.

Como comunidad, hemos vivido tiempos difíciles siendo parte de un ecosistema tan complicado que incluye tantos países y a veces perdemos empuje, es difícil, pero aún estamos aquí, solo esperamos que no pierdan el internes ni la fe en nosotros, porque aún somos Fedora.

Si te interesó alguno de los temas de este artículo, se libre de dejar un comentario, hacerme un ping en IRC (como tatica) o simplemente enviarme un email (taticaATfedoraprojectDOTcom) si quieres discutir algo de forma más privada. La idea es crear un debate saludable que nos ayude a identificar nuestras debilidades y nos permita convertirlas en fortalezas para continuar creciendo como comunidad.

NOTA: Los cronogramas para los FADs vendrán mas adelante, sean pacientes :)


This post has a nicer formatting that can be seen at it's original source at tatica.org , so feel free to hit the link and read better version!

September 15, 2015

Fedora Atomic Logo Idea

The Fedora Cloud Working Group recently decided that in Fedora 24 (or perhaps a bit further out depending on how the tooling/process can support it) that the Atomic version of Fedora is going to be the primary focus of the working group. (Background discussion on their list is available too.)

This has an affect on the Fedora website as the Fedora Cloud edition shifts from a buffet of kind of equally-positioned cloud- and container-related images to a more focused set of images optimized for container hosting (using Atomic) and a set of more clearly ancillary images that are also useful for cloud/container deployment of Fedora that aren’t based on the Atomic platform. We need to position these images accordingly on the website to meet the new model.

Matthew Miller and I discussed how the Cloud WG decision might effect the website and ideas for how we could update the website to suit for Fedora 24. One idea for how we could do this:

  • Consider replacing the “Cloud” edition slot on the front of getfedora.org with a Fedora “Atomic” edition brand.
  • Convert getfedora.org/cloud to focus instead solely on Atomic (maybe redoing the URL to getfedora.org/atomic).
  • Build out a separate cloud image resource site (similar to arm.fedoraproject.org, which is focused on all ARM-related builds across Fedora) with the full set of Cloud Base images (and maybe Fedora Docker containers too?) Then, pull these in to the edition site via a link in the “Other Downloads” section.

Anyhow, this is just an idea. The Atomic brand is already a pretty strong one, so I think trying to force something like “Fedora Atomic” under the current cloud logomark might miss the opportunity for Fedora to work with the brand recognition Atomic already has upstream. The question is – is that even possible? Luckily, I think the answer might be yes :)

The current Fedora Cloud logo.

The current Fedora Cloud logo.

The Atomic upstream logo.

The Atomic upstream logo.

I poked around a little bit with the Atomic logo (I believe tigert created the original awesome logo!), thickened it up and rounded out the lines a little bit so I could use it as a mask on the purple Fedora triangle texture in the same way the original cloud mark is used in the current cloud logo. I think it looks pretty cool; here it is in the context of the other Fedora Edition logos:

Fedora Atomic logo idea

I was kind of worried they wouldn’t hang together as a set, especially since the three logomarks here had been so close (Cloud’s mark was a 90 degrees rotated Server mark, and Workstation is Server with the top two bars merged to make a display,) but in practice it looks like this is really not a concern.

On the to-do list next are mockups for how a potential new cloud.fpo site might look as well as an updated getfedora.org/cloud (or getfedora.org/atomic as the case might be.) I started poking at mocking up a cloud.fpo site for the base cloud images and other cloud goodies but will probably need to iterate that on the Cloud WG list to get it right.

Ideas? Feedback? Comments are open of course :)

Fedora Developer Website Design

Fedora Developer Logo

For the past few weeks I have been working on mockups and the HTML/CSS for a new Fedora website, the Fedora Developer portal (likely to eventually live at developers.fedoraproject.org.) The goal of the site is to provide resources and information to developers building things on Fedora (not primarily developers contributing to Fedora itself.)

A bunch of folks have been contributing content to the site, and Adam Šamalík and Petr Hracek set up the initial first-cut prototype of the site, configuring jekyll to generate the site and building out the basic framework of the site. The prototype was shared with the Fedora Environment and Stacks Working Group mailing list, and after some feedback and iteration on the initial prototype, Petr asked me to take a look at the overall UX / design of the site. So that’s how I came to be involved here. :)

Competitive Analysis and Sitemap

First, to better understand the space this site is in, I took a look at various developer sites for all sorts of OS platforms and took in the sorts of information they provided and how they organized it. I looked at:

  • Red Hat Developers – main nav is streamlined – solutions, products, downloads. Also has community, events, blogs. Large banner for features. Has a membership / join process. Front page directory of technologies under the solutions nav item.
  • Microsoft Windows Dev Center – main nav is a bit cluttered; core features seem to be developer docs, downloadable tools, code samples, community. Has a “get started” beginners’ guide. Features blog posts, videos, feature highlights. Has a log in.
  • Android Developers – main nav is “design | develope | distribute.” Features SDK, code sample library, and videos. Has case studies. Also has blog and support links.
  • Apple Developer – main nav is “platforms | Resources | Programs | Support | Member Center.” Has a membership program of some sort with log in. Front page is not so useful – solely promo banners for random things; full footer that extrapolates more on what’s under each of the main nav items. Resources page has a nice directory with categorized breakdown of all the resources on the site (seems like it’d make a better front page, honestly.) Includes forums, docs, and videos.
  • Ubuntu Developer – cluttered main nav, nav items contain Ubuntu-specific jargon – e.g. not sure what ‘scopes’ or ‘core’ actually are or why I’d care, has a community, has a log in. Has blog and latest events highlights but they are identical. Similar to Apple, actually useful information is pushed down to the full header at the very bottom of the page – including SDK, tutorials, get started guide, how to publish apps, community.

One thing that was common to all of these sites was the developer.*.com URL. (developer.windows.com does redirect to the dev.windows.com URL.) I think because of this, developer.fedoraproject.org seems like it would match the broader platform developer URL pattern out there.

Another thing they seemed to all have in common were directories of technologies – frameworks, platforms, langauges, tools, etc. – affiliated with their own platform. Many focused on deployment too – mostly to app stores, but deployment nonetheless.

Looking at the main structure of the site in the initial prototype, I felt it honestly was a pretty good organizational structure given the other developer sites out there. I wanted to tweak some of the wording of the headers (to make them action-oriented,) and had some suggestions as to additional content pieces that could be developed, but for the most part the prototype had a solid structure. I drew up a sitemap in Inkscape to help visualize it:

Suggested sitemap for developer.fedoraproject.org. Click on image above to view SVG source in git.

Suggested sitemap for developer.fedoraproject.org. Click on image above to view SVG source in git.


With confidence in the site information architecture / basic structure of the content, I then started mocking up what it could look like. Some things I considered while drawing this out:

  • The visual challenge here is to give the site its own feel, but also make sure it feels like a part of the Fedora ‘family,’ and has a visual design that really feels related to the other new Fedora sites we have like getfedora.org, spins.fedoraproject.org, and arm.fedoraproject.org.
  • There should probably be a rotating banner feature area where features and events could be called out on the front page and maybe even on subpages. I don’t like the page full of promos that is the Apple Developer front page – it comes off as a bit disorganized IMHO – so rotating banners seemed preferable to avoid banners taking over the whole front page.
  • The main content of the website is mostly a series of simple reference guides about the platforms, frameworks, and languages in Fedora, which I understand will be kept updated and added to regularly. I think reference material can appear as rather static and perhaps stale, but I think the site should definitely come across as being updated and “living,” so featuring regularly updated content like blog posts could help with that.

So here’s what I came up with, taking some article content from developerblog.redhat.com to fill in the blog post areas –

Mockup for the front page of developer.fedoraproject.org. Click on image to view mockup source and other mockups in git.

Mockup for the front page of developer.fedoraproject.org. Click on image to view mockup source and other mockups in git.

A few notes about the design here:

  • To keep this looking like it’s part of the Fedora family, I employed a number of elements. I stuck with a white background horizontal branding/nav bar along the top and a fat horizontal banner below that. It also has the common Fedora websites footer (which may need some additions / edits;) and a mostly white, blue, and gray color palette. The base font is OpenSans, as it is for the other sites we’ve released in the past year. The site still has its own feel though; there are some little tweaks here and there to do this. For example, I ended up modifying the front page design such that the top banner runs all the way to the very top margin, and recedes only on sub pages to show the white horizontal background on the top header.
  • There is, as planned, a rotating banner feature area. The example in the mockups features DevAssistant, and the team already has other feature banners planned.
  • Blog content in the form of two featured posts as well as a recent blog headlines listing hopefully will inject a more active / current sense to the overall site.
  • I made mockups for each of the major sections of the site and picked out some CC-BY licensed photography roughly related to each corresponding section in its title banner up top.


Petr had also asked if I’d be able to provide the CSS, images, and icons for the site once the mockups were done. So I decided why not? The framework he and Adam used to set up the site was a static framework I was not familiar with – Ruby-based Jekyll, also used by GitHub Pages – and I thought it might be fun to learn more about it.


If you check out the tree for the website implementation, you’ll see a bunch of basic HTML files as well as markdown (*.md) files (the latter mostly in the content repo, which gets set up as a subdirectory under the website tree when you check the project out.) Jekyll lets you break down pages of the site into reusable chunks (e.g., header, footer, etc.), and it also lets you design different layouts that you can link to different pieces of content.

Whether any given page / chunk of content you’re working on is a *.md file or a *.html file, Jekyll has this thing at the top of each file called ‘front matter’ where you can configure the page (e.g., set which layout gets applied to it,) or even define variables. This is where I set the longer titles for each page/section as well as placed the descriptions for the sections that get placed in the title banner area.

Bizarre Jekyll Issue

Insert random interlude here :)

So I ran into a crazy, probably obscure issue with Jekyll during this process – due to my being a newbie and misunderstanding how it worked, yes, but Jekyll did happily build and spew out the site without complaint or pointing out the issue, so perhaps this little warning might help someone else. (Red Hatters Alex Wood and Jason Rist were really helpful in trying to help me debug this crazy issue. The intarwebs just totally failed on this one.)

I was trying to use page variables when trying to implement the title banners at the top of every page – I needed to know which page I was on in order to display the correct page title and description at the top. The variables were just spitting out blank nothingness in the built page. It turns out the issue was that I was using *.md files that had the same name as *.html files, and some variables were set in one file and some another file, and Jekyll seemed to want to just blank them all out when it encountered more than one file with the same base file name. I was able to fix the problem by merging the files into one file (I stuck with HTML and deleted the *.mds.)

Here it is

So the implemented site design is in place in the repo now, and I’ve handed the work back off the team to tweak, hook up functionality to, and to finish up content development. There is a development build of the website at developer-phracek.rhcloud.com, but I’m pretty sure that’s behind from the work I finished last week since I see a lot of issues I know I fixed in the code. It’s something to poke around though and use to get a feel for the site.

Want to Help?

we need your help!

If you poked around the development version of the site, you might have noticed there’s quite a bit more content needed. This is something you can help with!

The team has put together a contribution guide, and the core site content is basically formatted in Markdown syntax (Here’s a neat markdown tutorial.) More information about how to contribute is on the front page of the content repo in GitHub.

Thoughts? Ideas? Need help contributing? Hit me up in the comments :)

FUDCon Córdoba 2015

El FUDCon Córdoba fue uno de esos eventos que nos recuerda porqué hacemos lo que hacemos. Un evento lleno de camaradería, que en medio de su intimidad, nos permitió compartir ideas, proyectos y experiencias.

Lleno de buenas vibras y energías, de gente increíble que con sus conferencias demuestra ser expertos en lo que hacen, con miles de abrazos que nos muestran la calidad de las personas que forman parte de la comunidad… en fin, un evento de esos que no quieres que se terminen.

<iframe allowfullscreen="true" class="youtube-player" frameborder="0" height="390" src="http://www.youtube.com/embed/rPYX8o-m19s?version=3&amp;rel=1&amp;fs=1&amp;autohide=2&amp;showsearch=0&amp;showinfo=1&amp;iv_load_policy=1&amp;wmode=transparent" type="text/html" width="640"></iframe>

El evento tuvo casi 20 conferencias y 8 talleres, en los que los asistentes tuvieron la oportunidad de conocer más sobre Fedora, lo que hacemos y lo que nos gusta. Abarcamos temas desde Empaquetado, desarrollo, sysadmin, diseño, documentación, traducción y más.

Espero que este pequeño video les muestre lo “re-linda” que es ser parte de la familia Fedora y les anime a unirse. Gracias en especial a los organizadores, Matias Maceira, Valentin Basel y Laura Fontanesi, por dedicar tanto de su tiempo personal a reunirnos y permitirnos ser parte de su día a día durante el evento.

Se vienen más artículos, los que contienen las fotos, sobre mi participación en el evento, y el mas importante sobre las metas y retos que nos hemos propuesto para levantar LATAM y darle un giro de 360 grados que de seguro, nos hará crecer aún mas como comunidad.

This post has a nicer formatting that can be seen at it's original source at tatica.org , so feel free to hit the link and read better version!

September 13, 2015

Inkscape workshop for Linux statt Windows

Internet is this nice technology, who makes it possible to give a workshop even without being at a place. So yesterday I gave a workshop from Cambodia in Germany. But I had interesting expiriences with in Mumble did not work well, even its lighter and has good latency handling but Google hangout did work, I think Google has some priority in the network here, what is strange. But all participants from https://linux-statt-windows.org had fun in the workshop and learned something on the end.

So next weekend next event this time Software Freedom Day where I will give an talk, here in Phnom Penh.

September 07, 2015

Inkscape Workshop at Smallworld

Last weekend, I had the first Inkscape workshop at smallworld. It was very sucessful, we had 13 participants. Thats the maximum, the small room in smallworld can handle for an workshop. All the participants had a lot of fun and achieved the goal. Some of them was really talented. But the want more Inkscape workshops, well this time I have the time to do it :D

September 05, 2015

Fedora 23 Will Have Beautiful Supplemental Wallpaper

The submission phase for the supplemental wallpaper for Fedora 23 isnt over yet. There are so far 169 submissions. But I had to reject this time already 40 because they used material of other pictures without quotation or an trademark was included. So we have 120 submissions in the pot right now.That are right now my favorites:

But there is still one week you can submit your wallpaper, so grab your camera and shoot some nice pictures ;)

September 03, 2015

How I organize my photos

Not long ago, there was a talk about how people deal with their photos: organize, edit, archive and such, and I gave then a partial answer. Why partial? Because I follow two slightly different processes, one when the photos are made for fun and the other when they are for work. Since that answer was partial and made behind a walled garden, I feel the need to expand it in a public piece. I don't pretend what I do is perfect, actually I recognize some flaws myself, but I got there after years of improvements and is not final.

As a sidenote, I do use a Linux desktop, MATE under Fedora, and almost exclusively Free Software, GIMP, darktable, ImageMagick, UFRaw, G'MIC, but what I do is pretty generic, can be done with various other tools. I may follow with another piece on using these tools.

Fun is fun

organize photos

When I talk about pictures made for fun, I mean they are not made for a paying customer, period. This can include anything from photos made for exhibitions, snapshots with the daughter, pictures for my blog, for Wikipedia and whatnot. Usually I take them with an older APS-C DSLR, a Canon 600D, but sometime I bring the FF DSLR. For the most part, I try to protect the better camera, but sometime I am lazy and grab whatever is closer or greedy and want prettier pictures.

The first thing to be noted is that for fun pictures, in the large majority of cases I shoot in JPEG. ...yes, I hear the outrage for such a blasphemy, but the truth is, JPEG is good enough for most of those pics, RAW would be a waste of space and time. When I feel the shoot is important or the light is really difficult, I do use RAW, even for fun pictures.

As a matter of discipline and to keep myself in shape, I try to take pictures as often as possible, ideally every day, and as soon as possible I download the pictures in my computer and then erase the memory cards. The camera has to be ready at any moment to take as much pictures as possible.

I do not use any fancy software to organize the pictures, just the file manager and a directory structure. Of course, it helps that the file manager, with the right plugin, can display thumbnails even for RAWs. The photos made in a day go into a folder with a name like YYYY-MM-DD, for example yesterday pics are in the folder 2015-09-02. Sometime, when I want to find the folder easier, I add a keyword, as there I have a 2015-08-14-seaside

organize photos

As soon as the pictures are downloaded, I try to process them - the next day probably others will come and the newest are always the most exciting. So, I enter the folder and delete some pictures: those which are failed or boring. I still don't delete enough (or still take too many), but I'm getting there, improving continuously (space is cheap, some will say). From the too many undeleted pictures left, I copy a few in a working folder, to be edited and then published. Every year I have a new working folder, and when there are more pictures from a certain event (say, more than 10), they go in a subfolder.

Almost exclusively I edit my 'for fun' pictures with GIMP, this is the editing software I feel the most comfortable with and the one that gives me the most control. There are not many pictures, so I can take my time with them. If there are RAWs, GIMP will call UFRaw for the import, and in the rare cases it is needed, G'MIC will provide some advanced filters. For batch operations like mass-resize or mass-watermarking, there is ImageMagick.

Speaking of watermarks, I almost never do it, but there are are a few exceptions, like the pictures which I suspect have the potential to be 'stolen' by newspapers (it happened a few times, even with watermarked pictures). I firmly believe a watermark will destroy the image, so I try to avoid that.

Again, because next day may come with another pictures, I try to publish my photos as soon as possible. Still, I don't want to spam my viewers, so sometimes there is a delay. For the photography blog, I don't post more than 4 items a day, and for photography sites (the likes of 500px) I post only once in a while. Social media is something I still have to work on: I lost a lot of readers (or at least interactions with readers) a couple of years ago, I blame the loss on posting too much and try to work on it. Publishing go hand in hand with license, so almost everything shoot for fun is published under a CC-BY-SA license: free to use, free to modify, free to almost anything.

Of course, there is archiving. From time to time (not on a schedule, mostly when I run out of space) I move the unedited pictures, with their directory structure, from the computer's hard drive to two external drives, in a manual process. The edited pictures stay on the computer for the entire year, maybe even next year. They have copies online and at least the copy on G+ is high quality (do you know Facebook destroys your pictures with aggressive compression and metadata removal?)


As I said before, I recognize some flaws. The most important couple of them:

  • I do not have continuous backup, there is one only when pictures are moved to the external drives. What is currently on the computer is at danger of data loss. Still, they are 'for fun' pictures and I am lazy, so the loss won't be huge, only at most a few weeks of 'for fun' pictures;
  • When I am away for a while, in a trip or vacation, I can't properly process the photos, so when returning home a lot of work will pile-up. For a while I will have to process both old and new images.

Work is serious

organize photos

For work, you have to deliver the best result from a technical point of view, so when there is a paying customer I use my full frame DSLR, which happens to be a Canon 6D, a camera recognized for its good low-light performance. As for shooting, the pictures are taken as RAW and JPEG. JPEG is there as a backup, while the RAW is the one to be edited. Here I need 1) to get the most possible from the pictures and 2) deal with low-light situations which happens a lot when doing event photography.

Again, as soon as I get home, I download the pictures from the memory cards. But this time I do not delete the cards, I put them in a closet, to have a backup somewhere until the processing is done. Processing the photos for an event may take up to a few weeks.

I have a different directory hierarchy for the work photos, so I copy there all the files, in a directory named after the specific client or work. If the work was an event, the first thing is to make a quick and small selection (10-20 pictures) which I edit fast and deliver the same day, as a preview. The idea is for the client to have something really fast, and if he wants to post pictures on social media while it's hot, he can post pictures from me, not some crappy phone-made images.

Then I parse the files with the file manager and its native image viewer, deleting only very few, and make a selection with images to be edited and delivered. From this selection I copy all the RAWs in a different, working folder.

organize photos

Considering the large amount of images (for a wedding it can be around 1000 pictures), editing with GIMP would be a poor option, so I use darktable instead. After a few days or weeks, depending of the size of the work, images are exported with darktable at a resolution good for large prints. Then for some images that I think need more advanced editing, I open and process them further with GIMP.

After that, I deliver to the client the images, in two sets: one at big, printable, resolution, and another resized for web use. Of course, there is no watermark in sight, the client paid for the images, they are not to be tainted in any way.

If the job requires it, then I start working on the printed album. Here the work is done with GIMP ...blasphemy I hear again? Why not use Scribus? Simple: the print shop requires sRGB JPEGs, and they do a very nice job with that. When there is to be made an engraving on the album's leather cover, I prepare it with Inkscape and save in a vector format (PDF/EPS).

Only after the printed album was delivered to the client I can consider the job done. Then I move the files (sources, edits, album pages) to the two external drives and erase the memory cards.

Of course, somewhere during this process, when I get the time, a few pictures are added to my online portfolios. I have to advertise myself, right? This time, as the images are made for the client, the license can't be a free one. Sorry for that, I wish clients open to free licenses, I would offer a discount for that.


  • Since there is a lot of time from when the pictures are taken and until I get them in the backup system, for a while the memory cards are the backup. I could probably change that and save them faster;
  • I still have a lot of work to do with promotion.

organize photos

September 02, 2015

The summer is over, the wallpapers are not
I know that after the calendar the sun is over, but looking outside, it looks and feels like the middle of the summer. And the truth is, for the last month I was all the time on the road, so even if the pictures are taken a while ago, only now I got the opportunity to edit them as desktop wallpapers for a blog post. If you like any of them, feel free to use (CC-BY-SA).
sea wallpaper
sea wallpaper
sea wallpaper
sea wallpaper
sea wallpaper
II Ciclo de Talleres sobre Herramientas Libres

Durante mi estadía en Argentina para la celebración del FUDcon, estaré formando parte del II Ciclo de Talleres Sobre Herramientas Libres, conversando un poco sobre la Edición Gráfica Libre. Utilizaremos herramientas como Gimp, Inkscape y Darktable, con la idea de solventar dudas y curiosidades de los asistentes, Quienes me conocen saben que será algo divertido y quienes no… los espero!

Día/Hora: Lunes 7 de Septiembre – 20 a 22hs

Entrada Gratuita

Los talleres tienen como objetivo realizar una introducción y fomentar el uso de herramientas de software libre en diferentes áreas como el diseño gráfico, la edición de audio y la impresión 3D. También, habrá un espacio para la discusión acerca de nuevas prácticas culturales y la propiedad intelectual en tiempos de internet.


Cronograma de actividades:

Lunes 7/9: ” Edición Gráfica Libre” Breve introducción al uso de las herramentas Darktable, Gimp e Inkscape para edición de imágenes y fotografías. A cargo de María “Tatica” Leandro.

Lunes 21/09: “En la cresta de la ola: impresión 3D” Diseño y fabricación de impresoras 3D con software y hardware libres. A cargo de Valentín Basel

Lunes 5/10: Taller: “Audio para todos, Ruido para nadie” Grabación y edición de sonido con el software libre Audacity. A cargo de Marcelo Tuller

Lunes 19/10: Charla-taller “Primavera remix: ¿cambio de paradigma o triunfo del robo? Discusiones sobre la propiedad intelectual en tiempos de Internet” Espacio para pensar los recorridos desde la persecución de piratas, plagiarios, Niks y engordadores de Borges hasta las propuestas para acceder y habitar la cultura. Presentan: Ana Almada, Carolina Goth y Maximiliano Giraldes.

This post has a nicer formatting that can be seen at it's original source at tatica.org , so feel free to hit the link and read better version!

August 16, 2015

Make Fedora 23 Beautiful

I opened earlier this week the submission phase for Fedora 23 Supplemental Wallpaper. But this time I announced it in FedoraMagazine and you can find everything to it there.

August 04, 2015

Some summer wallpapers
It's been a while since my last post here with free (as in CC-BY-SA) "wallpaper-ized" photos and I am not sure anyone missed them, but the hell, it's summer and I have a few appropriate images, let's share them.
sea wallpaper
sea wallpaper
sea wallpaper
sea wallpaper
sea wallpaper

July 25, 2015

Flock is coming

Its just a few weeks to 3rd Flock, where the Fedora birds come together. The schedule is out for a while and as you can see I have two things which I will “present”.

The first one is Design Clinic, where you can come if you need help from the Design Team, Máirín Duffy, Ryan Lerch, Marie Nordin, Meghan Richardson and me will be there to helping you with problems you have. You can come with everything, you need a poster for an event so com, you need a logo so come, you need help with UX design so come, you have any idea where we can improve from the design perspective come and speak with us.

So far we have 3 projects we want already to work on:

  • Ralph Bean asked us a while ago if we can improve the “fedmenu”, some might have noticed it already that are the little buttons down in the corner if you are logged in into a page of Fedoras infrastructure.
  • Pierre-Yves Chibon, drives since a long time an service called “This week in Fedora” and he wants an design to present it better in the web.
  • Matt Miller wants help with an presence for “Two Week Atomic”

So if you have something just come along and grab us for help! You can also write to the design team mailing list, if you are not at Flock and have a thing where we should work on.

The second thing I have is the “Wallpaper Hunt“. As you might know I am responsible for getting the supplemental wallpapers for each Fedora release. Btw. our nice little application for doing that was started on first Flock but looking back to that Flock, I received after it some submissions from Charleston, that was definitely not good and there was so nice motives in Charleston to sad we had not one wallpaper in the next release which was shot during Flock. And there was so nice motives! This Flock I want to change that. With Marie Nordin I located a nice spot where we want to go and try to shoot pictures that can show up in Fedoras next version.

So I know we have talented photographer between us, lets get together going there and try get some nice pictures on this way we can share our knowledge and equipment and I think we will have some fun to. The only chance we have to do it, is Wednesday after the talks, so come to me before I will tell you where we meet.

On Saturday as you can see in the schedule we have some time then get the pictures processed.

July 14, 2015

Event report: FUDCon APAC 2015, Pune

I’m writing a blog post after very long. Somewhere between the last post and this one, I’ve graduated and started working for Mesitis Capital as the Product Designer. On the open source community front, I haven’t programmed much recently, but I have been mentoring a couple of students over this year’s GSoC. Two weeks ago, I was at FUDCon in Pune. Here’s a quick summary.

Day 0 - Arrival Day

For the first evening, it was mostly just people arriving and us meeting up over dinner at Kushal’s place. I really enjoyed meeting Suchakra after long - we had a quick discussion around our AskFedora student Anuradha, since mid-term evaluations were around the corner. I met Harish and Danishka who live in Singapore - they shared with me tips around housing, transport, expenses, hackerspaces - all the things I’ll need when I move later this year.

I had a workshop the next day, so I wanted to sleep “early”, but it got pretty late as usual ;-)

Day 1 - First Workshop Day

FUDCon at MITCOE - picture stolen from Suchakra's blog

The morning was mostly meeting folks who arrived that day - Gnokii, Tuan and the rest. Come afternoon, and it was time for my workshop on building responsive front end. This was my first attempt doing few things - conducting a session without slides, programming stuff on the stage, the topic itself - and I think a lot of those choices were great because I ended up heavily modifying what I had wanted to show. I do regret that I couldn’t get around to teaching the stuff I really wanted to, but given a beginner audience, I’m happy they picked up some key ideas. A couple of them also emailed me after the event asking for further resources, so it does look like it was handy.

In the evening, we had a sort of mini FUDPub - most of us speakers & volunteers staying at the hotel went to a nearby Pub. Gnokii, Somvandda, Yogi, Danishka and I got on a table and we were discussing breweries and food - pretty interesting stuff. It turns out Charul and Sinny were neighbors - so Suchakra and I ended up chatting about work, projects, college life, etc - again sleeping quite late.

Day 2 - Meeting students

I didn’t have any sessions scheduled for the second day, so I took the opportunity to hang out with students. I learned that many students from Amrita University, Kollam were in town, so we headed up for lunch together, discussing projects and scope for them to contribute to some FOSS projects. Later during the day, some students from MITCOE spent quite some time with me; we talked about how the Fedora Project is organized, who does what, and how one gets into areas that interests them. There were two students interesting in contributing to the Design team, so I explained them about various things Design team does, the people involved, tools they use, and encouraged them to attend the workshops from the Design track on the final day.

In the evening, we had the social event at bluO in Phoenix MarketCity, a large shopping complex. There was bowling organized, great food, and a very energetic environment.

Day 3 - Final Day

I had an early joint workshop session on how Git works with Mayur. Once again, catering to the audience, we decided to focus on what it is, and how to fiddle with it. While Mayur took the stage and maintained an overall flow around the session, I went around looking at people’s screens and ensuring everyone was doing the right thing. There were lots of questions popping around Git server centric infrastructure - it was fun answering them. There were also a couple of people who weren’t new to Git but didn’t like merge conflicts, so we sat down and helped them around it.

Harish soon followed with a key signing party. I’m happy I attended it - it was great refresher material and I got some concepts cleared in my head around the whole GPG process. As it always is the case, I learn better by doing, so I’ll try to teach it to somebody and hopefully become more clear that way.

For the night, we had dinner at the hotel - once again, it was fun recommending Indian dishes to my non local friends, and it does look like they enjoyed it.

Overall, amazing time at my first FUDCon. I look forward to it next year! :-)

Picture credits: Suchakra’s blog at http://suchakra.wordpress.com

July 07, 2015


I will do in November a new event about Free Software graphic tools – FOSSOGRAPHY. This event plans to bring developer and user of this software together. Its thought of a kind of showcase about the newest developments in this areas and what can be done with free software. The projects shall win this way new users as even more contributors.
But it shall be also a place where the various programmers of the different projects can meet and connect to work on stuff where the programs should be working together. But also a place where you can come and tell people about an idea you have that might get software in this area improved.

The Call for Papers as well the registration for the event is open now and closes on 30th September. We search for talks, handout sessions, workshops, hackfest from the following areas:

  • Open Source and photographics
  • Free Software tools for image manipulation and raw development
  • 3D graphics and renderer
  • Free Software for vector graphics
  • Font design with Open Source
  • Free Software tools for 2D & 3D animation
  • Video editing and production with Open Source
  • Game development and asset creation with Open Source
  • UX design in/for and with Open Source
  • Desktop publishing and print design with FreeSoftware
  • Open Source 3D printing soft- and hardware
  • Open Source Color Management
  • Aerial photography and video with Open Source
  • DIY (open source) dolly systems
  • File formats for free graphic software

The idea to this evnet, was born a long time ago as another event who looks wants the same doesnt become what it should be.
After the decision was made to do it was open the place where it should be and there was a lot of thinking if it is a good idea to go first time to Asia. Yeah there are some disadvantages, like working style of Asians or the most Europeans/Americans think flying there would be more expensive as travelling inside Europe or the the amount of FOSS contributors isnt that high on this continent. But at a certain point we as free software movement have to go to Asia to get them involved and not always saying, we dont have contributors there!

But there is something else, we have to carry the costs for the event, where is actually a positive thing doing it in Asia as that gets amazingly cheap as well we want to support speakers and projects with there travel costs. We try to collect most of this money from the community, so if you believe in the goal of the event and/or using this tools, you can help us. We made a pledgie for that purpose and an indiegogo campaign will follow. But watch we want to give you something in return!

July 01, 2015

FUDCon APAC 2015 – Summary

I was last week in Pune for FUDCon, so its time to write about the experiences.

Day -2

I had to start my travel 2 days before the event from airport Leipzig flying to Munich, well the travel to Leipzig and also the checkin and flight was without something to mention. Just one hour ride to Leipzig and 40 minutes flight to Munich. I had a long layover in Munich so I checked before the situation with WIFI and electricity, well Munich has free wifi and they even proudly anounced that the equipped the gate areas with power supply, well they was there but simple not working. With a little searching I found one which was working but there was nothing to sit there so I spent the time in EMEA Ambassadors meeting standing :D

Day -1

Also for that day there was no action, boarding the plane in the morning and leaving it in Mumbai in the night. The immigration process with the TVOA visa worked well, except to find the counter for them was difficult. So if you travel to India and eligible to get it, thats the easiest way.
Outside the airport Prima Yogi Loviniltra and a volunteer did already wait for me, just Ryan Lerch was missing but he joined as a few minutes later. So the fetch on the airport was well organized. The cab ride took some time but interesting conversations made that not feelable. So we arrived in the morning in Pune just enough for 3 hours sleep.

Day 0

I had not really time for a good breakfast but I needed one as I had not a dinner either, but Kushal was already standing there telling me I was to late. But I managed to grab something to eat even the waiter always removed my tools when I grabbed something. Also here the transport was well organized and the bus for bringing us to MIT was already waiting.
On the first day I joined a few sessions but I will write only something about the most important for me. We had a BoF session for the next APAC FUDCon. What I am worried about is the style which is coming up there, just finding some point why a thing not might be good instead of trying to find out how problems can be solved!

Day 1

I started the day with Jiri Eischmanns presentation about the Fedora workstation and his presence and future. I joined several other talks to, where I just want to mention the Achieving Community Goals With Fedora one from Tenzin Chokden, awesome job of Joerg Simon and Fabian Affolter and their l10n hackfest for the tibetian language, good work. Besides that I had many organizational conversations for organzing stuff in the APAC region.

Day 2

This was actually the most busy day for me as I had in the morning my own workshop about using Inkscape. Well there are some negative things, the room was not the best choice, its hard to work on a small table attached to the chair. But more worst was that the picture from projector was looped to an camera, but the camera was missing so we had to find that out first, so I lost some time for the workshop. But we still managed to draw with the participants what I wanted to achieve and they have a good foundation to use Inkscape in their work and learn it more. I already prepared a screencast, which you can find here.

Ryan switched more to a presentation style, which I only do on events to impress people what with our free software tools can be done and how easy it can be. But as I expect people on a FOSS event like FUDCon are already open to using our tools and just need some help starting to work with them and the best way to learn it is by doing.

After the lunch we had another Ambassadors BoF for APAC, time to speak more Ambassador stuff. We made during this year some progress in APAC and on FUDCon it was visible a lot of asians in a Fedora Ambassador shirts, but we still have not all equipped with them.

We also made progress in producing F21 media centralized but still there are some problems to solve as the process didnt work well, we had no central production in APAC for F22 but we talked how we shall do it in the future and think found the best solution for it. We also had time to discuss if it would possible to replace the DVD media at least partly with USB sticks. We agreed on doing a research on prices until next FAD APAC end of the year and look there if we do it or not. And yes we found an place where we want to do the next FAD – Singapore so we will work on it during the next months to organize it. So we moved again forward.

Day 3

Some went out really in the morning to spent some time in Mumbai, but I am to old for touristic pressure even I would like to have seen more from that city, I was in India for FUDCon and not for an touristic tour. So I went out of the hotel at noon and the cab brought me to the airport, where I enjoyed the sun outside and later I spent some time with Danishka Naven and Izhar Firdaus in the airport.

Day 4

This day I entered a plane in Mumbai short after the day had begun and woke up landing in Zurich. Well I found easily an AC port in this airport and free wifi was also available so I could do some work during the time I had to wait for the next flight, wich was this time just 5 hours later. After this flight I just had a short trip with the train and I arrived right in time for the Design Team meeting.


It was an interesting trip to India seeing how people live there and make new friends, meeting people I worked already with and meeting old friends. I think we moved for the Ambassadors in the APAC region and that means Fedora makes progress in the future in Asia.

WLE 2015 in... Brazil
Lajedo de Pai Mateus - Pedra do Capacete
By Ruy Carvalho (Own work) CC BY-SA, via Wikimedia Commons

This year I was invited once more to be a jury member for the Brazilian Wiki Loves Earth photo competition (thanks Rodrigo!) and it was a pleasure to witness so many wonderful images (yes, I am a bit jealous for my recent inactivity in travel/landscape photography).

Taking a look at their top 10 winners anyone would probably agree this is quality stuff, which will rightfully enrich Wikipedia. Myself, after seeing the larger (around 600 images) selection for the jury, I dare to conclusion a significant increase in quality over the previous year. And I understand the increase was also in quantity, so it looks like a win-win.

Congratulations to the organizers and all the participants!

PS: take a few more moments to admire the winners from the other countries, they are added to the page gradually, as each local jury get its work done. I still ting the Brazilian pictures are among the best so far :)

Cacimba do Padre - Fernando de Noronha
By Dante Laurini Jr (Own work) CC BY-SA, via Wikimedia Commons
Fedora Hubs Update!!!


The dream is real – we are cranking away, actively building this very cool, open source, socially-oriented collaboration platform for Fedora.

Myself and Meghan Richardson, the Fedora Engineering Team’s UX intern for this summer, have been cranking out UI mockups over the past month or so (Meghan way more than me at this point. :) )

Screenshot from 2015-06-23 09-24-44

We also had another brainstorming session. We ran the Fedora Hubs Hackfest, a prequel to the Fedora Release Engineering FAD a couple of weeks ago.

After a lot of issues with the video, full video of the hackfest is now finally available (the reason for the delay in my posting this :) ).

<iframe allowfullscreen="allowfullscreen" frameborder="0" height="315" src="https://www.youtube.com/embed/p-KYhPlUUBU" width="560"></iframe>

Let’s talk about what went down during this hackfest and where we are today with Fedora Hubs:

What is Fedora Hubs, Exactly?

(Skip directly to this part of the video)

We talked about two elevator pitches for explaining it:

  • It’s an ‘intranet’ page for the Fedora Project. You work on all these different projects in Fedora, and it’s a single place you can get information on all of them as a contributor.
  • It’s a social network for Fedora contributors. One place to go to keep up with everything across the project in ways that aren’t currently possible. We have a lot of places where teams do things differently, and it’s a way to provide a consistent contributor experience across projects / teams.

Who are we building it for?

(Skip directly to this part of the video)

  • New Fedora Contributors – A big goal of this project is to enable more contributors and make bootstrapping yourself as a Fedora contributor less of a daunting task.
  • Existing Fedora Contributors – They already have a workflow, and already know what they’re doing. We need to accommodate them and not break their workflows.

The main philosophy here is to provide a compelling user experience for new users that can potentially enhance the experience for existing contributors but at the very least will never disrupt the current workflow of those existing contributors. Let’s look at this through the example of IRC, which Meghan has mocked up in the form of a web client built into Fedora Hubs aimed at new contributor use:

If you’re an experienced contributor, you’ve probably got an IRC client, and you’re probalby used to using IRC and wouldn’t want to use a web client. IRC, though, is a barrier to new contributors. It’s more technical than the types of chat systems they’re accustomed to. It becomes another hurdle on top of 20 or so other hurdles they have to clear in the process of joining as a contributor – completely unrelated to the actual work they want to do (whatever it is – design, marketing, docs, ambassadors, etc.)

New contributors should be able to interact with the hubs IRC client without having to install anything else or really learn a whole lot about IRC. Existing contributors can opt into using it if they want, or they can simply disable the functionality in the hubs web interface and continue using their IRC clients as they have been.

Hackfest Attendee Introductions

(Skip directly to this part of the video)

Next, Paul suggested we go around the room and introduce ourselves for anybody interested in the project (and watching the video.)

  • Máirín Duffy (mizmo) – Fedora Engineering UX designer working on the UX design for the hubs project
  • Meghan Richardson (mrichard) – Fedora Engineering UX intern from MSU also working on the UX design for the hubs project
  • Remy Decausemaker (decause) – Fedora Community lead, Fedora Council member
  • Luke Macken (lmacken) – Works on Fedora Infrastructure, release engineering, tools, QA
  • Adam Miller (maxamillion) – Works on Release engineering for Fedora, working on build tooling and automation for composes and other things
  • Ralph Bean (threebean) – Software engineer on Fedora Engineering team, will be spending a lot of time working on hubs in the next year
  • Stephen Gallagher (sgallagh) – Architect at Red Hat working on the Server platform, on Fedora’s Server working group, interested in helping onboard as many people as possible
  • Aurélien Bompard (abompard) – Software developer, lead developer of Hyperkitty
  • David Gay (oddshocks) – Works on Fedora infrastructure team and cloud teams, hoping to work on Fedora Hubs in the next year
  • Paul Frields (sticksteR) – Fedora Engineering team manager
  • Pierre-Yves Chibon (pingou) – Fedora Infrastructure team member working mostly on web development
  • Patrick Uiterwijk (puiterwijk) – Member of Fedora’s system administration team
  • Xavier Lamien (SmootherFrOgZ) – Fedora Infrastructure team member working on Fedora cloud SIG
  • Atanas Beloborodov (nask0) – A very new contributor to Fedora, he is a web developer based in Bulgaria.
  • (Matthew Miller and Langdon White joined us after the intros)

Game to Explore Fedora Hub’s Target Users

(Skip directly to this part of the video)

We played a game called ‘Pain Gain’ to explore both of the types of users we are targeting: new contributors and experienced Fedora contributors. We started talking about Experienced Contributors. I opened up a shared Inkscape window and made two columns: “pain” and “gain:”

  • For the pain column, we came up with things that are a pain for experienced contributors the way our systems / processes currently work.
  • For the gain column, we listed out ways that Fedora Hubs could provide benefits for experienced contributors.

Then we rinsed and repeated for new contributors:


While we discussed the pains/gains, we also came up with a lot of sidebar ideas that we documented in an “Idea Bucket” area in the file:


I was worried that this wouldn’t work well in a video chat context, but I screen-shared my Inkscape window and wrote down suggestions as they were brought up and I think we came out with a useful list of ideas. I was actually surprised at the number of pains and gains on the experienced contributor side: I had assumed new contributors would have way more pains and gains and that the experienced contributors wouldn’t have that many.

Prototype Demo

(Skip directly to this part of the video)

Screenshot from 2015-06-23 12-57-27

Ralph gave us a demo of his Fedora Hubs prototype – first he walked us through how it’s built, then gave the demo.


In the README there is full explanation of how the prototype works so I won’t reiterate everything there. Some points that came up during this part of the meeting:

  • Would we support hubs running without Javascript? The current prototype completely relies on JS. Without JS, it would be hard to do widgets like the IRC widget. Some of the JS frameworks come with built-in fail modes. There are some accessibility issues with ways of doing things with JS, but a good design can ensure that won’t happen. For the most part, we are going to try to support what a default Fedora workstation install could support.
  • vi hotkeys for Hubs would be awesome. :) Fedora Tagger does this!
  • The way the widgets work now, each widget has to define a data function that gets called with a session object, and it has to return JSON-ifiable python code. That gets stored in memcached and is how the wsgi app and backend communicate. If you can write a data function to return JSON and write a template the data gets plugged into – that’s mainly what’s needed. Take a look at the stats widget – it’s pretty simple!
  • All widgets also need a ‘should_invalidate()’ function that lets the system know what kinds of information apply to which widgets. Every fedmsg has to go through every widget to see if it invalidates a given widget’s data – we were worried that this would result in a terrible performance issue, but by the end of the hackfest we had that figured out.
  • Right now the templates are ginja2, but Ralph thinks we should move to client-side (javascript) templates. The reason is that when updated data gets pushed over websockets from the bus, it can involve garbage communication any time new changes in data come across – it’s simpler that the widget doesn’t have to request the templates and instead the templates are already there in the client.
  • Angular could be a nice client-side way of doing the templates, but Ralph had heard some rumors that AngularJS 2 was going to support only Chrome, and AngularJS 1.3 and 2 aren’t compatible. nask0 has a lot of experience with Angular though and does not think v2 is going to be Chrome-only.
  • TODO: Smoother transitions for when widgets pop into view as they load on an initial load.
  • Langdon wondered if there would be a way to consider individual widgets being able to function as stand-alones on desktops or mobile. The raw zeromq pipes could be hooked up to do this, but the current design uses EventSource which is web-specific and wouldn’t translate to say a desktop widget. Fedora Hubs will emit its own fedmsgs too, so you could build a desktop widget using that as well.
  • Cache invalidation issues was the main driver of the slowness in Fedora Packages, but now we have a cache that updates very quickly so we get constant time access to delivering those pages.

Mockup Review

Screenshot from 2015-06-23 13-48-56

Next, Meghan walked us through the latest (at the time :) we have more now!) mockups for Fedora Hubs, many based on suggestions and ideas from our May meetup (the 2nd hubs video chat.)

Creating / Editing Hubs

(Skip directly to this part of the video)

First, she walked us through her mockups for creating/editing hubs – how a hub admin would be able to modify / set up their hub. (Mockup (download from ‘Raw’ and view in Inkscape to see all screens.)) Things you can modify are the welcome message, colors, what widgets get displayed, the configuration for widgets (e.g. what IRC channel is associated with the hub?), and how to add widgets, among many other things.

Meghan also put together a blog post detailing these mockups.

One point that came up here – a difference is that when users edit their own hubs, they can’t associate an IRC channel with it, but a nick and a network, to enable their profile viewers to pm them.

We talked about hub admins vs FAS group admins. Should they be different or exactly the same? We could make a new role in FAS – “hub admin” – and store it there if it’s another one. Ralph recommended keeping it simple by having FAS group admins and hub admins one and the same. Some groups are more strict about group admins in FAS, some are not. Would there be scenarios where we’d want people to be able to admin the FAS group for a team but not be able to modify the hub layout (or vice-versa?) Maybe nesting the roles – if you’re a FAS admin you can be FAS admin + hub admin, if you’re a hub admin you can just admin the hub but not the FAS group.

Another thing we talked about is theming hubs. Luke mentioned that Reddit allows admins to have free reign in terms of modifying the CSS. Matthew mentioned having a set of backgrounds to choose from, like former Fedora wallpapers. David cautioned that we want to maintain some uniformity across the hubs to help enable new contributors – he gave the example of Facebook, where key navigational elements are not configurable. I suggested maybe they could only tweak certain CSS classes. Any customizations could be stored in the database.

Another point: members vs subscribers on a hub. Subscribers ‘subscribe’ to a hub, members ‘join’ a hub. Subscribing to a hub adds it to your bookmarks in the main horizontal nav bar, and enables certain notifications for that hub to appear in your feed. We talked about different vocabulary for ‘subscribe’ vs ‘join’ – instead of ‘subscribe’ we talking about ‘following’ or ‘starring’ (as in Github) vs joining. (Breaking News :) Since then Meghan has mocked up the different modes for these buttons and added the “star” concept! See below.)


We had a bit of an extended discussion about a lot of the different ways someone could be affiliated with a team/project that has a hub. Is following/subscribing too non-committal? Should we have a rank system so you could move your way up ranks, or is it a redundant gameification given the badge system we have in place? (Maybe we can assign ranks based on badges earned?) Part of the issue here is for others to identify the authority of the other people they’re interacting with, but another part is for helping people feel more a part of the community and feel like valued members. Subscribing is more like following a news feed, being a member is more being part of the team.

Joining Hubs

(Skip directly to this part of the video)

The next set of mockups Meghan went through showed us the workflow of how a user requests membership in a given hub and how the admin receives the membership request and handles it.

We also tangented^Wtalked about the welcome message on hubs and how to dismiss or minimize them. I think we concluded that we would let people collapse them and remove them, and if they remove them we’ll give them a notification that if they want to view them at any time they can click on “Community Rules and Guidelines.”

Similarly, the notification to let the admin know that a user has requested access to something and they dismiss it and want to tend to it later – it will appear in the admin’s personal stream as well for later retrieval.

We talked about how to make action items in a user’s notification feed appear differently than informational notifications; some kind of different visual design for them. One idea that came up was having tabs at the top to filter between types of notifications (action, informational, etc.) I explained how we were thinking about having a contextual filter system in the top right of each ‘card’ or notification to let users show or hide content too. Meghan is working on mockups for this currently.

David had the idea of having action items assigned to people appear as actions within their personal stream… since then I have mocked this up:


Personal Profiles

(Skip directly to this part of the video)

Next Meghan walked us through the mockups she worked on for personal profiles / personal streams. One widget she mocked up is for personal library widgets. Other widgets included a personal badges earned display, hubs you’re a member of, IRC private message, a personal profile.

Meghan also talked about privacy with respect to profiles and we had a bit of a discussion about that. Maybe, for example, by default your library could be private, maybe your stream only shows your five most recent notifications and if someone is approved (using a handshake) as a follower of yours they can see the whole stream. Part of this is sort of a bike lock thing…. everything in a user’s profile is broadcast on fedmsg, but having it easily accessible in one place in a nice interface makes it a lot easier (like not having a lock on your bike.) One thing Langdon brought up is that we don’t want to give people a false sense of privacy. So we have to be careful about the messaging we do around it. We thought about whether or not we wanted to offer this intermediate ‘preview’ state for people’s profiles for those viewing them without the handshake. An alternative would be to let the user know who is following them when they first start following them and to maintain a roster of followers so it is clear who is reading their information.

Here’s the blog post Meghan wrote up on the joining hubs and personal profile mockups with each of the mockups and more details.

Bookmarks / main nav

(Skip directly to this part of the video)

The main horizontal navbar in Fedora Hubs is basically a bookmarks bar of the hubs you’re most interested in. Meghan walked us through the bookmarks mockups – she also covered these mockups in detail on her bookmarks blog post.


Yes. Yes, it is.

So you may be wondering when this is going to be available. Well, we’re working on it. We could always use more help….


Where’s stuff happening?

How does one help? Well, let me walk you through where things are taking place, so you can follow along more closely than my lazy blog posts if you so desire:

  • Chat with us: #fedora-hubs on irc.freenode.net is where most of the folks working on Fedora Hubs hang out, day in and day out. threebean’s hooked up a bot in there too that pushes notifications when folks check in code or mockup updates.
  • Mockups repo: Meghan and I have our mockups repo at https://github.com/fedoradesign/fedora-hubs, which we both have hooked up via Sparkleshare. (You are free to check it out without Sparkleshare and poke around as you like, of course.)
  • Code repo: The code is kept in a Pagure repo at https://pagure.io/fedora-hubs. You’ll want to check out the ‘develop’ branch and follow the README instructions to get all setup. (If I can do it, you can. :) )
  • Feature planning / Bug reporting: We are using Pagure’s issue tracker at https://pagure.io/fedora-hubs/issues to plan out features and track bugs. One way we are using this which I think is kind of interesting – it’s the first time I’ve used a ticketing system in exactly this way – is that for every widget in the mockups, we’ve opened up a ticket that serves as the design spec with mockups from our mockup repo embedded in the ticket.
  • Project tracking: This one is a bit experimental. But the Fedora infra and webdev guys set up http://taiga.fedoraproject.org – an open source kanban board – that Meghan and I started using to keep track of our todo list since we had been passing post-it notes back and forth and that gets a bit unwieldy. It’s just us designers using it so far, but you are more than welcome to join if you’d like. Log in with your Fedora staging password (you can reset it if it’s not working and it’ll only affect stg) and ping us in #fedora-hubs to have your account added to the kanban board.
  • Notification Inventory: This is an inventory that Meghan started of the notifications we’ve come up with for hubs in the mockups.
  • Nomenclature Diagram for Fedora Hubs: We’ve got a lot of neat little features and widgets and bits and bobs in Fedora Hubs, but it can be confusing talking about them without a consistent naming scheme. Meghan created this diagram to help sort out what things are called.

How can I help?

Well, I’m sure glad you asked. :) There’s a few ways you can easily dive in and help right now, from development to design to coming up with cool ideas for features / notifications:

  1. Come up with ideas for notifications you would find useful in Fedora Hubs! Add your ideas to our notification inventory and hit us up in #fedora-hubs to discuss!
  2. Look through our mockups and come up with ideas for new widgets and/or features in Fedora Hubs! The easiest way to do this is probably to peruse the mini specs we have in the pagure issue tracker for the project. But you’re free to look around our mockups repo as well! You can file your widget ideas in Pagure (start the issue name with “Idea:” and we’ll review them and discuss!
  3. Help us develop the widgets we’ve planned! We’ve got little mini design specs for the widgets in the Fedora Hubs pagure issue tracker. If a widget ticket is unassigned (and most are!), it’s open and free for you to start hacking on! Ask Meghan and I any questions in IRC about the spec / design as needed. Take a look at the stats widget that Ralph reviewed in explaining the architecture during the hackfest, and watch Ralph’s demo and explanation of how Hubs is built to see how the widgets are put together.
  4. There are many other ways to help (ask around in #fedora-hubs to learn more,) but I think these have a pretty low barrier for starting up depending on your skillset and I think they are pretty clearly documented so you can be confident you’re working on tasks that need to get done and aren’t duplicating efforts!

    Hope to see you in #fedora-hubs! :)

June 22, 2015

Solving networked scanner issue on HP all-in-one printers
Looking and talking at Ask Fedora, it will be nice to share suggestion for proper networked scanner support on HP all-in-one printers. One of solution is to install hplip-gui via terminal.
sudo dnf install hplip-gui
su -c "dnf install hplip-gui
Unfortunately, the frontend is not listed on Gnome Software due to appdata missing.

Another solution is to directly edit /etc/cups/printers.conf and change the device URI. To find the correct URI with HP protocol  of your networked HP all-in-one printer, use hp-setup -i or hp-setup hostname. The URI should be listed like
Where hp:/net/ is the protocol replacing dnssd://, zc=hostname is the name of hostmane for the all-in-one printer sometime subsituted by ip=ipaddress

For example, the uri of Photosmart eStation C510 is 
Save the change and restart either the system or simply type sudo systemctl restart cups.

You should be able to run a networked scanner with your favourite scanner application like simple-scan. The reason of the process is due to a bug from hplip that failed to assign the hp:/net protocol to their own printer. Hopefull HP will fix the problem in the incoming future.

June 12, 2015

Fondo blanco en 1 minuto – Gimp

Sé que últimamente no he tenido tiempo de publicar en mi blog debido a que estoy super ocupada con el trabajo y la casa (nada de que preocuparse, son buenas noticias), así que mientras trabajaba, decidí simplemente grabar como hago las cosas; creo que a veces hay que dejar de complicarse y solo mostrar las ediciones tal y como son.

En este video podrán ver como se edita una foto de producto si lo único que tienen son hojas blancas y un par de luces. En mi caso, el problema fue que cuando lavé mi fondo blanco para softbox sinplemente murio, se peló (gamuza) y quedó inservible; por lo que tuve que recurrir al plan B y utilizar simples hojas blancas carta.

Espero el tutorial les sea de utilidad, está a velocidad normal y creo que eso les mostrará que es fácil editar. Hay varias formas de hacer lo mismo, sin embargo, es bueno mostrar al menos una de las fáciles. Espero les guste y volver a publicar con mas frecuencia los podcast de tatica!


This post has a nicer formatting that can be seen at it's original source at tatica.org , so feel free to hit the link and read better version!

June 06, 2015

Trying Gnome Boxes 3.16.2 on Fedora 22
Fedora 23 on Gnome Boxes screenshot
Fedora 23 Rawhide within Gnome Boxes

Gnome Boxes is an application similar to VirtualBox that allows installing a operating systems via virtualization or use it remotely. The main focus is the simplicity to casual users wanting to try their system.  One of new features is the ability to do an express installation with minimal interaction which is convenient for a quick setup for say Microsoft Windows system up to 8.1.

One of weakness is the lack of transferring data within the virtualizer as done on VirtualBox useful to do the work on format not supported by applications on Linux distribution notable Fedora which is my main system. On some occasion, Boxes will not detect the existing virtualized system I installed on the main session until the restart. It can be annoying but not enough to detract the experience.

Overall, Gnome Boxes is a very useful tool for developers and also designers wanting to run their operating system without dual boot. The test was done on ASUS X550ZE laptop.

June 02, 2015

Fedora Design Team Update (Two for One!)

Fedora Design Team Logo

I have been very occupied in recent weeks with piggies of various shapes, sizes, and missions in life [1], so I missed posting the last design team meeting update. This is going to be a quick two-for-one with mostly links and not any summary at all. I’ve been trying hard to run the meetings so the auto-generated summaries are more usable, but I am always happy for tips on doing this even better from meetbot pros (like you? :) ?)


Fedora Design Team Meeting 19 May 2015

Fedora Design Team Meeting 2 June 2015

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.


[1] Expect some explanation in a few weeks, or look for me or Dan Walsh at the Red Hat Summit later this month. :)

May 26, 2015

Status of ASUS X550ZE laptop
I updated a status report for aiming a full out of box experience for ASUS X550 family laptop. It is a AMD Kaveri powered laptop featuring Dual Radeon GPU. Known issues are missing functional hotkeys (Fn), broken webcam support and lack of optimized power management.
Fedora 22 Design Suite ready
For artists and designers (i.e. graphics and web), Fedora 22 Design Suite is now available and received a new website located on https://labs.fedoraproject.org/en/design-suite/ . Listed features from the wiki:

  • Now based on Fedora Workstation media.
  • Addition of Sparkleshares, PDF Mod and Shutter applications.
  • Inclusion of plugins for Blender (Lux Render and YaFaRay) and Inkscape (Sozi and Table).
  • Latest versions of Entangle (0.7.0) and Inkscape (0.91)
  • Gimp gained a new G'Mic plugin replacing Greycstation as default.
  • Two shortcut icons for documentation of both Design Suite and Design Team
  • Updated the list of tutorials related to design
Users preferring installing  Fedora Workstation from network can add Design Suite category from the installer.

May 15, 2015

Debatiendo el sistema evaluativo Universitario Venezolano

Como dicen por ahí, “Soñar no cuesta nada”; pero a veces parece que por la misma desidia y desinterés general de la población ya ni eso queremos hacer. No soy graduada universitaria, aunque poco me faltó (razones personales), sin embargo, debido a la profesión que decidí seguir siempre me he encontrado inmersa en el mundo académico. En mis primeros años la gente siempre cuestionaba el hecho de que una Bachiller fuera a decirle a un TSU o Ing. como hacer las cosas; sin embargo, con el pasar de los años la gente comprendió que en el mundo tecnológico no todo se aprende en la Universidad, es más, ya es poco lo que se aprende para afrontar el mundo actual.

En mi vida he podido discutir con alumnos como les gustaría ser evaluados, y también he contado con la oportunidad de tener conversatorios con grupos de profesores Universitarios sobre el mismo tema. Uno de mis favoritos sucedió en la Universidad de Yacambú, donde durante casi 12 horas conversamos sobre las nuevas herramientas en el mundo del Diseño Gráfico y como ya este debía ser llamado “Diseño Integral” para que se pudiera formar a un artista más completo.

Este simple comentario genero un interesante debate entre conocidos (y no) que me hizo escribir este artículo para que, quizás entre mis lectores, se genere un debate más amplio y profundo sobre como se esta evaluando el conocimiento en una era donde el conocimiento está en cualquier rincón.


Si en vez de hacer Tesis/Pasantías se mandara a contribuir en proyectos; y se evaluara en base a los commits…

Reinventar el concepto actual de academia

Tal como comentó Juan, habría que crear conceptos y metodologías nuevas donde los estudiantes comprendieran que el Software actual es más que sentarse en una oficina de 8-5 y que trata más sobre las interacciones que podemos tener con personas de todo el mundo, mientras desarrollamos en un ambiente de comunicación instantánea con nuestros colegas. También se tendría que cambiar el concepto erróneo de los círculos académicos actuales donde el profesionalismo es calificado en una escala de Pasantía a Tesis, sin términos medios.

Una de las cosas que me decepcionó durante mi época Universitaria era ir a visitar la biblioteca de la universidad y mirar con decepción como el 80% de las tesis ahí contenidas eran “desarrollos” de páginas web… y digo “desarrollos” porque era solo instalar un Joomla a algún familiar y pasarlo por tesis. ¿Es que ya no nos interesa ser profesionales y lo único que importa es tener un papel que nos enaltezca el ego?.

Autonomía Utópica

Miguel es profesor Universitario, muy joven, pero con más experiencia que la mayoría de sus colegas sesentones. Es un joven que, a pesar de tener un trabajo estable en un Start-Up de “puta madre” gasta tiempo y energía en educar a jóvenes como el para que aprendan de su experiencia y se conviertan en profesionales de verdad y no de papel. Miguel comenta que “muchas de las certificaciones y cursos en el área académica no están dirigidos al manejo de herramientas, sino a teorías o conceptos”, lo cual no se ajusta a nuestra era actual donde desarrollamos sin siquiera saberlo.


El principal problema que expone Miguel es que “elaborar una materia no es algo de la noche a la mañana porque se debe desarrollar el programa analítico, buscar los temas, pasar por la burocracia interna de la Universidad, para luego pasar por la burocracia del Ministerio de Educación Superior, eso sin tomar en cuenta que el método de evaluación puede afectar la normativa existente y sería necesario hacer un ajuste de la norma primero”. De cierta forma, pareciese que el sistema Universitario Venezolano no quiere mejorar, ya que eso podría significar mas horas de trabajo, esfuerzo y dedicación. Pero seamos honestos, ¿Quien quiere dedicarse a -entrenar competencia- por un sueldo mínimo?

Luego de preguntar mucho (ya que dicho documento no se encuentra en la web del Ministerio) me facilitaron el documento donde dicta las pautas del Contrato Colectivo del 2013-2014 (el del 2015 aún está en discusión y ya estamos a Mayo).En el tabulador, el mayor sueldo pagado es a los profesores de Dedicación Exclusiva (Entiéndase, no puede trabajar en otro lugar de forma oficial) y fue fijado a partir del 01-01-2014 en 15.297Bs. Recordemos que no se han ajustado los sueldos de los profesores desde dicha fecha. Lo triste del caso es que la gran mayoría de los Profesores no son de dedicación exclusiva, sino Asistentes, Asociados o Auxiliares. Para poner un ejemplo de una persona profesional que conozco, esta es una foto de la constancia de trabajo de el Padre de una amiga que, además de ser un excelente profesional, es un gran catedrático. Me pregunto, ¿Estaría Ud. dispuesto a trabajar durante uno o dos años para desarrollar un nuevo pensum universitario por un sueldo de 5.118Bs?

Me parece que criticar este salario sin que se tenga conocimiento de cuanto gana un Profesor fuera de nuestras fronteras es injusto, por lo que también investigué estas cifras. Un profesor gana en promedio entre 30.000USD y 130.000USD al año; esto nos indica que el salario mínimo mensual de un Educador está en 2.500USD. El profesor mejor pagado de nuestro país gana lo siguiente:

Profesor de Tiempo Completo y Dedicación Exclusiva: 15.297Bsf a la tasa SICAD (12Bs) = 1.274USD

Profesor de Tiempo Completo y Dedicación Exclusiva: 15.297Bsf a la tasa SIMADI (171Bs) = 89USD

Profesor de Tiempo Completo y Dedicación Exclusiva: 15.297Bsf a la tasa de Mercado Negro (300Bs) = 50USD

Incluso calculando el salario más alto del tabulador Venezolano a tasa preferencial, no llega ni a la mitad del salario mínimo de un profesor fuera de nuestras fronteras. Con esto, varias preguntas surgen. ¿A que tasa -real- debemos calcular el salario Venezolano? ¿Ud. Profesor Universitario, gana 15.297Bs o está en un escalafón diferente? ¿Luego de conocer estas cifras aún le parece mal que los profesores se rebusquen fuera del ambiente académico?

Soluciones reales en momentos de crisis

Es muy fácil decir “Suban los sueldos” o “Trabajen para construir la patria”, pero la verdad (como decimos los de IT cuando nos piden favores -grandes-) es que “nosotros no comemos cables” y los profesores dudo que coman libros. Desde mi punto de vista, las 4 profesiones que deberían estar en el tope del escalafón de sueldos deberían ser los Profesores, los Médicos, los Ing. Agrícolas y los Policías; de esa forma se asegura educación, salud, alimentación y seguridad de alta calidad; sin embargo, no creo que el Gobierno deba asumir absolutamente todo. Si el gobierno no puede pagar un sueldo digno a un profesional, entonces la privatización de servicios (completa o parcial) tiene que ser la solución. Al no ofrecerse sueldos de calidad vemos dos problemáticas, la primera es que los Profesionales que trabajan actualmente en el entorno educativo no se exigen ya que no tienen una motivación salarial (y quien diga que la motivación es mejorar a la patria claramente no tiene familia que mantener), y la segunda problemática es que los graduandos que salen a la calle a buscar trabajo prefieren ser taxistas o ejercer una profesión diferente (o emigrar) en busca de un salario digno que le permita vivir bien. Entonces, ¿Como podemos motivar al profesional para que trabaje -por la patria-?

prof-univOtra posible solución es que, ya que los pensum son desarrollados completamente bajo la tutela del Ministerio de Educación, se escoja un grupo de Educadores, se desarrolle un Simposio (Pago, no necesariamente costoso, para ayudar con los costos y generar conciencia de que el conocimiento cuesta) donde durante una semana se debatan estos temas y se hagan propuestas realistas que puedan terminar en un enriquecimiento del compendio de temas que componen las carreras actuales. Ojo, a este Simposio deberían ser invitados no solo los Profesores con larga trayectoria, sino aquellos profesionales que conocen el campo laboral actual y puedan ajustar las viejas enseñanzas a los nuevos requerimientos del entorno productivo Venezolano.

En fin, este artículo es más que todo una reflexión, un análisis y un texto que busca quizás crear un poco de conciencia sobre el tema de la educación Universitaria. Recordemos que en el mundo actual, el mayor cúmulo de conocimiento viene de la información digital que (queramos o no) está ahí. En vez de verla como el enemigo, veamosla como la mejor herramienta que tenemos para mejorar como profesionales y personas.

This post has a nicer formatting that can be seen at it's original source at tatica.org , so feel free to hit the link and read better version!

May 13, 2015

FREE Firefox?

Let's assume one is a "normal" Firefox user, so based on Windows and with no knowledge about using directly the mirrors (or without intimate knowledge of obscure acronyms). And let's assume the same person wants a FREE web browser, one with no binary blobs, with source available and not blocking the content from its user.

The challenge is, going from the Firefox start page, find a way to download the FREE version, without using external websites (so no Google search).

free firefox 38

Answer: Expand the menu thingy at the top, then go to the About page, then to the blog and find there an apologising post with a deep-buried link inside.