Normal view

This Week in GNOME: #232 Upcoming Deadlines

16 January 2026 at 00:00

Update on what happened across the GNOME project in the week from January 09 to January 16.

GNOME Releases

Sophie (she/her) reports

The API, UI, and feature freeze for GNOME 50 is closing in. The deadline is in about two weeks from now on Jan 31 at 23:59 UTC. After that, the focus will be on bug fixes, polishing, and translations for GNOME 50.

Sophie (she/her) announces

GNOME 50 alpha has been released. One of the biggest changes is the removal of X11 support from several components like GNOME Shell, while the login screen can still launch non-X11 sessions of other desktop environments. More information is available in the announcement post.

Third Party Projects

Ronnie Nissan reports

Embellish v0.6.0 was released this week. I finally was able to make the app translatable, which was not easy due to me not knowing how to translate GKeyFiles. I also added Arabic translations.

I had also released v0.5.2 to update to the latest GNOME runtime and switch to the new libadwaita shortcuts dialog.

You can get Embellish from flathub

Nathan Perlman announces

v1.1.1 of Rewaita was released this week!

To recap, Rewaita allows you to easily modify Adwaita. Like changing the color scheme to match Tokyonight or Gruvbox, or make the window controls look more like MacOS.

A lot has changed over the last month, so this post covers v1.0.9 -> v1.1.1.

What’s new?

  • Patched up most remaining holes in Gnome Shell integration, especially with the overview and dock
  • Extra customization options: transparency, window borders, and sharp corners
  • Major performance improvements
  • Added two new light themes: Kanagawa-Paper, and Thorn
  • Fixed issue with Tokyonight Storm
  • Now allows palette swapping/tinting your wallpapers
  • Added Vietnamese translations, thanks to @hthienloc
  • UI changes + uses Fortune for text snippets
  • Updated adwgtk3 to v6.4
  • New Zypper package for OpenSUSE users
  • Won’t autostart when running in background is disabled
  • ‘Get Involved’ page now loads correctly

I hope you all enjoy this release, and I look forward to seeing your creations on r/gnome and r/unixporn!

Image

Image

Ronnie Nissan announces

Concessio v0.2.0 and v0.2.1 were released this week. The updates include:

  • Switching to Blueprint for UI definitions.
  • Update to the latest GNOME runtime.
  • Use the new libadwaita shortcuts dialog.
  • Make the application accessible to screen reader.

Concessio can be downloaded from flathub

Turtle

Manage git repositories in Nautilus.

Philipp reports

Turtle 0.14 released!

There has been a massive visual improvement on how the commit log graph looks. Instead of adding branches at the top when “Show All Branches” is enabled it now weaves the branches into the graph directly ontop of its parent commit. This results in a much narrower graph, see screenshot below showing the same git repo before and after the change.

It is now also possible to configure the menu entries of the file manager context menu entries.

See the release for more details.

Image

Flare

Chat with your friends on Signal.

schmiddi announces

Version 0.18.0 of Flare was now released. Besides allowing for Flare being used as a primary device, this release contains a critical hotfix that since Tuesday of this week (2026-01-13) some messages are not received properly anymore, which got worse on Wednesday. I urge everyone to upgrade, and check in with one of their official Signal applications that you have not missed any critical messages.

GNOME Foundation

Allan Day says

Another weekly GNOME Foundation update is available this week, covering highlights from the past 7 days. The update includes details from this week’s board meeting, FOSDEM preparations, GUADEC planning, and Flathub infrastructure development.

Digital Wellbeing Project

Ignacy Kuchciński (ignapk) says

As part of the Digital Wellbeing project, sponsored by the GNOME Foundation, there is an initiative to redesign the Parental Controls to bring it on par with modern GNOME apps and implement new features such as Screen Time monitoring, Bedtime Schedule and Web Filtering.

Recently, the changes preventing children from unlocking after their bedtime and allowing parents to extend their screen time have been merged in GNOME Shell (!3980, !3999).

These were the last remaining bits for the parental controls session limits integration in Shell 🎉

Image

Image

That’s all for this week!

See you next week, and be sure to stop by #thisweek:gnome.org with updates on your own projects!

Allan Day: GNOME Foundation Update, 2026-01-16

16 January 2026 at 17:48

Welcome to my regular weekly update on what’s been happening at the GNOME Foundation. As usual, this post just covers highlights, and there are plenty of smaller and in progress items that haven’t been included.

Board meeting

The Board of Directors had a regular meeting this week. Topics on the agenda included:

  • switching to a monthly rather than bi-monthly meeting schedule, which will give more time for preparation and follow-up
  • creating an Audit Committee, which is a requirement for the upcoming audit
  • performing a routine evaluation of how the organisation is being managed

According to our new schedule, the next meeting will be on 9th February.

New finance platform

As mentioned last week, we started using a new platform for payments processing at the beginning of the year. Overall the new system brings a lot of great features which will make our processes more reliable and integrated. However, as we adopt the tool we are having to deal with some ongoing setup tasks which mean that it is taking additional time in the short term.

GUADEC 2026 planning

Kristi has been extremely busy with GUADEC 2026 planning in recent weeks. She has been working closely with the local team to finalise arrangements for the venue and accommodation, as well as preparing the call for papers and sponsorship brochure.

If you or your organisation are interested in sponsoring this fantastic event, just reach out to me directly, or email [email protected]. We’d love to hear from you.

FOSDEM preparation

FOSDEM 2026 is happening over the weekend of 31st January and 1st February, and preparations for the event continue to be a focus. Maria has been organising the booth, and I have been arranging the details for the Advisory Board meeting which will happen on 30 January. Together we have also been hunting down a venue for a GNOME social event on the Saturday night.

Digital Wellbeing

This week the final two merge requests landed for the bedtime and screen time parental controls features. These features were implemented as part of our Digital Wellbeing program, and it’s great to see them come together in advance of the GNOME 50 release. More details can be found in gnome-shell!3980 and gnome-shell!3999.

Many thanks to Ignacy for seeing this work through to completion!

Flathub

Among other things, Bart recently wrapped up a chunk of work on Flathub’s build and publishing infrastructure, which he’s summarised in a blog post. It’s great to see all the improvements that have been made recently.

That’s it for this week. Thanks for reading, and have a great weekend!

Gedit Technology blog: gedit 49.0 released

16 January 2026 at 10:00

gedit 49.0 has been released! Here are the highlights since version 48.0 which dates back from September 2024. (Some sections are a bit technical).

File loading and saving enhancements

A lot of work went into this area. It's mostly under-the-scene changes where there was a lot of dusty code. It's not entirely finished, but there are already user-visible enhancements:

  • Loading a big file is now much faster.
  • gedit now refuses to load very big files, with a configurable limit (more details).

