Difference between revisions of "Who made Geeklog?"

From GeeklogWiki
Jump to: navigation, search
m (getting rid of the "1.x" ...)
m (new AptitudeCMS URL)
Line 1: Line 1:
 
Geeklog was originally used to run the SecurityGeeks and NewsGeeks websites, and has since been released under the GNU General Public License (version 2). It is a bona fide Open Source / Free Software project. The template code Geeklog uses is from PHPLib, however, which is under the LGPL.
 
Geeklog was originally used to run the SecurityGeeks and NewsGeeks websites, and has since been released under the GNU General Public License (version 2). It is a bona fide Open Source / Free Software project. The template code Geeklog uses is from PHPLib, however, which is under the LGPL.
  
Geeklog was originally created by Jason Whittenburg, but like all good open source projects, depends on the community. Geeklog is currently maintained by Dirk Haun whilst Tony Bibbs focuses on [http://www.apteno.net/AptitudeCMS/trac/ AptitudeCMS] (formerly ''Geeklog 2'').
+
Geeklog was originally created by Jason Whittenburg, but like all good open source projects, depends on the community. Geeklog is currently maintained by Dirk Haun whilst Tony Bibbs focuses on [http://www.aptitudecms.org/ AptitudeCMS] (formerly ''Geeklog 2'').
  
 
Thanks for your continued support, and let us know what we can do to make Geeklog better.
 
Thanks for your continued support, and let us know what we can do to make Geeklog better.

Revision as of 18:19, 30 October 2009

Geeklog was originally used to run the SecurityGeeks and NewsGeeks websites, and has since been released under the GNU General Public License (version 2). It is a bona fide Open Source / Free Software project. The template code Geeklog uses is from PHPLib, however, which is under the LGPL.

Geeklog was originally created by Jason Whittenburg, but like all good open source projects, depends on the community. Geeklog is currently maintained by Dirk Haun whilst Tony Bibbs focuses on AptitudeCMS (formerly Geeklog 2).

Thanks for your continued support, and let us know what we can do to make Geeklog better.