Table of Contents

Date

06 Jul 2017

Agenda

New action items

Standing action items

• Capture API use cases relevant to your organization
• Identify high-priority use cases in Confluence or to Former user (Deleted)
• Tell Former user (Deleted) about API errors & exceptions that need work

Actions items from previous meetings

Language Bindings

• Former user (Deleted): create API definitions based on SJC abstracted binding layer and generate a YAML Swagger specification from it
• Former user (Deleted): Look into how to enable limited cross-pod capabilities on the Foundation's test pod and others to make integration testing possible.
• Former user (Deleted), Former user (Deleted), Matt Joyce (Deactivated):
  
  • Schedule a call to discuss API binding consistency. Coordinate with Former user (Deleted) and Dan Nathanson (Deactivated).
  • Start a list of the basic functionality bindings should have test for before being considered active. (Possibly Former user (Deleted) too.)
  • Draft list of API endpoints that should be supported by active language bindings.

Use Cases

• Former user (Deleted): review API use cases with LLC team before the next meeting to determine/document whether they're supported by the existing API.
• Former user (Deleted): work with Johan Sandersson to create detailed use cases to define the capabilities that bots should have access to
• All: review the job story format and consider whether to use this format for use cases.

Consuming the Symphony API

• All: If you are aware of an open source project that provides a good API for creating bots, tell Former user (Deleted).
• Former user (Deleted): Talk to Former user (Deleted) about bot deployment work, possibly contributing to Foundation.

Attendees

Meeting notes