2023-02-22 Meeting notes

1 min

Scribe

All

@Tod Olson  is next, followed by @Ankita Sen 

1 min

TCR Board Review

All

5 min

CC / PC Updates

@Maccabee Levine / @Tod Olson 

Any updates from the PC and/or CC?

• CC: There was no meeting this week.

• PC: There was no meeting last week.

Project Finances

• @Craig McNally reached out to @Mike Gorrell asking for more information about how funding decisions are made
  
  

  • The impetus for this was the decision to stop funding the community developer

• @Mike Gorrell will join the TC meeting on Mar 1, 2023 to discuss with us.

10 min

Technical Council Sub Groups Updates

All

Technical Goals/Objectives: @Craig McNally will add to agenda for today, TC will either vote up/down today, or will take a week to review and vote next meeting.

Charter Revisions: topic with TC next week, group nearly ready to wind down.

DR Process Improvements: deadline to review is up today. No objections have come up. Migrated DRs are accepted by default and group can close down.

15-20 min

RFCs

All

• @Olamide Kolawole to walk us through the draft RFC:  https://github.com/folio-org/rfcs/pull/6

• Advance this to the "Public Review" stage in the RFC process?

Updates:

• Name change to Tenant Collection Kafka Topics, signal moving away form current per-tenant topics to topics for collections of tenants

• Outcome would allow Kafka admin to continue the current style of per-tenant topics (by having collections of single tenants), or to consolidating multiple tenants into collections.

Conversation:

• Goal is to advance RFC to public review process

• Concern about tenant separation being out of scope.

  • Goal of RFC was to reduce the partition count and therefore reduce costs

  • Tenant separation seems to be another large issue and too much scope for this RFC

  • Original per-tenant Kafka messages at least allowed us to keep

  • Temporary Kafka security solution would be rendered obsolete/deprecated by this RFC (though it seems unlikely this will be done any time soon)

    • Does the ALL  tenant topic would close the door to the possibility of separating tenant messages?

    • RFC describes an option to combine tenant message, not a requirement

    • Major trade-off is that we are committing in the long term to support two fundamentally different approaches for the foreseeable future, but does keep the door open

  • RFC is intended to be practical was of addressing pain points, which includes limited development and funding; hurdle is very high to implement enhanced security

• Other notes?

• Inference: providers do not migrate all tenants to new flower releases all at once, and therefore need multiple versions of a module are active at once. This gives a scenario where multiple versions of Inventory will be consuming a message.

• Response was cut off due to end of meeting

• To continue in dedicated discussion on Monday

Outcomes:

• Continue discussion on Monday during dedicated discussion time, 11AM Eastern

5-10 min

DR-000032 - Splitting Database Read/Write Traffics in RMB

All

• Decision has been marked as Approved, etc.

• Communication has not yet gone out yet

  • Plan is to post messages to #development and #spring-force slack channels 

  • Briefly discuss what the message should be...  

5 min

WOLFcon Volunteers

All

From slack:

Mike Gorrell 
Hello. Another WOLFcon is being planned (tentatively August 22-24 in Chicago), and we want the FOLIO community to be ready. In order to achieve this we need Volunteers to help plan WOLFcon. Please consider chipping in and join the #folio-wolfcon-planning-group

Notes:

1 min

Charter Revisions

@Craig McNally 

• Revisions have been sent to the CC.  @Jenn Colt will join the CC meeting on Feb 27, 2023 to discuss with them

1 min

Upcoming meetings

@Craig McNally 

• TC dedicated discussion:  Feb 27, 2023 11:00 AM ET

  • Nothing planned - Cancel this week's dedicated discussion?

*

Decision Log Review

@Craig McNally /All

Moved to discussion for next week.

• Take a look at the decision log, migrated decisions

  • Are any adjustments required? 

  • Do any of these require additional discussion?

• Next steps?  

  • Communication about the consolidated decision log?  Where?  When?  Who will do this?

20 min

WOLFcon Hot Topics

All

An overview was provided of the "hot topics" at WOLFcon.  It seems clear that the TC ought to be involved in these discussions/efforts;  what is the best way to participate?

• Platform minimal

• Applications/bounded contexts & application management

• Blue/green deployments

• Kafka/messaging improvements

• FOLIO governance

• API technical debt

• ???

Notes: Deferred

Cyber Resilience Act

@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

Ease of Installing FOLIO

All / @Ian Walls 

From last week:

• Ease of installing/deploying FOLIO - @Ian Walls @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...

Revisiting FOLIO Governance

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