-
Notifications
You must be signed in to change notification settings - Fork 63
Meeting agenda 2019 06 25
Luke W Johnston edited this page Jun 26, 2019
·
7 revisions
- Time: Tuesday, 25 June 2019, 21:30 UTC
- Location: https://zoom.us/j/9434606083 (starting here: https://zoom.us/j/3923408221)
- Moderator: Christina Koch
- Note taker: Luke Johnston
- Apologies:
- Introductions
- Overview of progress to date:
- Proposals. There are no proposals currently, can skip.
- Discussion items
- Next steps
- Select moderator for next meeting
- Which datasets to use? Authors choice for choosing, whatever works best for the context
- Luke: Merge in PR for links
- Getting start novice (data and paths)
- Greg: Too much deviating into paths etc
- Damien: Have data in directory so no paths are introduced?
- Several say yes good idea
- We'll do it that way for now
- Brandeis:
- Question, algorithmic, others have comments? For data analysis
- Maddy will look over data analysis review for Python when ready
- Greg will review reproducible PR
- Content will be separate between Novice R and Python
- Joel question: everything separate or share text?
- Yes, share as needed but definitely for novice it will be separate and maybe even different order
- Damien question: How to review? Fork review and look at in bookdown? When is PR good enough to merge in?
- Review how you feel comfortable (review raw Markdown, or as generated book)
- Greg: Don't need to be perfect, just get things done and create more material.
- Christina question: Who to let know who merges?
- Flag either Luke or Greg about merging/final check of PR.
- What's the process for contributing?
- Need more detailed or guided contributing.
- Style guide in contributing
- Also how style is set throughout book for learners to know about, like a legend of sorts
- Maddy: That's a great idea Brandeis It might be good as more of a sidebar than a section - the distinction between all the types is not obvious to beginners, but it would be good to have it written down to refer to. Like a glossary more than an introduction.
- Damien: We can probably add to the style guide as we go? Maybe a style_guide.md file?
- Convert column names in data to reformat to snake case in datasets
- Or get them to clean it up
- Or get clean first and then show them messy later on, to show that in the real world things are messy
- Damien about #128:
- Live coding then exercises and back and forth?
- Other assignments?
- Brandeis: depends on culture of class. Think about maybe having link to exercise or have them to do it as inclass exercise or as take home. And depending on instructors. Maybe also include "capstone"... but for later. Let's get more content down first.
- Damien: Concept given in the exercise.
- Maddy: Material is readable with exercises optional. So its not required but keep flexibility.
- Damien to make proposal: Where to put exercises? End, throughout?
- Jonathan to moderate next meeting.