Date

Oct 11, 2016

Attendees

Name	Organisation	Present / Absent
@Michael Harmon	Symphony LLC	Present
@john.stecher@barclays.com	Goldman Sachs	Absent
@Lawrence Miller (Deactivated)	Symphony LLC	Absent (possibly due to travel)
@Former user (Deleted)	Markit	Present
@Former user (Deleted)	Credit Suisse	Absent (due to travel)
@Peter Monks (secretary)	Symphony Software Foundation	Present

Actions items from previous meeting(s)

@Michael Harmon, @john.stecher@barclays.com, @Lawrence Miller (Deactivated), @Former user (Deleted): review Symphony Foundation Contribution Lifecycle Proposal and prepare comments / feedback for discussion in a future ESCo meeting

@Peter Monks: schedule that discussion into future ESCo meeting agenda

@Peter Monks: schedule "WG ontology" discussion into future ESCo meeting agenda

@Lawrence Miller (Deactivated): follow up offline with @Former user (Deleted) and @Michael Harmon regarding limitations around rich content

@Lawrence Miller (Deactivated): locate internal LLC conversations (if any) around "messaging strategy and vision", and then work with @john.stecher@barclays.com and Nathan Bricklin on potential new WG on this topic

@Peter Monks: push agenda items we didn't get to to subsequent meeting(s)

Agenda

Time	Item	Who	Notes

Time	Item	Who	Notes
5 min	Roll call	@Peter Monks
5 min	Review action items from last meeting(s)	@Peter Monks
20 min	Update on Open Sourcing plan	@Lawrence Miller (Deactivated)	This will be a summary of what was presented at recent Foundation and LLC board meetings
15 min	Kickoff WG ontology discussion	All	Action item from the 2016-09-20 meeting. From that conversation (summarised, and with emphasis added): Frank: Perhaps the focus on the container is too narrow? - - - - - - - - 8< - - - - - - - - Have you considered the implementation of a UI component? Or is it focused on API interactions with the Symphony back end? I see this WG as being about more than just the container James: in fact one of the problems was calling it the "Desktop Wrapper WG" from the get go, while not defining either term. When I first started I couldn't tell if it was about the container or the APIs. Frank: my recommendation would be to revisit the charter of this group. And change the "desktop" and "APIs" - I'm not saying we merge it with the API WG that Anthony is working on, but more the "extensions API". Lawrence: it's an interesting question around how you decompose this. How do you integrate the UI elements and speak to the UI elements. They're all rendered in HTML, so when you talk about the user visible constructs, are they components of the API or are they aspects of which HTML widget libraries do you use in the HTML front end code, whether it's API related or not? Are you talking about an API or an HTML coding standard? I don't mean to complicate it, but I think it's a really good idea to try to figure out where these things should live. James: it's an ontology question, and would also help with Anthony's WG. If we're going to have WGs around Symphony, perhaps ESCo needs to define an ontology of WGs, both of the current ones and future ones. Proposed objective for this agenda item (comments welcome!): decide whether the ESCo should define a WG ontology, and if so, when and how.
5 min	AOB	@Peter Monks

Meeting notes

Didn't achieve quorum, so meeting adjourned without further discussion
Some potential upcoming conflicts:
- @Peter Monks is at a conference next Tuesday (18th). Not expected to impact ESCo secretarial duties, but will let the group know if so.
- @Michael Harmon & @Lawrence Miller (Deactivated) have some upcoming travel, either next week (18th) or the following week (25th) - will let the group know so meetings can be re-scheduled if needed.

Action items

@Peter Monks to let the group know if his conference attendance will impact the weekly ESCo call

@Michael Harmon to let the group know once his & @Lawrence Miller (Deactivated)'s upcoming travel plans are finalised

@Peter Monks to reschedule ESCo meetings, if necessary

2016-10-11 - ESCo - Meeting agenda/minutes

Table of Contents