Table of Contents

Date

18 Oct 2016

Attendees

Actions items from previous meeting

Agenda

Meeting notes

• A vote was conducted between October 11-13, with the motion to approve the proposed Charter.  A representative from each of the nine participating companies was asked to vote Yes/No or Abstain.  Anthony shared the voting results; 6 Yes, 1 No, 2 Absent.   The result is that motion was passed and the proposed charter was approved by the Working Group members
• Anthony shared the next steps; we are required to present the charter to ESCo for ratification. We are currently on their November 1 agenda. If ratified, then we can publically organize and begin work.
• Paul T from Symphony LLC informed the group that the LLC was the single No vote. He elaborated that there are two objectives within the charter – the first being a set of guidelines and standards on API design. The second on functional requirements for APIs. The LLC supports the first objective, but remains opposed to the second objective. Below is the position he sent pertaining to the LLC's vote (email also attached.)

  • As a basic underlying principle, we view product governance at the foundation level as closely interrelated to code contributions, and would expect to see code contribution as an integral part of functional product governance.  The underlying code implementing Symphony's APIs has not yet been contributed to the Foundation and there is not yet a governance process for the evolution of that codebase. Once the code is contributed, there will be a governance process established for that code.  The second objective therefore is likely to conflict with this code governance process.  While we do not object to the working group making functional feedback informally, placement in a charter is likely to result in a conflict and therefore we are unable to support this motion

• Anthony also acknowledged the dependency on the second objective to have code available to review. This situation as it relates to the timing and effective benefit of the second objective will be made visible to the ESCo when presenting the charter for ratification.

Next Meeting will depend on the ratification result by the ESCo. Presuming a successful ratification, then a kick off meeting would be held shortly there after to setup the meeting frequencies, roles and work streams.

Action items

• @Anthony to share the ESCo result by email, following the ratification meeting. If approved by the ESCo, then create a formal kickoff meeting.