Language Selection

English French German Italian Portuguese Spanish

What should fit in a FOSS license?

Filed under
OSS
Legal

What terms belong in a free and open source software license? There has been a lot of debate about this lately, especially as many of us are interested in expanding the role we see that we play in terms of user freedom issues. I am amongst those people that believe that FOSS is a movement thats importance is best understood not on its own, but on the effects that it (or the lack of it) has on society. A couple of years ago, a friend and I recorded an episode about viewing software freedom within the realm of human rights; I still believe that, and strongly.

I also believe there are other critical issues that FOSS has a role to play in: diversity issues (both within our own movement and empowering people in their everyday lives) are one, environmental issues (the intersection of our movement with the right-to-repair movement is a good example) are another. I also agree that the trend towards "cloud computing" companies which can more or less entrap users in their services is a major concern, as are privacy concerns.

Given all the above, what should we do? What kinds of terms belong in FOSS licenses, especially given all our goals above?

First, I would like to say that I think that many people in the FOSS world, for good reason, spend a lot of time thinking about licenses. This is good, and impressive; few other communities have as much legal literacy distributed even amongst their non-lawyer population as ours. And there's no doubt that FOSS licenses play a critical role... let's acknowledge from the outset that a conventionally proprietary license has a damning effect on the agency of users.

