atmur@lemmy.world to linuxmemes@lemmy.worldEnglish · edit-23 months agoSeeing big companies take advantage of BSD or MIT licensed projects without sharing their contributions will always pain me.lemmy.worldimagemessage-square82fedilinkarrow-up1813arrow-down118
arrow-up1795arrow-down1imageSeeing big companies take advantage of BSD or MIT licensed projects without sharing their contributions will always pain me.lemmy.worldatmur@lemmy.world to linuxmemes@lemmy.worldEnglish · edit-23 months agomessage-square82fedilink
minus-squareKaryoplasma@discuss.tchncs.delinkfedilinkarrow-up4·edit-23 months agoDelete 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.
minus-squareIsoSpandy@lemm.eelinkfedilinkarrow-up2·3 months agoSo just replace my old licence file with the GPL?
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.
So just replace my old licence file with the GPL?
Yeah.