this post was submitted on 16 Jun 2024
1150 points (100.0% liked)

linuxmemes

23908 readers
1262 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
  • Don't get baited into back-and-forth insults. We are not animals.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
  • 5. πŸ‡¬πŸ‡§ Language/язык/Sprache
  • This is primarily an English-speaking community. πŸ‡¬πŸ‡§πŸ‡¦πŸ‡ΊπŸ‡ΊπŸ‡Έ
  • Comments written in other languages are allowed.
  • The substance of a post should be comprehensible for people who only speak English.
  • Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
  • 6. (NEW!) Regarding public figuresWe all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations.
  • Keep discussions polite and free of disparagement.
  • We are never in possession of all of the facts. Defamatory comments will not be tolerated.
  • Discussions that get too heated will be locked and offending comments removed.
  • Β 

    Please report posts and comments that break these rules!


    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.

    founded 2 years ago
    MODERATORS
     

    Context:

    Permissive licenses (commonly referred to as "cuck licenses") like the MIT license allow others to modify your software and release it under an unfree license. Copyleft licenses (like the Gnu General Public License) mandate that all derivative works remain free.

    Andrew Tanenbaum developed MINIX, a modular operating system kernel. Intel went ahead and used it to build Management Engine, arguably one of the most widespread and invasive pieces of malware in the world, without even as much as telling him. There's nothing Tanenbaum could do, since the MIT license allows this.

    Erik Andersen is one of the developers of Busybox, a minimal implementation of that's suited for embedded systems. Many companies tried to steal his code and distribute it with their unfree products, but since it's protected under the GPL, Busybox developers were able to sue them and gain some money in the process.

    Interestingly enough, Tanenbaum doesn't seem to mind what intel did. But there are some examples out there of people regretting releasing their work under a permissive license.

    (page 2) 50 comments
    sorted by: hot top controversial new old
    [–] [email protected] 15 points 9 months ago* (last edited 9 months ago) (14 children)

    I'm an idiot making a thing, and I need to pick a license. Where's a good place to talk to people more knowledgeable than myself on the subject?

    EDIT: so my thing isn't software, i probably should have mentioned that. I am making a ruleset and setting for something similar to but not exactly a tabletop rpg. The ORC license sounds promising, but the legalese makes my brain gray out. ChatGPT tells me to use a version of the Creative Commons license, but ChatGPT isn't exactly reliable.

    [–] [email protected] 13 points 9 months ago

    https://choosealicense.com/

    Very simple guide with in depth examples if you want further clarification.

    [–] [email protected] 9 points 9 months ago* (last edited 9 months ago) (1 children)

    Not an expert by any means, but it depends.

    Are you okay with people potentially making a closed-source fork of your code? If yes, then choose a permissive license like MIT, BSD, or Apache. If you do not want people to make closed-source versions of your code, and want all forks to remain open-source, then go with GPL.

    Remember that choosing the GPL means other people, especially businesses, will be less likely to consider your project because that would mean they would have to make their versions open-source, which some people may not want to do.

    EDIT: As always, this is not legal advice and I am not a lawyer.

    load more comments (1 replies)
    load more comments (12 replies)
    [–] [email protected] 15 points 9 months ago

    Permissive License promoters are corporate trolls

    [–] [email protected] 14 points 9 months ago (2 children)

    Someone please SUE ANYCUBIC AND CREALITY FOR STEALING KLIPPER !!!!!!! Make them give back to the community that created their business !!

    load more comments (2 replies)
    [–] [email protected] 14 points 9 months ago

    Interestingly enough, Tanenbaum doesn’t seem to mind what intel did.

    Yeah, duh. Intelligent people read licenses before they pick one.

    But there are some examples out there of people regretting releasing their work under a permissive license.

    That's like signing a contract before reading it and then complaining that it contains provisions that surprise you when they are enacted. I'm baffled on a regular basis by how many people understand FOSS licenses only on the basis for hearsay, for example when people insist that GPLed source code must be made available free of charge for everyone. The GNU project has a FAQ about the GPL that spells it out that this is not the case and yet hardly anyone discussing FOSS licenses has even read the FAQ.

    [–] [email protected] 13 points 9 months ago* (last edited 9 months ago) (3 children)

    Permissive licenses are truer to the spirit of free software but copyleft, while kind of a copout, seems more pragmatic due to corporations. I wouldn't avoid copyleft licensing on principle or anything but it feels incongruous to want to make something freely available to all but then nitpick over how they use it.

    load more comments (3 replies)
    [–] [email protected] 13 points 9 months ago (7 children)

    Busybox was quickly replaced by BSD-licensed Toybox everywhere for that exact reason.

    Copyleft licenses (like the Gnu General Public License) mandate that all derivative works remain free.

    This is false. It's perfectly legal to take GPL-licensed work, modify it, and sell it. As long as the work itself does not reach the general public, you don't need to release it's source code to the public (e.g. your work for the military, you take money for your work, and provide source code to them, but not release it publicly).

    load more comments (7 replies)
    [–] [email protected] 13 points 9 months ago (2 children)

    My project is MIT because the upstream project is MIT, could I slap a GPL on there? How would I do that? What would that change?

    [–] [email protected] 16 points 9 months ago

    Yes you can. You just change the license that lives with the code.

    What it changes depends on the project, how it's used, who uses it, etc. It's really a social question of how people might interact with your project differently.

    [–] [email protected] 8 points 9 months ago* (last edited 9 months ago) (2 children)

    You can use the gpl license in newer versions of your software, but keep in mind, in order to avoid future misunderstandings, that you can only do that because the upstream project uses the mit license. If the project used a reciprocal license like the gpl, you'd need to stick to it or use a compatible one. You can't, for example, take a upstream gpl project and use a mit license

    load more comments (2 replies)
    [–] [email protected] 12 points 9 months ago* (last edited 9 months ago) (4 children)

    Really?...

    Just about every FOSS and Source-Available license that I've seen is perfectly valid. As a software developer, one has the option to choose how they wish to license their software. This can be based upon one's personal philosophical view or what seems most appropriate for the piece of software.

    Not everyone is motivated by profit. Most software that I develop personally is permissively licensed because IDGAF as long as I have enough to get by. If I write some code that makes someone else's life better or easier, that's more than enough for me.

    Wait. What am I saying? This is the Internet and, according to the rules of corpo social media, we're all supposed to be dicks to each other to further "engagement". WHICH ONE OF YOU SAVAGES IS USING TAB INDENTATION INSTEAD OF BLOCKS IN YOUR LICENSE FILES?!?;?!!!!111one

    load more comments (4 replies)
    [–] [email protected] 9 points 9 months ago* (last edited 9 months ago) (1 children)

    We are at risk

    of losing many developers who would otherwise choose a license like the GPL. Fortunately, I'm glad to be surrounded by people, just like you, who care about licenses like GPL. By uploading this type of content and engaging with it, be show our commitment to it. I wish to suggest how we can deal with this threat.

    We will lose developers who choose GPL if we use words that suggest GPL is "restrictive". Sure, the word "restrictive" was avoided in this meme by using the word "copyleft", but the cognitive jump from "permissive" to "restrictive" is minimal: just add an "opposite" and you've got "permissive is the opposite to restrictive". It really is that simple. That's how brain works (check out Relational Frame Theory to see how that works).

    So what can we do about it?

    Well, we can approach this with science. There is a historical global trend towards people being more meta-cognitive. That means that people are becoming more aware of how our thoughts interpret everyday reality and how to be intentional with our relationship with our thoughts so that we live better lives. We know this trend is happening to virtually everyone everywhere because of the work of brilliant sociologists like Anthony Giddens and Christian Welzel. Heck, even the history of psychology β€”going from noticing and changing behaviors (behaviorism) to noticing and changing behaviors and thoughts (cognitive-behaviorism), to noticing and changing the context and function of behaviors, thoughts, and emotions (functional contextualism)β€” reflects this trend.

    We can use meta-cognition in our favor; we can use the meta-cognitive tool of framing to change how we think about GPL and MIT licenses. Effective communicators like influencers, political campaign experts, and influential activists use framing all the time. For example, instead of using the dangerous framing that suggests GPL is 'restrictive', we can use another one that truly displays the virtues of the license.

    What would this other frame look like? I may not have a perfect answer, but here are some

    ways of framing (thinking about) the relationship between licenses like GPL and MIT:

    (ironically!!!, these were 'suggested' by an LLM; I wonder if these frames already existed)

    • "Investment-Protecting Licenses" vs. "Investment-Risking Licenses" (as in developers invest by working on projects that they could (not) lose the ability to contribute to)
    • "Community-Resource-Guarding Licenses" vs. "Exploitation-Vulnerable Licenses"
    • "Give-and-Take Licenses" vs. "Take-and-Keep Licenses" ⭐
    • "Freedom-Ensuring Licenses" vs. "Freedom-Risking Licenses" ⭐
    • "Contribution-Rewarding Licenses" vs. "Contribution-Exploiting Licenses"
    • "Open-Source-Preserving Licenses" vs. "Closed-Source-Enabling Licenses"

    I'd be happy to hear what you think, including suggestions!

    [–] [email protected] 12 points 9 months ago (3 children)

    There's a fair bit of bias in those terms, which make GPL seem like a 'better' choice than an unrestricted license like MIT.
    The truth is, GPL is restrictive to developers. Copying just one line from a gpl-licensed project will automatically restrict you to using only gpl-compatible licenses. I'd prefer to advocate for LGPL and similar licenses, as they seem to offer a better tradeoff between user and developer freedom.

    load more comments (3 replies)
    load more comments
    view more: β€Ή prev next β€Ί