/
2022-11-02 Meeting notes

2022-11-02 Meeting notes

Nov 02, 2022

Date

Nov 2, 2022

Attendees 

  • @Craig McNally

  • @Ingolf Kuss 

  • @Vijay Gopalakrishnan 

  • @Ankita Sen 

  • @Chulin Meng 

  • @Jeremy Huff 

  • @Ian Walls 

  • @Jakub Skoczen 

  • @Marc Johnson 

  • @Olamide Kolawole 

  • @Zak_Burke 

  • @Zorian Sasyk 

  • @Jenn Colt 

Discussion items

Time

Item

Who

Notes

Time

Item

Who

Notes

1 min

Scribe

All

@Tod Olson is next followed by  @Ankita Sen 
@Jenn Colt covered

-

TCR Board Review

All

No news.

-

RFCs

All

No news.

10-15 min

Technical Council Sub Groups Updates

All

 

  • Breaking changes making progress, RFC under consideration. RFC may be ready next week. ADR possibly some time after.

  • Improve TCR process, kick off meeting tomorrow

  • Charter meeting to come

5-10 min

Retrospective on the ADR Process

@Craig McNally 

Notes:

  • Several action items were identified

  • Review together?

  • Probably want to create a subgroup to make improvements

From today:

  • Handing off to sub group would probably work best. Review items on your own. Let Craig know if you have questions. Added to subgroups page. Vijay will lead.

1 min

Organizing our wiki space

@Craig McNally 

  • Created an "Archived" section under "Meeting Notes", consolidated meeting notes older than 2022 there.

  • Created an "Archived" section at the top level, started moving things there which no longer seem relevant.  We can review this together at some point, maybe deleting some things for good, or putting them back if they are still relevant.

  • This effort is still a WIP.  Let me know if you have any input/ideas.

  • @Jeremy Huff We might want a TC Calendar event at regular intervals to archive.  @Craig McNally did so, repeating in January.

Updates:

  • Technical Skills in Demand page – Verified with CC that it isn't used.  Archived.

  • FOLIO Architectural Blueprint Strategic Changes page – Archived per suggestion from last week.

Todo:

  • Development Teams and Resources page 

 

1 min

Renaming wiki spaces

@Peter Murray / @Craig McNally 

Just raising awareness of this conversation in slack (#tech-council / #folio-tech-leads):

There has been a request to rename the "COHORT2019" Confluence space ([FOLIO-3623] Rename Confluence spaces). This does not seem to be a thing that is done lightly...Atlassian doesn't officially support it, but there is a knowledgebase article with instructions for accomplishing it.  As long as a renaming is happening, it seems to make sense to consider renaming https://folio-org.atlassian.net/wiki/display/FOLIJET/ to something more generic (like "DEVELOPER" or "FOLIODEV"?).

Is renaming the FOLIJET space a good idea or a bad idea? If it is a good idea, what would we want the space key to be?

Not trying to solve this here and now.  If you have thoughts, questions, or suggestions feel free to chime in on slack.

5-10 min

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.

  • @Vijay Gopalakrishnan advised that he was meeting with @Marc Johnson on Friday to resolve outstanding questions and that this work should be ready for next week

Today:

10-15 min

Things FOLIO could do better

All

From @Tom Cramer in #tech-council:

Since September, the CC, PC and TC have canvassed many community members on “what are things that could be better about FOLIO?” This came out of discussions at WOLFcon in Hamburg about what the priorities were for advancing & investing the project. 20+ council members interviewed 60+ informants from the community, producing a list of 175 items.

These items can be found in a grouped list that sorts the input into 13 different categories. This is a rich gauge of where many community members find the project--I recommend reading through this doc all at once to capture the gestalt. (~15 min)

A synthesis of all the input can be found in this presentation. The last three slides contain some specific and actionable opportunities for the FOLIO councils to consider and adopt as priority items around which to organize community effort.

Today:

  • Review the presentation together? 

  • Ask all members to review the more detailed list on their own?

Notes:

  • Reviewed presentation, a lot of feedback on "run on a laptop" point

    • Seen as barrier to contributing

    • Better management of dependencies between modules might help

 

 

 

 

*

Topic backlog

All

Review/introduce/triage unprioritized items, and if there's time start discussion items.

Topic Backlog

10 min

Consolidated Decision Log

All / @Maccabee Levine 

What, if anything should we do with the Decision log in the Technical Designs and Decisions wiki space?  Is it worth consolidating those decisions with the TC's ADRs?  Should we cross-reference?  Clarify the scope of these decisions, and whether or not decisions should still be made/logged here?  

See discussion in #tech-council for additional details.

  • @Craig McNally Decision log left when Tech Leads group fell apart with new governance structure.  Are decisions still made or logged in that space?  Where does this lie in the backlog.

  • @Maccabee Levine Motivations are to have a single list of decisions, to build developer-buy in and solve the longstanding issues with what decisions TC has authority to make.  Also to know what we have to keep updated vs archive.

  • @Craig McNally By consensus, added to the middle/bottom of the list.

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:

 

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?

 

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.

 

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 

Action Items