3 ms·
On a related note: is there a chance in hell of re-licensing RStudio such that it is not AGPLv3?
by codex 13y ago
On a related note: is there a chance in hell of re-licensing RStudio such that it is not AGPLv3?
- jcheng 13y agoWe'll happily sell you a commercial license if you'd prefer that. Email us at info@rstudio.com for details. If you mean a different open-source license, sorry, we don't plan to relicense.
- aspensmonster 13y agoAnd from a different direction... Thank you for using the AGPLv3 and GPLv3 licenses in your work :)
- dllthomas 13y agoSeconded.
- codex 13y agoThe issue is one of evaluation: I am prohibited from using the software at all, even on toy problems, to determine whether I'd like to buy a commercial license. Crazy, perhaps, but that's how hostile the AGPLv3 is to businesses.
- jcheng 13y agoGotcha. Well, I'm sure we can arrange an eval if you e-mail us. Forgive us for not having these options on our website (yet), it took us a little bit by surprise that some companies might want the option to relicense.
- dllthomas 13y agoThis seems incorrect, unless you are prohibited purely by fiat (in which case it's a demonstration of how hostile your particular business is to the AGPLv3, not vice-versa). Requirements of GPL or AGPL licenses don't encumber you if you're not interacting with others (distributing software to them, or - with AGPL - providing a service).
- tommorris 13y agoThat is a problem with your employer, not a problem with the AGPL...
- belorn 13y agoCould you define what kind of toy problem that would be hindered by the license? I could speculate. Maybe your company has patents covering RStudio software and wants to go suing its customers. That would indeed pose a problem with AGPLv3. Maybe your company produces devices which have web servers in them, and those servers are going to host "toy" pages which uses Shiny, and the devices are locked down with DRM which prevent modification to Shiny. I guess it would be possible... Or maybe the company does not want to ever give out code under any circumstances, regardless if it's a toy project with no inherent value to the company. This is clearly possible, which is why a dual licensing scheme sometimes is a good choice. I am intensively curious about which one it is.