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-282557948,https://api.github.com/repos/pydata/xarray/issues/1254,282557948,MDEyOklzc3VlQ29tbWVudDI4MjU1Nzk0OA==,1964655,2017-02-26T14:02:48Z,2017-02-26T14:02:48Z,CONTRIBUTOR,"FYI, `xarray` is now available in [Debian](https://packages.debian.org/source/sid/python-xarray).","{""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-278698787,https://api.github.com/repos/pydata/xarray/issues/1254,278698787,MDEyOklzc3VlQ29tbWVudDI3ODY5ODc4Nw==,1964655,2017-02-09T16:43:22Z,2017-02-09T16:43:22Z,CONTRIBUTOR,"The complex bit of code embedding is that both MIT and BSD have a clause saying that redistribution from source (even partially) should keep the original copyright notice (which includes authors, dates and license summary). It is straightforward to do when the original file is untouched, however things get a bit more difficult when portions of code gets included in larger modules, or so-called ""compatibility"" modules, where there is an aggregate of code with **mixed** copyright.

That's why the `NOTICE` file is useful. You just have to aggregate all copyright information in this one file and you are guaranteed to comply. Besides, commercial entities or packagers like myself, who need to survey the compliance of each software, have an easier time doing their work.

Did my explanation make sense?","{""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-278693067,https://api.github.com/repos/pydata/xarray/issues/1254,278693067,MDEyOklzc3VlQ29tbWVudDI3ODY5MzA2Nw==,1964655,2017-02-09T16:25:24Z,2017-02-09T16:25:24Z,CONTRIBUTOR,"*Most* Apache-licensed software follow these guidelines, nonetheless. And for the case of `xarray`, where there are instances of embedded code from other copyrighted projects, I believe it should be beneficial to follow these conventions too. The final decision is yours at the end.

Regardless of your decision, I need a comprehensive list of all embedded code which falls under a different copyright than `xarray`.

Thanks,","{""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-278590912,https://api.github.com/repos/pydata/xarray/issues/1254,278590912,MDEyOklzc3VlQ29tbWVudDI3ODU5MDkxMg==,1964655,2017-02-09T09:32:36Z,2017-02-09T09:32:36Z,CONTRIBUTOR,"> 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.

That is indeed the purpose of the NOTICE file. Since the Apache license state that all source code should start with the Apache copyright header, then individual copyrights from embedded portions of code should be listed in an additional `NOTICE` file to comply with their respective redistribution clauses.

> I'm not opposed to adding a NOTICE file

You do know you are supposed to provide one as per the [Apache Software Policy](http://apache.org/dev/apply-license.html), right? Details about its content and formatting are provided [here](http://www.apache.org/legal/src-headers.html#notice).

I am also providing an example from the [ITK project](https://github.com/Kitware/ITK/blob/master/NOTICE), since you seem to be having doubts about my statement. I can give you many more if your are still not convinced.

>  but I haven't seen it in other projects in the scientific Python space

Because most projects from the scientific Python stack (including [Numpy](https://github.com/numpy/numpy/blob/master/LICENSE.txt) and [Pandas](https://github.com/pandas-dev/pandas/blob/master/LICENSE) that you mentioned) use the simpler [BSD-3-Clause](https://opensource.org/licenses/BSD-3-Clause).

> Maybe we're all just being careless, though :)

Nope, just yourself in this case.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,206137485