DPDK community structure changes
 help / color / mirror / Atom feed
From: Hemant Agrawal <hemant.agrawal@nxp.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>,
	"O'Driscoll, Tim" <tim.odriscoll@intel.com>
Cc: "moving@dpdk.org" <moving@dpdk.org>,
	"techboard@dpdk.org" <techboard@dpdk.org>
Subject: Re: [dpdk-moving] [dpdk-techboard]  changes in the Technical Board
Date: Mon, 6 Feb 2017 12:53:27 +0000
Message-ID: <DB5PR04MB1605EF2F42723019975F8FB389400@DB5PR04MB1605.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <1536736.Y1UUVgnqSY@xps13>

HI Thomas,

> -----Original Message-----
> From: techboard [mailto:techboard-bounces@dpdk.org] On Behalf Of
> Thomas Monjalon
> Sent: Tuesday, January 31, 2017 4:43 PM
> To: O'Driscoll, Tim <tim.odriscoll@intel.com>
> Cc: moving@dpdk.org; techboard@dpdk.org
> Subject: Re: [dpdk-techboard] [dpdk-moving] changes in the Technical Board
> 
> 2017-01-25 11:57, O'Driscoll, Tim:
> > Next Meeting:
> > Tuesday January 31st at 3pm GMT, 4pm CET, 10am EST, 7am PST. We can
> discuss any preliminary input that Mike has from his membership
> discussions, discuss the desired budget level, and hopefully get an update
> from the Tech Board on any changes they're planning to make.
> 
> I have provided some feedbacks from the Technical Board in the charter.
> Please, could we discuss or approve them in the next meeting today?
> 
> We should also discuss about integrating the charter in the website.
> I suggest creating a dedicated page dpdk.org/charter linked from the "home"
> page and from the "about" page.
> 
> We also need to refresh the technical board description.
> I suggest to move the section http://dpdk.org/dev#board to a dedicated
> page dpdk.org/techboard linked from the "dev" page and from the "about"
> page.
> 
> Here is a first draft for the page dpdk.org/techboard:
> 

[Hemant]  I could not find details about the Technical Board Chair,  you may add some details about it as well e.g.

Technical Board Chair

How he will be elected? E.g. The Technical Board Chair will elected by the process of nomination/election within the technical board. 
Term ?  The term of technical board will be for 1 years. There are no restrictions,  the current Technical Board Chair can be re-elected for next term.
Governing Board Rep? He will be the representative of the Technical Board in Governing Board. He may choose to nominate another Technical Board Member to attend Governing Board meetings. 

> -------------------------
> 
> More high level details are defined in the dpdk.org/charter.
> 
> Scope
> 
> 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.
> The scope of this body is limited to the questions directly related to the
> development in the following repositories:
> 	- dpdk.git
> 	- dpdk-stable.git
> 	- dpdk-next-*.git
> 	- dpdk-ci.git
> 	- dpdk-web.git
> 
> Members
> 
> The 9 current members of techboard@dpdk.org are:
> 	* Bruce Richardson
> 	* Hemant Agrawal
> 	* Jan Blunck
> 	* Jerin Jacob
> 	* Konstantin Ananyev
> 	* Olivier Matz
> 	* Stephen Hemminger
> 	* Thomas Monjalon
> 	* Yuanhan Liu
> 
> Renewal
> 
> Technical Board positions are held by individuals, not companies.
> However, employees of a single company should not occupy more than 40%
> of board seats.
> 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.
> There will be some renewal when it will be felt as needed.
> 
> Meetings
> 
> A short meeting happens on IRC every two weeks.
> The quorum required for a meeting to proceed is a 70% majority of the
> Technical Board.
> Any contributor can ask to add a topic in the agenda by sending an email to
> techboard@dpdk.org.
> The board members will add any topic of interest in the agenda.
> 
> Roles
> 
> The new project repositories must be approved by the Technical Board,
> while applying the non-technical criteria defined by the Governing Board.
> If a technical discussion lacks of explanation, details or evidence, it will be
> asked on the mailing list.
> If a patch does not receive any or enough comment, the board will help to
> make it progressing on the mailing list.
> If there is no consensus in a discussion, a decision can be taken by the
> Technical Board and explained on the mailing list.
> 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.
> 
> Feedback
> 
> Minutes are sent to dev@dpdk.org so anyone can comment.
> However, the technical discussions should happen in the original thread.
> 
> -------------------------

      parent reply	other threads:[~2017-02-06 12:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-25 11:57 [dpdk-moving] Minutes from "Moving DPDK to Linux Foundation" call, January 24th O'Driscoll, Tim
2017-01-25 15:48 ` Wiles, Keith
2017-01-25 16:16   ` O'Driscoll, Tim
2017-01-25 16:30     ` Ed Warnicke
2017-01-25 17:10       ` O'Driscoll, Tim
2017-01-25 17:29         ` George Zhao
2017-01-25 17:39           ` Zhu, Heqing
2017-01-25 18:06             ` O'Driscoll, Tim
2017-01-25 18:15               ` Michael Dolan
2017-01-26  1:33           ` Xu, Qian Q
2017-01-31 11:12 ` [dpdk-moving] changes in the Technical Board Thomas Monjalon
2017-01-31 11:55   ` Vincent Jardin
2017-01-31 13:16     ` Thomas Monjalon
2017-01-31 13:40   ` O'Driscoll, Tim
2017-02-06 12:53   ` Hemant Agrawal [this message]

Reply instructions:

You may reply publicly 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=DB5PR04MB1605EF2F42723019975F8FB389400@DB5PR04MB1605.eurprd04.prod.outlook.com \
    --to=hemant.agrawal@nxp.com \
    --cc=moving@dpdk.org \
    --cc=techboard@dpdk.org \
    --cc=thomas.monjalon@6wind.com \
    --cc=tim.odriscoll@intel.com \
    /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

This inbox may be cloned and mirrored by anyone:

	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

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.moving


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