RUBRIC:
An OSF account and project; ✅
A Zotero account;✅
Zotero library linked to OSF;✅
A *.bib file;✅
A GitHub account;✅
A welcome page Wiki on your OSF project;✅
Another wiki page that describes your bare-bones plans (serving as a mini example pre-registration);✅
Been added to the LDP Organization on GitHub;✅
A GitHub repository inside the LDP organization;✅
Finished creating necessary folders (code, data, outputs, etc) and associated _README files within your RStudio project directory;✅
Committed and pushed these changes to GitHub;✅
Connected your GitHub repo to OSF;✅
A .csl file; (find a csl file here (Links to an external site.)) and instructions on how to access and use a CSL file in your markdown document✅
An initial script (.R file) which downloads your data and uses groundhog to manage packages;✅ (optional, however)
A *.RProj file;✅
A preregistration file on OSF;✅
Created a view-only link for your OSF project and send it to your peer;✅
An *.Rmd file that will become your manuscript.✅
A .gitgnore file✅
The complete folder structure and respective files in each folder (data - raw and clean -, code, manuscript, outputs, etc. + README and LICENSE - at least)✅
Your remote repository should have branches that reflect different aspects of the development of your project (e.g., one for analysis, one for figures, one for writing…)✅
An open pull request (PR) from a development branch to your main branch, requesting a review from one of your colleagues.✅
Final Grade: 20/20
Hi Emma, great job and love the improvements from last time! I have a few nit-picky suggestions that aren't crucial, but they might be somewhat helpful. The first thing is maybe instead of the folder "manuscripts" in your github repo, you could title it something a little more descriptive since you also have your pregreg in there? Perhaps "written-outputs" or "prereg-and-manuscript"? Another thing I noticed is that there are some readme files in different formats - "_README.md" and "README". By the looks of it though, the "README" format github is able to recognize as a readme file and puts it in the description section at the bottom of each folder but I think in class we were told "_README"? So I might've missed something because I'm not sure which type to use. Maybe we can figure that out together? Another tip would be to maybe put a pdf of your pregreg actually in your OSF project files so it is easily accessible and easy to read. Otherwise looking good!! :)
RUBRIC:
An OSF account and project; ✅
A Zotero account;✅
Zotero library linked to OSF;✅
A *.bib file;✅
A GitHub account;✅
A welcome page Wiki on your OSF project;✅
Another wiki page that describes your bare-bones plans (serving as a mini example pre-registration);✅
Been added to the LDP Organization on GitHub;✅
A GitHub repository inside the LDP organization;✅
Finished creating necessary folders (code, data, outputs, etc) and associated _README files within your RStudio project directory;✅
Committed and pushed these changes to GitHub;✅
Connected your GitHub repo to OSF;✅
A .csl file; (find a csl file here (Links to an external site.)) and instructions on how to access and use a CSL file in your markdown document✅
An initial script (.R file) which downloads your data and uses groundhog to manage packages;✅ (optional, however)
A *.RProj file;✅
A preregistration file on OSF;✅
Created a view-only link for your OSF project and send it to your peer;✅
An *.Rmd file that will become your manuscript.✅
A .gitgnore file✅
The complete folder structure and respective files in each folder (data - raw and clean -, code, manuscript, outputs, etc. + README and LICENSE - at least)✅
Your remote repository should have branches that reflect different aspects of the development of your project (e.g., one for analysis, one for figures, one for writing…)✅
An open pull request (PR) from a development branch to your main branch, requesting a review from one of your colleagues.✅
Final Grade: 20/20
Hi Emma, great job and love the improvements from last time! I have a few nit-picky suggestions that aren't crucial, but they might be somewhat helpful. The first thing is maybe instead of the folder "manuscripts" in your github repo, you could title it something a little more descriptive since you also have your pregreg in there? Perhaps "written-outputs" or "prereg-and-manuscript"? Another thing I noticed is that there are some readme files in different formats - "_README.md" and "README". By the looks of it though, the "README" format github is able to recognize as a readme file and puts it in the description section at the bottom of each folder but I think in class we were told "_README"? So I might've missed something because I'm not sure which type to use. Maybe we can figure that out together? Another tip would be to maybe put a pdf of your pregreg actually in your OSF project files so it is easily accessible and easy to read. Otherwise looking good!! :)