waltz
waltz copied to clipboard
Request to restart monthly FINOS Waltz project calls
Transferring from https://github.com/finos/community/issues/302 cc @TheJuanAndOnly99
Request to restart monthly FINOS Waltz project calls
The NatWest OSPO would like to request a monthly Waltz project call to support the adoption of the project.
The start date and agenda management can be discussed and agreed once the appetite of FINOS, @davidwatkins73 and @JWoodland-Scott is understood.
Thanks for your consideration.
James.
Hello 👋🏻
Just closing the loop on this thread @maoo and @davidwatkins73.
Let me know if a monthly Waltz call was agreed as it would be good to start inviting the NWG Waltz team to calls.
Speak soon,
James.
I had a chat with @maoo last week and we agreed that restarting these calls is a good idea.
I'm thinking about the best way to organize them and am currently thinking:
- Monthly (early afternoon uk time if possible to cover as many geographies as possible)
- Split into 3 segments
- ad hoc (recent developments, queries from the user / adopter community)
- short session on a particular feature in Waltz (e.g. taxonomies, flows, assessments) etc.
- dev topics (what is being worked on, what is being planned, what needs help, ideas from the community).
Thoughts ?
@davidwatkins73 and @maoo,
I'm very happy with the suggestions made above and have included @TheJuanAndOnly99 to help schedule the Monday meetings and place on the FINOS community calendar.
There is a very active Waltz engineering community at NWG, so I suggest leaning into the UK / IST timezones if engineering is most active in these regions. I suggest meeting at 13:00 BST or before.
I will introduce you to the NWG Waltz maintainers over email so we can align our roadmaps and figure out how NWG can contribute into the upstream project.
James.
Thanks @mcleo-d !
@davidwatkins73 - please confirm time and cadence, and we'll setup the meetings and Zoom accesses for you @JWoodland-Scott . TY!
How about the first Thurs of every month (starting 2024-05-02). We do have some interest from some other banks (US based) so not sure how we can balance the timings to cover all timezones (2pm ?)
We propose having each meeting lasting 1hr where the meeting has 3 distinct parts:
- new releases and user group q+a
- deep dive on topic (to be advertised in advance, see further below for our starting set of topics)
- contributor topics (coordinating features, notification of larger upcoming work items)
Initial topics:
- data flows (incl. classification rules)
- differences between logical flows, physical flows and specs
- data types
- flow participants (apps, actors, eudas)
- flow classification rules
- taxonomies (ratings, admin)
- ...
- assessments
- ...
- reporting
- ...
Happy to adapt the topics based on community feedback.
(@maoo - do we get a view on predicted attendance prior to each meeting ?)
Possibly shifting the first session back a week or two to accommodate Bank Holidays. Will post here once the dates and cadence have been confirmed.
Calls have resumed - closing this issue