Improved preferences

gedit screenshot - reset all preferences

gedit screenshot - spell-checker preferences

There is now a "Reset All..." button in the Preferences dialog. And it is now possible to configure the default language used by the spell-checker.

Python plugins removal

Initially due to an external factor, plugins implemented in Python were no longer supported.

During some time a previous version of gedit was packaged in Flathub in a way that still enabled Python plugins, but it is no longer the case.

Even though the problem is fixable, having some plugins in Python meant to deal with a multi-language project, which is much harder to maintain for a single individual. So for now it's preferable to keep only the C language.

So the bad news is that Python plugins support has not been re-enabled in this version, not even for third-party plugins.

More details.

Summary of changes for plugins

The following plugins have been removed:

  • Bracket Completion
  • Character Map
  • Color Picker
  • Embedded Terminal
  • Join/Split Lines
  • Multi Edit
  • Session Saver

Only Python plugins have been removed, the C plugins have been kept. The Code Comment plugin which was written in Python has been rewritten in C, so it has not disappeared. And it is planned and desired to bring back some of the removed plugins.

Summary of other news

  • Lots of code refactorings have been achieved in the gedit core and in libgedit-gtksourceview.
  • A better support for Windows.
  • Web presence at gedit-text-editor.org: new domain name and several iterations on the design.
  • A half-dozen Gedit Development Guidelines documents have been written.

Wrapping-up statistics for 2025

The total number of commits in gedit and gedit-related git repositories in 2025 is: 884. More precisely:

138	enter-tex
310	gedit
21	gedit-plugins
10	gspell
4	libgedit-amtk
41	libgedit-gfls
290	libgedit-gtksourceview
70	libgedit-tepl

It counts all contributions, translation updates included.

The list contains two apps, gedit and Enter TeX. The rest are shared libraries (re-usable code available to create other text editors).

If you do a comparison with the numbers for 2024, you'll see that there are fewer commits, the only module with more commits is libgedit-gtksourceview. But 2025 was a good year nevertheless!

For future versions: superset of the subset

With Python plugins removed, the new gedit version is a subset of the previous version, when comparing approximately the list of features. In the future, we plan to have a superset of the subset. That is, to bring in new features and try hard to not remove any more functionality.

In fact, we have reached a point where we are no longer interested to remove any more features from gedit. So the good news is that gedit will normally be incrementally improved from now on without major regressions. We really hope there won't be any new bad surprises due to external factors!

Side note: this "superset of the subset" resembles the evolution of C++, but in the reverse order. Modern C++ will be a subset of the superset to have a language in practice (but not in theory) as safe as Rust (it works with compiler flags to disable the unsafe parts).

Onward to 2026

Since some plugins have been removed, this makes gedit a less advanced text editor. It has become a little less suitable for heavy programming workloads, but for that there are lots of alternatives.

Instead, gedit could become a text editor of choice for newcomers in the computing science field (students and self-learners). It can be a great tool for markup languages too. It can be your daily companion for quite a while, until your needs evolve for something more complete at your workplace. Or it can be that you prefer its simplicity and its not-going-in-the-way default setup, plus the fact that it launches quickly. In short, there are a lot of reasons to still love gedit ❤️ !

If you have any feedback, even for a small thing, I would like to hear from you :) ! The best places are on GNOME Discourse, or GitLab for more actionable tasks (see the Getting in Touch section).

Ignacio Casal Quinteiro: Mecalin

15 January 2026 at 19:13

Many years ago when I was a kid, I took typing lessons where they introduced me to a program called Mecawin. With it, I learned how to type, and it became a program I always appreciated not because it was fancy, but because it showed step by step how to work with a keyboard.

Now the circle of life is coming back: my kid will turn 10 this year. So I started searching for a good typing tutor for Linux. I installed and tried all of them, but didn’t like any. I also tried a couple of applications on macOS, some were okish, but they didn’t work properly with Spanish keyboards. At this point, I decided to build something myself. Initially, I  hacked out keypunch, which is a very nice application, but I didn’t like the UI I came up with by modifying it. So in the end, I decided to write my own. Or better yet, let Kiro write an application for me.

Mecalin is meant to be a simple application. The main purpose is teaching people how to type, and the Lessons view is what I’ll be focusing on most during development. Since I don’t have much time these days for new projects. I decided to take this opportunity to use Kiro to do most of the development for me. And to be honest, it did a pretty good job. Sure, there are things that could be better, but I definitely wouldn’t have finished it in this short time otherwise.

So if you are interested, give it a try, go to flathub and install it: https://flathub.org/apps/io.github.nacho.mecalin

In this application, you’ll have several lessons that guide you step by step through the different rows of the keyboard, showing you what to type and how to type it.

ImageThis is an example of the lesson view.

You also have games.

ImageThe falling keys game: keys fall from top to bottom, and if one reaches the bottom of the window, you lose. This game can clearly be improved, and if anybody wants to enhance it, feel free to send a PR.

ImageThe scrolling lanes game: you have 4 rows where text moves from right to left. You need to type the words before they reach the leftmost side of the window, otherwise you lose.

For those who want to support your language, there are two JSON files you’ll need to add:

  1. The keyboard layout: https://github.com/nacho/mecalin/tree/main/data/keyboard_layouts
  2. The lessons: https://github.com/nacho/mecalin/tree/main/data/lessons

Note that the Spanish lesson is the source of truth; the English one is just a translation done by Kiro.

If you have any questions, feel free to contact me.

Asman Malika: Think About Your Audience

14 January 2026 at 12:07

When I started writing this blog, I didn’t fully understand what “think about your audience” really meant. At first, it sounded like advice meant for marketers or professional writers. But over time, I’ve realized it’s one of the most important lessons I’m learning, not just for writing, but for building software and contributing to open source.

Who I’m Writing (and Building) For

When I sit down to write, I think about a few people.

I think about aspiring developers from non-traditional backgrounds, people who didn’t follow a straight path into tech, who might be self-taught, switching careers, or learning in community-driven programs. I think about people who feel like they don’t quite belong in tech yet, and are looking for proof that they do.

I also think about my past self, about some months ago. Back then, everything felt overwhelming: the tools, the terminology, the imposter syndrome. I remember wishing I could read honest stories from people who were still in the process, not just those who had already “made it.”

And finally, I think about the open-source community I’m now part of: contributors, maintainers, and users who rely on the software we build.

Why My Audience Matters to My Work

Thinking about my audience has changed how I approach my work on Papers.

Papers isn’t just a codebase, it’s a tool used by researchers, students, and academics to manage references and organize their work. When I think about those users, I stop seeing bugs as abstract issues and start seeing them as real problems that affect real people’s workflows.

The same applies to documentation. Remembering how confusing things felt when I was a beginner pushes me to write clearer commit messages, better explanations, and more accessible documentation. I’m no longer writing just to “get the task done”. I’m writing so that someone else, maybe a first-time contributor, can understand and build on my work.

Even this blog is shaped by that mindset. After my first post, someone commented and shared how it resonated with them. That moment reminded me that words can matter just as much as code.

What My Audience Needs From Me

I’ve learned that people don’t just want success stories. They want honesty.

They want to hear about the struggle, the confusion, and the small wins in between. They want proof that non-traditional paths into tech are valid. They want practical lessons they can apply, not just motivation quotes.

Most of all, they want representation and reassurance. Seeing someone who looks like them, or comes from a similar background, navigating open source and learning in public can make the journey feel possible.

That’s a responsibility I take seriously.

How I’ve Adjusted Along the Way

Because I’m thinking about my audience, I’ve changed how I share my journey.

I explain things more clearly. I reflect more deeply on what I’m learning instead of just listing achievements. I’m more intentional about connecting my experiences, debugging a feature, reading unfamiliar code, asking questions in the GNOME community, to lessons others can take away.

Understanding the Papers user base has also influenced how I approach features and fixes. Understanding my blog audience has influenced how I communicate. In both cases, empathy plays a huge role.

Moving Forward

Thinking about my audience has taught me that good software and good writing have something in common: they’re built with people in mind.

As I continue this internship and this blog, I want to keep building tools that are accessible, contributing in ways that lower barriers, and sharing my journey honestly. If even one person reads this and feels more capable, or more encouraged to try, then it’s worth it.

That’s who I’m writing for. And that’s who I’m building for.

Flathub Blog: What's new in Vorarbeiter

14 January 2026 at 00:00

It is almost a year since the switch to Vorarbeiter for building and publishing apps. We've made several improvements since then, and it's time to brag about them.

RunsOn

In the initial announcement, I mentioned we were using RunsOn, a just-in-time runner provisioning system, to build large apps such as Chromium. Since then, we have fully switched to RunsOn for all builds. Free GitHub runners available to open source projects are heavily overloaded and there are limits on how many concurrent builds can run at a time. With RunsOn, we can request an arbitrary number of threads, memory and disk space, for less than if we were to use paid GitHub runners.

We also rely more on spot instances, which are even cheaper than the usual on demand machines. The downside is that jobs sometimes get interrupted. To avoid spending too much time on retry ping-pong, builds retried with the special bot, retry command use the on-demand instances from the get-go. The same catch applies to large builds, which are unlikely to finish in time before spot instances are reclaimed.

The cost breakdown since May 2025 is as follows:

Cost breakdown

Once again, we are not actually paying for anything thanks to the AWS credits for open source projects program. Thank you RunsOn team and AWS for making this possible!

Caching

Vorarbeiter now supports caching downloads and ccache files between builds. Everything is an OCI image if you are feeling brave enough, and so we are storing the per-app cache with ORAS in GitHub Container Registry.

This is especially useful for cosmetic rebuilds and minor version bumps, where most of the source code remains the same. Your mileage may vary for anything more complex.

End-of-life without rebuilding

One of the Buildbot limitations was that it was difficult to retrofit pull requests marking apps as end-of-life without rebuilding them. Flat-manager itself exposes an API call for this since 2019 but we could not really use it, as apps had to be in a buildable state only to deprecate them.

Vorarbeiter will now detect that a PR modifies only the end-of-life keys in the flathub.json file, skip test and regular builds, and directly use the flat-manager API to republish the app with the EOL flag set post-merge.

Web UI

GitHub's UI isn't really built for a centralized repository building other repositories. My love-hate relationship with Buildbot made me want to have a similar dashboard for Vorarbeiter.

The new web UI uses PicoCSS and HTMX to provide a tidy table of recent builds. It is unlikely to be particularly interesting to end users, but kinkshaming is not nice, okay? I like to know what's being built and now you can too here.

Reproducible builds

We have started testing binary reproducibility of x86_64 builds targetting the stable repository. This is possible thanks to flathub-repro-checker, a tool doing the necessary legwork to recreate the build environment and compare the result of the rebuild with what is published on Flathub.

While these tests have been running for a while now, we have recently restarted them from scratch after enabling S3 storage for diffoscope artifacts. The current status is on the reproducible builds page.

Failures are not currently acted on. When we collect more results, we may start to surface them to app maintainers for investigation. We also don't test direct uploads at the moment.

Jussi Pakkanen: How to get banned from Facebook in one simple step

13 January 2026 at 18:06

I, too, have (or as you can probably guess from the title of this post, had) a Facebook account. I only ever used it for two purposes.

  1. Finding out what friends I rarely see are doing
  2. Getting invites to events
Facebook has over the years made usage #1 pretty much impossible. My feed contains approximately 1% posts by my friends and 99% ads for image meme "humor" groups whose expected amusement value seems to be approximately the same as punching yourself in the groin.

Still, every now and then I get a glimpse of a post by the people I actively chose to follow. Specifically a friend was pondering about the behaviour of people who do happy birthday posts on profiles of deceased people. Like, if you have not kept up with someone enough to know that they are dead, why would you feel the need to post congratulations on their profile pages.

I wrote a reply which is replicated below. It is not accurate as it is a translation and I no longer have access to the original post.

Some of these might come via recommendations by AI assistants. Maybe in the future AI bots from people who themselves are dead carry on posting birthday congratulations on profiles of other dead people. A sort of a social media for the deceased, if you will.

Roughly one minute later my account was suspended. Let that be a lesson to you all. Do not mention the Dead Internet Theory, for doing so threatens Facebook's ad revenue and is thus taboo. (A more probable explanation is that using the word "death" is prohibited by itself regardless of context, leading to idiotic phrasing in the style of "Person X was born on [date] and d!ed [other date]" that you see all over IG, FB and YT nowadays.)

Apparently to reactivate the account I would need to prove that "[I am] a human being". That might be a tall order given that there are days when I doubt that myself.

The reactivation service is designed in the usual deceptive way where it does not tell you all the things you need to do in advance. Instead it bounces you from one task to another in the hopes that sunk cost fallacy makes you submit to ever more egregious demands. I got out when they demanded a full video selfie where I look around different directions. You can make up your own theories as to why Meta, a known advocate for generative AI and all that garbage, would want a high resolution scans of people's faces. I mean, surely they would not use it for AI training without paying a single cent for usage rights to the original model. Right? Right?

The suspension email ends with this ultimatum.

