PROJET AUTOBLOG


Free Software Foundation Europe

source: Free Software Foundation Europe

⇐ retour index

Digital Markets Act - Device Neutrality must be consolidated in the legislation

lundi 13 décembre 2021 à 00:00

Digital Markets Act - Device Neutrality must be consolidated in the legislation

On December 15, the Digital Markets Act, the EU's comprehensive regulatory package for internet platforms, will go through plenary voting at the European Parliament. The FSFE calls for consolidating Device Neutrality to enable fair and non-discriminatory use of Free Software in digital devices.

The European Union is about to introduce a major overhaul of Internet legislation with the Digital Markets Act (DMA). After successful committee voting on 22 November, the European Parliament will conduct plenary voting on 15 December. The FSFE advocates Device Neutrality as a fundamental step to achieve a contestable, open, and competitive digital market in the EU and urges the European Parliament to secure this principle in the final voting.

Device Neutrality - fostering Free Sofware in an end-user centric digital market

The DMA focuses on "gatekeepers", understood as very large tech companies that have control over large parts of digital services, such as search engines, social networking services, messaging services, operating systems, and online intermediation services. While digital devices are a ubiquitous reality in all aspects of life, our control over the hardware and software running on them is increasingly being limited. Device Neutrality is the policy concept that users should have the right of non-discrimination of the services and software they use, based on platform control by hardware vendors, manufacturers, and service providers. The goal is to enable users to bypass gatekeepers and enable a fair and non-discriminatory use of Free Software in devices.

After many iterations and amendments, the DMA's final text submitted to the plenary voting incorporates the following Device Neutrality principles, which the FSFE urges the European Parliament to consolidate in the plenary voting:

Device neutrality principles

Support FSFE

The FSFE is looking for an office assistant

vendredi 10 décembre 2021 à 00:00

The FSFE is looking for an office assistant

We are looking for an office assistant for 20-25 hours per week in our Berlin office. As part of our office management team you will organise the FSFE's day-to-day operations. Your job will be to provide clerical support to our staff and coordinate daily administrative activities.

Our ideal candidate has experience as an office administrator, secretary, event organisator, or another relevant administrative role. As a family friendly organisation we can offer flexible working hours.

About the FSFE

Free Software Foundation Europe is a charity that empowers users to control technology. Software is deeply involved in all aspects of our lives and it is important that technology empowers rather than restricts us. Free Software gives everybody the rights to use, understand, adapt, and share software. These rights help support other fundamental freedoms like freedom of speech, press, and privacy.

The FSFE helps individuals and organisations to understand how Free Software contributes to freedom, transparency, and self-determination. It enhances users' rights by abolishing barriers to Free Software adoption, encourages people to use and develop Free Software, and provides resources to enable everyone to further promote Free Software in Europe.

We are involved in many activities in the legal, economic, political and technical areas around Free Software. Our work is made possible by a community of volunteers, supporters, donors, and staff. The office assistant's job will be to be the administrative backbone of our operations.

Main responsibilities

Qualifications

Attitude

We are looking for a reliable, well-organised, and punctual team player who will be part of our administrative backbone in Berlin and thus support the organisation in making the world better for future generations.

How to apply

To apply, please send a maximum one-page cover letter and a maximum two-page CV (only PDFs are accepted) by email to jobs@fsfe.org, with the subject "organisational wizard". Please do not include pictures of yourself in the application.

Your personal data will be deleted 3 months after we have made our decision. The closing date for applications is Sunday, 2 January 2022.

Free Software is meant to serve everyone regardless of their age, ability or disability, gender identity, sex, race, nationality, religion or sexual orientation. Hence, we encourage applications from all backgrounds and promise to judge all applications on merit, without reference to any of the characteristics listed. To promote diversity and equality in the Free Software community, we shall give preference to applicants who identify as part of a traditionally marginalised demographic in technology for applications of equal strength.

Support FSFE

20 Years FSFE: Interview with Vincent Lequertier on AI

jeudi 9 décembre 2021 à 00:00

20 Years FSFE: Interview with Vincent Lequertier on AI

