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. Matt On Tuesday, April 24, 2018 at 9:19:58 AM UTC-5, Zellyn wrote: > > On Tuesday, April 24, 2018 at 9:38:36 AM UTC-4, matthe...@gmail.com wrote: >> >> For Go you may want to consider the AGPL which also requires any network >>> app to provide its source code. These GNU licenses are from the Free >>> Software Foundation which has a traditionally radical philosophy toward >>> computers: https://www.gnu.org/licenses/why-affero-gpl.en.html So far I >>> personally like the AGPL approach. >> >> > Nobody at Google (or many other companies) can touch anything AGPL. > > Zellyn > -- 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.
