Topic | Updates/Notes |
|---|
Member Match Update - Jessica | → Send out Airtable form/log in to team , moved into section, mix → Plan to send our community wide reminder Monday/Tuesday (5/1 or 5/2) Apps close May 6, 2023, will extend to May 19 Will make matches at next monthly (May 26)
|
Team Updates | Patrick has been promoted and has stepped back resigned from his role in UAC, still help with matches? Bailey left OU on April 24. Her new email is: bailey.hoffner@okstate.edu. Feel free to reach out! Mary has taken the planning and note-taking reigns. Regina is here to help finish out the year, thank you!
|
Finishing out the term Member Engagement Sub-Team Calendar 2022-2023 | Make next year’s matches during May monthly Mary sends out another discussion q next week Team retrospective (not submitted, just for our use) One more board report (probably)
|
- Draft Member Match Thank You + Final “Survey” Text Box
Last month, we decided to not create a full survey and instead offer a text box (or something similar) for participants to add any feedback. Sent in conjunction with the ending thank you email. [Link] to last year’s final thank you email? - Jessica?
Final “survey” draft → Bailey will make this super simple form in Airtable and share
| → Mary will draft final thank you email and survey feedback form |
- Listserv Discussions in lieu of Final Quarterly Event Report - Mary
| |
Discussion | Regina: Usually at end of term, team itself conducts retrospective (review work plan, what worked/didn’t, set priorities for next term) → not due until end of June to larger UAC Suzanne will reach out to Sarah P. to see if she will return for next term Regina will have a small role on the team, attending monthlies and providing support Code of Conduct response: Shows that code of conduct does work, when written wanted it to be actionable Learned things, had just enough people Just needed a majority consensus across the member engagement sub-team and ASpace leaders Mary: how early in process to bring in the team? can the team decide if it is a violation before making decisions? How do decide if it is a code of conduct violation? But do not want to be the people who decide what is harm or is not? Suggestions for what to do in code of conduct How do you balance responding to feedback like that with urgency? How urgent does response need to be? Case where we should have had a meeting and taken time, but do not want to be reactionary Discuss: Speed in terms of response time Going forward, reach out to complainants to ask what they want us to do, what want to come out of this Example: if there is no immediate harm, we can take two weeks? to respond, add this to the code
Add discussion of code of conduct to next year’s onboarding so team feels prepared for this responsibility Add checkbox of reviewing code of conduct to yearly workplan, ongoing
Most sub-teams take a break in July and come back after SAA Probably be another board report in July Get going with the group in August
|
| - Jessica: Send out community-wide reminder to apply to the member match program May 1 or 2, will announce extended deadline to May 19 then
- Mary: Send out one more discussion question to listserv before next monthly
- Mary: Draft final thank you email and survey form thing for feedback, review at next meeting
- Mary: Begin team retrospective based on last year’s: https://archivesspace.atlassian.net/l/c/PyLSsAXM
- Suzanne: reach out to Sarah P. to see if she will return to Member Engagement next year
- Mary: Begin to draft next year’s work plan, including code of conduct review session in fall and regular discussion through the year → last year’s plan: https://archivesspace.atlassian.net/l/cp/aYewhTJh
|