Re: cvs commit: xml-fop/src/hyph cs.xml da.xml de.xml de_DR.xml el.xml en_GB.xml en_US.xml fr.xml nl.xml no.xml sk.xml tr.xml
With the help of many people I've done an licensing audit last March. See the Wiki page [1] for the whole protocol. The original Dutch hyphenation file that was used to create nl.xml is published under the LPPL license which includes a restriction that makes it impossible for The Apache Foundation to use and distribute. [1] http://nagoya.apache.org/wiki/apachewiki.cgi?FOPAudits/March2003 On 27.02.2004 21:14:40 Simon Pepping wrote: On Fri, Feb 27, 2004 at 06:24:38PM -, [EMAIL PROTECTED] wrote: jeremias2004/02/27 10:24:38 Removed: src/hyph cs.xml da.xml de.xml de_DR.xml el.xml en_GB.xml en_US.xml fr.xml nl.xml no.xml sk.xml tr.xml Log: Removed legally problematic files as done for the maintenance branch. What are those legal problems? The Dutch file nl.xml is based on the hyphenation patterns created by the Dutch TeX user group, and are freely distributed with TeX software. Why cannot FOP distribute them? Jeremias Maerki
Re: Applying the new license
The (documentation) sources all need a license header (docs and src/documentation). That's one part remaining. The other is the rest of the hyphenation files. But there it may not be so simple as to apply the Apache license. We will need to doublecheck the audit results and see where we can apply the ALv2 and where we have to do something else (getting grants, or doing something like we do for the JARs in our repository). BTW, we need to update our site to reflect that new releases and especially new contributions by developers will fall under the new license. The new license contains in implicit copyright grant which makes our life a lot easier when we accept contributions. And what's equally important is that it's a lot easier for contributors, too, because they don't have to send in grants for bigger contributions anymore. See section 5 in the new license. But all that doesn't mean we can neglect our duty to check the origin of contributions. Especially for the hyphenation patterns this may still be problematic because someone who does a hyphenation file conversion may not be entitled to submit it to the ASF because he is not the (only) copyright holder and license restrictions may not allow our distributing the file. On 28.02.2004 00:27:19 Peter B. West wrote: Apart from the hyphenation problem below, what manual work remains? Jeremias Maerki
RE: [VOTE] Remove Visitor Patterns from AbstractRenderer.java
-Original Message- From: Glen Mazza [mailto:[EMAIL PROTECTED] This simplification, even if temporary, drops the average IQ needed to understand the Renderer classes perhaps 30 points, more into my range*, hopefully opening the door for more developers to start filling out these renderers. Glen *That of a house plant. Give yourself some credit, man! Besides that, higher IQ only means 'faster understanding under the same circumstances' and not 'more understanding, period'... background knowledge remains the more fundamental prerequisite. Anyway, I can see now that the 'simplification' in question at least offers the benefit of needing a re-implementation of text-justification (among others) which will fit more harmoniously into the redesigned API, instead of merely copying the Maintenance way of doing things and having to 'rape' the new design because we so rabidly want to keep that part working as it did before. It just might prove more worthwhile to be forced to re-think the process of justification in terms of the 1.0 API... let's hope so. Cheers, Andreas
Re: Applying the new license
On Feb 28, 2004, at 1:22 AM, Jeremias Maerki wrote: Especially for the hyphenation patterns this may still be problematic because someone who does a hyphenation file conversion may not be entitled to submit it to the ASF because he is not the (only) copyright holder and license restrictions may not allow our distributing the file. On 28.02.2004 00:27:19 Peter B. West wrote: Apart from the hyphenation problem below, what manual work remains? Jeremias Maerki It would also be nice, if there were some sort of repository or links page on the FOP site where people can go to get hyphenation files that cannot be included in FOP because they do not meet the needs of the ALv2 (assuming there are no negative legal ramifications). That way, this valuable information is still accessible, and simplifies the process of getting the information. It might mean a little more legwork on our part, but it may end up being 'worth it' in the long run. Also, I don't know how I can be of use, but if there's anything I can do in this regard (e.g., take a text blurb and 'apply' it to a set of files), I'd be happy to help. I just need a little direction on how to contribute. Web Maestro Clay
