LibrePlanet discussion list archive (unofficial mirror)
 help / color / mirror / Atom feed
From: Caleb Herbert <csh@bluehome.net>
To: Chad Larson <BPYZs1fx@mailtoo.hungrycats.org>
Cc: Michael Pagan <michael.pagan@member.fsf.org>,
	libreplanet-discuss@libreplanet.org
Subject: Re: 7 Reasons to Avoid Open Source?
Date: Mon, 04 Dec 2017 09:06:10 -0600	[thread overview]
Message-ID: <1512399970.3357.12.camel@leela> (raw)
In-Reply-To: <20171204021255.n5atlesyayeeeuyw@hungrycats.org>


[-- Attachment #1.1: Type: text/plain, Size: 1130 bytes --]

On Sun, 2017-12-03 at 21:12 -0500, Chad Larson wrote:
> Merely using a VCS is not sufficient.  Traceability requires identifying
> individual persons responsible for determining requirements for the
> code, establishing their competence to design and implement the code, and
> demonstrating that the code implements the requirements correctly for each
> product that uses the code.  Industrial regulations require traceability
> to determine which individual personally made which implementation
> decisions and which individual tested and verified the results.

Sounds like they want better documentation.  Ask Red Hat.

> Traceability is very expensive, in terms of both development cost and
> liberty for the developers.  If you think of it as a map to know who to
> sue when things go badly wrong, you're not entirely wrong.

Sounds like they want the benefits of a warranty.  Ask Red Hat.

Reminder: Department of Defense will use software without a warranty IF
and ONLY IF it is free.  Is some company more important than the DoD?

-- 
Caleb Herbert
OpenPGP public key: http://bluehome.net/csh/pubkey

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

[-- Attachment #2: Type: text/plain, Size: 183 bytes --]

_______________________________________________
libreplanet-discuss mailing list
libreplanet-discuss@libreplanet.org
https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss

  parent reply	other threads:[~2017-12-04 15:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-03  4:45 7 Reasons to Avoid Open Source? Mary-Anne Wolf
2017-12-03  8:05 ` Andrés Muñiz Piniella
2017-12-03 10:44 ` Thomas Harding
2017-12-03 12:32   ` N.Thomas
2017-12-03 15:29   ` C.W. Epema
2017-12-03 19:22 ` Michael Pagan
2017-12-04  2:12   ` Chad Larson
2017-12-04 14:51     ` Thomas Harding
2017-12-04 15:06     ` Caleb Herbert [this message]
2017-12-04 19:02       ` Chad Larson
2017-12-04 23:59         ` Thomas Harding
2017-12-04 16:20   ` Adonay Felipe Nogueira

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

  List information: https://lists.gnu.org/mailman/listinfo/libreplanet-discuss

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1512399970.3357.12.camel@leela \
    --to=csh@bluehome.net \
    --cc=BPYZs1fx@mailtoo.hungrycats.org \
    --cc=libreplanet-discuss@libreplanet.org \
    --cc=michael.pagan@member.fsf.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).