Page Comparison

Should we change the governance model to slightly reduce the size of CC (from 15 to 13, and corresponding quorum chance) given limited interest in elections and departures? See FOLIO Governance Model#Charter

• Decision: 13 members and quorum of 7 - align with PC and TC: Action item for Simeon Warner : write up the change and let it discuss and ratify with other councils
• The CC is worried to find enough new members to fill in the vacant seats in the next election period - Tom is proposing to find a solution here
• Paula will leave definitley, Dracine has/ will leave as well
• Balance the need for experienced, qualified  members and people "sitting forever" in their positions
• Action item: Tricouncil Meeting in afternoon

What do CC members expect from next years work and what do they want to bring in? Can we collect the most important topics and go forward with them?

• Make the community developer advocate happen!  
  • Add a certain timeline to decision making - have a defined decision framework → how to get there?
• Meaningful meetings
• Health check: follow up of action items and end every initiative properly with an decision or a task - follow up on them and make things happen 
• Missed topics: like MOU for contributions:   CC needs to come to an agreement about this topic first → action item: summarize the need and put it on CC's agenda
• productive governance structure
  • activating the members  - how?
• Result: Give the council a strategic agenda for their election period and follow this up
  • do a retrospective before starting freshly
  • check after 6 month
  • Have a backlog and maintain it
  • Asking people to report to CC where appropriate: like the future developer advocate
  • Have a "carry forward" area in the minutes
  • Add the CC calendar to the minutes
• What helps the developing parties (vendors) 
  • K-Int: why do we have the scratch environments → how can FOLIO be run in individual environments? Would reduce costs
    • would make development much easier
      • CC would need more background abou this to find a way forward
    • Transparent cost models to maintain an app  - 4 people to maintain an app over time 
      • CC needs to have transparency about those costs and sees ways to support this?
      • MoU for maintenance could be a way the CC would want to engage? Action item; on agenda of a next meeting with additional technical background information
  • EBSCO: 
    • Agrees to the point above
    • Hosting / Developement needs additional documentation for sustainable maintenance and transparent information about changes of scope and resources (e.g. people leaving)  → Action item for CC
    • Develpment is never "done"  - commitment is needed: test coverage, health check, liability, documentation
• How can we start to surface and manage the most importatn issues of the product and the community?
  • Goal for the next year
  • Define this nearer in the Tri-Council Meeting and take away action items
    • break it down in doeable chunks
    • Architectual evolution: Define and realize a process to solve the defined issues as a CC task (together with others) 
  • How can we make the community early and effective aware of known issues?
    • Find a critical mass
    • Identify systemic issues earlier
    • Roadmap analysis is key on a regular base 
    • PC had a prio group  with a concept: Demo to PC with invitation to CC (May, 19 2023), Wiki page:  FOLIO Prioritization and Roadmap Working Group, WolfCON 2023 session:

      Widget Connector
      url https://docs.google.com/presentation/d/10sAf0ujJB-1kHBoZETIRnTWUgMDoDeFF419VzCWnncM/edit#slide=id.g239eff78b51_0_31

    • Transparency as a key word
      • What will come out of it?
      • How many resources are at the project?
      • Who understands the full scope?
        • Integrate the Release Stakeholder for updates
        • Integrate the main developing partners with updates
      • Right now, these information is already somewhere, but it is often not accessible to the councils and mainly not to the CC (on managment level)
      • Community process should contain not only the gathering of ideas but more: Reason, POC, Community Approval → means: write a proper document → tie it to domains and add swim lanes for features → work for SIG's?
        • → give intitiatives to the responsible SIGs and Councils for transparency (not for decision)
        • Even if everything is in Jira: update to the community on behalf of the Jiras
      • Action item for CC: Community communitcation norms  - subgroup?
        • Subgroup: Tom (Kickoff), Ian Christopher , member PC + TC
      • Result: idea about changing the ask on SIG's!  Information and discussion in the SIGs and a transport of summaries to upper levels

Tom Cramer 

No meeting next Monday 8/28...?