DPDK community structure changes
 help / color / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: web@dpdk.org
Cc: moving@dpdk.org
Subject: [dpdk-moving] [PATCH 2/2] charter: simplify description of links
Date: Fri, 31 Mar 2017 18:44:16 +0200
Message-ID: <1490978656-20568-2-git-send-email-thomas.monjalon@6wind.com> (raw)
In-Reply-To: <1490978656-20568-1-git-send-email-thomas.monjalon@6wind.com>

The charter was written without hyperlink support.
The links are revisited now that it is in HTML format.

Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com>
---
 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:
-	<a href= "/browse/">http://dpdk.org/browse/</a>.
+	This structure is listed in
+	the <a href= "/browse/">repository home page</a>.
 <p>
 	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:
-	<a href= "/browse/">http://dpdk.org/browse/</a>.
+	These can be browsed in
+	the <a href= "/browse/">repository home page</a>.
 <p>
 	Changes to this structure, including approval for any new sub-projects,
 	are the responsibility of the Technical Board
@@ -180,7 +180,7 @@
 	<ol>
 		<li>
 			Approval of any exceptions to the Intellectual Property Policy
-			(see <a href="#licexception">section 6.c</a>).
+			(see <a href="#licexception">clause 6.c</a>).
 		<li>
 			Approval of any changes to this document
 			(see <a href="#amendments">section 12</a>).
