2023-01-11 Meeting notes

Jenn Colt is next, followed by Florian Gleixner 

All

Reminder:  27th January is the Deadline for acceptance of new modules by Technical Council

All

Went through the subgroup list quickly, no many updates:

• Discussion session on 23rd for goals doc
• Localization - no updates, things happening in PC though
• AWS - group will be on going
• Breaking changes- working
• TCR - working
• Charter - Doodle poll coming
• Central configuration - setting module discussions on going
• Architecture - on hold

New RFC to review from Olamide

• https://github.com/folio-org/rfcs/pull/4

Radhakrishnan Gopalakrishnan suggested that the first step would be for TC members to start commenting on the RFC Craig McNally will remind folks to start giving feedback

Today:

•  How to move on to the second stage - could resolve existing questions and resurface them in the next stage
• Moving on allows opening up the audience, impact on upgrades could be significant
• Marc will resolve his comments if needed. Olamide can decide what should be in the RFC and what should be out of scope. Olamide will look at most recent questions, document responses and then resolve.

Craig McNally 

• tri-council meeting:  12 Jan 2023 9:30 AM ET (Product Council is at https://zoom.us/j/867230970 (and then Tri-Council Meeting apparently also))
  • Quick update from each council -  TODO:  need a 3 minute summary of what we've been working on since WOLFcon
  • Topic:  "What is FOLIO?"
    • Try to reach agreement on terminology... Simeon and Kristin to provide strawman definitions
      • the FOLIO "platform" vs "product"
      • what is an "app"
      • etc.
    • Update on where various related efforts stand...
      • platform minimal
      • Julie Bickle's group/FOLIO builds
      • etc.
• Folio chairs meeting:  10 Jan 2023 
  • recurring every 2nd Tuesday of each month
• TC dedicated discussion:  09 Jan 2023 11:00 AM ET
  • Topic:  Tools/Dependencies Versions continued

Craig McNally /All

From Craig McNally in #tech-council:

This was brought to my attention earlier today...
https://blog.nlnetlabs.nl/open-source-software-vs-the-cyber-resilience-act/
While it's still just a proposal, I think FOLIO should keep an eye on, and maybe even try to get ahead of in anticipation of this.  I will add it to the agenda for next week's meeting.  This is a short read that does a decent job of laying it all out.  Please take a look prior to next Wednesday.  Thanks! 

• Have folks had a chance to read through any of this?
• What, if anything do we think the TC should do about this?
  • Raise awareness among other councils?
  • Seek legal advice in anticipation of this being passed?
  • Is there anything else we want to do to be more prepared for this in the event it does get passed?

Today: Deferred

All / Ian Walls 

From last week:

• Ease of installing/deploying FOLIO - Ian Walls , Marc Johnson , Jeremy Huff
  •  Primary task the Tc would take on by making FOLIO easier to get up and running. Would also reduce AWS costs so that the money coming from Membership groups can be flowed to other aspects of FOLIO. Tc is the best equipped group to decide on how to make installing and deploying Folio easier and cheaper.
  • Craig McNally - Brainstorming open ended session with Ian Walls and then discuss further before or after WOLFcon depending on the brainstorming session. Ian Walls and Tod Olson to frame the topics of discussion for the brainstorming. 

Today:

• Probably defer, but keep on the agenda so we don't lose track of this...

All / Ian Walls 

Slack discussion:  Revisiting FOLIO Governance 

• • Ian Walls - should be best discussed in cross council meeting possibly at WOLFcon. Idea to was bring this up at a high community level not necessarily the Pc or TC. Doesn't need to be on TC agenda next week. Aspects to be discussed at WOLFcon.
  • See also:  messages to PC and CC council channels