From: Stephen Hemminger <stephen@networkplumber.org>
To: "Mcnamara, John" <john.mcnamara@intel.com>
Cc: Thomas Monjalon <thomas.monjalon@6wind.com>,
"web@dpdk.org" <web@dpdk.org>,
"techboard@dpdk.org" <techboard@dpdk.org>
Subject: Re: [dpdk-web] [dpdk-techboard] [PATCH] update techboard description
Date: Thu, 9 Mar 2017 09:25:11 -0800 [thread overview]
Message-ID: <20170309092511.5a3d5e7f@xeon-e3> (raw)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE233256855@IRSMSX104.ger.corp.intel.com>
On Thu, 9 Mar 2017 10:49:24 +0000
"Mcnamara, John" <john.mcnamara@intel.com> wrote:
> > -----Original Message-----
> > From: web [mailto:web-bounces@dpdk.org] On Behalf Of Stephen Hemminger
> > Sent: Wednesday, March 8, 2017 11:29 PM
> > To: Thomas Monjalon <thomas.monjalon@6wind.com>
> > Cc: web@dpdk.org; techboard@dpdk.org
> > Subject: Re: [dpdk-web] [dpdk-techboard] [PATCH] update techboard
> > description
> >
> > ...
> >
> > Fine as far as it goes. There are some later issues that need to be
> > addressed in revisions. We need a Code Of Conduct and a process for
> > handling infractions documented before first offense.
>
> Hi Stephen,
>
> Agreed. We should do that as soon as possible. Do you have any recommendations
> for a suitable CoC from a similar Open Source community.
>
> John
>
Opendaylight has no CoC but the web page has good resources:
https://wiki.opendaylight.org/view/GettingStarted:Code_of_Conduct
Openstack has one:
https://www.openstack.org/legal/community-code-of-conduct/
next prev parent reply other threads:[~2017-03-09 17:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-20 11:24 [dpdk-web] " Thomas Monjalon
2017-03-08 23:29 ` [dpdk-web] [dpdk-techboard] " Stephen Hemminger
2017-03-09 10:24 ` Thomas Monjalon
2017-03-09 10:49 ` Mcnamara, John
2017-03-09 17:25 ` Stephen Hemminger [this message]
2017-03-09 10:28 ` [dpdk-web] " Thomas Monjalon
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=20170309092511.5a3d5e7f@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=john.mcnamara@intel.com \
--cc=techboard@dpdk.org \
--cc=thomas.monjalon@6wind.com \
--cc=web@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).