It has been so long since I went to my last Fedora conference that to be honest, I was overwhelm. Having so many friends around who actually understand my love for open source and communities, was something that I needed. After 4 countries, I finally arrived to this lovely city that mesmerize me in every way. Budapest has become my favorite city in the world and I will take with me all my life everything that happened during FLOCK… I can literally say that my life changed here. I will try to make a resume of what happened at Flock, so please fetch yourself a drink and lets start.

Diversity and Inclusion: Expanding the concept and reaching ALL the community.

Timing not always seems perfect, but sometimes things work just as they should at the end. When I was named Diversity & Inclusion Advisory I didn’t knew that life would get in the middle and would ended up actually helping people after a bit more than 3 years. I’m glad I was able to catch up with this team who has been doing a fantastic job. I’ve been contributing with amazing people for years, and finally meeting my team, Amita, Justin, Jona and Bee, was like a dream come true.

Probably the best from FLOCK was to being able to record several members from our community who kindly accepted to say their names, the places where they come from and the language they speak, and create a small video showing how Diverse and Inclusive Fedora is. Produce a short 2min video in such a chaotic schedule is challenging enough, so after 3 hours of recording, and a rough 2:30hs of editing, I ended up finishing the render of the video just as I was plugin my laptop to the main stage… People usually don’t know how long it takes to do something like that, but I’m just glad everyone seemed to like it and that my laptop didn’t died in the process.

While working on the video, I was able to have small interviews with several folks from Fedora and got to ask them how comfortable they felt in the community. It was satisfactory to learn from them that the overall care we have take to make minorities feel more included has worked, however, it was a bit sad to learn how hard has been for our contributors to deal with burn out, how tired they are of putting fires out instead doing new projects and mainly getting a general sense of getting stuck into the same routine.

As our team says, our labor is not only to help with the diversity efforts for making everyone feel comfortable, but we also need to work more to include more effective ways to give people a sense of purpose, provide new challenges that put them on a fun path and give them the recognition they deserve. Fedora has always put a lot of effort into bringing new people to contribute, but I’ve seen that the old contributors are getting on a side because “everything is working” and we need to take care of that. They need the same attention (and I would dare to say that probably more) than new contributors do. At the end, is this amazing group of people who has to mentor new contributors. Feel free to reach me or any member of the Diversity and Inclusion Team if you feel that this words got your attention and you’re willing to share some thoughts. Anonymity is a top priority.

Marketing: You won't sell what you don't show.

I like to think that conferences like this have 3 parts: Friends, Knowledge and Memories. Meeting your old friends face to face or making new friends is what motivate us to enjoy this conferences. Knowledge is spread and connections between people from same and different projects are made allowing new ideas to flow… but Memories are what keep people motivated and active during the months or years before meeting again. In a world full of cameras and social networks, we sometimes forget that best moments are captured while people is concentrated in the first two items. If you want to get the real face of conferences you need to document it while people is not seeing, when people is making friends and sharing knowledge.

It was quite satisfactory to see the reaction of people at the Helia Conference Room once they saw the Flock resume video. Being able to show them how fun the last 4 days were, was a key point to conclude a fantastic experience. Filling the Social Networks with good quality pictures increased the attention into our community, and more people was willing to share their content so everyone could see the things we were doing. Having quality content is key to spread what we do. Having quality writers and proper localization will help us reach more fantastic people that will help us grow.

Lets never forget the importance of Memories. At the end, these are the ones we can look back and the best way to remind us why we contribute in projects like this. It’s not just the contributions we make, but also the connections we make.

Design: If it's not broken... build it from the scratch!

Who doesn’t like a bit of a challenge? After the “Survey no-Survey” (lets call it -interviews- so we don’t get into Legal) I did notice that there are several services that are working, but could be better. Meeting riecatnor and Tanvi was one of the highlights of FLOCK. Design team has always been a small group, but numbers aren’t exactly growing. Marie’s badges workshop ended up being a fantastic opportunity not just to check and close tickets, but brought a great discussion about how Badges are being used and where should we aim to. Having Renata there to conduct a small usability test with new and old contributors, help us identify some things that could be done better at Badges. We have no idea right now about the specifics, but I think great things will come for the Badges platform. Having friends at different team is probably what makes this community the best… so when pingou heard that we might do some changes to Badges, he and Xavier jumped in… we don’t even have a design or anything for it… but that’s when you realize that “is more fun (and productive) to build from the scratch instead just fixing old bugs”.

