he/him 
because we’d be set upon by gangs of frenzied eric raymond disciples
-
-
-
Replying to @b0neskull @maybekatz
...but yes, I’ll try it. I still don’t really understand the difference between GPL flavors though, given that I work primarily in javascript (does the LGPL even make sense for interpreted code?)
1 reply 0 retweets 1 like -
Replying to @b0neskull @maybekatz
LGPL basically says that if you modified the library you MUST also ship your changes under the same or a compatible license. But it doesn't add any requirements to the larger application. GPL counts using the library as a change, and so the application using it must also be GPL.
1 reply 0 retweets 1 like -
This is the reason that the FSF doesn't really suggest anyone use the LGPL--it doesn't bring any meaningful teeth. Mostly, if you had to patch a library, you WANT the upstream author to take your changes just so you can stop floating a patch, regardless of license.
1 reply 0 retweets 1 like -
The GPL by contrast means (or is intended to mean) that the entire software ecosystem that your contribution lives must be free software.
1 reply 0 retweets 1 like -
This falls down a bit around "distribution", because the licensing teeth only take effect when you want to distribute copies. And if you're running a service with it, but never give the software to anyone, that isn't distribution. And that's what the AGPL tries to address.
1 reply 0 retweets 3 likes -
And that concludes my IANAL licensing talk. =p `Hopefully not too cringey for actual lawyers.
1 reply 0 retweets 2 likes -
Something I've never heard anyone address is: For front end libraries, does including them on your website constitute a derivative copy? My v IANAL gut feeling would be yes, and that would definitely result in the whole front end needing to be GPL, and likely the backend too.
2 replies 0 retweets 0 likes -
many lawyers would agree, which is why any viral license is forbidden on most big company websites, on any part of the stack.
1 reply 0 retweets 2 likes
Replying to @ljharb @ReBeccaOrg and
My internal code got flagged just because it had a string that contained "AGPL". The "fear" is real.
1:36 PM - 31 Aug 2019
0 replies
0 retweets
5 likes
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.