Meeting agenda 2020 03 19

• Time: Thursday, 19 March 2020, 21:00 UTC
• Location: https://zoom.us/j/8911989380
• Moderator: Kate Hertweck
• Note taker:
• Attendees:
• Apologies:

Agenda

1. Overview of progress to date on sections of content:

   • Novice R: all on hold
   • Novice Python: all on hold
   • Intermediate: current focus of our efforts, specifically the chapter assignments in the table below
     • CI review

2. Overview of progress to date on other items

3. Proposals

   • Documentation

4. Discussion items

   • Folder hierarchy
   • String formatting
   • Persona names
   • Shebang

5. Next steps

   • Milestone 1
   • Goals for next meeting
   • Minute taker for next meeting

Minutes

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	@SaraMati
7	Automating Analyses	py-rse/automate.Rmd	@joelostblom	DONE
8	Program configuration	py-rse/configuration.Rmd	@DamienIrving	IN PROGRESS
9	Error handling	py-rse/errors.Rmd	@joelostblom	NEEDS REVIEW
10	Working in teams	py-rse/teams.Rmd	@k8hertweck	DONE
11	Code style, review and refactor	py-rse/style.Rmd	@gvwilson
12	Project structure	py-rse/project.Rmd	@k8hertweck	IN PROGRESS
13	Python packaging	py-rse/package-py.Rmd	@joelostblom	WAITING FOR #345 & #347
14	Correctness	py-rse/correct.Rmd	@lwjohnst86	DONE
15	Continuous integration	py-rse/ci.Rmd	@lwjohnst86	NEEDS REVIEW
16	Publishing	py-rse/publish.Rmd	@DamienIrving

Minute notes

• Write better README lesson

  • In favour

• Teaching shebang

  • Damien: Original were in, took it out, cause not sure. But probably good to include it.
  • Put back in scripting lesson

• Persona names

  • Resolved. Only use Amira Khan. No parent names though.

• String formatting.

  • Resolved. f strings.
  • Use a label to keep take of this for the novice material

• Folder structure

  • Structure found in comment that has "excited" emoji and thumbs up #347
  • For Python.
  • Go with pkg_name/pkg_name/ instead of bin/.
  • Aim to build a package

• If anyone has time, they can:

  • Find FIXMEs or TODOs and start addressing them
  • How file structure is at start each chapter
  • Review CI, packaging, error handling
  • Add images of concepts (just pictures) for those image references names as FIXME