@CapriciousDay@lemmy.ml we already did this a decade ago with the Do No Evil license in https://www.json.org/license.html and learned the approach is not compatible with FOSS. Projects have added a layer of accountability with contributor agreements, but those only limit your ability to participate in the development of the project directly. They don’t limit your rights to do what you want with the code.
@Cris_Color@lemmy.world
@abeorch@friendica.ginestes.es @pastermil@sh.itjust.works
Many years ago I worked on a project with some FSF staff who refused to use non-FOSS solutions to coordinate or conduct meetings. While the developers involved where all prolific contributors to open source projects used by millions of people, they were all willing to compromise on some of the tools we use to develop and communicate for “the greater good”. The FSF staff weren’t willing to make those compromises. At the time I was frustrated by this. As Slack ownership changed, costs increased and policies around what they could do with “our” data evolved, I now have a lot more respect for the FSF staff who are “holding the line”.