6 ms·
II.B.15: use, under any circumstance, any open source software subject to the GNU Affero General Public License v.3, or greater; That's spooky. Any idea why?
by orwin 7y ago
II.B.15: use, under any circumstance, any open source software subject to the GNU Affero General Public License v.3, or greater;
That's spooky. Any idea why?
- joelhaasnoot 7y agoI don't fully understand the context, but I'm guessing that if you provide a service using software that's AGPL licensed and use Square to sell it, they have no way of complying to the AGPL terms of providing end users (your customers) with the source code and/or a link to it.
- Illniyar 7y agoThe service provider might be breaking the AGPL, but square isn't liable. It isn' using the AGPL it self and isn't a party to the copyright contract.
- the_mitsuhiko 7y agoIf they need to redistribute some AGPL content they are liable.
- Illniyar 7y agoI don' see square having any service that offers fulfillment (for example where you can download your order). Even if they do though it would be a stretch to hold them liable, it's like requiring github to be agpled if you upload your agpl code there.
- the_mitsuhiko 7y agoThis is for their store system: https://squareup.com/us/en/online-store https://squareup.com/us/en/online-store
- eesmith 7y agoI have two problems with accepting that as a correct interpretation: 1) they place no restrictions on any other license. What if I use the Server Side Public License, or something else with a similar requirement to distribute? 2) the specifically say "v3", while the original AGPL also had that requirement. I, like Illniyar, also think the AGPLv3 doesn't have that interpretation in the first place. At what point would Square have accepted the copyright license?
- logicallee 7y agoI looked it up. Agpl is meant to close the loophole whereby, you know Google can use GPL tools while they index the web but I can't demand a copy of their private repos source code, since I just get to use the result (over the web). Agpl closes this loophole. I think gpl is enough for web apps. I don't think I should have the right to demand all of gmail's or google search's server-side code if they use but don't distribute gpl software as part of making it. But all companies need to steer really clear of agpl code. Even editing an image using an agpl image editor could taint the image, even though you're not exporting any code. I would absolutely demand that anyone working for me not use any agpl software. I think it would taint even the copywrite on a logo. Maybe I would be tainted by publishing a document they wrote in an agpl text editor, even if they license it to me. Just my impression after 5 minutes of research. If someone has more detailed legal position please do correct whatever I got wrong.
- snvzz 7y ago>But all companies need to steer really clear of agpl code. Even editing an image using an agpl image editor could taint the image, even though you're not exporting any code. This is an outrageous claim. Citation needed.
- logicallee 7y agoDude, I literally didn't know what agpl is. I found: >Just my impression after 5 minutes of research. If someone has more detailed legal position please do correct whatever I got wrong. after 5 minutes of Googling. downvoting my personal research results after 5 minutes of Googling won't get anyone to answer with the corrected version. I had never heard of agpl until I googled it and summarized what I saw. It's a summary. if you put up a web app where you modify open source software as part of your stack, you have to publish those changes if people ask for them. Even if you are not distributing those changes. (This is my impression.) I look forward to a correction from an expert - it's why I posted what I found. (Yes, what I found was outrageous.)
- snvzz 7y ago