2022-12-14 Meeting notes

Owned by Craig McNally
Last updated: Dec 14, 2022 by Jenn Colt
4 min read

Date

Attendees 

Discussion items

TimeItemWhoNotes
1 minScribeAll

Jakub Skoczen is next, followed by Raman Auramau 

Jenn Colt subbed in

-TCR Board Review

All

No news.

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

-RFCsAll

No news.

10-20 min

Technical Council Sub Groups Updates

All

  • Updates:
    • TBD
    • TBD
  • There are several new subgroups... do we want to iron out deliverables/goals/other details for those today?
  • There are a few subgroups which are well past their end date, what can we do to help wrap these efforts up?

____

Goals - Progress made, discussion to come

Breaking changes-  met and are working more on the RFC. Will discuss whether an ADR is needed. Interested in exploring how breaking changes should be communicated out, queued up to discuss after this is out the door. Will give heads up when need more agenda time.

TCR Process - held the retro, discussed feedback- how to triage, how to get feedback from those who couldn't attend, group will reach out to them.

Charter - discussion upcoming

Discussion of new groups and wrapping up older ones later on.


5-10 minAdditional meeting time dedicated to topic discussions

Craig McNally 

Topics:

  • Tools/Dependencies Versions (see previous notes for details)
  • Goals & Objectives (see previous notes for details)
  • TBD

Today:

  • Doodle poll ... still didn't get answers from everyone...

  • The best we can do is Mondays 11:00AM - 12:00PM ET 

___

Craig will send invite

15-20 minCharter Review

Jenn Colt / All

Draft charter - https://folio-org.atlassian.net/wiki/display/TC/2022+Draft
Previous charter - https://folio-org.atlassian.net/wiki/display/TC/Tech+Council+Charter

_____

Discussion of infrastructure bullet. What are we invested in/responsible for? Snapshots might be a focus more than things like JIRA, Jenkins, TestRails, etc. If not us then who for some of the infrastructure? Ask CC what they meant by infrastructure? Stuff required to run FOLIO system vs stuff required to run the project and development (like JIRA, jenkins). TC has had minimal involvement in any of those project oriented decisions. Craig will reach out to CC for clarification on infrastructure. Ask about specific aspects (CI/CD, etc).

Security policy/group question - Does TC delegate to security? Craig says yes security council reports to TC. TC responsibility delegated. Should use wording that gives wiggle room which is the policy wording.

Are the TCRs/ADRs adequately covered? Perhaps by the blueprint/vision/standards related bullets. Passive vs proactive tone of bullets. Enforcement is more than maintaining/documenting. Making the rules and enforcing them.

Group will meet again after the break.

5-10 minReporting Landscape / In-app reporting

Maccabee Levine / All

Discussion in #tc-internal about in-app reporting sparked a desire to get a handle on the current (broader) reporting landscape in FOLIO.

Maccabee Levine took on the task to investigate and provide a summary

This should help frame conversations better 

-----

Summary of current reporting solutions: https://folio-org.atlassian.net/wiki/display/FOLIOtips/FOLIO+Reporting+Options

Scope, 2022 goals and roadmap: https://folio-org.atlassian.net/wiki/display/RPT/About+the+Reporting+SIG

Query Development: https://github.com/folio-org/folio-analytics

WolfCon 2022: Intro to the Library Data Platform. Speakers: Nassib Nassar
https://prod-zoom-recordings-openlibraryfoundation-org.s3.amazonaws.com/5b9bf7e3-630c-4d06-80c0-c9e89307a68f%2Fshared_screen_with_speaker_view%28CC%29.mp4  (Start around 4 hrs, 3 min)
Presentation
https://static.sched.com/hosted_files/wolfcon2022/0c/20220831-ldp-wolfcon-2022.pdf 

_____

SIG would be interested in weighing in on cross-app proposed reporting solutions.

Will look into export manager more.

Will meet with Nassib.

What "in app" reporting already exists?

Improve definition of "in app"

In app vs cross app (one app involved vs multiple apps involved). Originally related to what reporting sig did/didn't have to do.

*Topic backlogAllReview/introduce/triage unprioritized items, and if there's time start discussion items.

Topic Backlog

20 min

WOLFcon Hot TopicsAll

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


Optimistic Locking interfering with batch update in inventory

Tod Olson 

Conversation started in slack:

The Data Migration subgroup of SysOps has been struggling with how optimistic locking has interfered with batch update in Inventory. They've asked me to bring it to TC to see if there's a way to push this forward. The current open ticket is MODINVSTOR-924 Batch update with optimistic locking disabled. (This was split off from MODINVSTOR-910.)

Topic has been addressed. Core team has agreed to implement as separate API that disables optimistic locking.

See also Bulk Operations redesign, different issue but seems related.

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 

    • 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




Action Items

  •