PROJET AUTOBLOG


Free Software Foundation Europe

source: Free Software Foundation Europe

⇐ retour index

Mise à jour

Mise à jour de la base de données, veuillez patienter...

Ready for foss-north 2023?

mercredi 12 avril 2023 à 01:00

Ready for foss-north 2023?

The FSFE is organising a track covering political and legal aspects of Free Software at foss-north; the conference in Gothenburg that brings together Nordic Free Software communities. It will take place on April 24 and 25 followed by the community day that will take place on April 23. It is time to register and get your tickets!

This year's foss-north will take place on April 24 and 25, following a community day on April 23. It will be a local, face-to-face event. While the past foss-north has focused on the technical aspects of Free Software, this year there will also be room for presenting political, legal, and social issues related to software freedom.

Join the Conversation

The FSFE is co-organising a track on political, social and legal issues around Free Software in the Palmstedt Room.

It will be two days full of interesting topics such as license compliance with AI assisted coding, municipal collaboration on Free Software, enabling Free Software through procurement projects, the role of Free Software for citizen participation and more. Lina Ceballos, Policy Project Manager at the FSFE, will present our position on the Interoperable Europe Act in a keynote.

If you want to know more about the speakers and the talks, you can check the whole schedule here.

Community Day and Social Event

The Communitiy Day is taking place on Sunday April 23. This is a day of communities activities taking place around various locations in Gothenburg. Do you want to know how to get creative with Free Software or want to join us for a chat during our social dinner? Join us and please register your attendance.

Do you want to join us sharing your Free Software projects with the community? It can be a workshop, a development sprint, an install-fest or something completely different - you decide. Simply get in touch with johan (at) foss-north.se for more details. All the organising participants will get a ticket discount for the Conference on April 24 and 25.

Don’t forget to register and to get your tickets!

Please remember that you need to register to take part in the activities of the Community Day. If you want to take part in the conference, don’t forget to get your tickets here!

See you in Gothenburg!

Support FSFE

EU: Liability, Interoperable Europe Act +++ Partial Router Freedom in Greece

mardi 4 avril 2023 à 01:00

EU: Liability, Interoperable Europe Act +++ Partial Router Freedom in Greece

In April’s newsletter we discuss EU proposals affecting Free Software: the introduction of liability rules for software and the Interoperable Europe Act. Greece secures Router Freedom but excludes fiber connections.

EU: Proposed liability rules will harm Free Software

The EU is currently debating the introduction of liability rules for software, including Free Software. The relevant proposals are the AI Act, Product Liability Directive (PLD), and Cyber Resilience Act (CRA). The way they are, all proposals will harm the Free Software ecosystem and thus the society and the economy.

We, therefore, propose a solution that will lead to more security while safeguarding the Free Software ecosystem. Liability should be shifted to those deploying Free Software instead of those developing Free Software, and those who significantly financially benefit from this deployment should make sure the software becomes CE-compliant.

Alexander Sander, FSFE Policy Consultant, presenting the FSFE position on liability in a public hearing in the European Parliament.

The Interoperable Europe Act needs a “Free Software first” approach

The Interoperable Europe Act (IEA) aims to assist public administration to share, reuse, and integrate information technology and data across borders. Although the proposed IEA has the potential to be a game changer in allowing the EU to guide with example in the digitalisation path without having to reinvent the wheel, several problematic aspects stand in the way, including the following:

Greece secures Router Freedom but excludes fiber connections

Check here the status of Router Freedom in your country

Routers and modems are gateways to the Internet. As with any other digital devices, consumers should be able to choose such an important piece of equipment. The Greek regulator, EETT, has adopted new rules introducing Router Freedom in the country. Since 2021, the FSFE has been working with policymakers to protect the interests of end-users. Civil society and industry organisations backed the FSFE and contributed positively to this new law.

We regret that EETT excluded fiber networks as a default for Router Freedom. Although end-users can require a separation of the optical network equipment and routers, this restricts users from plugging their fiber router directly into the network. Even so, Greek consumers are better served by a clear framework for Router Freedom. We encourage the regulator to make the new rules effective; freedom of terminal equipment requires constant monitoring of internet service providers’ commercial practices.

Young Hackers' Fixes

While reading novels and watching movies on his laptop, David thought how convenient it would be to turn pages or pause the video with a wave of the hand and made it happen. Andrei added clipboard functionality to ‘bemenu’, a dynamic menu program. Meet Andrei and David who both participated in the first edition of the Youth Hacking 4 Freedom competition.

