forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject svn commit: rev 20900 - forrest/trunk/legal
Date Tue, 08 Jun 2004 07:38:10 GMT
Author: crossley
Date: Tue Jun  8 00:38:10 2004
New Revision: 20900

Modified:
   forrest/trunk/legal/oreilly.codepolicy.txt   (contents, props changed)
   forrest/trunk/legal/oreilly.permission.txt   (contents, props changed)
Log:
Fix dos2unix line-endings and 'svn propset svn:eol-style'


Modified: forrest/trunk/legal/oreilly.codepolicy.txt
==============================================================================
--- forrest/trunk/legal/oreilly.codepolicy.txt	(original)
+++ forrest/trunk/legal/oreilly.codepolicy.txt	Tue Jun  8 00:38:10 2004
@@ -1,103 +1,103 @@
-http://www.oreilly.com/pub/a/oreilly/ask_tim/2001/codepolicy.html
-
-*O'Reilly Policy on Re-Use of Code Examples from Books*
-
-Bruce Epstein, author of /Director in a Nutshell/ (out of print) and
-Lingo in a Nutshell <http://www.oreilly.com/catalog/lingonut/>, who is
-now working as a part-time editor for O'Reilly (he is editor of Colin
-Moock's recently published ActionScript: The Definitive Guide
-<http://www.oreilly.com/catalog/actscript/>) sent in the following
-question:
-
-"What is our policy with regard to programmers incorporating code
-examples from books into their work? I get asked this all the time."
-
-The short answer is this:
-
-You can use and redistribute example code from our books for any
-non-commercial purpose (and most commercial purposes) as long as you
-acknowledge their source and authorship. The source of the code should
-be noted in any documentation as well as in the program code itself (as
-a comment). The attribution should include author, title, publisher, and
-ISBN.
-
-As is often the case, there's a longer answer as well. Bruce made it
-really easy for me to put this response together, since he forwarded an
-unofficial reply on this subject that he'd sent to the FlashCoders
-mailing list. What appears below is based on his message. (Hey, anyone
-else who wants to send the answer as well as the question to Ask Tim can
-make my job a lot easier :-) Thanks, Bruce.)
-
-As per the copyright notice in our books, O'Reilly reserves all rights
-to the material in the book, including the code examples. This literally
-means that you can use the example code all you like, but you can't
-publish or redistribute it without our permission. In reality, we are
-comfortable with any reasonable "fair use" of the code, and you can
-assume permission is granted without contacting us. The threshold of
-what is reasonable (fair use) depends on a number of factors. First, if
-the book is published under an open source or open publication license,
-you can use the code examples without any obligation to us. Otherwise,
-use the following sanity tests:
-
-   1.
-
-      If the code is incorporated into a software product, Web site, or
-      Web service, is the product, site, or service a commercial
-      venture? We don't object to commercial ventures, but if someone is
-      looking to profit from our work (or that of our authors'), and the
-      use is substantial, we may want to consider a license fee. (Send
-      licensing queries to permissions@oreilly.com
-      <mailto:permissions@oreilly.com>.)
-
-   2.
-
-      Is the O'Reilly material incidental to the entire product? Are you
-      using only a small excerpt? For example, you can't publish a
-      CD-ROM of code examples from O'Reilly books without our explicit
-      permission. But we aren't going to worry if you use a routine
-      taken from our books as part of a huge software project, in which
-      the borrowed code is incidental.
-
-   3.
-
-      Does the work compete with O'Reilly? For example, if you are a
-      book publisher, you can't use anything from our books without our
-      permission.
-
-   4.
-
-      Is proper credit given? Such credit would include a statement
-      specifying the source of the material, such as "Derived from
-      Example 10-2, /ActionScript: The Definitive Guide/ by Colin Moock.
-      Copyright 2001 O'Reilly & Associates." Note that giving credit
-      does not insulate you from prosecution if you improperly use
-      copyrighted material!
-
-   5.
-
-      Does your use fall within fair use provisions of copyright law?
-      (Academic research, commentary, etc.) For example, you don't need
-      O'Reilly's explicit permission to post a snippet of code on a
-      mailing list if you are pointing out a bug, asking a question, or
-      answering one. We especially like it when people answer questions
-      by pointing to our books, quoting from them, and citing their
-      examples, as long as they acknowledge the source!
-
-      Acknowledging the source is particularly important. Bruce didn't
-      mention this in his posting to FlashCoders, but I know that he
-      personally was bit by this one. Someone was routinely answering
-      Lingo questions on a mailing list by supplying examples from
-      Bruce's book, without acknowledging the source (and leading people
-      to believe that the poster had written them).
-
-We put the code from our books online because we want it to be used.
-(Who wants to type it in?) That's why we make it available in lots of
-ways: for download from the Web (all examples are linked from the book's
-catalog page on /oreilly.com/), in our CD Bookshelf products, and in our
-new Safari online service.
-
-If you are interested in licensing O'Reilly book content as a third
-party, send your request to corporate@oreilly.com
-<mailto:corporate@oreilly.com>.
-
---Tim
+http://www.oreilly.com/pub/a/oreilly/ask_tim/2001/codepolicy.html
+
+*O'Reilly Policy on Re-Use of Code Examples from Books*
+
+Bruce Epstein, author of /Director in a Nutshell/ (out of print) and
+Lingo in a Nutshell <http://www.oreilly.com/catalog/lingonut/>, who is
+now working as a part-time editor for O'Reilly (he is editor of Colin
+Moock's recently published ActionScript: The Definitive Guide
+<http://www.oreilly.com/catalog/actscript/>) sent in the following
+question:
+
+"What is our policy with regard to programmers incorporating code
+examples from books into their work? I get asked this all the time."
+
+The short answer is this:
+
+You can use and redistribute example code from our books for any
+non-commercial purpose (and most commercial purposes) as long as you
+acknowledge their source and authorship. The source of the code should
+be noted in any documentation as well as in the program code itself (as
+a comment). The attribution should include author, title, publisher, and
+ISBN.
+
+As is often the case, there's a longer answer as well. Bruce made it
+really easy for me to put this response together, since he forwarded an
+unofficial reply on this subject that he'd sent to the FlashCoders
+mailing list. What appears below is based on his message. (Hey, anyone
+else who wants to send the answer as well as the question to Ask Tim can
+make my job a lot easier :-) Thanks, Bruce.)
+
+As per the copyright notice in our books, O'Reilly reserves all rights
+to the material in the book, including the code examples. This literally
+means that you can use the example code all you like, but you can't
+publish or redistribute it without our permission. In reality, we are
+comfortable with any reasonable "fair use" of the code, and you can
+assume permission is granted without contacting us. The threshold of
+what is reasonable (fair use) depends on a number of factors. First, if
+the book is published under an open source or open publication license,
+you can use the code examples without any obligation to us. Otherwise,
+use the following sanity tests:
+
+   1.
+
+      If the code is incorporated into a software product, Web site, or
+      Web service, is the product, site, or service a commercial
+      venture? We don't object to commercial ventures, but if someone is
+      looking to profit from our work (or that of our authors'), and the
+      use is substantial, we may want to consider a license fee. (Send
+      licensing queries to permissions@oreilly.com
+      <mailto:permissions@oreilly.com>.)
+
+   2.
+
+      Is the O'Reilly material incidental to the entire product? Are you
+      using only a small excerpt? For example, you can't publish a
+      CD-ROM of code examples from O'Reilly books without our explicit
+      permission. But we aren't going to worry if you use a routine
+      taken from our books as part of a huge software project, in which
+      the borrowed code is incidental.
+
+   3.
+
+      Does the work compete with O'Reilly? For example, if you are a
+      book publisher, you can't use anything from our books without our
+      permission.
+
+   4.
+
+      Is proper credit given? Such credit would include a statement
+      specifying the source of the material, such as "Derived from
+      Example 10-2, /ActionScript: The Definitive Guide/ by Colin Moock.
+      Copyright 2001 O'Reilly & Associates." Note that giving credit
+      does not insulate you from prosecution if you improperly use
+      copyrighted material!
+
+   5.
+
+      Does your use fall within fair use provisions of copyright law?
+      (Academic research, commentary, etc.) For example, you don't need
+      O'Reilly's explicit permission to post a snippet of code on a
+      mailing list if you are pointing out a bug, asking a question, or
+      answering one. We especially like it when people answer questions
+      by pointing to our books, quoting from them, and citing their
+      examples, as long as they acknowledge the source!
+
+      Acknowledging the source is particularly important. Bruce didn't
+      mention this in his posting to FlashCoders, but I know that he
+      personally was bit by this one. Someone was routinely answering
+      Lingo questions on a mailing list by supplying examples from
+      Bruce's book, without acknowledging the source (and leading people
+      to believe that the poster had written them).
+
+We put the code from our books online because we want it to be used.
+(Who wants to type it in?) That's why we make it available in lots of
+ways: for download from the Web (all examples are linked from the book's
+catalog page on /oreilly.com/), in our CD Bookshelf products, and in our
+new Safari online service.
+
+If you are interested in licensing O'Reilly book content as a third
+party, send your request to corporate@oreilly.com
+<mailto:corporate@oreilly.com>.
+
+--Tim

