2023-01-09 - Tools/Deps Versions Discussion

1 min

Scribe

All

*

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

• @Vijay Gopalakrishnan - Need to review as group, get some feedback and close it. Version 1 was reviewed and certain things finalised but later discussion revealed a different approach was needed. Reviewed in today'S meeting for active feedback and discussion about the topic.

• @Jeremy Huff - Concerns about the list of Officially Supported Technologies - this document was created for the new module technical evaluation , it was intended for another purpose so rolling it out into central processes might cause issue.

• @Marc Johnson - Officially Supported Technologies is not a secondary document of this process, the point of the process is to have a list of things Folio as an application officially supports which is essentially like this exact document.. @Vijay Gopalakrishnan agrees.

• @Vijay Gopalakrishnan hard to get this done without having a separate meeting. Craig will send out a doodle poll for a separate meeting.

Today: 

• Recap:

  • Discussed process for capturing the current state.   Who/How is still TBD

  • Oleksii P. (Release coordinator) to create JIRAs, let the teams sort out timing, etc.

  • Need to update the current officially approved technologies page(s)

  • Scope:

    • Major infrastructure (kafka, postgres, etc.)

    • Shared toolsing/frameworks (e.g. java, spring, etc.)

• Review/discuss questions in Managing Tools/Frameworks/Dependencies Version - v0.2 DRAFT#Questions? as a group today.

  • How do we designate/delegate component ownership?

    • Florian: It should be development teams since many of these things are dev-driven

    • Marc: Not sure that will work... in most cases there are multiple teams using each of these things which might not agree.  How do we choose a single owner?

    • Marc: Teams usually don't actively collaborate with other teams.  

    • Craig: Maybe we should start with the low-hanging fruit?

      • UI stuff → Stripes Architecture team

      • Elasticsearch/Opensearch → the team responsible for mod-search

      • etc.

  • How do we handle cases where the component owners don't do anything?

    • The issue will eventually come up when there's a need, be it security, or feature-driven

    • If needed the team with the need can bring this to the TC

• Next steps:

  • Vijay to update the document with owners, updated scenarios, etc.

  • Figure out how to communicate this out to the dev teams, especially those which have been designated as owners.

  • Vijay to create a Decision Record.