In our sixth birthday publication we are interviewing Vincent Lequertier about crucial aspects of artificial intelligence, such as its transparency, its connection to Open Science, and questions of copyright. Vincent also recommends further readings and responds to 20 Years FSFE.

A PhD candidate at the Claude Bernard university in Lyon who researches artificial intelligence for healthcare, Vincent supports software freedom and volunteers for the FSFE in his free time. He has been a part of the System Hackers, the team responsible for the technical infrastructure of the FSFE, for many years. His contribution was valuable in setting the foundation for the for the good state that the FSFE's System Hackers team is today. Vincent is also a member of the FSFE's General Assembly, and participates in the 'Public Money? Public Code!' campaign. In our interview, Vincent shares his thoughts answering questions about the current state of AI and its future implications.

Interview with Vincent Lequertier

FSFE: You are deeply involved in the field of artificial intelligence. How would you explain to a 10-year-old what AI is?

Vincent Lequertier: A few years ago I was a speaker at a local radio station, and sometimes I was responsible for mixing the audio. At the station, there were several inputs: the mics of the radio speakers (mine included), the music, the jingles, and so on. And then there was the output broadcast to the radio listeners. Between the inputs and output there was the mixing table, with its uncountable knobs and sliders. I needed to adjust the knobs and sliders so that the inputs were well mixed together, thus producing an output that sounded nice to the listeners. At the time of writing, an AI works just like that. It automatically adjusts the numerous parameters of a digital, virtual mixing table. Once put through it, the inputs produce a satisfying output according to a predefined definition of success (that the sound was nice in this analogy).

A PhD candidate at the Claude Bernard university in Lyon who researches artificial intelligence for healthcare, Vincent supports Software Freedom and volunteers for the FSFE in his free time.

You are advocating for accessible and transparent AI. According to your research, what would you say are the necessary requirements to make sure that programs using artificial intelligence are accessible and transparent?

Reusing AIs makes sense because they are costly to develop and train, both in terms of human and computer resources. Additionally, training AI models demands a lot of data which are particularly hard to obtain and work with. Therefore, being able to reuse an AI is important, as it saves time and potentially scarce resources. Moreover, making an AI available to others fosters innovation by facilitating collaboration. I think a fundamental requirement for AI accessibility is Free Software, because AIs licensed as Free Software (also known as Open Source) are inherently accessible. Other requirements can be Open Standards and Open Data. AI models should therefore be published and freely accessible.

Transparency in AI is the ability to understand and interpret the output coming from it. Although given the complexity of today's AI systems transparency can be hard to obtain, it is an important characteristic as it fosters trust. Being able to understand why a given output was produced, and what part contributed the most to it, increases confidence in the model and makes it easier to debug. Moreover, understanding the role played by each input can help data-driven policy making. For example, in healthcare, understanding the most important factors impacting the quality of patients' care for a disease can validate or change healthcare practices. Free Software is a key part of transparency because it allows everyone to use the AI and analyze its predictions to better understand them.

How can we make sure that inequalities in our current societies do not pass on to AI data training? How can we assure that AI results are fair?

As AI is really good at magnifying existing inequalities found in the data used for its training, fairness issues will creep into AI. Detecting those issues in the dataset and in the AI's output is therefore critical. However, simply removing data that might be a source for unfairness (e.g. a training dataset variable that is not representative of the data used once the model is put in production) may not always work, because these data might be correlated to other attributes in the dataset which would need to be removed as well. Completely removing any potential inequality may therefore remove a lot of data from the dataset, potentially limiting the ability of the AI to properly address the problem it has been designed to solve. Inequalities therefore come from badly constructed datasets, and advanced methods are required to circumvent them.

Data related to COVID-19 are public, and the most popular website to visualize these data as well as other tools are Free Software.

To detect fairness issues, a definition of fairness must be decided upon. For example, fairness may be defined as whether pairs of similar individuals get similar predictions (individual fairness), or it may be defined as whether predictions are similar across a majority and minority group according to some characteristics (group fairness). This fairness measure may be computed once the AI has been trained to identify potential unfairness, or may be computed during the AI training so that it can take the notion of fairness into account when it adjusts its parameters.

