Table of Contents

Date

09 Nov 2017

Time	Item	Who	Notes
5 min	Convene & roll call
55 min	Quick review/update on confluence changes and goals. Looking for agreement Coverage mapping (work) Fishing for Extensions API direction and leadership Test coverage for all bindings – how do we verify? Call for use case examples to help our community Namespace conventions – are people aware? Any impacts?	Former user (Deleted)	See below

Looking good, no incomplete tasks.

Add new action items here.

Name	Organisation	Present?
Former user (Deleted) (Chair)	BNY Mellon	N
Dhilip Buddha	BlackRock	N
Kashik Chaubal	BlackRock	N
David Deng	Citi	N
Former user (Deleted)	At-Large Member	Y
Matthew Gardner	BlackRock	N
Matt Joyce (Deactivated)	Symphony LLC	N
Former user (Deleted)	Morgan Stanley	Y
Anton Kozyr	BlackRock	N
Former user (Deleted)	BNY Mellon	N
Ian J. McDermott	JP Morgan	N
Dan Nathanson (Deactivated)	Symphony LLC	N
Barun Patnayak	Citi	N
Former user (Deleted)	JP Morgan	N
Johan Sandersson	FactSet	N
Former user (Deleted)	FactSet	N
Leslie Spiro	Tick42	N
Former user (Deleted)	IHS Markit	Y
Peter Monks	Symphony Software Foundation	N
Aaron Williamson	Symphony Software Foundation	N

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.