[ ] Ensure that the material matches the presentation and the book. The first priority for the book is that it matches any changes made to the presentation. The bookdown can and should have extra text so that participants can work through the material without help (i.e. the extra text should essentially fill the spot of a presenter, consider taking material from the presenter notes and adding it here).
[ ] Eng. and Fr. Book - Chapter 0.2 - Contributor section should be added (currently under construction) and updated to match README. (Issue58 ).
[ ] Eng. presentation - Slide 8 - Hide this text from the presentation using the ??? in Rmarkdown presentation code “Note: Should not be super long, they have the script to make the plots. You can almost just give them time to think while you help participants with installing packages. If there is none, you can just skip the time to think, and simply have a group discussion plot by plot.”
[ ] Fr. presentation - Merge diapo 65 avec 66 version pour unifier avec la version eng.
[ ] Correct code chunks from challanges Verify that all code shown in the presentation is present in the RMarkdown version. It is particularly important for the exercises (or challenges) to match the challenges in the presentations. Verify that code runs correctly.
[ ] Eng. & Fr. versions - Correct challenge 8 mod.glm <- glm.nb(PLD ~ temp + feeding.type, family = poisson(), data = inverts) the correct code should be, "mod.glm <- glm.nb(PLD ~ temp + feeding.type, data = inverts)",* glm.nb automatically uses family poisson, and you shouldn't include it in the code.
[ ] Verify the code. Verify that the code chunks work, and that relevant outputs (tables, figures, etc.) are being shown correctly in the book.
[ ] Verify the writing. Reading through the text (presentation and book) to improve the grammar and syntax is greatly appreciated. We listed some of the errors, but there might be some more.
[ ] Fr. presentation - Diapo 23 (Manque une "v" à pouvoir "nous voulons pouoir faire")
[ ] Fr. presentation - Diapo 26 (il y a un mot répété "Au lieu d'estimer d'estimer une ordonnée")
Please read through the presenter and developer protocol for help with the GitHub workflow. For RMarkdown help, refer to our book template. R Markdown: The Definitive Guide is also a very helpful resource, and covers the tasks outlined below, including how to preview the book locally while you work.
[ ] Ensure that the material matches the presentation and the book. The first priority for the book is that it matches any changes made to the presentation. The bookdown can and should have extra text so that participants can work through the material without help (i.e. the extra text should essentially fill the spot of a presenter, consider taking material from the presenter notes and adding it here).
[ ] Correct code chunks from challanges Verify that all code shown in the presentation is present in the RMarkdown version. It is particularly important for the exercises (or challenges) to match the challenges in the presentations. Verify that code runs correctly.
[ ] Verify the code. Verify that the code chunks work, and that relevant outputs (tables, figures, etc.) are being shown correctly in the book.
[ ] Verify the writing. Reading through the text (presentation and book) to improve the grammar and syntax is greatly appreciated. We listed some of the errors, but there might be some more.