2023-01-18 Meeting notes

1 min

Scribe

All

@Florian Gleixner is next followed by @Jeremy Huff 

10-20 min

TCR Board Review

All

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

• https://folio-org.atlassian.net/browse/TCR-9 - 

• https://folio-org.atlassian.net/browse/TCR-21 -
  Discussion between vjay and Marc
  Recommendations for the team (will not fail the review).
  Personal Data Disclosure has to be included in actual version
  x-okapi-teanant header has not to be provided if Auth token is not evaluated. Need changes in TCR Template/Process?
  Outdated dependency found
  OWASP check found one issue
  Overall the module meets all criteria
  Craig and vjay will merge the ticket
  
  

• https://folio-org.atlassian.net/browse/TCR-22 -
  Submitted in a state where the module is not complete. Not sure what the expectation is? Orchid deadline? Would probably formally meet the criteria. Diskussion what we do here:
  Jeremy: We are fine voting no, even if the module passes the evaluation
  Tod: Agree, Team does not want to game the system, wants to get module included in Orchid
  Craig: Hard decision. Tend not to pass. Marc offered to do a "speed review" before deadline.
  Jeremy and Tod: Discuss with the PC?
  Maccabee: TCR Process: module has to be ready to be included before review
  Craig: Team could show, what the module does, if it is ready for inclusion
  Tod: What are the risks accepting the module
  Mark Veksler: Better look at the remaining functionality, that needs to be implemented
  Jeremy: Dont want to set a precedence to let people submit unfinished modules
  Craig: What if we let it pass, and the module will be finished, but for example no tests will be included.
  Florian: Review modules that are extended later should be reviewed as well. A module could be submitted if a consistent subset of functionality is ready.
  Craig: Not sure, if the module works in any way. Should wait for Marc? Yes. Discuss next week again.
  
  
  
  
  

• https://folio-org.atlassian.net/browse/TCR-23 (Draft)  (to be cancelled) - it'll be canceled once the review workflow in Jira is updated

• https://folio-org.atlassian.net/browse/TCR-24 -
  Meeting tomorrow. Deadline for inclusion is 27. Jan.

10-15 min

Technical Council Sub Groups Updates

All

Went through the subgroup list quickly, no many updates:

Breaking Changes: Meeting yesterday. Updates for Definitions in RFC. PR is in progress.

Improve TCR Process: Reviewed Board last week. Defined some action items from feedback.

Tech Council Charter Revisions: Draft next week.

ADR process improvements: Added new state REJECTED

5-10 min

RFCs

All

RFC to review from Olamide:  https://github.com/folio-org/rfcs/pull/4

Previous Notes:

• 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.

Today:

• We have 4 Weeks for review. Need to form a subgroup.

• Olamide has to create a new PR for draft review.

1 min

Upcoming meetings

@Craig McNally 

• TC charter discussion:  Jan 20, 2023 10:00 AM ET

  • @Craig McNally will lead the discussion in @Jenn Colt's absence.

• TC dedicated discussion:  Jan 23, 2023 11:00 AM ET

  • Topic:  TC Goals and Objectives (@Tod Olson)

Slack Discussion

https://folio-project.slack.com/archives/CAQ7L02PP/p1673967475802819

Julian asks to add OpenAPI to supported technologies

Craig will answer positive.

*

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 , @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...

Revisiting FOLIO Governance

All / @Ian Walls 

Slack discussion:  Revisiting FOLIO Governance