From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <thomas.monjalon@6wind.com>
Received: from mail-wm0-f43.google.com (mail-wm0-f43.google.com [74.125.82.43])
 by dpdk.org (Postfix) with ESMTP id 43F0A3B5
 for <web@dpdk.org>; Fri, 31 Mar 2017 18:45:26 +0200 (CEST)
Received: by mail-wm0-f43.google.com with SMTP id t189so3465913wmt.1
 for <web@dpdk.org>; Fri, 31 Mar 2017 09:45:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=6wind-com.20150623.gappssmtp.com; s=20150623;
 h=from:to:cc:subject:date:message-id;
 bh=XIgdk7l1bNb5xrcP/QVNzrha2EnY6xoDaVO6bA4oZXY=;
 b=Gc030LvTjlIkBaMxTdCGc/joi25J/NIUgdAuW2IHJUMdus2hC9Js35ZbqbZJ1+yonJ
 2WFs5NCwDXisrKd6uW8JBB8p4KhaFhX8K62Z2f+oglU/Mzmdxmx2QXF63OpbSUaZLzDa
 Z3o6xWPP8YRbqLLkBUWIKO/y3Wr3K5IKPbmRUlkUEYwea836v8+t1nzJTygRVOQ8mjmT
 krYSlyM3Z/zZgHYyPOBwcu+sXeL7sgH5rMwPqrFTR/tHwXAhaCy2Ozhpz+XliWMljktI
 F9W+10qR0AMcSjDCxZLCtVUs8ki9sm3SJfxnkFrR+fEAqpRR52zecJQfUqEw1E1v1WZ9
 qYHQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20161025;
 h=x-gm-message-state:from:to:cc:subject:date:message-id;
 bh=XIgdk7l1bNb5xrcP/QVNzrha2EnY6xoDaVO6bA4oZXY=;
 b=eQ93ZnCpWjgbU1ypbg3C/Wta2uxZGex0U4SD4ED8pQnfr4f1WjcAy6ClA5svqLZA4H
 /xWaDZWcC51zFvWty+MhkzhYG1FpewgSdsn8EfEn1sGKDrtdQmFtvFo2vURO/RLbTEDs
 Lt2cILnexrXCFoeVxotpG++jUqFQaQnoH/HgwF7pN2m4yHz0rofJ9oK7S2JH290edNNZ
 W3s03rjUezyahfdkk0oZIQGy9JEL5acAs50EdfA0LHb/IBS1ZCHbxrjjR5nVGa5+lXbj
 DWefTrzpzDqrYmEu9hyUswDzNEgGPW0q1scpwFWpzSyXO0oXJ53t6TDa5irULAehp//r
 sl1g==
X-Gm-Message-State: AFeK/H2dTjH4Kd/iLL+GG9dSbnJH9YCAf3+V1aYtfnU1P5aocCD+jh6FxGuCpHMjZnSwA1By
X-Received: by 10.28.143.84 with SMTP id r81mr4016067wmd.14.1490978725812;
 Fri, 31 Mar 2017 09:45:25 -0700 (PDT)
Received: from XPS13.localdomain (184.203.134.77.rev.sfr.net. [77.134.203.184])
 by smtp.gmail.com with ESMTPSA id v14sm7328981wra.43.2017.03.31.09.45.24
 (version=TLS1_2 cipher=ECDHE-RSA-AES128-SHA bits=128/128);
 Fri, 31 Mar 2017 09:45:24 -0700 (PDT)
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: web@dpdk.org
Cc: moving@dpdk.org
Date: Fri, 31 Mar 2017 18:44:15 +0200
Message-Id: <1490978656-20568-1-git-send-email-thomas.monjalon@6wind.com>
X-Mailer: git-send-email 2.7.0
Subject: [dpdk-web] [PATCH 1/2] charter: standardize numbering
X-BeenThere: web@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK website maintenance <web.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/web>,
 <mailto:web-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/web/>
List-Post: <mailto:web@dpdk.org>
List-Help: <mailto:web-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/web>,
 <mailto:web-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Fri, 31 Mar 2017 16:45:26 -0000

Use the same numbering format in every sections:
	1.a.i.1

Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com>
---
 about/charter.html | 82 ++++++++++++++++++++++++++----------------------------
 content.css        |  9 ++++++
 2 files changed, 49 insertions(+), 42 deletions(-)

diff --git a/about/charter.html b/about/charter.html
index eb8b0ba..1130cac 100644
--- a/about/charter.html
+++ b/about/charter.html
@@ -42,7 +42,7 @@
 <h2 id="mission">Mission of the Data Plane Development Kit Project</h2>
 <p>
 	The mission of DPDK is to:
-<ol type="a">
+<ol>
 	<li>
 		Create an open source, production quality, vendor neutral
 		software platform for enabling fast dataplane I/O,
@@ -80,7 +80,7 @@
 <h2 id="governance">Project Governance</h2>
 <p>
 	Governance for DPDK will be provided by two boards:
-<ol type="1">
+<ol>
 	<li>
 		A Governing Board which deals with budget, marketing,
 		lab resources, administrative, legal and licensing issues.
