9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Tom Glinos, x4302 tg@utstat.utstat.toronto.edu
Subject: what, me worry? Oh yes!
Date: Sat,  8 Apr 1995 10:15:03 -0400	[thread overview]
Message-ID: <19950408141503.7gOQnhNBjOxjhW_Cn6XTk9Umru3U99qqYnN6DZzbjXQ@z> (raw)

License arrangements are made to protect and enhance the business
position of the company granting the license and to ACCOMPLISH
certain goals and objectives.

USG made a mess and started off the "UNIX wars" when it introduced
the SVR4 license a decade ago. The sad thing was, management was warned
(by a small but vocal group) that the license was a stinker.
But, management was convinced by the marketing droids who came up
with this evil document that all would be well. This was even after
private communications from major licensees to "smarten up" were
passed along.

What I learned was the following:

(1) Lawyers are wonderful people who protect your position if you
can clearly state it to them. They are not to be blamed in this case.

(2) Management must understand what it's doing with its license.
If the "intent" can't be explained in a few simple easy to
read sentences then you have a problem.

(3) Management must know what its goals and objectives are
in introducing the product and appreciate the ramifications
of the terms and conditions in the  license.
(A very hard thing to do.)

It's easy come up with a bad license, it hard to come up with a good one.

-- 
=================
Users choose DOS and MAC's over UNIX	| Tom Glinos @ U of Toronto Statistics
You are not expected to understand this.| tg@utstat.toronto.edu






             reply	other threads:[~1995-04-08 14:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1995-04-08 14:15 Tom [this message]
1995-04-09  3:29 Berny

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=19950408141503.7gOQnhNBjOxjhW_Cn6XTk9Umru3U99qqYnN6DZzbjXQ@z \
    --to=9fans@9fans.net \
    /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).