Waltz Project Meeting: 2024-06-10

[davidwatkins73]

Description

Date

Monday 10 June 2024 - 8am EST / 1pm UK (BST)
Occurs the second Monday of every month

Zoom

Join Zoom Meeting
https://zoom.us/j/98495304665

Meeting ID: 984 9530 4665
Passcode: 202795

Find your local number: https://zoom.us/u/aeyTu3Q7E8

Untracked attendees

Name	Firm	Comment

Meeting notices

• FINOS Project leads are responsible for observing the FINOS guidelines for running project meetings. Project maintainers can find additional resources in the FINOS Maintainers Cheatsheet.

• All participants in FINOS project meetings are subject to the LF Antitrust Policy, the FINOS Community Code of Conduct and all other FINOS policies.

• FINOS meetings involve participation by industry competitors, and it is the intention of FINOS and the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in, any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws. Please contact [email protected] with any questions.

• FINOS project meetings may be recorded for use solely by the FINOS team for administration purposes. In very limited instances, and with explicit approval, recordings may be made more widely available.

Agenda

• Convene, roll call, welcome new people (5mins)
• Display FINOS Antitrust Policy summary slide
• 2024 FINOS State of Open Source in Financial Services Survey
• Review Meeting Notices (see above)
• Approve previous meeting minutes - https://github.com/finos/waltz/issues?q=is%3Aissue+is%3Aclosed+label%3Ameeting
• Users: Recap of Waltz improvements since 1.23
• Collaborators: Upcoming development areas
  • Logical flow becoming pure aggregation of physical flows
  • Java 17
• AOB, Q&A & Adjourn (5mins)

Decisions Made

• ...

Action Items

• ...

Project Microsite: https://waltz.finos.org

[davidwatkins73]

What's New(ish)

Summary of major changes over the past few years

General

• Navigation overhauled, now uses a collapsable sidebar instead of a header bar
• Markdown can interpolate common entity variables. This allows for inlining, user-definable deep links (i.e. we call out to another system to render some surveys using a word doc template). Also used to allow 'per-section' customised help to be rendered
• Data driven permission support (for flows, taxonomy ratings, assessments)

Reporting

• Report grids provide a convenient way for end users to define a custom tabular report which can draw together information from a wide range of Waltz entities - Image
  • Has found extensive uses for ad-hoc reporting, regulatory compliance tracking and as a mechanism to ease custom integration with other systems.

Application

• Commission date added (alongside existing planned decom and actual decom dates)
• Taxonomy mappings support 'primary' flag, allocations, decom dates, replacements
  • The primary flag is used in summary lists to give additional context, e.g. showing the primary function of each application in a group - Image
• Multiple cost types can be registered against apps - Image
• Attestation improvements to assist users with many attestations to perform

Flows

• Numerous look n' feel and performance improvements
• Flow classification rules replaced authority statements - Image
  • classifications can be fully defined by client
  • rules can be directional (i.e. a consumer rule vs a producer rule)
  • rule scoping can be narrowed to specific apps to provide support for legacy/heritage flows
  • page for each rule, showing: companion app rules, and companion data type rules

Assessments (enums)

• Multi valued assessments
• Users can specify their 'favourite' assessments
• Admins can define which assessments to display in entity lists (e.g. always show 'Cloud onboarding' flag when showing lists of applications)

App Groups

• Org units can be incorporated into groups, useful for defining organisational structures which cannot be easily expressed as a single branch
• Users now have a favourites group, as they navigate through Waltz they can easily add/remove apps to this group
  • The favourites group is used to drive the activity log on the homepage - Image

Surveys

• Many user interface improvements, particularly around tracking/informing users which surveys they need to complete/approve - Image
• Conditional survey questions. Preconditions can be either survey based (based on answers given elsewhere in the survey) or environmental (based on properties of the surveyed entity) - Image
• Multi select answers
• Custom roles can be defined to allow for teams to self-manage survey templates and runs
• Comprehensive export options
• Support for questions which can be linked to taxonomies

End User Applications

• End User Apps (aka EUDAs / EUMAs / EUC), are now first class entities - Image
  • They can participate in flows (like applications and actors)
  • Support bookmarks, assessments, people etc
  • Upcoming: will support taxonomy mappings

Legal Entities

• Legal Entities can be represented in Waltz
  • They be used to link applications to Legal Entities (i.e. through a Controlling Legal Entity relationship)
  • They can have assessments (e.g. jurisdiction information)
    • This can then be 'rippled' to associated apps
  • Legal Entities can include many of the other typical Waltz entity relationships (people, bookmarks etc)

[mcleo-d]

James McLeod / NatWest

[davidwatkins73]

Here :)

[jessica-woodland-scott-db]

Hi, Jess here :)

[mcleo-d]

Just to socialise here 👉🏻 finos/devops-automation#203

NatWest Open Source Supply Chain Security Roundtable

NatWest Group is running an Open Source Supply Chain Security “FINOS Members + Limited Guests, Chatham House Rule” roundtable, to celebrate OSFF London, on behalf of the FINOS DevOps Automation SIG.

• Tuesday 25th June at 9:30am BST / 2pm IST - Fully Hybrid over Zoom

The roundtable is fully virtual, with 10 places available at NatWest, London for those wanting to join us in the room (registration in the comments below).

During the meeting we should explore [WIP please feedback in the comments]

1. Aligning the RT to the DevOps Automation “Open Source Supply Chain Security” Working Group.
2. Safe ingress of Open Source materials / dependencies into a banking engineering scenario.
3. Safe storage and continuous monitoring of internal Open Source registries and Route to Live.
4. Automation tools on repos and IDEs (DevSecOps + shift left).
5. OpenSSF and FS-ISAC training, alignment and standardisation.

We look forward to celebrating OSFF London with you, on behalf of NatWest Group!

James.

[mcleo-d]

Just to socialise roundtable two here 👉🏻 finos/open-source-readiness#276

How to Measure InnerSource, Open Source and Enterprise Projects - CHAOSS, Agur, 8KNOT, Backstage, GitLab and GitHub

NatWest Group is running a How to Measure InnerSource, Open Source and Enterprise Projects “FINOS Members + Limited Guests, Chatham House Rule” roundtable, to celebrate OSFF London, on behalf of FINOS Open Source Readiness.

Tuesday 18th June at 2:00pm BST / 6:30pm IST / 9am EST - Fully Hybrid over Zoom
The roundtable is fully virtual, with a number of places available at NatWest, London for those wanting to join us in the room (registration in the comments below).

• Home - CHAOSS
• Info - osci.io
• Software - CHAOSS

This meeting follows on from Open Source Readiness finos/open-source-readiness#274 on 5th June 2024 by moving into the How and Next Steps for FINOS banks like NatWest Group.

We look forward to celebrating OSFF London with you, on behalf of NatWest Group!

James.

[davidwatkins73]

Relevant (some new) issues based on conversation around the Waltz fine-grained permission model:

#7087 - Permissions: Export fine grained permissions for downstream tool consumption
#6166 - Permissions: Document fine-grained permission model
#7090 - Permissions: admin screen/s
#7089 - Permissions: Section on person page to display involvement based permissions