If you think we suspended your account by mistake, you have 180 days to appeal our decision. If you miss this deadline your account will be permanently disabled.

Well, mr Zuckerberg, my response is the following:

Image

Close it! Delete it! Burn it down to the ground! I'd do it myself this very moment, but I can't delete the account without reactivating it first.

Let it also be noted that this post is a much better way of proving that I am a human being than some video selfie thing that could be trivially faked with genAI.

Arun Raghavan: Accessibility Update: Enabling Mono Audio

13 January 2026 at 00:09

If you maintain a Linux audio settings component, we now have a way to globally enable/disable mono audio for users who do not want stereo separation of their audio (for example, due to hearing loss in one ear). Read on for the details on how to do this.

Background

Most systems support stereo audio via their default speaker output or 3.5mm analog connector. These devices are exposed as stereo devices to applications, and applications typically render stereo content to these devices.

Visual media use stereo for directional cues, and music is usually produced using stereo effects to separate instruments, or provide a specific experience.

It is not uncommon for modern systems to provide a “mono audio” option that allows users to have all stereo content mixed together and played to both output channels. The most common scenario is hearing loss in one ear.

PulseAudio and PipeWire have supported forcing mono audio on the system via configuration files for a while now. However, this is not easy to expose via user interfaces, and unfortunately remains a power-user feature.

Implementation

Recently, Julian Bouzas implemented a WirePlumber setting to force all hardware audio outputs (MR 721 and 769). This lets the system run in stereo mode, but configures the audioadapter around the device node to mix down the final audio to mono.

This can be enabled using the WirePlumber settings via API, or using the command line with:

wpctl settings node.features.audio.mono true

The WirePlumber settings API allows you to query the current value as well as clear the setting and restoring to the default state.

I have also added (MR 2646 and 2655) a mechanism to set this using the PulseAudio API (via the messaging system). Assuming you are using pipewire-pulse, PipeWire’s PulseAudio emulation daemon, you can use pa_context_send_message_to_object() or the command line:

pactl send-message /core pipewire-pulse:force-mono-output true

This API allows for a few things:

  • Query existence of the feature: when an empty message body is sent, if a null value is returned, feature is not supported
  • Query current value: when an empty message body is sent, the current value (true or false) is returned if the feature is supported
  • Setting a value: the requested setting (true or false) can be sent as the message body
  • Clearing the current value: sending a message body of null clears the current setting and restores the default

Looking ahead

This feature will become available in the next release of PipeWire (both 1.4.10 and 1.6.0).

I will be adding a toggle in Pavucontrol to expose this, and I hope that GNOME, KDE and other desktop environments will be able to pick this up before long.

Hit me up if you have any questions!

Khrys’presso du lundi 12 janvier 2026

12 January 2026 at 06:42

 

Comme chaque lundi, un coup d’œil dans le rétroviseur pour découvrir les informations que vous avez peut-être ratées la semaine dernière.


Tous les liens listés ci-dessous sont a priori accessibles librement. Si ce n’est pas le cas, pensez à activer votre bloqueur de javascript favori ou à passer en “mode lecture” (Firefox) ;-)

Brave New World

Spécial IA

Les Facepalm de la semaine

Spécial Renée Nicole Good

Spécial femmes dans le monde

Spécial Palestine et Israël

Spécial France

RIP

  • Généalogies féministes et fractures politiques : à la mémoire d’Eleni Varikas (blogs.mediapart.fr)

    Le vendredi 9 janvier 2026, Eleni Varikas s’est éteinte à Paris. Son travail s’est concentré sur la théorie féministe, le colonialisme, les origines du racisme et les problématiques de l’exclusion. À travers une lecture exigeante de l’universalisme moderne, Eleni Varikas n’a cessé d’en interroger les angles morts, les exclusions constitutives et les hiérarchies qu’il prétend pourtant abolir.

Spécial femmes en France

Spécial médias et pouvoir

Spécial emmerdeurs irresponsables gérant comme des pieds (et à la néolibérale)

Spécial recul des droits et libertés, violences policières, montée de l’extrême-droite…

Spécial résistances

Spécial outils de résistance

Spécial GAFAM et cie

Les autres lectures de la semaine

Les BDs/graphiques/photos de la semaine

Les vidéos/podcasts de la semaine

Les trucs chouettes de la semaine

Image

Retrouvez les revues de web précédentes dans la catégorie Libre Veille du Framablog.

Les articles, commentaires et autres images qui composent ces « Khrys’presso » n’engagent que moi (Khrys).

Allan Day: GNOME Foundation Update, 2026-01-09

9 January 2026 at 15:56

Welcome to the first GNOME Foundation update of 2026! I hope that the new year finds you well. The following is a brief summary of what’s been happening in the Foundation this week.

Trademark registration renewals

This week we received news that GNOME’s trademark registration renewals have been completed. This is an example of the routine legal functions that the GNOME Foundation handles for the GNOME Project, and is part of what I think of as our core operations. The registration lasts for 10 years, so the next renewal is due in 2036. Many thanks to our trademark lawyers for handling this for us!

Microsoft developer account

Another slow registration process that completed this week was getting verified status on our Microsoft Developer Account. This was primarily being handled by Andy Holmes, with a bit of assistance on the Foundation side, so many thanks to him. The verification is required to allow those with Microsoft 365 organizational accounts to use GNOME Online Accounts.

Travel Committee

The Travel Committee had its first meeting of 2026 this week, where it discussed travel sponsorships for last month’s GNOME.Asia conference. Sadly, a number of people who were planning to travel to the conference had their visas denied. The committee spent some time assessing what happened with these visa applications, and discussed how to support visa applicants better in future. Thanks in particular to Maria for leading that conversation.

GNOME.Asia Report

Also related to GNOME.Asia: Kristi has posted a very nice report on the event, including some very nice pictures. It looks like it was a great event! Do make sure that you check out the post.

Audit preparation

As I mentioned in previous posts, audit preparation is going to be a major focus for the GNOME Foundation over the next three months. We are also finishing off the final details of our 2024-25 accounts. These two factors resulted in a lot of activity around the books this week. In addition to a lot of back and forth with our bookkeeper and finance advisor, we also had a regular monthly bookkeeping call yesterday, and will be having an extra meeting to make more process in the next few weeks.

New payments platform rollout

With it being the first week of the month, we had a batch of invoices to process and pay this week. For this we made the switch to a new payments processing system, which is going to be used for reimbursement and invoice tracking going forward. So far the system is working really well, and provides us with a more robust, compliant, and integrated process than what we had previously.

Infrastructure

Over the holiday, Bart cleared up the GNOME infrastructure issues backlog. This led him to write a service which will allow us to respond to GitLab abuse reports in a better fashion. On the Flathub side, he completed some work on build reproducibility, and finished adding the ability to re-publish apps that were previously marked as end of life.

