summaryrefslogtreecommitdiff
path: root/about/techboard.html
blob: abf3e07c46672c033b55aae96d15afda02a0384f (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
<!DOCTYPE html>
<html lang="en">
<head>
	<meta charset="utf-8" />
	<meta name=viewport content="width=device-width, initial-scale=1" />
	<title>DPDK Technical Board</title>
	<link rel="stylesheet" href="/reset.css" />
	<link rel="stylesheet" href="/layout.css" />
	<link rel="stylesheet" href="/content.css" />
	<script type="text/javascript">
		var _gaq = _gaq || [];
		_gaq.push(['_setAccount', 'UA-39229303-1']);
		_gaq.push(['_setDomainName', 'dpdk.org']);
		_gaq.push(['_setAllowLinker', true]);
		_gaq.push(['_trackPageview']);
		(function() {
			var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
			ga.src = '//www.google-analytics.com/ga.js';
			var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
		})();
	</script>
</head>
<body>
<header>
	<h1><a href="//dpdk.org/"><img src="/logos/dpdk.png"
		alt="DPDK: Data Plane Development Kit"></a></h1>
	<nav>
		<ul>
			<li><a href="/">Home</a>
			<li><a href="/download">Download</a>
			<li><a href="/doc">Documentation</a>
			<li><a href="/dev">Development</a>
			<li><a href="/ml">Mailing Lists</a>
			<li><a href="/events">Events</a>
			<li><a href="/news">News</a>
			<li><a href="/about" id="current">About</a>
		</ul>
	</nav>
</header>
<section>
<h2>Technical Board</h2>

<p>More high level details are defined in the <a href="/about/charter">charter</a>.

<h3 id="scope">Scope</h3>
<p>The decision making process is primarily based on consensus.
However in rare cases, the Technical Board can make a decision
when consensus is not reached on the mailing list.
<p>The scope of this body is limited to the questions directly related
to the development in the following repositories:
<ul>
	<li>dpdk.git
	<li>dpdk-stable.git
	<li>dpdk-next-*.git
	<li>dpdk-ci.git
	<li>dpdk-web.git
</ul>

<h3 id="members">Members</h3>
<p>The 8 current members of
<a href="mailto:techboard@dpdk.org">techboard@dpdk.org</a> are:
<ul>
	<li>Bruce Richardson
	<li>Ferruh Yigit
	<li>Hemant Agrawal
	<li>Jerin Jacob
	<li>Konstantin Ananyev
	<li>Olivier Matz
	<li>Stephen Hemminger
	<li>Thomas Monjalon
</ul>

<h3 id="renewal">Renewal</h3>
<p>Technical Board positions are held by individuals, not companies.
However, employees of a single company should not occupy more than 40% of board seats.
<p>It can be decided to remove a member if there is an approval of 2/3 of the whole Technical Board.
It can be decided either to replace the member, or to redefine the size of the board.
<p>There will be some renewal when it will be felt as needed.

<h3 id="meetings">Meetings</h3>
<p>A short meeting happens on IRC (freenode #dpdk-board) every two weeks.
<p>The quorum required for a meeting to proceed is a 70% majority of the Technical Board.
<p>The Chair is a rotating role among members.
<p>Any contributor can ask to add a topic
in the <a href="https://annuel.framapad.org/p/r.0c3cc4d1e011214183872a98f6b5c7db">agenda</a>
by sending an email
to <a href="mailto:techboard@dpdk.org">techboard@dpdk.org</a>.
The board members will add any topic of interest
in the <a href="https://annuel.framapad.org/p/r.0c3cc4d1e011214183872a98f6b5c7db">agenda</a>.
<p>Minutes are sent to <a href="/ml/archives/dev/">dev@dpdk.org</a> so anyone can comment.
However, the technical discussions should happen in the original thread.
<p>There is a <a href="/dev/techboard-minutes">list of previous meeting minutes</a>.

<h3 id="roles">Roles</h3>
<ul>
	<li>The new project repositories must be approved by the Technical Board,
	while applying the non-technical criteria defined by
	the <a href="/about/charter#govboard">Governing Board</a>.
	<li>If a patch does not receive any or enough comment, the board may discuss it
	in order to provide an input on the mailing list.
	<li>If there is no consensus in a discussion, a decision can be taken
	by the Technical Board and explained on the mailing list.
</ul>
<p>For a vote to be passed, a majority (> 50%) of the total Technical Board is required
(not just a majority of those in attendance at the meeting).
In the event of a deadlock the Technical Board Chair shall have the casting vote.

</section>
<footer></footer>