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.

En estos días realicé el siguiente comentario en Twitter: “Si en vez de hacer tesis/pasantías se mandara a contribuir en proyectos; y se evaluara en base a los commits…”

tata-twit
 

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.

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?

photo_2015-05-15_08-16-17
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-?

Otra 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.

prof-univ
afd

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.

Flattr this!

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.

May 11, 2015

15th Anniversary Linuxwochen Vienna

As all the last year in May the event row called Linuxwochen makes it stop in Vienna and I represented Fedora there. This year it was an special event as the Linuxwochen could celebrate their 15th anniversary. And this years event was indeed special, normally this event is compared to others a smaller one as it is from Thursday to Saturday. But this year it was on Thursday already crowded and it looked some more Germans have found their way to Vienna. Also both of the workshop I gave in Vienna was an success and as always filled with people.
Personally I think the exhibition area was this year a nice one to, as Axiom Apertus Beta was presented there, first that this open source camera was presented in public and also Mozilla did show an TV running Firefox (an TV that you can buy, greetings to Ubuntu).
The social event was this year also a nice one, with an special delicious cake. So it was all in all a win to been there personally as for Fedora.

May 07, 2015

Time to kick the tires on the new Fedora websites in staging!

So a couple of weeks ago I mentioned the work robyduck and the Fedora websites team have been putting in on the new websites for Fedora, primarily, spins.fedoraproject.org and labs.fedoraproject.org. Here’s the handy little diagram I put together back then to explain:

diagram showing four different fedora sites

This week, robyduck got the new site designs into staging, which means you can try out the new work-in-progress sites right now and provide us your helpful feedback, suggestions (and dare I suggest it) content contributions to make the sites even better. :)

labs.fedoraproject.org

Click below to visit the staging site:
Screenshot from 2015-05-07 17:02:39

spins.fedoraproject.org

Click below to visit the staging site:
Screenshot from 2015-05-07 17:02:29

You may notice as you peruse through the Fedora Labs staging site and the Fedora Spins staging site you’re going to see some bogus stuff. For example, the Robotics Suite page highlights Gimp and Inkscape as included applications. :) This is because a lot of the content is filler content and we need help from the users of these spins and experts in the individual technologies of what we should be featuring and how we should be describing these spins.

So this is sort of a continuation of our earlier call for help, but this one is really mostly focused on content – we really need your help.

help-1

With the staging sites for spins.fedoraproject.org and labs.fedoraproject.org up and running, we are hoping this will make it easier for folks to understand where we are lacking content and could use some help figuring out what to say about each spin. It helps to see it all in context for every spin.

This is a good way to contribute to an open source project if you enjoy writing or documentation – we will handle all the details of getting the content into the pages, you would simply need to email us or blog comment (or whatever is easiest for you) the content you are contributing.

If you are interested in helping us out or even have a particular interest in one of the following spins that is in most need of help, can you get in touch with us and we’ll help you get started?

  • Robotics Suite – needs list of featured applications with short descriptions.
  • Fedora Jam – needs list of featured applications with short descriptions. Could use an updated top-level description (the 2 paragraphs up top) as well.
  • Security Lab – needs list of featured applications with short descriptions.
  • Sugar on a Stick – needs list of featured applications with short descriptions.

We’d appreciate any help you can provide. Get in touch in the comments to this post!

May 05, 2015

Fedora Design Team Update

Fedora Design Team Logo

Fedora Design Team Meeting 5 May 2015

This is a very, very quick summary post:

Highlights

  • We had three tickets that opened up today – ticket 371 for a sticker design that mleonova picked up, ticket 369 for the flock 2015 t-shirt which riecatnor picked up, and 210 for an updated map graphics which bronwynmowens grabbed.
  • We had some nice “Going to FUDcon” artwork designed by jurankdankkal and gnokki in ticket 359 – good work!!
  • Bronwyn finished her the artwork for her first ticket, ticket 347 which is a series of banners to advertise Fedora on stackexchange.
  • We gave threebean some advice on fedmenu (ticket 374) and I think we came up with some interesting ideas. I am going to copy/pasta the discussion into ticket 374 and we may end up having another discussion about it.
  • kirkB has been making progress on ticket 364 (to update the Design team wiki page) and posted his draft asking for comments / feedback. If you are a design team member please take a look and let him know what you think in the ticket! :)

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.

April 30, 2015

Do you know robotics?

Hi :)

Plea for help here :)

rg1024-tripulated-robot

The websites team and I would like to feature a photo of some real robots that have been programmed and/or built using Fedora as the main banner image for the Fedora Robotics spin – but we don’t know of any specific Fedora robots. We’d even be happy with a picture of a non-Fedora robot at this point.

If you know someone who is knowledgable about robotics and/or Fedora robotics, and who may have a picture they’d be willing to let us use, can you please get in touch?

Thanks :)

April 29, 2015

Darktable 1.6.6 necesita más Fedora Testers!!!

Screenshot from 2014-04-26 19:23:16Saludos Usuarios Fedora, tal como Kasun indicó en su correo a la lista de la Comunidad Darktable, se necesitan más betatesters para que la versión 1.6.6 esté disponible para todos.

Darktable 1.6.6 está actualmente en los repos de testing. Luego de que 3 usuarios confirmen que funciona, será automáticamente enviado al repo de updates y estará disponible en todo el mundo. Si quieres ser un tester, esto es lo que debes hacer:

Paso 1: Instala darktable 1.6.6 desde el repo de testing de la siguiente forma.

su -c “yum –enablerepo=updates-testing update darktable”

Paso 2: Revisa la aplicación y verifica como funciona.

Paso 3: Ve a la dirección que corresponde a tu versión de Fedora y registrate (Debes crear una cuenta Fedora si no tienes una).

https://admin.fedoraproject.<wbr></wbr>org/updates/FEDORA-2015-6991/<wbr></wbr>darktable-1.6.6-1.fc21  para Fedora 21

https://admin.fedoraproject.<wbr></wbr>org/updates/FEDORA-2015-6981/<wbr></wbr>darktable-1.6.6-1.fc20  para Fedora 20

https://admin.fedoraproject.<wbr></wbr>org/updates/FEDORA-2015-6976/<wbr></wbr>darktable-1.6.6-1.fc22  para Fedora 22

Paso 4: Agrega “Funciona para mi / Works for me” en los comentarios (agregalo en inglés, solo copia y pega el texto ;) )

Y eso es todo! Darktable 1.6.6 será público!

Flattr this!

Vienna Calling

Next week there will be the austrian road show called Linuxwochen make its station in Vienna and Fedora will be present. We will have of course an booth there and I will deliver also 2 workshops, one for Inkscape and one for Blender. You find the full schedule with all talks and workshops here.

April 23, 2015

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

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

spins.fedoraproject.org front page screenshot

spins.fedoraproject.org front page screenshot

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

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

Different kinds of spins

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

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

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

Here’s a rough diagram to illustrate:

diagram showing four different fedora sites

Desktop Spins (spins.fpo)

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

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

spins.fpo mockup

spins.fpo mockup

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

Desktop spin details page

Desktop spin details page

Functional Spins (labs.fpo)

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

labs.fpo front page mockup

labs.fpo front page mockup

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

labs.fpo details page mockup

labs.fpo details page mockup

ARM

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

Anyway here’s where that mockup is at now:

Fedora builds for ARM mockup

Fedora builds for ARM mockup

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

NOOOOOOOO!!!!11 NOT TRUE!

help-1

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

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

Thanks :)

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

April 22, 2015

Fedora Design Team Update

Fedora Design Team Logo

Fedora Design Team Meeting 21 April 2015

Summary

Announcements/News

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

Tickets Needing Feedback

Tickets Needing Updates

Tickets Needing Triage

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

Completed Tickets

LinuxFest NorthWest Ad

FEDORA-quarter-page_2015_lfnw_quarter-inch-NObleed-v5

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

Tickets Open For You to Take!

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

See you next time?

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

April 07, 2015

Fedora Design Team Update

Fedora Design Team Logo

Fedora Design Team Meeting 7 April 2015

Summary

I don’t actually have time today to post a full summary, so just a few bullet points:

  • Bronwyn, my new intern, started today so we welcomed her at the meeting and she took on her first ticket, which she’s working on right now.
  • We walked through tickets needing attention and tickets needing triage.
  • We talked about the F22 Beta readiness meeting – I will attend to represent the team this Thursday.
  • We talked about Flock and discussed more details about the topics we’d like to propose.

March 28, 2015

Testing Design Suite on Asus X550ZE
I recently bought an ASUS X550ZE to replace the venerable Sony VAIO N250E laptop. The reason of choosing an AMD powered laptop is for long term support i.e. the use of Vulkan API in future AMD GPU driver. In summary, here is the ASUS X550ZE specification taken from ASUS website:
  • Processor
    AMD® APU A10-7400P /A8-7200P/FX-7600P Processor
  • Chipset
    AMD A76M FCH
  • Memory
    DDR3L 1600 MHz SDRAM, 8 GB
  • Display
    15.6" 16:9 /Full HD (1920x1080)
  • Graphic
    AMD Radeon® R5 M230 + Radeon® R7 M265 DX Dual Graphics with 2GB DDR3 VRAM Built-in A10-7400P
  • Storage
    2.5" 9.5mm SATA
    1TB 5400/7200 RPM
  • Optical Drive
    Super-Multi DVD
  • Card Reader
    2 -in-1 card reader ( SD/ SDHC/ MMC)
  • Camera
    VGA Web Camera
  • Networking
    Integrated 802.11 b/g/n
    Built-in Bluetooth™ V4.0 (Optional)
    10/100/1000/Gigabits Base T
  • Interface
    1 x COMBO audio jack
    1 x VGA port/Mini D-sub 15-pin for external monitor
    2 x USB 3.0 port(s)
    1 x RJ45 LAN Jack for LAN insert
    1 x HDMI

  • Audio
    Built-in Speakers And Microphone
    SonicMaster
  • Battery
    4Cells 44 Whrs
  • Power Adapter
    Output :
    19 V DC, 4.74 A, 90 W
    Input :
    100 -240 V AC, 50/60 Hz universal
Booting Fedora Design Suite 22 Beta TC5 went well except a bug on Radeon driver prompting to set "nomodeset" on boot configuration. Once at the desktop session, ithe following issues are:
  • Fn buttons from backlight to volume not functional
  • Touchpad not functional. Not sure if it is related on the xorg-x11-drv-libinput or xorg-x11-drv-synaptics and possible the laptop is new.
  • High power consumption. With only the generic graphical driver (llvmpipe), the battery longevity is only two hours without proper power management
  • Because of use of generic graphical driver , neither Cheese nor Video works without crashing. Attempting to use Wayland will cause fallback to login screen.

On the positive side:
  • Bluetooth is functional
  • Display is set at high setting i.e. Full HD (1920x1080)
  • Applications like Gimp, Inkscape takes advantage of the quad-core feature.
Despite the shortcoming due to driver issues, the laptop is still useful for work usage. Perhaps a kernel update will address the problem.

Update:
After removing "nomodeset" from boot parameter, the login screen displayed under Wayland. The default Gnome session crashed but the Gnome on Wayland runs smoothly aside some known issues.

March 25, 2015

Winner Wallpaper for Fedora 22

The 5 days the Fedora contributors had to choose there favorites amongst the submissions for Fedora 22 Supplemental Wallpaper are over and here is the result:

Congratulation to all winners, and for the not chosen one, there will be definitely a Fedora 23 contest. Where your picture ended up and also some statistics you can find at nuancier.

Summary of Enabling New Contributors Brainstorm Session

Photo of Video Chat

So today we had a pretty successful brainstorm about enabling new contributors in Fedora! Thank you to everyone who responded my call for volunteers yesterday – we were at max capacity within an hour or two of the post! :) It just goes to show this is a topic a lot of folks are passionate about!

Here is a quick run-down of how it went down:

Video Conference Dance