FOSDEM

FOSDEM 2026 preparations continued this week. We will be having an Advisory Board meeting, for which attendance is looking good, so good that we are currently in the process of booking a bigger room. We are also in the process of securing a venue for a GNOME social event on the Saturday night.

GNOME Foundation donation receipts

Bart added a new feature to donate.gnome.org this week, to allow donors to generate a report on their donations over the last calendar year. This is intended to provide US tax payers with the documentation necessary to allow them to offset their donations against their tax payments. If you are a donor, you can generate a receipt for 2025 at donate.gnome.org/help .

That’s it for this week’s update! Thanks for reading, and have a great weekend.

Jussi Pakkanen: AI and money

9 January 2026 at 13:56

If you ask people why they are using AI (or want other people to use it) you get a ton of different answers. Typically none of them contain the real reason, which is that using AI is dirt cheap. Between paying a fair amount to get something done and paying very little to give off an impression that the work has been done, the latter tends to win.

The reason AI is so cheap is that it is being paid by investors. And the one thing we know for certain about those kinds of people is that they expect to get their money back. Multiple times over. This might get done by selling the system to a bigger fool before it collapses, but eventually someone will have to earn that money back from actual customers (or from government bailouts, i.e. tax payers).

I'm not an economist and took a grand total of one economics class in the university, most of which I have forgotten. Still, using just that knowledge we can get a rough estimate of the money flows involved. For simplicity let's bundle all AI companies to a single entity and assume a business model based on flat monthly fees.

The total investment

A number that has been floated around is that AI companies have invested approximately one trillion (one thousand billion or 1e12) dollars. Let's use that as the base investment we want to recover.

Number of customers

Sticking with round figures, let's assume that AI usage becomes ubiquitous and that there are one billion monthly subscribers. For comparison the estimated number of current Netflix subscribers is 300 million.

Income and expenses

This one is really hard to estimate. What seems to be the case is that current monthly fees are not enough to even pay back the electricity costs of providing the service. But let's again be generous and assume that some sort of a efficiency breakthrough happens in the future and that the monthly fee is $20 with expenses being $10. This means a $10 profit per user per month.

We ignore one-off costs such as buying several data centers' worth of GPUs every few years to replace the old ones.

The simple computation

With these figures you get $10 billion per month or $120 billion per year. Thus paying off the investment would take a bit more than 8 years. I don't personally know any venture capitalists, but based on random guessing this might fall in the "takes too long, but just about tolerable" level of delay.

So all good then?

Not so fast!

One thing to keep in mind when doing investment payback calculations is the time value of money. Money you get in "the future" is not as valuable as money you have right now. Thus we need to discount them to current value.

Interest rate

I have no idea what a reasonable discount rate for this would be. So let's pick a round number of 5.

The "real-er" numbers

At this point the computations become complex enough that you need to break out the big guns. Yes, spreadsheets.

Image

Here we see that it actually takes 12 years to earn back the investment. Doubling the investment to two trillion would take 36 years. That is a fair bit of time for someone else to create a different system that performs maybe 70% as well but which costs a fraction of the old systems to get running and operate. By which time they can drive the price so low that established players can't even earn their operating expenses let alone pay back the original investment. 

Exercises for the reader

  • This computation assumes the system to have one billion subscribers from day one. How much longer does it take to recuperate the investment if it takes 5 years to reach that many subscribers? What about 10 years?
  • How long is the payback period if you have a mere 500 million paid subscribers?
  • Your boss is concerned about the long payback period and wants to shorten it by increasing the monthly fee. Estimate how many people would stop using the service and its effect on the payback time if the fee is raised from $20 to $50. How about $100? Or $1000?
  • What happens when the ad revenue you can obtain by dumping tons of AI slop on the Internet falls below the cost of producing said slop?

Engagement Blog: GNOME ASIA 2025-Event Report

9 January 2026 at 11:35

GNOME ASIA 2025 took place in Tokyo, Japan, from 13–14 December 2025, bringing together the GNOME community for the featured annual GNOME conference in Asia.
The event was held in a hybrid format, welcoming both in-person and online speakers and attendees from across the world.

GNOME ASIA 2025 was co-hosted with the LibreOffice Asia Conference community event, creating a shared space for collaboration and discussion between open-source communities.

Image
Photo by Tetsuji Koyama, licensed under CC BY 4.0

About GNOME.Asia Summit

The GNOME.Asia Summit focuses primarily on the GNOME desktop while also covering applications and platform development tools. It brings together users, developers, foundation leaders, governments, and businesses in Asia to discuss current technologies and future developments within the GNOME ecosystem.

The event featured 25 speakers in total, delivering 17 full talks and 8 lightning talks across the two days. Speakers joined both on-site and remotely.

Image
Photo by Tetsuji Koyama, licensed under CC BY 4.0

 

 

 

 

 

 

 

 

Around 100 participants attended in person in Tokyo, contributing to engaging discussions and community interaction. Session recordings were published on the GNOME Asia YouTube channel, where they have received 1,154 total views, extending the reach of the event beyond the conference dates.

With strong in-person attendance, active online participation, and collaboration with the LibreOffice Asia community, GNOME ASIA 2025 once again demonstrated the importance of regional gatherings in strengthening the GNOME ecosystem and open-source collaboration in Asia.

Image
Photo by Tetsuji Koyama, licensed under CC BY 4.0

 

 

This Week in GNOME: #231 Blueprint Maps

9 January 2026 at 00:00

Update on what happened across the GNOME project in the week from January 02 to January 09.

GNOME Core Apps and Libraries

Maps

Maps gives you quick access to maps all across the world.

mlundblad announces

Thanks to work done by Jamie Gravendeel Maps has now been ported to use Blueprint to define the UI templates. Also Hari Rana ported the share locations (“Send to”) dialog to AdwDialog.

Image

Image

Third Party Projects

Giant Pink Robots! says

Version v2026.1.5 of the Varia download manager was released with automatic archive extraction, improvements to accessibility and tons of bug fixes and small improvements. The biggest part of this new release however is macOS support, albeit in an experimental state for now. With this, Varia now supports all three big desktop OS platforms: Linux, Windows and Mac. https://giantpinkrobots.github.io/varia/

francescocaracciolo announces

Newelle, AI Assistant for Gnome, received a new major update!

  • Added MCP server support, enabling integration with thousands of apps
  • Added Tools, extensions can now add new tools very easily
  • Added the possibility to set some models as favoutites
  • You can now trigger recording and TTS stop with keyboard shortcuts

Download it on Flathub

Phosh

