| Wed Jul 24 04:02:02 2024 by Mizuki |
| The current versioning system (month - year) doesn’t really work if you have more than one releases in a month - like just now. (Jul 9 - Jul 22). Users looking at the code or using "planet -R" will only see "July 2024" and have a hard time knowing which version it is. Maybe it'd be better to change the version string to something like "2024.07.22"? Also, do you have any plan to adopt maybe a more formal FOSS license for your code? Like BSD or Expat etc… |
| Tue Jul 30 09:56:04 2024 by Torben |
| Yes, using exact dates for versioning is a good idea. I will do so from the next release onwards. As for licensing, I haven't given it much thought. I lean toward a Creative Commons license, but I'm not sure how well that works for code. |
| Tue Jul 30 10:59:17 2024 by Mizuki |
| Unfortunately CC explicitly recommend against using it for software... https://opensource.stackexchange.com/questions/9242/why-does-creative-commons-recommend-not-using-cc-by-licenses-for-software |
| Thu Jun 18 07:48:43 2026 by rubiefawn |
| The current license has a "copyleft" clause: > Redistribution of the program or parts or modifications thereof in any form must contain the original copyright notice and must in no way restrict distribution of other versions of the program over what is stipulated in this copyright notice. Adopting the MPLv2 or GPLv3 might be more appropriate than BSD/Expat. https://opensource.org/license/MPL-2.0 https://opensource.org/license/gpl-3.0 |