Infra594 - Updated Cloud Dev Tools Working Group Charter to 1.7 and WGPA
Signed-off-by: Zhou Fang <zhou.fang@eclipse-foundation.org>
Change-Id: I4e5853a583a11c38f94935d43402a4f573c5c501
diff --git a/workinggroups/content/en_eclipse_cloud_development_charter.php b/workinggroups/content/en_eclipse_cloud_development_charter.php
index f172e81..407a4cc 100644
--- a/workinggroups/content/en_eclipse_cloud_development_charter.php
+++ b/workinggroups/content/en_eclipse_cloud_development_charter.php
@@ -1,8 +1,7 @@
-
<div id="maincontent">
<div id="midcolumn">
<h1><?php print $pageTitle; ?></h1>
- <p>Version 1.6 Revision history is at end of document.</p>
+ <p>Version 1.7 Revision history is at end of document.</p>
<h2>Scope, Goals and Vision</h2>
<p>The Eclipse Cloud Development Tools Working Group drives the evolution and broad adoption of
de facto standards for cloud development tools, including language support, extensions, and
@@ -32,9 +31,7 @@
<strong>Eclipse Cloud Development</strong>
</p>
<p>Is an Eclipse top-level project, with a focus on developing applications for and in the
- cloud. Eclipse Cloud Development member projects includes: Che, Theia, Dirigible, CodeWind,
- Sprotty, Eclipse Tools for CloudFoundry, Flux, Orion, and Winery. Additional projects may be
- added by the Steering Committee at its discretion.</p>
+ cloud.</p>
<p>
<strong>Web IDE</strong>
</p>
@@ -45,7 +42,7 @@
<p>Is a complete IDE, including developer run-time and developer tools, which runs entirely in a
cloud environment.</p>
<p>
- <strong>Workspace management solution</strong>
+ <strong>Workspace Management Solution</strong>
</p>
<p>Is a mechanism for composing and managing a complete developer’s environment, including
source code, language run-times and libraries, and developer tools, including debuggers,
@@ -72,36 +69,99 @@
<p>ECD WG participants have signed the ECD WG Participation Agreement and have fulfilled the
requirements as stated in the WG Participation Agreement.</p>
<p>
- <strong>ECD WG deliverables and results</strong>
+ <strong>ECD WG Deliverables and Results</strong>
</p>
<p>The services and goods (software, documents, marketing plans and collateral, etc.) to be
delivered hereunder are referred to in this document as ECD WG deliverables and results.</p>
- <h2>Governance</h2>
- <p>The Eclipse Cloud Development Tools working group is designed as:</p>
+ <h2>Governance and Precedence</h2>
+ <h3>Applicable Documents</h3>
+ <p>
+ The following governance documents are applicable to this charter, each of which can be found
+ on the <a href="/org/documents">Eclipse Foundation Governance Documents page</a>
+ or the <a href="/legal">Eclipse Foundation Legal Resources page</a>:
+ </p>
<ul>
- <li>a member driven organization, led by its strategic members,</li>
- <li>a means to foster a vibrant and sustainable ecosystem of users, contributors and service
- providers,</li>
- <li>a means to organize the community of each project or component so that strategic users and
- developers define the roadmap collaboratively.</li>
+ <li>Eclipse Foundation Bylaws</li>
+ <li>Eclipse Foundation Working Group Process</li>
+ <li>Eclipse Foundation Working Group Operations Guide</li>
+ <li>Eclipse Foundation Code of Conduct</li>
+ <li>Eclipse Foundation Communication Channel Guidelines</li>
+ <li>Eclipse Foundation Membership Agreement</li>
+ <li>Eclipse Foundation Intellectual Property Policy</li>
+ <li>Eclipse Foundation Antitrust Policy</li>
+ <li>Eclipse Foundation Development Process</li>
+ <li>Eclipse Foundation Trademark Usage Guidelines</li>
</ul>
- <p>In order to implement these principles, the following governance bodies have been defined
- (each a "Body"):</p>
- <ul>
- <li>The Steering Committee</li>
- <li>The Marketing and Brand Committee</li>
- </ul>
+ <p>
+ All Members must be parties to the Eclipse Foundation Membership Agreement, including the
+ requirement set forth in Section 2.2 to abide by and adhere to the Bylaws and then-current
+ policies of the Eclipse Foundation, including but not limited to the Intellectual Property and
+ Antitrust Policies.
+ </p>
+ <p>
+ In the event of any conflict between the terms set forth in this Working Group's Charter
+ and the Eclipse Foundation Bylaws, Membership Agreement, Development Process, Working
+ Group Process, or any policies of the Eclipse Foundation, the terms of the Eclipse Foundation
+ Bylaws, Membership Agreement, process, or policy shall take precedence.
+ </p>
<h2>Membership</h2>
- <p>An entity must have executed the ECD WG Participation Agreement, and adhere to
- the requirements set forth in this Charter to participate. Every entity must be at least an
- Eclipse Contributing member, with the exception of Guest Members which may be Associate members
- of the Eclipse Foundation</p>
+ <p>
+ With the exception of Guest members as described
+ below, an entity must be at least a Contributing Member
+ of the Eclipse Foundation, have executed the Eclipse
+ Cloud Development Tools Working Group Participation
+ and adhere to the requirements
+ set forth in this Charter to participate.
+ </p>
+ <p>
+ The participation fees associated with each of these
+ membership classes are shown in the Annual
+ Participation Fees section. These are annual fees, and are
+ established by the Eclipse Cloud Development Tools
+ Working Group Steering Committee, and will be updated
+ in this charter document accordingly.
+ </p>
+ <p>
+ The fees associated with membership in the Eclipse
+ Foundation are separate from any Working Group
+ membership fees, and are decided as described in the
+ Eclipse Foundation Bylaws and detailed in the Eclipse
+ Foundation Membership Agreement.
+ </p>
<p>There are three classes of ECD WG membership - Strategic, Participant, and Guest. Each of
these classes is described in detail below.</p>
- <p>All matters related to Membership in the Eclipse Foundation and this ECD working
- group are governed by the Eclipse Foundation Bylaws, Membership Agreement and
- Working Group Process. These matters include, without limitation, delinquency, payment of
- dues, termination, resignation, reinstatement, and assignment.</p>
+ <h3>Classes of Membership</h3>
+ <h4>Strategic Members</h4>
+ <p>Strategic Members want to influence the definition and further development of the relevant
+ standards being adopted and promoted by ECD projects, as well as all of the deliverables of
+ the ECD WG.</p>
+ <p>
+ They are members of the Steering Committee and invest an essential amount of resources to
+ sustain the WG activities. Typically Strategic Members include users of the technologies and
+ results provided by the ECD WG. Most of them use one of the ECD projects as the basis for a
+ commercial product. Strategic Members of this working group must be at least a Contributing
+ Member of the Eclipse Foundation.
+ </p>
+
+ <h4>Participant Members</h4>
+ <p>
+ Participant Members consider interoperability and standards adoption related to ECD a
+ relevant addition to their business. They are either users of the related technology and
+ service offerings or they are interested in adoption, extension and service provisioning for
+ one or more ECD projects. Participant Members of this working group must be at least a Contributing
+ Member of the Eclipse Foundation.
+ </p>
+ <h4>Guest Members</h4>
+ <p>
+ Guest Members are organizations which are Associate members of the
+ Eclipse Foundation. Typical guests include R&D partners, universities,
+ academic research centers, etc. Guests may be invited to participate in
+ committee meetings at the invitation of the respective committee, but
+ under no circumstances do Guest members have voting rights. Guest
+ members are required to execute the Working Group's Participation
+ Agreement.
+ </p>
+ <h3>Membership Summary</h3>
<table class="table">
<thead>
<tr>
@@ -151,152 +211,208 @@
</tbody>
</table>
- <h3>Strategic Members</h3>
- <p>Strategic Members want to influence the definition and further development of the relevant
- standards being adopted and promoted by ECD projects, as well as all of the deliverables of
- the ECD WG.</p>
- <p>They are members of the Steering Committee and invest an essential amount of resources to
- sustain the WG activities. Typically Strategic Members include users of the technologies and
- results provided by the ECD WG. Most of them use one of the ECD projects as the basis for a
- commercial product.</p>
- <p>Strategic Members of the ECD working group are required to commit to strategic membership for a three (3) year period.</p>
-
- <h3>Participant Members</h3>
- <p>Participant Members consider interoperability and standards adoption related to ECD a
- relevant addition to their business. They are either users of the related technology and
- service offerings or they are interested in adoption, extension and service provisioning for
- one or more ECD projects.</p>
- <h3>Guest Members</h3>
- <p>Guests are organizations who have been invited for one year by the ECD WG Steering Committee
- to participate in particular aspects of the activities of the Working Group. Typically guests
- include R&D partners, Universities and academic research centers. Guest membership is
- free of charge and invitations may be renewed once by the Steering Committee. Guests are
- required to sign an Eclipse and ECD WG Membership Agreement, but when participating in
- meetings of an ECD body, they have no voting rights.</p>
+ <h2>Special Interest Groups</h2>
+ <p>
+ A Special Interest Group (SIG) is a lightweight structure formed within the Working Group with a
+ focus to collaborate around a particular topic or domain of direct interest to the working group.
+ SIGs are designed to drive the objectives of a subset of the Members of the Working Group in
+ helping them achieve a dedicated set of goals and objectives. The scope of the SIG must be
+ consistent with the scope of the Working Group Charter.
+ </p>
+ <p>
+ The creation of a SIG requires approval of the Steering Committee. Each SIG may be either
+ temporary or a permanent structure within the working group. SIGs can be disbanded at any
+ time by self selection presenting reasons to and seek approval from the Steering Committee.
+ Steering Committees may disband a SIG at any time for being inactive or non compliant with the
+ Working Group's Charter, or by request of the SIG itself. SIGs operate as a non-governing
+ Body of the Working Group. There are no additional annual fees to Members for participation in
+ a SIG.
+ </p>
+ <h2>Sponsorship</h2>
+ <p>
+ Sponsors are companies or individuals who provide money or services to the working group on
+ an ad hoc basis to support the activities of the Working Group and its managed projects. Money
+ or services provided by sponsors are used as set forth in the working group annual budget. The
+ working group is free to determine whether and how those contributions are recognized. Under
+ no condition are sponsorship monies refunded.
+ </p>
+ <p>Sponsors need not be members of the Eclipse Foundation or of the Working Group.</p>
+
+ <h2>Governance</h2>
+ <p>The Eclipse Cloud Development Tools Working Group is designed as:</p>
+ <ul>
+ <li>a member driven organization, led by its strategic members,</li>
+ <li>a means to foster a vibrant and sustainable ecosystem of users, contributors and service providers,</li>
+ <li>a means to organize the community of each project or component so that strategic users and developers define the roadmap collaboratively.</li>
+ </ul>
+ <p>In order to implement these principles, the following governance bodies have been defined (each a "Body"):</p>
+ <ul>
+ <li>The Steering Committee</li>
+ <li>The Marketing and Brand Committee</li>
+ </ul>
+
<h2>Governing Bodies</h2>
<h3>Steering Committee</h3>
<h4>Powers and Duties</h4>
<p>Steering Committee members are required to:</p>
<ul>
<li>Define and manage the strategy of the working group.</li>
+ <li>Define and manage which Eclipse Foundation projects are included within the scope of this working group.</li>
+ <li>Ensure the consistency of logo usage and other marketing materials.</li>
<li>Define and manage the technical roadmap.</li>
<li>Review and approve this charter.</li>
<li>Review and approve any trademark policy referred to it by the Marketing and Brand
Committee.</li>
<li>Define the annual fees for all classes of working group membership.</li>
+ <li>Establish an annual program plan.</li>
<li>Approve the annual budget based upon funds received through fees.</li>
- <li>Invite Guest members to participate in the working group.</li>
+ <li>Approve the creation of subcommittees and define the purpose, scope, and membership of each such subcommittee.</li>
+ <li>Approve the creation and retirement of Special Interest Groups (SIGs)</li>
</ul>
<h4>Composition</h4>
<ul>
- <li>Each Strategic (Consumer and Developer) Member of the working group has a seat on the
- Steering Committee.</li>
- <li>At least one seat is allocated to Participant Members. Participant Member seats are
- allocated following the Eclipse "Single Transferable Vote", as defined in the Eclipse
+ <li>Each Strategic Member of the working group is entitled to a seat on the Steering Committee.</li>
+ <li>One seat is allocated to Participant Members. The Participant Member seat is
+ allocated following the Eclipse "Single Transferable Vote", as defined in the Eclipse
Bylaws.</li>
+ <li>
+ The Committee elects a chair of the Steering Committee. This chair is elected among
+ the members of the Committee. They will serve for a 12 month period or until their
+ successor is elected and qualified, or as otherwise provided for in this Charter. There is
+ no limit on the number of terms the chair may serve.
+ </li>
</ul>
+ <h4>Meeting Management</h4>
+ <p>The Steering Committee meets at least twice a year.</p>
+ <p>
+ As prescribed in the Eclipse Foundation Working Group Process, all meetings related to the
+ working group will follow a prepared agenda and minutes are distributed two weeks after the
+ meeting and approved at the next meeting at the latest, and shall in general conform to the
+ Eclipse Foundation Antitrust Policy.
+ </p>
+
<h3>Marketing and Brand Committee</h3>
<h4>Powers and Duties</h4>
<p>The Marketing and Brand Committee members are required to:</p>
<ul>
- <li>Define and execute the marketing strategy for the working group</li>
- <li>Define and implement marketing and communication activities for the working group</li>
- <li>Define and implement developer and end user outreach programs</li>
- <li>Provide requirements to the Eclipse Foundation for conferences and events related to the
- ECD WG</li>
- <li>Define the trademark policy, if applicable, and refer to it for approval by the Steering
- Committee.</li>
- <li>Ensure the consistency of logo usage and other marketing materials</li>
+ <li>Define strategic marketing priorities, goals, and objectives for the working group.</li>
+ <li>Coordinate and support the implementation of developer and end-user outreach programs.</li>
+ <li>Raise issues for discussion and provide feedback to the Foundation on the execution of marketing, brand, and communications activities for the working group.</li>
+ <li>Assist the Eclipse Foundation in the working group's participation in conferences and events related to the working group.</li>
+ <li>Define the trademark policy, if applicable, and refer to it for approval by the Steering Committee.</li>
+ <li>Collaborate with other working group members to develop co-marketing strategies, amplify messaging on social channels, and share best practices.</li>
</ul>
+ <p>
+ Committee members are expected to be leaders in communicating key messaging on behalf of
+ the working group, and to play a leadership role in driving the overall success of the working
+ group marketing efforts. In particular, members are encouraged to engage their respective
+ marketing teams and personnel to amplify and support the achievement of the working group's
+ goals and objectives.
+ </p>
<h4>Composition</h4>
<ul>
- <li>Each Strategic Member of the working group has a seat on the Marketing Committee.</li>
- <li>At least one seat is allocated to Participant Members. Participant Member seats are
+ <li>Each Strategic Member of the working group is entitled to a seat on the Marketing Committee.</li>
+ <li>One seat is allocated to Participant Members. The Participant Member seat is
allocated following the Eclipse "Single Transferable Vote", as defined in the Eclipse
Bylaws.</li>
<li>The Committee elects a chair who reports to the Steering Committee. This chair is elected
- among the members of the Committee. They will serve from April 1 to March 31 of each
- calendar year, or until their successor is elected and qualified, or as otherwise provided
- for in this Charter.</li>
+ among the members of the Committee. They will serve for a 12 month period, or until their successor
+ is elected and qualified, or as otherwise provided for in this Charter.</li>
</ul>
- <h2>Meeting Management</h2>
- <h3>Common Dispositions</h3>
- <p>For all matters related to membership action, including without limitation: meetings, quorum,
- voting, electronic voting action without meeting, vacancy, resignation or removal, the respective terms
- set forth in the Eclipse Foundation Bylaws apply.</p>
- <h3>Meeting frequency</h3>
+ <h4>Meeting Management</h4>
+ <p>The Marketing and Brand Committee meets at least twice a year.</p>
+
+ <h2>Common Dispositions</h2>
+ <p>
+ The dispositions below apply to all governance bodies for this working group, unless otherwise
+ specified. For all matters related to membership action, including without limitation: meetings, quorum,
+ voting, vacancy, resignation or removal, the respective terms set forth in the Eclipse Foundation Bylaws apply.
+ </p>
+ <p>
+ Appointed representatives on the Body may be replaced by the Member organization they are
+ representing at any time by providing written notice to the Steering Committee. In the event a
+ Body member is unavailable to attend or participate in a meeting of the Body, they may be
+ represented by another Body member by providing written proxy to the Body's mailing list in
+ advance. As per the Eclipse Foundation Bylaws, a representative shall be immediately removed
+ from the Body upon the termination of the membership of such representative's Member
+ organization.
+ </p>
+ <h3>Voting</h3>
+ <h4>Simple Majority</h4>
+ <p>
+ Excepting the actions specified below for which a Super Majority is required, votes of the Body
+ are determined by a simple majority of the representatives represented at a committee meeting
+ at which a quorum is present.
+ </p>
+ <h4>Super Majority</h4>
+ <p>
+ For actions (i) requesting that the Eclipse Foundation Board of Directors approve a specification
+ license; (ii) approving specifications for adoption; (iii) modifying the working group charter; (iv)
+ approving or changing the name of the working group; and (v) approving changes to annual
+ Member contribution requirements; any such actions must be approved by no less than two-thirds (2/3) of the representatives represented at a committee meeting at which a quorum is
+ present.
+ </p>
+ <h3>Term and Dates of Elections</h3>
+ <p>This section only applies to the Steering Committee and the Marketing Committee.</p>
+ <p>
+ All representatives shall hold office until their respective successors are appointed or elected, as
+ applicable. There shall be no prohibition on re-election or re-designation of any representative
+ following the completion of that representative's term of office.
+ </p>
+ <h4>Strategic Members</h4>
+ <p>
+ Strategic Members Representatives shall serve in such capacity on committees until the earlier
+ of their removal by their respective appointing Member organizations or as otherwise provided
+ for in this Charter. each serve one-year terms and shall be elected to serve for a 12 month term
+ or until their respective successors are elected and qualified, or as otherwise provided for this in
+ this charter. in such capacity on committees until the earlier of their removal and replacement
+ by their respective appointing Member organization or as otherwise provided for in this Charter.
+ </p>
+ <h4>Elected Representatives</h4>
+ <p>
+ Elected representatives shall each serve one-year terms and shall be elected to serve for a 12
+ month period, or until their respective successors are elected and qualified, or as otherwise
+ provided for in this Charter. Procedures governing elections of Representatives may be
+ established pursuant to resolutions of the Steering Committee provided that such resolutions
+ are not inconsistent with any provision of this Charter.
+ </p>
+
+ <h3>Meeting Frequency</h3>
<p>Each governing body meets at least twice a year. All meetings may be held at any
place that has been designated from time-to-time by resolution of the corresponding Body. All
meetings may be held remotely using phone calls, video calls, or any other means as designated
from time-to-time by resolution of the corresponding Body.</p>
- <h3>Invitation and quorum</h3>
- <p>No Body meeting will be deemed to have been validly held unless a notice of same has been
- provided to each of the representatives in Good Standing at least fifteen (15) calendar days
- prior to such meeting, the notice should identify all potential actions to be undertaken by
- the Body at the Body meeting. No representative may be intentionally excluded from Body
- meetings and all representatives shall receive notice of the meeting as specified above;
- however, Body meetings need not be delayed or rescheduled merely because one or more of the
- representatives cannot attend or participate so long as at least a quorum of the Body (as
- defined in the Common Dispositions section) is represented at the Body meeting. Electronic
- voting shall be permitted in conjunction with any and all meetings of the Body, the subject
- matter of which requires a vote of the Body to be delayed until each such representative in
- attendance thereat has conferred with his or her respective Member organization.</p>
<h3>Place of Meetings</h3>
<p>All meetings may be held at any place that has been designated from time-to-time by
resolution of the corresponding body. All meetings may be held remotely using phone calls,
video calls, or any other means as designated from time-to-time by resolution of the
corresponding body.</p>
+ <h3>Regular Meetings</h3>
+ <p>
+ No Body meeting will be deemed to have been validly held unless a notice of same has been
+ provided to each of the representatives at least fifteen (15) calendar days prior to such meeting;
+ which notice will identify all potential actions to be undertaken by the Body at the Body meeting.
+ No representative may be intentionally excluded from Body meetings and all representatives
+ shall receive notice of the meeting as specified above; however, Body meetings need not be
+ delayed or rescheduled merely because one or more of the representatives cannot attend or
+ participate so long as at least a quorum of the Body is represented at the Body meeting.
+ </p>
<h3>Actions</h3>
<p>The body may undertake an action only if it was identified in a body meeting notice or
otherwise identified in a notice of special meeting.</p>
<h3>Invitations</h3>
<p>The body may invite any ECD WG member to any of its meetings. These invited attendees have no
right of vote.</p>
- <h3>Decisions</h3>
- <p>Decisions shall be taken by simple majority vote, unless specified otherwise. The body has a
- quorum if all representatives have properly been invited. Decisions shall be reported in
- writing. Guests do not have any voting rights.</p>
- <h3>Term and Dates of Elections</h3>
- <p>This section only applies to the Steering Committee, and the Marketing Committee.</p>
- <p>All representatives shall hold office until their respective successors are appointed or
- elected, as applicable. There shall be no prohibition on re-election or re-designation of any
- representative following the completion of that representative's term of office.</p>
- <h4>Strategic Members</h4>
- <p>Strategic Members Representatives shall serve in such capacity on committees until the
- earlier of their removal and replacement by their respective appointing Member organization or as otherwise
- provided for in this Charter.</p>
- <h4>Elected representatives</h4>
- <p>Elected representatives shall each serve one-year terms and shall be elected to serve from
- July 1 to June 30 of each calendar year, or until their respective successors are elected and
- qualified, or as otherwise provided for in this Charter. Procedures
- governing elections of Representatives may be established pursuant to resolutions of the
- Steering Committee provided that such resolutions are not inconsistent with any provision of
- this Charter.</p>
- <h3>Applicable Documents</h3>
- <p>The following governance documents are applicable to this charter, each of which can be found on the <a href="https://www.eclipse.org/org/documents/">Eclipse Foundation Governance Documents page</a> or the <a href="https://www.eclipse.org/legal/">Eclipse Foundation Legal Resources page</a>.</p>
- <ul>
- <li>Eclipse Foundation Bylaws</li>
- <li>Eclipse Foundation Working Group Process</li>
- <li>Eclipse Foundation Working Group Operations Guide</li>
- <li>Eclipse Foundation Membership Agreement</li>
- <li>Eclipse Foundation Intellectual Property Policy</li>
- <li>Eclipse Foundation Antitrust Policy</li>
- <li>Eclipse Foundation Development Process</li>
- <li>Eclipse Foundation Trademark Usage Guidelines</li>
- </ul>
- <p>All Members must be parties to the Eclipse Foundation Membership Agreement, including the
- requirement set forth in Section 2.2 to abide by and adhere to the Bylaws and then-current policies of the
- Eclipse Foundation, including but not limited to the Intellectual Property and Antitrust
- Policies.</p>
- <p>In the event of any conflict between the terms set forth in this Working Group's Charter and
- the Eclipse Foundation Bylaws, Membership Agreement, Development Process, Working Group Process, or any policies of the Eclipse Foundation, the terms of the Eclipse Foundation Bylaws, Membership Agreement, process, or policy shall take precedence.</p>
- <h3>Eclipse Cloud Development Tools Working Group Annual Participation Fees Schedule A</h3>
- <p>The annual fees have been established by the Eclipse Cloud
- Development Tools Steering Committee as follows:</p>
+ <h2>Eclipse Cloud Development Tools Working Group Fees</h2>
+ <p>
+ Established fees cannot be charged retroactively and any fee structure change will be
+ communicated to all members via the mailing list and will be charged the next time a
+ member is invoiced.
+ </p>
+ <h3>Eclipse Cloud Development Tools Working Group Annual Participation Fees - Schedule A</h3>
+ <p>The annual fees have been established by the Eclipse Cloud Development Tools Steering Committee as follows:</p>
<h4>Strategic Member Annual Participation Fees</h4>
- <p>Strategic members are required to execute the Eclipse Cloud Development
- Participation Agreement. Strategic members are required to commit to three (3) years of
- Participation Membership.</p>
+ <p>Strategic members are required to execute the Eclipse Cloud Development Working Group Participation Agreement.</p>
<table class="table table-stripped" cellspacing="0">
<thead>
<tr>
@@ -328,7 +444,7 @@
</tbody>
</table>
<h4>Participation Member Annual Participation Fees</h4>
- <p>Participant Members are required to execute the Eclipse Cloud Development Participation
+ <p>Participant Members are required to execute the Eclipse Cloud Development Working Group Participation
Agreement.</p>
<table class="table table-stripped" cellspacing="0">
<thead>
@@ -357,13 +473,19 @@
</tr>
</tbody>
</table>
- <p>Guest members pay no WG Participation Fees.</p>
- <p><strong>Version History</strong></p>
- <p>1.6 Updates in support of the Eclipse Foundation corporate restructuring<br>
- 1.5 Updates to fee schedule as per Steering Committee resolution January 23, 2020<br>
- 1.0 Ratified by ECD Tools Steering Committee October 3, 2019<br>
- Version 0.9 - Community Draft<br>
- Version 0.8 - Community Draft</p>
+ <p>
+ Guest members pay no Working Group Participation Fees, but are required to execute the Eclipse Cloud
+ Development Working Group Participation Agreement.
+ </p>
+ <p><strong>Version History</strong></p>
+ <ul>
+ <li>1.7 Removal of three year commitment for Strategic Members and other standard refinements</li>
+ <li>1.6 Updates in support of the Eclipse Foundation corporate restructuring</li>
+ <li>1.5 Updates to fee schedule as per Steering Committee resolution January 23, 2020</li>
+ <li>1.0 Ratified by ECD Tools Steering Committee October 3, 2019</li>
+ <li>Version 0.9 - Community Draft</li>
+ <li>Version 0.8 - Community Draft</li>
+ </ul>
</div>
-</div>
+</div>
\ No newline at end of file
diff --git a/workinggroups/wgpa/eclipse-cloud-development-tools-participation-agreement.pdf b/workinggroups/wgpa/eclipse-cloud-development-tools-participation-agreement.pdf
index f28b866..728053e 100644
--- a/workinggroups/wgpa/eclipse-cloud-development-tools-participation-agreement.pdf
+++ b/workinggroups/wgpa/eclipse-cloud-development-tools-participation-agreement.pdf
Binary files differ