A pure wayland shell for mobile devices.

Guido announces

Phosh 0.52 is out:

We’ve added a QR code to the Wi-Fi quick setting so clients can connect easily by scanning it and there’s a new gesture to control brightness on the lock screen.

There’s more — see the full details here.

Image

Flare

Chat with your friends on Signal.

schmiddi announces

Version 0.18.0-beta.1 of Flare was now released on flathub-beta. This release includes fixes for using Flare as a primary device, which I have done successfully for a while now. Feel free to test it out and provide feedback. Note that if you want to try it out, I would heavily encourage linking Signal-Desktop to Flare in order to set your profile information and to start new chats. Feel free to give feedback if you have any issues with this beta in the Matrix room or issue tracker.

Emergency Alerts

Receive emergency alerts

Leonhard reports

Emergency Alerts 2.0.0 has been released! It finally brings the long-awaited weather alerts for the U.S. and air raid alerts for Ukraine. Location selection is now also more powerful, allowing you to choose any point on Earth, and the new map view lets you see active alerts and affected areas at a glance. Please note that to make all this possible, the way locations are stored had to be updated. When you first launch the app after updating, it tries to migrate your existing locations automatically. In rare cases, this may not work and you might need to re-add them manually. If that happens a notification will be sent.

Highlights:

  • Weather alerts now available across the U.S.
  • Air raid alerts now available for Ukraine
  • Pick any point on Earth as a location
  • New map view showing active alerts and impacted areas

Image

Image

Image

GNOME Websites

Sophie (she/her) says

The www.gnome.org pages are now available in English, Bulgarian, Basque, Brazilian Portuguese, Swedish, Ukrainian, and Chinese. You can contribute additional translations on l10n.gnome.org.

Image

Miscellaneous

Guillaume Bernard reports

Damned Lies has been refreshed during the last weeks of 2025.

To refresh the statistics of branches, many of you complained that the task was synchronous and ended in timeouts. I have reworked this part in anticipation of ticket #409 (asynchronous git pushes) and the refresh now delegates refresh statistics to a Celery worker. For git pushes, we’ll use Celery tasks the same way!

In short, this means every time you click the refresh statistics button, it will start a job in the background, and a progress bar will show you the refresh status of the job in real time. There will be a maximum of three concurrent refreshes at a time, that should be enough :-).

In addition to these major changes, I reworked the presentation of languages and POT files in modules:

  1. The date & time of the POT file generation is now shown with the number of messages.

  2. Your languages are shown on top of the list; it will no longer be necessary to scroll down to find your language in the language list.

Image

Image

Arjan reports

PyGObject 3.55.1 has been released. It’s the second development release (it’s not available on PyPI) in the current GNOME release cycle.

Notable changes include:

  • A fix do do_dispose() is always called on your object.
  • You can define a do_constructed() method that will be called after the object is initialised.
  • A regression in 3.55.0 has been fixed: instance data is now saved and outlives the garbage collector.

All changes can be found in the Changelog

This release can be downloaded from Gitlab and the GNOME download server.If you use PyGObject in your project, please give it a swing and see if everything works as expected.

That’s all for this week!

See you next week, and be sure to stop by #thisweek:gnome.org with updates on your own projects!

Les Accords du Lion d’Or, un tiers-lieu à dimension culturelle en cours de dégafamisation

7 January 2026 at 09:00

Parce qu’il nous semble toujours aussi important de promouvoir les démarches de transition vers les outils numériques éthiques opérées par les organisations, voici un nouvel opus pour notre série de témoignages de Dégooglisation. Un grand merci à Étienne d’avoir pris le temps de nous raconter comment le tiers-lieu Les Accords du Lion d’Or dans lequel il est investi, a changé de vie numérique..

Bonjour, peux-tu te présenter brièvement pour le Framablog ?

Bonjour, je suis Étienne régisseur et technicien du spectacle en transition, passionné d’informatique depuis fort longtemps, je quitte le milieu du spectacle pour me consacrer désormais à ma première passion. J’ai rencontré l’association Les Accords du Lion d’Or en 2016, un tiers-lieu à vocation culturelle fraîchement installé dans mon village natal, juste à côté de la ville dans laquelle je suis revenu m’installer après ma formation et quelques années de travail à Bruxelles.
C’est un projet aux multiples facettes, spectacles vivant, lieu de mémoire du village, projet de forêt nourricière, recherche sur le numérique, en lien avec les habitant⋅e⋅s… J’avais été invité à coanimer une rencontre avec des écoliers au sujet des photos et vieilles cartes postales du village, comment faire un travail de mémoire. C’est un projet qui ressemblait beaucoup à ce que j’avais moi-même vécu à l’école de Simandre en 2003 : numériser et classer dans une base de données sommaire, une partie de ces photos. C’est ainsi que j’ai rencontré l’association.
Située dans un lieu emblématique au cœur du village et de part la volonté d’être à la rencontre des habitants, de nombreuses histoires et matières, cartes postales, images, menus, récits et autres sont arrivées au Lion d’Or ; le besoin d’enregistrer et préserver les souvenirs s’est accentué.

Entête du site Les accords du Lion d'or

Entête du site Les Accords du Lion d’Or

Nous avons alors choisi de démarrer une base de données avec comme objet les images. Fort de mes convictions elle serait sur GNU/Linux, ce choix était entre mes mains et la confiance de l’équipe était là.
À ce jour, nous sommes un collectif multiforme, un conseil collégial d’administration, 1 salariée à 80 % chargée de missions, 1 salariée à 70 % animatrice nature, 1 salarié à 25 % agent en charge du développement des usages numériques en 2023 : c’est moi, une artiste plasticienne et trois artistes du spectacle pleinement impliqués dans la vie de l’association.
Au fil des projets il s’est avéré que plusieurs personnes au sein de l’équipe étaient sensibles aux questions de souveraineté numérique. Rapidement, nous nous sommes rendu compte des compétences que j’avais accumulées au fil des années et de l’intérêt pour l’association d’en faire un sujet commun.

 

Quel a été le déclencheur de votre dégafamisation ?

En fait on a pas vraiment eu un déclic, ça s’est fait au fur et à mesure en fonction des besoins des salariés de l’association. Pas à pas nous avons fait des choix de plus en plus importants toujours dans une démarche de recherche et d’expérimentation qui sont des valeurs importantes au Lion d’Or. Par exemple, le site de l’association est éco-conçu : sobriété et inclusion. Ce premier acte avait été posé avant même mon arrivée.
Ma rencontre avec l’association a probablement été un des déclencheurs tout de même, car j’arrivais avec une démarche engagée personnellement depuis longtemps : explorer l’auto-hébergement. J’ai apporté mon expérience du numérique dans plusieurs projets, lors de la création d’un escape-game en assistant l’équipe, dont le duo artistique « Scénocosme », la création de la base de données d’images, la création de documents pour les expositions en coopération avec les habitants… Et de fil en aiguille on a tissé ce lien de confiance avec un numérique différent.