We tried to use OpenTokRTC but had some technical issues (we were hitting an upper limit and people were getting booted, and some folks could see/hear some but not others. So we moved onto the backup plan – BlueJeans – and that worked decently.

Roleplay Exercise: Pretend You’re A Newbie!

Watch this part of the session starting here!

For about the first 30 minutes, we brainstormed using a technique called Understanding Chain to roleplay as if we were new contributors trying to get started in Fedora and noting all of the issues we would run into. We started thinking about how would we even begin to contribute, and then we started thinking about what barriers we might run up against as we continued on. Each idea / thought / concept got its own “sticky note” (thanks to Ryan Lerch for grabbing some paper and making some large scale stickies,) I would write the note out, Ryan would tack it up, and Stephen would transcribe it into the meeting piratepad.

Photo of the whiteboard with all of the sticky notes taped to it.

Walkthrough of the Design Hubs Concept Thus Far

Watch this part of the session starting here!

Next, I walked everyone through the design hubs concept and full set of mockups. You can read up more on the idea at the original blog post explaining the idea from last year. (Or poke through the mockups on your own.)

Screenshot of video chat: Mo explaining the Design Hubs Concept

Comparing Newbie Issues to Fedora Hubs Offering

Watch this part of the session starting here!

We spent the remainder of our time wakling through the list of newbie issues we’d generated during the first exercise and comparing them to the Fedora Hubs concept. For each issue, we asked these sorts of questions:

  • Is this issue addressed by the Fedora Hubs design? How?
  • Are there enhancements / new features / modifications we could make to the Fedora Hubs design to better address this issue?
  • Does Fedora Hubs relate to this issue at all?

We came up with so many awesome ideas during this part of the discussion. We had ideas inline with the issues that we’d come up with during the first exercise, and we also had random ideas come up that we put in their own little section on the piratepad (the “Idea Parking Lot.”)

Here’s a little sampling of ideas we had:

  • Fedorans with the most cookies are widely helpful figures within Fedora, so maybe their profiles in hubs could be marked with some special thing (a “cookie monster” emblem???) so that new users can find folks with a track record of being helpful more easily. (A problem we’d discussed was new contributors having a hard time tracking down folks to help them.)
  • User hub profiles can serve as the centralized, canonical user profile for them across Fedora. No more outdated info on wiki user pages. No more having to log into FAS to look up information on someone. (A problem we’d discussed was multiple sources for the same info and sometimes irrelvant / outdated information.)
  • The web IRC client we could build into hubs could have a neat affordance of letting you map an IRC nick to a real life name / email address with a hover tool tip thingy. (A problem we’d discussed was difficulty in finding people / meeting people.)
  • Posts to a particular hub on Fedora hubs are really just content aggregated from many different data sources / feeds. If a piece of data goes by that proves to be particularly helpful, the hub admins can “pin” it to a special “Resources” area attached to the hub. So if there’s great tutorials or howtos or general information that is good for group members to know, they can access it on the team resource page. (A problem we’d discussed was bootstrapping newbies and giving them helpful and curated content to get started.)
  • Static information posted to the hub (e.g. basic team metadata, etc.) could have a set “best by” date and some kind of automation could email the hub admins every so often (every 6 months?) and ask them to re-read the info and verify if it’s still good or update it if not. (The problem we’d discussed here was out-of-date wiki pages.)
  • Having a brief ‘intake questionnaire’ for folks creating a new FAS account to get an idea of their interests and to be able to suggest / recommend hubs they might want to follow. (Problem-to-solve: a lot of new contributors join ambassadors and aren’t aware of what other teams exist that could be a good place for them.)

There’s a lot more – you can read through the full piratepad log to see everything we came up with.

Screenshot of video chat discussion

Next Steps

Watch this part of the session starting here!

Here’s the next steps we talked about at the end of the meeting. If you have ideas for others or would like to claim some of these items to work on, please let me know in the comments!

  1. We’re going to have an in-person meetup / hackfest in early June in the Red Hat Westford office. (mizmo will plan agenda, could use help)
  2. We need a prioritized requirements list of all of the features. (mizmo will work on this, but could use help if anybody is interested!)
  3. The Fedora apps team will go through the prioritized requirements list when it’s ready and give items an implementation difficult rating.
  4. We should do some resarch on the OpenSuSE Connect system and how it works, and Elgg, the system they are using for the site. (needs a volunteer!)
  5. We should take a look at the profile design updates to StackExchange and see if there’s any lessons to be learned there for hubs. (mizmo will do this but would love other opinions on it.)
  6. We talked about potentially doing another video chat like this in late April or early May, before the hackfest in June.
  7. MOAR mockups! (mizmo will do, but would love help :))

How to Get Involved / Resources

So we have a few todos listed above that could use a volunteer or that I could use help with. Here’s the places to hang out / the things to read to learn more about this project and to get involved:

Please let us know what you think in the comments! :)

March 24, 2015

Fedora Design Team Update

Fedora Design Team Logo

Fedora Design Team Meeting 24 March 2015

Completed Tickets

Ticket 361: Fedora Reflective Bracelet

This ticket involved a simple design for a reflective bracelet for bike riders to help them be more visible at night. The imprint area was quite small and the ink only one color, so this was fairly simple.

Tickets Open For You to Take!

One of the things we required to join the design team is that you take and complete a ticket. We have one ticket currently open and awaiting you to claim it and contribute some design work for Fedora :):

Discussion

Fedora 22 Supplemental Wallpapers Vote Closes Tomorrow!

Tomorrow (Wednesday, March 25) is the last day to get in your votes for Fedora 22’s supplemental wallpapers! Vote now! (All Fedora contributors are eligible to vote.)

(Oh yeah, don’t forget – You’ll get a special Fedora badge just for voting!)

Fedora 22 Default Wallpaper Plan

A question came up what our plan was with the Fedora 22 wallpaper – Ryan Lerch created the mockups that we shipped / will ship in the alpha and beta and the feedback we’ve got on these is positive thus far so we’ll likely not change direction for Fedora 22’s default wallpaper. The pattern is based on the pattern Ryan designed for the Fedora.next product artwork featured on getfedora.org.

However, it is never too early to think about F23 wallpaper. If you have some ideas to share, please share them on the design team list!

2015 Flock Call for Papers is Open!

Flock is going to be at the Hyatt Regency in Rochester, New York. The dates are August 12 to August 15.

Gnokii proposed that we figure out which design team members are intending to go, and perhaps we could plan out different sessions for a design track. Some of the sessions we talked about:

  • Design Clinic – bring your UI or artwork or unfiled design team ticket to an open “office hours” session with design team members and get feedback / critique / help.
  • Wallpaper Hunt – design team members with cameras could plan a group photoshoot to get nice pictures that could make good wallpapers for F23 (rietcatnor suggested Highland Park as a good potential place to go.
  • Badge Design Workshop – riecatnor is going to propose this talk!

I started a basic wiki page to track the Design Team Flock 2015 presence – add your name if you’re intending to go and your ideas for talk proposals so we can coordinate!

(I will message the design-team list with this idea too!)

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.

Enabling New Contributors Brainstorm Session

You (probably don’t, but) may remember an idea I posted about a while back when we were just starting to plan out how to reconfigure Fedora’s websites for Fedora.next. I called the idea “Fedora Hubs.”

Some Backstory

The point behind the idea was to provide a space specifically for Fedora contributors that was separate from the user space, and to make it easier for folks who are non-packager contributors to Fedora to collaborate by providing them explicit tools to do that. Tools for folks working in docs, marketing, design, ambassadors, etc., to help enable those teams and also make it easier for them to bring new contributors on-board. (I’ve onboarded 3 or 4 people in the past 3 months and it still ain’t easy! It’s easy for contributors to forget how convoluted it can be since we all did it once and likely a long time ago.)

Well, anyway, that hubs idea blog post was actually almost a year ago, and while we have a new Fedora project website, we still don’t have a super-solid plan for building out the Fedora hub site, which is meant to be a central place for Fedora contributors to work together:

The elevator pitch is that it’s kind of like a cross between Reddit and Facebook/G+ for Fedora contributors to keep on top of the various projects and teams they’re involved with in Fedora.

There are some initial mockups that you can look through here, and a design team repo with the mockups and sources, but that’s about it, and there hasn’t been a wide or significant amount of discussion about the idea or mockups thus far. Some of the thinking behind what would drive the site is that we could pull in a lot of the data from fedmsg, and for the account-specific stuff we’d make API calls to FAS.

Let’s make it happen?

"Unicorn - 1551"  by j4p4n on openclipart.org. Public Domain.

“Unicorn – 1551″ by j4p4n on openclipart.org. Public Domain.

Soooo…. Hubs isn’t going to magically happen like unicorns, so we probably need to figure out if this is a good approach for enabling new contributors and if so how is it going to work, who is going to work on it, what kind of timeline are we looking at – etc. etc. So I’m thinking we could do a bit of a design thinking / brainstorm session to figure this out. I want to bring together representatives of different teams within Fedora – particularly those teams who could really use a tool like this to collaboate and bring new contributors on board – and have them in this session.

For various reasons, logistically I think Wednesday, March 25 is the best day to do this, so I’m going to send out invites to the following Fedora teams and ask them to send someone to participate. (I realize this is tomorrow – ugh – let’s try anyway.) Let me know if I forgot your team or if you want to participate:

  • Each of the three working groups (for development representation)
  • Infrastructure
  • Websites
  • Marketing
  • Ambassadors
  • Docs
  • Design

I would like to use OpenTokRTC for the meeting, as it’s a FLOSS video chat tool that I’ve used to chat with other Fedorans in the past and it worked pretty well. I think we should have an etherpad too to track the discussion. I’m going to pick a couple of structured brainstorming games (likely from gamestorming.com) to help guide the discussion. It should be fun!

The driving question for this brainstorm session is going to be:

How can we lower the bar for new Fedora contributors to get up and running?

Let me know if this question haunts you too. :)

This is the time we’re going to do this:

  • Wednesday March 25 (tomorrow!) from 14:00-16:00 GMT (10-12 AM US Eastern.)

Since this is short-notice, I am going to run around today and try to personally invite folks to join and try to build a team for this event. If you are interested let me know ASAP!

(‘Wait, what’s the rush?’ you might ask. I’m trying to have a session while Ryan Lerch is still in the US Eastern timezone. We may well end up trying another session for after he’s in the Australian timezone.)


Update

I think we’re just about at the limit of folks we can handle from both the video conferencing pov and the effectiveness of the brainstorm games I have planned. I have one or two open invites I’m hoping to hear back from but otherwise we have full representation here including the Join SIG so we are in good shape :) Thanks Fedora friends for your quick responses!

March 20, 2015

Fedora 22 wallpaper – voting open!

The submission phase for Fedora 22 Supplemenal Wallpaper is now over and the voting is open. You can vote, if yu have an Fedora account cla +1 until 25th of March. Dont forget to claim the badge, the link for the claim will be showed after the voting. But nw is als time to say something to the submissions, we received this time not a lot, that might be because of the shortage of the submission phase. We got 69 submissions thats half of the last one. Unfortunately I had to deny a lot of them because persons or trademarks on them or wrong format. The quality of the submissions is this time als not that good, a lot of our good photographers did nt submit something. Personally I find it hard to find 16 amngst the submissions, tht would be worthy to gt packaged. But this are my personally favorites:

But now go and look for yourself and vote.

March 10, 2015

Fedora Design Team Update

Fedora Design Team Logo

One of the things the Fedora Design Team decided to do following the Design Team Fedora Activity Day(s) we had back in January was to meet more regularly. We’ve started fortnightly meetings; we just had our second one.

During the FAD, we figured out a basic process for handling incoming design team tickets and Chris Roberts and Paul Frields wrote the SQL we needed to generate ticket reports for us to be able to triage and monitor our tickets more efficiently. From our whiteboard:

1

Anyhow, with those ticket reports in place and some new policies (if a ticket is older than 4 weeks with no response from the reporter, we’ll close it; if a ticket hasn’t had any updates in 2 weeks and the designer who took the ticket is unresponsive, we open it up for others) we went through a massive ticket cleanout during the FAD. We’ve been maintaining that cleanliness at our fortnightly meetings: we have only 16 open tickets now!

Were you to join one of our meetings, you’ll note we spend a lot of time triaging tickets together and getting updates on ticket progress; we also have an open floor for announcements and for designers to get critique on things they are working on.

Here’s a report from our latest meeting. I don’t know if I’ll have time to do this style of summary after every meeting, but I’ll try to do them after particularly interesting or full meetings. When I don’t post one of these posts, I will post the meetbot links to the design-team mailing list, so that is the best place to follow along.

Fedora Design Team Meeting 10 March 2015

Completed Tickets

FUDCon APAC 2015 Call for Proposals Poster

Shatadru designed a poster for FUDCon APAC in ticket 353; we closed the ticket since the CFP was closed.

353-3-1-compressed

LiveUSB Creator Icons

Gnokii took on a new ticket to design some icons for the new LiveUSB creator UI.

FUDCon Pune Logo design

logo date

Suchakra and Yogi together created the logo for FUDCon Pune, and we closed the ticket as the work was all done and accepted.

Standee Banner Design for Events

banner-czech2

Gnokii gave us a print-ready CMYK tiff for this banner design ticket; we updated it with a link to the file and asked for feedback from the reporter (siddesh.)

Fedora Magazine favicon

Ryan Lerch created a favicon for Fedora Magazine, so we closed the ticket seeing as it was done. :)

Tickets In Progress

Tickets Open For You to Take!

One of the things we required to join the design team is that you take and complete a ticket. We opened up 3 tickets for folks to be able to take – this could be you! Let me know if you want to work on any of these!

Discussion

Fedora 22 Supplemental Wallpapers Submission Window Closing Soon!

Gnokii pointed out that we really need more submissions for Fedora 22 supplemental wallpapers; the deadline is March 19. If you have some nice photography you’d like to submit or have a friend who has openly licensed photography you think would be a good match for Fedora, please submit it! All of the details are on gnokii’s blog post, and you can submit them directly in Nauncier, our wallpaper submission & voting app.

1/4 Page Ad for LinuxFest Northwest

One of our newest members, mleonova, put together some mockups for an ad for Fedora to go in the LinuxFest Northwest program. We gave her some critiques on her work and she is going to work on a final draft now.

New look for Fedora Magazine

Screenshot from 2015-03-10 14:38:11

Ryan Lerch put together a new design for Fedora Magazine on a test server and shared it with us for feedback; overall the feedback was overwhelmingly positive and we only had a couple of suggestions/ideas to add.

Ask.fedoraproject.org Redesign

Suchakra, Banas, and Sadin worked on a redesign of ask.fedoraproject.org during the Design Team FAD for ticket 199 and Suchakra showed us some things he’d been working on for that ticket. So far the work looks great, and it’s now listed as a possible summer project for a Fedora intern in GSoc.

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.

Fedora Design Suite 22 Alpha
Design Suite Alpha 22 is available for downloading along the Workstation edition of Fedora 22 Alpha which is based.
The spins includes plugins for both Gimp (Gmic), Inkscape (support of making tables) and Blender (LuxRender). Shutter, a screenshot tool for desktop, is  added at the request of Design Team.

More documentations related to Design Suite and Design Team are added for informing users, however known issue is swapped names of the correct url address which is fixed for beta release.

In addition, the installer received similar updates for users looking to use Design related group of packages via either Server  edition or other spin variants.

February 24, 2015

New GIMP 2.9.1 master builds available for Fedora

After a 6-month hiatus, I have finally gotten the GIMP 2.9.1 development builds working again for Fedora 21. These development builds are built from the upstream git master branch of what will be GIMP 2.10 when it is released.

Check out the COPR page for these builds for futher details on enabling and installing from this repo, but also note that this is an experimental repo of unstable software, so tread cautiously.

The one major feature that is of most interest is the ability to do image manipulations with 32bit float precision; which is possible in version 2.9.1 of GIMP via the power of GEGL.

 

February 23, 2015

Make Fedora 22 Beautiful !

