The Ethical Source Movement

This is so nice :hugs:

https://ethicalsource.dev

Software is considered Ethical Source if it meets the following five criteria:

  1. It is freely distributed with source code and can be used or combined with other software without a royalty or fee.
  2. It is developed in public and is welcoming of community contributions.
  3. Its community is governed by a code of conduct that is consistently and fairly enforced.
  4. Its creators have the right to prohibit its use by individuals or organizations engaged in human rights violations or other behavior that they deem unethical.
  5. Its creators have the right to solicit reasonable and voluntary compensation from the communities or institutions that benefit from the software.

It seems that the disgrace of RMS is opening brand new perspectives…

4 Likes

Sounds cool. The idea is to create a license? We were thinking with Leo that it would be cool to have a cooperative license. (Some software that only can be used if it is used in a coop organisation). This sounds good.

That’s an interesting idea but might it be complex to enforce & depend heavily on how co-ops are defined. Is open source is more “self-enforcing”.

3 Likes

I think the key difference is perhaps what is being enforced, the Ethical Source criteria is motivated by the desire to place moral restrictions on the type of people and organisations that are allowed to use the code and / or the things the code is used for, whereas free / open source licenses don’t place restrictions of this nature, there are broadly three types of free / open source licenses:

  1. MIT/X11/Apache/BSD style licenses generally require you to preserve the authorship of the code and include a copy of the license if you distribute it, however you don’t have many other restrictions, you are allowed to include the code into proprietary products and distribute these without source code, this is why capitalist corporations such as Apple, Microsoft and Google generally only support and use these permissive licenses — they allow them to do what they wish with the software to make money and they don’t have to share any improvements they make.
  2. GPL/CopyLeft style licenses require you to share any changes you make to the code if you distribute the code and require you to pass on the same rights that you have. Corporations often ban the use of these licenses, they hate them as sharing isn’t something that is in their nature, some people are of the view that Google’s development of an alternative to the GNU/Linux kernel, Google Fuchsia, is motivated by a desire to escape the restrictions of the GPLv2 that the GNU/Linux kernel is released under.
  3. AGPL style licenses these place an additional restriction over and above those of the GPL, if you provide a service that uses code under these terms you have to let the users of the service have access to the code. This is to close the loophole that the likes of Amazon have made billions from — AWS is based on charging people for using free open source software, however they don’t share the improvements they make as they don’t distribute the code.
2 Likes

Hi!

I’m not a licenses expert, but I’m interested in this topic. I remembered the Peer to peer license or copyfarleft:

c. You may exercise the rights granted in Section 3 for commercial purposes only if :
i. You are a worker-owned business or worker-owned collective; and
ii. all financial gain, surplus, profits and benefits produced by the business or collective are distributed among the worker-owners

There is an interesting debate here : https://wiki.p2pfoundation.net/Copyfarleft

4 Likes

1 Like

Quite a fan of this sort of licensing. It has the virality of say the GPL but what it encourages is not simply exposure of the code but also the organisational format and keeps the cash within the cooperative movement.

Really good quality software of this kind (say if someone did the next Nginx…) could convince some that they need to be a cooperative in order to benefit…

1 Like

Oh, I didn’t know about that license. Sounds very bueno.

Hey, I’ve started engaging with this work over on the issue tracker https://github.com/EthicalSource/hippocratic-license/issues and asked to join the working group https://ethicalsource.dev/apply/. Would be cool to see others getting in on this!

