Comment by 0x0 | Hacker News Reader

Comment by 0x0 | Hacker News Reader

Parent Full thread

Well, the question here is if the PHP code someone wrote to power a public web site would be considered to be a partly derivative or combined work of the AGPL testing library, wouldn't it?

Just a leftover test function inside the main app referencing this library would probably be enough to consider it a derivative or combined work, no?

(Not sure how HTTP comes into play regarding the linking and combining of a project and this AGPL library?)

I think the terms are difficult to understand. In the general case who knows what a library author intended or how think they understand the license??

(Also, claiming GPL only pertains to binary software sounds really quite imprecise too. Just because you receive source code does not mean you can use it or distribute it in any way you see fit. You would still need to abide by whatever license accompanies the non-binary software)

I'm not sure why you would have a test function in the main app as opposed to separate testing - but yes, it would.

The intention of the AGPL is clear in my opinion and not really up for author interpretation. If someone is accessing code on a server (binary or interpreted), they have a right to obtain and modify that source code.

Aside from SaaS testing suites, I do not know of any examples where test code is accessed by users over a network.

It is, thus, 100% OK to use this source code to test a closed source project.

If the GPL had the same added clause as the AGPL, then there would be a serious number of infringing web apps.

The first sentence of the wikipedia page explains it best: "Both versions of the AGPL were designed to close a perceived application service provider "loophole" (the "ASP loophole") in the ordinary GPL, where by using but not distributing the software, the copyleft provisions are not triggered."

No use == no copyleft requirement, and I would hope it's pretty clear that simply by having a piece of AGPL software in the same directory as another piece of software that it is not inherently using it.

OK then I guess we agree in this instance. :)

I'd just like to clarify the problem I see with this: When the library is added to the project and is on the include-path (in the IDE, whatever), I think there's a non-zero risk that some developer on the project ends up putting a reference to it in the main app. At least it's something one needs to be careful about.

Reply on news.ycombinator.com