Image

Bannière du couple d’artistes Scénocosme

Comme nous sommes une petite équipe de salariés (en lien avec un conseil d’administration qui a confiance lui aussi !), la question de la dégafamisation nous concernait directement. Être peu nombreux a été clairement un atout pour la rapidité, la simplicité dans toutes les étapes de cette transition, on en reparlera souvent.
Tout le monde était éveillé d’une manière ou d’une autre sur le sujet, certains ayant déjà fait des choix pour leur vie numérique personnelle (il faut dire que dans les livres qui sont posés ici et là dans le tiers-lieu il y a Yggdrasil, Pablo Servigne, Cyril Dion, Socialter ;-)). Quand j’ai proposé de passer une première étape décisive, passer de GDrive à Nextcloud sur un petit NAS, le choix a été rapidement fait. Les quelques craintes soulevées ont été discutées directement and voilà ! Elles concernaient principalement le maintien des données, ne pas perdre le travail en cours. Nous n’avons rien perdu et ça a même été l’occasion de donner une nouvelle arborescence au dossier de travail qui avait déjà 3 ans de données.
Nous avons par la suite organisé une rencontre avec les membres du CA pour leur présenter les outils et les fonctionnements qui ont été reçus avec des avis mitigés mais confiants sur le moment car l’intérêt pour eux n’était pas direct.

 

Comment avez-vous organisé votre dégafamisation ?

Pour nous, ça s’est vraiment fait au fur et à mesure, à petit pas. L’association est toujours en recherche, en expérimentation sur tous les sujets qui la concerne, donc à chaque fois que nous nous posions la question nous pouvions faire un choix dans cette direction.
J’avais connaissance du réseau des C.H.A.T.O.N.S. et nous avons contacté Hadoly pour avoir un avis, c’est grâce à eux que nous utilisons Yunohost qui est un élément technique important de cette expérience.

Image

Le logo d’HADOLY, un CHATON lyonnais qui vient de fêter ses 10 ans.

On peut résumer les grandes étapes qu’on détaillera plus bas :

  • 2018 – réalisation du site internet en éco-conception
  • 2019 – démarrage de la base de données d’images : GNU/Linux et DigiKam
  • 2019 – N.A.S. pour les sauvegardes et première bascule pour le partage de fichiers et les agendas
  • 2022 – installation d’un serveur dédié pour rapatrier plus de services.
  • 2023 – changement de système d’exploitation pour 2 salariées de MacOS vers GNU/Linux
  •  2024 – changement d’outil de comptabilité

 

Est-ce que vous avez rencontré des résistances que vous n’aviez pas anticipées, qui vous ont pris par surprise ? Au contraire, y a-t-il eu des changements dont vous aviez peur et qui se sont passés comme sur des roulettes ?

Ça a franchement roulé. Je crois que pour tous dans l’équipe la transition a été fluide même si elle a demandé des temps d’adaptation et lorsqu’il y avait à faire un ajustement, on a pu réagir tout de suite. Par exemple la migration des agendas, nous étions tous dans la même pièce et je guidais chacun·e dans la marche à suivre.
Une nouvelle fois, être en petit nombre a été un atout. Un autre point non négligeable est d’avoir quelqu’un « dédié » à la question, régulièrement présent pour répondre aux questions ou difficultés techniques. C’est presque de la formation continue. Les choses se sont faites au fur et à mesure et ça a permis à chacun et chacune de s’approprier chaque outil petit à petit. Un gros passage a quand même été le changement de système d’exploitation pour la chargée de mission, Véro, lors de notre première install’party, après 30 années avec MacOS, passer à Kubuntu a demandé beaucoup d’énergie et d’adaptabilité. Elle a fait preuve de beaucoup de souplesse et détermination pour changer d’un seul coup tout un environnement de travail (contact, e-mail, suite bureautique, classification…).

Image

Kubuntu

On pourrait parler des problématiques techniques mais ça a quand même bien fonctionné de ce côté là, c’est aussi grâce à l’arrivée de la fibre optique dans le village qui nous a permis de franchir l’étape de l’auto-hébergement.

 

Parlons maintenant outils ! Quels outils ou services avez-vous remplacé, et par quoi, sur quels critères ?

Voici un tableau récapitulatif que je vais vous détailler ci-dessous :

Phase Service Outil d’avant Remplacé par
NAS 2019 Agenda partagé Google Agenda Nextcloud calendar
Partage de fichiers Google Drive Nextcloud files
Serveur auto-hébergé 2022 E-mails Gmail Yunohost
Sondages Doodle Nextcloud poll
Formulaires Google forms Nextcloud forms
2024 Suivi des adhésions Excel Paheko
Comptabilité Numbers Paheko

 

Les critères étaient simples :

  • nous ne voulions pas donner d’argent à une entreprise comme Alphabet (maison mère de Google) ;
  • nous avions besoin que ce soit ouvert, interopérable et que ça puisse durer dans le temps ;
  • nous voulions de la collaboration.

C’est quand le compte Google à commencer à afficher « votre espace de stockage est faible » que les choses ont réellement commencé à bouger. On avait deux choix, payer pour agrandir le cloud ou trouver une autre solution. On venait tout juste d’acheter un NAS pour pouvoir sauvegarder notre base de donnée d’images, du stockage on en avait ! Ça a donc répondu à notre premier besoin, la ressource on l’avait, pas besoin de payer.
J’avais commencé à tester pour moi des systèmes avec Owncloud, avant même le fork qui a donné naissance à Nextcloud, et je trouvais ça « fou » ces outils, vraiment puissants. Nextcloud était apparu en 2016 avec des valeurs clairement posées, une communauté hyper active. J’ai donc proposé de l’installer sur notre NAS. Tout le monde est toujours partant pour les expériences ici. Ça répondait clairement à notre deuxième critère qu’on retrouve dans tous les logiciels libres, on pouvait y importer nos données existantes et on savait qu’on pourrait les récupérer à tout moment, pour les mettre ailleurs si notre expérience à domicile ne marchait pas.
Le choix de Nextcloud a été fait pour la simplicité de mise en œuvre. Une fois installé, nombres d’applications sont disponibles en un clic. On avait besoin du partage de fichier, l’agenda était là en même temps.
La suite découle un peu de ça, on avait Nextcloud, il était facile de rapatrier nos sondages et formulaires.
Rapatrier nos e-mails n’a pas été un choix facile, mais la volonté de le faire était vraiment très présente. Techniquement, j’avais mis le nez dans le système des e-mails mais c’est vraiment complexe et fragile. Quand Hadoly nous a parlé de Yunohost j’ai fait quelques mois de test et puis j’ai proposé à l’association une nouvelle expérience : depuis nous avons nos e-mails sur notre serveur.
Suite au passage en conseil collégial en 2023 et de changements qui en ont découlé, j’ai fait le constat suivant : Denis enregistrait les adhérents dans Paheko, Marie-Line faisait les dépôts en banque puis notait son travail dans un tableur, Gilles pointait les relevés de banque au fluo, Bénédicte triait les factures dans un classeur, Véro suivait un peu tout ça à la fois avec ses propres tableurs, Pierre faisait le suivi de trésorerie sur un autre tableur ; tout ceci coûtait beaucoup d’énergie à chacun et chacune et la mise en commun était laborieuse. J’avais mis à l’essai Paheko dans une association plus petite et je me suis vite rendu compte que ce pourrait être l’outil idéal pour que chacun puisse continuer à faire ce qu’il fait, en réduisant la lourde charge de la mise en commun. C’est donc le critère de la collaboration qui nous a permis cette dernière bascule.