Free Software is also important here, as it allows everyone to check for fairness issues, whether by inspecting the source code or by running the AI directly and analysing its predictions.

Vincent Lequertier presents crucial points about AI during an FSFE Community meeting in Bolzano. Italy, 2019.

Your research focuses on healthcare, a field that has universally raised the question of supporting Open Science. To what extent are health metrics and biometrics open? Is artificial intelligence for healthcare a big and globally collaborative aim or independent and competitive?

Well, it depends! Because of security and privacy, access to individualized healthcare metrics is often restricted and each study using them must be approved by a ethical committee. However, aggregated statistics may be widely available. For example, the website data.gouv.fr has a section dedicated to healthcare. Also, the data related to COVID-19 are public, and the most popular website to visualize these data as well as other tools are Free Software.

The openness and collaborative aspects of research on AI will improve, partly because scientific journals encourage researchers to share all the research materials, including source code, and also because funding institutions can also ask them to do so. [...] I also think that the line of reasoning around our "Public Money? Public Code!" campaign applies for AI research.

However, it should be noted that data without enough granularity can reduce the AI's performance in healthcare, as, just like humans, an AI application needs to have detailed information, especially if the goal of the AI is to make predictions at the individual level. Because healthcare outcomes are so dependent on context, prediction abilities depend on specific healthcare situations. More open data and more Free Software (i.e. Open Science) make it easier to collaborate. A shared dataset released under a Free Software licence creates a "playground" where AI models can be easily compared and where we can create benchmarking tasks, such as hospital length of stay prediction. Without a proper benchmarking task, finding methodological improvements is harder. An example of an open dataset for healthcare is MIMIC. Also, a lot of papers about AI research are freely available on arxiv.org. I think the openness and collaborative aspects of research on AI will improve, partly because scientific journals encourage researchers to share all the research materials, including source code, and also because funding institutions can also ask them do do so. For example the Horizon 2020 program of the European Union values Open Science.

I also think that the line of reasoning around our "Public Money? Public Code!" campaign applies for AI research.

A common expectation for the future of AI is that it can have abrupt economical and societal impact by making many job positions redundant. Do you see this as a possibility for the upcoming years? If so, is there any practice that could alleviate these consequences? Would Free Software be one?

I think AI has come a long way in the last ten years. It is more and more able to organize and structure information. The fields which have made the most impressive progress are natural language processing (i.e. tasks involving text such as sentiment analysis) and computer vision (i.e. tasks involving images such as image classification). In natural language processing, deep learning models can semantically understand words and documents as well as the relationships between them. So I think the jobs where AI will be able to assist us (I consider things only from a technical point of view here) are the jobs dealing with a lot of structured information that needs to be understood, processed, and memorized, as AI is becoming better at this than us. For example, AI-based software has shown good results in assisting in radiology, legal document analysis, and programming (see next question). So it's possible that AI makes people more efficient, which would reduce the amount of human work required. However, this work would require skills where AI does not work well at the time of writing, such as creativity or emphatic and thoughtful communication.

The jobs where AI will be able to assist us (I consider things only from a technical point of view here) are the jobs dealing with a lot of structured information that needs to be understood, processed, and memorized, as AI is becoming better at this than us. For example, AI-based software has shown good results in assisting in radiology, legal document analysis, and programming.

If AI is bound to get better, and will at some point have the capacity to completely automate some work, transparency and fairness can only become more and more important. Although not sufficient, Free Software is a big part of what helps putting strong safeguards in place.

However, I don't think it's up to the scientific community to design policies around employment. Putting together a proof of concept or finding a novel theory that could automate some work is not a reason for implanting it in everyday lives. In the past years, the EU has already had to deal with AI applications that are impressive technically but raise ethical concerns. For example, the Clearview AI facial recognition platform has been judged illegal in some EU countries, and citizens have the right to opt out from this technology. The next few years will be important with regard to AI ethical concerns, and the upcoming EU Artificial Intelligence Act might play a big role in it.

And finally, although I'm not a historian, I think that over the last centuries we have made tremendous technological progress and society has always evolved along with it. Thinking about the past challenges of technological improvements would help us to understand whether they would be different this time around, and how to deal with them as best as we can.