Modified: forrest/trunk/legal/oreilly.permission.txt
==============================================================================
--- forrest/trunk/legal/oreilly.permission.txt	(original)
+++ forrest/trunk/legal/oreilly.permission.txt	Tue Jun  8 00:38:10 2004
@@ -1,81 +1,81 @@
-From cindyw@oreilly.com Thu Jun  3 09:05:16 2004
-Return-Path: <cindyw@oreilly.com>
-Delivered-To: user0009-dave@brondsema.net
-Received: (qmail 14470 invoked from network); 2 Jun 2004 21:12:58 -0000
-Received: from minotaur.apache.org (209.237.227.194)
-  by 0 with SMTP; 2 Jun 2004 21:12:58 -0000
-Received: (qmail 87257 invoked by uid 1775); 2 Jun 2004 21:13:44 -0000
-Delivered-To: brondsem@locus.apache.org
-Received: (qmail 87184 invoked from network); 2 Jun 2004 21:13:43 -0000
-Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
-  by minotaur.apache.org with SMTP; 2 Jun 2004 21:13:43 -0000
-Received: (qmail 35227 invoked by uid 500); 2 Jun 2004 21:14:00 -0000
-Delivered-To: apmail-brondsem@apache.org
-Received: (qmail 35134 invoked by uid 99); 2 Jun 2004 21:14:00 -0000
-Received: from [209.204.146.35] (HELO smtp1.oreilly.com) (209.204.146.35)
-  by apache.org (qpsmtpd/0.27.1) with ESMTP; Wed, 02 Jun 2004 14:14:00 -0700
-Received: from cindyw.oreilly.com (dhcp-172-24-30-220.west.ora.com
-    [172.24.30.220])
-	by smtp1.oreilly.com (Postfix) with ESMTP
-	id 93D2E14A1C; Wed,  2 Jun 2004 14:13:39 -0700 (PDT)
-Message-Id: <4.3.2.7.2.20040602140354.00c45838@pop3.west.ora.com>
-X-Sender: cindyw@pop3.west.ora.com
-X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
-Date: Wed, 02 Jun 2004 14:13:01 -0700
-To: Dave Brondsema <brondsem@apache.org>, permissions@oreilly.com
-From: Cindy Wetterlund <cindyw@oreilly.com>
-Subject: Re: using code in an Apache project
-Cc: simonstl@oreilly.com
-In-Reply-To: <1085402426.40b1ed3a86ef4@secure.solidusdesign.com>
-Mime-Version: 1.0
-Content-Type: text/plain; charset="us-ascii"; format=flowed
-X-Virus-Checked: Checked
-X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N
-X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on 
-	ferrari.solidusdesign.com
-X-Spam-Level: 
-X-Spam-Status: No, hits=0.0 required=4.0 tests=none autolearn=no version=2.63
-
-Hi Dave,
-
-Thanks for your mail and interest.
-
-Yes, you have O'Reilly's permission (and the author's who
-was happy to hear of your interest) to re-use some of the code
-from XSLT Cookbook for the Forrest project.
-
-It would be great if you would cite the usage by acknowledging
-the original title/author with a standard credit line.
-
-Thanks Dave.
-
-Cindy
-
-At 08:40 AM 5/24/2004 -0400, Dave Brondsema wrote:
-
->The Apache Forrest project (http://xml.apache.org/forrest/) would like to use
->some of the code included in the XSLT Cookbook.  Forrest is licensed under the
->Apache License 2.0 (http://www.apache.org/licenses/)
->
->According to 
->http://www.oreilly.com/pub/a/oreilly/ask_tim/2001/codepolicy.html,
->I think this would be ok.  However, we would feel more comfortable if explicit
->permission was given for us to use and distribute your code as part of our 
->project.
->
->Personally, I would suggest that O'Reilly code be licensed under a known Open
->Source license, such as the Apache License.  This would make it clear to all
->what is allowed and what is not.
->
->Thanks!
->
->--
->Dave Brondsema : brondsem@apache.org
->http://www.brondsema.net  : personal
->http://www.splike.com  : programming
-
-Cindy Wetterlund
-International Rights and
-Licensing Manager
-cindyw@oreilly.com
-
+From cindyw@oreilly.com Thu Jun  3 09:05:16 2004
+Return-Path: <cindyw@oreilly.com>
+Delivered-To: user0009-dave@brondsema.net
+Received: (qmail 14470 invoked from network); 2 Jun 2004 21:12:58 -0000
+Received: from minotaur.apache.org (209.237.227.194)
+  by 0 with SMTP; 2 Jun 2004 21:12:58 -0000
+Received: (qmail 87257 invoked by uid 1775); 2 Jun 2004 21:13:44 -0000
+Delivered-To: brondsem@locus.apache.org
+Received: (qmail 87184 invoked from network); 2 Jun 2004 21:13:43 -0000
+Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
+  by minotaur.apache.org with SMTP; 2 Jun 2004 21:13:43 -0000
+Received: (qmail 35227 invoked by uid 500); 2 Jun 2004 21:14:00 -0000
+Delivered-To: apmail-brondsem@apache.org
+Received: (qmail 35134 invoked by uid 99); 2 Jun 2004 21:14:00 -0000
+Received: from [209.204.146.35] (HELO smtp1.oreilly.com) (209.204.146.35)
+  by apache.org (qpsmtpd/0.27.1) with ESMTP; Wed, 02 Jun 2004 14:14:00 -0700
+Received: from cindyw.oreilly.com (dhcp-172-24-30-220.west.ora.com
+    [172.24.30.220])
+	by smtp1.oreilly.com (Postfix) with ESMTP
+	id 93D2E14A1C; Wed,  2 Jun 2004 14:13:39 -0700 (PDT)
+Message-Id: <4.3.2.7.2.20040602140354.00c45838@pop3.west.ora.com>
+X-Sender: cindyw@pop3.west.ora.com
+X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
+Date: Wed, 02 Jun 2004 14:13:01 -0700
+To: Dave Brondsema <brondsem@apache.org>, permissions@oreilly.com
+From: Cindy Wetterlund <cindyw@oreilly.com>
+Subject: Re: using code in an Apache project
+Cc: simonstl@oreilly.com
+In-Reply-To: <1085402426.40b1ed3a86ef4@secure.solidusdesign.com>
+Mime-Version: 1.0
+Content-Type: text/plain; charset="us-ascii"; format=flowed
+X-Virus-Checked: Checked
+X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N
+X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on 
+	ferrari.solidusdesign.com
+X-Spam-Level: 
+X-Spam-Status: No, hits=0.0 required=4.0 tests=none autolearn=no version=2.63
+
+Hi Dave,
+
+Thanks for your mail and interest.
+
+Yes, you have O'Reilly's permission (and the author's who
+was happy to hear of your interest) to re-use some of the code
+from XSLT Cookbook for the Forrest project.
+
+It would be great if you would cite the usage by acknowledging
+the original title/author with a standard credit line.
+
+Thanks Dave.
+
+Cindy
+
+At 08:40 AM 5/24/2004 -0400, Dave Brondsema wrote:
+
+>The Apache Forrest project (http://xml.apache.org/forrest/) would like to use
+>some of the code included in the XSLT Cookbook.  Forrest is licensed under the
+>Apache License 2.0 (http://www.apache.org/licenses/)
+>
+>According to 
+>http://www.oreilly.com/pub/a/oreilly/ask_tim/2001/codepolicy.html,
+>I think this would be ok.  However, we would feel more comfortable if explicit
+>permission was given for us to use and distribute your code as part of our 
+>project.
+>
+>Personally, I would suggest that O'Reilly code be licensed under a known Open
+>Source license, such as the Apache License.  This would make it clear to all
+>what is allowed and what is not.
+>
+>Thanks!
+>
+>--
+>Dave Brondsema : brondsem@apache.org
+>http://www.brondsema.net  : personal
+>http://www.splike.com  : programming
+
+Cindy Wetterlund
+International Rights and
+Licensing Manager
+cindyw@oreilly.com
+

Mime
View raw message