2023-09-12 Meeting notes

60 min

Review of issues: brainstorming ideas to move forward

Supporting documentation:

• SIG Conversation notes 2022

• SIG Presentation 2022 (includes some action items)

• PC Notes from presentation

• SIGs with PC Liaisons

• Easy RetroBoard with ideas

All

Ideas:

• Could we review apps and make sure all are assigned to SIG? Identify gaps?

• Can liaisons identify issues and bring up with PC?

Current status:

• Monthly SIG reports are not accomplishing any particular goal at moment.

• "We talked about this," but generally not concrete

• Not really early surfacing of problems/issues

Scope: What should our subgroup consider?

STG: Restructure the SIG Report

• Template for SIG report:

  • UXProds developed

  • Issues discussed

  • Problems

  • Tie-In with Roadmap?

  • Do you want to come to PC to talk about something?

• Attendance for PC meeting should be limited to discussion items.

• Can each SIG find its place in the roadmap or indicate when features are on the wishlist? New features that aren't represented on the Roadmap may identify gaps in coverage

  • Example: searching items and being able to select items that fall within the search scope, only in draft, not on the roadmap

• Make sure that SIGs are capturing desired functionality in features

STG: Make sure SIGs understand the role of the PC: we don't assign developers, we are influencers, coordinators - core platform team is the only "contributed resource" team: organization has an MOU where they've committed a particular person's time to work on the project. Other teams are more "self-directed," or directed by particular portions of the project that use specific priorities (organizations, vendors, etc.)

STG: flesh out the role of the liaison to help make sure liaisons understand responsibilities. What types of discussions should happen within the SIG

STG: track the requests that come in, clarify the action items, and track statuses. What tools could we use?

LTG: Review SIGs for support/structure

• What's the scope of SIGs? App-based? Functional?

• Should all develop teams be associated with a SIG for community input?

  • e.g., Entity Management: work being done in community vs. work being done to support LC Needs

  • e.g., Lists Apps: should reporting weigh in on develop or is this being developed as part of client requirements and be donated to FOLIO?

    • Would be good to find a home for Lists within a SIG

    • would be the place for how the Lists App overlaps with LDP App