@@ -98,12 +98,12 @@
 <p>
 	The Governing Board covers the full scope of DPDK, including all sub-projects.
 	Responsibilities of the Governing Board are:
-<ol type="i">
+<ol>
 	<li>
 		Electing a Chair to preside over meetings,
 		authorize expenditures approved by the Governing Board,
 		and manage any day-to-day operations.
-	<ol type="a">
+	<ol>
 		<li>
 			The Chair will be elected on an annual basis.
 		<li>
@@ -145,13 +145,13 @@
 <h4 id="govcomposition">Composition</h4>
 <p>
 	The Governing Board shall consist of:
-<ol type="i">
+<ol>
 	<li>
 		One representative appointed by each Gold Member
-		as specified in <a href="#goldrep">clause 4.d.a</a> below.
+		as specified in <a href="#goldrep">clause 4.d.i</a> below.
 	<li>
 		Up to two Silver Member representatives
-		as specified in <a href="#silverrep">clause 4.e.a</a> below.
+		as specified in <a href="#silverrep">clause 4.e.i</a> below.
 	<li>
 		One representative of the Technical Board,
 		to be nominated by the Technical Board on an annual basis.
@@ -160,7 +160,7 @@
 <h4 id="govconduct">Conduct</h4>
 <p>
 	Conduct of Governing Board meetings:
-<ol type="i">
+<ol>
 	<li>
 		Governing Board meetings shall be limited to
 		the Governing Board representatives,
@@ -177,7 +177,7 @@
 		(<em>not</em> just a &frac23; majority of those in attendance at the meeting).
 		In the event of a deadlock the Governing Board Chair
 		shall have the casting vote.
-	<ol type="a">
+	<ol>
 		<li>
 			Approval of any exceptions to the Intellectual Property Policy
 			(see <a href="#licexception">section 6.c</a>).
@@ -217,11 +217,11 @@
 	A separate Technical Board may be established for other sub-projects
 	in future if any of them grows sufficiently large to require one.
 	Responsibilities of the Technical Board are:
-<ol type="i">
+<ol>
 	<li>
 		Electing a Chair to preside over meetings,
 		and manage any day-to-day operations.
-	<ol type="a">
+	<ol>
 		<li>
 			The Chair will be elected on an annual basis.
 		<li>
@@ -235,7 +235,7 @@
 		will be defined by the Technical Board.
 		The Technical Board will apply non-technical criteria
 		for new sub-projects that are defined by the Governing Board
-		(see <a href="#subprojcriteria">section 3.1.1, point ix</a>)
+		(see <a href="#subprojcriteria">section 3.1.1, point i</a>)
 		when making its decision on proposed new projects.
 		Requests can be submitted by emailing
 		<a href="mailto:techboard@dpdk.org">techboard@dpdk.org</a>.
@@ -277,13 +277,13 @@
 <h4 id="techcomposition">Composition</h4>
 <p>
 	The Technical Board shall consist of:
-<ol type="i">
+<ol>
 	<li>
 		The composition of the Technical Board is documented at:
 		<a href="/about/techboard">http://dpdk.org/about/techboard</a>.
 	<li>
 		To be added to or removed from the Technical Board:
-	<ol type="a">
+	<ol>
 		<li>
 			A candidate must be nominated by an existing member of the Technical Board and
 		<li>
@@ -291,7 +291,7 @@
 	</ol>
 	<li>
 		When adding or removing members, the Technical Board must consider the following:
-	<ol type="a">
+	<ol>
 		<li>
 			Positions on the Technical Board are determined based on technical merit.
 			A new member must have a strong history of contribution
@@ -311,7 +311,7 @@
 <h4 id="techconduct">Conduct</h4>
 <p>
 	Conduct of Technical Board meetings:
-<ol type="i">
+<ol>
 	<li>
 		Technical Board meetings shall be open to the public.
 	<li>
@@ -327,7 +327,7 @@
 </ol>
 
 <h2 id="membership">Membership</h2>
-<ol type="a">
+<ol>
 	<li>
 		DPDK is a free, open source project that welcomes all contributors.
 		Anybody can use or contribute to DPDK.
@@ -353,7 +353,7 @@
 		may from time to time adopt with notice to members.
 	<li>
 		Gold Members shall be entitled to:
-	<ol type="a">
+	<ol>
 		<li id="goldrep">
 			Appoint a representative to the Governing Board
 			and any other committees established by the Governing Board.
@@ -370,7 +370,7 @@
 	</ol>
 	<li>
 		Silver Members shall be entitled to:
-	<ol type="a">
+	<ol>
 		<li id="silverrep">
 			Annually elect one representative to the Governing Board
 			and any other committees established by the Governing Board
@@ -392,7 +392,7 @@
 	<li id="lab">
 		Gold and Silver Members shall be entitled to participate in
 		an open DPDK Project performance lab (if created):
-	<ol type="a">
+	<ol>
 		<li>
 			They will be able to contribute hardware
 			to be hosted in the lab for DPDK performance testing.