Women’s Day tribute

Thank you to everyone who is making the tech sector more inclusive! Let’s continue working together to achieve gender parity and embrace equity. Moreover, Free Software can help close the gender gap. The use and development of Free Software, by providing accessible digital tools, support the process of digital transformation and provide women and other under-represented groups with digital skills and the opportunity to develop their own software according to their needs.

Ada & Zangemann book

Author reading in Somerville MA, USA, a few weeks ago

Several weeks ago, Matthias Kirschner, Ada & Zangemann’s writer and FSFE president, talked about the inspiration behind this book and the need to raise awareness about Free Software. The English version is already available in the US and it can be pre-ordered in Europe. The book is under a Creative Commons license. Feel free to check if our volunteers are already translating it into your native language. You can even join them!

Upcoming events

Contribute to our Newsletter

If you would like to share any thoughts, pictures, or news, please send them to us. As always, the address is newsletter@fsfe.org. We're looking forward to hearing from you! If you also want to support us and our work, join our community and support us with a donation or a monthly contribution. Thanks to our community and all the volunteers, supporters, and donors who make our work possible. And thanks to our translators, who enable you to read this newsletter in your native languages.

Your editor, Fani Partsafyllidou

Support FSFE

The Interoperable Europe Act needs a “Free Software first” approach

jeudi 23 mars 2023 à 00:00

The Interoperable Europe Act needs a “Free Software first” approach

The Interoperable Europe Act (IEA) aims to assist public administration to share, reuse and integrate information technology and data across borders. Clear rules with concrete activities and budget are missing. The role of civil society is overlooked, and there is not yet clear definitions of Free Software and Open Standards.

With the IEA, the EU is aiming to create a dedicated legal framework on interoperability that until now has been non-binding. Interoperability is a core element of the ongoing digitalisation, also of public services. Hence, the interplay among public administration, private sector, and civil society has to be acknowledged as a crucial component to lead Europe into an interoperable ecosystem.

Although we welcome that the European Commission already acknowledges the importance of Free Software (also known as “Open Source”) and Open Standards for interoperability, they are not clearly defined. Moreover, the current text falls short into recognising the role of other stakeholders in the proposed governance approach, such as the case of civil society not only as an expertise provider but also as a decision-making actor. Lastly, the text remains unclear with regard to concrete activities to promote interoperability, and a dedicated budget for such.

Let’s make things clearer

Free Software and Open Standards create the conditions for interoperability. Free Software is crucial when building public services that are accessible for everybody across borders and sectors. Open Standards allow the conditions needed for those systems to be able to communicate with each other enabling the freely sharing of data. These two prevent lock-in and other artificial barriers to interoperability, and promote choice between vendors and technology solutions.

At the moment Free Software and Open Standards are indicated as factors to enhance interoperability, however clear definitions of such are not given. Until now, the lack of definitions and clear actions has led to loopholes not only in the interpretation but also in the implementation of previous digital initiatives. We therefore call upon the legislator to clearly define these two key drivers in this legislation, and take the opportunity to proposed specific actions to promote interoperability by making use of them.

Furthermore, Free Software solutions and Open Standards should be considered the default when it comes to interoperable digital solutions, even more so when those are funded by public money. In line with the proposed text, the“Interoperability assessment”can come in hand when a public administrations aims to procure a new digital solution. The default should be a digital solution that enhances such interoperability based on Free Software. If this is not the case, public bodies must justify, based on this assessment, the reasons to not arrive to such decision. Court of Auditors can play an important role when monitoring such decisions and publishing reports on publicly funded digital systems on a steady basis.

The more the merrier: stakeholder involvement

The main purpose of the public sector is to provide public services that are necessary for the well-being of the society. The involvement of different stakeholders in the IEA should not come into question. The interoperability of the public sector involves the sharing of data and information among different public bodies which can raise concerns among the public. Involving others, specially civil society in the decision making process will not only help to build trust from the public but also to ensure that this regulation is guided by democratic and participatory principles.

When it comes to innovation, it is important to bear in mind that numerous non-governmental organisations are often at the forefront of innovation and can offer new ideas and approaches. Innovation doesn’t only happen in the public sector. Therefore, a larger variety of stakeholders must be included as part of this governance workflow, specially civil society actors.