Image

Logo de Paheko, logiciel libre de gestion d’association.

 

Est-ce qu’il reste des outils auxquels vous n’avez pas encore pu trouver une alternative libre et pourquoi ?

Oui il en reste deux qui sont liés : les e-mails de notre lettre d’information (newsletter) et un moyen de communiquer sur nos évènements (Facebook).
La raison principale du non changement est le temps nécessaire à la transition et à l’apprentissage d’un nouvel outil. Nous avons regardé pour une alternative sur notre serveur (listmonk) mais il y a un gros travail à faire pour migrer depuis MailChimp et appréhender ce nouveau programme. Nous venons de toucher la limite des 2000 inscriptions d’un compte gratuit chez ce fournisseur, donc nous nous pencherons sur la question en 2025, une fois que nous aurons mené à bien la transition comptable vers Paheko.
Nous avons fait le choix fort de quitter Facebook, après avoir constaté que nous ne faisions que fournir de la matière première à cette entreprise afin qu’elle puisse placer ses annonces, les fils d’actu ne ressemblent plus à rien de nos jours, l’information n’arrive même plus jusqu’au destinataire. Nous avons regardé du côté de Mastodon mais ce n’est pas vraiment d’un réseau social virtuel dont nous avons besoin mais d’un espace ou pouvoir partager nos évènements et convier les publics. On pose tout de même nos évènements autour du numérique sur l’Agenda Du Libre.
Questionner notre communication nous pose grandement la question de l’attention disponible de manière générale.
Il y a aussi des considérations techniques plus ou moins abstraites. Dans l’univers des e-mails la chasse est vraiment faite aux indépendants par les entreprises qui monopolisent le domaine, les e-mails peuvent ne pas arriver à destination sans raison valable, une exclusion arbitraire peut tomber à tout moment et empêcher tous les e-mails d’arriver à destination. Je crois que les e-mails ne sont plus utilisés à bon escient de nos jours, cela en fait un système sur-sollicités, sous pression. Malheureusement c’est encore un canal précieux pour la communication.
Jusqu’à il n’y a pas si longtemps on ne trouvait aucun C.H.A.T.O.N.S. dans la catégorie des campagnes d’e-mailing et ceux qui le proposent maintenant, n’assurent pas livraison des e-mails, seulement leur création.

Quels étaient vos moyens humains et financiers pour effectuer cette transition vers un numérique éthique ?

Alors concernant le matériel nous avions obtenu une subvention de la région Bourgogne-Franche-Comté pour l’achat du NAS et du PC qui accueillerait la base de données d’images.
Nous avons aussi été soutenus par la CAF, une de nos partenaires pour le faible investissement qu’a représenté l’achat du serveur d’occasion de la phase 2.

Pour le travail humain la première phase de mise en route s’est faite bénévolement, la place pour l’expérimentation est grande ici au Lion d’Or, cela correspond aussi à la période COVID ou j’avais pas mal de temps disponible. Pour la deuxième phase nous avons obtenu un financement du FNADT (Fonds National d’Aménagement et de Développement du Territoire) pour mon poste à 1/4 de temps (35h/mois) pour le « développement des usages du numérique » qui comprenait un temps dédié à la mise en place de ces nouveaux outils entre-autres.

 

Image

Étienne lors d’un accompagnement individualisé. (source : site Les Accords du Lion d’Or)

 

Est-ce que votre dégafamisation a un impact direct sur votre public ou utilisez-vous des services libres uniquement en interne ? Si le public est en contact avec des solutions libres, comment y réagit-il ? Est-il informé du fait que ça soit libre ?

Comme je le disais plus haut, c’est vraiment ce qui a fait notre force pour cette transition, le fait que je sois présent sur plusieurs projets ici a permis un accompagnement régulier des salariés et des autres utilisateurices.
Je mène aussi un atelier mensuel que nous avons appelé Causeries, ou nous traversons de nombreux sujets autour du numérique et où j’ai régulièrement l’occasion de présenter nos outils et détailler leur fonctionnement.

Image

La causerie informalion (Source : site Les Accords du lion d’Or)

Quels conseils donneriez-vous à des structures comparables à la vôtre qui voudraient se dégafamiser aussi ?

Cette dégafamisation a principalement un impact interne à l’association. Nous avons un peu communiqué sur le sujet mais notre public est peu confronté à ce changement, quelques dossiers partagés, quelques sondages, surtout à l’adresse des adhérents. Les retours sont neutres.
C’est quelque-chose que l’on pourrait voir changer, nous n’avons eu absolument aucuns soucis jusqu’à présent et nous débattons de la possibilité d’ouvrir des accès à d’autres structures proches ou aux adhérents. Faire comprendre la nature expérimentale du projet et ramener sur le devant le fait que les services proposés sont à échelle modeste et donc faillibles, est une question à ne pas prendre à la légère mais correspond intégralement aux valeurs de l’association, « parfaitement imparfait » disons-nous souvent ici. Ramener cette faillibilité c’est remettre en question nos usages, la dépendance que nous avons à nos outils et trouver des solutions de repli, retrouver une échelle de temps plus souple sont des valeurs que nous portons pour l’avenir.

Image

Un mot de la fin, pour donner envie de migrer vers les outils libres ?

En ce tournant vers le monde du libre et en acceptant les remises en questions liées, on gagne en liberté, de moyens, de mouvements et en humanité.
Et n’hésitez pas à venir faire un tour au Lion d’Or pour en discuter !

❌