FSFE Community Meeting during Rencontres mondiales du logiciel libre conference in Strasbourg. France, 2018.

What legal issues do you think will be raised regarding AI in the next ten years? Would it be issues of ownership or responsibility? For example, we are already seeing ethical and technical aspects of the AI ownership in Github's Copilot. We are interested to know what the upcoming crucial questions are, according to you.

Issues around ownership and responsibility will be very important, and Copilot is a prime example of that, where the fundamental question is whether AI creations can be considered as novel ideas, and, if they do, whether they are copyrightable on their own. Specifically on Copilot, the fact that a code completion tool may yield straight copies of licensed work can be problematic, as, at the time of writing, the AI does not know the licence under which the source of autocompleted code is released, and how the licence should be respected. For example, to the best of my knowledge, it is not clear whether code autocompleted by Copilot originally released under the GNU Public Licence makes the rest of the project a derivative work. Being able to freely use source code often comes with obligations that need to be fulfilled, regardless of whether it is accessed by an AI or a human being. Our REUSE project, which aims to make it easier to programmatically understand how a project and its diverse components are licensed, may help building licensing-aware programming tools. The same legal troubles apply to other models able to generate content, in domains such as in painting or in music production.

Another legal issue is with patents, where the question of whether an AI can be a patent author is still undecided. In the UK and EU, a patent whose inventor was an AI was rejected because they considered that AI does not have a legal personality and cannot have a legal right over its output. But a couple of months ago, the first patent which lists AI as the inventor was approved.

The fundamental question is whether AI creations can be considered as novel ideas, and, if they do, whether they are copyrightable on their own.

Is there any book about artificial intelligence you would like to recommend to our readers?

I can't recommend "Genesis" from Bernard Beckett enough. It is a small novel showing a philosophical debate around the questions of what it means to be human and of whether machines can have consciousness. The classic "I, Robot" from Isaac Asimov also raises many questions that make a lot of sense today (it was published in 1950!) If we are building autonomous robots with some freedom of action, what safeguards must we put in place? The book is really about how to ensure AI works as intended.

You have been a part of the FSFE for several years. What is an important thing that you learnt from this experience?

I learnt that Free Software can be viewed from a lot of different angles and is not only a technical topic. This translates into the diversity and breadth of our community. This diversity is a huge strength.

And what is a story that still makes you smile when you remember it?

My first FOSDEM in 2019. I met some awesome people from our community. That was really heartwarming.

As a last question, what do you wish the FSFE for the next 20 years?

I wish the FSFE will be able to tackle the challenges ahead. The next years will be full of innovations that will make technology even more ubiquitous in our lives. I hope we will be able to keep spreading the word about Free Software and the values behind it.

Being able to freely use source code often comes with obligations that need to be fulfilled, regardless of whether it is accessed by an AI or a human being. Our REUSE project, which aims to make it easier to programmatically understand how a project and its diverse components are licensed, may help building licensing-aware programming tools.

FSFE: Thank you very much!

About "20 Years FSFE"

In 2021 the Free Software Foundation Europe turns 20. This means two decades of empowering users to control technology.

Turning 20 is a time when we like to take a breath and to look back on the road we have come, to reflect the milestones we have passed, the successes we have achieved, the stories we have written, and the moments that brought us together and that we will always joyfully remember. In 2021 we want to give momentum to the FSFE and even more to our pan-European community, the community that has formed and always will form the shoulders that our movement relies on.

20 Years FSFE is meant to be a celebration of everyone who has accompanied us in the past or still does. Thank you for your place in the structure of the FSFE today and for setting the foundation for the next decades of software freedom to come.

Support FSFE

FSFE is hiring a working student specialised on websites

lundi 6 décembre 2021 à 00:00

FSFE is hiring a working student specialised on websites

We are looking for a working student to support our work to empower people to control technology. The person will work 10-15 hours per week and will maintain and improve the FSFE's websites. Applicants have to be enrolled in a German university and can work remotely.

About the FSFE

Free Software Foundation Europe is a charity that empowers users to control technology. Software is deeply involved in all aspects of our lives and it is important that technology empowers rather than restricts us. Free Software gives everybody the rights to use, understand, adapt, and share software. These rights help support other fundamental freedoms like freedom of speech, press, and privacy.

