Merge branches 'df-FO', 'df-submission-appeal' and 'df-remove-dir' in…

…to director-free

index.bs

@@ -369,11 +369,10 @@ Related Members</h5>
 	[=Related Members=] <em class="rfc2119">must</em> disclose these relationships
 	according to the mechanisms described in the <a href="https://www.w3.org/Member/Intro">New Member Orientation</a> [[INTRO]].
 
-<h3 id="Team">
+<h3 id="Team" oldids="def-Director">
 The W3C Team</h3>
 
 	The <dfn export lt="Team | W3C Team">Team</dfn> consists of
-	the Director,
 	<dfn>CEO</dfn>,
 	W3C paid staff,
 	unpaid interns,
@@ -386,24 +385,12 @@ The W3C Team</h3>
 	and communicates with the Members and the public
 	about the Web and W3C technologies.
 
-	The [=Director=] and CEO <em class="rfc2119">may</em> delegate responsibility
+	The CEO <em class="rfc2119">may</em> delegate responsibility
 	(generally to other individuals in the Team)
-	for any of their roles described in this document,
-	except <a href="#tag-participation">participation in the TAG</a>.</p>
-	<dfn noexport lt="Team Decision | Team's Decision">Team Decisions</dfn> derive from the [=Director=] and [=CEO=]'s authority,
+	for any of their roles described in this document.
+	<dfn noexport lt="Team Decision | Team's Decision">Team Decisions</dfn> derive from the [=CEO=]'s authority,
 	even when they are carried out by other members of the [=Team=].
 
-	The <dfn id="def-Director" export lt="Director|W3C Director">Director</dfn> is the lead technical architect at W3C,
-	whose responsibilities are identified throughout this document in relevant places.
-	Some key ones include:
-	assessing <a href="#def-Consensus" id="DirectorDecision">consensus</a> within W3C for architectural choices,
-	publication of <a href="#Reports">technical reports</a>,
-	and chartering new Groups;
-	appointing group <a href="#GeneralChairs">Chairs</a>,
-	adjudicating as "tie-breaker" for [=Group decision appeals=],
-	and deciding on the outcome of formal objections;
-	the Director is generally Chair of the <a href="#TAG">TAG</a>.
-
 	Team administrative information such as Team salaries,
 	detailed budgeting,
 	and other business decisions
@@ -2002,7 +1989,7 @@ Consensus</h4>
 	or <a href="#distributed-meeting">distributed</a>)
 	as well as through <a href=#discussion-archiving>persistent text-based discussions</a>.
 
-	Note: The Director and CEO have the role of
+	Note: The CEO has the role of
 	assessing consensus within the Advisory Committee.
 
 	The following terms are used in this document
@@ -5210,15 +5197,8 @@ Rejection of a Submission Request, and Submission Appeals</h3>
 	  the Team <em class="rfc2119">must not</em> make statements about why a Submission request was rejected.
 
 	  The [=Advisory Committee representative=](s) of the [=Submitters=](s)
-	  <em class="rfc2119">may</em> initiate a Submission Appeal
-	  of the [=Team's Decision=] to the [=TAG=]
-	  if the reasons are related to Web architecture,
-	  or to the [=Advisory Board=]
-	  if the request is rejected for other reasons.
-	  In this case the [=Team=] <em class="rfc2119">should</em> make available
-	  its rationale for the rejection to the appropriate body.
-	  The [=Team=] will establish a process for such appeals
-	  that ensures the appropriate <a href="#confidentiality-levels">level of confidentiality</a>.
+	  <em class="rfc2119">may</em> initiate a [=Submission Appeal=].
+	  The procedure for handling <dfn>Submission Appeals</dfn> is the same as for [=Formal Objections=].
 
 <h2 id="GAProcess">
 Process Evolution</h2>