Content Comparison

WOLFCon Debrief: action item - revitalize SIG relationships and understanding

• Who are the SIGs?
  • Spreadsheet of SIGs: https://docs.google.com/spreadsheets/d/1hr7Vx-swyCGfQ3571AK8nYx2MMWb1VFoaqrCYOPE8mM/edit#gid=0
• Who is SIG liaison?
• Creation question template for conversation with SIGs
  • Desired areas of develop
  • Successes/failures
  • resources - POs and development teams
• Assign PC members to have conversations with SIGs and bring back to PC

Revitalizing the SIGs has been on a wish-list for an agenda item for a while, and it came up as a topic of discussion at WOLFcon. Is there a way we could be sharing information better about what the SIGs are doing?  Which ones are active? Which ones need a product owner? (Do we have Product Council liaisons for each of them?) Some SIGs are more active at a sub-group level.

Noting the wiki is not up-to-date everywhere...noting especially about sub-group levels.

Lots of changes and additions to the "Spreadsheet of SIGs" (see link to the left)

PRIV might be a good group to include in a discussion about scope criteria for development.

Public Library SIG: might it be time to try reviving this group and see if it can gather funding for specific development needs that they have?

SysOps SIG is getting a little more traction with issues that were identified years ago (e.g., minimal platform installation) but are now more urgent with more FOLIO installations. Can these needs get addressed before they cause problems for a bigger community? These tend to be cross-cutting and architectural questions.

WOLFCon Debrief: coordination with other councils

• Council roles and understanding
• Shared understanding of definitions for what we are working on
• PC authority and influence working through our charter

The chairs of the councils are going to try to set up quarterly cross-council meetings for information sharing and raise issues that straddle councils.

It is probably impossible to manage at a level of functional detail and at the overview/coordination level. So it is important for the PC to decide and what level it wants to operate. This is a good topic for the cross-council discussion. PC should also be more up-front with CC when we have resource struggles. The TC is also thinking about reviewing its charter (not a radical change but examining its responsibilities).

Proposal in 2 parts: 1) practical steps to return to what this group does (to be reviewed in the group tomorrow and eventually brought to PC); 2) looking at the FOLIO architecture and longer-term plans.

For a future meeting: a process for how we keep the roadmap up-to-date. There was a lot of work to tie the roadmap into current development; how do we best leverage this work?

Discovery/Integration API

• potential need for SIG

Kristin will work on a template of questions to ask SIGs (in the same spreadsheet).

We can return to the debrief in the next meeting as well.