Disclaimer: IANAL!!!! The answer are provided without any guarantee of accuracy.
On 22.01.2007 07:08:04 Praveen Nayak wrote: > Hi, > > I want to use the Batik viewer as a part of my application, and the > license file that shipped along with Batik managed to confuse me. > > There are a few gaps in my understanding of the license. It will be > nice if anyone can fill them up for me. > > 1. Should the Batik license be added at the place the JAR files > (batik-all.jar etc) are placed or where the license of the > application is placed? That's more or less up to you. It should be in a place where people can easily identify which license applies to which artifact. The next Batik release will even contain the license in the META-INF of each JAR. That will make it easier. > 2. Can the license file name be changed (from the current name - > license) if it clashes with other file name? Yes, of course. We do the same for third-party JARs in the lib directory. > 3. I have made a small modification to one of the files that is a > part of Batik. Is the requirement only that I should update the > source .java file comments to add info that I changed it, package > it into a jar and ship that jar, or should I mention this change somewhere > else as well. If you ship a binary, the change is not visible, so it makes sense to note that in either the NOTICE file or a separate README. > 4. The end of the license file has the line: > Copyright [yyyy] [name of the copyright owner] and instructions to modify > it. > > Where must this be modified? In this same license file or somewhere else? That only applies if you build your own ALv2 licensed project. At the ASF, we use a slightly different license header now in our source files. If you modify a source file from Batik, you can add the above line with your own copyright (which then applies to the part you changed). But that is not strictly mandatory. However, if you modified Batik in a way that Batik would profit from it, please consider sending a patch to improve it so you don't have to track all changes in the future. > I am sorry if my questions appear naive, but this is the first time > I am using an open source project. Don't worry. These are all no-nonsense questions. Jeremias Maerki --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
