The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: tfb@tfeb.org (Tim Bradshaw)
Subject: [TUHS] Ultrix...
Date: Fri, 6 Sep 2002 02:27:39 +0100	[thread overview]
Message-ID: <15736.1163.252006.420197@tfeb.org> (raw)
In-Reply-To: <slrnanfrp5.1ei.mirian@trantor.cosmic.com>

* Mirian Crzig Lennox wrote:

> In fact, the concept of "intellectual property" is a fairly recent
> perversion, and the consequence has been a steady depletion of the
> public domain.  When a piece of software (and Ultrix is an excellent
> example) is tied up in copyright long after it is of any value to
> anyone beyond pure academic interest, nothing is added to anyone's
> wealth, and society as a whole loses.

I think this is kind of unfair in many cases.  Firstly copyright has
lasted for a fairly long time for, well, a fairly long time. It's not
some sinister new development which is keeping ultrix in copyright.
Secondly, it's all very well to say that old and valueless bits of
software should be freed, but if you are the organisation which has
the copyright on these things it's really less trivial than you might
think to just give them away.  For a start, there's (almost by
definition) no money in it, so any kind of work needed is costing
money.  Secondly there may be just plain trade-secret stuff in there,
what do you do about that?  There may be all sorts of other awful
things that you don't want to let the world see.

I'm really in favour of giving things away when they're no longer
interesting but I don't think there's just some magic trick you can
do.  Here's a related example: we have a fairly large chunk of
software which I'm wondering if we could open source.  We have the
copyright (I wrote it).  There aren't any trade secrets in it.  But
what there are is some fairly pointed comments about various people
and companies.  I don't think they are defamatory, but I'd really want
to excise them before I gave it out.  So now I have to check through
tens of thousands of lines of code, for no money, just so I can give
it away.

Hmm, this is off-topic, sorry.  I just wanted to say that it doesn't
have to be malice, sometimes it's just hard.

--tim




  reply	other threads:[~2002-09-06  1:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-05  3:15 Ian King
2002-09-05 23:56 ` Mirian Crzig Lennox
2002-09-06  1:27   ` Tim Bradshaw [this message]
2002-09-06 13:59     ` Mirian Crzig Lennox
  -- strict thread matches above, loose matches on Subject: below --
2002-09-06 16:58 Ian King
2002-09-06  1:27 Ian King
2002-08-28 17:48 Michael Sokolov
2002-08-28 16:07 Johnny Billquist

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=15736.1163.252006.420197@tfeb.org \
    --to=tfb@tfeb.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 NNTP newsgroup(s).