You are viewing a plain text version of this content. The canonical link for it is here.
Posted to legal-discuss@apache.org by "Brett Porter (JIRA)" <ji...@apache.org> on 2009/11/16 12:07:39 UTC

[jira] Created: (LEGAL-65) storing a patch to an EPL library in the svn repository

storing a patch to an EPL library in the svn repository
-------------------------------------------------------

                 Key: LEGAL-65
                 URL: https://issues.apache.org/jira/browse/LEGAL-65
             Project: Legal Discuss
          Issue Type: Question
            Reporter: Brett Porter


The Maven project would like to add a performance testing project that utilises an EPL library, which is possible under the current policies. However, it is required to apply a patch to the EPL library to use in this project. It is not intended to distribute the patched EPL binary, or the EPL sources themselves, but to instruct the user of the project to check out the EPL sources themselves and apply the supplied patch. 

Is it acceptable to include the patch file in the Apache svn repository?

[relevant thread: http://mail-archives.apache.org/mod_mbox/maven-dev/200911.mbox/%3cD9933C42-CBBC-4F66-9CA8-79A987BF658A@apache.org%3e]

-- 
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-65) storing a patch to an EPL library in the svn repository

Posted by "Brett Porter (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/LEGAL-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12778767#action_12778767 ] 

Brett Porter commented on LEGAL-65:
-----------------------------------

yes, temporary until applied upstream, though it was noted that it may take a Very Long Time for such a thing to occur - so it could be a fairly permanent fixture

> storing a patch to an EPL library in the svn repository
> -------------------------------------------------------
>
>                 Key: LEGAL-65
>                 URL: https://issues.apache.org/jira/browse/LEGAL-65
>             Project: Legal Discuss
>          Issue Type: Question
>            Reporter: Brett Porter
>
> The Maven project would like to add a performance testing project that utilises an EPL library, which is possible under the current policies. However, it is required to apply a patch to the EPL library to use in this project. It is not intended to distribute the patched EPL binary, or the EPL sources themselves, but to instruct the user of the project to check out the EPL sources themselves and apply the supplied patch. 
> Is it acceptable to include the patch file in the Apache svn repository?
> [relevant thread: http://mail-archives.apache.org/mod_mbox/maven-dev/200911.mbox/%3cD9933C42-CBBC-4F66-9CA8-79A987BF658A@apache.org%3e]

-- 
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] Assigned: (LEGAL-65) storing a patch to an EPL library in the svn repository

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

Henri Yandell reassigned LEGAL-65:
----------------------------------

    Assignee: Brett Porter

> storing a patch to an EPL library in the svn repository
> -------------------------------------------------------
>
>                 Key: LEGAL-65
>                 URL: https://issues.apache.org/jira/browse/LEGAL-65
>             Project: Legal Discuss
>          Issue Type: Question
>            Reporter: Brett Porter
>            Assignee: Brett Porter
>
> The Maven project would like to add a performance testing project that utilises an EPL library, which is possible under the current policies. However, it is required to apply a patch to the EPL library to use in this project. It is not intended to distribute the patched EPL binary, or the EPL sources themselves, but to instruct the user of the project to check out the EPL sources themselves and apply the supplied patch. 
> Is it acceptable to include the patch file in the Apache svn repository?
> [relevant thread: http://mail-archives.apache.org/mod_mbox/maven-dev/200911.mbox/%3cD9933C42-CBBC-4F66-9CA8-79A987BF658A@apache.org%3e]

-- 
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-65) storing a patch to an EPL library in the svn repository

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

Henri Yandell closed LEGAL-65.
------------------------------

    Resolution: Fixed

> storing a patch to an EPL library in the svn repository
> -------------------------------------------------------
>
>                 Key: LEGAL-65
>                 URL: https://issues.apache.org/jira/browse/LEGAL-65
>             Project: Legal Discuss
>          Issue Type: Question
>            Reporter: Brett Porter
>            Assignee: Brett Porter
>
> The Maven project would like to add a performance testing project that utilises an EPL library, which is possible under the current policies. However, it is required to apply a patch to the EPL library to use in this project. It is not intended to distribute the patched EPL binary, or the EPL sources themselves, but to instruct the user of the project to check out the EPL sources themselves and apply the supplied patch. 
> Is it acceptable to include the patch file in the Apache svn repository?
> [relevant thread: http://mail-archives.apache.org/mod_mbox/maven-dev/200911.mbox/%3cD9933C42-CBBC-4F66-9CA8-79A987BF658A@apache.org%3e]

-- 
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-65) storing a patch to an EPL library in the svn repository

