Put github and slack into separate schemas for #27

[dherbst]

For #27 puts tap_github into views_github and tap-slack into views_slack

For example:

datawarehouse=# \dt views_github.*
                 List of relations
    Schema    |       Name       | Type  |  Owner   
--------------+------------------+-------+----------
 views_github | assignees        | table | postgres
 views_github | collaborators    | table | postgres
 views_github | contributors     | table | postgres
 views_github | issue_labels     | table | postgres
 views_github | languages        | table | postgres
 views_github | repository       | table | postgres
 views_github | stargazers       | table | postgres
 views_github | team_members     | table | postgres
 views_github | team_memberships | table | postgres
 views_github | teams            | table | postgres
(10 rows)

[chriscardillo]

Implementation looks good, though #28 suggests that the work of creating schemas should be moved to its own DAG.

If #20 is merged in, it should be as easy as moving datawarehouse_setup.py into its own DAG folder.

[dherbst]

Sounds good.

[dherbst]

Here are the schemas the data will go into:

datawarehouse=# \dn
    List of schemas
    Name    |  Owner   
------------+----------
 public     | postgres
 tap_github | postgres
 tap_slack  | postgres
 views      | postgres
(4 rows)