Migrate knowledge base to github

[capsulecorplab]

This is a high-level task for outlining and discussing strategies for migrating Coral's knowledge-base from Google Drive to GitHub. This migration is intended to better facilitate contributor workflow, as the project begins to grow in complex and team size, as well as for establishing (and beta testing) a more formalized process for sanctioning "official" contributions into the Space Decentral knowledge-base.

Completion of this task will entail:

• Complete profile of documentation templates, and associated style guides (see Create documentation templates #97)
• .travis.yml file for enabling continuous integration (CI) for enforcing style guide conformance for documents submitted to the research/ folder via pull requests (PR) (see Setup travis-ci to enforce style guide conformance #98).
• CONTRIBUTING.md doc, detailing best-practices for contributor workflow (see Create Contributing.md #52).
• GPL-3 Contributor License Agreement (CLA) plugin, using cla-assistant, enabled for contributions to the Coral repository via pull requests (PR).
• Update Code of Conduct - details TBD.

Please feel free to comment if anything seems unclear or missing from the above.

[capsulecorplab]

@cagonzalez8, this may be a bit of a monster of a task, but would this be something of interest to you?

I'm labeling this as an icebox item for now, but the sooner we adopt such a solution, the less work I suspect it'll be having to migrate any existing work into the "Github time-capsule". @founder-outbound @Suzibianco @Engineer1119 your feedback is welcome as always.

[Suzibianco]

Seems good to me, I am beginning to understand the urgency 😅 Our current system is generating a lot of ad-hoc documents and no traceability at all.