Time is flying, Fedora 21 is there just 2 months and Fedora 22 alpha is before the door. So it is time to open the Supplemental Wallpaper Contest. We will use again Nuancier Fedoras application fr the submission and the voting. There are also this time some changes, there is now a team of mentors, who look over the submissions and make suggestions how it can be improved. The submission phase is this time much much shorter, you have only until 19th of March to make your submission.

There are some rules of technical nature:

  • Submitted wallpapers must use a format that can be read by software available in Fedora Package Collection. Preferred image formats include SVG and PNG.
  • Master files, which may be further edited, should be maintained in non-lossy formats. Preserving vector graphics, raster layers, and channels is important for such materials.
  • Originals for landscape formats must be a minimum of 1600 pixels wide and 1200 pixels high. The larger the better. Photographic submissions should be made at the highest resolution the camera is capable of.
  • Submitted wallpapers should be provided in a 16 x 9 aspect ratio when possible.
  • No watermarks, signatures, photographer/creator names, or messages may be included in any part of the work. However if the license allows, and the photo is compelling enough, we could remove watermarks.

and some of organizational nature:

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

To get inspiration, you can always look on former submissions, that are my personal favorites from the last contest:

The deadline until you can submit your artwork is the March 19 2015 at 23:59 UTC. The voting will open automatically after this deadline and as many said the period for the voting shall be longer it will be this time open until 25th of March

For the badges hunters, yes there will be badges for it. There will be a badge for submissions, it will be awarded after the examination of the picture if it fits the rules, which you can see above. Another one will be awarded if your submission is chosen and also for the voting process there will be one. So successful submission makes 2 badges ;) For further questions, you can send me a mail and don’t hesitate to ask me for assistance just write me a mail gnokii@fedoraproject.org.

February 11, 2015

Kdenlive video formats export

A few years ago I used to regularly publish videos, so back then I started with an evaluation of FOSS video editors available for Fedora. At the time I decided the "winner" to be Kdenlive (at the time PiTiVi was useless, OpenShot unavailable and Blender unknown for its video editing capabilities), despite all the drawbacks of its KDE interface and sudden crashes.

Fast-forward, about a year ago, I needed again some video editing, this time for a home project. Not wanting to deal with KDE again (I don't want to flame KDE, I just find a GTK2 interface more friendly to use and GTK apps integrate better in my desktop), I tried OpenShot and it worked good enough.

Fast-forward again to current times, after upgrading my desktop to Fedora 21 (from F18, no less!) I needed again a video editing task, I fired-up OpenShot but it refused to cooperate (something related to creating a video clip from a sequence of images, something I used it for before), so back to the old friend Kdenlive again.

Yes, Kdenlive can do the work just fine, it just had an unintuitive UI annoyance that had me searching the web to learn where to find a simple option (I was not seeing a tree for the forest). You open the render window and there are not many formats to pick from besides MP4, MPEG-2 and Matroska. Where are the others? Not gone, but hidden behind a "Destination" drop-down.

kdenlive video formats export

I can see why they decided to split the list in smaller sections, it can be quite long, however 1: I didn't see the drop-down and surely many others don't and 2: categories are totally arbitrary: MKV is a file, AVI a media player and WebM a website? Why? Fortunately, you can add them as Favorites or learn their place quite fast (unfortunately,after you close the app and open it again, it will default again to File rendering instead of Favorites)

kdenlive video formats export

Some other issue that made me lose a lot of time is related to video quality. At first I created a video with the default format, which is MP4 with H.264, which from what I tried later is the thest regarding file size / image quality (didn't try WebM, it isn't useful for my client here, who is the type of person using Internet Explorer on Windows 8, so it has to work OOTB). Then I tried to find a set of settings for MPEG2 or AVI/XVid close to it. No luck! By trial and error (which means rendering the video again and again) I settled for one while the file size is not that large (only ~2.5X time larger) and image quality not absolutely horrible (note: my personal projects always default to WebM).

kdenlive video formats export

February 10, 2015

Back 2 work

It’s some time now that I was in Westford for the Design Team FAD, it was great and we achieved a lot during this weekend. We came down to 17 open  tickets for the Design Team and discussed how we will work in the future.  The only thing what wasnt that nice is the flying time, I was really jetlagged after the return and additionally I fetched a nice cold which brought me down for more then a week. So I was a little bit down for nearly 3 weeks, but now I am back but I have so many mails to read and answer that it will be my work for the next 3 days.

Next station will be the Chemnitzer Linux-Tage, where I will have together with Robert Scheck an talk. Next to that I have to arrange the Linuxwochen in Vienna, which have also started their CfP. So if somebody wants to help me on the booth…. and there is also some work to do for Fossography in November. So a lot of work waits for me.

February 06, 2015

Corebird 0.9 Now available in Fedora 21

Corebird 0.9 was released a few months ago, and it is now finally available in the official Fedora repos. Check out my previous post for details on some of the new features in this update.

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

 

 

February 03, 2015

Inkscape Development builds for Fedora have moved

Now that Inkscape 0.91 is now released, I have done a bit of housecleaning and moved the Inkscape Development builds for Fedora into a new COPR called inkscape-devel.

The version numbers for these builds are a little different from what I have done in the past, and now are more in line with the upstream way of naming these builds. The development versions now have a version number of 0.91+devel. This may mean that you have to remove older versions of devel builds from the older repos I did before using these repos.

 

January 30, 2015

New version of Inkscape available

So excited that the new version of Inkscape is now finally out! I have been using development versions of Inkscape 0.91 for over a year now, and it is packed full of useful new features and improvements.

The updated package for Fedora should be hitting the repos soon, but the builds are available in koji if you can’t wait and want to install directly from there. I also did a writeup about the release for Fedora Magazine outlining some of the features that I use on a daily basis in Inkscape 0.91.

 

 

GNOME Builder Robot

This is a little render I recently did of the GNOME Builder robot by Jimmac using the Blender Freestyle renderer.

Inkscape 0.91 built and ready for testing in Fedora 21

Earlier this week, the Inkscape upstream made the final tarballs available for the long-awaited new 0.91 version of Inkscape. This version has not been announced by upstream yet, but thanks to the awesome Fedora Inkscape package maintainer Limb, this version is now available for testing on Fedora 21. Please try it out, and give karma to the package in Bodhi.

This updated package is the next major release of Inkscape after the 0.49 version of Inkscape that was released several years ago.

This major update provides many additional features and enhancements as well as hundreds of bug fixes and stability improvements. A detailed list of the new features in this version of Inkscape is available in the upstream release notes

Some of the notable new features in Inscape 0.91 include:

  • A new measurement tool that allows the artist to measure distances and angles in their drawing in realtime.
  • Updates to the text tool including the ability to customise the unit of measurement for text size, and support for choosing font style variants in the text toolbar.
  • The align and distribute dialog now features a new set of features that allow the user to exchange position of selected objects.
  • A new “Select Same” that allows an artist to select objects that have the same properties as the currently selected object. For example, you could select an object that has a fill of blue. Then, using the new feature select all other objects in the drawing with a fill set to that same shade of blue.
  • A new path effect, Power Stroke that allows you to easily create variable width strokes.
  • The Gradient view in the fill and stroke dialog now displays a list of all the gradients in the document. The list displays the gradient, the gradient name, and number of uses of that gradient in the document.
  • The new greyscale display mode that shows a preview of your drawing in greyscale.
  • Improved rendering performance with the new Cairo-based renderer, and the addition of multi-threaded rendering of SVG filters
  • A new feature in the node tool (targeted at type designers) that allows you to insert new nodes at the selected segments extreme values.
Corebird 0.9 now in Fedora for testing

Version 0.9 of Corebird is now in the updates-testing repo for Fedora 21 and Rawhide.

Please check it out, test and give karma!

This update makes this already awesome twitter client much better, with a bunch of updates, including:

  • Mentions, hashtags and links now get highlighted directly in the dialog where tweets are composed.
  • The avatar icon in the top left of the main Corebird window is now clickable. When clicked, every account configured in Corebird is displayed in a list, allowing a quicker way of switching accounts.
  • The dark theme setting in the Corebird user preferences is now removed. If you previously set the dark theme, it will continue to work, but is not really a supported feature of corebird, so the theme may render strangely. It is also still possible to turn the dark theme on or off using the GNOME dconf editor.
  • The arrow keys on the keyboard can now be used to navigate between images if a tweet has multiple images or videos attached.
  • Avatars in tweets and profiles now show if the user is a Twitter verified account.
  • Corebird now has a back button in the main window to easily navigate between panes.
  • Many tweaks to the user interface, including better spacing of elements in the user interface, and updated icons.

January 29, 2015

Event report: Design FAD, Westford

We had a fantastic Design team FAD between 16-18 January at Red Hat’s Westford office. For me, it turned out to be an opportunity to (finally!) meet in person with my mentor Emily, and Mo, two people I’ve been in touch with over IRC/email like forever. Among others physically present were Marie, Sirko, Suchakra, Chris, Prima, Zach, Samuel, Langdon, Paul, Luya and Ryan. Kushal showed up remotely albeit the odd hours in India.

Mo on the whiteboard

Mo did a great job outlining topics we needed to discuss on the whiteboard the first day. At first it looked like a lot to me and honestly I felt like we’d never get to half of them. At the end of the day, to my (pleasant) surprise, we had covered most, if not all of the planned topics. We spent quality time evaluating what the team’s goals are and prioritizing them. We revised our ticket flow into a more structured and well-defined one. We discussed newbie management and how to deal with design assets.

Random discussions

Suchakra, Zach and I worked on redesigning askfedora. What was supposed to be a low-fidelity mockup winded up being pretty hi-fi, since I wanted to take Inkscape lessons from Suchakra and we dug into the details. Suchakra has blogged twice about it, so if you’d like to learn more, find the first one here and the second here.

Askfedora mockup - photo courtesy Suchakra's blog

If we manage to squeeze in time, we’d like to work on the redesign in the weekends. Another group focused on cleaning tickets, so as you’d imagine, lots of trac emails getting tossed around. When I had a look at the design trac after they were done, it seemed like another trac altogether!

Ticket discussions

GlitterGallery was also brought up. What I took back for the GG team from the FAD was that our main priorities are improving the file history view and SparkleShare integration. On my return, I’ve already started work on a new branch.

Quick GG status demo

Emily and I intended to do a GG hackfest once everyone leaves on the final day, but we had transportation issues and couldn’t continue. To make up for that, we held an IRC meeting yesterday to assign tasks to Paul, Emily, Shubham (new kid on the block), and I. I’m excited about how the repo is active again!

Productive FAD for everyone :) Thanks to the local organizers and Gnokii, super worthwhile.

(Gnokii, sorry I sucked at gaming!)

Gnokii playing Champions of Regnum

(Photos courtesy Prima).

January 26, 2015

gimp-paint-studio addon soon on Gnome Software Center
Image speaks itself. gimp-paint-studio package just got an metainfo needed for Gnome Software Center as add-on for Gimp based on related Richard Hughes' blog. The updated package will be shortly available in Rawhide and also in Fedora 21 updates-testing repository. It will not be included for Fedora 20 due  to the preview release of Gnome Software lacking addons support. Next step will be contacting upstream adding that metainfo.  Hopefully other add-ons maintainers for applications such as Inkscape and Blender will do the same to bring a richful experiences to users.

January 25, 2015

Event report: IIT Madras Hackfest & Release Party

This year started for me with a 3 nights Hackfest workshop at Indian Institute of Technology, Madras. While the workshop strayed completely off my goals, the post event commentary seems to indicate that attendees had a good time.

Students were screened for attending based on a general-FOSS questionnaire, followed by their submissions to a set of programming tests set by the mentors. I mentored on behalf of the Fedora Project. Other mentors included Anoop & Kunal (Drupal), Kunal (Wikimedia Foundation) and Nalin (iBus Sharda Project).

Mentors group photo

I began to worry because almost everyone showed up with Windows machines initially, and I had planned intensive exercises with no time allocated for setting up a Linux distribution. However, it wouldn’t have made a lot of sense to dive into programming activity when students were new to the idea of a distribution, command line and installing packages. Which is why I decided to dedicate a whole lot of time explaining all of those things with patience; from my experience, I’ve always had folks quit eventually once they get back home because they couldn’t set up their development environment. At least I got to distribute some fresh Fedora 21 DVDs that way ;)

Kids happy with their DVDs

Half of first night was spent explaining software philosophy, what it means for a project to be FOSS, what it means to be part of a community - that kind of thing, after which I had students install packages required for the rest of the event. I followed it up by an extensive workshop on Git. Most of them picked it up rather well. I would have gone ahead further with explaining colloboration over GitHub and the general workflow, but they seemed too sleepy for another hour of devspeak. 5am!

By this time, I realized that goals I had set weren’t going to be met, so I made a change in plan. Originally, I had thought I’d introduce them to Python and Flask while I pick it up myself (since that’s the stack used in most of Fedora’s infra projects), but this was a complete newbie crowd. I stuck with what I’m comfortable with. After spending time collaborating over GitHub on some projects we started, I had the students pick up Ruby the second night. I explained the concept of programming libraries, how they’re organized and shared, and how they’re hackable. A ruby library I once wrote would solve one of their screening process problems, I showed them how. The second day got me wondering what it’d have been like to have had a mentor help me when I got started, because I remember installing and understanding RVM/Ruby the first time took me two weeks (these kids had it set in minutes). It wasn’t until for GlitterGallery that I tried it again!

Whiteboard Musings

On the way from the airport to the Uni, I thought I’d showcase Shonku, but for the same reasons as I stuck with Ruby, I chose Jekyll. I was a little furious when I learned I’d even have to explain what a blog is, but given that everyone had a Jekyll blog running in a couple of hours, complete with some theme-hacks, I’d guess it was worthwhile.

Happy about the productive second night, I spent the following afternoon arranging cake for the release party. I was dissapointed at most of the major Chennai cake shops not having colors other than pink and green, I definitely didn’t want a Fedora Cake with the wrong colors! As a result, I had to overshoot the requested budget few dollars but I landed a nice one from Cakewalk, complete with a photoprint. Samosas and juice was courtesy IITM.

Cake!

