Merge this repo and the dashboard repo

[tanius]

Graphryder consists of a JavaScript application running in the browser (graphryder-dashboard) that talks to a server-side component (graphryder-api – this repository).

Currently, both components reside in one Git repository each, but that makes no sense:

• They can only be used together, so they form one software together.
• None of the two is so generic that we would expect it to be used as a dependency in other software projects.
• And neither do we expect any of the two to be supplied in multiple alternative implementations ("same interface, different behavior") in the future. If we'd want to add importing from a different forum software, we'd add another importer to graphryder-api instead of forking and adapting it for that purpose.

So: one software, one repository. Both components should be merged into one repository named graphryder. To give a prominent example, it's done the same way in Discourse.

There's one side benefit: by starting that repository graphryder as a fresh repository on Github, it will not show up as "forked from …". This would properly communicate that this software is now maintained by Discourse.

[tanius]

Actually, maybe better don't merge the repositories. It might be that the better approach is indeed to keep Graphryder Dashboard as an independent repo that can talk to one of several implementations of the API. In our case, we would create one as a Discourse plugin (see #13) and would then no longer require Graphryder API.