figure out policy on contributions / dataset branches

[noahfl]

We need a clear-cut policy/implementation on the kind of access people will have to our repository. For those who want to save their branches remotely, forking may be better over cloning.

Potential options (add as we think of more):

1. Leave the installation process as-is and provide instructions for changing the remote repo to a fork (reference here: https://admcpr.com/what-the-fork/). This would allow people to push their own commits and also make pull requests for when non-Rotman users want to contribute to the repository

Now that I think about it this might be the best option. This will be easy for people who just wanna use the stock pipeline and don't care about saving their changes remotely, but would require others to learn how to work with forks (we can link them to some existing documentation on that).

[noahfl]

Here's some GitHub official documentation on forks people can check out: https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/working-with-forks