Infra599 - Updated Eclipse Foundation Working Group Process Revision to Version 2.2
Signed-off-by: Zhou Fang <zhou.fang@eclipse-foundation.org>
Change-Id: I16765fa08e4aee3304a9c65a281ec58fb0e66efd
diff --git a/workinggroups/content/process.html b/workinggroups/content/process.html
index eeb0bc2..d20a856 100644
--- a/workinggroups/content/process.html
+++ b/workinggroups/content/process.html
@@ -1,7 +1,7 @@
<div id="preamble">
<div class="sectionbody">
<div class="paragraph">
-<p>Version 2.1</p>
+<p>Version 2.2</p>
</div>
<div id="toc" class="toc">
<div id="toctitle" class="title">Table of Contents</div>
@@ -154,7 +154,16 @@
<p>Specifications are created and maintained by Specification Projects. Each Specification Project is aligned with exactly one Working Group. Specification Projects are said to work under the purview of a particular Working Group, or—more specifically—the Specification Committee of a Working Group.</p>
</div>
<div class="paragraph">
-<p>Prior to the Working Group engaging in any specification work, the Steering Committee must vote to adopt a particular version of the EFSP or derivative thereof. The Steering Committee must further vote to adopt a default Patent License (either Compatible Patent License or Implementation Patent License) as defined by the Eclipse Foundation Intellectual Property Policy.</p>
+ <p>
+ The Eclipse Foundation Specification Process (EFSP) is the specification process for all
+ working groups that engage in specification development. A working group may tailor the EFSP
+ for their unique requirements provided they follow the process for doing so as defined in the
+ EFSP. As stated in the EFSP, the Implementation Patent License shall be the default Patent
+ License for working groups that engage in specification development. However, the EFSP
+ allows for a working group to override the default Implementation Patent License and instead
+ use the Compatible Patent License, as those terms are defined in the Eclipse Foundation
+ Intellectual Property Policy, by a super majority vote of the working group's Steering Committee.
+ </p>
</div>
</div>
</div>
@@ -496,7 +505,7 @@
<p>The <em>Incubation Phase</em> provides an opportunity to further evolve the Working Group Charter, recruit additional Participants, and start building and executing on the Marketing Plan.</p>
</div>
<div class="paragraph">
-<p>If the Working Group engages in specification work, the Steering Committee must formally agree by super-majority (two-thirds) vote to adopt the EFSP. They may opt to engage the Specification Committee to parameterize or otherwise specialize the process to suit the specific needs of the Working Group.</p>
+<p>If the Working Group engages in specification work, the Steering Committee may opt to engage the Specification Committee to parameterize or otherwise specialize the process to suit the specific needs of the Working Group.</p>
</div>
<div class="paragraph">
<p>Success criteria:</p>
@@ -513,15 +522,6 @@
<p>Working Group committees (as defined by the Charter) operational;</p>
</li>
<li>
-<p>When the Working Group engages in specification development:</p>
-</li>
-<li>
-<p>Formally adopt the Eclipse Foundation Specification Process or a derivative thereof;</p>
-</li>
-<li>
-<p>Formally adopt the choice of Patent License for Specifications;</p>
-</li>
-<li>
<p>Program Plan defined;</p>
</li>
<li>
