summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRobin H. Johnson <robbat2@gentoo.org>2015-08-08 13:49:04 -0700
committerRobin H. Johnson <robbat2@gentoo.org>2015-08-08 17:38:18 -0700
commit56bd759df1d0c750a065b8c845e93d5dfa6b549d (patch)
tree3f91093cdb475e565ae857f1c5a7fd339e2d781e /licenses/Alasir
downloadgentoo-56bd759df1d0c750a065b8c845e93d5dfa6b549d.tar.gz
gentoo-56bd759df1d0c750a065b8c845e93d5dfa6b549d.tar.bz2
gentoo-56bd759df1d0c750a065b8c845e93d5dfa6b549d.zip
proj/gentoo: Initial commit
This commit represents a new era for Gentoo: Storing the gentoo-x86 tree in Git, as converted from CVS. This commit is the start of the NEW history. Any historical data is intended to be grafted onto this point. Creation process: 1. Take final CVS checkout snapshot 2. Remove ALL ChangeLog* files 3. Transform all Manifests to thin 4. Remove empty Manifests 5. Convert all stale $Header$/$Id$ CVS keywords to non-expanded Git $Id$ 5.1. Do not touch files with -kb/-ko keyword flags. Signed-off-by: Robin H. Johnson <robbat2@gentoo.org> X-Thanks: Alec Warner <antarus@gentoo.org> - did the GSoC 2006 migration tests X-Thanks: Robin H. Johnson <robbat2@gentoo.org> - infra guy, herding this project X-Thanks: Nguyen Thai Ngoc Duy <pclouds@gentoo.org> - Former Gentoo developer, wrote Git features for the migration X-Thanks: Brian Harring <ferringb@gentoo.org> - wrote much python to improve cvs2svn X-Thanks: Rich Freeman <rich0@gentoo.org> - validation scripts X-Thanks: Patrick Lauer <patrick@gentoo.org> - Gentoo dev, running new 2014 work in migration X-Thanks: Michał Górny <mgorny@gentoo.org> - scripts, QA, nagging X-Thanks: All of other Gentoo developers - many ideas and lots of paint on the bikeshed
Diffstat (limited to 'licenses/Alasir')
-rw-r--r--licenses/Alasir48
1 files changed, 48 insertions, 0 deletions
diff --git a/licenses/Alasir b/licenses/Alasir
new file mode 100644
index 000000000000..90582b3a750f
--- /dev/null
+++ b/licenses/Alasir
@@ -0,0 +1,48 @@
+
+ The Alasir Licence
+
+
+ This is a free software. It's provided as-is and carries absolutely no
+warranty or responsibility by the author and the contributors, neither in
+general nor in particular. No matter if this software is able or unable to
+cause any damage to your or third party's computer hardware, software, or any
+other asset available, neither the author nor a separate contributor may be
+found liable for any harm or its consequences resulting from either proper or
+improper use of the software, even if advised of the possibility of certain
+injury as such and so forth.
+
+ The software isn't a public domain, it's a copyrighted one. In no event
+shall the author's or a separate contributor's copyright be denied or violated
+otherwise. No copyright may be removed unless together with the code
+contributed to the software by a holder of the respective copyright. A
+copyright itself indicates the rights of ownership over the code contributed.
+Back and forth, the author is defined as the one who holds the oldest
+copyright over the software. Furthermore, the software is defined as either
+source or binary computer code, which is organised in the form of a single
+computer file usually.
+
+ The software (the whole or a part of it) is prohibited from being sold or
+leased in any form or manner with the only possible exceptions:
+
+a) money may be charged for a physical medium used to transfer the software;
+b) money may be charged for optional warranty or support services related to
+ the software.
+
+ Nevertheless, if the software (the whole or a part of it) is desired to
+become an object of sale or lease (the whole or a part of it), then a separate
+non-exclusive licence agreement must be negotiated from the author. Benefits
+accrued should be distributed between the contributors or likewise at the
+author's option.
+
+ Whenever and wherever the software is distributed, in either source or
+binary form, either in whole or in part, it must include the complete
+unchanged text of this licence agreement unless different conditions have been
+negotiated. In case of a binary-only distribution, the names of the copyright
+holders must be mentioned in the documentation supplied with the software.
+This is supposed to protect rights and freedom of those who have contributed
+their time and labour to free software development, because otherwise the
+development itself and this licence agreement are of a very little sense.
+
+ Nothing else but this licence agreement grants you rights to use, modify
+and distribute the software. Any violation of this licence agreement is
+recognised as an action prohibited by an applicable legislation.