3 ms·
If there is, say, a high-quality AGPL hash-table implementation, and I combine that into my TCP stack, the resulting work is AGPL, sure. But I can't actually us
by geofft 9y ago
If there is, say, a high-quality AGPL hash-table implementation, and I combine that into my TCP stack, the resulting work is AGPL, sure. But I can't actually use the TCP stack - I have no way to make source code available to people who connect to my TCP stack. There's no TCP option for a URL for source code.
So, I cannot run the program as I wish for any purpose. I can run it for limited purposes: those where there is no network interaction, and those where the network interaction is rich enough to support offering source code.
- haldean 9y agoYou do not have to offer the source code using the source code or through the service it provides. If you just throw it up on GitHub or whatever it still counts.
- geofft 9y agoThat still means that I must offer the entire source code for my TCP stack to the world. That's not how any other free software license works - if I'm running a GPL'd TCP stack like Linux's, and I've made modifications to it, I don't have to offer the sources for it unless I'm distributing the program. Merely using the modified code to be on the network does not imply a source obligation. I mean, it is probably reasonable, in the abstract, to have licenses that say "You may not modify this software internally and use it at all unless you make the changes public." Plenty of licenses have required that. Those licenses are non-free in the FSF sense, and they have rejected such licenses before.