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

1 files changed, 58 insertions, 0 deletions

diff --git a/licenses/SixXS b/licenses/SixXS
new file mode 100644
index 000000000000..b8e72ac69f3c
--- /dev/null
+++ b/licenses/SixXS
@@ -0,0 +1,58 @@
+AICCU LICENSE
+~~~~~~~~~~~~~
+
+For the quick reader this is a slightly modified BSD license:
+ - names changed from Regents/University to SixXS.
+ - point 3 -'written', for us an email will suffice.
+ - point 4 and 5 added.
+
+Basically we thus allow anybody to use it in any way, but we would like
+to be notified when you are using it for not connecting to SixXS.
+The meaning of 'SHOULD' is described in IETF's RFC 2119 / BCP 14.
+--
+
+Copyright (C) SixXS
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions
+are met:
+1. Redistributions of source code must retain the above copyright
+   notice, this list of conditions and the following disclaimer.
+2. Redistributions in binary form must reproduce the above copyright
+   notice, this list of conditions and the following disclaimer in the
+   documentation and/or other materials provided with the distribution.
+3. Neither the name of SixXS nor the names of its contributors
+   may be used to endorse or promote products derived from this software
+   without specific prior permission.
+4. One should not remove any reference to, or logo of, SixXS.
+5. When the software is altered to not use SixXS services, one is kindly
+   asked to notify SixXS of this by sending an email to the SixXS Staff
+   at info@sixxs.net, containing at least the following details:
+   8<--------
+   Organisation : Organisation Name
+   Email        : mailbox@example.com
+   Website      : http://www.example.com
+   is using software <Software Name> for:
+   <
+    description of:
+       the usage
+       the reason why it was modified
+   >
+   -------->8
+   Additional information details may of course be provided.
+   We request this to be able to know why people would choose not to
+   use the services provided by SixXS and the participating ISP's.
+
+THIS SOFTWARE IS PROVIDED BY SIXXS AND CONTRIBUTORS ``AS IS'' AND
+ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+ARE DISCLAIMED.  IN NO EVENT SHALL SIXXS OR CONTRIBUTORS BE LIABLE
+FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+SUCH DAMAGE.
+