5 ms·
KISS: Treat it as any other proprietary license. In theory 4 (or whatever) years later some version will become licensed under Open Source license but by that
by PeterZaitsev 4y ago
KISS: Treat it as any other proprietary license.
In theory 4 (or whatever) years later some version will become licensed under Open Source license but by that time it will be well past EOL ridden with bugs and security holes and unsafe to use.
Of course (in theory) you could take on maintaining such version yourself in practice it does not make any practical sense
- ianbutler 4y agoI'm actually looking to apply this to one of my own projects. But I'd like something where for each major version it changes to AGPL 1 year (the change date) after it becomes available. That will be somewhat defeated if everything regardless of version just changes to AGPL 4 years later. You could very reasonably say "Who knows if you'll be working on this 4 years from now"* but I still think it makes sense to fully understand the conditions of a license before slapping it on my stuff. Especially if my initial intent is business related. *And I think this is generally a good way to stop abandonware
- PeterZaitsev 4y agoTypically it is used similary to EOL in Software. You know when PostgreSQL 15 goes EOL it is different from PostgreSQL 14 Same here - the change date is different for major versions - when you create new major version of product it gets change date adjusted.