So I'm working on an #OrgMode document that's probably about 2/3 #emacs #lisp code. I'm planning on releasing it shortly, but I'm not sure what to do about the licensing. Normally I use the #AGPL for my code, but since this isn't strictly code, I'm wondering if some version of the #CreativeCommons license might be a better fit. Do they have a #copyleft variant?
FoxFunction
in reply to Jonathan Lamothe • • •Jonathan Lamothe likes this.
bignose
in reply to Jonathan Lamothe • • •No reason to deviate from #AGPL for this, @me.
The document has an obvious source form. It consists (in part) of program code. There should be no problem applying AGPL conditions for recipients.
Do you anticipate any specific problems with that plan?
Jonathan Lamothe
in reply to bignose • •Ross A. Baker
in reply to Jonathan Lamothe • • •CC-BY-SA is Creative Commons' answer to copyleft. CC-BY-SA-4.0 is one-way compatible into GPLv3. (The 4.0 is important!)
There's no CC license that forces code all the way to AGPLv3, but you can say "code blocks AGPLv3, the rest CC-BY-SA-4.0." You have to choose whether a single license or the Affero clause matters more.
Jonathan Lamothe likes this.
Jonathan Lamothe
in reply to Jonathan Lamothe • •So, I decided to just go full AGPL. Perhaps a weird choice, but it gets the job done.
codeberg.org/jlamothe/lord-cha…
Please note: this is a work in progress.