However, I also believe that user freedom can only be achieved via a multi-layered approach. We cannot provide privacy by merely adding privacy-requirements terms to a license, for instance; encryption is key to our success. I am also a supporter of code of conducts and believe they are important/effective (I know not everyone does; I don't care for this to be a CoC debate, thanks), but I believe that they've also been very effective and successful checked in as CODE-OF-CONDUCT.txt alongside the traditional COPYING.txt/LICENSE.txt. This is a good example of a multi-layered approach working, in my view.

So acknowledging that, which problems should we try to solve at which layers? Or, more importantly, which problems should we try to solve in FOSS licenses?

Here is my answer: the role of FOSS licenses is to undo the damage that copyright, patents, and related intellectual-restriction laws have done when applied to software. That is what should be in the scope of our licenses. There are other problems we need to solve too if we truly care about user freedom and human rights, but for those we will need to take a multi-layered approach.

To understand why this is, let's rewind time. What is the "original sin" that lead to the rise proprietary software, and thus the need to distinguish FOSS as a separate concept and entity? In my view, it's the decision to make software copyrightable... and then, adding similar "state-enforced intellectual restrictions" categories, such as patents or anti-jailbreaking or anti-reverse-engineering laws.

Read more

More in Tux Machines

5 common open source testing myths debunked

Open source tools are constantly changing the landscape of testing, and the community around these tools is bigger and more vocal than ever. The first-ever State of Open Source Testing Survey examines the latest trends and developments across the software development industry. This survey received over 2,000 responses from practitioners across the behavior-driven development, functional testing, and load testing domains. The survey reveals a great deal about software testing and how it uses open source, and based on the results, it's reasonable to expect an increased rate of adoption and deployment of open source tools. Read more

The 20 Best Open Source BI Tools and Software in 2020

Open source BI tools provide a great value to the Linux users for managing their business. Business intelligence tools are popularly known as BI tools. It doesn’t matter whether it is a brick and mortar business organization or online business; they have to work with a lot of data for business intelligence. Business intelligence consists of some strategies for the data analysis of any business. Though it is not possible to process these huge piles of accumulated data manually. The open source software developers have created some computer programs for business intelligence. Read more

Linux email client Geary is getting a responsive (phone-friendly) UI

I’m a big fan of desktop e-mail client Geary — it’s in our list of the best Ubuntu apps after all — so I’m particularly thrilled to hear that a “mobile version” is in the works. Okay, okay: I say “mobile version” but what I more accurately mean is a mobile “face” for the app. Y’know: a responsive interface designed to work well on a range of mobile devices, be it Linux phones like the Librem 5 or upcoming Linux tablets like the PineTab. Alex, aka BabyWogue, uncovered work on an adaptive UI for Geary in code on the Geary repo on the Purism Gitlab instance. He built it and, as you’d expect, demoes the current state of progress in a video on his YouTube channel (which you can see embedded below). Read more

today's leftovers

  • Finally Landed on Planet GNOME

    Should I start with a deep introduction? Not sure! Okay, let me start from my first time with Linux. I installed my first Linux when I was around 17, It was OpenSUSE. I just burned iso and booted, HAHAHA It was a magnetic disk era. After some years I was getting deep into Linux. I consider Linux as an Icecream. Lots of flavors to eat. Eat whatever you like. Or make your own flavor. 4-5 years ago I was jumping over multiple distros. I tried multiple linux distros. But now I'm settled on a custom build Debian distro. My first encounter with GNOME was on Fedora. I still love Fedora. But Debian is ultra-fast with only selected packages and easy to make its flavor. This is my short Linux story.

  • Sound Recorder to modern HIG I

    I'm back, reporting here what's done so far. I decided to post about every change in sound recorder I'm working on but most of the work was behind a scene. I mean no UI change. But now new changes noticeable to end-users. I'm also writing this development blog cause, I don't wanna give chance to other people to spread some false information about development around (Social Media, YouTube). If you are reading this and you are working on any GNOME project, Please take 5-6 min and write about it frequently. As I told I'm working on GNOME Sound Recorder, recently I changed many things in the application.

  • LibreOffice Tuesday T&T: Impress Presenter Screen

    LibreOffice Impress is a valuable presentation software, with plenty of advanced features. One of the most liked by skilled presenters is the so called Presentation Screen, which shows the current and the next slide on screen, and the notes. It helps the presenter to maintain the rythm of the presentation, and to remember the details of the talk. According to LibreOffice default configuration, the Presenter Screen shows only if the PC is connected to two displays. For some people this is a feature, for some others this is a bug.

  • PeaZip 7.3.1

    PeaZip is an open source file and archive manager. It's freeware and free of charge for any use. PeaZip can extract most of archive formats both from Windows and Unix worlds, ranging from mainstream 7Z, RAR, TAR and ZIP to experimental ones like PAQ/LPAQ family, currently the most powerful compressor available.

  • How CHAOSS Measures Open Source Community Health

    To learn more about the project, we spoke with Dawn Foster, Director of Open Source Community Strategy at VMware and member of the CHAOSS governing board. FOSSlife: Please give our readers a bit of background on the CHAOSS project. How did it originate and what are its goals? Dawn Foster: The community was formed as a result of a Birds of a Feather at the Linux Foundation Open Source Leadership Summit in 2017 out of a shared desire to collaborate on ways to measure open source project health. It was officially announced as a Linux Foundation project a few months later at the LF Open Source Summit North America. The idea was to bring together several different analytics tools, like GrimoireLab and cregit, into a coordinated effort while also developing metrics definitions that could be used by any implementation. [...] Dawn Foster: Anyone can participate in the CHAOSS project! I think sometimes people think that CHAOSS is all about software development on the tools we use to gather the metrics, and while that's an important part of what we do, it isn't everything. Most of the time, the working groups are discussing and defining metrics, which is something anyone can do. We collaboratively work together in documents to define metrics to better understand what questions they answer and why they are important in addition to talking about what data you might need to collect. In some cases, like with many of the diversity and inclusion metrics, qualitative measurements are an important element of the metrics definitions. We need people from all backgrounds with different skills to help us define metrics in a way that is useful for a variety of people and organizations. In addition to the metrics, CHAOSS is a fun community of smart and welcoming people, so it's a place where you can enjoy contributing!

  • NVIDIA K8s Device Plugin for Wind River Linux

    The advent of containers has changed the way computational workloads are managed and orchestrated in modern computing environments. Given the paradigm shift towards the microservices, container orchestration has become of critical importance in today’s distributed and cloud systems [1]. Managing edge devices on the scale of hundreds and thousands is an onerous task. Fortunately, orchestrators such as Kubernetes take the complexity out of updates, roll-backs, and more in a platform-agnostic environment. [2]. Orchestrators provide the means to manage heterogeneous edge clusters. It is necessary to not only orchestrate containers but to discover the hardware specialized devices that the containers and orchestrator can leverage. Failing to manage these resources can lead to inefficiency, time drain, concurrency issues, and more.