Skip to content

Instantly share code, notes, and snippets.

@gorenje

gorenje/Legal Notices.txt

Last active December 11, 2024 11:36
Show Gist options
  • Save gorenje/a775f44bb9307852911f7f3534666442 to your computer and use it in GitHub Desktop.
Save gorenje/a775f44bb9307852911f7f3534666442 to your computer and use it in GitHub Desktop.
Download ZIP
Legal Notice found on iPhones & iPads containing many Open Source licenes and authors
Raw
README.txt
View raw

(Sorry about that, but we can’t show files that are this big right now.)

@gorenje
Copy link
Author

gorenje commented Dec 11, 2024

Some highlights:

"THE BEER-WARE LICENSE" (Revision 42):
  <[email protected]> wrote this file.  As long as you retain this notice you can do whatever you want with this stuff. If we meet some day, and you think this stuff is worth it, you can buy me a beer in return.  Poul-Henning Kamp

Richard Hipp ( SQLite )
SQLite Copyright 
All of the deliverable code in SQLite has been dedicated to the public domain by the authors. All code authors, and representatives of the companies they work for, have signed affidavits dedicating their contributions to the public domain and originals of those signed affidavits are stored in a firesafe at the main offices of Hwaci. Anyone is free to copy, modify, publish, use, compile, sell, or distribute the original SQLite code, either in source code form or as a compiled binary, for any purpose, commercial or non-commercial, and by any means.
The previous paragraph applies to the deliverable code in SQLite - those parts of the SQLite library that you actually bundle and ship with a larger application. Portions of the documentation and some code used as part of the build process might fall under other licenses. The details here are unclear. We do not worry about the licensing of the documentation and build code so much because none of these things are part of the core deliverable SQLite library.
All of the deliverable code in SQLite has been written from scratch. No code has been taken from other projects or from the open internet. Every line of code can be traced back to its original author, and all of those authors have public domain dedications on file. So the SQLite code base is clean and is uncontaminated with licensed code from other projects.
Obtaining an Explicit License to Use SQLite
Even though SQLite is in the public domain and does not require a license, some users want to obtain a license anyway. Some reasons for obtaining a license include:
* You are using SQLite in a jurisdiction that does not recognize the public domain.
* You are using SQLite in a jurisdiction that does not recognize the right of an author to dedicate their work to the public domain.
* You want to hold a tangible legal document as evidence that you have the legal right to use and distribute SQLite.
* Your legal department tells you that you have to purchase a license.
If you feel like you really have to purchase a license for SQLite, Hwaci, the company that employs the architect and principal developers of SQLite, will sell you one. Contributed Code
In order to keep SQLite complete free and unencumbered by copyright, other contributors to the SQLite code base are asked to likewise dedicate their contributions to the public domain. If you want to send a patch or enhancement for possible inclusion in the SQLite source tree, please accompany the patch with the following statement: The author or authors of this code dedicate any and all copyright interest in this code to the public domain. We make this dedication for the benefit of the public at large and to the detriment of our heirs and successors. We intend this dedication to be an overt act of relinquishment in perpetuity of all present and future rights this code under copyright law.
We are not able to accept patches or changes to SQLite that are not accompanied by a statement such as the above. In addition, if you make changes or enhancements as an employee, then a simple statement such as the above is insufficient. You must also send by surface mail a copyright release signed by a company officer. A signed original of the copyright release should be mailed to: Hwaci, 6200 Maple Cove Lane, Charlotte, NC 28269, USA
A template copyright release is available in PDF or HTML. You can use this release to make future changes.

Andrew Tridgell ( spamsum )
Copyright © 2002 Andrew Tridgell
[Apple Note: Apple elects to license this file under the Artistic License.  The original code for this file may be found at https://web.archive.org/web/20080228215157/http://samba.org/ftp/unpacked/junkcode/spamsum/]
The "Artistic License"
...

Larry Wall ( Perl Kit )
Copyright © 1989-1997 Larry Wall. All rights reserved.
This program is free software; you can redistribute it and/or modify it under the terms of either: a) the GNU General Public License as published by the Free Software Foundation; either version 1, or (at your option) any later version, or b) the Artistic License which comes with this Kit.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See either the GNU General Public License or the Artistic License for more details.
You should have received a copy of the Artistic License with this Kit, in the file named Artistic.  If not, I'll be glad to provide one.  You should also have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
For those of you that choose to use the GNU General Public License, my interpretation of the GNU General Public License is that no Perl script falls under the terms of the GPL unless you explicitly put said script under the terms of the GPL yourself.  Furthermore, any object code linked with perl does not automatically fall under the terms of the GPL, provided such object code only adds definitions of subroutines and variables, and does not otherwise impair the resulting interpreter from executing any standard Perl script.  I consider linking in C subroutines in this manner to be the moral equivalent of defining subroutines in the Perl language itself.  You may sell such an object file as proprietary provided that you provide or offer to provide the Perl source, as specified by the GNU General Public License.  (This is merely an alternate way of specifying input to the program.)  You may also sell a binary produced by the dumping of a running Perl script that belongs to you, provided that you provide or offer to provide the Perl source as specified by the GPL.  (The fact that a Perl interpreter and your code are in the same binary file is, in this case, a form of mere aggregation.)  This is my interpretation of the GPL.  If you still have concerns or difficulties understanding my intent, feel free to contact me.  Of course, the Artistic License spells all this out for your protection, so you may prefer to use that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment