Meetings - PHDSAG Workshop Planning - Feb 21, 2024

[ran-codes]

Date: 2024-02-21 (14:14)
Parent: [[Meetings - Obsidian page]]
Status:
Attendants:
Tags: #meetings
Links:

---

Distilled Notes

---

Agenda/Fleeting Notes

Planning the Ana-lu and Diana (Top down)

• Diana and Ana-Lucia to give workshop on MM/DD/YYYY
• Identify what day the work shop will be
  • second week of spring quarter
  • time: usually 3-4 or 4-5
  • date:
    • april 8th is eclipse . no good
    • sometime that week
    • (Lisa and Hal will confirm and send details
  • 6ish week in the future
• Identify the learning goals of this workshop
  • Basic GitHub
    • cloning
    • making changes
    • Commiting
    • pulling
    • pushing
• Where should our code/repository sit
  • who ever is teaching
• Identify the format of the 1 hour workshop
  • Before workshop: (Lisa and Hal)
    • set final date and time
    • Prepare the audience
      • Communicating the workshop aims and goals:
        • we need to be u-front and say this is a hands on workshop and here are hte pre-reqs and be ready to work.
      • exclitly tell taht what software to isntall ebfore them for pre-requitemnt
        • sign up for github
        • intall git
        • install GItHUb desktop
        • Rstudio
    • Scheudle a dry run before the actual work (just us lisa, hal, ana-lua, diana, ran … and a outsider for feedback - Mark, Paula)
  • 5 minutes Intro (Lisa Hal)
  • (50 min) Practical (Ana-lucia and Diana) introducing basics of GItHub
    • follow a long an build your own repository teach basic github
      • Ana-lu and Dian will figure this out
    • collaborative simple thing (similar to R ladies)
      • We set up a repo before hand
      • during workshop walk through for everyone to themselves
        • cloning the repo
        • running some code on the repo (prints())
        • make small change to code
        • commit
        • pushing to repo
        • we review the final product after everyone amde change
  • Outro
  • Post workshop
    • Survey after the course (Lisa will adapt a form that we can send out after)

Notes on workshop

• workshop format (helping)
  • maybe we think of structure in the start pair people up.
  • identify TA’s (Lisa, Hal, Mark, Ran)
  • seat people around the TA… so that they can help

---

Moving forward brainstorm (after workshop 2)

• future plan
  • Lisa
    • second week of spring
    • shouldn’t squeeze two in spring
    • look at evaluations
    • spend time planning for fall,winter
    • put this on CV
  • Hal
    • depends how much we get done next session
    • maybe early may/june
    • 1 hour
    • this is practical weorkshop is new
    • PHDSAG skills building wokrshop is a new thing
    • twice quarter at most
  • Ana-lucia
    • looking at evaluations,
  • Diana
    • count me in for TA or instructor
  • Ran
    • leaning towards another followup in may/june building on basics and focusing on best pratices and collaroative workflows (maybe Lisa/Hal)
    • a yearly cycle
    • once we get to a critical skill mass we can start doing really cool things
    • long term delvierable amitnainedby PHDSAG (eg. https://nccs.urban.org/nccs/)
• next steps
  • focus on Diana and Ana-lu workshop
  • touch base after or before to discuss the future plan
    • revist collaboration plan next time
  • Staff to come to workshop
    • nice to build connectiosn ebtweens tudents and staff

Future ideas

• other session of PHDSAG
  • did resumes
  • career development
  • we can build a online prodcut hta tbuilds on previous
• Future sessions
  • a preview of potential ‘best practice’ workflo
    • Workflow best practices (how best to use GitHub)
      • self work and collaborative work (e.g. PR)
      • when do you work on the same repo/project or when should we open a new one? how to split work
    • Particular Uses case examples
      • how to set up a code review
  • Advanced actions
    • PR
• PHDSAG GitHub org?