DPDK community structure changes
 help / color / Atom feed
From: Dave Neary <dneary@redhat.com>
To: Francois Ozog <francois.ozog@linaro.org>, moving@dpdk.org
Subject: Re: [dpdk-moving] [Topics]
Date: Wed, 26 Oct 2016 14:47:08 +0200
Message-ID: <5810A5CC.4030508@redhat.com> (raw)
In-Reply-To: <CAHFG_=UjcFHHWPwr-k64g7SgoSoT9vkEEuO6d0hzcXDiK8ouOA@mail.gmail.com>

Hi again,

On 10/25/2016 10:58 AM, Francois Ozog wrote:
> Tim mentioned we need to revise budget, actually I see a few set of
> topics  adress:
> - legal: bylaws, CLA, TCO

I would like to ask for what OVS had to agree to - I suspect that it is
very lightweight, there are probably not even specific by-laws - I would
not be surprised to find that it was a corporate contributors agreement
only.

I don't know what you mean by a TCO, but I do not believe we should add
a CLA (beyond what I mention below).

> - governance: board, TSC...

I do think we should create a budget oversight group, but a board and
TSC sounds a lot like the default set-up for an LF project which is
bootstrapping - that's not the case for DPDK, we have a technical
governance framework in place already, I do not see the need to set up a
TSC.

> - finance: budget, membership

It will be good to discuss whether we want to have a membership
agreement or whether we would be happy with a generic organizational
copyright and patent license (explicitly agreeing to license
contributions under the BSD license + patent grant) with a DCO for
contributions, tied to the signed-off-by on patches (which we have
already, unless I am mistaken).

Thanks,
Dave.

> I'll post a few things on [legal] later today.
> 
> Cordially,
> 
> François-Frédéric
> 
> PS: just saw the mailing list anouncement, so I bcc'ed the people I know
> just in case...
> 
> 
> 
> -- 
> Linaro <http://www.linaro.org/>	
> François-Frédéric Ozog | /Director Linaro Networking Group/
> T: +33.67221.6485 <tel:%2B33.67221.6485>
> francois.ozog@linaro.org <mailto:francois.ozog@linaro.org> | Skype: ffozog
> 
> 

-- 
Dave Neary - NFV/SDN Community Strategy
Open Source and Standards, Red Hat - http://community.redhat.com
Ph: +1-978-399-2182 / Cell: +1-978-799-3338

  parent reply index

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-25  8:58 Francois Ozog
2016-10-25 11:27 ` O'Driscoll, Tim
2016-10-25 14:00   ` [dpdk-moving] description of technical governance Thomas Monjalon
2016-10-26 10:21     ` O'Driscoll, Tim
2016-10-28  9:13       ` O'Driscoll, Tim
2016-10-28 16:52         ` Matt Spencer
2016-10-28 19:22           ` Thomas Monjalon
2016-10-28 22:54             ` Vincent Jardin
2016-10-31 15:20               ` Matt Spencer
2016-10-31 16:07                 ` Michael Dolan
2016-10-31 16:18                   ` Matt Spencer
2016-10-31 16:33                     ` Michael Dolan
2016-10-31 16:43                       ` Matt Spencer
2016-10-31 16:52                         ` Michael Dolan
2016-10-31 16:56                           ` O'Driscoll, Tim
2016-10-31 16:58                             ` Michael Dolan
2016-10-31 18:31                             ` Jan Blunck
2016-10-31 19:41                               ` Vincent JARDIN
     [not found]                   ` <DB5PR04MB1605482F1C67F9B797EB9AE289A60@DB5PR04MB1605.eurprd04.prod.outlook.com>
2016-11-08  8:11                     ` Jaswinder Singh
2016-11-08  9:37                       ` O'Driscoll, Tim
2016-12-20 14:41       ` Thomas Monjalon
2016-10-25 14:55 ` [dpdk-moving] [Topics] Dave Neary
2016-10-26 12:47 ` Dave Neary [this message]
2016-10-26 15:00   ` Francois Ozog

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=5810A5CC.4030508@redhat.com \
    --to=dneary@redhat.com \
    --cc=francois.ozog@linaro.org \
    --cc=moving@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