issue_comments: 152308371

This data as json

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/pull/636#issuecomment-152308371 https://api.github.com/repos/pydata/xarray/issues/636 152308371 MDEyOklzc3VlQ29tbWVudDE1MjMwODM3MQ== 2020717 2015-10-29T20:26:14Z 2015-10-29T20:26:14Z NONE

I was just informed that "our lawyers looked it over and said we're OSI compliant."

Specifically "He compared the wording of both ours and the BSD one that you referenced, and said they are about 98% similar. The other 2%, which is something that's in the BSD that's not in ours, doesn't cause our license to be non-compliant."

Do you think this works? I do think we should fix the bad link to GRIBEX and point to the current ECMWF license. -dave

On Thu, Oct 29, 2015 at 2:16 PM, David Brown dbrown@ucar.edu wrote:

We are looking into our options on this. I know there were NCAR legal people involved in producing the current license. Hopefully given the current environment we will be to put it into a standard form that clearly meets the OSI requirement.

On Thu, Oct 29, 2015 at 11:14 AM, Filipe notifications@github.com wrote:

but it would be nice to be able to say that you use a standard license

[image: :+1:]

— Reply to this email directly or view it on GitHub https://github.com/xray/xray/pull/636#issuecomment-152253168.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   112677315