Table of Contents

Date

Nov 9, 2017

Agenda

Time	Item	Who	Notes

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?	@Frank Tarsillo	See below
			Open

Action items

Add new action items here.

Attendees

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.