I’m trying to figure out if a badges simplification, both as in quantity and quality would be good for the overall behavior of the website, and probably going from pngs to svg’s and having a badge reduction could also make us have a faster website… so If you’re interested on helping us explore this ideas, come to the Badges channel (both irc and freenode) or just ping me wherever you see me.

Serious stuff goes here: Catching up with the new Fedora structure.

I used to knew the Fedora structure like the palm of my hand, but again timing isn’t perfect, and Fedora changed EVERYTHING as soon as I went into my maternity leave… I won’t lie that even if things look better on an organizational level, it has been harder than ever to get around how things work now. One of the hardest things I’ve always seen at Fedora resources is that we are so energetic into explaining how our process work, that we end up with more web pages explaining the same thing than we should. I hope someday this changes and it seems that we are on that path, but there’s still a lot of work to do there.

I wasn’t able to attend the Mindshare meeting since it collided with D&I, however, thx to telegram and an angel who helped me have a voice there, I was able to drop a couple of comments and get some answers. Time to divide the final part into sections:

– LATAM: It was really disappointing to learn that FUDcons stopped while I was on my break. Conferences like this are not just a fantastic opportunity to get things done faster since everyone is at the same place, but also a reward to the effort that our contributors put during a long year into having the community working smoothly. Latin America is a complex region due distances and that’s a fact, but it seemed a decision with no solid -communitary- arguments to just stop. LATAM people is worth the effort, and we will work on making them feel more included. Our diversity is awesome, recognition is needed but also guidance into taking the community to a level where we all feel like doing more.

– Burn out: Most of us who join a community do it for the challenge of doing new things and meeting new people who understands the geeky world we live in. But when you have to do the same thing for a couple of years (or even a decade), getting stuck into repetitive tasks tends to get you exhausted. I thought I was alone on that path, but seems that not. We did empathize on working towards helping our contributors into get new challenges that put them on that creative and joyful path once again, so a refreshment allows them to cope with the routine of supporting a community like Fedora. No easy task, but we can all make a good impact if we look to our sides and try to encourage our fellas.

Final thoughts

If you got here, thank you. Has been a long time since I had the opportunity to see my old friends, catch up with a community I love and learn everything that happened while I was afk being a mom. Sometimes I get the feeling that I’m jumping into things that might be done or already discussed, but if there’s something I’ve learn in so many years, is that new energy (even from old contributors), can shake things enough to make actual improvements.

NOTE: If you see yourself in a picture and want me to remove it or if you want to get a photo I took from you, just send me a message :)

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

A couple of friends were curious about how I did my ghost picture for my recent project. Just in case you have no idea what I’m talking, I started a small photo-project to explore light and shadows and as usual, tell stories… long time I didn’t do it, right?

I tried to record it 2 times with Gnome’s desktop recorder but kept failing (I was an avid user of recordmydesktop), so finally on my 3rd attempt I used SimpleScreenRecorder which ended up being super easy to use, and not lagy at all. Since I got the recording on the 3rd time, this is not the picture I posted (probably better after so much damn practice, but who cares), so if you see differences between both, now you know the reason.

Here’s the TimeLapse video of the edit because I doubt you want to see 39mins of me cleaning sky and fabrics with a mouse, however, since I know people might get bored, below the video you will find a list of some of the parameters I used for the full edit.

After selecting the images that would help me archive the final output I started the editing. I used darktable for the pre-processing and get the main black/white images. For most images I used pretty much the same modules (a few adjusts here and there to exposure since was working with 100% natural light):

  • Monochrome Module: Just because I like to have a base sample of the monochrome version.
  • Filmic
    • Middle Gray Luminance: 9.13%
    • White Relative Exposure: 2.81 EV
    • Black Relative Exposure: -7.98 EV
    • Contrast: 1.574
    • Shadows & Highlights: 2.25%
  • Equalizer (Check Video)
  • And a bit of Highpass to help my old camera (Check Video)

Once that was done, copied the style to the rest of the pics and ended up with several images to play.

It’s mostly play with each image until you get the result you want. The GIMP process is hard to explain through steps, but there are a couple of tricks that I think are important to follow while doing this kind of edits:

  • Work with mask layers… If you use just the eraser, you will end up deleting things that you might need later. So use masks, own them… love them…
  • When come to fabric borders, use the curve and fine tune them easily.
  • Merging fabric isn’t easy and takes time. There’s no magic formula.

So for the editing part you will definitely will have to check the video and enjoy the 39min -to- 5min cut :)

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

