Skip to content

Meeting agenda 2020 04 23

Luke W Johnston edited this page Apr 23, 2020 · 8 revisions

Agenda

  1. Python RSE

Now that we've hit DONE on every chapter in the table below, we need to do a sweep of all the chapters to complete any outstanding FIXME's and to ensure consistent formatting across chapters. This will include:

Each item with a question mark needs to be discussed at this meeting because we haven't settled on exactly what is required.

  1. R RSE

  2. Novice Python

Progress report on Zipf's Law updates

Chapter Title File Assignee Progress
1 Introduction py-rse-index.Rmd @DamienIrving DONE
2 Basics of the unix shell py-rse/bash-basics.Rmd @SaraMati DONE
3 Going further with the unix shell py-rse/bash-advanced.Rmd @SaraMati DONE
4 Command line programs py-rse/py-scripting.Rmd @DamienIrving DONE
5 Git at the command line py-rse/git-cmdline.Rmd @cwickham DONE
6 Advanced Git py-rse/git-advanced.Rmd @DamienIrving UNDER REVIEW
7 Automating Analyses py-rse/automate.Rmd @joelostblom DONE
8 Program configuration py-rse/configuration.Rmd @DamienIrving DONE
9 Error handling py-rse/errors.Rmd @joelostblom DONE
10 Working in teams py-rse/teams.Rmd @k8hertweck DONE
11 Code style, review and refactor py-rse/style.Rmd @gvwilson DONE
12 Project structure py-rse/project.Rmd @k8hertweck IN PROGRESS
13 Python packaging py-rse/package-py.Rmd @joelostblom DONE
14 Correctness py-rse/correct.Rmd @lwjohnst86 DONE
15 Continuous integration py-rse/ci.Rmd @lwjohnst86 DONE
16 Publishing py-rse/publish.Rmd @DamienIrving DONE

Minutes

  • Assign out exercises, add more to chapters.
  • Move acknowledgements to one section, near beginning. Greg will take it.
  • Deal with git history and change timestamps? Greg will look into it (#364)
  • #363 PR: Add tree to end, start of chapters? For each chapter or no?
    • Prefer end of chapter whenever tree is changed.
  • Headings: Topic ending rather than question approach.
  • "you" vs "we": More focus on we rather than you, especially in context of actually doing it together.
  • Setup #305: Maybe put in appendix? Or only in online version?
    • Actually, point to Carpentries or some other more frequently updated resource.
  • f.string: Assign Greg to it.
  • Greg will run through the whole thing as a first pass for editing, preferably in May.
  • For diagrams, set up templates or something.
    • Luke will look into it (maybe use draw.io or graphviz or whatever).
    • Need pdf and svg for print and online.
  • We need cover images!