workinggroups/content/en_eclipse_cloud_development_charter.php - www.eclipse.org/org - Git at Google


 <div id="maincontent">
   <div id="midcolumn">
     <h1><?php print $pageTitle; ?></h1>
     <p>Version v1.5. Revision history is at end of document.</p>
     <h2>Scope, Goals&nbsp;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
       developer workspace definition. In addition, the group explores the impacts and optimizations
       for running developer tools in a cloud environment, including scale out / scale-to-zero
       execution of compute-intensive tasks like CI and testing.</p>
     <p>The working group:</p>
     <ul>
       <li>Engages with the Eclipse and broader developer community to ensure broad adoption of
         emerging standards for cloud-based developer tools</li>
       <li>Coordinates interoperability work on Language Server Protocol&nbsp;(LSP), Debug Adapter
         Protocol&nbsp;(DAP), and other developer tool protocols (workspace lifecycle management,
         source control, continuous integration infrastructure, user management, etc), and propose
         evolutions to these protocols for additional use-cases</li>
       <li>Defines requirements for running developer workspaces, including runtime environments and
         developer tools, in a Cloud Development Environment</li>
       <li>Promotes the adoption of developer tool plugins, and plugin marketplaces to Eclipse Cloud Developer projects</li>
       <li>Collaborates on the joint promotion of standards adoption among Eclipse Cloud Developer
         projects</li>
     </ul>
     <p>The Eclipse Cloud Development Tools Working Group (ECD WG) accelerates the adoption of Cloud
       IDE and container-based workspace management, through the adoption of standards, the
       engagement with 3rd party developer tool providers, and through the promotion of Eclipse
       projects to cloud developers.</p>
     <h2>Definitions</h2>
     <p>
       <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>
     <p>
       <strong>Web IDE</strong>
     </p>
     <p>Is an Integrated Development Environment whose front-end can run in a web browser.</p>
     <p>
       <strong>Cloud Developer Workspace and IDE</strong>
     </p>
     <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>
     </p>
     <p>Is a mechanism for composing and managing a complete developer&rsquo;s environment, including
       source code, language run-times and libraries, and developer tools, including debuggers,
       profilers, and other developer tools, in containers, deployed and managed on a cloud platform.</p>
     <p>
       <strong>Rapid Application Development (RAD)</strong>
     </p>
     <p>Is an approach for adaptive software development focused on increasing productivity during
       the development process and to shorten the time to market for ready to use solutions.
       Techniques such as modelling of business processes, domain models, generation by templates,
       data-driven accelerators, DSLs, No-Code/Low-Code tooling, etc. in the Cloud context falls in
       this category and are also in scope for the ECD WG.</p>
     <p>
       <strong>Eclipse Members</strong>
     </p>
     <p>
       Eclipse Members have signed the Eclipse Membership Agreement and are in good standing. For a
       complete overview over the Eclipse Membership process and the current Eclipse members refer to
       the<a href="https://eclipse.org/membership">&nbsp;Eclipse Membership Page.</a>
     </p>
     <p>
       <strong>ECD&nbsp;WG Participants</strong>
     </p>
     <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>
     </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>
     <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>Membership</h2>
     <p>An entity must have executed the ECD WG Participation Agreement once defined, and adhere to
       the requirements set forth in this Charter to participate. Every entity must be at least an
       Eclipse Solutions member, with the exception of Guest Members which may be Associate members
       of the Eclipse Foundation</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>At its creation, there will be no fees associated with membership in the working group for
       2019. One of the initial tasks of the governing body of the group will be to define a fee
       structure and budget which will allow the working group to execute on its objectives in 2020
       and beyond.</p>
     <p>In addition, all matters related to Membership in the Eclipse Foundation and this ECD working
       group are governed by the Eclipse Foundation Bylaws, Eclipse Membership Agreement and Eclipse
       Working Group Process. These matters include, without limitation, delinquency, payment of
       dues, termination, resignation, reinstatement, and assignment.</p>
     <table class="table">
       <thead>
         <tr>
           <td colspan="1" rowspan="1">
             <p>Committee Representation</p>
           </td>
           <td colspan="1" rowspan="1">
             <p>Strategic Participant</p>
           </td>
           <td colspan="1" rowspan="1">
             <p>Participant Participant</p>
           </td>
           <td colspan="1" rowspan="1">
             <p>Guest Participant</p>
           </td>
         </tr>
       </thead>
       <tbody>
         <tr>
           <td colspan="1" rowspan="1">
             <p>Steering Committee</p>
           </td>
           <td colspan="1" rowspan="1">
             <p>Appointed</p>
           </td>
           <td colspan="1" rowspan="1">
             <p>Elected</p>
           </td>
           <td colspan="1" rowspan="1">
             <p>N/A</p>
           </td>
         </tr>
         <tr>
           <td colspan="1" rowspan="1">
             <p>Marketing and Brand Committee</p>
           </td>
           <td colspan="1" rowspan="1">
             <p>Appointed</p>
           </td>
           <td colspan="1" rowspan="1">
             <p>Elected</p>
           </td>
           <td colspan="1" rowspan="1">
             <p>N/A</p>
           </td>
         </tr>
       </tbody>
     </table>
     <p>Participants who resign, or otherwise terminate their participation in the working group,
       lose their rights to access and use any private assets and data of the working group after the
       effective date of the termination.</p>
     <h3>Strategic Member</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>
     <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&amp;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>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 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 budget and fees for all classes of working group membership each year.</li>
       <li>Invite Guest members to participate in the working group.</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
         Bylaws.</li>
     </ul>
     <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>
     </ul>
     <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
         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>
     </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 terms
       set forth in Section 6 of the Eclipse Foundation Bylaws apply.</p>
     <h3>Meeting frequency</h3>
     <p>Each&nbsp;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 thirty (30) 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 as set forth
       in Section Voting above.</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>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, Specification 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 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. As an exception, in 2019, elected
       representatives shall serve from the date of elections until June 30, 2020. 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>
     <ul>
       <li><a href="https://www.eclipse.org/org/documents/eclipse_foundation-bylaws.pdf">Eclipse
           Bylaws</a></li>
       <li><a href="https://www.eclipse.org/org/workinggroups/industry_wg_process.php">Industry
           Working Group Process</a></li>
       <li><a
         href="https://www.eclipse.org/org/documents/2018-01_Eclipse_MEMBERSHIP_AGMT.pdf"
       >Eclipse Membership Agreement</a></li>
       <li><a href="https://www.eclipse.org/org/documents/Eclipse_IP_Policy.pdf">Eclipse Intellectual
           Property Policy</a></li>
       <li><a href="https://www.eclipse.org/org/documents/Eclipse_Antitrust_Policy.pdf">Eclipse
           Antitrust Policy</a></li>
       <li><a href="https://www.eclipse.org/projects/dev_process/development_process.php">Eclipse
           Development Process</a></li>
     </ul>
     <p>All Members must be parties to the Eclipse Foundation Membership Agreement, including the
       requirement set forth in Section 2.2 to follow 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, Eclipse Development Process, Eclipse
       Industry 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 Fees</h3>
     <p>In 2019 the fees will be $ 0. The initial Steering Committee will be tasked with defining a
       fee structure and budget for following years, starting with calendar year 2020, based on
       resource requirements to achieve the objectives of the group. Members agree to pay the annual
       fees as established by the Steering Committee.</p>
     <h3>Eclipse Cloud Development Tools Working Group Annual Participation Fees Schedule A</h3>
     <p>Beginning in 2020, 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.&nbsp; Strategic members are required to commit to three (3) years of
       Participation Membership.</p>
     <table class="table table-stripped" cellspacing="0">
       <thead>
         <tr>
           <th width="80%">Corporate Revenue</th>
           <th class="text-center" width="20%">Annual Fees&nbsp;
           </th>
       </thead>
       <tbody>
         <tr>
           <td>Annual Corporate Revenues greater than $1&nbsp;billion&nbsp;</td>
           <td class="text-center">$100,000</td>
         </tr>
         <tr>
           <td>Annual Corporate Revenues greater than $500 million but less than or equal to $1&nbsp;billion&nbsp;</td>
           <td class="text-center">$60,000</td>
         </tr>
         <tr>
           <td>Annual Corporate Revenues greater than $100 million but less than or equal to $500&nbsp;million&nbsp;</td>
           <td class="text-center">$25,000</td>
         </tr>
         <tr>
           <td>Annual Corporate Revenues greater than $10 million but less than or equal to $100&nbsp;million&nbsp;</td>
           <td class="text-center">$15,000</td>
         </tr>
         <tr>
           <td>Annual Corporate Revenues less than or equal to $10&nbsp;million</td>
           <td class="text-center">$7,500</td>
         </tr>
       </tbody>
     </table>
     <h4>Participation Member Annual Participation Fees</h4>
     <p>Participant Members are required to execute the Eclipse Cloud&nbsp; Development Participation
       Agreement.</p>
     <table class="table table-stripped" cellspacing="0">
       <thead>
         <tr>
           <th width="80%">Corporate Revenue</th>
           <th class="text-center" width="20%">Annual Fees&nbsp;
           </th>
         </tr>
       </thead>
       <tbody>
         <tr>
           <td>Annual Corporate Revenues greater than $1&nbsp;billion</td>
           <td class="text-center">$15,000</td>
         </tr>
         <tr>
           <td>Annual Corporate Revenues greater than $500 million but less than or equal to $1&nbsp;billion</td>
           <td class="text-center">$10,000</td>
         </tr>
         <tr>
           <td>Annual Corporate Revenues greater than $100 million but less than or equal to $500&nbsp;million</td>
           <td class="text-center">$7,500&nbsp;</td>
         </tr>
         <tr>
           <td>Annual Corporate Revenues less than or equal to $100&nbsp;million</td>
           <td class="text-center">$2,000</td>
         </tr>
       </tbody>
     </table>
     <p>Guest members pay no WG Participation Fees.</p>
     <p><strong>Version History</strong></p>
       <p>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>

   </div>
 </div>

	<div id="maincontent">
	<div id="midcolumn">
	<h1><?php print $pageTitle; ?></h1>
	<p>Version v1.5. 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
	developer workspace definition. In addition, the group explores the impacts and optimizations
	for running developer tools in a cloud environment, including scale out / scale-to-zero
	execution of compute-intensive tasks like CI and testing.</p>
	<p>The working group:</p>
	<ul>
	<li>Engages with the Eclipse and broader developer community to ensure broad adoption of
	emerging standards for cloud-based developer tools</li>
	<li>Coordinates interoperability work on Language Server Protocol (LSP), Debug Adapter
	Protocol (DAP), and other developer tool protocols (workspace lifecycle management,
	source control, continuous integration infrastructure, user management, etc), and propose
	evolutions to these protocols for additional use-cases</li>
	<li>Defines requirements for running developer workspaces, including runtime environments and
	developer tools, in a Cloud Development Environment</li>
	<li>Promotes the adoption of developer tool plugins, and plugin marketplaces to Eclipse Cloud Developer projects</li>
	<li>Collaborates on the joint promotion of standards adoption among Eclipse Cloud Developer
	projects</li>
	</ul>
	<p>The Eclipse Cloud Development Tools Working Group (ECD WG) accelerates the adoption of Cloud
	IDE and container-based workspace management, through the adoption of standards, the
	engagement with 3rd party developer tool providers, and through the promotion of Eclipse
	projects to cloud developers.</p>
	<h2>Definitions</h2>
	<p>
	<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>
	<p>
	<strong>Web IDE</strong>
	</p>
	<p>Is an Integrated Development Environment whose front-end can run in a web browser.</p>
	<p>
	<strong>Cloud Developer Workspace and IDE</strong>
	</p>
	<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>
	</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,
	profilers, and other developer tools, in containers, deployed and managed on a cloud platform.</p>
	<p>
	<strong>Rapid Application Development (RAD)</strong>
	</p>
	<p>Is an approach for adaptive software development focused on increasing productivity during
	the development process and to shorten the time to market for ready to use solutions.
	Techniques such as modelling of business processes, domain models, generation by templates,
	data-driven accelerators, DSLs, No-Code/Low-Code tooling, etc. in the Cloud context falls in
	this category and are also in scope for the ECD WG.</p>
	<p>
	<strong>Eclipse Members</strong>
	</p>
	<p>
	Eclipse Members have signed the Eclipse Membership Agreement and are in good standing. For a
	complete overview over the Eclipse Membership process and the current Eclipse members refer to
	the<a href="https://eclipse.org/membership"> Eclipse Membership Page.</a>
	</p>
	<p>
	<strong>ECD WG Participants</strong>
	</p>
	<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>
	</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>
	<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>Membership</h2>
	<p>An entity must have executed the ECD WG Participation Agreement once defined, and adhere to
	the requirements set forth in this Charter to participate. Every entity must be at least an
	Eclipse Solutions member, with the exception of Guest Members which may be Associate members
	of the Eclipse Foundation</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>At its creation, there will be no fees associated with membership in the working group for
	2019. One of the initial tasks of the governing body of the group will be to define a fee
	structure and budget which will allow the working group to execute on its objectives in 2020
	and beyond.</p>
	<p>In addition, all matters related to Membership in the Eclipse Foundation and this ECD working
	group are governed by the Eclipse Foundation Bylaws, Eclipse Membership Agreement and Eclipse
	Working Group Process. These matters include, without limitation, delinquency, payment of
	dues, termination, resignation, reinstatement, and assignment.</p>
	<table class="table">
	<thead>
	<tr>
	<td colspan="1" rowspan="1">
	<p>Committee Representation</p>
	</td>
	<td colspan="1" rowspan="1">
	<p>Strategic Participant</p>
	</td>
	<td colspan="1" rowspan="1">
	<p>Participant Participant</p>
	</td>
	<td colspan="1" rowspan="1">
	<p>Guest Participant</p>
	</td>
	</tr>
	</thead>
	<tbody>
	<tr>
	<td colspan="1" rowspan="1">
	<p>Steering Committee</p>
	</td>
	<td colspan="1" rowspan="1">
	<p>Appointed</p>
	</td>
	<td colspan="1" rowspan="1">
	<p>Elected</p>
	</td>
	<td colspan="1" rowspan="1">
	<p>N/A</p>
	</td>
	</tr>
	<tr>
	<td colspan="1" rowspan="1">
	<p>Marketing and Brand Committee</p>
	</td>
	<td colspan="1" rowspan="1">
	<p>Appointed</p>
	</td>
	<td colspan="1" rowspan="1">
	<p>Elected</p>
	</td>
	<td colspan="1" rowspan="1">
	<p>N/A</p>
	</td>
	</tr>
	</tbody>
	</table>
	<p>Participants who resign, or otherwise terminate their participation in the working group,
	lose their rights to access and use any private assets and data of the working group after the
	effective date of the termination.</p>
	<h3>Strategic Member</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>
	<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>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 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 budget and fees for all classes of working group membership each year.</li>
	<li>Invite Guest members to participate in the working group.</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
	Bylaws.</li>
	</ul>
	<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>
	</ul>
	<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
	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>
	</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 terms
	set forth in Section 6 of the Eclipse Foundation Bylaws apply.</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 thirty (30) 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 as set forth
	in Section Voting above.</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>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, Specification 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 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. As an exception, in 2019, elected
	representatives shall serve from the date of elections until June 30, 2020. 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>
	<ul>
	<li><a href="https://www.eclipse.org/org/documents/eclipse_foundation-bylaws.pdf">Eclipse
	Bylaws</a></li>
	<li><a href="https://www.eclipse.org/org/workinggroups/industry_wg_process.php">Industry
	Working Group Process</a></li>
	<li><a
	href="https://www.eclipse.org/org/documents/2018-01_Eclipse_MEMBERSHIP_AGMT.pdf"
	>Eclipse Membership Agreement</a></li>
	<li><a href="https://www.eclipse.org/org/documents/Eclipse_IP_Policy.pdf">Eclipse Intellectual
	Property Policy</a></li>
	<li><a href="https://www.eclipse.org/org/documents/Eclipse_Antitrust_Policy.pdf">Eclipse
	Antitrust Policy</a></li>
	<li><a href="https://www.eclipse.org/projects/dev_process/development_process.php">Eclipse
	Development Process</a></li>
	</ul>
	<p>All Members must be parties to the Eclipse Foundation Membership Agreement, including the
	requirement set forth in Section 2.2 to follow 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, Eclipse Development Process, Eclipse
	Industry 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 Fees</h3>
	<p>In 2019 the fees will be $ 0. The initial Steering Committee will be tasked with defining a
	fee structure and budget for following years, starting with calendar year 2020, based on
	resource requirements to achieve the objectives of the group. Members agree to pay the annual
	fees as established by the Steering Committee.</p>
	<h3>Eclipse Cloud Development Tools Working Group Annual Participation Fees Schedule A</h3>
	<p>Beginning in 2020, 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>
	<table class="table table-stripped" cellspacing="0">
	<thead>
	<tr>
	<th width="80%">Corporate Revenue</th>
	<th class="text-center" width="20%">Annual Fees
	</th>
	</thead>
	<tbody>
	<tr>
	<td>Annual Corporate Revenues greater than $1 billion </td>
	<td class="text-center">$100,000</td>
	</tr>
	<tr>
	<td>Annual Corporate Revenues greater than $500 million but less than or equal to $1 billion </td>
	<td class="text-center">$60,000</td>
	</tr>
	<tr>
	<td>Annual Corporate Revenues greater than $100 million but less than or equal to $500 million </td>
	<td class="text-center">$25,000</td>
	</tr>
	<tr>
	<td>Annual Corporate Revenues greater than $10 million but less than or equal to $100 million </td>
	<td class="text-center">$15,000</td>
	</tr>
	<tr>
	<td>Annual Corporate Revenues less than or equal to $10 million</td>
	<td class="text-center">$7,500</td>
	</tr>
	</tbody>
	</table>
	<h4>Participation Member Annual Participation Fees</h4>
	<p>Participant Members are required to execute the Eclipse Cloud  Development Participation
	Agreement.</p>
	<table class="table table-stripped" cellspacing="0">
	<thead>
	<tr>
	<th width="80%">Corporate Revenue</th>
	<th class="text-center" width="20%">Annual Fees
	</th>
	</tr>
	</thead>
	<tbody>
	<tr>
	<td>Annual Corporate Revenues greater than $1 billion</td>
	<td class="text-center">$15,000</td>
	</tr>
	<tr>
	<td>Annual Corporate Revenues greater than $500 million but less than or equal to $1 billion</td>
	<td class="text-center">$10,000</td>
	</tr>
	<tr>
	<td>Annual Corporate Revenues greater than $100 million but less than or equal to $500 million</td>
	<td class="text-center">$7,500 </td>
	</tr>
	<tr>
	<td>Annual Corporate Revenues less than or equal to $100 million</td>
	<td class="text-center">$2,000</td>
	</tr>
	</tbody>
	</table>
	<p>Guest members pay no WG Participation Fees.</p>
	<p><strong>Version History</strong></p>
	<p>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>

	</div>
	</div>