Last night was Release Party and final night. All of us mentors got together in the larger lab to talk about things that were common across any community. I explained students what IRC is, had them lurk around our channels for a bit (and make a complete mess!), and showed them what it means to write proper emails to a mailing list (no top posting, etc). I did a brief introduction to Fedora.next and what it means to the community.

Speaking about Fedora.next

We had an exchange of thoughts, people shared their experiences getting to know about Free Software projects, and the overall atmosphere was pleasant. Our Fedora group left to our meeting room, where I had everyone create a FAS account, showed them around some of our wikipages, and provided them with tips on getting involved better. Finally, in a hope to get them started with Rails, I started talking about designing databases, how APIs talk to each other, and how web apps are structured in general. Well, we did end up cloning GG and setting it up, but I can’t tell how much of that they really understood ;)

All, in all, good fun.

Students: friendly group photo

(Thanks to Abhishek Ahuja for the great photos).

January 19, 2015

Mist wallpapers reloaded
A while ago, a set of misty wallpapers proved to be quite appreciated. Fast forward a year and some more, after another misty morning, here's a new set of free pictures ready to be used as walllpapers.
mist wallpaper
mist wallpaper
mist wallpaper
mist wallpaper
mist wallpaper
mist wallpaper
mist wallpaper

January 17, 2015

Fedora Activity Day Design Team - Day 1
A quick summary of the events. I met some Mofamiliar and new faces behind their IRC nickname including gnokii which is strong sense of humour and pro-active. The process was about reorganizing the Design Team by priority of the project. Mo covered the brainstorming where the rough task is pictured on https://luya.fedorapeople.org/fad-2015/
The complete edited version will follow soon.

January 14, 2015

Fedora Design Team FAD this weekend!

Design Team FAD Logo

Starting this Friday through the weekend, we’re having the very first Fedora Design Team FAD here at Red Hat’s Boston-area office. A number of design team members are going to come together for two and a half days and plan the basic roadmap for the design team over the next year or two, as well as more hands-on tasks that could involve cleaning out our ticket queue and maybe even working on wallpaper ideas for Fedora 22. :)

Join Us Virtually!

We want to allow remote participants (yes, even you :) ) to join us, so we will have an OpenTokRTC video stream as well as a Google On Air Hangout for each day of the event. We will also be in #fedora-design on irc.freenode.net, and we’ll have a shared notepad on piratepad.

Video Stream Links

OpenTokRTC

OpenTokRTC is an open source project for webrtc video conferencing; opentokrtc.com is the demo site set up by TokBox, the project’s sponsor. If you have issues with this feed, please jump to the appropriate Google Hangout.

Google Hangouts

Google Hangouts are unfortunately not open source, but we have set these up as “On Air” hangouts so you do not need to be logged into Google to view them nor should you need to install Google’s plugin to view them.

Other Resources

Chat + Notes
  • #fedora-design on irc.freenode.net – this is the official chat channel for the event.
  • Design FAD piratepad – we’ll take notes as the event progresses here; for example, as we make decisions we’ll track them here.

What are We Working on, When?

We’ll flesh out the fine details of the schedule during the first hour or so of the event; I will try to update the session titles on FedoCal to reflect that as we hash it out. (Likely, it will be documented on the piratepad first.)

Schedule
  • Schedule on FedoCal (note that FedoCal has built-in timezone conversion so you can view in your local timezone :) )

 

See you there! :)

November 24, 2014

OpenMovieNight Phnom Penh

On friday evening I had another OpenMovieNight, this time in Phnom Penh again at Development Innovations. It turned out as a good event we had around 40 participants and after an short talk about copyright, creative commons licenses, open source and free software, we had a lot of fun with the 33 movies I had chosen for the show.

As some already asked in IRC here is the complete list of movies I presented:

November 21, 2014

Inkscape Workshop Phnom Penh

I had yesterday the opportunity to give an Inkscape workshop at Development Innovations Cambodia in Phnom Penh. The participatns was only from several NGO’s, so called multiplicators and it turned out great. One day isnt that much time, to learn enough about Inkscape to use it in a professional way, but you can get at least the foundations to use it and learn more by yourself. But we had a lot of fun together and there was really some talented people amongst the 23 participants and the best two of them had already Fedora stickers on their laptop, so Open Source community in Cambodia begins to grow.

November 20, 2014

Workshop at Smallworld

I am still in Cambodia and after FAD I had on monday and tuesday an workshop about open source graphic tools at Smallworld Cambodia. It was great as always I like being there, its a nice place and its really nice to see how this young people organize to get an better education. The workshop was really good and there was really talented people amongst the particiants. I even managed to help one to install an Fedora on his laptop. The only thing bad was, that my tuesday morning started not so nice with being fetched in the elevator but I was still on time at the place.

So Fedora found again more friends in Cambodia, it might need time to get them to contributors but I have hope for it. At least they start using more and more free software and thats a good thing.

Shooting yourself in the foot, part 53326: Mozilla
Step 1: with bad design decisions one after another (Australis is a shining example of that) slide yourself into irrelevance;
Step 2: when market share goes below some threshold, the main sponsor diminishes (or suspend?) payments;
Step 3: in retaliation, hurt the users by forcing om them a sub-par alternative as a default;
Step 4: profit bleed even more angry users and go even faster into irrelevance.

Brilliant strategy Mozilla!

Myself, I am still using Firefox for the time being, but that's exclusively due to Gecko.

November 17, 2014

Fedora comes to University - Coimbatore Contribution Camp Report

At my University in Coimbatore, we run a tech{know}logy club, where we try to talk about interesting things in technology that normally isn’t covered in the classroom. We had a set of freshers join our club in August through the induction program. On Software Freedom Day in September, they were introduced to the idea of FOSS, open source communities and how it’s possible to contribute to them. When I went to Hanoi for our Ambassadors meeting, I decided to host a contribution camp in Uni sometime this year. Here’s the wikipage which has all the essential bits.

Background week

My friend Manjush and awesome (fresher) junior Sachin did a great job gathering a bunch of interested freshers and other students in our digital library for a half week before the camp took place. On the first day, they helped with installing Fedora (and other distributions of choice) onto the participants’ computers. They spent another day explaining what packages are and helping install the important ones. I showed up for the last two days and helped with Git and Jekyll.

Day One - Thursday

All of us agreed that the best way to motivate folks towards the camp was to screen a movie at our Auditorium. We were expecting 70, but were delighted to be able to host 180 students for Internet’s Own Boy: The Story of Aaron Swartz .

Movie Screening Poster, courtesy Anirudh Menon

For those initiated to the world of Free Software, the Startup Community, and DRM oriented arguments, the movie was a reminder of Swartz and the role he played in shaping part of our world. For the rest, they got to hear about terminologies, ideas and people they could later go and Google. Overall, the silence in the hall towards the end of the movie touched me. We invited everyone to join us for Day Two, and many did.

Day Two - Friday

We wanted to be less theoretic, so we structured our sessions that way. We expected 40 people, 45 showed up. I think if not for Google Club’s mindless discussion about landing jobs by marketing Google products, we would have had a larger attendance. Abhishek Ahuja started the day, speaking about FOSS in general - what it is, why bother, how it affects him. He followed it up with FOSS alternatives to popular software.

Ahuja talking about an interesting GIMP plugin he once discovered Sachin went next, he provided a rather neat introduction to the popular GNU/Linux distributions and the history/community behind them. One interesting thing he did was talk about desktop environments - something people get to hear about often but don’t really understand. From what I could understand, the audience was confusing distributions and desktop environments.

Sachin presenting various desktop environments

I’m actually quite proud of those who attended - the sessions were held after class because we didn’t have much choice, and it’s tiring for freshers who have to wake up early for Yoga classes and walk all the way to our session hall. I didn’t want them to sit and listen to us in hunger, so I arranged for snacks with the money I had asked Tuan to allocate for this event. Anyway, after a quick break, we were back to the sessions.

I’ve seen Manjush try the most distributions, so we had him speak about his timeline of the various GNU/Linux distributions he tried. At least to me who’s spent enough time doing tech support for my peers with respect to installing distributions, it was an entertaining talk. He spoke about problems with installation, problems with lack of language support, problems with community, problems with bundled software, problems with licenses and every other kind of problem one can think of. I was proud when he said he eventually settled on Fedora since it gave him everything he wanted.

Manjush talking about his difficulties with distributions he previously used

I did the last session: Fedora A-Z Guide (partially due to time constraints). Now our University provides us with some hurdles: fresher’s don’t get to use laptops, lab usage is fairly restricted, and girls can’t hang out past 7.30pm (after which anything we want to do happens). So I tried to pick up the non-technical bunch of areas, or areas with less technical intensity, while making sure they have the opportunity to participate over their smartphone. I explained how Wikipedia is everyone’s encyclopaedia, and how they can host their own. Through this, I tried to excite them about the power of a collaborative community, and how they can start contributing with whatever existing skill they have. Some students seem to have gone back home and edited few Wikipedia pages as well :)

Yours truly running through the A-Z guide

Day Three - Monday

Come final day and we had a new set of faces. The attendance was 40. The demand seemed to be the Fedora A-Z guide, so I went over it once more, this time talking about fewer topics, but with more depth. For example, I showed them the badges project, traced a badge to the trac and showed them how the badges are designed and how they evolve. That seems to have gotten them pretty amused, because I met at least 3 people who said they’d like to contribute to badges.

Next up, I went over the hands-on bits from my FOSS 101 workshop at FOSSASIA Phnom Penh and SFD Hanoi. We had a brief look at Fedora and Mozilla’s contribute pages, OpenHatch and CodeTriage. I explained how we communicate - mailing lists, blogs, issue pages, IRC. I explained ettiquettes to follow when one is interacting with a community. It looked like a lot of people related with the usage of SMS lingo and hyper-exclamations (sigh, teens) - I got to see a lot of giggling and smiling around.

Good Procrastination and Bad Procrastination

After the usual snack break, it was time for my final presentation. When I asked a faculty for feedback on Day Two, he felt we were getting a little too technical for the freshers, and that we should do a funny/inspiring session. So I did one called “Good Nervous and Bad Nervous”, and it pretty much rocked :) I brought up lots of experiences from my personal life, what I learned from little things my friends in the Fedora and FOSS community taught me through their words and actions. I look forward to polish it and do the talk again sometime, or maybe even blog it.

So.. that’s the most of our camp, and we’re meeting again this evening to help people with any problems they have in getting started. I’ll be running a survey for the attendees later this week, and if the results seem interesting, I’ll share it.

Closing Notes & Thanks

  1. Although I’m excited about the enthusiasm everyone displayed, I wish the overall technical aptitude of the attendees was higher. I have another semester left here, I’ll try my best to fix that.
  2. I’ve started a reimbursement request on the apac trac (#161) for the food - I’ll upload bills and supply reports today.
  3. I’ve run out of swag now, so I need to figure out something before my Fedora Project workshops at IIT Madras in early Jan
  4. Thanks to: Manjush who kickstarted the sessions, the week prior to the camp. Sachin, our wizard first year who helped out pretty much everywhere. Proud of you! The University, for not making the permission process too much of a hassle to me. Everyone who attended, spoke or blogged.

November 12, 2014

Developments with Fedora Join Landing

If you went to Flock 2014 or attended it remotely, you’d remember I did a talk called Curious Case of Fedora Freshmen. One of the concerns raised in the session revolved around our current Join pages. Here’s the contribute wikipage, the first thing you’d land if you ran a Google search for Fedora Contribute. Then there’s the Join Page, which directs you to various sections within the Join wikipage. For the most of us who’re already involved with the project, these resources may seem as good enough guidelines for a newcomer to be on boarded, making efforts towards a new Join experience seem superfluous.

Over the course of the last year or so, I ended up participating in several meetups in my University, geared at getting people on boarded into FOSS communities. Out of curiousity, I’ve spent time researching how the first steps for several other communities are. Here’s Mozilla’s, my current favorite. Here’s Drupal’s. Here’s Wikimedia’s.

Our Join process could use some improvement. Inspired by some of the links I pointed out earlier, Gnokii’s slides on contributing to Fedora as a non-programmer, and my own experiences dealing with juniors in college and interested folks I meet at conferences, I’ve decided to go ahead and work on building a new boarding point for people who’d like to contribute to the Fedora Project. To start with, I have a couple of mockups for such a website, viewed on mobile. I also managed to find two enthusiastic students, who I’m mentoring with the development process. We had a super quick meeting the other day to spark things.

First Page Second Page

I wanted this post to serve as a notifier to the community, so in case you have any ideas/suggestions, feel free to add them into the comments section! :) I’ll try to keep sharing updates as the project progresses.

November 02, 2014

Big Week Cambodia

This November will be a busy month for me, I will fly to Cambodia again and bring some Fedora energy there. Its my second visit to this country and I look forward to it. I will have an talk at Royal University of Phnom Penh. RUPP is using Fedora for teaching there students basic skills for Linux. But as always, its teached more about technical stuff as what Linux or Fedora really is, projects driven by volunteers. RUPP gives me the great opportunity to speak to all there IT students about how they can contribute to Fedora and learn even more by doing so. But I will do some other things more.

  • On 14th of November I will join the Fedora Release Party Phnom Penh and help Somvannda Kong and Nisa Ban by giving an talk at this event. Truong Anh Tuan is giving another one. So it looks there will be an interesting program with talks and fun. Yes, Fedora 21 will not be released that day, but Beta will be available at least and we can show the features of the upcoming version.
  • On 15th of November I will help in the morning Somvannda in preparing the packaging workshop, which will be done that day remotely by Robert Scheck. So we will help the attendees to install all the necessary software for the workshop so that Robert can start without being enforced to take care of that.
  • The rest of November 15th and 16th I will join the FAD APAC, where the activities for the next year will be planned.
  • 17th and 18th of November I will deliver a 3 days workshop at Smallworld Cambodia, about doing Graphics with Free Software tools.
  • 20th of November I will be back at Development Innovations for delivering an Inkscape workshop to attendees from several NGO’s
  • 21st of November I doing an Open Movie Night at the same place, talking about free software and free culture and of course showing some examples what can be done with free software.
  • 22nd and 23rd of November I will do another Join Fedora workshop, as I did in February at Open Institute Phnom Penh. I hope that during all my presentations at RUPP, Release Party and so on, get enough people interested to start working for Fedora. In the workshop we will do all the  things together that are necessary to become a Fedora contributor.

