From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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 ; Fri, 31 Mar 2017 18:45:26 +0200 (CEST) Received: by mail-wm0-f43.google.com with SMTP id t189so3465913wmt.1 for ; 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 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 --- 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 @@

Mission of the Data Plane Development Kit Project

The mission of DPDK is to: -

    +
    1. Create an open source, production quality, vendor neutral software platform for enabling fast dataplane I/O, @@ -80,7 +80,7 @@

      Project Governance

      Governance for DPDK will be provided by two boards: -

        +
        1. A Governing Board which deals with budget, marketing, lab resources, administrative, legal and licensing issues. @@ -98,12 +98,12 @@

          The Governing Board covers the full scope of DPDK, including all sub-projects. Responsibilities of the Governing Board are: -

            +
            1. Electing a Chair to preside over meetings, authorize expenditures approved by the Governing Board, and manage any day-to-day operations. -
                +
                1. The Chair will be elected on an annual basis.
                2. @@ -145,13 +145,13 @@

                  Composition

                  The Governing Board shall consist of: -

                    +
                    1. One representative appointed by each Gold Member - as specified in clause 4.d.a below. + as specified in clause 4.d.i below.
                    2. Up to two Silver Member representatives - as specified in clause 4.e.a below. + as specified in clause 4.e.i below.
                    3. One representative of the Technical Board, to be nominated by the Technical Board on an annual basis. @@ -160,7 +160,7 @@

                      Conduct

                      Conduct of Governing Board meetings: -

                        +
                        1. Governing Board meetings shall be limited to the Governing Board representatives, @@ -177,7 +177,7 @@ (not just a ⅔ majority of those in attendance at the meeting). In the event of a deadlock the Governing Board Chair shall have the casting vote. -
                            +
                            1. Approval of any exceptions to the Intellectual Property Policy (see section 6.c). @@ -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: -
                                +
                                1. Electing a Chair to preside over meetings, and manage any day-to-day operations. -
                                    +
                                    1. The Chair will be elected on an annual basis.
                                    2. @@ -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 section 3.1.1, point ix) + (see section 3.1.1, point i) when making its decision on proposed new projects. Requests can be submitted by emailing techboard@dpdk.org. @@ -277,13 +277,13 @@

                                      Composition

                                      The Technical Board shall consist of: -

                                        +
                                        1. The composition of the Technical Board is documented at: http://dpdk.org/about/techboard.
                                        2. To be added to or removed from the Technical Board: -
                                            +
                                            1. A candidate must be nominated by an existing member of the Technical Board and
                                            2. @@ -291,7 +291,7 @@
                                          1. When adding or removing members, the Technical Board must consider the following: -
                                              +
                                              1. 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 @@

                                                Conduct

                                                Conduct of Technical Board meetings: -

                                                  +
                                                  1. Technical Board meetings shall be open to the public.
                                                  2. @@ -327,7 +327,7 @@

                                                  Membership

                                                  -
                                                    +
                                                    1. 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.
                                                    2. Gold Members shall be entitled to: -
                                                        +
                                                        1. Appoint a representative to the Governing Board and any other committees established by the Governing Board. @@ -370,7 +370,7 @@
                                                      1. Silver Members shall be entitled to: -
                                                          +
                                                          1. Annually elect one representative to the Governing Board and any other committees established by the Governing Board @@ -392,7 +392,7 @@
                                                          2. Gold and Silver Members shall be entitled to participate in an open DPDK Project performance lab (if created): -
                                                              +
                                                              1. 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: -
                                                                  +
                                                                  1. 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 for an example.

                                                                    Intellectual Property Policy

                                                                    -
                                                                      +
                                                                      1. All new inbound contributions to DPDK shall be made under the following licenses: -
                                                                          +
                                                                          1. The GPLv2 license (https://www.gnu.org/licenses/old-licenses/gpl-2.0.en.html) shall be used for code that runs in the kernel. Current examples of this are: -
                                                                              +
                                                                              1. lib/librte_eal/linuxapp/igb_uio
                                                                              2. @@ -481,10 +481,10 @@ >https://www.gnu.org/licenses/old-licenses/lgpl-2.0.en.html) shall be used for code that is shared between the kernel and userspace. Current examples of this are: -
                                                                                  +
                                                                                  • BSD/GPLv2: -
                                                                                      +
                                                                                      1. All files in: drivers/crypto/qat/qat_adf/
                                                                                      2. @@ -496,14 +496,14 @@
                                                                                    1. BSD/LGPLv2: -
                                                                                        +
                                                                                        1. lib/librte_eal/bsdapp/eal/include/exec-env/rte_dom0_common.h
                                                                                        2. lib/librte_eal/linuxapp/eal/include/exec-env/rte_dom0_common.h, rte_kni_common.h
                                                                                        -
                                                                                      +
                                                                                1. The 3-clause BSD license (

                                                                                  Budget

                                                                                  -
                                                                                    +
                                                                                    1. 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.
                                                                                    2. - As described in 3.1.3 clause v, + As described in 3.1.3 clause e, the Governing Board will publish a public version of the budget. Questions on the budget should be addressed to the Governing Board.

                                                                                    General & Administrative Expenses

                                                                                    -
                                                                                      +
                                                                                      1. 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 @@

                                                                                      Antitrust Guidelines

                                                                                      -
                                                                                        +
                                                                                        1. All members shall abide by The Linux Foundation Antitrust Policy available at @@ -588,7 +588,7 @@

                                                                                        Code of Conduct

                                                                                        -
                                                                                          +
                                                                                          1. The Governing Board may adopt a specific Project code of conduct, with approval from the LF. @@ -602,7 +602,7 @@

                                                                                            General Rules and Operations

                                                                                            The DPDK project shall be conducted so as to: -

                                                                                              +
                                                                                              1. Engage in the work of the project in a professional manner consistent with maintaining a cohesive community, @@ -628,13 +628,11 @@

                                                                                              Amendments

                                                                                              -
                                                                                                -
                                                                                              1. - 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. -
                                                                                              +

                                                                                              + 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. 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