Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Nancy Bigham <bigham@cthulhu.engr.sgi.com>
To: Florian Lohoff <flo@rfc822.org>
Cc: Ralf Baechle <ralf@oss.sgi.com>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Ulf Carlsson <ulfc@calypso.engr.sgi.com>,
	linux@cthulhu.engr.sgi.com, linux-mips@fnet.fr,
	linux-mips@vger.rutgers.edu
Subject: Re: Indy Documentation
Date: Tue, 16 May 2000 10:17:16 -0700	[thread overview]
Message-ID: <3921829C.9AB0FB4E@engr.sgi.com> (raw)
In-Reply-To: 20000516120830.F2191@paradigm.rfc822.org

Florian Lohoff wrote:
> 
[...]
> 
> What is the license or publishing restrictions of those documents ?
> 

The documentation is copyrighted by SGI. Attached are two sections from
internal web pages at SGi explaining copyright infringement and fair use
of copyright material.

For more information on U.S. laws regarding copyrights, see
http://www.loc.gov/copyright/circs/circ1.html

===============
WHAT IS COPYRIGHT INFRINGEMENT?

Copyright infringement occurs where someone copies all or a significant
portion of a copyrighted work. 

To prove infringement, a copyright holder must demonstrate that the
alleged infringer had access to the original work (typically a
reasonable opportunity to see or hear it), and that the infringer's
resulting work
was substantially similar thereto. The copyright holder need not prove
such access where the similarity between the works is so striking as to
preclude the possibility that one was created without reference to the
other. 

Although this is still a developing area of the law, courts have held
computer software copyrights infringed when object code was
disassembled, translated into another language, modified, or emulated by
utilizing
the same "structure, sequence, and organization" as the original. Under
this rule, it is entirely possible that one software program could
infringe the copyright of another without having a single line of code
identical to the copyrighted work. On a more basic level, literal
copying of a work (or even a small but significant
portion) will also infringe the original. 

Silicon Graphics is committed to protecting its works (especially
software programs) through copyright registration, and to avoiding
copyright infringement by company employees. Please bring any suspected
copyright infringement to Legal Services' attention as quickly as
possible. 

For specific information regarding Silicon Graphics' position on
copyright infringement, see Legal Services' document called
"Intellectual Property Policies and Guidelines" 

WHAT IS "FAIR USE"OF A COPYRIGHTED WORK? 

Not all copying of copyrighted works is illegal. The "fair use" doctrine
allows unauthorized copying of all or portions of copyrighted works in
certain instances, but typically on a "not-for-profit" basis. Since most
Silicon Graphics' uses are on a "for-profit" basis, as they are in
connection with our business, we are unlikely to meet these
requirements. 

Therefore, if you wish to use tables, figures, pictures, sound,
extensive quotations, or other aspects of a copyrighted work, we must
first secure the written permission of the work's author. When in doubt,
please
assume that you need such authorization, and contact Legal Services for
assistance. 
=======

The short answer is that Ralf cannot make copies and distribute the
documents he has without permission from SGI. Seeing how I gave him the
docs, I can certainly talk to our legal department to see if it's
possible to allow him to make copies. 

We would have to take the contents of the Exabyte types under the same
consideration - i.e. review for legal rights to distribute contents.
It's quite possible that there are contents on backup tapes that SGI has
no right to redistribute.

Nancy
-- 
Nancy Bigham
SGI          MS 8U-500   650 933-1608   bigham@engr.sgi.com

  parent reply	other threads:[~2000-05-16 17:29 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-13 13:21 Indy Documentation Ulf Carlsson
2000-05-13 13:42 ` Guido Guenther
2000-05-14  6:08   ` Florian Lohoff
2000-05-13 16:32 ` Florian Lohoff
2000-05-14 18:58   ` Geert Uytterhoeven
2000-05-15 21:23     ` Ralf Baechle
2000-05-16 10:08       ` Florian Lohoff
2000-05-16 16:40         ` Ralf Baechle
     [not found]           ` <Pine.GSO.3.96.1000517124358.24276C-100000@delta.ds2.pg.gda.pl>
2000-05-17 16:06             ` Ralf Baechle
2000-05-16 17:17         ` Nancy Bigham [this message]
2000-05-17 11:39           ` Florian Lohoff
2000-05-14 22:04   ` Jan-Benedict Glaw
2000-05-13 23:46 ` Alan Cox
2000-05-13 23:46   ` Alan Cox
2000-05-15 18:22 ` Ulf Carlsson
2000-05-15 19:19   ` Guido Guenther
  -- strict thread matches above, loose matches on Subject: below --
2000-05-16 11:02 Kevin D. Kissell
2000-05-16 11:02 ` Kevin D. Kissell

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=3921829C.9AB0FB4E@engr.sgi.com \
    --to=bigham@cthulhu.engr.sgi.com \
    --cc=flo@rfc822.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-mips@fnet.fr \
    --cc=linux-mips@vger.rutgers.edu \
    --cc=linux@cthulhu.engr.sgi.com \
    --cc=ralf@oss.sgi.com \
    --cc=ulfc@calypso.engr.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox