...
\
...
\uD83D\uDDE3 Discussion topics
Item | Notes |
---|---|
Objective/Audience for the session |
|
| do survey about interest and topics, then call out for the planning committee, meet 3 times, put your name here. Local logistics team is already formed. Start a page where we can put in a google form https://docs.google.com/forms/d/14Za-Ug4m-STVwYvMcdav6ADGjPKENHdowaTjL234MxI/edit |
Inclusion actions | There is no cost for the conference and perhaps less travel costs, reaching new audiences and we have many community and potential community members in the Midwest. No decisions are being made here. We may be able to record presentation. IU Indianapolis inclusion statements and safe area guidance? Trying to be as inclusive as possible while recognizing that some wouldn’t be able to travel to this location. |
Funding for catering and support to keep costs | Sponsors hard. IU and PALNI can cover some meal and catering costs. Can other organizations pick up any costs or at least fund their people to attend? Dinner are on their own Sponsors - Amazon, tech services providers that we are all users of, |
✅ Action items
- Jill Morris to write up ask (Draft by end of 06/14)
- david.schober to reach out to Veronica about program committee
06-11-2024
...
Half first day, Full Day second
...
Some un-conference time.
...
First day, broad demo/ share-fair and an un-conference activity.
first day
...
structured
...
second day
dev break outs
community road maps
user-feedback sessions
plenary/ report out
Provide feedback to the board / Some loose way/ learn more about the Samvera Community/ How can I contribute
IDEAS:
Create a PR for docs / or Open and Issue / session
What do you wish you knew session
Make it very interactive
COMMITTEE STRUCTURE:
Small, light team
Amanda (Hyku), Jon (Liaison),
The committee is not responsible for registration or logistics/ just a program committee.
GOALS of the Meeting
Outreach to potential new adopters
Move away from a report out structure and move toward actively doing something together
Bring together a group of practioneers to further develop the community
Second Meeting Notes 5/2/2024
Meeting notes (AI created)
Samvera Midwest planning meeting - May 02
VIEW RECORDING: https://fathom.video/share/5CzYaJzJ_7jYSyzaHszsd9_mpyuqhLwB
Meeting Purpose:
Discuss planning for a Samvera regional meeting in Indianapolis in September 2024
...
Create a topic/interest survey for potential attendees
Ask for planning committee volunteers in the survey
Review survey draft and finalize before next week's virtual connect
Share survey and do some planning updates at virtual connect
Form a program committee to start planning details
Action ItemsReview Google Form survey responses and compile list of potential programming topics
Create Google Form survey with draft topics
Reach out to local AWS representative to inquire about potential sponsorship
Edit and review Google Form survey based on call discussion
First Meeting Notes
Samvera Regional Meeting - Midwest - April 05
Meeting Purpose:
Discuss hosting a Samvera regional meeting in the Midwest to replace the national Samvera Connect conference this year. Determine location, timing, themes, and audience.
Key Takeaways:
The meeting will likely be held in Indianapolis on September 25-26.
Accessibility will be a major theme, focused on user experience/management rather than just software development.
Attendance goal is around 50 people.
50, 40, 30 person room and maybe auditorium at IU Indianapolis hosting.
IU Bloomington contributing catering up to $3000. PALNI will contribute additional catering needed. PALCI might be able to as way to keep from charging conference costs.
Topics:
Regional Meeting Purpose
Opportunity to engage a broader audience than the national Connect conference
Can incorporate developer-focused sessions but also focus on users and adoption
Important to make it useful for attendees and structure it so they don't feel overwhelmed
Location & Timing
Late September/October best time period to avoid conflicts
Midwest location makes sense regionally; Indiana is central though some have concerns
Indianapolis recommended as convenient with more amenities than other Indiana options
Dates flexible depending on venue availability
Themes & Audience
Accessibility a key focus - both software and content management
Developer-focused sessions could be included as a track
Outreach to potential new adopters is another opportunity
Logistics
1.5-2 days recommended for those traveling
50 attendees max so smaller spaces needed, not a large plenary room
Budget ~$10K for catering, AV, etc. but facility may be free
Next Steps:
Confirm Indianapolis venue and dates
Refine program based on themes and audience
Promote meeting to potential attendees
...