From: Stephen Hemminger <stephen@networkplumber.org>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Jason Cooper <jason@lakedaemon.net>,
ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [CORE TOPIC] hobbyist recruiting
Date: Mon, 12 May 2014 09:08:53 -0700 [thread overview]
Message-ID: <20140512090853.7ba61854@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <20140512135836.GD3378@lunn.ch>
My impression is that although a small number of new developers come from the hobbyist
ranks, the large majority come from companies that are developing products that use Linux.
As Greg says if the hobbyist contributes they get hired up by some company in today's market.
I would be interested in hearing success and failures of others in getting these corporate
developers to contribute and get involved upstream. It can be a management issue, it could
be personal fears or it could be cultural but in my experience many talented people still shy
away from contributing to any upstream project.
In my world, the problem isn't hobbyist recruiting but internal recruiting; and keeping the
good people contributing instead of going off to other projects.
next prev parent reply other threads:[~2014-05-12 16:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-11 5:30 [Ksummit-discuss] [CORE TOPIC] hobbyist recruiting 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 [this message]
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=20140512090853.7ba61854@nehalam.linuxnetplumber.net \
--to=stephen@networkplumber.org \
--cc=andrew@lunn.ch \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.