💾 Archived View for ew.srht.site › en › 2020 › 20201217-towards-a-proper-flightlog-3.gmi captured on 2024-06-16 at 13:40:26. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2022-03-01)
-=-=-=-=-=-=-
I wrote:
More things to contemplate:
* Adding explicit licenses to scripts, images, text.
I came across this entry today, where the author complains about "a thief" that had put the authors source code on github.
https://cheapskatesguide.org/articles/my-stolen-code-on-github.html
https://github.com/Mr-Steal-Your-Script/bwfForum
It seems that the author was not willing to give up control over the code, at least not in the sense to put his work under GPL or AGPL. He added a homebrew sort of license. In my opinion, if you do not want to give up "control" over a piece of source code, then do not publish it. Once published, it is out of your hand.
For source code, my personal list is short: GPLv3+ or AGPLv3+ for network facing services, or CC0. I translate CC0 into "Do as you please, but leave me alone".
See
for a comprehensive list of licenses and their texts.
Disclaimer: I am not a laywer.