...
| Time | Item | Who | Notes |
|---|---|---|---|
| Start | Why are we having this IG? | SVT | |
| Intros - Your name, university, role - Samvera involvment in one sentence | RJS | ||
| Current Status of the Roadmap | SVT | ||
| Areas where we need help (ex: bulk stuff, valkyrie, analytics round 2, accessibility) | SVT | ||
| Towards the End | Meeting Times and Interest Group Guidelines | RJS | Samvera IG/WG FrameworkInterest Group/Working Group Framework#InterestGroups |
Action items
- @
NOTES
Clear to a lot of people that it's a lot of work to tech lead and product own a roadmap as everyone's local needs hit up against community needs. Steve is 20% PO and Mike is 20% as technical lead. A good opportunity to call on the community to bolster this work. We can do a better job of PO'ing and TL'ing in a way that makes sense.
...
STEVE: A lot of things to do next -
SLACK Group - Jess fire up a Slack group
Ryan schedule next meeting
Action Items:
- Collect all documents for the roadmap in one location (Steve)
- Good idea to include a section of the roadmap to identify what hyrax is NOT going to be - scope, what are we trying to get to (Group)
- What is the process for identifying work and proposing ideas? (Group)
- How does one gather resources for the work? (Group)
- Build a hyrax page for all the things on the roadmap (Steve)
- Subgroup for grooming labelling PRing etc. (Chris organize?)
- Lists of devs who are skilled in particular areas (related to Core Components WG stuff) - is core components working on building this? (Steve contact Ben Armintor)
- Review list of Hyrax code reviewers on GH… (maybe Chris and Lynette?)
- Hang on after samvera tech call for review and issue triage (Steve organize)