3 ms·
The license you had until yesterday (which he's free to use the code under as it was available yesterday) allows him to sell a service that uses your program.
by _-___________-_ 7y ago
The license you had until yesterday (which he's free to use the code under as it was available yesterday) allows him to sell a service that uses your program.
If he's actually redistributing the software without including the license then that's another thing.
- _-___________-_ 7y agoHmm: "ektor.io is not a service, it's a software you own forever after downloading it" IANAL but I believe the Apache license should be retained on any unmodified parts of the program (and distributed with it)
- rolltiide 7y agoHow does that work btw, would I just use rollback the commit and branch from the old commit if I wanted the apache license version? I've also seen people try to erase old commits to change licenses, I was wondering what that actually means for use since the code would have still had an older version with the more liberal license
- _-___________-_ 7y agoIf you have, or can get, a copy of the code that was released with the old license, you can use it under that license.
- rolltiide 7y agoNice yeah. Most of the time I just skip the controversies on Hackernews and stick with my philosophy of "just clone and move on" You can tell when some repositories are going to be hot and removed soon, often times that nukes the forks too. So just download.