-
Notifications
You must be signed in to change notification settings - Fork 63
Meeting agenda 2019 10 22
Greg Wilson edited this page Oct 22, 2019
·
5 revisions
- Time: Tuesday, 22 October 2019, 21:00 UTC
- Location: https://zoom.us/j/9434606083
- Moderator: Charlotte Wickham
- Note taker: Greg Wilson
- Apologies:
- Overview of progress to date on sections of content:
- Overview of progress to date on other items
- Proposals:
- Discussion items:
- Next steps
- Select moderator for next meeting
- (Previous moderators, in reverse chronological order: Greg Wilson, Luke Johnston, Damien Irving, Madeleine Bonsma-Fisher)
Present:
-
Charlotte Wickham (CW)
-
Greg Wilson (GVW)
-
Damien Irving (DI)
-
Kate Hertweck (KH)
-
Madeleine Bonsma-Fisher (MBF)
-
Joel Ostblom (JO)
-
Elizabeth Wickes (EW)
-
Novice R: no reports
-
Novice Python:
- MBF reviewed Jupyter/Jupytext
- JO
-
RSE:
- GVW has done lots of updates, suggests merging and then reviewing on top of that
- will do the merge and others will then comment
- KH proposes splitting into project management vs. team management
- Novice Py/R shares material on how to be a member of a project (e.g., why a CoC)
- RSE material is material for people running a project (e.g., how to enforce a CoC)
- DI: writing Python command-line scripts, almost ready for merge
- GVW: where to explain how to write modules to be imported into notebooks?
- DI: will add beside command-line scripting stuff
- JO: discuss when to break things into modules should be here too - how to get code out of a notebook into a script
- CW: novice should be exposed to the idea of reusing code outside notebooks, and there is already mention in the novice R chapter
- EW: there is material on how to import in the novice material
- JO: break at "dumping functions into file" but before "making a module"
- EW: volunteers to help
- DI and JO will point out starting points
- GVW has done lots of updates, suggests merging and then reviewing on top of that
-
JO: what Python plotting library?
- matplotlib, seaborn, ...
- GVW: votes for seaborn
- JO: we're always going to have dataframes, so that doesn't require matplotlib
- MBF: how transferable is one library to the next?
- JO: it's complicated...
- EW: installation headaches with seaborn
- DI: static images are most important (because that's what winds up in publications)
- EW: what about maintenance crews?
- JO: altair has some annoyances
- discussion continues in issue until someone is ready to put forward a proposal
-
GVW: prompts in the text?
- DI: likes prompts - people can handle a dollar sign
- MBF: no prompts (has seen people type it and has done it herself), and if you have to warn people, you can warn them either way
- KH: no prompt unless the material specifically demands it
- only include the prompt when it's specific to the content
- EW: pro-prompt - "you know you're in Unix because you see the dollar sign" is the first thing talked about in the Unix lesson
- important that they know difference between prompts in different contexts: shell vs. interpreter vs. cell
- JO: death to prompts!
- CW: no prompt in novice R book
- CW: can we use prompts in RSE but not in novice?
- split the decision: what to do in novice and what to do in RSE?
- Nov 5
- Madeleine Bonsma-Fisher (moderator), Charlotte Wickham (note-taker)