ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Hans Verkuil <hverkuil@xs4all.nl>
To: Li Zefan <lizefan@huawei.com>, Wolfram Sang <wsa@the-dreams.de>
Cc: Jason Cooper <jason@lakedaemon.net>,
	ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [CORE TOPIC] hobbyist recruiting
Date: Mon, 12 May 2014 11:40:29 +0200	[thread overview]
Message-ID: <5370970D.2030205@xs4all.nl> (raw)
In-Reply-To: <53708F74.3070200@huawei.com>

On 05/12/2014 11:08 AM, Li Zefan wrote:
> On 2014/5/12 16:38, Wolfram Sang wrote:
>>
>>>> that there really is no central TODO list. Maybe there could be a 
>>>> Documentation/NewcomersStartHere-like file that would list for
>>>> instance the TODO files in drivers/staging? It's nothing big, but
>>>> would certainly help people find their ways.
>>
>> To be honest, I think it is something big. Keeping a file up-to-date
>> which has detailed information from various subsystems is quite some
>> task. More subsystem specific TODO files might be helpful, iff the
>> maintainer manages to keep it up to date. From a newbie, I'd expect to
>> find out how to find all TODO files in a kernel tree ;)
>>
> 
> This was once discussed in Kernel Summit.
> 
> http://lwn.net/Articles/412639/
> 
> "Part of the problem, it seems, is that these lists tend not to be "sexy";
> maintainers tend to keep the more interesting tasks for themselves."
> 
> Which I myself have to admit. :)
> 

But how many of those interesting tasks are suitable for beginners? If it is
interesting for a maintainer, then I think it is very unlikely to be suitable
for someone with little experience.

We are trying to find people who are good programmers, are motivated, have
the time to spend many hours per week *of their own time* on these projects
and are willing to do that unpaid (which is typical for a beginner). Rare as
hen's teeth.

If someone shows up on a mailinglist who demonstrates those qualities, then
I'm sure any self-respecting maintainer will go out of their way to help
them. I know I would.

My opinion is that there is nothing wrong with mentoring programs as such,
but don't do it with the expectation to get fresh kernel developer blood.

I've mentored a few summer interns doing open source work and in all cases
got more out of them then I put in, but none of them became regular
contributors (which is a shame, since some were really good).

I found it a useful method to get projects done for which I had no time,
for the interns to learn about the company and open source world, and I
actually enjoy mentoring. And with luck they might try to find a job at
the company after finishing their education.

But it's not a magic bullet that will suddenly give you a new crop of
active open source contributors, let alone new subsystem maintainers.

Those that are actually interested in doing that will find their way
regardless of any mentoring programs.

In my opinion it is similar to the current craze of teaching everyone to
code. I don't believe that will result in a single competent new programmer.
Those that are really interested and motivated in the topic will find their
own way, and helping those will be much more useful.

Regards,

	Hans

  reply	other threads:[~2014-05-12  9:41 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 [this message]
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=5370970D.2030205@xs4all.nl \
    --to=hverkuil@xs4all.nl \
    --cc=jason@lakedaemon.net \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=lizefan@huawei.com \
    --cc=wsa@the-dreams.de \
    /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