Hi, I agree with almost all of Alex's answers here, will comment on a few below.
What's important IMO with those changes is to back them with JIRA issues, to be able to track what's been changed in those Batik/Velocity forks. And, as Dave says, the goal should be to contribute the changes back to those projects (after the parity release I assume). On Fri, Jun 8, 2012 at 7:36 PM, Alex Harui <aha...@adobe.com> wrote: > On 6/8/12 8:28 AM, "Carol Frampton" <cfram...@adobe.com> wrote: >> ...Should I remove all the copyrights in the files and replace them with >> Apache >> v2 licenses? > I'm pretty sure answer is no. This is third-party works as covered in [1]... Agreed. > ...We don't have to make RAT run clean, whatever it does find must be clearly > in Category A or B. I wish RAT had some filter for that, and maybe I will > put one together if I find time.... RAT does have an exclusions list, where you can define files that it ignores. Having that list in svn makes things traceable. >> ...There are also README and some other text files and Java manifest files >> without copyrights. Are those exceptions? > If we can put Apache headers in without breaking something, we probably > should.... I wouldn't do that for small files that have no creative content - I don't think we really care about copyright notices in READMEs and manifest files, especially if we inherit them from another Apache project. >> If so, I wonder why RAT doesn't >> know the .mf file type. I know that there is suppose to be a LICENSE and a >> NOTICE file in the META-INF directory of each jar.... It's probably not used often, and you should be able to add that to RAT's exclusions list. HTH, -Bertrand > [1] http://www.apache.org/legal/src-headers.html
