From: Li Zefan <lizefan@huawei.com>
To: 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 17:08:04 +0800 [thread overview]
Message-ID: <53708F74.3070200@huawei.com> (raw)
In-Reply-To: <20140512083825.GB2665@katana>
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. :)
next prev parent reply other threads:[~2014-05-12 9: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 [this message]
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=53708F74.3070200@huawei.com \
--to=lizefan@huawei.com \
--cc=jason@lakedaemon.net \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--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 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.