2018-01-10 Meeting notes

2018-01-10 Meeting notes

Table of Contents

Date

Jan 10, 2018

Action items

Add new action items here.

Meeting notes

Nick Kolba: One issue we just raised to Lynn and I think it’s been open on the Symphony side, but besides that I’d just be interested in seeing where we are with the open window API.

Lynn Neir: There was a proposal to add “open window” to SSF. I’ll check on the PR. I know it’s been implemented; I don’t know if it’s been merged. I don’t see a PR yet, but I created a ticket on it.

Aaron Williamson: You think it’s been implemented?

Lynn Neir: I thought so. I don’t see a PR on the open source project, so it may still be on their board. I need to push that forward.

Nick Kolba: That would be great, it’s been awhile.

Mazy Dar: Lynn, a couple questions on the APIs going forward. You guys are supporting the published SSF API, right?

Lynn Neir: Yes.

Mazy Dar: When it changes, what is the process you’re thinking for notifying us?

Lynn Neir: The documentation on the wiki should be accurate. We don’t have a way on there to say when it’s coming out.

Aaron Williamson: Would you be opposed to having a wiki page that you update with the date that API changes are

Mazy Dar: So you won’t make any API changes without discussion with this group?

Lynn Neir: Oh yeah, we’re not making any changes without discussing it here and updating the documentation. But we can definitely update a page saying when that functionality will be available on the Symphony side. There may be features there that don’t need an API, so that’s just a matter of watching the repo. But API changes will go through this group.

Mazy Dar: What’s an example of a change to the wrapper that won’t involve a change to the API?

Lynn Neir: I don’t know, maybe just a change to the way the API is implemented in the wrapper.

Mazy Dar: Got it.

Lynn Neir: Most of what’s going on now is bug fixes, trying to get it stable and whatnot.

Aaron Williamson: Was there anything else outstanding?

LS: There was one question about how states could be saved with Symphony, and I need to produce a proposal. Second, whether we know how the Foundation will manage the Plexus piece and Symphony integration.

Aaron Williamson: I think what I’ve mostly heard from participants in this group is that it should be a separate Working Group. It’s probably something that should go up to ESCo.

Lawrence Miller: I’d say it hasn’t been decided yet where it should go, but I think it’s something we should get DB’s input on first.

Aaron Williamson: That makes sense. Any other business? Ok, then we’ll adjourn.

Agenda

Time

Item

Who

Notes

Time

Item

Who

Notes

5 min

Convene & roll call





10 min

Review action items from previous meetings



See Action Items from previous meetings

5 min

AOB & adjourn





Attendees

Name

Organisation

Present?

Name

Organisation

Present?

@Former user (Deleted) (chair)

Credit Suisse



@Leslie Spiro (interim chair)

Tick42

Y

Jim Bunting

ChartIQ



Jonathan Christensen

Symphony LLC



Andrew Christie

Ipreo



Siddarth Dalal (@sidd)

ChartIQ



Mazy Dar

OpenFin

Y

@Gareth Davies

Goldman Sachs



@Colin Eberhardt (He/Him)

ScottLogic



@Matthew Gardner

BlackRock



Mark Hu

Citi



Brian Ingenito

Morgan Stanley



@Former user (Deleted)

Symphony LLC



@Former user (Deleted)

Morgan Stanley



Richard Kleter

Deutsche Bank



@Former user (Deleted)

OpenFin

Y

@Former user (Deleted)

Citadel

Y

@Former user (Deleted)

Deutsche Bank



Adam Lancaster

Tick42

Y

@Ian J. McDermott

JP Morgan



@Lawrence Miller (Deactivated)

Symphony LLC

Y

@Lynn Neir (Deactivated)

Symphony LLC

Y

@Former user (Deleted)

JP Morgan



Ed Sanders

JP Morgan



@Johan Sandersson

FactSet

Y

@Former user (Deleted)

Morgan Stanley



@Former user (Deleted)

HSBC



Ryan Sharp

ChartIQ



@Former user (Deleted)

Symphony Software Foundation



@Peter Monks

Symphony Software Foundation



@Aaron Williamson

Symphony Software Foundation

Y

Need help? Email help@finos.org we'll get back to you.

Content on this page is licensed under the CC BY 4.0 license.
Code on this page is licensed under the Apache 2.0 license.