The FSFE helps individuals and organisations to understand how Free Software contributes to freedom, transparency, and self-determination. It enhances users' rights by abolishing barriers to Free Software adoption, encourages people to use and develop Free Software, and provides resources to enable everyone to further promote Free Software in Europe.

We are involved in many activities in the legal, economic, political and technical areas around Free Software. Our work is made possible by a community of volunteers, supporters, donors, and staff. The web working student's job will strengthen the public perception of the FSFE and allow more people to work effectively with the web presences.

Group picture of our 2019 web-a-thon in Frankfurt

Main responsibilities

Qualifications

Attitude

We are looking for a reliable, well-organised member of our technical teams who is keen to learn about old and new technologies. You support the whole organisation in its mission. Long-term thinking, efficiency and effectiveness are more important to you than the newest cool technology on the block.

When people have technical questions, you can support them and also have interest in explaining them the underlying technology in an adequate language.

Working time and compensation

The desired working time is 10-15 hours per week but can be discussed. You can work from anywhere in Germany, but should be willing to travel 1-2 times a year to staff and web-team meetings. The salary is based on the currently applicable minimum wage in Germany but can be higher depending on your experience. A mandatory requirement due to administrative reasons is that you are enrolled as a student at a university in Germany, and have a working permit for Germany, for example by EU citizenship.

How to apply

To apply, please send a maximum one-page cover letter -- including the desired hours per week -- and a maximum two-page CV (only PDFs are accepted) by email to jobs@fsfe.org, with the subject "website student" and your name. Please do not include pictures of yourself in the application.

Your personal data will be deleted 3 months after we have made our decision. The closing date for applications is Sunday 31 December 2021.

Free Software is meant to serve everyone regardless of their age, ability or disability, gender identity, sex, race, nationality, religion or sexual orientation. Hence, we encourage applications from all backgrounds and promise to judge all applications on merit, without reference to any of the characteristics listed. To promote diversity and equality in the Free Software community, we shall give preference to applicants who identify as part of a traditionally marginalised demographic in technology for applications of equal strength.

Support FSFE

Infrastructure living the ideals of software freedom

vendredi 3 décembre 2021 à 00:00

Infrastructure living the ideals of software freedom

Can organisations with limited resources be digitally sovereign and still provide modern services? It is not trivial, but the FSFE proves it's possible. Take a deep dive with us into our infrastructure to learn how we run all the different services within the FSFE and cope with numerous challenges. A story non only for techies.

Charity, non-profit organisations run into limits every day: personnel, budget, time, and the pressing question how to use donations most efficiently. When it comes to technical infrastructure, many organisations unfortunately decide to outsource and use proprietary, non-free services. By this, they give up software freedom and thereby digital sovereignty and independence.

Since its founding more than 20 years ago, the FSFE has been pursuing the opposite way. Right from the start, we have relied on Free Software although it sometimes meant not being able to use and offer trendy services. Also, given the limited resources, we constantly have to choose between useful features and maintainability.

And still, neither is our infrastructure perfect nor is it 1:1 transferable to other organisations. But we think it's important that organisations exchange their experiences and learning, especially when it's about something as important as software freedom.

Therefore, let us take you on a journey through our infrastructure and its principles, from shiny user interfaces of our services, crossing the virtualisation methods and monitoring, down to the bare metal servers they are running on. This is a story not only for techies, but for everyone interested in making or keeping an NGO independent from proprietary service providers.

One team and its principles

All of the FSFE's infrastructure is managed by the System Hackers. Only a few years ago, in a time of larger technical debt and restructuring, the team was only three people. Fortunately, since then we have experienced a steady growth of membership. Today, it is a healthy team consisting of 9 active volunteers, complemented by two staff members who dedicate some of their working time to the team's tasks.

Picture from the 2020 meeting of the System Hackers in Lyon

With a team this size it was crucial to define the most basic principles of this team. They form the basis of the System Hackers' goals: as much control as possible over services and servers by using 100% Free Software, internal and external transparency, and bearable complexity, and at the same time providing useful features for the various FSFE teams and the whole community.

