All of lore.kernel.org
 help / color / mirror / Atom feed
From: "P.O. Gaillard" <pierre-olivier.gaillard@fr.thalesgroup.com>
To: Kyle Moffett <mrmacman_g4@mac.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Linux - open design??
Date: Tue, 14 Dec 2004 10:01:43 +0100	[thread overview]
Message-ID: <41BEABF7.6060505@fr.thalesgroup.com> (raw)
In-Reply-To: 3A1635D6-4D8D-11D9-B94B-000393ACC76E@mac.com

Kyle Moffett wrote:
> for that kind of thing to be useful.  Oh, and BTW, concerning a 
> traceability matrix,
> generally it doesn't really exist except for proprietary software.  
> Linux design is
> not "requirements-based" as commercial software is, it's 
> "I-want-this-feature-bad-
> -enough-to-code-it-and-get-it-included-based".  I suspect that companies 
> like
> IBM internally have requirements-based systems to organize their employees
> into various tasks, but publicly there is no such system, aside from 
> "It's broken
> and I fixed it with this patch:".

Hi, some of the APIs of Linux do get tested with full traceability. For 
instance, there is the Open Posix Test Suite. It tests the combination of Linux 
and libraries to check that they conform to Posix specifications.
This seems to be sponsored by Intel as far as I remember.

The OSDL also is writing specifications for Linux (e.g. Carrier Grade Linux) or 
ways to integrate components from the Linux world (e.g. kernel.org sources + 
high res timers from Montavista) to achieve some kind of performance.

I would therefore say that there are in fact roadmaps and specifications for 
Linux (note that this is my opinion as a user). And more seem to be emerging 
even though most of the development is probably driven by the process that Kyle 
just described.

	these were my 2 cents as a user,

	P.O. Gaillard




  reply	other threads:[~2004-12-14  9:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-14  3:48 Tilt Wheel Mouse Drivers Missing mike cox
2004-12-14  4:01 ` Linux - open design?? ram mohan
2004-12-14  4:54   ` Zwane Mwaikambo
2004-12-14  5:01   ` Kyle Moffett
2004-12-14  9:01     ` P.O. Gaillard [this message]
2004-12-14  8:56   ` Bernd Petrovitsch
2004-12-14 11:26   ` Helge Hafting
2004-12-14 12:13   ` Olaf Dietsche
2004-12-16  9:22     ` Got Info - Linux - open design ram mohan

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=41BEABF7.6060505@fr.thalesgroup.com \
    --to=pierre-olivier.gaillard@fr.thalesgroup.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mrmacman_g4@mac.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 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.