On Mon, Dec 10, 2012 at 6:09 AM, Donal Lafferty <donal.laffe...@citrix.com> wrote: > Does anyone have a link describing the attribution requirements for code > licensed under ASF v2.0? > > I noticed some driver code on another CloudOS project that appears to be a > derivative of a previous version of the same driver in that code base. The > comments are unchanged and the structure very similar. Both versions of the > driver are ASF v2.0, but the derivative work lacks the original author's > copyright notice. > > Is this legit under ASF 2.0? > > I'd have thought at the very least you had to carry forward notice from the > original work.
Take a look at section 4 of the ASLv2 license itself [1]. It lays out the rules of derivative work for ASLv2 licensed software. In our case, we would probably do the following: 1 - Retain the original copyright notice(s) at the top of the file(s) in question 2 - Add a comment to header of the source code files in question, noting that they have been modified from the original source project's version. 3 - Include the relevant contents of the source project's NOTICE file in our own This all assumes that the code in question is licensed under ASLv2, but specifics may lead to a slightly different interpretation. Are you asking for the purpose of a CloudStack code submission? Or are you asking more generally about ASLv2? -chip [1] http://www.apache.org/licenses/LICENSE-2.0.html