Infra 3928 - New OSGI WG Charter
Signed-off-by: Yi Liu <yi.liu@eclipse-foundation.org>
Change-Id: I97231e61b4303db493c2facc03932e2056470a8e
diff --git a/workinggroups/content/en_osgi-charter.php b/workinggroups/content/en_osgi-charter.php
new file mode 100644
index 0000000..aa797cd
--- /dev/null
+++ b/workinggroups/content/en_osgi-charter.php
@@ -0,0 +1,328 @@
+<?php
+/**
+ * Copyright (c) 2019 Eclipse Foundation.
+ *
+ * This program and the accompanying materials are made
+ * available under the terms of the Eclipse Public License 2.0
+ * which is available at /legal/epl-2.0/
+ *
+ * Contributors:
+ * Eric Poirier (Eclipse Foundation) - Initial implementation
+ *
+ * SPDX-License-Identifier: EPL-2.0
+ */
+?>
+<div id="maincontent">
+ <div id="midcolumn">
+ <h1><?php print $pageTitle; ?></h1>
+ <p>Draft - Not yet approved</p>
+ <p>Version 0.93 - Revision history is at end of document.</p>
+ <h2>Vision and Scope</h2>
+ <p>The OSGi Working Group will drive the evolution and broad adoption of software technologies
+derived from or related to the OSGi Specification Project. The OSGi Specification Project is an
+open source initiative to create software specifications, implementations of those specifications, and
+Technology Compatibility Kits (TCKs) for those specifications that enable development, deployment,
+and management of embedded, server-side and cloud-native applications. The OSGi Specification
+Project is based on Specifications, Reference Implementations and Compliance Tests of the former
+OSGi Alliance and uses those materials as the baseline for creating new specifications,
+implementations and TCKs, or revising existing OSGi Alliance specifications, reference
+implementations and compliance tests.</p>
+ <p>The working group will:</p>
+ <ul>
+ <li>Provide vendor neutral services to the OSGi ecosystem.</li>
+ <li>Leverage the Eclipse Foundation Specification Process to formalize the specifications that are defined within the scope of this working group.</li>
+ <li>Define compatibility rules and a compatibility and branding process for implementations of these specifications to ensure application portability.</li>
+ <li>Leverage Eclipse Foundation licensing and intellectual property flows that encourage community participation, protect community members, and encourage usage.</li>
+ <li>Manage the overall technical and business strategies for the OSGi WG and related projects.</li>
+ <li>Establish and drive a funding model that enables this working group and its community to operate on a sustainable basis.</li>
+ <li>Promote the OSGI brand and its value in the marketplace.</li>
+ </ul>
+
+ <h2>Governance and Precedence</h2>
+ <p><strong>Applicable Documents</strong></p>
+ <ul>
+ <li><a href="/org/documents/eclipse_foundation-bylaws.pdf">Eclipse Foundation Bylaws</a></li>
+ <li><a href="/org/workinggroups/process.php">Eclipse Foundation Working Group Process</a></li>
+ <li><a href="/org/documents/eclipse_membership_agreement.pdf">Eclipse Foundation Membership Agreement</a></li>
+ <li><a href="/org/documents/Eclipse_IP_Policy.pdf">Eclipse Foundation Intellectual Property Policy</a></li>
+ <li><a href="/org/documents/Eclipse_Antitrust_Policy.pdf">Eclipse Foundation Antitrust Policy</a></li>
+ <li><a href="/projects/dev_process/">Eclipse Foundation Development Process</a></li>
+ <li><a href="/projects/efsp/">Eclipse Foundation Specification Process</a></li>
+ <li><a href="/legal/tck.php">Eclipse Foundation Technology Compatibility Kit License</a></li>
+ <li><a href="/legal/efsl.php">Eclipse Foundation Specification License</a></li>
+ <li><a href="/legal/logo_guidelines.php">Eclipse Foundation Trademark Usage Guidelines</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>All Members must further be parties to the OSGi Working Group Participation Agreement.</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>
+ Strategic and Participant working group members must be at least a <a href="/membership/#tab-levels">Contributing Member</a> of the Eclipse Foundation. All working group members must have executed the OSGi WG Participation Agreement once defined, and adhere to the requirements set forth in this Charter to participate.
+ </p>
+ <p>
+ There are four classes of OSGi working group membership - Strategic, Participant, Committer, 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 OSGi WG 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 <a href="/org/documents/eclipse_foundation-bylaws.pdf">Eclipse Foundation Bylaws</a> and detailed in the <a href="/org/documents/eclipse_membership_agreement.pdf">Eclipse Foundation Membership Agreement</a>.
+ </p>
+ <h3>Classes of OSGi WG membership</h3>
+ <h4>Strategic members</h4>
+ <p>Strategic Members are organizations that view OSGi technology as strategic to their organization and are investing significant resources to sustain and shape the activities of this working group.</p>
+ <p>Strategic Members of the OSGi working group must be at least a Contributing Member of the Eclipse Foundation, and have a minimum of 1 developer participating on the OSGi Specification Project.</p>
+ <p>Founding Strategic Members of the OSGi working group are required to commit to their initial strategic membership for a three (3) year period.</p>
+ <h4>Participant members</h4>
+ <p>Participant Members are typically organizations that deliver products or services based on OSGi technology. These organizations want to participate in the development of the OSGi technology ecosystem.</p>
+ <p>Participant Members of the OSGi working group must be at least Contributing Members of the Eclipse Foundation.</p>
+ <h4>Committer members</h4>
+ <p>Committer Members are individuals who through a process of meritocracy defined by the Eclipse Foundation Development Process are able to contribute and commit materials to the Eclipse Foundation projects included in the scope of this working group. Committers may be members by virtue of working for a member organization, or may choose to complete the membership process independently if they are not. For further explanation and details, see the <a href="/membership/become_a_member/committer.php">Eclipse Foundation Committer Membership</a> page.</p>
+ <h4>Guest members</h4>
+ <p>
+ Guest Members are organizations which are Associate members of the Eclipse Foundation who have been invited for one year, renewable, by the OSGi WG Steering Committee to participate in particular aspects of the activities of the Working Group. Typical guests include JUGs, 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 OSGi WG Participation Agreement.
+ </p>
+ <h3>Membership Summary</h3>
+ <table class="table table-bordered">
+ <tbody>
+ <tr>
+ <td> </td>
+ <td>
+ Strategic Member
+ </td>
+ <td>
+ Participant Member
+ </td>
+ <td>
+ Committer Member
+ </td>
+ <td>
+ Guest Member
+ </td>
+ </tr>
+ <tr>
+ <td>
+ Member of the Steering Committee
+ </td>
+ <td>
+ Appointed
+ </td>
+ <td>
+ Elected
+ </td>
+ <td>
+ Elected
+ </td>
+ <td>
+ N/A
+ </td>
+ </tr>
+ <tr>
+ <td>
+ Member of the Specification Committee
+ </td>
+ <td>
+ Appointed
+ </td>
+ <td>
+ Elected
+ </td>
+ <td>
+ Elected
+ </td>
+ <td>
+ Invitation Only
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ <p>All matters related to Membership in the Eclipse Foundation and this OSGi Working Group will be 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>
+
+ <h2>Governance</h2>
+ <p>This OSGi Working Group is designed as:</p>
+ <ul>
+ <li>a 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>
+ <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 Specification Committee</li>
+ </ul>
+ <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. This will require acceptance of the specification process by these projects.</li>
+ <li>Define and manage a process for projects outside of the Eclipse Foundation to be included in the OSGi WG Materials.</li>
+ <li>Define and manage the roadmaps.</li>
+ <li>Review and approve this charter.</li>
+ <li>Review and approve the specification process.</li>
+ <li>Review and approve the trademark policy to ensure compatibility of independent implementations of specifications.</li>
+ <li>Establish the fees for all classes of working group membership, and to approve an annual program plan and budget based on the fees collected for each year.</li>
+ <li>Invite Guest members to participate in the working group.</li>
+ <li>Define and approve the trademark policy to be used by all OSGi Specification Project specifications.</li>
+ <li>Ensure the consistency of logo usage.</li>
+ </ul>
+ <h4>Composition</h4>
+ <ul>
+ <li>Each Strategic Member of the working group has a seat on the Steering Committee.</li>
+ <li>At least one seat is allocated to Participant Members. Additional seats may be added by a super-majority resolution of the Steering Committee. Participant Member seats are elected following the Eclipse Foundation "Single Transferable Vote", as defined in the Eclipse Foundation Bylaws.</li>
+ <li>At least one seat is allocated to Committer Members. Additional seats may be added by a super-majority resolution of the Steering Committee. Committer Member seats are elected following the Eclipse "Single Transferable Vote", as defined in the Eclipse Foundation Bylaws.</li>
+ </ul>
+ <h4>Meeting Management</h4>
+ <p>The Steering Committee meets at least twice a year.</p>
+
+ <h3>Specification Committee</h3>
+ <h4>Powers and Duties</h4>
+ <p>Specification Committee members are required to:</p>
+ <ul>
+ <li>Define the specification process to be used by all OSGi Specification Project specifications, and refer to it for approval by the Steering Committee.</li>
+ <li>Ensure that all specification expert groups operate in an open, transparent, and vendor-neutral fashion in compliance with the specification process.</li>
+ <li>Approve specifications for adoption by the community.</li>
+ <li>Approve profiles which define collections of specifications which meet a particular market requirement.</li>
+ <li>Work with the Eclipse OSGi Project Management Committee (OSGi PMC) to ensure that the specification process is complied with by all specification projects.</li>
+ </ul>
+ <h4>Composition</h4>
+ <ul>
+ <li>Each Strategic Member of the working group has a seat on the Specification Committee.</li>
+ <li>At least one seat is allocated to Participant Members. Participant Member seats are elected following the Eclipse "Single Transferable Vote", as defined in the Eclipse Bylaws.</li>
+ <li>At least one seat is allocated to Committer Members. Committer Member seats are elected following the Eclipse "Single Transferable Vote", as defined in the Eclipse Bylaws.</li>
+ <li>At least one seat is allocated to a representative of the OSGi PMC. The OSGi PMC may decide how to select its representative.</li>
+ <li>Guest members that have been invited by the OSGi WG Steering Committee as observers. Guest members have no voting rights.</li>
+ <li>Any additional individuals as designated from time to time by the Eclipse Executive Director.</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>
+ <h4>Meeting Management</h4>
+ <p>The Specification Committee meets at least once per quarter.</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 terms set forth in Section 6 of the Eclipse Foundation Bylaws apply.</p>
+ <h4>Good Standing</h4>
+ <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, telephonically or video-conferencing) 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 send a representative and may vote by proxy, 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>
+ <h4>Voting</h4>
+ <p>
+ <strong>Super Majority</strong>
+ </p>
+ <p>For actions (i) requesting that the Eclipse Foundation Board of Directors approve a specification license;
+(ii) approving specifications for adoption; (iii) amending the terms of the working group’s Participation
+agreement; (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 in Good Standing represented at a committee meeting at which a quorum is
+present.</p>
+ <h4>Term and Dates of elections</h4>
+ <p>This section only applies to the Steering Committee and Specification 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>
+ <p>
+ <strong>Strategic Members</strong>
+ </p>
+ <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>
+ <p>
+ <strong>Elected representatives</strong>
+ </p>
+ <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>
+ <h4>Meetings Management</h4>
+ <p>
+ <strong>Place of meetings</strong>
+ </p>
+ <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>
+ <p>
+ <strong>Regular meetings</strong>
+ </p>
+ <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,
+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>
+ <p>
+ <strong>Actions</strong>
+ </p>
+ <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>
+ <h4>Invitations</h4>
+ <p>The Body may invite any member to any of its meetings. These invited attendees have no right of vote.</p>
+
+ <h3>OSGi Working Group Annual Participation Fees Schedule A</h3>
+ <p>The following fees have been established by the OSGi WG Steering Committee.</p>
+
+ <h3>OSGi WG Strategic Member Annual Participation Fees</h3>
+ <p>Strategic members pay $0 in fee for 2020.</p>
+ <p>Strategic members are required to execute the OSGi WG Participation Agreement, and to begin
+paying the fees shown below effective January 1, 2021.</p>
+ <p>Founding Strategic members are required to commit to an initial three (3) years of membership.</p>
+ <table class="table table-stripped" cellspacing="0">
+ <thead>
+ <tr>
+ <th width="55%">Corporate Revenue</th>
+ <th class="text-center" width="20%">Annual Fees</th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>Annual Corporate Revenues greater than $100 million</td>
+ <td class="text-center">$15,000</td>
+ </tr>
+ <tr>
+ <td>Annual Corporate Revenues less than or equal to $100 million</td>
+ <td class="text-center">$3,500</td>
+ </tr>
+ </tbody>
+ </table>
+
+ <h3>OSGi WG Participant Member Annual Participation Fees</h3>
+ <p>Participant members pay $0 in fees for 2020.</p>
+ <p>Participant members are required to execute the OSGi WG Participation Agreement, and to begin
+paying the fees shown below effective January 1, 2021.</p>
+ <table class="table table-stripped" cellspacing="0">
+ <thead>
+ <tr>
+ <th width="55%">Corporate Revenue</th>
+ <th class="text-center" width="20%">Annual Fees</th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>Annual Corporate Revenues greater than $10 million, or has 10 or more employees</td>
+ <td class="text-center">$5,000</td>
+ </tr>
+ <tr>
+ <td>Annual Corporate Revenues less than or equal to $10 million, and less than 10 employees</td>
+ <td class="text-center">$1,000</td>
+ </tr>
+ </tbody>
+ </table>
+
+ <h3>OSGi WG Committer Member Annual Participation Fees</h3>
+ <p>Committer members pay no annual fees, but are required to execute the OSGi WG Participation Agreement.</p>
+
+ <h3>OSGi WG Guest Member Annual Participation Fees</h3>
+ <p>Guest members pay no annual fees, but are required to execute the OSGi WG Participation Agreement.</p>
+
+ <p class="margin-top-20"><strong>OSGi WG Charter Version History</strong></p>
+ <ul>
+ <li>v0.90 Initial draft created May 5, 2020</li>
+ <li>v0.91 May 7, 2020, Eliminated Enterprise class membership; Eliminated Marketing Committee and moved relevant duties to the Steering Committee; Changed “compliance tests” to “TCKs” where appropriate; Minor corrections to fees tables.</li>
+ <li>v0.92 May 12, 2020, Revised utilizing the feedback provided on V0.91 by OSGi Board and Officers</li>
+ <li>v0.93 October, 2020, Revised by Eclipse Foundation</li>
+ </ul>
+ </div>
+</div>
\ No newline at end of file
diff --git a/workinggroups/osgi-charter.php b/workinggroups/osgi-charter.php
new file mode 100644
index 0000000..4cbb9d1
--- /dev/null
+++ b/workinggroups/osgi-charter.php
@@ -0,0 +1,33 @@
+<?php
+/**
+ * Copyright (c) 2019 Eclipse Foundation and others.
+ *
+ * This program and the accompanying materials are made
+ * available under the terms of the Eclipse Public License 2.0
+ * which accompanies this distribution, and is available
+ * at http://eclipse.org/legal/epl-2.0
+ *
+ * Contributors:
+ * Eric Poirier (Eclipse Foundation) - Initial implementation
+ *
+ * SPDX-License-Identifier: EPL-2.0
+ */
+
+require_once($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/app.class.php");
+
+$App = new App();
+$Theme = $App->getThemeClass();
+
+include($App->getProjectCommon());
+
+$pageTitle = "OSGi Working Group Charter";
+$Theme->setPageTitle($pageTitle);
+$Theme->setPageKeywords("OSGi, wg, charter, eclipse");
+$Theme->setPageAuthor("Eclipse Foundation");
+
+ob_start();
+include("content/en_" . $App->getScriptName());
+$html = ob_get_clean();
+
+$Theme->setHtml($html);
+$Theme->generatePage();
