From: Jason Cooper <jason@lakedaemon.net>
To: Greg KH <greg@kroah.com>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [CORE TOPIC] hobbyist recruiting
Date: Thu, 15 May 2014 23:47:57 -0400 [thread overview]
Message-ID: <20140516034757.GX27822@titan.lakedaemon.net> (raw)
In-Reply-To: <20140512232302.GB17027@kroah.com>
On Tue, May 13, 2014 at 01:23:02AM +0200, Greg KH wrote:
> On Mon, May 12, 2014 at 12:38:38PM -0400, Jason Cooper wrote:
> > On Sun, May 11, 2014 at 09:26:30PM +0200, Greg KH wrote:
...
> > > If you track the number of unique people I take patches from, it's
> > > going up, as is our number of unique contributors to the kernel overall.
> > > It's been constantly increasing for the past 8 years, ever since I
> > > started tracking the kernel development statistics.
> >
> > Cool, I didn't know you were actively tracking that. Is the data
> > publicly hosted? Is that based on merged patches, or posted emails?
>
> It's based on merged patches, and can all be found at:
> https://github.com/gregkh/kernel-history
> along with the scripts that generate the numbers.
Great! Thanks.
> > My primary goal is to draw attention to the issue of aggressive mail
> > filtering, new devs can pop up anywhere, and acknowledging them. By
> > acknowledge, I mean answering the email, and treating them like everyone
> > else. But we have to spot the emails first.
>
> Why would someone "new" be treated any differently? Everyone should be
> treated with the same response and respect.
I fully agree. I'm concerned that my 'recruiting' mantra may be
mis-read as 'coddle the newbie and don't make any sudden movements'.
Which I am emphatically _not_ saying. We are in complete agreement wrt
treating everyone exactly the same.
I'd like to quantify responses, or lack thereof, to first-timers on the
primary mailinglists. From that data, determine *if* anything needs to
be tweaked. For me personally, I'll explicitly add a mailfilter to catch
first-time posters so that I can advise/direct them appropriately.
If others are interested in assisting in that effort, I'll post any
needed bits I've generated that are easy to integrate into the numerous
email workflows we all have.
thx,
Jason.
prev parent reply other threads:[~2014-05-16 3:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-11 5:30 Jason Cooper
2014-05-11 17:57 ` Sebastian Hesselbarth
2014-05-11 19:16 ` Levente Kurusa
2014-05-11 19:26 ` Greg KH
2014-05-11 19:50 ` Levente Kurusa
2014-05-11 20:33 ` Hans Verkuil
2014-05-11 21:35 ` Theodore Ts'o
2014-05-12 8:19 ` Wolfram Sang
2014-05-12 8:38 ` Wolfram Sang
2014-05-12 9:08 ` Li Zefan
2014-05-12 9:40 ` Hans Verkuil
2014-05-12 9:54 ` Wolfram Sang
2014-05-12 13:58 ` Andrew Lunn
2014-05-12 16:08 ` Stephen Hemminger
2014-05-21 14:32 ` Dan Carpenter
2014-05-12 16:38 ` Jason Cooper
2014-05-12 23:23 ` Greg KH
2014-05-16 3:47 ` Jason Cooper [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=20140516034757.GX27822@titan.lakedaemon.net \
--to=jason@lakedaemon.net \
--cc=greg@kroah.com \
--cc=ksummit-discuss@lists.linuxfoundation.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