2022-02-14 Meeting notes

We have had limited activity on the membership letter. Who would like to contribute to that? The goal is to wrap and send by the end of February.

• Discussion 
• Volunteers to work on finalizing the letter: Harry, Tom, Mike,  Kirstin, Rachel during the week 

We are now engaged with a team from EBSCO who will do the actual work of updating the site. We will need website copy to be created. Who would like to contribute to that?

• Mike gives an update about progress. Any other volunteers to join the team?  Boaz

Coming out of our Retrospective we identified the following action items:

• Develop an articulated framework for maintenance 
• Craft the membership drive this year around our actual needs (i.e. specific roles, costs, etc.)
• Review and redesign the MoUs to be more reflective of our current needs
• Define which costs should be “FOLIO” costs and which things should we strategically define as contributed - a theory of resourcing and how it is applied.
• Should we consider hiring someone professional to raise funding?
• Can we define more roles defined within the CC rather than everything being volunteer-based or delegated to subgroups.
• Review the FOLIO Manager definition (single person vs group)

 Which of these do we want to explore more deeply in this meeting?

• Point 1, 2, 4 is critical
• What about donated resources? What model are we aiming for?
• long ago, there were conversations about a central team. It would take 7 FTE, $1.2M per year to fund just baseline maintenance
  • this seemed unobtainable then; it was dropped
  • this seems like an underestimate now
• there have been recent discussions – a Scope Criteria WG (out of CC, PC and Tech Council) – that has talked about slimmed down "core" that would make maintenance easier
• Open questions (Tom's List)
  • what is our theory of resourcing for development
  • what is our theory of resourcing for maintenance
  • what do we want from project partners?
    • libraries
    • commercial
  • how do product teams fit in
  • how do we onboard new contributors
  • what kind of resourcing do we want?
    • in kind?
    • financial?
  • how do we balance innovation vs. maintenance? who does each?
• Proposal: let's have a focused effort to unpack these issues and understand them
  • once we have common frame of reference, we can think work on proposing solutions and short- and long-term strategies
• Looking at the teams–these are new features, right? when will they be done? Never
  • how much maintenance is needed? this is invisible right now. 
• We have (at least) two different models
  • ERM team is dedicated to a module
  • Vega team (e.g.) is doing new innovation / features
• We are good at coming up with needs; we are less good at having a common resourcing strategy. We can identify $5M worth of needs; if we had $5M in resourcing, how would we spend it? 
• What should we do next? 
  • have a high level vision then work to get there?  (right to left reengineering)
  • or start with where we are now, and how can we improve that?  (left to right reengineering)
  • It would be helpful to start focusing on tangible aspects of where we are now–it's foundational
  • the Scope criteria working group is doing a lot of overlapping work right now. Start with a preso from them? 
    • though note that group's work needs to be validated against the wider context will be important 
• the contribution chart shows very heavy investment from EBSCO
  • do we want more contribution from others? 
• next step: let's align scope criteria working group objectives to this group