incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alan Cabrera <l...@toolazydogs.com>
Subject Re: svn commit: r1488735 - in /incubator/public/trunk/tools: NOTICE.txt requirements.txt setup.py src/asf/utils/ src/asf/utils/__init__.py src/asf/utils/config.py src/asf/utils/file.py tests/test_config.py
Date Tue, 04 Jun 2013 13:46:21 GMT

On Jun 4, 2013, at 5:58 AM, Kevan Miller <kevan.miller@gmail.com> wrote:

> 
> On Jun 4, 2013, at 8:46 AM, Greg Stein <gstein@gmail.com> wrote:
> 
>> On Jun 4, 2013 4:22 AM, "ant elder" <ant.elder@gmail.com> wrote:
>>> 
>>> This "when in doubt leave it out" approach has gone a long way at
>>> smoothing podling release reviews compared to the olden days.
>> 
>> Seriously? The inserted code uses our own license! Go look at 4(d) and tell
>> me we should not insert a notice. It is both Right, and what is demanded by
>> our own license.
> 
> I haven't seen a description of where this code is coming from. Is it a contribution
from LinkedIn? Is it some open source code from LinkedIn that we are copying into our svn
from some other project?
> 
> If it's the former and LinkedIn has requested attribution for their contribution, then
let's observe their request and add attribution to the NOTICE.
> 
> If it's the latter *and* the subject code has a NOTICE file, then we absolutely must
include the relevant portions of their NOTICE in our NOTICE. Otherwise, 4 (d) doesn't require
us to do anything. Agreed?


The code is internal LinkedIn code that I copied with the appropriate permissions.  Attribution
was requested.


Regards,
Alan




---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Mime
View raw message