GitHub issue widget about deepreader

[jtauber]

I then added:

Actually now that I think more about it, you could use GitHub integration not just for tasks that are orthogonal to the text (like your example of widget development plans) but actually for some crowdsourcing projects (although perhaps not student assessment). For example, imagine you had a repository where issues were labeled with CTS URNs or OSIS IDs. The GitHub widget could retrieve the relevant issue(s) for the passage being interacted with and let the reader view those issues and comment on them right from within the widget.

[jtauber]

So I think the starting point here is a widget that is hard-coded to a particular repo and lists the open issues in that repo.

Second step would be to allow some sort of interaction (which would require authentication)

Third step would be to (optionally) support scoping of issues to the text being viewed via CTS URN or OSIS ID label on the GitHub issue.

[balain]

I'd like to tackle this (at least steps 1 & 2) as a learning exercise, if it isn't urgent. It might take me several weeks...

[jtauber]

@balain things not marked Milestone 2 or 3 are definitely not urgent.

Would be excellent if you tackled this. It would be especially interesting if you used GitHub's GraphQL API because I think GraphQL could prove very interesting for a lot of DeepReader use cases and so working out how to support GraphQL queries from DeepReader would help us with a whole range of things.

[balain]

I submitted a pull request with a new GitHub component, but almost immediately (coincidentally?), my GitHub account was locked. I've asked to have it reinstated, but until then, I'm guessing my pull request won't be visible to you... GitHub issue resolved; pull request renamed -- WIP...