From: linas@austin.ibm.com (Linas Vepstas)
To: Wolfgang Denk <wd@denx.de>
Cc: linuxppc-dev@ozlabs.org, linuxppc-embedded@ozlabs.org,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [JOB] Senior Embedded Linux Video Engineer
Date: Fri, 14 Jul 2006 11:38:14 -0500 [thread overview]
Message-ID: <20060714163814.GD11943@austin.ibm.com> (raw)
In-Reply-To: <20060714162100.E027F352681@atlas.denx.de>
On Fri, Jul 14, 2006 at 06:21:00PM +0200, Wolfgang Denk wrote:
>
> > Should I post our embedded PPC kernel related work openings here?
>
> NO!!!
>
> This is a technical discussion group. Job offerings, commercial ads
> and all this stuff is off topic here. Please re-read the list info at
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded resp. -dev
>
> It says: "...discussions/patches should pertain to software
> development for the kernel core ppc32 embedded processor support and
> any driver/chip/board support for ppc32 based embedded systems."
>
> "Software development". This does not allow for job offers, ads or
> other crap.
I respectfully disagree. There may well be people who would rather
work on PowerPC Linux kernels more than any other thing in the world,
and it is entirely appropriate for job openings for PowerPC Linux kernel
programmers to be posted here.
Much as I would like to be, and not for lack of trying, indpendently
wealthy off some dot-com IPO, so that I may code on whatever I wished,
I have, in fact, failed at this, and must stick to actual employment
to feed, cloth and educate my family. I am not alone.
There is a long precedent for this in academic societies, and you will
find job postings in Nature, Science, Physics Today and American
Mathematical Monthly. Frankly, there simply are not so many job
opporunities that we, much like engineers and scientists in general,
can afford to thumb our noses at them.
If you in fact are especially fortunate, then perhaps you could
mentor someone younger: someone who is hot, smart, and fresh out of
college, a good talent, who has contributed good patches, but is now
faced with the need to find rent and beer money. What advice can you
give them, "tough luck Squidward, go work at the Krusty Krab?"
--linas
next prev parent reply other threads:[~2006-07-14 16:38 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-13 20:33 [JOB] Senior Embedded Linux Video Engineer Davenport, Richard
2006-07-14 8:07 ` Christoph Hellwig
2006-07-14 8:43 ` Stephen Rothwell
2006-07-14 11:22 ` Wolfgang Denk
2006-07-14 14:35 ` bbosch
2006-07-14 14:58 ` John W. Linville
2006-07-14 15:20 ` jschopp
2006-07-14 16:21 ` Wolfgang Denk
2006-07-14 16:38 ` Linas Vepstas [this message]
2006-07-14 18:41 ` Frank
2006-07-14 19:14 ` Segher Boessenkool
2006-07-14 17:29 ` Tim Bird
2006-07-14 18:03 ` Olof Johansson
2006-07-14 18:40 ` Geoff Thorpe
2006-07-16 15:12 ` Wolfgang Denk
2006-07-17 1:12 ` David H. Lynch Jr.
2006-07-17 3:28 ` Geoff Thorpe
2006-07-14 19:13 ` Tim Bird
2006-07-14 19:17 ` Olof Johansson
2006-07-15 3:23 ` David H. Lynch Jr.
-- strict thread matches above, loose matches on Subject: below --
2006-07-13 20:51 Davenport, Richard
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=20060714163814.GD11943@austin.ibm.com \
--to=linas@austin.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc-embedded@ozlabs.org \
--cc=sfr@canb.auug.org.au \
--cc=wd@denx.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;
as well as URLs for NNTP newsgroup(s).