Aside from purely asynchronous work, emails, and chat, the System Hackers also met at least once per year in pre-pandemic times, and continue doing that in virtual form. During these meetings, we were able to tackle more complex decisions and technical changes efficiently, but also just enjoyed non-technical conversations and fun activities. The team is coordinated by us, the authors of this text, Albert and Max, who also maintain a large number of services and systems.

Services, services everywhere

The FSFE's infrastructure is very service-oriented. Volunteers and staff rely on basic functionality like sending and receiving email or exchanging files, but also on a website fed by a version control system, a wiki, or video chat systems. To give an example for the complex interconnection of different components, just drafting and releasing this news item involved at least 12 services that have to seamlessly work together.

The currently most crucial and used services contain Mailman for mailing lists, or Gitea as our Git version control system. To allow sharing and saving knowledge our Wiki Caretakers maintain MoinMoin, while Björn takes care of Nextcloud to share files, coordinate tasks, and collaboratively edit documents. We run our own BigBlueButton and Jitsi instances for video conferencing, and XMPP/Jabber for text-based chats. Very recent service additions are Matrix as another chat service, initiated and maintained by Michael, and Peertube for hosting and sharing our videos on own infrastructure, made possible by Alvar.

The list of services is much larger and also contains fundamental systems like the Account Management System and Community Database developed by Reinhard, our own DNS servers, or Drone as our CI/CD system that processes data from Gitea, checks them, and deploys them on other servers eventually.

Needless to say, the team regularly receives requests to provide additional services. Here, the challenge is to make a careful selection based on available resources (computing, space, volunteer time) and estimated use for the organisation, and evaluating whether a solution is well-maintainable, not largely overlapping with existing services, and generally leaving a good impression.

Sometimes that also means we have to test solutions in practice over a longer period of time. Real-time editing of documents is a good example for that, for which we currently have multiple possibilities available. Longer documents are often edited as ODF files via Collabora Online attached to Nextcloud, but some editors prefer Etherpad or use Git directly. All solutions have advantages and downsides, and finding a good path between having diverse options on one side, and tool overload on the other is anything but trivial.

Virtualisation and deployment

While the FSFE owns dedicated servers in actual racks (we will come to that later), all services run in some sort of virtualisation. In total there are 43 virtual machines distributed over different data centres at the time of writing this article. Some have a purely internal role, for instance being a gateway for other virtual machines or assisting web services with obtaining TLS certificates.

An overview of the currently running virtual servers of the FSFE, and their distribution over the different clusters.

Some others, in turn, themselves host a number of diverse services. Since 2017 we have been using Docker as a container engine. That has not been an easy choice since the technology adds a lot of complexity and sometimes requires stunning workarounds to be operated in a secure fashion. On the other hand, especially for smaller services or larger self-coded tools, it is great to spin them up quickly, test and deploy them via our Continuous Integration system, provide a more or less uniform local development environment, and maintain an (admittedly limited) reproducibility of configurations.

We are regularly evaluating alternative engines that provide a more seamless rootless mode, are still compatible with our CI/CD system (Drone) and reverse proxy, and ideally do not require a major rewrite of existing deployment code. Also, here again, it is important for the System Hackers that at least two members understand a high-priority technology in depth.

To bootstrap virtual machines and deploy non-container services in a reproducible way, we rely a lot on Ansible, a provisioning and configuration management tool. While Ansible deployments may also have their shortcomings, we appreciate the infrastructure-as-code approach that can be executed from any computer and does not require a central server. Meanwhile, only the minority of services are deployed via neither Ansible nor Docker which makes understanding existing infrastructure, onboarding new volunteers, and documenting changes much easier.

The all-seeing eye and uniformity

Dozens of servers and services: how do you know if there is a problem with one of them? We have to admit that up until two years ago we sometimes only learnt about a crashed server via an email from a random friendly community member. Now a monitoring system based on Icinga2 takes care of this. Currently 50 hosts and 690 services are continuously checked, for example for pending upgrades of the operating system, systemd services, failed backups, disk space, or TLS certificate validity.

