@clacke
> That's your whole VM right there, and even stuff outside it
I have some sympathy for the goals of a license that says 'if you want to use our software on your server, you have to release the code source of all the software on your server under any FSF or OSI approved licenses'.
But the devil is in the details. Where does software end and sensitive data begin? If you set out to enforce compliance with such a license, how could you know you'd succeeded without full server access?
@notclacke The #CAL is another one I haven't look at the details of yet. One concern I have with over-enthusiastic extendion of #copyleft beyond what the #AGPL does (one that Perens and Kuhn might share) is that it could make copyleft licenses even scarier to company lawyers, increasing the fervency of the anti-copyleft PR messaging many companies target at younger developers.
@clacke @strypey in hindsight, the drama over the drafting process of the #Holochain #CAL seems to be fear of it being more effective in promoting #FLOSS than #FSF or #OSI #Licence s. You did voice concerns about FUD, but wouldn't you say that FUD against GPL failed (people serious about software were not all sheeple)? And I bet the people behind that FUD themselves free-loaded off GPL'ed software (and stayed silent on the more effective AGPL - probably stayed silent on the CAL too?).