@@ -421,7 +421,7 @@
 	Beyond that, each sub-project within DPDK shall be responsible
 	for its own technical governance and technical decision making,
 	including issues such as:
-<ol type="a">
+<ol>
 	<li>
 		Determining the process and tools to be used
 		for development, CI, validation etc.
@@ -447,18 +447,18 @@
 	>http://dpdk.org/browse/apps/pktgen-dpdk/tree/CONTRIBUTING.TXT</a> for an example.
 
 <h2 id="ip">Intellectual Property Policy</h2>
-<ol type="a">
+<ol>
 	<li>
 		All new inbound contributions to DPDK
 		shall be made under the following licenses:
-	<ol type="a">
+	<ol>
 		<li>
 			The GPLv2 license
 			(<a href="https://www.gnu.org/licenses/old-licenses/gpl-2.0.en.html"
 			>https://www.gnu.org/licenses/old-licenses/gpl-2.0.en.html</a>)
 			shall be used for code that runs in the kernel.
 			Current examples of this are:
-		<ol type="i">
+		<ol>
 			<li>
 				lib/librte_eal/linuxapp/igb_uio
 			<li>
@@ -481,10 +481,10 @@
 			>https://www.gnu.org/licenses/old-licenses/lgpl-2.0.en.html</a>)
 			shall be used for code that is shared between the kernel and userspace.
 			Current examples of this are:
-		<ol type="i">
+		<ul>
 			<li>
 				BSD/GPLv2:
-			<ol type="1">
+			<ol>
 				<li>
 					All files in: drivers/crypto/qat/qat_adf/
 				<li>
@@ -496,14 +496,14 @@
 			</ol>
 			<li>
 				BSD/LGPLv2:
-			<ol type="1">
+			<ol start="4">
 				<li>
 					lib/librte_eal/bsdapp/eal/include/exec-env/rte_dom0_common.h
 				<li>
 					lib/librte_eal/linuxapp/eal/include/exec-env/rte_dom0_common.h,
 					rte_kni_common.h
 			</ol>
-		</ol>
+		</ul>
 		<li>
 			The 3-clause BSD license
 			(<a href="https://opensource.org/licenses/BSD-3-Clause"
@@ -533,7 +533,7 @@
 </ol>
 
 <h2 id="budget">Budget</h2>
-<ol type="a">
+<ol>
 	<li>
 		The Governing Board shall approve an annual budget
 		and never commit to spend in excess of funds raised.
@@ -550,13 +550,13 @@
 		arises related to DPDK, The Linux Foundation will coordinate
 		with the Governing Board to address gap funding requirements.
 	<li>
-		As described in <a href="#govtransp">3.1.3 clause v</a>,
+		As described in <a href="#govtransp">3.1.3 clause e</a>,
 		the Governing Board will publish a public version of the budget.
 		Questions on the budget should be addressed to the Governing Board.
 </ol>
 
 <h2 id="expenses">General &amp; Administrative Expenses</h2>
-<ol type="a">
+<ol>
 	<li>
 		The Linux Foundation shall have custody of and final authority
 		over the usage of any fees, funds and other cash receipts.
@@ -573,7 +573,7 @@
 </ol>
 
 <h2 id="antitrust">Antitrust Guidelines</h2>
-<ol type="a">
+<ol>
 	<li>
 		All members shall abide by The Linux Foundation Antitrust Policy
 		available at <a href="http://www.linuxfoundation.org/antitrust-policy">
@@ -588,7 +588,7 @@
 </ol>
 
 <h2 id="coc">Code of Conduct</h2>
-<ol type="a">
+<ol>
 	<li>
 		The Governing Board may adopt a specific Project code of conduct,
 		with approval from the LF.
@@ -602,7 +602,7 @@
 <h2 id="genrules">General Rules and Operations</h2>
 <p>
 	The DPDK project shall be conducted so as to:
-<ol type="a">
+<ol>
 	<li>
 		Engage in the work of the project in a professional manner
 		consistent with maintaining a cohesive community,
@@ -628,13 +628,11 @@
 </ol>
 
 <h2 id="amendments">Amendments</h2>
-<ol type="a">
-	<li>
-		This charter may be amended by a two-thirds vote of
-		the entire Governing Board,
-		subject to approval by The Linux Foundation.
-		Proposed changes must be communicated publicly
-		to the community prior to being approved by the Governing Board.
-</ol>
+<p>
+	This charter may be amended by a two-thirds vote of
+	the entire Governing Board,
+	subject to approval by The Linux Foundation.
+	Proposed changes must be communicated publicly
+	to the community prior to being approved by the Governing Board.
 
 </section>
diff --git a/content.css b/content.css
index 4336558..2d94ec3 100644
--- a/content.css
+++ b/content.css
@@ -168,6 +168,15 @@ section#charter ol {
 	text-align: justify;
 	text-justify: inter-word;
 }
+section#charter ol {
+	list-style-type: lower-latin;
+}
+section#charter ol ol {
+	list-style-type: lower-roman;
+}
+section#charter ol ol ol {
+	list-style-type: lower-decimal;
+}
 section#charter li {
 	margin-top: 0.6em;
 }
-- 
2.7.0