@@ -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 i</a>)
+		(see <a href="#subprojcriteria">clause 3.1.1.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>.
@@ -279,8 +279,8 @@
 	The Technical Board shall consist of:
 <ol>
 	<li>
-		The composition of the Technical Board is documented at:
-		<a href="/about/techboard">http://dpdk.org/about/techboard</a>.
+		The composition of the Technical Board is documented at
+		<a href="/about/techboard#members">dpdk.org/about/techboard#members</a>.
 	<li>
 		To be added to or removed from the Technical Board:
 	<ol>
@@ -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
 		<a href="https://www.linuxfoundation.org/about/bylaws">
-		https://www.linuxfoundation.org/about/bylaws</a>.
+		The Linux Foundation Bylaws</a>.
 	<li>
 		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.
 		<li>
 			Participate in an open DPDK performance lab
-			as outlined in <a href="#lab">section 4, clause f</a> below.
+			as outlined in <a href="#lab">clause 4.f</a> below.
 		<li>
 			Be prominently identified as Gold sponsors of the project
 			at DPDK-funded events.
@@ -380,7 +379,7 @@
 			and published publicly by the Governing Board.
 		<li>
 			Participate in an open DPDK performance lab
-			as outlined in <a href="#lab">section 4, clause f</a> below.
+			as outlined in <a href="#lab">clause 4.f</a> below.
 		<li>
 			Be identified as Silver sponsors of the project
 			at DPDK-funded events.
@@ -434,17 +433,14 @@
 </ol>
 <p>
 	For the core DPDK project, technical governance is documented in
-	the Contributor's Guidelines
-	(<a href="/doc/guides/contributing/"
-	>http://dpdk.org/doc/guides/contributing/</a>)
-	and on the DPDK.org Development web page
-	(<a href="/dev/">http://dpdk.org/dev</a>).
+	the <a href="/doc/guides/contributing/">Contributor's Guidelines</a>
+	and on the <a href="/dev/">Development web page</a>.
 <p>
 	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 <a href="/browse/apps/pktgen-dpdk/tree/CONTRIBUTING.TXT"
-	>http://dpdk.org/browse/apps/pktgen-dpdk/tree/CONTRIBUTING.TXT</a> for an example.
+	>pktgen-dpdk/tree/CONTRIBUTING.TXT</a> for an example.
 
 <h2 id="ip">Intellectual Property Policy</h2>
 <ol>
@@ -453,9 +449,8 @@
 		shall be made under the following licenses:
 	<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>)
+			The <a href="https://www.gnu.org/licenses/old-licenses/gpl-2.0.en.html"
+			>GPLv2 license</a>
 			shall be used for code that runs in the kernel.
 			Current examples of this are:
 		<ol>
@@ -469,16 +464,15 @@
 				lib/librte_eal/linuxapp/kni/ethtool/ixgbe
 		</ol>
 		<li>
-			A dual 3-clause BSD/GPLv2 license
-			(<a href="https://opensource.org/licenses/BSD-3-Clause"
-			>https://opensource.org/licenses/BSD-3-Clause</a>,
+			A dual
+			<a href="https://opensource.org/licenses/BSD-3-Clause"
+			>3-clause BSD</a>/
 			<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>)
-			or 3-clause BSD/LGPLv2 license
-			(<a href="https://opensource.org/licenses/BSD-3-Clause"
-			>https://opensource.org/licenses/BSD-3-Clause</a>,
+			>GPLv2</a> license or
+			<a href="https://opensource.org/licenses/BSD-3-Clause"
+			>3-clause BSD</a>/
 			<a href="https://www.gnu.org/licenses/old-licenses/lgpl-2.0.en.html"
-			>https://www.gnu.org/licenses/old-licenses/lgpl-2.0.en.html</a>)
+			>LGPLv2</a> license
 			shall be used for code that is shared between the kernel and userspace.
 			Current examples of this are:
 		<ul>
@@ -486,36 +480,43 @@
 				BSD/GPLv2:
 			<ol>
 				<li>
-					All files in: drivers/crypto/qat/qat_adf/
+					All files in
+					<a href="/browse/dpdk/tree/drivers/crypto/qat/qat_adf/"
+					>qat_adf</a>
 				<li>
-					lib/librte_eal/common/include/rte_pci_dev_features.h,
-					rte_pci_dev_feature_defs.h
+					<a href="/browse/dpdk/tree/lib/librte_eal/common/include/rte_pci_dev_features.h"
+					>rte_pci_dev_features.h</a>,
+					<a href="/browse/dpdk/tree/lib/librte_eal/common/include/rte_pci_dev_feature_defs.h"
+					>rte_pci_dev_feature_defs.h</a>
 				<li>
-					lib/librte_eal/linuxapp/xen_dom0/dom0_mm_dev.h,
-					dom0_mm_misc.c
+					<a href="/browse/dpdk/tree/lib/librte_eal/linuxapp/xen_dom0/dom0_mm_dev.h"
+					>dom0_mm_dev.h</a>,
+					<a href="/browse/dpdk/tree/lib/librte_eal/linuxapp/xen_dom0/dom0_mm_misc.c"
+					>dom0_mm_misc.c</a>
 			</ol>
 			<li>
 				BSD/LGPLv2:
 			<ol start="4">
 				<li>
-					lib/librte_eal/bsdapp/eal/include/exec-env/rte_dom0_common.h
+					<a href="/browse/dpdk/tree/lib/librte_eal/bsdapp/eal/include/exec-env/rte_dom0_common.h"
+					>rte_dom0_common.h</a>
 				<li>
-					lib/librte_eal/linuxapp/eal/include/exec-env/rte_dom0_common.h,
-					rte_kni_common.h
+					<a href="/browse/dpdk/tree/lib/librte_eal/linuxapp/eal/include/exec-env/rte_dom0_common.h"
+					>rte_dom0_common.h</a>,
+					<a href="/browse/dpdk/tree/lib/librte_eal/linuxapp/eal/include/exec-env/rte_kni_common.h"
+					>rte_kni_common.h</a>
 			</ol>
 		</ul>
 		<li>
-			The 3-clause BSD license
-			(<a href="https://opensource.org/licenses/BSD-3-Clause"
-			>https://opensource.org/licenses/BSD-3-Clause</a>)
+			The <a href="https://opensource.org/licenses/BSD-3-Clause"
+			>3-clause BSD license</a>
 			shall be used for all other contributions.
 	</ol>
 	<li>
 		All contributions shall include a "Signed-off-by:" line
 		which certifies that the contribution complies with
-		the Developer Certificate of Origin
-		(<a href="http://developercertificate.org"
-		>http://developercertificate</a>).
+		the <a href="http://developercertificate.org"
+		>Developer Certificate of Origin</a>.
 	<li id="licexception">
 		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.
 	<li>
-		As described in <a href="#govtransp">3.1.3 clause e</a>,
+		As described in <a href="#govtransp">clause 3.1.3.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>
@@ -575,9 +576,9 @@
 <h2 id="antitrust">Antitrust Guidelines</h2>
 <ol>
 	<li>
-		All members shall abide by The Linux Foundation Antitrust Policy
-		available at <a href="http://www.linuxfoundation.org/antitrust-policy">
-		http://www.linuxfoundation.org/antitrust-policy</a>.
+		All members shall abide by
+		<a href="http://www.linuxfoundation.org/antitrust-policy"
+		>The Linux Foundation Antitrust Policy</a>.
 	<li>
 		All members shall encourage open participation
 		from any organization able to meet the membership requirements,
@@ -594,9 +595,8 @@
 		with approval from the LF.
 	<li>
 		All participants in LF Project events shall abide by
-		The Linux Foundation Events Code of Conduct, available at:
-		<a href="http://events.linuxfoundation.org/EVENT-CODE-OF-CONDUCT">
-		http://events.linuxfoundation.org/EVENT-CODE-OF-CONDUCT</a>.
+		<a href="http://events.linuxfoundation.org/EVENT-CODE-OF-CONDUCT"
+		>The Linux Foundation Events Code of Conduct</a>.
 </ol>
 
 <h2 id="genrules">General Rules and Operations</h2>
-- 
2.7.0

  reply index

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-31 16:44 [dpdk-moving] [PATCH 1/2] charter: standardize numbering Thomas Monjalon
2017-03-31 16:44 ` Thomas Monjalon [this message]
2017-05-30 20:19 ` Thomas Monjalon

Reply instructions:

You may reply publically to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1490978656-20568-2-git-send-email-thomas.monjalon@6wind.com \
    --to=thomas.monjalon@6wind.com \
    --cc=moving@dpdk.org \
    --cc=web@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

DPDK community structure changes

Archives are clonable:
	git clone --mirror http://inbox.dpdk.org/moving/0 moving/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 moving moving/ http://inbox.dpdk.org/moving \
		moving@dpdk.org
	public-inbox-index moving


Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.moving


AGPL code for this site: git clone https://public-inbox.org/ public-inbox