www-legal-discuss mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marvin Humphrey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LEGAL-295) Merge others codes having same license but different copyrights
Date Fri, 24 Mar 2017 16:43:41 GMT

    [ https://issues.apache.org/jira/browse/LEGAL-295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15940689#comment-15940689

Marvin Humphrey commented on LEGAL-295:

I submit that a file which is copied from Spring is not a contribution; it is a bundled dependency
a.k.a. third-party work, and should be treated as such.

See http://www.apache.org/legal/src-headers.html#3party for instructions on how to treat bundled
third-party works.

Note that it can be tricky and laborious to figure out how the licensing and notification
requirements of a large project apply when selecting only a small piece out, but that's a
task you're signing up for.  (Though this case may be unusually easy, since Spring is ALv2
and from what I can tell doesn't provide a NOTICE file.)

In general, I would expect to see third-party code separated much more cleanly from the main
code base than we see in this pull request.  I suggest reworking the patch to avoid intermingling
the Spring code with your own.

Having established that we are bundling a third-party work, the answer about how to handle
@author tags should now become clear:

* Leave any @author tags in bundled third-party code alone.
* Don't add @author tags representing third-party authors to the main code base.

> Merge others codes having same license but different copyrights
> ---------------------------------------------------------------
>                 Key: LEGAL-295
>                 URL: https://issues.apache.org/jira/browse/LEGAL-295
>             Project: Legal Discuss
>          Issue Type: Question
>            Reporter: Yasser Zamani
> As an ASF contributor, in one of my pull requests, I copied and merged other ones codes
to an existing ASF project. Both are under same license, Apache License V2, but the other
one code has the below copyright at his file header:
> {noformat}
>  * Copyright 2002-2014 the original author or authors.
> {noformat}
> and existing ASF project has:
> {noformat}
>  * Copyright 2002-2006,2009 The Apache Software Foundation.
> {noformat}
> While the other one code has defined several `@author` tags above his class definition
(rather than any other place e.g. methods and etc) and while our existing ASF project does
not accept `@author` tag:
> # Is it legal to not include `@author` tags and the copyright statement?
> # If no, how to handle this?
> Thanks in advance!

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org

View raw message