3 ms·
Totally understand. I went back and forth many times around the license. I figured I could always open it up more in the future. Happy to clarify use cases o
by sawka 5y ago
Totally understand. I went back and forth many times around the license. I figured I could always open it up more in the future. Happy to clarify use cases or write a proprietary license if need be if a particular corp is worried. Also, it is unencumbered if you use it for internal facing applications (the use case I was most focused on).
- netr0ute 5y agoWhy make it so complicated? I would just use a vanilla AGPLv3.
- sawka 5y agoThis project spun out of my startup https://dashborg.net https://dashborg.net and I'm hoping to create a hosted SaaS service out of it with security/authentication and maybe some other premium features. I don't have that service yet, and I didn't want to get "cloud-poached" before I even had a chance to launch. That being said, I get the concerns. I'll likely re-license the core as vanilla MIT in the future.
- jabbany 5y agoCouldn't a cloud service just get a team to do some clean room reverse engineering to make a similar or even compatible tool without violating copyright? IIRC software licenses are copyright licenses (you can't use the code / make derivatives based on the code) not patents (you can't make a product based on this _idea_).
- sawka 5y agoSure they could, but projects at big companies move so slowly, it would take them months just to staff the team, get a manager, a designer, and project-manager, and engineers assigned :) . Not really trying to restrict it, I want people to use it (even for free)! I just also want to be able to launch my startup
- netr0ute 5y agoIronic, because getting "cloud-poached" would be one of my end goals.