lwjohnst86 commented 4 years ago

Please only use for minutes and agendas. Each comment should contain both the agenda and the minutes of a single meeting (use edit button to add minutes).

lwjohnst86 commented 4 years ago

Meeting 2020-11-20

Agenda

Quick round of introductions and any updates from Python RSE
Discuss and decide on timeline and plan https://github.com/merely-useful/r-rse/issues/1
- Related: Estimated times when people will work on this (e.g. I will work on this each month for a few full days at a time)
Discuss and decide on course design https://github.com/merely-useful/r-rse/pull/20/files
Brainstorm and discuss ideas for item 2 of https://github.com/merely-useful/r-rse/issues/1
- Discuss and decide how to allocate tasks as this stage
Discuss roles: https://github.com/merely-useful/r-rse/issues/2
Plan next meeting and send out calender invites with Zoom link.

Minutes

Summarized from notes taken during meeting

Present:
- Luke Johnson (LJ)
- Greg Wilson (GW)
- Randi Cohen (RC)
- Kate Hertweck (KH)
- Madeleine Bonsma-Fisher (MBF)
- Charlotte Wickham (CW)
- Ian Flores Siaca (IFS)
Update on Python version
- Two reviews in, third may be coming but no need to wait
- A couple of diagrams and some minor text tweaks and we'll wrap up
Process for R version
- RC will need an outline or proposal to get approval
- Process will be the same (reviews, production, etc.)
- Signatories on vol 2 contract are the people who contribute
Timeline and plan at #1
- Timeline looks reasonable (2-4 hr/week from each contributor)
Course design from #20: broad agreement
- Drake doesn't belong if we're going the package route
- CI w/ GitHub Actions provided templates? Through usethis.
- learnr tutorials don't seem in scope. Remove.
Discussion of project assignments in #20:
- Is final project first or second projects? (individual is first, group is second). Rename to "out of class projects" to remove confusion.
  - P1 could be something very small and should replicate solved problem.
  - P2 could be a larger package
  - What about those doing book on own? Then we set this project as something instructors can add if want to, but not necessary for self-learners.
  - Include in "notes to instructors", as a starting point for them.
  - Milestones within each
General discussion:
- Audience for this book is also for those who want/need to teach this stuff but don't know what to teach
- Set on the Zipf's Law project? Changing will only make more work, so for now keep as is. Plus good to have with side-by-side comparison.
- Not sure how all packages developed will fit within course. (Clarified in course design)
How to allocate tasks?
- People go through and pick sections/chapters. For now we do both assignment projects and exercises within chapters.
- Could split tasks by having one person do the Zipf's project assignments and others do parallel exercises
Two action items for next meeting
- 1: go through course design and indicate sections of interest
- 2: think about team roles (outside of writing)
Meet in two weeks at this time.

cwickham commented 3 years ago

Meeting 2020-12-03

Thursday, December 3 20:00 UTC

Agenda

Action items from last meeting:

