DPDK community structure changes
 help / color / mirror / Atom feed
From: "Mcnamara, John" <john.mcnamara@intel.com>
To: Dave Neary <dneary@redhat.com>, "moving@dpdk.org" <moving@dpdk.org>
Subject: Re: [dpdk-moving] Proposal a Committer model
Date: Thu, 17 Nov 2016 08:14:41 +0000	[thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE202661E75@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <582CBEBA.5030301@redhat.com>



> -----Original Message-----
> From: Dave Neary [mailto:dneary@redhat.com]
> Sent: Wednesday, November 16, 2016 8:17 PM
> To: Mcnamara, John <john.mcnamara@intel.com>; moving@dpdk.org
> Subject: Re: [dpdk-moving] Proposal a Committer model
> 
> Hi,
> 
> Does it make sense to have this discussion on "moving"? I thought this
> list was reserved for conversations related to the move to the LF, while
> this seems like something which is independent of, and orthogonal to, the
> move. Shouldn't this be a topic of discussion for the developer community,
> dev@dpdk.org?
> 


Hi,

I meant to cross post it between moving@dpdk.org and dev@dpdk.org since, as you say, this affects the developer community as well. I'll repost it to dev@dpdk.org.

John

      reply	other threads:[~2016-11-17  8:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-15 23:35 Mcnamara, John
2016-11-16 10:45 ` Thomas Monjalon
2016-11-16 15:13   ` Bruce Richardson
2016-11-16 16:23     ` Wiles, Keith
2016-11-16 19:42     ` Jerin Jacob
2016-11-17  9:27       ` Mcnamara, John
2016-11-17 13:43         ` Thomas Monjalon
2016-11-17 14:05           ` Wiles, Keith
2016-11-18 10:45             ` Hemant Agrawal
2016-11-18 17:14               ` Stephen Hemminger
2016-11-17 22:57         ` Ed Warnicke
2016-11-18 10:45         ` Hemant Agrawal
2016-11-16 20:16 ` Dave Neary
2016-11-17  8:14   ` Mcnamara, John [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=B27915DBBA3421428155699D51E4CFE202661E75@IRSMSX103.ger.corp.intel.com \
    --to=john.mcnamara@intel.com \
    --cc=dneary@redhat.com \
    --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).