This is eased by other parts of our strategy: except 4 virtual machines, all run on Debian GNU/Linux. After initial creation, a new machine will experience a baseline setup taking care of fundamental security settings, monitoring, backup, and automatic upgrades. Thanks to this, maintenance of a server is mostly limited to the service it is running, and other improvements can be applied to a large number of hosts automatically within a few minutes.

To further ease management and maintenance, we sometimes write our own tools. For instance ssh-key-distributor provides a simple interface and deployment method to manage and document access via SSH on our servers. Or docker-utils which is tailored to our Docker infrastructure and takes care of analysing and upgrading Docker images and containers. Both tools have been created by our working student Linus. You can find more tools and generally most Ansible/Docker deployment code in the System Hackers' Git organisation.

Bare metal servers

Unlike the current trend of the IT industry, we are proud to run the vast majority of services on our own physical servers. This guarantees the most sovereignty, data security by full disk encryption, and technological independence for us. To increase resilience, we bundle three servers each into a Proxmox cluster with Ceph storage, so if one physical server crashes a virtual machine is just moved to one of the two other servers in the cluster.

As an additional safety net, the three clusters and a solo machine are spread over four different data centres which kindly donate the colocation to us.

However, this is only possible thanks to a fortunate combination of conditions. First of all, we are lucky to have Albert with us who has a lot of experience with, among various other areas, Proxmox, Ceph, and the depths of networking. Then, we have the kind support of the data centres providing colocation as well as hardware donors, and the FSFE supporters that contribute financially. And we also profit from a more or less identical setup on all four sites which makes maintenance a bit easier. But still, we are considering giving up the cluster containing the oldest servers as well as the solo physical machine to reduce work and complexity.

Challenges behind and ahead

Over the course of the years, we managed to overcome many challenges: technical debt, antique software that blocked operating system upgrades, lack of hardware resources, fatal crashes of single points of failures, and hard technical decisions about how to develop the infrastructure further. In one of these hard times, our back-then intern and since then System Hacker Vincent played an important role and helped set the foundation for the good state we are in today. Despite all preparation and evaluation, we have made many mistakes, but most importantly we have learnt a lot by them.

Facing us right now are new hurdles. For example, with the high amount of servers, we can no longer give every virtual machine a dedicated IPv4 address. Unfortunately, many technologies and internet services, even large proprietary and supposedly professional companies, still do not support the more modern, future-proof, and already 20 years old IPv6 protocol. This requires us to fiddle around with a few hacks like reverse proxies, container discovery services, NAT, and VPNs.

Another interesting decision ahead is the one of communication channels. While plain-text email and, since 2004, XMPP/Jabber have formed the de-facto standard within the FSFE, many people meanwhile prefer Matrix, Discourse, or still the traditional IRC. While we see advantages and disadvantages for all of them, we also want to avoid fragmentation of our community. This is not a pure technical question, but a great example of the need for good inter-team communication and decision-making.

Last but not least, we have a few technologies that are head scratchers for us. Let's take Mailman 2 as an example that has powered our 116 mailing lists for years. Unfortunately, the project is no longer actively developed, and the successor and its alternatives all have serious downsides. Here, we need to conduct a careful evaluation and many tests, and eventually find the best solution in the mass of imperfect options.

With all that said, we would like to express our thanks to the many Free Software projects and their developers out there. They grant us the ability to choose from different solutions, they form the basis of our infrastructure, and they provide astonishing solutions that make our lives easier every day. It is a pleasure to be part of this large community.

Why all of this?

As you can see, the technical infrastructure of our organisation is anything but boring or simple. This is not only due to the size of the FSFE and its community, but also due to our own high standards: living software freedom in practice and maintaining as much technical independence and sovereignty as possible. At the same time, we care for technical accessibility to also allow non-technical contributors to interact with our services. That sometimes requires extra work and tools, but we are convinced that it is worth it.

All of this depends on the dedication and long-time commitment of many people, and is fed by its productive use and the feedback of the whole FSFE community. And it is only possible thanks to the FSFE's supporters who enable us to invest resources in a fully Free Software infrastructure. If you share this ideal, please consider a donation.

Support FSFE