Versions Compared

Old Version 2

changes.mady.by.user Mike Gorrell

Saved on

compared with

New Version 3

changes.mady.by.user Mike Gorrell

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Date

27-Jan-2021

Attendees

Discussion items

Time

Item

Who

Notes


Roadmap TaskforceTodThe Roadmap Task Force has been formed and wants to collect info from various groups. Tod will introduce this concept. We will meet with Taskforce representatives next week 2021-02-17.

Spring WayTC

TC has discussed this originally on 2020-11-04 where we concluded:

Outcomes:

1) We agree and accept that Spring Way is an acceptable alternative to RMB

2) Tech Council recommends that new modules use the Spring Way Framework and OpenAPI instead of RMB and RAML but we should understand that there will be gaps in our processes (documentation, CI/CD) for the first (few?) modules that head down this path and the project will have to work to close those gaps.

3) Tech Council recommends an opportunistic approach for existing modules: when work needs to be done a migration to the Spring Way will be considered. A more detailed discussion around a planned migration can be had in the future.

and then again on 2021-01-13 where we got an update on what tasks would be needed to include Spring Way modules into the standard CI/CD pipeline. There were actions from that meeting.

TODAY we'll discuss guidance for development teams to use Spring Way. What resources, standards, tools, etc. are they to use to adopt our recommendation (Tech Council recommends that new modules use the Spring Way Framework and OpenAPI instead of RMB and RAML)?  Discussion:

  • Could point people to FOLIO Spring Base GitHub repo - this is the closet thing to "this is what Spring Way means"
  • Could point them at a couple of projects that are using Spring.
  • Could connect them with Spitfire team who "owns" Spring Way as of right now (but won't)
  • Not totally clear who is responsible for owning and maintaining, making architectural decisions, documentation, etc.
  • Perhaps coming out of today's meeting TC pushes the following:
    • Leverage the channel - #folio-spring-base
    • Encourage the members of that channel to create a backlog and communicate needs and issues via this channel
    • Seek a Product Owner to be the person to understand and set priorities for things that are added to the backlog
    • Could we ask one of the developers to take on this PO role? Or would it make sense for the Core:Platform team to assume this leadership role? Jakub agrees that its better for Core:Platform and Jakub will be the technical product owner for Spring Way. Need to discuss timeline for him and the team.
    • Should be analogous to Core Platform and Stripes-Force
    • TC should probably be more involved in setting the high level goals here.
    • We will follow up in 2 weeks to check in on needs and progress



Budget management processTC

Ran out of time

In a past meeting (2021-01-27) we said: We'll schedule a conversation about how to establish and manage a policy around changes that might impact our budget.

Discuss:



New Technology requests - evaluation criteriaTC

Ran out of time

The TC needs to develop a set of criteria/checklist to be reviewed when new technologies are suggested/requested... so that we can make consistent and transparent decisions. Our brainstorming ideas include: