On 14.08.2008 18:16:29 Kenneth D Weinert wrote: > So, the first difficulty: > > I finally found the license info for the AFM component, but as far as > I can tell it's not online anywhere, just part of the distribution of > the AFM files. It's an HTML file. Do I add this file to the PDFBox > distribution and link to it, add the contents as some sort of popup, ... ?
I'll look into this when I've got time. If something's unclear just note it on this list (as you've done) so it doesn't get forgotten. > Just curious what the established way of doing this is. Unfortunately, not all projects do it exactly the same way. I usually like to keep the license text near to the third-party libraries along with a separate text file that lists all the third-parties. If I were you, I'd just look after the website and let us committers deal with the legal details. I don't want you to lose a lot of time over that. > I'll also be putting together some patches (I presume you'd want > individual file patches) to fix some minor typos in the online > documentation. Yes, an SVN diff is the preferred format for changed files. http://apache.org/dev/contributors.html#patches New files are sometimes easier to pack into a ZIP file. The file(s) should then be attached to a JIRA issue. BTW, if your changes are non-trivial (i.e. have some amount of original work on your part in it) we need a CLA (Contributor License Agreement) on file with the ASF: http://apache.org/licenses/#clas I know paperwork is silly but we're all on the safer side this way. Anyway, thanks already for the time you're investing here! I don't have too much time available to look after PDFBox but I'll do my best. Please be patient if you don't always get an immediate answer. > > Jeremias Maerki wrote: > > On 13.08.2008 21:09:51 Ken Weinert wrote: > >> On the page about redistributing PDFBox > >> > (http://incubator.apache.org/pdfbox/userguide/redistribution.html#Redistributing+PDFBox) > >> it says "The below table summarizes the licences that are included ..." > >> but it really only mentions components. > >> > >> I will presume that the required elements are also all open source, but > >> just because it's open source doesn't mean that it's compatible with all > >> uses. > > > > On first glace, I'd say yes, although I haven't looked closer at the > > "JAI-CMM" entry. > > > >> Could the actual licenses be added to that page? > > > > That will surely be done in time as part of the preparations for the > > first Apache release. > > > >> Would it be better if I submitted a patch to the page that included the > >> licenses (or at least made the component name a link to the license info > >> for that component)? > > > > Absolutely. Any help is very welcome!!! > > > > Thanks, > > Jeremias Maerki > > > > - -- > Ken Weinert > http://quarter-flash.com Jeremias Maerki
