USER Meeting Summaries

[smklibrarian]

Here you will find a thread of meeting summaries from the internal project team. We meet each week to track project progress, synthesize and share findings, discuss community engagement, and make plans. If you follow this discussion, you will stay updated on project progress, successes + challenges, conversations, and have an opportunity to ask questions/comment.

We remove any personally identifiable information.

[smklibrarian]

Oct 26 Meeting Summary

• Action: Start labeling projects with keywords in the Projects and People List.
• Action: Email CS&S about potential listservs, etc. for outreach
• Action: Generate initial outreach list by EOD Friday. Add ‘Send Research Survey’ action next to names/projects we want to send to in the Projects and People List
• We will meet Friday to synthesize conversations so far and converge on questions + themes to ground next phases, with goal of defining + dividing up key tasks.
  --> Action: Come prepared to brain dump and co-synthesize readings/conversations, etc had so far.
• Coworking Friday to draft survey questions.
• Draft survey outreach language once we draft some questions.
• Goal: Send out survey Nov 2.
• Project team to join the OSD design call Nov 2.
  --> Action: Make list of goals + questions for OSD call
• Action: Add questions for in-the-moment convos at All Things Open
• Action: Set bot reminder for Friday Slack progress standup

[smklibrarian]

Nov 16 Meeting Summary

• We reviewed the People and Projects List and added actions to send research to a few more folks/groups.
  -->ACTION: Review any others from the list of folks in networks that 1) we should definitely send research survey to, and 2) need a specific follow up?
• We also discussed whether to include ethnographic + qualitative software tools. We all felt ‘yes’ and provided some helpful examples
  ACTION: Also think about including indigenous and non-Western ways of knowing
  ACTION: Think about how to change survey outreach language for different audiences
  ACTION: Get started on interview questions, meet together on Friday for synthesis meeting + coworking on questions.
  ACTION: Draft consent form
  ACTION: Interview protocol
  --> Set up Cal booking links.
  Budget
• We discussed project budget in terms of travel + conferences as well as translation support
• Questions for next week:
  - What translation services would be useful? I.e. sending survey in another language or two; and/or hiring research support to some interviews in another language (broader Q about including global projects)
  - What conferences do we want to attend in addition to FOSDEM? Mix of OS + Academic?

[smklibrarian]

Nov 30 Weekly Summary

Survey

• Further survey outreach, opening up to bigger mailing lists/listservs.
  -->ACTION: Indicate any others we should send in Projects + People Board(
  Interviews:
• Setting up interview booking link and calendar holds.
  ALL: Interview Docs to Review + resolve comments, Slack for further discussion + clarification if needed
  - interview outreach
  - interview questions
  - consent + reimbursement form

Synthesis:

• Set up an interview synthesis board.
  QUESTION for ALL: Should we set up a similar synthesis board for survey?
• Help resolving and addressing synthesis comments as they arise
• Goal to start outreach Friday!
  -- > Start with people we’ve already talked to + survey respondents
  ACTION: send initial round of interview outreach emails.
  ALL: Update - Projects + People board with any folks we talked about interviewing + status of that convo

Etc

• ACTION: start posting to open repo
• Send email to funder re: events, survey link, open repo.
  ALL: Add/review conferences we way want to attend

[smklibrarian]

Dec 7 22 Weekly Summary

Ongoing Tasks:

• Review/updating/adding context to Projects + People Board
• Add/review conferences we way want to attend

Interviews:

• Docs (interview questions, outreach drafts, and consent form) ready to go
• Bulk outreach is paused as we finalize bookings calendar.
• Will focus on 1:1 invites/follow ups this week

OCEAN Designer diary studies update

• At OCEAN wrap up workshop, we might share/workshop some of the ecosystem mapping work

Discussion:

• Possible events: upcoming DC event, FOSS Backstage, and Collegeville 2023
• Translation needs (for budget adjustment)
• Decision around Spanish translation of survey, hold for additional translation needs

Ecosystem Mapping

• Idea around splitting interviews between questions and mapping (~25 interviews with interview guide + ~25 with ecosystem mapping (1:1 but option for focus group)
• Create mapping process

Artifact Sampling/Shadowing

• Develop/adapt a designer shadowing template

Things to include in Open Repo

• Added license
• Need to add more context to the READ ME

[smklibrarian]

Dec 14 2022 Meeting Summary

Ongoing Tasks
- Review/updating/adding context to Projects + People Board as we talk with folks and come across projects
- Add/review conferences we way want to attend

Interviews
- Kicking off this week, pausing next two weeks, running through Jan.
- Created interview tracker status of outreach/scheduling and take interview notes.
- More outreach to some projects today, then more Jan 3
- using self-hosted cal.com instance for bookings

Survey
- Q: ~ 17 responses - should we do another outreach push?
- We are talking with Localization Lab about translating survey into Spanish + maybe Portuguese.
- Q: When does it make sense to start survey synthesis?

Synthesis Discussions
- Templates
- Made debrief template in Miro - the idea is to jot down fresh insights immediately post-interview.
- TO DO: add a section to label ‘final output ideas’
- Discussed synthesis approach and tooling
- Maybe adapt a codebook to tag themes with key quotes from interview transcripts?
- Sprint idea: We discussed booking the Jan 23-Feb 9 as two weeks of synthesis sprint. The goal would be for some of us to dive deep + focus only on Sloan synthesis during our available time, and not work on other projects/take external meetings.
- We also talked about different output ideas, and documenting helpful insights re: outputs as we move along with synthesis. Discussed a process idea where we test evidence we collect with certain project teams, and then produce a case study