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
