issue_comments

Table actions

1 row where issue = 206137485 and user = 10050469 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date), updated_at (date)

user 1

  • fmaussion · 1 ✖

issue 1

  • Provide more detailed copyright information · 1 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
278694881 https://github.com/pydata/xarray/issues/1254#issuecomment-278694881 https://api.github.com/repos/pydata/xarray/issues/1254 MDEyOklzc3VlQ29tbWVudDI3ODY5NDg4MQ== fmaussion 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
}
   Provide more detailed copyright information 206137485

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

CREATE TABLE [issue_comments] (
   [html_url] TEXT,
   [issue_url] TEXT,
   [id] INTEGER PRIMARY KEY,
   [node_id] TEXT,
   [user] INTEGER REFERENCES [users]([id]),
   [created_at] TEXT,
   [updated_at] TEXT,
   [author_association] TEXT,
   [body] TEXT,
   [reactions] TEXT,
   [performed_via_github_app] TEXT,
   [issue] INTEGER REFERENCES [issues]([id])
);
CREATE INDEX [idx_issue_comments_issue]
    ON [issue_comments] ([issue]);
CREATE INDEX [idx_issue_comments_user]
    ON [issue_comments] ([user]);