797
Seeing big companies take advantage of BSD or MIT licensed projects without sharing their contributions will always pain me. (lemmy.world)
submitted 2 months ago* (last edited 2 months ago) by atmur@lemmy.world to c/linuxmemes@lemmy.world
82 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[-] IsoSpandy@lemm.ee 10 points 2 months ago

Can someone help me? I have been licencing my code under BSD2Clause, I wish to switch to gplv3. How do I switch?

  1. Do I have to put the licence at the top of every file?
  2. Where do I put my name ie Copyright

Thank you

[-] chris@l.roofo.cc 19 points 2 months ago

Here is a guide from the GNU website: https://www.gnu.org/licenses/gpl-howto.en.html

[-] IsoSpandy@lemm.ee 2 points 2 months ago

Thank you so much. This is exactly what I needed

[-] darkpanda@lemmy.ca 3 points 2 months ago

One other thing you may have to do if you have contributors who have also committed code is to get their permission to change the license as well, as the code they committed may still be under their copyright and not yours, and they can choose to allow their code to be relicensed or not. Some projects use a contributor release to reassign copyright for contributions for reasons like this, for instance. This is partly the reason why the Linux kernel has never changed to GPLv3 and still uses GPLv2 (and also because Linus just doesn’t like some provisions of the GPLv3) — it would be pretty much impossible to get everyone who contributed code to a project as large as the kernel to agree to a license change. Any code that couldn’t be changed would need to be extracted and rewritten, and that’s not going to happen given the sheer size of the code base.

If you don’t have other contributors then you’re home free. You can’t retroactively change licenses to existing copies of the code that have been distributed, but you can change it going forward.

[-] Karyoplasma@discuss.tchncs.de 4 points 2 months ago* (last edited 2 months ago)

Delete the current LICENSE file in your repository and replace it with the new one.

You don't have to put your name, year etc anywhere, the license is valid for the entire repo. You are not filing for an IP, it's just a usage license.

Note that all the legal jargon is not necessary, you can write one yourself as long as you make it clear what you allow and what you don't allow.

I.e. "don't be a dick" requires elaboration, "do not use my code if you intend to make money off of it or parts of it" is clear and legally binding.

[-] IsoSpandy@lemm.ee 2 points 2 months ago

So just replace my old licence file with the GPL?

this post was submitted on 28 Aug 2024
797 points (98.1% liked)

linuxmemes

21172 readers
668 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 members of the community for any reason.
  • 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.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
    • 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, and wants to interject for a moment. You can stop now.

    • Please report posts and comments that break these rules!

    founded 1 year ago
    MODERATORS
    poopsmith@lemmy.world
    zephyr@lemmy.world
    rtxn@lemmy.world