Live data from Hacker News

OwnCloud Infinite Scale added EULA that prohibits commercial use [pdf]

github.com

111–112 of 112 posts

Re: OwnCloud Infinite Scale added EULA that prohibits commercial use [pdf]

#111

Earlier quoted context omitted.

It is a mistake for the intent of GPL licenses because if the place they received it closes down it can become difficult to get the source / de facto closed source. The solution to this is for every place using the software to become a mirror or otherwise allow access to the source code in the same way as if they were distributing GPL binaries, correct.

> It is a mistake for the intent of GPL licenses because if the place they received it closes down it can become difficult to get the source / de facto closed source. Are there any examples of AGPLv3 software that has become de facto closed because the original vendor no longer distributes it and nobody else distributes their copy? Sounds like a made up problem, theoretically possible but so unlikely as to not be an…

> but it doesn't seem like a big problem in practice.

Oh good, now you're all caught up with what I wrote in the first place.

Re: OwnCloud Infinite Scale added EULA that prohibits commercial use [pdf]

#112
post #110

Earlier quoted context omitted.

https://www.gnu.org/licenses/old-licenses/gpl-2.0-faq.html#G... "arms length communication".

Thanks for the link. However, after reading the whole section I am left believing that using the API of an AGPL project would indeed be considered "incorporating" it. Note how the "arms length" usage, as described, mentions completely separated software such as a shell and a notepad application. The separation between a shell and a notepad (i.e. different applications altogether), or a kernel and a compiler (i.e. the…

here is my example that i was involved in. a proprietary software "app" wants to build a system for doing some work. They also need some accounting to be done so instead of reinventing the wheel, they were recommended to use an agpl covered accounting software as a DB. the software would send commands and the accounting package would record them and spit out reports using api.

They were told, this use case is allowed under GPL because the proprietary software was using the agpl one as a data store without any modifications. The license requirements of code share would be enough in the license file and link to the source code. Virality would not be attached in this case

Post reply on HN