ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Levente Kurusa <levex@linux.com>
To: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
	Jason Cooper <jason@lakedaemon.net>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [CORE TOPIC] hobbyist recruiting
Date: Sun, 11 May 2014 21:16:02 +0200	[thread overview]
Message-ID: <20140511190752.GC2527@linux.com> (raw)
In-Reply-To: <536FBA0E.5090301@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 4260 bytes --]

Hi,

On Sun, May 11, 2014 at 07:57:34PM +0200, Sebastian Hesselbarth wrote:
> On 05/11/2014 07:30 AM, Jason Cooper wrote:
> > 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.

For the past few months, I've been doing research on new contributors
and what I've found is there plenty of interest but people don't seem
to knwo where to start their journey. Another problem is that they
begin but fail to continue. They don't submit more than one patch.

Of course, the Eudyptula challenge did bring some new developers,
but as far as I see most of them posted only one patch/patchset.
Maybe, there is a way so that they will stay and work more?
Keep them somehow in the game, i.e. badges? Mozilla's Open Badges?

> 
> I copy Jason's proposal. Based on my last year's experience with the
> hobbyist slot on ELC, I suggest to continue the effort. It was an
> exciting experience and nice to see the people you know from the
> mailing lists.
> 
> Although I think Ksummit would be more suited and more interesting
> for Kernel hobbyists to attend than ELC was. The chance to meet known
> people and participate in interesting topics is higher than on the
> (IMHO) commercially orientated ELC.

Indeed, as a hobbyist I can second this!

And AFAIK last year the folks had some hobbyist spots.

> 
> Also, for the co-maintainer topic, I think some maintainers really
> need some supporters reviewing the basic stuff already. There is
> some maintainers who have people reducing the vast amount of patches,
> but some others really need a helping hand.
> 
> IMHO, even hobbyists are suited for co-maintainership as it is a
> good opportunity to get more insight into core kernel, common
> mistakes, patch organization, and git workflow and we should
> encourage promising recuitees early to constantly assist other
> maintainers.
> 
> Sebastian
> _______________________________________________
> Ksummit-discuss mailing list
> Ksummit-discuss@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

  reply	other threads:[~2014-05-11 19:16 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 [this message]
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=20140511190752.GC2527@linux.com \
    --to=levex@linux.com \
    --cc=jason@lakedaemon.net \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=sebastian.hesselbarth@gmail.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