1: go through course design and indicate sections of interest (update #23 to assign yourself) 2: think about team roles (outside of writing)
Next meeting: Propose same time, in two weeks
Action items for next meeting: Assign yourselves to chapters (#23) and start working on potential final exercise (only a rough draft!) to check off some items in #23

Minutes

Present:
- Luke Johnson (LJ)
- Kate Hertweck (KH)
- Madeleine Bonsma-Fisher (MBF)
- Charlotte Wickham (CW)
- Ian Flores Siaca (IFS)
- Joel Ostblom (JO)

Indicate sections of interest Action: Indicate your interest in particular chapters in #23.

Re-visit in a week to reach some concensus on assignments.

Action: Once you have a chapter, draft what the final exercise might look like in that chapter.

The final exercise works towards assignment 1 - outside of classroom work that builds to a deliverable after Chapter 7. We don't know what assignment 1 is yet, but you should be able to generally describe what the exercise should be.

The chapter will also include other exercises done in class that use the Zipf's Law package to teach the material, but we are not drafting these yet.

More details on chapter contents lives in Syllabus.

Action: LJ needs to make sure IFS and MB have editing permissions.
Team roles #2

Suggested additions:
- MB: Exercise tester, someone at the audience level
- JO: take on more of a floating role.
- Cheerleader / "Pep talk giver". Rotating? Kate will take a turn?
Action: Update #2 to reflect a role you are willing to take (even if temporarily)
Final Project Ideas

Action: Add any ideas to #29 to start brainstorming.
Next meeting: Same time, in two weeks

cwickham commented 3 years ago

Meeting 2020-12-17

Thursday, December 17 20:00 UTC

Agenda

Updates on action items from last meeting:
1. Chapter assignments: #23
2. Draft Final exercises: #30 CW, #31 MBF, #32 IFS
3. Final Project Ideas: #29
4. Roles: #2
Next meeting: Same time, in three weeks?

Minutes

Present:

Luke Johnson (LJ)
Kate Hertweck (KH)
Madeleine Bonsma-Fisher (MBF)
Charlotte Wickham (CW)
Ian Flores Siaca (IFS)
Joel Ostblom (JO)

Updates on action items from last meeting:
1. Chapter assignments: #23 Assigned both primary (lead for chapter) and secondary (bounce ideas off, review, approve PR).
2. Draft Final exercises: In progress #30 CW, #31 MBF, #32 IFS Secondary person to review, once primary and secondary agree, merge. We'll review all together before we move on to next step. Action: Keep working on drafting final exercises, aiming to be done by next meeting.
3. Final Project Ideas: #29 Consensus on weather example: room for localization, expansion Action CW will take a stab at putting something together.
4. Roles: #2 Complete
Next meeting: Same time, in four weeks, Jan 14. Then Jan 28th.

cwickham commented 3 years ago

Meeting 2021-01-14

Thursday, January 14 20:00 UTC

Agenda

Progress update, round table.
- CW: Update on final project idea: https://github.com/merely-useful/r-rse/issues/29#issuecomment-760437658
Thoughts on this: https://github.com/merely-useful/r-rse/pull/33
Thoughts on assignment so far: https://github.com/merely-useful/r-rse/pull/27
- Finish reviewing and commenting on it by next meeting?

Minutes

Present:
- Luke Johnson (LJ)
- Kate Hertweck (KH)
- Madeleine Bonsma-Fisher (MBF)
- Charlotte Wickham (CW)
- Ian Flores Siaca (IFS)
Progress update, round table.
- LK: final assignment drafted (please review)
- IFS: reviewed one, written one more final exercise,
- CW: one more final exercise drafted, needs review
- KH: File system no PR yet, might be more conceptual
- MBF: Drafts for all three assigned chapters
Thoughts on this: https://github.com/merely-useful/r-rse/pull/33 Either agree or neutral, LJ will merge.
Thoughts on assignment so far: https://github.com/merely-useful/r-rse/pull/27
- Action: Finish reviewing and commenting on it by next meeting.
IFS: Infrastructure issues, when do we start implementing these?

Whenever - doesn't affect writing since content and infrastructure, are mostly independent.

Except, wait on renv issue for now, since may increase build time.
IFS: Authorship?

For now, include names of poeple that attend r-rse meetings, and authors on py-rse (since we may re-use content). Sort names alphabetically.

Can re-visit again when ready to publish.
CW: Update on final project idea: https://github.com/merely-useful/r-rse/issues/29#issuecomment-760437658

Data analysis or data access? Do we assume data vis, data wrangling? Audience? User personas?

Conclusions: Aim for more complicated weather data (e.g. at least daily observations), not US centric, no paywall.

Actions:

Review project assignment #27
Finish final exercises #23
Think about other sources of weather data #29

Next meeting: Jan 28th same time

cwickham commented 3 years ago

2021-01-28

Thursday January 28th 12:00 UTC

Agenda

Agree on project assignment and merge.
Agree on final exercises and to move on to next stage.
Discuss #29, sources of data and any other brainstormed ideas.
Brainstorm estimated number of exercises to aim for in each chapter as we work through phases 4 and 5 (#1).

Minutes

Present:
- Luke Johnson (LJ)
- Kate Hertweck (KH)
- Madeleine Bonsma-Fisher (MBF)
- Charlotte Wickham (CW)
- Ian Flores Siaca (IFS)
Agree on project assignment and merge.

Action: Ian to review today, then get merged in.
Agree on final exercises and to move on to next stage.

A few reviews pending.

Action: Finish pending reviews, get your chapters merged and checked off in #23.

Action: Once all merged, JO, LJ and KH to do once over of all chapters to check they make sense in sequence.
Discuss #29, sources of data and any other brainstormed ideas.

GHCN data looks best.

Do we want places with distinct seasonality, extremes? Agree to focus on Kenya - a country with a range of type climates (and not US-centric).
Brainstorm estimated number of exercises to aim for in each chapter as we work through phases 4 and 5 (#1).

Clarification:
- Core exercises: formative, happen in the body of the chapter, most likely in class, lots of scaffolding, practice what has just been covered. Build the core package.
- Final exercises: summative, happen at the end of the chapter, most likely outside class. Build the assignment package.
Core package: Zipfs Law Assignment package: Kenya climate data as one concrete example, but customizable to class/instructor.

For now, develop drafts of packages, and core exercises in parallel. Then reconcile to check packages cover neccessary exercises, with nothing extraneous.

Actions:
- Draft packages: CW=Zipfs Law, IFS=Kenya. Put repos in merely-useful org for now.
- Everyone else: Drafting core exercises for chapters, rough idea of steps to be taken, code to be used etc.

Next meeting: same time in two weeks? Feb 11th

cwickham commented 3 years ago

2021-02-11

Thursday Feb 11th 20:00 UTC

Agenda

Progress updates.
For reviewers of first-phase-review: Syllabus needs a lot of work, so @lwjohnst86 is making a separate PR that we can all review.
Discuss #61

Minutes

Present:

Luke Johnson (LJ)
Kate Hertweck (KH)
Madeleine Bonsma-Fisher (MBF)
Charlotte Wickham (CW)
Ian Flores Siaca (IFS)
Joel Ostblom (JO)

Progress updates:
- LJ: Syllabus needs heavy review, issue opened for that.
  - CW: Draft Zipfs package up at: https://github.com/merely-useful/zipfs
  - IFS: Draft Kenya package up at: https://github.com/merely-useful/kenyaweather/issues
  - JO: Will have a bit more time to work on assignments next week
For reviewers of first-phase-review: Syllabus needs a lot of work, so @lwjohnst86 is making a separate PR that we can all review.
Discuss #61. Agreed, in main body "you" refers to reader, in instructor chapters/sections "you" refers instructor.

Action items:

Provide comments on packages
Complete review assignments (if you have them)
Keep working on drafting code/exercises in chapters.

Next Meeting - same time in two weeks

cwickham commented 3 years ago

2021-02-25

Thursday Feb 25th 20:00 UTC

Agenda

Progress updates.

Minutes

Present:

Luke Johnson (LJ)
Kate Hertweck (KH)
Madeleine Bonsma-Fisher (MBF)
Charlotte Wickham (CW)
Joel Ostblom (JO)

Progress updates:
- LJ: Reviewing stuff
- KH: Reviewed syllabus
Syllabus Discussion: Is syllabus the right name for this content? Syllabus has a specific meaning in US and Canadian university contexts. If we want learner to read it, needs to be obviously part of main content. Content for instructors should be obviously not part of main content.

As an example: https://moderndive.com/index.html We should have a diagram as part of our syllabus/introduction

Content can live where is for now. KH might make an issue for rearrangement/renaming if time over next two weeks.
Next meeting: Same time two weeks

cwickham commented 3 years ago

2021-03-11

Thursday Mar 11th 20:00 UTC

Agenda

Progress update.
- Progress of review for #59
Discuss https://github.com/merely-useful/r-rse/issues/59#issuecomment-796919906

Minutes

Present:

Luke Johnson (LJ)
Madeleine Bonsma-Fisher (MBF)
Charlotte Wickham (CW)
Ian Flores Siaca (IFS)
Joel Ostblom (JO)

Progress update.
- LJ: reviews almost done, some progress on chapter steps
- MBF: PRs for bullet point outlines, ready for review.
- IFS: Kenya weather almost done. Has everything, works. One function needs some re-factoring.
- CW: Setting goal of two chapters with bullet point outlines by next meeting.
Discuss https://github.com/merely-useful/r-rse/issues/59#issuecomment-796919906

Idea is once current overall review is done, review one or two chapters together during the meeting. Keeps everyone on same page, and up to date with chapters they don't work on. Yes, we'll do this.

Next meeting: Same time (for those going onto DST this weekend, others check link or calendar invite), in two weeks.

cwickham commented 3 years ago

2021-03-25

Thursday March 25th 19:00 UTC

Agenda

Progress updates:
- Ready for review #65
Discuss #71

Minutes

Present:

Luke Johnson (LJ)
Kate Hertweck (KH)
Madeleine Bonsma-Fisher (MBF)
Charlotte Wickham (CW)

Progress updates:
- LJ: Ready for review #65, almost done one action steps.
- KH: Made comments on #65 too. Think about learner personas. Will take a look at packages.
- CW: Two chapters bullet pointed, committing to one more for next time.
Discuss #71
- Where do get people to do their read/write exercises? Want to be authentic, also instructors may have their own ideas on this anyway.
- Learner personas, we don't have someone who is a student taking a class. Should we add one. KH will take a look.

Next meeting: Same time in two weeks? CW to check with IFS and JO.

cwickham commented 3 years ago

2021-04-08

Thursday April 8th 19:00 UTC

Agenda

Progress Updates
CW: Propose moving meeting time +1, or -1 hour.
- Thursday, April 22, 2021 at 18:00:00 UTC or,
- Thursday, April 22, 2021 at 20:00:00 UTC

Minutes

Present:

Luke Johnson (LJ)
Kate Hertweck (KH)
Madeleine Bonsma-Fisher (MBF)
Charlotte Wickham (CW)
Ian Flores Siaca (IFS)

Progress updates:
- LJ: No updates
- KH: Submitted issue on terminology "book" vs. "course" #73. Do we need a persona for an instructor? Yes. Move up to "Who might be interested in this book?". Will update personas.
- IFS: Will push bullets for chapter 7, working on chapter 9.
- CW: Added action steps for Code Correctness
- MBF: What was the split between Community Involvement and Project Management?
  - Community Involvement - "people using the code", how to install from GitHub, file an issue/bug report, etc. Only one code author.
  - Team Package Management - "people who are contributing code". Dealing with PRs. Many code authors.
MBF will revise the Community Involvement and Project Management to be consistent with this discussion.
CW: Propose moving meeting time +1, or -1 hour.
- Thursday, April 22, 2021 at 18:00:00 👍🏻
- Thursday, April 22, 2021 at 20:00:00 UTC

Actions for all: Keep up on reviews, outlining your assigned chapters. When primary and secondary leads agree, then merge. End of May is our deadline.

cwickham commented 3 years ago

2021-04-22

Thursday, April 22, 2021 at 18:00:00

Agenda

Progress updates.
Discussion on use of Governance file? Thoughts?
@joelostblom status of first phase review?
@ian-flores good to merge #82?

Minutes

Present:

Luke Johnson (LJ)
Kate Hertweck (KH)
Madeleine Bonsma-Fisher (MBF)
Charlotte Wickham (CW)
Ian Flores Siaca (IFS)
Joel Ostblom (JO)

Progress updates.
- LJ: Finished, reviewed.
- IFS: Pushed Chapter 7, still working on Chapter 9, went through Infrastructure issues, and created project board. Start with spell checker, linter and contributing guidelines. Then build system. Contributing: Luke has something in progress here, will have PR soon. KH also has some stuff to add contributing. Will wait for LJ's PR before tackling this.
- JO: Will get to it next week.
- CW: Done.
- MBF: One more, probably submit tomorrow.
- KH: Will respond to LJ's review comments. Then review on existing PRs.
Discussion on use of Governance file? Thoughts? IFS: really useful in a current project.
KH: want to see more of this in the world, we should recommend (and model it). KH will take on some research on what the file should look like. MBF: should there be separate repo for team organizing, or have it happen in project repo? LJ: likes having a separate repo, e.g. when have multiple projects worked on when you have control over org. KH: this might be someone's first project, so better to keep simpler, e.g. keep in project.
@joelostblom status of first phase review - on its way.
@ian-flores good to merge #82? Yes. IFS will merge.

Next meeting: same time two weeks.

cwickham commented 3 years ago

2021-05-06

Thursday, May 6, 2021 at 18:00:00 UTC

Agenda

Progress updates.
- Finished first review phase!
Forgo "second phase review" after finishing items 4 and 5 of #1?
Discuss #75
Discuss #96

Minutes

Present:

Luke Johnson (LJ)
Kate Hertweck (KH)
Madeleine Bonsma-Fisher (MBF)
Charlotte Wickham (CW)
Ian Flores Siaca (IFS)

Progress updates.
- Finished first review phase!
- IFS: Pushed Chapter 9, working on file validator GitHub action
- CW: Will review Chapter 9
- KH: Reviewing MBH PR's for material split. Suggestion: first chapter the bare minimum for interacting with anyone, second chapter what makes the process of working with others easy. Combine 12 and 14? Or some of 12 into 10? KW will take another look for how to divide this content over these chapters. Splitting 12: Issue tracking and labeling -> 10, Project management -> 14.
- MBF: Responded to review, will wait on KH for final merge.
Forgo "second phase review" after finishing items 4 and 5 of #1? Discuss a chapter a week instead of review? In the meeting discuss one or two chapters, presented by lead author. Start once we have finished items 4 and 5? We want to start this soon, but needs early chapters finished. KH to work on first chapter ASAP. LJ will make schedule.
Discuss #75
- KH: Should this be a different book?
- CW: Will be hard to integrate with our very linear package flow.
- LJ: Acknowledge this is a thing and refer to other resources, e.g. ROpenSci, tidyverse design guide.
Discuss #96
- CW: Are the labels enough? Or do we use chunk options too?
- LJ: Thinking chunk options too.
- CW: Draft, and try with a chapter first?
- CW: How do we automate?
- LJ: Maybe pull out chunks into script, script tuns to generate tmp git repo, git repo moved to github. Hopefully if we figure out code labelling we can punt this to later.

cwickham commented 3 years ago

2021-05-20

Thursday, May 20, 2021 at 18:00:00 UTC

Agenda

Progress updates.

Minutes

Progress updates

Short meeting this time so just a few brief updates (added by Joel hence the different formatting):

Luke, no updates, will make review schedule that will start at the next meeting.
Kate, had more time recently, just submitted PR on the file system chapter and R projects chapter. Also submitted a PR on the community involvement splitting parts of it into other chapters.
- Will not be available for meetings mid June.
Ian cleaned up yaml file PR, will address comments on ch 9 next.
Maddy, no updates
Joel, no updates

lwjohnst86 commented 3 years ago

2021-06-03

Thursday, June 3, 2021 at 18:00:00 UTC

Agenda

Progress updates.
Quick review of #96
Reminder to finish review of #100.
Git in Terminal vs using gert package for when RStudio integration isn't enough.
Review and discuss preface and assignment (schedule at #103).

Minutes

Present:

Luke Johnson (LJ)
Kate Hertweck (KH)
Madeleine Bonsma-Fisher (MBF)
Charlotte Wickham (CW)
Ian Flores Siaca (IFS)
Joel Ostblom (JO)

Progress updates.
- LJ: Some organizational stuff, no other updates.
- KH: Git solo, do we need to introduce Unix? Not really necessary for Git anymore (use gert instead). See #105. Add some Git stuff to Appendix, e.g. security, link to other good resources. No objections to dropping Unix. KH will work on editing to reflect that. IFS: Is Gert widely used? LJ uses it.
- IFS: Chapter 15 pushed and merged
Quick review of #96 Purpose: make it easier to work with book content programmatically. CW: Will try out format on first chapter, package setup.
Reminder to finish review of #100. Done and merged.
Git in Terminal vs using gert package for when RStudio integration isn't enough. Resolved. Use gert.
Review and discuss preface and assignment (schedule at #103). MBF: Will add how this review will work in issue.

Review discussion for preface and appendix:
- Do we need an R package for the book? No.
- Should we fold the assignments into "For Instructors"? Remove ambiguity between in-text exercises and assignments for students. I.e. in preface don't mention "assignments" but still talk about the packages that are being built.
- Should the final exercises be pulled out into a separate chapter? Final exercises should be for kenyaweather (first project). Let's have all the final exercises in a single place as well, at some point.

Next meeting same time, two weeks.
KH and CW to lead reviews on first two chapters: #103

cwickham commented 3 years ago

2021-06-17

Thursday, June 17, 2021 at 18:00:00 UTC

Agenda

Progress Updates
Review
- chapters/02-filesystem.Rmd led by KH
- chapters/03-package-setup.Rmd led by CW

Minutes

Present:

Luke Johnson (LJ)
Kate Hertweck (KH)
Madeleine Bonsma-Fisher (MBF)
Charlotte Wickham (CW)
Ian Flores Siaca (IFS)

Agenda

Progress Updates
- LJ: No updates
- KH: IFS and CW take a look at https://github.com/merely-useful/talk/pull/1. IFS: Is this a talk that is scheduled? No, make it easy to pair up and give a talk if invited etc. Prepared so at the ready when needed.
- IFS: No updates.
Review
- chapters/02-filesystem.Rmd led by KH
  
  Updates in: https://github.com/merely-useful/r-rse/pull/107
  
  MBF: Will our screenshots use default window layout? Yes. But, we might also mention Appendix where we talk about defaults people might change.
  
  KH: Include talking about putting code in a source file.
- chapters/03-package-setup.Rmd led by CW
  
  IFS: How much detail to go in to regarding start up scripts, .Rprofile, .Renviron etc. ? Not much, just focus on the end results of the usethis functions.
  
  Do in appendix? Make an issue about this. CW to open.

Next time: July 1st.

cwickham commented 3 years ago

2021-07-01

Thursday, July 01, 2021 at 18:00:00 UTC

Agenda

Review:

Led by CW: chapters/04-function-development.Rmd
Led by KH: chapters/05-version-control-solo.Rmd (I am so sorry, I had a calendar sync malfunction with the new job and will miss the first half of the meeting)

Minutes

Present:

Luke Johnson (LJ)
Madeleine Bonsma-Fisher (MBF)
Charlotte Wickham (CW)
Ian Flores Siaca (IFS)
Joel Ostblom (JO)
Kate Hertweck (KH)

Progress Updates
- CW: Some questions about labelling etc, in #96
Review:
- Led by CW: chapters/04-function-development.Rmd
  - Native pipe vs. tidyverse pipe Native only first argument, tidyverse in lots of existing work Use tidyverse pipe for now.
  - Should we use rlang::abort() or stop()? Think about this.
  - Preview testing, early in this chapter when have working chunk, and perhaps when adding an example to docs.
- Led by KH: chapters/05-version-control-solo.Rmd (I am so sorry, I had a calendar sync malfunction with the new job and will miss the first half of the meeting)
  - Current version references git commands, but this will be done with point and click interface.
  - Branches introduced now to help scaffold up to forks etc. in later working with others chapter. Maybe remove branch exercises from final exercise.
  - Automate screenshots? May be easier with web pages as opposed to RStudio IDE. KW will open issue.
  - Final exericse will be for kenyaweather. First exercise will be nested in main narrative. Second one becomes final exercise.
  - GitHub authentication? What and how much to cover? Don't want to demotivate, but does make life easier.

Next time: In four weeks July 29th

cwickham commented 3 years ago

2021-07-29

Thursday, July 29, 2021 at 18:00:00 UTC

Agenda

Review:
- CW: chapters/06-code-correctness.Rmd
- IFS: chapters/07-build-management.Rmd
Some review https://github.com/merely-useful/r-rse/pull/104?
Discuss #111

Minutes

code correctness:

More generic final exercise or no?
Ian: Thought about Test Driven Development?
- Probably will mention it, as a process
Luke: Do defensive programming here?
- Its mostly in function development, we'll not do it here.
- https://github.com/merely-useful/r-rse/blob/cab2ed14ed82c3a3240b24ddc7847f144fe1d6c3/chapters/04-function-development.Rmd#L69
- Unit tests are one component of defensive programming, but this chapter shouldn't be on the functions themselves.

build management:

Comment from Ian: Showcasing things through IDE vs code-based, should discuss this.
Luke: Maybe use CLI for infrastructure of building book, e.g. https://docs.github.com/en/actions/managing-workflow-runs/using-workflow-run-logs#viewing-logs-with-github-cli
Charlotte: Maybe also have someone else install your package and use it.
- To build off of that, maybe incorporate rOpenSci "checks"? (e.g. presence of unit tests, etc)? Maybe as a section in the "CRAN checks" area?
- What about solo learners? Maybe they can install from github, so they have an idea of what the user experiences? Or install on another computer they have access to?

Discuss #111:

need to think about non-native speakers and cultural idioms, and not alienating others
need to stay consistent
maybe only have images as silly and not text?
- maybe generalize images rather than use screenshots?
- E.g. with a big concept map, workflow concept map etc.
- Or e.g. add silly faces/oogly eyes to images
Let's revisit this after two meetings
maybe not use emojis though

Other business:

Maddy switch dates for next meeting.
Charlotte will be off for a while and Kate will take over organizing.

cwickham commented 3 years ago

2021-08-12

Thursday, Aug 12, 2021 at 18:00:00 UTC

Agenda

Review:

chapters/09-package-website.Rmd
chapters/11-version-control-workflow.Rmd
Update timeline by 2 months?

Minutes

For package website:

Link coc/contributing in website

For workflow with Github:

Branch protection up to this chapter from 13?
Idea: Script to add PR to learners repo?

For the timeline:

Maybe new deadline for mid Dec for milestone 7?

k8hertweck commented 3 years ago

2021-08-26

Thursday, Aug 26, 2021 at 18:00:00 UTC

Agenda

Review:

chapters/08-documentation.Rmd
chapters/10-community-involvement.Rmd
Update timeline by 2 months? Check with those not in attendance at previous meeting

Minutes

Chapter 8: Documentation

not sure what content will look like for documenting test functions, assuming relatively small amount of content required, good because it integrates across other chapters' content
include typo to show what errors highlighted by "spelling" look like
change final exercise about vignettes to show how package interacts with another package

Chapter 10: Community involvement

include more tie-ins with previous chapter (package website)
include exercise that asks students to consider what should go into a code of conduct associated with group work: use to motivate why a CoC is needed, before introducing boilerplate text
move up contributing guidelines, so it can bridge with technical concept in previous chapter

Next meeting

updating timelines
specify tasks required and when (freeze on package code? use waldo)
one chapter written to use as template for structure, tone, etc

k8hertweck commented 3 years ago

2021-09-09

Thursday, Sept 9, 2021 at 18:00:00 UTC

Agenda

Review:

chapters/12-package-release.Rmd
chapters/13-team-package-dev.Rmd

Planning for next steps:

Updating timeline: complete first pass of chapter drafts by mid-December 2021? Should decide items below moving forward with chapters
finalize final package(s?) and freeze on package code; use waldo)
specify exactly what tasks are required and when
have one chapter written to use as template for structure of content, tone of writing, etc (decide which chapter and who should do this)

Minutes

Kate and Maddy were the only attendees. We deferred discussion of the last two chapters till next time, and identified a plan for completing chapter drafts (see agenda for next meeting). We identified a plan and time

k8hertweck commented 3 years ago

2021-09-23

Thursday, Sept 23, 2021 at 18:00:00 UTC

Agenda

Review:

chapters/12-package-release.Rmd
chapters/13-team-package-dev.Rmd

Planning for next steps:

Proposal for updating timeline, with deadlines indicated when possible:

by Oct 7: Ian drafts packaging chapter (for the rest of us to use as template), including both code chunks and narrative (for language/tone)
by Oct 7: Kate identifies which parts of zipfs package are developed in each chapter
at Oct 7 meeting: finalize final package(s?) and freeze on package code; use waldo)
write out code for in-text chunks in chapters, make everything executable (put in R chunk), this doesn't have to be done by person in charge of chapter, guidelines for formatting here
write sentences comprising the chapter content (noting that some places don't have very clear concepts outlined yet)
by mid-December: write final exercises for each chapter (with possible solutions to ensure feasibility)
complete review/proofreading of chapters
write instructions for instructors

Minutes

Present: Kate, Luke, Ian, Maddy

Chapter 12 - Package release

Will we use the CRAN Windows builder? Mention it but don’t make them do it (to avoid using CRAN resources)
Some of these ‘best practices’ involve a lot of activity for only a little return, so talk about them but don’t have them as an exercise. Move 2B and 2C in exercises to a callout at the end of the chapter.
On use / overuse of free resources:
- are we worried about overuse of rHub from people using the book itself?
- it's worth thinking about scaling whenever we recommend free resources. But the further you get in the book, the less likely people are to do the exercise as training (as opposed to doing it for real).
- possibly include in instructor notes a warning to assess the impact of many students using free resources.
- rHub is backed by the R consortium, so they have money and resources.

Chapter 13: team-based development

remove separate solo/team directions, tell solo folks to assume they will be eventually working in a team and they'll be preparing for that
line 30: what is callout box?
we could have them transfer their project to the repo?
github 2FA is now in an appendix, but we still mention it here
how to help people understand setting permissions, as it relates to security, responsibility, accountability, and division of labor? We want to help people feel like this isn't a super scary thing, but also make sure that their work is protected from accidental actions. We should make sure we have a larger group of people read this section to ensure we're representing a variety of perspectives
coordinate exercises here with the previous chapter
indicate options about where information in this chapter can reside
we need to develop these documents for this project!
example of project that has all of these included: https://github.com/carpentries/glosario
chapter has a lot of content, we may need to recalibrate how much time to spend on each idea, especially since some content was moved from chapter 12. This is also the LAST CHAPTER!
change exercises for project and milestone to project OR milestone

Admin

Ian will draft a chapter by Oct 7
at October 7 meeting, will look over chapter and discuss
Kate will look at which parts of package are developed in which chapter to avoid conflicts make sure nothing is missing
for everyone: take a stab now at writing out code in your chapters to cross-reference with the template.

k8hertweck commented 3 years ago

2021-10-07

Thursday, Oct 07, 2021 at 18:00:00 UTC

Agenda

review draft of packaging chapter, focusing on use as template for later chapters
review plan for code/files developed in each chapter
finalize package code (at least zipfs) and agree on code freeze (and steps needed before then)
identify at least the next deadline for upcoming tasks (see below)
(small note, there's actually one last chapter that we need to add to the repo, the "summary" chapter: #109).
Review #104?

Upcoming tasks:

write out in-text code for chapters, make everything executable (put in R chunk)
write sentences comprising the chapter content
by mid-December: write final exercises for each chapter (with possible solutions to ensure feasibility)
complete review/proofreading of chapters
write instructions for instructors

Minutes

Discussed Luke’s chapter draft
- don’t worry too much about code evaluating correctly, pseudocode is ok as a start
- follow conventions in issue #96
- Luke has a plan for how GitHub actions will be used to generate everything
Discussed Kate’s layout notes
- zipfs files will be created in a temporary directory
- move README creation to package setup chapter – use usethis function, but say that other sections will be discussed later
- edit README in version control chapter - move some things from chapter 8?
- plot_rank and fit_zipfs aren’t explicitly necessary for pedagogy – keep plot_rank, but move fit_zipfs to appendix (math may be unnecessarily intimidating, not actually needed for purpose of book, the log-log plot by itself gets the zipfs point across)
Discussed timeline:
- stick to revised timeline
- next meeting in one month, everyone have 1 complete chapter draft by then
- gentle check-in in two weeks (asynchronous)
- chapter 2nds have moved to chapter heads for Charlotte’s chapters

Action items:

@k8hertweck: make issues for changes resulting from layout discussion (README, plot_rank, fit_zipfs)
@mbonsma: review Luke’s intro changes and persona changes
@lwjohnst86: review Maddy’s chapter changes
everyone: work on 1 chapter draft

lwjohnst86 commented 2 years ago

2021-11-18

Thursday, Nov 18, 2021 at 18:00:00 UTC

Agenda

Updates

Minutes

Forgot to take minutes?

lwjohnst86 commented 2 years ago

2022-01-13

Agenda

Status updates.
Did we take minutes from last meeting?

Minutes

Present: Luke, Kate, Charlotte, Madeleine

Updates:

moved some chapters from Charlotte and reassigned to secondaries, can keep things as they are in schedule and Charlotte can take back most of her chapters.
Everyone is working (slowly) on adding text to their chapters.
Should we borrow text straight from the Python book? YES: feel free to lift exactly and then modify for tone.
Writing: we'll need to make sure the tone is cohesive, probably near the end. Split reviews into "technical" and "tone"?
Make sure code chunks are executable so we can work on compiling the whole thing

lwjohnst86 commented 2 years ago

2022-01-27

Agenda

Status updates.

Minutes

lwjohnst86 commented 2 years ago

2022-02-24

Agenda

Status updates.

Minutes

Is license an issue with using material from python book? (open issue, @k8hertweck look into it)
Some progress, but its been hard.

cwickham commented 2 years ago

2022-03-10

Agenda

Status updates.
- CW: Won't make it to meeting, incremental progress on chapter 4.

lwjohnst86 commented 2 years ago

2022-04-07

Agenda

Updates

Minutes

Maddy finished a rough draft of her chapter
Others are working along, having difficulty with finding time, but happy with progress.
Might start stricter/more firmer deadlines during the summer.

lwjohnst86 commented 2 years ago

2022-06-30

Agenda

Discuss and plan #131

Minutes

Do monthly asynch co-working day, first Thursday of the month, but first session will be July 14th.
Will try Discord. Luke will send out info about how to join.
Will switch to using Quarto instead of R Markdown (but really, it doesn't change much in the end for writing, only for building the website).

merely-useful / r-rse

Minutes and agendas #8

Meeting 2020-11-20

Agenda

Minutes

Meeting 2020-12-03

Agenda

Minutes

Meeting 2020-12-17

Agenda

Minutes

Meeting 2021-01-14

Agenda

Minutes

2021-01-28

Agenda

Minutes

2021-02-11

Agenda

Minutes

2021-02-25

Agenda

Minutes

2021-03-11

Agenda

Minutes

2021-03-25

Agenda

Minutes

2021-04-08

Agenda

Minutes

2021-04-22

Agenda

Minutes

2021-05-06

Agenda

Minutes

2021-05-20

Agenda

Minutes

Progress updates

2021-06-03

Agenda

Minutes

2021-06-17

Agenda

Minutes

Agenda

2021-07-01

Agenda

Minutes

2021-07-29

Agenda

Minutes

2021-08-12

Agenda

Minutes

2021-08-26

Agenda

Minutes

Chapter 8: Documentation

Chapter 10: Community involvement

Next meeting

2021-09-09

Agenda

Minutes

2021-09-23

Agenda

Minutes

Chapter 12 - Package release

Chapter 13: team-based development

Admin

2021-10-07

Agenda

Upcoming tasks:

Minutes

2021-11-18

Agenda

Minutes