You are viewing a plain text version of this content. The canonical link for it is here.
Posted to legal-discuss@apache.org by "Henri Yandell (JIRA)" <ji...@apache.org> on 2009/08/18 06:45:14 UTC

[jira] Created: (LEGAL-60) Bugs found in 3rd party code

Bugs found in 3rd party code
----------------------------

                 Key: LEGAL-60
                 URL: https://issues.apache.org/jira/browse/LEGAL-60
             Project: Legal Discuss
          Issue Type: Question
            Reporter: Henri Yandell



Noticed one project asking on the list about patches they had made to an external 3rd party library. Realized that we may want a specific FAQ item along the lines of:

Qn: "In the course of developing an Apache project, we have found a bug in a 3rd party dependency, and would like to provide the fix we have created back to the original source. Can it be licensed under the original source's license? "

---

In some sense this is a no-op. The submitter licenses their code to the ASF and are welcome to license it to someone else. There is room for greyness if the individual submitting the code to the ASF is not the individual submitting it to the upstream source. I don't see us caring but the details there might get tricky.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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


[jira] Commented: (LEGAL-60) Bugs found in 3rd party code

Posted by "Niclas Hedhman (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/LEGAL-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12744367#action_12744367 ] 

Niclas Hedhman commented on LEGAL-60:
-------------------------------------

The question has a "would like to provide the fix back to the original source", actually makes the question irrelevant to ASF. There is no need to provide the 'fix' via ASF infrastructure or release procedures, hence doesn't touch us at all. It will be a "fix" from one unaffiliated individual or group of individuals to the project in question. Whether or not they also contribute to ASF under different licenses are irrelevant.

> Bugs found in 3rd party code
> ----------------------------
>
>                 Key: LEGAL-60
>                 URL: https://issues.apache.org/jira/browse/LEGAL-60
>             Project: Legal Discuss
>          Issue Type: Question
>            Reporter: Henri Yandell
>
> Noticed one project asking on the list about patches they had made to an external 3rd party library. Realized that we may want a specific FAQ item along the lines of:
> Qn: "In the course of developing an Apache project, we have found a bug in a 3rd party dependency, and would like to provide the fix we have created back to the original source. Can it be licensed under the original source's license? "
> ---
> In some sense this is a no-op. The submitter licenses their code to the ASF and are welcome to license it to someone else. There is room for greyness if the individual submitting the code to the ASF is not the individual submitting it to the upstream source. I don't see us caring but the details there might get tricky.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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


[jira] Closed: (LEGAL-60) Bugs found in 3rd party code

Posted by "Henri Yandell (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/LEGAL-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Henri Yandell closed LEGAL-60.
------------------------------

    Resolution: Invalid

The bit I was thinking of was one in which the patch is made to a copy at the ASF, and then a separate person wants to send the patch to the upstream project.

The answer is probably to go work with the original patch creator.

Resolving as 'INVALID'.

> Bugs found in 3rd party code
> ----------------------------
>
>                 Key: LEGAL-60
>                 URL: https://issues.apache.org/jira/browse/LEGAL-60
>             Project: Legal Discuss
>          Issue Type: Question
>            Reporter: Henri Yandell
>
> Noticed one project asking on the list about patches they had made to an external 3rd party library. Realized that we may want a specific FAQ item along the lines of:
> Qn: "In the course of developing an Apache project, we have found a bug in a 3rd party dependency, and would like to provide the fix we have created back to the original source. Can it be licensed under the original source's license? "
> ---
> In some sense this is a no-op. The submitter licenses their code to the ASF and are welcome to license it to someone else. There is room for greyness if the individual submitting the code to the ASF is not the individual submitting it to the upstream source. I don't see us caring but the details there might get tricky.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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