infra-4229 updated about page for working groups

Signed-off-by: Zhou Fang <zhou.fang@eclipse-foundation.org>

Change-Id: I12ced40246dfef1b5c0775508f6deb738db261f2
diff --git a/workinggroups/about.php b/workinggroups/about.php
index 6e26d97..a10763b 100644
--- a/workinggroups/about.php
+++ b/workinggroups/about.php
@@ -21,7 +21,7 @@
 
 include ($App->getProjectCommon());
 
-$pageTitle = "About Eclipse Working Groups";
+$pageTitle = "About Working Groups";
 $Theme->setPageTitle($pageTitle);
 $Theme->setPageKeywords("eclipse, working, groups");
 $Theme->setPageAuthor("Christopher Guindon");
diff --git a/workinggroups/content/en_about.php b/workinggroups/content/en_about.php
index 906348d..b8b03d5 100644
--- a/workinggroups/content/en_about.php
+++ b/workinggroups/content/en_about.php
@@ -16,93 +16,70 @@
 ?>
 <h1><?php print $pageTitle; ?></h1>
 <h2>Fostering open industry collaboration to develop new industry platforms</h2>
-<h3 id="wg-intro">Introducing Eclipse Working Groups</h3>
-<p>Companies looking to drive innovation and efficiencies within their own
-  organizations are increasingly looking to external sources to advance new
-  ideas. Commonly referred to as “open innovation,” this paradigm encourages
-  collaboration across organizational boundaries, and is often practiced in the
-  open source community. Eclipse Working Groups allow organizations to combine
-  the best practices of open source development with a set of services required
-  for open innovation, enabling organizations to foster industry collaborations.</p>
-<p>Eclipse Working Groups provide a vendor-neutral governance structure that
-  allow organizations to freely collaborate on new technology development. Based
-  on the experience within the Eclipse community, collaboration among
-  organizations can:</p>
+<p>
+  Companies, organizations, and individuals looking to drive innovation and efficiencies within industry are increasingly looking to external sources to advance new ideas. Commonly referred to as “open innovation,” this paradigm encourages collaboration across organizational boundaries, and is often practiced in the open source community. Working groups allow organizations to combine the best practices of open source development with a set of services required for open innovation, enabling organizations to foster industry collaborations.
+</p>
+<p>
+  At the Eclipse Foundation, working groups provide a vendor-neutral governance structure that allows members of the foundation to collaborate on solving industry problems and to drive shared innovation through the related Eclipse Foundation open source projects. The collaboration promotes and augments Eclipse technologies to meet the needs of specific industries and communities, including through the development and implementation of joint marketing programs to increase awareness, adoption, and contributions. Find out more about the <a href="/org/workinggroups/operations.php#relationship-with-open-source-projects">relationship between working groups and projects</a>. 
+</p>
+<p>
+  Through working groups, member organizations can collaborate to:
+</p>
 <ul>
-  <li>help improve the supply chain of software development tools in a
-    particular industry</li>
-  <li>create a new technology platform that increases interoperability among
-    organizations and technologies</li>
-  <li>allow organizations to increase their use of open source technology.</li>
+  <li>help improve the supply chain of software development tools, frameworks, and runtimes in a particular industry</li>
+  <li>develop specifications in open source</li>
+  <li>create new technology platforms that increases interoperability among organizations and technologies</li>
+  <li>drive the industry adoption and support of strategic open source projects and technologies, including developer advocacy, marketing outreach, brand promotion, compatibility program, etc. </li>
 </ul>
