From: Tuomo Valkonen <tuomov@iki.fi>
To: Adrian Bunk <bunk@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [poll] Is the megafreeze development model broken?
Date: Mon, 12 Nov 2007 19:16:26 +0200 [thread overview]
Message-ID: <20071112171626.GA8838@jolt.modeemi.cs.tut.fi> (raw)
In-Reply-To: <20071112165616.GM9771@stusta.de>
On 2007-11-12 17:56 +0100, Adrian Bunk wrote:
> Yes, by asking immediately
> Is this issue still present with $latest_upstream_version?
That's still a user complaining about problems fixed ages ago,
and a couple more who never even bothered complaining, just
decided that the software is crap because it doesn't work.
> Let's check your statement against reality:
>
> They are called linux-*
I have various kernel-image packages.
> Open source development does not work by whining and trying to spread
> your opinion through fake "polls" - either you implement what you want
> yourself or it won't happen.
I did not post this "poll".
I'll just complain how shoddy FOSS has become, and fix to Windows.
There's little point in using FOSS these days, when nothing is done
better, and many things worse, than in closed source. I simply don't
have the time to fix all the woeful FOSS crap by myself.
> But an important observation is that when you start something other
> people consider worthwhile there will be other people who participate in
> what you do, or who even continue it when you decide to switch to other
> projects instead.
Typically they write a clone from scratch, because the right
herd-approved language or the right license wasn't originally used,
or so. They expect the author to maintain their shoddy patches that
would be better implemented as separate modules -- taking example
from the monolithic unbuildable kernel [1] -- and when you ask for
quality, they disappear or threaten with a fork. It's very difficult
to get quality contributions. And then there are projects that would
really demand a lot of input before even starting the actual coding
work, but the FOSS herd works on the worse-is-better fallacy that
results in crappy software that it has become too late to fix the
fundamental flaws in, when you notice the it. Essential core software
needs a lot of input before starting the work, instead of a small
(one-man) elite creating it and then the herd uncritically adopting
it based on the "oooh! shiny!" factor, after which it will be very
difficult to fix.
[1]: http://iki.fi/tuomov/b/archives/2007/04/01/T19_09_22/
--
Tuomo
next prev parent reply other threads:[~2007-11-12 17:16 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-07 22:56 ciol
2007-11-07 23:06 ` Rik van Riel
2007-11-07 23:11 ` ciol
2007-11-08 1:36 ` Adrian Bunk
2007-11-08 20:45 ` ciol
2007-11-08 6:18 ` Stephen Hemminger
2007-11-08 13:38 ` David Newall
2007-11-08 14:26 ` Chris Snook
2007-11-08 20:41 ` ciol
2007-11-09 0:15 ` Chris Snook
2007-11-12 11:09 ` Eric W. Biederman
2007-11-12 13:51 ` Tuomo Valkonen
2007-11-12 15:20 ` Adrian Bunk
2007-11-12 16:02 ` Tuomo Valkonen
2007-11-12 16:56 ` Adrian Bunk
2007-11-12 17:16 ` Tuomo Valkonen [this message]
2007-11-12 17:34 ` Adrian Bunk
2007-11-12 17:42 ` Tuomo Valkonen
2007-11-13 10:11 ` David Newall
2007-11-12 17:37 ` Rogelio M. Serrano Jr.
2007-11-12 17:53 ` Tuomo Valkonen
2007-11-13 12:28 ` Radoslaw Szkodzinski
2007-11-13 13:09 ` Tuomo Valkonen
2007-11-12 16:13 ` Rogelio M. Serrano Jr.
2007-11-12 17:14 ` Adrian Bunk
2007-11-12 17:18 ` Tuomo Valkonen
2007-11-12 23:39 ` Matthias Schniedermeyer
2007-11-13 0:12 ` Tuomo Valkonen
2007-11-12 17:30 ` david
2007-11-12 18:25 ` Rogelio M. Serrano Jr.
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=20071112171626.GA8838@jolt.modeemi.cs.tut.fi \
--to=tuomov@iki.fi \
--cc=bunk@kernel.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®