SILC Toolkit license change

Hello,

The SILC Toolkit license is changing.  From SILC Toolkit 1.0 and onward 
the SILC Toolkit will also be BSD licensed to allow easier integration to 
commercial products.  This email is sent to ask all possible contributors 
whether they are willing to accept the license change.  I earlier sent 
email to contributors listed in CREDITS file.  If you received that email, 
you should reply to that email, instead of this one.

If you have not contributed anything, do not reply to this email.  If you 
think you have contributed to the SILC Toolkit answer the question:

Are you willing to change the license of your contribution from GNU GPL to 
revised BSD license (http://www.opensource.org/licenses/bsd-license.php)?

What you will need to do is to reply in this email either saying:

    "Yes, I accept license change from GNU GPL to revised BSD"

or

    "No, I do not accept license change from GNU GPL to revised BSD"

You will need to reply to this email.  Saying Yes or No online on SILCNet 
is not enough.  You have one (1) week from today (2005/05/01) to answer to
this email.

NOTE:  This license change affects only SILC Toolkit.  SILC Client, SILC 
Server, or any other distribution released by SILC Project is NOT affected 
(anything under apps/ subdirectory is not affected).  In terms of 
contributed code, if you have contributed code into any configuration 
files, Makefiles, or any documentation file, or any source file under lib/ 
subdirectory, and/or includes/ subdirectory in the CVS source tree, then 
your answer to this email is necessary.

FAQ:

Q: Why the license change?

A: Because I have promised to make SILC Toolkit more accessible in commercial 
use.


Q: Why BSD license?

A: I had long talks with FSF and to make any other license compatible with GPL 
and LGPL, which I require, the end result is that the license would be very 
close to BSD license.  In the end, I decided to go with BSD instead of going 
through long process to come up a new suitable license.


Q: What happens if I do not accept the license change?

A: One of the following will happen in that case:

    1. Your contributed code will be replaced with other free implementation
       of equivalent code.

    2. The code you have contributed will be rewritten from scratch.

    3. Your contributed code will be entirely removed from the SILC Toolkit.

    If you answer No, then I will try to determine the code you have
    contributed, and then decide one of the three choices listed above.  If
    your contribution is a "one-liner" (ie. one line of code or other typo
    fix, etc.), I will _ignore_ your No answer, and consider the code as
    fair-use.


Q: Do I have to digitally sign my reply email?

A: No you do not, however, you may do so if you wish.


 	Pekka
________________________________________________________________________
  Pekka Riikonen                                 priikone at silcnet.org
  Secure Internet Live Conferencing (SILC)       http://silcnet.org/
__________________________________________________________________
Info:    https://lists.silcnet.org/mailman/listinfo/silc-announce
Archive: https://lists.silcnet.org/pipermail/silc-announce
FAQ:     http://silcnet.org/support/faq/