XDP Newbie developer discussions
 help / color / mirror / Atom feed
From: Jesper Dangaard Brouer <brouer@redhat.com>
To: "xdp-newbies@vger.kernel.org" <xdp-newbies@vger.kernel.org>
Cc: Arthur Gautier <baloo@gandi.net>, brouer@redhat.com
Subject: Re: Should we remove xdp-newbies from kernel patch CC-list?
Date: Mon, 29 Jul 2019 14:09:16 +0200	[thread overview]
Message-ID: <20190729140916.77ede7a7@carbon> (raw)
In-Reply-To: <20190705204852.42be642f@carbon>

On Fri, 5 Jul 2019 20:48:52 +0200
Jesper Dangaard Brouer <brouer@redhat.com> wrote:

> On Fri, 5 Jul 2019 18:08:12 +0000
> Arthur Gautier <baloo@gandi.net> wrote:
> 
> > On Fri, Jul 05, 2019 at 03:24:28PM +0200, Jesper Dangaard Brouer wrote:  
> > > On Thu, 4 Jul 2019 16:19:00 +0200
> > > Jesper Dangaard Brouer <brouer@redhat.com> wrote:
> > >     
> > > > Question to people subscribed to xdp-newbies@vger.kernel.org mailing
> > > > list.  As you likely have noticed, patches and kbuild-bot is sending
> > > > XDP related kernel stuff to this mailing list.  This is caused by being
> > > > listed in the kernel MAINTAINERS file[1].
> > > > 
> > > > I've tried to create a survey to collect answers easier:
> > > >  https://www.surveymonkey.com/r/MTSL5T3    
> > > 
> > > I did choose an US holiday for this survey, so I guess US participants
> > > are not well represented, but the preliminary results are fairly clear
> > > with 69% for "Remove from MAINTAINERS file".
> > > 
> > > I'll give it until tomorrow, to get the US results, before sending a
> > > patch that removes this list.    
> > 
> > Hello Jesper,
> > 
> > To be fair, a ton of people in the US takes a holiday on July 5th to
> > make a 4 days weekend. You might want to let it run until Monday 8th.  
>  
> Fair point, it is bad timing.  Unfortunately I travel on holidays
> Sunday 7th, thus that will delay the patch until after my holidays, and
> likely after the merge window (as Linus will make rc8 or release this
> Sunday).  I guess, we are not in a hurry... so let's just wait, until
> after the merge window.

(Back from vacation...)
I've just closed the survey. The final results are very clear.

Results:
 - Remove from MAINTAINERS file = 72.73%
 - Keep in MAINTAINERS file     = 36.36%

I'm going to send a kernel patch shortly...

Thanks you all for participating in voting.  It is important to me that
we keep this XDP user community healthy and interactive.  I will try to
focus my info/mails to be more focused on how to getting started coding
with XDP/eBPF.

-- 
Best regards,
  Jesper Dangaard Brouer
  MSc.CS, Principal Kernel Engineer at Red Hat
  LinkedIn: http://www.linkedin.com/in/brouer

  reply	other threads:[~2019-07-29 12:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-04 14:19 Should we remove xdp-newbies from kernel patch CC-list? Jesper Dangaard Brouer
2019-07-05 13:24 ` Jesper Dangaard Brouer
2019-07-05 18:08   ` Arthur Gautier
2019-07-05 18:48     ` Jesper Dangaard Brouer
2019-07-29 12:09       ` Jesper Dangaard Brouer [this message]
2019-07-08 17:28 ` Zvi Effron
2019-07-08 21:31   ` David Miller
2019-07-08 21:38     ` Toke Høiland-Jørgensen

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=20190729140916.77ede7a7@carbon \
    --to=brouer@redhat.com \
    --cc=baloo@gandi.net \
    --cc=xdp-newbies@vger.kernel.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