From: "O'Driscoll, Tim" <tim.odriscoll@intel.com>
To: Francois Ozog <francois.ozog@linaro.org>,
"moving@dpdk.org" <moving@dpdk.org>
Subject: Re: [dpdk-moving] [Topics]
Date: Tue, 25 Oct 2016 11:27:57 +0000 [thread overview]
Message-ID: <26FA93C7ED1EAA44AB77D62FBE1D27BA676071BB@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <CAHFG_=UjcFHHWPwr-k64g7SgoSoT9vkEEuO6d0hzcXDiK8ouOA@mail.gmail.com>
> From: moving [mailto:moving-bounces@dpdk.org] On Behalf Of Francois Ozog
> Sent: Tuesday, October 25, 2016 9:59 AM
> To: moving@dpdk.org
> Subject: [dpdk-moving] [Topics]
>
> Hi,
>
> Tim mentioned we need to revise budget, actually I see a few set of topics adress:
> - legal: bylaws, CLA, TCO
> - governance: board, TSC...
> - finance: budget, membership
>
> 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...
That's a good list. I was thinking the same thing and had similar items in mind. If you can start some discussion on the legal issues, that would be great.
One thing I think we need to consider is what the benefits of membership would be. We didn't really cover this in our discussions earlier in the year. We're all agreed that technical contributions and decisions should be independent of membership, but it seems reasonable that companies who contribute should get something in return for their contribution to the project. Possibilities might include: board seats, having a say in how the project budget is spent, the ability to host equipment in a DPDK CI/test lab etc. This spans the "governance: board" and "membership" items above. I can look into this a bit further and post some further thoughts on this.
We also have a gap in terms of documenting technical governance. Even ignoring the move to LF, Matt in particular was looking for more clarity on this. Thomas: would you be willing to create and post a proposal on this?
Tim
next prev parent reply other threads:[~2016-10-25 11:28 UTC|newest]
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 [this message]
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
2016-10-26 15:00 ` Francois Ozog
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=26FA93C7ED1EAA44AB77D62FBE1D27BA676071BB@IRSMSX108.ger.corp.intel.com \
--to=tim.odriscoll@intel.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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).