4 ms·
I have been toying with a similar idea, but for born-FOSS source projects. I like copyleft licenses but I find the legalese in them too complex and I fear that
by gioele 10y ago
I have been toying with a similar idea, but for born-FOSS source projects.
I like copyleft licenses but I find the legalese in them too complex and I fear that they will cause problem down the road because of changes in the legal landscape. I am also worried about leaving code around that is useful but unusable by other for legal reasons. For all these reasons I would like to license my projects like this:
* They are born AGPLv3/OHL.
* All the published revisions older than 5 years are
released into the public domain (CC0).
Simple and easy to state, incredibly complex to write down. Especially if you want to make it enforceable without me (or the other contributors) being alive. From what I understand, the concept of a "legally binding promise" is even more fuzzy across the jurisditions than that of a "simple" copyleft license.
- perlgeek 10y ago> From what I understand, the concept of a "legally binding promise" is even more fuzzy across the jurisditions than that of a "simple" copyleft license. Couldn't you work around this by granting usage rights now that you're only allowed to exercise in three years? Contracts with specified durations are quite common, including those whose start date is in the future (like, renting a booth or a flat for a specific duration).