← Back to context Comment by pwdisswordfishz 1 year ago They don't have to release source for internal forks. 4 comments pwdisswordfishz Reply wyldfire 1 year ago They do if they're AGPL licensed and the internal form software is used to provide a user facing service. amszmidt 1 year ago But then it isn’t “internal”… zelcon 1 year ago It’s too hard to determine what pieces of your stack interact with public-facing services, particularly in a monorepo with thousands of developers. The effort involved and the legal risk if you get it wrong makes it an easy nope. Just ban AGPL. 1 reply →
wyldfire 1 year ago They do if they're AGPL licensed and the internal form software is used to provide a user facing service. amszmidt 1 year ago But then it isn’t “internal”… zelcon 1 year ago It’s too hard to determine what pieces of your stack interact with public-facing services, particularly in a monorepo with thousands of developers. The effort involved and the legal risk if you get it wrong makes it an easy nope. Just ban AGPL. 1 reply →
amszmidt 1 year ago But then it isn’t “internal”… zelcon 1 year ago It’s too hard to determine what pieces of your stack interact with public-facing services, particularly in a monorepo with thousands of developers. The effort involved and the legal risk if you get it wrong makes it an easy nope. Just ban AGPL. 1 reply →
zelcon 1 year ago It’s too hard to determine what pieces of your stack interact with public-facing services, particularly in a monorepo with thousands of developers. The effort involved and the legal risk if you get it wrong makes it an easy nope. Just ban AGPL. 1 reply →
They do if they're AGPL licensed and the internal form software is used to provide a user facing service.
But then it isn’t “internal”…
It’s too hard to determine what pieces of your stack interact with public-facing services, particularly in a monorepo with thousands of developers. The effort involved and the legal risk if you get it wrong makes it an easy nope. Just ban AGPL.
1 reply →