You are viewing a plain text version of this content. The canonical link for it is here.
Posted to legal-discuss@apache.org by Stefano Bagnara <ap...@bago.org> on 2008/08/14 16:01:08 UTC
Reuse of ASF source code and NOTICE
Hi all,
In a recent commit to Apache JAMES Mime4J I introduced a
Base64OutputStream released from another ASF PMC (Apache MyFaces).
Should we add anything to our NOTICE?
I ask this because I happen to look at wicket main NOTICE file and I see
they made a reference to each file they copied around from other ASF
products:
http://svn.apache.org/repos/asf/wicket/trunk/NOTICE
I referenced the source in the svn commit and I added a line to the
source file header saying "This class has been copied from Apache
MyFaces Trinidad 1.2.8"
I thought the main "This product includes software developed at The
Apache Software Foundation (http://www.apache.org/)." allowed us to
include any source from any ASF project without further references, but
I'd like to have confirmation for this.
In this specific case I add that the NOTICE for the ASF MyFaces Trinidad
package I downloaded to get the Base64OutputStream.java file include this:
-------------
Portions of this software were originally based on the following:
- software copyright (c) 2000-2006, Oracle Corp, <http://www.oracle.com/>.
and are licensed to the Apache Software Foundation under the
"Software Grant and Corporate Contribution License Agreement"
-------------
I tried to understand if the Base64OutputStream was from this
grant/contribution or not, but I can only find this:
http://svn.apache.org/viewvc/myfaces/trinidad/trunk/trinidad-api/src/main/java/org/apache/myfaces/trinidad/util/Base64OutputStream.java?revision=404824&view=markup
and the original incubated code:
http://svn.apache.org/viewvc/incubator/adffaces/trunk/adf-faces/adf-faces-api/src/main/java/org/apache/myfaces/adf/util/Base64OutputStream.java?revision=404824&view=markup&pathrev=404824
The first version of the NOTICE file is newer than the import above and
already includes the Oracle reference:
http://svn.apache.org/viewvc/myfaces/trinidad/trunk/NOTICE.txt?revision=466284&view=markup
From my understanding (also scanning markmail for "Oracle" +
"Trinidad") Oracle contributed minor parts of the code (mainly message
bundle translations and a portlet-bridge code.. but MyFaces team
included a generic reference to Oracle in the main NOTICE.
Looking in trinidad-1.2.8-src-all.zip java files I see many of them have
a version header with an "oracle" reference in the path:
-----
@version $Name: $ ($Revision:
adfrt/faces/adf-faces-api/src/test/java/oracle/adf/view/faces/convert/ConverterTestCase.java#0
$) $Date: 17-oct-2005.16:28:54 $
------
The Base64OutputStream is not one of them.
Stefano
---------------------------------------------------------------------
DISCLAIMER: Discussions on this list are informational and educational
only. Statements made on this list are not privileged, do not
constitute legal advice, and do not necessarily reflect the opinions
and policies of the ASF. See <http://www.apache.org/licenses/> for
official ASF policies and documents.
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org
Re: Reuse of ASF source code and NOTICE
Posted by Stefano Bagnara <ap...@bago.org>.
Matthias Wessendorf ha scritto:
>> If Oracle provided a notice and has not removed it, that notice
>> requirement needs to carry forward to any ASF project that includes
>> that code. That being said, I see no requirement to acknowledge
>> another ASF project, but you are, of course, welcome to do so.
>
> means an extension of our (Trinidad) code, needs to include the ORA
> notice as well ?
>
> -Matthias
If you have it in Trinidad NOTICE than anyone using that code will have
to inherit your NOTICE content.
If you want to put a statement about the source of the code but you
don't need it to be inherited by ALv2 targeted users then you better
should put the statement in a README file or anything else that is not
the NOTICE file.
The NOTICE purpose is to have the list of credits to be "relayed" when
you redistribute a product or parts of a product licensed under the
Apache License v2 terms.
At least this is what I understood so far and I'm not a lawyer.
Stefano
---------------------------------------------------------------------
DISCLAIMER: Discussions on this list are informational and educational
only. Statements made on this list are not privileged, do not
constitute legal advice, and do not necessarily reflect the opinions
and policies of the ASF. See <http://www.apache.org/licenses/> for
official ASF policies and documents.
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org
Re: Reuse of ASF source code and NOTICE
Posted by Matthias Wessendorf <ma...@apache.org>.
Hi,
late in the game...
(I work for Oracle)
>> I'd like to understand if the fact that Oracle donated the code under the
>> "Software Grant and Corporate Contribution License Agreement" makes their
>> NOTICE sentence "redundant" or if it's still a requirement to keep that
>> sentence in any product reusing code from their artifacts.
>
> It is not automatically redundant. It is quite possible for someone
> to provide us a grant, and to include a notice on the software that
> they contribute. An employee of Oracle could also remove the notice,
> we should not.
We added that notice during undergoing incbuation. So we kept it afterwards.
Does this mean we have to remove the notice on the Oracle code ?
Or should/cloud we keep it ?
>
>> The sentence from their NOTICE seems to me not a requirement because
>> otherwise we would have a NOTICE including references to each contributor
>> that contributed code under the CLA/CCLA, but I'm not a lawyer and I would
>> feel happier if you can confirm it.
>>
>> Otherwise I guess I would have to add this to our NOTICE:
>> ------------
>> The Base64OutputStream class included in this package is based on code from
>> Apache MyFaces Trinidad. Portions of Apache MyFaces Trinidad were originally
>> based on the following:
>>
>> software copyright (c) 2000-2006, Oracle Corp, <http://www.oracle.com/>.
>> and are licensed to the Apache Software Foundation under the
>> "Software Grant and Corporate Contribution License Agreement"
>> -------------
>
> If Oracle provided a notice and has not removed it, that notice
> requirement needs to carry forward to any ASF project that includes
> that code. That being said, I see no requirement to acknowledge
> another ASF project, but you are, of course, welcome to do so.
means an extension of our (Trinidad) code, needs to include the ORA
notice as well ?
-Matthias
>
>> Stefano
>>
>> ---------------------------------------------------------------------
>> DISCLAIMER: Discussions on this list are informational and educational
>> only. Statements made on this list are not privileged, do not
>> constitute legal advice, and do not necessarily reflect the opinions
>> and policies of the ASF. See <http://www.apache.org/licenses/> for
>> official ASF policies and documents.
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
>> For additional commands, e-mail: legal-discuss-help@apache.org
>
> ---------------------------------------------------------------------
> DISCLAIMER: Discussions on this list are informational and educational
> only. Statements made on this list are not privileged, do not
> constitute legal advice, and do not necessarily reflect the opinions
> and policies of the ASF. See <http://www.apache.org/licenses/> for
> official ASF policies and documents.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
> For additional commands, e-mail: legal-discuss-help@apache.org
>
>
--
Matthias Wessendorf
Need JSF and Web 2.0?
http://code.google.com/p/facesgoodies
further stuff:
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
mail: matzew-at-apache-dot-org
---------------------------------------------------------------------
DISCLAIMER: Discussions on this list are informational and educational
only. Statements made on this list are not privileged, do not
constitute legal advice, and do not necessarily reflect the opinions
and policies of the ASF. See <http://www.apache.org/licenses/> for
official ASF policies and documents.
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org
Re: Reuse of ASF source code and NOTICE
Posted by Sam Ruby <ru...@intertwingly.net>.
On Tue, Aug 19, 2008 at 5:43 AM, Stefano Bagnara <ap...@bago.org> wrote:
> Sam Ruby ha scritto:
>>
>> On Thu, Aug 14, 2008 at 10:01 AM, Stefano Bagnara <ap...@bago.org> wrote:
>>>
>>> Hi all,
>>>
>>> In a recent commit to Apache JAMES Mime4J I introduced a
>>> Base64OutputStream
>>> released from another ASF PMC (Apache MyFaces). Should we add anything to
>>> our NOTICE?
>>> [...]
>>> I referenced the source in the svn commit and I added a line to the
>>> source file header saying "This class has been copied from Apache
>>> MyFaces Trinidad 1.2.8"
>>>
>>> I thought the main "This product includes software developed at The
>>> Apache Software Foundation (http://www.apache.org/)." allowed us to
>>> include any source from any ASF project without further references, but
>>> I'd like to have confirmation for this.
>>
>> There is no legal requirement for one ASF project to give attribution
>> to another ASF project. This, however, does not mean that attribution
>> requirements imposed by third parties can be dropped merely because
>> the code was obtained from an ASF source instead of directly from the
>> third party.
>>
>>> In this specific case I add that the NOTICE for the ASF MyFaces Trinidad
>>> package I downloaded to get the Base64OutputStream.java file include
>>> this:
>>> -------------
>>> Portions of this software were originally based on the following:
>>>
>>> - software copyright (c) 2000-2006, Oracle Corp,
>>> <http://www.oracle.com/>.
>>> and are licensed to the Apache Software Foundation under the
>>> "Software Grant and Corporate Contribution License Agreement"
>>> -------------
>>> [...]
>>
>> Is is the responsibility of the PMCs to ensure that IPR policies are
>> followed. This should be brought up first with the MyFaces PMC. If
>> this does not result in adequate resolution, then either the Legal
>> Affairs Committee or the board will get involved.
>
> A MyFaces developer replied that the Base64OutputStream I "copied" from
> their product was part of the original contribution by Oracle.
>
> --- Quote ---
> the code was donated to the ASF in 2006, when Oracle donated
> "Trinidad" (formal ADF Faces 10.x)
> This code is now licensed under the Apache 2.0 license.
> -------------
>
> My understanding is that ALv2 tell me that I HAVE TO copy their NOTICE
> content to our NOTICE.
>
> The fact is that we have an artifact being (got 3 +1 today, I've not voted
> yet) released without such a NOTICE (Oracle is not mentioned in our NOTICE).
>
> I'd like to understand if the fact that Oracle donated the code under the
> "Software Grant and Corporate Contribution License Agreement" makes their
> NOTICE sentence "redundant" or if it's still a requirement to keep that
> sentence in any product reusing code from their artifacts.
It is not automatically redundant. It is quite possible for someone
to provide us a grant, and to include a notice on the software that
they contribute. An employee of Oracle could also remove the notice,
we should not.
> The sentence from their NOTICE seems to me not a requirement because
> otherwise we would have a NOTICE including references to each contributor
> that contributed code under the CLA/CCLA, but I'm not a lawyer and I would
> feel happier if you can confirm it.
>
> Otherwise I guess I would have to add this to our NOTICE:
> ------------
> The Base64OutputStream class included in this package is based on code from
> Apache MyFaces Trinidad. Portions of Apache MyFaces Trinidad were originally
> based on the following:
>
> software copyright (c) 2000-2006, Oracle Corp, <http://www.oracle.com/>.
> and are licensed to the Apache Software Foundation under the
> "Software Grant and Corporate Contribution License Agreement"
> -------------
If Oracle provided a notice and has not removed it, that notice
requirement needs to carry forward to any ASF project that includes
that code. That being said, I see no requirement to acknowledge
another ASF project, but you are, of course, welcome to do so.
> Stefano
>
> ---------------------------------------------------------------------
> DISCLAIMER: Discussions on this list are informational and educational
> only. Statements made on this list are not privileged, do not
> constitute legal advice, and do not necessarily reflect the opinions
> and policies of the ASF. See <http://www.apache.org/licenses/> for
> official ASF policies and documents.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
> For additional commands, e-mail: legal-discuss-help@apache.org
---------------------------------------------------------------------
DISCLAIMER: Discussions on this list are informational and educational
only. Statements made on this list are not privileged, do not
constitute legal advice, and do not necessarily reflect the opinions
and policies of the ASF. See <http://www.apache.org/licenses/> for
official ASF policies and documents.
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org
Re: Re: Reuse of ASF source code and NOTICE
Posted by Matthias Wessendorf <ma...@apache.org>.
On Tue, Aug 19, 2008 at 1:08 PM, Stefano Bagnara <ap...@bago.org> wrote:
> Sam Ruby ha scritto:
>>
>> On Tue, Aug 19, 2008 at 5:43 AM, Stefano Bagnara <ap...@bago.org> wrote:
>>>
>>> Sam Ruby ha scritto:
>>>>
>>>> On Thu, Aug 14, 2008 at 10:01 AM, Stefano Bagnara <ap...@bago.org>
>>>> wrote:
>>>>>
>>>>> Hi all,
>>>>>
>>>>> In a recent commit to Apache JAMES Mime4J I introduced a
>>>>> Base64OutputStream
>>>>> released from another ASF PMC (Apache MyFaces). Should we add anything
>>>>> to
>>>>> our NOTICE?
>>>>> [...]
>>>>> I referenced the source in the svn commit and I added a line to the
>>>>> source file header saying "This class has been copied from Apache
>>>>> MyFaces Trinidad 1.2.8"
>>>>>
>>>>> I thought the main "This product includes software developed at The
>>>>> Apache Software Foundation (http://www.apache.org/)." allowed us to
>>>>> include any source from any ASF project without further references, but
>>>>> I'd like to have confirmation for this.
>>>>
>>>> There is no legal requirement for one ASF project to give attribution
>>>> to another ASF project. This, however, does not mean that attribution
>>>> requirements imposed by third parties can be dropped merely because
>>>> the code was obtained from an ASF source instead of directly from the
>>>> third party.
>>>>
>>>>> In this specific case I add that the NOTICE for the ASF MyFaces
>>>>> Trinidad
>>>>> package I downloaded to get the Base64OutputStream.java file include
>>>>> this:
>>>>> -------------
>>>>> Portions of this software were originally based on the following:
>>>>>
>>>>> - software copyright (c) 2000-2006, Oracle Corp,
>>>>> <http://www.oracle.com/>.
>>>>> and are licensed to the Apache Software Foundation under the
>>>>> "Software Grant and Corporate Contribution License Agreement"
>>>>> -------------
>>>>> [...]
>>>>
>>>> Is is the responsibility of the PMCs to ensure that IPR policies are
>>>> followed. This should be brought up first with the MyFaces PMC. If
>>>> this does not result in adequate resolution, then either the Legal
>>>> Affairs Committee or the board will get involved.
>>>
>>> A MyFaces developer replied that the Base64OutputStream I "copied" from
>>> their product was part of the original contribution by Oracle.
>>>
>>> --- Quote ---
>>> the code was donated to the ASF in 2006, when Oracle donated
>>> "Trinidad" (formal ADF Faces 10.x)
>>> This code is now licensed under the Apache 2.0 license.
>>> -------------
>>>
>>> My understanding is that ALv2 tell me that I HAVE TO copy their NOTICE
>>> content to our NOTICE.
>>>
>>> The fact is that we have an artifact being (got 3 +1 today, I've not
>>> voted
>>> yet) released without such a NOTICE (Oracle is not mentioned in our
>>> NOTICE).
>>>
>>> I'd like to understand if the fact that Oracle donated the code under the
>>> "Software Grant and Corporate Contribution License Agreement" makes their
>>> NOTICE sentence "redundant" or if it's still a requirement to keep that
>>> sentence in any product reusing code from their artifacts.
>>
>> It is not automatically redundant. It is quite possible for someone
>> to provide us a grant, and to include a notice on the software that
>> they contribute. An employee of Oracle could also remove the notice,
>> we should not.
>
> From my overview of svn history the NOTICE credit has been added by an ASF
> committer some months after the first code was imported in the incubator.
> Unfortunately it was not clear if this was a requirement from Oracle or
> simply to put some historical fact in the NOTICE file.
I think we added it just for incubator reasons?
This is a long time ago....
>
>>> The sentence from their NOTICE seems to me not a requirement because
>>> otherwise we would have a NOTICE including references to each contributor
>>> that contributed code under the CLA/CCLA, but I'm not a lawyer and I
>>> would
>>> feel happier if you can confirm it.
>>>
>>> Otherwise I guess I would have to add this to our NOTICE:
>>> ------------
>>> The Base64OutputStream class included in this package is based on code
>>> from
>>> Apache MyFaces Trinidad. Portions of Apache MyFaces Trinidad were
>>> originally
>>> based on the following:
>>>
>>> software copyright (c) 2000-2006, Oracle Corp, <http://www.oracle.com/>.
>>> and are licensed to the Apache Software Foundation under the
>>> "Software Grant and Corporate Contribution License Agreement"
>>> -------------
>>
>> If Oracle provided a notice and has not removed it, that notice
>> requirement needs to carry forward to any ASF project that includes
>> that code. That being said, I see no requirement to acknowledge
>> another ASF project, but you are, of course, welcome to do so.
>
> I did the mistake to commit the Base64OutputStream from MyFaces without
> fixing the NOTICE, but now my PMC is going to release an official version of
> our product including that class and not including the NOTICE credits to
> Oracle. I didn't vote for that release because I was trying to understand
> this issue.
>
> How should I deal with this? Who is liable for the release not including the
> credits in a similar case and what am I supposed to do to fix this ASAP?
>
> I made every PMC member aware of the issue before the release VOTE started
> and I fixed our NOTICE in trunk to include the above statement so that the
> next version will include it, but you know at most I can vote "-1" but this
> won't stop a release (majority and 3 +1 are already there).
>
> Stefano
>
> ---------------------------------------------------------------------
> DISCLAIMER: Discussions on this list are informational and educational
> only. Statements made on this list are not privileged, do not
> constitute legal advice, and do not necessarily reflect the opinions
> and policies of the ASF. See <http://www.apache.org/licenses/> for
> official ASF policies and documents.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
> For additional commands, e-mail: legal-discuss-help@apache.org
>
>
--
Matthias Wessendorf
Need JSF and Web 2.0?
http://code.google.com/p/facesgoodies
further stuff:
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
mail: matzew-at-apache-dot-org
---------------------------------------------------------------------
DISCLAIMER: Discussions on this list are informational and educational
only. Statements made on this list are not privileged, do not
constitute legal advice, and do not necessarily reflect the opinions
and policies of the ASF. See <http://www.apache.org/licenses/> for
official ASF policies and documents.
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org
Re: Re: Reuse of ASF source code and NOTICE
Posted by Stefano Bagnara <ap...@bago.org>.
Sam Ruby ha scritto:
> On Tue, Aug 19, 2008 at 5:43 AM, Stefano Bagnara <ap...@bago.org> wrote:
>> Sam Ruby ha scritto:
>>> On Thu, Aug 14, 2008 at 10:01 AM, Stefano Bagnara <ap...@bago.org> wrote:
>>>> Hi all,
>>>>
>>>> In a recent commit to Apache JAMES Mime4J I introduced a
>>>> Base64OutputStream
>>>> released from another ASF PMC (Apache MyFaces). Should we add anything to
>>>> our NOTICE?
>>>> [...]
>>>> I referenced the source in the svn commit and I added a line to the
>>>> source file header saying "This class has been copied from Apache
>>>> MyFaces Trinidad 1.2.8"
>>>>
>>>> I thought the main "This product includes software developed at The
>>>> Apache Software Foundation (http://www.apache.org/)." allowed us to
>>>> include any source from any ASF project without further references, but
>>>> I'd like to have confirmation for this.
>>> There is no legal requirement for one ASF project to give attribution
>>> to another ASF project. This, however, does not mean that attribution
>>> requirements imposed by third parties can be dropped merely because
>>> the code was obtained from an ASF source instead of directly from the
>>> third party.
>>>
>>>> In this specific case I add that the NOTICE for the ASF MyFaces Trinidad
>>>> package I downloaded to get the Base64OutputStream.java file include
>>>> this:
>>>> -------------
>>>> Portions of this software were originally based on the following:
>>>>
>>>> - software copyright (c) 2000-2006, Oracle Corp,
>>>> <http://www.oracle.com/>.
>>>> and are licensed to the Apache Software Foundation under the
>>>> "Software Grant and Corporate Contribution License Agreement"
>>>> -------------
>>>> [...]
>>> Is is the responsibility of the PMCs to ensure that IPR policies are
>>> followed. This should be brought up first with the MyFaces PMC. If
>>> this does not result in adequate resolution, then either the Legal
>>> Affairs Committee or the board will get involved.
>> A MyFaces developer replied that the Base64OutputStream I "copied" from
>> their product was part of the original contribution by Oracle.
>>
>> --- Quote ---
>> the code was donated to the ASF in 2006, when Oracle donated
>> "Trinidad" (formal ADF Faces 10.x)
>> This code is now licensed under the Apache 2.0 license.
>> -------------
>>
>> My understanding is that ALv2 tell me that I HAVE TO copy their NOTICE
>> content to our NOTICE.
>>
>> The fact is that we have an artifact being (got 3 +1 today, I've not voted
>> yet) released without such a NOTICE (Oracle is not mentioned in our NOTICE).
>>
>> I'd like to understand if the fact that Oracle donated the code under the
>> "Software Grant and Corporate Contribution License Agreement" makes their
>> NOTICE sentence "redundant" or if it's still a requirement to keep that
>> sentence in any product reusing code from their artifacts.
>
> It is not automatically redundant. It is quite possible for someone
> to provide us a grant, and to include a notice on the software that
> they contribute. An employee of Oracle could also remove the notice,
> we should not.
From my overview of svn history the NOTICE credit has been added by an
ASF committer some months after the first code was imported in the
incubator. Unfortunately it was not clear if this was a requirement from
Oracle or simply to put some historical fact in the NOTICE file.
>> The sentence from their NOTICE seems to me not a requirement because
>> otherwise we would have a NOTICE including references to each contributor
>> that contributed code under the CLA/CCLA, but I'm not a lawyer and I would
>> feel happier if you can confirm it.
>>
>> Otherwise I guess I would have to add this to our NOTICE:
>> ------------
>> The Base64OutputStream class included in this package is based on code from
>> Apache MyFaces Trinidad. Portions of Apache MyFaces Trinidad were originally
>> based on the following:
>>
>> software copyright (c) 2000-2006, Oracle Corp, <http://www.oracle.com/>.
>> and are licensed to the Apache Software Foundation under the
>> "Software Grant and Corporate Contribution License Agreement"
>> -------------
>
> If Oracle provided a notice and has not removed it, that notice
> requirement needs to carry forward to any ASF project that includes
> that code. That being said, I see no requirement to acknowledge
> another ASF project, but you are, of course, welcome to do so.
I did the mistake to commit the Base64OutputStream from MyFaces without
fixing the NOTICE, but now my PMC is going to release an official
version of our product including that class and not including the NOTICE
credits to Oracle. I didn't vote for that release because I was trying
to understand this issue.
How should I deal with this? Who is liable for the release not including
the credits in a similar case and what am I supposed to do to fix this ASAP?
I made every PMC member aware of the issue before the release VOTE
started and I fixed our NOTICE in trunk to include the above statement
so that the next version will include it, but you know at most I can
vote "-1" but this won't stop a release (majority and 3 +1 are already
there).
Stefano
---------------------------------------------------------------------
DISCLAIMER: Discussions on this list are informational and educational
only. Statements made on this list are not privileged, do not
constitute legal advice, and do not necessarily reflect the opinions
and policies of the ASF. See <http://www.apache.org/licenses/> for
official ASF policies and documents.
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org
Re: Reuse of ASF source code and NOTICE
Posted by Stefano Bagnara <ap...@bago.org>.
Sam Ruby ha scritto:
> On Thu, Aug 14, 2008 at 10:01 AM, Stefano Bagnara <ap...@bago.org> wrote:
>> Hi all,
>>
>> In a recent commit to Apache JAMES Mime4J I introduced a Base64OutputStream
>> released from another ASF PMC (Apache MyFaces). Should we add anything to
>> our NOTICE?
>> [...]
>> I referenced the source in the svn commit and I added a line to the
>> source file header saying "This class has been copied from Apache
>> MyFaces Trinidad 1.2.8"
>>
>> I thought the main "This product includes software developed at The
>> Apache Software Foundation (http://www.apache.org/)." allowed us to
>> include any source from any ASF project without further references, but
>> I'd like to have confirmation for this.
>
> There is no legal requirement for one ASF project to give attribution
> to another ASF project. This, however, does not mean that attribution
> requirements imposed by third parties can be dropped merely because
> the code was obtained from an ASF source instead of directly from the
> third party.
>
>> In this specific case I add that the NOTICE for the ASF MyFaces Trinidad
>> package I downloaded to get the Base64OutputStream.java file include this:
>> -------------
>> Portions of this software were originally based on the following:
>>
>> - software copyright (c) 2000-2006, Oracle Corp, <http://www.oracle.com/>.
>> and are licensed to the Apache Software Foundation under the
>> "Software Grant and Corporate Contribution License Agreement"
>> -------------
>> [...]
> Is is the responsibility of the PMCs to ensure that IPR policies are
> followed. This should be brought up first with the MyFaces PMC. If
> this does not result in adequate resolution, then either the Legal
> Affairs Committee or the board will get involved.
A MyFaces developer replied that the Base64OutputStream I "copied" from
their product was part of the original contribution by Oracle.
--- Quote ---
the code was donated to the ASF in 2006, when Oracle donated
"Trinidad" (formal ADF Faces 10.x)
This code is now licensed under the Apache 2.0 license.
-------------
My understanding is that ALv2 tell me that I HAVE TO copy their NOTICE
content to our NOTICE.
The fact is that we have an artifact being (got 3 +1 today, I've not
voted yet) released without such a NOTICE (Oracle is not mentioned in
our NOTICE).
I'd like to understand if the fact that Oracle donated the code under
the "Software Grant and Corporate Contribution License Agreement" makes
their NOTICE sentence "redundant" or if it's still a requirement to keep
that sentence in any product reusing code from their artifacts.
The sentence from their NOTICE seems to me not a requirement because
otherwise we would have a NOTICE including references to each
contributor that contributed code under the CLA/CCLA, but I'm not a
lawyer and I would feel happier if you can confirm it.
Otherwise I guess I would have to add this to our NOTICE:
------------
The Base64OutputStream class included in this package is based on code
from Apache MyFaces Trinidad. Portions of Apache MyFaces Trinidad were
originally based on the following:
software copyright (c) 2000-2006, Oracle Corp, <http://www.oracle.com/>.
and are licensed to the Apache Software Foundation under the
"Software Grant and Corporate Contribution License Agreement"
-------------
Stefano
---------------------------------------------------------------------
DISCLAIMER: Discussions on this list are informational and educational
only. Statements made on this list are not privileged, do not
constitute legal advice, and do not necessarily reflect the opinions
and policies of the ASF. See <http://www.apache.org/licenses/> for
official ASF policies and documents.
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org
Re: Reuse of ASF source code and NOTICE
Posted by Sam Ruby <ru...@intertwingly.net>.
On Thu, Aug 14, 2008 at 10:01 AM, Stefano Bagnara <ap...@bago.org> wrote:
> Hi all,
>
> In a recent commit to Apache JAMES Mime4J I introduced a Base64OutputStream
> released from another ASF PMC (Apache MyFaces). Should we add anything to
> our NOTICE?
>
> I ask this because I happen to look at wicket main NOTICE file and I see
> they made a reference to each file they copied around from other ASF
> products:
> http://svn.apache.org/repos/asf/wicket/trunk/NOTICE
>
> I referenced the source in the svn commit and I added a line to the
> source file header saying "This class has been copied from Apache
> MyFaces Trinidad 1.2.8"
>
> I thought the main "This product includes software developed at The
> Apache Software Foundation (http://www.apache.org/)." allowed us to
> include any source from any ASF project without further references, but
> I'd like to have confirmation for this.
There is no legal requirement for one ASF project to give attribution
to another ASF project. This, however, does not mean that attribution
requirements imposed by third parties can be dropped merely because
the code was obtained from an ASF source instead of directly from the
third party.
> In this specific case I add that the NOTICE for the ASF MyFaces Trinidad
> package I downloaded to get the Base64OutputStream.java file include this:
> -------------
> Portions of this software were originally based on the following:
>
> - software copyright (c) 2000-2006, Oracle Corp, <http://www.oracle.com/>.
> and are licensed to the Apache Software Foundation under the
> "Software Grant and Corporate Contribution License Agreement"
> -------------
>
> I tried to understand if the Base64OutputStream was from this
> grant/contribution or not, but I can only find this:
> http://svn.apache.org/viewvc/myfaces/trinidad/trunk/trinidad-api/src/main/java/org/apache/myfaces/trinidad/util/Base64OutputStream.java?revision=404824&view=markup
> and the original incubated code:
> http://svn.apache.org/viewvc/incubator/adffaces/trunk/adf-faces/adf-faces-api/src/main/java/org/apache/myfaces/adf/util/Base64OutputStream.java?revision=404824&view=markup&pathrev=404824
>
> The first version of the NOTICE file is newer than the import above and
> already includes the Oracle reference:
> http://svn.apache.org/viewvc/myfaces/trinidad/trunk/NOTICE.txt?revision=466284&view=markup
>
> From my understanding (also scanning markmail for "Oracle" + "Trinidad")
> Oracle contributed minor parts of the code (mainly message bundle
> translations and a portlet-bridge code.. but MyFaces team included a generic
> reference to Oracle in the main NOTICE.
>
> Looking in trinidad-1.2.8-src-all.zip java files I see many of them have a
> version header with an "oracle" reference in the path:
> -----
> @version $Name: $ ($Revision:
> adfrt/faces/adf-faces-api/src/test/java/oracle/adf/view/faces/convert/ConverterTestCase.java#0
> $) $Date: 17-oct-2005.16:28:54 $
> ------
>
> The Base64OutputStream is not one of them.
Is is the responsibility of the PMCs to ensure that IPR policies are
followed. This should be brought up first with the MyFaces PMC. If
this does not result in adequate resolution, then either the Legal
Affairs Committee or the board will get involved.
> Stefano
>
>
> ---------------------------------------------------------------------
> DISCLAIMER: Discussions on this list are informational and educational
> only. Statements made on this list are not privileged, do not
> constitute legal advice, and do not necessarily reflect the opinions
> and policies of the ASF. See <http://www.apache.org/licenses/> for
> official ASF policies and documents.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
> For additional commands, e-mail: legal-discuss-help@apache.org
- Sam Ruby
---------------------------------------------------------------------
DISCLAIMER: Discussions on this list are informational and educational
only. Statements made on this list are not privileged, do not
constitute legal advice, and do not necessarily reflect the opinions
and policies of the ASF. See <http://www.apache.org/licenses/> for
official ASF policies and documents.
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org
Re: Reuse of ASF source code and NOTICE
Posted by Stefano Bagnara <ap...@bago.org>.
William A. Rowe, Jr. ha scritto:
> Stefano Bagnara wrote:
>> In this specific thread I was asking how to deal with this as a
>> release has already been voted by my PMC including the "code" but not
>> including the credits.
>
> Fill in the NOTICE.
>
> Next round of the release, perhaps choose a different code base that
> doesn't
> offend the community.
I already dealt with the NOTICE in trunk.
But the release already have 4 binding +1 (I did not vote, but our PMC
gone ahead with approving the release even with this open issue).
That's why I was trying to understand what should I do next. If I am not
liable for this mistake then I don't care of doing anything else,
otherwise I want to know how to remove the release even if the remaining
members of the PMC voted to release it and ignored this issue.
I still have to understand what is the liability of each ASF contributor
wrt mistakes, that's why I'm a bit paranoid about this.
Stefano
---------------------------------------------------------------------
DISCLAIMER: Discussions on this list are informational and educational
only. Statements made on this list are not privileged, do not
constitute legal advice, and do not necessarily reflect the opinions
and policies of the ASF. See <http://www.apache.org/licenses/> for
official ASF policies and documents.
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org
Re: Reuse of ASF source code and NOTICE
Posted by "William A. Rowe, Jr." <wr...@rowe-clan.net>.
Stefano Bagnara wrote:
> Simon Kitching ha scritto:
>
>> Oracle wrote 100% of ADFFaces. It then went through the incubator
>> where significant changes were made, but mostly by Oracle employees.
>> It has then had some changes, but not significant ones, as part of the
>> MyFaces trinidad project. So it is *probably* true that Oracle funded
>> the development of the code you are reusing. It seems fair to credit
>> them in the NOTICE.
>
> I thought that ASF suggested to remove copyright notices few years ago,
> and I removed any reference to my name in the code I donated/contributed
> to the ASF, that's why I wondered if this Oracle statement was redundant
> once they contributed it as part of their CCLA and granted copyright
> license for it.
Here, there is a small distinction with a difference, and it would likely
apply to an ASF codebase that's taken lock, stock and barrel into a new
project. Since this is a fork, it does make sense that at the point that
the ASF acquired the code, we designate it as such.
The httpd project has similar NOTICE with respect to NCSA server.
> IIRC at that time there was also some mass-commit to remove the @author
> string from classes, without involving any of the @authors. So maybe
> this is was not appropriate, according to this Oracle issue.. or maybe
> this was ok because that @authors were not in the NOTICE file... ?!
An @author assertion isn't a ©copyright assertion. They may be the same,
but not necessarily.
> In this specific thread I was asking how to deal with this as a release
> has already been voted by my PMC including the "code" but not including
> the credits.
Fill in the NOTICE.
Next round of the release, perhaps choose a different code base that doesn't
offend the community. When confronted at the APR project with additional
NOTICE requirements of submitted components, authors have been asked to drop
the notice requirement or the patch won't be considered. Authors have
generally removed their attribution requirement :)
---------------------------------------------------------------------
DISCLAIMER: Discussions on this list are informational and educational
only. Statements made on this list are not privileged, do not
constitute legal advice, and do not necessarily reflect the opinions
and policies of the ASF. See <http://www.apache.org/licenses/> for
official ASF policies and documents.
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org
Re: Reuse of ASF source code and NOTICE
Posted by Stefano Bagnara <ap...@bago.org>.
Matthias Wessendorf ha scritto:
>> Yes! If you don't want to make the "credits" viral then you use the README.
>> If you want the Oracle credits to be virally present in any derivation of
>> that work then you leave it in the NOTICE.
>
> I am not 100% on Oracle's position about that ;-)
>
>> I don't have any request for you to move from NOTICE to README, I'm just
>> trying to understand what kind of mistake I did when I copied
>> Base64OutputStream from Trinidad and not added the Oracle credits to our
>> NOTICE. If Oracle is happy with the credits being not viral and moved from
>> NOTICE to README then this would probably backwardly fix my mistake, but
>> anyway I have already fixed any future release of our product (adding Oracle
>> credit to our NOTICE for now and proposing a different implementation of
>> Base64OutputStream that is also more efficient).
>
> Well, I am not an offical speaks man, but I bet there is nobody that
> has any problems.
>
> @Base64OutputStream: do you mind to "fix" ours as well ? :-)
Maybe we are OT now, but you can find it attached to MIME4J-71 for
review. https://issues.apache.org/jira/browse/MIME4J-71
Feel free to take it from there (the grant for inclusion has been
granted) or to wait for us to review and release the next mime4j if you
want "checked" code.
Stefano
---------------------------------------------------------------------
DISCLAIMER: Discussions on this list are informational and educational
only. Statements made on this list are not privileged, do not
constitute legal advice, and do not necessarily reflect the opinions
and policies of the ASF. See <http://www.apache.org/licenses/> for
official ASF policies and documents.
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org
Re: Reuse of ASF source code and NOTICE
Posted by Matthias Wessendorf <ma...@apache.org>.
> Yes! If you don't want to make the "credits" viral then you use the README.
> If you want the Oracle credits to be virally present in any derivation of
> that work then you leave it in the NOTICE.
I am not 100% on Oracle's position about that ;-)
>
> I don't have any request for you to move from NOTICE to README, I'm just
> trying to understand what kind of mistake I did when I copied
> Base64OutputStream from Trinidad and not added the Oracle credits to our
> NOTICE. If Oracle is happy with the credits being not viral and moved from
> NOTICE to README then this would probably backwardly fix my mistake, but
> anyway I have already fixed any future release of our product (adding Oracle
> credit to our NOTICE for now and proposing a different implementation of
> Base64OutputStream that is also more efficient).
Well, I am not an offical speaks man, but I bet there is nobody that
has any problems.
@Base64OutputStream: do you mind to "fix" ours as well ? :-)
-Matthias
>
> Thank you for your feedback,
> Stefano
>
> ---------------------------------------------------------------------
> DISCLAIMER: Discussions on this list are informational and educational
> only. Statements made on this list are not privileged, do not
> constitute legal advice, and do not necessarily reflect the opinions
> and policies of the ASF. See <http://www.apache.org/licenses/> for
> official ASF policies and documents.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
> For additional commands, e-mail: legal-discuss-help@apache.org
>
>
--
Matthias Wessendorf
Need JSF and Web 2.0?
http://code.google.com/p/facesgoodies
further stuff:
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
mail: matzew-at-apache-dot-org
---------------------------------------------------------------------
DISCLAIMER: Discussions on this list are informational and educational
only. Statements made on this list are not privileged, do not
constitute legal advice, and do not necessarily reflect the opinions
and policies of the ASF. See <http://www.apache.org/licenses/> for
official ASF policies and documents.
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org
Re: Reuse of ASF source code and NOTICE
Posted by Stefano Bagnara <ap...@bago.org>.
Matthias Wessendorf ha scritto:
> On Wed, Aug 20, 2008 at 3:10 PM, Stefano Bagnara <ap...@bago.org> wrote:
>> Matthias Wessendorf ha scritto:
>>> Hi,
>>>
>>> On Wed, Aug 20, 2008 at 2:19 PM, Matthias Wessendorf <ma...@apache.org>
>>> wrote:
>>>>> What is not clear here is whether Oracle specifically requested this.
>>>>> Based on what I have seen so far, I see no evidence that they have.
>>>> I think, it was just done for some incubator reasons. let me check
>>>> older archives
>>>> about that.
>>> I think I found the old thread:
>>> http://marc.info/?l=incubator-general&m=115757673411139&w=2
>>>
>>> b/c of this reply I started to look at other (donated) projects in the
>>> incubator.
>>> So I added the Oracle note. But generally, what's wrong in mention that at
>>> Oracle major parts of Trinidad have been developed?
>> Nothing wrong. But when you write this in NOTICE then it is a specific
>> request your make via Apache License v2 that anyone using that code or part
>> of that code will have to bring that NOTICE with him.
>
> ah, ok. So your suggestion is to have a README or so instead, isn't it ?
Yes! If you don't want to make the "credits" viral then you use the
README. If you want the Oracle credits to be virally present in any
derivation of that work then you leave it in the NOTICE.
I don't have any request for you to move from NOTICE to README, I'm just
trying to understand what kind of mistake I did when I copied
Base64OutputStream from Trinidad and not added the Oracle credits to our
NOTICE. If Oracle is happy with the credits being not viral and moved
from NOTICE to README then this would probably backwardly fix my
mistake, but anyway I have already fixed any future release of our
product (adding Oracle credit to our NOTICE for now and proposing a
different implementation of Base64OutputStream that is also more efficient).
Thank you for your feedback,
Stefano
---------------------------------------------------------------------
DISCLAIMER: Discussions on this list are informational and educational
only. Statements made on this list are not privileged, do not
constitute legal advice, and do not necessarily reflect the opinions
and policies of the ASF. See <http://www.apache.org/licenses/> for
official ASF policies and documents.
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org
Re: Reuse of ASF source code and NOTICE
Posted by Matthias Wessendorf <ma...@apache.org>.
On Wed, Aug 20, 2008 at 3:10 PM, Stefano Bagnara <ap...@bago.org> wrote:
> Matthias Wessendorf ha scritto:
>>
>> Hi,
>>
>> On Wed, Aug 20, 2008 at 2:19 PM, Matthias Wessendorf <ma...@apache.org>
>> wrote:
>>>>
>>>> What is not clear here is whether Oracle specifically requested this.
>>>> Based on what I have seen so far, I see no evidence that they have.
>>>
>>> I think, it was just done for some incubator reasons. let me check
>>> older archives
>>> about that.
>>
>> I think I found the old thread:
>> http://marc.info/?l=incubator-general&m=115757673411139&w=2
>>
>> b/c of this reply I started to look at other (donated) projects in the
>> incubator.
>> So I added the Oracle note. But generally, what's wrong in mention that at
>> Oracle major parts of Trinidad have been developed?
>
> Nothing wrong. But when you write this in NOTICE then it is a specific
> request your make via Apache License v2 that anyone using that code or part
> of that code will have to bring that NOTICE with him.
ah, ok. So your suggestion is to have a README or so instead, isn't it ?
-M
>
> In the mean time I wrote a new Base64OutputStream based on code from
> commons-codec that has no NOTICE requirement but ASF, so this issue is
> really low priority for me, but of course is interesting to understand this
> non-technical stuff better.
>
> My only remaining concern wrt this issue is that Apache JAMES mime4j 0.4 has
> been released and it includes Base64OutputStream from trinidad and it does
> not have any credit to Oracle for this. That's why I was asking if the
> release have to be removed from www.apache.org or if we can move on and
> simply fix this in mime4j 0.5
>
> Stefano
>
> ---------------------------------------------------------------------
> DISCLAIMER: Discussions on this list are informational and educational
> only. Statements made on this list are not privileged, do not
> constitute legal advice, and do not necessarily reflect the opinions
> and policies of the ASF. See <http://www.apache.org/licenses/> for
> official ASF policies and documents.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
> For additional commands, e-mail: legal-discuss-help@apache.org
>
>
--
Matthias Wessendorf
Need JSF and Web 2.0?
http://code.google.com/p/facesgoodies
further stuff:
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
mail: matzew-at-apache-dot-org
---------------------------------------------------------------------
DISCLAIMER: Discussions on this list are informational and educational
only. Statements made on this list are not privileged, do not
constitute legal advice, and do not necessarily reflect the opinions
and policies of the ASF. See <http://www.apache.org/licenses/> for
official ASF policies and documents.
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org
Re: Reuse of ASF source code and NOTICE
Posted by Stefano Bagnara <ap...@bago.org>.
Matthias Wessendorf ha scritto:
> Hi,
>
> On Wed, Aug 20, 2008 at 2:19 PM, Matthias Wessendorf <ma...@apache.org> wrote:
>>> What is not clear here is whether Oracle specifically requested this.
>>> Based on what I have seen so far, I see no evidence that they have.
>> I think, it was just done for some incubator reasons. let me check
>> older archives
>> about that.
>
> I think I found the old thread:
> http://marc.info/?l=incubator-general&m=115757673411139&w=2
>
> b/c of this reply I started to look at other (donated) projects in the
> incubator.
> So I added the Oracle note. But generally, what's wrong in mention that at
> Oracle major parts of Trinidad have been developed?
Nothing wrong. But when you write this in NOTICE then it is a specific
request your make via Apache License v2 that anyone using that code or
part of that code will have to bring that NOTICE with him.
In the mean time I wrote a new Base64OutputStream based on code from
commons-codec that has no NOTICE requirement but ASF, so this issue is
really low priority for me, but of course is interesting to understand
this non-technical stuff better.
My only remaining concern wrt this issue is that Apache JAMES mime4j 0.4
has been released and it includes Base64OutputStream from trinidad and
it does not have any credit to Oracle for this. That's why I was asking
if the release have to be removed from www.apache.org or if we can move
on and simply fix this in mime4j 0.5
Stefano
---------------------------------------------------------------------
DISCLAIMER: Discussions on this list are informational and educational
only. Statements made on this list are not privileged, do not
constitute legal advice, and do not necessarily reflect the opinions
and policies of the ASF. See <http://www.apache.org/licenses/> for
official ASF policies and documents.
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org
Re: Reuse of ASF source code and NOTICE
Posted by Matthias Wessendorf <ma...@apache.org>.
Hi,
On Wed, Aug 20, 2008 at 2:19 PM, Matthias Wessendorf <ma...@apache.org> wrote:
>> What is not clear here is whether Oracle specifically requested this.
>> Based on what I have seen so far, I see no evidence that they have.
>
> I think, it was just done for some incubator reasons. let me check
> older archives
> about that.
I think I found the old thread:
http://marc.info/?l=incubator-general&m=115757673411139&w=2
b/c of this reply I started to look at other (donated) projects in the
incubator.
So I added the Oracle note. But generally, what's wrong in mention that at
Oracle major parts of Trinidad have been developed?
-Matthias
>
> -Matthias
>
> --
> Matthias Wessendorf
>
> Need JSF and Web 2.0?
> http://code.google.com/p/facesgoodies
>
> further stuff:
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> mail: matzew-at-apache-dot-org
>
--
Matthias Wessendorf
Need JSF and Web 2.0?
http://code.google.com/p/facesgoodies
further stuff:
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
mail: matzew-at-apache-dot-org
---------------------------------------------------------------------
DISCLAIMER: Discussions on this list are informational and educational
only. Statements made on this list are not privileged, do not
constitute legal advice, and do not necessarily reflect the opinions
and policies of the ASF. See <http://www.apache.org/licenses/> for
official ASF policies and documents.
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org
Re: Reuse of ASF source code and NOTICE
Posted by Matthias Wessendorf <ma...@apache.org>.
> What is not clear here is whether Oracle specifically requested this.
> Based on what I have seen so far, I see no evidence that they have.
I think, it was just done for some incubator reasons. let me check
older archives
about that.
-Matthias
--
Matthias Wessendorf
Need JSF and Web 2.0?
http://code.google.com/p/facesgoodies
further stuff:
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
mail: matzew-at-apache-dot-org
---------------------------------------------------------------------
DISCLAIMER: Discussions on this list are informational and educational
only. Statements made on this list are not privileged, do not
constitute legal advice, and do not necessarily reflect the opinions
and policies of the ASF. See <http://www.apache.org/licenses/> for
official ASF policies and documents.
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org
Re: Reuse of ASF source code and NOTICE
Posted by Sam Ruby <ru...@intertwingly.net>.
On Tue, Aug 19, 2008 at 8:28 AM, Stefano Bagnara <ap...@bago.org> wrote:
> Simon Kitching ha scritto:
>>
>> Stefano Bagnara schrieb:
>>>
>>> Emmanuel Bourg ha scritto:
>>>>
>>>> There is an alternative that may simplify this issue. Commons Codec has
>>>> a Base64Input/OuputStream already, it will be part of the upcoming 1.4
>>>> release. You may simply add a dependency instead of copying the code from
>>>> MyFaces. That's a relatively small jar (50k).
>>>>
>>>> Emmanuel Bourg
>>>
>>> Thank you for the pointer.
>>>
>>> I checked commons-codec but only for released code and it was not there.
>>> We won't probably add a dependency for this (our product is a basic library
>>> and have no dependencies so far), but we can copy that code from
>>> commons-codec without the need to credit Oracle, so it may worth the change
>>> (or we could use maven-shade-plugin to better deal with this "minor"
>>> dependency).
>>>
>>> But first I have to deal with our release in progress issue :-( ,
>>
>> Then why not just add the notice? It seems quite reasonable to me to do
>> so.
>
> That's what I already done for trunk, after I received this answers.
> http://svn.apache.org/viewvc?view=rev&revision=687018
> https://issues.apache.org/jira/browse/MIME4J-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
>
>> Oracle wrote 100% of ADFFaces. It then went through the incubator where
>> significant changes were made, but mostly by Oracle employees. It has then
>> had some changes, but not significant ones, as part of the MyFaces trinidad
>> project. So it is *probably* true that Oracle funded the development of the
>> code you are reusing. It seems fair to credit them in the NOTICE.
>
> I don't care HERE of what is fair or not. HERE I want to understand what is
> required by the law and what is the policy by the ASF. ;-)
NOTICE is only for notices that we are required to provide -- such as
the notices that previous versions of the Apache License required.
These should be trimmed to a minimum; the working assumption being
that this is text that would tend to appear in places such as an
"about" menu option on a GUI, or on a flash screen on application
startup.
What is not clear here is whether Oracle specifically requested this.
Based on what I have seen so far, I see no evidence that they have.
The LICENSE file should describe the licenses under which this
software is made available, and in this case there is a software
grant, so no additional mention is required.
> I wrote plenty of code for the ASF and I never asked anyone to credit me,
> like most of other ASF committers do.
>
> I thought that ASF suggested to remove copyright notices few years ago, and
> I removed any reference to my name in the code I donated/contributed to the
> ASF, that's why I wondered if this Oracle statement was redundant once they
> contributed it as part of their CCLA and granted copyright license for it.
>
> IIRC at that time there was also some mass-commit to remove the @author
> string from classes, without involving any of the @authors. So maybe this is
> was not appropriate, according to this Oracle issue.. or maybe this was ok
> because that @authors were not in the NOTICE file... ?!
>
> That's something I didn't know, and it is good to increase the knowledge
> with this cases. Maybe in future for some contributions I'll prefer to be
> credited in the NOTICE so anyone reusing my code will not only have to
> credit ASF but also me.
>
>> Agreed we don't want to have a NOTICE entry for every small bit of code
>> reuse, eg one or two classes. But for larger chunks it does seem fair. In
>> this case it certainly seems easiest to just add the notice now and then
>> have this debate at leisure rather than holding up your release. I thought
>> your proposed wording on an earlier email was fine.
>
> Taking care of NOTICE in every generated artifact is a cost, so if I will
> find a different implementation that won't require to have a NOTICE
> statement I'll take it. I don't have issues with Oracle at all, and I like
> to credit where credit is due. If you read this full thread you will see
> that I introduced it as a MISTAKE (i didn't see the NOTICE content at
> first).
>
> In this specific thread I was asking how to deal with this as a release has
> already been voted by my PMC including the "code" but not including the
> credits.
>
> Stefano
>
> ---------------------------------------------------------------------
> DISCLAIMER: Discussions on this list are informational and educational
> only. Statements made on this list are not privileged, do not
> constitute legal advice, and do not necessarily reflect the opinions
> and policies of the ASF. See <http://www.apache.org/licenses/> for
> official ASF policies and documents.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
> For additional commands, e-mail: legal-discuss-help@apache.org
>
>
---------------------------------------------------------------------
DISCLAIMER: Discussions on this list are informational and educational
only. Statements made on this list are not privileged, do not
constitute legal advice, and do not necessarily reflect the opinions
and policies of the ASF. See <http://www.apache.org/licenses/> for
official ASF policies and documents.
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org
Re: Reuse of ASF source code and NOTICE
Posted by Stefano Bagnara <ap...@bago.org>.
Simon Kitching ha scritto:
> Stefano Bagnara schrieb:
>> Emmanuel Bourg ha scritto:
>>> There is an alternative that may simplify this issue. Commons Codec
>>> has a Base64Input/OuputStream already, it will be part of the
>>> upcoming 1.4 release. You may simply add a dependency instead of
>>> copying the code from MyFaces. That's a relatively small jar (50k).
>>>
>>> Emmanuel Bourg
>>
>> Thank you for the pointer.
>>
>> I checked commons-codec but only for released code and it was not
>> there. We won't probably add a dependency for this (our product is a
>> basic library and have no dependencies so far), but we can copy that
>> code from commons-codec without the need to credit Oracle, so it may
>> worth the change (or we could use maven-shade-plugin to better deal
>> with this "minor" dependency).
>>
>> But first I have to deal with our release in progress issue :-( ,
>
> Then why not just add the notice? It seems quite reasonable to me to do so.
That's what I already done for trunk, after I received this answers.
http://svn.apache.org/viewvc?view=rev&revision=687018
https://issues.apache.org/jira/browse/MIME4J-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
> Oracle wrote 100% of ADFFaces. It then went through the incubator where
> significant changes were made, but mostly by Oracle employees. It has
> then had some changes, but not significant ones, as part of the MyFaces
> trinidad project. So it is *probably* true that Oracle funded the
> development of the code you are reusing. It seems fair to credit them in
> the NOTICE.
I don't care HERE of what is fair or not. HERE I want to understand what
is required by the law and what is the policy by the ASF. ;-)
I wrote plenty of code for the ASF and I never asked anyone to credit
me, like most of other ASF committers do.
I thought that ASF suggested to remove copyright notices few years ago,
and I removed any reference to my name in the code I donated/contributed
to the ASF, that's why I wondered if this Oracle statement was redundant
once they contributed it as part of their CCLA and granted copyright
license for it.
IIRC at that time there was also some mass-commit to remove the @author
string from classes, without involving any of the @authors. So maybe
this is was not appropriate, according to this Oracle issue.. or maybe
this was ok because that @authors were not in the NOTICE file... ?!
That's something I didn't know, and it is good to increase the knowledge
with this cases. Maybe in future for some contributions I'll prefer to
be credited in the NOTICE so anyone reusing my code will not only have
to credit ASF but also me.
> Agreed we don't want to have a NOTICE entry for every small bit of code
> reuse, eg one or two classes. But for larger chunks it does seem fair.
> In this case it certainly seems easiest to just add the notice now and
> then have this debate at leisure rather than holding up your release. I
> thought your proposed wording on an earlier email was fine.
Taking care of NOTICE in every generated artifact is a cost, so if I
will find a different implementation that won't require to have a NOTICE
statement I'll take it. I don't have issues with Oracle at all, and I
like to credit where credit is due. If you read this full thread you
will see that I introduced it as a MISTAKE (i didn't see the NOTICE
content at first).
In this specific thread I was asking how to deal with this as a release
has already been voted by my PMC including the "code" but not including
the credits.
Stefano
---------------------------------------------------------------------
DISCLAIMER: Discussions on this list are informational and educational
only. Statements made on this list are not privileged, do not
constitute legal advice, and do not necessarily reflect the opinions
and policies of the ASF. See <http://www.apache.org/licenses/> for
official ASF policies and documents.
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org
Re: Reuse of ASF source code and NOTICE
Posted by Emmanuel Bourg <eb...@apache.org>.
Simon Kitching a écrit :
> Then why not just add the notice? It seems quite reasonable to me to do so.
It seems more reasonable to have a unique implementation of a utility
class across several projects instead of 2 implementations. They can
copy the class from Commons Codec for this release, and later replace it
with a dependency when Commons Codec 1.4 is released.
Emmanuel Bourg
---------------------------------------------------------------------
DISCLAIMER: Discussions on this list are informational and educational
only. Statements made on this list are not privileged, do not
constitute legal advice, and do not necessarily reflect the opinions
and policies of the ASF. See <http://www.apache.org/licenses/> for
official ASF policies and documents.
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org
Re: Reuse of ASF source code and NOTICE
Posted by Simon Kitching <sk...@apache.org>.
Stefano Bagnara schrieb:
> Emmanuel Bourg ha scritto:
>> There is an alternative that may simplify this issue. Commons Codec
>> has a Base64Input/OuputStream already, it will be part of the
>> upcoming 1.4 release. You may simply add a dependency instead of
>> copying the code from MyFaces. That's a relatively small jar (50k).
>>
>> Emmanuel Bourg
>
> Thank you for the pointer.
>
> I checked commons-codec but only for released code and it was not
> there. We won't probably add a dependency for this (our product is a
> basic library and have no dependencies so far), but we can copy that
> code from commons-codec without the need to credit Oracle, so it may
> worth the change (or we could use maven-shade-plugin to better deal
> with this "minor" dependency).
>
> But first I have to deal with our release in progress issue :-( ,
Then why not just add the notice? It seems quite reasonable to me to do so.
Oracle wrote 100% of ADFFaces. It then went through the incubator where
significant changes were made, but mostly by Oracle employees. It has
then had some changes, but not significant ones, as part of the MyFaces
trinidad project. So it is *probably* true that Oracle funded the
development of the code you are reusing. It seems fair to credit them in
the NOTICE.
Agreed we don't want to have a NOTICE entry for every small bit of code
reuse, eg one or two classes. But for larger chunks it does seem fair.
In this case it certainly seems easiest to just add the notice now and
then have this debate at leisure rather than holding up your release. I
thought your proposed wording on an earlier email was fine.
Regards, Simon
---------------------------------------------------------------------
DISCLAIMER: Discussions on this list are informational and educational
only. Statements made on this list are not privileged, do not
constitute legal advice, and do not necessarily reflect the opinions
and policies of the ASF. See <http://www.apache.org/licenses/> for
official ASF policies and documents.
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org
Re: Reuse of ASF source code and NOTICE
Posted by Stefano Bagnara <ap...@bago.org>.
Emmanuel Bourg ha scritto:
> There is an alternative that may simplify this issue. Commons Codec has
> a Base64Input/OuputStream already, it will be part of the upcoming 1.4
> release. You may simply add a dependency instead of copying the code
> from MyFaces. That's a relatively small jar (50k).
>
> Emmanuel Bourg
Thank you for the pointer.
I checked commons-codec but only for released code and it was not there.
We won't probably add a dependency for this (our product is a basic
library and have no dependencies so far), but we can copy that code from
commons-codec without the need to credit Oracle, so it may worth the
change (or we could use maven-shade-plugin to better deal with this
"minor" dependency).
But first I have to deal with our release in progress issue :-( ,
Stefano
---------------------------------------------------------------------
DISCLAIMER: Discussions on this list are informational and educational
only. Statements made on this list are not privileged, do not
constitute legal advice, and do not necessarily reflect the opinions
and policies of the ASF. See <http://www.apache.org/licenses/> for
official ASF policies and documents.
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org
Re: Reuse of ASF source code and NOTICE
Posted by Emmanuel Bourg <eb...@apache.org>.
There is an alternative that may simplify this issue. Commons Codec has
a Base64Input/OuputStream already, it will be part of the upcoming 1.4
release. You may simply add a dependency instead of copying the code
from MyFaces. That's a relatively small jar (50k).
Emmanuel Bourg
---------------------------------------------------------------------
DISCLAIMER: Discussions on this list are informational and educational
only. Statements made on this list are not privileged, do not
constitute legal advice, and do not necessarily reflect the opinions
and policies of the ASF. See <http://www.apache.org/licenses/> for
official ASF policies and documents.
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org