2021-10-07 Product Council Meeting notes

Kristin Martin

 Kristin Martin

Kristin, Anya, Owen, and Brooks create the draft document.

Rather than using Trello—and adding another tool for everyone to track—use the capabilities of Confluence to set agendas and track decisions.  At the end of each PC, use some time for people to suggest new topics.  An agenda-setting meeting will take the place of what PC Exec used to do; it will be an open meeting where the agenda is set but the topics themselves are not discussed.

PC observed the struggles that TC had with recent decisions, including confusion about voting on Slack (are abstentions possible, how long should a vote be open).

During the meeting, there was a discussion of how Voting/Decisions are made at PC, and that discussion is reflected in the "Roles and Norms" document.  How do "lazy consensus" and voting interact?  Can only elected members of the Product Council call for a vote on an otherwise lazy consensus decision?  Should proxy votes be allowed?

•  Kristin Martin will clean up the Google doc and post it for review at the next PC meeting.

It is an open question about how to establish representation with the other two councils and with the SIGs.  Next step, create a table on the wiki to identify where overlaps and gaps exist now.

Another future action item is to look at the reports that PC asks SIGs to make to ensure this is effective for both the SIGs and PC.

Kristin Martin / Jesse Koennecke

SysOps SIG is looking where there are issues with integrations that affect an institution's ability to adopt FOLIO and review this with the Implementors group; this feeds into the SWOT analysis, for instance.  Could there be a survey that collects this information?  Working through the Implementors group can try to catch sites that have implemented FOLIO but don't necessarily come to FOLIO meetings.

Implement a documentation framework to be reviewed after the Documentation Working Group meeting.

Provide sufficient documentation for implementers to set up and configure functional apps feeds into the desire to have a survey; will work with the implementer's group.

Develop a support process within the community for FOLIO adopters is something the Support SIG is working on.

Clearly document library requirements for performance is something that can be reviewed by Product Owners.

• Owen Stephensto research where the performance documentation is going and how it is being use.
  

Measure implementers satisfaction is related to Develop an Implementers SWOT Analysis.

Define and document FOLIO's scope of functionality is in discussion.

• Sharon Wiles-Youngand Anya to work with Implementers group to develop SWOT Analysis
  

Revise the current ranking, prioritization, and staffing process has been talked about in the Capacity Planning group, including doing away with the current ranking structure.  The people working on this should be aware of the next item: Ensure the roadmap includes longer term, architectural, and resource requirement considerations. We also want to look at how other open source projects gather requirements needs from a project's users.