I am working on a project to generate a 508 compliant annual PDF Publication from our database using iText 7 java library. This library works great for accessible PDFs. We are in the process of procurement to get a commercial license to use for our future applications.
For this particular application however, we are planning to create an executable java jar file that will run once a year in a server that can connect to our databases. It will sit in the backend and we will run the application manually or using a cronjob (java -jar application). Since this publication has to come out by the end of September and since procurement process takes around 4 to 6 months, we are planning to make this application open sourced. The resulting PDF however will be put as a download in our closed application manually. I read through many websites about the extent of using AGPL V3 license but was still unclear. I also saw this:
- May I use AGPL license in a desktop application without providing the source code?
- Can I legally use iText under the AGPL license if my application is only available on a local area network?
- AGPLv3 source redistribution: when does it apply to my code for a server-side Java app using an AGPL-licensed library?
There were so many mixed answers out there and also our scenario is bit different. So here are my questions:
- In our scenario, do we need to make the source code open?
- If yes to question 1, are we allowed to use iText 7 as an open source alternative in this particular scenario?
- If yes to question 2, what portion of the source code needs to be open? Since we host the file (even though manually added) in a separate public but closed application, do we need to make the source code of this application also open?
Update: To clarify things a bit, for our current application, we are using the community version of iText 7 and are in no way modifying the source code.
It would be nice if we could hear back from the author himself. (@BrunoLowagie; @bruno-lowagie)