feat: operations guide v2.5
Change-Id: Ic97116e999dd43c800af9de665ac9fbbaa8ba4e0
diff --git a/workinggroups/content/en_operations.html b/workinggroups/content/en_operations.html
index 703dc99..0cecf25 100644
--- a/workinggroups/content/en_operations.html
+++ b/workinggroups/content/en_operations.html
@@ -2,7 +2,7 @@
<div id="preamble">
<div class="sectionbody">
<div class="paragraph">
-<p>Version 2.4</p>
+<p>Version 2.5</p>
</div>
<div id="toc" class="toc">
<div id="toctitle" class="title">Table of Contents</div>
@@ -37,7 +37,10 @@
<a href="#h.2s7d4f6g8h1j">SIG Formation, Leadership and Membership Composition</a>
</li>
<li>
- <a href="#h.3i6o8p2a4s7d">Governance</a>
+ <a href="#h.fk90431mwm">Leadership</a>
+ </li>
+ <li>
+ <a href="#h.5f9g1h7j3k5l">SIG Lead</a>
</li>
<li>
<a href="#h.7u2w4e6r8t1y">Tools and Communication</a>
@@ -60,6 +63,7 @@
<ul class="sectlevel2">
<li><a href="#h.puy6ear5wq5w">Steering Committee</a></li>
<li><a href="#h.prvx2gq33dat">Specification Committee</a></li>
+<li><a href="#h.vm49vv17pt">Technical Advisory Committee</a></li>
<li><a href="#h.zw4bu1rlcv5">Project Management Committee (PMC)</a></li>
<li><a href="#h.exw3gowdu1xz">Marketing and Brand Committee</a></li>
<li><a href="#h.fh7t00xr7txo">Relationship Between Committees</a></li>
@@ -406,7 +410,7 @@
</li>
<li>
The scope of the SIG must be consistent with the scope of the working
- group charter.
+ group charter
</li>
<li>
The SIG must have at all times three or more member organizations
@@ -426,7 +430,7 @@
</h4>
<p>
A SIG can be proposed by any member of the working group.The Steering
- committee must approve of creation of a SIG.
+ committee must approve the creation of a SIG.
</p>
<ul>
<li>
@@ -435,6 +439,9 @@
of the SIG, and how to participate.
</li>
<li>
+ The SIG proposal has one or more designated Special Interest Group Lead(s) (SIGL).
+ </li>
+ <li>
The scope of the SIG must be consistent with the scope of the working
group charter.
</li>
@@ -444,27 +451,44 @@
</li>
<li>
The working group's Steering Committee must approve the formal creation
- of the SIG
+ of the SIG.
+ </li>
+ </ul>
+ <h4 id="h.fk90431mwm"><a class="anchor" href="#h.fk90431mwm"></a><a class="link" href="#h.fk90431mwm">Leadership</a></h4>
+ <p>
+ Each SIG must have one or more designated SIGL. The SIGL must ensure
+ that the Special Interest Group;
+ </p>
+ <ul>
+ <li>
+ operates effectively by guiding the overall direction and by removing
+ obstacles, solving problems, and resolving conflicts;
</li>
<li>
- Once created, the SIG must name a Chair from within its membership
+ operates using open source rules of engagement of transparency and
+ open participation; and
+ </li>
+ <li>
+ conforms to the Eclipse Foundation Intellectual Property and
+ Antitrust Policies and associated processes specifically;
</li>
</ul>
<div class="sect4">
- <h5 id="h.5f9g1h7j3k5l">
- <a href="#h.5f9g1h7j3k5l">SIG Chair</a>
- </h5>
- <p>Chair</p>
+ <h4 id="h.5f9g1h7j3k5l">
+ <a class="anchor" href="#h.5f9g1h7j3k5l"></a>
+ <a class="link" href="#h.5f9g1h7j3k5l">SIG Lead</a>
+ </h4>
+ <p>Lead</p>
<ul>
<li>
- The primary functions of a Chair are administrative, including:
+ The primary functions of a Lead are administrative, including:
<ul>
<li>
Collecting and compiling topics for the meetings, and sharing the
agenda beforehand
</li>
<li>
- Chairing meetings of the SIG
+ Leading meetings of the SIG
</li>
<li>
Ensuring that meeting minutes are published to the Working
@@ -675,6 +699,30 @@
</div>
</div>
<div class="sect2">
+ <h3 id="h.vm49vv17pt"><a class="anchor" href="#h.vm49vv17pt"></a><a class="link" href="#h.vm49vv17pt">Technical Advisory Committee</a></h3>
+ <div class="paragraph">
+ <p>
+ The Technical Advisory Committee (TAC) recommends which Eclipse
+ Foundation open source projects should be included within the purview of
+ the associated working group.
+ </p>
+ <p>
+ It is responsible for establishing, evolving and enforcing policies and
+ processes that augment the EDP and the EFSP to support such things as
+ quality, functional safety, supply chain security and so on for the
+ Eclipse Foundation open source projects that participate in the
+ associated working groups branded releases. The committee establishes an
+ annual release roadmap and a roadmap process with project and PMC
+ stakeholders. The committee further establishes a coordinated release
+ plan. The TAC sets, evolves and enforces engineering policies and
+ procedures for the creation and distribution of the branded working group
+ releases. The TAC must establish a set of principles to guide its
+ deliberations which must be approved by the Steering Committee and
+ Executive Director.
+ </p>
+ </div>
+</div>
+<div class="sect2">
<h3 id="h.zw4bu1rlcv5"><a class="anchor" href="#h.zw4bu1rlcv5"></a><a class="link" href="#h.zw4bu1rlcv5">Project Management Committee (PMC)</a></h3>
<div class="paragraph">
<p>A PMC is not directly aligned with any Working Group.</p>
@@ -745,7 +793,7 @@
<div class="sect3">
<h4 id="h.co6j5eb09fww"><a class="anchor" href="#h.co6j5eb09fww"></a><a class="link" href="#h.co6j5eb09fww">Representative Obligations</a></h4>
<div class="paragraph">
-<p>Once elected to represent the members of their constituency, Elected representatives, like every other member of the committee, have the responsibility and obligation of directly defining and implementing the working group's charter. Working group committees require quorum and regularly vote on matters pertaining to the working group. As a result, elected representatives are required to be in regular attendance at meetings.</p>
+<p>Once elected to represent the members of their constituency, elected representatives, like every other member of the committee, have the responsibility and obligation of directly defining and implementing the working group's charter. Working group committees require quorum and regularly vote on matters pertaining to the working group. As a result, elected representatives are required to be in regular attendance at meetings.</p>
</div>
<div class="paragraph">
<p>Representatives may designate an alternate for committee representation. These alternates may be added to mailing lists and participate in meetings. Alternates can be assigned proxy for voting purposes.</p>
@@ -786,7 +834,7 @@
</div>
<div class="paragraph">
<p>
- For membership classes other than Committer Members, any individuals is an employee, consultant, director, officer, or agent of an organization that is a Member of that class in the working group may stand for election.
+ For membership classes other than Committer Members, any individual who is an employee, consultant, director, officer, or agent of an organization that is a Member of that class in the working group may stand for election.
However, each Member may have at most one individual stand for election to any particular committee.
Should more than one person be nominated from the same Member (including by self-nomination), it is incumbent on the Member representative to determine which should stand for election, and to do so prior to the start of the election.
Further, for clarity, a single Member may not have two representatives elected to any particular committee as representatives of their class of Member, even if this means a seat remains vacant.
@@ -798,42 +846,34 @@
</p>
</div>
<div class="paragraph">
-<p>All positions may be self nominated.</p>
-</div>
-<div class="paragraph">
<p>The members of that constituency are likewise eligible to vote for their representative. For Committer Members, this means the Committer Members engaged in projects under the purview of the working group; for all other classes of membership, the working group representatives of each Member of that class may vote.</p>
</div>
<div class="paragraph">
-<p>Elections pass through several phases:</p>
+<p>We typically allow ten business days for the Nomination Phase and Ballot Distribution Phase. As a result, it can often take a full month to complete the entire process. Additionally, extensions to these phases can be considered and will affect any arranged schedules. The typical phases of elections are:</p>
</div>
-<div class="olist arabic">
- <ol class="arabic">
- <li>
- Working Group Election Announcement
- </li>
- <li>
- Nomination Phase (Call for Nominations/Extensions)
- </li>
- <li>
- Nomination Acceptance Phase - Confirmation, Bio's and Pictures Submissions
- </li>
- <li>
- Notice of Candidates Standing Phase
- </li>
- <li>
- Ballot Distribution Phase
- </li>
- <li>
- Count of Results Phase
- </li>
- <li>
- Election Results Announcement
- </li>
- </ol>
-</div>
-<div class="paragraph">
-<p>We typically allow ten business days for the Nomination Phase and Ballot Distribution Phase. As a result, it can often take a full month to complete the entire process. Additionally, extensions to these phases can be considered and will affect any arranged schedules.</p>
-</div>
+<ul>
+ <li>
+ Working Group Election Announcement
+ </li>
+ <li>
+ Nomination Phase (Call for Nominations/Extensions)
+ </li>
+ <li>
+ Nomination Acceptance Phase - Confirmation, Bio’s and Pictures Submissions
+ </li>
+ <li>
+ Notice of Candidates Standing Phase
+ </li>
+ <li>
+ Ballot Distribution Phase
+ </li>
+ <li>
+ Count of Results Phase
+ </li>
+ <li>
+ Election Results Announcement
+ </li>
+</ul>
<div class="paragraph">
<p>All communication must be conducted via email using the general working group mailing list. Services may be used for an election, provided their use does not represent an unreasonable or onerous barrier for participation. Voters can only vote once and voting choices remain anonymous. Votes must be auditable, verifiable and independently observable.</p>
</div>
@@ -843,10 +883,7 @@
<p>All representative elections are conducted by the Eclipse Foundation.</p>
</div>
<div class="paragraph">
-<p>The Eclipse Foundation will use the working group's public mailing list to conduct the election (elections must always be run on a public mailing list).</p>
-</div>
-<div class="paragraph">
-<p>Nominations must be sent to the general mailing list of the working group. Ballots are distributed to email addresses on file with the Eclipse Foundation.</p>
+<p>The Eclipse Foundation will use the working group's public mailing list to conduct the election (elections must always be run on a public mailing list). Nominations must be sent to the general mailing list of the working group. Ballots are distributed to email addresses on file with the Eclipse Foundation. All positions may be self nominated.</p>
</div>
<div class="paragraph">
<p>Note that ballot distribution may be provided by the Eclipse Foundation via a third party election service.</p>
@@ -859,6 +896,77 @@
</div>
</div>
</div>
+<h4 id="h.14v4p5qjxn04"><a class="anchor" href="#h.14v4p5qjxn04"></a><a class="link" href="#h.14v4p5qjxn04">Appointed and Elected Representative Entitlement and Vacancy</a></h4>
+<p>
+ Each Eclipse working group charter establishes one or more standing
+ committees. These committees have as members a combination of appointed
+ and/or elected representatives, based on the various rights defined for each
+ class of participation. The following clarifications are intended to capture
+ the scenario when committee members’ status changes. In all cases, should
+ this description conflict with either the Eclipse Bylaws or the Eclipse
+ Foundation Working Group Process, those documents shall prevail.
+</p>
+<h4 id="h.ca4pf0vve99"><a class="anchor" href="#h.ca4pf0vve99"></a><a class="link" href="#h.ca4pf0vve99">Appointed Member Representative</a></h4>
+<p>
+ For those members entitled to appoint an individual as a representative to a
+ working group committee, that representative must be an employee, officer,
+ director, or consultant of the working group’s strategic membership. Should
+ that representative no longer meet this requirement, then they are deemed to
+ have immediately resigned from the committee.
+</p>
+<p>
+ Should a strategic member choose to not appoint a representative or replace
+ its appointed representative to a committee, the member’s seat is considered
+ vacant and the seat will not count towards achieving quorum for committee
+ meetings.
+</p>
+<h4 id="h.0kc03ejfmd"><a class="anchor" href="#h.0kc03ejfmd"></a><a class="link" href="#h.0kc03ejfmd">Elected Member Representative</a></h4>
+<p>
+ In the case of an elected member representative (i.e. Participant, Enterprise
+ and so on), such elected representative must be an employee, officer,
+ director, or consultant of a working group member in the associated class of
+ membership.
+</p>
+<p>
+ Should an elected representative no longer meet the requirements to hold the
+ seat (e.g., they leave the employment of the member or their member
+ organisation terminates their participation in the working group), then they
+ are deemed to have immediately resigned from the committee and the seat is
+ vacant.
+</p>
+<p>
+ Note that as defined in the Eclipse Bylaws and Eclipse Foundation Working
+ Group Process, individuals are elected to committees (and not the member
+ organisation). That is, the governing body is composed of individuals
+ (natural persons). The net result is that the member organisation of the
+ elected representative does not get to appoint someone else as the elected
+ representative if, for example, their employee leaves their company. Instead,
+ it is the governing body’s decision whether to leave the seat vacant or
+ request the Eclipse Foundation to call an election to fill the seat for an
+ interim period. While the seat is vacant, it will not count towards
+ achieving quorum.
+</p>
+<h4 id="h.lwm9d820"><a class="anchor" href="#h.lwm9d820"></a><a class="link">Elected Committer Member Representative</a></h4>
+<p>
+ In the case of an elected committer member representative, such
+ representative must be either an individual who is a Committer Member or an
+ employee, officer, director, or consultant of a Member in order to be
+ eligible to serve as a Committer Member. Committer member representatives
+ who, for whatever reason, no longer have committer status on a project under
+ the purview of the working group or are no longer a Committer member of the
+ Eclipse Foundation are deemed to have immediately resigned from the committee
+ and the seat is vacant. Committer member representatives who change
+ employment continue to serve in the committees they have been elected to
+ provided that they promptly address any necessary agreements required to
+ maintain their committer status on a project under the purview of the working
+ group.
+</p>
+<p>
+ As with elected member representatives, it is the governing body’s decision
+ whether to leave the seat vacant or request the Eclipse Foundation to call an
+ election to fill the seat for an interim period. While the seat is vacant,
+ it will not count towards achieving quorum.
+</p>
<div class="sect2">
<h3 id="h.16s3m8kuxa83"><a class="anchor" href="#h.16s3m8kuxa83"></a><a class="link" href="#h.16s3m8kuxa83">Committee Agenda and Minutes</a></h3>
<div class="paragraph">
@@ -1401,7 +1509,15 @@
<p>Allocated and administered by the Eclipse Webmaster.</p>
</div>
<div class="paragraph">
-<p>Hugo-based website, owned and managed by the Eclipse Foundation, and hosted on GitLab (either in the <a href="https://gitlab.eclipse.org/eclipsefdn/it/websites">Websites</a> group or in a working group specific GitLab group). Design and creation of the website starts when the proposal enters the Incubation Phase; and deployed in advance of the Working Group entering the Operational Phase. The steering committee must document a policy for determining who has privileged access to this resource.</p>
+<p>
+ Hugo-based website, owned and managed by the Eclipse Foundation, and hosted
+ on GitLab (either in the <a href="https://gitlab.eclipse.org/eclipsefdn/it/websites">Websites</a> group
+ or in a working group specific GitLab group). Design and creation of the
+ website starts when the proposal enters the Incubation Phase; and is deployed in
+ advance of the Working Group entering the Operational Phase. The steering
+ committee must document a policy for determining who has privileged access to
+ this resource.
+</p>
</div>
</div>
<div class="sect3">
@@ -1909,3 +2025,4 @@
</li>
</ul>
</div>
+</div>
