...
Technical debt - software maintenance subsection - out of conversations over last 6-12 months. trey and Ben put together a group called Component Maintenance WG. Try to understand the core components of the samvera products and how to idenifty POs for those core components. Would address issues with those POs.
Question of different resourcing - this group will help figure out how we do that. SVT will not be benevolent dictator.
Could this group be the one that captures and coalesces those issues.. Some cases where features get lost or dropped. Not infrequent - to contribute your feature back to community is intimidating, may take resources locally. Work with local institutions and see if they can hand it back. Or work together to pull their feature back.
Where do we need help now?
Lynette - Collections is wrapping up
Analytics core - working now
Valkyrie - 2 cycles and is working on getting a 3rd cycle later in the year
Group and repsonsibility - LaRita is on that.
Tom Johnson - working on bulk stuff.
This leaves
Accessibility. UX IG may want to take the lead.
David: Has anyone asked about Accessibility is critical for next phase?
SVT: some have identified this as an issue. PSU and DCE. Good way to identify an issueor lead on coordinating work. Getting resources together - will be a challenge - if you make the approach a "if you want a thing, you need to make it happen" - ask people to do work who can't - that resourcing approach means that people think they're being rejected. Or few groups who actually participate and all work is on them.
David: just knowing if an adoption plan hinges on a feature being adopted to adopt platform -
SVT: easier to do that locally but doesn't bridge back to community
David: batch edit and bulk import export