Besides that activities I will have some meetings with friends and partners to organize some stuff in the future.

October 24, 2014

Winners of Wiki Loves Romania 2014

Organizing Wiki Loves Monuments in Romania this year was the hardest so far. Why so? We had a bigger budget, which allowed us to be more ambitious, so on top of the free photography contest for Wikipedia we had to manage a photo exhibition, a 2 day field trip, an additional contest for juniors, a team of volunteering interns and more. But it was rewarding, the results are notable: over 8200 pictures from 216 contributors.

I will tease with the top 3 photos from the contest, you can see all of them on our website.

1st place: Bogdan Croitoru with Monumentul triumfal Tropaeum Traiani
006 MG 6430 Tropaeum Traiani Adamclisi 006
2nd place: Dragoș Pîrvulescu with Fortificație medievală
Cetatea Râșnov, văzută din șoseaua Cristian-Râșnov.
3rd place: Zsolt Deak pentru Ansamblul bisericii evanghelice fortificat-vedere aeriana
Ansamblul bisericii evanghelice fortificat-vedere aeriana

You can also see the winning pictures, along with highlights from the previous editions and winners of the section dedicated to younger contributors in a photo exhibition opened for 3 weeks at the National Library in Bucharest. After that, the expo will move for a couple more weeks at Universitatea de Vest in Timișoara.

expo

October 08, 2014

Software Freedom Day Hanoi: Fedora Report

I was in Hanoi last month to participate in the APAC ambassadors meeting, as well as the Software Freedom Day event. This post summarizes notes from the trip.

APAC Ambassadors Meeting

On the first day, we had a meeting set up, to go through the current year’s budget, and discuss concerns with our respective countries. Tuan, Thang, Alick, Somvannda and yours truly were physically present. Gnokii, Kushal and Ankur participated for significant portions of time, remotely over IRC.

Fedora Folks posing at the SFD banner Photo: Unknown

We started with a general discussion about the APAC situation. Some (not sic) moments:

Tuan:

We have a lack of physical meetups among APAC folks.

Tuan was my roomate in Prague (at Flock), and we had a brief discussion about this. For most APAC meetings, at least until a few weeks ago, there would be very few representatives from Asian countries. When the budget was to be made for the current FY, Tuan announced over the mailing lists, but nobody showed up.

We discussed how this situation is improving. In November this year, a FAD is planned where folks have been invited to help with the budget planning. The recent meetings have run over an hour and we regularly have irregular meetings these days ;) While that is indeed trouble, it indicates interest, which is a good thing.

Kushal:

We should stop people from treating Fedora as a travel agency.

For context, here’s a blogpost around the same concern. Many Indians just want to become ambassadors, because they think that warrants them funds to travel. It’s of course great if people have been contributing in volumes and want funds to travel and speak about it - in fact, that’s encouraged. But in the recent times, Kushal says he receives mentorship requests, where the person doesn’t want to go through the mentoring process and wants to gain ambassador status directly. Kushal quoted examples and how the mentors team in India dealt with it.

Us hard at work Photo: Somvannda

Next, we worked on the most important bit: the budget. Alick volunteered to review and update Q2 and I helped with Q1. Alick got lucky since most events planned in Q2 were cancelled and there wasn’t much to review. Thang helped me cross-check events, swag requests and travel tickets from Q1.

After a lunch break, we turned to discuss Ambassador Polos and FAD Phnom Penh. I had been working on cleaning up the entire APAC trac for two weeks, but was unable to complete it because people hardly respond. Finally, at the meeting, with help from everyone present, the APAC trac is now Sparkly!

Software Freedom Day at the Uni

This was my second SFD, first being the one I helped organize in school. The way this one was organized was definitely more colorful - it started off with a Tux dance!

Alick had some swag flown over from China, so we used them up at our booth - it disappeared quickly, even before we had a chance to grab some of the folks and do some Fedora preaching. Nonetheless, it was super fun. I think we managed to direct some of the students to our Fedora room for the afternoon sessions. With the swag all gone and not much agenda for the rest of the morning, we headed to the main hall.

Sponsors being felicitated Photo: Alick

I’m going to have to quote the following line from Alick’s report:

Alick:

Sarup, Somvannda, and I are honored to be introduced as special international guests to the event (in English).

It was funny (although exciting) to attend the first few talks in the regional language. Well, we even attended the “How to contribute to Fedora without programming skills” keynote by Tuan in Vietnamese ;)

Come afternoon, we moved to our Fedora room. While Trang and I went around gathering folks to attend our sessions, Thang introduced the attendees to the Fedora Project - who we are, what we do, our goals, and why bother. He did his session in Vietnamese, and the attendees were visibly glued.

Next was Alick’s session on FOSS Software Defined Radio. I think he did a great job introducing the topic - it was a topic unfamiliar to me, but now I get the basics. I liked his idea of motivating through examples.

Finally, I did my mini workshop on FOSS 101. Prior to the event, we had a little debate around what I should talk about - GSoC? Git? Rails? From my understanding of the audience, I decided to do a diluted version of my FOSSASIA workshop. I introduced attendees to the idea of FOSS, put up quotes sent to me by Sumanah and Tatica (who I’ve always felt are great examples of our awesome lady FOSS activists) and showed them around IRC & the idea of mailing lists. I wrapped up with a basic introduction to Git (for which I should thank Alick for his help with the demos and Trang for the translation).

Arrangements

Day 0 was 18 September 2014. I was put up at the Hanoi Legacy Hotel near the Hoan Kiem lake. My roomate was Alick, who arrived later in the evening. Somvannda was at the hotel a day in prior. Tuan and Thang being the locals, were our awesome hosts. For dinner on all but the last day, we had street food near the hotel. On the last day, we had dinner with the VFOSSA folks, other organizers and volunteers.

The meeting was held on the first day, 19 September, at the VAIP office. The SFD event was held on the second day, 20 September at Hanoi University of Engineering and Technology.

Fun Memories

As you would guess, we had fun along the way! On Day 0, Somvannda and I went around Hanoi’s streets hunting for Egg Coffee.

For dinner, Tuan and Thang took the rest of us to a nearby food joint, where we tried out some rather interesting Vietnamese food. I (kinda) picked up how to use a chopstick too.

Newly acquired chopstick skills Photo: Me

On Day 1, after the meeting was over, we headed to the Water Puppet Theater - a unique concept. For dinner, we roamed the street for local food, followed by a brief trip to the Night Market in the Hanoi Old Quarter. I wish we could have revisited the place on the final day as well, but we couldn’t as the events ended late.

On the final day, we were joined by the awesome (hopefully significant future contributors) Trang and Phuong. Trang made us try “Corn in Fish Sauce” and we wrapped up with the usual beer :-)

It was definitely a weekend well spent and I’d like to thank everyone for the fun and productive time!

October 03, 2014

Software Freedom Day Hanoi: Fedora Report

I was in Hanoi last month to participate in the APAC ambassadors meeting, as well as the Software Freedom Day event. This post summarizes notes from the trip.

APAC Ambassadors Meeting

On the first day, we had a meeting set up, to go through the current year’s budget, and discuss concerns with our respective countries. Tuan, Thang, Alick, Somvannda and yours truly were physically present. Gnokii, Kushal and Ankur participated for significant portions of time, remotely over IRC.

Fedora Folks posing at the SFD banner Photo: Unknown

We started with a general discussion about the APAC situation. Some (not sic) moments:

Tuan:

We have a lack of physical meetups among APAC folks.

Tuan was my roomate in Prague (at Flock), and we had a brief discussion about this. For most APAC meetings, at least until a few weeks ago, there would be very few representatives from Asian countries. When the budget was to be made for the current FY, Tuan announced over the mailing lists, but nobody showed up.

We discussed how this situation is improving. In November this year, a FAD is planned where folks have been invited to help with the budget planning. The recent meetings have run over an hour and we regularly have irregular meetings these days ;) While that is indeed trouble, it indicates interest, which is a good thing.

Kushal:

We should stop people from treating Fedora as a travel agency.

For context, here’s a blogpost around the same concern. Many Indians just want to become ambassadors, because they think that warrants them funds to travel. It’s of course great if people have been contributing in volumes and want funds to travel and speak about it - in fact, that’s encouraged. But in the recent times, Kushal says he receives mentorship requests, where the person doesn’t want to go through the mentoring process and wants to gain ambassador status directly. Kushal quoted examples and how the mentors team in India dealt with it.

Us hard at work Photo: Somvannda

Next, we worked on the most important bit: the budget. Alick volunteered to review and update Q2 and I helped with Q1. Alick got lucky since most events planned in Q2 were cancelled and there wasn’t much to review. Thang helped me cross-check events, swag requests and travel tickets from Q1.

After a lunch break, we turned to discuss Ambassador Polos and FAD Phnom Penh. I had been working on cleaning up the entire APAC trac for two weeks, but was unable to complete it because people hardly respond. Finally, at the meeting, with help from everyone present, the APAC trac is now Sparkly!

Software Freedom Day at the Uni

This was my second SFD, first being the one I helped organize in school. The way this one was organized was definitely more colorful - it started off with a Tux dance!

Alick had some swag flown over from China, so we used them up at our booth - it disappeared quickly, even before we had a chance to grab some of the folks and do some Fedora preaching. Nonetheless, it was super fun. I think we managed to direct some of the students to our Fedora room for the afternoon sessions. With the swag all gone and not much agenda for the rest of the morning, we headed to the main hall.

Sponsors being felicitated Photo: Alick

I’m going to have to quote the following line from Alick’s report:

Alick:

Sarup, Somvannda, and I are honored to be introduced as special international guests to the event (in English).

It was funny (although exciting) to attend the first few talks in the regional language. Well, we even attended the “How to contribute to Fedora without programming skills” keynote by Tuan in Vietnamese ;)

Come afternoon, we moved to our Fedora room. While Trang and I went around gathering folks to attend our sessions, Thang introduced the attendees to the Fedora Project - who we are, what we do, our goals, and why bother. He did his session in Vietnamese, and the attendees were visibly glued.

Next was Alick’s session on FOSS Software Defined Radio. I think he did a great job introducing the topic - it was a topic unfamiliar to me, but now I get the basics. I liked his idea of motivating through examples.

Finally, I did my mini workshop on FOSS 101. Prior to the event, we had a little debate around what I should talk about - GSoC? Git? Rails? From my understanding of the audience, I decided to do a diluted version of my FOSSASIA workshop. I introduced attendees to the idea of FOSS, put up quotes sent to me by Sumanah and Tatica (who I’ve always felt are great examples of our awesome lady FOSS activists) and showed them around IRC & the idea of mailing lists. I wrapped up with a basic introduction to Git (for which I should thank Alick for his help with the demos and Trang for the translation).

Arrangements

Day 0 was 18 September 2014. I was put up at the Hanoi Legacy Hotel near the Hoan Kiem lake. My roomate was Alick, who arrived later in the evening. Somvannda was at the hotel a day in prior. Tuan and Thang being the locals, were our awesome hosts. For dinner on all but the last day, we had street food near the hotel. On the last day, we had dinner with the VFOSSA folks, other organizers and volunteers.

The meeting was held on the first day, 19 September, at the VAIP office. The SFD event was held on the second day, 20 September at Hanoi University of Engineering and Technology.

Fun Memories

As you would guess, we had fun along the way! On Day 0, Somvannda and I went around Hanoi’s streets hunting for Egg Coffee.

For dinner, Tuan and Thang took the rest of us to a nearby food joint, where we tried out some rather interesting Vietnamese food. I (kinda) picked up how to use a chopstick too.

Newly acquired chopstick skills Photo: Me

On Day 1, after the meeting was over, we headed to the Water Puppet Theater - a unique concept. For dinner, we roamed the street for local food, followed by a brief trip to the Night Market in the Hanoi Old Quarter. I wish we could have revisited the place on the final day as well, but we couldn’t as the events ended late.

On the final day, we were joined by the awesome (hopefully significant future contributors) Trang and Phuong. Trang made us try “Corn in Fish Sauce” and we wrapped up with the usual beer :-)

It was definitely a weekend well spent and I’d like to thank everyone for the fun and productive time!

October 01, 2014

Inkscape: Donde cada elemento es una capa

¿Te has preguntado en que se diferencia Inkscape de GIMP? Una de las principales razones por las cuales Inkscape es más utilizada para elaborar publicidad, es porque trata a cada elemento como una capa individual, esto permite que al elaborar un arte central, puedas simplemente reorganizar los elementos que lo componen para realizar un nuevo diseño, por lo tienes que olvídate de borrar y parchar nada.

En Gimp, si dibujamos varias figuras y no colocamos cada una en una capa, cuando queramos separarlas, no podremos, ya que todos los componentes que hicimos forman parte de una misma capa, en cambio, si realizamos las mismas figuras en inkscape, la diferencia es que podremos separarlas y trabajar con ellas como elementos individuales ya que cada una de ellas se comporta como una capa.

Por ejemplo, el diseño de esta web fue hecho con inkscape, así que dale un vistazo, deja tu comentario y no olvides suscribirte a mi canal de youtube y a este portal para seguir aprendiendo de forma fácil y rápida!

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

Y si te gusta mi contenido, no te olvides de votar por este blog como Mejor Blog de Software Libre, solo dale click al botón amarillo que dice “Votar” y confirma tu email! :D

Flattr this!

September 25, 2014

Donde encontrar increibles Fotos Gratuitas

Uno de los retos mas grandes cuando nos toca realizar un website o una publicidad en general es encontrar fotografías geniales a un buen costo (o gratis dependiendo del cliente), y no es que sea malo pagar por fotografías, pero a veces el cliente es pequeño y pues el presupuesto no alcanza. En la red hay miles de servicios que proveen fotografías de alta calidad por un costo de suscripción mensual, por paquete o por fotografía, pero hay un mundo de sitios que ofrecen fotografías de forma gratuita bajo una licencia amigable para esas necesidades que tanto tenemos como diseñadores. Veamos algunos de mis favoritos:

