From: Rob Landley <rob@landley.net>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Francois Romieu <romieu@fr.zoreil.com>,
"Theodore Ts'o" <tytso@thunk.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
ksummit-2013-discuss@lists.linuxfoundation.org
Subject: Re: Kernel summit 2013: Call for Hobbyists
Date: Tue, 20 Aug 2013 03:24:59 -0500 [thread overview]
Message-ID: <1376987099.2737.63@driftwood> (raw)
In-Reply-To: <CAMuHMdXeQXUZ0pt1tb3Ch8j6mmqz9AiGirmjcp=a2ZDXX6VqtA@mail.gmail.com> (from geert@linux-m68k.org on Sun Aug 18 03:26:03 2013)
On 08/18/2013 03:26:03 AM, Geert Uytterhoeven wrote:
> On Fri, Aug 16, 2013 at 11:02 PM, Francois Romieu
> <romieu@fr.zoreil.com> wrote:
> > As a hobbyist, I have less time than most pro and must cope with
> > whatever brain juice remains after the paid work. It doesn't make me
>
> Indeed. And the dosing of brain juice is not always aligned with the
> steady
> pace of Linux kernel development, causing hobyists to miss merge
> windows,
> resubmissions, and general follow-up.
And those of us who don't have "follow linux-kernel" as part of a day
job's responsibilities tend to be several days behind, so it's hard to
participate in coversations.
I seldom get paid to work on a current kernel. I _have_ been paid to
beat some horrible vendor board support package with a rock until it
sticks to the hardware, but this is invariably multiple years behind
current and has a lineage like "vanilla kernel, forked by android for
ice cream sandwich, then forked by TI's Netra Board Support Package,
then forked by Polycom because implementing Skype in hardware seemed
like a good idea at the time". (My last contract involved Centos 6.3, a
fresh release with a 4 year old kernel. Lots of backporting stuff from
~3.4 to 2.6.32 or whatever it was using. Because that's when what I
needed was feature complete and there were fewer API changes than
current, that's why.)
I do sometimes get to chip bits off and port them to upstream, after
the fact, if there's time, and if my boss can shield the effort from
every legal department's ironclad desire to do the absolute minimum
required and no more. Usually there's just a nominal source tarball
snapshot (no source control history, that's confidential) posted to
some obscure website when the hardware finally ships (and the dev
team's broken up), and if you _do_ diff this obsolete thing against
vanilla the diff is multiple megabytes and most of it wasn't our
changes.
Intermittently getting paid to do that means I _don't_ qualify as a
hobbyist, apparently. Even though the vast majority of actual open
soruce programming I get done is in the downtime _between_ contracts.
(I'm listed in MAINTAINERS for trying to prevent documentation from
falling through the cracks when nobody else merges it through their
tree. I got paid to work on Linux documentation once, for a very nice 6
months back in 2007, but I didn't get listed in MAINTAINERS until ~3
years after that stopped.)
Rob
prev parent reply other threads:[~2013-08-20 10:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-15 2:26 Kernel summit 2013: Call for Hobbyists Theodore Ts'o
2013-08-15 10:38 ` Borislav Petkov
2013-08-16 6:14 ` Rob Landley
2013-08-16 21:02 ` Francois Romieu
2013-08-18 8:26 ` Geert Uytterhoeven
2013-08-20 8:24 ` Rob Landley [this message]
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=1376987099.2737.63@driftwood \
--to=rob@landley.net \
--cc=geert@linux-m68k.org \
--cc=ksummit-2013-discuss@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=romieu@fr.zoreil.com \
--cc=tytso@thunk.org \
/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