2017-11-9 Meeting notes
- Former user (Deleted)
Owned by Former user (Deleted)
Table of Contents
Date
Agenda
| Time | Item | Who | Notes |
|---|---|---|---|
| 5 min | Convene & roll call | ||
| 55 min |
| Former user (Deleted) | See below |
Action items
Task report
Looking good, no incomplete tasks.
Add new action items here.
Attendees
| Name | Organisation | Present? |
|---|---|---|
Former user (Deleted) (Chair) | BNY Mellon | N |
| Dhilip Buddha | BlackRock | N |
| Kashik Chaubal | BlackRock | N |
| David Deng | Citi | N |
| At-Large Member | Y | |
| BlackRock | N | |
| Symphony LLC | N | |
| Morgan Stanley | Y | |
| Anton Kozyr | BlackRock | N |
| BNY Mellon | N | |
| JP Morgan | N | |
| Symphony LLC | N | |
| Barun Patnayak | Citi | N |
| JP Morgan | N | |
| FactSet | N | |
| FactSet | N | |
| Tick42 | N | |
| IHS Markit | Y | |
| Symphony Software Foundation | N | |
| Symphony Software Foundation | N |
Meeting notes
- Minimal attendance
- All agreed to confluence changes after clarification on Extensions API applicability. Extensions API should be viewed as a focus on use cases and examples, but could include discussion on existing limitations and improvements.
- Discussion revolved on best way to represent use cases that can be referenced, maintained and provide clear examples using different language bindings.
- Agreed that we should create a new repo called "Symphony-by-Example" which would provide a combination of documentation and code examples
- We should leverage the simple markdown construct from Bruce Skingle (Deactivated) project
- Initial focus should be on publishing any existing content vs figuring out best structure.
- Recommend examples are represented by deep links to supported repostories that maintain work. This doesn't prevent anyone from publishing new examples directly within the project.
- The new repo is not limited to the REST API or Extension API projects, but can be used as a general purpose cook book of sorts.
- End of the meeting focused on followups related to followups on namespace proposal and test coverage for bindings.
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.