From: "Robert P. J. Day" <rpjday@mindspring.com>
To: "linux-os (Dick Johnson)" <linux-os@analogic.com>
Cc: Clemens Koller <clemens.koller@anagramm.de>,
shaneed cm <just4kernel@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: request for Linux kernel related project ideas
Date: Thu, 23 Aug 2007 12:04:42 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0708231159070.5500@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.61.0708231147340.5012@chaos.analogic.com>
i really don't want to turn this into a thread that never dies, so let
me just clarify what i'm talking about:
On Thu, 23 Aug 2007, linux-os (Dick Johnson) wrote:
> On Thu, 23 Aug 2007, Robert P. J. Day wrote:
> > i'm not sure that it's appropriate for LKML folks to be giving
> > anyone suggestions for projects. the eventual choice of project
> > should be based on what *shaneed* wants, not what other people
> > tell him he should be doing.
> > in addition, sometimes part of the work involved in a school
> > project involves doing enough research to just make the *choice*.
> > what shaneed is asking is that others do that work for him.
> > IMHO, he should be told politely but firmly that selecting a topic
> > is *his* problem. that's just part of the academic process.
> >
> Of course it is appropriate. Day's response is very strange indeed.
> As part of a student's research, he should ask questions of people
> who are likely to know some answers about his query.
>
> In fact, if students for which I am an adviser didn't ask such
> questions, and simply selected a project, I would question the
> validity of the project. Projects are not selected in a vacuum. Just
> like "real world" industry, there must be a need (read market) for
> the project (read product).
let's make sure we're not talking at cross-purposes here, ok? i see
nothing wrong with someone asking for suggestions for projects in a
particular area, such as, "hey, i'm particularly interested in the
efficiency of R/W operations to flash-based filesystems, can someone
suggest a project in that area that would ultimately be useful to the
kernel community in general?" that's perfect, no problem there, i
think that's a *great* idea.
however, what the OP seemed to be asking was for suggestions for a
project with a wide-open playing field, with no restrictions whatever,
and that's what i find inappropriate. someone asking for that kind of
help should at least have put in the effort to narrow the field of
interest. as i said, that's part of the academic process -- putting
in the time to, minimally, figure out what field you're interested in.
once you do that, then you're good to go.
rday
--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA
http://crashcourse.ca
========================================================================
next prev parent reply other threads:[~2007-08-23 16:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-23 8:10 shaneed cm
2007-08-23 12:00 ` Clemens Koller
2007-08-23 12:00 ` Robert P. J. Day
2007-08-23 12:35 ` OT: " Clemens Koller
2007-08-23 15:55 ` linux-os (Dick Johnson)
2007-08-23 16:04 ` Robert P. J. Day [this message]
2007-08-29 18:12 ` Bill Davidsen
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=Pine.LNX.4.64.0708231159070.5500@localhost.localdomain \
--to=rpjday@mindspring.com \
--cc=clemens.koller@anagramm.de \
--cc=just4kernel@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.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
all inboxes | Powered by JetHome®