Closed lwjohnst86 closed 1 year ago
Summarized from notes taken during meeting
Thursday, December 3 20:00 UTC
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
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:
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
Thursday, December 17 20:00 UTC
Updates on action items from last meeting:
Next meeting: Same time, in three weeks?
Present:
Updates on action items from last meeting:
Chapter assignments: #23 Assigned both primary (lead for chapter) and secondary (bounce ideas off, review, approve PR).
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.
Final Project Ideas: #29 Consensus on weather example: room for localization, expansion Action CW will take a stab at putting something together.
Roles: #2 Complete
Next meeting: Same time, in four weeks, Jan 14. Then Jan 28th.
Thursday, January 14 20:00 UTC
Present:
Progress update, round table.
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
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:
Next meeting: Jan 28th same time
Thursday January 28th 12:00 UTC
Present:
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:
Next meeting: same time in two weeks? Feb 11th
first-phase-review
: Syllabus needs a lot of work, so @lwjohnst86 is making a separate PR that we can all review.Present:
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. Agreed, in main body "you" refers to reader, in instructor chapters/sections "you" refers instructor.
Action items:
Next Meeting - same time in two weeks
Present:
Progress updates:
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
Present:
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.
Present:
Progress updates:
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.
Present:
Progress updates:
MBF will revise the Community Involvement and Project Management to be consistent with this discussion.
CW: Propose moving meeting time +1, or -1 hour.
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.
Thursday, April 22, 2021 at 18:00:00
Present:
Progress updates.
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.
Thursday, May 6, 2021 at 18:00:00 UTC
Present:
Progress updates.
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
Discuss #96
Thursday, May 20, 2021 at 18:00:00 UTC
Short meeting this time so just a few brief updates (added by Joel hence the different formatting):
Thursday, June 3, 2021 at 18:00:00 UTC
Present:
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
Thursday, June 17, 2021 at 18:00:00 UTC
chapters/02-filesystem.Rmd
led by KHchapters/03-package-setup.Rmd
led by CWPresent:
Progress 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.
Thursday, July 01, 2021 at 18:00:00 UTC
Review:
Present:
Progress Updates
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
Thursday, July 29, 2021 at 18:00:00 UTC
code correctness:
build management:
Discuss #111:
Other business:
Thursday, Aug 12, 2021 at 18:00:00 UTC
Review:
chapters/09-package-website.Rmd
chapters/11-version-control-workflow.Rmd
For package website:
For workflow with Github:
For the timeline:
Thursday, Aug 26, 2021 at 18:00:00 UTC
Review:
chapters/08-documentation.Rmd
chapters/10-community-involvement.Rmd
Thursday, Sept 9, 2021 at 18:00:00 UTC
Review:
chapters/12-package-release.Rmd
chapters/13-team-package-dev.Rmd
Planning for next steps:
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
Thursday, Sept 23, 2021 at 18:00:00 UTC
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:
write instructions for instructors
Present: Kate, Luke, Ian, Maddy
Thursday, Oct 07, 2021 at 18:00:00 UTC
zipfs
files will be created in a temporary directoryusethis
function, but say that other sections will be discussed laterplot_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)Action items:
Present: Luke, Kate, Charlotte, Madeleine
Updates:
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).