At the moment the engagement of other stakeholders is reduced to the so called “Interoperable Community”, which aims to provide with expertise and input the actual decision making body, the “Interoperable Board”. We therefore highlight the importance of including others in this board, specially civil society. By allowing a wide community to flourish, the EU could achieve its most ambitious goal of building human-centred digital public services.

“The Interoperable Europe Act is the potential chance the EU has to make a major change in how procurement of digital services is handled. By going on the direction of Free Software first, the EU can assure that tax’s payers money is spent in the most efficient way, while it will create the collaborative ecosystem that is needed to achieve interoperability in Europe” explains Lina Ceballos, FSFE Policy Project Manager.

Network of public administrations for re-using solutions

The IEA can be more ambitious in setting up the proper assistance and the network that public administrations need in the digital implementation of such legislation. Currently, proposals such as trainings are included. However, the text fails to address the scope of such trainings, as well as to highlight the dedicated budget needed for such. There is hereof a clear importance of training - with a proper budget allocation - for civil servants on Free Software technologies, workflows and its impact in transparency and trustworthy interoperable digital infrastructure.

Bringing together best practices is also part of this initiative, and it is included as one of the features that the “Interoperable Europe portal” might offer. However, the promotion of the path leading to those good practices is absent. In this regard, more emphasis on the creation, use, and re-use of Free Software solutions could strengthen the collaborative ecosystem that is needed while bringing public administrations closer and enhancing cross-border collaboration.

Monitoring and evaluation

Monitoring plays a fundamental role within this proposal, specially when it comes to different member states approaching these guidelines. The EU must enable the coordination and knowledge exchange for innovative public procurement procedures among member states along with proper monitoring and evaluation strategies.

In order to implement a proper monitoring and evaluation, the EU needs to make sure to gather and make use of proper indicators and statistics that show first how many of the new digital solutions procured, or in-house developed, have been released under a Free Software licence, and second, how many of the existing digital solutions have migrated into a Free Software solution in order to proceed with the “Interpretability Assessment”.

It is not possible to properly evaluate and monitor, if one does not have a clear understanding of the state of play and its fluctuation over time. This will enable an accurate oversee of the way public funds are being used. Combining this monitoring with the respective reports from the Code of Auditors both in Member States as well as at the EU level will only enrich the procedure.

Conclusion

An open and interoperable digital public sector is critical to addressing the social, economic and political challenges of democratic nations.

The proposed Interoperable Europe Act has the potential to be a game changer in allowing the EU guide with example in the digitalisation path without having to reinvent the wheel over and over again. However, concrete activities, along with a dedicated budget, are needed to support member states, and local administration all over Europe. Much clearer definitions of the key elements of this digital ecosystem must also be included. If the interoperability of digital public services is to keep the interest of people at its centre, their involvement and agency in such processes must guide these efforts.

This legislation is a potential opportunity to close the existing loopholes as well as define clear monitoring and evaluation indicators while laying the ground for the proper budget allocation needed for these efforts. This is, indeed, the legislation where Free Software and Open Standards must lead the way in the design and delivery of accessible and open public digital services.

Support FSFE

EU: Proposed liability rules will harm Free Software

jeudi 23 mars 2023 à 00:00

EU: Proposed liability rules will harm Free Software

The EU is currently debating the introduction of liability rules for software, including Free Software. The relevant proposals are the AI Act, Product Liability Directive (PLD), and Cyber Resilience Act (CRA). The way they are, all proposals will harm the Free Software ecosystem and thus the society and the economy.

The main debate happens around the Cyber Resilience Act. We will therefore discuss the risks and solutions using this Act as an example.

While we welcome the discussion on more cyber security we doubt that the introduction of liability alone will lead to more cyber security. Especially in Free Software, far-reaching security measures are already in place. Those measures differ from those of proprietary software.

The proposal to exclude Free Software “outside the course of a commercial activity” would fail to address a large part of software that will not be covered but is deployed. At the same time smaller and non-profit projects would be harmed as they would have to bear major costs.

We, therefore, propose a solution that will lead to more security while safeguarding the Free Software ecosystem:

  1. Liability should be shifted to those deploying Free Software instead of those developing Free Software and
  2. Those who significantly financially benefit from this deployment should make sure the software becomes CE-compliant

