So it sounds like the AGPL is a good license to choose if you want to keep your code from being used by big companies… ;-)
> On Apr 25, 2018, at 8:48 AM, 'David Chase' via golang-nuts > <golang-nuts@googlegroups.com> wrote: > > > > On Tuesday, April 24, 2018 at 10:45:35 AM UTC-4, matthe...@gmail.com wrote: > I’m curious if some companies juggle the GPL. I guess if the app is used > internally only then there’s no problem with accidentally requiring a > proprietary program to be released as source code to the world. I’d have > thought the case would be the same with the AGPL. Do people count as > individuals in a corporate license with the ability to freely redistribute? > > I can understand completely avoiding the issue. Language is interpretable and > only a court or whatever would decide what was really agreed to. The FSF > seems to put a lot of work into building up their licenses with legal > precedence. > > I have never worked anywhere that could touch AGPL code. > It was at the level of "just don't, and don't waste anyone's time asking. > Don't." > This is not legal advice, I am just telling you what the policy is/was at all > these companies. > > > > -- > You received this message because you are subscribed to the Google Groups > "golang-nuts" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to golang-nuts+unsubscr...@googlegroups.com > <mailto:golang-nuts+unsubscr...@googlegroups.com>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
