Browse files

License moved to BSD

  • Loading branch information...
antirez committed Nov 30, 2009
1 parent 89dbed7 commit 7be3608cb7569be353d0d38e0f35fcb13cbe4521
Showing with 12 additions and 388 deletions.
  1. +7 −347 COPYING
  2. +1 −1 Makefile
  3. +1 −37 README
  4. +1 −1 aht.h
  5. +1 −1 antigetopt.c
  6. +1 −1 visitors.c

Large diffs are not rendered by default.

Oops, something went wrong.
@@ -1,7 +1,7 @@
# Makefile for visitors
# Copyright (C) 2004 Salvatore Sanfilippo <>
# All Rights Reserved
-# Under the GPL license version 2
+# Under the BSD license (see COPYING)
DEBUG?= -g
CFLAGS?= -O2 -Wall -W
@@ -57,43 +57,7 @@ Without this code the screen resolution report will not work.
-Unfortunately I can't accept source code written by external contributors
-without a "Copyright Assignment", because I'm not sure I'll take the
-GPL license in the future, instead I may switch to BSD, or even to create
-a commercial version of Visitors (very unlikely). Because I don't like
-the idea of "Copyright Assignment" at all I'll be happy to implement
-any useful feature in Visitors for you so: Please send suggestions
-and bug reports. Thank you.
-There is some kind of problem with the GPL and small projects, when
-you can expect an amount of help by external contributors that is so
-little that's not worth the "License Lock-In" problem. What I mean
-is that Visitors is under the GPL license, and I'm not sure I'll be
-happy with this license forever. For example I may want to change
-the license using the BSD in the future, it's worth to lost the
-ability to do it just to accept some patch?
-When it's a big project and it is very likely to get a lot of contribs
-all is ok, I start directly with the BSD license. An example of this
-is the "Jim Interpreter", an open source program I started to develop
-after Visitors itself (see You get a lot of help,
-the project gets bigger/better, still if you want you can use the
-code for your commercial stuff (it's BSD), and everybody can do it.
-Also note that nor the GPL accepting patches, nor the BSD allow
-the open source developer to create software that is available in
-two flawours: one free, and one commercial. BSD allows this but
-everybody can create another commercial product based on the same
-code: not fair. GPL allows this if you don't accept patches, that's
-also not good given that after all the code contributed will stay
-anyway in the GPL product forever.
-This is why I don't accept patches for Visitors, and why I'm highly
-unhappy with this solution. If you have some idea or comment please
-feel free to send it to antirez (at) gmail (dot) org.
+Please send patches, I'll merge it, but be aware the project is now licensed under the BSD license, it's no longer GPLed.
2 aht.h
@@ -1,7 +1,7 @@
/* An implementation of hash tables:
* Copyright(C) 2000-2004 by Salvatore Sanfilippo <>
- * This software is under the GNU GPL license
+ * This software is under the BSD license
#include <sys/types.h>
@@ -1,6 +1,6 @@
/* antigetopt -- a getopt replacement
* Copyright(C) 2001 Salvatore Sanfilippo <>
- * This software is released under the GPL license
+ * This software is released under the BSD license (see COPYING)
* see the COPYING file for more information */
/* $Id: antigetopt.c,v 2005/10/02 22:44:47 antirez Exp $ */
@@ -3,7 +3,7 @@
* Copyright (C) 2004-2006 Salvatore Sanfilippo <>
* All Rights Reserved.
- * This software is released under the terms of the GPL license version 2.
+ * This software is released under the terms of the BSD license.
* Read the COPYING file in this distribution for more details. */
#include <stdio.h>

0 comments on commit 7be3608

Please sign in to comment.