Overall task tracking and roadmap

[lwjohnst86]

Who does what

Reviewer roles: @AlisaDK

Session	Person
preamble/syllabus.qmd	@lwjohnst86
sessions/introduction.qmd	@lwjohnst86
sessions/server-basics.qmd	@nunonog
sessions/databases.qmd	@K-Beicher
sessions/prototyping.qmd	@omarsilverman @nunonog
sessions/optimizing.qmd	@lwjohnst86 @omarsilverman
sessions/troubleshooting.qmd
sessions/what-next.qmd	@lwjohnst86
appendix/project.qmd	@lwjohnst86

General roadmap with estimated timeline

This timeline is assuming maybe 2-3 days of work a month, potentially less.

Month	Milestones
Oct-Nov 2024	Announcement/advertising course to colleagues and groups?

Contributing tips

• Read more detail on the Contributing Guidelines page.

• In general, create a pull request for each milestone (e.g. after finishing your learning objective, submit a Pull Request). Fewer changes made per Pull Request (a "small PR") are easier to review, approve, and merge, so in general make fewer changes for every PR.

• If using RStudio, use the usethis::pr_* helper workflow. See the instructions on the usethis package website. The functions to use would be:

  # Make sure to have a GitHub Token created:
  # usethis::create_github_token()
  
  # Add the token so R knows about it
  gitcreds::gitcreds_set()
  
  # Create a new branch
  pr_init("name-of-new-branch")
  
  # Make and commit changes
  
  # Push your changes to GitHub and make a Pull Request
  pr_push()
  
  # Fill in the details of the Pull Request page that opened up
  
  # Stop work on your local branch by moving back to the main branch
  pr_pause()
  
  # After your PR has been merged, run these two commands
  pr_resume() 
  # Select your branch that was just merged
  pr_finish()