From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-f42.google.com (mail-wm0-f42.google.com [74.125.82.42]) by dpdk.org (Postfix) with ESMTP id C196F2B98 for ; Fri, 31 Mar 2017 18:45:30 +0200 (CEST) Received: by mail-wm0-f42.google.com with SMTP id x124so3496061wmf.0 for ; Fri, 31 Mar 2017 09:45:30 -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:in-reply-to:references; bh=uUneaXf+HLti13MstAU/EkewIIsG3jeOk78eZkgQ3qw=; b=rocxxz8wdNMDXjzk9jf7Goqh1BnDiiptuDNyqpc9VMuLYleJEO2/ecz7U4ehsLOS3e V9nMhX/aYCXN8ZocHb5LkG88ikKC50mDxG7EN7bxkBbhclanjLoG+3lnsCld1Q7W2SES peCbhuXToKva0RGZKYTloQSKjQLhhDhM9/Wm2bd1H1WUdbkDuNz1xziTZU73Tyrly4JH /bUuV8bzE0pVvQ0lWwXCyvFWW8mS9mURTK5gi/XQnOQoRqQsR17zogbXvdxcya78/+gv n7jxJ4EnmoKjnbKaOcBSTSHp/qd2Py/nkQ2D6KqLJ3COGZmeFjARnvLNibEtfJEEA2Ke oXrQ== 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:in-reply-to :references; bh=uUneaXf+HLti13MstAU/EkewIIsG3jeOk78eZkgQ3qw=; b=XJXeIHwVQs5Vs+QKoIJ0piMTd3az3zKZEGRCe5NdGYH9Zvsds3XOSp+vShhL9fIP1U kjzCvBLURJDuRYbVbPPJJngy17CTIYOP1PfKvHqpOyM0DrNwA/kKUlLhYJ2kXpH9I3DF pF5Lb3aOV0bZqnLk/tVYUeDJ8/ar9e0mssJSzmpanKobEwId3+vcHCCA6T+GqDuCRZq5 CZ1ljwdSe9t8c3yTbVLrxAtuN4uXyWk2AnK9uixEqBdmEE4q0ODm0QhscxbgP5lGhJEx 6mwMJM0kVwouLVWo306G+VWeEhEAb4Xm5n5Elef1KppYoIMhfk85DGeNFkSinUQ9LoTq U5cQ== X-Gm-Message-State: AFeK/H2Q27QTOke6wZulLj1YQZzW+3T5XQCLc8gdQ0VjyV/GaWksW6/yX3En1/R+fyq+qP7p X-Received: by 10.28.59.8 with SMTP id i8mr4182847wma.27.1490978730405; Fri, 31 Mar 2017 09:45:30 -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.29 (version=TLS1_2 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 31 Mar 2017 09:45:29 -0700 (PDT) From: Thomas Monjalon To: web@dpdk.org Cc: moving@dpdk.org Date: Fri, 31 Mar 2017 18:44:16 +0200 Message-Id: <1490978656-20568-2-git-send-email-thomas.monjalon@6wind.com> X-Mailer: git-send-email 2.7.0 In-Reply-To: <1490978656-20568-1-git-send-email-thomas.monjalon@6wind.com> References: <1490978656-20568-1-git-send-email-thomas.monjalon@6wind.com> Subject: [dpdk-web] [PATCH 2/2] charter: simplify description of links 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:31 -0000 The charter was written without hyperlink support. The links are revisited now that it is in HTML format. Signed-off-by: Thomas Monjalon --- about/charter.html | 100 ++++++++++++++++++++++++++--------------------------- 1 file changed, 50 insertions(+), 50 deletions(-) diff --git a/about/charter.html b/about/charter.html index 1130cac..9fdf094 100644 --- a/about/charter.html +++ b/about/charter.html @@ -65,13 +65,13 @@ which are used to apply changes to specific parts of DPDK before these are pulled into the master repository, and a stable release repository. - This structure is documented at: - http://dpdk.org/browse/. + This structure is listed in + the repository home page.

The sub-projects that are also hosted as part of the DPDK Project are typically applications that are closely related to DPDK. - These are listed at: - http://dpdk.org/browse/. + These can be browsed in + the repository home page.

Changes to this structure, including approval for any new sub-projects, are the responsibility of the Technical Board @@ -180,7 +180,7 @@

  1. Approval of any exceptions to the Intellectual Property Policy - (see section 6.c). + (see clause 6.c).
  2. Approval of any changes to this document (see section 12). @@ -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 i) + (see clause 3.1.1.i) when making its decision on proposed new projects. Requests can be submitted by emailing techboard@dpdk.org. @@ -279,8 +279,8 @@ The Technical Board shall consist of:
    1. - The composition of the Technical Board is documented at: - http://dpdk.org/about/techboard. + The composition of the Technical Board is documented at + dpdk.org/about/techboard#members.
    2. To be added to or removed from the Technical Board:
        @@ -339,9 +339,8 @@ All Gold and Silver Members must be current corporate members of The Linux Foundation (at any level). Details of LF membership levels and rates are available in - The Linux Foundation Bylaws - https://www.linuxfoundation.org/about/bylaws. + The Linux Foundation Bylaws.
      1. All Gold and Silver Members enjoy the privileges and undertake the obligations described in this DPDK Project Charter, @@ -359,7 +358,7 @@ and any other committees established by the Governing Board.
      2. Participate in an open DPDK performance lab - as outlined in section 4, clause f below. + as outlined in clause 4.f below.
      3. Be prominently identified as Gold sponsors of the project at DPDK-funded events. @@ -380,7 +379,7 @@ and published publicly by the Governing Board.
      4. Participate in an open DPDK performance lab - as outlined in section 4, clause f below. + as outlined in clause 4.f below.
      5. Be identified as Silver sponsors of the project at DPDK-funded events. @@ -434,17 +433,14 @@

      For the core DPDK project, technical governance is documented in - the Contributor's Guidelines - (http://dpdk.org/doc/guides/contributing/) - and on the DPDK.org Development web page - (http://dpdk.org/dev). + the Contributor's Guidelines + and on the Development web page.

      For the other sub-projects within DPDK, technical governance will be documented in a CONTRIBUTING.txt file in the root directory for the sub-project. See http://dpdk.org/browse/apps/pktgen-dpdk/tree/CONTRIBUTING.TXT for an example. + >pktgen-dpdk/tree/CONTRIBUTING.TXT for an example.

      Intellectual Property Policy

        @@ -453,9 +449,8 @@ shall be made under the following licenses:
        1. - The GPLv2 license - (https://www.gnu.org/licenses/old-licenses/gpl-2.0.en.html) + The GPLv2 license shall be used for code that runs in the kernel. Current examples of this are:
            @@ -469,16 +464,15 @@ lib/librte_eal/linuxapp/kni/ethtool/ixgbe
        2. - A dual 3-clause BSD/GPLv2 license - (https://opensource.org/licenses/BSD-3-Clause, + A dual + 3-clause BSD/ https://www.gnu.org/licenses/old-licenses/gpl-2.0.en.html) - or 3-clause BSD/LGPLv2 license - (https://opensource.org/licenses/BSD-3-Clause, + >GPLv2 license or + 3-clause BSD/ https://www.gnu.org/licenses/old-licenses/lgpl-2.0.en.html) + >LGPLv2 license shall be used for code that is shared between the kernel and userspace. Current examples of this are:
        3. - The 3-clause BSD license - (https://opensource.org/licenses/BSD-3-Clause) + The 3-clause BSD license shall be used for all other contributions.
      1. All contributions shall include a "Signed-off-by:" line which certifies that the contribution complies with - the Developer Certificate of Origin - (http://developercertificate). + the Developer Certificate of Origin.
      2. If an alternative inbound or outbound license is required for compliance with the license for a leveraged open source project @@ -550,7 +551,7 @@ arises related to DPDK, The Linux Foundation will coordinate with the Governing Board to address gap funding requirements.
      3. - As described in 3.1.3 clause e, + As described in clause 3.1.3.e, the Governing Board will publish a public version of the budget. Questions on the budget should be addressed to the Governing Board.
      @@ -575,9 +576,9 @@

      Antitrust Guidelines

      1. - All members shall abide by The Linux Foundation Antitrust Policy - available at - http://www.linuxfoundation.org/antitrust-policy. + All members shall abide by + The Linux Foundation Antitrust Policy.
      2. All members shall encourage open participation from any organization able to meet the membership requirements, @@ -594,9 +595,8 @@ with approval from the LF.
      3. All participants in LF Project events shall abide by - The Linux Foundation Events Code of Conduct, available at: - - http://events.linuxfoundation.org/EVENT-CODE-OF-CONDUCT. + The Linux Foundation Events Code of Conduct.

      General Rules and Operations

      -- 2.7.0