Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Attendance, first topics

Date

Attendees 

Discussion items

TimeItemWhoNotes
1 minScribeAll

Tod Olson (Florian Gleixner  is is next but absent, followed by Jeremy Huff  convening)

10-15 minTCR Board Review

All

TCR-6 (Jeremy Huff ) - have begun review, small group sat in to learn how

TCR-9  (Zak Burke )

TCR-17 (volunteer needed?) - Marc Johnson had already looked at this a bit, will continue with review

TCR-18 (volunteer needed?) - Zak Burke 

-RFCsAll

Nothing to review

10-15 min

Technical Council Sub Groups Updates

All


Cross-council scope group - dissolved, 

Documentation - decision was made to use the wiki for onboarding documetation

Breaking Changes - discussion continues, coming to some clarity

5-10Managing Dependencies
20 minTC Charter ReviewAll

Previous:

Members were asked to review the TC charter in preparation for today's discussion.  

  • Go through the charter together?
  • Are there specific areas of the charter we should focus on?
  • Is anything that's missing, or should be removed?

Notes: TC charter has been updated recently, how would the TC like to review it?

Jeremy Huff Was it written by TC or by someone else? - Craig McNally It was written by TC?

Craig McNally Let's create a draft version, discuss it, communicate to other councils before publishing

Tod Olson A comment to Guiding Principles .... (smth that should be explicitly stated as a GP) - Tod will add a comment to the doc

Some conversation followed.. some comments were added to the doc itself

Review and comments from TC members are welcome


Today:

Time Permitting

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:

5-10 minTools/Dependencies Versions

Previous:


Today:

???Technology Changes & Releases

Previous:

  • How/when to make significant technology changes in coordination with the release schedules of other tools, e.g. keeping in sync with Node LTS releases, or Java 17 or Postgres 14, etc. 
    • May be overlapping with the Tools/dependency versions (see above)
    • Marc Johnson - It would be useful to relate the changes to match the release schedules
    • See also:  messages in TC channel

Today:

10 minRetrospective on the ADR Process
  • Discuss if we want to try and do this during a TC meeting or schedule a dedicated meeting.
  • What's working well for us?  What needs to be clarified?  
  • Scope / level of detail,
  • Clarify what information belongs in which section
  • Is it mandatory for accompanying materials (details designs/proposals/etc.) to be on the wiki, or can they live in google docs, etc.?
  • We agreed to do this sort of exercise after each RFC, but think it's worth doing this for ADRs - maybe not after each one, but periodically.
  • Retro board: https://easyretro.io/publicboard/bk8DxfBbCeZIYL1pnsBPUN2xgYb2/a07d2c6b-754b-4446-8743-7f32f2911928
Topic Backlog

How can/should the TC weigh in on the architectural impact of new modules?

Introduce the topic

  • What do we want to get out of this conversation?
  • Does this require a subgroup or individual to generate a proposal?

Optimistic Locking interfering with batch update in inventory

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


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

...