ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Levente Kurusa <levex@linux.com>
Cc: Jason Cooper <jason@lakedaemon.net>,
	ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [CORE TOPIC] hobbyist recruiting
Date: Sun, 11 May 2014 21:26:30 +0200	[thread overview]
Message-ID: <20140511192630.GA14115@kroah.com> (raw)
In-Reply-To: <20140511190752.GC2527@linux.com>

On Sun, May 11, 2014 at 09:16:02PM +0200, Levente Kurusa wrote:
> Of course, the Eudyptula challenge did bring some new developers,
> but as far as I see most of them posted only one patch/patchset.

How do you know who is doing this challenge and who isn't?  I see a lot
of new people coming in with multiple sets of patches for cleanups and
good fixes over the past month or so.  Trying to track where they
actually come from is nothing I really care about, and is probably
impossible.

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.

> Maybe, there is a way so that they will stay and work more?

I have loads of work for people to do if they want to do it:
	drivers/staging/*/TODO

> Keep them somehow in the game, i.e. badges? Mozilla's Open Badges?

Gamifaction?  Really?  No.

greg k-h

  reply	other threads:[~2014-05-11 19:27 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 [this message]
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

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=20140511192630.GA14115@kroah.com \
    --to=greg@kroah.com \
    --cc=jason@lakedaemon.net \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=levex@linux.com \
    /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