The Foundation's members organize Working Groups as needed to address specific technical and industry issues affecting the Foundation's work and to provide guidance to the Engineering Steering Committee and to Foundation projects in the form of best practice guides, roadmap recommendations, and position papers.
Each Working Group operates within the scope of a charter that the group itself creates while incubating. These Working Group charters primarily look to influence and produce artefacts that are within the scope of the Foundation (e.g. standards and best practices for use by Foundation-hosted projects), or are of primary interest to the Foundation. While influencing and providing input to Symphony Communication Services LLC's closed-source product development is expected to form part of the work of a Working Group, charters should try to avoid relying entirely on influencing the LLC to deliver their goals.
Table of Contents
|Table of Contents|
Existing Working Groups
|Financial Objects Standardization||Working Group - Financial Objects Standardization||Active|
|Desktop / Wrapper API||Working Group - Desktop Wrapper API||Active|
|API||Working Group - API|
|Open Source Readiness||N/A|
Formation of a Working Group
The following participants are required for the formation of a Working Group:
|Board Sponsor(s)||At least one||Ensure sponsorship and visibility, but also alignment between Working Group proceedings and the Foundation strategy.|
|Chairs||Two||A chairperson responsible for running the Working Group, ensuring progress, reporting periodically to the ESCo, and liaising with Projects and Members. A co-chair to serve as secretary at Working Group meetings and to act as chair when the chair is unavailable.|
|Members||At least two||Individuals actively participating to Working Groups proceedings.|
|Participation in Working Groups is voluntary and restricted to Foundation Members.|
- Gauge interest among other members. The more support there is for the idea, the more likely it is that the Working Group proposal will be approved. Usually, this process begins with a discussion on the email@example.com list. Follow instructions on the Get in touch page to join the list. Begin looking for members that are willing to fill the required roles (Board Sponsor, Chair, Members) listed in the section above.
- Create a Working Group issue in the WG Jira project. See the Financial Objects Standardization group for an example. Be sure to include:
- A proposed charter for the Working group
- Objectives and tangible deliverables
- A list of proposed initial participants, including members, co-chairs, a secretary, and a Board sponsor. (Alternatively, ask members to propose themselves for these roles by editing the description or adding a comment.)
- The Engineering Steering Committee will review the proposal for validity and completeness and will hold a vote. The ESCo may approve or reject the proposal, or may ask the organizer(s) to provide additional information or make changes to the proposed charter. If the proposal is rejected, the ESCo will provide reasons for its decision.
- If the group is approved, the Foundation will create a wiki space to allow collaboration. If required, a JIRA project can be created to support project management of the Working Group.
Meetings and decisionmaking
Working Group meetings are called and run by the group's chair (or co-chair). Working Groups are encouraged to operate by consensus, but are required to adopt an explicit governance model for non-consensus action. Each Working Group is free to determine its own governance model, but the Foundation recommends adopting the ESCo Foundation's voting rules.
After a Working Group is approved by the ESCo, the Working Group will determine its own process and criteria for admitting new members. Admissions need not be approved by the ESCo, but will be reported to the ESCo from time to time. The ESCo will resolve any disputes within Working Groups regarding admission of members. Only Foundation members are eligible to participate in Working Groups, except upon specific approval of the ESCo.
Reporting and Deliverables
Working Groups are required to report quarterly to the ESCo on their progress. Working Group deliverables (draft specifications, recommendations, etc.) should be presented to the ESCo upon completion.
Coordination with Projects
Working Groups are expected to coordinate with Projects as needed to ensure that Projects' work is aligned with Working Group deliverables (e.g. best practices).
Working Groups are encouraged to use their wiki space to organize and to publish meeting minutes, work product, etc. To track progress on an individual deliverable, the chair can create an INFRA issue in JIRA and assign tasks to Working Group members.
The concepts described in this page and its sub-pages were ratified by the ESCo when it approved a package of governance refinements on 2016-12-01 that clarified a number of missing or poorly defined details.