I do think that work shows us the limits of the GPL. It still seems to be the best tool we have for stopping privatisation of the software through sublicensing but Freedom 0 (use for any purpose) is problematic in that at some point, the software freedom stops corresponding to human freedoms (your software is used somewhere in the process of putting kids in a cage, see https://icebreaker.dev). GPL licensed projects got blacklisted by Google and some other megacorps so they were effectively able split the community and delegitimise its use but this work goes straight for the licenses that Google and not-friends love and need, the permissisve style licenses.

There are some interesting developments with the new Hippocratic license versions. They’ve tied it to the UDHR which is a totally not fuzzy ethical position. They’re also working on integrating -H (-Hippocratic) addons to other licenses, like the BSD-H where the ethical elements have become somehow “pluggable” into other licenses. They also seem to be aware of the issues withe permissiveness and copyleft that a number of people have raised on the issue tracker.

It ain’t perfect but I think it’s worth engaging in.

Do you have a project in mind to use this license on?

I can see the point behind the Coopyleft license for CoopCycle, they want to prevent a non-cooperative competitor from being able to use their code, rather than using the traditional copyleft approach, which would be to force any competitors who did use their code to share improvements with them.

I was just wondering what you think the use case for this license might be?

When there is a copyleft version of it, I’ll consider using it rather than the GPL.

I’d like to have a copyleft license that includes ethical restrictions for the software I write. For me, the practical benefit is to scare off more bad actors (e.g. GPL’d code is blacklisted by some megacorps). Otherwise, it’s a good awareness raising tool and has already started some heated discussions on ethics in software and what we can do about it.

You’re not into this license or?

I posted some thoughts on this approach in general here:

I’m yet to be convinced, especially when the corporations are pushing open source licenses that allow code to be privatised, that we shouldn’t be uniting behind CopyLeft / Free Software…

Indeed, I wouldn’t use the “forked from MIT” license they have now since you can just sublicense it and away you go back to proprietary world. Copyleft is a must but the overall point is that we can’t just stick to our guns with GPL, Free Software and the usual Copyleft arguments because we’re falling short on the Freedom 0. issue.

To be fair, none of us could probably raise enough resources to even win a copyleft license violation enforcement case so there is definitely limits to the license approach in the first place… but heck, it’s a good tool so far…

1 Like

In case people don’t know what this refers to:

A program is free software if the program’s users have the four essential freedoms: [1]

  • The freedom to run the program as you wish, for any purpose (freedom 0).
  • The freedom to study how the program works, and change it so it does your computing as you wish (freedom 1). Access to the source code is a precondition for this.
  • The freedom to redistribute copies so you can help others (freedom 2).
  • The freedom to distribute copies of your modified versions to others (freedom 3). By doing this you can give the whole community a chance to benefit from your changes. Access to the source code is a precondition for this.

1. The reason they are numbered 0, 1, 2 and 3 is historical. Around 1990 there were three freedoms, numbered 1, 2 and 3. Then we realized that the freedom to run the program needed to be mentioned explicitly. It was clearly more basic than the other three, so it properly should precede them. Rather than renumber the others, we made it freedom 0.

https://www.gnu.org/philosophy/free-sw.en.html

3 Likes

Fresh off the press.

2 Likes

https://opensource.google/docs/patching/#forbidden

“You can’t patch projects with any of the following licenses: … Hippocratic License”

1 Like

Very interesting reading indeed.

https://opensource.google/docs/using/agpl-policy/

Seems that to prevent enclosure by corporations one simply has to apply AGPL. This is an incredibly strong take in response and imagine most large software companies have a similar approach.

3 Likes

I listened to the talk and I’m still not convinced by the concept of the ethical software license, I do however think that refusing to work for these capitalist corporations and boycotting their products and services is a good idea, but alternatives are needed, hence the purpose of Webarchitects is: “the provision of internet based services for socially responsible groups and individuals, using free open source software”.

Seems that to prevent enclosure by corporations one simply has to apply AGPL.

Exactly.

Enforced sharing of digital information is an anathema to capital because it could result in abundance, capital depends on enforced scarcity.

I’d like to see all digital artefacts and the digital designs of everything, (products, buildings, food etc) shared under terms similar to the (A)GPL, not just software, this isn’t something that Richard Stallman agrees with, following is an audio clip of me arguing with him about this 9 years ago… :roll_eyes:.

The above audio clip does illustrate the point that the speaker from the ethical source movement made in the video above, the pioneers of the Free software movement like Stallman are philosophically individualistic, I failed to explain the fundamental, societal implications that would arise from the designs of everything being Free and Stallman could only comprehend the question I put to him in terms of the implications for individual consumers producing their own things.

Perhaps the hack at the core of the Free software movement, using copyright law to enforce sharing rather than the purpose it was designed for, preventing sharing, is about as much as we can hope to achieve through the use of a software license within the current system?

4 Likes

Agree. My point of view: “For the Free Software Community to survive it must break free from libertarian sentiments and fight its battle into the very center where money runs the software world, the Free Market Economy.” For anyone interested, please read my paper A Business Case for Free Software.

Another good one :wave:

https://modelviewculture.com/pieces/the-culture-war-in-open-source-is-on

is about as much as we can hope to achieve through the use of a software license

I feel like we can also expand the risk for corps in adopting programs with ethical copyleft licenses. Take point 4 where it explains that IBM was worried about the “The Software shall be used for Good, not Evil” clause in the JSLint license. That was just a single line and it shook things up.

I like that it is one tool that is part of a broader strategy to escalate. Look at the “what can you do about it” bit in https://icebreaker.dev, using the license was just one part, the rest was fighting talk about resisting and boycotting. We need a leg to stand on when we want to demand restrictions and I don’t think we have that with the current free software definition.