-<p>The Eclipse Foundation, through Eclipse Working Groups, provides five basic
-  services to enable these types of collaborations:</p>
-<ul>
-  <li><a href="#wg-neutral">Governance</a></li>
-  <li><a href="#wg-ip">Intellectual Property Management and Licensing</a></li>
-  <li><a href="#wg-process">Development Processes</a></li>
-  <li><a href="#wg-infra">IT Infrastructure</a></li>
-  <li><a href="#wg-eco">Ecosystem Development</a></li>
-</ul>
-<p>Any collaboration needs these services. Eclipse Working Groups make it easy
-  to reuse the services provided by the Eclipse Foundation rather than creating
-  them from scratch.</p>
-<h2 id="wg-neutral" class="h3">Vendor-Neutral Governance</h2>
-<p>Good governance controlling how decisions are made, policies are set and
-  disputes resolved is important for any successful collaboration.</p>
-<p>The Eclipse Foundation, a not-for-profit corporation, is governed by a set of
-  bylaws, agreements, and policies that ensure a vendor-neutral governance model
-  for Working Group collaborations.</p>
-<p>All entities in a Working Group participate based on their contributions and
-  merit. No one individual or organization has any special status or veto.</p>
-<h2 id="wg-ip" class="h3">Intellectual Property (IP) Management</h2>
-<p>Collaborations among different organizations requires due diligence on the
-  co-developed intellectual property. Eclipse Working Groups are established
-  under the IP policies of the Eclipse Foundation. These policies ensure that
-  any open source software created in Eclipse projects is available for use by
-  anyone, including developers of commercial software products.</p>
-<p>The Eclipse Foundation consciously promotes and encourages software vendors
-  to use Eclipse technology for building their commercial software products and
-  services. This is made possible by the requirement that all Eclipse projects
-  are licensed under the Eclipse Public License (EPL), a commercial-friendly OSI
-  approved licensed.</p>
-<p>The Eclipse Foundation also undertakes a number of steps to attempt to ensure
-  the pedigree of the intellectual property contained within Eclipse projects.
-  The first step in the due diligence process is trying to ensure that all
-  contributions are made by the rightful copyright holder and made under the
-  EPL. All committers are required to sign a committer agreement stipulating
-  that all of their contributions are their original work and are being
-  contributed under the EPL.</p>
-<p>The second step is requiring that all source code for contributions created
-  outside the Eclipse development process go through the Eclipse Foundation IP
-  approval process. This process includes analyzing selected code contributions
-  to ascertain the provenance of the code and its license compatibility with the
-  EPL. Contributions that contain code not compatible with the EPL are intended
-  to be screened out through this approval process and thus not added to an
-  Eclipse project.</p>
-<p>The end result is a level of confidence that Eclipse open source projects can
-  be safely distributed in commercial products.</p>
-<h2 id="wg-infra" class="h3">IT Infrastructure</h2>
-<p>The Eclipse Foundation manages the IT infrastructure for Eclipse Working
-  Groups, including Git code repositories, Bugzilla databases, Hudson CI
-  servers, development-oriented mailing lists and newsgroups, download sites and
-  websites.</p>
-<p>The infrastructure is designed to provide reliable and scalable services for
-  the committers developing the Eclipse technology and the consumers using the
-  technology.</p>
-<h2 id="wg-process" class="h3">Development Process</h2>
-<p>The Eclipse community has created a successful development process for
-  large-scale distributed development that involves many different
-  organizations. At the core of the Eclipse process are the common open source
-  development principles of openness, transparency, and meritocracy. The Eclipse
-  Foundation provides services and support to help Working Groups implement and
-  succeed in their collaborative development.</p>
-<h2 id="wg-eco" class="h3">Ecosystem Development</h2>
-<p>An important way that the Eclipse Foundation supports the community is
-  through active marketing and promotion of Eclipse Working Groups and the wider
-  Eclipse ecosystem.</p>
-<p>To assist in the development of the Eclipse Working Groups, the Eclipse
-  Foundation organizes a number of activities, including co-operative marketing
-  events, community conferences (EclipseCon, Eclipse Day), online resource
-  (Eclipse Marketplace), bi-annual Members meetings, and other programs to
-  promote the entire Eclipse community.</p>
+<p>Participation in a working group is only open to Eclipse Foundation members.</p>
+
+<h2 id="wg-services" style="font-size: 27px">Services for Working Groups</h3>
+<p>
+  The Eclipse Foundation provides working groups with <a href="#wg-neutral">vendor-neutral governance</a> , <a href="#wg-eco">ecosystem development and marketing services</a>, <a href="#wg-collaborative">collaborative management</a>, <a href="#wg-spec">specification development</a> and <a href="#wg-branding">branding and compatibility</a>.
+</p>
+<p>
+  The foundation also provides <a href="/org/services/#IP_Management">intellectual property management and licensing</a>, shared <a href="/org/services/#IT">IT infrastructure</a>, and <a href="/org/services/#Development">development processes</a> for the projects complemented and promoted by the working groups.
+</p>
+
+<h3 id="wg-neutral">Vendor-Neutral Governance</h3>
+<p>
+  Good governance controlling how decisions are made, policies are set and disputes resolved is important for any successful collaboration.
+</p>
+<p>
+  The Eclipse Foundation, a not-for-profit corporation, is governed by a set of Bylaws, agreements, and policies, including antitrust and intellectual property management policies, that ensure a vendor-neutral governance model for working group collaborations.
+</p>
+<p>
+  All entities in a working group participate based strictly on their contributions and merit. Working groups are able to define rights based on membership within a working group. This ensures that no one individual or organization has any special status or veto.
+</p>
+
+<h3 id="wg-eco">Ecosystem Development and Marketing</h3>
+<p>
+  Working groups are most effective when a diverse group of organizations get involved and collaborate. The Eclipse Foundation provides marketing expertise, processes, and platforms to enable working group members to jointly grow the awareness of and participation in working groups and their projects.
+</p>
+<p>
+  Our team of marketing professionals support working groups with brand development, press and analyst relations, content creation (e.g. white papers, case studies, eBooks), event coordination, advertising, social media management, and other working group-specific activities. Find out more about the <a href="/org/services/marketing">marketing services</a> provided by the Foundation.
+</p>
+
+<h3 id="wg-collaborative">Collaborative management</h3>
+<p>
+  There is a tight coupling between working groups and open source projects hosted at the Eclipse Foundation that is very valuable to the open source community. Working groups can help coordinate the efforts of otherwise separate open source projects by providing things like shared vision and a roadmap; and determine how to leverage working group resources to best serve the open source community. The Foundation helps set up shared responsibilities, manages budgets and provides governance for these shared initiatives. 
+</p>
+<p>
+  The <a href="https://marketplace.eclipse.org/">Eclipse Marketplace</a> and <a href="https://open-vsx.org/">OpenVSX registry</a> are concrete examples of cross-project initiatives that working groups have built with the collaborative management offered by the Eclipse Foundation.
+</p>
+
+<h3 id="wg-spec">Specification Development</h3>
+<p>
+  A specification provides definitions, descriptions of semantic behavior, data formats, protocols, and/or other referenced specifications, along with technical artifacts, intended to enable the development and verify compatibility of independent implementations.
+</p>
+<p>
+The <a href="/projects/efsp/">Eclipse Foundation Specification Process</a> (EFSP) defines a general framework for the development of specifications in open source at the Eclipse Foundation. All specification development occurs under the purview of a working group that — through their designated specification committee — plays a critical role in the general governance, and management of the intellectual property flows that are particular to specifications.
+</p>
+
+<h3 id="wg-branding">Branding and Compatibility</h3>
+<p>
+  Working groups can build on the value of their specifications and develop a trusted ecosystem of implementers and consumers, by creating a branding and compatibility program. . Products that implement specifications and pass the corresponding Technology Compatibility Kit (TCK) can be branded as compatible implementations. Consumers can trust that branded products are truly compatible.
+</p>
+
+<h3>Join a Working Group</h3>
+<p><a href="/org/workinggroups/explore.php">Explore our working groups</a> to learn more about their vision and scope, and how to join.</p>
\ No newline at end of file