Needs proof reading

[maxcampb]

Proofreading to check that it all makes sense :)

• [x] Chris @cbrown5
• [x] Mischa @mpturschwell
• [x] Christina @cabuelow
• [ ] Briana @bholg
• [ ] Olivia

[maxcampb]

This is really great! Couple of thoughts @maxcampb @cbrown5 :

• [x] suggest add in file naming protocol - jenny bryan's 'naming things' is awesome: http://www2.stat.duke.edu/~rcs46/lectures_2015/01-markdown-git/slides/naming-slides/naming-slides.pdf
• [x] provide protocol/tips for dealing with existing projects not developed under this framework
• [x] On almost a daily basis, I switch between my work laptop (windows) and personal laptop (mac). Any foreseeable issues with this?
• [x] could change ‘Figures’ to ‘outputs’ folder - e.g. sometimes you want to save a .csv output for a table etc..., so I tend to have a single ‘outputs’ folder with sub folders for figures, etc.
• [x] could we just ask the eResearch center to set up seascapes lab research drive instead of using google drive? I think this is my preferred option because research drives can be mounted on the remote server (and we're getting another one for students to use so they have more computing power). So I keep all my data and R projects on the research drive (even if they’re not big spatial data) and do all of my analyses on the remote server or the HPC. But maybe there is some advantage to google drive over research drive?
• [x] another potential limitation not listed in the readme is limited interactivity with HPC?

[maxcampb]

@cabuelow thanks for the very thoughtful comments. Here are my responses:

I have added file naming protocol, and conversion of existing projects as issues which I will resolve.

I highly doubt there will be any issues with swapping operating systems (you might have to be a little clever with your profile to ensure that your directories are always working - can show you some tricks if needed)

Agreed. Have changed "Figures" to "Outputs". Not sure if you all prefer starting with lower case @cabuelow @cbrown5 ? I like upper case for the first letter mostly just because I think it looks better.

Using the eResearch drive, sounds like a great idea to me. I'll open an issue for this to discuss too.

I doubt there will be any problems interacting with the HPC if you have no issues when using the research drive?

[cabuelow]

Another idea, we could have bimonthly or monthly code review sessions - a nice way to learn and also make sure we stay up-to-date with best coding/data management practices

[maxcampb]

I think this is a wonderful idea I will add it as an idea in discussions.