On 3/1/16, 5:22 PM, "Todd Lipcon" <t...@cloudera.com> wrote:
>On Tue, Mar 1, 2016 at 4:05 PM, Justin Mclean <justinmcl...@me.com> wrote:
>
>> Hi,
>>
>> > I seem to recall reading some place or another that pointers
>> > to licenses in the forms of URLs or textual references are frowned
>>upon,
>> > because licenses may change over time, or the links may break
>>
>> Correct. Also most licenses say you much include the full text of the
>> license in your distribution.
>>
>>
>OK. In the case that we've incorporated code, we could switch to doing:
>
>"""
>src/kudu/gutil/valgrind.h: Hybrid BSD (half BSD, half zlib)
>src/kudu/util (some portions): 3-clause BSD license
>src/kudu/util (HdrHistogram-related classes): public domain
>src/kudu/util/{random-util.cc},{random.h}: some portions adapted from
>WebRTC project (modules/video_coding/main/test/test_util.cc) under a
>3-clause BSD license.
>
> For full license text of the above licenses, please refer to the license
>headers at the top of the respective files.
>"""
>
>...and then make sure that those files contain the full text of the
>license, instead of copy-pasting the text into LICENSE.txt. Does that
>sound
>like the best path forward?
I haven't been following carefully, but isn't there a BSD header in these
files? If so, couldn't your LICENSE refer people to the headers in those
files?
-Alex
