Licensing #2
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
rsstube is currently "GPLv3 or later"...
Right now, I own the code, so I can do whatever I want. If at some point, other people want to submit non-public domain code, it will help if I already have appropriate license policies in place.
Some licensing choices I might consider:
adding an iOS exception
Would this Python project even be useful on iOS?
limiting to GPL version 3
How much do I trust the FSF? How concerned am I about compatibility with hypothetical GPLv4 feed readers?
relicensing to AGPL
How concerned am I about someone trying to run rsstube as a service? How problematic of a license do I consider the AGPL? I probably would not take this route. I'm only very recently becoming aware of the issues with the AGPL, but this Twitter thread by marcan42, for example, makes some good points, including, among other things, arguing that the AGPL is not a free software license.
dedicating to the public domain (or using an equivalent license)
Is copyleft worthwhile for this project?
I'm thinking about relicensing to "GPLv2 or later" or "GPLv2 or GPLv3" because I don't want to make rsstube incompatible with GPLv2 feed readers.
I will relicense rsstube as GPLv2 or later. At this time, I don't want to add an iOS exception, but I would consider it if there was a reason.
Changed in
db1f10b691
I think I will make this program public domain/equivalent.
I would like to make rsstube possible for any free feed reader to incorporate without licensing compatibility issues. I think I'm not particularly concerned with what non-free software might arise from this. (Honestly, the most likely possibility is some sort of web-based rsstube-as-a-service thing, and under the current GPL licensing, I'm not defending against that anyway.)
Furthermore, this project is primarily just documenting how various websites work, in code form. The useful part of the code is informational, not creative.