html_url,issue_url,id,node_id,user,created_at,updated_at,author_association,body,reactions,performed_via_github_app,issue
https://github.com/pydata/xarray/issues/1254#issuecomment-278703545,https://api.github.com/repos/pydata/xarray/issues/1254,278703545,MDEyOklzc3VlQ29tbWVudDI3ODcwMzU0NQ==,1217238,2017-02-09T16:58:40Z,2017-02-09T16:58:40Z,MEMBER,"> Did my explanation make sense?

Yes, I agree and appreciate your feedback 👍.

I'll see what I can put together here to make things easier for downstream distributors. Since we do have a few files with mixed copyright, a NOTICE file could be appropriate.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,206137485
https://github.com/pydata/xarray/issues/1254#issuecomment-278694881,https://api.github.com/repos/pydata/xarray/issues/1254,278694881,MDEyOklzc3VlQ29tbWVudDI3ODY5NDg4MQ==,10050469,2017-02-09T16:30:58Z,2017-02-09T16:30:58Z,MEMBER,"> I need a comprehensive list of all embedded code which falls under a different copyright than xarray

yes this makes sense. But just for my understanding. You said:

> most projects from the scientific Python stack (including Numpy and Pandas that you mentioned) use the simpler BSD-3-Clause.

What we want to achieve here is properly acknowledge which part of the code is not from xarray, and therefore acknowledge libraries which are under the ""simpler"" BSD license. So I thought that the rules that should apply here are not Apache's ones but the BSD ones, right? 


","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,206137485
https://github.com/pydata/xarray/issues/1254#issuecomment-278686390,https://api.github.com/repos/pydata/xarray/issues/1254,278686390,MDEyOklzc3VlQ29tbWVudDI3ODY4NjM5MA==,1217238,2017-02-09T16:03:50Z,2017-02-09T16:03:50Z,MEMBER,"From the page you link:
""This document is a ""how to"" guide aimed at Apache Committers assembling LICENSE and NOTICE files for an Apache product.""

Xarray is not an Apache product, so strictly speaking these guidelines do not apply.

""It does not apply to developers outside the ASF who are applying the Apache License to their work.""
https://www.apache.org/legal/src-headers.html","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,206137485
https://github.com/pydata/xarray/issues/1254#issuecomment-278532896,https://api.github.com/repos/pydata/xarray/issues/1254,278532896,MDEyOklzc3VlQ29tbWVudDI3ODUzMjg5Ng==,1217238,2017-02-09T02:57:40Z,2017-02-09T02:57:40Z,MEMBER,"@ghisvail Thanks for your interest here and your help distributing xarray.

Currently, adapted/copied work is only called out in the code base itself (e.g., [1](https://github.com/pydata/xarray/blob/master/xarray/core/pycompat.py), [2](https://github.com/pydata/xarray/blob/master/xarray/core/npcompat.py), [3](https://github.com/pydata/xarray/blob/d49014d0357d08289cf99aeb54bcefe48ed6e7a0/xarray/core/indexing.py#L129)). But this certainly could be done less haphazardly. Probably we should include text of each license at the appropriate locations, or at least a direct reference to the fact hat it has a different license.

I'm not opposed to adding a NOTICE file, but I haven't seen it in other projects in the scientific Python space that I emulated in xarray (e.g., pandas or NumPy).  NumPy doesn't call out all the licenses included it in at all (and there are quite a few), except where the source code itself appears. Maybe we're all just being careless, though :).

As for the Apache license, I see terms like `If the Work includes a ""NOTICE"" text file...` but I don't actually see where it requires writing such a file.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,206137485