Free Software with its four freedoms to use, study, share, and improve the code makes it easy for anyone to develop and improve the code while making it available to everyone. In cases of security incidents, developers - who might only get micro or small payments, are non-profit, or even do not earn a single Euro for their work - might be liable. To make them liable could lead to large burdens that projects could not handle alone. Free Software is everywhere nowadays, and those deploying Free Software, especially Free Software from small projects, must take on more responsibility, if only out of their own interest.

Putting the burden of liability on these small or non-profit entities would harm the Free Software ecosystem and thus society and business equally, because due to the lack of funding and resources to go through these procedures, some of these projects might have to stop completely, but also it won't necessarily lead to more security. Moreover, many small Free Software projects already have well-working security assessments in place. Introducing new workflows or even consulting third parties would have financial consequences that would be almost impossible to bear. Ways to address the funding problem could be a dedicated fund to support these projects, or the introduction of a scoring system that shows how much a company invests in the security of the Free Software projects it uses. However, neither of these proposals can be implemented quickly, so the problem will persist. Therefore, transferring liability to those who deploy the software and try to profit significantly from it seems to be a better solution.

To address this, the current wording needs to be improved. The concept of “commercial activity” should be replaced with an approach that focuses on deployment rather than on development. And the responsibility to fulfill these requirements should be on the entity that benefits in the market. Likewise, exemptions for non-profit entities and micro enterprises should be introduced. In other words, liability should be moved towards those deploying these solutions that are substantial profit-oriented companies.

This will ensure that all Free Software solutions that are used on a significant level are assessed under the liability rules in the CRA, PLD, and AI Act, but the financial burden will be shifted to those who try to make a profit from these solutions. So they will be the ones having to make sure that someone runs through the procedures needed for their software to get the CE label. Deployers could collaborate and ensure that they fund projects they use or could run through the procedures themselves. They ought to make sure that modifications are fed back into the projects.

We presented this position also in a public hearing in the European Parliament.

It is a complex debate with far-reaching implications and changing positions every day. We will continue to work on this issue in the upcoming month. If you are interested in getting involved or joining our activities, please contact us via email.

Support FSFE

Meet Andrei and David, two first edition YH4F participants

mardi 21 mars 2023 à 00:00

Meet Andrei and David, two first edition YH4F participants

The coding period of the Youth Hacking 4 Freedom hacking contest has been running for almost three months now. The competition continues to be a fun contest for young hackers to test and develop their skills. The previous edition ended with 35 great projects submitted with inspiring stories behind them. Read about Andrei's and David's projects.

The rules for the contest are simple: the projects must be Free Software. There are no limits to the possibilities on the kinds of projects that can be submitted. Any technical idea is welcome. This gives each participant the chance to create a project according to their wishes, skills, and interests. At the end of the first edition of the Youth Hacking 4 Freedom competition, 35 amazing projects had been submitted. Each of these projects has an inspiring story behind it. Let us introduce you to two of these amazing projects. Take a look at Andrei's handy tool for dmenu and David's "OpenCV Hand Gesture Control" project.

Before joining YH4F, Andrei was already involved in the Free Software world. He has not only used various GNU/Linux distributions as his main operating system, but also made sure it stays fun with games available for everybody. He recently helped port Minetest (a Free Software game) to the cross-platform library "Simple DirectMedia Layer" (SDL), which helps developers to make sure their games are working on different types of operating systems. But instead of sticking to only a technical world Andrei channels his artistic energy into both shell and film scripts.

The mind behind "OpenCV Hand Gesture Control" is David. David has a passion for Free Software and software development. He learned the basics of Scratch programming in Grade 3. Since then he has improved his skills and widened his knowledge of programming. David started writing scripts in Python and Bash and has now moved on to learning Rust. After the YH4F contest David has also continued to work on projects such as the Matrix-Modbot, which is a bot that automatically moderates Matrix rooms.

FSFE: Hello Andrei and David. Thank you for joining us.

FSFE: How did you come into contact with programming and how did you learn to program?

David: When I was in China, in grade 3 I was introduced to Scratch programming and immediately became fond of it. Then I learned through experimenting with the program to create simple animations and games. When I got my first computer, I started to learn Python from a video series for beginners. After learning the basics, I began to write some small scripts in Python and Bash for myself. And last year, I managed to secure an internship position at a software company. There I learned a lot and this experience also led me to learning about python OOP design and software design in general. Now I am learning Rust and working on a project called Matrix-Modbot, which is an automated bot for Matrix.

