=======
LICENSE
=======

The following contributors hold Copyright (c) over their respective portions 
of code and documentation:

The main portion of initial code (~95%); Current maintainer: 

    Pavel Cisar <pcisar@ibphoenix.cz>

Contributors:

[Initial trace API & nbackup support; Python 3 support]
    Philippe Makowski <pmakowski@espelida.com>

Some code in inital version is Python code from KInterbasDB 3.3.0. 
As it's very hard to find out who exactly was the original author of used code, 
here is the full list of KInterbasDB contributors:

[Author of original version; maintained through version 2.0:]

    1998-2001 [alex] Alexander Kuznetsov <alexan@users.sourceforge.net>

[Author of ~90% of current code, most of current documentation; maintained through version 3.3:]

    2002-2007 [dsr] David S. Rushby <woodsplitter@rocketmail.com>

[Finishing touch to v3.3; New Documentation; Current maintainer:]

    2008-2011 [paci] Pavel Cisar <pcisar@ibphoenix.cz>

[Significant Contributors:]

    2001-2002 [maz] Marek Isalski <kinterbasdb@maz.nu>

        Marek made important first steps in removing the limitations of version 2.0 
        in preparation for version 3.0.

    2001 [eac] Evgeny A. Cherkashin <eugeneai@icc.ru>

        Evgeny wrote the first version of the distutils build script, 
        which was included in a 2.x point release.

    2001-2002 [janez] Janez Jere <janez.jere@void.si>

        Janez contributed several bugfixes, including fixes for the date and time 
        parameter conversion code in preparation for version 3.0.

Permission to use, copy, modify, and distribute this software and its documentation 
for any purpose and without fee or royalty is hereby granted, provided that the above 
copyright notice appears in all copies and that both the copyright notice and 
this permission notice appear in supporting documentation or portions thereof, 
including modifications, that you make.

The authors disclaim all warranties with regard to this software, including all 
implied warranties of merchantability and fitness. In no event shall any author 
be liable for any special, indirect or consequential damages or any damages whatsoever 
resulting from loss of use, data or profits, whether in an action of contract, 
negligence or other tortious action, arising out of or in connection with the use 
or performance of this software.
