mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Cyrill Gorcunov <gorcunov@gmail.com>,
	tytso@mit.edu, hch@infradead.org, viro@ZenIV.linux.org.uk,
	linux-kernel@vger.kernel.org, davem@davemloft.net
Subject: Re: CFD: linux-wanking@vger.kernel.org (was [PATCH] Standard indentation of arguments)
Date: Thu, 22 May 2008 02:01:55 +0300	[thread overview]
Message-ID: <20080521230155.GC16376@cs181133002.pp.htv.fi> (raw)
In-Reply-To: <20080521123127.3b3b66af.akpm@linux-foundation.org>

On Wed, May 21, 2008 at 12:31:27PM -0700, Andrew Morton wrote:
>...
> For more substantial starter projects the best we have (as far as I
> know) is http://kernelnewbies.org/KernelProjects, but that's just a
> teeny subset.
> 
> We're not very good at this, I'm afraid.  I seem to recall that Rik has
> offered to help out here, so perhaps whenever one notices a
> hey-someone-should-do-this project, it could be forwarded to Rik and he
> can put it up there.
>...

Let's look at it from another angle:

We should not aim at being good at this.

What do we need more in the kernel:
- people testing development kernels
- people fixing bugs
- people maintaining code
- people reviewing code

What do we already have more than enough:
- people developing new bugs^Wfeatures

If someone wants to do a project that's OK.
And if some kernel developer wants to assist him that's OK.

But in my opinion stuff like "I need a project for university" requests 
are not our problem, and they tend to not bring much for us.

Offering any serious mentoring for newbies will only keep developers 
busy who could otherwise do things that would bring more value to the 
kernel.

And we've just seen that having people who do not even know the basics 
of C sending dozens of checkpatch cleanups doesn't bring us any gain.

There are many other open source projects where it might be easier to 
get started and that are really looking for people wanting to get 
involved.

> The #1 project for all kernel beginners should surely be "make sure
> that the kernel runs perfectly at all times on all machines which you
> can lay your hands on".  Usually the way to do this is to work with
> others on getting things fixed up (this can require persistence!) but
> that's fine - it's a part of kernel development.

Fully agreed, and this is the only area I see where a newbie can be a 
net win for us from the first second.

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  parent reply	other threads:[~2008-05-21 23:04 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-21  5:58 [PATCH] Standard indentation of arguments Jianjun Kong
2008-05-21  7:19 ` Jiri Slaby
2008-05-21 11:35   ` David Newall
2008-05-21  8:34 ` CFD: linux-wanking@vger.kernel.org (was [PATCH] Standard indentation of arguments) Al Viro
2008-05-21  8:50   ` Andrew Morton
2008-05-21  9:19     ` CFD: linux-wanking@vger.kernel.org David Miller
2008-05-21  9:41     ` CFD: linux-wanking@vger.kernel.org (was [PATCH] Standard indentation of arguments) Al Viro
2008-05-21 17:44       ` Andrew Morton
2008-05-21 19:45         ` Theodore Tso
2008-05-21 20:38           ` Rene Herman
2008-05-21 20:50             ` Andrew Morton
2008-05-21 21:08               ` Rene Herman
2008-05-21 21:12                 ` Andrew Morton
2008-05-21 21:32                   ` Rene Herman
2008-05-22 19:40           ` Jaya Kumar
2008-05-21 10:32     ` Christoph Hellwig
2008-05-21 12:09       ` Theodore Tso
2008-05-21 17:46         ` Andrew Morton
2008-05-21 18:57           ` Cyrill Gorcunov
2008-05-21 19:31             ` Andrew Morton
2008-05-21 20:10               ` CFD: linux-wanking@vger.kernel.org David Miller
2008-05-21 21:25                 ` Willy Tarreau
2008-05-21 21:44                   ` Stefan Richter
2008-05-21 21:56                     ` Willy Tarreau
2008-05-21 21:08               ` CFD: linux-wanking@vger.kernel.org (was [PATCH] Standard indentation of arguments) Valdis.Kletnieks
2008-05-21 23:01               ` Adrian Bunk [this message]
2008-05-21 23:17                 ` Rene Herman
2008-05-21 23:55                   ` Adrian Bunk
2008-05-22  0:10                     ` Rene Herman
2008-05-22 14:31                       ` Adrian Bunk
2008-05-21 23:35                 ` Al Viro
2008-05-22  0:38                   ` Adrian Bunk
2008-05-22  1:05                     ` Alan Cox
2008-05-22 16:08                 ` Stefan Richter
2008-05-21 19:33             ` Randy Dunlap
2008-05-21 19:45               ` Cyrill Gorcunov
2008-05-21 19:54                 ` Andrew Morton
2008-05-21 20:06                   ` Jesper Juhl
2008-05-21 20:27                     ` CFD: linux-wanking@vger.kernel.org (was [PATCH] Standard indentation of arguments), " Jonathan Corbet
2008-05-21 20:37                       ` Jesper Juhl
2008-05-21 23:46                         ` Jesper Juhl
2008-05-22  0:12                           ` Adrian Bunk
2008-05-22  0:32                             ` Jesper Juhl
2008-05-22  1:03                             ` Alan Cox
2008-05-22 14:56                             ` Pavel Machek
2008-05-22 15:29                             ` Arjan van de Ven
2008-05-22  0:14                           ` Al Viro
2008-05-22  0:34                             ` Jesper Juhl
2008-05-22  1:07                           ` Johannes Weiner
2008-05-22  4:51                           ` Cyrill Gorcunov
2008-05-22  5:34                           ` david
2008-05-31 16:23                           ` Nick Andrew
2008-05-21 19:42             ` Johannes Weiner
2008-05-21 19:47               ` Cyrill Gorcunov
2008-05-21 19:49           ` CFD: linux-wanking@vger.kernel.org David Miller
2008-05-21 22:03             ` Al Viro

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=20080521230155.GC16376@cs181133002.pp.htv.fi \
    --to=bunk@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=davem@davemloft.net \
    --cc=gorcunov@gmail.com \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tytso@mit.edu \
    --cc=viro@ZenIV.linux.org.uk \
    /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

all inboxes | Powered by JetHome®