@Nicholas Kolba

@Jonathan Teper

JPM

Saori Fotenos

Refinitiv

@Riko Eksteen

Adaptive

rikoe

@Tim Kolecke

@Rob Underwood (Deactivated)

FINOS

brooklynrob

@James McLeod (Unlicensed)

FINOS

5 min

Convene & roll call

5 min

Review action items from previous meetings (see above)

10 min

Migration to Github to replace Confluence Wiki

General mood of the group was they did like the idea of using Github overall for managing the use cases – we get the visibility of the technical teams much better. Nice to be integrated into the technical workflows .

Suggested way forward to finalize next month:

1. Continue to listen to and reflect on on-going feedback from Voice program on their move to using Github exclusively (i.e., not using Atlassian Confluence)

2. Start moving towards a Kanban Board. Start moving the following items to the kanban board:

   1. meeting minutes

   2. drafting of use cases

   3. program task management

15 min

Survey

@Nicholas Kolba

Final review on survey - decide next steps

Discussion ensued on whether survey should be anonymous or not. Concerns were made about people able to speak on the record 

• FINOS staff to work on a proposal as to: 

  • survey tool that we'll use

  • thoughts about how we would market & spread word on the survey. We'd like recipients to be able to share the survey, ideally via a link

  • Framing: one response per individual

  • Goals of the survey:

    • Get feedback that's as honest as possible

    • Understand how many organizations are implementing FDC3 and how well/ how many institutions are doing anything with FDC3

  • Anonimity. Responses should not be anonymous, because we'd like to be able to follow up + there isn't anything on this survey that requires anonomity

    • make it optional for the respondent to make it anonymous or not?

  • FINOS as unbiased third party to run the survey and treat responses:

    • Structure proposal: FINOS to run and send out the survey. This way, FINOS can see all details but will not distribute them with FINOS members who are vendors, so they cannot use it for marketing purposes

    • Privacy will also allow respondents to give truly candid feedback

    • @Rob Underwood (Deactivated) to double check with FINOS leadership whether this is feasible

  • Survey responses.

    • Results should be presented in aggregate and made publicly available

    • Only thing that's kept private are individual responses + names of firms

15 min

PoP revisions

group

• Proposed POP revision can be found here: FDC3 POP Compared with New Standard POP (2).pdf

• The only change would be that "Committee" is now called "Project"

• FDC3 PMC to review POP and highlight any concerns they may have

5 min

AOB & adjourn

• Saori will most probably not focus on FDC3, makes most sense for JT to be the chair for the Use Cases WG and for Saori to leave PMC

• @Aitana Myohl to off-board Saori from PMC and UC WG