dttsf

Death to Stock Photo es un servicio al cual te suscribes dejando tu email en su website, y mensualmente envía sets de 10 fotografías ambientadas usualmente en el tema del mes, con una calidad increíble y una variedad super útil. Cada vez que recibes un correo de ellos te emocionas solo al ver el titulo porque sabes que una explosión de creatividad ha llegado a tu correo.

pixabay

Pixabay es un excelente sitio donde el orden de sus etiquetas y categorías son la clave para encontrar lo que quieras, cuando quieras. No requiere registrarse y su interfaz es muy parecida a la de 500px, por lo que encontrar y descargar contenido es pan comido.

nos

New Old Stock es una colección de fotografías públicas antiguas que están libres de todo tipo de restricción de derechos de autor. Es muy a lo tumblr y es algo difícil ubicar fotos por categorías o etiquetas, sin embargo, la cantidad de fotografías referenciales a artículos y momentos históricos que tiene es simplemente hermosa.

littlevisuals

Little Visuals sigue el estilo de Death to StockPhoto pero cada 7 días. Tiene fotos hermosas bajo dominio público pero lo bueno es que en su web, tienen a disposición todo el histórico de packs, por lo que si te perdiste uno o apenas te estás uniendo, puedes revisar los packs anteriores y bajar lo que necesites.

picjumbo

PicJumbo es un sitio que disfruta de una variedad abismal de contenido, además de tener un excelente plugin para tu browser que te avisa cuando hay contenido nuevo. Se agregan fotos nuevas diariamente, así que nunca te quedarás sin contenido fresco para tus necesidades.

Y recuerda que las votaciones para Mejor Blog de SoftwareLibre aún están abiertas, vota si aún no lo has hecho!!!

Flattr this!

September 24, 2014

DevAssistant Heuristic Review Part 2: Inventory of Issues

This is Part 2 of a 3-part blog series; this post builds on materials featured in an earlier post called DevAssistant Heuristic Review Part 1: Use Case Walkthroughs.

In this part of the DevAssistant heuristic review, we’ll walk through an itemized list of the issues uncovered by the use case-based walkthrough we did in part 1.

Since this is essentially just a list of issues, let me preface it by explaining how I came up with this list. Basically, I combed through the walkthrough and noted any issues that were encountered and mentioned in it, large and small. The result of this was a flat list of issues. Next, I went through the list and tried to determine a set of categories to organize them under by grouping together issues that seemed related. (You could do this in a group setting via a technique called “affinity mapping” – another fancy UX term that in essence just basically means writing everything out on post-its and sticking related post-it notes together. Fancy name for playing with sticky pieces of paper :) )

Breaking the issues into categories serves a few purposes:

  • It makes the list easier to read through and understand, since related issues are adjacent to each other.
  • It breaks up the list so you can review it in chunks – if you’re only interested in a certain area of the UI, for example, you can hone in on just the items relevant to you.
  • It tends to expose weak areas in great need of attention – e.g., if you have 5 categories and one of them is attached to a particular screen and the other 4 are more generic, you know that one screen needs attention (and should probably be a high priority for redesign.)

All right, so here is the list!

Base UI Design

These issues apply not to specific dialogs or screens, but more to the basic mechanics of the UI and the mental model it creates for users.

  1. Takes time to get situated: When I first look at this UI, I’m not sure where to get started. Because the first tab says “Create Project” and the second says “Modify Project,” I get the impression that you might progress through the tabs in order from left-to-right. From poking around, though, this doesn’t appear to be the case. So at initial glance, it’s hard for me to understand the overall flow or direction I’m meant to go in through the interface.
  2. Projects created/imported feel very disconnected from DevAssistant: It feels like there is no follow-up once you create or import a project via DevAssistant. I expected to be able to browse a list of the projects I’d imported/created using DevAssistant after doing so, but there doesn’t appear to be any link to them. DevAssistant seems to forget about them or not recognize them afterwards. Sure, they live on the file system, but they may live in all different places, and I may need some reminders / instruction about how to work with them – the filesystem doesn’t provide any context on that front.
  3. Little user guidance after project creation / import: After the user creates a project, all they really get is a green “Done” notification on the setup wizard window. I think there’s a lost opportunity here to guide the user through everything you set up for them so they know how to take advantage of it. Maybe have a little guide (easily dismissed or optional) that walks the user through the options they selected? For example, if they chose the vim option, have a section that activates on the post-project creation screen that talks about how DevAssistant customizes vim and how they can make use of it in their workflow. Basically, nudge the users towards what they need to do next! Offer to open up Eclipse or vim for them? Offer to open up the project in their file manager? Etc. etc.

Clarity / Context

These are issues where the UI isn’t clear about what information it needs or what is happening or why the user would pick a specific option. The cop-out fix for these types of issues is to write a lot of documentation; the right way to fix them is to redesign! If an option is confusing to explain and benefits all users, just turn it on by default if it’s not harmful instead of putting the burden of selecting it on the user. If the pros/cons of a config option aren’t clear, explain them – add some contextual documentation right into the app via tool tips or more clear text in the UI.

  1. Tab names unclear: The names of the tabs across the top don’t give me a good idea of what I can actually do. What does “prepare environment” mean? Looking at the interface, I think that going through one of the wizards under “Create Project,” would prepare an environment for the selected type of project, so why would I click on “Prepare Environment?”
  2. Prepare Environment options confusing: When I look at the options under “Prepare Environment,” I see “Custom Project” (what does this mean vs. the “Custom Task” tab?) and “DevAssistant.” These options don’t help me understand what “Prepare Environment” means. :-/
  3. DevAssistant button under Prepare Environment confusing: Why would I want to set up the environment for DevAssistant and checkout sources? Is the “Dev Assistant” button under “Prepare Environment” meant specifically for developers who work on DevAssistant itself?
  4. Some options could use more explanation / optimization: Some of the options in the dialogs could use more explanation but they don’t have any tooltips or anything. For example, why would I choose Python 2 vs. Python 3 when creating a new project? What are the pros/cons? How do I take advantange of the customizations offered for vim so I can determine if they’re worth setting up? (Or why wouldn’t I want to set them up? If it doesn’t take up much disk space and it’s a good value add why not just do it if I have a vimrc?)
  5. Not sure what “deps only” means: This could be my ignorance not being a real developer, but most if not all of the config dialogs I ran into had a ‘Deps-Only’ option and it’s still unclear to me what that actually means. I get depenencies in the context of yum/RPM, and I get them in the context of specific stacks, but I’m not sure how DevAssistant would generically determine them? Also, what happens if I don’t check off ‘Only install dependencies’ and check off everything else? Do the dependencies get installed or not? If I check off ‘Only install dependencies’ and also check off everything else, does that mean none of the other things I checked off happen because I checked off ‘Only install dependencies?’ The grammar of the string makes it ambiguous and the option itself could use some wordsmithing to be a bit clearer.
  6. What happens if you choose an option that requires something not installed? It’s not clear to me what happens if you pick vim or Eclipse, for example, in one of the options dialogs on a system that does not have them installed. Does it project setup fail, or does it pull in those apps? Maybe DevAssistant could check what development environments it supports that you already have installed and gray out the ones you don’t have installed, with a way to select them while explicitly choosing to install the development environment as well?
  7. Users need appropriate context for the information you’re asking them: There were a few cases, particularly related to connecting to github accounts, where the user is asked for their name and email address. It isn’t clear why this information is being asked for, and how it’s going to be used. For example, when you ask for my name, are you looking for my full name (Máirín Duffy,) just my first name (Máirín,) or my nick (mizmo?) (And can you support fadas? Or should I type “Mairin” instead of “Máirín”?)

Human Factors

This is a bucket for issues that put unnecessary burden / inconvenience on the user. A good example of this in web application design is a 3 levels deep javascript tiered dropdown menu that disappears if you mouse off of it. :) It makes the user physically have to take action or go through more steps than necessary to complete a task.

  1. Hover help text not easily discovered / pain to access: After a while of poking around, I notice that there are nice explanations of what each button under each tab means in a hover. My initial thought – putting this valuable information under a hover makes it more challenging to access, especially since you can only read the description for one item at a time. (This makes it hard to compare items when you’re trying to figure out which one is the right one for you.)
    Hover tips for create project buttons.

    Hover tips for create project buttons.

  2. Window Jumps – This happens when clicking on buttons in the main setup wizard window and new windows are launched. For example, go to “Modify Project” tab. Click on Eclipse Import or Vim Setup. It moves the DevAssistant up and to the right. Click back. The window remains up and to the right. Why did it move the window? It should remember where the user placed the window and stay there I think.
  3. Project directory creation defaults to user’s homedir: I think a lot of users try to keep their home directory neat and orderly – defaulting to creating / importing projects to users’ home directories seems the wrong approach. One thing to try would be to make a devassistant directory during the first run of the application, and defaulting to creating and importing projects to there. Another option, which could be done in conjunction with defaulting to a ~/devassistant directory, could be to ask the user during first run or have a configuration item somewhere so that the user can set their preferred repository directory in one place, rather than every time they create/import a project.
  4. No way to create new project directory in file chooser for project directory selection: In a lot of the specific project creation dialogs, there’s an option to specify a project directory other than the user’s home. However, the file chooser that pops up when you click on “Browse” doesn’t allow you to create a new directory. This makes it more of a hassle (you have to go outside the DevAssistant application) to create a fresh directory to store your projects in.
  5. Holy modal dialogs, Batman! I encountered a few modal dialogs during the process that made interactions with the application a bit awkward. Some examples:
    • There was a very large Java error dialog that was hidden under another window on my desktop, and it made buttons on the main progress/setup window unclickable so I couldn’t dismiss the main window without dismissing the Java error window. (And the Java error window didn’t have any button, not even an ‘X’ in the upper right corner, to dismiss it.) (See Use Case 2 for more details on this specific scenario.)
      This was too long to display fully on my 2560x1440 monitor... the button to close it wasn't accessible. Luckily I know how to Alt+F4.

      This was too long to display fully on my 2560×1440 monitor… the button to close it wasn’t accessible. Luckily I know how to Alt+F4.

    • During the Django setup process (Use Case 1) and during the C project use case (Use Case 2), there was a small modal dialog that popped up a little after the setup process began, asking for permission to install 20 RPM packages. It halted the progress being made – similar to how old Anaconda would pop up little dialogs during the install process. It’s better to ask questions like this up-front.
    • Another time during the Django setup process (Use Case 1), there was a tiny modal dialog that aligned to the upper left corner of the screen. I completely missed it, and this halted the project creation process. (It was a dialog asking for my name, related to Github account connection.)
      http://blog.linuxgrrl.com/wp-content/uploads/2014/08/Screenshot-from-2014-08-30-215454-1024×576.png
  6. If the user fills something out incorrectly, it’s not possible to recover in some cases. This is just another vote to ask users needed information up front and avoiding modal dialogs – I filled out the wrong email address in one of the pop up modals during the project creation process and realized too late I used the wrong email address.
  7. Git name / email address very sticky and not easily fixed: During Use Case 1, I was prompted for my name and didn’t realize it was the name that would be attached to my git commits. Once it’s input though, there’s no way to update it. It’s unclear where it’s stored – I blew away the project I was creating when I input it, thinking it was stored in the .git/config file, but DevAssistant still remembered it. Configuration items like this that apply to all projects should be editable within the UI if they can be input in the UI.
  8. Text fields for inputting long paths are unnecessarily short: This is pointed out specifically in Use Case 2, but I think all the setup dialogs were affected by it. The text dialog for putting the path to your project in, for example, was only long enough in my case for “/home/duffy/Repo” to be visible. The field should be longer than that by default.

Status / Transactional

These are issues that revolve around the current status of the task the user is trying to complete. An example of a common issue related to this in UIs in general is lack of progress bars for long-running tasks.

  1. When main window is waiting on user input, it should be made clear: During the Django setup process in Use Case 1, I had opted to use Github for the new project I was creating. After filling out the config screen and pressing ‘Run,’ it looked like the project creation process was going to be a while so I multi-tasked and worked on something else. I checked on the main window a few times – at a certain point, it said “In progress” but it wasn’t actually doing anything – a tiny little window popped up in the upper-left corner, halting the whole process. It would have been better to ask me for that information up front, as to not halt the process. But it also would have been good, if the main window is waiting on something, for it to let the user know it’s waiting and isn’t “In progress.” (Maybe it could say, “Paused, waiting on user input?”)

  2. Ask users all of the information you need up front, so they can walk away from the computer while you set things up: Speaking of that last point – this was an issue we had in the old Anaconda, too. During the installation process, sometimes error messages or dialogs would pop up during the install process and they would halt install progress. So the user may have gone to get a coffee, come back, and everything wasn’t done because anaconda sat there a lot of the time asking if it was okay to import some GPG key. When you have a long-running process (a git repo sync, for example,) I think it’s better to ask the user for everything you need up front rather than as the application needs it. It’s akin to someone coming up to your desk to ask a question, going away for a couple of minutes, then tapping you on the shoulder and asking you another question, then coming back 3 minutes later to ask another one – people like that are annoying, right?! (Well, small children get away with this though, being as cute as they are. :) )
  3. Transaction status unclear after errors or even after completion: When I canceled the Django project creation in Use Case 1 because I input the wrong email address, I wasn’t sure of the state of the project and how to proceed cleanly. What directories had been created on my system? What packages had been installed? Etc. I would have liked to clean up if possible, but it wasn’t clear to me what had happened and it didn’t seem like there was an easy way to undo it. Ideally, after hitting cancel, the application would have explained to me something about the state of the system and recommended a forward course of action (is it better to blow everything away and start over? Or re-run the command using the same parameters?)
  4. Little/Vague progress indication: There’s a yellow “in progress” string on the wizard screen after you hit run, and the cursor goes into spinner mode if you focus on that dialog, but there could be better progress indication. A spinner built into the window (here’s an example) is a good option if it’s not possible to do a progress bar. Progress bars are a little better in that they give the user an indication of how much time it might take to complete.