Posted by "Henri Yandell (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/LEGAL-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12778750#action_12778750 ] 

Henri Yandell commented on LEGAL-65:
------------------------------------

Seems fine to me. Could be used as a how-to for needing to modify a 3rd party category B dependency.

Is this temporary until the patch is applied upstream?

> storing a patch to an EPL library in the svn repository
> -------------------------------------------------------
>
>                 Key: LEGAL-65
>                 URL: https://issues.apache.org/jira/browse/LEGAL-65
>             Project: Legal Discuss
>          Issue Type: Question
>            Reporter: Brett Porter
>
> The Maven project would like to add a performance testing project that utilises an EPL library, which is possible under the current policies. However, it is required to apply a patch to the EPL library to use in this project. It is not intended to distribute the patched EPL binary, or the EPL sources themselves, but to instruct the user of the project to check out the EPL sources themselves and apply the supplied patch. 
> Is it acceptable to include the patch file in the Apache svn repository?
> [relevant thread: http://mail-archives.apache.org/mod_mbox/maven-dev/200911.mbox/%3cD9933C42-CBBC-4F66-9CA8-79A987BF658A@apache.org%3e]

-- 
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-65) storing a patch to an EPL library in the svn repository

Posted by "Henri Yandell (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/LEGAL-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12786876#action_12786876 ] 

Henri Yandell commented on LEGAL-65:
------------------------------------

Some further thoughts:

*1* Apache committer submitting a patch they've authored back to a non-Apache project. Non-issue; we don't consider them an Apache committer when in that role.
*2* Apache committer storing a patch at Apache to a 3rd party project [category A/B]. Not an issue.
*3* Apache committer submitting a patch another Apache committer authored, and stored at Apache, back to a non-Apache project. A little messier. EIther a) they get the permission of the original author (i.e. what they really get is that individuals copy and not the one at Apache) or b) it's Apache sending it back. In neither case am I concerned. Slightly more complex if the patch at Apache has had multiple committers working on it as item a) would need multiple approvals.
*4* Apache project hosting lots of 3rd party patches - potentially a bad community smell. Though I could see Gump doing such a thing without it being a bad smell (for example).

Did this go ahead Brett? Can you document how it was managed, it would be nice to standardize the approach so that it's easier for projects to click when they have a bad smell. Important items imo would be the patch being in a decoupled place, and information existing on its submission upstream. 

Note that for some cases we may be happy patching the category B source and distributing that as our binary. 

> storing a patch to an EPL library in the svn repository
> -------------------------------------------------------
>
>                 Key: LEGAL-65
>                 URL: https://issues.apache.org/jira/browse/LEGAL-65
>             Project: Legal Discuss
>          Issue Type: Question
>            Reporter: Brett Porter
>
> The Maven project would like to add a performance testing project that utilises an EPL library, which is possible under the current policies. However, it is required to apply a patch to the EPL library to use in this project. It is not intended to distribute the patched EPL binary, or the EPL sources themselves, but to instruct the user of the project to check out the EPL sources themselves and apply the supplied patch. 
> Is it acceptable to include the patch file in the Apache svn repository?
> [relevant thread: http://mail-archives.apache.org/mod_mbox/maven-dev/200911.mbox/%3cD9933C42-CBBC-4F66-9CA8-79A987BF658A@apache.org%3e]

-- 
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-65) storing a patch to an EPL library in the svn repository

Posted by "Craig Russell (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/LEGAL-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779002#action_12779002 ] 

Craig Russell commented on LEGAL-65:
------------------------------------

I see no legal or social barriers to the project supplying a patch file to a third party component that is then applied by a user.


> storing a patch to an EPL library in the svn repository
> -------------------------------------------------------
>
>                 Key: LEGAL-65
>                 URL: https://issues.apache.org/jira/browse/LEGAL-65
>             Project: Legal Discuss
>          Issue Type: Question
>            Reporter: Brett Porter
>
> The Maven project would like to add a performance testing project that utilises an EPL library, which is possible under the current policies. However, it is required to apply a patch to the EPL library to use in this project. It is not intended to distribute the patched EPL binary, or the EPL sources themselves, but to instruct the user of the project to check out the EPL sources themselves and apply the supplied patch. 
> Is it acceptable to include the patch file in the Apache svn repository?
> [relevant thread: http://mail-archives.apache.org/mod_mbox/maven-dev/200911.mbox/%3cD9933C42-CBBC-4F66-9CA8-79A987BF658A@apache.org%3e]

-- 
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