IANAL, so there's that. Given that AGPL applies even when the code isn't distributed but is run as a service behind a network point, I think it would apply to this case too. For example, if someone took your library and ran it as a server, they'll have to release *your* code too under AGPL I think.
@sriku.org interesting! I don't see how they could do that since they wouldn't have permission to relicense my code
Where does the barrier sit? I'm fine licensing llm-pdf-to-images under AGPL but I'm not OK doing the same for llm itself - that loads functionality from llm-to-pdf-images via […]
With Apache 2, there is no compulsion to release the source of your library. So in this case Apache 2 is not applicable since the server creator is being forced to release source? Maybe worth running a tool that checks license compatibility or something.
Comments
I'm distributing a single line, "PyMuPDF" a https://github.com/simonw/llm-pdf-to-images/blob/0ce38f1e0e5effc1ecff0aafd009417d7d78a745/pyproject.toml#L12 - which causes the user's system to […]
Where does the barrier sit? I'm fine licensing llm-pdf-to-images under AGPL but I'm not OK doing the same for llm itself - that loads functionality from llm-to-pdf-images via […]