DPDK website maintenance
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: web@dpdk.org, techboard@dpdk.org
Subject: Re: [dpdk-web] [dpdk-techboard] [PATCH] update techboard description
Date: Thu, 09 Mar 2017 11:24:03 +0100	[thread overview]
Message-ID: <2903339.cFK4MDzFIP@xps13> (raw)
In-Reply-To: <20170308152903.60009058@xeon-e3>

2017-03-08 15:29, Stephen Hemminger:
> 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. This will help CYA and attract a more diverse
> set of contributors. If a CoC is not created by techboard one will be placed
> upon us by LF.
> 
> One issue that has come up on the kernel developers list is how to handle people
> who spam the community with useless and broken patches. There is already an unofficial
> short list of known abusers who are ignored. As DPDK gets bigger we are bound
> to attract these clueless developers. What is the plan for that? Is it a tech
> board topic.

Yes it may be a techboard topic.
It can also be discussed on dev@dpdk.org before discussing in techboard meeting.
Feel free to open the discussion.

  reply	other threads:[~2017-03-09 10:24 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 [this message]
2017-03-09 10:49   ` Mcnamara, John
2017-03-09 17:25     ` Stephen Hemminger
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=2903339.cFK4MDzFIP@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=stephen@networkplumber.org \
    --cc=techboard@dpdk.org \
    --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).