Layout / Aesthetics

These are issues around the actual layout, typography, padding, arrangement of widgets, widget choices in a given screen or dialog. They tend to be surface issues, and usually it’s a better use of time to rethink and redesign a dialog completely rather than fix these kinds of issues only on the surface (which could be akin to putting a different shade of lipstick on.)

  1. Package install confirmation dialog layout issues: So this is pretty surface-level critique – but there’s a few issues with the layout of the dialog asking the user if it’s okay to install packages via Yum. Here’s what it looks like initially:

    Usually the button that moves you forward is the farthest to the right, and the cancel is to the left. Here, the ‘Show packages’ button is on the right. I think maybe, ‘show packages’ should not be on the same line as ‘Ok’ and ‘Cancel,’ but instead maybe it should be a link above the buttons that expands into the full list (limited to a specific max vertical height of course, as to not make the buttons disappear so they are not clickable!) The list itself, has numbers, ‘1’ and ‘2’ before some of the package names – it’s unclear to me why they are there. Also, the list is very long but there’s no way to filter or search through it, so that might be a nice thing to offer. What are people concerned about when evaluating a list of packages to be installed on their system? The number of packages and total size might be useful – the size isn’t listed so that could be a good piece of information to add. I could go on and on about this dialog, but hopefully this demonstrates that the dialog could use some more iteration.
  2. Layout of options via linear checkbox list can cause confusion about relationship between options: In several cases during the walkthrough, I became unsure of how to fill out the setup wizard for various project types because I wasn’t sure how the different checkbox options would work. In one case, it seemed as if particular selections of checkboxes could never result in success (e.g., in use case 4 when I tried to create a custom project with only the ‘deps only’ checkbox selected.) In other cases, some of the options seemed to be vaguely related to each other (Eclipse or vim) and others seemed less related (github vs python 3 or 2.) I think probably each screen needs to be reviewed and potentially rearranged a bit to better represent the dependencies between the checkboxes, base requirements, etc. For example, categorizing the options – put Eclipse and VIM under a “Development Environment” category, put git / github / etc. options under a “Version Control” category, etc.

Feature Set

These issues are around the features that are available (whether or not they are appropriate / useful or accessible / placed correctly) as well as features that might be needed that are missing.

  1. No way to import pre-existing project that wasn’t created with DevAssistant? This one seems like a bit of a show stopper. I tried to import a project that wasn’t created using DevAssistant (which is the majority of upstream projects at this point,) and it didn’t work. It bailed out after detecting there’s no .devassistant in the repo. If there is a way to do this, it’s not clear to me having gone through the UI. It would be nice if it could import an existing project and create a .devassistant for it and help manage it.
  2. The button to create a github project is under the ‘Modify Project’ tab, not the ‘Create Project’ tab: This is a bit of an oddity – the create project tab is more focused on languages / frameworks… creating a new project in GitHub is definitely creating a new project though, so it doesn’t make sense for it to be under “Modify Project.”

Bugs

These are just outright bugs that don’t have so much to do with the UI specifically.

  1. Screen went black during root authentication during Django setup: I think this was some kind of bug, and wasn’t necessarily DevAssistant’s fault.
  2. Could not create a Django project on development version of Fedora: My Django project creation failed. The error message I got was “Package python-django-bash-completion-1.6.6-1.fc21.noarch.rpm is not signed. Failed to install dependencies, exiting.” Now, while this is a little unfair to point out since I was using F21 Alpha TC4 – DevAssistant should probably be able to fail more gracefully when the repos are messed up. When errors happen, the best error messages explain what happened and what the user could try to do to move forward. There’s no suggestion here for what to do. I tried both the “Back” and “Main window” buttons. Probably, at the least, it should offer to report the bug for me, and give me explicit suggestions, e.g., “You can click ‘Back’ to try again in case this is a temporary issue, or you may click ‘Main Window’ to work on a different project.” It probably could offer a link to the documentation or maybe some other help places (ask.fedoraproject.org questions tagged DevAssistant maybe?)
  3. Unable to pull from or push to github: During the Use Case 1 walkthrough, I was left with a repo that I couldn’t pull from or push to github. It looks like DevAssistant created a new RSA key, successfully hooked it up to my Github account, but for some reason the system was left in a state that couldn’t interact with github.
  4. C project / Eclipse project creation didn’t work: There was a Java/Eclipse error message pop up and an error with simple_threads.c. Seems like a bug? (Full error log)
  5. Tooltip for Eclipse import talks about running it in the projects directory: This seems like a bug – the string is written specifically for the command line interface. It should be more generic.

Up Next

Next, we’ll talk about some ways to address some of these issues, and hopefully walk through some sketchy mockups. This one might take a bit longer because I haven’t sketched anything out yet. If I’m not able to post Part 3 this week, expect it sometime next week.

DevAssistant Heuristic Review Part 1: Use Case Walkthroughs

You might be asking yourself, “What the heck is a heuristic review?”

It’s just a fancy term; I learned it from reading Jakob Nielsen‘s writings. It’s a simple process of walking through a user interface (or product, or whatever,) and comparing how it works to a set of general principles of good design, AKA ‘heuristics.’

To be honest, the way I do these generally is to walk through the interface and document the experience, giving particular attention to things that jump out to me as ‘not quite right’ (comparing them to the heuristics in my head. :) ) This is maybe more accurately termed an ‘expert evaluation,’ then, but I find that term kind of pompous (I don’t think UX folks are any better than the folks whose software they test,) so ‘heuristic review’ it shall be!

Anyway, Sheldon from the DevAssistant team was interested in what UX issues might pop out to me as I kicked the tires on it. So here’s what we’re going to do:

  • Here in Part 1, I’ll first map out all the various pieces of the UI so we can get a feel for everything that is available. Then, I’ll walk through four use cases for working with the tool, detailing all the issues I run into and various thoughts around the experience.
  • In Part 2, I’ll analyze the walkthrough results and create a categorized master list of all the issues I encountered.
  • In Part 3, I’ll suggest some fixes / redesigns to address the issues catalogued in Part 3.

Okay – ready for this? :) Let’s go!

Setup Wizard Mapping

(This is the initial dialog that appears when you start DevAssistant.)

Screenshot of the initial DevAssistant screen

Screenshot of the initial DevAssistant screen

I’m starting this review of DevAssistant’s GUI by walking through each tab and mapping out a hierarchy of how it is arranged at a high level. This helps me get an overall feel for how the application is laid out.

  • Create Project
    • C
    • C++
    • Java
      • Simple Apache Maven Project
      • Simple Java ServerFaces Projects
    • Node.js
      • Express.JS Web Framework
      • Node.JS application
    • Perl
      • Basic class
      • Dancer
    • PHP
      • Apache, MySQL, and PHP Helper
    • Python
      • Django
      • Flask
      • Lib
      • Python GTK+ 3
    • Ruby
      • Ruby on Rails
  • Modify Project
    • C/C++ projects
      • Adding header
      • Adding library
    • Docker
      • develop
    • Eclipse Import
    • Github
      • Create github repository
    • Vim Setup
  • Prepare Environment
    • Custom Project
    • DevAssistant
  • Custom Task
    • Make Coffee

Use Case Testing

I’m going to come up with some use cases based on what I know about DevAssistant and try to complete them using the UI.

Use Cases for Testing

  1. Create a new website using Django.
  2. Create a new C project, using Eclipse as a code editor.
  3. Import a project I already have on my system that I have cloned from Github, and import it into Eclipse.
  4. Begin working on an upstream project by locally cloning that project and creating a development environment around it.

Use Case 1: Create a new website using Django

I’m not much of a Django expert, so this may end up being hilarious. So I know Django is Python-based, and this is a new project, so I click on the “Create Project” tab, then I click on “Python.” I select “Django” from the little grey menu that pops up. The little grey menu looks a little bit weird and isn’t the type of widget I was expecting, but it works I guess, and I succesfully click on “Django.” Note: the items in the submenu under Python are organized alphabetically.

An example of the little grey menu - this one appears when you click on the Python button. Not all of the buttons have a grey menu.

An example of the little gray menu – this one appears when you click on the Python button. Not all of the buttons have a gray menu.

A new screen pops up, and the old one disappears. I had the old screen (the main DevAssistant window) placed in the lower right of my screen. The new screen that appears (Project: Create Project-> Python -> Django) jumps up and to the right – it’s centered perfectly on my left monitor. It looks like I’m meant to feel that this is a second page to the same window (for example, the way the subitems of GNOME control center work.) Instead, thought, it feels like a separate window because it’s a little bit larger than the first window and it jumped across the screen so dramatically.

Django project setup window

Django project setup window

This new window is a bit overwhleming for me. First it asks for a project name. I like ponies, and Django does too, so I call my project “Ponies.”

Next, it wants to know where to create the project. It suggests /home/duffy, but man is my home pretty messy. I click on “Browse” to pick somewhere else, thinking I might create a “Projects” subdirectory under /home/duffy to keep things nice and clean. There isn’t a way to create a directory in this file chooser, so I drop down to a terminal and create the folder I want, then fill out the field to say, “/home/duffy/Projects” and move on.

Now, it’s time to look through available options. Hm. This is definitely the most overwhelming part of the screen. Looking through the options… two seem to be related to coding environments – there’s a checkbox for eclipse, and there’s a checkbox for vim. There’s an option to use Python3 instead of Python 2. There’s an option to add dockerfile and create a docker image. There’s a virtualenv option, and a deps-only option. I think I understand all of these options except for “Deps-only,” which is labeled, “Only install dependencies.” If I don’t only install dependencies, then what happens? What is the alternative to clicking that box? I’m not sure.

Anyway, back to the editors. I like vim, but this is a fresh desktop spin installation and I know that doesn’t come with vim preinstalled. I wonder what will happen if I pick vim. I decide to do it.

Oh, and there’s a Github option. It will create a GitHub repo and push the sources there. That is pretty slick; I click that checkbox too and provide my github username. Then I click “Run” in the lower right corner. (Note that a lot of new GNOME 3 apps have the button to progress forward in the upper right.)

Next, pops up a screen that has a log that spits out some log style spew, looking like it’s installing some RPMs. Quickly, a modal dialog pops up that says:


Installing 20 RPM packages by Yum. Is this ok?

[ No ] [ Yes ] [ Show packages ]

The modal dialog has the same problem of being centered to the whole desktop rather than centered along where the parent window was. I like that it offers to show me which packages it’s going to install. I click on “Show packages.” I get a very nice scrollable display in the same window, neat and clean. I click “hide packages” to hide the list. Then I click “Yes” to move forward.

Now things got a bit weird. My whole screen went black. A gnome-shell style black dialog is in the center of this black screen and it is asking for my root password. I don’t think the screen behind the dialog should be black. It feels a little weird. (turns out this was a F21 TC4 issue only.) I type in my root password and click to continue.

And it seems the process failed. (To be fair, I am doing this on an alpha test candidate – F21 TC4 – so the issue may be with the repos and not DevAssistant’s fault.) It says:


Resolving RPM dependencies ...
Failed to install dependencies, exiting.

I like the option to copy the error message to the clipboard, and to view and copy to clipboard the debug logs. It errored out because of a packaging issue, it looks like:


Package python-django-bash-completion-1.6.6-1.fc21.noarch.rpm is not signed
1
Failed to install dependencies, exiting.
Failed to install dependencies, exiting.

There is also a “Back” button and a “Main window” button; I’m not sure which to click. I try “Back” first. That brings me back to the screen I filled all the details in for my project; however I know it won’t work now when I click run.

So at this point, I emailed Sheldon to let him know that I ran into some breakage, and he told me that it wasn’t necessary to test on F21 TC4 – what’s in F20 at this point is reasonably recent and worth doing a heuristic review on. So let’s continue from this point, using F20. :)

This time, I pick the same options on the create new Django project screen, and when I press forward, it says it’s installing 21 packages. Okay. It seems to be going, and I realize after wasting precious minutes of life reading crap on Twitter that it has been quite some time. I check back on the DevAssistant window – it looks like it’s still working, but it’s kind of not clear what it’s really doing.

Then I notice the tiny little dialog peering down at me from the extreme upper left corner of my laptop screen (it is easy to find in this screenshot; harder when other windows are open):

Hey, little guy! Whatcha doing up there?

Hey, little guy! Whatcha doing up there?

So this is another window positioning issue. I drag that little guy (who has some padding and alignment issues himself, but nothing earth-shattering) closer to the center of the screen so I can fill him out. The problem is, I’m not really sure of the context – why does it want my name? Does it just want my nickname, my first name, my full name, my IRC handle…? I end up typing ‘mairin’ and hit enter.

This little dialog is centered with the main window, thankfully.

This little dialog is centered with the main window, thankfully.

And then, something clicks. “I bet it wants my name and email address for the git config.” Well, crap. I already typed in “mairin,” and that’s not the name I want on my commits. I hit “Cancel” on the email dialog shown above, and try to “start over” by going back to the main window and creating the “Ponies” project again. But… ugh:

I changed the path from ~/Projects to ~/Code just because.

I changed the path from ~/Projects to ~/Code just because.

