Bruno, thanks for your answers.
Am 17.02.2010 00:53, schrieb Bruno Lowagie: > The license change was announced on different occasions, at least 6 > months before the actual change. > Still I think, a prominent news item on the website or a prominent README_LICENSE_CHANGE.TXT in the tarballs would help. I just can say that In my case, I did not notice the change. Adding the iText JAR to a project was a no-brainer for me until now, comparable with, say, adding Apache Commons Logging to it. Eclipse will import the new namespace with one single click on the "Quick Fix" menu item so this is not something where I give much thought about normally. > Companies asking a quote are contacted and asked about the context of > their use of iText. Even people using free mail addresses such as > hotmail, with nicknames such as "harakiri" received a reply, but no quote. > I don't know who "harakiri" is. I wrote an email with complete company information including our address, list of executives etc. to Mark Storer, Paolo Soares and Mark Stephens on 10/14/2009. Mark replied that Paolo or Bruno would be able to do it. Paolo did not respond. When I asked for the email address of Bruno I got the answer that I should contact a person named Andrew to reach Bruno (!?!?). I contacted Andrew but he replied Bruno wouldn't have time to do it. Although both Mark and Andrew were very friendly and helpful, the whole story does not give the impression of professionality about iText Software Corp. By the way, in the end, we ditched this part of the requirements specification in accordance with the customer and instead used a simple workaround. > I don't recall such a request; unless you're the one hiding behind the > nickname harakiri. > See above. Some other questions: Since AGPL is not compatible with neither closed-source licenses nor the Apache License nor the LGPL there are lots of projects which will get problems now because of the license change. Have you asked major players like Jasper Reports what they will do now? I guess that changing the Jasper Reports license to AGPL is not an option... You mentioned in another thread that it is forbidden to change the "producer line" of iText. I see that the AGPL has a provision for that (7b). Does this also hold for version 4.2.0 which is licensed LGPL/MPL? I cannot see a provision like that in the original LGPL/MPL. Markus ------------------------------------------------------------------------------ SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev _______________________________________________ iText-questions mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/itext-questions Buy the iText book: http://www.1t3xt.com/docs/book.php Check the site with examples before you ask questions: http://www.1t3xt.info/examples/ You can also search the keywords list: http://1t3xt.info/tutorials/keywords/
