ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Jason Cooper <jason@lakedaemon.net>
To: ksummit-discuss@lists.linuxfoundation.org
Subject: [Ksummit-discuss] [CORE TOPIC] hobbyist recruiting
Date: Sun, 11 May 2014 01:30:37 -0400	[thread overview]
Message-ID: <20140511053037.GQ12708@titan.lakedaemon.net> (raw)

All,

During the proposal period for last year's KS, there was quite a bit of
talk regarding maintainer survivorship.  imho, the best solution
involves continuously bringing in new maintainers and developers as they
crop up.  Should we encounter the unfortunate situation of needing to
find a replacement, having plenty of pre-trained developers on hand
gives us more flexibility.

As a hobbyist, I of course think the answer is recruiting more hobbyists
into the ranks :)

Unfortunately, we ran out of time during the lightning round last year
for me to give a short presentation on the topic of hobbyist recruiting.

I'm not a fan of reaching out in the direct sense.  I much prefer to
keep my eye out for new comers who seek out the community and make sure
they don't get ignored.  I know a lot of us have pretty aggressive mail
filtering out of necessity.  For those interested in assisting me, I'd
like to discuss creating some basic resources to facilitate spotting new
comers and directing them as appropriate.

Something as simple as creating a separate mailbox and ruleset for
senders we haven't seen before (with a few keywords to filter out the
spam) would help greatly.

On a related topic, I've also started receiving patches from first time
contributors who are taking part in the Eudyptula Challenge [1].  No, I
hadn't heard of it either.  It's very similar to the Matasano Crypto
Challenge [2], except that it builds up to contributing patches to the
kernel.

If this topic is accepted, I'll give a status update on the hobbyists
I've seen since the last KS, what work they've done (hint: those
Chromecasts can boot mainline now ;-), I'll also compile some rough
stats on first-time posters to the most popular email lists.  eg was it
legit, did anyone respond, did the poster return?  Currently, I'm
thinking lkml and lakml would be most relevant.  There may be other
lists I'm not aware of.  Please let me know if that's the case.

If anyone is already doing work in this area, I'd be interested in
hearing from you as well.

Nominations:

Jason Cooper		(auto-nominated)
Andrew Lunn
Sebastian Hesselbarth	(auto-nominated)

thx,

Jason.

[1] http://eudyptula-challenge.org/
[2] http://www.matasano.com/articles/crypto-challenges/

             reply	other threads:[~2014-05-11  5:30 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-11  5:30 Jason Cooper [this message]
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

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=20140511053037.GQ12708@titan.lakedaemon.net \
    --to=jason@lakedaemon.net \
    --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