07 Apr 2026
Fedora People
Rénich Bon Ćirić: Historia de Planeta Libre
¿Te acuerdas de Planeta Linux México? Qué tiempos aquellos, compa. Hoy me puse nostálgico pensando en cómo ese espacio nos unía a todos los que andábamos metidos en el rollo del software libre hace ya más de dos décadas. Planeta Libre no es nomás un agregador de blogs; es la neta, es la continuación de un esfuerzo comunitario que se niega a morir.
Orígenes y Nostalgia
El proyecto nace de esa pinche nostalgia por los tiempos dorados. Durante los primeros años de los 2000, ese espacio era el punto de encuentro fundamental. Como miembro de la comunidad de Fedora, siempre valoré esa interacción única que se armaba entre desarrolladores, usuarios y entusiastas. ¡Era puro fuego!
Note
Fue en aquel Planeta original donde tuve el honor de conocer y convivir con grandes luminarios de la escena mexicana.
Figuras como Gunnar Wolf, cuyo blog Nice Grey Life ha sido una referencia constante, y muchos otros que le dieron forma a lo que hoy entendemos como el ecosistema de software libre en nuestro país. Había varios otros. La neta, les debemos un buen.
La Misión de Continuar
Con el paso de los años, las plataformas cambian y los espacios a veces se pierden gacho. Pero la necesidad de ese "pulso" comunitario sigue ahí, bien latente. Planeta Libre surgió como un intento personal de recuperar esa chispa, de mantener viva la conversación que iniciamos hace tantos años. ¿No crees que hace falta más de eso hoy en día?
Evolución Técnica y Apoyo Comunitario
Inicialmente, el proyecto comenzó su andadura técnica bajo el dominio planeta.libre, utilizando la red OpenNIC. Era una declaración de principios: un espacio libre en una red libre. ¡Bien perro!
Poco después, recibimos un impulso chido, que estuvo de locos: Octavio Álvarez (alvarezp), un pilar indiscutible de nuestra comunidad (conocido por su chamba en el Gultij y en proyectos como Debian y LibreOffice), decidió donar el dominio oficial planetalibre.org.
Tip
Esta generosa donación no solo nos dio un hogar más estable, sino que validó todo el esfuerzo. ¡Gracias, mi Octavio!
Hoy, Planeta Libre está construido con tecnología moderna (Crystal y Kemal), buscando ser rápido, seguro y, sobre todo, un espejo fiel de lo que nuestra comunidad está creando día con día. Digo, sin mencionar que se la pela todo el mundo con la velocidad de procesamiento; la cual es < 100 µs. Micro... como en millonésimas de segundo.
Agradecimientos
Este proyecto existe gracias a gente chingona:
- La comunidad original de Planeta Linux México:
- Por darnos el ejemplo y el espacio inicial que tanto extrañábamos.
- Los de OpenNIC:
- Sin esos batos, la neta, no se arma la cosa. Que chido que existan y que nos echen la mano.
- Octavio Álvarez (alvarezp):
- Por su generosidad al donar el dominio y su eterno compromiso técnico con México. Esperemos que sean muchos, muchos... MUCHOS años. ;D
- La Comunidad de Fedora:
- Por ser el motor de mi propia formación técnica y comunitaria. ¡Fedora manda!
¡Sigamos escribiendo esta historia juntos, que esto apenas se vuelve a poner bueno!
07 Apr 2026 6:00pm GMT
Fedora Community Blog: Fedora Code of Conduct Report 2025
The Fedora Project's Code of Conduct and its reports are managed by the Fedora Code of Conduct Committee, the Fedora Community Architect, and the Fedora Project Leader. We publish this summary to demonstrate our commitment to community safety and our project's social fabric.
This post covers the year of reports received in the 2025 calendar year. The purpose of publishing the annual Code of Conduct Report is to provide transparency, insight, and awareness into the health signs of the community.
How'd it go in 2025
In 2025, we had a slight uptick in engagement from 2024. 14 reports were opened in 2025, compared to 11 reports in 2024. While we saw some members step down this year, the Fedora Code of Conduct Committee (CoCC) also refreshed its membership with new voices. Jef Spaleta, Chris Idoko, and Ankur Sinha were nominated this year to maintain responsiveness and steer our community standards forward.
The majority of issues reported in the year 2025 were largely handled through "shoulder taps" and formal reach-outs. This is in comparison to disciplinary actions or emergency action requiring bans or long-term suspensions. While reports did increase from 2024 to 2025, the difference is negligible. The Committee expects this number to fluctuate annually, as world events and international conflicts often impact the social dynamics of communities like ours.
You can see the full data from 2025 in the table below.
Community Health Assessment
After six years of reporting, looking back at our journey from the modernization of the Code of Conduct to where we stand today, it is encouraging to see how much we have grown together. Yearly reports indicate while our community continues to have conflicts (as any healthy community ought to), incident severity continues to decrease comparing reports spanning 2020 through 2025. We attribute this consistent reduction in "opened reports" and "CoC interventions" to the maturity of our self-moderation culture.
A significant part of this positive atmosphere is thanks to the refreshed CoC guidelines established by Marie Nordin in 2021 successfully addressing the peak in incidents that occurred in the COVID-19. These were roadmaps on how we want to treat each other. Seeing these guidelines in actions in our reports shows that they are working as hoped. We feel the community is in a healthy place at this time, but a healthy committee is one that never stops listening. We would love to hear your thoughts, feedback and suggestions on how we can continue to help our shared spaces feel safe, inclusive and welcoming.
| Year | Reports Opened | Reports Closed | Warnings Issued | Moderations Issued | Suspensions Issued | Bans Issued |
| 2025 | 14 | 14 | 1 | 2 | 0 | 0 |
| 2024 | 11 | 11 | 1 | 0 | 1 | 0 |
| 2023 | 17 | 17 | 5 | 3 | 1 | 1 |
| 2022 | 21 | 24 | 6 | 3 | 0 | 0 |
| 2021 | 23 | 24 | 2 | 1 | 0 | 1 |
| 2020 | 20 | 16 | 8 | 4 | 2 | 0 |
Looking forward to 2026
If you witness or are part of a situation that violates Fedora's Code of Conduct, please open a private report on the [Code of Conduct repo] or email codeofconduct@fedoraproject.org. As always, your reports are confidential and only visible to the Code of Conduct Committee.
Remember that opening a CoC report does not automatically mean action will be taken. Sometimes things can be clarified, improved, or resolved entirely. Or, it could be something pretty small, but it definitely wasn't okay, and you don't want to make a big deal… open that report anyway, because it could show a pattern of behavior that is negatively impacting more people than yourself.
Here is a reminder to our Fedora community to be kind and considerate to each other in all our interactions. We all depend on each other to create a community that is healthy, safe, and happy. Most of all, we love seeing folks self-moderate and stand up for the right thing day to day in our community. Keep it up, and keep being awesome Fedora, we <3 you!
About the Committee
Fedora Project's Code of Conduct and reports are managed by the Fedora Code of Conduct Committee (CoCC). The Fedora CoCC is made up of the Fedora Project Leader, Jef Spaleta; the Fedora Community Architect, Justin Wheeler; the Red Hat legal team, as appropriate; and community nominated members. Jef Spaleta, Chris Onoja Idoko, Ankur Sinha, nominated this year.
We're incredibly grateful to Josh Berkus and Laura Santamaria for stepping up as term-limited members of the Fedora Code of Conduct Committee (CoCC). Their commitment ensured we had consistent coverage through September 30th, 2025, providing vital support until our newest nominees were fully onboarded and trained.
The post Fedora Code of Conduct Report 2025 appeared first on Fedora Community Blog.
07 Apr 2026 12:00pm GMT
06 Apr 2026
Fedora People
Fedora Infrastructure Status: Matrix server maintenance
06 Apr 2026 11:15am GMT
Guillaume Kulakowski: Migrer ses DNS sur Cloudflare : retour d’expérience et pièges à éviter
06 Apr 2026 8:00am GMT
04 Apr 2026
Fedora People
Alexander Bokovoy: kurbu5: MIT Kerberos plugins in Rust
04 Apr 2026 7:10pm GMT
Kevin Fenzi: misc fedora bits first week of april 2026
A somewhat quiet week in fedora land this time, which is nice, as it allows for catching up on planned work. Of course there was the usual flow of day to day items too.
DeploymentConfig to Deployment
Long ago OpenShift used a custom object called 'DeploymentConfig' to define how to deploy applications. After a while it was deprecated in favor of the normal k8s 'Deployment' object. We have a bunch of apps using the old DeploymentConfig and we wanted to migrate them to the new Deployment.
To be clear, this is just a deprecation right now, it's not been removed from OpenShift yet, but we wanted to get things moveed sooner rather than later.
So, Pedro did all the heavy lifting here and created pull requests for all our apps to move them.
I spent some time this last week merging those and then doing the dance to change the existing app over, which roughly was:
-
merge pull request
-
delete DeploymentConfig
-
run ansible to deploy the Deployment
-
check that everything was redeployed and working correctly.
I managed to find a few apps in staging that were not working or deployed correctly and had to fix those up along the way. We also hit some issues with selectors not getting updated, so applications didn't have correct routes/services.
There's a few more of these to do, but will probibly wait until after freeze is over to do them as they could be disruptive.
Fedora 44 Final freeze
Speaking of freeze, we started the Fedora 44 Final infrastructure freeze. So far things are looking smooth for composes and such.
There are a few blockers currently, but hopefully we can get them sorted out and get a good release soon.
koji packaging
koji 1.36.0 came out last week and I spent a bit of time this week looking at modernizing the fedora spec to more match the python packaging guidelines and also to enable tests.
My somewhat hacky pr is at https://src.fedoraproject.org/rpms/koji/pull-request/29
It's nice to run the tests and have things not throwing deprecation warnings.
Upcoming blogs and vacation
I have some posts planned which I need to actually write up sometime. One on my solar system, which is mostly going great, and another fun one on open source monitoring of blood glucose levels. Perhaps this weekend.
I'm going to be largely away from the internet the week of April 20th. I'm going on a family vacation to Hawaii. :) I have never been there, so it should be pretty fun. I'll probibly check emails from time to time, but I will definitely not be around day to day on matrix/slack/irc/whatever.
comments? additions? reactions?
As always, comment on mastodon: https://fosstodon.org/@nirik/116347877029785741
04 Apr 2026 6:18pm GMT
Vedran Miletić: The follow-up
04 Apr 2026 2:43pm GMT
Vedran Miletić: The academic and the free software community ideals
04 Apr 2026 2:43pm GMT
Vedran Miletić: Should I do a Ph.D.?
04 Apr 2026 2:43pm GMT
Vedran Miletić: Markdown vs reStructuredText for teaching materials
04 Apr 2026 2:43pm GMT
Vedran Miletić: I am still not buying the new-open-source-friendly-Microsoft narrative
04 Apr 2026 2:43pm GMT
Vedran Miletić: Free to know: Open access and open source
04 Apr 2026 2:43pm GMT
Vedran Miletić: Fly away, little bird
04 Apr 2026 2:43pm GMT
Vedran Miletić: Enabling HTTP/2, HTTPS, and going HTTPS-only on inf2
04 Apr 2026 2:43pm GMT
Vedran Miletić: Celebrating Graphics and Compute Freedom Day
04 Apr 2026 2:43pm GMT
Vedran Miletić: Browser wars
04 Apr 2026 2:43pm GMT