@FiloSottile question: does using an external Go library require the entire codebase to be licensed in a compatible manner (e.g. GPLv3 dep)
-
-
Replying to @AndreaBarisani
@AndreaBarisani IANAL, but I'd say that if you vendor it, it's totally a derived work, if you just use it I guess it's like linking.1 reply 0 retweets 0 likes -
Replying to @FiloSottile
@AndreaBarisani OTOH if you distribute binaries, you are again making derived work I'm afraid. But really IANAL1 reply 0 retweets 0 likes -
Replying to @FiloSottile
@FiloSottile the plan for now is conditional usage (via build tags) and avoid distributeing binaries, I'd like to avoid BSD-style > GPLv31 reply 0 retweets 0 likes -
Replying to @AndreaBarisani
@AndreaBarisani As long as you don't vendor that *might* be fine, yeah1 reply 0 retweets 0 likes -
Replying to @FiloSottile
@FiloSottile we are not, anyway I reached out to the author to see his take on this ;), worst case we re-license but I'd like to avoid it1 reply 0 retweets 0 likes -
Replying to @AndreaBarisani
@AndreaBarisani@FiloSottile maybe@BrandonPhilips or@mjg59 know how this works?3 replies 0 retweets 0 likes -
Replying to @gtank__
@_gtank@AndreaBarisani@FiloSottile (I am not a lawyer, not legal advice, etc)1 reply 0 retweets 1 like
@mjg59 @_gtank @FiloSottile implicit IANAL all over, yes :). Thx!
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.