Infra4253-updated the iotwg charter
Signed-off-by: Zhou Fang <zhou.fang@eclipse-foundation.org>
Change-Id: I8ba5bf16e0d50b2a9ecaf552eb52f3f7cec9a80b
diff --git a/workinggroups/content/en_iotwg_charter.php b/workinggroups/content/en_iotwg_charter.php
index f5d07d2..b64ce5f 100644
--- a/workinggroups/content/en_iotwg_charter.php
+++ b/workinggroups/content/en_iotwg_charter.php
@@ -17,328 +17,373 @@
<div id="maincontent">
<div id="midcolumn">
<h1><?php print $pageTitle; ?></h1>
- <p>November, 2020 - Revision history is at end of document</p>
- <h2>Introduction to IoT</h2>
- <p>Many industry domains such as smart metering, energy management, inventory control, fleet
- management, healthcare, and security have an inherent need for technology, products and
- solutions that interface physical world events from sensors, actuators and other types of
- devices, with Enterprise and Web applications. IoT technology enables these domains,
- supporting not only the devices and device networks, but also integration with a wide range of
- enterprise middleware and Web programming models.</p>
- <p>An IoT solution is generally composed of:</p>
+ <p>Version 2.0 Revision History at End</p>
+ <h2>Mission Statement</h2>
+ <p>
+ The mission of Eclipse IoT is to provide a forum for individuals and organizations to build and promote open source software, open standards and open collaboration models needed to create a scalable, enterprise-ready and open Internet of Things.
+ </p>
+
+ <h2>Vision</h2>
+ <p>
+ The main objective of the Eclipse IoT Working group is to encourage, develop, and promote open source solutions that will be able to compete successfully in challenging and fragmented markets of IoT ecosystems all around the globe. For this the working group aims for:
+ </p>
<ul>
- <li />
- <p>Physical assets and devices (sensors, actuators, controllers, LCD display, etc.)</p>
- <li />
- <p>IoT Gateway to manage assets and server communication. These include communication modules
- with wireless connectivity (GPRS, 3G, WiFi, Wimax, etc.)</p>
- <li />
- <p>Monitoring or other domain-specific server infrastructure, with which gateways,
- communication modules and assets in the field communicate.</p>
+ <li>
+ Creating a vendor-neutral member-driven community of open source projects that fosters inclusion and collaboration.
+ </li>
+ <li>
+ Reflecting the achievements of the community through a strong and distinctive brand.
+ </li>
+ <li>
+ Striving to support a wide range of embedded platforms, programming models, connection types, and communication protocols.
+ </li>
+ <li>
+ Providing a vivid platform to collaborate on widely accepted IoT architectural guidelines, that
+ </li>
+ <ul>
+ <li>
+ Promote open standard communication protocols to deal with IoT requirements and constraints such as; power, CPU, cost, connection availability, and bandwidth.
+ </li>
+ <li>
+ Help to balance the right level of coupling coupling between applications, systems and communication interfaces.
+ </li>
+ <li>
+ Bridge the gap between the Information Technology and Operational Technology ecosystems.
+ </li>
+ <li>
+ Develop, document and promote IT & OT best practices.
+ </li>
+ </ul>
+
+ <li>
+ Fostering Open Source IoT development solutions, like development environment, development boards, that
+ </li>
+ <ul>
+ <li>
+ Integrate well with open source Enterprise and Web development tools and environments.
+ </li>
+ <li>
+ Assert modular, state-of-the-art application architecture as well as the appropriate reuse of software components (e.g. drivers, communication protocols).
+ </li>
+ <li>
+ Support developers who need to integrate IoT, Enterprise, and Web application systems. e.g. hardware and infrastructure costs, no relevant software engineering environment, proprietary interfaces, numerous and complex programming models.
+ </li>
+ </ul>
+
+ <li>
+ Facilitating open source support for IoT-oriented middleware, including IoT integration with established middleware solutions.
+ </li>
</ul>
- <p>Usually, the IoT server infrastructure has to be interfaced with other information systems.
- Examples are telecom operators (e.g. SIM card subscription management or billing), and
- enterprise systems (e.g. cargo tracking and vehicle maintenance). An IoT server also needs to
- expose interfaces allowing third-party applications to access collected data, accept and
- process control functions, and to perform management and provisioning operations on modules
- and assets in the field.</p>
- <h2>Concerns Addressed by the Eclipse IoT Working Group</h2>
- <p>The objective of the IoT Working group is to encourage, develop, and promote open source
- solutions that can be used to overcome market inhibitors found in most IoT ecosystems, such
- as:</p>
+ <p>
+ To achieve these goals, the Eclipse IoT working group will pursue initiatives related to the following domains:
+ </p>
<ul>
- <li />
- <p>Fragmented market: wide range of embedded platforms, programming models, connection types,
- communication protocols.</p>
- <li />
- <p>No widely accepted IoT architectural guidelines.</p>
- <li />
- <p>Limited choices in accepted open, standard communication protocols to deal with IoT
- requirements and constraints such as; power, CPU, cost, connection availability, and
- bandwidth.</p>
- <li />
- <p>Unnecessarily tight coupling between applications, systems and communication interfaces.</p>
- <li />
- <p>Lack of Open Source IoT development solutions (development environment, development boards)</p>
- <li />
- <p>Lack of integration with open source Enterprise and Web development tools and environments.</p>
- <li />
- <p>Monolithic applications and lack of reusable software components (e.g. drivers,
- communication protocols)</p>
- <li />
- <p>High barrier of entry to developers who need to integrate IoT, Enterprise, and Web
- application systems. e.g. hardware and infrastructure costs, no relevant software
- engineering environment, proprietary interfaces, numerous and complex programming models.</p>
- <li />
- <p>Inadequate open source support for IoT-oriented middleware, including IoT integration with
- established middleware solutions.</p>
+ <li>
+ Development tools, including simulators and emulators
+ </li>
+ <li>
+ Reference architectures
+ </li>
+ <li>
+ Programming models and frameworks
+ </li>
+ <li>
+ Open and standard communication protocols
+ </li>
+ <li>
+ Open APIs
+ </li>
</ul>
- <h2>Purpose and scope of the Working Group</h2>
- <p>The Eclipse Foundation is a place where people collaborate to deliver exemplary, extensible
- tools, frameworks and runtime components. The IoT Working Group aims at defining an open
- development environment and key runtimes for IoT solutions that will enable open solutions.
- The IoT Working Group will address the following topics:</p>
- <ul>
- <li />
- <p>Development tools, including simulators/emulators</p>
- <li />
- <p>Reference architecture and programming model</p>
- <li />
- <p>Effective decoupling between applications, systems and communication interfaces</p>
- <li />
- <p>Open and standard communication protocols</p>
- <li />
- <p>Open and standard APIs (embedded & server).</p>
- <li />
- <p>Frameworks and services for IoT gateways and IoT Cloud platforms</p>
- <li />
- <p>Communicate and evangelize the solutions produced by the IoT WG</p>
- </ul>
- <h2>Connections with other standards and industry groups</h2>
- <p>The IoT Working Group will also work in collaboration with other IoT Industry Groups
- and Standards organizations in order to avoid fragmentation and duplication of effort,
- including groups like oneM2M, OASIS, OMA, IETF, IIC and others.</p>
- <h2>Work areas</h2>
- <p>The IoT Working Group will work on the following topics:</p>
- <h3>IoT software components</h3>
- <p>The IoT Working Group will identify and specify software components needed to
- efficiently develop IoT solutions (communication services, industrial protocol
- implementations).</p>
- <h3>IoT use cases</h3>
- <p>The IoT working group will identify and maintain common use cases that represent typical IoT
- environments. The goal is to highlight the capabilities and requirements that need to be
- standardized to ensure open interoperability, portability, reusability, and ease of
- integration.</p>
- <h3>Reference architecture</h3>
- <p>The IoT Working Group will work on the definition of a set of architectural
- guidelines ("IoT Blueprints") for IoT solutions, derived from the identified use
- cases.</p>
- <h3>IoT tooling</h3>
- <p>The IoT Working Group will work on the requirements and specifications to support
- the integration of IoT tooling, with relevant Eclipse tooling that is used by developers of
- the Enterprise and Web applications who integrate with IoT embedded and server applications.</p>
- <h3>Open IoT Specifications and Standards</h3>
- <p>The IoT Working Group will identify, reference and provide implementations of open
- specifications and standards that support the development and deployment of IoT solutions. The
- Working Group may also be responsible for defining compatibility test suites for IoT
- specifications and in some cases creating and maintaining an IoT specification.</p>
- <h3>APIs</h3>
- <p>The IoT Working Group will work on the definition of Application Programming
- Interfaces both on the embedded and on the server-side in order to help increase the
- modularity, extensibility and effective decoupling of IoT solutions.</p>
- <h3>IoT software components repository</h3>
- <p>The IoT Working Group will define the technical requirements for allowing the
- delivery of IoT-oriented software components (industrial protocol drivers, embedded devices
- models, code generators, etc.) via the Eclipse Marketplace.</p>
- <h3>IoT "hacker place" and sandbox</h3>
- <p>Because IoT development requires actual hardware, and likely prepaid airtime, in order to
- perform end-to-end experiments, the IoT Working Group may work on the definition of a
- so-called "hacker place", which will take the form of a website easing the ordering
- of IoT developer kits (development boards, wireless sensors, 3G modems, etc.). The IoT Working
- Group will work together with the Eclipse Foundation and hardware providers to propose
- discounts on developer kits, airtime, etc.</p>
- <p>Developing and testing IoT integration with Enterprise and Web applications requires access
- to middleware, monitoring servers, enterprise servers and various Web application interfaces.
- The IoT Working Group will work to define and promote the availability of a
- "sandbox" of accessible server environments for the development, testing and
- integration of IoT systems with Enterprise, Web, and cloud-based software to developers using
- Eclipse IoT tools and runtimes.</p>
- <h3>Communication and Evangelism</h3>
- <p>The IoT Working Group will work to communicate and evangelize the solutions
- developed by the IoT WG. The activities may include joint press releases, joint trade show
- participation, publishing white papers and/or preparing other content that communicates the
- vision and solutions of the WG.</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="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>
+ <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</a> page or the <a href="/legal">Eclipse Foundation Legal Resources</a> page:
+ </p>
<ul>
<li>Eclipse Foundation Bylaws</li>
- <li>Eclipse Foundation Membership Agreement</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 Membership Agreement</li>
<li>Eclipse Foundation Intellectual Property Policy</li>
<li>Eclipse Foundation Antitrust Policy</li>
- <li>Eclipse Foundation Trademark Usage Guidelines</li>
- <li>Eclipse Foundation Working Group Process</li>
<li>Eclipse Foundation Development Process</li>
+ <li>Eclipse Foundation Trademark Usage Guidelines</li>
+ <li>Eclipse Foundation Technology Compatibility Kit License</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, Specification Process, Working Group Process or any policies of the Eclipse Foundation, the terms of the respective Eclipse Foundation Bylaws, Membership Agreement, process or policy shall take precedence.
+ </p>
- <p>All Members of the working group must be parties to the Eclipse Foundation Membership
-Agreement, including the requirement set forth in Section 2.2 to abide by and adhere to follow
-the Bylaws and then-current policies of the Eclipse Foundation, including but not limited to the
-Intellectual Property and Antitrust Policies.</p>
+ <h2>Membership</h2>
+ <p>
+ With the exception of Guest members as described below, an entity must be at least a <a href="/membership/#tab-levels">Contributing Member</a> of the Eclipse Foundation, have executed the Eclipse IoT working group participation agreement 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 IoT 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 four classes of Eclipse IoT working group membership - Leader, Innovator, Supporter and Guest.
+ </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, Working Group Process, Development
-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>Steering Committee Roles and Responsibilities</h2>
- <p>The Eclipse IoT Working Group will have a Steering Committee to help guide the strategy and
- operation of the working group. The Steering Committee will make decisions based on a
- simple majority vote of the committee members.</p>
- <p>The roles and responsibilities of the Steering Committee include:</p>
- <ul>
- <li />
- <p>Provide guidance and approval of the annual Eclipse IoT Working Group strategy, positioning
- and roadmap.</p>
- <li />
- <p>Approve the technical architecture and composition of any Eclipse IoT solution stack that
- is based on the overall roadmap.</p>
- <li />
- <p>Coordination and recruitment of resources to accelerate key project development and
- integration of the Eclipse IoT roadmap.</p>
- <li />
- <p>Coordinate Eclipse IoT Working Group membership recruitment</p>
- <li />
- <p>Approve Eclipse IoT Testbeds.</p>
- <li />
- <p>Approval of any Eclipse IoT documents, include technical architectures, blueprints, white
- papers.</p>
- <li />
- <p>Elect a chair of the Eclipse IoT Working Group</p>
- <li />
- <p>Define the annual fees for all classes of working group membership</p>
- <li />
- <p>Approve the annual budget based upon funds received through fees</p>
- <li />
- <p>Establish sub-committees of the Eclipse IoT Working Group, ex. Architecture and Technical
- Committee</p>
- </ul>
- <h3>Participation Guidelines - Membership</h3>
- <p>With the exception of Guest members as described below, an entity must be at least a
- Contributing Member of the Eclipse Foundation. All members must have executed the Eclipse IoT Working Group Participation
- Agreement, and adhere to the requirements set forth in this Charter to participate.</p>
- <p>There are three classes of Eclipse IoT working group membership - Strategic, Participant, and
- Guest. Each of these classes is described in detail below.</p>
- <p>The participation fees associated with each of these membership classes is shown in the
- tables in Schedule A. These are annual fees, and are established by the Eclipse IoT 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>
- <h4>Strategic members</h4>
- <p>Strategic members are required to:</p>
- <ul>
- <li>
- <p>Be a Strategic or Contributing member of the Eclipse Foundation.</p>
- </li>
- <li>
- <p>Lead at least one Eclipse IoT project and contribute at least 4 FTE working on Eclipse
- IoT projects or Eclipse IoT Working Group activities. The activities can include 1)
- committers working on Eclipse open source projects that support the IoT roadmap, 2)
- creation of roadmaps and technical documents (including, for example, architectures,
- blueprints and best practices) supporting the WG work, 3) evangelism and community
- development for the WG and 4) other activities agreed to by the Steering committee.</p>
- </li>
- <li>
- <p>Strategic members may also be invited to join the Steering Committee if they demonstrate
- contributions to at least one Eclipse IoT project, and be approved by a simple majority of
- the existing Strategic members.</p>
- </li>
- <li>
- <p>Regularly participate in Working Group meetings and provide timely feedback on Working
- Group documents.</p>
- </li>
- <li>
- <p>Provide executive-level representation at quarterly Steering Committee meetings.</p>
- </li>
- <li>
- <p>Provide ongoing marketing and community development support to the Eclipse IoT community.</p>
- </li>
- </ul>
- <h4>Participant Members</h4>
- <p>Participant Members are required to:</p>
- <ul>
- <li>
- <p>Be an Eclipse Foundation member at the Strategic or Contributing level.</p>
- </li>
- <li>
- <p>Regularly participate in the Working Group meetings.</p>
- </li>
- </ul>
+ <h3>Classes of Membership</h3>
+ <h4>Leader Members</h4>
+ <p>
+ Leader Members are organizations that view this Working Group standards and technologies as strategic to their organization and are investing significant resources to sustain and shape the activities of this working group. They are Leader Members of this working group and must be at least a Contributing Member of the Eclipse Foundation, and are expected to have a minimum of two developers participating on its projects.
+ </p>
+ <h4>Innovator Members</h4>
+ <p>
+ Innovator Members are organizations that view Eclipse IoT technologies as important to their corporate and product strategy. They are typically organizations that deliver products or services based upon related standards, specifications and technologies, or view this working group’s standards and technologies as strategic to their organization. These organizations want to participate in the development and direction of an open ecosystem related to this working group. Innovator Members of this working group must be at least a Contributing Member of the Eclipse Foundation.
+ </p>
+ <h4>Supporter Members</h4>
+ <p>
+ Supporter Members are organizations that want to participate in an open ecosystem related to this working group and wish to show their support for it. Supporter Members of this working group must be at least a Contributing Member of the Eclipse Foundation.
+ </p>
<h4>Guest Members</h4>
- <p>Eclipse Foundation Associate Members may be invited by the Steering Committee to join and
- participate in the Working Group as Guest members.</p>
- <h3>Working Group Process</h3>
<p>
- The IoT Working Group will follow the <a
- href="/org/workinggroups/industry_wg_process.php"
- >Eclipse Foundation Working Group Process</a>.
- </p>
- <h3>Eclipse IoT Working Group Annual Participation Fees Schedule A</h3>
- <p>
- The following fees have been established by the Eclipse IoT Steering Committee.<br /> The
- following are the annual fees associated with each class of membership in the Eclipse IoT
- Working Group. All fees are in USD.
+ Guest Members are organizations which are Associate members of the Eclipse Foundation who have been invited by the Steering Committee to participate in particular aspects of the activities of the Working Group. 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>
- <h4>Eclipse IoT Strategic Member Annual Participation Fees</h4>
- <p>Steering Committee members are required to execute the Eclipse IoT Participation Agreement.</p>
+ <h2>Membership Summary</h2>
+ <table class="table table-stripped text-center">
+ <thead>
+ <tr >
+ <th class='text-center'>Committee Representation</th>
+ <th class='text-center'>Leader</th>
+ <th class='text-center'>Innovator</th>
+ <th class='text-center'>Supporter</th>
+ <th class='text-center'>Guest</th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>Steering Committee</td>
+ <td>Appointed</td>
+ <td>Elected</td>
+ <td>N/A</td>
+ <td>N/A</td>
+ </tr>
+ <tr>
+ <td>Marketing and Brand Committee</td>
+ <td>Appointed</td>
+ <td>Elected</td>
+ <td>N/A</td>
+ <td>N/A</td>
+ </tr>
+ </tbody>
+ </table>
+
+ <h2>Governance</h2>
+ <p>This Eclipse IoT working group is designed as:</p>
+ <ul>
+ <li>a vendor-neutral, member-driven organization, </li>
+ <li>a means to foster a vibrant and sustainable ecosystem of components and service providers,</li>
+ <li>a means to organize the community of each project or component so that users and developers define the roadmap collaboratively.</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 the working group members. </li>
+ <li>Establish an annual program plan.</li>
+ <li>Approve the annual budget based upon funds received through working group fees.</li>
+ <li>Invite Guest members to participate in the working group.</li>
+ </ul>
+ <h4>Composition</h4>
+ <p>Each Leader Member of the working group has a seat on the Steering Committee.</p>
+ <p>
+ One seat is allocated to Innovator Members. Innovator Member seats are allocated following the Eclipse "Single Transferable Vote", as defined in the Eclipse Foundation Bylaws.
+ </p>
+ <p>
+ The Committee elects a chair of 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. There is no limit on the number of terms the chair may serve.
+ </p>
+ <h4>Meeting Management</h4>
+ <p>The Steering Committee meets at least twice a year.</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 strategic marketing priorities, goals, and objectives for the working group.</li>
+ <li>Coordinate 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>Provide requirements to the Eclipse Foundation for 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 Leader Member of the working group has a seat on the Marketing Committee.</li>
+ <li>One seat is allocated to Innovator Members. Innovator 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. There is no limit on the number of terms the chair may serve. </li>
+ </ul>
+
+ <h3>Meeting Management</h3>
+ <p>The Marketing and Brand Committee meets at least twice a year.</p>
+
+ <h3>Common Dispositions</h3>
+ <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, electronic voting action without meeting, vacancy, resignation or removal, the respective terms set forth in the Eclipse Foundation Bylaws apply.
+ </p>
+
+ <h3>Good Standing</h3>
+ <p>
+ A representative shall be deemed to be in Good Standing, and thus eligible to vote on issues coming before the Body they participate in, if the representative has attended (in person or telephonically) a minimum of three (3) of the last four (4) Body meetings (if there have been at least four meetings). 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 which shall be included in determining whether the representative is in Good Standing. 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 in Good Standing 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) approving or changing the name of the working group; and (iv) approving changes to annual Member contribution requirements; any such actions must be approved by no less than two-thirds (2/3) of the representatives in Good Standing 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>Leader Members</h4>
+ <p>
+ Leader 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 June 1 to May 31 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>
+
+ <h2>Meetings Management</h2>
+ <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>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 in Good Standing 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 will 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. 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>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 member to any of its meetings. These invited attendees have no right to vote.</p>
+ <h3>Working Group Fees</h3>
+ <p>
+ The Steering Committee defines a fee structure and approves an annual budget based on resource requirements necessary to achieve the objectives of the group. Members agree to pay the annual fees as established by the Steering Committee.
+ </p>
+ <p>
+ All new members are expected to pay the pro-rated fees for the associated calendar year. Beginning with the next calendar year, fees will be assessed on an annual basis.
+ </p>
+ <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>
+
+ <h2>Working Group Annual Participation Fees Schedule A</h2>
+ <p>The following fees have been established by the Eclipse IoT Steering Committee. These fees are in addition to each participant’s membership fees in the Eclipse Foundation.</p>
+ <h3>Eclipse IOT Leader Member Annual Participation Fees</h3>
+ <p>Leader members are required to execute theEclipse IoT Working Group Participation Agreement.</p>
<table class="table table-stripped">
<thead>
- <tr>
+ <tr >
<th>Corporate Revenue</th>
<th>Annual Fees</th>
</tr>
</thead>
<tbody>
<tr>
- <td>
- <p>Annual Corporate Revenues greater than $250 million</p>
- </td>
- <td>
- <p>$50,000</p>
- </td>
+ <td>Annual Corporate Revenues greater than €1 billion</td>
+ <td>€50 000</td>
</tr>
<tr>
- <td>
- <p>Annual Corporate Revenues greater than $100 million but less than or equal to $250
- million</p>
- </td>
- <td>
- <p>$30,000</p>
- </td>
+ <td>Annual Corporate Revenues greater than €250 million but less than or equal to €1 billion</td>
+ <td>€30 000</td>
</tr>
<tr>
- <td>
- <p>Annual Corporate Revenues greater than $50 million but less than or equal to $100
- million</p>
- </td>
- <td>
- <p>$15,000</p>
- </td>
+ <td>Annual Corporate Revenues greater than €50 million but less than or equal to €250 million</td>
+ <td>€15 000</td>
</tr>
<tr>
- <td>
- <p>Annual Corporate Revenues greater than $10 million but less than or equal to $50
- million</p>
- </td>
- <td>
- <p>$10,000</p>
- </td>
+ <td>Annual Corporate Revenues greater than €10 million but less than or equal to €50 million</td>
+ <td>€10 000</td>
</tr>
<tr>
- <td>
- <p>Annual Corporate Revenues less than or equal to $10 million</p>
- </td>
- <td>
- <p>$5,000</p>
- </td>
+ <td>Annual Corporate Revenues less than or equal to €10 million</td>
+ <td>€5 000</td>
</tr>
</tbody>
</table>
- <h4>Eclipse IoT Participant Member Annual Participation Fees</h4>
- <p>Participant Members pay no annual fees, but are required to execute the Eclipse IoT Working Group Participation Agreement.</p>
- <h4>Eclipse IoT Guest Members</h4>
- <p>Eclipse Foundation Associate Members may be invited by the Steering Committee to join and
- participate in the Working Group as Guest Members. Guest members pay no annual fees, but are
- required to execute the Eclipse IoT Working Group Participation Agreement.</p>
- <p><strong>Version History</strong></p>
+ <h3>Eclipse IoT Innovator Member Annual Participation Fees</h3>
+ <p>Innovator members are required to execute the Eclipse IoT Working Group Participation Agreement.</p>
+ <table class="table table-stripped">
+ <thead>
+ <tr >
+ <th>Corporate Revenue</th>
+ <th>Annual Fees</th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>Annual Corporate Revenues greater than €1 billion</td>
+ <td>€25 000</td>
+ </tr>
+ <tr>
+ <td>Annual Corporate Revenues greater than €250 million but less than or equal to €1 billion</td>
+ <td>€15 000</td>
+ </tr>
+ <tr>
+ <td>Annual Corporate Revenues greater than €50 million but less than or equal to €250 million</td>
+ <td>€10 000</td>
+ </tr>
+ <tr>
+ <td>Annual Corporate Revenues greater than €10 million but less than or equal to €50 million</td>
+ <td>€5 000</td>
+ </tr>
+ <tr>
+ <td>Annual Corporate Revenues less than or equal to €10 million</td>
+ <td>€2 000</td>
+ </tr>
+ </tbody>
+ </table>
+ <h3>Eclipse IoT Supporter Member Annual Participation Fees</h3>
+ <p>Supporter Members pay no annual fees, but are required to execute the Eclipse IoT Working Group Participation Agreement.</p>
+ <h3>Eclipse IoT Guest Member Annual Participation Fees</h3>
+ <p>Guest members pay no annual fees, but are required to execute the Eclipse IoT Working Group Participation Agreement.</p>
+
+ <br>
+
+ <p><strong>Charter History</strong></p>
<ul>
- <li>November, 2020 Updated in support of the Eclipse Foundation corporate restructuring</li>
+ <li>V1.9 November, 2020 Updated in support of the Eclipse Foundation corporate restructuring.</li>
+ <li>
+ V2.0 March 19, 2021 Completely restructured following the new working group charter template. Renamed existing membership levels. Added Innovator level.
+ <ul>
+ <li>Approved by the Steering Committee, June 21, 2021</li>
+ <li>Approved by Executive Director, June 22, 2021</li>
+ </ul>
+ </li>
</ul>
</div>
</div>
\ No newline at end of file
diff --git a/workinggroups/wpga/eclipse-iot-working-group-participation-agreement.pdf b/workinggroups/wpga/eclipse-iot-working-group-participation-agreement.pdf
index 3bc1701..a212076 100644
--- a/workinggroups/wpga/eclipse-iot-working-group-participation-agreement.pdf
+++ b/workinggroups/wpga/eclipse-iot-working-group-participation-agreement.pdf
Binary files differ