Andrei: I used to go to a programming club a friend of mine invited me to. We were writing C++ to solve some mathematical problems (things like greatest common factor, factorial etc.) though we (unofficially) spent too much time playing games there as well.

FSFE: Andrei, can you tell us what was your first contact with Free Software?

Andrei: When I was going through The Odin Project they required at some point to install a derivative of Ubuntu (they said nearly half of software engineers use it and it’s easier to install software and so on). I was convinced my computer would stop booting but went along with it. Xubuntu installed fine! Later on I learned all about the parts of the free GNU/Linux operating system and how they work together so now I have started writing package files (PKGBUILDs) on Arch so that I may too try and contribute to this freeing ecosystem.

FSFE: Andrei, you have already coded before and used Free Software in your daily life. What motivated you to participate in the YH4F contest?

Andrei: I did not know the FSF had an European sister organisation before and I was really happy to get involved! I really liked the way the contest gives an opportunity to choose a concrete, practical task and go through with it. (Too often I get stuck halfway on coding a cool thing, and that’s not great.)

FSFE: David, what motivated you to join the YH4F contest?

David: I saw the advertisement on Mastodon and became interested in the competition, so I joined and used my free time to work on the project.

FSFE: David, how did you come up with your project idea to use your hand motion for executing commands?

David: It actually started while I was trying to read novels or to watch movies on my laptop. When I read, I am usually in a relaxed position and I find it cumbersome to reach for the mouse or the keyboard to turn pages, so I thought: What if I can turn pages or pause the video with the wave of my hand? And that is how I got my idea for the project.

David demonstrating his "OpenCV Hand Gesture Control" project.

FSFE: Andrei, could you also give us an overview of your project

Andrei: I added clipboard functionality to a dynamic menu program called bemenu. Pressing ctrl-Y inserts the system clipboard into the command's command buffer now.

FSFE: What motivated you to work on your project?

David: It was mainly to solve my own problem, and my program could also be used on smart TVs or other devices with a camera to control the device without using a keyboard or a controller.

Andrei: The bemenu project is written in C, and it sounded nice to maybe learn to do some advanced tasks in C like programmatically copying and pasting. That it would solve a practical problem for me was a nice bonus too.

FSFE: Andrei, could you briefly explain what a dynamic menu like bemenu is?

Andrei: A dynamic menu takes in a list of things, for example some URLs, or some commands, or usernames, and allows matching and selecting one of them. For example, typing in fire or fox will match firefox but still allow selecting fire or fox by itself. This means, for example, that finding and running a command is made much easier. Think of it as a start menu, except one that can be programmed to be taken into other programs, like for example using it as a password prompt or a confirmation box. This works because it always gives back the thing that was selected, and that can be used by a different program.

FSFE: Did any of you encounter any problems during the coding period or the building period?

David: I did encounter many issues, and they were mostly some design flaws that I did not anticipate. At that time I had little knowledge about software design and was struggling to make the code clean and cohesive.

Andrei: It turns out getting clipboard data is not the same everywhere! It is one thing on X11, and a different thing on Wayland. At first, writing a clipboard manager myself sounded fine (a likely story!), though eventually I decided on using wl-clipboard and xclip. I am glad I learned to not be excessively afraid of pulling in dependencies where it really solves a complex problem that writing by hand would make little sense.

FSFE: David, can every user define the shortcuts themself and do you have an example on how your program works?

David: Yes, and there is an example config file in the git repo of the OpenCV-Hand-Gesutre-Control. For example three fingers to the right open a terminal window.

FSFE: How did you train your tool to recognise your hand movements?

David: The hand movement recognition is based off OpenCV, however I used a 3rd party library to provide a trained model as implementing the same model myself would be “reinventing the wheel”, but this time the wheel would probably not spin as well.

FSFE: Andrei and David do you think you will continue working on your project and what would be some next steps you would like to realize?

Andrei: I think I am happy with how the project is right now! They may say code never stops changing, but when something is really finished that is great feeling. I’m sure I’ll be back at it if something feels like it needs improvement though! My confidence is certainly there now.

David: I think I will work on the project in the future and re-factor the code as it is currently quite messy and somewhat buggy. To make the detection more accurate, I could use the power of python’s data science libraries to make better sense of the input data.

FSFE: Thank you for your time and we wish you both good luck with your next steps.

The coding period for the second edition of YH4F is still ongoing. For more information about the contest please visit yh4f.org.

Support FSFE