Imagine a team meeting. It is attended by a diverse group: folks of different experience, skills, age, background, culture, work title, and time on the team.
I experienced hundreds of such meetings in my career. These meetings are usually dominated by:
Extroverts
More experienced colleagues (Senior engineers, leads, managers, and higher)
Folks that are on the team for a long time
Top performers
(a single person can match all 4 :)
I’m so happy to write this article. With Packit and
Copr, we are improving the RPM ecosystem
so much that we can work on User Experience (rather Developer Experience) more
and more. Finally \o/
Carefully.
And think about them, Tomas! After you’re done, interpret them.
/noted
Okay, less poetry, more science.
This is a short story on how I spent a few hours trying to renew a Let’s
Encrypt certificate for my home server. And kept on
failing. Until I succeeded and learnt a lesson (which is in the $title).
My colleague, @FrostyX, recently shared a Red Hat Developer article, Thousands of PyPI and RubyGems RPMs now available for RHEL 9, with us.
TL;DR access thousands of RPMs automatically generated from PyPI and RubyGems on RHEL 9.
Sounds intriguing, I wanted to give it a shot.
…I recently finished decommissioning an old project of ours: CentOS Stream 8 source-git repositories.
It was one of the weirdest tasks I have done in my career.
Why?
…I blogged recently which means I need to do it again before another year of silence 😁
So… containers, we know them for years now but they still tend to cause us problems thanks to the extra layers of abstraction, storage and… Networking.
……when the numbers are not increasing consistently.
We have moved from httpd + mod_wsgi to launch Packit’s API server with
mod_wsgi-express.
That change simplified
how we run Packit - look at the number of removed lines! But sadly it broke a
Grafana chart I used almost daily. The chart shows an
amount of traffic from GitHub webhooks Packit processes.
It’s Sunday evening, January 2nd and I finally made myself to start writing this blog post. It was on my plate for more than four weeks: I guess it’s hard to write when you don’t have the frame. I did not really know what I want to achieve with this writing: new year sounded like a great excuse.
This is my first blog post with no technical content. We’ll see if one of many going forward.
…It’s Friday evening, 19:00 (7pm) and I just spent more than an hour resolving a problem in anaconda. The problem was that builds sometimes failed with:
/bin/sh: /sandcastle/docker-io-usercont-sandcastle-prod-20210212-101715691597/missing: No such file or directory
The irony, right? A file called “missing” is actually missing.
Luckily, I was successful and figured it out. Beer incoming.
…This is a follow-up to the open-source-as-a-service blog post of a friend and a colleague of mine, Stef Walter.
TL;DR of Stef’s article is that open source services are hard to contribute to. Any first-time contributor is probably having hard times to try changes locally in the same way the service is deployed in production.
Imagine that you’d be able to contribute to GitHub and try your change in some playground moments later you opened your PR. Freakin’ awesome, right?! I strongly advise you to read Stef’s blog post to understand this concept further.
In this article I’d like to discuss the practical side of this - how can one actually achieve such glorious service contribution model?
…