Add details for using GitHub

[plzmsu]

we should fill out the GitHub section more, probably to include the general stuff (not repository list) from following: https://docs.google.com/document/d/1Hf6whmT48RBGdYTarVF7IGTwyGrPf840NEys5qS6mIk/edit#

In particular, we need to include mention of how one interfaces with existing project-wide repositories. I think we want people to work on the organization GitHub rather than their own GitHub. This should be written as a guide for 1) how you start using GitHub (see link above), 2) how you work in a GitHub organization like NEON-biodiversity, etc.

[billspat]

I agree! Should we also suggested standard workflow (as we dicussed over email)? Finally, should writing about using Git (or any other 'non-R' tech) go into our R-guide because it's closely related, or into a policy/worflow document we started for NEON-biodiv? Somehow I was thinking the R guide should focus on R, and the coding policy is for everything else. OR should we really just have one document that covers R, Git, data organization, EDI, etc? The "policy" doc for NEON-biodiv would be things very specific to NEON and also mostly "see our R guide for how to use git" I'm ok with any of those, just want to avoid redundancy and encourage as many collaborators as possible.