Si al entrar a la opción de verificar estado de su GitLab y observa el siguiente mensaje: Migrations are pending. To resolve this issue, run: bin/rails db:migrate RAILS_ENV=production, solo debe ejecutar el siguiente comando:

sudo gitlab-rake db:migrate RAILS_ENV=production

Espero que esta información les sea útil, saludos.

A veces es necesario enviar mensaje que aparezcan en la pantalla del equipo en forma de notificación, para esto solo se debe ejecutar el siguiente comando.

msg * /server:x.x.x.x /time:600 Escriba su mensaje aquí.

x.x.x.x corresponde al IP del equipo al cual va a enviar el mensaje. En cambio si desea enviar el mismo mensaje a varios equipos el procedimiento es el siguiente:

  1. Cree un archivo de texto llamado lista.txt que contenga los IP (un IP por linea) de los equipos que recibirán el mensaje.
  2. Cree un archivo de texto llamado mensaje.txt con el siguiente contenido:
FOR /F %%p IN (C:\lista.txt) DO msg * /server:%%p /time:600 Escriba su mensaje aquí.

Cambie la extensión del archivo mensaje.txt a mensaje.bat, luego de esto solo falta ejecutar el script.

Espero que esta información les sea útil, saludos.

TFTP son las siglas de Trivial file transfer Protocol (Protocolo de transferencia de archivos trivial).

Es un protocolo de transferencia muy simple semejante a una versión básica de FTP. TFTP a menudo se utiliza para transferir pequeños archivos entre computadoras en una red, como cuando un terminal X Window o cualquier otro cliente ligero arranca desde un servidor de red.

La instalación del paquete es bastante simple, basta con ejecutar el siguiente comando:

sudo apt-get install tftpd-hpa

El directorio de trabajo por defecto es /var/lib/tftpboot y la configuración se ubica en /etc/default/tftpd-hpa.

Si va a utilizar el servidor solo para descargas no necesita hacer ninguna modificación pero si desea realizar cargas en el servidor debe modificar la configuración de la siguiente forma:

Busque la siguiente linea:


Y modifíquela de la siguiente forma:

TFTP_OPTIONS="--secure --create"

Luego reinicie el servicio con el siguiente comando:

sudo systemctl restart tftpd-hpa

Y listo, adicionalmente para evitar problemas ejecute los siguientes comandos

sudo chown -R tftp:tftp /var/lib/tftpboot
sudo chmod -R 644 /var/lib/tftpboot

Espero que esta información les sea útil, saludos.

Una pregunta muy común entre usuarios de rsync es como evitar la copia de un archivo; para ello solo debemos agregar un parámetro al momento de ejecutar el comando:

rsync -avhn --exclude 'Thumbs.db' origen destino

En este ejemplo excluimos el archivo thumb.db pero puede sustituirse por cualquier archivo.

Espero que esta información les sea útil, saludos…

Este pequeño truco nos permite saber la IP publica de un equipo desde la linea de comandos, solo basta ejecutar el siguiente comando:

dig +short

Una alternativa a dicho comando podría ser la siguiente:

dig TXT +short

Espero que esta información les sea útil, saludos…

Gitlab es un servicio web de control de versiones y desarrollo de software colaborativo basado en Git. Además de gestor de repositorios, el servicio ofrece también alojamiento de wikis y un sistema de seguimiento de errores, todo ello publicado bajo una Licencia de código abierto.

Fue escrito por los programadores ucranianos Dmitriy Zaporozhets y Valery Sizov en el lenguaje de programación Ruby. La compañía, GitLab Inc., cuenta con un equipo de 150 miembros y más de 1400 usuarios. Es usado por organizaciones como la NASA, el CERN, IBM o Sony.

Para reiniciar una instalación de GitLab Omnibus solo debe ejecutar el siguiente comando:

sudo gitlab-ctl restart

Para reiniciar un componente por separado solo debe agregar el nombre del servicio, por ejemplo:

sudo gitlab-ctl restart nginx

Para chequear el estado del servicio solo debe ejecutar lo siguiente:

sudo gitlab-ctl status

Y para aplicar los cambios después de modificar los archivos de configuración solo debe ejecutar lo siguiente:

sudo gitlab-ctl reconfigure

Adicionalmente si usted instalo GitLab a partir de su código fuente solo debe ejecutar el siguiente comando para reiniciarlo:

sudo service gitlab restart

Espero que esta información les sea útil, saludos.