Markus Meyer wrote: > 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.
I asked Andrew what this was about. He forwarded me this: iText Software wrote you on "14. Oktober 2009 um 18:57" > I just heard back from Bruno re your request. "I won't have time to do > this for many months." You replied on the same day, saying "thanks for the update". You were asked to contact Andrew because I was at the film festival in Ghent at that time (October 6-17): I only went online to check my mail, giving priority to Andrew's mail. His answer was correct: I don't have the time to accept development assignments as long as the book isn't finished. > 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... Don't worry, JasperSoft was contacted long before the license change. JasperSoft and other projects can get out of trouble by moving to the AGPL. If that's not an option, they are probably making money with their project, in which case they should have no problem buying a license ;-) > 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. The rule is present in the source code. You can't miss that obligation if you try to change that line. Moreover there are a number of secret fingerprints in each iText generated PDF that allow us to find out if iText was used or not. It's also impossible to miss the AGPL license, because: - it's mentioned in every source code header. - due to the change in package names, you can't just "upgrade" from the MPL/LGPL version to the AGPL version. - At the same time of the license change we removed obsolete code, - and we moved to Java 5. That's not what I'd call a "silent" license change... I don't really agree with "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." We've even broken the automatic Maven updates so that people couldn't say: "we upgraded to iText 5 and we didn't know the license had changed." I don't see what else we could have done on top of the changes listed above. best regards, Bruno ------------------------------------------------------------------------------ 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/