So there are a few problems here:

  • The form field for my name lacked enough context for me to understand what information the software really wanted from me.
  • I figured out what the software wanted from me too late – and there isn’t any way for me to go back and fix it via the user interface, as far as I can tell.
  • There’s a transactional issue: in order to completely finish creating the project as I requested, DevAssistant needed some additional information. I bailed out of providing that information, leaving the project in an unknown state. (Will it work, and just miss the features that required information I didn’t provide? Since I bailed out early, which features will be missing? Is there a way to fix it by filling them in afterwards? Should I just delete from the filesystem and start over again?

The latter is what I did – I went into nautilus, nuked my ~/Code/Ponies directory, and ran through the Django project creation process (same options) from the main DevAssistant window one more time.

Unfortunately, it remembered the name I had given it. Normally this is a wonderful thing – interfaces that ask the same question of a user over and over again are annoying. In this instance, however, the politeness of remembering my name was a bit unforgiving – how could I correct my name now? Will all projects I create in the future using DevAssistant have “mairin” as my name instead of the “Máirín Duffy” of my vain desires??

Well, a rose by any other name would smell as sweet – whatever. Let’s carry on. So I am asked my GitHub password after my email address, which I provide, and soon afterwars I am greeted with a completed progress screen, a link to the project I created on GitHub, and a perusable log of everything DevAssistant just did:

That was definitely an easy way to create a project on GitHub.

That was definitely an easy way to create a project on GitHub.

So I think I’m done at this point? Maybe? I’m not 100% clear where to go from here. Some potential issues I’ll note at this point:

  • The project I created on GitHub through this process is completely empty. I was expecting some Django-specific boilerplate content to be present in the repo by default, and maybe some of the files suggested by GitHub (README, LICENSE, .gitignore.) But maybe that part happens later?
  • There’s an ssh issue in the logs. Ah. Now we see why my repo on GitHub is empty:

    Problem pushing source code: ssh_askpass: exec(/usr/libexec/openssh/ssh-askpass): No such file or directory
    Host key verification failed.
    fatal: Could not read from remote repository.

I didn’t see a seahorse dialog pop up asking me to unlock my ssh key. I open up seahorse – it looks like DevAssistant made an RSA key for me. I’m not sure what’s going on here, then. It never asked me for a passphrase to create a new key.

I have an interesting test case in that I have a new laptop that I didn’t copy my real ssh key over to yet. I wonder how this would have gone done if I did have my real ssh key on this system…

Then, I get an email from GitHub:


The following SSH key was added to your account:

DevAssistant
98:a0:c9:9e:aa:44:08:ae:c4:96:a0:f9:1c:96:34:04

If you believe this key was added in error, you can remove the key and disable
access at the following location:

https://github.com/settings/ssh

If the new ssh key was added to my account, then why didn’t this work? :-/

My big question now is: what do I do next? Here is what I have:

  • A new boilerplate Django project in my home directory.
  • An empty GitHub project.
  • Some stuff that got added to vim (how do I use it?)

What I don’t have that I was expecting:

  • Some kind of button or link or something to the boilerplate code that was created locally with some tips / hints / tricks for how to work with it. (Links to tutorials? Open up some of the key files you start working with in that environment in tabs in Geany or Eclipse or some IDE? Okay so I selected vim – tell me how to open this up in vim?)
  • Some acknowledgement of the ‘Ponies’ project I just created in the DevAssistant UI. I feel that my ponies have been forgotten. There isn’t any tab or space in the interface where I can view a list of projects I created using DevAssistant and manage them (e.g., like changing the ssh key or changing my name / email address associated with the project.)

I’m feeling a bit lost. Like when the lady in my GPS is telling me how to get to Manhattan and she stops talking to me somewhere in the Bronx.

Use Case 2: Create a new C project, using Eclipse as a code editor.

Back to the main window in DevAssistant! I click on the “C” button and right away am greeted with the “Create Project -> C” screen, which I dutifully fill out to indicate a desire to use Eclipse and to upload to GitHub:

Screenshot from 2014-08-30 23:14:44

A modal alert dialog ask me if it’s okay to install 139 packages (and again, helpfully offers a list of them if I want it.)

(The alignment within the dialog is a bit off; there’s a lot of extra padding on the bottom and the buttons are a bit high up. The OK button should probably be the right-most one, and a different widget used for ‘show packages,’ (like a disclosure triangle, maybe.)

The dialog that asks for permission to install required dependencies. The alignment within the dialog is a bit off; there's a lot of extra padding on the bottom and the buttons are a bit high up. The OK button should probably be the right-most one, and a different widget used for 'show packages,' (like a disclosure triangle, maybe.)

The dialog that asks for permission to install required dependencies. The alignment within the dialog is a bit off; there’s a lot of extra padding on the bottom and the buttons are a bit high up. The OK button should probably be the right-most one, and a different widget used for ‘show packages,’ (like a disclosure triangle, maybe.)

First, I click to show the list of packages. Now I see why there is so much padding on the bottom of the dialog. :) But it’s not enough space to comfortably skim the list of dependencies:

Selection_101

I drag out the window size to make it a bit bigger to more comfortably view the list. Some package names have a “1:” in front of them, some have “2:” in front of them, some have nothing in the front. I’m not sure why.

Selection_102

Anyway, enough playing around. I agree it’s okay to install the dependencies.

I watch the dialog. 139 packages is a lot of packages. While they are downloaded, there’s no progress bar or animation or anything to let me know that it’s still actively working and not crashed or otherwise unstable. The only indications I have are the cursor getting set to spinner mode when I go to the DevAssistant window, and the text, “Downloading Packages:” at the bottom of the visible log in the DevAssistant window:

Screenshot from 2014-08-30 23:20:00

After a little while, unfortunately, things didn’t go so well:

DevAssistant setup wizard_104

Here’s the full error log.

So now I’m not sure what state I’m left in. The “DevAssistant setup wizard” window has grayed out “Main window” and “Debug logs” buttons – the only live button is “Copy to clipboard.” I click on “x” in the upper right corner and it tries to quit but it doesn’t seem to do anything. Then I notice the large Java error popup window hidden behind my browser window:

This was too long to display fully on my 2560x1440 monitor... the button to close it wasn't accessible. Luckily I know how to Alt+F4.

This was too long to display fully on my 2560×1440 monitor… the button to close it wasn’t accessible. Luckily I know how to Alt+F4.

Once I closed that window, the main DevAssistant wizard window changed, and I was able to get access to the main window and back buttons.

On to the next use case!

Use Case 3: Import a project I already have on my system that I have cloned from Github, and import it into Eclipse

All right, so what project should I import? I’m going to import my selinux-coloring-book repo. :) This is a git repo I created on github and have synced locally. Let’s see if I can import it and open it in eclipse.

So I go back to the main DevAssistant setup wizard window and I click on the ‘Modify Project’ tab along the top (is this the right one to use? I’m not sure):

The "Modify Project" tab

The “Modify Project” tab

I’m not sure whether I should do “Eclipse Import” or “Github.” If I hover over the Github button, it says:

Subassistants of Github assistant provide various ways to work with Github repos. Available subassistants: Create Github repository.

While the first sentence of the description makes this seem like the right choice, the last sentence gives me the sense that the only thing this button can do is create a new github repo since that seems to be the only available subassistant (whatever a subassistant is.)

The Eclipse Import hover message is:

This assistant can import already created project into Eclipse. Just run it in the projects directory.

This seems like what I want, except the last line has me confused. I’m running a UI, so why is it telling to me to run something in a directory? (I’m assuming this is maybe a shared help text with a command-line client, so it wasn’t written with the GUI in mind?) Anyway, I’m going to go with the “Eclipse Import” button.

Again, the main DevAssistant window disappears and a new window pops up, ignoring my window placement of the first window and centering itself on top of my windows in the middle of my active screen. Here’s what that new window looks like:

Window shown after the Eclipse Import process is started.

Window shown after the Eclipse Import process is started.

So I notice a few issues on this screen (although note some of them may be because I’m not a real developer and I haven’t used Eclipse in years):

  • There are two text fields where the user can specify a path on the file system. While such paths are usually pretty long, the fields aren’t wide enough to show much beyond the portion of my path that points to my home directory – /home/duffy. So these fields should probably be wider, given the length of these kinds of paths.
  • I’m not sure what Deps-Only is going to do – what kind of project is it assuming I have? Is it going to somehow detect the dependencies (from make files?) and install them without importing the project? Why would I want to do that?
  • The options are listed out with checkboxes – and you can click them all at once. Does that make sense to do? I guess it does – I could specify the Eclipse workspace directory (although is that in ~/workspace or $PROJECT-PATH/eclipse?), and the path to the project, and that I only want deps-only. It seems like maybe ‘deps-only’ is an option that is subject to path though – if I don’t specify a path, how is it going to detect deps?
  • In fact, the process fails completely if I only select the “Deps-Only” checkbox and nothing else. So this selection shouldn’t be possible.

I end up just specifying my path (which points to /home/duffy/Repositories/selinux-coloring-book,) checking nothing else off, and clicking “run.” This doesn’t work – I get a blank “Log from current process” window that says “Failed” on the bottom:

DevAssistant setup wizard_110

On a whim, I check to make sure Eclipse is installed – yeah it is. That’s not the issue. I go back and check of the “Eclipse” checkbox in addition to the “Path” checkbox – looks like the failed C project creation made a ~/workspace directory, so I use that one. I hit run again…

DevAssistant setup wizard_110

I’m not sure where to go from here, so I’ll move on to the next use case.

Use Case 4: Begin working on an upstream project by locally cloning that project and creating a development environment around it

What upstream project should I work on? Let’s try something I don’t already have synced locally that isn’t too huge. I’ll choose fedora-tagger.

Okay back to the main DevAssistant window:

Screenshot of the initial DevAssistant screen

Screenshot of the initial DevAssistant screen

Where do I start? Not “Create Project,” because that’s for a new project. I look under “Prepare Environment:”

Prepare environment tab

Prepare environment tab

I’m not going to be working on DevAssistant or OpenStack, so I examine the hover text for “Custom Project:”

Only use this with projects whose upstream you trust, since the project can specify arbitrary custom commands that will run on your machine. The custom assistant sets up environment for developing custom project previously created with DevAssistant.

Hm. So two things here:

  • This won’t work, because fedora-tagger wasn’t created with DevAssistant.
  • I don’t think I would trust any project with this option, unless I could at least examine the commands it specified to run before running them. It would be nice to have a way to do that. Looking at the dialog linked to this button, it doesn’t look like there is.

Okay, so now what will I do? It doesn’t seem like there is a way to complete this use case under “Prepare Environment” unless my upstream is OpenStack or DevAssistant. The “Custom Task” tab won’t work, because the only option there is “Make Coffee.” So I’ll try to “Modify Project” tab:

The "Modify Project" tab

The “Modify Project” tab

Even though I know from an earlier use case that the hover text for the “Github” button seems to indicate that it can only create new Github projects, I try it. Nope, it just lets you create a new project. Hm. Well fedora-tagger is a python project. There’s a C/C++ projects button – maybe I should pick a C project instead.

So I’ll try a C project. What is written in C? I know a lot of GNOME stuff is written in C; I’m sure I could find something there. So I look at the tooltip on the C/C++ projects button:

This assistant will help you ito [sic] modify your C/C++ projects already created by devassistant. Avalaible [sic] subassistants: Adding header, Adding library

Well, I don’t know any GNOME C projects that were created with DevAssistant. :-/ At this point, I’m not sure how to move forward. I click on the “Get help…” link in the upper right:

Problem loading page - Mozilla Firefox_122

It looks like doc.devassistant.org doesn’t work at all. Nor does devassistant.org …. it must be down. It’s still up on readthedocs.org though… okay let’s see:

Preparing: Custom – checkout a custom previously created project from SCM (git only so far) and install needed dependencies

This seems to be what I need? But the button for “Custom Project” said that the project should have been created with DevAssistant. Let’s try it anyway. :) I’ll use gnome-hello, which is a small C demo project.

First screen for "Custom Project"

First screen for “Custom Project”

A couple things on this screen:

  • All of the items are checkboxes, except for URL which has a red asterisk (‘*’) – why? Is that one required? Then it should probably have a checked and grayed checkbox?
  • Again, the text fields for typically long path strings are pretty narrow.

I paste in the gnome-hello git url (git://git.gnome.org/gnome-hello) and hit “Run.”

Custom Project completion dialog.

Custom Project completion dialog.

Hmm, okay. So it didn’t find a .devassistant and bailed out. What did it do on my filesystem?

Project directory created by Custom Project wizard

Project directory created by Custom Project wizard

I would have preferred it not dump the git repo in my home dir – but I suppose that the path was an option I could have specified on the screen before. It might be better for me to be able to specify that I keep my git repos in ~/Repositories… so by default DevAssistant uses that so I don’t have to input it every time.

I don’t think there’s anything else I can do here, so I’ll finish here.

On to analysis!

In Part 2, we’ll go through the walkthrough and pull out all of the issues encountered, then sort them into different categories. Look for that post soon. :)

Como hacer videos para Instagram usando Kdenlive + Instashot

Te has preguntado como hago mis videos de Instagram? Trabajar con Kdenlive es muy fácil y una de las cosas que mas me gusta es que puedes arrastrar cualquier video, imagen o audio y automáticamente se cargará en la aplicación. Hacer un video en Kdenlive es como armar un rompecabezas, solo debes arrastrar las piezas que ya cargaste y ordenarlas. Puedes separar las pistas, cortarlas, agregarles efectos y mucho más. Poco a poco iré explicando como trabajar mas detalladamente con Kdenlive, pero primero, quiero que vean la potencialidad de esta aplicación y se enamoren de ella como yo lo he hecho.

Una vez exportado nuestro video mp4 lo copiaremos a nuestro teléfono, abriremos instashot y selecionaremos video. Navegaremos hasta encontrar nuestro video y lo cargaremos a la aplicación. En este punto verás una serie de opciones en la parte inferior, seleccionaremos Fit de ajustar, y si queremos que el video sea cuadrado como instagram, seleccionaremos Full. Puedes probar las otras opciones si te da curiosidad. Cuando estés feliz con el encuadre, pulsa el visto bueno a la derecha y en la parte superior encontrarás el enlace directo para cargarlo a instagram. Tarda un poco ya que le baja la calidad, al menos ese fue mi caso y eso te dará la opción de publicar de una vez.

Y así es como realizo los videos que me gusta compartir con ustedes en instagram y que ultimamente “creo” que los han hecho reir un monton. Recuerden que sus dudas se convierten en podcast, así que no sean timidos y dejen un comentario… ahh…. y si les gusta mi contenido, no olviden ir a portal programas y votar por tatica.org como mejor Blog de SoftwareLibre, su voto significa mucho para mi!

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

Flattr this!