/
2022-08-24 Meeting notes

2022-08-24 Meeting notes

Aug 24, 2022

Date

Aug 24, 2022

Attendees 

  • @Craig McNally 

Discussion items

Time

Item

Who

Notes

Time

Item

Who

Notes

1 min

Scribe

All

@Jakub Skoczen will take notes today 

-

TCR Board Review

All

Nothing to review

10-15 min

Technical Council Sub Groups Updates

All

 

Translations subgroup had/has meetings to define the scope of issues.

Breaking Changes subgroup continues work on some items (e.g., HTTP statuses). Need to push this out to somewhen to the end of October?

-

RFCs

All

Nothing to review

5-10 min

Cross-App data sync

@Raman Auramau 

 

1 min

Quarterly Community Update

@Craig McNally 

**Reminder**:  The next Quarterly Community Update is approaching (last day of WOLFcon).  I will be pulling together lists of accomplishments, goals, etc. soon.  Please let me know if you have any ideas/thoughts.  Once I have something I will share it at an upcoming TC meeting.

10-15 min

WOLFcon Working Sessions

All / @Jakub Skoczen 

Discuss how we want to plan & run these working sessions.  Brainstorm ideas?

Three topics - tech debt items, arch blueprint, and ... The question is about the format of the sessions (now they are marker as "working meeting").

Need to have volunteers who would be able to facilitate.

Coordination is an important thing here, because of potential overlaps or duplication.

Agreed to circle back next week.

-

Tools/Dependencies Versions

@Vijay Gopalakrishnan 

Previous:

  • Tools/dependency versions - @Vijay Gopalakrishnan took on this topic as a project. There is also a proposal Managing Tools/Framework Dependencies currently in Draft stage with feedbacks as latest as 02.08.2022.

Today:

  • Deferred until Vijay returns

15-20 min

Technology Changes & Releases

@Marc Johnson 

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:

Time Permitting

Retrospective on the ADR Process

@Craig McNally 

  • 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

Time Permitting

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

@Marc Johnson 

Introduce the topic

  • What do we want to get out of this conversation?

  • Does this require a subgroup or individual to generate a proposal?

Time Permitting

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

Time Permitting

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

Time Permitting

Other topics

All

Topic Backlog:

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

Action Items